diff --git a/marked/Rel-16/23_series/23011/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23011/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3c8cba2de5f544b1618d8290980a7a7cfed2563 --- /dev/null +++ b/marked/Rel-16/23_series/23011/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c02a9f66376da844b478b46932fe78993f1a074ed6fb38c03576d56fda0fcaca +size 72392 diff --git a/marked/Rel-16/23_series/23011/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23011/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e3de48cc052d57620e7a62953b6c28b4b4c4ef7 --- /dev/null +++ b/marked/Rel-16/23_series/23011/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd32836a0d86530c9c0cd20b2e560908393c336d6a784dc49f8143b65e83033f +size 95383 diff --git a/marked/Rel-16/23_series/23011/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23011/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0cb500a41742f5490eeffcf968cc5a694c0a11b --- /dev/null +++ b/marked/Rel-16/23_series/23011/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:398c14d3a08f0e13478c003ad984c0680dd98d2339f52b5efb4b94c94f0a3341 +size 55544 diff --git a/marked/Rel-16/23_series/23011/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23011/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5686fc9cecda226a984e50825ae3f6a34a10cd5 --- /dev/null +++ b/marked/Rel-16/23_series/23011/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99efebec7217c45d9fb4370308eb5190e2303befc9f3548e60e67db341ce4232 +size 109483 diff --git a/marked/Rel-16/23_series/23011/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23011/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..807435ee6ec8a8fdb4fca8e4f9ff968da0b33433 --- /dev/null +++ b/marked/Rel-16/23_series/23011/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66bef86c695f514181fe1a40c661c50f684df2c9e4fbf2c422a664c1a399628b +size 100590 diff --git a/marked/Rel-16/23_series/23011/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23011/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..462bd0ba030136503e71b307e88daad2f5ac011a --- /dev/null +++ b/marked/Rel-16/23_series/23011/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4300fa0c61f11db19148d7ee3f49852590b4b8773195aa691c675f314dc74457 +size 81591 diff --git a/marked/Rel-16/23_series/23011/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23011/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8fe10d771c72b2c5877e44261121f74728f404b --- /dev/null +++ b/marked/Rel-16/23_series/23011/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:026dd67e3b4e2ae60991e9dafb12b9fa7926779d73c5759bd9bee8a09c1d6bef +size 54919 diff --git a/marked/Rel-16/23_series/23011/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23011/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..576ea6f9845f5d8ae8d94249d8edc8547b67e1ee --- /dev/null +++ b/marked/Rel-16/23_series/23011/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d53e43e0fe4837967f0291d2e46f5c0456a99bd7313f512a37d1aae7ed178647 +size 93619 diff --git a/marked/Rel-16/23_series/23011/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23011/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a3261094a8ca9e222b9e255c72779e310097190 --- /dev/null +++ b/marked/Rel-16/23_series/23011/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:335f579afe7fea789499fd62a5814380e10b82eccda0c622d21c7e6030c548ea +size 56424 diff --git a/marked/Rel-16/23_series/23011/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23011/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d3afa5f9922e42521442df06cde7aac624cd5c90 --- /dev/null +++ b/marked/Rel-16/23_series/23011/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b06b383b4f66b762d0f29c0501153a5499ca8da5229338a060b5acc55460a91 +size 57373 diff --git a/marked/Rel-16/23_series/23011/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23011/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d3fe209aef3f197b8828b38aac4c6cb78973238 --- /dev/null +++ b/marked/Rel-16/23_series/23011/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:524834912776a0269c21515856b0ec470b08722d40780be3c88dc0280ec8d876 +size 126908 diff --git a/marked/Rel-16/23_series/23011/raw.md b/marked/Rel-16/23_series/23011/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1b3c7e015c9b6850053eaa43e27f8a31819d0718 --- /dev/null +++ b/marked/Rel-16/23_series/23011/raw.md @@ -0,0 +1,655 @@ + + + + + + +# --- Contents + +| | | +|-------------------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 1.1 References ..... | 5 | +| 1.2 Abbreviations ..... | 6 | +| 2 Activation, deactivation, registration, erasure, interrogation and invocation ..... | 6 | +| 2.1 General ..... | 6 | +| 2.1.1 Definition of "state vectors" ..... | 7 | +| 2.1.2 Handling of service states at the HLR..... | 8 | +| 2.1.2.1 Encoding of SS-Status ..... | 8 | +| 2.1.2.2 Invocation of services at the HLR ..... | 8 | +| 2.1.3 Handling of SS-Status at the VLR or the SGSN ..... | 9 | +| 2.1.3.1 Invocation of services at the VLR or the SGSN ..... | 9 | +| 2.1.3.2 Interrogation of the service at the VLR and notifications from VLR..... | 9 | +| 2.1.4 Handling of SS-Status at the MS..... | 9 | +| 2.2 Handling of call independent SS procedures with respect to basic service groups ..... | 9 | +| 2.3 Exceptional handling of basic service codes..... | 10 | +| 3 Password handling ..... | 14 | +| 3.1 General ..... | 14 | +| 3.2 Registration of password..... | 20 | +| 3.3 Use of password ..... | 20 | +| 3.4 Deactivation ..... | 22 | +| 4 Supplementary service data management..... | 23 | +| 5 Format of description ..... | 23 | +| Annex A (informative): Change history..... | 24 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document describes the general aspects on how supplementary services 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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- 1 Scope + +The present document describes the general aspects on how supplementary services in the 3GPP system are realised from a technical point of view. + +Description of technical realisation for specific supplementary services can be found in 3GPP TS 23.072, 230.8x and 230.9x-series technical specifications. + +All supplementary services may require signalling on the radio path. Signalling procedures and messages used are defined in the 3GPP TS 24.072, 24.08x and 24.09x-series of technical specifications. + +For some supplementary services information needs to be transferred between the Home Location Register (HLR), the Visitor Location Register (VLR), the Mobile services Switching Centre (MSC) and the Serving GPRS Support Node (SGSN). Signalling procedures for such information transfer are defined in 3GPP TS 29.002. + +Definitions and descriptions of supplementary services are given in the 3GPP TS 22.072, 22.08x and 22.09x-series of technical specifications. + +Definitions are given in 3GPP TS 22.004.. + +NOTE: The technical specifications on the technical realisation of supplementary services do not distinguish between subscriber, user and customer, since all three do not fully cover the textual needs. Generally the term "subscriber" is used, even if this person is not having the subscription. + +## 1.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 22.004: "General on Supplementary Services". +- [3] 3GPP TS 22.030: "Man-Machine Interface (MMI) of the Mobile Station (MS)". +- [4] 3GPP TS 23.081: "Line Identification Supplementary Services - Stage 2". +- [5] 3GPP TS 23.082: "Call Forwarding (CF) Supplementary Services - Stage 2". +- [6] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Service - Stage 2". +- [7] 3GPP TS 23.084: "MultiParty (MPTY) Supplementary Service - Stage 2". +- [8] 3GPP TS 23.085: "Closed User Group (CUG) Supplementary Service - Stage 2". +- [9] 3GPP TS 23.086: "Advice of Charge (AoC) Supplementary Service - Stage 2". +- [10] 3GPP TS 23.088: "Call Barring (CB) Supplementary Service - Stage 2". +- [11] 3GPP TS 23.090: "Unstructured Supplementary Service Data (USSD) - Stage 2". +- [12] 3GPP TS 24.080: "Mobile radio Layer 3 Supplementary Service specification - Formats and coding". +- [13] 3GPP TS 24.081: "Line Identification Supplementary Service - Stage 3". + +- [14] 3GPP TS 24.082: "Call Forwarding Supplementary Service - Stage 3". +- [15] 3GPP TS 24.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Service - Stage 3". +- [16] 3GPP TS 24.084: "MultiParty (MPTY) Supplementary Service - Stage 3". +- [17] 3GPP TS 24.085: "Closed User Group (CUG) Supplementary Service - Stage 3". +- [18] 3GPP TS 24.086: "Advice of Charge (AoC) Supplementary Service - Stage 3". +- [19] 3GPP TS 24.088: "Call Barring (CB) Supplementary Service - Stage 3". +- [20] 3GPP TS 24.090: "Unstructured Supplementary Service Data (USSD) - Stage 3". +- [21] 3GPP TS 29.002: "Mobile Application Part (MAP)". + +## 1.2 Abbreviations + +Abbreviations used in the present document are listed in 3GPP TS 21.905. + +# --- 2 Activation, deactivation, registration, erasure, interrogation and invocation + +## 2.1 General + +Activation, deactivation, registration, erasure, interrogation and invocation are defined independently from a particular supplementary service. Whether they are applicable to a particular supplementary service or not is defined in the corresponding 3GPP TS 23.08x and 23.09x-series. Activation, deactivation, registration, erasure and invocation are applicable for CS domain. For PS domain only invocation of call barring of SMS is applicable. + +The invocation of a supplementary service is executed as described in the corresponding stage 2 description and always includes an MSC and a location register for CS domain and an SGSN for PS domain. + +When an MSC receives a request for either activation/deactivation or registration/erasure or an interrogation, it invokes one of the following procedures. + +The MSC then can: + +- contact only the current VLR (e.g. interrogation of a call forwarding conditional supplementary service); +- contact only the HLR (e.g. interrogation of the supplementary service call forwarding unconditional); +- contact the HLR, after which the HLR updates the VLR (e.g. registration of a forwarding number for a conditional call forwarding supplementary service). + +Which of the above listed procedures is applied for a call independent supplementary service operation is described in the corresponding 3GPP TS 23.08x and 23.09x -series. + +Successful activation, deactivation, registration and erasure change the service state at the HLR. These transitions (if applicable to a particular service) are defined in the 3GPP TS 23.08x and 23.09x -series. Note that the HLR may also change the service state due to "HLR Induction" (see subclause 2.1.1). + +In connection with supplementary service operations the served subscriber or remote subscribers may get notifications from the network. . + +If an SGSN receives a request for registration, erasure, activation, deactivation, interrogation or change of password, it shall return an error to the MS. + +### 2.1.1 Definition of "state vectors" + +In order to provide a tool to define service states the concept of a "state vector" is introduced. The state vector is used to represent the state of the service in terms of four variables: + +- 1) Provisioning State, +possible values are "Provisioned" or "Not Provisioned"; +- 2) Registration State, +possible values are "Registered", "Erased", or "Not Applicable"; +- 3) Activation State, +possible values are "Not Active", "Active and Operative" or "Active and Quiescent"; +- 4) HLR Induction State, +possible values are "Induced" or "Not Induced". + +The state vector represents the state of the service by using all four variables together. The state vector is represented using the notation: + +*(Provisioning State, Registration State, Activation State, HLR Induction State)* + +e.g.: (Provisioned, Registered, Not Active, Not Induced). + +Note that the state vector is a logical (not a physical) representation of the service state. Note also that though some parts of the state vector are similar to elements of SS-Status the mapping between the state vector and SS-Status is not one to one. The use of state vectors is not intended to specify any particular implementation internally in a node. There is a relationship specified between the state vector and parts of the transfer syntax. This relationship is not a direct one-to-one mapping. + +The following text specifies the semantics of each variable in the state vector. + +The three variables "Provisioning State", "Registration State" and "Activation State" are used to represent the state of the service according to the normal behaviour based on service provider and user actions. + +The "HLR Induction State" records whether or not the HLR has temporarily induced the service (e.g. if the VLR does not support CUG, the HLR may induce an outgoing barring service). The Provisioning State, Registration State and Activation State are not affected by HLR induction of a service. + +#### Provisioning State + +- has value "provisioned", if the subscriber has a subscription to the service; +- has value "Not Provisioned" otherwise. + +#### Registration State + +- has value "Not Applicable", if registration is not applicable to the service; +- has value "Registered", if registration is applicable, and there is registration data available; +- has value "Erased" otherwise. + +#### Activation State + +- has value "Active and Operative", if the service is in a state where it can be invoked (and this is not due to HLR induction); +- has value "Active and Quiescent", if the service is in a state where it cannot be invoked, but where it will automatically move to the "Active and Operative" state when conflicting conditions are removed; +- has value "Not Active" otherwise. + +#### HLR Induction State + +- has the value "Induced" if the HLR has induced the service (e.g. if the VLR does not support CUG, the HLR may induce an outgoing barring service); +- has the value "Not Induced" otherwise. + +For further information about how HLR induction applies to particular services refer to the 3GPP TS 23.08x and 23.09x-series. + +### 2.1.2 Handling of service states at the HLR + +Valid states (represented by state vectors) are defined on a service-by-service basis in the 3GPP TS 23.08x and 23.09x -series. For each service the set of valid states represents the logical states that can exist in the HLR. The HLR contains the master copy of service state information. + +#### 2.1.2.1 Encoding of SS-Status + +To send service state information to the VLR, the SGSN or the MS, the HLR often uses the SS-Status parameter. This parameter contains four bits (referred to here as the "P bit", "R bit", "A bit" and "Q bit"). In a phase 2 context the HLR shall encode the SS-Status using the mapping defined in this subclause from the service states to SS-Status. + +If the HLR Induction State is "Not Induced" then: + +- If the Provisioning State is "Provisioned", then the P bit shall be 1, otherwise the P bit shall be 0. +- If the Registration State is "Registered", the R bit shall be 1. If the Registration State is "Not Registered" the R bit shall be 0. If the Registration State is "Not Applicable" the R bit shall be either 0 or 1. +- If the Activation State is "Active and Operative" the A bit shall be 1 and the Q bit shall be 0. If the Activation State is "Active and Quiescent" the A bit shall be 1 and the Q bit shall be 1. If the Activation State is "Not Active" the A bit shall be 0 and the Q bit shall be either 0 or 1. + +If the HLR Induction State is "Induced" then the P bit shall be 1, the R bit shall be 0 or 1, the A bit shall be 1 and the Q bit shall be 0. + +**Table 2.1: Encoding of the P, R, A and Q bits in the SS-Status parameter** + +| HLR Induction State "Not Induced" | P bit | R bit | A bit | Q bit | +|-----------------------------------------------------------------------------------|--------|---------------|-------------|---------------| +| Provisioning State "Provisioned"
"Not Provisioned" | 1
0 | | | | +| Registration State "Registered"
"Not Registered"
"Not Applicable" | | 1
0
0/1 | | | +| Activation State "Active and Operative"
"Active and Quiescent"
"Not Active" | | | 1
1
0 | 0
1
0/1 | + +| | P bit | R bit | A bit | Q bit | +|-------------------------------|-------|-------|-------|-------| +| HLR Induction State "Induced" | 1 | 0/1 | 1 | 0 | + +#### 2.1.2.2 Invocation of services at the HLR + +If the service can be invoked at the HLR (e.g. to bar an incoming call) then invocation is possible only if the Activation State is "Active and Operative". Note that the concept of HLR induction does not apply to services invoked at the HLR as the HLR can invoke the effect of these services without needing to induce them first. + +### 2.1.3 Handling of SS-Status at the VLR or the SGSN + +The VLR shall store sufficient information to support VLR based invocation, interrogation and notifications from the VLR to the MS. The SGSN shall store sufficient information to support SGSN based invocation. + +The VLR or the SGSN shall not check the internal consistency of SS-Status values received from the HLR (i.e. it shall not impose any rules relating values of some bits in SS-Status to other bits). The VLR or the SGSN shall not check that the SS-Status received from the HLR is valid according to the VLR's or SGSN's definition of the relevant service. + +#### 2.1.3.1 Invocation of services at the VLR or the SGSN + +The ability to invoke the service at the VLR (e.g. to forward a call, or create an MPTY call) is based on the A and Q bits of SS-Status. The service can only be invoked if A=1 and Q=0. Other bits in SS-Status are not relevant to invocation at the VLR. . + +The ability to invoke the service at the SGSN (i.e. to bar MO SMS submission) is based on the A bit of SS-Status. The service can only be invoked if A=1. Other bits in SS-Status are not relevant to invocation at the SGSN. + +#### 2.1.3.2 Interrogation of the service at the VLR and notifications from VLR + +If the VLR sends a notification or an interrogation result that includes an SS-Status parameter the VLR shall set the P, R, A and Q bits to the same values received from the HLR. Unless stated otherwise in individual service specifications, if the service is not provisioned and the VLR has not received a value for SS-Status from the HLR then if the VLR has to send SS-Status for that service it shall set the P, R, A, and Q bits to 0. + +### 2.1.4 Handling of SS-Status at the MS + +The MS has to interpret SS-Status values received from the network. The following information is provided as guidance as to how to treat the SS-Status information: + +- The P, A and Q bits are relevant for all phase 2 supplementary services for which the MS may receive SS-Status information from the network. +- The value of the R bit is only relevant if registration is applicable to the supplementary service the SS-Status relates to. +- The A and Q bits shall be treated as a pair with the following meanings assumed: + - If A=1 and Q=0, then the service is "Active and Operative"; + - If A=1 and Q=1, then the service is "Active and Quiescent"; + - If A=0 and Q=0 or 1, then the service is deactivated. +- The MS may assume that if P=0 then the service is also deactivated (and if registration is applicable erased). +- If registration is applicable to the service then the MS may assume that if R=0 then the service is also deactivated. + +## 2.2 Handling of call independent SS procedures with respect to basic service groups + +A request for registration, erasure, activation, deactivation or interrogation of a supplementary service always refers to a basic service group. + +The basic service group may be either an elementary basic service group (defined in 3GPP TS 22.004) or a collective basic service group (defined in 3GPP TS 22.030). + +The following text and figure 2.1 describe the general handling of call independent SS procedures in the destination entity with respect to basic service groups. + +- The VLR or HLR (i.e. the destination entity) shall check the received request for general problems (see figure 2.1 sheet 2 and sheet 3). + +- In case of general error the procedure shall be terminated by sending an error towards the MS (see figure 2.1 sheet 1). +- If there is no general problem, the HLR or VLR shall split the received basic service group (BSG) into elementary basic service groups (EBSG) and continue with separate handling of each elementary basic service group (see figure 2.1 sheet 1). + +Note that the received basic service group may be an elementary basic service group. In this case splitting is not required. + +- Elementary basic service groups shall be ignored if: + - there is no basic service provisioned in the group; or + - the supplementary service is not applicable for any basic service within this elementary basic service group;(see figure 2.1 sheet 4). + +Note that in case the SS is either not provisioned or all the elementary basic service groups were ignored a general error will be returned (see above). + +For interrogation the following handling continues (see figure 2.1 sheet 4): + +- For all other elementary basic service groups the information requested will be returned to the MS and the procedure is terminated. + +For registration/erasure and activation/deactivation the following handling continues (see figure 2.1 sheet 4): + +- For all other elementary basic service groups the requested procedure will either be executed or rejected due to interaction with other supplementary services. +- If the request cannot be accepted for any of these elementary basic service groups due to interaction, the corresponding error will be returned and the procedure is terminated. +- If the request was executed for all of these elementary basic service groups an acknowledgement is returned towards the MS and the procedure is terminated. + +Note that this acknowledgement will include the same basic service group as received in the request. + +- In case the request is accepted for some but not for all of these elementary basic service groups, partial acceptance will be signalled towards the MS and the procedure will be terminated. + +The return errors for supplementary service operations and applicability of these errors are defined in 3GPP TS 24.080. Detailed description of call independent handling for a specific supplementary service is described in 3GPP TS 23.08x and 23.09x -series of technical specifications. + +## 2.3 Exceptional handling of basic service codes + +When an individual teleservice code or bearer service code is sent by an MS instead of an elementary basic service group the network shall treat such a request as a request for the corresponding elementary basic service group. + +The response to such a request shall include the elementary basic service group code of this basic service code if this is required by the protocol or application. + +![Flowchart for Process SS_REQUEST_WITH_BS_GROUP. It starts with an 'idle' state, followed by an 'SS request'. A 'general SS_request_handling' block (see sheets 2 and 3) follows. An 'error' decision point leads to an 'error' state if yes, or to 'split request to EBSG' if no. A loop follows: 'take request of first EBSG' (connector 1), 'specific SS_request_handling' (see sheet 4), and 'last EBSG' decision. If 'last EBSG' is no, 'take request of next EBSG' leads back to 'specific SS_request_handling'. If 'last EBSG' is yes, a 'successful for any EBSG' decision follows. If 'successful for any EBSG' is no, an 'error' state is reached. If 'successful for any EBSG' is yes, a 'partial acceptance' state is reached. Both 'partial acceptance' and 'error' states lead to an 'idle' state (connector 1).](5a4e62bead259c258d069fd3663ea670_img.jpg) + +**Process SS\_REQUEST\_WITH\_BS\_GROUP** 311\_211(1) + +``` +graph TD; idle1([idle]) --> SS_request[/SS request/]; SS_request --> general[general SS_request_handling]; general -.-> S23[see sheets 2 and 3]; general --> error1{error}; error1 -- yes --> error2[error]; error1 -- no --> split[split request to EBSG]; split --> take1[take request of first EBSG]; take1 --> specific[specific SS_request_handling]; specific -.-> S4[see sheet 4]; specific --> lastEBSG{last EBSG}; lastEBSG -- yes --> successful{successful for any EBSG}; lastEBSG -- no --> takeNext[take request of next EBSG]; takeNext --> specific; take1 -- 1 --> specific; successful -- yes --> partial[partial acceptance]; successful -- no --> error2; partial --> idle2([idle]); error2 --> idle2; idle2 -- 1 --> idle1; +``` + +Handling in HLR and VLR + +BS: Basic Service. +BSG: Basic Service group. +EBSG: Elementary Basic Service group. +SS: Supplementary Service. + +NOTE: Only BS and SS included in the request are relevant. + +Flowchart for Process SS\_REQUEST\_WITH\_BS\_GROUP. It starts with an 'idle' state, followed by an 'SS request'. A 'general SS\_request\_handling' block (see sheets 2 and 3) follows. An 'error' decision point leads to an 'error' state if yes, or to 'split request to EBSG' if no. A loop follows: 'take request of first EBSG' (connector 1), 'specific SS\_request\_handling' (see sheet 4), and 'last EBSG' decision. If 'last EBSG' is no, 'take request of next EBSG' leads back to 'specific SS\_request\_handling'. If 'last EBSG' is yes, a 'successful for any EBSG' decision follows. If 'successful for any EBSG' is no, an 'error' state is reached. If 'successful for any EBSG' is yes, a 'partial acceptance' state is reached. Both 'partial acceptance' and 'error' states lead to an 'idle' state (connector 1). + +**Figure 2.1 (sheet 1 of 4): Handling of call independent SS procedures with respect to basic service groups** + +![Flowchart for general_SS_request_handling. It starts with an oval connector, followed by a series of decision diamonds: 'SS supported by this entity', 'required parameter missing', 'irrelevant parameter value', 'request applicable for this SS', 'interrogation', and 'SS provisioned'. 'Yes' paths lead to connector '1'. 'No' paths lead to error boxes: 'set error unexpected data value', 'set error data missing', 'set error unexpected data value', 'set error illegal SS operation', and 'set error SS error status', all of which lead to connector '2'. Notes on the right define BS, BSG, and SS, and mention 'Handling of the entire request'.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Procedure general\_SS\_request\_handling + +311\_212(2) + +``` +graph TD; Start([ ]) --> D1{SS supported by this entity}; D1 -- yes --> D2{required parameter missing}; D1 -- no --> E1[set error unexpected data value]; D2 -- yes --> E2[set error data missing]; D2 -- no --> D3{irrelevant parameter value}; D3 -- yes --> E3[set error unexpected data value]; D3 -- no --> D4{request applicable for this SS}; D4 -- yes --> D5{interrogation}; D4 -- no --> E4[set error illegal SS operation]; D5 -- yes --> C1((1)); D5 -- no --> D6{SS provisioned}; D6 -- yes --> C1; D6 -- no --> E5[set error SS error status]; E1 --> C2((2)); E2 --> C2; E3 --> C2; E4 --> C2; E5 --> C2; +``` + +Handling of the entire request + +BS: Basic Service. +BSG: Basic Service Group. +SS: Supplementary Service. + +Flowchart for general\_SS\_request\_handling. It starts with an oval connector, followed by a series of decision diamonds: 'SS supported by this entity', 'required parameter missing', 'irrelevant parameter value', 'request applicable for this SS', 'interrogation', and 'SS provisioned'. 'Yes' paths lead to connector '1'. 'No' paths lead to error boxes: 'set error unexpected data value', 'set error data missing', 'set error unexpected data value', 'set error illegal SS operation', and 'set error SS error status', all of which lead to connector '2'. Notes on the right define BS, BSG, and SS, and mention 'Handling of the entire request'. + +Figure 2.1 (sheet 2 of 4): Handling of call independent SS procedures with respect to basic service groups + +![Flowchart for general_SS_request_handling procedure. It starts with a decision 'any BS provisioned within the BSG'. If 'no', it goes to 'set error BS Not Provisioned'. If 'yes', it goes to 'any BS applicable within the same EBSG'. If 'no', it goes to 'set error BS Not Provisioned'. If 'yes', it goes to 'SS requiring password or password registration'. If 'no', it goes to 'set error BS Not Provisioned'. If 'yes', it goes to 'SS_request' (To process PW1 as specified in TS GSM 03.11). Then 'Wait_for_PW' (Waiting for indications from process PW1, PW2, PW3 or PW4 as specified in TS GSM 03.11). A parallel block contains 'SS Get Password', 'SS Get New Password', 'SS Get New Password Again', 'SS User Errors', 'SS Password Changed', and 'SS Acknowledge'. 'SS User Errors' leads to 'Set ERROR'. 'SS Get Password' leads to 'SS Get Password' (diamond), then 'Wait for password', then 'SS Get Password_Ack', then 'SS Receive Password' (To processes PW1, PW2, PW3 or PW4 specified in TS GSM 03.11), then 'Wait_for_PW'. All paths lead to a final circle with an X.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Procedure general\_SS\_request\_handling + +311\_213(2) + +``` +graph TD + Start((1)) --> D1{any BS provisioned within the BSG} + D1 -- no --> Error1[set error BS Not Provisioned] + D1 -- yes --> D2{any BS applicable within the same EBSG} + D2 -- no --> Error1 + D2 -- yes --> D3{SS requiring password or password registration} + D3 -- no --> Error1 + D3 -- yes --> SS_request[/SS_request / To process PW1 as specified in TS GSM 03.11/] + SS_request --> Wait_for_PW1([Wait_for_PW / Waiting for indications from process PW1, PW2, PW3 or PW4 as specified in TS GSM 03.11./]) + Wait_for_PW1 --> ParallelBlock + subgraph ParallelBlock [ ] + direction TB + P1[SS Get Password] + P2[SS Get New Password] + P3[SS Get New Password Again] + P4[SS User Errors] + P5[SS Password Changed] + P6[SS Acknowledge] + end + P4 --> Set_ERROR[Set ERROR] + P1 --> D4{SS Get Password} + D4 --> Wait_for_password([Wait for password]) + Wait_for_password --> P7[SS Get Password_Ack] + P7 --> P8[/SS Receive Password / To processes PW1, PW2, PW3 or PW4 specified in TS GSM 03.11./] + P8 --> Wait_for_PW2([Wait_for_PW]) + Error1 --> End((2)) + Set_ERROR --> End + P6 --> End + Wait_for_PW2 --> End +``` + +Flowchart for general\_SS\_request\_handling procedure. It starts with a decision 'any BS provisioned within the BSG'. If 'no', it goes to 'set error BS Not Provisioned'. If 'yes', it goes to 'any BS applicable within the same EBSG'. If 'no', it goes to 'set error BS Not Provisioned'. If 'yes', it goes to 'SS requiring password or password registration'. If 'no', it goes to 'set error BS Not Provisioned'. If 'yes', it goes to 'SS\_request' (To process PW1 as specified in TS GSM 03.11). Then 'Wait\_for\_PW' (Waiting for indications from process PW1, PW2, PW3 or PW4 as specified in TS GSM 03.11). A parallel block contains 'SS Get Password', 'SS Get New Password', 'SS Get New Password Again', 'SS User Errors', 'SS Password Changed', and 'SS Acknowledge'. 'SS User Errors' leads to 'Set ERROR'. 'SS Get Password' leads to 'SS Get Password' (diamond), then 'Wait for password', then 'SS Get Password\_Ack', then 'SS Receive Password' (To processes PW1, PW2, PW3 or PW4 specified in TS GSM 03.11), then 'Wait\_for\_PW'. All paths lead to a final circle with an X. + +Figure 2.1 (sheet 3 of 4): Handling of call independent SS procedures with respect to basic service groups + +![Flowchart for handling call independent SS procedures. It starts with a connector, checks if any BS is provisioned within the EBSG. If no, it checks if any SS is applicable. If yes, it performs an interrogation. If no, it executes the requested procedure. If interrogation is yes, it sets SS info for EBSG. If interrogation is no, it checks for incompatibility. If incompatible, it sets an error. Finally, all paths lead to an exit connector.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Procedure specific\_SS\_request\_handling + +311\_214(1) + +Handling of elementary BS groups + +BS: Basic Service +EBSG: Elementary Basic Service Group +SS: Supplementary Service + +NOTE: Execution of the procedure and setting of SS info for EBSGs is described in the GSM 03.8x and 03.9x series of technical specifications. + +``` +graph TD; Start([ ]) --> Q1{any BS provisioned within the EBSG}; Q1 -- no --> Q2{no SS applicable for any BS within this EBSG}; Q1 -- yes --> Q2; Q2 -- no --> Q3{interrogation}; Q2 -- yes --> P1[execute requested procedure]; Q3 -- yes --> P2[set SS info for EBSG]; Q3 -- no --> Q4{incompatible with other SS for this EBSG}; Q4 -- yes --> P3[set error $S incompatibility]; Q4 -- no --> P1; P1 --> End([X]); P2 --> End; P3 --> End; +``` + +Flowchart for handling call independent SS procedures. It starts with a connector, checks if any BS is provisioned within the EBSG. If no, it checks if any SS is applicable. If yes, it performs an interrogation. If no, it executes the requested procedure. If interrogation is yes, it sets SS info for EBSG. If interrogation is no, it checks for incompatibility. If incompatible, it sets an error. Finally, all paths lead to an exit connector. + +Figure 2.1 (sheet 4 of 4): Handling of call independent SS procedures with respect to basic service groups + +# 3 Password handling + +## 3.1 General + +Some supplementary services can be subscribed with the option "control of supplementary service by subscriber using password" as described in the corresponding 3GPP TS 23.08x and 23.09x -series of technical specifications. This option is applicable only for the CS domain. These services are referenced in the following as protected supplementary services. + +The password is stored in the HLR only. + +It has to be memorised by the network, if a wrong password has been used. Therefore, the HLR stores the value of the Wrong Password Attempts counter (WPA). + +If a password check is done with an incorrect password, the WPA is incremented by one. If a password check is passed, WPA is set to zero. If WPA exceeds the value three, the subscription option "control of supplementary service" is set to "by the service provider". This makes registration of password and activation or deactivation of protected supplementary services impossible (see 3GPP TS 22.004). + +When the service provider registers a password, the WPA is set to zero. + +When an attempt to perform an operation requiring a password is received by the network, the network has to check whether the requesting subscriber has subscribed to the option "control of supplementary service by subscriber using password". This is shown in figure 3.1 (function PW1). + +If this option has the value "by the service provider" the WPA has to be checked. When WPA exceeds three, then more than three attempts with a wrong password have been made and the appropriate message will be sent to the user. If the value of WPA is less than or equal to three, then the subscriber has not subscribed to "control of supplementary service by subscriber using password". + +When a password is supplied, it has to be checked, whether it is identical to the one stored. If this applies, then WPA is reset to zero. Otherwise WPA is incremented by one and dependent of the value of the counter, the network shall request the password again, or shall send an error message and update the subscription option as shown in figure 3.2 (function PW2). + +After the input of a wrong password more than three consecutive times, the only possibility to reset the Wrong Password Attempts counter (WPA) is, to register a new password by the service provider. + +Figures 3.3 and 3.4 show the procedures executed by the network in order to check the format (function PW3) and to check the new password (function PW4). + +![Flowchart for Process PW1: Check of subscription option (HLR). The process starts at an 'idle' state, branches into 'register password', 'activate protected SS', and 'deactivate protected SS'. These merge at a decision 'PW option control by subscriber'. If 'yes', it goes to 'get password' then 'wait for old password'. If 'no', it goes to 'WPA <= 3'. If 'yes', it goes to 'error SS subscription violation'. If 'no', it goes to 'error number of PW attempts violation'. Both error states lead to an 'idle' state.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Process PW1 + +311\_31(1) + +PW: Password. + +``` +graph TD; Start([ ]) --> Idle1([idle]); Idle2([idle]) --> Register[/register password/]; Idle2 --> Activate[/activate protected SS/]; Idle2 --> Deactivate[/deactivate protected SS/]; Register --> Merge(( )); Activate --> Merge; Deactivate --> Merge; Merge --> Decision1{PW option control by subscriber}; Decision1 -- yes --> GetPassword[/get password/]; GetPassword --> WaitOldPassword([wait for old password]); Decision1 -- no --> Decision2{WPA <= 3}; Decision2 -- yes --> ErrorSS[/error SS subscription violation/]; Decision2 -- no --> ErrorWPA[/error number of PW attempts violation/]; ErrorSS --> Idle3([idle]); ErrorWPA --> Idle3; +``` + +Flowchart for Process PW1: Check of subscription option (HLR). The process starts at an 'idle' state, branches into 'register password', 'activate protected SS', and 'deactivate protected SS'. These merge at a decision 'PW option control by subscriber'. If 'yes', it goes to 'get password' then 'wait for old password'. If 'no', it goes to 'WPA <= 3'. If 'yes', it goes to 'error SS subscription violation'. If 'no', it goes to 'error number of PW attempts violation'. Both error states lead to an 'idle' state. + +Figure 3.1: PW1; Check of subscription option (HLR) + +![Flowchart for Process PW2: Check of password input (HLR). The process starts with 'wait for old password', followed by 'receive password'. A decision 'password OK' follows. If 'yes', it sets 'WPA := 0' and then checks 'register password'. If 'yes', it goes to 'get new password' and 'wait for new password'. If 'no', it goes to 'acknowledge' and 'idle'. If 'password OK' is 'no', it increments 'WPA := WPA + 1' and checks 'WPA > 3'. If 'yes', it 'set subscription option control by SP', then 'error PW attempts violation', and 'idle'. If 'no', it goes to 'negative password check' and 'idle'.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Process PW2 + +311\_32(1) + +PW: Password. +WPA: Wrong Password attempts counter. +SP: Service Provider. + +``` +graph TD; Start([wait for old password]) --> Recv[/receive password/]; Recv --> OK{password OK}; OK -- yes --> WPA0[WPA := 0]; OK -- no --> WPAinc[WPA := WPA + 1]; WPA0 --> Reg{register password}; Reg -- yes --> NewPW[/get new password/]; NewPW --> WaitNew([wait for new password]); Reg -- no --> Ack[/acknowledge/]; Ack --> Idle1([idle]); WPAinc --> WPAgt3{WPA > 3}; WPAgt3 -- yes --> SetSub[set subscription option control by SP]; SetSub --> Error[/error PW attempts violation/]; Error --> Idle2([idle]); WPAgt3 -- no --> NegCheck[/negative password check/]; NegCheck --> Idle3([idle]); +``` + +Flowchart for Process PW2: Check of password input (HLR). The process starts with 'wait for old password', followed by 'receive password'. A decision 'password OK' follows. If 'yes', it sets 'WPA := 0' and then checks 'register password'. If 'yes', it goes to 'get new password' and 'wait for new password'. If 'no', it goes to 'acknowledge' and 'idle'. If 'password OK' is 'no', it increments 'WPA := WPA + 1' and checks 'WPA > 3'. If 'yes', it 'set subscription option control by SP', then 'error PW attempts violation', and 'idle'. If 'no', it goes to 'negative password check' and 'idle'. + +Figure 3.2: PW2; Check of password input (HLR) + +![Flowchart for Process PW3: Format check (HLR). The process starts with 'wait for new password', followed by 'receive new password', then a decision 'format OK'. If 'yes', it goes to 'get new password again' and back to 'wait for new password again'. If 'no', it goes to 'error password registration failure (invalid format)' and then to 'idle'.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +Process PW3 + +311\_33(1) + +``` +graph TD; A([wait for new password]) --> B[/receive new password/]; B --> C{format OK}; C -- yes --> D[/get new password again/]; D --> E([wait for new password again]); C -- no --> F[/error password registration failure (invalid format)/]; F --> G([idle]); +``` + +Flowchart for Process PW3: Format check (HLR). The process starts with 'wait for new password', followed by 'receive new password', then a decision 'format OK'. If 'yes', it goes to 'get new password again' and back to 'wait for new password again'. If 'no', it goes to 'error password registration failure (invalid format)' and then to 'idle'. + +Figure 3.3: PW3; Format check (HLR) + +![Flowchart for Process PW4: Check of new password (HLR). The process starts with 'wait for new password again', followed by 'receive new password'. A decision 'password twice identical' follows. If 'yes', it goes to 'password changed'. If 'no', it goes to 'error password registration failure (new Passwords Mismatch)'. Both paths lead to 'idle'.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Process PW4 + +311\_34(1) + +``` +graph TD; Start([wait for new password again]) --> Input[/receive new password/]; Input --> Decision{password twice identical}; Decision -- yes --> Success{password changed}; Decision -- no --> Failure{error password registration failure (new Passwords Mismatch)}; Success --> End([idle]); Failure --> End; +``` + +Flowchart for Process PW4: Check of new password (HLR). The process starts with 'wait for new password again', followed by 'receive new password'. A decision 'password twice identical' follows. If 'yes', it goes to 'password changed'. If 'no', it goes to 'error password registration failure (new Passwords Mismatch)'. Both paths lead to 'idle'. + +Figure 3.4: PW4; Check of new password (HLR) + +## 3.2 Registration of password + +If the served mobile subscriber at provision time has selected the subscription option "control of supplementary service by subscriber using password", the service provider has to register a password at provision time. Furthermore the served mobile subscriber can change the password by an appropriate control procedure at any time. The control procedure consists of three steps: first, the old password has to be provided; secondly, the new password has to be given, after which it has to be verified by providing it once more (see figure 3.5). + +If the served mobile subscriber at provision time has selected the subscription option "control of supplementary service by the service provider" an attempt to register a password will be denied and the served mobile subscriber should receive a notification. + +The subscriber can register a new password, thus causing the previous registration to be overridden (see figure 3.5). + +## 3.3 Use of password + +If the served mobile subscriber at provision time has selected the subscription option "control of supplementary service by subscriber using password" the supplementary service is activated only if the subscriber provides the correct password to the network. + +If the served mobile subscriber at provision time has selected the subscription option "control of supplementary service by the service provider", the supplementary service cannot be activated by the subscriber. The activation has to be performed by the service provider. An attempt to activate the service will be denied and the served mobile subscriber should receive a notification. + +If the served mobile subscriber at provision time has selected the subscription option "control of supplementary service by subscriber using password", and if a wrong password is entered to activate the service the supplementary service will not be activated and the served mobile subscriber is notified. + +The information flow for activation of a protected supplementary service is shown in figure 3.6. + +![Sequence diagram showing the registration of a new password between MS, MSC, VLR, and HLR. The diagram includes messages like Register, Get password, Old password, New password, and Password changed. Annotations PW1, PW2, and PW3 indicate password handling programs at the HLR.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + Note right of HLR: PW1 + MS->>MSC: Register + MSC->>VLR: Register password + VLR->>HLR: Register password + HLR-->>VLR: Get password + VLR-->>MSC: Get password + MSC-->>MS: Get password + MS->>MSC: Old password + MSC->>VLR: Old password + VLR->>HLR: Old password + Note right of HLR: PW2 + HLR-->>VLR: Get password + VLR-->>MSC: Get password + MSC-->>MS: Get password + MS->>MSC: New password + MSC->>VLR: New password + VLR->>HLR: New password + Note right of HLR: PW3 + HLR-->>VLR: Get password + VLR-->>MSC: Get password + MSC-->>MS: Get password + MS->>MSC: New password + MSC->>VLR: New password + VLR->>HLR: New password + Note right of HLR: PW4 + HLR-->>VLR: Password changed + VLR-->>MSC: Password changed + MSC-->>MS: Release complete + MS-->>MSC: \ Facility +``` + +Sequence diagram showing the registration of a new password between MS, MSC, VLR, and HLR. The diagram includes messages like Register, Get password, Old password, New password, and Password changed. Annotations PW1, PW2, and PW3 indicate password handling programs at the HLR. + +**Figure 3.5: Registration of a new password** + +NOTE: PW1, PW2 and PW3 indicate password handling programs. + +![Sequence diagram showing the activation of a protected supplementary service between MS, MSC, VLR, and HLR.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + Note right of HLR: PW1 + MS->>MSC: Activate SS + MSC->>VLR: Activate SS + VLR->>HLR: Activate SS + HLR-->>VLR: Get password + VLR-->>MSC: Get password + MSC-->>MS: Password + MS->>MSC: Release complete + Note right of MS: \ Facility + MSC->>VLR: Password + VLR->>HLR: Password + Note right of HLR: PW2 ICH + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note right of MS: \ Facility +``` + +The diagram illustrates the sequence of messages for activating a protected supplementary service. It involves four lifelines: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The process begins with the MS sending an 'Activate SS' message to the MSC. The MSC then forwards this to the VLR, which in turn sends it to the HLR. The HLR responds with a 'Get password' message to the VLR, which is passed back to the MSC and then to the MS. The MS replies with a 'Password' message to the MSC. The MSC passes this password to the VLR, which then sends it to the HLR. The HLR performs checks (PW2 ICH) and sends an 'Acknowledge' message back through the VLR and MSC to the MS. Finally, the MS sends a 'Release complete' message to the MSC, which is passed back to the MS. A note '\ Facility' is associated with the 'Release complete' message. + +Sequence diagram showing the activation of a protected supplementary service between MS, MSC, VLR, and HLR. + +**Figure 3.6: Activation of protected supplementary service** + +NOTE: SS indicates any of the protected supplementary services. +PW1 and PW2 indicate password handling programs. +ICH indicates interaction checks if necessary. + +## 3.4 Deactivation + +The procedure for activation, described in subclause 3.3, is valid also correspondingly for deactivation. + +The information flow for deactivation of protected supplementary service is shown in figure 3.7. + +![Sequence diagram showing the deactivation of a protected supplementary service. Lifelines: MS, MSC, VLR, HLR. The process involves: 1. MS sends 'Deactivate SS' to MSC. 2. MSC sends 'Deactivate SS' to VLR. 3. VLR sends 'Deactivate SS' to HLR. 4. HLR responds with 'Get password' (PW1) to VLR. 5. VLR sends 'Get password' to MSC. 6. MSC sends 'Get password' to MS. 7. MS responds with 'Password' to MSC. 8. MSC sends 'Password' to VLR. 9. VLR sends 'Password' (PW2) to HLR. 10. HLR sends 'Acknowledge' to VLR. 11. VLR sends 'Acknowledge' to MSC. 12. MSC sends 'Release complete \ Facility' to MS.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: PW1 + Note right of HLR: PW2 + MS->>MSC: Deactivate SS + MSC->>VLR: Deactivate SS + VLR->>HLR: Deactivate SS + HLR-->>VLR: Get password + VLR-->>MSC: Get password + MSC-->>MS: Get password + MS->>MSC: Password + MSC->>VLR: Password + VLR->>HLR: Password + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete \ Facility + +``` + +Sequence diagram showing the deactivation of a protected supplementary service. Lifelines: MS, MSC, VLR, HLR. The process involves: 1. MS sends 'Deactivate SS' to MSC. 2. MSC sends 'Deactivate SS' to VLR. 3. VLR sends 'Deactivate SS' to HLR. 4. HLR responds with 'Get password' (PW1) to VLR. 5. VLR sends 'Get password' to MSC. 6. MSC sends 'Get password' to MS. 7. MS responds with 'Password' to MSC. 8. MSC sends 'Password' to VLR. 9. VLR sends 'Password' (PW2) to HLR. 10. HLR sends 'Acknowledge' to VLR. 11. VLR sends 'Acknowledge' to MSC. 12. MSC sends 'Release complete \ Facility' to MS. + +**Figure 3.7: Deactivation of protected supplementary service** + +NOTE: SS indicates any of the protected supplementary services. PW1 and PW2 indicate password handling programs. + +# 4 Supplementary service data management + +For the supplementary services that are considered "activated as a result of provision", when the service is provisioned the following applies: + +when subscription data is sent from the HLR to the VLR, and when an interrogation is sent from the HLR or VLR to the MS: + +- "Provision status" indicators shall be set to "Provisioned"; +- "Activation status" indicators shall be set to "Active". + +# 5 Format of description + +The supplementary services are described according to the following format: + +- subclause x.1 Functions and information flows; +- subclause x.2 Information stored in HLR; +- subclause x.3 Information stored in VLR and SGSN; +- subclause x.4 Handover. + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|--------|---------|-----|-----|---------|-----|---------|---------------------------------------------------| +| TSG CN# | Spec | Old Ver | CR | Rev | | Cat | New Ver | Subject/Comment | +| Apr 1999 | 03.11 | 6.0.0 | | | R97 | | | Transferred to 3GPP CN1 | +| CN#03 | 23.011 | | | | R99 | | 3.0.0 | Approved at CN#03 | +| | 23.011 | 3.0.0 | | | R99 | | 3.0.1 | List of references updated from 2G to 3G | +| CN#09 | 23.011 | 3.0.1 | 002 | 1 | R99 | F | 3.1.0 | SDL refresh | +| CN#11 | 23.011 | 3.1.0 | | | Rel-4 | | 4.0.0 | Release 4 after CN#11 | +| CN#15 | 23.011 | 4.0.0 | | | Rel-4 | | 4.0.1 | References updated | +| CN#16 | 23.011 | 4.0.1 | | | Rel-5 | | 5.0.0 | Release 5 after CN#16 | +| CN#19 | 23.011 | 5.0.0 | | | Rel-6 | | 6.0.0 | Introduction of Call Barring for SMS in PS domain | +| CT#36 | 23.011 | 6.0.0 | | | Rel-7 | | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.011 | 7.0.0 | | | Rel-8 | | 8.0.0 | Upgraded unchanged from Rel-7 | +| 2009-12 | - | 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) | +| 2014-09 | - | 11.0.0 | - | - | Rel-12 | | 12.0.0 | Update to Rel-12 version (MCC) | +| 2015-12 | - | 12.0.0 | - | - | Rel-13 | | 13.0.0 | Update to Rel-13 version (MCC) | +| 2017-03 | - | 13.0.0 | - | - | Rel-14 | | 14.0.0 | Update to Rel-14 version (MCC) | +| 2018-06 | - | 14.0.0 | - | - | Rel-15 | - | 15.0.0 | Update to Rel-15 version (MCC) | +| 2020-07 | - | - | - | - | - | - | 16.0.0 | Update to Rel-16 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23016/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23016/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dec8e5f6dd9e72a357ba0081891939034a7ccd1 --- /dev/null +++ b/marked/Rel-16/23_series/23016/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f09cde001ae4e10c958428ab72a81b18b9fcb605b9e656dd843b5db2c1c7c87 +size 44802 diff --git a/marked/Rel-16/23_series/23016/171115f072e42b379238ed0dd438e9d7_img.jpg b/marked/Rel-16/23_series/23016/171115f072e42b379238ed0dd438e9d7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d609795b94cf4f12b111601f99958f7db118d439 --- /dev/null +++ b/marked/Rel-16/23_series/23016/171115f072e42b379238ed0dd438e9d7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e530d1a0ace699543f1fe2ee8a580be87ac46083718ebb79a0e571792a65d201 +size 7853 diff --git a/marked/Rel-16/23_series/23016/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23016/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bdb51934e479f1ab32f48a4626f34f5a690227b8 --- /dev/null +++ b/marked/Rel-16/23_series/23016/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d4e95c570674987b0e8b393fb76ad93716a555fb118f2600ecfadab70901ab9 +size 167995 diff --git a/marked/Rel-16/23_series/23016/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23016/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fff824169bdd1473ed7a3a584f9139b6bbb7e88b --- /dev/null +++ b/marked/Rel-16/23_series/23016/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29f0e5f2c07b45ffbdd628a4d69d38c513562f7fbbf02d838499b8fb26d0e4bd +size 18654 diff --git a/marked/Rel-16/23_series/23016/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23016/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6381404ae85ceeacdd0ffa6edbf61d5d420af18 --- /dev/null +++ b/marked/Rel-16/23_series/23016/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79356cf6a5897a9431a0efe6d44e776e2bf1980dfb642eb2f36daff57f09d55b +size 182980 diff --git a/marked/Rel-16/23_series/23016/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/Rel-16/23_series/23016/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..99be10846565ffa3afee240dbedc3c4ae609a974 --- /dev/null +++ b/marked/Rel-16/23_series/23016/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2936d6f6fc11f81657b47274c4a27e02a98890d74c1ef17ed215fb816e375526 +size 37915 diff --git a/marked/Rel-16/23_series/23016/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/Rel-16/23_series/23016/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..495a4d384b0f5ee924f192e353bc0299105282e4 --- /dev/null +++ b/marked/Rel-16/23_series/23016/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9bc862a066b35637aec4e991e35974494723179b80f0511d7cea4b0e2859424f +size 5151 diff --git a/marked/Rel-16/23_series/23016/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23016/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22ffdcea12cfd5c018aa725bf987e2b39c2cf342 --- /dev/null +++ b/marked/Rel-16/23_series/23016/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02ec688fc99637f236522ccfd6707d1234814ce06d4e2b0582099faa0b7141cc +size 105883 diff --git a/marked/Rel-16/23_series/23016/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg b/marked/Rel-16/23_series/23016/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01dbea7e8a8eb7ebc86fbbec37f452044a014301 --- /dev/null +++ b/marked/Rel-16/23_series/23016/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88d7cc8ab70fbb80b05ac22b18cc9abccd273e360c765070fa0306badb919480 +size 39484 diff --git a/marked/Rel-16/23_series/23016/6470d350326789d5306eabcb76533951_img.jpg b/marked/Rel-16/23_series/23016/6470d350326789d5306eabcb76533951_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..884fe12cdd859d54dd5a30cafddf84e7d21fdca8 --- /dev/null +++ b/marked/Rel-16/23_series/23016/6470d350326789d5306eabcb76533951_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5af85f5f73230626f3409f0a42aa523b3dd000d38a7510d2e1b457eb18c66f3 +size 78584 diff --git a/marked/Rel-16/23_series/23016/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/Rel-16/23_series/23016/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c9b3a0058cf955371e12ac9e6268081b9694a60 --- /dev/null +++ b/marked/Rel-16/23_series/23016/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7235ab23516be747779cbee8a70975fff66312753f1a70faa0c40291d720909f +size 30696 diff --git a/marked/Rel-16/23_series/23016/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23016/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e59add642318e65517b21fd1a8ae52e3c43a1927 --- /dev/null +++ b/marked/Rel-16/23_series/23016/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73b6eee2ab1f9abafe05b22968a8b37cedccdb1e526a1d79ce0d162fe8b9a340 +size 64159 diff --git a/marked/Rel-16/23_series/23016/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23016/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..55ae1a156cc53e19b488f4adf03aa53ef335443b --- /dev/null +++ b/marked/Rel-16/23_series/23016/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1988150aa38bf2b04fd024b6e06db68efb9a8a9fd4c04756abfbee520a0a835 +size 123939 diff --git a/marked/Rel-16/23_series/23016/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23016/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..625aeedb736e24b0cf4ee6a563d1e0b1f6f7e64b --- /dev/null +++ b/marked/Rel-16/23_series/23016/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f90b88578fe7eb809590a4530ba12d184465f402afbac29c672c7c0b53d60775 +size 149953 diff --git a/marked/Rel-16/23_series/23016/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23016/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8924732ce786ae61edea6a06008e6d8c9b4e8434 --- /dev/null +++ b/marked/Rel-16/23_series/23016/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee230006d87f176a3922d27177dd3ad69ce5745595774ed9059f43ffbb52f220 +size 42450 diff --git a/marked/Rel-16/23_series/23016/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg b/marked/Rel-16/23_series/23016/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c635e1012355e4fe0c18da31837f0b3636df46ad --- /dev/null +++ b/marked/Rel-16/23_series/23016/9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7cbb2db89ce0e047f823e9a585370c0b2242ad8ec127d838e4481efddc662aeb +size 20198 diff --git a/marked/Rel-16/23_series/23016/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23016/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccd470caf3b4059fe12e42bd1f27768845684afe --- /dev/null +++ b/marked/Rel-16/23_series/23016/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:508486c57bca4700cc067746007040a11879a5807f165973f01bc2f68bac9636 +size 17478 diff --git a/marked/Rel-16/23_series/23016/9cd90f495b95ad2116ff780248c26d95_img.jpg b/marked/Rel-16/23_series/23016/9cd90f495b95ad2116ff780248c26d95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84e8c99364eef1fefd2fe5b494455c80472ca165 --- /dev/null +++ b/marked/Rel-16/23_series/23016/9cd90f495b95ad2116ff780248c26d95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f78e892f3a1b6c3c91b22f46bff04afcb7649ae2b6d59c67209f1921313b54f +size 9461 diff --git a/marked/Rel-16/23_series/23016/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg b/marked/Rel-16/23_series/23016/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e3078cb756faac1f6bb384cab353d537d9b887f --- /dev/null +++ b/marked/Rel-16/23_series/23016/9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c61236d128362887e642277f7ff4fd776ffc2b28718c5e496c77831680a993eb +size 44139 diff --git a/marked/Rel-16/23_series/23016/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23016/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7aaf947545ca7b163a6ca2c989e5522410d5b07c --- /dev/null +++ b/marked/Rel-16/23_series/23016/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b18321a902e1d241553a063305f1284175bb334256f27e2093590325682df49 +size 4646 diff --git a/marked/Rel-16/23_series/23016/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg b/marked/Rel-16/23_series/23016/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..345f920949c56ce87d981e431ce7bb090a37bc5f --- /dev/null +++ b/marked/Rel-16/23_series/23016/ca5dc5fde2061d0ca2051ef7840fc842_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba4a0781fac69cb78b0284d8459a3c6f9065d19da9fc118cc17b0a8108b99f88 +size 3886 diff --git a/marked/Rel-16/23_series/23016/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/marked/Rel-16/23_series/23016/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6c1b2851644eb21ddae79736770deede13a6748 --- /dev/null +++ b/marked/Rel-16/23_series/23016/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0d324a7814c0a01fcb342abece86a3e7b1fdd82373bcf6f91e4c25638594a19 +size 5817 diff --git a/marked/Rel-16/23_series/23016/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23016/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02a84c6c58aa16dcf353d615dc58bc2854bd4711 --- /dev/null +++ b/marked/Rel-16/23_series/23016/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fee98a20c763c6634b01720a85c472debc393aecfdbf8858064a795801efc65 +size 137250 diff --git a/marked/Rel-16/23_series/23016/e9b43ac020435f8121e8592f31afdc52_img.jpg b/marked/Rel-16/23_series/23016/e9b43ac020435f8121e8592f31afdc52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f394992aa8d224c13e97e8c0a8f166dcf4208ff --- /dev/null +++ b/marked/Rel-16/23_series/23016/e9b43ac020435f8121e8592f31afdc52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82119539e7b4f27b5a2ef9028634e236ed963e64923f53aef2ecce8812e0f7ee +size 2827 diff --git a/marked/Rel-16/23_series/23016/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-16/23_series/23016/f0a97d0d3818a253c1d2a009966081b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41140e09f3cc640319bd9b3ce395a05c46f9910e --- /dev/null +++ b/marked/Rel-16/23_series/23016/f0a97d0d3818a253c1d2a009966081b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71117cde2bede66e1aefd9da852a3110f50676da4f66d068e4d9da7419707ad8 +size 17886 diff --git a/marked/Rel-16/23_series/23016/raw.md b/marked/Rel-16/23_series/23016/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..8a6b7c6afb9416bf10c6a6b98dbd1cd732b141b5 --- /dev/null +++ b/marked/Rel-16/23_series/23016/raw.md @@ -0,0 +1,1382 @@ + + + + + + +# --- Contents + +| | | +|-------------------------------------------------------------------------------------|----| +| Foreword ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Abbreviations ..... | 6 | +| 3.2 Definitions..... | 7 | +| 4 General on handling of subscriber information ..... | 10 | +| 4.1 Updating of the VLR or the SGSN in framed operation..... | 11 | +| 4.2 Updating of VLR and the SGSN in stand alone operation ..... | 12 | +| 4.2.1 Insertion of data in the VLR or the SGSN ..... | 12 | +| 4.2.2 Deletion of data in the VLR or the SGSN ..... | 13 | +| 4.2.3 Change of data in the VLR or in the SGSN ..... | 13 | +| 4.3 Order of information and distribution over message boundaries..... | 13 | +| 4.3.1 Order of information sent by the HLR ..... | 13 | +| 4.3.2 Order of information received by the VLR or the SGSN..... | 14 | +| 4.4 Abstract data structure of shared subscriber data..... | 14 | +| 4.5 Handling of supplementary service data with respect to basic service data ..... | 15 | +| 4.5.1 General ..... | 15 | +| 4.5.2 Changes to basic service subscription ..... | 15 | +| 4.5.3 Special rules for BS61 and BS81 "alternate" and "followed-by" services..... | 16 | +| 4.5.4 Consistency of Supplementary Service data ..... | 16 | +| Annex A (informative): Change history..... | 32 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- 1 Scope + +This specification gives the stage 2 description of the subscriber data management handling between: + +- the Home Location Register (HLR) and the Visitor Location Register (VLR); +- the Home Location Register (HLR/HSS) and the Serving GPRS Support Node (SGSN). + +A number of procedures require updating of subscriber information: + +- location updating; +- restoration; +- modification of data by the operator; +- modification of data by the subscriber via the Mobile Station (MS). + +Updating of subscriber information from HLR/HSS to SGSN is required in the following situations: + +- GPRS location updating; +- EPS location updating; +- modification of data by the operator. + +Only the rules for the updating of subscriber data from the HLR to the VLR and from the HLR/HSS to the SGSN are described in this specification; these rules only apply when the MAP protocol is used for subscriber data updating (see 3GPP TS 29.002 [23]). Public Land Mobile Network (PLMN) specific and Unstructured Supplementary Service Data (USSD) subscriber data are out of scope of this specification. The GPRS context update from the SGSN to the GGSN and the EPC bearer context update from the SGSN to the P-GW via S-GW are out of scope of this specification. + +NOTE: The term 'HLR' should be read 'HLR/HSS' throughout the document. + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)". +- [3] 3GPP TS 22.004: "General on supplementary services". +- [4] 3GPP TS 23.007: "Restoration procedures". +- [5] 3GPP TS 23.008: "Organization of subscriber data". +- [6] 3GPP TS 23.011: "Technical realization of Supplementary Services". +- [7] 3GPP TS 23.015: "Technical realization of Operator Determined Barring (ODB)". +- [8] 3GPP TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2". + +- [9] 3GPP TS 23.067: "Enhanced Multi-Level Precedence and Preemption service (EMLPP); Stage 2". +- [10] 3GPP TS 23.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL) phase 3 - Stage 2". +- [11] 3GPP TS 23.081: "Line identification supplementary services; Stage 2". +- [12] 3GPP TS 23.082: "Call Forwarding (CF) Supplementary Services; Stage 2". +- [13] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services; Stage 2". +- [14] 3GPP TS 23.084: "Multi Party (MPTY) Supplementary Service; Stage 2". +- [15] 3GPP TS 23.085: "Closed User Group (CUG) Supplementary Service; Stage 2". +- [16] 3GPP TS 23.086: "Advice of Charge (AoC) Supplementary Service; Stage 2". +- [17] 3GPP TS 23.088: "Call Barring (CB) Supplementary Service; Stage 2". +- [18] 3GPP TS 23.090: "Unstructured Supplementary Service Data (USSD); Stage 2". +- [19] 3GPP TS 23.091: "Explicit Call Transfer (ECT) Supplementary Service; Stage 2". +- [20] 3GPP TS 23.093: "Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2". +- [21] 3GPP TS 23.096: "Name Identification Supplementary Service; Stage 2". +- [22] 3GPP TS 23.116: "Super-Charger technical realization; Stage 2." +- [23] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [24] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". +- [25] 3GPP TS 22.001: "Principles of circuit telecommunications services supported by a Public Land Mobile Network (PLMN)". +- [26] 3GPP TS 22.003: "Circuit Teleservices supported by a Public Land Mobile Network (PLMN)". +- [27] 3GPP TS 42.032: " Immediate Service Termination (IST); Service Description - Stage 1". +- [28] 3GPP TS 43.035: " Immediate Service Termination (IST); Stage 2". +- [29] 3GPP TS 43.068: " Voice Group Call Service (VGCS); Stage 2". +- [30] 3GPP TS 43.069: " Voice Broadcast Service (VBS); Stage 2". +- [31] 3GPP TS 23.071: "Location Services (LCS); Functional Description; Stage 2". +- [32] 3GPP TS 23.135: "Multicall supplementary service; Stage 2". +- [33] 3GPP TS 23.072: "Call Deflection Supplementary Service; Stage 2". +- [34] 3GPP TS 23.012: "Location Management Procedures". + +# --- 3 Definitions and abbreviations + +## 3.1 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TS 21.905 apply. + +## 3.2 Definitions + +Subscriber data to be stored in the HLR, VLR and SGSN are defined in 3GPP TS 23.008, 3GPP TS 23.271, 3GPP TS 23.135 and in 3GPP TS 23.06x, 3GPP TS 23.08x and 3GPP TS 23.09x-series of technical specifications. + +Voice Broadcast Service (VBS), Voice Group Call Service (VGCS) and enhanced Multi Level Precedence and Pre-emption Service (eMLPP) Data related to group call area, cell or dispatcher attributes is only stored in the Group Call Register (GCR) which is linked to each MSC/VLR. + +The GCR and its stored data is out of scope of this specification. + +Subscriber related VBS, VGCS and eMLPP Data only concerns entitlement data for these-services and is seen as shared non-GPRS subscriber data. + +### **GPRS and non-GPRS subscriber data:** + +The HLR has to download data to the VLR and to the SGSN. In this specification those data sent to the VLR are called non-GPRS subscriber data and those data sent to the SGSN are called GPRS subscriber data. + +Whenever the refining identifier non-GPRS or GPRS is missing a common rule is addressed which hold for both kinds of subscriber data. + +Subscriber data specific to non-GPRS shall only be sent from the HLR to the VLR. Subscriber data specific to GPRS shall only be sent from the HLR to the SGSN. + +Subscriber data common to both non-GPRS and GPRS (regional subscription information) are downloaded from the HLR to both entities. + +**Shared non-GPRS subscriber data:** Common subset of subscriber data defined to be stored in both the HLR and VLR. Subscriber data only stored in the HLR is not part of shared subscriber data. Shared subscriber data includes: + +- BS: Bearer Service (see 3GPP TS 22.002); +- TS: Teleservice (see 3GPP TS 22.003); +- BSG: Basic Service Group (see 3GPP TS 22.001, 3GPP TS 22.004 and 3GPP TS 23.011); +- EBSG: Elementary Basic Service Group (see 3GPP TS 23.011); +- CBSG: Collective Basic Service Group (see 3GPP TS 23.011); +- LSA Information: Localized Service Area Information (see 3GPP TS 23.073); +- SC Information: Super-Charger Information (see 3GPP TS 23.116); +- IST Information: Immediate Service Termination Information (see 3GPP TS 43.035). + +**Shared GPRS subscriber data:** Common subset of subscriber data defined to be stored in both the HLR and SGSN. Subscriber data only stored in the HLR is not part of shared subscriber data. Shared GPRS subscriber data includes: + +- TS: Teleservice (see 3GPP TS 22.003); +- PDP Context (see 3GPP TS 23.060); +- LSA Information: Localized Service Area Information (see 3GPP TS 23.073); +- SC Information: Super-Charger Information (see 3GPP TS 23.116); +- Charging Information (see 3GPP TS 23.060). + +**Mandatory data:** Data required to form a self-consistent set of subscriber data. The context governs whether a specific parameter is mandatory, e.g. the data set for a specific service may be optional, however if data for this service is present, then parameters within this data set may be mandatory. + +Mandatory data is defined by the service description (see e.g. 3GPP TS 23.06x, 3GPP TS 23.08x and 3GPP TS 23.09x-series of technical specifications, 3GPP TS 23.015, 3GPP TS 23.071 and 3GPP TS 23.135) and by PLMN defined requirements. + +NOTE: The above definition is seen from a semantic point of view. Semantically, mandatory parameters may be defined as syntactically optional or mandatory by the protocol. + +**Optional data:** Data which is defined as subscriber data, but which is not required to form a self-consistent set of subscriber data; the context governs whether a specific parameter is optional. + +Optional data is data which is defined by the service description (see e.g. 3GPP TS 23.06x, 3GPP TS 23.08x and 3GPP TS 23.09x-series of technical specifications, 3GPP TS 23.015, 3GPP TS 23.271 and 3GPP TS 23.135) or by PLMN defined requirements but is not defined as mandatory data. + +NOTE: The above definition is seen from a semantic point of view. Semantically optional parameters are always defined as syntactically optional by the protocol. + +**Missing data:** Data which is mandatory in a given context but is not received nor is valid data available locally. + +**Unexpected data:** Data which is received and cannot be further processed. This may be either: + +- optional data not required in a given context; or +- optional or mandatory data, required in this context but received with an unexpected value. + +**Overlapping data:** Two different cases of overlapping within subscriber data are possible: + +- two or more parameters are to be stored at the same address in the data structure (see subclause 4.4); +- two or more BSGs within a BSG list include or are identical with one and the same EBSG. + +The following groups of non-GPRS subscriber information are defined: + +- Subscriber information (Group A): + - International Mobile Subscriber Identity (IMSI); + - basic Mobile Station International ISDN Number (MSISDN); + - category; + - subscriber status; + - LMU identifier (GSM only). +- Basic service information (Group B): + - Bearer Service list; + - Teleservice list. + +NOTE: VBS and VGCS entitlement data are subsumed under Teleservices. + +- Supplementary Service (SS) information (Group C): + - forwarding information including deflection information; + - call barring information; + - Closed User Group (CUG) information; + - eMLPP data; + - MC data; + - SS Data. +- Operator Determined Barring (ODB) information (Group D): + - ODB Data for non-GPRS services; +- Roaming restriction information (Group E): + +- roaming restriction due to unsupported feature. +- Regional subscription information (Group F): + - regional subscription data. +- VBS/VGCS subscription information (Group G): + - VBS subscription data; + - VGCS subscription data. +- CAMEL subscription information (Group H): + - Originating CAMEL Subscription Information (O-CSI); + - Dialled Service CAMEL Subscription Information (D-CSI); + - VMSC Terminating CAMEL Subscription Information (VT-CSI); + - Supplementary Service Invocation Notification CAMEL Subscription Information (SS-CSI); + - Translation Information Flag CAMEL Subscription Information (TIF-CSI); + - Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI); + - Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI); + - Mobility Management Event Notification CAMEL Subscription Information (M-CSI). +- LSA Information (Group I): + - LSA data. +- Super-Charger (SC) Information (Group K): + - Age Indicator. +- Location Services (LCS) information (Group X): + - GMLC List; + - LCS Privacy Exception List; + - MO-LR List; + - LCS Service Types. +- IST Information (Group J): + - IST data. +- Bearer Service Priority Information (Group L): + - Bearer Service Priority Data. +- Administrative Restriction Information (Group M): + - Access Restriction Data. + +The following groups of GPRS subscriber information are defined: + +- Subscriber information (Group P1): + - International Mobile Subscriber Identity (IMSI); + - basic Mobile Station International ISDN Number (MSISDN); + - subscriber status. + +- Basic service information (Group P2): + - Teleservice list. +- Operator Determined Barring (ODB) information (Group P3): + - ODB Data for GPRS services. +- Roaming restriction information (Group P4): + - roaming restriction in SGSN due to unsupported feature. +- Regional subscription information (Group P5): + - regional subscription data. +- GPRS subscription information (Group P6): + - GPRS subscription data. +- EPS subscription information (Group P6a): + - EPS subscription data. +- SGSN CAMEL subscription information (Group P7): + - GPRS CAMEL subscription information; + - Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI); + - Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI); + - Mobility Management Event for GPRS Notification CAMEL Subscription Information (MG-CSI). +- LSA Information (Group P8): + - LSA data. +- Super-Charger (SC) Information (Group P9): + - Age Indicator. +- Charging Information (Group P10): + - Subscribed Charging Characteristics. +- Location Services (LCS) information (Group P11): + - GMLC List; + - LCS Privacy Exception List; + - MO-LR Lis; + - LCS Service Types. +- Administrative Restriction Information (Group P12): + - Access Restriction Data. + +# --- 4 General on handling of subscriber information + +In general, the VLR and SGSN stores only a subset of the subscriber data available in the HLR. Similarly, the GGSN stores only a subset of the subscriber data available in the SGSN. Updating of subscriber information shall be done in a way to make available and to keep consistency of data shared between the HLR and the VLR, and between the HLR and the SGSN as appropriate. + +Two different cases for the updating of subscriber data can be identified: + +1. framed operation: during location update or restoration a complete set of the shared subscriber data needs to be inserted in the VLR or the SGSN; +2. stand-alone operation: whenever subscriber data are added, deleted or changed in the HLR, this may need partial insertion, deletion or change of shared subscriber data in the VLR or the SGSN. + +Subclauses 4.1 to 4.4 explain the actions of the HLR and the VLR or the SGSN within a framed or stand-alone dialogue on subscriber data handling. + +## 4.1 Updating of the VLR or the SGSN in framed operation + +For some services the VLR or the SGSN shall indicate in the subscriber data request to the HLR whether it supports the service, or (in case of a service with multiple phases) which phases it supports. Whether or not this indication is required for the service is defined in service specification. + +If requested by the framing operation, the HLR shall send all relevant stored shared subscriber data to the VLR or the SGSN. This may be done with one or more messages within a single dialogue. + +For services for which the VLR or the SGSN is required to indicate support of the service, the HLR shall send subscriber data to the VLR or the SGSN only if corresponding indication was received from the VLR or the SGSN in the subscriber data request. If both the originating entity and the HLR support the Super-Charger functionality the HLR may provide no subscriber data as part of the location update procedure, see 3GPP TS 23.116. For control of stand-alone operation the HLR shall store the information for which of these services the subscriber data was sent. + +For services for which the VLR or the SGSN is required to indicate supported phases of the service, the HLR shall send subscriber data to the VLR for at most one of the supported phases of service indicated in the subscriber data request. In this case the HLR may send also no data at all if none of the supported phases is suitable. For the case of stand-alone operation the HLR shall store the information for which phase of service the data was sent. + +The HLR may send all stored shared subscriber data to the VLR or the SGSN with one or more messages within a single dialogue. + +The VLR or the SGSN shall check the received messages, and: + +- a) if mandatory data is missing in a message: + - the VLR or the SGSN may immediately reject the message towards the HLR; or + - the VLR or the SGSN may acknowledge the message towards the HLR and wait for further data from the HLR. + +NOTE: Which of the two options apply is either defined by the protocol specification or is an implementation option. + +- b) if unexpected data are received in a message: + - the VLR or the SGSN may reject the message towards the HLR; or + - in case of unexpected data not required in a given context, the VLR or the SGSN may acknowledge the message towards the HLR and ignore this unexpected data. All other data shall be stored by the VLR or the SGSN. + +NOTE: Which of the two possibilities apply is an implementation option. + +- c) if data for unsupported services or features is received: + - the VLR or the SGSN shall respond towards the HLR to the message indicating these features and shall ignore all received data related to them. All other subscriber data shall be stored; +- d) if cases a), b) and c) do not apply for a message, the VLR or SGSN shall store all subscriber data received. + +If during the entire dialogue none of the messages was rejected by the VLR or the SGSN and at termination of the dialogue no mandatory subscriber data are missing, the VLR or the SGSN shall erase all previously stored data and + +shall store the data received from the HLR and mark the subscriber data as "confirmed by HLR". Otherwise the subscriber data shall remain marked as "not confirmed by HLR" (see TS 3GPP TS 23.007). + +The HLR shall check all responses from the VLR or the SGSN, and: + +- a) if a message is rejected, no further updating of the VLR or the SGSN shall occur. The further action on the framing operation is out of scope of this specification; +- b) if one or more unsupported features are indicated by the VLR or the SGSN, the HLR may: + - store subscriber data including replacement feature(s) locally; + - store and send subscriber data including replacement feature(s); + - ignore this indication. + +NOTE: Which of the three options apply for which feature is out of scope of this specification + +- c) if a message is acknowledged by the VLR or the SGSN, this shall be recognized by the HLR. + +The further action on the framing operation after all shared subscriber and replacement data have been sent (e.g. closing of the dialogue) is out of scope of this specification. + +## 4.2 Updating of VLR and the SGSN in stand alone operation + +If shared subscriber data are added, deleted or changed in the HLR, the HLR shall insert or delete this subscriber data in the VLR or the SGSN to keep consistency of data stored. + +For services for which the VLR or the SGSN is required to indicate support of the service in the request, the HLR shall insert or delete this subscriber data in the VLR or the SGSN only if an appropriate indication is stored in the HLR (see subclause 4.1). + +For services for which the VLR or the SGSN is required to indicate supported phases of the service in the request, the HLR shall insert or delete subscriber data in the VLR or the SGSN only if it was added, deleted or changed for the phase of the service for which the data was sent to the VLR or the SGSN in the framed operation. + +### 4.2.1 Insertion of data in the VLR or the SGSN + +For the insertion of data, the HLR may send one or more messages in a single dialogue. + +The VLR or the SGSN shall check the received data, and: + +- a) if mandatory data is missing in a message: + - the VLR or the SGSN may reject the message towards the HLR; or + - the VLR or the SGSN may acknowledge the message towards the HLR and wait for further data from HLR. + +NOTE: Which of the two possibilities apply is either defined by the protocol specification or an implementation option. + +- b) if unexpected data are received: + - the VLR or the SGSN may reject the message towards the HLR; or + - in case of unexpected data not required in a given context, the VLR or the SGSN may acknowledge the message towards the HLR and ignore this unexpected data. All other data shall be stored by the VLR or the SGSN. + +NOTE: Which of the two possibilities apply is an implementation option. + +- c) if data for unsupported services or features is received: + - the VLR or the SGSN shall respond towards the HLR to the message indicating these features and shall ignore all data assigned to them. All other subscriber data shall be stored. + +- d) if cases a), b) and c) do not apply for a message, the VLR or the SGSN shall store all subscriber data received. + +If during the entire dialogue none of the messages was rejected by the VLR or the SGSN and at termination of the dialogue no subscriber data are missing, the VLR or the SGSN shall mark the subscriber data as "confirmed by HLR". Otherwise the subscriber data shall be marked as "not confirmed by HLR" (see 3GPP TS 23.007). + +The HLR shall check all responses from the VLR or the SGSN, and: + +- a) if a message is rejected no further updating of the VLR or the SGSN is allowed and the HLR shall terminate the dialogue; + - b) if one or more unsupported features are indicated by the VLR or the SGSN, the HLR may: + - store subscriber data including replacement feature(s) locally; + - store and send subscriber data including replacement feature(s); + - ignore this indication. +- NOTE: Which of the three possibilities apply for which feature is out of scope of this specification +- c) if a message is acknowledged by the VLR or the SGSN, this shall be recognized by the HLR. + +After all required shared subscriber and replacement data have been sent, the HLR shall terminate the dialogue with the VLR or the SGSN. + +### 4.2.2 Deletion of data in the VLR or the SGSN + +Deletion needs a separate dialogue. + +HLR and VLR or SGSN actions are the same as above except for the following case: + +- if, in response to deletion, one or more unsupported features are indicated by the VLR or the SGSN, the HLR may: + - delete subscriber data including replacement feature(s) locally; + - delete subscriber data including replacement feature(s) locally and in the VLR or the SGSN (NOTE); + - take no further action. + +NOTE 1: Which of the three options apply for which feature is out of scope of this specification. + +NOTE 2: This deletion in the VLR or the SGSN needs a separate dialogue. + +The VLR or SGSN shall terminate the dialogue with the HLR in response to the HLR. + +### 4.2.3 Change of data in the VLR or in the SGSN + +If existing data in the VLR or the SGSN is to be modified, the HLR may insert the replacing data, which overwrites the existing data according to the rules described in subclause 4.4. Alternatively, the HLR may delete the existing data as described in subclause 4.2.2 and then insert the replacing data as described in subclause 4.2.1. + +## 4.3 Order of information and distribution over message boundaries + +### 4.3.1 Order of information sent by the HLR + +The order of information is defined by the order in which the transfer syntax is generated by the HLR. This includes a sequence of messages as well as the syntax within a message (first to last message, component, operation, parameter, etc...). + +With the above definitions, the following rules shall apply for non-GPRS subscriber data for the order of information within an HLR-VLR dialogue: + +- Group A information (subscriber status) shall be sent first; + +- Group B information shall be sent after Group A information and before any Group C, E, F, G, H, J, L, M or X information; +- Group D information shall be sent after Group A information and in any order with respect to Group B, C, E, F, G, H, J, K, L, M and X information; +- a specific order of Group C, E, F, G, H, J, K, L, M or X information is not required. + +There is no requirement for the sending of subscriber information groups in the same message. + +With the above definitions, the following rules shall apply for GPRS subscriber data for the order of information within a dialogue: + +- Group P1 information (subscriber status) shall be sent first; +- Group P2 information shall be sent after P1 information and before P4 and P5 information; +- Group P3 information shall be sent after Group P1 information and in any order with respect to Group P2, P4, P5, P6, P6a, P7, P8, P11 and P12 information; +- a specific order of Group P4, P5, P6, P6a, P9, P10, P11 and P12 information is not required. + +### 4.3.2 Order of information received by the VLR or the SGSN + +Normally, the order of information sent and received shall be identical. However, if subscriber data are sent distributed over several messages within a dialogue in exceptional cases the order of these messages may change during transmission. + +If the order of information received violates the rules given above, the VLR or the SGSN has the following options: + +- the VLR or the SGSN rejects all messages which cannot be processed due to violation of these rules. In this case, checking of missing mandatory parameters is done for each message; +- the VLR or the SGSN processes and accepts all received messages although rules are violated. In this case, checking of missing mandatory parameters is done after the last message i.e. after termination of the dialogue. + +Both options may be used in a single implementation. Missing parameters may be detected during the dialogue. For other parameters, the checking is done after termination of the dialogue between the HLR and the VLR or the SGSN. + +The VLR or the SGSN is not required to handle received data in a specific order. As a consequence, any overlapping of data within a dialogue should be avoided to keep consistency of data between HLR and VLR or the SGSN. If the VLR or SGSN indicates that it does not support a feature or service, the HLR may send data for a feature or service to replace the unsupported one. If the data of that service or feature had already been sent, this shall not be regarded as overlapping data. + +## 4.4 Abstract data structure of shared subscriber data + +Figure 1 shows the general organization of the shared non-GPRS subscriber data stored in the HLR and VLR. Figure 2 shows the overall organization of subscriber data stored in HLR and SGSN. The figures 3 to 25 show the organization of the shared subscriber data stored in the HLR and VLR or in the HLR and SGSN. This structure is only valid for data stored in the registers and is not identical with the structure in the protocol, defining how data are transferred. + +NOTE: This description is only a model for the logical structure and does not define the specific implementation of the data storage. + +With this structure, the following general rules for the handling of subscriber data are defined: + +- the root of this data tree is always the IMSI which identifies the subscriber; +- to address a specific parameter within this hierarchical tree, it is necessary to start from the IMSI and to go through the branches until the parameter is reached. The list of parameters met on the way defines the address of the parameter within the data structure; +- to delete or insert a specific parameter, the complete address information is required; + +- if a parameter is inserted, all parameters in the address and the parameter itself shall be marked as present. A parameter value is stored irrespective of whether a value was already stored; +- if a parameter is deleted, all parameters connected to it in the sub-branches are also deleted i.e. they are marked as not present; +- if a parameter is overwritten with a new value, parameters connected to it in the sub-branches shall be set according to the rules of the individual service specification. + +In addition to the general rules given above, special rules apply to certain specific subscriber data. This is out of scope of this specification (see references in the notes in figures 1 to 25). + +## 4.5 Handling of supplementary service data with respect to basic service data + +Some supplementary service data is qualified by Elementary Basic Service Group (EBSG) data. This part of the service data is below the parameter "BSG" in the abstract data hierarchy, and is referred to as the "EBSG-related SS data". This clause provides special rules for handling of EBSG-related SS data. + +The internal representation of EBSGs and EBSG-related SS data in the HLR and VLR is outside the scope of this specification. For simplicity this description uses a model where all EBSG-related SS data is stored against individual EBSGs. Implementations may use alternative internal data structures. + +### 4.5.1 General + +EBSG-related SS data shall be stored in the HLR and VLR for all EBSGs that meet all the following criteria: + +- at least one basic service in the EBSG is supported; and +- the supplementary service is applicable to at least one (possibly different) basic service in the EBSG; and +- the subscriber has a subscription to at least one (possibly different) basic service in the EBSG. + +EBSG-related SS data shall not be stored for any other EBSGs. + +For each service for which the HLR sends EBSG-related SS data to the VLR, the HLR shall send the data for all EBSGs that meet all the following criteria: + +- at least one basic service in the EBSG is supported at the HLR; and +- the supplementary service is applicable to at least one (possibly different) basic service in the EBSG; and +- the subscriber has a subscription to at least one (possibly different) basic service in the EBSG. + +At any time, if the HLR has to send identical EBSG-Related SS data for several EBSGs, then it may be able to represent a set of EBSGs by a collective basic service group (CBSG), or by omitting the EBSG information altogether. This is specified in detail in 3GPP TS 29.002. + +### 4.5.2 Changes to basic service subscription + +Changes to the basic service subscription can impact EBSG-related SS data. + +If a new basic service is provisioned, and this is the first basic service to be provisioned for this subscriber in a particular EBSG, then the HLR shall update supplementary service data in the VLR if necessary. The HLR shall insert in the VLR EBSG-related SS data for the new EBSG for all supplementary services that: + +- have EBSG-related SS data; and +- are applicable to at least one basic service in the new EBSG; and +- are in a state where the VLR should receive data (normally this means the service must be provisioned). + +If a new basic service is provisioned, and this is not the first basic service provisioned for this subscriber in a particular EBSG, then the HLR is not required to send any new supplementary service data as a result. + +If a basic service is withdrawn, and this was the last remaining basic service provisioned for this subscriber in a particular EBSG, then when they are informed about the withdrawal of the basic service the HLR and VLR shall locally delete any supplementary service data relating to that EBSG. + +If a basic service is withdrawn, and this was not the last remaining basic service provisioned for this subscriber in a particular EBSG, then the HLR and VLR shall not make any changes to supplementary service data as a result. + +### 4.5.3 Special rules for BS61 and BS81 "alternate" and "followed-by" services + +There is no EBSG-related SS data for the groups BS61 and BS81 ("alternate" and "followed-by"). Instead, supplementary services related to these basic services are handled according to the bearer service group BS2x or BS3x corresponding to the data part of the "alternate" and "followed by" bearer service (see 3GPP TS 22.004). This means that special rules are required for subscribers with subscriptions to BS61 or BS81. + +For the handling of EBSG-related SS data, a subscription to BS61 or BS81 shall be treated in the same way as a subscription to a basic service in each of the groups "all data circuit asynchronous" and "all data circuit synchronous" (BS2x and BS3x). If a user subscribes to BS61 or BS81 then the HLR shall send any relevant EBSG-related SS data to the VLR for the groups BS2x and BS3x even if the subscriber does not subscribe to any basic services in the groups BS2x and BS3x. + +Examples: + +- if a user who does not subscribe to any basic services in BS2x or BS3x is given a subscription to BS81 then the HLR updates the VLR with any relevant EBSG-related SS data for the groups BS2x and BS3x. If the subscription to BS81 is then withdrawn, the VLR locally deletes all EBSG-related SS data for BS2x and BS3x. +- if a user who has a subscription to BS21, but not to any basic services in BS3x is given a subscription to BS81 then the HLR updates the VLR with any relevant EBSG-related SS data for the group BS3x. If the subscription to BS81 is then withdrawn, the VLR locally deletes all EBSG-related SS data for BS3x (though not for BS2x). + +EBSG-related SS data shall not be qualified by the groups BS61 or BS81. + +### 4.5.4 Consistency of Supplementary Service data + +In some cases, the protocol used between the HLR and VLR encodes some data that is not EBSG-related SS data with an EBSG qualifier. In this case, the HLR shall ensure that when this data is sent it is always the same for all EBSGs. If this data is modified, the HLR must send the supplementary service data to the VLR for all EBSGs which meet all the following criteria: + +- at least one basic service in the EBSG is supported; and +- the supplementary service is applicable to at least one (possibly different) basic service in the EBSG; and +- the subscriber has a subscription to at least one (possibly different) basic service in the EBSG. + +![Abstract data structure of non-GPRS Subscriber Data (Data sent to the VLR)](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` +graph TD; IMSI --- Basic_MSISDN[Basic MSISDN]; IMSI --- Category[Category]; IMSI --- Basic_Service_List[Basic Service List]; IMSI --- Forwarding_Info[Forwarding Info]; IMSI --- Call_Barring_Info[Call Barring Info]; IMSI --- CUG_Info[CUG Info]; IMSI --- SS_Data[SS Data]; IMSI --- ODB_Data[ODB Data for non-GPRS services]; IMSI --- Roaming_Restriction_Data[Roaming Restriction Data in the VLR]; IMSI --- Regional_Subscription_Data[Regional Subscription Data]; IMSI --- VBS_VGCS_Data[VBS, VGCS Data]; IMSI --- CAMEL_Subscription_Info[CAMEL Subscription Info]; IMSI --- NAEA_Prefered_Carrier_Id[NAEA, Preferred Carrier Id]; IMSI --- LSA_Data[LSA Data]; IMSI --- IST_Data[IST Data]; IMSI --- LMU_Indicator[LMU Indicator]; IMSI --- LCS_Information[LCS Information]; IMSI --- Super_Charger_Information[Super Charger Information]; IMSI --- Bearer_Service_Priority_Data[Bearer Service Priority Data]; IMSI --- Administrative_Restriction_Information[Administrative Restriction Information]; +``` + +The diagram illustrates the abstract data structure of non-GPRS Subscriber Data sent to the VLR. It is a hierarchical tree structure starting with IMSI at the root. The data is organized into several categories, some of which are grouped into boxes. The categories are: Basic MSISDN, Category, Basic Service List, Forwarding Info, Call Barring Info, CUG Info, SS Data, ODB Data for non-GPRS services, Roaming Restriction Data in the VLR, Regional Subscription Data, VBS, VGCS Data, CAMEL Subscription Info, NAEA, Preferred Carrier Id, LSA Data, IST Data, LMU Indicator, LCS Information, Super Charger Information, Bearer Service Priority Data, and Administrative Restriction Information. + +Abstract data structure of non-GPRS Subscriber Data (Data sent to the VLR) + +**Figure 1: Abstract data structure of non-GPRS Subscriber Data (Data sent to the VLR)** + +![Abstract data structure of GPRS Subscriber Data (Data sent to the SGSN). The diagram shows a hierarchical list of data elements under the root 'IMSI'.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +graph LR + IMSI --- AM[Access Mode] + IMSI --- BM[Basic MSISDN] + IMSI --- BSL[Basic Service List] + IMSI --- CBI[Call Barring Info] + IMSI --- ODB[ODB Data for GPRS services] + IMSI --- RR[Roaming Restriction Data in the SGSN] + IMSI --- RSD[Regional Subscription Data] + IMSI --- GSD[GPRS subscription Data] + IMSI --- ESD[EPS subscription Data] + IMSI --- SCS[SGSN CAMEL subscription information] + IMSI --- LD[LSA Data] + IMSI --- SCI[Super-Charger Information] + IMSI --- CI[Charging Information] + IMSI --- LI[LCS Information] + IMSI --- ARI[Administrative Restriction Information] + +``` + +Abstract data structure of GPRS Subscriber Data (Data sent to the SGSN). The diagram shows a hierarchical list of data elements under the root 'IMSI'. + +**Figure 2: Abstract data structure of GPRS Subscriber Data (Data sent to the SGSN)** + +![Basic Service List diagram showing Teleservices and Bearer Services categories.](9cd90f495b95ad2116ff780248c26d95_img.jpg) + +``` + +graph LR + Root --- TS[Teleservices] + TS --- TS1[TS (1)] + TS --- TSDots[...] + TS --- TSn[TS (n)] + Root --- BS[Bearer Services] + BS --- BS1[BS (1)] + BS --- BSDots[...] + BS --- BSn[BS (n)] + style Root width:0px,height:0px + +``` + +Basic Service List diagram showing Teleservices and Bearer Services categories. + +NOTE: For detailed information see 3GPP TS 22.001, 3GPP TS 22.002, 3GPP TS 22.003 and 3GPP TS 29.002. + +**Figure 3: Basic Service List** + +![A hierarchical tree diagram showing the structure of Forwarding Information (FI) for various call forwarding scenarios. The root branches into five main call forwarding types: CFU, CFB, CFNRc, CFNRy, and CD. Each type has a set of common parameters (Subscription Options, Provisioning State) and specific parameters (BSG entries with Activation/Registration states, Forwarded-to Number, Subaddress, or No Reply Condition Timer).](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` +graph TD + Root[ ] --- CFU[Call Forwarding Unconditional (CFU)] + Root --- CFB[Call Forwarding on mobile subscriber Busy (CFB)] + Root --- CFNRc[Call Forwarding on mobile subscriber Not Reachable (CFNRc)] + Root --- CFNRy[Call Forwarding on No Reply (CFNRy)] + Root --- CD[Call Deflection (CD)] + + CFU --- CFU_SO[Subscription Options] + CFU --- CFU_PS[Provisioning State] + CFU --- CFU_BSG1[BSG(1)] + CFU --- CFU_Dots1[.....] + CFU --- CFU_BSGn[BSG(n)] + + CFU_BSG1 --- CFU_BSG1_AS[Activation State] + CFU_BSG1 --- CFU_BSG1_RS[Registration State] + + CFU_BSGn --- CFU_BSGn_AS[Activation State] + CFU_BSGn --- CFU_BSGn_RS[Registration State] + + CFB --- CFB_SO[Subscription Options] + CFB --- CFB_PS[Provisioning State] + CFB --- CFB_BSG1[BSG(1)] + CFB --- CFB_Dots1[.....] + CFB --- CFB_BSGn[BSG(n)] + + CFB_BSG1 --- CFB_BSG1_AS[Activation State] + CFB_BSG1 --- CFB_BSG1_RS[Registration State] + CFB_BSG1 --- CFB_BSG1_FTN[Forwarded-to Number] + CFB_BSG1_FTN --- CFB_BSG1_FTN_SA[Subaddress] + + CFB_BSGn --- CFB_BSGn_AS[Activation State] + CFB_BSGn --- CFB_BSGn_RS[Registration State] + CFB_BSGn --- CFB_BSGn_FTN[Forwarded-to Number] + CFB_BSGn_FTN --- CFB_BSGn_FTN_SA[Subaddress] + + CFNRc --- CFNRc_SO[Subscription Options] + CFNRc --- CFNRc_PS[Provisioning State] + CFNRc --- CFNRc_BSG1[BSG(1)] + CFNRc --- CFNRc_Dots1[.....] + CFNRc --- CFNRc_BSGn[BSG(n)] + + CFNRc_BSG1 --- CFNRc_BSG1_AS[Activation State] + CFNRc_BSG1 --- CFNRc_BSG1_RS[Registration State] + CFNRc_BSG1 --- CFNRc_BSG1_FTN[Forwarded-to Number] + CFNRc_BSG1_FTN --- CFNRc_BSG1_FTN_SA[Subaddress] + + CFNRc_BSGn --- CFNRc_BSGn_AS[Activation State] + CFNRc_BSGn --- CFNRc_BSGn_RS[Registration State] + CFNRc_BSGn --- CFNRc_BSGn_FTN[Forwarded-to Number] + CFNRc_BSGn_FTN --- CFNRc_BSGn_FTN_SA[Subaddress] + + CFNRy --- CFNRy_SO[Subscription Options] + CFNRy --- CFNRy_PS[Provisioning State] + CFNRy --- CFNRy_BSG1[BSG(1)] + CFNRy --- CFNRy_Dots1[.....] + CFNRy --- CFNRy_BSGn[BSG(n)] + + CFNRy_BSG1 --- CFNRy_BSG1_AS[Activation State] + CFNRy_BSG1 --- CFNRy_BSG1_RS[Registration State] + CFNRy_BSG1 --- CFNRy_BSG1_NRCT[No Reply Condition Timer] + CFNRy_BSG1 --- CFNRy_BSG1_FTN[Forwarded-to Number] + CFNRy_BSG1_FTN --- CFNRy_BSG1_FTN_SA[Subaddress] + + CFNRy_BSGn --- CFNRy_BSGn_AS[Activation State] + CFNRy_BSGn --- CFNRy_BSGn_RS[Registration State] + CFNRy_BSGn --- CFNRy_BSGn_NRCT[No Reply Condition Timer] + CFNRy_BSGn --- CFNRy_BSGn_FTN[Forwarded-to Number] + CFNRy_BSGn_FTN --- CFNRy_BSGn_FTN_SA[Subaddress] + + CD --- CD_SO[Subscription Options] + CD --- CD_PS[Provisioning State] +``` + +A hierarchical tree diagram showing the structure of Forwarding Information (FI) for various call forwarding scenarios. The root branches into five main call forwarding types: CFU, CFB, CFNRc, CFNRy, and CD. Each type has a set of common parameters (Subscription Options, Provisioning State) and specific parameters (BSG entries with Activation/Registration states, Forwarded-to Number, Subaddress, or No Reply Condition Timer). + +NOTE: For detailed information see 3GPP TS 23.072, 3GPP TS 23.082 and 3GPP TS 29.002. + +**Figure 4: Forwarding Info** + +![Hierarchical tree diagram for Call Barring Info](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +This hierarchical tree diagram represents the 'Call Barring Info' structure. It branches into three main categories: 'Barring of All Outgoing Calls (BAOC)', 'Barring of Outgoing International Calls (BOIC)', and 'Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC)'. Each category has a 'Provisioning State' sub-element. The 'BOIC' and 'BOIC-exHC' categories further branch into multiple 'BSG' (Barring Service Group) elements, labeled 'BSG(1)' through 'BSG(n)', each with its own 'Activation State' sub-element. The 'BAOC' category also has 'BSG(1)' through 'BSG(n)' elements, but they are not explicitly shown with 'Activation State' sub-elements in this diagram. + +Hierarchical tree diagram for Call Barring Info + +NOTE: For detailed information see 3GPP TS 23.088 and 3GPP TS 29.002. + +**Figure 5: Call Barring Info** + +![Hierarchical tree diagram for CUG Info](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +This hierarchical tree diagram represents the 'CUG Info' structure. It starts with 'Closed User Group (CUG)', which branches into 'Interlock(1)' and 'Interlock(m)'. Each 'Interlock' element has 'CUG Index', 'Intra CUG Restrictions', and multiple 'BSG' (Barring Service Group) elements labeled 'BSG(1)' through 'BSG(n)'. Below the 'Interlock' elements, there are 'BSG(1)' and 'BSG(n)' elements, each with 'Preferential CUG' and 'Inter CUG Accessibility' sub-elements. + +Hierarchical tree diagram for CUG Info + +NOTE: For detailed information see 3GPP TS 23.085 and 3GPP TS 29.002. + +**Figure 6: CUG Info** + +- Calling Line Identification Presentation (CLIP) + - Provisioning State + - Activation State + - Override Category +- Calling Line Identification Restriction (CLIR) + - Provisioning State + - Activation State + - Presentation Mode +- Connected Line identification Presentation (COLP) + - Provisioning State + - Activation State + - Override Category +- Connected Line identification Restriction (COLR) + - Provisioning State + - Activation State +- Call Waiting (CW) + - Provisioning State + - BSG(1) + - Activation State + - ..... + - BSG(n) + - Activation State +- Call Hold (HOLD) + - Provisioning State + - Activation State +- Multi Party (MPTY) + - Provisioning State + - Activation State +- Advice of Charge Information (AoCI) + - Provisioning State + - Activation State +- Advice of Charge Charging (AoCC) + - Provisioning State + - Activation State +- Explicit Call Transfer (ECT) + - Provisioning State + - Activation State +- Calling Name Presentation (CNAP) + - Provisioning State + - Activation State + - Override Category +- enhanced Multi-Level Precedence Pre-Emption (eMLPP) + - Provisioning State + - Activation State + - Maximum Entitled Priority + - Default +- Multicall (MC) + - Provisioning State + - Activation State + - Registration State + - Subscribed maximum CS bearers + - User defined maximum CS bearers + +![A hierarchical tree diagram showing the structure of LCS (Location Services) classes and their associated states. The root branches into 'Completion of Calls to Busy Subscriber (CCBS)-originating NW' and 'Completion of Calls to Busy Subscriber (CCBS)-destination NW'. The 'LCS Privacy Exception Class' branches into 'Universal', 'Call Session Related', 'Call Session Unrelated', 'PLMN Operator', and 'Service Type'. The 'MO-LR Class' branches into 'Basic Self Location', 'Autonomous Self Location', and 'Transfer To Third Party'. Each class has sub-states: 'Provisioning State', 'Activation State', and 'Registration State' (where applicable).](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` +graph TD + Root[ ] --- CCBS_O[Completion of Calls to Busy Subscriber (CCBS)-originating NW] + Root --- CCBS_D[Completion of Calls to Busy Subscriber (CCBS)-destination NW] + CCBS_O --- PS_O[Provisioning State] + CCBS_O --- AS_O[Activation State] + CCBS_D --- PS_D[Provisioning State] + CCBS_D --- AS_D[Activation State] + Root --- LPE_C[ ] + LPE_C --- LPE_CU[LCS Privacy Exception Class Universal] + LPE_C --- LPE_CSR[LCS Privacy Exception Class Call Session Related] + LPE_C --- LPE_CSU[LCS Privacy Exception Class Call Session Unrelated] + LPE_C --- LPE_CPO[LCS Privacy Exception Class PLMN Operator] + LPE_C --- LPE_CST[LCS Privacy Exception Class Service Type] + LPE_CU --- PS_U[Provisioning State] + LPE_CU --- AS_U[Activation State] + LPE_CU --- Reg_U[Registration State] + LPE_CSR --- PS_R[Provisioning State] + LPE_CSR --- AS_R[Activation State] + LPE_CSR --- Reg_R[Registration State] + LPE_CSU --- PS_S[Provisioning State] + LPE_CSU --- AS_S[Activation State] + LPE_CSU --- Reg_S[Registration State] + LPE_CPO --- PS_Op[Provisioning State] + LPE_CPO --- AS_Op[Activation State] + LPE_CPO --- Reg_Op[Registration State] + LPE_CST --- PS_T[Provisioning State] + LPE_CST --- AS_T[Activation State] + LPE_CST --- Reg_T[Registration State] + Root --- MO_LR_C[ ] + MO_LR_C --- MO_LR_CBSL[MO-LR Class Basic Self Location] + MO_LR_C --- MO_LR_CASL[MO-LR Class Autonomous Self Location] + MO_LR_C --- MO_LR_CTT[MO-LR Class Transfer To Third Party] + MO_LR_CBSL --- PS_BSL[Provisioning State] + MO_LR_CBSL --- AS_BSL[Activation State] + MO_LR_CBSL --- Reg_BSL[Registration State] + MO_LR_CASL --- PS_ASL[Provisioning State] + MO_LR_CASL --- AS_ASL[Activation State] + MO_LR_CASL --- Reg_ASL[Registration State] + MO_LR_CTT --- PS_TT[Provisioning State] + MO_LR_CTT --- AS_TT[Activation State] + MO_LR_CTT --- Reg_TT[Registration State] +``` + +A hierarchical tree diagram showing the structure of LCS (Location Services) classes and their associated states. The root branches into 'Completion of Calls to Busy Subscriber (CCBS)-originating NW' and 'Completion of Calls to Busy Subscriber (CCBS)-destination NW'. The 'LCS Privacy Exception Class' branches into 'Universal', 'Call Session Related', 'Call Session Unrelated', 'PLMN Operator', and 'Service Type'. The 'MO-LR Class' branches into 'Basic Self Location', 'Autonomous Self Location', and 'Transfer To Third Party'. Each class has sub-states: 'Provisioning State', 'Activation State', and 'Registration State' (where applicable). + +NOTE: For detailed information see 3GPP TS 23.067, 3GPP TS 23.081, 3GPP TS 23.083, 3GPP TS 23.084, 3GPP TS 23.086, 3GPP TS 23.091, 3GPP TS 23.093, 3GPP TS 23.096, 3GPP TS 23.135, 3GPP TS 29.002 and 3GPP TS 23.071. + +The codes below are used for the single purpose of enabling the visited network to notify the home network whether or not the particular Supplementary Service is supported. These codes are also included in the LCS Information parameter and the visited network shall use the codes in the LCS Information parameter, and only this parameter, to obtain the information needed for the LCS Supplementary Service. + +- LCS Privacy Exception Class Universal +- LCS Privacy Exception Class Call Session Related +- LCS Privacy Exception Class Call Session Unrelated +- LCS Privacy Exception Class PLMN Operator +- LCS Privacy Exception Class Service Type +- MO-LR Class Basic Self Location +- MO-LR Class Autonomous Self Location + +- MO-LR Class Transfer To Third Party + +**Figure 7: SS Data** + +``` + +└Subscriber Status +├all OG-Calls Barred +├international OG-Calls Barred +├international OG-Calls Not To HPLMN Country Barred +├inter-zonal OG-Calls Barred +├inter-zonal OG-Calls Not To HPLMN Country Barred +├international OG-Calls Not To HPLMN Country AND + inter-zonal OG-Calls Barred +├Premium Rate Information OG-Calls Barred +├Premium Rate Entertainment OG-Calls Barred +├SS Access Barred +├all call transfers Barred +├chargeable call transfers Barred +├international call transfers Barred +├inter-zonal call transfers Barred +├doubly chargeable call transfers Barred +├multiple call transfers Barred +├PLMN-Specific Barring Type 1 +├PLMN-Specific Barring Type 2 +├PLMN-Specific Barring Type 3 +└PLMN-Specific Barring Type 4 + +``` + +NOTE: For detailed information see 3GPP TS 23.015 and 3GPP TS 29.002. + +**Figure 8: ODB Data for non-GPRS services** + +``` + +└Subscriber Status +├all OG-Calls Barred +├international OG-Calls Barred +├international OG-Calls Not To HPLMN Country Barred +├inter-zonal OG-Calls Barred +├inter-zonal OG-Calls Not To HPLMN Country Barred +├international OG-Calls Not To HPLMN Country AND + inter-zonal OG-Calls Barred +├PLMN-Specific Barring Type 1 +├PLMN-Specific Barring Type 2 +├PLMN-Specific Barring Type 3 +├PLMN-Specific Barring Type 4 +├All Packet Oriented Services Barred +├Roamer Access To HPLMN AP-Barred +└Roamer Access To VPLMN AP-Barred + +``` + +NOTE: For detailed information see 3G TS 23.015 and 3G TS 29.002. + +**Figure 9: ODB Data for GPRS services** + +``` + +└Roaming Restriction Due To Unsupported Feature + +``` + +NOTE: For detailed information see 3GPP TS 29.002. + +**Figure 10: Roaming Restriction Data in the VLR** + +``` + +└Roaming Restricted in the SGSN Due To Unsupported Feature + +``` + +NOTE: For detailed information see 3GPP TS 29.002. + +**Figure 11: Roaming Restriction Data in the SGSN** + +![Diagram of Regional Subscription Data structure](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` +└ZoneCode(1) +├..... +└ZoneCode(k) +``` + +A hierarchical tree diagram representing Regional Subscription Data. It starts with a root node 'ZoneCode(1)', followed by an ellipsis '.....', and ending with 'ZoneCode(k)'. + +Diagram of Regional Subscription Data structure + +NOTE: For detailed information see 3GPP TS 29.002. + +**Figure 12: Regional Subscription Data** + +![Diagram of Voice Group Call Data structure](171115f072e42b379238ed0dd438e9d7_img.jpg) + +``` +└VGCS membership List +├Group-Id(1) +├..... +└Group-Id (n) +``` + +A hierarchical tree diagram representing Voice Group Call Data. It starts with a root node 'VGCS membership List', followed by 'Group-Id(1)', an ellipsis '.....', and 'Group-Id (n)'. + +Diagram of Voice Group Call Data structure + +NOTE: For detailed information see 3GPP TS 43.068 and 3GPP TS 29.002. + +**Figure 13: Voice Group Call Data** + +![Diagram of Voice Broadcast Call Data structure](9167fa5ebcb66516d1bbb421ec9bba7b_img.jpg) + +``` +└VBS membership List +├Group-Id(1) +│└Broadcast Call Initiation Entitlement +├..... +└Group-Id (n) +└Broadcast Call Initiation Entitlement +``` + +A hierarchical tree diagram representing Voice Broadcast Call Data. It starts with a root node 'VBS membership List', followed by 'Group-Id(1)' which has a child node 'Broadcast Call Initiation Entitlement', an ellipsis '.....', and 'Group-Id (n)' which also has a child node 'Broadcast Call Initiation Entitlement'. + +Diagram of Voice Broadcast Call Data structure + +NOTE: For detailed information see 3GPP TS 43.069 and 3GPP TS 29.002. + +**Figure 14: Voice Broadcast Call Data** + +![A hierarchical tree diagram showing CAMEL Subscription Information. The root is 'CAMEL Subscription Information', which branches into four main categories: 'Originating CAMEL Subscription Info', 'Dialled Service CAMEL Subscription Info', 'VMS C Terminating CAMEL Subscription Info', and 'SS Invocation Notification CAMEL Subscription Info'. Each category has its own sub-elements, such as TDP Data Lists, DP Criteria Lists, and CAMEL Capability Handling.](26d664119ad25250780f554633444e54_img.jpg) + +``` +graph TD + Root[CAMEL Subscription Information] --> Originating[Originating CAMEL Subscription Info] + Root --> Dialled[Dialled Service CAMEL Subscription Info] + Root --> VMS[VMS C Terminating CAMEL Subscription Info] + Root --> SS[SS Invocation Notification CAMEL Subscription Info] + + Originating --> TDPList1[TDP Data List] + TDPList1 --> OBCSM1[O-BCSM CAMEL TDP Data (1)] + OBCSM1 --> OBCSM1_1[O-BCSM TDP] + OBCSM1 --> OBCSM1_2[DP Criteria] + OBCSM1 --> OBCSM1_3[Service Key] + OBCSM1 --> OBCSM1_4[gsmSCF Address] + OBCSM1 --> OBCSM1_5[Default Call Handling] + OBCSM1 --> OBCSM1_6[.....] + TDPList1 --> OBCSMn[O-BCSM CAMEL TDP Data (n)] + OBCSMn --> OBCSMn_1[O-BCSM TDP] + OBCSMn --> OBCSMn_2[DP Criteria] + OBCSMn --> OBCSMn_3[Service Key] + OBCSMn --> OBCSMn_4[gsmSCF Address] + OBCSMn --> OBCSMn_5[Default Call Handling] + Originating --> CAMELCap1[CAMEL Capability Handling] + + Dialled --> DPCriteriaList[DP Criteria List] + DPCriteriaList --> DPCriterion1[DP Criterion (1)] + DPCriterion1 --> DPCriterion1_1[Service Key] + DPCriterion1 --> DPCriterion1_2[gsmSCF Address] + DPCriterion1 --> DPCriterion1_3[Default Call Handling] + DPCriterion1 --> DPCriterion1_4[.....] + DPCriteriaList --> DPCriterionn[DP Criterion (n)] + DPCriterionn --> DPCriterionn_1[Service Key] + DPCriterionn --> DPCriterionn_2[gsmSCF Address] + DPCriterionn --> DPCriterionn_3[Default Call Handling] + Dialled --> CAMELCap2[CAMEL Capability Handling] + + VMS --> TDPList2[TDP Data List] + TDPList2 --> VTBCSM1[VT-BCSM CAMEL TDP Data (1)] + VTBCSM1 --> VTBCSM1_1[VT-BCSM TDP] + VTBCSM1 --> VTBCSM1_2[DP Criteria] + VTBCSM1 --> VTBCSM1_3[Service Key] + VTBCSM1 --> VTBCSM1_4[gsmSCF Address] + VTBCSM1 --> VTBCSM1_5[Default Call Handling] + VTBCSM1 --> VTBCSM1_6[.....] + TDPList2 --> VTBCSMn[VT-BCSM CAMEL TDP Data (n)] + VTBCSMn --> VTBCSMn_1[VT-BCSM TDP] + VTBCSMn --> VTBCSMn_2[DP Criteria] + VTBCSMn --> VTBCSMn_3[Service Key] + VTBCSMn --> VTBCSMn_4[gsmSCF Address] + VTBCSMn --> VTBCSMn_5[Default Call Handling] + VMS --> CAMELCap3[CAMEL Capability Handling] + + SS --> NotificationCriterion[Notification Criterion] + SS --> gsmSCFAddress1[gsmSCF Address] + SS --> ActivationFlag1[Activation Flag] + SS --> NotificationFlag1[Notification Flag] +``` + +A hierarchical tree diagram showing CAMEL Subscription Information. The root is 'CAMEL Subscription Information', which branches into four main categories: 'Originating CAMEL Subscription Info', 'Dialled Service CAMEL Subscription Info', 'VMS C Terminating CAMEL Subscription Info', and 'SS Invocation Notification CAMEL Subscription Info'. Each category has its own sub-elements, such as TDP Data Lists, DP Criteria Lists, and CAMEL Capability Handling. + +![A hierarchical tree diagram showing CAMEL subscription information. The root is a vertical line. From this line, four horizontal branches extend to the right. The first branch is 'Notify on Change of Subscriber Data Flag'. The second branch is 'Translation Information Flag CAMEL Subscription Information'. The third branch is 'MO SMS CAMEL Subscription Info'. The fourth branch is 'MT SMS CAMEL Subscription Info'. From the 'MT SMS CAMEL Subscription Info' branch, four more horizontal branches extend to the right: 'Mobility Management Event Notification CAMEL Subscription Info', 'Mobility Trigger List', 'Service Key', and 'gsmSCF Address'.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` +graph LR; Root[ ] --- N[Notify on Change of Subscriber Data Flag]; Root --- T[Translation Information Flag CAMEL Subscription Information]; Root --- MO[MO SMS CAMEL Subscription Info]; Root --- MT[MT SMS CAMEL Subscription Info]; MT --- M[Mobility Management Event Notification CAMEL Subscription Info]; MT --- L[Mobility Trigger List]; MT --- K[Service Key]; MT --- A[gsmSCF Address]; style Root fill:none,stroke:none +``` + +A hierarchical tree diagram showing CAMEL subscription information. The root is a vertical line. From this line, four horizontal branches extend to the right. The first branch is 'Notify on Change of Subscriber Data Flag'. The second branch is 'Translation Information Flag CAMEL Subscription Information'. The third branch is 'MO SMS CAMEL Subscription Info'. The fourth branch is 'MT SMS CAMEL Subscription Info'. From the 'MT SMS CAMEL Subscription Info' branch, four more horizontal branches extend to the right: 'Mobility Management Event Notification CAMEL Subscription Info', 'Mobility Trigger List', 'Service Key', and 'gsmSCF Address'. + +NOTE: For detailed information see 3GPP TS 23.072, 3GPP TS 23.078 and 3GPP TS 29.002. + +**Figure 15: CAMEL subscription info** + +![Hierarchical tree diagram of LCS Information structure](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +LCS Information +├── GMLC List +│ ├── GMLC Address (1) +│ └── GMLC Address (n) +├── LCS Privacy Exception List +│ ├── Universal Privacy Class +│ │ ├── Provisioning State +│ │ ├── Activation State +│ │ └── Registration State +│ ├── Call/Session Related Privacy Class +│ │ ├── Provisioning State +│ │ ├── Activation State +│ │ ├── Registration State +│ │ ├── Notification to MS User +│ │ └── External Client List +│ │ ├── External Client (1) +│ │ │ ├── Address +│ │ │ ├── Notification to MS User +│ │ │ └── GMLC restriction +│ │ │ ..... +│ │ └── External Client (n) +│ │ ├── Address +│ │ ├── Notification to MS User +│ │ └── GMLC restriction +│ ├── Call/Session Unrelated Privacy Class +│ │ ├── Provisioning State +│ │ ├── Activation State +│ │ ├── Registration State +│ │ ├── External Client List +│ │ │ ├── External Client (1) +│ │ │ │ ├── Address +│ │ │ │ ├── Notification to MS User +│ │ │ │ └── GMLC restriction +│ │ │ │ ..... +│ │ │ └── External Client (n) +│ │ │ ├── Address +│ │ │ ├── Notification to MS User +│ │ │ └── GMLC restriction +│ │ └── Notification to MS User +│ ├── PLMN Operator Privacy Class +│ │ ├── Provisioning State +│ │ ├── Activation State +│ │ ├── Registration State +│ │ └── PLMN Client List +│ │ ├── PLMN client ID (1) +│ │ │ ..... +│ │ └── PLMN client ID (n) +├── MO-LR List +│ ├── Basic Self Location Class +│ │ ├── Provisioning State +│ │ ├── Activation State +│ │ └── Registration State +│ ├── Autonomous Self Location Class +│ │ ├── Provisioning State +│ │ ├── Activation State +│ │ └── Registration State +│ └── Transfer to Third Party Class +│ ├── Provisioning State +│ ├── Activation State +│ └── Registration State +├── LCS Service Types +├── Provisioning State +├── Activation State +├── Registration State +├── Service Type List +└── Service Type Identity (1) + +``` + +Hierarchical tree diagram of LCS Information structure + +![Diagram showing LCS Information structure with Notification to MS User and Service Type Identity (n) components.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` +graph TD + subgraph LCS_Information [LCS Information] + direction TB + L1[Notification to MS User] --> L1_1[GMLC restriction] + L1_2[....] + L2[Service Type Identity (n)] --> L2_1[Notification to MS User] + L2_1 --> L2_2[GMLC restriction] + end +``` + +Diagram showing LCS Information structure with Notification to MS User and Service Type Identity (n) components. + +NOTE: For detailed information see 3GPP TS 23.271 and 3GPP TS 29.002. + +**Figure 16: LCS Information** + +![Diagram showing PDP Context List structure with multiple PDP Context entries.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +``` +graph TD + subgraph PDP_Context_List [PDP Context List] + direction TB + L1[PDP Context (1)] --> L1_1[PDP Context Identifier] + L1_2[PDP Type] + L1_3[PDP Address] + L1_4[VPLMN Address Allowed] + L1_5[Quality of Service Subscribed] + L1_6[Access Point Name] + L1_7[PDP Context Charging Characteristics] + L1_8[....] + L2[PDP Context (n)] + end +``` + +Diagram showing PDP Context List structure with multiple PDP Context entries. + +NOTE: The figure shows the information in the SGSN. For detailed information see 3GPP TS 23.060. For information about the GGSN information, see 3GPP TS 23.008. + +**Figure 17: GPRS subscription data** + +![Diagram showing APN Configuration List structure with Default Context and multiple APN Configuration entries.](9ee1a10ae91d4878e24b2e7dbaa95c2e_img.jpg) + +``` +graph TD + subgraph APN_Configuration_List [APN Configuration List] + direction TB + L1[Default Context] + L2[APN Configuration (1)] --> L2_1[Context Identifier] + L2_2[PDN Type] + L2_3[Served Party IPv4 Address] + L2_4[APN] + L2_5[EPS QoS Subscribed] + L2_6[PDN GW Identity] + L2_7[PDN GW Allocation Type] + L2_8[VPLMN Address Allowed] + L2_9[Charging Characteristics] + L2_10[AMBR] + L2_11[Specific APN Info List] + L2_12[Served Party IPv6 Address] + L2_13[....] + L3[APN Configuration (n)] + end +``` + +Diagram showing APN Configuration List structure with Default Context and multiple APN Configuration entries. + +**Figure 17a: EPS subscription data** + +![Diagram of LSA data in the VLR showing a hierarchical structure starting with LSA Only Access Indicator and LSA Data List, which contains multiple LSA Data entries (1 to n), each with Identity, Attributes, and Active Mode Indicator.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +|—LSA Only Access Indicator +|—LSA Data List + | + |—LSA Data (1) + | |—LSA Identity + | |—LSA Attributes + | |—LSA Active Mode Indicator + | + | . . . . + | + |—LSA Data (n) + +``` + +Diagram of LSA data in the VLR showing a hierarchical structure starting with LSA Only Access Indicator and LSA Data List, which contains multiple LSA Data entries (1 to n), each with Identity, Attributes, and Active Mode Indicator. + +NOTE: For detailed information see 3GPP TS 23.073 and 3GPP TS 29.002. + +**Figure 18: LSA data in the VLR** + +![Diagram of LSA data in the SGSN showing a hierarchical structure starting with LSA Only Access Indicator and LSA Data List, which contains multiple LSA Data entries (1 to n), each with Identity, Attributes, and Active Mode Indicator.](f0a97d0d3818a253c1d2a009966081b1_img.jpg) + +``` + +|—LSA Only Access Indicator +|—LSA Data List + | + |—LSA Data (1) + | |—LSA Identity + | |—LSA Attributes + | |—LSA Active Mode Indicator + | + | . . . . + | + |—LSA Data (n) + +``` + +Diagram of LSA data in the SGSN showing a hierarchical structure starting with LSA Only Access Indicator and LSA Data List, which contains multiple LSA Data entries (1 to n), each with Identity, Attributes, and Active Mode Indicator. + +NOTE: For detailed information see 3GPP TS 23.073 and 3GPP TS 29.002. + +**Figure 19: LSA data in the SGSN** + +![Diagram showing a single entry for IST Alert Timer.](e9b43ac020435f8121e8592f31afdc52_img.jpg) + +``` + +|—IST Alert Timer + +``` + +Diagram showing a single entry for IST Alert Timer. + +NOTE: For detailed information see 3GPP TS 43.035 and 3GPP TS 29.002. + +**Figure 20: IST data in the VLR** + +└Age Indicator + +NOTE: For detailed information see TS 23.116 and TS 29.002. + +**Figure 21: Super-Charger Information** + +![Hierarchical tree diagram for Figure 21: Super-Charger Information. The root is 'SGSN CAMEL subscription information', which branches into 'GPRS CAMEL Subscription Information', 'MO SMS CAMEL Subscription Info', 'MT SMS CAMEL Subscription Info', and 'Mobility Management Event for GPRS Notification CAMEL Subscription Info'. 'GPRS CAMEL Subscription Information' further branches into 'TDP Data List', 'CAMEL Capability Handling', and 'GPRS CAMEL TDP Data (1)' through '(n)'. Each 'GPRS CAMEL TDP Data' entry contains 'GPRS TDP', 'Service Key', 'gsmSCF Address', and 'Default GPRS Handling'.](6470d350326789d5306eabcb76533951_img.jpg) + +``` + +└SGSN CAMEL subscription information +├ GPRS CAMEL Subscription Information +│ ├── TDP Data List +│ │ ├── GPRS CAMEL TDP Data (1) +│ │ │ ├── GPRS TDP +│ │ │ ├── Service Key +│ │ │ ├── gsmSCF Address +│ │ │ └ Default GPRS Handling +│ │ ├── .... +│ │ └ GPRS CAMEL TDP Data (n) +│ │ ├── GPRS TDP +│ │ ├── Service Key +│ │ ├── gsmSCF Address +│ │ └ Default GPRS Handling +│ └ CAMEL Capability Handling +├ MO SMS CAMEL Subscription Info +├ MT SMS CAMEL Subscription Info +└ Mobility Management Event for GPRS Notification + CAMEL Subscription Info + ├── Mobility Trigger List + ├── Service Key + └ gsmSCF Address + +``` + +Hierarchical tree diagram for Figure 21: Super-Charger Information. The root is 'SGSN CAMEL subscription information', which branches into 'GPRS CAMEL Subscription Information', 'MO SMS CAMEL Subscription Info', 'MT SMS CAMEL Subscription Info', and 'Mobility Management Event for GPRS Notification CAMEL Subscription Info'. 'GPRS CAMEL Subscription Information' further branches into 'TDP Data List', 'CAMEL Capability Handling', and 'GPRS CAMEL TDP Data (1)' through '(n)'. Each 'GPRS CAMEL TDP Data' entry contains 'GPRS TDP', 'Service Key', 'gsmSCF Address', and 'Default GPRS Handling'. + +**Figure 22: SGSN CAMEL subscription info** + +![Hierarchical tree diagram for Figure 23a: MO SMS CAMEL Subscription Info. The root is 'MO SMS CAMEL Subscription Info', which branches into 'TDP Data List' and 'CAMEL Capability Handling'. 'TDP Data List' further branches into 'MO SMS CAMEL TDP Data (1)' through '(n)'. Each 'MO SMS CAMEL TDP Data' entry contains 'MO SMS TDP', 'Service Key', 'gsmSCF Address', and 'Default SMS Handling'.](5b6e139e89c6ce90107ea7d7d77620a0_img.jpg) + +``` + +└ MO SMS CAMEL Subscription Info +├ TDP Data List +│ ├── MO SMS CAMEL TDP Data (1) +│ │ ├── MO SMS TDP +│ │ ├── Service Key +│ │ ├── gsmSCF Address +│ │ └ Default SMS Handling +│ ├── .... +│ └ MO SMS CAMEL TDP Data (n) +│ ├── MO SMS TDP +│ ├── Service Key +│ ├── gsmSCF Address +│ └ Default SMS Handling +└ CAMEL Capability Handling + +``` + +Hierarchical tree diagram for Figure 23a: MO SMS CAMEL Subscription Info. The root is 'MO SMS CAMEL Subscription Info', which branches into 'TDP Data List' and 'CAMEL Capability Handling'. 'TDP Data List' further branches into 'MO SMS CAMEL TDP Data (1)' through '(n)'. Each 'MO SMS CAMEL TDP Data' entry contains 'MO SMS TDP', 'Service Key', 'gsmSCF Address', and 'Default SMS Handling'. + +**Figure 23a: MO SMS CAMEL Subscription Info** + +![Figure 23b: MT SMS CAMEL Subscription Info. A hierarchical tree diagram showing the structure of MT SMS CAMEL Subscription Info. The root is 'MT SMS CAMEL Subscription Info', which branches into 'TDP Data List' and 'CAMEL Capability Handling'. 'TDP Data List' branches into 'MT SMS CAMEL TDP Data (1)' and 'MT SMS CAMEL TDP Data (n)'. 'MT SMS CAMEL TDP Data (1)' and 'MT SMS CAMEL TDP Data (n)' both branch into 'MT SMS TDP', 'DP Criteria', 'Service Key', 'gsmSCF Address', and 'Default SMS Handling'. There is an ellipsis between 'MT SMS CAMEL TDP Data (1)' and 'MT SMS CAMEL TDP Data (n)'.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +├ MT SMS CAMEL Subscription Info +│ ├ TDP Data List +│ │ ├ MT SMS CAMEL TDP Data (1) +│ │ │ ├ MT SMS TDP +│ │ │ ├ DP Criteria +│ │ │ ├ Service Key +│ │ │ ├ gsmSCF Address +│ │ │ └ Default SMS Handling +│ │ ├ . . . . . +│ │ └ MT SMS CAMEL TDP Data (n) +│ │ ├ MT SMS TDP +│ │ ├ DP Criteria +│ │ ├ Service Key +│ │ ├ gsmSCF Address +│ │ └ Default SMS Handling +│ └ CAMEL Capability Handling + +``` + +Figure 23b: MT SMS CAMEL Subscription Info. A hierarchical tree diagram showing the structure of MT SMS CAMEL Subscription Info. The root is 'MT SMS CAMEL Subscription Info', which branches into 'TDP Data List' and 'CAMEL Capability Handling'. 'TDP Data List' branches into 'MT SMS CAMEL TDP Data (1)' and 'MT SMS CAMEL TDP Data (n)'. 'MT SMS CAMEL TDP Data (1)' and 'MT SMS CAMEL TDP Data (n)' both branch into 'MT SMS TDP', 'DP Criteria', 'Service Key', 'gsmSCF Address', and 'Default SMS Handling'. There is an ellipsis between 'MT SMS CAMEL TDP Data (1)' and 'MT SMS CAMEL TDP Data (n)'. + +**Figure 23b: MT SMS CAMEL Subscription Info** + +![Figure 24: Bearer Service Priority Data in the VLR. A tree diagram showing 'CS Allocation/Retention priority'.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +``` +└ CS Allocation/Retention priority +``` + +Figure 24: Bearer Service Priority Data in the VLR. A tree diagram showing 'CS Allocation/Retention priority'. + +NOTE: For detailed information see 3GPP TS 23.008. + +**Figure 24: Bearer Service Priority Data in the VLR** + +![Figure 25: Charging Information. A tree diagram showing 'Subscribed Charging Characteristics'.](dc1f232cfd39be5c20b21374ad4c04c0_img.jpg) + +``` +└ Subscribed Charging Characteristics +``` + +Figure 25: Charging Information. A tree diagram showing 'Subscribed Charging Characteristics'. + +NOTE: For detailed information see 3GPP TS 23.060. + +**Figure 25: Charging Information.** + +![Figure 26: Administrative Restriction Information in the VLR. A tree diagram showing 'Access Restriction Data'.](ca5dc5fde2061d0ca2051ef7840fc842_img.jpg) + +``` +└ Access Restriction Data +``` + +Figure 26: Administrative Restriction Information in the VLR. A tree diagram showing 'Access Restriction Data'. + +NOTE: For detailed information see 3GPP TS 23.012 [34]. + +**Figure 26: Administrative Restriction Information in the VLR** + +# Annex A (informative): Change history old + +| Change history | | | | | | | +|----------------|-----------|---------|-------|---------|-------------|----------------------------------------------------------------------------------------| +| TSG CN# | Spec | Version | CR | | New Version | Subject/Comment | +| Apr 1999 | GSM 03.16 | 7.0.0 | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.016 | | | | 3.0.0 | Approved at CN#03 | +| CN#04 | 23.016 | 3.0.0 | 001 | R99 | 3.1.0 | Introduction of TIF-CSI for Call Deflection | +| CN#04 | 23.016 | | 002r1 | R99 | 3.1.0 | Missing SS-CSI in description of CAMEL Subscription | +| CN#05 | 23.016 | 3.1.0 | 003r1 | R99 | 3.2.0 | Non-CAMEL IST implementation | +| CN#06 | 23.016 | 3.2.1 | 004r3 | R99 | 3.3.0 | Introduction of the Super-Charger Concept in TS 23.016 | +| CN#06 | 23.016 | 3.2.1 | 006 | R99 | 3.3.0 | Support of Subscriber Data Management in the HLR and VLR for LCS | +| CN#06 | 23.016 | 3.2.1 | 009 | R99 | 3.3.0 | Correction of VLR subscription Data | +| CN#06 | 23.016 | 3.2.1 | 008r1 | R99 | 3.3.0 | Introduction of CAMEL phase 3 | +| CN#07 | 23.016 | 3.3.0 | 010 | R99 | 3.4.0 | Correction of LSA Information | +| CN#07 | 23.016 | 3.3.0 | 011r1 | R99 | 3.4.0 | The addition of priority information | +| CN#07 | 23.016 | 3.3.0 | 012r2 | R99 | 3.4.0 | Introduction of subscriber data for Multicall | +| CN#08 | 23.016 | 3.4.0 | 013r1 | R99 | 3.5.0 | Addition of information related to charging | +| CN#08 | 23.016 | 3.4.0 | 014 | R99 | 3.5.0 | Clarifications on GSM vs. UMTS specific parts | +| CN#08 | 23.016 | 3.4.0 | 015 | R99 | 3.5.0 | Addition of charging characteristics per PDP context | +| CN#09 | 23.016 | 3.5.0 | 016 | R99 | 3.6.0 | Correction to Delete Subscriber Data | +| CN#11 | 23.016 | 3.6.0 | 018 | R99 | 3.7.0 | Alignment about Notification to MS User between 29.002 , 23.171(LCS Stage2) and 23.016 | +| CN#11 | 23.016 | 3.7.0 | | Rel-4 | 4.0.0 | Version increased from R99 to Rel-4 after CN#11 | +| CN#11 | 23.016 | 3.7.0 | 017r1 | Rel-4 | 4.0.0 | Add three subscriber statuses to the ODB Data for GPRS services | +| CN#11 | 23.016 | 3.7.0 | 019r2 | Rel-4 | 4.0.0 | Extension of call related privacy class for LCS Release 4 | +| CN#11 | 23.016 | 3.7.0 | 020r1 | Rel-4 | 4.0.0 | PS domain support for LCS Release 4 | +| CN#15 | 23.016 | 4.0.0 | 023r2 | Rel-4 | 4.1.0 | Clarification on overlapping data | +| CN#15 | 23.016 | 4.0.0 | | Rel-4 | 4.1.0 | References updated | +| CN#15 | 23.016 | 4.1.0 | 021 | Rel-5 | 5.0.0 | Collective CR on 23.016 | +| CN#16 | 23.016 | 5.0.0 | 025 | Rel-5 | 5.1.0 | Clarification of introducing Session related and unrelated class | +| CN#16 | 23.016 | 5.0.0 | 026 | Rel-5 | 5.1.0 | LCS: Codeword and Service Type | +| CN#17 | 23.016 | 5.1.0 | 029 | Rel-5 | 5.2.0 | Introduction of Call Deflection | +| CN#19 | 23.016 | 5.2.0 | 030r1 | Rel-6 | 6.0.0 | Introduction of Call Barring for SMS in PS domain | +| CN#23 | 23.016 | 6.0.0 | 034r2 | Rel-6 | 6.1.0 | Correction to SS data for LCS SS | +| CN#23 | 23.016 | 6.0.0 | 035r1 | Rel-6 | 6.1.0 | Include administrative restriction subscription parameter | +| CT#36 | 23.016 | 6.1.0 | | Rel-7 | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.016 | 7.0.0 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.016 | 8.0.0 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| CT#47 | 23.016 | 9.0.0 | 0037 | Rel-9 | 9.1.0 | Addition of EPS Subscription Information | +| 2011-03 | 23.016 | 9.1.0 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 23.016 | 10.0.0 | - | Rel-11 | 11.0.0 | Update to Rel-11 version (MCC) | +| 2014-09 | 23.016 | 11.0.0 | - | Rel-12 | 12.0.0 | Update to Rel-12 version (MCC) | +| 2015-12 | 23.016 | 12.0.0 | - | Rel-13 | 13.0.0 | Update to Rel-13 version (MCC) | +| 2017-03 | 23.016 | 13.0.0 | - | Rel-14 | 14.0.0 | Update to Rel-14 version (MCC) | +| 2018-06 | 23.016 | 14.0.0 | - | Rel-15 | 15.0.0 | Update to Rel-15 version (MCC) | +| 2020-07 | - | - | - | - | 16.0.0 | Update to Rel-16 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23018/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23018/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc5ad8c3bf7c9014e19a82269d7a994ec8c850f0 --- /dev/null +++ b/marked/Rel-16/23_series/23018/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed981b259be44faf9a3ecc26b1be01129edbeb641fad816ca49cd4ed9ff54ce7 +size 67346 diff --git a/marked/Rel-16/23_series/23018/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23018/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0548ea825d32b2903bac56675828484ff1ee2316 --- /dev/null +++ b/marked/Rel-16/23_series/23018/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e37f5a8f88879217fb717179c28ae94aeba01a0c9c21bd7b7739b308a9513b4f +size 164090 diff --git a/marked/Rel-16/23_series/23018/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-16/23_series/23018/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cfc796f7a465d457c9c3dad5ac9cc0d87eae0a03 --- /dev/null +++ b/marked/Rel-16/23_series/23018/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:642919f9a561b535f8ddb528cc90a7f09d4dacb9c803f1d138981777bffaeb6f +size 136461 diff --git a/marked/Rel-16/23_series/23018/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/23_series/23018/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d62a95a2a7a44f7dfbcad0f94a2d52e7fab28220 --- /dev/null +++ b/marked/Rel-16/23_series/23018/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa004050d07c0c1248df9b07249f1f257d325e9fcd0dbb5b84e43e7ec20ac1ed +size 98508 diff --git a/marked/Rel-16/23_series/23018/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-16/23_series/23018/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa335c30a98c500bc9d5e68352c8f755fe743471 --- /dev/null +++ b/marked/Rel-16/23_series/23018/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00f0e39c40f67140f8a76d30b09c10e19ee7805ce993e087d81913c095d03446 +size 69081 diff --git a/marked/Rel-16/23_series/23018/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-16/23_series/23018/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bdab49f80f2c6800afe0e6bc068d2f76fd15ca9 --- /dev/null +++ b/marked/Rel-16/23_series/23018/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5310db982cdeef8ad7d1581b521b67d3767ec145e7b20649e542ff8ff78c3e64 +size 115806 diff --git a/marked/Rel-16/23_series/23018/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-16/23_series/23018/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..946eacaa69e189abc91033b91fc28c0c5630049b --- /dev/null +++ b/marked/Rel-16/23_series/23018/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f4782ff6cedcba13d3a087f6e00337a7386cd4132a49501bb43957aeedb3307 +size 74470 diff --git a/marked/Rel-16/23_series/23018/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-16/23_series/23018/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..760eb44cf2f609b37d10d340cd91af3b5a51048c --- /dev/null +++ b/marked/Rel-16/23_series/23018/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5d21d2895e24cc789c8d95dc70d238ac804690089de10f98cfaaaacdf8f8b570 +size 135825 diff --git a/marked/Rel-16/23_series/23018/17431d8b59408f09df7552d8bdbaa015_img.jpg b/marked/Rel-16/23_series/23018/17431d8b59408f09df7552d8bdbaa015_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41477310529acf9fd104b4115c61cf4ec72b5e5b --- /dev/null +++ b/marked/Rel-16/23_series/23018/17431d8b59408f09df7552d8bdbaa015_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed260ded5f414ce9c5a71e8ccd93d21e118e7f035957f64b7369cbe82cf9c5f1 +size 68977 diff --git a/marked/Rel-16/23_series/23018/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-16/23_series/23018/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07757dd501b8a7083c01660d1946eb603e159867 --- /dev/null +++ b/marked/Rel-16/23_series/23018/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdfb2fcb9d71e3d6d95be541a6e90fe10a1ad0359c41757ce3af9d7f200cb1a8 +size 90334 diff --git a/marked/Rel-16/23_series/23018/184d3d9a856c77aae93652f4fe30f752_img.jpg b/marked/Rel-16/23_series/23018/184d3d9a856c77aae93652f4fe30f752_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6350480ec760f1856734b50cd604370ef89b76f8 --- /dev/null +++ b/marked/Rel-16/23_series/23018/184d3d9a856c77aae93652f4fe30f752_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b87dce442ef0753700c3983b1e49da7dea6df469406098cff45445d5d209e769 +size 140038 diff --git a/marked/Rel-16/23_series/23018/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/23_series/23018/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c77f0d85cd627d60fa609eb78f97d1195fcbc6e --- /dev/null +++ b/marked/Rel-16/23_series/23018/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cd30d24eb6ec6e6f904e9cb762ada810a2b496e31cb279cc2b3f1af67678a7c +size 132766 diff --git a/marked/Rel-16/23_series/23018/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/marked/Rel-16/23_series/23018/18bb06865e2dada3656ea3d57f290f7f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c527a26a0b4e01ff0eaabc357c06f6f1942cc5d4 --- /dev/null +++ b/marked/Rel-16/23_series/23018/18bb06865e2dada3656ea3d57f290f7f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e63099e5629b2e13d415035e50483d94560d6cf0c0564a63c2b7ace0c68e64db +size 119174 diff --git a/marked/Rel-16/23_series/23018/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23018/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b124dc322e0fc91f7433636e2532be82b4a9820 --- /dev/null +++ b/marked/Rel-16/23_series/23018/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:80e0c795cf20409e447af6b5c24997663e032e3f30b863d557e65659afcde214 +size 123851 diff --git a/marked/Rel-16/23_series/23018/1bc1746388cb64bf23b356ce2365dfc2_img.jpg b/marked/Rel-16/23_series/23018/1bc1746388cb64bf23b356ce2365dfc2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b0974e8aed2aab5cf3168e8a9dd7704f7fcab10 --- /dev/null +++ b/marked/Rel-16/23_series/23018/1bc1746388cb64bf23b356ce2365dfc2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c624ff1df541e612c4dcf6d8fac9fcf4b21a98bce867d73e2deb97126aaf29ac +size 120851 diff --git a/marked/Rel-16/23_series/23018/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg b/marked/Rel-16/23_series/23018/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19a66e7d21195e860cf245f9b7fe884013c7dd0b --- /dev/null +++ b/marked/Rel-16/23_series/23018/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff2b2ccaac5f1e57656ccec9e7833b9269b84c2285e3c13187a1e6128c2b336f +size 82001 diff --git a/marked/Rel-16/23_series/23018/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-16/23_series/23018/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63a9316e6daa3d74c5c2199a13dca3c271233cb2 --- /dev/null +++ b/marked/Rel-16/23_series/23018/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:130fe433894839759805e8201c5edae72686e5ea7b0da01fedaa427489013cc2 +size 119283 diff --git a/marked/Rel-16/23_series/23018/245166735676c675f98f535bc4c6f0a1_img.jpg b/marked/Rel-16/23_series/23018/245166735676c675f98f535bc4c6f0a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9366dd7fa710058a58a8f437d63d08fe8c71b04 --- /dev/null +++ b/marked/Rel-16/23_series/23018/245166735676c675f98f535bc4c6f0a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0048f20833bb2221e5773ecd8982e174210dbb7c7135a9c51c738d5d0568bb32 +size 153074 diff --git a/marked/Rel-16/23_series/23018/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg b/marked/Rel-16/23_series/23018/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82f4879122db42030047190cbfdf5e3df1bea1dd --- /dev/null +++ b/marked/Rel-16/23_series/23018/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89e3084b1257da03d4c82259d120a7f0d50a5b0e2066c3e627229e378b375e56 +size 67243 diff --git a/marked/Rel-16/23_series/23018/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23018/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c641579f05db1af746308ea9ebdfcc20edfb976 --- /dev/null +++ b/marked/Rel-16/23_series/23018/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b4a5d81d2345261927ca542966e6ff003fbd02b45b3a0cbd87c8180681b8a22 +size 142813 diff --git a/marked/Rel-16/23_series/23018/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23018/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ac2a4da851d9f43571d62dadfe8528ff152c153 --- /dev/null +++ b/marked/Rel-16/23_series/23018/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0a36ae20f52c2275bd121cf9d2a444c34c3ca07ed7a4aabcdb9272efb3b10e2 +size 112599 diff --git a/marked/Rel-16/23_series/23018/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/23_series/23018/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a8bd9bb632b45a3ce7d7c88114aea574f60e9f7 --- /dev/null +++ b/marked/Rel-16/23_series/23018/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9fb0861431a4dd6bf13d7fbd5ea336c443d3422845ae597df4ccf00b56aea971 +size 76922 diff --git a/marked/Rel-16/23_series/23018/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23018/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc94474e995368e25f4c9ce2d8a28b2fa2035622 --- /dev/null +++ b/marked/Rel-16/23_series/23018/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d98ca1c88c319444f528748fe3a41db8c4891766b46f6ce4159996dc7b9adbb9 +size 197834 diff --git a/marked/Rel-16/23_series/23018/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/23_series/23018/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d6da7f1bb6771ca073f9f4e2e94c2c7ff092432 --- /dev/null +++ b/marked/Rel-16/23_series/23018/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce063da1339ef3dd222c87f494be897644df59d4a99ed5bb996c3bc1f785dc29 +size 142632 diff --git a/marked/Rel-16/23_series/23018/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23018/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..901b9a7a75482fff307feeb521a65596be7f4119 --- /dev/null +++ b/marked/Rel-16/23_series/23018/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8d2ebbcab8699fe38fa610bce6589695f9cc0ed4c27f7f6edd9faadbec287975 +size 207203 diff --git a/marked/Rel-16/23_series/23018/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Rel-16/23_series/23018/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2bee29de7366043126be5f8946424f6f1244c53 --- /dev/null +++ b/marked/Rel-16/23_series/23018/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5a812803e24ef4390e0f08252eb4f9a1ceec34c3e4dddcff501be2642fd4de7 +size 127738 diff --git a/marked/Rel-16/23_series/23018/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/23_series/23018/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcb50462bbe18563ed4bf8bf54e5f4a1d09517f3 --- /dev/null +++ b/marked/Rel-16/23_series/23018/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28c6e70a51cb3379de585470f4ca5da78075fe3cc7aeccdb39d051ef49570dd7 +size 117101 diff --git a/marked/Rel-16/23_series/23018/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-16/23_series/23018/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb86febbe13f47f645bc583b21678222a7bde73a --- /dev/null +++ b/marked/Rel-16/23_series/23018/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1389a11bb914570cd9ad8590cfd8774deb2e694a28115d44cfdd79188f989ff7 +size 110098 diff --git a/marked/Rel-16/23_series/23018/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-16/23_series/23018/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9aa3f905bc3762b9fb013c2c5f1f5d6b003b9a9b --- /dev/null +++ b/marked/Rel-16/23_series/23018/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23b7f52a8de8dfcdbdc9fb804702e179011307d2a777eedd9f9c2b6d7788c0d8 +size 203843 diff --git a/marked/Rel-16/23_series/23018/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23018/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..093b3ad11d0d5f803eb92df28d98fd35215063a6 --- /dev/null +++ b/marked/Rel-16/23_series/23018/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5171aeacec52619ade34d2bad2d5763eb4d31b50c89fba0531975ba9f866c59d +size 156579 diff --git a/marked/Rel-16/23_series/23018/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/23_series/23018/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..707322352eca8d0d293ad6824d01d268c3d483c6 --- /dev/null +++ b/marked/Rel-16/23_series/23018/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82921d57f3a6b4023e6d1ef46cd788825546d329ec0f6e1013999ccac53181e1 +size 94990 diff --git a/marked/Rel-16/23_series/23018/3334fcca5dac808f4fd3840aba35bc2e_img.jpg b/marked/Rel-16/23_series/23018/3334fcca5dac808f4fd3840aba35bc2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8736d177b7990ff230e4990b2ebc2e82eee19d80 --- /dev/null +++ b/marked/Rel-16/23_series/23018/3334fcca5dac808f4fd3840aba35bc2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d29fc8eb0c052c78a05d5336f1a73198f0003284c762d8e05dfecd66e6b40f9 +size 75161 diff --git a/marked/Rel-16/23_series/23018/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-16/23_series/23018/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc76ce897565fc804007d2e43ca7adf66f5a1344 --- /dev/null +++ b/marked/Rel-16/23_series/23018/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5c286bb036000c342064ea8f99983c9c887b068bff1d4bec3060be61bd32b79 +size 99140 diff --git a/marked/Rel-16/23_series/23018/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23018/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b5e3aa90c8f05f254662d77ff8c686551030f84 --- /dev/null +++ b/marked/Rel-16/23_series/23018/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:17fcd0444ea8cea5b63464d04dbb2ed5ba2748768eac9065efc151a231e28d93 +size 96406 diff --git a/marked/Rel-16/23_series/23018/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-16/23_series/23018/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa2f13295aa86aea54f46a47f927b94d3805e0c8 --- /dev/null +++ b/marked/Rel-16/23_series/23018/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43dd9db2f38294dda8989a0c98ae9ebb1ba1754b6829e301983eeea58cd3d997 +size 75860 diff --git a/marked/Rel-16/23_series/23018/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-16/23_series/23018/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddd42b08d559e596c09acb875b6c88395152c1ae --- /dev/null +++ b/marked/Rel-16/23_series/23018/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34866148dbfb0837c0b071db7477f1b53021e7edb5da422e4a6e617a905971d2 +size 70160 diff --git a/marked/Rel-16/23_series/23018/38d82ffe820e339811b396206f40a201_img.jpg b/marked/Rel-16/23_series/23018/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f189b1bf1d661782f9eb8234a3a9662cdfc1080 --- /dev/null +++ b/marked/Rel-16/23_series/23018/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:575e00229100df9b79763af01b5ea53bdf3037116bf51f04667856fe66541eca +size 91506 diff --git a/marked/Rel-16/23_series/23018/3ec35c497a0765a1a885c85f214b1bef_img.jpg b/marked/Rel-16/23_series/23018/3ec35c497a0765a1a885c85f214b1bef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..236283af42532b4f41a0c7cc739c36a002c1adc0 --- /dev/null +++ b/marked/Rel-16/23_series/23018/3ec35c497a0765a1a885c85f214b1bef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea3dc8ec5cd0c2505d335e865ccea2bd9d2b1175fad8a32a0d8fbe04a8864947 +size 75363 diff --git a/marked/Rel-16/23_series/23018/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/23_series/23018/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6240761748d8d581461f56e7ae923a8ffa1edf0f --- /dev/null +++ b/marked/Rel-16/23_series/23018/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b93c0a20572a0d6f48c29a26483cfee026af7cdfd13281e7da69141e122646f +size 116048 diff --git a/marked/Rel-16/23_series/23018/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/marked/Rel-16/23_series/23018/4806f9f95fff13a30d6523bd6ffeac63_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c5e05fa4fddf2af54b84fdff1f1bbe98914113e --- /dev/null +++ b/marked/Rel-16/23_series/23018/4806f9f95fff13a30d6523bd6ffeac63_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a8b7ae5fba6715f1698d2bc080e0aee4725a1a4455b310d1d3981182def0f67 +size 81590 diff --git a/marked/Rel-16/23_series/23018/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-16/23_series/23018/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0179b3aa84ef2db59667a5197d1ceaaa80be4e0a --- /dev/null +++ b/marked/Rel-16/23_series/23018/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:92202c20d9447b776c35ccda41bfd1cecd48b58ff21058a539a9af79f8b8dd22 +size 91874 diff --git a/marked/Rel-16/23_series/23018/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-16/23_series/23018/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1477c55046920c20f012ebaaea6130fa483eaf8f --- /dev/null +++ b/marked/Rel-16/23_series/23018/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ff861499d4306c823baeb5b8fa0b14023f5eaf9fb67ae8938d1e940eaeef401e +size 106380 diff --git a/marked/Rel-16/23_series/23018/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/23_series/23018/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00efb2ed6ec386389ae44651588de7b3364799fb --- /dev/null +++ b/marked/Rel-16/23_series/23018/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5609c3c305c5951e701cf4b59d4819325c543fe94821ff4a81025a06dc277b33 +size 102564 diff --git a/marked/Rel-16/23_series/23018/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/marked/Rel-16/23_series/23018/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..430d499b91bd3d77d926f4e01c9b5aec15f1d6eb --- /dev/null +++ b/marked/Rel-16/23_series/23018/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26fbbb3262e01ad908ebdcc761c82aaa1278b634d5f21aef0c753748b1d33004 +size 146322 diff --git a/marked/Rel-16/23_series/23018/536768a30136cd5c2d57f46c25d1d804_img.jpg b/marked/Rel-16/23_series/23018/536768a30136cd5c2d57f46c25d1d804_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a899daad626e9ef2148de3816208f26d1ced9c7b --- /dev/null +++ b/marked/Rel-16/23_series/23018/536768a30136cd5c2d57f46c25d1d804_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db0d01585e355d8310839a339fc6e24e9466f59b6c3514487372aaf264bd9978 +size 90180 diff --git a/marked/Rel-16/23_series/23018/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg b/marked/Rel-16/23_series/23018/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca7b6b8a2aa2352c11e5906a587743fdb106ee65 --- /dev/null +++ b/marked/Rel-16/23_series/23018/53f1f7d17b3e7aae62169c41d2a88a77_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d2c59f5f548968e5450b0b1ca87a30e303f9eccc7931f0a782aec2bcf2997a6 +size 149223 diff --git a/marked/Rel-16/23_series/23018/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/23_series/23018/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3165ac5015e573798912a2dd365eba2e7653b034 --- /dev/null +++ b/marked/Rel-16/23_series/23018/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1172b47fb6f9b40aa194c30fc7ff46d1288a1dfc0469a60ace492f6a39f4cba +size 118664 diff --git a/marked/Rel-16/23_series/23018/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-16/23_series/23018/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df90e6867e2b18d247cf7f466fad3da2ac997e23 --- /dev/null +++ b/marked/Rel-16/23_series/23018/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cc847e1f7a23c3998db65d1fe65cb7a04ae0ee56f6485dbf46e64c769a97dde6 +size 111256 diff --git a/marked/Rel-16/23_series/23018/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/23_series/23018/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..581b3044112662b8cd5d9345f0f46d1cb1d7979b --- /dev/null +++ b/marked/Rel-16/23_series/23018/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3e79d46eb3d37a90324b8025c3cdc83c7031378078a166eabbc1dd091d1f582 +size 120731 diff --git a/marked/Rel-16/23_series/23018/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23018/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e8bb732ef47ea6ac9a2404ad3ef5ebd0a14718d --- /dev/null +++ b/marked/Rel-16/23_series/23018/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0ec8f4e2dccf13ce2bb24e970b686127622e2e10eba86897300d45288791181 +size 78941 diff --git a/marked/Rel-16/23_series/23018/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-16/23_series/23018/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b0df387478e6fcbb5e32f4bfb3a683e8e338d53 --- /dev/null +++ b/marked/Rel-16/23_series/23018/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e16154f673e0bf5e0bfd2ac93f468299999d7361ce1f7256f36a7a8fb48076c +size 80717 diff --git a/marked/Rel-16/23_series/23018/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-16/23_series/23018/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97bb4c0aba46ee6feb6abb81378b3ef00df70ca4 --- /dev/null +++ b/marked/Rel-16/23_series/23018/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed20b0829e8a035af534610775a1ec68913d0e6a23067086c74dd661012a9be3 +size 121657 diff --git a/marked/Rel-16/23_series/23018/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-16/23_series/23018/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..878172cbdd80f2ca02e6c5fbd9f9627e84f3977d --- /dev/null +++ b/marked/Rel-16/23_series/23018/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7958f5553881f356d956e042de28d27ca2e215b039312928f62ad7c70d5b3012 +size 119032 diff --git a/marked/Rel-16/23_series/23018/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg b/marked/Rel-16/23_series/23018/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..414461ac85efd77d25635708bf1cea4b2ac79402 --- /dev/null +++ b/marked/Rel-16/23_series/23018/61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b58791ef6568a8a2bf6a3218338a0fc7a71204ba3318b3ef577b3576ea2b8567 +size 117549 diff --git a/marked/Rel-16/23_series/23018/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/23_series/23018/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d8ac4283f2eabd36bb44e594796f704066c8e4a2 --- /dev/null +++ b/marked/Rel-16/23_series/23018/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71381e52c6b601dba1c41037700e5869053f2c643da6d47d0d7f35dd213fac7e +size 156943 diff --git a/marked/Rel-16/23_series/23018/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/23_series/23018/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7a4478c6f5a3ded720d03eab7530efb768cd278 --- /dev/null +++ b/marked/Rel-16/23_series/23018/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67a5279b0cfef09bd0cd0a79244b499cfa1f9134f02ef3d1ca53758c9acf60c3 +size 126826 diff --git a/marked/Rel-16/23_series/23018/69467ece0a576b4c2ec3e0c89ba61527_img.jpg b/marked/Rel-16/23_series/23018/69467ece0a576b4c2ec3e0c89ba61527_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..911bf67db094182c10b64515e1a9a75f09812560 --- /dev/null +++ b/marked/Rel-16/23_series/23018/69467ece0a576b4c2ec3e0c89ba61527_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf80b8716c50c6afb50429850589eb82fd75b9b7a5d77545f7a77b39bb7c0c14 +size 68576 diff --git a/marked/Rel-16/23_series/23018/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-16/23_series/23018/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48f065ea30c4bb8c6ea9b7525ae16fd737402f1a --- /dev/null +++ b/marked/Rel-16/23_series/23018/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0fe48d8281b7c6e89436e3ce5aa130e28c08f2cee9336bef179927c64d0d5cf1 +size 171623 diff --git a/marked/Rel-16/23_series/23018/69edc2887e907309499ac95b47ab6905_img.jpg b/marked/Rel-16/23_series/23018/69edc2887e907309499ac95b47ab6905_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72691d356c31be2497277c4169f454dbe34e6011 --- /dev/null +++ b/marked/Rel-16/23_series/23018/69edc2887e907309499ac95b47ab6905_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3870f5c9b8a5241361161289ed174729a4ffed1aac13add8e700b51e225f0d30 +size 154172 diff --git a/marked/Rel-16/23_series/23018/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-16/23_series/23018/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68662167d6d93c42bb76b69a5b361c00ca17a265 --- /dev/null +++ b/marked/Rel-16/23_series/23018/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aea0492901048d96652dcc8c4d8c42df653625948aa59be4f662dfa1d899d414 +size 113946 diff --git a/marked/Rel-16/23_series/23018/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/23_series/23018/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff2d12fbd4f4af325ff3d25eefa6d8e0b6e4bd54 --- /dev/null +++ b/marked/Rel-16/23_series/23018/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10761e607f453525310c8649b74c2fdea2347e296d6a34cb20372873ce3e3308 +size 182722 diff --git a/marked/Rel-16/23_series/23018/6e9d059430baba0c363e33749f68b107_img.jpg b/marked/Rel-16/23_series/23018/6e9d059430baba0c363e33749f68b107_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f18a250464bd60da818feff40130a360c9b66cea --- /dev/null +++ b/marked/Rel-16/23_series/23018/6e9d059430baba0c363e33749f68b107_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bdaa52f53693de7f7b51d20c4942c611958cc1b2e45a8f24df339448871729f +size 106929 diff --git a/marked/Rel-16/23_series/23018/710ff83dc4a77abbe489fbf1a462845a_img.jpg b/marked/Rel-16/23_series/23018/710ff83dc4a77abbe489fbf1a462845a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1f202aaf2a025ca10fe43b8917349f44c1bbc19 --- /dev/null +++ b/marked/Rel-16/23_series/23018/710ff83dc4a77abbe489fbf1a462845a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dde108005c91f0ecd9e49375638f5345fc121f66b3f4dd3d7738a811dce154d8 +size 81538 diff --git a/marked/Rel-16/23_series/23018/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-16/23_series/23018/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3d0615d054ff9a66cb96149c9840fd8fba1bc7cf --- /dev/null +++ b/marked/Rel-16/23_series/23018/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f845ac35d213368dc9f03881fe1c0238151918b511ca7df79b04390530d26b53 +size 121751 diff --git a/marked/Rel-16/23_series/23018/72d448a65347c51989171748789c7d4b_img.jpg b/marked/Rel-16/23_series/23018/72d448a65347c51989171748789c7d4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e1d3eb26eefafcf6d4f32abca96a4aa51f681a36 --- /dev/null +++ b/marked/Rel-16/23_series/23018/72d448a65347c51989171748789c7d4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f03b3afb328e74e7861607b8f2dbf5f45a8e73836139c66babe050ca4a396111 +size 106033 diff --git a/marked/Rel-16/23_series/23018/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-16/23_series/23018/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42d1ede9af282dc22a97e51a296736ce2ef64b19 --- /dev/null +++ b/marked/Rel-16/23_series/23018/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f951b86dcceeeb7249bf2def1ce921ca74d800cad56abeb7c59af583db5d295d +size 78419 diff --git a/marked/Rel-16/23_series/23018/77464a47f104d0d647b2414591137b64_img.jpg b/marked/Rel-16/23_series/23018/77464a47f104d0d647b2414591137b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..30e75df4e60814e5d12b7bc7a4614f6e646a4db7 --- /dev/null +++ b/marked/Rel-16/23_series/23018/77464a47f104d0d647b2414591137b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4760b69d2e86831f2c7bbc1109e4690f66dfee0b7eb35af71fe4ce413fca915e +size 144322 diff --git a/marked/Rel-16/23_series/23018/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23018/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89a7f3faf0d562c1da6368fe3f598ca28dc2bda2 --- /dev/null +++ b/marked/Rel-16/23_series/23018/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b0e3e8a55595b390187fefe362f4d78e31eca969ca7f66155de09da01c9031d +size 154665 diff --git a/marked/Rel-16/23_series/23018/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/marked/Rel-16/23_series/23018/78ffccd66df9bafd96e3e081110d09dd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff72748c3ddae116e86cf746fa291ffe0a55908a --- /dev/null +++ b/marked/Rel-16/23_series/23018/78ffccd66df9bafd96e3e081110d09dd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03d50e6e3e7067ea8938910c87513067b8a87ab36a540258984f00e842626de0 +size 50050 diff --git a/marked/Rel-16/23_series/23018/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23018/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21a73c48a5b5c39dc24f250867805644161e55a5 --- /dev/null +++ b/marked/Rel-16/23_series/23018/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d89de5f0d0966e573c4725cbe625c963f9b2fad307ca120eb25082ad48439acb +size 162423 diff --git a/marked/Rel-16/23_series/23018/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/marked/Rel-16/23_series/23018/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6949751aac48dd7ee26dcb2aa5a4671a019ae85 --- /dev/null +++ b/marked/Rel-16/23_series/23018/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:51eaf2186763624058b8cfdfa841e0c5423a33a1fc6c24a970030dc40f1c2759 +size 41579 diff --git a/marked/Rel-16/23_series/23018/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/23_series/23018/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64ed6af888fb932c307ec890d8dd0d1ec1ea90a7 --- /dev/null +++ b/marked/Rel-16/23_series/23018/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45b15d83fe6c13f943cd1a8e16f4920c44c4f0d95005e61aab64d1bfe9e1b85d +size 150927 diff --git a/marked/Rel-16/23_series/23018/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23018/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a4490defabcde26b2bb3e1055d19b8ac84232a4 --- /dev/null +++ b/marked/Rel-16/23_series/23018/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1aa8c8a71fe41ee7f48adbc12fa6b52d2a3c815638a65cd9e3c26434d47fd039 +size 83409 diff --git a/marked/Rel-16/23_series/23018/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23018/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22c27ad74e993a815830b579ac2d4735124ea57a --- /dev/null +++ b/marked/Rel-16/23_series/23018/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcee2dcb61b73b77124c4ad9a8c68848fc21cc9b6f377cf29836cf6177cb9a7f +size 164753 diff --git a/marked/Rel-16/23_series/23018/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/23_series/23018/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76b3c291e225cb011d368dbaac083dfdc98bf357 --- /dev/null +++ b/marked/Rel-16/23_series/23018/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5182f8b247b0297c02953763e15a6a0597d8389dc324fd4ea98c99fec9eee2ef +size 100573 diff --git a/marked/Rel-16/23_series/23018/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23018/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48fd22364b8e76004f9c53f3bca30ac2323c57c5 --- /dev/null +++ b/marked/Rel-16/23_series/23018/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6330088cf1f3db985b1324a22f73d4b7eba2014bf9c6646877e1060cc85bec44 +size 90216 diff --git a/marked/Rel-16/23_series/23018/884c44b6cb9fbe15347e0562a6085df2_img.jpg b/marked/Rel-16/23_series/23018/884c44b6cb9fbe15347e0562a6085df2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d364ae40f6a00b3489110746355275cc1b861d3d --- /dev/null +++ b/marked/Rel-16/23_series/23018/884c44b6cb9fbe15347e0562a6085df2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7978078a41896c9201bce5a854a22cd0cd8e76492d02c21f1b5d79974b89d821 +size 59720 diff --git a/marked/Rel-16/23_series/23018/88b0f3f4393228e9ea4d6542aef7c399_img.jpg b/marked/Rel-16/23_series/23018/88b0f3f4393228e9ea4d6542aef7c399_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d320f43d827b55b7fcec4c09e190e9bf4f48e6c2 --- /dev/null +++ b/marked/Rel-16/23_series/23018/88b0f3f4393228e9ea4d6542aef7c399_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6526a35c8420db7f96629289c3fd19a7ada226dda1fa46fcd3d515fa1ee9039a +size 144861 diff --git a/marked/Rel-16/23_series/23018/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/23_series/23018/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..347bd7f583adace44e0cec8fc93395575ea2d96a --- /dev/null +++ b/marked/Rel-16/23_series/23018/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f77a261a1f2e040c07fc088d790beedec0e031d0bdff936fc6bab0382aca0427 +size 65661 diff --git a/marked/Rel-16/23_series/23018/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/23_series/23018/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f798997fc51262c4f262f072300adcb8bede17c9 --- /dev/null +++ b/marked/Rel-16/23_series/23018/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc07930bb8c887daaee96e44643561b712ebb4fa067c5b749eb4a6671a0bfc48 +size 104791 diff --git a/marked/Rel-16/23_series/23018/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23018/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae4feb01b45739002bf1fb1794c89556ced8a2c0 --- /dev/null +++ b/marked/Rel-16/23_series/23018/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5662c532e3c29c420f7546bd3ba938f9e03f4d804ef1f632e97928cd3f1b7550 +size 130652 diff --git a/marked/Rel-16/23_series/23018/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg b/marked/Rel-16/23_series/23018/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b81e564b6921e476550ecc0b9d44204532d380e --- /dev/null +++ b/marked/Rel-16/23_series/23018/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23c5be6c742b589364bfb0e45b0947895b63d43292df821adc8691de49fb0809 +size 146560 diff --git a/marked/Rel-16/23_series/23018/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23018/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..809d6772cc69536c85fc012cf84e68d071122042 --- /dev/null +++ b/marked/Rel-16/23_series/23018/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc4473158ad6bc3bac7d2bee7b5800825e3a8e3c23376bcb2283f754ca0cd432 +size 74610 diff --git a/marked/Rel-16/23_series/23018/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/23_series/23018/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03632256d000b397d7a1c284e387ca04a0cf2a75 --- /dev/null +++ b/marked/Rel-16/23_series/23018/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70a59c14fa99d92f50804819f52733cec00b2419d64367a576a525853b419e7a +size 111370 diff --git a/marked/Rel-16/23_series/23018/92724c769da9d46b730fde1a6dccb023_img.jpg b/marked/Rel-16/23_series/23018/92724c769da9d46b730fde1a6dccb023_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc5d2ac59b93dfa88e7e9e9a6606925706a4504b --- /dev/null +++ b/marked/Rel-16/23_series/23018/92724c769da9d46b730fde1a6dccb023_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ebe1e3862fcb40f59cb0e3e520ddfad96bd3b06cb13b84a9ac53e58bfbc758c +size 82936 diff --git a/marked/Rel-16/23_series/23018/93bd00a00fa28558486f0664550699b1_img.jpg b/marked/Rel-16/23_series/23018/93bd00a00fa28558486f0664550699b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1f7528624920eb584a2fd51a891027ace709e4eb --- /dev/null +++ b/marked/Rel-16/23_series/23018/93bd00a00fa28558486f0664550699b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29e2f431d7d9a94c50b04b3917a87ea9b9d28ec6c40f8d7929f9cb4f44f45589 +size 103418 diff --git a/marked/Rel-16/23_series/23018/9958beca8f65818eb0ff893647af94de_img.jpg b/marked/Rel-16/23_series/23018/9958beca8f65818eb0ff893647af94de_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83ab4d15a04b858250e055264af267aadcb51718 --- /dev/null +++ b/marked/Rel-16/23_series/23018/9958beca8f65818eb0ff893647af94de_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:796a15d4dafca014f50e974b11d88867db8f95499ea086785993bcdf0d619835 +size 83307 diff --git a/marked/Rel-16/23_series/23018/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/23_series/23018/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d485f19123b1818c1bf7d8c25d0e99205b0d08b3 --- /dev/null +++ b/marked/Rel-16/23_series/23018/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b07d7c58245e38ff2b46c67191a03665a58d247040b9e85a1873a94b2aeef805 +size 93423 diff --git a/marked/Rel-16/23_series/23018/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/23_series/23018/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8075473e230d9f67d85dd16f5ef96abecfb80a9d --- /dev/null +++ b/marked/Rel-16/23_series/23018/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d76e420532849f3dbbe3957658fc501abe0ff948aa4be66a840b3b58e7450d95 +size 90847 diff --git a/marked/Rel-16/23_series/23018/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/marked/Rel-16/23_series/23018/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62466730039f23a29278ae31b040d5106ce7e2d7 --- /dev/null +++ b/marked/Rel-16/23_series/23018/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d54c002b87216e555e356028559694d925ccfa62cd562545db89f290311f1243 +size 98290 diff --git a/marked/Rel-16/23_series/23018/9ba75f891de20483c291538e38701d96_img.jpg b/marked/Rel-16/23_series/23018/9ba75f891de20483c291538e38701d96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78353877c02e6e0eb9071d112cac9171894f3c0a --- /dev/null +++ b/marked/Rel-16/23_series/23018/9ba75f891de20483c291538e38701d96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b53eb24498f391871d8eec72d0f1f8ccba246e081493e2913df05d93f28fc932 +size 88892 diff --git a/marked/Rel-16/23_series/23018/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-16/23_series/23018/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ed92f4430cce6ebec980dbbdeded8f3963e331c6 --- /dev/null +++ b/marked/Rel-16/23_series/23018/9c45844d796e85ae05505870a54e4eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a795e69fe139341ab0127261b22e30bde5863926a53efffa5be845021262508 +size 70519 diff --git a/marked/Rel-16/23_series/23018/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/marked/Rel-16/23_series/23018/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6570e9820c136004be9b76eb2fd3cc3d48898cd --- /dev/null +++ b/marked/Rel-16/23_series/23018/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bd1c603dedfec0d2b36ab7b9e8d6f6af493d8408df4491c798e1447a3ac0414 +size 105501 diff --git a/marked/Rel-16/23_series/23018/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/marked/Rel-16/23_series/23018/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..be99ff77f1a15f518d15f932106de84f0f7bf08a --- /dev/null +++ b/marked/Rel-16/23_series/23018/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8aaa404c8315cdafda9c54f2ad0720b177182492faacf363c317ccaf1dcf249f +size 68089 diff --git a/marked/Rel-16/23_series/23018/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/23_series/23018/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a34e9cae4c1e931d5f15a17b32961f3af38710e --- /dev/null +++ b/marked/Rel-16/23_series/23018/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4c507690f53c70d95088ea16e6c378e41d71fb9d31038add59edcb447d1b8dc +size 131742 diff --git a/marked/Rel-16/23_series/23018/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23018/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69bfdea67f96d25b17b50f2a44248de630def689 --- /dev/null +++ b/marked/Rel-16/23_series/23018/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bd243f967663aa8287770d4cbb60ddc711262cf5e0e2fcdb7deaaf5b1faf745 +size 74121 diff --git a/marked/Rel-16/23_series/23018/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-16/23_series/23018/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b5828e94b88b3c2011ed94b1e4f8ff449164e52 --- /dev/null +++ b/marked/Rel-16/23_series/23018/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c595e4393669068f50668ac1e639b1047073b42d0ecd4e42d5accc6c9b4b69f +size 79499 diff --git a/marked/Rel-16/23_series/23018/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23018/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d9593e3628b3cf8a612bf61ca3fe3644f902075 --- /dev/null +++ b/marked/Rel-16/23_series/23018/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d65c9ab15c378047ef0c84484710a0a46156c615f6c98a27b2d87d76edc7265a +size 146325 diff --git a/marked/Rel-16/23_series/23018/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23018/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8907280a3519125bf0d2b756d4c70cade6e0746 --- /dev/null +++ b/marked/Rel-16/23_series/23018/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4fed4bd6fc2218c8f066444e4404c4751c6b5560da9633a9033fb983830f6259 +size 90908 diff --git a/marked/Rel-16/23_series/23018/a5404b7275b06497eecf9b5883604753_img.jpg b/marked/Rel-16/23_series/23018/a5404b7275b06497eecf9b5883604753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44c6b9d56f33ac79ff0155c1d30054878f18e319 --- /dev/null +++ b/marked/Rel-16/23_series/23018/a5404b7275b06497eecf9b5883604753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ecd395379ed1367f48dd0e28df7d8bed2376dc11f071c7dcb9b151a59bf7b51 +size 73072 diff --git a/marked/Rel-16/23_series/23018/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Rel-16/23_series/23018/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd0ba8d35606a1fe1fc97da241819afd263d6ba2 --- /dev/null +++ b/marked/Rel-16/23_series/23018/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5bee80274e7fbf43ca775a6772283d4f1c941a1970a2c54c761d5ed2bf687ff +size 68593 diff --git a/marked/Rel-16/23_series/23018/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/marked/Rel-16/23_series/23018/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4be2f4657db0f4ad4c25308174bfe26ca9701479 --- /dev/null +++ b/marked/Rel-16/23_series/23018/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1754abf68cbc359815eda9d7b4541908d94774e6c4ccd155130919200fe961f9 +size 97793 diff --git a/marked/Rel-16/23_series/23018/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-16/23_series/23018/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a545467e4af154a693d9c8143a860d3f05a7bc45 --- /dev/null +++ b/marked/Rel-16/23_series/23018/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a11b706ff7c071a0ea55270c46dae3d656c7d4ca352677e180118a3aece5b73e +size 92952 diff --git a/marked/Rel-16/23_series/23018/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23018/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4786cfa1fede021cb24e7efa4fb0702f09546ebc --- /dev/null +++ b/marked/Rel-16/23_series/23018/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bc0afc887de67529d0932ab353854710fc2c1d1d217a9c33e9aa99e679356a3 +size 153993 diff --git a/marked/Rel-16/23_series/23018/b02ba0b73e95416eb547976f6145b169_img.jpg b/marked/Rel-16/23_series/23018/b02ba0b73e95416eb547976f6145b169_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7727f166491f60f420d9cf3d46f435c2edfcdf00 --- /dev/null +++ b/marked/Rel-16/23_series/23018/b02ba0b73e95416eb547976f6145b169_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:331a6d81b53332641753a1a268b2fec7642341d343af982deaa24ab68a6c9f0d +size 90393 diff --git a/marked/Rel-16/23_series/23018/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/23_series/23018/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf653e1de7b7aeff45a15e89760d55b1911403e2 --- /dev/null +++ b/marked/Rel-16/23_series/23018/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0e5809ba2cd81e4309331ae959ddc9c1e4c3d96ef67692762a90c15f902132f +size 139714 diff --git a/marked/Rel-16/23_series/23018/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23018/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f8a6be946263896172c1fe1c2fa0130f8f86969 --- /dev/null +++ b/marked/Rel-16/23_series/23018/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20eaf7853d7435550c3ed1473d372d1d61da65009ca14ffb708ba8f6dcae94e5 +size 107408 diff --git a/marked/Rel-16/23_series/23018/b50f38be091844d58b11e3d47bc71e73_img.jpg b/marked/Rel-16/23_series/23018/b50f38be091844d58b11e3d47bc71e73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc15fa807da906bd8782429a92a55b52c1346c46 --- /dev/null +++ b/marked/Rel-16/23_series/23018/b50f38be091844d58b11e3d47bc71e73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d1a3453d59ba625d0db0a3c3a72e99ca05f3bad10de13fc85ed5af1df2d8f382 +size 102094 diff --git a/marked/Rel-16/23_series/23018/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23018/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..702186376e4886996fb5db36b65851b2aa92f8aa --- /dev/null +++ b/marked/Rel-16/23_series/23018/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4b04415e19fcc40fd24e594f9dc9786590f0b91e2589cb56329fc801dce1c26 +size 138539 diff --git a/marked/Rel-16/23_series/23018/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/marked/Rel-16/23_series/23018/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6a3e1df0986f71a4afb17846e36caa6a3522c26 --- /dev/null +++ b/marked/Rel-16/23_series/23018/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4bed55f5429b5ac1df85093640360145019cfbe9df52b24c578558c0f2f1c67a +size 74826 diff --git a/marked/Rel-16/23_series/23018/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/23_series/23018/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45a73202271ab38387ecb7f04fe9e8497d018d75 --- /dev/null +++ b/marked/Rel-16/23_series/23018/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c40b3df17ca0d90b60e0eaeb7c7a58aab49c7c6f23afd7f8c2da2a4b08d20be +size 88690 diff --git a/marked/Rel-16/23_series/23018/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-16/23_series/23018/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4eb45fecf46ee6fccce58d033d6201c08bda41cf --- /dev/null +++ b/marked/Rel-16/23_series/23018/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5cc92702117c32dd6bb14c10f5a985fac982a90d1af7382faa900539d46386d +size 121259 diff --git a/marked/Rel-16/23_series/23018/c0ca823603794512478906b302176bca_img.jpg b/marked/Rel-16/23_series/23018/c0ca823603794512478906b302176bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dce6aa53433edb71a8dc6d33b2b955fb0cd949ea --- /dev/null +++ b/marked/Rel-16/23_series/23018/c0ca823603794512478906b302176bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c2ce2ce254335f2437256034c88744efa296bb1cf9f82ab9d6574bfe6e6aeaa1 +size 109144 diff --git a/marked/Rel-16/23_series/23018/c21bad844b5cb6026c067a1f43ce67c3_img.jpg b/marked/Rel-16/23_series/23018/c21bad844b5cb6026c067a1f43ce67c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fa541fa0a0e36ab510a32a0b05a87476e7a0e49 --- /dev/null +++ b/marked/Rel-16/23_series/23018/c21bad844b5cb6026c067a1f43ce67c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e6ab9f60282c7e34128c4a0e5e7963ca9aacfe878d72c71d33f29d9227e5075 +size 117237 diff --git a/marked/Rel-16/23_series/23018/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23018/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e43de82454104b24e0f748e9033fb3023713d78e --- /dev/null +++ b/marked/Rel-16/23_series/23018/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b995922091b0be0ed05be517c656c2ce31f3605ac68d1fd2c7a36c60ce102e8 +size 76690 diff --git a/marked/Rel-16/23_series/23018/cc7baa8e5118f4b42c01166637c738ea_img.jpg b/marked/Rel-16/23_series/23018/cc7baa8e5118f4b42c01166637c738ea_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5bf807fd07e5906266e5bbe5c18743eb6b88bc07 --- /dev/null +++ b/marked/Rel-16/23_series/23018/cc7baa8e5118f4b42c01166637c738ea_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b42e7baf0c93523cc66f1b9342120b5058611c139b13d6a347f7aec3a8b7be2 +size 148535 diff --git a/marked/Rel-16/23_series/23018/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/marked/Rel-16/23_series/23018/d04c50badc78d5ba47bf4e352af4a754_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..270ec8054ae9114bce005c1bb252632c9c2735d6 --- /dev/null +++ b/marked/Rel-16/23_series/23018/d04c50badc78d5ba47bf4e352af4a754_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:653bc3b71e72000afdf6bba113f9daee5f870930844a6db28a7ba1ad66c8129f +size 124077 diff --git a/marked/Rel-16/23_series/23018/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23018/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b0b4333e1bf4f54613c6d78f83bc1c5871fc24c --- /dev/null +++ b/marked/Rel-16/23_series/23018/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c3f5df60ceef3dc99a6db4eacd4aa83eaf3e7d8ed43fccb1e53e0014ebca0bf8 +size 216871 diff --git a/marked/Rel-16/23_series/23018/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg b/marked/Rel-16/23_series/23018/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..732110a21a0a8be79b8972f8ee7b9ba3b287f6de --- /dev/null +++ b/marked/Rel-16/23_series/23018/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b1ca521af4f824340551c433319bf47b20ae7634ec2b020b03da29ffcdb47d72 +size 141043 diff --git a/marked/Rel-16/23_series/23018/d2417b04116c354deccb25d98a84a0fb_img.jpg b/marked/Rel-16/23_series/23018/d2417b04116c354deccb25d98a84a0fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..067ac16f684dcdf7dc3a9640b469573ae4bf3c77 --- /dev/null +++ b/marked/Rel-16/23_series/23018/d2417b04116c354deccb25d98a84a0fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d10392a9d63d1e7a130289fdd38f142f792e0117a3643f58a602e167a3d4563 +size 108027 diff --git a/marked/Rel-16/23_series/23018/d3ca266c298aeb34b019960c6c36f187_img.jpg b/marked/Rel-16/23_series/23018/d3ca266c298aeb34b019960c6c36f187_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c66b7b0358d90a927a9b8a0eefcb3ec952b35cd --- /dev/null +++ b/marked/Rel-16/23_series/23018/d3ca266c298aeb34b019960c6c36f187_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af945c643ef93de044cea0c382b41902139e1f632fc6e4fc85a6f36c7a347c4c +size 195802 diff --git a/marked/Rel-16/23_series/23018/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/marked/Rel-16/23_series/23018/da85343976fdbb19f866d9ddbdad0eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bac204c9c3d1ba21bf4c2d9340850b4115df5a34 --- /dev/null +++ b/marked/Rel-16/23_series/23018/da85343976fdbb19f866d9ddbdad0eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e89a4784e9550f4ea513fbc90a599a5eb18de5db18cc6c857078f6868f86a305 +size 76474 diff --git a/marked/Rel-16/23_series/23018/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/23_series/23018/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f287f3e43e3ebbe315ee44999b3ec37e72176e4e --- /dev/null +++ b/marked/Rel-16/23_series/23018/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba16a02b7778141795350f34eb4b9096e0bc3ca109dad3b32542fe7e1573c4d6 +size 123517 diff --git a/marked/Rel-16/23_series/23018/db7a693cf26f527ac6c0d4d41da20858_img.jpg b/marked/Rel-16/23_series/23018/db7a693cf26f527ac6c0d4d41da20858_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3070bbdc196d1042414fd77b507088f20773e005 --- /dev/null +++ b/marked/Rel-16/23_series/23018/db7a693cf26f527ac6c0d4d41da20858_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06fea4a5d6952cb391ebb77d19131324f397f3a83ba93bfdafdc863918d14864 +size 55076 diff --git a/marked/Rel-16/23_series/23018/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/Rel-16/23_series/23018/dbd4bab54b57e8d1abf80e3de6471130_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ef3a7bf40fd3c42a6e60604973b1cce75259247 --- /dev/null +++ b/marked/Rel-16/23_series/23018/dbd4bab54b57e8d1abf80e3de6471130_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:62c6fe42ecd051475e5afc56b511b4e1473a4e102b4e4053c988ef27d03e7006 +size 117578 diff --git a/marked/Rel-16/23_series/23018/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-16/23_series/23018/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7fcaebf1bb36705599f8e572d42799e2380e119 --- /dev/null +++ b/marked/Rel-16/23_series/23018/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1086487b919c13d7e2a91f275dfed414a11c0a52c289837e11150bdd67dace79 +size 51719 diff --git a/marked/Rel-16/23_series/23018/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/marked/Rel-16/23_series/23018/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90ffeca6a21f20b8a6d151c0452126bc2cc1fa20 --- /dev/null +++ b/marked/Rel-16/23_series/23018/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb34cc5a45ff4098648930fa271095aef6d892cbc4b11f6b1a43fcaba6947380 +size 121435 diff --git a/marked/Rel-16/23_series/23018/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/marked/Rel-16/23_series/23018/e16bfa31d748f4d99ec4ae3d16656926_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b5e1e8d4259f8756ea761fbd97ba7dd5c5890c6 --- /dev/null +++ b/marked/Rel-16/23_series/23018/e16bfa31d748f4d99ec4ae3d16656926_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f170eb8103bed39fdc1d45b8d6a13407aee9de626310e7a3e0184ab1bcde1225 +size 138159 diff --git a/marked/Rel-16/23_series/23018/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23018/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ddd42b08d559e596c09acb875b6c88395152c1ae --- /dev/null +++ b/marked/Rel-16/23_series/23018/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34866148dbfb0837c0b071db7477f1b53021e7edb5da422e4a6e617a905971d2 +size 70160 diff --git a/marked/Rel-16/23_series/23018/e18841eb4a995df8354a793459e12fd0_img.jpg b/marked/Rel-16/23_series/23018/e18841eb4a995df8354a793459e12fd0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68880d4276646ca6a57a4bfd9354b0f1e6ffa808 --- /dev/null +++ b/marked/Rel-16/23_series/23018/e18841eb4a995df8354a793459e12fd0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c87b48254f7d45c0f22249ae2719ffc3eabbf046f78578cab05ca50c6cec53f3 +size 64893 diff --git a/marked/Rel-16/23_series/23018/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-16/23_series/23018/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..63c5655bf1d220e93bb2a29e687dbe595b392b62 --- /dev/null +++ b/marked/Rel-16/23_series/23018/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7494e4f9b59cb1c119a914df090f494ecb712f73659dedd984d118e6d650c3ef +size 115749 diff --git a/marked/Rel-16/23_series/23018/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23018/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8662698e8a60dc78094bfd51316ecfd5a3d7b94a --- /dev/null +++ b/marked/Rel-16/23_series/23018/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:741ccc93d04609c797f39a9900b5c68eb8bf694cfa92277012d4e43899bbf050 +size 106019 diff --git a/marked/Rel-16/23_series/23018/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-16/23_series/23018/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37c3a3e8cd382695d1587e660b0c559afd2c499f --- /dev/null +++ b/marked/Rel-16/23_series/23018/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:65ce24816358ca77716aab7f1b6ad2fbba915f6e8ddc90b70fd2189e7f3a5b31 +size 116315 diff --git a/marked/Rel-16/23_series/23018/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/marked/Rel-16/23_series/23018/eabcb2f8b9acedb194571d5bc734b463_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dbf3281e5663171ca773fe6b795edda968ddb78a --- /dev/null +++ b/marked/Rel-16/23_series/23018/eabcb2f8b9acedb194571d5bc734b463_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:94296e131a91d6ed5b3a4bf9b9e57b85d072f97c9ffb1118ca35cd5eb81b9bb0 +size 156479 diff --git a/marked/Rel-16/23_series/23018/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23018/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3de3f430a974ddbd1e04450ee628968ec9fc407 --- /dev/null +++ b/marked/Rel-16/23_series/23018/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6059fab55fe6c72faaa252d276b11560feaa12872b0ea135361b4e2ac161b2d9 +size 69827 diff --git a/marked/Rel-16/23_series/23018/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Rel-16/23_series/23018/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8b94f9ee4aa6091814f09a7881b4f379388fea6 --- /dev/null +++ b/marked/Rel-16/23_series/23018/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1da18eb29d809aadf657a130c1ed5e9ef853dc8ce3a1cf48e806b5f801ea0438 +size 116662 diff --git a/marked/Rel-16/23_series/23018/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg b/marked/Rel-16/23_series/23018/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3956a39f2c616d4240e2f7b1eb0702901203856c --- /dev/null +++ b/marked/Rel-16/23_series/23018/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fdff5fae2036e9d92121d1a44ade59e1dae4b4acb5f8cb67e21bef523a0f5c4b +size 90625 diff --git a/marked/Rel-16/23_series/23018/f5deee2f3301ee351c4008283ffafbb3_img.jpg b/marked/Rel-16/23_series/23018/f5deee2f3301ee351c4008283ffafbb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47f15a53696d1fb62eb17d9bfabb57e85e01e800 --- /dev/null +++ b/marked/Rel-16/23_series/23018/f5deee2f3301ee351c4008283ffafbb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28ac8be0b421614e060ed9cd571d069891b97b4e2e74b1339771562544e4e259 +size 127256 diff --git a/marked/Rel-16/23_series/23018/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/Rel-16/23_series/23018/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c29d619c36d8fe2980383b99620ee748cb3eed8a --- /dev/null +++ b/marked/Rel-16/23_series/23018/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:933a66589982b7eac1713f19681b8ff6d3bf49ad6a5fc7cdf8b00a5c48dc2442 +size 153411 diff --git a/marked/Rel-16/23_series/23018/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg b/marked/Rel-16/23_series/23018/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51ce365ce9c91d86f20595b921becdd74bf9f814 --- /dev/null +++ b/marked/Rel-16/23_series/23018/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67a28ccfb024f5fd38ccff57bcf1782bb3e80b774559143d7ec2e34f217fad20 +size 89136 diff --git a/marked/Rel-16/23_series/23018/fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg b/marked/Rel-16/23_series/23018/fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..350f85165b0b1596475be8e8bf39e0a361c89e3e --- /dev/null +++ b/marked/Rel-16/23_series/23018/fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89b7a7034571eccc60f8c8e19f1f060b0dff5491d407715755add645be46e247 +size 80375 diff --git a/marked/Rel-16/23_series/23018/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-16/23_series/23018/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95661e671a02fafd8570c57cde9d58a9d919a96b --- /dev/null +++ b/marked/Rel-16/23_series/23018/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98daf0d3468f76b1f350d9299e030fcaa95d02135485f906b96aa2afd96a4b85 +size 116877 diff --git a/marked/Rel-16/23_series/23018/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-16/23_series/23018/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..659eb08098c4d99670fc81609119fbd99805626e --- /dev/null +++ b/marked/Rel-16/23_series/23018/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4466aa079878e36a273e6998d9f42e4595d49a8f268cd9a1bfdebefa6291458b +size 92953 diff --git a/marked/Rel-16/23_series/23018/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/23_series/23018/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4508322ed092f7d51674101164468bb2502fe701 --- /dev/null +++ b/marked/Rel-16/23_series/23018/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5cdd16f41360279523cc92230bdcc936c1a15c4ca6d1c430e7549526208f442 +size 108463 diff --git a/marked/Rel-16/23_series/23018/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23018/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cde001831e5e54b6986b558fffee5eaa8750903c --- /dev/null +++ b/marked/Rel-16/23_series/23018/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc4187ab0013750e743c34a192764dc79c4d5a33f22500f3e334f9ed300badcb +size 80915 diff --git a/marked/Rel-16/23_series/23018/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-16/23_series/23018/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8ebbad02a8bd1cb3c65e32edcd83298b573966a --- /dev/null +++ b/marked/Rel-16/23_series/23018/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84ef3c80d8bddf0e7300363f15ad64ef3a685e61b66e75e4d76e89eb4ba154f5 +size 156110 diff --git a/marked/Rel-16/23_series/23018/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/marked/Rel-16/23_series/23018/ffe0fef452a0ae9a20253c319c54e13c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..395bac8ee61423bd16e9924a26ec1fee02458641 --- /dev/null +++ b/marked/Rel-16/23_series/23018/ffe0fef452a0ae9a20253c319c54e13c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4dc1f638b8afe9c64f89f7a410f9f1e23c7d36b2857a1d1157929b3e2a4fceee +size 118924 diff --git a/marked/Rel-16/23_series/23018/raw.md b/marked/Rel-16/23_series/23018/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2875937c772c7cbd3c57ed945a9f9603b379de31 --- /dev/null +++ b/marked/Rel-16/23_series/23018/raw.md @@ -0,0 +1,10378 @@ +# Contents + +| | | +|----------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 7 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 3 Definitions and abbreviations ..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Abbreviations ..... | 10 | +| 4 Architecture..... | 11 | +| 4.1 Architecture for an MO call ..... | 11 | +| 4.2 Architecture for an MT call..... | 12 | +| 4.3 Architecture for a TO call ..... | 13 | +| 5 Information flows..... | 14 | +| 5.1 Information flow for an MO call..... | 14 | +| 5.2 Information flow for retrieval of routeing information for an MT call..... | 17 | +| 5.2.1 Mobile Terminating Roaming Retry Call after successful Retrieval of Routeing Information..... | 18 | +| 5.2.2 Mobile Terminating Roaming Retry Call during Retrieval of Routeing Information ..... | 20 | +| 5.2.3 Mobile Terminating Roaming Forwarding Call after successful Retrieval of Routeing Information..... | 23 | +| 5.2.4 Mobile Terminating Roaming Forwarding Call during Retrieval of Routeing Information..... | 29 | +| 5.3 Information flow for an MT call ..... | 31 | +| 6 Principles for interactions with supplementary services..... | 33 | +| 6.1 Call Deflection service (3GPP TS 23.072) ..... | 34 | +| 6.2 Line identification services (3GPP TS 23.081)..... | 34 | +| 6.2.1 Calling Line Identification Presentation (CLIP) ..... | 34 | +| 6.2.2 Calling Line Identification Restriction (CLIR) ..... | 34 | +| 6.2.3 Connected Line Identification Presentation (COLP)..... | 34 | +| 6.2.4 Connected Line Identification Restriction (COLR) ..... | 34 | +| 6.3 Call forwarding services (3GPP TS 23.082)..... | 34 | +| 6.3.1 Call Forwarding Unconditional (CFU) ..... | 34 | +| 6.3.2 Call Forwarding on mobile subscriber Busy (CFB)..... | 34 | +| 6.3.3 Call Forwarding on No Reply (CFNRy) ..... | 34 | +| 6.3.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc)..... | 34 | +| 6.4 Call wait (3GPP TS 23.083)..... | 35 | +| 6.5 Call hold (3GPP TS 23.083) ..... | 35 | +| 6.6 Multiparty (3GPP TS 23.084)..... | 35 | +| 6.7 Closed user group (3GPP TS 23.085) ..... | 35 | +| 6.8 Advice of charge (3GPP TS 23.086)..... | 35 | +| 6.9 User-to-user signalling (3GPP TS 23.087) ..... | 35 | +| 6.10 Call barring (3GPP TS 23.088)..... | 35 | +| 6.10.1 Barring of outgoing calls ..... | 35 | +| 6.10.2 Barring of incoming calls ..... | 35 | +| 6.11 Explicit Call Transfer (3GPP TS 23.091) ..... | 36 | +| 6.12 Completion of Calls to Busy Subscriber (3GPP TS 23.093) ..... | 36 | +| 6.13 Multicall (3GPP TS 23.135)..... | 36 | +| 7 Functional requirements of network entities..... | 36 | +| 7.1 MO call..... | 37 | +| 7.1.1 Functional requirements of serving MSC..... | 37 | +| 7.1.1.1 Process_OCH_MSC ..... | 37 | +| 7.1.1.2 Procedure Process_Access_Request_MSC ..... | 37 | +| 7.1.1.3 Procedure OG_Call_Setup_MSC ..... | 37 | +| 7.1.1.4 Procedure Obtain_IMSI_MSC ..... | 39 | +| 7.1.1.5 Procedure Authenticate_MSC ..... | 39 | +| 7.1.1.6 Procedure Obtain_IMEI_MSC ..... | 39 | +| 7.1.1.7 Procedure Check_IMEI_MSC ..... | 39 | +| 7.1.1.8 Procedure Establish_Originating_TCH_If_Required..... | 40 | +| 7.1.1.9 Procedure Set_CLI_Presentation_Indicator_MSC ..... | 40 | + +| | | | +|----------|--------------------------------------------------------|-----| +| 7.1.1.10 | Procedure Send_Alerting_If_Required..... | 40 | +| 7.1.1.11 | Procedure Set_COLP_Info_MSC..... | 40 | +| 7.1.1.12 | Procedure Send_Access_Connect_If_Required ..... | 40 | +| 7.1.1.13 | Procedure Handle_AoC_MO_MSC ..... | 40 | +| 7.1.1.14 | Procedure TCH_Check..... | 41 | +| 7.1.2 | Functional requirements of VLR..... | 67 | +| 7.1.2.1 | Process OCH_VLR..... | 67 | +| 7.1.2.2 | Procedure Process_Access_Request_VLR..... | 67 | +| 7.1.2.3 | Procedure OG_Call_Subscription_Check_VLR ..... | 67 | +| 7.1.2.4 | Procedure Obtain_Identity_VLR..... | 67 | +| 7.1.2.5 | Procedure Obtain_IMSI_VLR..... | 67 | +| 7.1.2.6 | Procedure Authenticate_VLR..... | 67 | +| 7.1.2.7 | Procedure Obtain_Authentication_Sets_VLR..... | 68 | +| 7.1.2.8 | Procedure Start_Tracing_VLR ..... | 68 | +| 7.1.2.9 | Procedure Check_IMEI_VLR ..... | 68 | +| 7.1.2.10 | Procedure Obtain_IMEI_VLR..... | 68 | +| 7.1.2.11 | Process Fetch_Authentication_Sets_VLR..... | 68 | +| 7.1.2.12 | Procedure Check_BAOC..... | 68 | +| 7.1.2.13 | Procedure OG_CUG_Check..... | 68 | +| 7.1.2.14 | Procedure Get_LI_Subscription_Info_MO_VLR ..... | 68 | +| 7.1.2.15 | Procedure Get_AoC_Subscription_Info_VLR..... | 68 | +| 7.1.2.16 | Procedure Check_OG_Barring..... | 68 | +| 7.1.2.17 | Process Update_Location_VLR ..... | 68 | +| 7.2 | Retrieval of routeing information for MT call ..... | 95 | +| 7.2.1 | Functional requirements of GMSC ..... | 95 | +| 7.2.1.1 | Process MT_GMSC..... | 95 | +| 7.2.1.2 | Procedure Obtain_Routeing_Address..... | 97 | +| 7.2.1.3 | Procedure Send_ACM_If_Required..... | 98 | +| 7.2.1.4 | Procedure Send_Answer_If_Required ..... | 99 | +| 7.2.1.5 | Procedure Send_Network_Connect_If_Required..... | 99 | +| 7.2.1.6 | Procedure Handle_COLP_Forwarding_Interaction_MSC ..... | 99 | +| 7.2.1.7 | Procedure Activate_CF_Process..... | 99 | +| 7.2.1.8 | Process MT_CF_MSC..... | 99 | +| 7.2.1.9 | Macro CUG_Support_Check_GMSC ..... | 101 | +| 7.2.2 | Functional requirements of HLR..... | 127 | +| 7.2.2.1 | Process SRI_HLR..... | 127 | +| 7.2.2.2 | Procedure Check_Parameters ..... | 129 | +| 7.2.2.3 | Procedure Subscription_Check_HLR..... | 129 | +| 7.2.2.4 | Procedure First_Forwarding_HLR ..... | 130 | +| 7.2.2.5 | Procedure PRN_Error_HLR..... | 130 | +| 7.2.2.6 | Procedure Forward_CUG_Check ..... | 130 | +| 7.2.2.7 | Void ..... | 130 | +| 7.2.2.8 | Procedure Check_IC_Barring..... | 130 | +| 7.2.2.9 | Procedure IC_CUG_Check..... | 130 | +| 7.2.2.10 | Procedure Handle_CFU..... | 130 | +| 7.2.2.11 | Procedure Handle_CFNRc ..... | 131 | +| 7.2.2.12 | Procedure Domain_Selection_HLR ..... | 131 | +| 7.2.3 | Functional requirements of VLR..... | 148 | +| 7.2.3.1 | Process PRN_VLR ..... | 148 | +| 7.2.3.2 | Process Restore_Subscriber_Data_VLR ..... | 149 | +| 7.2.3.3 | Process PSI_VLR ..... | 149 | +| 7.2.3.4 | Procedure Retrieve_Location_Info_VLR..... | 150 | +| 7.2.3.5 | Procedure Active_Info_Retrieval_VLR ..... | 150 | +| 7.2.4 | Functional requirements of MSC ..... | 167 | +| 7.2.4.1 | Process Prepage_MSC..... | 167 | +| 7.2.4.2 | Procedure Prepaging_Page_MS_MSC ..... | 167 | +| 7.2.4.3 | Prepaging_Search_For_MS_MSC..... | 167 | +| 7.2.4.4 | Process OSI_MSC ..... | 167 | +| 7.2.4.5 | Process RCL_MSC..... | 167 | +| 7.2.4.6 | Procedure Active_Info_Retrieval_Page_MSC ..... | 167 | +| 7.2.4.7 | Procedure Active_Info_Retrieval_Search_MSC ..... | 167 | +| 7.2.4.8 | Procedure Retrieve_IMEI_If_Required..... | 168 | + +| | | | +|-----------|-------------------------------------------------------|-----| +| 7.3 | MT call..... | 176 | +| 7.3.1 | Functional requirements of serving MSC..... | 176 | +| 7.3.1.1 | Process ICH_MSC..... | 176 | +| 7.3.1.2 | Procedure Page_MS_MSC ..... | 178 | +| 7.3.1.3 | Procedure Search_For_MS_MSC..... | 179 | +| 7.3.1.4 | Procedure Complete_Call_In_MSC ..... | 180 | +| 7.3.1.5 | Void ..... | 181 | +| 7.3.1.6 | Procedure Set_CLIP_Info_MSC ..... | 181 | +| 7.3.1.7 | Void ..... | 182 | +| 7.3.1.8 | Procedure Establish_Terminating_TCH_If_Required ..... | 182 | +| 7.3.1.9 | Procedure Handle_AoC_MT_MSC..... | 182 | +| 7.3.1.10 | Procedure Set_COL_Presentation_Indicator_MSC ..... | 182 | +| 7.3.2 | Functional requirements of VLR..... | 224 | +| 7.3.2.1 | Process ICH_VLR ..... | 224 | +| 7.3.2.2 | Void ..... | 225 | +| 7.3.2.3 | Procedure Search_For_MS_VLR..... | 225 | +| 7.3.2.4 | Procedure Get_CW_Subscription_Info_VLR ..... | 225 | +| 7.3.2.5 | Procedure Get_LI_Subscription_Info_MT_VLR..... | 225 | +| 7.3.2.6 | Procedure Handle_CFB ..... | 226 | +| 7.3.2.7 | Procedure Handle_CFNRy ..... | 226 | +| 7.4 | Subs_FSM ..... | 240 | +| 7.4.1 | Functional requirements of serving MSC..... | 240 | +| 7.4.1.1 | Process Subs_FSM ..... | 240 | +| 7.4.1.1.1 | Macro Check_Ongoing_Calls..... | 241 | +| 7.4.1.1.2 | Macro Update_Non_Speech_Calls_Status ..... | 241 | +| 7.4.1.1.3 | Macro Increment_Call_Counter..... | 241 | +| 7.4.1.1.4 | Macro Decrement_Call_Counter ..... | 241 | +| 7.5 | TO call..... | 263 | +| 7.5.1 | Functional requirements of inter-connecting MSC ..... | 263 | +| 7.5.1.1 | Process TO_MSC ..... | 263 | +| 8 | Contents of messages..... | 271 | +| 8.1 | Messages on the B interface (MSC-VLR) ..... | 272 | +| 8.1.1 | Abort..... | 272 | +| 8.1.2 | Authenticate..... | 272 | +| 8.1.3 | Authenticate ack ..... | 273 | +| 8.1.4 | Authenticate negative response ..... | 273 | +| 8.1.5 | Call arrived ..... | 273 | +| 8.1.6 | Check IMEI ..... | 273 | +| 8.1.7 | Check IMEI ack..... | 273 | +| 8.1.8 | Check IMEI negative response..... | 273 | +| 8.1.9 | Complete Call..... | 274 | +| 8.1.10 | Complete Call ack ..... | 275 | +| 8.1.11 | Complete Call negative response ..... | 275 | +| 8.1.12 | Forward New TMSI ..... | 275 | +| 8.1.13 | Forward New TMSI ack..... | 275 | +| 8.1.14 | Forward New TMSI negative response ..... | 275 | +| 8.1.15 | Obtain Subscriber Info ..... | 275 | +| 8.1.16 | Obtain Subscriber Info ack..... | 275 | +| 8.1.17 | Page MS..... | 276 | +| 8.1.18 | Page MS ack..... | 276 | +| 8.1.19 | Page MS negative response ..... | 276 | +| 8.1.20 | Page MS via SGSN ..... | 277 | +| 8.1.21 | Process Access Request..... | 277 | +| 8.1.22 | Process Access Request ack ..... | 277 | +| 8.1.23 | Process Access Request negative response ..... | 278 | +| 8.1.24 | Process Call Waiting ..... | 278 | +| 8.1.25 | Process Call Waiting ack..... | 279 | +| 8.1.26 | Process Call Waiting negative response..... | 279 | +| 8.1.27 | Provide IMEI ..... | 279 | +| 8.1.28 | Provide IMEI ack ..... | 279 | +| 8.1.29 | Provide IMSI ..... | 279 | + +| | | | +|-------------------------------|-----------------------------------------------------|------------| +| 8.1.30 | Provide IMSI ack..... | 279 | +| 8.1.31 | Radio connection released..... | 279 | +| 8.1.32 | Search For MS..... | 279 | +| 8.1.33 | Search For MS ack ..... | 280 | +| 8.1.34 | Search For MS negative response ..... | 280 | +| 8.1.35 | Search for MS via SGSN..... | 281 | +| 8.1.36 | Send Info For Incoming Call..... | 281 | +| 8.1.37 | Send Info For Incoming Call ack ..... | 282 | +| 8.1.38 | Send Info For Incoming Call negative response ..... | 282 | +| 8.1.39 | Send Info For Outgoing Call ..... | 283 | +| 8.1.40 | Send Info For Outgoing Call negative response..... | 283 | +| 8.1.40A | Send UESBI-Iu to Access Network ..... | 283 | +| 8.1.41 | Start security procedures ..... | 284 | +| 8.1.42 | Trace subscriber activity..... | 284 | +| 8.1.43 | Use existing TMSI..... | 284 | +| 8.1.44 | Release MSRN ..... | 284 | +| 8.2 | Messages on the C interface (MSC-HLR) ..... | 284 | +| 8.2.1 | Send Routeing Info..... | 284 | +| 8.2.2 | Send Routeing Info ack ..... | 286 | +| 8.2.3 | Send Routeing Info negative response ..... | 286 | +| 8.3 | Messages on the D interface (VLR-HLR)..... | 287 | +| 8.3.1 | Provide Roaming Number..... | 287 | +| 8.3.2 | Provide Roaming Number ack ..... | 288 | +| 8.3.3 | Provide Roaming Number negative response ..... | 288 | +| 8.3.4 | Provide Subscriber Info ..... | 289 | +| 8.3.5 | Provide Subscriber Info ack ..... | 289 | +| 8.3.5.1 | Location information ..... | 291 | +| 8.3.6 | Provide Subscriber Info negative response ..... | 291 | +| 8.3.7 | Restore Data ..... | 291 | +| 8.3.8 | Restore Data ack..... | 292 | +| 8.3.9 | Restore Data negative response..... | 292 | +| 8.4 | Messages on the F interface (MSC-EIR) ..... | 292 | +| 8.4.1 | Check IMEI ..... | 292 | +| 8.4.2 | Check IMEI ack..... | 292 | +| 8.4.3 | Check IMEI negative response..... | 292 | +| 8.5 | Messages on the MSC internal interface..... | 293 | +| 8.5.1 | CF cancelled ..... | 293 | +| 8.5.2 | Perform Call Forwarding..... | 293 | +| 8.5.3 | Perform Call Forwarding ack ..... | 293 | +| 8.5.4 | Perform Call Forwarding negative response ..... | 293 | +| 8.6 | Messages on the VLR internal interface ..... | 293 | +| 8.6.1 | Call arrived ..... | 293 | +| 8.6.2 | PAR completed..... | 293 | +| 8.7 | Messages on the Gs interface ..... | 294 | +| 8.7.1 | Page MS..... | 294 | +| 8.7.2 | Send MS information ..... | 294 | +| 8.7.3 | Send MS information ack..... | 294 | +| 8.7.4 | Send MS information negative response..... | 294 | +| 8.8 | Messages on the E interface (GMSC-VMSC) ..... | 295 | +| 8.8.1 | Release Resources ..... | 295 | +| Annex A (informative): | Handling of an IAM at an MSC..... | 296 | +| Annex B (informative): | Change history..... | 298 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document specifies the technical realization of the handling of calls originated by a 3G mobile subscriber and calls directed to a 3G mobile subscriber, up to the point where the call is established 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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 Indicates a TSG approved Release 1999 document under change control; + - 4 Indicate a TSG approved Release 4 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 + +The present document specifies the technical realization of the handling of calls originated by a UMTS or GSM mobile subscriber and calls directed to a UMTS or GSM mobile subscriber, up to the point where the call is established. Normal release of the call after establishment is also specified. Trunk Originated call is also modelled. + +In the present document, the term MS is used to denote a UMTS UE or GSM MS, as appropriate. + +The handling of DTMF signalling and Off-Air Call set-up (OACSU) are not described in the present document. + +The details of the effects of UMTS or GSM supplementary services on the handling of a call are described in the relevant 3GPP TS 23.07x, 3GPP TS 23.08x and 3GPP TS 23.09x series of specifications. + +The specification of the handling of a request from the HLR for subscriber information is not part of basic call handling, but is required for both CAMEL (3GPP TS 23.078 [12]) and optimal routeing (3GPP TS 23.079 [13]). The use of the Provide Subscriber Information message flow is shown in 3GPP TS 23.078 [12] and 3GPP TS 23.079 [13]. + +The logical separation of the MSC and VLR (shown in clauses 4, 5 and 7), and the messages transferred between them (described in clause 8) are the basis of a model used to define the externally visible behaviour of the MSC/VLR, which is a single physical entity. They do not impose any requirement except the definition of the externally visible behaviour. + +If there is any conflict between the present document and the corresponding stage 3 specifications (3GPP TS 24.008 [26], 3GPP TS 25.413 [27], 3GPP TS 48.008 [2] and 3GPP TS 29.002 [29]), the stage 3 specification shall prevail. + +# --- 2 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 43.020: "Security related Network Functions". +- [2] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC - BSS) interface Layer 3 specification". +- [3] 3GPP TS 52.008: "Telecommunication management; GSM subscriber and equipment trace". +- [4] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [5] 3GPP TS 23.003: "Numbering, addressing and identification". +- [6] 3GPP TS 23.012: "Location management procedures". +- [7] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [8] Void +- [9] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [10] 3GPP TS 23.066: "Support of GSM Mobile Number Portability (MNP); Stage 2". +- [11] 3GPP TS 23.072: "Call deflection Supplementary Service; Stage2". +- [12] 3GPP TS 23.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL); Stage 2". + +- [13] 3GPP TS 23.079: "Support of Optimal Routeing (SOR); Technical realization; Stage 2". +- [14] 3GPP TS 23.081: "Line identification Supplementary Services; Stage 2 ". +- [15] 3GPP TS 23.082: "Call Forwarding (CF) Supplementary Services; Stage 2". +- [16] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Service; Stage 2". +- [17] 3GPP TS 23.084: "Multi Party (MPTY) Supplementary Service; Stage 2". +- [18] 3GPP TS 23.085: "Closed User Group (CUG) Supplementary Service; Stage 2". +- [19] 3GPP TS 23.086: "Advice of Charge (AoC) Supplementary Service; Stage 2". +- [20] 3GPP TS 23.087: "User-to-User Signalling (UUS) Supplementary Service; Stage 2". +- [21] 3GPP TS 23.088: "Call Barring (CB) Supplementary Service; Stage 2". +- [22] 3GPP TS 23.091: "Explicit Call Transfer (ECT) supplementary service; Stage 2". +- [23] 3GPP TS 23.093: "Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2". +- [24] 3GPP TS 23.116: "Super-charger technical realization; Stage 2". +- [25] 3GPP TS 23.135: "Multicall supplementary service; Stage 2". +- [25a] 3GPP TS 23.195: "Provision of UE Specific Behaviour Information to Network Entities". +- [26] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [27] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling". +- [28] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". +- [29] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [30] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". +- [31] 3GPP TS 29.010: "Information Element Mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC) Signalling Procedures and the Mobile Application Part (MAP)". +- [32] 3GPP TS 33.102: "3G Security; Security architecture ". +- [33] ITU-T Recommendation Q.761 (1999): " Signalling System No. 7 - ISDN User Part functional description ". +- [34] ITU-T Recommendation Q.762 (1999): "Signalling System No. 7 - ISDN User Part general functions of messages and signals". +- [35] ITU-T Recommendation Q.763 (1999): "Signalling System No. 7 - ISDN User Part formats and codes". +- [36] ITU-T Recommendation Q.764 (1999): " Signalling System No. 7 – ISDN user part signalling procedures". +- [37] ITU-T Recommendation Q.850 (05/1998) including Amendment 1 (07/2001): "Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part". +- [38] 3GPP TS 23.172: "Technical realization of Circuit Switched (CS) multimedia service ; UDI/RDI fallback and service modification; Stage 2". + +- [39] 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) - Stage 2". +- [40] 3GPP TS 23.221: "Technical specification Group Services and System Aspects; Architectural Requirements". +- [41] 3GPP TS 29.118: "Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification". +- [42] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2". +- [43] 3GPP TS 23.007: "Restoration procedures". + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**A subscriber:** the calling mobile subscriber + +**B subscriber:** the mobile subscriber originally called by the A subscriber + +**C subscriber:** the subscriber to whom the B subscriber has requested that calls be forwarded +The C subscriber may be fixed or mobile. + +**Location Information:** information to define the whereabouts of the MS, and the age of the information defining the whereabouts + +**PLMN Bearer Capability:** information transferred over the UMTS or GSM access interface to define the information transfer capabilities to be used between the MS and the network for a circuit-switched connection + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-----------------|---------------------------------------------------------------------------------------------------------------------------| +| A&O | Active & Operative | +| ACM | Address Complete Message | +| ANM | ANswer Message | +| AoC | Advice of Charge | +| BC | Bearer Capability | +| BOIC-exHC&BOIZC | Barring of Outgoing International Calls except those directed to the HPLMN Country & Barring of Outgoing InterZonal Calls | +| BOIZC | Barring of Outgoing InterZonal Calls | +| BOIZC-exHC | Barring of Outgoing InterZonal Calls except those directed to the HPLMN Country | +| CCBS | Completion of Calls to Busy Subscriber | +| CFB | Call Forwarding on Busy | +| CFNRc | Call Forwarding on mobile subscriber Not Reachable | +| CFNRy | Call Forwarding on No Reply | +| CFU | Call Forwarding Unconditional | +| CLIP | Calling Line Identity Presentation | +| CLIR | Calling Line Identity Restriction | +| COLP | COnnected Line identity Presentation | +| COLR | COnnected Line identity Restriction | +| CSG | Closed Subscriber Group | +| CUG | Closed User Group | +| CW | Call Waiting | +| FTN | Forwarded-To Number | +| FTNW | Forwarded-To NetWork | +| GMSCB | Gateway MSC of the B subscriber | +| GPRS | General Packet Radio Service | +| HLC | Higher Layer Compatibility | + +| | | +|----------|--------------------------------------------------------------------------------| +| HLRB | The HLR of the B subscriber | +| HPLMNB | The HPLMN of the B subscriber | +| IAM | Initial Address Message | +| IPLMN | Interrogating PLMN - the PLMN containing GMSCB | +| IWU | Inter Working Unit | +| LLC | Lower Layer Compatibility | +| MO | Mobile Originated | +| MPTY | MultiParTY | +| MT | Mobile Terminated | +| NDUB | Network Determined User Busy | +| NRCT | No Reply Call Timer | +| PgA | Paging Area | +| PLMN BC | (GSM or UMTS) PLMN Bearer Capability | +| PRN | Provide Roaming Number | +| PUESBINE | Provision of User Equipment Specific Behaviour Information to Network Entities | +| SCUDIF | Service Change and UDI/RDI Fallback | +| SGSN | Serving GPRS support node | +| SIFIC | Send Information For Incoming Call | +| SIFOC | Send Information For Outgoing Call | +| SRI | Send Routeing Information | +| TO | Trunk Originated | +| UDUB | User Determined User Busy | +| UESBI-Iu | User Equipment Specific Behaviour Information over the Iu interface | +| VLRA | The VLR of the A subscriber | +| VLRB | The VLR of the B subscriber | +| VMSCA | The Visited MSC of the A subscriber | +| VMSCB | The Visited MSC of the B subscriber | +| VPLMNA | The Visited PLMN of the A subscriber | +| VPLMNB | The Visited PLMN of the B subscriber | + +# 4 Architecture + +Subclauses 4.1 and 4.2 show the architecture for handling a basic MO call and a basic MT call. A basic mobile-to-mobile call is treated as the concatenation of an MO call and an MT call. + +## 4.1 Architecture for an MO call + +A basic mobile originated call involves signalling between the MS and its VMSC via the BSS, between the VMSC and the VLR and between the VMSC and the destination exchange, as indicated in figure 1. + +In figure 1 and throughout the present document, the term BSS is used to denote a GSM BSS or a UTRAN, as appropriate. + +![Flowchart titled 'Procedure Obtain_Routeing_Address' (ORA4(6)) detailing the architecture for a basic mobile originated call. The process starts with 'a' (MS), followed by 'SCUE_Choose_Voice_Communication' (BSS), 'CCSI_MT_Choose_Voice_Communication' (VMSC), and 'Store Forwarding Information' (VMSC). A decision 'MSRN contains a forwarding number?' leads to either 'Send MT_GMSCB' (VMSC) or 'Routing between MSRN' (VMSC). Both paths lead to 'Result = success' (VMSC), which then leads to 'Result = success' (BSS) and finally to the destination 'x' (Exchange).](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) + +``` + +graph TD + a((a)) --> BSS[SCUE_Choose_Voice_Communication] + BSS -.-> TS1[See TS 23.172] + BSS --> VMSC[CCSI_MT_Choose_Voice_Communication] + VMSC -.-> TS2[See TS 23.093] + VMSC --> SFI[Store Forwarding Information] + SFI --> Decision{MSRN contains a forwarding number?} + Decision -- No --> VMSC2[Routing between MSRN] + Decision -- Yes --> TS3[See TS 23.088] + TS3 --> VMSC3[Send MT_GMSCB] + VMSC3 --> Decision2{Result = success?} + Decision2 -- No --> VMSC4[Routing between MSRN] + Decision2 -- Yes --> VMSC5[Routing between MSRN] + VMSC4 --> VMSC6[Destination between VMSC address] + VMSC5 --> VMSC6 + VMSC6 --> Decision3{Result = success?} + Decision3 -- No --> VMSC7[Routing between MSRN] + Decision3 -- Yes --> VMSC8[Result = success] + VMSC8 --> BSS2[Result = success] + BSS2 --> Exchange((x)) + +``` + +Flowchart titled 'Procedure Obtain\_Routeing\_Address' (ORA4(6)) detailing the architecture for a basic mobile originated call. The process starts with 'a' (MS), followed by 'SCUE\_Choose\_Voice\_Communication' (BSS), 'CCSI\_MT\_Choose\_Voice\_Communication' (VMSC), and 'Store Forwarding Information' (VMSC). A decision 'MSRN contains a forwarding number?' leads to either 'Send MT\_GMSCB' (VMSC) or 'Routing between MSRN' (VMSC). Both paths lead to 'Result = success' (VMSC), which then leads to 'Result = success' (BSS) and finally to the destination 'x' (Exchange). + +Figure 1: Architecture for a basic mobile originated call + +In figure 1 and throughout the present document, the term ISUP is used to denote the telephony signalling system used between exchanges. In a given network, any telephony signalling system may be used. + +When the user of an MS wishes to originate a call, the MS establishes communication with the network using radio interface signalling, and sends a message containing the address of the called party. VMSCA requests information to handle the outgoing call (SIFOC) from VLRA, over an internal interface of the MSC/VLR. If VLRA determines that the outgoing call is allowed, it responds with a Complete Call. VMSCA: + +- establishes a traffic channel to the MS; and +- constructs an ISUP IAM using the called party address and sends it to the destination exchange. + +## 4.2 Architecture for an MT call + +A basic mobile terminated call involves signalling as indicated in figure 2. Communication between VMSCB and the MS is via the BSS, as for the mobile originated case. If VPLMNB supports GPRS and the Gs interface between VLRB and the SGSN is implemented (see 3GPP TS 23.060 [9]) and there is an association between VLRB and the SGSN for the MS, the paging signal towards the MS goes from VMSCB via VLRB and the SGSN to the BSS. The IPLMN, containing GMSCB, is in principle distinct from HPLMNB, containing HLRB, but the practice for at least the majority of current UMTS or GSM networks is that a call to an MS will be routed to a GMSC in HPLMNB. + +![Flowchart titled 'Procedure Obtain_Routeing_Address' (ORA5(6)). It details the logic for routing a mobile terminated call. The process starts at node 5, leading to a 'Result' decision. If 'No', it checks 'CAMEL_FTN' and 'GSM_FTN'. If 'CAMEL_FTN' is 'Yes', it calls 'CAMEL MT_GMSC_Notify_CF' (referencing TS 23.078). If 'GSM_FTN' is 'Yes', it calls 'SCUDIF_Check_Service_Compatibility' (referencing TS 23.172). Both lead to node 2. If 'Result' is 'Yes', it leads to 'Result := Fail' and then to an error node (circle with X).](78ffccd66df9bafd96e3e081110d09dd_img.jpg) + +``` + +graph TD + Start((5)) --> Result{Result} + Result -- No --> CAMEL_FTN{CAMEL_FTN} + CAMEL_FTN -- Yes --> CAMEL_MT_GMSC_Notify_CF[CAMEL MT_GMSC_Notify_CF] + CAMEL_MT_GMSC_Notify_CF -.-> TS_23_078[See TS 23.078] + CAMEL_FTN -- No --> GSM_FTN{GSM_FTN} + GSM_FTN -- Yes --> SCUDIF_Check_Service_Compatibility[SCUDIF_Check_Service_Compatibility] + SCUDIF_Check_Service_Compatibility -.-> TS_23_172[See TS 23.172] + CAMEL_MT_GMSC_Notify_CF -- Continue --> Node2((2)) + SCUDIF_Check_Service_Compatibility -- Continue --> Node2 + Result -- Yes --> Result_Fail[Result := Fail] + Result_Fail --> Error((X)) + +``` + +Flowchart titled 'Procedure Obtain\_Routeing\_Address' (ORA5(6)). It details the logic for routing a mobile terminated call. The process starts at node 5, leading to a 'Result' decision. If 'No', it checks 'CAMEL\_FTN' and 'GSM\_FTN'. If 'CAMEL\_FTN' is 'Yes', it calls 'CAMEL MT\_GMSC\_Notify\_CF' (referencing TS 23.078). If 'GSM\_FTN' is 'Yes', it calls 'SCUDIF\_Check\_Service\_Compatibility' (referencing TS 23.172). Both lead to node 2. If 'Result' is 'Yes', it leads to 'Result := Fail' and then to an error node (circle with X). + +Figure 2: Architecture for a basic mobile terminated call + +When GMSCB receives an ISUP IAM, it requests routing information from HLRB using the MAP protocol. HLRB requests a roaming number from VLRB, also using the MAP protocol, and VLRB returns a roaming number in the Provide Roaming Number Ack. HLRB returns the roaming number to GMSCB in the Send Routeing Info ack. GMSCB uses the roaming number to construct an ISUP IAM, which it sends to VMSCB. When VMSCB receives the IAM, it requests information to handle the incoming call (SIFIC) from VLRB, over an internal interface of the MSC/VLR. If VLRB determines that the incoming call is allowed, it requests VMSCB to page the MS. VMSCB pages the MS using radio interface signalling. When the MS responds, VMSCB informs VLRB in the Page ack message. VLRB instructs VMSCB to connect the call in the Complete call, and VMSCB establishes a traffic channel to the MS. + +## 4.3 Architecture for a TO call + +A basic trunk originated call involves signalling between the PSTN and the PLMN's MSC, as indicated in figure x. The originating exchange may also be another MSC of the same or different PLMN. + +The MSC may also be connected to PBX but that is outside the scope of this document. In the PBX case same modelling applies but the PBX signalling is different to ISUP. + +![Figure 4.3.1: Architecture for a basic trunk originated call. This is a flowchart titled 'Procedure Obtain_Routing_Address' with the code 'ORA6(6)'. It starts with an oval labeled '2' leading to a box 'BOR=OR', then 'Address Completion'. A decision diamond 'Routing?' has a 'Fail' path to 'Result=Aborted' and a 'Success' path to 'Send TO 23.012'. The next box is 'Route to appropriate destination address', which leads to another decision diamond 'Routing?'. This second 'Routing?' has a 'Fail' path to 'Result=Aborted' and a 'Success' path to 'Send TO 23.012'. Below this, a decision diamond 'Routing address?' has a 'True' path leading to a sequence of boxes: 'Routing address', 'Destination address', 'OR=True', 'Result=Success', and an oval connector. The 'False' path from 'Routing address?' leads to a decision diamond 'CAMEL phase 2 or later supported?'. If 'Yes', it goes to 'CAMEL MT-CHARGE-DIRECT' and then to a decision diamond 'OR=False?'. If 'No', it goes to 'CAMEL MT-CHARGE-DIRECT' and then to a decision diamond 'OR=False?'. Both 'OR=False?' diamonds lead to 'Result=Success' and an oval connector. There are also 'Send TO 23.012' messages associated with the CAMEL paths.](ddc7460821484f1ae2835c67955c554c_img.jpg) + +Figure 4.3.1: Architecture for a basic trunk originated call. This is a flowchart titled 'Procedure Obtain\_Routing\_Address' with the code 'ORA6(6)'. It starts with an oval labeled '2' leading to a box 'BOR=OR', then 'Address Completion'. A decision diamond 'Routing?' has a 'Fail' path to 'Result=Aborted' and a 'Success' path to 'Send TO 23.012'. The next box is 'Route to appropriate destination address', which leads to another decision diamond 'Routing?'. This second 'Routing?' has a 'Fail' path to 'Result=Aborted' and a 'Success' path to 'Send TO 23.012'. Below this, a decision diamond 'Routing address?' has a 'True' path leading to a sequence of boxes: 'Routing address', 'Destination address', 'OR=True', 'Result=Success', and an oval connector. The 'False' path from 'Routing address?' leads to a decision diamond 'CAMEL phase 2 or later supported?'. If 'Yes', it goes to 'CAMEL MT-CHARGE-DIRECT' and then to a decision diamond 'OR=False?'. If 'No', it goes to 'CAMEL MT-CHARGE-DIRECT' and then to a decision diamond 'OR=False?'. Both 'OR=False?' diamonds lead to 'Result=Success' and an oval connector. There are also 'Send TO 23.012' messages associated with the CAMEL paths. + +Figure 4.3.1: Architecture for a basic trunk originated call + +In figure x and throughout the present document, the term ISUP is used to denote the telephony signalling system used between exchanges. In a given network, any telephony signalling system may be used. + +The MSC receives a setup (IAM) message from the originating exchange. The MSC analyses the called party number and routes the call to an appropriate destination. If the called party number is an MSISDN the gateway MSC functionality is activated. If the MSISDN belongs to another PLMN (or is ported out), the call is routed to another PLMN. If the called number is a PSTN number then the call is routed to (appropriate) PSTN operator. There may be other destinations also. + +# 5 Information flows + +In this clause and clause 7, the terms "security procedures" and "security control" denote the UMTS ciphering and integrity protection mechanism defined in 3GPP TS 33.102 [32] or the GSM ciphering mechanism defined in 3GPP TS 43.020 [1], as appropriate. + +## 5.1 Information flow for an MO call + +An example information flow for an MO call is shown in figure 3; many variations are possible. Signalling over the radio interface between MSA and BSSA or VMSCA is shown by dotted lines; signalling over the Iu interface (for UMTS) or the A interface (for GSM) between BSSA and VMSCA is shown by dashed lines; signalling over the B interface between VMSCA and VLRA is shown by chain lines; and ISUP signalling between VMSCA and the destination exchange is shown by solid lines. + +![Flowchart for Procedure Send_ACM_If_Required. It starts with a connector symbol, followed by a decision 'ACM sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to another decision 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Address Complete', then 'ACM sent := True', and finally to an exit connector. A note on the left says 'Procedure to send an Address Complete Message to the preceding exchange if one is required for this call'. A note on the right says 'Signals to the left are to the originating exchange'.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Procedure Send\_ACM\_If\_Required + +SACMIR1(1) + +``` +graph TD; Start([ ]) --> ACM_Sent{ACM sent}; ACM_Sent -- True --> Call_Progress{{Call Progress}}; ACM_Sent -- False --> Network_Connect_Sent{Network connect sent}; Network_Connect_Sent -- True --> Call_Progress; Network_Connect_Sent -- False --> Address_Complete{{Address Complete}}; Address_Complete --> ACM_Sent_True[ACM sent := True]; ACM_Sent_True --> End(( )); +``` + +Procedure to send an Address Complete Message to the preceding exchange if one is required for this call + +Signals to the left are to the originating exchange + +Flowchart for Procedure Send\_ACM\_If\_Required. It starts with a connector symbol, followed by a decision 'ACM sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to another decision 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Address Complete', then 'ACM sent := True', and finally to an exit connector. A note on the left says 'Procedure to send an Address Complete Message to the preceding exchange if one is required for this call'. A note on the right says 'Signals to the left are to the originating exchange'. + +- NOTE 1: Authentication may occur at any stage during the establishment of an MO call; its position in this message flow diagram is an example. +- NOTE 2: Security procedures may be initiated at any stage after authentication; the position in this message flow diagram is an example. +- NOTE 3: If ciphering is not required for a GSM connection, the MSC may send a CM service accept towards the MS; optionally it may instead send a "start ciphering" request indicating that no ciphering is required. This option is not available for a UMTS connection [ffs]. +- NOTE 4: The network may request the IMEI from the MS, and may check the IMEI, at any stage during the establishment of an MO call, either as part of the procedure to start security procedures or explicitly after security procedures have started; this is not shown in this message flow diagram. + +**Figure 3: Information flow for a basic mobile originated call** + +When the user wishes to originate a call, MSA establishes a signalling connection with BSSA, and sends a Connection Management (CM) service request to BSSA, which relays it to VMSCA. VMSCA sends a Process Access Request to VLRA. VLRA may then initiate authentication, as described in 3GPP TS 33.102 [32] for UMTS and 3GPP TS 43.020 [1] for GSM. VLRA may also initiate security procedures at this stage, as described in 3GPP TS 33.102 [32] for UMTS 3GPP TS 43.020 [1] for GSM. If the user originates one or more new MO calls in a multicall configuration, MSA sends a CM service request through the existing signalling connection for each new call. + +If the MS has performed the Connection Management (CM) service request in a CSG cell, VLRA shall control if the CSG cell is allowed by the CSG subscription data stored in VLRA. If the CSG cell is not allowed, VLRA shall reject the Process Access Request. + +If the MS has performed the Connection Management (CM) service request in a hybrid cell, VLRA shall set the CSG membership status in the Process Access Request ack according to the CSG subscription data stored in VLRA. + +If VLRA determines that MSA is allowed service, it sends a Process Access Request ack to VMSCA. If VMSCA has received a Start security procedures message from VLRA, the Process Access Request ack message triggers a Start security procedures message towards BSSA; otherwise VMSCA sends a CM Service Accept message towards BSSA. + +If BSSA receives a Start security procedures message from VMSCA, it initiates security procedures as described in 3GPP TS 33.102 [32] for UMTS and 3GPP TS 43.020 [1] for GSM; when security procedures have been successfully initiated, MSA interprets this in the same way as a CM Service Accept. If security procedures are not required at this stage, BSSA relays the CM Service Accept to MSA. + +When MSA has received the CM Service Accept, or security procedures have been successfully initiated, MSA sends a Set-up message containing the B subscriber address via BSSA to VMSCA. MSA also uses the Set-up message to indicate the bearer capability required for the call; VMSCA translates this bearer capability into a basic service, and determines whether an interworking function is required. VMSCA sends to VLRA a request for information to handle the outgoing call, using a Send Info For Outgoing Call (SIFOC) message containing the B subscriber address. + +If VLRA determines that the call should be connected, it sends a Complete Call message to VMSCA. VMSCA sends a Call Proceeding message via BSSA to MSA, to indicate that the call request has been accepted, and sends an Allocate channel message to BSSA, to trigger BSSA and MSA to set up a traffic channel over the radio interface. The Call Proceeding message includes bearer capability information if any of the negotiable parameters of the bearer capability has to be changed. When the traffic channel assignment process is complete (indicated by the Allocation complete message from BSSA to VMSCA), VMSCA constructs an ISUP IAM using the B subscriber address, and sends it to the destination exchange. + +When the destination exchange returns an ISUP Address Complete Message (ACM), VMSCA sends an Alerting message via BSSA to MSA, to indicate to the calling user that the B subscriber is being alerted. + +When the destination exchange returns an ISUP ANswer Message (ANM), VMSCA sends a Connect message via BSSA to MSA, to instruct MSA to connect the speech path. + +The network then waits for the call to be cleared. + +For an emergency call, a different CM service type (emergency call) is used, and the mobile may identify itself by an IMEI. It is a network operator option whether to allow an emergency call when the mobile identifies itself by an IMEI. Details of the handling are shown in clause 7. + +## 5.2 Information flow for retrieval of routeing information for an MT call + +The information flow for retrieval of routeing information for an MT call is shown in figure 4. ISUP signalling between the originating exchange and GMSCB, and between GMSCB and VMSCB is shown by solid lines; signalling over the MAP interfaces between GMSCB and HLRB and between HLRB and VLRB, and over the B interface between VLRB and VMSCB is shown by chain lines; signalling over the Iu interface (for UMTS) or the A interface (for GSM) between VMSCB and BSSB is shown by dashed lines; and signalling over the radio interface between BSSB and MSB is shown by dotted lines. + +![Sequence diagram showing information flow for retrieval of routeing information for a basic mobile terminated call. The diagram involves six entities: GMSC, HLRB, VLRB, VMSCB, BSSB, and MSB. The sequence starts with an IAM message to GMSC. GMSC sends an SRI to HLRB, which sends a PRN to VLRB. VLRB sends a Page MS to VMSCB. VMSCB sends a Page to BSSB, which then sends a Page to MSB. MSB responds with Chan req, Imm ass, and Page resp. VMSCB receives MS conn estab from BSSB and sends a Process access rec (note 2) to VLRB. VLRB sends a PRN ack to HLRB, which sends an SRI ack to GMSC. VMSCB also sends Start security procedures to BSSB, which sends Security control command to MSB. MSB responds with Security control response. Finally, GMSC sends an IAM (note 3) to VMSCB.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant HLRB + participant VLRB + participant VMSCB + participant BSSB + participant MSB + + Note left of GMSC: IAM + GMSC->>HLRB: SRI (chain line) + HLRB->>VLRB: PRN (chain line) + Note right of VLRB: (note 1) + VLRB->>VMSCB: Page MS (chain line) + VMSCB-->BSSB: Page (dashed line) + BSSB-->MSB: Page (dotted line) + MSB-->BSSB: Chan req (dotted line) + BSSB-->MSB: Imm ass (dotted line) + MSB-->BSSB: Page resp (dotted line) + BSSB-->VMSCB: MS conn estab (dashed line) + VMSCB->>VLRB: Process access rec (note 2) (chain line) + VLRB->>VMSCB: Start security procedures (chain line) + VLRB->>HLRB: PRN ack (chain line) + HLRB->>GMSC: SRI ack (chain line) + VMSCB->>VLRB: Process access req ack (chain line) + VMSCB-->BSSB: Start security procedures (dashed line) + BSSB-->MSB: Security control command (dotted line) + MSB-->BSSB: Security control response (dotted line) + Note left of GMSC: IAM (note 3) + GMSC->>VMSCB: IAM (solid line) + +``` + +Sequence diagram showing information flow for retrieval of routeing information for a basic mobile terminated call. The diagram involves six entities: GMSC, HLRB, VLRB, VMSCB, BSSB, and MSB. The sequence starts with an IAM message to GMSC. GMSC sends an SRI to HLRB, which sends a PRN to VLRB. VLRB sends a Page MS to VMSCB. VMSCB sends a Page to BSSB, which then sends a Page to MSB. MSB responds with Chan req, Imm ass, and Page resp. VMSCB receives MS conn estab from BSSB and sends a Process access rec (note 2) to VLRB. VLRB sends a PRN ack to HLRB, which sends an SRI ack to GMSC. VMSCB also sends Start security procedures to BSSB, which sends Security control command to MSB. MSB responds with Security control response. Finally, GMSC sends an IAM (note 3) to VMSCB. + +NOTE 1: If pre-paging is used, paging is initiated after VLRB has accepted the PRN message. The paging procedure is described in subclause 5.3. + +NOTE 2: VMSCB starts the timer for the release of radio resources after it sends the Process Access Request message to VLRB. VMSCB releases the radio resource allocated for the MT call if the timer expires before the IAM is received, and when the MAP RELEASE\_RESOURCES message is received from the GMSC. + +NOTE 3: If an ISUP REL message is received at the GMSC between sending of SRI and receiving of SRI ack, the GMSC does not send IAM to the VMSC. Instead a MAP Release\_Resources message may be sent to the VMSC. + +**Figure 4: Information flow for retrieval of routeing information for a basic mobile terminated call** + +When GMSCB receives an IAM, it analyses the called party address. If GMSCB can derive an HLR address from the B party address, it sends a request for routeing information (SRI) to HLRB. If GMSCB supports pre-paging (i.e. it is prepared to wait long enough for the SRI ack to allow pre-paging to be completed), it indicates this by an information element in the SRI message. + +HLRB decides whether pre-paging is supported according to the following criteria: + +- GMSCB has indicated that it supports pre-paging; and +- HLRB supports pre-paging (i.e. it is prepared to wait long enough for the PRN ack to allow pre-paging to be completed). + +HLRB sends a request for a roaming number (PRN) to VLRB; if pre-paging is supported, it indicates this by an information element in the PRN message. If Paging Area function is supported in HLRB then HLRB sends the paging area if stored in HLR. VLRB returns the roaming number in the PRN ack, and HLRB relays the roaming number to GMSCB in the SRI ack. GMSCB constructs an IAM using the roaming number, and sends it to VMSCB. + +If the GMSC performs domain selection through HLR interrogation and the HLR supports domain selection functionality, HLRB executes domain selection functionality. The HLR shall: + +- send PRN to VLRB as defined in this section , if the result of domain selection is to handle the call in CS domain; or +- reply with SRI ack without sending PRN to VLRB, if the result of domain selection is to transfer the call from CS domain to IMS domain. + +### 5.2.1 Mobile Terminating Roaming Retry Call after successful Retrieval of Routeing Information + +The information flow for mobile terminating roaming retry call after successful retrieval of routeing information is shown in figure 4a. It applies to a mobile terminating call while the called mobile is simultaneously moving from an old to a new MSC, if the GMSC, the HLR and the old terminating VMSC support the MT Roaming Retry procedure. + +In that case, upon receipt of: + +- an ISUP IAM message which was preceded by a MAP Cancel Location procedure, or +- a MAP Cancel Location procedure while on-going paging, + +the old VMSC shall instruct the GMSC to resume terminating call procedure by sending a MAP Resume Call Handling message. The GMSC shall then release the ISUP connection to the old VMSC, terminate any open CAP dialogue, and retry the terminating call setup towards the new MSC by sending an additional SRI to the HLR. This second SRI request leads to obtaining a roaming number from the new MSC towards which the call can then be delivered (possibly after new CAMEL interactions). + +An HLR supporting the "mobile terminating roaming retry" feature shall always send a MAP Cancel Location message message to the old VLR upon receipt of the MAP Update Location from the new VLR. This shall also apply if the HLR and the old VLR support Super-Charger (see 3GPP TS 23.116 [24]), regardless of whether the new VLR indicates or not during the location update procedure that the previous network entity must be notified. + +- NOTE 1: HLRs compliant with an earlier release of the specification and supporting mobile terminating roaming retry and Super-Charger may not always send a Cancel Location message in a supercharged network. To support mobile terminating roaming retry with such HLR implementations, the old VLR can start a timer upon receipt of the MAP Send Identification message while on-going paging to trigger the sending of an internal Cancel Location to the old MSC and thus the sending of a MAP Resume Call Handling message by the old MSC to the GMSC after the sending of the MAP Update Location by the new VLR to the HLR. + +#### Procedure Obtain\_Routeing\_Address + +ORA2(6) + +Procedure in a GMSC to determine the address to which a call should be routed + +Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the HLR + +![Flowchart for Procedure Obtain_Routeing_Address. The process starts with 'Wait_for_Routeing_Info', followed by 'Send Routeing Info negative response'. A decision 'If MT Roaming Retry is supported and MT Roaming Retry Indicator received?' follows. If Yes, it goes to 'Clear RoamingRetry Supported IE' -> 'Send Routeing Info' -> 'Wait_for_Routeing_Info'. If No, it goes to 'Call Released?'. If Yes, 'Result:= Aborted'. If No, 'SCUDIF negative SRI response handling' -> 'See TS 23.172'. Both lead to a 'Result' junction. From 'Result', 'Pass' leads to connector '4'. 'Fail' leads to 'OR_Handle_SRI Negative Response (Own PLMN)' -> 'See TS 23.079' -> 'Result= Pass?'. If 'Result= Pass?' is Yes, 'Result:=Pass' -> connector. If No, 'Error= Unknown subscriber?'. If Yes, 'MOBILE NUMBER PORTABILITY_IN_QoHR' -> 'See TS 23.066' -> 'Result:=Fail' -> connector. If No, 'Result= Number ported?'. If Yes, 'Routeing address:= routeing number' -> 'Result:= Routeing number' -> connector. If No, 'Result:=Fail' -> connector. A 'Release' -> 'Set: Call Released' -> 'Wait_for_Routeing_Info' path is also shown on the left.](77464a47f104d0d647b2414591137b64_img.jpg) + +``` + +graph TD + W1([Wait_for_Routeing_Info]) --> S1[Send Routeing Info negative response] + S1 --> D1{If MT Roaming Retry is supported and MT Roaming Retry Indicator received?} + D1 -- Yes --> C1[Clear RoamingRetry Supported IE] + C1 --> S2[Send Routeing Info] + S2 --> W2([Wait_for_Routeing_Info]) + D1 -- No --> D2{Call Released?} + D2 -- Yes --> R1[Result:= Aborted] + D2 -- No --> S3[SCUDIF negative SRI response handling] + S3 --> T1[See TS 23.172] + R1 --> J1((X)) + S3 --> J2{Result} + T1 --> J2 + J2 -- Pass --> C4((4)) + J2 -- Fail --> S4[OR_Handle_SRI Negative Response Own PLMN] + S4 --> T2[See TS 23.079] + T2 --> D3{Result= Pass?} + D3 -- Yes --> R2[Result:=Pass] + R2 --> J3((X)) + D3 -- No --> D4{Error= Unknown subscriber?} + D4 -- Yes --> S5[MOBILE NUMBER PORTABILITY_IN_QoHR] + S5 --> T3[See TS 23.066] + T3 --> R3[Result:=Fail] + R3 --> J4((X)) + D4 -- No --> D5{Result= Number ported?} + D5 -- Yes --> S6[Routeing address:= routeing number] + S6 --> R4[Result:= Routeing number] + R4 --> J5((X)) + D5 -- No --> R5[Result:=Fail] + R5 --> J4 + R5 --> J2 + R1 --> S7[Release] + S7 --> S8[Set: Call Released] + S8 --> W3([Wait_for_Routeing_Info]) + +``` + +Flowchart for Procedure Obtain\_Routeing\_Address. The process starts with 'Wait\_for\_Routeing\_Info', followed by 'Send Routeing Info negative response'. A decision 'If MT Roaming Retry is supported and MT Roaming Retry Indicator received?' follows. If Yes, it goes to 'Clear RoamingRetry Supported IE' -> 'Send Routeing Info' -> 'Wait\_for\_Routeing\_Info'. If No, it goes to 'Call Released?'. If Yes, 'Result:= Aborted'. If No, 'SCUDIF negative SRI response handling' -> 'See TS 23.172'. Both lead to a 'Result' junction. From 'Result', 'Pass' leads to connector '4'. 'Fail' leads to 'OR\_Handle\_SRI Negative Response (Own PLMN)' -> 'See TS 23.079' -> 'Result= Pass?'. If 'Result= Pass?' is Yes, 'Result:=Pass' -> connector. If No, 'Error= Unknown subscriber?'. If Yes, 'MOBILE NUMBER PORTABILITY\_IN\_QoHR' -> 'See TS 23.066' -> 'Result:=Fail' -> connector. If No, 'Result= Number ported?'. If Yes, 'Routeing address:= routeing number' -> 'Result:= Routeing number' -> connector. If No, 'Result:=Fail' -> connector. A 'Release' -> 'Set: Call Released' -> 'Wait\_for\_Routeing\_Info' path is also shown on the left. + +###### **Figure 4a: Information flow for a mobile terminating roaming retry call after successful Retrieval of Routeing Information** + +1. A GMSC supporting the "mobile terminating roaming retry" feature includes the Call Reference Number, the GMSC address and the MT Roaming Retry Supported IE in the first SRI sent to the HLR. + 2. A HLR supporting the "mobile terminating roaming retry" feature includes the Call Reference Number, the GMSC address and the MT Roaming Retry Supported IE in the PRN sent to the MSC/VLR if received in the SRI. + - 2'. An old VLR supporting the "mobile terminating roaming retry" feature may indicate in the MAP Send Identification response sent to the new VLR whether there is a pending mobile terminating call at the old VLR. + 3. Receipt of the MT Roaming Retry Supported IE in the PRN indicates that the GMSC supports the Resume Call Handling procedure and the mobile terminating roaming retry feature. Upon receipt of the ISUP IAM message which was preceded by a MAP Cancel Location message, or upon receipt of the MAP Cancel Location message while paging, the old MSC/VLR stops paging, if paging was on-going, and if it supports the "mobile terminating roaming retry" feature and did receive the MT Roaming Retry Supported IE in the PRN, sends an RCH message to the GMSC with the MT Roaming Retry IE. The old MSC shall terminate any open CAP dialogue when receiving RCH ACK or ISUP REL message. + 4. Upon receipt of the RCH message with the MT roaming retry IE, the GMSC acknowledges the RCH message, releases the call towards the old MSC/VLR, terminates T-CSI dialog with the SCP, if any exists, using T-Abandon EDP, and re-sends a new SRI to the HLR (still a 'basic call' interrogation type) using a new call reference number. + 5. To avoid looping, the new SRI shall be sent without the Roaming Retry Supported IE. Furthermore, the GMSC shall use an appropriate high value for the timer supervising receipt of SRI ACK. Note that the Suppress T-CSI field is not set since the Mobile Terminating procedure is restarted from the beginning including the handling of CAMEL interaction on T-CSI (this is because T-CSI treatments may end differently if old and new MSCs are not in the same PLMN or in the same geographical area, e.g. different charging rates or regional service subscription). + 6. Upon receipt of a SRI request or PRN ack (regardless of the PRN response from the old VLR) during an on-going Update Location procedure, the HLR delays the sending of the PRN to the new VLR till completion of the Update Location procedure. + 7. Receipt of the MSRN from the new MSC/VLR enables the GMSC to relay the call towards the new MSC/VLR. + 8. If the IAM message is received before the Location Update procedure is completed with the MS, the new MSC may delay the setup of the call until the completion of the Location Update procedure or start at once the normal terminating call procedure. In the former case, if the Location Update is received with the "follow-on" indication and if the VMSC supports the "follow-on" indication, the incoming IAM may either be handled as a waiting call or forwarded as Busy (CFB), depending on the state of the "follow-on" call and the subscriber's subscription data. +If no IAM message has been received at the time the Location Update procedure completes, the new MSC may shortly defer the release of the signalling connection with the MS if the old VLR indicated in the MAP Send Identification response that there is a pending mobile terminating call at the old VLR. +- NOTE 2: For a CS Fallback mobile terminating call, the new MSC also defers the release of the signalling connection with the MS if the MS includes the "CSMT" flag in the Location Update message (see subclause 7.5 of 3GPP TS 23.272 [42]). + +Similarly, a HLR supporting the "mobile terminating roaming retry" feature should wait for the completion of any on-going Location Update procedure when processing other terminating requests e.g. MAP-SEND-ROUTING-INFO-FOR-SM, MAP-SEND-ROUTING-INFO-FOR-LCS, MAP-ANY-TIME-INTERROGATION. More generally, this also applies to all TCAP transactions that the HLR may have to open toward a VLR (e.g. USSD, PSI). + +### 5.2.2 Mobile Terminating Roaming Retry Call during Retrieval of Routeing Information + +The information flow for mobile terminating roaming retry call during retrieval of routing information is shown in figure 4b. It applies to a mobile terminating call while the called mobile is simultaneously moving from an old to a new + +MSC, if the GMSC and the HLR support the MT Roaming Retry procedure. The procedure may e.g. apply during pre-paging if the GMSC, HLR and old MSC/VLR support pre-paging. + +In that case, upon receipt of: + +- a MAP Cancel Location procedure while on-going pre-paging, + +the old VMSC/VLR shall return a PRN negative response to the HLR. If "Suppress T-CSI" was included in the SRI request, the HLR shall relay a SRI negative response with the error "absent subscriber" including the reason "mtRoamingRetry" to the GMSC. If "Suppress T-CSI" was not included in the SRI request, and the called party is roaming to a different MSC/VLR during the PRN procedure, the HLR may either return a SRI negative response with the error "absent subscriber" including the reason "mtRoamingRetry" to the GMSC, or instead delay the sending of a PRN request to the new VLR until completion of the Update Location procedure. + +The GMSC shall release the T-CSI dialogue (if existing) and retry the terminating call setup towards the new MSC by sending an additional SRI to the HLR when receiving a SRI negative response with the error "absent subscriber" including the reason "mtRoamingRetry". This second SRI request leads to obtaining a roaming number from the new MSC towards which the call can then be delivered (possibly after new CAMEL interactions). + +NOTE 1: If "Suppress T-CSI" was included in the SRI request, the mobile terminating procedure is restarted from the beginning including the handling of CAMEL interaction on T-CSI, because T-CSI treatments can end differently if old and new MSCs are not in the same PLMN or in the same geographical area, e.g. different charging rates or regional service subscription. + +An HLR supporting the "mobile terminating roaming retry" feature shall always send a MAP Cancel Location message message to the old VLR upon receipt of the MAP Update Location from the new VLR. This shall also apply if the HLR and the old VLR support Super-Charger (see 3GPP TS 23.116 [24]), regardless of whether the new VLR indicates or not during the location update procedure that the previous network entity must be notified. + +NOTE 2: Legacy HLR implementations supporting mobile terminating roaming retry and Super-Charger may not always send a Cancel Location message in a supercharged network. To support mobile terminating roaming retry with such HLR implementations, the old VLR can start a timer upon receipt of the MAP Send Identification message while on-going paging to trigger the sending of an internal Cancel Location to the old MSC and thus the sending of a PRN negative response to the HLR after the sending of the MAP Update Location by the new VLR to the HLR. + +![Sequence diagram showing information flow for a mobile terminating roaming retry call. Lifelines: GMSC, HLR, Old VMSC/VLR, New VMSC/VLR, MS. The diagram shows the interaction between these entities during a call setup, including location updates, authentication, and routing information exchange.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant HLR + participant OldVMSC_VLR as Old VMSC/VLR + participant NewVMSC_VLR as New VMSC/VLR + participant MS + + Note right of GMSC: 1 SRI (B, GMSC@, call Ref., Roamingretry) + GMSC->>HLR: SRI (B, GMSC@, call Ref., Roamingretry) + Note right of HLR: 2 PRN (call ref., GMSC@) + HLR->>OldVMSC_VLR: PRN (call ref., GMSC@) + Note right of OldVMSC_VLR: Pre-Paging + OldVMSC_VLR-->>MS: Pre-Paging + Note right of OldVMSC_VLR: Send Identification 2' + OldVMSC_VLR->>NewVMSC_VLR: Send Identification 2' + Note right of NewVMSC_VLR: Authentication Procedure + NewVMSC_VLR->>HLR: Update Location + Note right of HLR: 3 Cancel Location + HLR->>OldVMSC_VLR: Cancel Location + OldVMSC_VLR->>HLR: Cancel Location Ack + Note right of OldVMSC_VLR: Old MSC/VLR stops pre-paging timer if it is ongoing pre-paging and return a PRN negative response + NewVMSC_VLR->>HLR: Insert Subscriber Data (multiple) + Note right of HLR: 3 PRN Negative Response + HLR->>OldVMSC_VLR: PRN Negative Response + Note right of OldVMSC_VLR: 4 + Note right of GMSC: 2nd SRI Negative Response (Absent Subscriber / Roaming retry) + GMSC->>HLR: SRI Negative Response (Absent Subscriber / Roaming retry) + Note right of GMSC: 2nd SRI (B, basic call interrogation) 5 + GMSC->>HLR: SRI (B, basic call interrogation) + Note right of GMSC: HLR delays the sending of PRN until location update procedure finishes. 6 + NewVMSC_VLR->>HLR: Insert Subscriber Data (continued) + NewVMSC_VLR->>HLR: Update Location Ack + HLR->>NewVMSC_VLR: PRN + NewVMSC_VLR->>HLR: PRN ACK (MSRN) 7 + Note right of GMSC: 2nd SRI ACK (MSRN) 7 + GMSC->>HLR: SRI ACK (MSRN) + HLR->>NewVMSC_VLR: IAM (MSRN) + Note right of NewVMSC_VLR: New VMSC/VLR may delay setup until location update procedure finishes. 8 + NewVMSC_VLR->>MS: LocUpdate Accept + NewVMSC_VLR->>MS: TMSI Realloc Cmplt + NewVMSC_VLR->>MS: Setup + MS->>NewVMSC_VLR: Call Confirmed + Note right of NewVMSC_VLR: Normal MT call procedure follows. + +``` + +Sequence diagram showing information flow for a mobile terminating roaming retry call. Lifelines: GMSC, HLR, Old VMSC/VLR, New VMSC/VLR, MS. The diagram shows the interaction between these entities during a call setup, including location updates, authentication, and routing information exchange. + +**Figure 4b: Information flow for a mobile terminating roaming retry call during Retrieval of Routeing Information** + +1. A GMSC supporting the "mobile terminating roaming retry" feature includes the Call Reference Number, the GMSC address, and the MT Roaming Retry Supported IE in the first SRI sent to the HLR. The Pre-paging Supported IE is included in the SRI message if the GMSC supports the "Pre-paging" feature. + +2. A HLR supporting the "mobile terminating roaming retry" feature includes the Call Reference Number and the GMSC address in the PRN sent to the MSC/VLR if received in the SRI. If GMSC and HLR support the "Pre-paging" feature, the Pre-paging Supported IE is included in the PRN message. +- 2'. An old VLR supporting the "mobile terminating roaming retry" feature may indicate in the MAP Send Identification response sent to the new VLR whether there is a pending mobile terminating call at the old VLR. +3. Upon receipt of the MAP Cancel Location message while pre-paging, the old MSC/VLR stops pre-paging and sends a PRN negative response message to the HLR. If meanwhile the HLR has received a new Update Location procedure from a new MSC/VLR, the HLR returns a SRI negative response with error "absent subscriber" including the reason "mtRoamingRetry" to the GMSC. +4. Upon receipt of the SRI negative response with error "absent subscriber" including the reason "mtRoamingRetry", the GMSC re-sends a new SRI to the HLR (still a 'basic call' interrogation type) using a new call reference number. +- 5.-8. See the same procedures from step 5 to step 8 in the figure 4a. + +Similarly, a HLR supporting the "mobile terminating roaming retry" feature should wait for the completion of any ongoing Location Update procedure when processing other terminating requests e.g. MAP-SEND-ROUTING-INFO-FOR-SM, MAP-SEND-ROUTING-INFO-FOR-LCS, MAP-ANY-TIME-INTERROGATION. More generally, this also applies to all TCAP transactions that the HLR may have to open toward a VLR (e.g. USSD, PSI). + +### 5.2.3 Mobile Terminating Roaming Forwarding Call after successful Retrieval of Routeing Information + +The information flow for mobile terminating roaming forwarding (MTRF) call after successful retrieval of routeing information is shown in figure 4c. It applies to a mobile terminating call while the called mobile is simultaneously moving from an old to a new MSC, if the old and the new terminating MSC/VLRs support the MT Roaming Forwarding procedure. The HLR should also support the Mobile Terminating Roaming Forwarding procedure in order to ensure that roaming forwarding can be offered in all scenarios (e.g. in case of IMSI in the LAU Request from UE). + +NOTE 1: The full support of MTRF for roaming scenarios requires both home network (HLR) and visited network (VLRs) to support the MTRF procedures and protocol extensions. As deployment scenarios may exist where the home network (HLR) has not been updated to support MTRF the visited network can perform a limited roaming forwarding solution autonomously if the MTRF Supported flag is signalled in the MAP Send Identification message under the conditions defined in this clause. + +The new terminating VLR shall include an MTRF Supported flag in the MAP Update Location message sent to the HLR. If the HLR authorises the MTRF call between the old and the new terminating MSCs, the HLR shall include the MTRF Supported And Authorized flag and the new MSC/VLR numbers in the MAP Cancel Location message sent to the old VLR. Otherwise if the HLR disallows the MTRF call between the old and the new terminating MSCs, the HLR shall include the MTRF Supported And Not Authorized flag in the MAP Cancel Location message sent to the old VLR. The new VLR may also signal the MTRF Supported flag and the new MSC/VLR numbers in the MAP Send Identification message to indicate to the old VLR that it supports MTRF. + +An HLR supporting the "mobile terminating roaming forwarding" feature shall always send a MAP Cancel Location message message to the old VLR upon receipt of the MAP Update Location from the new VLR. This shall also apply if the HLR and the old VLR support Super-Charger (see 3GPP TS 23.116 [24]), regardless of whether the new VLR indicates or not during the location update procedure that the previous network entity must be notified. + +If the old VLR receives a MAP Send Identification message containing the MTRF Supported flag it shall not trigger any MAP Provide Roaming Number request to the new terminating VLR until it has received the MAP Cancel Location message. + +Upon receipt of a MAP Cancel Location message while ongoing paging, if either of the following is true: + +- the MAP Cancel Location message includes the MTRF Supported And Authorized flag or; +- the MAP Cancel Location message does not include the MTRF Supported And Not Authorized flag and the old VLR has received the MTRF Supported flag earlier in the MAP Send Identification message, + +the old VLR shall send a MAP Provide Roaming Number request (including the MTRF Indicator and the parameters received from the HLR in the MAP Provide Roaming Number) to the new terminating VLR. The new terminating MSC/VLR shall then allocate an MSRN to allow the call to be routed from the old MSC to the new MSC and send it to the old VLR within the MAP Provide Roaming Number response. + +#### Procedure Obtain\_Routeing\_Address + +ORA2(6) + +Procedure in a GMSC to determine the address to which a call should be routed + +Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the HLR + +![Flowchart for Procedure Obtain_Routeing_Address. The process starts with 'Wait_for_Routeing_Info', followed by 'Send Routeing Info negative response'. A decision 'If MT Roaming Retry is supported and MT Roaming Retry Indicator received?' follows. If 'Yes', it goes to 'Clear RoamingRetry Supported IE', 'Send Routeing Info', and 'Wait_for_Routeing_Info'. If 'No', it checks 'Call Released?'. If 'Yes', 'Result:= Aborted'. If 'No', it goes to 'SCUDIF negative SRI response handling' (See TS 23.172). Both lead to a 'Result' triangle. From 'Result', 'Pass' leads to connector '4', 'Fail' leads to 'OR Handle_SRI Negative_Response (Own PLMN)' (See TS 23.079). From 'OR Handle_SRI Negative_Response (Own PLMN)', 'Result= Pass?' follows. If 'Yes', 'Result:=Pass' leads to a connector. If 'No', 'Error= Unknown subscriber?' follows. If 'Yes', it goes to 'MOBILE NUMBER PORTABILITY_IN_QoHR' (See TS 23.066). If 'No', 'Result= Number ported?' follows. If 'Yes', 'Routeing address:= routeing number' and 'Result:= Routeing number' lead to a connector. If 'No', 'Result:=Fail' leads to a connector. A 'Retry Send Routeing Info' block also leads to 'Wait_for_Routeing_Info'.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +``` + +graph TD + Start([Wait_for_Routeing_Info]) --> SendNeg[Send Routeing Info negative response] + SendNeg --> Decision1{If MT Roaming Retry is supported and MT Roaming Retry Indicator received?} + Decision1 -- Yes --> ClearIE[Clear RoamingRetry Supported IE] + ClearIE --> SendInfo[Send Routeing Info] + SendInfo --> WaitInfo1([Wait_for_Routeing_Info]) + Decision1 -- No --> Decision2{Call Released?} + Decision2 -- Yes --> Aborted[Result:= Aborted] + Decision2 -- No --> SCUDIF[SCUDIF negative SRI response handling] + SCUDIF --> TS172[See TS 23.172] + Aborted --> ResultTriangle1{Result} + SCUDIF --> ResultTriangle1 + ResultTriangle1 -- Pass --> Connector4((4)) + ResultTriangle1 -- Fail --> HandleSRI[OR Handle_SRI Negative_Response (Own PLMN)] + HandleSRI --> TS079[See TS 23.079] + HandleSRI --> ResultPass{Result= Pass?} + ResultPass -- Yes --> PassResult[Result:=Pass] + PassResult --> ConnectorX1(( )) + ResultPass -- No --> UnknownSub{Error= Unknown subscriber?} + UnknownSub -- Yes --> Portability[MOBILE NUMBER PORTABILITY_IN_QoHR] + Portability --> TS066[See TS 23.066] + UnknownSub -- No --> NumberPorted{Result= Number ported?} + NumberPorted -- Yes --> RouteingAddr[Routeing address:= routeing number] + RouteingAddr --> RouteingNum[Result:= Routeing number] + RouteingNum --> ConnectorX2(( )) + NumberPorted -- No --> FailResult[Result:=Fail] + FailResult --> ConnectorX3(( )) + Retry[Retry Send Routeing Info] --> WaitInfo2([Wait_for_Routeing_Info]) + WaitInfo2 --> SendInfo + +``` + +Flowchart for Procedure Obtain\_Routeing\_Address. The process starts with 'Wait\_for\_Routeing\_Info', followed by 'Send Routeing Info negative response'. A decision 'If MT Roaming Retry is supported and MT Roaming Retry Indicator received?' follows. If 'Yes', it goes to 'Clear RoamingRetry Supported IE', 'Send Routeing Info', and 'Wait\_for\_Routeing\_Info'. If 'No', it checks 'Call Released?'. If 'Yes', 'Result:= Aborted'. If 'No', it goes to 'SCUDIF negative SRI response handling' (See TS 23.172). Both lead to a 'Result' triangle. From 'Result', 'Pass' leads to connector '4', 'Fail' leads to 'OR Handle\_SRI Negative\_Response (Own PLMN)' (See TS 23.079). From 'OR Handle\_SRI Negative\_Response (Own PLMN)', 'Result= Pass?' follows. If 'Yes', 'Result:=Pass' leads to a connector. If 'No', 'Error= Unknown subscriber?' follows. If 'Yes', it goes to 'MOBILE NUMBER PORTABILITY\_IN\_QoHR' (See TS 23.066). If 'No', 'Result= Number ported?' follows. If 'Yes', 'Routeing address:= routeing number' and 'Result:= Routeing number' lead to a connector. If 'No', 'Result:=Fail' leads to a connector. A 'Retry Send Routeing Info' block also leads to 'Wait\_for\_Routeing\_Info'. + +###### **Figure 4c: Information flow for a mobile terminating roaming forwarding call after successful Retrieval of Routeing Information** + +The sequence follows the normal MT terminating call with the following differences: + +1. If the Location Update Request contains a valid TMSI/old LAI (e.g. not after the old VLR restart), a new MSC/VLR supporting the MTRF feature may include the MTRF Supported flag and the new MSC/VLR numbers in the MAP Send Identification to the old VMSC. + +The new VLR shall not include the MTRF Supported flag in the MAP Send Identification message sent to the old VMSC if the Location Update message received from the MS indicates a CS fallback mobile originating call. + +An old VLR supporting the MTRF feature may indicate in the MAP Send Identification response sent to the new VLR whether there is a pending mobile terminating call at the old VLR. + +NOTE 2: it is implementation dependent if the new VLR decides to not include the MTRF Supported flag in the MAP Send Identification message sent to the old VMSC if the Location Update message received from the MS contains the "follow-on request pending" flag. + +2. A new MSC/VLR supporting the MTRF feature includes the MTRF Supported flag in the MAP Update Location message sent to the HLR, unless the Location Update message received from the MS indicates a CS fallback mobile originating call. + +NOTE 3: it is implementation dependent if the new VLR decides to not include the MTRF Supported flag in the MAP Update Location message sent to the HLR if the Location Update message received from the MS contains the "follow-on request pending" flag. + +3. Upon receipt of a MAP Update Location including the MTRF Supported flag, an HLR supporting the MTRF feature decides whether to authorise MTRF call between the old and the new MSCs based on roaming agreements with the old and the new MSCs. If MTRF is authorised, the HLR includes the MTRF Supported And Authorized flag and the new MSC/VLR numbers in the MAP Cancel Location message sent to the old VLR. If MTRF is not authorised, the HLR includes the MTRF Supported And Not Authorized flag in the MAP Cancel Location message sent to the old VLR. +4. Upon receipt of a MAP Cancel Location message while on-going paging and if it includes the MTRF Supported And Authorized flag or if the MAP Cancel Location message does include neither the MTRF Supported And Authorized flag nor the MTRF Supported And Not Authorized flag but the old MSC/VLR had received earlier the MTRF Supported flag at step 1, the old MSC/VLR stops paging. +5. If it supports MTRF and decides to apply MTRF based on local operator policy and optionally roaming agreements with the HLR and new MSC for MTRF, it sends a MAP Provide Roaming Number request (including the MTRF Indicator and the parameters received from the HLR in the MAP Provide Roaming Number) to the new terminating VLR. + +If the the MAP Cancel Location message does not include the MTRF Supported And Authorized flag and it did not receive the MTRF Supported flag at step 1 or if the MAP Cancel Location message includes the MTRF Supported And Not Authorized flag, the old MSC/VLR may initiate the MT Roaming Retry procedure as per subclause 5.2.1. + +If the old MSC supports both the MT Roaming Retry and the MT Roaming Forwarding procedures, and if the conditions for using these procedures are met, the MSC can decide based on operator policy which procedure to follow. + +6. Upon receipt of the MAP Provide Roaming Number Request, the new MSC/VLR may check roaming agreements with the HLR and the old MSC for MTRF. + +The new MSC/VLR may reject the MAP Provide Roaming Number Request with a cause indicating that the subscriber is busy if it has received from the MS a CM Service Request indicating a CS mobile originated call. + +If the new VLR rejects the MTRF request, the new VLR returns a negative response to the old VLR. + +As an option, the new MSC/VLR may check whether it also performs the GMSC function for the call by comparing the GMSC address received in the MAP Provide Roaming Number with its own MSC address. If so, + +the GMSC / new MSC/VLR may proceed as shown in figure 4ca to deliver the MT call directly to the UE without further involving the old MSC/VLR. + +7. If the new VLR accepts the MAP Provide Roaming Number request, upon successful completion of the MAP Update Location procedure with the HLR, the new MSC/VLR allocates an MSRN to allow the call to be routed from the old MSC to the new MSC. As an implementation option, the new MSC/VLR may allocate an MSRN before completion of the MAP Update Location procedure with the HLR. +8. The new MSC/VLR sends MSRN to the old VLR within the MAP Provide Roaming Number response. + +Upon receipt of the MSRN from the new MSC/VLR, the old MSC/VLR terminates any on-going Camel transaction. + +9. Receipt of the MSRN from the new MSC/VLR enables the old MSC to relay the call towards the new MSC. +10. If the IAM message is received before the Location Update procedure is completed with the MS, the new MSC may delay the setup of the call until the completion of the Location Update procedure or start at once the normal terminating call procedure. In the former case, if the Location Update is received with the "follow-on" indication and if the MSC supports the "follow-on" indication, the incoming IAM may either be handled as a waiting call or forwarded as Busy (CFB), depending on the state of the "follow-on" call and the subscriber's subscription data. + +The Location Update Accept message may be sent to the MS at any time after receipt of the MAP Update Location Ack from the HLR, i.e. the location update procedure with the MS is not affected by the MT Roaming Forwarding procedure. + +If no MAP Provide Roaming Number request has been received at the time the Location Update procedure completes, the new MSC may shortly defer the release of the signalling connection with the MS if the old VLR indicated in the MAP Send Identification response that there is a pending mobile terminating call at the old VLR. + +- NOTE 4: For a CS Fallback mobile terminating call, the new MSC also defers the release of the signalling connection with the MS if the MS includes the "CSMT" flag in the Location Update message (see subclause 7.5a of 3GPP TS 23.272 [42]). + +The MAP Update Location message and Send Identification message may include the new LMSI allocated by the new terminating MSC/VLR if the MTRF Supported flag is present in those messages. If available, the HLR shall include the new LMSI in the MAP Cancel Location message it sends to the old VLR if the MTRF Supported And Authorized flag is present in this message. If available, the old VLR shall include the new LMSI in the MAP Provide Roaming Number message it sends to the new VLR. + +A VLR may also set the MTRF Supported flag in the MAP Update Location message it sends to the HLR upon establishment of an SGs association (see 3GPP TS 23.272 [42]). This enables in particular mobile terminating roaming forwarding calls during the mobile terminated CS service delivery via an alternative MME in MME pool procedure when the new SGs association is established towards a new VLR (see clause 26 of 3GPP TS 23.007 [43]). + +The information flow for mobile terminating roaming forwarding (MTRF) call if the GMSC and the new MSC/VLR are the same node and if they support the option (in step 6) to deliver the MT call directly to the UE without further involving the old MSC/VLR is shown in figure 4ca. + +![Sequence diagram showing information flow for a mobile terminating roaming forwarding call. Lifelines: GMSC, New MSC/VLR, HLR, Old MSC/VLR, MS. The diagram is divided into two main parts by a dashed line. The top part shows steps 1 to 5 of the MTRF scenario. The bottom part shows steps 3 to 6, with some steps being blue text indicating modifications or specific actions. The sequence ends with 'Normal MT call procedure follows.'](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant NewMSCVLR as New MSC/VLR + participant HLR + participant OldMSCVLR as Old MSC/VLR + participant MS + + Note left of GMSC: 1. SRI (B, GMSC@, Call Ref.) + GMSC->>HLR: 1. SRI (B, GMSC@, Call Ref.) + HLR->>OldMSCVLR: PRN (GMSC@, Call Ref.) + OldMSCVLR->>HLR: PRN ACK (MSRN) + HLR->>NewMSCVLR: SRI ACK + NewMSCVLR->>GMSC: IAM (MSRN) + OldMSCVLR->>MS: Paging + MS->>OldMSCVLR: Location Update + OldMSCVLR->>NewMSCVLR: Location Update + + Note right of OldMSCVLR: 2. Steps 1 to 5 of MTRF scenario as per figure 4c + + Note left of NewMSCVLR: 3. PRN (MTRF Indicator, old MSC number, GMSC@, Call Ref.) + NewMSCVLR->>OldMSCVLR: 3. PRN (MTRF Indicator, old MSC number, GMSC@, Call Ref.) + OldMSCVLR->>NewMSCVLR: Insert Subscriber Data (continued) + NewMSCVLR->>OldMSCVLR: Update Location Ack + OldMSCVLR->>NewMSCVLR: Perform MTRF Optimal Routing + NewMSCVLR->>OldMSCVLR: 4. Release + OldMSCVLR->>NewMSCVLR: Release Complete + + Note left of NewMSCVLR: 5. New MSC/VLR closes the MAP dialogue locally. + NewMSCVLR->>OldMSCVLR: 5. MAP Abort + OldMSCVLR->>NewMSCVLR: Complete MTRF Optimal Routing + + Note left of NewMSCVLR: 6. New MSC/VLR delays setup until location update finishes. + NewMSCVLR->>OldMSCVLR: Location Update Accept + OldMSCVLR->>MS: TMSI Reallocation Complete + OldMSCVLR->>NewMSCVLR: Setup + NewMSCVLR->>MS: Call Confirmed + + Note right of OldMSCVLR: Further procedures related to location update. E.g. ciphering, TMSI reallocation. + + Note right of OldMSCVLR: Normal MT call procedure follows. + +``` + +Sequence diagram showing information flow for a mobile terminating roaming forwarding call. Lifelines: GMSC, New MSC/VLR, HLR, Old MSC/VLR, MS. The diagram is divided into two main parts by a dashed line. The top part shows steps 1 to 5 of the MTRF scenario. The bottom part shows steps 3 to 6, with some steps being blue text indicating modifications or specific actions. The sequence ends with 'Normal MT call procedure follows.' + +**Figure 4ca : Information flow for a mobile terminating roaming forwarding call after successful Retrieval of Routeing Information with MTRF Optimal Routing when the GMSC and the new MSC/VLR are the same node** + +The sequence follows the normal flow for MTRF call after successful Retrieval of Routeing Information (as specified in figure 4c) with the following differences: + +1. The GMSC shall include the GMSC address and the Call reference number used by the GMSC for this call in the MAP Send Routing Information . The HLR shall include these parameters in the MAP Provide Roaming Number if received in the MAP Send Routing Information. +2. Steps 1 to 5 as specified for figure 4c. +3. The new MSC/VLR shall determine that it also performs the GMSC function for the call identified by the Call Reference Number if the GMSC address received in the MAP Provide Roaming Number matches its own MSC address. +4. In that case, the GMSC shall send a Release message to the old MSC/VLR. Upon receipt of this message, the old MSC/VLR shall return a Release Complete message to the GMSC. +5. The new MSC/VLR shall close the MAP Dialogue (initiated in step 3) locally (i.e. MAP-Close service with the release method set to "pre-arranged end"). Alternatively, the new MSC/VLR may send a MAP Abort message to the old MSC/VLR after receiving the Release Complete message. The old MSC/VLR shall release all resources associated to the call (if not already done at step 4). + +NOTE 5: The MAP Abort message is sent after receipt of the Release Complete message to avoid the old MSC/VLR initiating a Release procedure towards the GMSC or invoking Call Forwarding upon receipt of the MAP Abort message.6. The new MSC/VLR shall then proceed with the establishment of the MT call without further involving the old MSC/VLR. + +NOTE 6: The internal messages between the GMSC and the new MSC/VLR are implementation specific and not further described in 3GPP specifications. + +### 5.2.4 Mobile Terminating Roaming Forwarding Call during Retrieval of Routeing Information + +The information flow for mobile terminating roaming forwarding (MTRF) call during retrieval of routeing information is shown in figure 4d. It applies to a mobile terminating call while the called mobile is simultaneously moving from an old to a new MSC, if the old and the new terminating MSC/VLRs support the MT Roaming Forwarding procedure. The HLR should also support the Mobile Terminating Roaming Forwarding procedure in order to ensure that roaming forwarding can be offered in all scenarios (e.g. in case of IMSI in the LAU Request from UE); an HLR that supports Optimal Routeing shall support the requirements defined in this clause to ensure that charging requirements for optimal routeing are never contravened. The procedure may e.g. apply during pre-paging if the GMSC, HLR and old MSC/VLR support pre-paging. + +The principles and requirements specified for MT Roaming Forwarding Call after successful Retrieval of Routeing Information (see clause 5.2.3) shall also apply for MT Roaming Forwarding Call during Retrieval of Routeing Information with the following modifications or clarifications. + +When an MSRN is retrieved successfully from the new MSC/VLR, the old MSC/VLR shall return the received MSRN within the MAP Provide Roaming Number response to the HLR, which allows the call to be routed from the GMSC to the new MSC. + +![Sequence diagram showing information flow for a mobile terminating roaming forwarding call during Retrieval of Routeing Information. The diagram involves five main entities: GMSC, HLR, Old MSC/VLR, New MSC/VLR, and MS. The sequence starts with SRI (B) from GMSC to HLR, followed by PRN from HLR to Old MSC/VLR. The Old MSC/VLR sends Pre-Paging to MS and step 1: Send Identification (MTRF supported, new MSC/VLR numbers) to New MSC/VLR. The New MSC/VLR performs an Authentication Procedure with MS. Step 2: Update Location (MTRF Supported) is sent from New MSC/VLR to HLR. Step 3: Cancel Location (MTRF Supported And Authorized, new MSC/VLR numbers) is sent from HLR to Old MSC/VLR, which responds with Cancel Location Ack. Step 4: Old MSC stops pre-paging timer. Insert Subscriber Data (multiple) is sent from HLR to New MSC/VLR. A decision box 5 states: If HLR authorizes MTRF feature then use new MSC/VLR numbers to trigger sending of PRN req to new VLR. Step 6: PRN (MTRF Indicator, old MSC Number) is sent from New MSC/VLR to HLR. Insert Subscriber Data (continued) and Update Location Ack are sent from HLR to New MSC/VLR. A decision box 7 states: After Update Location Ack is received, the new VLR returns MSRN to the old VLR. Step 8: PRN Ack (MSRN, VMSC Address) is sent from New MSC/VLR to HLR. Step 9: PRN Ack (MSRN, VMSC Address) is sent from HLR to GMSC, followed by IAM (MSRN). Step 10: SRI Ack (MSRN, VMSC Address) is sent from GMSC to HLR. A decision box 11 states: New MSC/VLR may delay setup until location update finishes. The final part shows the Normal MT call procedure: Location Update, TMSI realloc, Cmplt, SETUP, and Call Confirmed between New MSC/VLR and MS.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant HLR + participant OldMSC as Old MSC/VLR + participant NewMSC as New MSC/VLR + participant MS + + GMSC->>HLR: SRI (B) + HLR->>OldMSC: PRN + OldMSC->>MS: Pre-Paging + OldMSC->>NewMSC: 1. Send Identification (MTRF supported, new MSC/VLR numbers) + NewMSC->>MS: Authentication Procedure + NewMSC->>HLR: 2. Update Location (MTRF Supported) + HLR->>OldMSC: 3. Cancel Location (MTRF Supported And Authorized, new MSC/VLR numbers) + OldMSC->>HLR: Cancel Location Ack + Note over OldMSC: 4. Old MSC stops pre-paging timer + HLR->>NewMSC: Insert Subscriber Data (multiple) + Note over HLR,NewMSC: 5. If HLR authorizes MTRF feature then use new MSC/VLR numbers to trigger sending of PRN req to new VLR + NewMSC->>HLR: 6. PRN (MTRF Indicator, old MSC Number) + HLR->>NewMSC: Insert Subscriber Data (continued) + HLR->>NewMSC: Update Location Ack + Note over NewMSC: 7. After Update Location Ack is received, the new VLR returns MSRN to the old VLR. + NewMSC->>HLR: 8. PRN Ack (MSRN, VMSC Address) + HLR->>GMSC: 9. PRN Ack (MSRN, VMSC Address) + GMSC->>HLR: 10. SRI Ack (MSRN, VMSC Address) + HLR->>GMSC: IAM (MSRN) + Note over NewMSC: 11. New MSC/VLR may delay setup until location update finishes + NewMSC->>MS: Location Update + NewMSC->>MS: TMSI realloc + MS->>NewMSC: Cmplt + NewMSC->>MS: SETUP + MS->>NewMSC: Call Confirmed + Note over NewMSC,MS: Normal MT call procedure follows + +``` + +Sequence diagram showing information flow for a mobile terminating roaming forwarding call during Retrieval of Routeing Information. The diagram involves five main entities: GMSC, HLR, Old MSC/VLR, New MSC/VLR, and MS. The sequence starts with SRI (B) from GMSC to HLR, followed by PRN from HLR to Old MSC/VLR. The Old MSC/VLR sends Pre-Paging to MS and step 1: Send Identification (MTRF supported, new MSC/VLR numbers) to New MSC/VLR. The New MSC/VLR performs an Authentication Procedure with MS. Step 2: Update Location (MTRF Supported) is sent from New MSC/VLR to HLR. Step 3: Cancel Location (MTRF Supported And Authorized, new MSC/VLR numbers) is sent from HLR to Old MSC/VLR, which responds with Cancel Location Ack. Step 4: Old MSC stops pre-paging timer. Insert Subscriber Data (multiple) is sent from HLR to New MSC/VLR. A decision box 5 states: If HLR authorizes MTRF feature then use new MSC/VLR numbers to trigger sending of PRN req to new VLR. Step 6: PRN (MTRF Indicator, old MSC Number) is sent from New MSC/VLR to HLR. Insert Subscriber Data (continued) and Update Location Ack are sent from HLR to New MSC/VLR. A decision box 7 states: After Update Location Ack is received, the new VLR returns MSRN to the old VLR. Step 8: PRN Ack (MSRN, VMSC Address) is sent from New MSC/VLR to HLR. Step 9: PRN Ack (MSRN, VMSC Address) is sent from HLR to GMSC, followed by IAM (MSRN). Step 10: SRI Ack (MSRN, VMSC Address) is sent from GMSC to HLR. A decision box 11 states: New MSC/VLR may delay setup until location update finishes. The final part shows the Normal MT call procedure: Location Update, TMSI realloc, Cmplt, SETUP, and Call Confirmed between New MSC/VLR and MS. + +**Figure 4d: Information flow for a mobile terminating roaming forwarding call during Retrieval of Routeing Information** + +The sequence follows the normal MT terminating call with the following differences: + +- 1-2. Same as steps 1 and step 2 in figure 4c. +3. Same as step 3 in figure 4c, with the addition that the HLR shall not authorise MTRF between the old and the new MSCs if routing the call between the GMSC and the new MSC contravenes charging requirements if Optimal Routeing is supported (see 3GPP TS 23.079[13]). +4. Same as step 4 in figure 4c, where the old MSC/VLR stops pre-paging. +5. Same as step 5 in figure 4c. +6. Same as step 6 in figure 4c. If the OR interrogation indicator is received in the PRN request, the new VLR shall return a PRN negative response if it does not support Optimal Routeing (see 3GPP TS 23.079 [13]). +7. Same as step 7 in figure 4c. + +8. The new MSC/VLR returns to the old VLR a MAP Providing Roaming Number response including the MSRN, the new VMSC Address, and if the new MSC/VLR supports the MAP Release Resource procedure, the ReleaseResourcesSupported flag. +9. Upon receipt of the MSRN from the new VLR, the old VLR returns the PRN Ack to the HLR including the MSRN and the VMSC Address received from the new VLR, and the ReleaseResourcesSupported flag if received from the new MSC/VLR. +10. If the HLR needs to return the VMSC Address to the GMSC (as per the conditions specified in 3GPP TS 29.002 [29]), and if a VMSC Address was received with an MSRN in the PRN Ack, the HLR shall pass in the SRI ack to the GMSC the MSRN and the VMSC Address received in the PRN ack. +Receipt of the MSRN from the HLR enables the GMSC to relay the call towards the new MSC. +11. Same as step 10 in figure 4c. + +## 5.3 Information flow for an MT call + +An example information flow for an MT call is shown in figure 5; many variations are possible. ISUP signalling between GMSCB and VMSCB is shown by solid lines; signalling over the B interface between VMSCB and VLRB is shown by chain lines; signalling over the Iu interface (for UMTS) or the A interface (for GSM) between VMSCB and BSSB is shown by dashed lines; and signalling over the radio interface between VMSCB or BSSB and MSB is shown by dotted lines. + +![Flowchart for Procedure Obtain_Routeing_Address. It starts at connector 5, goes to a 'Result=Fail' decision. If 'Yes', it goes to 'Result:= Fail' and then to an error connector. If 'No', it goes to a 'Result' decision. From 'Result', 'CAMEL_FTN' leads to 'Continue' and connector 2, while 'GSM_FTN' leads to 'CAMEL_MT_GMSC_Notify_CF' (referencing TS 23.078). From 'CAMEL_MT_GMSC_Notify_CF', it goes to another 'Result' decision. From this 'Result', 'Fail' leads to 'Result:= Fail' and the error connector, while 'Reconnect' leads to 'Reconnect:= True' and connector 1. A 'SCUDIF_Check_Service_Compatibility' block (referencing TS 23.172) is shown as an alternative path from the first 'Result' decision.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +**Procedure Obtain\_Routeing\_Address** ORA5(6) + +Procedure in a GMSC +to determine the address +to which a call should be routed + +``` + +graph TD + 5((5)) --> R1{Result=Fail} + R1 -- Yes --> RF[Result:= Fail] + RF --> E((X)) + R1 -- No --> R2{Result} + R2 -- CAMEL_FTN --> C[Continue] + C --> 2((2)) + R2 -- GSM_FTN --> CMN[CAMEL_MT_GMSC_Notify_CF] + CMN -.-> TS23078[See TS 23.078] + CMN --> R3{Result} + R3 -- Fail --> RF + R3 -- Reconnect --> RT[Reconnect:= True] + RT --> 1((1)) + R2 -.-> SC[SCUDIF_Check_Service_Compatibility] + SC -.-> TS23172[See TS 23.172] + +``` + +Flowchart for Procedure Obtain\_Routeing\_Address. It starts at connector 5, goes to a 'Result=Fail' decision. If 'Yes', it goes to 'Result:= Fail' and then to an error connector. If 'No', it goes to a 'Result' decision. From 'Result', 'CAMEL\_FTN' leads to 'Continue' and connector 2, while 'GSM\_FTN' leads to 'CAMEL\_MT\_GMSC\_Notify\_CF' (referencing TS 23.078). From 'CAMEL\_MT\_GMSC\_Notify\_CF', it goes to another 'Result' decision. From this 'Result', 'Fail' leads to 'Result:= Fail' and the error connector, while 'Reconnect' leads to 'Reconnect:= True' and connector 1. A 'SCUDIF\_Check\_Service\_Compatibility' block (referencing TS 23.172) is shown as an alternative path from the first 'Result' decision. + +- NOTE 1: Security procedures may be initiated at any stage after the network has accepted the page response; the position in this message flow diagram is an example. +- NOTE 2: If Security procedures are not required, the MSC may send a Start security procedures message indicating that no ciphering is required. +- NOTE 3: This message flow diagram assumes that the MS has already been authenticated on location registration. If this is not so (for the first MT call after VLR restoration), the network may initiate authentication after the MS responds to paging. +- NOTE 4: The network may request the IMEI from the MS, and may check the IMEI, at any stage after the MS responds to paging, either as part of the procedure to start security procedures or explicitly after security procedures have been started; this is not shown in this message flow diagram. +- NOTE 5: If a connection between MSCB and MSB has been established as a result of pre-paging, the paging procedure is not performed. +- NOTE 6: If a connection between MSCB and MSB has been established as a result of pre-paging, VLRB sends the Call arrived message to MSCB to stop the guard timer for the release of the radio connection. + +**Figure 5: Information flow for a basic mobile terminated call** + +When VMSCB receives an IAM from GMSCB it sends to VLRB a request for information to handle the incoming call, using a Send Info For Incoming Call (SIFIC) message containing the roaming number received in the IAM. + +If VLRB recognizes the roaming number, and MSB is allowed service, it sends a request to VMSCB to page MSB. If a radio connection between the network and MSB is already established, VMSCB responds immediately to the page request. If no radio connection exists, VMSCB sends a page request to BSSB, and BSSB broadcasts the page on the paging channel. If VPLMNB supports GPRS and the Gs interface between VLRB and the SGSN is implemented (see 3GPP TS 23.060 [9]) and there is a valid association between VLRB and the SGSN for the MS, the paging signal towards the MS goes from VMSCB via VLRB and the SGSN to the BSS. + +If MSB detects the page, it sends a channel request to BSSB, which responds with an immediate assignment command, to instruct MSB to use the specified signalling channel. MSB then sends a page response on the signalling channel; BSSB relays this to VMSCB. VMSCB sends a Process access request message to VLRB to indicate that MSB has responded to paging. VLRB may then initiate authentication, as described in 3GPP TS 33.102 [32] for UMTS and 3GPP TS 43.020 [1] for GSM. VLRB may also initiate security procedures at this stage, as described in 3GPP TS 33.102 [32] for UMTS and 3GPP TS 43.020 [1] for GSM. + +If the MS is paged in a CSG cell, VLRB shall control if the CSG cell is allowed by the CSG subscription data stored in VLRB. If the CSG cell is not allowed, VLRB shall reject the the Process Access Request. + +If the MS is paged in a hybrid cell, VLRA shall set the CSG membership status in the Process Access Request ack according to the CSG subscription data stored in VLRA. + +VLRB may restore CSG data from CSS for a MT call after a VLRB restart. + +If VLRB determines that MSB is allowed service, it sends a Process access request ack to VMSCB. The Process access request ack message triggers a Start security procedures message towards BSSB; if VMSCB has not received a Start security procedures message from VLRB, the Start security procedures message indicates no ciphering. + +VLRB then sends a Complete call message to VMSCB. VMSCB sends a Set-up message towards MSB. The Set-up message may include bearer capability information for the call. + +When MSB receives the Set-up message from BSSB, it responds with a Call confirmed message. The Call Confirmed message includes bearer capability information if any of the negotiable parameters of the bearer capability has to be changed. When VMSCB receives the Call confirmed message via BSSB, it sends an Allocate channel message to BSSB. BSSB instructs MSB to tune to a traffic channel by sending an Assignment command. When MSB has tuned to the specified traffic channel it responds with an Assignment complete, message, which BSSB relays to VMSCB as an Allocation complete, and sends an Alerting message to indicate that the called user is being alerted. VMSCB sends an ACM to GMSCB, which relays it to the originating exchange. + +When the called user answers, MSB sends a Connect message, which BSSB relays to VMSCB. VMSCB: + +- responds with a Connect ack message towards MSB; +- sends an ANM to GMSCB, which relays it to the originating exchange; +- sends a Complete call ack to VLRB. + +The network then waits for the call to be cleared. + +# --- 6 Principles for interactions with supplementary services + +This clause specifies the principles used to describe the invocation of the GSM or UMTS supplementary services which were standardized when the present document was drafted. Registration, erasure, activation, deactivation and interrogation are call-independent operations; they are therefore outside the scope of the present document. Descriptions may be found in the stage 2 specifications for each supplementary service. + +In the modelling used in the present document, each supplementary service which a network entity supports is managed by a supplementary service handler, which handles data in the entity in which it runs. The call handling processes defined in the present document use the data to define the contents of messages to other entities. The basic call handling processes defined in the present document interact with the supplementary service handlers as shown in the SDL diagrams and the supporting text. If a network entity does not support a supplementary service, it bypasses the + +interaction with the handler for that supplementary service. Exceptions to this general principle are described later in this clause. + +## 6.1 Call Deflection service (3GPP TS 23.072) + +The basic call handling processes ICH\_MSC and ICH\_VLR interact with the CD supplementary service (3GPP TS 23.072 [11]) as described in subclauses 7.3.1 and 7.3.2 respectively. + +## 6.2 Line identification services (3GPP TS 23.081) + +### 6.2.1 Calling Line Identification Presentation (CLIP) + +The basic call handling processes ICH\_VLR and ICH\_MSC interact with the processes CLIP\_MAF001 and CLIP\_MAF002 (3GPP TS 23.081 [14]) as described in subclauses 7.3.1 and 7.3.2. + +### 6.2.2 Calling Line Identification Restriction (CLIR) + +The basic call handling processes OCH\_MSC and OCH\_VLR interact with the processes CLIR\_MAF004 and CLIR\_MAF003 (3GPP TS 23.081 [14]) as described in subclauses 7.1.1 and 7.1.2. + +### 6.2.3 Connected Line Identification Presentation (COLP) + +The basic call handling processes OCH\_MSC and OCH\_VLR interact with the processes COLP\_MAF006 and COLP\_MAF005 (3GPP TS 23.081 [14]) as described in subclauses 7.1.1 and 7.1.2. + +The basic call handling processes MT\_GMSC and ICH\_MSC interact with the process COLP\_MAF039 (3GPP TS 23.081 [14]) as described in subclauses 7.2.1 and 7.3.1. + +### 6.2.4 Connected Line Identification Restriction (COLR) + +The basic call handling processes ICH\_VLR and ICH\_MSC interact with the processes COLR\_MAF040 and COLR\_MAF041 (3GPP TS 23.081 [14]) as described in subclauses 7.3.2 and 7.3.1. + +## 6.3 Call forwarding services (3GPP TS 23.082) + +### 6.3.1 Call Forwarding Unconditional (CFU) + +The basic call handling process SRI\_HLR interacts with the process MAF007 (3GPP TS 23.082 [15]) as described in subclause 7.2.2. + +### 6.3.2 Call Forwarding on mobile subscriber Busy (CFB) + +The basic call handling process ICH\_VLR interacts with the process MAF008 (3GPP TS 23.082 [15]) as described in subclause 7.3.2. + +### 6.3.3 Call Forwarding on No Reply (CFNRy) + +The basic call handling process ICH\_VLR interacts with the process MAF009 (3GPP TS 23.082 [15]) as described in subclause 7.3.2. + +### 6.3.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc) + +The basic call handling processes SRI\_HLR and ICH\_VLR interact with the process MAF010 (3GPP TS 23.082 [15]) as described in subclauses 7.2.2 and 7.3.2. + +## 6.4 Call wait (3GPP TS 23.083) + +The basic call handling process ICH\_VLR interacts with the process MAF013 (3GPP TS 23.083 [16]) as described in subclause 7.3.2. Further details of the handling of call waiting are given in subclauses 7.3.1 and 7.3.2. + +## 6.5 Call hold (3GPP TS 23.083) + +Invocation of call hold before a basic call has been established will be rejected. + +The basic call handling processes OCH\_MSC and ICH\_MSC interact with the procedures Process\_Hold\_Request and Process\_Retrieve\_Request as described in subclauses 7.1.1 and 7.3.1. + +## 6.6 Multiparty (3GPP TS 23.084) + +Invocation of multiparty before a basic call has been established will be rejected. + +## 6.7 Closed user group (3GPP TS 23.085) + +The basic call handling process OCH\_VLR interacts with the process CUG\_MAF014 (3GPP TS 23.085 [18]) as described in subclause 7.1.2. + +The basic call handling process SRI\_HLR interacts with the process CUG\_MAF015 (3GPP TS 23.085 [18]) as described in subclause 7.2.2. + +The interactions between call forwarding and CUG (3GPP TS 23.085 [18]) are handled as described in subclause 7.2.2.6. + +## 6.8 Advice of charge (3GPP TS 23.086) + +The interactions between Advice of Charge (3GPP TS 23.086 [19]) and MO calls are handled as described in subclauses 7.1.1 and 7.1.2. + +The interactions between Advice of Charge (3GPP TS 23.086 [19]) and MT calls are handled as described in subclauses 7.3.1 and 7.3.2. + +## 6.9 User-to-user signalling (3GPP TS 23.087) + +The basic call handling processes OCH\_MSC, OCH\_VLR, MT\_GMSC and ICH\_MSC interact with the UUS supplementary service as described in subclauses 7.1.1, 7.1.2, 7.2.1 and 7.3.1 respectively. + +## 6.10 Call barring (3GPP TS 23.088) + +### 6.10.1 Barring of outgoing calls + +The basic call handling process OCH\_VLR interacts with the processes MAF017, MAF018 and MAF020 (3GPP TS 23.088 [21]) as described in subclause 7.1.2. + +### 6.10.2 Barring of incoming calls + +The basic call handling process SRI\_HLR interacts with the processes MAF022, MAF023 and MAF024 (3GPP TS 23.088 [21]) as described in subclause 7.2.2. + +## 6.11 Explicit Call Transfer (3GPP TS 23.091) + +There is no interaction between Explicit Call Transfer and the basic call handling described in the present document. + +## 6.12 Completion of Calls to Busy Subscriber (3GPP TS 23.093) + +The basic call handling processes OCH\_MSC, OCH\_VLR, MT\_GMSC, SRI\_HLR, PRN\_VLR, ICH\_MSC and ICH\_VLR interact with the CCBS supplementary service as described in subclauses 7.1.1, 7.1.2, 7.2.1, 7.2.2, 7.2.3, 7.3.1 and 7.3.2 respectively. + +## 6.13 Multicall (3GPP TS 23.135) + +The basic call handling processes OCH\_MSC, OCH\_VLR, ICH\_MSC & ICH\_VLR interact with the Multicall supplementary service as described in subclauses 7.1.1, 7.1.2, 7.3.1 and 7.3.2 respectively. + +# 7 Functional requirements of network entities + +The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the SDL diagrams. + +The entities described in this clause interwork with other entities over four different types of interface: + +- The Iu interface, used to interwork between the MSC and the UTRAN or the UMTS UE; +- The A interface, used to interwork between the MSC and the GSM BSS or the GSM MS; +- The C, D & F interfaces, used to interwork between the MSC & HLR (C), VLR & HLR (D) and MSC & EIR (F); +- Telephony signalling interfaces, used to interwork between an MSC and another exchange. + +The protocols used over the Iu interface are RANAP, which is specified in 3GPP TS 25.413 [27], for interworking with the UTRAN and DTAP, which is specified in 3GPP TS 24.008 [26], for interworking with the MS. + +The protocols used over the A interface are BSSMAP, which is specified in 3GPP TS 48.008 [2], for interworking with the BSS and DTAP, which is specified in 3GPP TS 24.008 [26], for interworking with the MS. + +The protocol used over the C, D & F interfaces is MAP, which is specified in 3GPP TS 29.002 [29]. + +For the purposes of the present document, the protocol used over telephony signalling interfaces is ISUP, which is specified in ITU-T Recommendations Q.761[33], Q.762 [34], Q.763 [35] and Q.764 [36]; other telephony signalling systems may be used instead. + +The present document shows the call handling application processes interworking with a protocol handler for each of the protocols listed above. Each protocol defines supervision timers. If a supervision timer expires before a distant entity responds to a signal, the handling is as defined in the appropriate protocol specification. In general, the protocol handler reports timer expiry to the application as an error condition or negative response. Where a timer is shown in the present document, therefore, it is an **application** timer rather than a **protocol** timer. Interworking with the protocol handlers uses functional signal names which do not necessarily have a one-to-one correspondence with the names of messages used in the protocols. + +An MSC which receives an IAM from an originating exchange may react in three different ways: + +- It acts as a transit exchange, i.e. it relays the IAM to a destination exchange determined by analysis of the called party address, and thereafter relays other telephony signalling between the originating and destination exchange until the connection is released. This behaviour is not specific to UMTS or GSM; +- It acts as a terminating exchange, i.e. it attempts to connect the call to an MS currently registered in the service area of the MSC; +- It acts as a GMSC, i.e. it interrogates an HLR for information to route the call. If the HLR returns routeing information, the MSC uses the routeing information from the HLR to construct an IAM, which it sends to a destination exchange determined by analysis of the routeing information from the HLR. + +Annex A describes the method which the MSC uses to decide how to process the IAM. + +The SDL diagrams in this clause show the handling for a number of optional features and services. If the handling consists only of a call to a procedure specific to the feature or service, the procedure call is omitted if the entity does not support an optional feature or service. If the handling consists of more than a call to a procedure specific to the feature or service, the text associated with each SDL diagram specifies the handling which applies if the entity does not support an optional feature or service. For simplicity of description, it is assumed that support for Operator Determined Barring and the Call Forwarding and Call Barring supplementary services is mandatory. + +## 7.1 MO call + +### 7.1.1 Functional requirements of serving MSC + +#### 7.1.1.1 Process OCH\_MSC + +The variable TCH allocated is global data, accessible to the procedure Establish\_Originating\_TCH\_If\_Required. + +The procedures CCBS\_Report\_Not\_Idle and CCBS\_Check\_Last\_Call are specific to CCBS; they are specified in 3GPP TS 23.093 [23]. + +#### 7.1.1.2 Procedure Process\_Access\_Request\_MSC + +Sheet 1: the processing starting with the input signal "Send UESBI-Iu to Access Network" is specific to PUESBINE. If the MSC does not support PUESBINE, this signal will not be received. + +Sheet 1: the task "Convert IMEISV to UESBI" is defined in 3GPP TS 23.195 [25a]. + +Sheet 2: instead of using the explicit procedure Obtain\_IMEI\_MSC, the VMSC may encapsulate the request for the IMEI in the Start security procedures message; the BSS relays the response in the Security procedures complete message to the MSC. + +Sheet 2: the VMSC maps the negative response received on the B interface to the appropriate reject cause according to the rules defined in 3GPP TS 29.010 [31]. + +Sheet 2: The Start security procedures message may indicate one of several ciphering algorithms, or (for GSM only) no ciphering. + +Sheet 2, sheet 3: At any stage, the MS may terminate the transaction with the network by sending a CM service abort message. + +Sheet 2, sheet 3: if the VMSC receives a Set-up message from the MS while the access request is being handled, the message is saved for processing after the access request has been handled. + +#### 7.1.1.3 Procedure OG\_Call\_Setup\_MSC + +Sheet 1: the variables Alerting sent, MS connected and Reconnect are global data, accessible to the procedures CCBS\_Check\_OG\_Call, CCBS\_OCH\_Report\_Failure, CCBS\_OCH\_Report\_Success, CCBS\_Check\_If\_CCBS\_Possible, Send\_Alerting\_If\_Required and Send\_Access\_Connect\_If\_Required. + +Sheet 1: the variable UUS1 result sent is specific to UUS. This variable is accessible to all UUS specific procedures. + +Sheet 1: the procedure UUS\_OCH\_Check\_Setup is specific to UUS; it is specified in 3GPP TS 23.087 [20]. + +Sheet 1: the VMSC converts the PLMN bearer capability negotiated between the VMSC and the MS to a basic service according to the rules defined in 3GPP TS 27.001 [28]. + +Sheet 1: the procedure CAMEL\_N\_CSI\_CHECK\_MSC is specific to CAMEL Phase 3 or later, it is specified in 3GPP TS 23.078 [12]. + +Sheet 1: the procedure Check\_OG\_Multicall\_MSC is specific to Multicall; it is specified in 3GPP TS 23.135 [25]. If the VMSC does not support Multicall, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 1: the variable "On\_Hold" is used only if the VMSC supports Call Hold. + +Sheet 1, sheet 2, sheet 3, sheet 6: the procedure CCBS\_OCH\_Report\_Failure is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 1, sheet 2, sheet 6, sheet 7, sheet 9: at any stage after the Set-up has been received, the MS may terminate the transaction with the network by sending a Release transaction request. + +Sheet 2, sheet 3, sheet 4, sheet 5, sheet 6, sheet 7, sheet 8, sheet 9: signals are sent to and received from the process Subs\_FSM as described in subclause 7.4. + +Sheet 3: the procedure Set\_CLI\_Presentation\_Indicator\_MSC is specific to CLIR. If the VMSC does not support CLIR, processing continues from the "Yes" exit of the test "Result=Call allowed?". + +Sheet 3: the procedure CAMEL\_OCH\_MSC\_INIT is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 3: the procedure CAMEL\_MO\_Dialled\_Services is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 3 or later, processing continues from the "Pass" exit of the test "Result?". + +Sheet 3: the procedure CCBS\_Check\_OG\_Call is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. If the VMSC does not support CCBS, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 3: the procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_OQoD is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10]. + +Sheet 3: the procedure UUS\_OCH\_Set\_Info\_In\_IAM is specific to UUS; it is specified in 3GPP TS 23.087 [20]. + +Sheet 3: the procedure CAMEL\_Store\_Destination\_Address is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 3: the procedure CCBS\_OCH\_Report\_Success is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 3, sheet 5: the procedure CAMEL\_OCH\_LEG1\_MSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 4, sheet 7: the procedures CAMEL\_Start\_TNRy and CAMEL\_Stop\_TNRy are specific to CAMEL phase 2 or later; they are specified in 3GPP TS 23.078 [12]. + +Sheet 4: the task "UTU2Cnt := 0" is executed only if the VMSC supports UUS + +Sheet 4: the procedure CAMEL\_OCH\_MSC\_ALERTING is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 4 or later, processing continues from the "Pass" exit of the test "Result?". + +Sheet 5: the procedure CAMEL\_OCH\_MSC\_ANSWER is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 5: the procedure Set\_COLP\_Info\_MSC is specific to COLP. + +Sheet 5: the procedure Handle\_AoC\_MO\_MSC is specific to AoC. + +Sheet 5: the task "Store CW treatment indicator for this call if received in SII2" is executed only if the VMSC supports CAMEL phase 3 or later. + +Sheet 5: The process CAMEL\_OCH\_LEG2\_MSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 6: the procedures CCBS\_Check\_If\_CCBS\_Possible and CCBS\_Activation\_MSC are specific to CCBS; they are specified in 3GPP TS 23.093 [23]. The task "Store CCBS Result" is executed only if the VMSC supports CCBS. If the VMSC does not support CCBS, processing continues from the "CCBS Not Possible" exit of the test "CCBS Result". + +Sheet 6, sheet 7: the procedure CAMEL\_OCH\_MSC\_DISC3 is specific to CAMEL Phase 1; it is specified in 3GPP TS 23.078 [12]. + +Sheet 6, sheet 7: the procedure CAMEL\_OCH\_MSC\_DISC4 is specific to CAMEL Phase 2 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 6, sheet 6: the procedure CAMEL\_OCH\_MSC1 is specific to CAMEL phase 2 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 2 or later, processing continues from the "No" exit of the test "Result=Reconnect?". + +Sheet 6, sheet 7, sheet 9: the processing in the branch beginning with the Int\_Release\_Call input will occur only if the MSC supports CAMEL. + +Sheet 7, sheet 9: the procedure UUS\_MSC\_Check\_UUS1\_UUI is specific to UUS; it is specified in 3GPP TS 23.087 [20]. + +Sheet 8: the input signal TNRY expired and all the subsequent processing are specific to CAMEL phase 2 or later, and will occur only if the VMSC supports CAMEL phase 2 or later. The procedure CAMEL\_OCH\_MSC2 is specified in 3GPP TS 23.078 [12]. + +Sheet 8: the input signal User To User is specific to UUS; it is discarded if the VMSC does not support UUS. + +Sheet 8: the procedures UUS\_MSC\_Check\_UUS2\_UUI\_to\_MS and UUS\_MSC\_Check\_UUS2\_UUI\_to\_NW are specific to UUS; they are specified in 3GPP TS 23.087 [20]. + +Sheet 9: the procedure CAMEL\_OCH\_MSC\_DISC1 is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL, processing continues from the "No" exit of the test "Result=CAMEL handling?". + +Sheet 9: the procedure CAMEL\_OCH\_MSC\_DISC2 is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL, processing continues from the "No" exit of the test "Result=CAMEL handling?". + +Sheet 10: the procedure Process\_Hold\_Request is specific to Call Hold; it is specified in 3GPP TS 23.083[16]. + +Sheet 10: the procedure Process\_Retrieve\_request is specific to Call Hold; it is specified in 3GPP TS 23.083[16]. + +#### 7.1.1.4 Procedure Obtain\_IMSI\_MSC + +The MS may terminate the transaction with the network while the VMSC is waiting for the MS to return its IMSI. If a CC connection has not been established, the MS uses CM Service Abort; otherwise it uses a Release, Release Complete or Disconnect. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process. + +#### 7.1.1.5 Procedure Authenticate\_MSC + +The MS may terminate the transaction with the network while the VMSC is waiting for the MS to respond to an authentication request. If a CC connection has not been established, the MS uses CM Service Abort; otherwise it uses a Release, Release Complete or Disconnect. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process. + +#### 7.1.1.6 Procedure Obtain\_IMEI\_MSC + +The Send IMEI request to the MS specifies the IMEISV as the requested identity. + +The MS may terminate the transaction with the network while the VMSC is waiting for the MS to return its IMEI. If a CC connection has not been established, the MS uses CM Service Abort; otherwise it uses a Release, Release Complete or Disconnect. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process. + +#### 7.1.1.7 Procedure Check\_IMEI\_MSC + +The MS may terminate the transaction with the network while the VMSC is waiting for the MS to return its IMEI. If a CC connection has not been established, the MS uses CM Service Abort; otherwise it uses a Release, Release Complete or Disconnect. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process. + +The MS may terminate the transaction with the network while the VMSC is waiting for the result of the IMEI check from the EIR. If a CC connection has not been established, the MS uses CM Service Abort; otherwise it uses a Release, Release Complete or Disconnect. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process. + +#### 7.1.1.8 Procedure Establish\_Originating\_TCH\_If\_Required + +#### 7.1.1.9 Procedure Set\_CLI\_Presentation\_Indicator\_MSC + +The MS may terminate the transaction with the network by sending a Release transaction message while a response is awaited from the process CLIR\_MAF004. The message is saved for processing after return from the procedure. + +#### 7.1.1.10 Procedure Send\_Alerting\_If\_Required + +The test "Backward call indicator=no indication" refers to the called party's status field in the backward call indicators parameter of the ISUP Address Complete message which triggered the call of the procedure Send\_Alerting\_If\_Required. + +The procedures UUS\_MSC\_Check\_UUS1\_UUI and UUS\_OCH\_Set\_Alert\_And\_Connect\_Param are specific to UUS; they are specified in 3GPP TS 23.087 [20]. If the VMSC does not support UUS, processing continues from the "Yes" exit of the test "Result=Pass?". + +If no useful information would be carried in the Progress message, it is not sent. + +#### 7.1.1.11 Procedure Set\_COLP\_Info\_MSC + +The MS may terminate the transaction with the network by sending a Release transaction message while a response is awaited from the process COLP\_MAF006. The message is saved for processing after return from the procedure. + +#### 7.1.1.12 Procedure Send\_Access\_Connect\_If\_Required + +The test "Acknowledgement required" refers to the result returned by the procedure Handle\_AoC\_MSC. If the VMSC does not support AoC, processing continues from the "No" exit of the test "Acknowledgement required". + +The procedure UUS\_OCH\_Set\_Alert\_And\_Connect\_Param is specific to UUS, it is specified in 3GPP TS 23.087 [20]. If the VMSC does not support UUS, processing continues from the "Yes" exit of the test "Result=Pass?". + +If no useful information would be carried in the Facility message, it is not sent. + +#### 7.1.1.13 Procedure Handle\_AoC\_MO\_MSC + +The charging parameters and the Boolean variable Acknowledgement required are global data which can be read by the parent process. + +#### 7.1.1.14 Procedure TCH\_Check + +![Flowchart for Procedure Obtain_Routeing_Address. It starts with a connector '2', followed by 'BOR:=OR', 'Activate CF_Process', and a 'Result?' decision. If 'Fail', it goes to 'Release' and 'Result:= Aborted'. If 'Release', it goes to 'Release'. If 'Pass', it goes to 'CCBS_MT_GMSC_Remove_Indicators_Store_FWT' (See TS 23.093), then 'Route_Permitted (OR,FTN, Reference Address)' (See TS 23.079). A 'Route permitted' decision follows. If 'False', it goes to a merge point, then a 'CAMEL phase 2 or higher supported?' decision. If 'No', it goes to 'CAMEL_MT_GMSC_DISC3' (See TS 23.078). If 'Yes', it goes to 'CAMEL_MT_GMSC_DISC4' (See TS 23.078). Both lead to 'CF cancelled' (To process MT_CF_MSC). If 'True' from 'Route permitted', it goes to 'Routeing address:= FTN', 'Destination address:= FTN', 'OR:=True', and 'Result:= Forward'. Both 'CF cancelled' and 'Result:= Forward' lead to exit connectors.](f5deee2f3301ee351c4008283ffafbb3_img.jpg) + +**Procedure Obtain\_Routeing\_Address** ORA6(6) + +*Procedure in a GMSC to determine the address to which a call should be routed* + +``` +graph TD; Start((2)) --> BOR["BOR:=OR"]; BOR --> Activate["Activate CF_Process"]; Activate --> Result{"Result?"}; Result -- Fail --> Release1{{Release}}; Release1 --> ResultAborted["Result:= Aborted"]; ResultAborted --> Exit1((X)); Result -- Release --> Release2{{Release}}; Release2 --> Release2; Result -- Pass --> CCBS["CCBS_MT_GMSC_Remove_Indicators_Store_FWT"]; CCBS -.-> TS23093["See TS 23.093"]; CCBS --> RoutePerm["Route_Permitted (OR,FTN, Reference Address)"]; RoutePerm -.-> TS23079["See TS 23.079"]; RoutePerm --> RoutePermitted{"Route permitted"}; RoutePermitted -- True --> RA1["Routeing address:= FTN"]; RA1 --> DA1["Destination address:= FTN"]; DA1 --> OR1["OR:=True"]; OR1 --> ResultForward["Result:= Forward"]; ResultForward --> Exit2((X)); RoutePermitted -- False --> Merge{ }; Merge --> CAMELPhase{"CAMEL phase 2 or higher supported?"}; CAMELPhase -- No --> CAMEL3["CAMEL_MT_GMSC_DISC3"]; CAMEL3 -.-> TS23078_1["See TS 23.078"]; CAMELPhase -- Yes --> CAMEL4["CAMEL_MT_GMSC_DISC4"]; CAMEL4 -.-> TS23078_2["See TS 23.078"]; CAMEL3 --> CFCancelled{{CF cancelled}}; CAMEL4 --> CFCancelled; CFCancelled -.-> ToProcess["To process MT_CF_MSC"]; CFCancelled --> RA2["Routeing address:= Reference address"]; RA2 --> DA2["Destination address:= Reference address"]; DA2 --> OR2["OR:=False"]; OR2 --> ResultPass["Result:= Pass"]; ResultPass --> Exit3((X)); +``` + +Flowchart for Procedure Obtain\_Routeing\_Address. It starts with a connector '2', followed by 'BOR:=OR', 'Activate CF\_Process', and a 'Result?' decision. If 'Fail', it goes to 'Release' and 'Result:= Aborted'. If 'Release', it goes to 'Release'. If 'Pass', it goes to 'CCBS\_MT\_GMSC\_Remove\_Indicators\_Store\_FWT' (See TS 23.093), then 'Route\_Permitted (OR,FTN, Reference Address)' (See TS 23.079). A 'Route permitted' decision follows. If 'False', it goes to a merge point, then a 'CAMEL phase 2 or higher supported?' decision. If 'No', it goes to 'CAMEL\_MT\_GMSC\_DISC3' (See TS 23.078). If 'Yes', it goes to 'CAMEL\_MT\_GMSC\_DISC4' (See TS 23.078). Both lead to 'CF cancelled' (To process MT\_CF\_MSC). If 'True' from 'Route permitted', it goes to 'Routeing address:= FTN', 'Destination address:= FTN', 'OR:=True', and 'Result:= Forward'. Both 'CF cancelled' and 'Result:= Forward' lead to exit connectors. + +Figure 6: Process OCH\_MSC + +![Flowchart for Procedure Send_ACM_If_Required. It starts with a connector symbol, followed by a decision 'ACM sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to another decision 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Address Complete', then 'ACM sent := True', and finally to an exit connector. Arrows pointing left indicate signals to the originating exchange.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +### Procedure Send\_ACM\_If\_Required + +SACMIR1(1) + +Procedure to send an Address Complete Message to the preceding exchange if one is required for this call + +Signals to the left are to the originating exchange + +``` +graph TD; Start([ ]) --> ACM_Sent{ACM sent}; ACM_Sent -- True --> Call_Progress{{Call Progress}}; ACM_Sent -- False --> Network_Connect_Sent{Network connect sent}; Network_Connect_Sent -- True --> Call_Progress; Network_Connect_Sent -- False --> Address_Complete{{Address Complete}}; Address_Complete --> ACM_Set_True[ACM sent := True]; ACM_Set_True --> End(( )); Call_Progress --> End; style Start fill:none,stroke:none; style End fill:none,stroke:none; +``` + +Flowchart for Procedure Send\_ACM\_If\_Required. It starts with a connector symbol, followed by a decision 'ACM sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to another decision 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Address Complete', then 'ACM sent := True', and finally to an exit connector. Arrows pointing left indicate signals to the originating exchange. + +Figure 7a: Procedure Process\_Access\_Request\_MSC (sheet 1) + +![Flowchart for Procedure Send_Answer_If_Required. It starts with a connector symbol, followed by a decision 'Answer sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to another decision 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Answer', then 'Answer sent:= True', and finally to an exit connector symbol.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +### Procedure Send\_Answer\_If\_Required + +SANMIR1(1) + +Procedure to send an Answer Message to the preceding exchange if one is required for this call + +Signals to the left are to the originating exchange + +``` +graph TD; Start([ ]) --> D1{Answer sent}; D1 -- True --> CP{{Call Progress}}; D1 -- False --> D2{Network connect sent}; D2 -- True --> CP; D2 -- False --> A{{Answer}}; A --> AS[Answer sent:= True]; AS --> End(( )); CP --> End +``` + +Flowchart for Procedure Send\_Answer\_If\_Required. It starts with a connector symbol, followed by a decision 'Answer sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to another decision 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Answer', then 'Answer sent:= True', and finally to an exit connector symbol. + +Figure 7b: Procedure Process\_Access\_Request\_MSC (sheet 2) + +![Flowchart for Procedure Send_Network_Connect_If_Required. It starts with a connector symbol, followed by a decision 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Answer sent'. If 'True', it goes to 'Answer sent'. If 'False', it goes to 'ACM sent'. If 'True', it goes to 'Answer'. If 'False', it goes to 'Connect'. Both 'Answer' and 'Connect' lead to assignment boxes ('Answer sent:= True' and 'Connect sent:= True' respectively), which then lead to a merge point and finally an end connector symbol.](8269648391c59363ea61243864a2adf7_img.jpg) + +### Procedure Send\_Network\_Connect\_If\_Required + +SNCONIR1(1) + +Procedure to send a Connect Message to the preceding exchange if one is required for this call + +Signals to the left are to the originating exchange + +``` +graph TD; Start([ ]) --> D1{Network connect sent}; D1 -- True --> CP{{Call Progress}}; D1 -- False --> D2{Answer sent}; D2 -- True --> CP; D2 -- False --> D3{ACM sent}; D3 -- True --> A{{Answer}}; D3 -- False --> C{{Connect}}; A --> AS[Answer sent:= True]; C --> CS[Connect sent:= True]; AS --> Merge(( )); CS --> Merge; Merge --> End((X)) +``` + +Flowchart for Procedure Send\_Network\_Connect\_If\_Required. It starts with a connector symbol, followed by a decision 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Answer sent'. If 'True', it goes to 'Answer sent'. If 'False', it goes to 'ACM sent'. If 'True', it goes to 'Answer'. If 'False', it goes to 'Connect'. Both 'Answer' and 'Connect' lead to assignment boxes ('Answer sent:= True' and 'Connect sent:= True' respectively), which then lead to a merge point and finally an end connector symbol. + +Figure 7c: Procedure Process\_Access\_Request\_MSC (sheet 3) + +![Flowchart for Procedure Handle_COLP_Forwarding_Interaction_MSC. It starts with a connector symbol, followed by 'Initiate handling of COLP', then 'Wait_For_COLP_Info'. From 'Wait_For_COLP_Info', it branches to 'Release' (with a note 'From originating exchange or destination exchange') and 'continue call handling'. Both branches lead to an end connector symbol. Two callouts on the left explain the procedure's context and signal directions.](32ff77da4286b58c4778033acaa10836_img.jpg) + +### Procedure Handle\_COLP\_Forwarding\_Interaction\_MSC + +COINT\_M1(1) + +``` +graph TD; Start([ ]) --> Init[Initiate handling of COLP]; Init --> Wait[Wait_For_COLP_Info]; Wait --> Release[Release]; Note1[From originating exchange or destination exchange] --- Release; Wait --> Continue[continue call handling]; Release --> End((X)); Continue --> End +``` + +Procedure in the GMSC or VMSC to handle the interaction between COLP and Call Forwarding + +Signals to/from the right are to/from the process COLP\_MAF039 + +Flowchart for Procedure Handle\_COLP\_Forwarding\_Interaction\_MSC. It starts with a connector symbol, followed by 'Initiate handling of COLP', then 'Wait\_For\_COLP\_Info'. From 'Wait\_For\_COLP\_Info', it branches to 'Release' (with a note 'From originating exchange or destination exchange') and 'continue call handling'. Both branches lead to an end connector symbol. Two callouts on the left explain the procedure's context and signal directions. + +Figure 8a: Procedure OG\_Call\_Setup\_MSC (sheet 1) + +![Flowchart for Procedure Activate_CF_Process. It starts with a connector, followed by 'Perform call forwarding (BOR, FTN)', then 'Wait_For_CF_Response'. A decision point leads to four paths: 1) 'Release' -> 'CF cancelled' -> 'Result= Fail' -> connector; 2) 'Perform call forwarding ack' -> 'Result= Pass' -> connector; 3) 'Perform call forwarding negative response' -> 'Result= Fail' -> connector; 4) 'Int_Release_Call' (From gsmSSF) -> 'CF cancelled' -> 'Result= Release' -> connector.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +### Procedure Activate\_CF\_Process ACFP1(1) + +Procedure in the MSC to initiate the process which handles call forwarding + +Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the process MT\_CF\_MSC unless marked otherwise + +``` +graph TD; Start([ ]) --> Step1[Perform call forwarding (BOR, FTN)]; Step1 --> Step2((Wait_For_CF_Response)); Step2 --> Decision{ }; Decision --> Path1[Release]; Decision --> Path2[Perform call forwarding ack]; Decision --> Path3[Perform call forwarding negative response]; Decision --> Path4[Int_Release_Call]; Path1 --> CF_Canc1[CF cancelled]; CF_Canc1 --> ResFail1[Result= Fail]; ResFail1 --> End1(( )); Path2 --> ResPass[Result= Pass]; ResPass --> End2(( )); Path3 --> ResFail2[Result= Fail]; ResFail2 --> End3(( )); Path4 --> FromGsmSSF[From gsmSSF]; Path4 --> CF_Canc2[CF cancelled]; CF_Canc2 --> ResRelease[Result= Release]; ResRelease --> End4(( )); +``` + +Flowchart for Procedure Activate\_CF\_Process. It starts with a connector, followed by 'Perform call forwarding (BOR, FTN)', then 'Wait\_For\_CF\_Response'. A decision point leads to four paths: 1) 'Release' -> 'CF cancelled' -> 'Result= Fail' -> connector; 2) 'Perform call forwarding ack' -> 'Result= Pass' -> connector; 3) 'Perform call forwarding negative response' -> 'Result= Fail' -> connector; 4) 'Int\_Release\_Call' (From gsmSSF) -> 'CF cancelled' -> 'Result= Release' -> connector. + +Figure 8b: Procedure OG\_Call\_Setup\_MSC (sheet 2) + +![Flowchart for Process MT_CF_MSC (MTCFMSC1(6)). The process starts at 'Idle', proceeds to 'Perform call forwarding', then 'CAMEL_CF_MSC_INIT' (See TS 23.078). It then checks 'Result = Leg1_only?'. If Yes, it goes to connector '4'. If No, it checks 'Result = Pass?'. If Yes, it goes to 'CAMEL_CF_Dialled_Services' (See TS 23.078). If No, it goes to connector '4'. From 'CAMEL_CF_Dialled_Services', it checks 'Result?'. If Fail, it goes to connector '4'. If Pass, it goes to 'Perform call forwarding ack(FTN)' (See TS 23.078). From 'Perform call forwarding ack(FTN)', if 'Leg1_only' is Yes, it goes to connector '4'. If Abort is Yes, it goes to 'Idle'. If Pass, it goes to 'Wait_For_IAM'. From 'Wait_For_IAM', it goes to 'Initial Address' (connector '1'). From 'Initial Address', it checks 'MOBILE NUMBER PORTABILITY IN OQoD' (See TS 23.066). If Yes, it goes to 'CAMEL_Store_Destination_Address (BOR, True)' (See TS 23.078) and then 'Wait_For_ACM'. If No, it goes to 'CAMEL_OCH_MSC_DISC3' (See TS 23.078) and then 'Idle'. From 'CF cancelled', it checks 'CAMEL phase 2 or higher supported?'. If Yes, it goes to 'CAMEL_OCH_MSC_DISC4' (See TS 23.078) and then 'Idle'. If No, it goes to connector '2'. From 'CAMEL_OCH_MSC1' (See TS 23.078), it checks 'Result = Reconnect?'. If Yes, it goes to connector '2'. If No, it goes to 'Result = Fail?'. From 'Result = Fail?', if Yes, it goes to 'Perform Call Forwarding negative response' and then 'Idle'. If No, it goes to connector '4'. From 'Leg1_status := Set-up', it goes to 'CAMEL_MT_CF_LEG1_MSC (Leg1_status)' (See TS 23.078) and then 'Idle'.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +**Process MT\_CF\_MSC** **MTCFMSC1(6)** + +Process in the MSC to handle call forwarding + +Signals to/from the left are to/from the parent process; signals to/from the right are to/from the destination exchange + +``` + +graph TD + Start([Idle]) --> PerformCF[Perform call forwarding] + PerformCF --> CAMEL_CF_MSC_INIT[CAMEL_CF_MSC_INIT] + CAMEL_CF_MSC_INIT --- SeeTS23078_1[See TS 23.078] + CAMEL_CF_MSC_INIT --> ResultLeg1Only{Result = Leg1_only?} + ResultLeg1Only -- Yes --> Connector4((4)) + ResultLeg1Only -- No --> ResultPass{Result = Pass?} + ResultPass -- No --> Connector4 + ResultPass -- Yes --> CAMEL_CF_Dialled_Services[CAMEL_CF_Dialled_Services] + CAMEL_CF_Dialled_Services --- SeeTS23078_2[See TS 23.078] + CAMEL_CF_Dialled_Services --> Result{Result?} + Result -- Fail --> Connector4 + Result -- Pass --> PerformCFack[Perform call forwarding ack(FTN)] + PerformCFack --- SeeTS23078_3[See TS 23.078] + PerformCFack -- Leg1_only --> Connector4 + PerformCFack -- Abort --> Idle1([Idle]) + PerformCFack -- Pass --> WaitForIAM[Wait_For_IAM] + WaitForIAM --> InitialAddress[Initial Address] + InitialAddress --- Connector1((1)) + InitialAddress --> MP[MOBILE NUMBER PORTABILITY IN OQoD] + MP --- SeeTS23066[See TS 23.066] + MP -- Yes --> StoreDest[CAMEL_Store_Destination_Address (BOR, True)] + StoreDest --- SeeTS23078_4[See TS 23.078] + StoreDest --> WaitForACM[Wait_For_ACM] + MP -- No --> CAMEL_OCH_MSC_DISC3[CAMEL_OCH_MSC_DISC3] + CAMEL_OCH_MSC_DISC3 --- SeeTS23078_5[See TS 23.078] + CAMEL_OCH_MSC_DISC3 --> Idle2([Idle]) + CFcancelled[CF cancelled] --> Phase2{CAMEL phase 2 or higher supported?} + Phase2 -- Yes --> CAMEL_OCH_MSC_DISC4[CAMEL_OCH_MSC_DISC4] + CAMEL_OCH_MSC_DISC4 --- SeeTS23078_6[See TS 23.078] + CAMEL_OCH_MSC_DISC4 --> Idle3([Idle]) + Phase2 -- No --> Connector2((2)) + CAMEL_OCH_MSC1[CAMEL_OCH_MSC1] --- SeeTS23078_7[See TS 23.078] + CAMEL_OCH_MSC1 --> Reconnect{Result = Reconnect?} + Reconnect -- Yes --> Connector2 + Reconnect -- No --> ResultFail{Result = Fail?} + ResultFail -- Yes --> NegResponse[Perform Call Forwarding negative response] + NegResponse --> Idle4([Idle]) + ResultFail -- No --> Connector4 + Leg1Status[Leg1_status := Set-up] --> CAMEL_MT_CF_LEG1_MSC[CAMEL_MT_CF_LEG1_MSC (Leg1_status)] + CAMEL_MT_CF_LEG1_MSC --- SeeTS23078_8[See TS 23.078] + CAMEL_MT_CF_LEG1_MSC --> Idle5([Idle]) + +``` + +Flowchart for Process MT\_CF\_MSC (MTCFMSC1(6)). The process starts at 'Idle', proceeds to 'Perform call forwarding', then 'CAMEL\_CF\_MSC\_INIT' (See TS 23.078). It then checks 'Result = Leg1\_only?'. If Yes, it goes to connector '4'. If No, it checks 'Result = Pass?'. If Yes, it goes to 'CAMEL\_CF\_Dialled\_Services' (See TS 23.078). If No, it goes to connector '4'. From 'CAMEL\_CF\_Dialled\_Services', it checks 'Result?'. If Fail, it goes to connector '4'. If Pass, it goes to 'Perform call forwarding ack(FTN)' (See TS 23.078). From 'Perform call forwarding ack(FTN)', if 'Leg1\_only' is Yes, it goes to connector '4'. If Abort is Yes, it goes to 'Idle'. If Pass, it goes to 'Wait\_For\_IAM'. From 'Wait\_For\_IAM', it goes to 'Initial Address' (connector '1'). From 'Initial Address', it checks 'MOBILE NUMBER PORTABILITY IN OQoD' (See TS 23.066). If Yes, it goes to 'CAMEL\_Store\_Destination\_Address (BOR, True)' (See TS 23.078) and then 'Wait\_For\_ACM'. If No, it goes to 'CAMEL\_OCH\_MSC\_DISC3' (See TS 23.078) and then 'Idle'. From 'CF cancelled', it checks 'CAMEL phase 2 or higher supported?'. If Yes, it goes to 'CAMEL\_OCH\_MSC\_DISC4' (See TS 23.078) and then 'Idle'. If No, it goes to connector '2'. From 'CAMEL\_OCH\_MSC1' (See TS 23.078), it checks 'Result = Reconnect?'. If Yes, it goes to connector '2'. If No, it goes to 'Result = Fail?'. From 'Result = Fail?', if Yes, it goes to 'Perform Call Forwarding negative response' and then 'Idle'. If No, it goes to connector '4'. From 'Leg1\_status := Set-up', it goes to 'CAMEL\_MT\_CF\_LEG1\_MSC (Leg1\_status)' (See TS 23.078) and then 'Idle'. + +Figure 8c: Procedure OG\_Call\_Setup\_MSC (sheet 3) + +![MSC Sequence diagram for MT_CF_MSC process. The diagram shows two lifelines. The left lifeline starts with 'Wait_For_ACM', followed by 'Address Complete', 'CAMEL_Start_TNRy' (See TS 23.078), 'UUS_MSC_Clear_UUS' (See TS 23.087), 'CAMEL_CF_MSC_ALERTING' (See TS 23.078), a 'Result?' decision, 'Address Complete', 'Wait_For_Answer', 'Answer', 'CAMEL_Stop_TNRy' (See TS 23.078), 'CAMEL_CF_MSC_ANSWER' (See TS 23.078), another 'Result?' decision, 'UUS_MSC_Clear_UUS' (See TS 23.087), 'Answer', and connector 'A'. The right lifeline starts with 'Connect', 'UUS_MSC_Clear_UUS' (See TS 23.087), 'CAMEL_CF_MSC_ANSWER' (See TS 23.078), a 'Result?' decision, 'Connect', and connector 'A'. A central 'Result?' decision point receives 'Else' signals from both 'Result?' decisions and leads to 'Reconnect' (connector 2), 'Release', or 'Idle'.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +### Process MT\_CF\_MSC + +MTCFMSC2(6) + +``` +sequenceDiagram + participant Left as Process in the MSC to handle call forwarding + participant Right as Signals to/from the left are to/from the parent process; signals to/from the right are to/from the destination exchange + Note over Left: Wait_For_ACM + Left->>Left: Address Complete + Note left of Left: See TS 23.078 + Left->>Left: CAMEL_Start_TNRy + Note left of Left: See TS 23.087 + Left->>Left: UUS_MSC_Clear_UUS + Note left of Left: See TS 23.078 + Left->>Left: CAMEL_CF_MSC_ALERTING + Left->>Left: Result? + alt Else + Note right of Left: Else + Note right of Left: X + alt Pass + Note left of Left: Address Complete + Note left of Left: Wait_For_Answer + Note left of Left: Answer + Note left of Left: See TS 23.078 + Left->>Left: CAMEL_Stop_TNRy + Note left of Left: See TS 23.078 + Left->>Left: CAMEL_CF_MSC_ANSWER + Left->>Left: Result? + alt Else + Note right of Left: Else + Note right of Left: X + alt Pass + Note left of Left: See TS 23.087 + Left->>Left: UUS_MSC_Clear_UUS + Note left of Left: Answer + Note left of Left: A + end + Note right of Right: Connect + Note right of Right: UUS_MSC_Clear_UUS + Note right of Right: See TS 23.087 + Note right of Right: CAMEL_CF_MSC_ANSWER + Note right of Right: See TS 23.078 + Note right of Right: Result? + alt Else + Note right of Right: Else + Note right of Right: X + alt Pass + Note right of Right: Connect + Note right of Right: A + end + Note right of Left: Result? + alt Else + Note right of Left: Else + Note right of Left: X + alt Pass + Note right of Left: Reconnect + Note right of Left: 2 + Note right of Left: Release + Note right of Left: Idle + end +``` + +MSC Sequence diagram for MT\_CF\_MSC process. The diagram shows two lifelines. The left lifeline starts with 'Wait\_For\_ACM', followed by 'Address Complete', 'CAMEL\_Start\_TNRy' (See TS 23.078), 'UUS\_MSC\_Clear\_UUS' (See TS 23.087), 'CAMEL\_CF\_MSC\_ALERTING' (See TS 23.078), a 'Result?' decision, 'Address Complete', 'Wait\_For\_Answer', 'Answer', 'CAMEL\_Stop\_TNRy' (See TS 23.078), 'CAMEL\_CF\_MSC\_ANSWER' (See TS 23.078), another 'Result?' decision, 'UUS\_MSC\_Clear\_UUS' (See TS 23.087), 'Answer', and connector 'A'. The right lifeline starts with 'Connect', 'UUS\_MSC\_Clear\_UUS' (See TS 23.087), 'CAMEL\_CF\_MSC\_ANSWER' (See TS 23.078), a 'Result?' decision, 'Connect', and connector 'A'. A central 'Result?' decision point receives 'Else' signals from both 'Result?' decisions and leads to 'Reconnect' (connector 2), 'Release', or 'Idle'. + +Figure 8d: Procedure OG\_Call\_Setup\_MSC (sheet 4) + +![Flowchart for Process MT_CF_MSC. It starts with a 'Wait_For_ACM, Wait_For_Answer' state. It branches into three main paths. The left path goes through a 'Release' block, then a decision 'CAMEL phase 2 or higher supported?'. If 'No', it goes to 'CAMEL_OCH_MSC_DISC3' then 'Release'. If 'Yes', it goes to 'CAMEL_OCH_MSC_DISC4' then 'Release'. The middle path goes through a 'Release' block, then a decision 'CAMEL phase 2 or higher supported?'. If 'No', it goes to 'CAMEL_OCH_MSC_DISC3' then 'Release'. If 'Yes', it goes to a decision 'Release cause= No answer from user?'. If 'Yes', it goes to connector '3'. If 'No', it goes to 'CAMEL_OCH_MSC1' (See TS 23.078), then a decision 'Result= Reconnect?'. If 'No', it goes to 'Release'. If 'Yes', it goes to 'CAMEL_Stop_TNRy' (See TS 23.078), then connector '2'. The right path is labeled 'From gsmSSF' and goes to 'Int_O_Release', then 'Release'. All three 'Release' blocks lead to a common 'Release call resources' block, which leads to the 'Idle' state.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +### Process MT\_CF\_MSC + +MTCFMSC3(6) + +Process in the MSC to handle call forwarding + +Signals to/from the left are to/from the parent process; signals to/from the right are to/from the destination exchange unless marked otherwise + +``` +graph TD; Start([Wait_For_ACM, Wait_For_Answer]) --> Release1[Release]; Start --> Release2[Release]; Start --> Int_O_Release[Int_O_Release]; Release1 --> CAMEL2_1{CAMEL phase 2 or higher supported?}; CAMEL2_1 -- No --> CAMEL_OCH_MSC_DISC3_1[CAMEL_OCH_MSC_DISC3]; CAMEL2_1 -- Yes --> CAMEL_OCH_MSC_DISC4_1[CAMEL_OCH_MSC_DISC4_1]; CAMEL_OCH_MSC_DISC3_1 --> Release3[Release]; CAMEL_OCH_MSC_DISC4_1 --> Release3; Release2 --> CAMEL2_2{CAMEL phase 2 or higher supported?}; CAMEL2_2 -- No --> CAMEL_OCH_MSC_DISC3_2[CAMEL_OCH_MSC_DISC3_2]; CAMEL2_2 -- Yes --> ReleaseCause{Release cause= No answer from user?}; ReleaseCause -- Yes --> Connector3((3)); ReleaseCause -- No --> CAMEL_OCH_MSC1[CAMEL_OCH_MSC1]; CAMEL_OCH_MSC1 --> SeeTS23078_1[See TS 23.078]; CAMEL_OCH_MSC1 --> ResultReconnect{Result= Reconnect?}; ResultReconnect -- No --> Release4[Release]; ResultReconnect -- Yes --> CAMEL_Stop_TNRy[CAMEL_Stop_TNRy]; CAMEL_Stop_TNRy --> SeeTS23078_2[See TS 23.078]; CAMEL_Stop_TNRy --> Connector2((2)); Int_O_Release --> Release5[Release]; Release3 --> ReleaseCallResources[Release call resources]; Release4 --> ReleaseCallResources; Release5 --> ReleaseCallResources; ReleaseCallResources --> Idle([Idle]); +``` + +Flowchart for Process MT\_CF\_MSC. It starts with a 'Wait\_For\_ACM, Wait\_For\_Answer' state. It branches into three main paths. The left path goes through a 'Release' block, then a decision 'CAMEL phase 2 or higher supported?'. If 'No', it goes to 'CAMEL\_OCH\_MSC\_DISC3' then 'Release'. If 'Yes', it goes to 'CAMEL\_OCH\_MSC\_DISC4' then 'Release'. The middle path goes through a 'Release' block, then a decision 'CAMEL phase 2 or higher supported?'. If 'No', it goes to 'CAMEL\_OCH\_MSC\_DISC3' then 'Release'. If 'Yes', it goes to a decision 'Release cause= No answer from user?'. If 'Yes', it goes to connector '3'. If 'No', it goes to 'CAMEL\_OCH\_MSC1' (See TS 23.078), then a decision 'Result= Reconnect?'. If 'No', it goes to 'Release'. If 'Yes', it goes to 'CAMEL\_Stop\_TNRy' (See TS 23.078), then connector '2'. The right path is labeled 'From gsmSSF' and goes to 'Int\_O\_Release', then 'Release'. All three 'Release' blocks lead to a common 'Release call resources' block, which leads to the 'Idle' state. + +Figure 8e: Procedure OG\_Call\_Setup\_MSC (sheet 5) + +![Sequence diagram for Process MT_CF_MSC. The process starts with 'Wait_For_Answer', followed by 'TNRy expired' (Internal). A connector '3' leads to 'Release', which then leads to 'CAMEL_OCH_MSC2' (See TS 23.078). A decision 'Result?' follows: 'Release' leads to a 'Release' block; 'Reconnect' leads to connector '2' and 'CAMEL_CF_Dialled_Services' (See TS 23.078); 'Fail' leads to 'Release call resources' (See TS 23.078) and then 'Idle'. From 'CAMEL_CF_Dialled_Services', a decision 'Result?' follows: 'Abort' leads back to the 'Release call resources' path; 'Pass' leads to connector '1'; 'Fail' leads to 'CAMEL_OCH_MSC1' (See TS 23.078). From 'CAMEL_OCH_MSC1', a decision 'Result=Reconnect?' follows: 'Yes' leads to connector '2'; 'No' leads to 'Perform Call Forwarding negative response' and then 'Idle'.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +### Process MT\_CF\_MSC + +MTCFMSC4(6) + +``` +sequenceDiagram + participant User + participant MT_CF_MSC + Note left of MT_CF_MSC: Process in the MSC to handle call forwarding + Note right of MT_CF_MSC: Signals to/from the left are to/from the parent process; signals to/from the right are to/from the destination exchange unless marked otherwise + + MT_CF_MSC->>User: Wait_For_Answer + Note right of MT_CF_MSC: Internal + MT_CF_MSC->>User: TNRy expired + Note right of MT_CF_MSC: 3 + MT_CF_MSC->>User: Release + Note right of MT_CF_MSC: CAMEL_OCH_MSC2 (See TS 23.078) + MT_CF_MSC->>User: Result? + alt Release: Release + alt Reconnect: 2, CAMEL_CF_Dialled_Services (See TS 23.078) + alt Fail: Release call resources (See TS 23.078) -> Idle + Note right of MT_CF_MSC: CAMEL_CF_Dialled_Services (See TS 23.078) + MT_CF_MSC->>User: Result? + alt Abort: Release call resources (See TS 23.078) -> Idle + alt Pass: 1 + alt Fail: CAMEL_OCH_MSC1 (See TS 23.078) + Note right of MT_CF_MSC: CAMEL_OCH_MSC1 (See TS 23.078) + MT_CF_MSC->>User: Result=Reconnect? + alt Yes: 2 + alt No: Perform Call Forwarding negative response -> Idle +``` + +Sequence diagram for Process MT\_CF\_MSC. The process starts with 'Wait\_For\_Answer', followed by 'TNRy expired' (Internal). A connector '3' leads to 'Release', which then leads to 'CAMEL\_OCH\_MSC2' (See TS 23.078). A decision 'Result?' follows: 'Release' leads to a 'Release' block; 'Reconnect' leads to connector '2' and 'CAMEL\_CF\_Dialled\_Services' (See TS 23.078); 'Fail' leads to 'Release call resources' (See TS 23.078) and then 'Idle'. From 'CAMEL\_CF\_Dialled\_Services', a decision 'Result?' follows: 'Abort' leads back to the 'Release call resources' path; 'Pass' leads to connector '1'; 'Fail' leads to 'CAMEL\_OCH\_MSC1' (See TS 23.078). From 'CAMEL\_OCH\_MSC1', a decision 'Result=Reconnect?' follows: 'Yes' leads to connector '2'; 'No' leads to 'Perform Call Forwarding negative response' and then 'Idle'. + +Figure 8f: Procedure OG\_Call\_Setup\_MSC (sheet 6) + +![Sequence diagram for Process MT_CF_MSC. The diagram shows a flow starting from 'Wait_For_Clear' to three parallel 'Release' paths. The left path goes through 'CAMEL_OCH_MSC_DISC1' (See TS 23.078) to 'Result_CAMEL_Handling?'. The middle path goes through 'CAMEL_OCH_MSC_DISC2' (See TS 23.078) to 'Result_CAMEL_Handling?'. The right path goes through 'Int_Q_Release' (From gsmSSF) to 'Release'. All three paths converge to 'Release call resources' and then 'Idle'. A second part of the diagram shows a '*' process with two outgoing arrows and one incoming arrow, leading to a '-' state.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +### Process MT\_CF\_MSC + +MTCFMSC5(6) + +Process in the MSC to handle call forwarding + +Signals to/from the left are to/from the parent process; signals to/from the right are to/from the destination exchange unless marked otherwise + +``` +sequenceDiagram + participant Parent + participant MT_CF_MSC + Note left of MT_CF_MSC: Process in the MSC to handle call forwarding + Note right of MT_CF_MSC: Signals to/from the left are to/from the parent process; signals to/from the right are to/from the destination exchange unless marked otherwise + + MT_CF_MSC->>Parent: Wait_For_Clear + Note right of MT_CF_MSC: From gsmSSF + MT_CF_MSC->>MT_CF_MSC: Release + MT_CF_MSC->>MT_CF_MSC: CAMEL_OCH_MSC_DISC1 + Note right of MT_CF_MSC: See TS 23.078 + MT_CF_MSC->>MT_CF_MSC: Result_CAMEL_Handling? + MT_CF_MSC->>MT_CF_MSC: Release + MT_CF_MSC->>MT_CF_MSC: Release + MT_CF_MSC->>MT_CF_MSC: CAMEL_OCH_MSC_DISC2 + Note right of MT_CF_MSC: See TS 23.078 + MT_CF_MSC->>MT_CF_MSC: Result_CAMEL_Handling? + MT_CF_MSC->>MT_CF_MSC: Result_Reconnect? + MT_CF_MSC->>MT_CF_MSC: Release + MT_CF_MSC->>MT_CF_MSC: Int_Q_Release + MT_CF_MSC->>MT_CF_MSC: Release + Note right of MT_CF_MSC: 2 + MT_CF_MSC->>MT_CF_MSC: Release call resources + MT_CF_MSC->>MT_CF_MSC: Idle + + Note right of MT_CF_MSC: * + MT_CF_MSC->>MT_CF_MSC: * + MT_CF_MSC->>MT_CF_MSC: - + MT_CF_MSC->>MT_CF_MSC: - + MT_CF_MSC->>MT_CF_MSC: - +``` + +Sequence diagram for Process MT\_CF\_MSC. The diagram shows a flow starting from 'Wait\_For\_Clear' to three parallel 'Release' paths. The left path goes through 'CAMEL\_OCH\_MSC\_DISC1' (See TS 23.078) to 'Result\_CAMEL\_Handling?'. The middle path goes through 'CAMEL\_OCH\_MSC\_DISC2' (See TS 23.078) to 'Result\_CAMEL\_Handling?'. The right path goes through 'Int\_Q\_Release' (From gsmSSF) to 'Release'. All three paths converge to 'Release call resources' and then 'Idle'. A second part of the diagram shows a '\*' process with two outgoing arrows and one incoming arrow, leading to a '-' state. + +Figure 8g: Procedure OG\_Call\_Setup\_MSC (sheet 7) + +![Flowchart for Process MT_CF_MSC. It starts at connector 'A', goes to a decision 'CAMEL phase 4 or later control relationship exists?'. If 'No', it goes to 'Wait_For_Clear'. If 'Yes', it goes to a sub-process 'CAMEL_MT_CF_LEG2_MSC' (referenced in TS 23.078), then sets 'Leg1_status := Active', then to another sub-process 'CAMEL_MT_CF_LEG1_MSC (Leg1_status)' (referenced in TS 23.078), and finally reaches the 'Idle' state.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +**Process MT\_CF\_MSC** **MTCFMSC6(6)** + +Process in the MSC to handle call forwarding + +``` +graph TD; A((A)) --> Decision{CAMEL phase 4 or later control relationship exists?}; Decision -- No --> Wait_For_Clear([Wait_For_Clear]); Decision -- Yes --> Sub1[CAMEL_MT_CF_LEG2_MSC]; Note1[See TS 23.078] -.-> Sub1; Sub1 --> Leg1_Status[Leg1_status := Active]; Leg1_Status --> Sub2[CAMEL_MT_CF_LEG1_MSC (Leg1_status)]; Note2[See TS 23.078] -.-> Sub2; Sub2 --> Idle([Idle]); +``` + +Flowchart for Process MT\_CF\_MSC. It starts at connector 'A', goes to a decision 'CAMEL phase 4 or later control relationship exists?'. If 'No', it goes to 'Wait\_For\_Clear'. If 'Yes', it goes to a sub-process 'CAMEL\_MT\_CF\_LEG2\_MSC' (referenced in TS 23.078), then sets 'Leg1\_status := Active', then to another sub-process 'CAMEL\_MT\_CF\_LEG1\_MSC (Leg1\_status)' (referenced in TS 23.078), and finally reaches the 'Idle' state. + +**Figure 8h: Procedure OG\_Call\_Setup\_MSC (sheet 8)** + +![Flowchart for CUG_Support_Check_GMSC macro. It starts with a connector, then a decision 'CUG info present?'. If 'No', it goes to 'Pass'. If 'Yes', it goes to 'GMSC supports CUG?'. If 'Yes', it goes to 'Outgoing Access present?'. If 'Yes', it goes to 'Pass'. If 'No' at any point, it goes to 'Fail'.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +### Macrodefinition CUG\_Support\_Check\_GMSC + +CUG\_SC1(1) + +Macro to check support of CUG in GMSC, if needed, and check if call can continue. + +``` +graph TD; Start([ ]) --> CUG{CUG info present?}; CUG -- No --> Pass((Pass)); CUG -- Yes --> GMSC{GMSC supports CUG?}; GMSC -- Yes --> Outgoing{Outgoing Access present?}; GMSC -- No --> Fail((Fail)); Outgoing -- Yes --> Pass; Outgoing -- No --> Fail; +``` + +Flowchart for CUG\_Support\_Check\_GMSC macro. It starts with a connector, then a decision 'CUG info present?'. If 'No', it goes to 'Pass'. If 'Yes', it goes to 'GMSC supports CUG?'. If 'Yes', it goes to 'Outgoing Access present?'. If 'Yes', it goes to 'Pass'. If 'No' at any point, it goes to 'Fail'. + +Figure 8i: Procedure OG\_Call\_Setup\_MSC (sheet 9) + +![Flowchart for Process SRI_HLR. The process starts with an 'Idle' state, followed by 'Send Routeing Info', 'Check_Parameters', and a 'Result= Pass?' decision. If 'Yes', it proceeds to 'Subscription Check_HLR', then 'SCUDIF_Subscription Check_HLR' (referencing TS 23.172), and then a 'Result= Fail?' decision. If 'No' to this decision, it goes to 'OR_HLR_CF' (referencing TS 23.079) and then to connector 7. If 'Yes', it goes to connector 6. From 'OR_HLR_CF', there is another 'Result= Fail?' decision. If 'Yes', it goes to connector 1. If 'No', it proceeds to a 'Result= Forward?' decision. If 'Yes', it goes to connector 2. If 'No', it proceeds to 'CAMEL_HLR_INIT' (referencing TS 23.078) and then to a 'Result= Fail?' decision. If 'Yes', it goes to connector 1. If 'No', it goes to connector 3.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +### Process SRI\_HLR + +**SRI\_HLR1(7)** + +Process in the HLR to handle a request for routing information + +Signals to/from the left are to/from the GMSC or the gsmSCF; signals to/from the right are to/from the VLR + +``` +graph TD; Start([Idle]) --> Send[Send Routeing Info]; Send --> Check[Check_Parameters]; Check --> Pass{Result= Pass?}; Pass -- Yes --> Sub[Subscription Check_HLR]; Sub --> SCUDIF[SCUDIF_Subscription Check_HLR]; SCUDIF -.-> TS23172[See TS 23.172]; SCUDIF --> Fail1{Result= Fail?}; Fail1 -- No --> OR[OR_HLR_CF]; OR -.-> TS23079[See TS 23.079]; OR --> Fail2{Result= Fail?}; Fail2 -- Yes --> C1_1((1)); Fail2 -- No --> Forward{Result= Forward?}; Forward -- Yes --> C2((2)); Forward -- No --> CAMEL[CAMEL_HLR_INIT]; CAMEL -.-> TS23078[See TS 23.078]; CAMEL --> Fail3{Result= Fail?}; Fail3 -- Yes --> C1_2((1)); Fail3 -- No --> C3((3)); Fail1 -- Yes --> C6((6)); Pass -- No --> C6; Fail2 -- No --> C7((7)); +``` + +Flowchart for Process SRI\_HLR. The process starts with an 'Idle' state, followed by 'Send Routeing Info', 'Check\_Parameters', and a 'Result= Pass?' decision. If 'Yes', it proceeds to 'Subscription Check\_HLR', then 'SCUDIF\_Subscription Check\_HLR' (referencing TS 23.172), and then a 'Result= Fail?' decision. If 'No' to this decision, it goes to 'OR\_HLR\_CF' (referencing TS 23.079) and then to connector 7. If 'Yes', it goes to connector 6. From 'OR\_HLR\_CF', there is another 'Result= Fail?' decision. If 'Yes', it goes to connector 1. If 'No', it proceeds to a 'Result= Forward?' decision. If 'Yes', it goes to connector 2. If 'No', it proceeds to 'CAMEL\_HLR\_INIT' (referencing TS 23.078) and then to a 'Result= Fail?' decision. If 'Yes', it goes to connector 1. If 'No', it goes to connector 3. + +Figure 8j: Procedure OG\_Call\_Setup\_MSC (sheet 10) + +![Flowchart for Process SRI_HLR. It starts at connector 3, goes to First_Forwarding_HLR. If Result=Fail? is Yes, it goes to HLR support Domain Selection?; if No, it goes to Result=Forward?. If Result=Forward? is Yes, it goes to connector 2; if No, it goes to HLR support Domain Selection?. Both HLR support Domain Selection? paths lead to Domain_Selection_HLR. From Domain_Selection_HLR, if Result=CS or IMS? is Yes, it goes to connector 12; if No, it goes to CAMEL_CSI_Check_HLR (See TS 23.078). CAMEL_CSI_Check_HLR leads to SCUDIF_CAMEL_CSI_Check_HLR (See TS 23.172). SCUDIF_CAMEL_CSI_Check_HLR leads to Result=CSI active?. If Yes, it goes to connector 4; if No, it goes to gsmSCF Initiated Call?. If gsmSCF Initiated Call? is Yes, it goes to Suppress_CGBS_Handling?; if No, it goes to connector 1. Suppress_CGBS_Handling? leads to OCBS_Handling_HLR (See TS 23.093). OCBS_Handling_HLR leads to Result = Forward. If Yes, it goes to connector 2; if No, it goes to Result = OK. If Result = OK is Yes, it goes to connector 5; if No, it goes to connector 1. The right side of the flowchart follows a similar path but ends at connector 1 from the Result=CSI active? decision.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +### Process SRI\_HLR + +Process in the HLR to handle a request for routing information + +### SRI\_HLR2(7) + +Signals to/from the left are to/from the GMSC or the gsmSCF; signals to/from the right are to/from the VLR + +``` +graph TD + 3((3)) --> F[First_Forwarding_HLR] + F --> RF{Result=Forward?} + RF -- Yes --> 2((2)) + RF -- No --> HDS{HLR support Domain Selection?} + HDS -- Yes --> DS[Domain_Selection_HLR] + HDS -- No --> CCH[CAMEL_CSI_Check_HLR] + CCH -- "See TS 23.078" --> SCCH[SCUDIF_CAMEL_CSI_Check_HLR] + SCCH -- "See TS 23.172" --> RCA{Result=CSI active?} + RCA -- Yes --> 4((4)) + RCA -- No --> GIC{gsmSCF Initiated Call?} + GIC -- Yes --> SCH{Suppress_CGBS_Handling?} + GIC -- No --> 1((1)) + SCH --> OCH[OCBS_Handling_HLR] + OCH -- "See TS 23.093" --> RFwd{Result = Forward} + RFwd -- Yes --> 2((2)) + RFwd -- No --> RO{Result = OK} + RO -- Yes --> 5((5)) + RO -- No --> 1((1)) + DS --> DCI{Result=CS or IMS?} + DCI -- IMS --> 12((12)) + DCI -- CS --> CCH + HDS -- Yes --> DS + HDS -- No --> DCI + DS --> DCI + DCI -- IMS --> 12((12)) + DCI -- CS --> CCH + CCH -- "See TS 23.078" --> SCCH + SCCH -- "See TS 23.172" --> RCA + RCA -- Yes --> 4((4)) + RCA -- No --> 1((1)) +``` + +Flowchart for Process SRI\_HLR. It starts at connector 3, goes to First\_Forwarding\_HLR. If Result=Fail? is Yes, it goes to HLR support Domain Selection?; if No, it goes to Result=Forward?. If Result=Forward? is Yes, it goes to connector 2; if No, it goes to HLR support Domain Selection?. Both HLR support Domain Selection? paths lead to Domain\_Selection\_HLR. From Domain\_Selection\_HLR, if Result=CS or IMS? is Yes, it goes to connector 12; if No, it goes to CAMEL\_CSI\_Check\_HLR (See TS 23.078). CAMEL\_CSI\_Check\_HLR leads to SCUDIF\_CAMEL\_CSI\_Check\_HLR (See TS 23.172). SCUDIF\_CAMEL\_CSI\_Check\_HLR leads to Result=CSI active?. If Yes, it goes to connector 4; if No, it goes to gsmSCF Initiated Call?. If gsmSCF Initiated Call? is Yes, it goes to Suppress\_CGBS\_Handling?; if No, it goes to connector 1. Suppress\_CGBS\_Handling? leads to OCBS\_Handling\_HLR (See TS 23.093). OCBS\_Handling\_HLR leads to Result = Forward. If Yes, it goes to connector 2; if No, it goes to Result = OK. If Result = OK is Yes, it goes to connector 5; if No, it goes to connector 1. The right side of the flowchart follows a similar path but ends at connector 1 from the Result=CSI active? decision. + +Figure 8k: Procedure OG\_Call\_Setup\_MSC (sheet 11) + +![Flowchart for Process SRI_HLR. It starts at connector 5, goes to OR_HLR_Interrogate_VLR (referencing TS 23.079). A decision 'Result= Fail?' follows. If Yes, it goes to connector 1. If No, it goes to 'Result= Forward?'. If Yes, it goes to connector 2. If No, it goes to SCUDIF_Set_Correct_PLMN_BC. A 'Result' triangle follows. From 'Result', 'SRI_Ack' goes to connector 4, and 'Set_PLMN_BC' leads to 'Continue' and a decision 'PLMN BC= NULL?'. If 'PLMN BC= NULL?' is Yes, it goes to 'Continue'. If No, it goes to 'Set PLMN BC parameter'. Both lead to 'Alerting Pattern required?'. If Yes, it goes to 'Set Alerting Pattern'. Both lead to CLI_HLR_Set_CLI (referencing TS 23.081), which ends at connector 8.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +### Process SRI\_HLR + +**SRI\_HLR3(7)** + +Process in the HLR to handle a request for routing information + +Signals to/from the left are to/from the GMSC or the gsmSCF; signals to/from the right are to/from the VLR + +``` +graph TD; 5((5)) --> OR_HLR_Interrogate_VLR[OR_HLR_Interrogate_VLR]; OR_HLR_Interrogate_VLR -.-> TS23079[See TS 23.079]; OR_HLR_Interrogate_VLR --> Result_Fail{Result= Fail?}; Result_Fail -- Yes --> 1((1)); Result_Fail -- No --> Result_Forward{Result= Forward?}; Result_Forward -- Yes --> 2((2)); Result_Forward -- No --> SCUDIF_Set_Correct_PLMN_BC[SCUDIF_Set_Correct_PLMN_BC]; SCUDIF_Set_Correct_PLMN_BC --> Result{Result}; Result -- SRI_Ack --> 4((4)); Result -- Set_PLMN_BC --> Continue[Continue]; Continue --> PLMN_BC_NULL{PLMN BC= NULL?}; PLMN_BC_NULL -- Yes --> Continue; PLMN_BC_NULL -- No --> Set_PLMN_BC_param[Set PLMN BC parameter]; Set_PLMN_BC_param --> Alerting_Pattern_Required{Alerting Pattern required?}; Alerting_Pattern_Required -- Yes --> Set_Alerting_Pattern[Set Alerting Pattern]; Alerting_Pattern_Required -- No --> CLI_HLR_Set_CLI[CLI_HLR_Set_CLI]; Set_Alerting_Pattern --> CLI_HLR_Set_CLI; CLI_HLR_Set_CLI -.-> TS23081[See TS 23.081]; CLI_HLR_Set_CLI --> 8((8)); +``` + +Flowchart for Process SRI\_HLR. It starts at connector 5, goes to OR\_HLR\_Interrogate\_VLR (referencing TS 23.079). A decision 'Result= Fail?' follows. If Yes, it goes to connector 1. If No, it goes to 'Result= Forward?'. If Yes, it goes to connector 2. If No, it goes to SCUDIF\_Set\_Correct\_PLMN\_BC. A 'Result' triangle follows. From 'Result', 'SRI\_Ack' goes to connector 4, and 'Set\_PLMN\_BC' leads to 'Continue' and a decision 'PLMN BC= NULL?'. If 'PLMN BC= NULL?' is Yes, it goes to 'Continue'. If No, it goes to 'Set PLMN BC parameter'. Both lead to 'Alerting Pattern required?'. If Yes, it goes to 'Set Alerting Pattern'. Both lead to CLI\_HLR\_Set\_CLI (referencing TS 23.081), which ends at connector 8. + +Figure 9: Procedure Obtain\_IMSI\_MSC + +![Flowchart for Process SRI_HLR. It starts at connector 8, checks if pre-paging is supported in the HLR, then if it's supported in the GMSC. If not supported in the GMSC, it skips to 'Provide Roaming Number'. If supported in the GMSC, it sets pre-paging supported and then provides the roaming number. Finally, it waits for the MSRN.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +**Process SRI\_HLR** + +**SRI\_HLR4(7)** + +Process in the HLR to handle a request for routing information + +``` +graph TD; Start((8)) --> HLR_Support{Pre-paging supported in HLR?}; HLR_Support -- Yes --> GMSC_Support{Pre-paging supported in GMSC?}; HLR_Support -- No --> Provide_RN{{Provide Roaming Number}}; GMSC_Support -- Yes --> Set_Supported[Set Pre-paging supported]; GMSC_Support -- No --> Provide_RN; Set_Supported --> Provide_RN; Provide_RN --> Wait_MS RN([Wait_For_ MSRN]) +``` + +Flowchart for Process SRI\_HLR. It starts at connector 8, checks if pre-paging is supported in the HLR, then if it's supported in the GMSC. If not supported in the GMSC, it skips to 'Provide Roaming Number'. If supported in the GMSC, it sets pre-paging supported and then provides the roaming number. Finally, it waits for the MSRN. + +**Figure 10: Procedure Authenticate\_MSC** + +![](7ed5d5770331f31ade15439a21c31425_img.jpg) + +Process SRI\_HLR +SRI\_HLR5(7) + +Process in the HLR to handle a request for routeing information + +Signals to/from the left are to/from the GMSC or the gsmSCF; signals to/from the right are to/from the VLR + +``` + + graph TD + Wait_For_MSRN([Wait_For_MSRN]) --> PRN_Neg_Resp{Provide Roaming +Number negative +response} + + PRN_Neg_Resp -- No --> PRN_Ack[/Provide +Roaming +Number ack/] + PRN_Ack --> Routeing_Addr[Routeing +address:= +MSRN] + Routeing_Addr --> SCUDIF_Check[SCUDIF_Check +Second_Service +after_PRN] + SCUDIF_Check --> TS_23_172[See TS 23.172] + SCUDIF_Check --> Result_Continue{Result= +Continue?} + + Result_Continue -- Yes --> Conn4((4)) + Result_Continue -- No --> Conn7((7)) + + PRN_Neg_Resp -- Yes --> PRN_Error_HLR[PRN_Error_ +HLR] + PRN_Error_HLR --> MT_Retry{MT Roaming Retry +supported and +received Update +Location Request?} + + MT_Retry -- Yes --> Set_Error[Set Error=Absent Subscriber +with reason "mtRoamingRetry" +in the SRI response] + Set_Error --> Send_Neg_Rsp[/Send Routeing +Info Negative Rsp/] + Send_Neg_Rsp --> Idle1([Idle]) + + MT_Retry -- No --> Result_Fail{Result= +Fail?} + Result_Fail -- Yes --> Conn1((1)) + Result_Fail -- No --> Forward_CUG[Forward_ +CUG_Check] + + Conn2((2)) --> Forward_CUG + + Forward_CUG --> Result_Allowed{Result= +Call +allowed?} + Result_Allowed -- Yes --> Conn9((9)) + Result_Allowed -- No --> Conn11((11)) + + Conn11 --> Conn12((12)) + Conn12 --> Set_Routeing_Addr[Set Routeing +address] + Set_Routeing_Addr --> TS_23_292[see TS 23.292] + + Conn4 --> Join_Point + Conn7 --> Join_Point + Conn10((10)) --> Join_Point + Set_Routeing_Addr --> Join_Point + + Join_Point --> Send_Ack[/Send +Routeing +Info ack/] + Send_Ack --> Idle2([Idle]) + + style Join_Point width:0px, height:0px + +``` + +Figure 11: Procedure Obtain\_IMEI\_MSC + +![Flowchart for Process SRI_HLR. It starts at connector 11, checks if forwarding is required. If not, it performs CAMEL and SCUDIF CSI checks. If CSI is active, it proceeds to the result; otherwise, it sets a negative response. If forwarding is required, it goes to connector 1. Both paths lead to a second service check before a final result. The result can pass (leading to connector 6 and an 'Idle' state), fail (leading to a negative response and an 'Idle' state), or trigger a second interrogation (leading to connector 7).](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +### Process SRI\_HLR + +SRI\_HLR6(7) + +Process in the HLR to handle a request for routing information + +``` +graph TD; 11((11)) --> F{Forwarding enquiry?}; F -- Yes --> 1((1)); F -- No --> C[CAMEL_CSI_Check_HLR]; C -.-> TS1[See TS 23.078]; C --> SC[SCUDIF_CAMEL_CSI_Check_HLR]; SC -.-> TS2[See TS 23.172]; SC --> RA{Result=CSI active?}; RA -- No --> NR[Set negative response: CUG reject]; NR --> SS[Called party SS interaction violation]; SS --> SC2[SCUDIF_Check_Second_Service_before_negative_response]; SC2 -.-> TS3[See TS 23.172]; RA -- Yes --> R{Result?}; 1 --> R; R -- Pass --> S[Send Routeing Info ack]; S --> Idle1([Idle]); R -- fail --> SN[Send Routeing Info negative response]; SN --> Idle2([Idle]); R -- Second_Interrogation --> 7((7)); 6((6)) --> SN; +``` + +Flowchart for Process SRI\_HLR. It starts at connector 11, checks if forwarding is required. If not, it performs CAMEL and SCUDIF CSI checks. If CSI is active, it proceeds to the result; otherwise, it sets a negative response. If forwarding is required, it goes to connector 1. Both paths lead to a second service check before a final result. The result can pass (leading to connector 6 and an 'Idle' state), fail (leading to a negative response and an 'Idle' state), or trigger a second interrogation (leading to connector 7). + +Figure 12: Procedure Check\_IMEI\_MSC + +![Flowchart for Process SRI_HLR. It starts at connector 9, sets the routing address to FTN, then calls SCUDIF_Set_Second_Service_when_Forwarded (refer to TS 23.172). A decision 'Result=Continue?' follows. If 'No', it goes to connector 10. If 'Yes', it checks 'Forwarding enquiry?'. If 'Yes', it goes to connector 10. If 'No', it calls CAMEL_T_CSI_CHECK_HLR (refer to TS 23.078), then CAMEL_O_CSI_CHECK_HLR (refer to TS 23.078), then CAMEL_D_CSI_CHECK_HLR (refer to TS 23.078), then SCUDIF_Check_Second_Service_when_Forwarded (refer to TS 23.172). Another 'Result=Continue?' decision follows. If 'No', it goes to connector 7. If 'Yes', it sends a routing info ack and goes to the 'Idle' state.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +### Process SRI\_HLR + +SRI\_HLR7(7) + +Process in the HLR to handle a request for routing information + +``` +graph TD; 9((9)) --> RA["Routing address:= FTN"]; RA --> SC1[SCUDIF_Set_Second_Service_when_Forwarded]; SC1 -.-> TS23172_1[See TS 23.172]; SC1 --> RC1{Result=Continue?}; RC1 -- No --> 10((10)); RC1 -- Yes --> FE{Forwarding enquiry?}; FE -- Yes --> 10; FE -- No --> CT[["CAMEL_T_CSI_CHECK_HLR"]]; CT -.-> TS23078_1[See TS 23.078]; CT --> CO[["CAMEL_O_CSI_CHECK_HLR"]]; CO -.-> TS23078_2[See TS 23.078]; CO --> CD[["CAMEL_D_CSI_CHECK_HLR"]]; CD -.-> TS23078_3[See TS 23.078]; CD --> SC2[["SCUDIF_Check_Second_Service_when_Forwarded"]]; SC2 -.-> TS23172_2[See TS 23.172]; SC2 --> RC2{Result=Continue?}; RC2 -- No --> 7((7)); RC2 -- Yes --> SRIA{{Send Routeing Info ack}}; SRIA --> Idle([Idle]); +``` + +Flowchart for Process SRI\_HLR. It starts at connector 9, sets the routing address to FTN, then calls SCUDIF\_Set\_Second\_Service\_when\_Forwarded (refer to TS 23.172). A decision 'Result=Continue?' follows. If 'No', it goes to connector 10. If 'Yes', it checks 'Forwarding enquiry?'. If 'Yes', it goes to connector 10. If 'No', it calls CAMEL\_T\_CSI\_CHECK\_HLR (refer to TS 23.078), then CAMEL\_O\_CSI\_CHECK\_HLR (refer to TS 23.078), then CAMEL\_D\_CSI\_CHECK\_HLR (refer to TS 23.078), then SCUDIF\_Check\_Second\_Service\_when\_Forwarded (refer to TS 23.172). Another 'Result=Continue?' decision follows. If 'No', it goes to connector 7. If 'Yes', it sends a routing info ack and goes to the 'Idle' state. + +Figure 13: Procedure Establish\_Originating\_TCH\_If\_Required + +![Flowchart for Procedure Check_Parameters. It starts with a note 'Procedure to check the parameters of a received message' and a start symbol. The first decision is 'All required parameters present?'. If 'No', it goes to 'Set negative response: Data missing' and then to 'Result:= Fail'. If 'Yes', it goes to the second decision 'All parameter values acceptable?'. If 'No', it goes to 'Set negative response: Unexpected data value' and then to 'Result:= Fail'. If 'Yes', it goes to 'Result:= Pass'.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +**Procedure Check\_Parameters** **Chk\_Par1(1)** + +``` +graph TD; Start([Start]) --> D1{All required parameters present?}; D1 -- No --> N1[Set negative response: Data missing]; D1 -- Yes --> D2{All parameter values acceptable?}; D2 -- No --> N2[Set negative response: Unexpected data value]; N1 --> R1[Result:= Fail]; N2 --> R1; D2 -- Yes --> R2[Result:= Pass]; R1 --> End1(( )); R2 --> End2(( )); Note[Procedure to check the parameters of a received message] +``` + +Flowchart for Procedure Check\_Parameters. It starts with a note 'Procedure to check the parameters of a received message' and a start symbol. The first decision is 'All required parameters present?'. If 'No', it goes to 'Set negative response: Data missing' and then to 'Result:= Fail'. If 'Yes', it goes to the second decision 'All parameter values acceptable?'. If 'No', it goes to 'Set negative response: Unexpected data value' and then to 'Result:= Fail'. If 'Yes', it goes to 'Result:= Pass'. + +**Figure 14: Procedure Set\_CLI\_Presentation\_Indicator\_MSC** + +![Flowchart for Procedure Subscription_Check_HLR. It starts with 'MS known?' (No leads to 'Set negative response: Unknown subscriber'), 'Number changed?' (Yes leads to 'Set negative response: Number changed'), 'Requested service provisioned?' (No leads to 'Set negative response: service not provisioned' with 'Bearer service or Teleservice'), 'gsmSCF Initiated Call?' (Yes leads to 'Suppress ICB?' or 'Suppress CUG?'), 'Result= Call barred?' (Yes leads to 'Set negative response: Call barred'), and 'Result= Call allowed?' (No leads to 'Set negative response: CUG reject'). All negative responses lead to 'Result:= Fail'. Success leads to 'Result:= Pass'.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +### Procedure Subscription\_Check\_HLR + +SC\_HLR1(1) + +Procedure in the HLR to make subscription checks for a mobile-terminated call + +``` +graph TD; Start([Start]) --> MS_known{MS known?}; MS_known -- No --> Neg1[Set negative response: Unknown subscriber]; MS_known -- Yes --> Num_changed{Number changed?}; Num_changed -- Yes --> Neg2[Set negative response: Number changed]; Num_changed -- No --> Derive[Derive requested basic service]; Note1[See TS 29.007] -.-> Derive; Derive --> Req_svc{Requested service provisioned?}; Req_svc -- No --> Neg3[Set negative response: service not provisioned]; Note2[Bearer service or Teleservice] -.-> Neg3; Req_svc -- Yes --> gsmSCF_1{gsmSCF Initiated Call?}; gsmSCF_1 -- No --> Neg3; gsmSCF_1 -- Yes --> Suppress_ICB{Suppress ICB?}; Suppress_ICB -- Yes --> Neg3; Suppress_ICB -- No --> Check_ICB[Check_IC_Barring]; Check_ICB --> Result_barred{Result= Call barred?}; Result_barred -- Yes --> Neg4[Set negative response: Call barred]; Result_barred -- No --> gsmSCF_2{gsmSCF Initiated Call?}; gsmSCF_2 -- No --> Neg4; gsmSCF_2 -- Yes --> Suppress_CUG{Suppress CUG?}; Suppress_CUG -- Yes --> Neg3; Suppress_CUG -- No --> Check_CUG[IC_CUG_Check]; Check_CUG --> Result_allowed{Result= Call allowed?}; Result_allowed -- No --> Neg5[Set negative response: CUG reject]; Result_allowed -- Yes --> Pass[Result:= Pass]; Neg1 --> Fail[Result:= Fail]; Neg2 --> Fail; Neg3 --> Fail; Neg4 --> Fail; Neg5 --> Fail; Pass --> EndPass([End]); Fail --> EndFail([End]); +``` + +Flowchart for Procedure Subscription\_Check\_HLR. It starts with 'MS known?' (No leads to 'Set negative response: Unknown subscriber'), 'Number changed?' (Yes leads to 'Set negative response: Number changed'), 'Requested service provisioned?' (No leads to 'Set negative response: service not provisioned' with 'Bearer service or Teleservice'), 'gsmSCF Initiated Call?' (Yes leads to 'Suppress ICB?' or 'Suppress CUG?'), 'Result= Call barred?' (Yes leads to 'Set negative response: Call barred'), and 'Result= Call allowed?' (No leads to 'Set negative response: CUG reject'). All negative responses lead to 'Result:= Fail'. Success leads to 'Result:= Pass'. + +Figure 15: Procedure Send\_Alerting\_If\_Required + +![Flowchart for Procedure First_Forwarding_HLR. It starts with a connector, followed by 'Handle_CFU'. A decision 'Result= Fail?' follows. If 'Yes', it goes to 'Set negative response: Forwarding violation' and then to a 'Result:= Fail' connector. If 'No', it goes to 'Result= Forward?'. If 'Yes', it goes to 'Result:= Forward' connector. If 'No', it goes to 'MS not reachable?'. If 'Yes', it goes to 'Handle_CFNRc'. If 'No', it goes to 'Result:= Continue' connector. From 'Handle_CFNRc', a decision 'Result= Fail?' follows. If 'Yes', it goes to 'Set negative response: Forwarding violation' and then to a 'Result:= Fail' connector. If 'No', it goes to 'Result= Forward?'. If 'Yes', it goes to 'Result:= Forward' connector. If 'No', it goes to 'Set negative response: Absent subscriber' and then to a 'Result:= Fail' connector.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +### Procedure First\_Forwarding\_HLR + +FF\_HLR1(1) + +Procedure in the HLR +to handle call forwarding +before interrogation of the VLR + +``` +graph TD; Start([ ]) --> Handle_CFU[Handle_CFU]; Handle_CFU --> Result_Fail_1{Result= Fail?}; Result_Fail_1 -- Yes --> Set_Neg_1[Set negative response: Forwarding violation]; Set_Neg_1 --> Result_Fail_1_end([ ]); Result_Fail_1 -- No --> Result_Forward_1{Result= Forward?}; Result_Forward_1 -- Yes --> Result_Forward_1_end([ ]); Result_Forward_1 -- No --> MS_Not_Reachable{MS not reachable?}; MS_Not_Reachable -- Yes --> Handle_CFNRc[Handle_CFNRc]; MS_Not_Reachable -- No --> Result_Continue[Result:= Continue]; Result_Continue --> Result_Continue_end([ ]); Handle_CFNRc --> Result_Fail_2{Result= Fail?}; Result_Fail_2 -- Yes --> Set_Neg_2[Set negative response: Forwarding violation]; Set_Neg_2 --> Result_Fail_2_end([ ]); Result_Fail_2 -- No --> Result_Forward_2{Result= Forward?}; Result_Forward_2 -- Yes --> Result_Forward_2_end([ ]); Result_Forward_2 -- No --> Set_Neg_3[Set negative response: Absent subscriber]; Set_Neg_3 --> Result_Fail_2_end; Result_Fail_1_end --> Result_Fail_2_end; Result_Fail_2_end --> Result_Fail_3_end([ ]); Result_Fail_3_end --> Result_Fail_4_end([ ]); +``` + +Flowchart for Procedure First\_Forwarding\_HLR. It starts with a connector, followed by 'Handle\_CFU'. A decision 'Result= Fail?' follows. If 'Yes', it goes to 'Set negative response: Forwarding violation' and then to a 'Result:= Fail' connector. If 'No', it goes to 'Result= Forward?'. If 'Yes', it goes to 'Result:= Forward' connector. If 'No', it goes to 'MS not reachable?'. If 'Yes', it goes to 'Handle\_CFNRc'. If 'No', it goes to 'Result:= Continue' connector. From 'Handle\_CFNRc', a decision 'Result= Fail?' follows. If 'Yes', it goes to 'Set negative response: Forwarding violation' and then to a 'Result:= Fail' connector. If 'No', it goes to 'Result= Forward?'. If 'Yes', it goes to 'Result:= Forward' connector. If 'No', it goes to 'Set negative response: Absent subscriber' and then to a 'Result:= Fail' connector. + +Figure 16: Procedure Set\_COLP\_Info\_MSC + +![Flowchart for Procedure PRN_Error_HLR. It starts with a connector, followed by 'CCBS_Report_PRN_Failure' (See TS 23.093). It then enters a series of decision diamonds: 'Negative response=OR not allowed??', 'Negative response=Facility not supported?', 'Negative response=Absent subscriber?', and 'Negative response=No roaming number?'. Each 'Yes' path leads to a 'Set negative response' block. The 'No' paths lead to 'Handle_CFNRc' blocks. From 'Handle_CFNRc', there are 'Result?' decision diamonds with 'Fail', 'Forward', and 'Not reachable' paths. 'Not reachable' leads to 'Super_Charged_SRI_Error_HLR'. 'Fail' and 'Not reachable' from 'Super_Charged_SRI_Error_HLR' lead to 'Set negative response: Forwarding violation'. 'Forward' paths lead to a final 'Result:= Forward' connector. 'Not reachable' from the second 'Result?' leads to 'Set negative response: System failure'. Final 'Result:= Fail' connectors are at the bottom left and bottom right.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +### Procedure PRN\_Error\_HLR + +PRN\_E\_H1(1) + +Procedure in the HLR to handle a negative response for a roaming number request + +``` +graph TD + Start([ ]) --> CCBS[CCBS_Report_PRN_Failure] + CCBS --- CCBS_Note[See TS 23.093] + CCBS --> D1{Negative response=OR not allowed??} + D1 -- Yes --> Set1[Set negative response: OR not allowed] + D1 -- No --> D2{Negative response=Facility not supported?} + D2 -- Yes --> Set2[Set negative response: Facility not supported] + D2 -- No --> D3{Negative response=Absent subscriber?} + D3 -- Yes --> Set3[Set negative response: Absent subscriber?] + D3 -- No --> D4{Negative response=No roaming number?} + D4 -- Yes --> Set4[Set negative response: System failure] + D4 -- No --> H1[Handle_CFNRc] + H1 --> R1{Result?} + R1 -- Fail --> Set5[Set negative response: Forwarding violation] + R1 -- Forward --> ResF[Result:= Forward] + R1 -- Not reachable --> SC[Super_Charged_SRI_Error_HLR] + SC --> R2{Result?=Purged?} + R2 -- Yes --> Set5 + R2 -- No --> Set6[Set negative response: Absent subscriber] + Set5 --> ResF + Set6 --> ResF + Set1 --> ResF + Set2 --> ResF + Set3 --> ResF + Set4 --> ResF + H2[Handle_CFNRc] --> R3{Result?} + R3 -- Fail --> Set7[Set negative response: Forwarding violation] + R3 -- Forward --> ResF + R3 -- Not reachable --> Set8[Set negative response: System failure] + Set7 --> ResF + Set8 --> ResF + Set5 --> ResL[Result:= Fail] + Set6 --> ResL + Set7 --> ResL + Set8 --> ResR[Result:= Fail] + ResF --> EndF([ ]) + ResL --> EndL([ ]) + ResR --> EndR([ ]) +``` + +Flowchart for Procedure PRN\_Error\_HLR. It starts with a connector, followed by 'CCBS\_Report\_PRN\_Failure' (See TS 23.093). It then enters a series of decision diamonds: 'Negative response=OR not allowed??', 'Negative response=Facility not supported?', 'Negative response=Absent subscriber?', and 'Negative response=No roaming number?'. Each 'Yes' path leads to a 'Set negative response' block. The 'No' paths lead to 'Handle\_CFNRc' blocks. From 'Handle\_CFNRc', there are 'Result?' decision diamonds with 'Fail', 'Forward', and 'Not reachable' paths. 'Not reachable' leads to 'Super\_Charged\_SRI\_Error\_HLR'. 'Fail' and 'Not reachable' from 'Super\_Charged\_SRI\_Error\_HLR' lead to 'Set negative response: Forwarding violation'. 'Forward' paths lead to a final 'Result:= Forward' connector. 'Not reachable' from the second 'Result?' leads to 'Set negative response: System failure'. Final 'Result:= Fail' connectors are at the bottom left and bottom right. + +Figure 17: Procedure Handle\_AoC\_MO\_MSC + +![Flowchart for Procedure Forward_CUG_Check. It starts with a connector, followed by a decision 'CUG provisioned for forwarding subscriber against requested basic service'. If 'No', it checks 'CUG info provided in routing information request'. If 'Yes', it proceeds to 'Result:= Call allowed'. If 'No', it proceeds to 'Perform Forwarding CUG authorisation'. If 'Yes', it proceeds to 'CUG authorisation result'. If 'Pass', it proceeds to 'Result:= Call allowed'. If 'Fail', it proceeds to 'Result:= Call barred'. Both 'Result:= Call allowed' paths lead to an 'Update CUG info' block, which then leads to a merge connector. The 'Result:= Call barred' path also leads to the merge connector.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +### Procedure Forward\_CUG\_Check + +FWD\_CUG1(1) + +``` +graph TD; Start([ ]) --> D1{CUG provisioned for forwarding subscriber against requested basic service}; D1 -- No --> D2{CUG info provided in routing information request}; D1 -- Yes --> P1[Perform Forwarding CUG authorisation]; P1 --> D3{CUG authorisation result}; D2 -- Yes --> R1[Result:= Call allowed]; D2 -- No --> P1; D3 -- Pass --> R2[Result:= Call allowed]; D3 -- Fail --> R3[Result:= Call barred]; R2 --> U[Update CUG info]; R3 --> Merge(( )); U --> Merge; Merge --> End(( )); +``` + +Procedure to carry out CUG authorisation check for a forwarded call + +CUG provisioned for forwarding subscriber against requested basic service + +CUG info provided in routing information request + +Perform Forwarding CUG authorisation + +As defined in TS 23.085 + +CUG authorisation result + +Result:= Call allowed + +Result:= Call barred + +Update CUG info + +As defined in TS 23.085 + +Flowchart for Procedure Forward\_CUG\_Check. It starts with a connector, followed by a decision 'CUG provisioned for forwarding subscriber against requested basic service'. If 'No', it checks 'CUG info provided in routing information request'. If 'Yes', it proceeds to 'Result:= Call allowed'. If 'No', it proceeds to 'Perform Forwarding CUG authorisation'. If 'Yes', it proceeds to 'CUG authorisation result'. If 'Pass', it proceeds to 'Result:= Call allowed'. If 'Fail', it proceeds to 'Result:= Call barred'. Both 'Result:= Call allowed' paths lead to an 'Update CUG info' block, which then leads to a merge connector. The 'Result:= Call barred' path also leads to the merge connector. + +Figure 18: Procedure Send\_Access\_Connect\_If\_Required + +![Flowchart for Procedure Check_IC_Barring. It starts with a connector, then checks if Operator determined BAIC is imposed. If Yes, it leads to a junction. If No, it checks if Operator determined BIC-Roam is imposed. If Yes, it leads to a junction. If No, it checks if MS is registered in HPLMN country. If Yes, it goes to connector 1. If No, it leads to a junction. Next, it checks if Operator determined BIC-RoamHZ is imposed. If Yes, it leads to a junction. If No, it checks if MS is registered in HPLMN zone. If Yes, it leads to a junction. If No, it leads to a junction. All junctions lead to a box 'Result:= Call barred (ODB)' which then leads to an end connector.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +### Procedure Check\_IC\_Barring + +CIB1(2) + +Procedure to check call request against SS barring and ODB categories + +``` +graph TD; Start([ ]) --> BAIC{Operator determined BAIC imposed?}; BAIC -- Yes --> Junction1(( )); BAIC -- No --> BICRoam{Operator determined BIC-Roam imposed?}; BICRoam -- Yes --> Junction1; BICRoam -- No --> HPLMNCountry{MS registered in HPLMN country?}; HPLMNCountry -- Yes --> C1((1)); HPLMNCountry -- No --> Junction1; Junction1 --> BICRoamHZ{Operator determined BIC-RoamHZ imposed?}; BICRoamHZ -- Yes --> Junction1; BICRoamHZ -- No --> HPLMNZone{MS registered in HPLMN zone?}; HPLMNZone -- Yes --> Junction1; HPLMNZone -- No --> Junction1; Junction1 --> Result[Result:= Call barred (ODB)]; Result --> End(( )); +``` + +Flowchart for Procedure Check\_IC\_Barring. It starts with a connector, then checks if Operator determined BAIC is imposed. If Yes, it leads to a junction. If No, it checks if Operator determined BIC-Roam is imposed. If Yes, it leads to a junction. If No, it checks if MS is registered in HPLMN country. If Yes, it goes to connector 1. If No, it leads to a junction. Next, it checks if Operator determined BIC-RoamHZ is imposed. If Yes, it leads to a junction. If No, it checks if MS is registered in HPLMN zone. If Yes, it leads to a junction. If No, it leads to a junction. All junctions lead to a box 'Result:= Call barred (ODB)' which then leads to an end connector. + +Figure 19: Procedure OCH\_VLRTCH\_Check + +### 7.1.2 Functional requirements of VLR + +7.1.2.1 Process OCH\_VLR + +7.1.2.2 Procedure Process\_Access\_Request\_VLR + +Sheet 1: it is a network operator decision (subject to MoU requirements) how often an MS should be authenticated. + +Sheet 1: it is a network operator decision (subject to MoU requirements) how often an MS should be authenticated. + +Sheet 2: the process Subscriber\_Present\_VLR is described in 3GPP TS 29.002 [29]. + +Sheet 2: it is a network operator decision (subject to MoU requirements) whether a GSM connection should be ciphered. A UMTS connection shall always be ciphered. + +Sheet 3: it is a network operator decision (subject to MoU requirements) how often an IMEI should be checked. + +Sheet 3, sheet 4, sheet 5: the procedure CCBS\_Report\_MS\_Activity is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 5: it is a network operator decision whether emergency calls are allowed from an ME with no SIM. + +#### 7.1.2.3 Procedure OG\_Call\_Subscription\_Check\_VLR + +Sheet 1: it is an implementation option to carry out the check for operator determined barring of all outgoing calls before the check on provisioning of the requested basic service. + +Sheet 1: the procedure Check\_OG\_Multicall\_VLR is specific to Multicall; it is specified in 3GPP TS 23.135 [25]. If the VMSC does not support Multicall, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 1: the procedure OG\_CUG\_Check is specific to CUG. If the VLR does not support CUG, processing continues from the "Yes" exit of the test "Result=Call allowed?". + +Sheet 1: the procedure Get\_LI\_Subscription\_Info\_MO\_VLR is specific to CLIR and COLP. If the VLR supports neither CLIR nor COLP, the procedure call is omitted. + +Sheet 1: the procedure Get\_AoC\_Subscription\_Info\_VLR is specific to AoC. + +Sheet 1: the procedure UUS\_OCH\_Check\_Provision is specific to UUS; it is specified in 3GPP TS 23.087 [20]. If the VMSC does not support UUS, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 2: the procedure CAMEL\_OCH\_VLR is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the VLR does not support CAMEL, processing continues from connector 1 to the call to the procedure Check\_OG\_Barring. + +Sheet 2: the negative response "call barred" indicates whether the reason is operator determined barring or supplementary service barring, according to the result returned by the procedure Check\_OG\_Barring. + +#### 7.1.2.4 Procedure Obtain\_Identity\_VLR + +It is a network operator decision whether open (non ciphered) identification of the MS by its IMSI is allowed. + +#### 7.1.2.5 Procedure Obtain\_IMSI\_VLR + +#### 7.1.2.6 Procedure Authenticate\_VLR + +Sheet 1: the number of unused authentication sets which triggers the VLR to request further authentication sets from the HLR is an operator option. + +#### 7.1.2.7 Procedure Obtain\_Authentication\_Sets\_VLR + +#### 7.1.2.8 Procedure Start\_Tracing\_VLR + +#### 7.1.2.9 Procedure Check\_IMEI\_VLR + +If the response from the EIR to a request to check an IMEI is: + +- blacklisted, then service is not granted; +- greylisted, then service is granted, but the network operator may decide to initiate tracing; +- whitelisted, then service is granted. + +#### 7.1.2.10 Procedure Obtain\_IMEI\_VLR + +#### 7.1.2.11 Process Fetch\_Authentication\_Sets\_VLR + +#### 7.1.2.12 Procedure Check\_BAOC + +Sheet 1: if the VLR receives an Abort message from the MSC while it is awaiting a response from the process MAF017, the message is saved for handling after return from the procedure. + +#### 7.1.2.13 Procedure OG\_CUG\_Check + +If the VLR receives an Abort message from the MSC while it is awaiting a response from the process MAF014, the message is saved for handling after return from the procedure. + +#### 7.1.2.14 Procedure Get\_LI\_Subscription\_Info\_MO\_VLR + +If the VLR does not support CLIR, it omits the signal interchange with the process CLIR\_MAF003. + +If the VLR does not support COLP, it omits the signal interchange with the process COLP\_MAF005. + +If the VLR receives an Abort message from the MSC while it is awaiting a response from the process CLIR\_MAF003 or the process COLP\_MAF005, the message is saved for handling after return from the procedure. + +#### 7.1.2.15 Procedure Get\_AoC\_Subscription\_Info\_VLR + +The indicator of whether or not AoC is provisioned is global data which can be read by the parent process. + +#### 7.1.2.16 Procedure Check\_OG\_Barring + +Sheet 3: if the VLR receives an Abort message from the MSC while it is awaiting a response from the process MAF018 or MAF020 (see 3GPP TS 23.088 [21]), the message is saved for handling after return from the procedure. + +#### 7.1.2.17 Process Update\_Location\_VLR + +The procedure Update\_HLR\_VLR is described in 3GPP TS 23.012 [6]. + +![Flowchart for Check_IC_Barring procedure](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +procedure Check\_IC\_Barring + +C IB 2(2) + +Procedure to check call request against SS barring and ODB categories + +``` +graph TD; Start((1)) --> Init1{{Initiate handling of BAIC}}; Init1 --> To1[To process MAF022]; Init1 --> Wait1([Wait_For_BAIC_Response]); Wait1 --> Cont1{{Continue call handling}}; Cont1 --> From1[From process MAF022]; Cont1 --> Dec1{Call barred?}; Dec1 -- Yes --> Res1[Result:= Call barred (SS barring)]; Res1 --> End1(( )); Dec1 -- No --> Init2{{Initiate handling of BIC-Roam}}; Init2 --> To2[To process MAF023]; Init2 --> Wait2([Wait_For_BIC-Roam_Response]); Wait2 --> Cont2{{Continue call handling}}; Cont2 --> From2[From process MAF023]; Cont2 --> Dec2{Call barred?}; Dec2 -- Yes --> Res2[Result:= Call barred (ACR)]; Res2 --> End2(( )); Dec2 -- No --> Init3{{Initiate handling of ACR}}; Init3 --> To3[To process MAF024]; Init3 --> Wait3([Wait_For_ACR_Response]); Wait3 --> Cont3{{Continue call handling}}; Cont3 --> From3[From process MAF024]; Cont3 --> Dec3{Call barred?}; Dec3 -- Yes --> Res2; Dec3 -- No --> Res3[Result:= Call allowed]; Res3 --> End3(( )); +``` + +The flowchart illustrates the 'Check\_IC\_Barring' procedure. It begins with a start node '1' leading to 'Initiate handling of BAIC', which connects to 'To process MAF022'. This is followed by 'Wait\_For\_BAIC\_Response' and 'Continue call handling' (receiving input from 'From process MAF022'). A decision diamond 'Call barred?' follows. If 'Yes', it leads to 'Result:= Call barred (SS barring)' and an end node. If 'No', it proceeds to 'Initiate handling of BIC-Roam', which connects to 'To process MAF023'. This is followed by 'Wait\_For\_BIC-Roam\_Response' and 'Continue call handling' (receiving input from 'From process MAF023'). Another decision diamond 'Call barred?' follows. If 'Yes', it leads to 'Result:= Call barred (ACR)' and an end node. If 'No', it proceeds to 'Initiate handling of ACR', which connects to 'To process MAF024'. This is followed by 'Wait\_For\_ACR\_Response' and 'Continue call handling' (receiving input from 'From process MAF024'). A third decision diamond 'Call barred?' follows. If 'Yes', it leads to the 'Result:= Call barred (ACR)' path. If 'No', it leads to 'Result:= Call allowed' and an end node. + +Flowchart for Check\_IC\_Barring procedure + +Figure 7.1.2.1: Process OCH\_VLR + +![Flowchart for Procedure IC_CUG_Check. It starts with a connector, followed by a decision 'HLR supports CUG?'. If 'No', it goes to 'SRI contains CUG info?'. If 'Yes', it goes to 'incoming call'. From 'SRI contains CUG info?', if 'No', it goes to 'Result:= Call allowed'. If 'Yes', it goes to 'Outgoing Access present?'. If 'No', it goes to 'Result:= Call barred (cause)'. If 'Yes', it goes to 'Wait_For_CUG_Response'. From 'Wait_For_CUG_Response', it branches to 'reject call (cause)', 'response to call request', and 'complete call (conditional CUG info)'. All three lead to 'Result:= Call allowed'. All three 'Result' boxes lead to a final connector.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +### Procedure IC\_CUG\_Check + +IC\_CUG1(1) + +Procedure to carry out CUG authorisation check for an incoming (MT) call + +Signals to/from the right are to/from the process CUG\_MAF015 + +``` +graph TD; Start([ ]) --> HLR{HLR supports CUG?}; HLR -- No --> SRI{SRI contains CUG info?}; HLR -- Yes --> incoming[incoming call]; SRI -- No --> Result1[Result:= Call allowed]; SRI -- Yes --> Access{Outgoing Access present?}; Access -- No --> Result2[Result:= Call barred (cause)]; Access -- Yes --> Wait[Wait_For_CUG_Response]; incoming --> Wait; Wait --> Reject[/reject call (cause)/]; Wait --> Response[/response to call request/]; Wait --> Complete[/complete call (conditional CUG info)/]; Reject --> Result3[Result:= Call allowed]; Response --> Result3; Complete --> Result3; Result1 --> End(( )); Result2 --> End; Result3 --> End; +``` + +Flowchart for Procedure IC\_CUG\_Check. It starts with a connector, followed by a decision 'HLR supports CUG?'. If 'No', it goes to 'SRI contains CUG info?'. If 'Yes', it goes to 'incoming call'. From 'SRI contains CUG info?', if 'No', it goes to 'Result:= Call allowed'. If 'Yes', it goes to 'Outgoing Access present?'. If 'No', it goes to 'Result:= Call barred (cause)'. If 'Yes', it goes to 'Wait\_For\_CUG\_Response'. From 'Wait\_For\_CUG\_Response', it branches to 'reject call (cause)', 'response to call request', and 'complete call (conditional CUG info)'. All three lead to 'Result:= Call allowed'. All three 'Result' boxes lead to a final connector. + +Figure 7.1.2.2a: Procedure Process\_Access\_Request\_VLR (sheet 1) + +![Flowchart for Procedure Handle_CFU. It starts with a connector, followed by CAMEL_CHECK_SII2_CDTI (referencing TS 23.078). A decision 'Result = Pass?' follows. If 'Yes', it proceeds to 'initiate handling of CFU', then 'Wait_For_CFU_Result', then 'continue call handling'. A second decision 'Error?' follows. If 'Yes', it goes to 'Result= Fail'. If 'No', it checks 'Normal call?'. If 'Normal call?' is 'Yes', it goes to 'Result= Continue'. If 'Normal call?' is 'No', it goes to 'Result= Forward'. All three result boxes ('Fail', 'Forward', 'Continue') lead to a common exit connector. Callouts indicate this is an HLR procedure for unconditional call forwarding and that signals are from/to the MAF007 process.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +### Procedure Handle\_CFU + +H\_CFU1(1) + +``` +graph TD; Start([ ]) --> CAMEL[CAMEL_CHECK_SII2_CDTI]; CAMEL --- Note1[See TS 23.078]; CAMEL --> Pass{Result = Pass?}; Pass -- Yes --> Init[initiate handling of CFU]; Pass -- No --> Continue[Result= Continue]; Init --> Wait[Wait_For_CFU_Result]; Wait --> ContinueCall[continue call handling]; ContinueCall --> Error{Error?}; Error -- Yes --> Fail[Result= Fail]; Error -- No --> Normal{Normal call?}; Normal -- Yes --> Continue; Normal -- No --> Forward[Result= Forward]; Fail --> End(( )); Forward --> End; Continue --> End; +``` + +Procedure in the HLR to handle Call Forwarding Unconditional + +Signals to/from the right are to/from the process MAF007 + +Flowchart for Procedure Handle\_CFU. It starts with a connector, followed by CAMEL\_CHECK\_SII2\_CDTI (referencing TS 23.078). A decision 'Result = Pass?' follows. If 'Yes', it proceeds to 'initiate handling of CFU', then 'Wait\_For\_CFU\_Result', then 'continue call handling'. A second decision 'Error?' follows. If 'Yes', it goes to 'Result= Fail'. If 'No', it checks 'Normal call?'. If 'Normal call?' is 'Yes', it goes to 'Result= Continue'. If 'Normal call?' is 'No', it goes to 'Result= Forward'. All three result boxes ('Fail', 'Forward', 'Continue') lead to a common exit connector. Callouts indicate this is an HLR procedure for unconditional call forwarding and that signals are from/to the MAF007 process. + +Figure 7.1.2.2b: Procedure Process\_Access\_Request\_VLR (sheet 2) + +![Flowchart for Procedure Handle_CFNRC. It starts with a connector, followed by a CAMEL_CHECK_SI2_CDTI block (referencing TS 23.078). A decision 'Result = Pass?' follows. If 'No', it goes to 'Result= Not reachable'. If 'Yes', it proceeds to 'initiate handling of CFNRC', then 'Wait_For_CFNRC_Result', and 'continue call handling'. A decision 'Error?' follows. If 'Yes', it goes to 'Result= Fail'. If 'No', it checks 'Mobile subscriber not reachable?'. If 'Yes', it goes to 'Result= Not reachable'. If 'No', it goes to 'Result= Forward'. All three result blocks converge to a final connector.](5e9af8986a5845504f251d3079da8078_img.jpg) + +### Procedure Handle\_CFNRC + +H\_CFNRC1(1) + +``` +graph TD; Start([ ]) --> CAMEL[CAMEL_CHECK
_SI2_CDTI]; CAMEL --- Note1[See TS 23.078]; CAMEL --> Pass{Result = Pass?}; Pass -- No --> NotReachable[Result= Not reachable]; Pass -- Yes --> Init[initiate handling of CFNRC]; Init --> Wait[Wait_For_CFNRC_Result]; Wait --> Continue[continue call handling]; Continue --> Error{Error?}; Error -- Yes --> Fail[Result= Fail]; Error -- No --> NotReachableCheck{Mobile subscriber not reachable?}; NotReachableCheck -- Yes --> NotReachable; NotReachableCheck -- No --> Forward[Result= Forward]; Fail --> End(( )); Forward --> End; NotReachable --> End +``` + +Procedure in the HLR or VLR to handle Call Forwarding on Mobile Subscriber Not Reachable + +Signals to/from the right are to/from the process MAF010 + +Flowchart for Procedure Handle\_CFNRC. It starts with a connector, followed by a CAMEL\_CHECK\_SI2\_CDTI block (referencing TS 23.078). A decision 'Result = Pass?' follows. If 'No', it goes to 'Result= Not reachable'. If 'Yes', it proceeds to 'initiate handling of CFNRC', then 'Wait\_For\_CFNRC\_Result', and 'continue call handling'. A decision 'Error?' follows. If 'Yes', it goes to 'Result= Fail'. If 'No', it checks 'Mobile subscriber not reachable?'. If 'Yes', it goes to 'Result= Not reachable'. If 'No', it goes to 'Result= Forward'. All three result blocks converge to a final connector. + +Figure 7.1.2.2c: Procedure Process\_Access\_Request\_VLR (sheet 3) + +![Flowchart for process Domain_Selection_HLR. It starts with a start symbol, followed by a process block 'Domain_Selection' with a note 'refer to TS 23.221'. A decision diamond asks 'Session to be routed to IMS?'. If 'yes', it goes to 'Result:= to IMS'. If 'no', it goes to 'Result:= to CS'. Both paths lead to a connector symbol.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +process Domain\_Selection\_HLR 1(1) + +procedure in the HLR to determine how to route the session + +``` +graph TD; Start([ ]) --> Domain_Selection[Domain_Selection]; Note[refer to TS 23.221] --- Domain_Selection; Domain_Selection --> Decision{Session to be routed to IMS?}; Decision -- yes --> ResultIMS[Result:= to IMS]; Decision -- no --> ResultCS[Result:= to CS]; ResultIMS --> Connector(( )); ResultCS --> Connector; +``` + +Flowchart for process Domain\_Selection\_HLR. It starts with a start symbol, followed by a process block 'Domain\_Selection' with a note 'refer to TS 23.221'. A decision diamond asks 'Session to be routed to IMS?'. If 'yes', it goes to 'Result:= to IMS'. If 'no', it goes to 'Result:= to CS'. Both paths lead to a connector symbol. + +Figure 7.1.2.2d: Procedure Process\_Access\_Request\_VLR (sheet 4) + +![Flowchart for Process PRN_VLR. The process starts at an 'Idle' state, receives a 'Provide Roaming Number' request, and checks parameters. If parameters pass, it checks for an OR indicator and supported services. If not supported, it sets a negative response. If supported, it converts the PLMN BC to basic service and checks if the service is supported by the VLR. If not, it sets a negative response. If supported, it checks if pre-paging is supported and allowed. If not allowed, it goes to connector 4. If allowed, it checks if the IMSI is known. If not known, it checks the reason in the serving network entity. If the result is purged, it goes to connector 3. If not purged, it goes to connector 1. If the IMSI is known, it checks the MTRF indicator. If present, it sets a negative response (Absent Subscriber) and goes to connector 1. If not present, it goes to connector 2. All negative responses lead to a 'Provide Roaming Number negative response' block, which then returns to the 'Idle' state.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +**Process PRN\_VLR** PRN\_VLR1(8) + +Process in the VLR to handle a request for a roaming number + +Signals to/from the left are to/from the HLR or the old VLR (MT Roaming Forwarding). + +``` + +graph TD + Start([Idle]) --> PRN{Provide Roaming Number} + PRN --> CP[Check Parameters] + CP --> RP{Result=Pass?} + RP -- No --> C1((1)) + RP -- Yes --> OIP{OR indicator present?} + OIP -- No --> PRNR{Provide Roaming Number negative response} + OIP -- Yes --> OS{OR supported?} + OS -- No --> PRNR + OS -- Yes --> CPNB[Convert PLMN BC to basic service] + CPNB --> SS{Service supported by VLR?} + SS -- No --> SNR[Set negative response: Facility not supported] + SNR --> PRNR + SS -- Yes --> PS{Pre-paging supported in VLR?} + PS -- No --> PA{Pre-paging allowed?} + PS -- Yes --> IK{IMSI known in VLR?} + PA -- No --> C4((4)) + PA -- Yes --> IK + IK -- No --> CR[Check Reason In Serving Network Entity] + CR --> STS[See TS 23.116] + CR --> RP2{Result= Purged?} + RP2 -- No --> C5((5)) + RP2 -- Yes --> C1_2((1)) + IK -- Yes --> MIP{MTRF indicator present?} + MIP -- Yes --> SNR2[Set negative response: Absent Subscriber] + SNR2 --> C1_3((1)) + MIP -- No --> C2((2)) + PRNR --> End([Idle]) + +``` + +Flowchart for Process PRN\_VLR. The process starts at an 'Idle' state, receives a 'Provide Roaming Number' request, and checks parameters. If parameters pass, it checks for an OR indicator and supported services. If not supported, it sets a negative response. If supported, it converts the PLMN BC to basic service and checks if the service is supported by the VLR. If not, it sets a negative response. If supported, it checks if pre-paging is supported and allowed. If not allowed, it goes to connector 4. If allowed, it checks if the IMSI is known. If not known, it checks the reason in the serving network entity. If the result is purged, it goes to connector 3. If not purged, it goes to connector 1. If the IMSI is known, it checks the MTRF indicator. If present, it sets a negative response (Absent Subscriber) and goes to connector 1. If not present, it goes to connector 2. All negative responses lead to a 'Provide Roaming Number negative response' block, which then returns to the 'Idle' state. + +Figure 7.1.2.2e: Procedure Process\_Access\_Request\_VLR (sheet 5) + +![Flowchart for Process PRN_VLR (PRN_VLR 2(8)). The process starts at node 2 and checks if subscriber data is dormant. If true, it sets a negative response 'Purged MS' and ends at node 1. If false, it checks if an MT RF indicator is present. If yes, it authorizes MT RF in the VLR and checks the result. If the result is 'Pass', it ends at node 9. If 'Fail', it sends a negative response 'Absent subscriber' to node 1. If the MT RF indicator is not present, it checks if the IMSI is detached. If true, it ends at node 9. If false, it checks if roaming in the LA is allowed. If no, it ends at node 9. If yes, it checks if MT Roaming Retry Supported. If no, it ends at node 9. If yes, it checks if data is confirmed by the HLR. If false, it checks if more authentication sets are needed. If yes, it fetches authentication sets, restores subscriber data, and ends at node 9. If true, it checks if the MSC per VLR is available. If no, it ends at node 9. If yes, it checks if the MSC number is stored. If yes, it uses the stored MSC number for MSRN. If no, it uses the received MSC number for MSRN. Both lead to allocating an MSRN. The process then calls CAMEL SET_SO, stores compatibility info, alerting patterns, and PGAs. It then calls CLI_PRN_VLR, CBSS_Handle_PRN, and provides a roaming numberack. Finally, it checks if MT Roaming Retry Supported or MT RF Indicator present. If yes, it ends at node 6. If no, it goes to Idle.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +**Process PRN\_VLR** PRN\_VLR 2(8) + +Process in the VLR to handle a request for a roaming number + +Signals to the left are to the HLR or the old VLR (MT Roaming Forwarding). + +``` + +graph TD + Start((2)) --> SD{Subscriber data dormant} + SD -- True --> SR1[Set negative response: Purged MS] + SR1 --> End1((1)) + SD -- False --> MT{MT RF Indicator present?} + MT -- Yes --> Auth[Authorize MT RF_VLR] + Auth --> Res{Result} + Res -- Pass --> End9((9)) + Res -- Fail --> SR2[Set negative response: Absent subscriber] + SR2 --> End1 + MT -- False --> IMSI{IMSI detached} + IMSI -- True --> End9 + IMSI -- False --> Roam{Roaming in LA allowed?} + Roam -- No --> End9 + Roam -- Yes --> MTRetry{MT Roaming Retry Supported} + MTRetry -- No --> End9 + MTRetry -- Yes --> DataConf{Data confirmed by HLR?} + DataConf -- False --> MoreAuth{More authentication sets needed?} + MoreAuth -- Yes --> Fetch[Fetch Authentication Sets_VLR] + Fetch --> Restore[Restore Subscriber Data_VLR] + Restore --> End9 + DataConf -- True --> MSCPerVLR{MSC per VLR} + MSCPerVLR -- No --> End9 + MSCPerVLR -- Yes --> MSCNum{Received MSC number = Stored MSC number?} + MSCNum -- Yes --> UseStored[Use stored MSC number for MSRN] + MSCNum -- No --> Confirmed{Confirmed by radio contact} + Confirmed -- True --> UseStored + Confirmed -- False --> UseReceived[Use received MSC number for MSRN] + UseReceived --> Allocate[Allocate MSRN] + UseStored --> Allocate + Allocate --> CAMEL[CAMEL SET_SO] + CAMEL --> StoreCompat[Store compatibility info] + StoreCompat --> StoreAlert[Store Alerting Pattern if received] + StoreAlert --> StorePGA[Store PgA if received and supported] + StorePGA --> CLI[CLI_PRN_VLR] + CLI --> CBSS[CBSS_Handle_PRN] + CBSS --> Provide[Provide Roaming Numberack] + Provide --> MTRetryOrMT{MT Roaming Retry Supported or MT RF Indicator present} + MTRetryOrMT -- Yes --> End6((6)) + MTRetryOrMT -- No --> Idle[Idle] + +``` + +See TS 23.078 + +PLMN BC, ISDN BC, ISDN LLC & ISDN HLC (as available) + +See TS 23.081 + +See TS 23.093 + +Flowchart for Process PRN\_VLR (PRN\_VLR 2(8)). The process starts at node 2 and checks if subscriber data is dormant. If true, it sets a negative response 'Purged MS' and ends at node 1. If false, it checks if an MT RF indicator is present. If yes, it authorizes MT RF in the VLR and checks the result. If the result is 'Pass', it ends at node 9. If 'Fail', it sends a negative response 'Absent subscriber' to node 1. If the MT RF indicator is not present, it checks if the IMSI is detached. If true, it ends at node 9. If false, it checks if roaming in the LA is allowed. If no, it ends at node 9. If yes, it checks if MT Roaming Retry Supported. If no, it ends at node 9. If yes, it checks if data is confirmed by the HLR. If false, it checks if more authentication sets are needed. If yes, it fetches authentication sets, restores subscriber data, and ends at node 9. If true, it checks if the MSC per VLR is available. If no, it ends at node 9. If yes, it checks if the MSC number is stored. If yes, it uses the stored MSC number for MSRN. If no, it uses the received MSC number for MSRN. Both lead to allocating an MSRN. The process then calls CAMEL SET\_SO, stores compatibility info, alerting patterns, and PGAs. It then calls CLI\_PRN\_VLR, CBSS\_Handle\_PRN, and provides a roaming numberack. Finally, it checks if MT Roaming Retry Supported or MT RF Indicator present. If yes, it ends at node 6. If no, it goes to Idle. + +Figure 7.1.2.3a: Procedure OG\_Call\_Subscription\_Check\_VLR (sheet 1) + +![Flowchart for Process PRN_VLR. It starts at connector 3, checks if MSRN is available. If No, it sets a negative response and goes to connector 1. If Yes, it allocates MSRN, calls CAMEL_SET_SOA (see TS 23.078), creates an IMSI record, and checks location info in HLR. If location info is not confirmed in HLR, it sets various flags (radio contact, HLR confirmation, IMSI detached) to False. Then it allocates LMSI (if used by VLR), stores compatibility info (PLMN BC, ISDN BC, ISDN LLC & ISDN HLC), and stores alerting pattern. It then reaches connector 6. From connector 6, it checks if data is confirmed by HLR. If False, it goes to Idle. If True, it checks if more authentication sets are needed. If Yes, it fetches authentication sets, restores subscriber data, and goes to Idle. If No, it provides a roaming number ack, calls CCBS_Handle_PRN (see TS 23.093), stores PgA, calls CLI_PRN_VLR (see TS 23.081), and goes to Idle.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +**Process PRN\_VLR** **PRN\_VLR3(8)** + +Process in the VLR to handle a request for a roaming number + +Signals to the left are to the HLR. + +``` + +graph TD + 3((3)) --> MSRN_Avail{MSRN available} + MSRN_Avail -- No --> NegResp[Set negative response: +No roaming number] + NegResp --> 1((1)) + MSRN_Avail -- Yes --> AllocMSRN[Allocate MSRN] + AllocMSRN --> CAMEL[CAMEL_SET_SOA] + CAMEL -.-> CAMEL_Ref[See TS 23.078] + CAMEL --> IMSIRec[Create IMSI record] + IMSIRec --> LocInfo[Location info confirmed in HLR:=] + LocInfo -.-> LocInfo_Ref[Only if >1 MSC per VLR] + LocInfo -- False --> Flags[Confirmed by radio contact:=False; +Data confirmed by HLR:=False; +IMSI detached:=False] + Flags --> AllocLMSI[Allocate LMSI] + AllocLMSI -.-> AllocLMSI_Ref[If used by VLR] + AllocLMSI --> StoreCompat[Store compatibility info] + StoreCompat -.-> StoreCompat_Ref[PLMN BC, ISDN BC, +ISDN LLC & ISDN HLC +(as available)] + StoreCompat --> StoreAlert[Store Alerting Pattern (if received)] + StoreAlert --> 6((6)) + 6 --> DataConfirmed{Data confirmed by HLR?} + DataConfirmed -- False --> Idle([Idle]) + DataConfirmed -- True --> MoreAuth{More authentication sets needed?} + MoreAuth -- Yes --> FetchAuth[Fetch Authentication Sets_VLR] + FetchAuth --> RestoreData[Restore Subscriber Data_VLR] + RestoreData --> Idle + MoreAuth -- No --> RoamAck{Provide Roaming Number ack} + RoamAck --> CCBS[CCBS_Handle_PRN] + CCBS -.-> CCBS_Ref[See TS 23.093] + CCBS --> StorePgA[Store PgA (if received and supported)] + StorePgA --> CLI[CLI_PRN_VLR] + CLI -.-> CLI_Ref[See TS 23.081] + CLI --> Idle + +``` + +Flowchart for Process PRN\_VLR. It starts at connector 3, checks if MSRN is available. If No, it sets a negative response and goes to connector 1. If Yes, it allocates MSRN, calls CAMEL\_SET\_SOA (see TS 23.078), creates an IMSI record, and checks location info in HLR. If location info is not confirmed in HLR, it sets various flags (radio contact, HLR confirmation, IMSI detached) to False. Then it allocates LMSI (if used by VLR), stores compatibility info (PLMN BC, ISDN BC, ISDN LLC & ISDN HLC), and stores alerting pattern. It then reaches connector 6. From connector 6, it checks if data is confirmed by HLR. If False, it goes to Idle. If True, it checks if more authentication sets are needed. If Yes, it fetches authentication sets, restores subscriber data, and goes to Idle. If No, it provides a roaming number ack, calls CCBS\_Handle\_PRN (see TS 23.093), stores PgA, calls CLI\_PRN\_VLR (see TS 23.081), and goes to Idle. + +Figure 7.1.2.3b: Procedure OG\_Call\_Subscription\_Check\_VLR (sheet 2) + +![Flowchart for Procedure Obtain_Identity_VLR. The process starts at connector 4 and proceeds through a series of decision diamonds and process blocks to handle a roaming number request. It includes checks for dormant subscriber data, IMSI detachment, roaming permissions, and location area ID. Depending on these checks, it may set negative responses (purged or absent subscriber), fetch authentication sets, restore data, search for the MS, or initiate paging via SGSN or directly to the MS. The process ends at connectors 1, 7, or 1 again.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +**Process PRN\_VLR** **PRN\_VLR4(8)** + +Process in the VLR to handle a request for a roaming number + +Signals to the right are to the MSC. + +``` + +graph TD + Start((4)) --> D1{Subscriber data dormant} + D1 -- True --> P1[Set negative response: Purged MS] + P1 --> End1((1)) + D1 -- False --> D2{IMSI detached?} + D2 -- Yes --> D3{Roaming in LA allowed?} + D2 -- No --> D4{Location area ID known?} + D3 -- Yes --> D4 + D3 -- No --> D4 + D4 -- Yes --> D5{Data confirmed by HLR?} + D4 -- No --> D6{Paging via SGSN possible?} + D5 -- True --> D7{Result=Pass?} + D5 -- False --> D8{More authentication sets needed?} + D8 -- Yes --> P2[Fetch Authentication Sets_VLR] + P2 --> P3[Restore Subscriber Data_VLR] + P3 --> D7 + D6 -- Yes --> P4[Set Paging via SGSN possible] + P4 --> P5[Page MS] + P5 --> Note1[Page type=circuit-switched call] + Note1 --> P6[Wait_For_Access_Request] + P6 --> End2((1)) + D7 -- Yes --> D9{Absent subscriber?} + D7 -- No --> D10{Location cancelled?} + D9 -- Yes --> P7[Set negative response: Absent subscriber] + P7 --> End3((1)) + D9 -- No --> D10 + D10 -- Yes --> P8[Set negative response: Purged MS] + P8 --> End4((1)) + D10 -- No --> End5((7)) + +``` + +Flowchart for Procedure Obtain\_Identity\_VLR. The process starts at connector 4 and proceeds through a series of decision diamonds and process blocks to handle a roaming number request. It includes checks for dormant subscriber data, IMSI detachment, roaming permissions, and location area ID. Depending on these checks, it may set negative responses (purged or absent subscriber), fetch authentication sets, restore data, search for the MS, or initiate paging via SGSN or directly to the MS. The process ends at connectors 1, 7, or 1 again. + +Figure 7.1.2.4: Procedure Obtain\_Identity\_VLR + +![Flowchart for Process PRN_VLR. It starts at connector 5, proceeds through Create IMSI record, Location info confirmed in HLR:=False (with note: Only if >1 MSC per VLR), an unnamed block (with notes: Confirmed by radio contact:=False; Data confirmed by HLR:=False; IMSI detached:=False), Allocate LMSI (with note: If used by VLR), Store compatibility info (with note: PLMN BC, ISDN BC, ISDN LLC & ISDN HLC (as available)), Fetch Authentication_Sets_VLR, Restore_Subscriber_Data_VLR, and Search_For_MS_VLR. It then reaches a decision 'Result=Pass?'. If Yes, it goes to 'Absent subscriber?'. If No, it goes to 'Wait_For_Access_Request'. If 'Absent subscriber?' is Yes, it goes to 'Set negative response: Absent subscriber' and then to connector 1. If 'Absent subscriber?' is No, it goes to connector 7.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +### Process PRN\_VLR + +PRN\_VLR5(8) + +Process in the VLR to handle a request for a roaming number + +``` +graph TD; 5((5)) --> Create[Create IMSI record]; Create --> Location[Location info confirmed in HLR:=False]; Location -.-> Note1[Only if >1 MSC per VLR]; Location --> Unnamed[ ]; Unnamed -.-> Note2["Confirmed by radio contact:=False; Data confirmed by HLR:=False; IMSI detached:=False"]; Unnamed --> Allocate[Allocate LMSI]; Allocate -.-> Note3[If used by VLR]; Allocate --> Store[Store compatibility info]; Store -.-> Note4["PLMN BC, ISDN BC, ISDN LLC & ISDN HLC (as available)"]; Store --> Fetch[Fetch Authentication_Sets_VLR]; Fetch --> Restore[Restore_Subscriber_Data_VLR]; Restore --> Search[Search_For_MS_VLR]; Search --> Result{Result=Pass?}; Result -- No --> Wait[Wait_For_Access_Request]; Result -- Yes --> Absent{Absent subscriber?}; Absent -- Yes --> Negative[Set negative response: Absent subscriber]; Negative --> 1((1)); Absent -- No --> 7((7)); +``` + +Flowchart for Process PRN\_VLR. It starts at connector 5, proceeds through Create IMSI record, Location info confirmed in HLR:=False (with note: Only if >1 MSC per VLR), an unnamed block (with notes: Confirmed by radio contact:=False; Data confirmed by HLR:=False; IMSI detached:=False), Allocate LMSI (with note: If used by VLR), Store compatibility info (with note: PLMN BC, ISDN BC, ISDN LLC & ISDN HLC (as available)), Fetch Authentication\_Sets\_VLR, Restore\_Subscriber\_Data\_VLR, and Search\_For\_MS\_VLR. It then reaches a decision 'Result=Pass?'. If Yes, it goes to 'Absent subscriber?'. If No, it goes to 'Wait\_For\_Access\_Request'. If 'Absent subscriber?' is Yes, it goes to 'Set negative response: Absent subscriber' and then to connector 1. If 'Absent subscriber?' is No, it goes to connector 7. + +Figure 7.1.2.5: Procedure Obtain\_IMSI\_VLR + +![Flowchart for Process PRN_VLR (PRN_VLR6(8)). The process starts with 'Wait_For_Access_Request'. It branches into three main paths: 1) 'Page MS via SGSN' leading to 'Page MS' (To SGSN) and 'Wait_For_Access_Request'. 2) 'Process Access Request' leading to 'MSRN available?'. 3) 'Page MS negative response' leading to 'MT Roaming Forwarding supported?'. The 'MSRN available?' path leads to 'MSC per VLR' and then to 'Allocate MSRN', 'CAMEL_SET_SO_A', 'Store compatibility info', 'Store Alerting Pattern (if received)', 'CLI_PRN_VLR', 'CCBS_Handle_PRN', and 'Provide Roaming Number ack' (connector 8). The 'MT Roaming Forwarding supported?' path leads to 'location cancelled with new VLR address?'. If 'Yes', it leads to 'Provide Roaming Number (MTRF Indicator)', 'Wait_For_MSRN', 'Provide Roaming Number Ack', and 'include MSRN'. If 'No', it leads to 'to New VLR' and 'Provide Roaming Number Negative Response'. The 'Busy subscriber?' and 'Absent Subscriber?' paths lead to connectors 7 and 1 respectively, with various negative response handling steps.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +**Process PRN\_VLR** + +Process in the VLR to handle a request for a roaming number + +**PRN\_VLR6(8)** + +Signals to the left are to the HLR; signals to/from the right are to/from the MSC or to/from the new VLR unless shown otherwise. + +``` + +graph TD + Start([Wait_For_Access_Request]) --> Branch1(( )) + Branch1 --> PMS[Page MS via SGSN] + Branch1 --> PAR[Process Access Request] + Branch1 --> PMNR[Page MS negative response] + + PMS --> PageMS[Page MS] + PageMS --> ToSGSN[To SGSN] + PageMS --> WFA[Wait_For_Access_Request] + + PAR --> MSRN_Avail{MSRN available?} + MSRN_Avail -- No --> NegResp[Set negative response: System failure] + MSRN_Avail -- Yes --> MSC_per_VLR{MSC per VLR} + + MSC_per_VLR -- >1 Yes --> RecMSC{Received MSC number= Stored MSC number?} + RecMSC -- No --> Confirmed{Confirmed by radio contact} + Confirmed -- True --> UseStored[Use stored MSC number for MSRN] + Confirmed -- False --> UseReceived[Use received MSC number for MSRN] + RecMSC -- Yes --> UseReceived + + UseReceived --> Allocate[Allocate MSRN] + Allocate --> CAMEL[CAMEL_SET_SO_A] + CAMEL --> StoreComp[Store compatibility info] + StoreComp --> StoreAlert[Store Alerting Pattern if received] + StoreAlert --> CLI[CLI_PRN_VLR] + CLI --> CCBS[CCBS_Handle_PRN] + CCBS --> ProvideAck[Provide Roaming Number ack] + ProvideAck --> Connector8((8)) + + PMNR --> MT_Roam{MT Roaming Forwarding supported?} + MT_Roam -- No --> ToNewVLR[to New VLR] + ToNewVLR --> NegResp2[Provide Roaming Number Negative Response] + NegResp2 --> NegResp3[Provide Roaming Number Negative Response] + NegResp3 --> Idle([Idle]) + + MT_Roam -- Yes --> LocCancelled{location cancelled with new VLR address?} + LocCancelled -- Yes --> ProvideRN[Provide Roaming Number MTRF Indicator] + ProvideRN --> WaitMSRN[Wait_For_MSRN] + WaitMSRN --> ProvideAck2[Provide Roaming Number Ack] + ProvideAck2 --> IncludeMSRN[include MSRN] + + NegResp --> NegResp4[Process Access Request negative response] + NegResp4 --> Busy{Busy subscriber?} + Busy -- Yes --> Connector7((7)) + Busy -- No --> Absent{Absent Subscriber?} + Absent -- Yes --> NegResp5[Set negative response: Absent subscriber] + Absent -- No --> NegResp6[Set negative response: No roaming number] + NegResp5 --> Connector1((1)) + NegResp6 --> Connector1 + +``` + +Flowchart for Process PRN\_VLR (PRN\_VLR6(8)). The process starts with 'Wait\_For\_Access\_Request'. It branches into three main paths: 1) 'Page MS via SGSN' leading to 'Page MS' (To SGSN) and 'Wait\_For\_Access\_Request'. 2) 'Process Access Request' leading to 'MSRN available?'. 3) 'Page MS negative response' leading to 'MT Roaming Forwarding supported?'. The 'MSRN available?' path leads to 'MSC per VLR' and then to 'Allocate MSRN', 'CAMEL\_SET\_SO\_A', 'Store compatibility info', 'Store Alerting Pattern (if received)', 'CLI\_PRN\_VLR', 'CCBS\_Handle\_PRN', and 'Provide Roaming Number ack' (connector 8). The 'MT Roaming Forwarding supported?' path leads to 'location cancelled with new VLR address?'. If 'Yes', it leads to 'Provide Roaming Number (MTRF Indicator)', 'Wait\_For\_MSRN', 'Provide Roaming Number Ack', and 'include MSRN'. If 'No', it leads to 'to New VLR' and 'Provide Roaming Number Negative Response'. The 'Busy subscriber?' and 'Absent Subscriber?' paths lead to connectors 7 and 1 respectively, with various negative response handling steps. + +Figure 7.1.2.6a: Procedure Authenticate\_VLR (sheet 1) + +![Flowchart for Process PRN_VLR. It starts at connector 7, checks if MSRN is available. If no, it sets a negative response and goes to connector 1. If yes, it checks MSC per VLR. If multiple MSCs, it checks if received MSC number matches stored. If not, it checks if confirmed by radio contact. If confirmed, it uses stored MSC number; otherwise, it uses received MSC number. Both paths lead to Allocate MSRN. Subsequent steps include CAMEL_SET_SO_A, Store compatibility info, Store Alerting Pattern, CLI_PRN_VLR, CCBS_Handle_PRN, Provide Roaming Number ack, and finally Idle. Notes include 'Process in the VLR to handle a request for a roaming number', 'Signals to the left are to the HLR.', and various 'See TS' references.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +### Process PRN\_VLR + +PRN\_VLR7(8) + +``` +graph TD; 7((7)) --> MSRN_Avail{MSRN available?}; MSRN_Avail -- No --> NegResp[Set negative response: No roaming number]; NegResp --> 1((1)); MSRN_Avail -- Yes --> MSC_Per_VLR{MSC per VLR}; MSC_Per_VLR -- Yes --> MultipleMSC{>1}; MultipleMSC -- Yes --> RecMSC{Received MSC number= Stored MSC number?}; MultipleMSC -- No --> Confirmed{Confirmed by radio contact}; MultipleMSC -- False --> UseRec[Use received MSC number for MSRN]; MultipleMSC -- True --> UseStore[Use stored MSC number for MSRN]; MSC_Per_VLR -- 1 --> UseRec; MSC_Per_VLR -- >1 --> UseStore; UseRec --> Allocate[Allocate MSRN]; UseStore --> Allocate; Allocate --> CAMEL[CAMEL_SET_SO_A]; CAMEL --> StoreComp[Store compatibility info]; StoreComp --> StoreAlert[Store Alerting Pattern if received]; StoreAlert --> CLI[CLI_PRN_VLR]; CLI --> CCBS[CCBS_Handle_PRN]; CCBS --> RoamAck{Provide Roaming Number ack}; RoamAck --> Idle([Idle]); +``` + +Process in the VLR to handle a request for a roaming number + +Signals to the left are to the HLR. + +See TS 23.078 + +PLMN BC, ISDN BC, ISDN LLC & ISDN HLC (as available) + +See TS 23.081 + +See TS 23.093 + +PAR pending:=False; PAR successful:=False; Fatal PAR error:=False + +Flowchart for Process PRN\_VLR. It starts at connector 7, checks if MSRN is available. If no, it sets a negative response and goes to connector 1. If yes, it checks MSC per VLR. If multiple MSCs, it checks if received MSC number matches stored. If not, it checks if confirmed by radio contact. If confirmed, it uses stored MSC number; otherwise, it uses received MSC number. Both paths lead to Allocate MSRN. Subsequent steps include CAMEL\_SET\_SO\_A, Store compatibility info, Store Alerting Pattern, CLI\_PRN\_VLR, CCBS\_Handle\_PRN, Provide Roaming Number ack, and finally Idle. Notes include 'Process in the VLR to handle a request for a roaming number', 'Signals to the left are to the HLR.', and various 'See TS' references. + +Figure 7.1.2.6b: Procedure Authenticate\_VLR (sheet 2) + +![Flowchart for Process PRN_VLR. It starts at node 8, sets PAR pending to True, sends a Process Access Request VLR, and then checks if the result passes. If yes, it sets PAR successful to True, PAR pending to False, reaches PAR Completed, waits for a call arrival, and then handles either a call arrival or a radio connection release to reach an Idle state. If the result does not pass, it sets PAR successful to False, PAR pending to False, and checks for a fatal PAR error. If there is a fatal error, it sets Fatal PAR error to True; otherwise, it sets it to False. Both error states lead to PAR Completed and then Idle.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +### Process PRN\_VLR + +PRN\_VLR8(8) + +Process in the VLR to handle a request for a roaming number + +Signals to/from the left are to/from the process ICH\_VLR; signals to/from the right are to/from the MSC + +``` +graph TD; Start((8)) --> P1[PAR pending:= True]; P1 --> P2[Process Access Request VLR]; P2 --> D1{Result= Pass?}; D1 -- No --> P3[PAR successful:= False]; D1 -- Yes --> P4[PAR successful:= True]; P4 --> P5[PAR pending:= False]; P5 --> D2{PAR Completed}; D2 --> P6[Wait_For_Call_Arrival]; P6 --> C1{{Call arrived}}; C1 --> C2{{Call arrived}}; C2 --> I1([Idle]); P3 --> P7[PAR pending:= False]; P7 --> D3{Fatal PAR error?}; D3 -- No --> P8[Fatal PAR error:= False]; D3 -- Yes --> P9[Fatal PAR error:= True]; P8 --> D4{PAR Completed}; P9 --> D4; D4 --> I2([Idle]); C1 --> R1{{Radio connection released}}; R1 --> P10[PAR successful:= False]; P10 --> P11[Fatal PAR error:= False]; P11 --> I1; +``` + +Flowchart for Process PRN\_VLR. It starts at node 8, sets PAR pending to True, sends a Process Access Request VLR, and then checks if the result passes. If yes, it sets PAR successful to True, PAR pending to False, reaches PAR Completed, waits for a call arrival, and then handles either a call arrival or a radio connection release to reach an Idle state. If the result does not pass, it sets PAR successful to False, PAR pending to False, and checks for a fatal PAR error. If there is a fatal error, it sets Fatal PAR error to True; otherwise, it sets it to False. Both error states lead to PAR Completed and then Idle. + +Figure 7.1.2.7a: Procedure Obtain\_Authentication\_Sets\_VLR (sheet 1) + +![Flowchart for Process Restore_Subscriber_Data_VLR. The process starts with an oval connector, followed by a 'Restore Data' decision diamond. A note on the left indicates this is a process in the VLR to restore subscriber data, and signals are to/from the HLR. The flow then goes to a 'Wait_For_Data' oval. A decision diamond 'Restore Data ack' follows. If 'Restore Data negative response' is received, the process ends with an error symbol. If 'Restore Data ack' is received, the sequence of steps is: 'Update Subscriber Data', 'Update HLR number', 'Update MS Not Reachable indicator' (with a note 'If received from HLR'), and 'Data confirmed by HLR:=True', which ends with an error symbol.](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +### Process Restore\_Subscriber\_Data\_VLR + +RSD\_VLR1(1) + +``` +graph TD; Start([ ]) --> RD{Restore Data}; RD --> WFD([Wait_For_Data]); WFD --> RDA{Restore Data ack}; RDA -- Restore Data negative response --> End1((X)); RDA --> USD[Update Subscriber Data]; USD --> UHN[Update HLR number]; UHN --> UMSNI[Update MS Not Reachable indicator]; UMSNI -- "If received from HLR" --> UMSNI; UMSNI --> DCH[Data confirmed by HLR:=True]; DCH --> End2((X)); +``` + +Process in the VLR to restore subscriber data + +Signals to/from the left are to/from the HLR + +Flowchart for Process Restore\_Subscriber\_Data\_VLR. The process starts with an oval connector, followed by a 'Restore Data' decision diamond. A note on the left indicates this is a process in the VLR to restore subscriber data, and signals are to/from the HLR. The flow then goes to a 'Wait\_For\_Data' oval. A decision diamond 'Restore Data ack' follows. If 'Restore Data negative response' is received, the process ends with an error symbol. If 'Restore Data ack' is received, the sequence of steps is: 'Update Subscriber Data', 'Update HLR number', 'Update MS Not Reachable indicator' (with a note 'If received from HLR'), and 'Data confirmed by HLR:=True', which ends with an error symbol. + +Figure 7.1.2.7b: Procedure Obtain\_Authentication\_Sets\_VLR (sheet 2) + +![Flowchart for Process PSI_VLR. It starts with an 'Idle' state, followed by 'Provide Subscriber Info', 'Check Parameters', and a series of decision diamonds: 'Result= Pass?', 'IMSI known in VLR?', 'Subscriber state requested?', 'IMSI detached?', 'Roaming in LA allowed?', and 'Location info requested?'. It includes process boxes like 'Set subscriber state requested', 'Subscriber state:= Network determined not reachable', 'Location info:= Stored location info', 'Subscriber state:= Assumed idle', 'Obtain Subscriber Info', 'Provide Subscriber Info ack', and 'Provide Subscriber Info negative response'. It ends with 'Wait_For_MSC_Response' or 'Idle' states.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +### Process PSI\_VLR + +Process in the VLR to handle a request from the HLR for subscriber information + +### PSI\_VLR1(2) + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the MSC + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> Provide1[/Provide Subscriber Info/]; Provide1 --> Check[Check Parameters]; Check --> Result{Result= Pass?}; Result -- No --> ProvideNeg[/Provide Subscriber Info negative response/]; Result -- Yes --> IMSIKnown{IMSI known in VLR?}; IMSIKnown -- No --> StateReq1{Subscriber state requested?}; IMSIKnown -- Yes --> StateReq2{Subscriber state requested?}; StateReq1 -- No --> StateAssumed[Subscriber state:= Assumed idle]; StateReq1 -- Yes --> IMSIDetached{IMSI detached?}; IMSIDetached -- Yes --> StateNotReachable[Subscriber state:= Network determined not reachable]; IMSIDetached -- No --> Roaming{Roaming in LA allowed?}; Roaming -- No --> StateNotReachable; Roaming -- Yes --> SetState[Set subscriber state requested]; StateAssumed --> LocationInfoReq{Location info requested?}; StateNotReachable --> LocationInfoReq; LocationInfoReq -- No --> StateAssumed; LocationInfoReq -- Yes --> LocationInfo[Location info:= Stored location info]; LocationInfo --> ProvideAck[/Provide Subscriber Info ack/]; SetState --> Obtain[Obtain Subscriber Info]; Obtain --> Wait[Wait_For_MSC_Response]; ProvideNeg --> Idle2([Idle]); ProvideAck --> Idle3([Idle]); +``` + +Flowchart for Process PSI\_VLR. It starts with an 'Idle' state, followed by 'Provide Subscriber Info', 'Check Parameters', and a series of decision diamonds: 'Result= Pass?', 'IMSI known in VLR?', 'Subscriber state requested?', 'IMSI detached?', 'Roaming in LA allowed?', and 'Location info requested?'. It includes process boxes like 'Set subscriber state requested', 'Subscriber state:= Network determined not reachable', 'Location info:= Stored location info', 'Subscriber state:= Assumed idle', 'Obtain Subscriber Info', 'Provide Subscriber Info ack', and 'Provide Subscriber Info negative response'. It ends with 'Wait\_For\_MSC\_Response' or 'Idle' states. + +Figure 7.1.2.8: Procedure Start\_Tracing\_VLR + +![Flowchart for Process PSI_VLR. It starts with 'Wait_For_MSC_Response', followed by 'Obtain Subscriber Info ack'. A decision 'Subscriber state received?' follows. If 'No', it goes to 'Set subscriber state'. If 'Yes', it goes to 'Active retrieval required?'. If 'No', it goes to 'Provide Subscriber Info ack'. If 'Yes', it goes to another decision 'Location info requested?'. If 'No', it goes to 'Provide Subscriber Info ack'. If 'Yes', it goes to 'Retrieve Location Info_VLR'. Both 'Active_Info_Retrieval_VLR' and 'Retrieve Location Info_VLR' lead to 'Provide Subscriber Info ack', which then leads to 'Idle'.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +### Process PSI\_VLR + +PSI\_VLR2(2) + +``` +graph TD; Start([Wait_For_MSC_Response]) --> Observe{Obtain Subscriber Info ack}; Observe --> Decision1{Subscriber state received?}; Decision1 -- No --> SetState[Set subscriber state]; SetState --> Decision2{Active retrieval required?}; Decision1 -- Yes --> Decision2; Decision2 -- No --> ProvideAck{Provide Subscriber Info ack}; Decision2 -- Yes --> Decision3{Location info requested?}; Decision3 -- No --> ProvideAck; Decision3 -- Yes --> RetrieveInfo[Retrieve Location Info_VLR]; RetrieveInfo --> ProvideAck; ActiveInfo[Active_Info_Retrieval_VLR] --> ProvideAck; ProvideAck --> Idle([Idle]) +``` + +Process in the VLR to handle a request from the HLR for subscriber information + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the MSC + +Flowchart for Process PSI\_VLR. It starts with 'Wait\_For\_MSC\_Response', followed by 'Obtain Subscriber Info ack'. A decision 'Subscriber state received?' follows. If 'No', it goes to 'Set subscriber state'. If 'Yes', it goes to 'Active retrieval required?'. If 'No', it goes to 'Provide Subscriber Info ack'. If 'Yes', it goes to another decision 'Location info requested?'. If 'No', it goes to 'Provide Subscriber Info ack'. If 'Yes', it goes to 'Retrieve Location Info\_VLR'. Both 'Active\_Info\_Retrieval\_VLR' and 'Retrieve Location Info\_VLR' lead to 'Provide Subscriber Info ack', which then leads to 'Idle'. + +Figure 7.1.2.9: Procedure Check\_IMEI\_VLR + +![Flowchart for Retrieve_Location_Info_VLR procedure. It starts with a decision 'Retrieve location info from SGSN?'. If 'Yes', it sends MS information, waits for a response, and then either stores the received info or sends a negative response. If 'No', it stores the stored location info and ends. Notes indicate this is a VLR procedure and signals are from the SGSN.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +### Procedure Retrieve\_Location\_Info\_VLR + +RLI\_VLR1(1) + +``` +graph TD; Start([ ]) --> Decision{Retrieve location info from SGSN?}; Decision -- Yes --> SendMS[Send MS information]; SendMS --> Wait[Wait_For_SGSN_Response]; Wait --> SendNeg[Send MS Information negative response]; Wait --> SendAck[Send MS Information ack]; SendNeg --> StoreNeg[Location info:= Stored location info]; StoreNeg --> EndNeg(( )); SendAck --> StoreAck[Location info:= Received location info]; StoreAck --> Derive[Derive location number, geodetic information and geographical information]; Derive --> EndAck(( )); Decision -- No --> StoreNo[Location info:= Stored location info]; StoreNo --> EndNo(( )); Note1[Procedure in the VLR to retrieve location information for a subscriber]; Note2[Signals to/from the right are to/from the SGSN]; +``` + +Procedure in the VLR to retrieve location information for a subscriber + +Signals to/from the right are to/from the SGSN + +Flowchart for Retrieve\_Location\_Info\_VLR procedure. It starts with a decision 'Retrieve location info from SGSN?'. If 'Yes', it sends MS information, waits for a response, and then either stores the received info or sends a negative response. If 'No', it stores the stored location info and ends. Notes indicate this is a VLR procedure and signals are from the SGSN. + +Figure 7.1.2.10: Procedure Obtain\_IMEI\_VLR + +![Flowchart for Active_Info_Retrieval_VLR procedure. It starts with 'Set information required', followed by a decision 'Paging via SGSN possible?'. If 'No', it goes to 'Location area ID known?'. If 'Yes', it goes to 'Set paging via SGSN possible', then to 'Location area ID known?'. From 'Location area ID known?', if 'No', it goes to 'Search for MS' (with 'Page type= Active information retrieval') and then to 'Wait_For_Search_Result'. If 'Yes', it goes to 'Page MS' (with 'Page type= Active information retrieval') and then to 'Wait_For_Page_Result'.](c07e21a8d65991db04263322f859c94f_img.jpg) + +### Procedure Active\_Info\_Retrieval\_VLR + +AIR\_VLR1(2) + +Procedure in the VLR to retrieve the current location information for a subscriber + +Signals to/from the right are to/from the MSC + +``` +graph TD; Start([ ]) --> SetInfo[Set information required]; SetInfo --> PagingPossible{Paging via SGSN possible?}; PagingPossible -- No --> LocationKnown{Location area ID known?}; PagingPossible -- Yes --> SetPaging[Set paging via SGSN possible]; SetPaging --> LocationKnown; LocationKnown -- No --> SearchMS[Search for MS]; SearchMS --> WaitSearch[Wait_For_Search_Result]; SearchMS --- SearchMSNote[Page type= Active information retrieval]; LocationKnown -- Yes --> PageMS[Page MS]; PageMS --> WaitPage[Wait_For_Page_Result]; PageMS --- PageMSNote[Page type= Active information retrieval]; +``` + +Flowchart for Active\_Info\_Retrieval\_VLR procedure. It starts with 'Set information required', followed by a decision 'Paging via SGSN possible?'. If 'No', it goes to 'Location area ID known?'. If 'Yes', it goes to 'Set paging via SGSN possible', then to 'Location area ID known?'. From 'Location area ID known?', if 'No', it goes to 'Search for MS' (with 'Page type= Active information retrieval') and then to 'Wait\_For\_Search\_Result'. If 'Yes', it goes to 'Page MS' (with 'Page type= Active information retrieval') and then to 'Wait\_For\_Page\_Result'. + +Figure 7.1.2.11: Process Fetch\_Authentication\_Sets\_VLR + +![Flowchart for Procedure Active_Info_Retrieval_VLR. It starts with 'Wait_For_Search_Result' and branches into three paths: 'Search for MS ack', 'Search for MS negative response', and 'Search for MS via SGSN'. The 'Search for MS ack' path includes a 'Roaming in LA allowed?' decision and 'Location info received?' checks. The 'Search for MS negative response' path leads to 'Subscriber state:=Not reachable' and another 'Location info received?' check. The 'Search for MS via SGSN' path leads to 'Page MS' and 'Wait_For_Search_Result'. A second 'Wait_For_Page_Result' block follows, with a 'Page MS ack' path leading to 'Location info received?' checks, and 'Page MS negative response' and 'Page MS via SGSN' paths leading to exit points.](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +### Procedure Active\_Info\_Retrieval\_VLR + +AIR\_VLR2(2) + +Procedure in the VLR to retrieve the current location information for a subscriber + +``` +graph TD + WFSR1([Wait_For_Search_Result]) --> S1[Search for MS ack] + WFSR1 --> S2[Search for MS negative response] + WFSR1 --> S3[Search for MS via SGSN] + S3 --> P1[Page MS] + P1 --> WFSR2([Wait_For_Search_Result]) + S1 --> R{Roaming in LA allowed?} + R -- No --> SS[Subscriber state:=Not reachable] + R -- Yes --> L1{Location info received?} + SS --> L2{Location info received?} + L1 -- Yes --> LI1[Location info:= Received location info] + L1 -- No --> LI2[Location info:= Stored location info] + L2 -- Yes --> LI3[Location info:= Received location info] + L2 -- No --> LI4[Location info:= Stored location info] + LI1 --> E1((X)) + LI2 --> E2((X)) + LI3 --> E3((X)) + LI4 --> E4((X)) + S2 --> E5((X)) + WFSR2 --> PMA[Page MS ack] + WFSR2 --> PMNR[Page MS negative response] + WFSR2 --> PMVSGSN[Page MS via SGSN] + PMVSGSN --> PM2[Page MS] + PM2 --> WPR([Wait_For_Page_Result]) + PMA --> L3{Location info received?} + L3 -- Yes --> LI5[Location info:= Received location info] + L3 -- No --> LI6[Location info:= Stored location info] + LI5 --> E6((X)) + LI6 --> E7((X)) + PMNR --> E8((X)) +``` + +Flowchart for Procedure Active\_Info\_Retrieval\_VLR. It starts with 'Wait\_For\_Search\_Result' and branches into three paths: 'Search for MS ack', 'Search for MS negative response', and 'Search for MS via SGSN'. The 'Search for MS ack' path includes a 'Roaming in LA allowed?' decision and 'Location info received?' checks. The 'Search for MS negative response' path leads to 'Subscriber state:=Not reachable' and another 'Location info received?' check. The 'Search for MS via SGSN' path leads to 'Page MS' and 'Wait\_For\_Search\_Result'. A second 'Wait\_For\_Page\_Result' block follows, with a 'Page MS ack' path leading to 'Location info received?' checks, and 'Page MS negative response' and 'Page MS via SGSN' paths leading to exit points. + +Figure 7.1.2.12: Procedure Check\_BAOC + +![Flowchart for Procedure Authorize_MTRF_VLR. It starts with a connector, followed by a decision 'On-going MAP Update Location procedure'. If 'Yes', it goes to a process 'wait for MAP Update Location response and completion of Location_Update_Completion_VLR procedure'. If 'No', it goes to a decision diamond. The decision diamond has a 'True' path leading to a process box with conditions: '"LA Allowed" flag AND Confirmed by Radio Contact AND Data Confirmed by HLR AND MM LA valid', which then leads to a 'Result:= Pass' box and an exit connector. The 'False' path from the decision diamond leads to a 'Result:= Fail' box and an exit connector.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +**Procedure Authorize\_MTRF\_VLR** AMT\_VLR1(1) + +Procedure in the VLR to authorize an MT Roaming Forwarding request received in Provide Roaming Number from old VLR + +``` +graph TD; Start([ ]) --> Decision1{On-going MAP Update Location procedure}; Decision1 -- Yes --> Process1[wait for MAP Update Location response and completion of Location_Update_Completion_VLR procedure]; Process1 --> Decision2{ }; Decision1 -- No --> Decision2; Decision2 -- True --> Process2[""LA Allowed" flag AND Confirmed by Radio Contact AND Data Confirmed by HLR AND MM LA valid"]; Process2 --> ResultPass[Result:= Pass]; ResultPass --> Exit1(( )); Decision2 -- False --> ResultFail[Result:= Fail]; ResultFail --> Exit2(( )); +``` + +Flowchart for Procedure Authorize\_MTRF\_VLR. It starts with a connector, followed by a decision 'On-going MAP Update Location procedure'. If 'Yes', it goes to a process 'wait for MAP Update Location response and completion of Location\_Update\_Completion\_VLR procedure'. If 'No', it goes to a decision diamond. The decision diamond has a 'True' path leading to a process box with conditions: '"LA Allowed" flag AND Confirmed by Radio Contact AND Data Confirmed by HLR AND MM LA valid', which then leads to a 'Result:= Pass' box and an exit connector. The 'False' path from the decision diamond leads to a 'Result:= Fail' box and an exit connector. + +Figure 7.1.2.13: Procedure OG\_CUG\_Check + +![Flowchart for Process Prepage_MSC. It starts with an 'Idle' state, branches into 'Page MS' and 'Search for MS' paths, both leading to 'Prepaging' messages and decision diamonds. The 'Page MS' path leads to 'Process Access Request MSC' if successful. Both paths lead to 'Start radio guard timer' and 'Wait For Call_Arrival'. From there, it branches into 'Call arrived', 'Radio guard timer expired', and 'Release transaction' paths, all leading to an 'Idle' state.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +### Process Prepage\_MSC + +PP\_MSC1(1) + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> PageMS[/Page MS/]; Idle1 --> SearchMS[/Search for MS/]; PageMS --> PrepagingPageMS[Prepaging Page MS MSC]; SearchMS --> PrepagingSearchMS[Prepaging Search for MS MSC]; PrepagingPageMS --> ResultPass1{Result= Pass?}; PrepagingSearchMS --> ResultPass2{Result= Pass?}; ResultPass1 -- No --> Idle2([Idle]); ResultPass1 -- Yes --> ProcessAccess[Process Access Request MSC]; ResultPass2 -- No --> Idle3([Idle]); ResultPass2 -- Yes --> StartTimer[Start radio guard timer]; ProcessAccess --> ResultPass3{Result= Pass?}; ResultPass3 -- No --> Idle4([Idle]); ResultPass3 -- Yes --> StartTimer; StartTimer --> WaitForCall[Wait For Call_Arrival]; WaitForCall --> CallArrived[/Call arrived/]; WaitForCall --> TimerExpired[/Radio guard timer expired/]; WaitForCall --> ReleaseTrans[/Release transaction/]; CallArrived --> StopTimer[Stop radio guard timer]; StopTimer --> Idle5([Idle]); TimerExpired --> ReleaseTrans1[Release transaction]; ReleaseTrans1 --> RadioReleased1{Radio connection released}; RadioReleased1 --> Idle5; ReleaseTrans --> BSSReleased[BSS released the radio resource]; ReleaseTrans --> RadioReleased2{Radio connection released}; RadioReleased2 --> Idle5; +``` + +Process in the MSC to handle a pre-paging request + +Signals to/from the left are to/from the VLR; signals to the right are to the BSS + +Flowchart for Process Prepage\_MSC. It starts with an 'Idle' state, branches into 'Page MS' and 'Search for MS' paths, both leading to 'Prepaging' messages and decision diamonds. The 'Page MS' path leads to 'Process Access Request MSC' if successful. Both paths lead to 'Start radio guard timer' and 'Wait For Call\_Arrival'. From there, it branches into 'Call arrived', 'Radio guard timer expired', and 'Release transaction' paths, all leading to an 'Idle' state. + +Figure 7.1.2.14: Procedure Get\_LI\_Subscription\_Info\_MO\_VLR + +![Flowchart for Procedure Prepaging_Page_MS_MSC. The process starts with a connector, checks if Location area ID is known. If No, it sets a negative response 'Unknown I AI' and ends. If Yes, it checks if MS connection exists. If No, it checks if paging via SGSN is possible. If Yes, it pages via SGSN, starts a timer, and waits for a response. If No, it pages in the specified location area. If Yes, it sets access connection status to Pass and ends. If Yes, it checks if MS is busy. If Yes, it sets a negative response 'Busy Subscriber' and ends. If No, it sets access connection status to Pass and ends. The 'Wait For Page_Response' block leads to four possible outcomes: Cancel Location (Result: Fail), MS connection established (Result: Pass), Page response timer expired (Result: Fail), and CM Service Request (Result: Fail).](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +### Procedure Prepaging\_Page\_MS\_MSC + +PPPMS\_M1(1) + +Procedure in the MSC to page an MS in a specified location area + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` + + graph TD + Start([ ]) --> L1{Location area ID known?} + L1 -- No --> N1[Set negative response: Unknown I AI] + N1 --> E1(( )) + L1 -- Yes --> L2{MS connection exists?} + L2 -- No --> L3{Paging via SGSN possible?} + L3 -- No --> P1[Page] + P1 --> E2(( )) + L3 -- Yes --> P2[Page MS via SGSN] + P2 --> T1[Start Page response timer] + T1 --> W1[Wait For Page_Response] + W1 --> C1[Cancel Location] + C1 --> N2[Set negative response: Location Cancelled] + N2 --> P3[Page MS negative response] + P3 --> R1[Result:= Fail] + R1 --> E3(( )) + W1 --> M1[MS connection established] + M1 --> S1[Set access connection status] + S1 --> R2[Result:= Pass] + R2 --> E4(( )) + W1 --> T2[Page response timer expired] + T2 --> N3[Set negative response: Absent Subscriber] + N3 --> P4[Page MS negative response] + P4 --> R3[Result:= Fail] + R3 --> E5(( )) + W1 --> CM1[CM Service Request] + CM1 --> CM2[CM Service Request] + CM2 --> N4[Set negative response: Busy Subscriber (NDUB)] + N4 --> P5[Page MS negative response] + P5 --> R4[Result:= Fail] + R4 --> E6(( )) + L2 -- Yes --> L4{MS busy?} + L4 -- Yes --> N5[Set negative response: Busy Subscriber] + N5 --> E7(( )) + L4 -- No --> S2[Set access connection status] + S2 --> R5[Result:= Pass] + R5 --> E8(( )) + +``` + +For circuit-switched call + To process OCH\_MSC + +Flowchart for Procedure Prepaging\_Page\_MS\_MSC. The process starts with a connector, checks if Location area ID is known. If No, it sets a negative response 'Unknown I AI' and ends. If Yes, it checks if MS connection exists. If No, it checks if paging via SGSN is possible. If Yes, it pages via SGSN, starts a timer, and waits for a response. If No, it pages in the specified location area. If Yes, it sets access connection status to Pass and ends. If Yes, it checks if MS is busy. If Yes, it sets a negative response 'Busy Subscriber' and ends. If No, it sets access connection status to Pass and ends. The 'Wait For Page\_Response' block leads to four possible outcomes: Cancel Location (Result: Fail), MS connection established (Result: Pass), Page response timer expired (Result: Fail), and CM Service Request (Result: Fail). + +Figure 7.1.2.15: Procedure Get\_AoC\_Subscription\_Info\_VLR + +![Flowchart for Procedure Prepaging_Search_For_MS_MSC. The process starts with a note 'Procedure in the MSC to page an MS in all location areas'. It enters a loop: 'MS connection exists?' (Yes leads to 'MS busy?'; No leads to 'Paging via SGSN possible?'). 'Paging via SGSN possible?' (Yes leads to 'Page MS via SGSN'; No leads to 'Page'). 'Page' leads to 'Start Page response timer' and 'Wait_For_Page_Response'. 'MS busy?' (Yes leads to 'Set negative response: Busy Subscriber'; No leads to 'Set access connection status'). 'Set access connection status' leads to 'Result:= Pass'. 'Set negative response: Busy Subscriber' leads to 'Page MS negative response' and 'Result:= Fail'. 'Wait_For_Page_Response' leads to three outcomes: 'MS connection established' (leads to 'Set access connection status' and 'Result:= Pass'), 'Page response timer expired' (leads to 'Set negative response: Absent Subscriber', 'Page MS negative response', and 'Result:= Fail'), and 'CM Service Request' (leads to 'For circuit-switched call', 'To process OCH_MSC', 'Set negative response: Busy Subscriber (NDUB)', 'Page MS negative response', and 'Result:= Fail'). All 'Result' blocks lead to an exit symbol.](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +### Procedure Prepaging\_Search\_For\_MS\_MSC + +PPSMS\_M1(1) + +``` +graph TD + Start([Start]) --> MS_Exists{MS connection exists?} + MS_Exists -- Yes --> MS_Busy{MS busy?} + MS_Exists -- No --> Paging_SGSN{Paging via SGSN possible?} + Paging_SGSN -- Yes --> Page_SGSN[/Page MS via SGSN/] + Paging_SGSN -- No --> Page[/Page/] + Page --> Start_Timer[Start Page response timer] + Start_Timer --> Wait_Response((Wait_For_Page_Response)) + MS_Busy -- Yes --> Neg_Resp_Busy[Set negative response: Busy Subscriber] + MS_Busy -- No --> Access_Status[Set access connection status] + Access_Status --> Res_Pass_1[Result:= Pass] + Neg_Resp_Busy --> Neg_Resp_Page[/Page MS negative response/] + Neg_Resp_Page --> Res_Fail_1[Result:= Fail] + Wait_Response --> MS_Established{MS connection established} + MS_Established -- Yes --> Access_Status_2[Set access connection status] + Access_Status_2 --> Res_Pass_2[Result:= Pass] + Wait_Response --> Timer_Expired{Page response timer expired} + Timer_Expired -- Yes --> Neg_Resp_Absent[Set negative response: Absent Subscriber] + Neg_Resp_Absent --> Neg_Resp_Page_2[/Page MS negative response/] + Neg_Resp_Page_2 --> Res_Fail_2[Result:= Fail] + Wait_Response --> CM_Request{CM Service Request} + CM_Request --> For_Circuit[For circuit-switched call] + CM_Request --> To_OCH[To process OCH_MSC] + CM_Request --> Neg_Resp_NDUB[Set negative response: Busy Subscriber (NDUB)] + Neg_Resp_NDUB --> Neg_Resp_Page_3[/Page MS negative response/] + Neg_Resp_Page_3 --> Res_Fail_3[Result:= Fail] +``` + +Procedure in the MSC to page an MS in all location areas + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR + +otherwise + +Paging via SGSN possible? + +In all location areas or in PgA if PgA received and supported + +Flowchart for Procedure Prepaging\_Search\_For\_MS\_MSC. The process starts with a note 'Procedure in the MSC to page an MS in all location areas'. It enters a loop: 'MS connection exists?' (Yes leads to 'MS busy?'; No leads to 'Paging via SGSN possible?'). 'Paging via SGSN possible?' (Yes leads to 'Page MS via SGSN'; No leads to 'Page'). 'Page' leads to 'Start Page response timer' and 'Wait\_For\_Page\_Response'. 'MS busy?' (Yes leads to 'Set negative response: Busy Subscriber'; No leads to 'Set access connection status'). 'Set access connection status' leads to 'Result:= Pass'. 'Set negative response: Busy Subscriber' leads to 'Page MS negative response' and 'Result:= Fail'. 'Wait\_For\_Page\_Response' leads to three outcomes: 'MS connection established' (leads to 'Set access connection status' and 'Result:= Pass'), 'Page response timer expired' (leads to 'Set negative response: Absent Subscriber', 'Page MS negative response', and 'Result:= Fail'), and 'CM Service Request' (leads to 'For circuit-switched call', 'To process OCH\_MSC', 'Set negative response: Busy Subscriber (NDUB)', 'Page MS negative response', and 'Result:= Fail'). All 'Result' blocks lead to an exit symbol. + +Figure 7.1.2.16a: Procedure Check\_OG\_Barring (sheet 1) + +![Flowchart for Process OSI_MSC. The flow starts at an oval, goes to an 'Idle' state (oval), then to 'Obtain Subscriber Info' (parallelogram), then to a decision 'Subscriber state requested?' (diamond). If 'Yes', it goes to 'Set subscriber state' (rectangle) and then to 'Obtain Subscriber Info ack' (parallelogram). If 'No', it bypasses 'Set subscriber state' and goes directly to 'Obtain Subscriber Info ack'. Finally, it returns to an 'Idle' state (oval).](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +**Process OSI\_MSC** + +Process in the MSC to handle a request from the VLR for information on the subscriber's location and state + +**OSI\_MSC1(1)** + +Signals to/from the left are to/from the VLR + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> ObtainInfo[Obtain Subscriber Info]; ObtainInfo --> Decision{Subscriber state requested?}; Decision -- Yes --> SetState[Set subscriber state]; SetState --> ObtainAck[Obtain Subscriber Info ack]; Decision -- No --> ObtainAck; ObtainAck --> Idle2([Idle]); +``` + +Flowchart for Process OSI\_MSC. The flow starts at an oval, goes to an 'Idle' state (oval), then to 'Obtain Subscriber Info' (parallelogram), then to a decision 'Subscriber state requested?' (diamond). If 'Yes', it goes to 'Set subscriber state' (rectangle) and then to 'Obtain Subscriber Info ack' (parallelogram). If 'No', it bypasses 'Set subscriber state' and goes directly to 'Obtain Subscriber Info ack'. Finally, it returns to an 'Idle' state (oval). + +Figure 7.1.2.16b: Procedure Check\_OG\_Barring (sheet 2) + +![Flowchart for Process AIR_MSC. It starts with an oval connector, leading to an 'Idle' state (oval). From 'Idle', it branches into two parallel paths: 'Search for MS' (parallelogram) followed by 'Active_Info_Retrieval_Search_MSC' (double rectangle), and 'Page MS' (parallelogram) followed by 'Active_Info_Retrieval_Page_MSC' (double rectangle). Both paths converge to a final 'Idle' state (oval).](38d82ffe820e339811b396206f40a201_img.jpg) + +### Process AIR\_MSC + +**AIR\_MSC1(1)** + +Process in the MSC to retrieve any one or more of the current location, MS classmark and IMEI of a subscriber + +Signals to/from the left are to/from the VLR + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> Search[/Search for MS/]; Idle1 --> Page[/Page MS/]; Search --> AIR_S[Active_Info_Retrieval_Search_MSC]; Page --> AIR_P[Active_Info_Retrieval_Page_MSC]; AIR_S --> Idle2([Idle]); AIR_P --> Idle2 +``` + +Flowchart for Process AIR\_MSC. It starts with an oval connector, leading to an 'Idle' state (oval). From 'Idle', it branches into two parallel paths: 'Search for MS' (parallelogram) followed by 'Active\_Info\_Retrieval\_Search\_MSC' (double rectangle), and 'Page MS' (parallelogram) followed by 'Active\_Info\_Retrieval\_Page\_MSC' (double rectangle). Both paths converge to a final 'Idle' state (oval). + +**Figure 7.1.2.16c: Procedure Check\_OG\_Barring (sheet 3)** + +![Flowchart of Procedure Active_Info_Retrieval_Page_MSC showing logic for paging a mobile station, handling SGSN paging, CM service requests, and location reporting.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +**Procedure Active\_Info\_Retrieval\_Page\_MSC** **AIRP\_MSC1(2)** + +Procedure in the MSC to page an MS in a specified location area for Active Location Retrieval + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` + + graph TD + Start([ ]) --> LAI_Known{Location +area ID +known?} + LAI_Known -- No --> SetNegUnknown[Set negative +response: +Unknown LAI] + LAI_Known -- Yes --> MS_Conn{MS +connection +exists?} + + MS_Conn -- Yes --> RetrieveIMEI_R[Retrieve_ +IMEI_If_ +Required] + RetrieveIMEI_R --> ReleaseTrans[Release +transaction] + ReleaseTrans --> PageMSAck_R>Page MS +ack] + PageMSAck_R --> End1(( )) + + MS_Conn -- No --> SGSN_Poss{Paging via +SGSN possible?} + + SGSN_Poss -- Yes --> PageSGSN>Page MS +via SGSN] + SGSN_Poss -- No --> Page>Page] + InSpecArea>In specified +location area] --> Page + + PageSGSN --> StartTimer[Start Page +response +timer] + Page --> StartTimer + + StartTimer --> WaitPageResp[[Wait_For_ +Page_ +Response]] + + WaitPageResp --> TimerExp SetNegAbsent[Set negative +response: +Absent +subscriber] + SetNegAbsent --> PageMSNeg>Page MS +negative +response] + PageMSNeg --> End2(( )) + + WaitPageResp --> MSConnEst RetrieveIMEI_C[Retrieve_ +IMEI_If_ +Required] + RetrieveIMEI_C --> PageMSAck_C>Page MS +ack] + PageMSAck_C --> End3(( )) + + WaitPageResp --> CMServiceReq ForCS[For circuit- +switched call] + CMServiceReq --> ToOCH[To process +OCH_MSC] + ForCS --> CMReq1>CM Service +Request] + ToOCH --> CMReq2>CM Service +Request] + CMReq1 --> RetrieveIMEI_CM[Retrieve_ +IMEI_If_ +Required] + CMReq2 --> RetrieveIMEI_CM + RetrieveIMEI_CM --> PageMSAck_CM>Page MS +ack] + PageMSAck_CM --> End4(( )) + + %% Right side branch + RetrieveIMEI_Right[Retrieve_ +IMEI_If_ +Required] --> GSMAccess{GSM +Access?} + GSMAccess -- Yes --> LocInfoReq{Location +info +requested?} + GSMAccess -- No --> SetNegUnknown + LocInfoReq -- No --> PageMSAck_Right>Page MS +ack] + LocInfoReq -- Yes --> ReportChange{Report on +change of +service area?} + ReportChange -- Yes --> SetNegUnknown + ReportChange -- No --> LocReportCtrl>Location +Reporting +Control] + LocReportCtrl --> WaitLocReport[[Wait_For_ +Location_ +Report]] + WaitLocReport --> LocReport LocInfoSet[Location info:= +Received +location info] + LocInfoSet --> PageMSAck_Right + PageMSAck_Right --> End5(( )) + + SetNegUnknown --> PageMSNegUnknown>Page MS +negative +response] + PageMSNegUnknown --> End6(( )) + +``` + +Flowchart of Procedure Active\_Info\_Retrieval\_Page\_MSC showing logic for paging a mobile station, handling SGSN paging, CM service requests, and location reporting. + +**Figure 7.1.2.17: Process Update\_Location\_VLR** + +## 7.2 Retrieval of routeing information for MT call + +### 7.2.1 Functional requirements of GMSC + +#### 7.2.1.1 Process MT\_GMSC + +Sheet 1: the variables ACM sent, Answer sent, Network connect sent, Reconnect and Resume call are global data, accessible to the procedures CCBS\_MT\_GMSC\_Check\_CCBS Possible, CCBS\_Set\_Diagnostic\_For\_Release, Obtain\_Routeing\_Address, Send\_ACM\_If\_Required, Send\_Answer\_If\_Required and Send\_Network\_Connect\_If\_Required. + +Sheet 1: the variable UUS CF interaction is specific to UUS; it is accessible to all UUS specific procedures in the GMSC. + +Sheet 1: the procedure MNP\_MT\_GMSC\_Set\_MNP\_Parameters is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10]. + +Sheet 1: the procedure OR\_Set\_ORA\_Parameters is specific to Support of Optimal Routeing; it is specified in 3GPP TS 23.079 [13]. + +Sheet 1: the procedure CAMEL\_Set\_ORA\_Parameters is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. + +Sheet 1: the parameters "Reference address", "OR" and "Own PLMN" are passed to the procedure Obtain\_Routeing\_Address only if the GMSC supports Optimal Routeing. The parameter "Destination address" is returned by the procedure Obtain\_Routeing\_Address only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. The Send Routeing Info negative response information element received in the execution of the procedure Obtain\_Routeing\_Address is global data, available to the parent process. + +Sheet 1: the suggested mapping from values of the Send Routeing Info negative response information element to values of the ISUP release cause (see ITU-T Recommendation Q.850 [37]) is shown in table 1. The mapping used is a matter for the network operator, depending on the telephony signalling system used. + +**Table 1: Suggested mapping of Send Routeing Info (SRI) +negative responses to ISUP release causes** + +| SRI negative response | ISUP release cause number | ISUP release cause name | +|---------------------------------------------------------------|----------------------------------|--------------------------------------------| +| Absent subscriber | 20 | Subscriber absent | +| Bearer service not provisioned | 57 | Bearer capability not authorized | +| Busy subscriber | 17 | User busy | +| Call barred (ODB) | 21 | Call rejected | +| Call barred (SS barring) | 21 | Call rejected | +| Call barred (ACR) | 31 | Normal, unspecified (NOTE 2) | +| CUG reject (Called party SS interaction violation) | 21 | Call rejected | +| CUG reject (Incoming calls barred within CUG) | 55 | Incoming calls barred within CUG | +| CUG reject (Subscriber not member of CUG) | 87 | User not member of CUG | +| CUG reject (Requested basic service violates CUG constraints) | 87 | User not member of CUG | +| Data missing | 111 | Protocol error, unspecified | +| Facility not supported | 69 | Requested facility not implemented | +| Forwarding violation | 21 | Call rejected | +| Number changed | 22 | Number changed | +| System failure | 111 | Protocol error, unspecified | +| Teleservice not provisioned | 57 | Bearer capability not authorized | +| Unexpected data value | 111 | Protocol error, unspecified | +| Unknown subscriber | 1 | Unallocated (unassigned) number | +| | 26 | Misrouted call to a ported number (NOTE 1) | + +NOTE 1: If the Diagnostic parameter indicates "NPDB mismatch", MNP can require a specific ISUP release cause value, according to National Coding Standard, to indicate "Misrouted call to a ported number", depending on national regulations. North American GSM Number Portability (NAGNP) requires the SRI negative response "unknown subscriber" to be treated differently under certain conditions. If the IAM received from the originating exchange contained the HPLMN routing number for NAGNP then the SRI negative response "unknown subscriber" shall be mapped to ISUP release cause number 26 "Misrouted call to a ported number"; under all other conditions the SRI negative response "unknown subscriber" shall be mapped to ISUP release cause number 1 "Unallocated (unassigned) number". + +NOTE 2: The GMSC will play an announcement towards the calling user to signal that the call is rejected due to anonymous call rejection and then include cause 24 "call rejected due to feature at destination" in ACM or CPG. See 3GPP TS 23.088 [21]. + +Sheet 1: it is an operator option whether to send an Address Complete message if the Number Portability Database returns a routeing number. If the GMSC sends an Address Complete message, it shall include the called party's status field of the Backward call indicator set to "no indication". + +Sheet 1: the called party address sent in the IAM to the process MT\_CF\_MSC is the Forwarded-to number received in the Perform Call Forwarding ack. + +Sheet 1: the procedure CAMEL\_Store\_Destination\_Address is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 1: it is an operator option whether to send an Address Complete message if the HLR returns forwarding information. If the GMSC sends an Address Complete message, it shall include the called party's status field of the Backward call indicator set to "no indication". + +Sheet 1, sheet 8: the process CAMEL\_MT\_LEG1\_GMSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 2: the procedures CAMEL\_Start\_TNRy and CAMEL\_Stop\_TNRy are specific to CAMEL phase 2 or later; they are specified in 3GPP TS 23.078 [12]. + +Sheet 2, sheet 3: the procedure CAMEL\_MT\_MSC\_ALERTING is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL phase 4 or later, processing continues from the "Pass" exit of the test "Result?". + +Sheet 2, sheet 3: the procedure CAMEL\_MT\_GMSC\_ANSWER is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL, processing continues from the "Pass" exit of the test "Result". + +Sheet 2, sheet 3: the task "Set destination address parameter" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. + +Sheet 3: the procedure Handle\_COLP\_Forwarding\_Interaction is specific to COLP. + +Sheet 4: the input signal Resume Call Handling and all the subsequent processing on this sheet are specific to Support of Optimal Routeing, and will occur only if the GMSC supports Optimal Routeing. The procedure OR\_Handle\_RCH is specified in 3GPP TS 23.079 [13]. + +Sheet 4, sheet 6: the procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Possible is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 5: the input signal TNRY expired and all the subsequent processing are specific to CAMEL phase 2 or later, and will occur only if the GMSC supports CAMEL phase 2 or later. The procedure CAMEL\_MT\_GMSC\_DISC5 is specified in 3GPP TS 23.078 [12]. + +Sheet 6: the procedure CAMEL\_MT\_GMSC\_DISC3 is specific to CAMEL phase 1; it is specified in 3GPP TS 23.078 [12]. + +Sheet 6: the procedures CAMEL\_MT\_GMSC\_DISC4 and CAMEL\_MT\_GMSC\_DISC6 are specific to CAMEL phase 2 or later, they are specified in 3GPP TS 23.078 [12]. + +Sheet 6: the procedure CCBS\_Set\_Diagnostic\_For\_Release is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 6, sheet 7: the processing in the branch beginning with the Int\_Release\_Call input will occur only if the MSC supports CAMEL. + +Sheet 7: the procedure CAMEL\_MT\_GMSC\_DISC1 is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL, processing continues from the "No" exit of the test "Result=CAMEL handling?". + +Sheet 7: the procedure CAMEL\_MT\_GMSC\_DISC2 is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL, processing continues from the "Normal handling" exit of the test "Result?". + +Sheet 7: after the GMSC has sent an IAM to the destination VMSC or the forwarded-to exchange (via the process MT\_CF\_MSC), it acts as a relay for messages received from the originating exchange and the destination VMSC or the process MT\_CF\_MSC. Any message other than Address Complete, Connect, Answer or Release causes no change of state in the process MT\_GMSC. + +Sheet 8: the procedure CAMEL\_MT\_LEG2\_GMSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. + +#### 7.2.1.2 Procedure Obtain\_Routeing\_Address + +Sheet 1: the procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_TQoD is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10]. + +Sheet 1: the procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Call is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 1: the procedure CLI\_MT\_GMSC is specific to Enhanced CLI Handling. It is specified in 3GPP TS 23.081 [14]. This procedure shall also be performed if the GMSC supports the ACR supplementary service. + +Sheet 1: for SCUDIF calls, the message Send Routeing Info shall include the ISDN BC of both the preferred and the less preferred service, as specified in 3GPP TS 23.172 [38]. + +Sheet 1: global flag "Clear MT Roaming Retry IE" is initialized to No at the start of MT\_GMSC procedure. + +Sheet 1: if Mobile Terminating Roaming Retry is supported, and if no Resume Call Handling message for roaming retry has been received, the GMSC shall include the GMSC address, the call reference number and the MT Roaming Retry Supported IE in the SRI message. + +Sheet 2: the procedure SCUDIF\_Negative\_SRI\_Response\_Handling is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the GMSC does not support SCUDIF, processing continues from the "Fail" exit of the test "Result". + +Sheet 2: the procedure OR\_Handle\_SRI\_Negative\_Response is specific to Support of Optimal Routeing. It is specified in 3GPP TS 23.079 [13]. If the GMSC does not support Optimal Routeing, processing continues from the "No" exit of the test "Result=Pass?". + +Sheet 2: the test "Error=Unknown subscriber" refers to the negative response value received from the HLR. + +Sheet 2: the procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_QoHR is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10]. + +Sheet 3: the procedure SCUDIF\_Check\_Service\_Availability is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the GMSC does not support SCUDIF, processing continues from the "continue" exit of the test "Result ?". + +Sheet 3: the procedure CAMEL\_MT\_GMSC\_INIT is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. + +Sheet 3: the procedure SCUDIF\_Check\_Service\_Compatibility is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. + +Sheet 3: sending of "Release Resources" is an implementation option. If support of "Release Resources" by the VMSC is not indicated in Send Routing Info ack, "Release Resources" shall not be sent. + +Sheet 4: the procedure SCUDIF\_Check\_Service\_Compatibility is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. + +Sheet 4: the procedure CCBS\_MT\_GMSC\_Check\_CCBS\_Indicators is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 4: the task "Store Forwarding Interrogation Required indicator" is executed only if the GMSC supports Optimal Routeing. + +Sheet 4: The test "MSRN contains a Routeing Number" is executed only if the SRF solution for call related MNP is used. If the SRF solution for call related MNP is not used, processing continues from the "No" exit of the test "MSRN contains a Routeing Number". + +Sheet 4: the procedure MNP\_MT\_GMSC\_Check\_MNP\_Indicators is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10]. + +Sheet 5: the procedure CAMEL\_MT\_GMSC\_Notify\_CF is specific to CAMEL phase 2 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL phase 2 or later, processing continues from the "Continue" exit of the test "Result". + +Sheet 5: the procedure SCUDIF\_Check\_Service\_Compatibility is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. + +Sheet 6: the task "BOR:=OR" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. + +Sheet 6: the procedures CCBS\_MT\_GMSC\_Remove\_Indicators\_Store\_FWT is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 6: the procedure Route\_Permitted is specific to Support of Optimal Routeing. It is specified in 3GPP TS 23.079 [13]. If the GMSC does not support Optimal Routeing, processing continues from the "True" exit of the test "Route permitted". + +Sheet 6: the procedure CAMEL\_MT\_MSC\_DISC3 is specific to CAMEL phase 1; it is specified in 3GPP TS 23.078 [12]. + +Sheet 6: the procedure CAMEL\_MT\_GMSC\_DISC4 is specific to CAMEL Phase 2 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 6: the task "OR:= True" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. + +#### 7.2.1.3 Procedure Send\_ACM\_If\_Required + +If no useful information would be carried in the Call Progress message, it is not sent. + +#### 7.2.1.4 Procedure Send\_Answer\_If\_Required + +If no useful information would be carried in the Call Progress message, it is not sent. + +#### 7.2.1.5 Procedure Send\_Network\_Connect\_If\_Required + +If no useful information would be carried in the Call Progress message, it is not sent. + +#### 7.2.1.6 Procedure Handle\_COLP\_Forwarding\_Interaction\_MSC + +The originating exchange or the destination exchange may release the call while a response is awaited from the process COLP\_MAF039. The message is saved for processing after return from the procedure. + +#### 7.2.1.7 Procedure Activate\_CF\_Process + +The processing in the branch beginning with the Int\_Release\_Call input will occur only if the MSC supports CAMEL. + +# 7.2.1.8 Process MT\_CF\_MSC + +Sheet 1: the procedure CAMEL\_CF\_MSC\_INIT is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 1, sheet 4: the procedure CAMEL\_CF\_Dialled\_Services is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL phase 3 or later, processing continues from the "Pass" exit of the test "Result?". + +Sheet 1, sheet 3, sheet 4: the procedure CAMEL\_OCH\_MSC1 is specific to CAMEL phase 2 or later; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL phase 2 or later, processing continues from the "Yes" exit of the test "Result=Reconnect?". + +Sheet 1: the procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_OQoD is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10]. + +Sheet 1: the procedure CAMEL\_Store\_Destination\_Address is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 1, sheet 3: the procedure CAMEL\_OCH\_MSC\_DISC3 is specific to CAMEL phase 1; it is specified in 3GPP TS 23.078 [12]. + +Sheet 1, sheet 3: the procedure CAMEL\_OCH\_MSC\_DISC4 is specific to CAMEL Phase 2 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 1, sheet 6: the procedure CAMEL\_MT\_CF\_LEG1\_MSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 2: the procedures CAMEL\_Start\_TNRy and CAMEL\_Stop\_TNRy are specific to CAMEL phase 2 or later; they are specified in 3GPP TS 23.078 [12]. + +Sheet 2: the procedure CAMEL\_CF\_MSC\_ANSWER is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "Pass" exit of the test "Result?". + +Sheet 2: the procedure UUS\_MSC\_Clear\_UUS is specific to UUS; it is specified in 3GPP TS 23.087 [20]. + +Sheet 2: the procedure CAMEL\_CF\_MSC\_ALERTING is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL phase 4 or later, processing continues from the "Pass" exit of the test "Result?". + +Sheet 3: the procedure CAMEL\_Stop\_TNRy is specific to CAMEL phase 2 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 3: the processing in the branch beginning with the Int\_O\_Release input will occur only if the MSC supports CAMEL. + +Sheet 4: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2 or later, and will occur only if the GMSC supports CAMEL phase 2 or later. The procedure CAMEL\_OCH\_MSC2 is specified in 3GPP TS 23.078 [12]. + +Sheet 5: the procedure CAMEL\_OCH\_MSC\_DISC1 is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "No" exit of the test "Result=CAMEL handling?". + +Sheet 5: the procedure CAMEL\_OCH\_MSC\_DISC2 is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "No" exit of the test "Result=Reconnect?". + +Sheet 5: the processing in the branch beginning with the Int\_O\_Release input will occur only if the MSC supports CAMEL. + +Sheet 5: after the process MT\_CF\_MSC has sent an IAM to the forwarded-to exchange, it acts as a relay for messages received from the parent process and the forwarded-to exchange. Any message other than Address Complete, Connect, Answer or Release causes no change of state in the process MT\_GMSC. + +Sheet 6: the process CAMEL\_MT\_CF\_LEG2\_MSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. + +### 7.2.1.9 Macro CUG\_Support\_Check\_GMSC + +![Flowchart for Procedure Active_Info_Retrieval_Search_MSC. It starts with a connector, then checks if an MS connection exists. If 'No', it checks if paging via SGSN is possible. If 'Yes', it searches for MS via SGSN. If 'No', it pages in all location areas. Both paths lead to starting a page response timer and waiting for a response. If the timer expires, it sets a negative response and searches for a negative response. If the connection is established, it retrieves IMEI if required, releases the transaction, and searches for an MS ack. If a CM Service Request is received (for circuit-switched calls or to process OCH_MSC), it retrieves IMEI if required and searches for an MS ack. If the connection exists initially, it retrieves IMEI if required, checks GSM access, location info requested, and report on change of service area. If no report, it controls location reporting, waits for a location report, receives it, and searches for an MS ack.](184d3d9a856c77aae93652f4fe30f752_img.jpg) + +**Procedure Active\_Info\_Retrieval\_Search\_MSC** **AIRS\_MSC1(1)** + +Procedure in the MSC to page an MS in all location areas for Active Location Retrieval + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` + + graph TD + Start([ ]) --> MS_Exists{MS connection exists?} + MS_Exists -- Yes --> Retrieve_IMEI_Req1[Retrieve_IMEI_If_Required] + MS_Exists -- No --> Paging_Possible{Paging via SGSN possible?} + Paging_Possible -- Yes --> Search_SGSN{{Search for MS via SGSN}} + Paging_Possible -- No --> Page[Page] + Page --> InAll[In all location areas] + InAll --> Start_Timer[Start Page response timer] + Search_SGSN --> Start_Timer + Start_Timer --> Wait_Response([Wait_For_Page_Response]) + Wait_Response --> Timer_Expired{Page response timer expired} + Wait_Response --> Connection_Established{MS connection established} + Wait_Response --> CM_Request{CM Service Request} + CM_Request --> ForCircuit[For circuit-switched call] + CM_Request --> ToOCH[To process OCH_MSC] + Timer_Expired --> Set_Neg[Set negative response: Absent subscriber] + Set_Neg --> Search_Neg{{Search for MS negative response}} + Search_Neg --> End1(( )) + Connection_Established --> Retrieve_IMEI_Req2[Retrieve_IMEI_If_Required] + Retrieve_IMEI_Req2 --> Release[Release transaction] + Release --> Search_Ack1{{Search for MS ack}} + Search_Ack1 --> End2(( )) + CM_Request --> Retrieve_IMEI_Req3[Retrieve_IMEI_If_Required] + Retrieve_IMEI_Req3 --> Search_Ack2{{Search for MS ack}} + Search_Ack2 --> End3(( )) + Retrieve_IMEI_Req1 --> GSM_Access{GSM Access?} + GSM_Access -- Yes --> Search_Ack3{{Search for MS ack}} + GSM_Access -- No --> Info_Requested{Location info requested?} + Info_Requested -- Yes --> Change_Report{Report on change of service area?} + Change_Report -- Yes --> Search_Ack3 + Change_Report -- No --> Loc_Reporting[Location Reporting Control] + Loc_Reporting --> Wait_Report([Wait_For_Location_Report]) + Wait_Report --> Loc_Report[Location Report] + Loc_Report --> Loc_Info[Location info:= Received location info] + Loc_Info --> Search_Ack3 + +``` + +Flowchart for Procedure Active\_Info\_Retrieval\_Search\_MSC. It starts with a connector, then checks if an MS connection exists. If 'No', it checks if paging via SGSN is possible. If 'Yes', it searches for MS via SGSN. If 'No', it pages in all location areas. Both paths lead to starting a page response timer and waiting for a response. If the timer expires, it sets a negative response and searches for a negative response. If the connection is established, it retrieves IMEI if required, releases the transaction, and searches for an MS ack. If a CM Service Request is received (for circuit-switched calls or to process OCH\_MSC), it retrieves IMEI if required and searches for an MS ack. If the connection exists initially, it retrieves IMEI if required, checks GSM access, location info requested, and report on change of service area. If no report, it controls location reporting, waits for a location report, receives it, and searches for an MS ack. + +Figure 36a: Process MT\_GMSC (sheet 1) + +![Flowchart for Procedure Retrive_IMEI_If_Required. It starts with a connector, leading to a decision 'IMEI requested?'. If 'No', it goes to another connector. If 'Yes', it goes to 'Send IMEI', then 'Wait_For_IMEI'. From 'Wait_For_IMEI', it branches into two parallel paths: one for 'IMEI' (leading to 'IMEI:= Received IMEI') and one for 'Release transaction'. Both paths converge to a final connector. A note indicates the 'Release transaction' path also leads 'To supervising process, if required'.](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) + +### Procedure Retrive\_IMEI\_If\_Required + +RIIR1(1) + +Procedure in the MSC to retrieve the IMEI of the MS if requested by the VLR + +Signals to/from the left are to/from the BSS + +``` +graph TD; Start([ ]) --> Decision{IMEI requested?}; Decision -- No --> End1(( )); Decision -- Yes --> SendIMEI{{Send IMEI}}; SendIMEI --> WaitForIMEI{{Wait_For_IMEI}}; WaitForIMEI --> IMEIPath[IMEI]; WaitForIMEI --> ReleasePath[Release transaction]; IMEIPath --> IMEIAssign[IMEI:= Received IMEI]; ReleasePath --> ReleaseTransaction[Release transaction]; ReleaseTransaction --> Supervising[To supervising process, if required]; IMEIAssign --> End2(( )); ReleaseTransaction --> End2 +``` + +Flowchart for Procedure Retrive\_IMEI\_If\_Required. It starts with a connector, leading to a decision 'IMEI requested?'. If 'No', it goes to another connector. If 'Yes', it goes to 'Send IMEI', then 'Wait\_For\_IMEI'. From 'Wait\_For\_IMEI', it branches into two parallel paths: one for 'IMEI' (leading to 'IMEI:= Received IMEI') and one for 'Release transaction'. Both paths converge to a final connector. A note indicates the 'Release transaction' path also leads 'To supervising process, if required'. + +Figure 36b: Process MT\_GMSC (sheet 2) + +![State transition diagram for Process ICH_MSC. It starts at 'Idle' and branches based on incoming signals from GMSC: 'Release Resources' or 'Initial Address'. The 'Initial Address' path involves processing call setup, CAMEL handling, and then a 'Result?' decision leading to 'Leg1_only', 'Reconnect', 'MSRN', 'Aborted', or 'Fail' states.](c0ca823603794512478906b302176bca_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC1(17) + +Process in the MSC to handle an incoming (MT) call + +Signals to/from the left are to/from the BSS; + signals to/from the right are to/from the VLR + unless marked otherwise + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Release_Resources: From GMSC + Release_Resources --> Release_Resources + Release_Resources --> Release_MSRN + Release_MSRN --> Idle + + Idle --> Initial_Address: From GMSC + Initial_Address --> Process_Address + Process_Address --> Send_Info_Incoming_Call + Send_Info_Incoming_Call --> Wait_For_Page_Request + Wait_For_Page_Request --> Continue_CAMEL_Handling + Continue_CAMEL_Handling --> CAMEL_INIT + CAMEL_INIT --> Result? + Result? --> Leg1_only + Result? --> Reconnect + Result? --> MSRN + Result? --> Aborted + Result? --> Fail + + Leg1_only --> Leg1_status + Leg1_status --> CAMEL_LEG1_MSC + CAMEL_LEG1_MSC --> Idle + Idle --> See_TS_23_078 + + Reconnect --> Send_Info_Reconnected_Call + Send_Info_Reconnected_Call --> Wait_For_Reconnected_Call_Result + + MSRN --> Set_Suppress_VT_CSI + Set_Suppress_VT_CSI --> Send_Info_Incoming_Call + Send_Info_Incoming_Call --> Wait_For_Page_Request + + Aborted --> Release + Fail --> Set_cause + Set_cause --> Release + Release --> Release_call_resources + Release_call_resources --> Idle + +``` + +**State Details:** + +- Process\_Address:** Convert ISDN BC/LLC/HLC (if present) to bearer service/teleservice & CS BC; Store UUS information (if received) +- Wait\_For\_Page\_Request:** ACM sent:=False; Answer sent:=False; BOR:=False; Network connect sent:=False; TCH allocated:=False; UUS1 result sent:=False; UUS1 implicit active:=False; UUS1 explicit active:=False; UUS2 active:=False; UUS3 active:=False; UUS CF interaction:=False; Call answered := False; On\_Hold:=False +- CAMEL\_INIT:** See TS 23.078 +- Leg1\_status := Set-up** +- CAMEL\_ICH\_LEG1\_MSC (Leg1\_Status)** +- See TS 23.078** +- Set\_Suppress\_VT\_CSI** +- Set\_cause** +- Release call resources** + +State transition diagram for Process ICH\_MSC. It starts at 'Idle' and branches based on incoming signals from GMSC: 'Release Resources' or 'Initial Address'. The 'Initial Address' path involves processing call setup, CAMEL handling, and then a 'Result?' decision leading to 'Leg1\_only', 'Reconnect', 'MSRN', 'Aborted', or 'Fail' states. + +Figure 36c: Process MT\_GMSC (sheet 3) + +![Flowchart for Process ICH_MSC. It starts with 'Wait For Page_Request' and branches into 'Send Info For Incoming Call negative response', 'Page MS', 'Send Info For Incoming Call Ack', 'Search For MS', and 'Complete Call'. Each branch has its own logic for handling the call, including result checks, CAMEL interactions, and resource management.](fc3e2b49a9f850951570e502393b697f_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC2(17) + +Process in the MSC to handle an incoming (MT) call + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR + +``` +graph TD; Start([Wait For Page_Request]) --> Branch1[ ]; Branch1 --> S1[Send Info For Incoming Call negative response]; Branch1 --> P[Page MS]; Branch1 --> S2[Send Info For Incoming Call Ack]; Branch1 --> CF[Call is to be forwarded]; Branch1 --> SF[Search For MS]; Branch1 --> C[Complete Call]; S1 --> SC[Set cause]; SC --> CAMEL4_1[CAMEL MT_GMSC_DISC4]; CAMEL4_1 --> R1{Result=Reconnect?}; R1 -- No --> Release1[Release]; Release1 --> ReleaseResources1[Release call resources]; ReleaseResources1 --> Idle1[Idle]; ReleaseResources1 --> TS1[See TS 23.078]; R1 -- Yes --> SIFC[Send Info For MT Reconnected Call]; SIFC --> WFCR1[Wait_For_Reconnected_Call_Result]; P --> PM[Page MS_MSC]; PM --> RP1{Result=Pass?}; RP1 -- No --> RF1{Result=Fail?}; RF1 -- No --> CAMEL6_1[CAMEL MT_GMSC_DISC6]; CAMEL6_1 --> ReleaseResources2[Release call resources]; ReleaseResources2 --> Idle2[Idle]; RF1 -- Yes --> WFCR2[Wait_For_MT_Call_Result]; RP1 -- Yes --> PAR[Process Access Request_MSC]; PAR --> RP2{Result=Pass?}; RP2 -- No --> CAMEL4_2[CAMEL MT_GMSC_DISC4]; CAMEL4_2 --> R2{Result=Reconnect?}; R2 -- No --> Release2[Release]; Release2 --> ReleaseResources3[Release call resources]; ReleaseResources3 --> Idle3[Idle]; ReleaseResources3 --> TS2[See TS 23.078]; R2 -- Yes --> SIFC; SF --> SFSM[Search_For_MS_MSC]; SFSM --> RP3{Result=Pass?}; RP3 -- No --> RF2{Result=Fail?}; RF2 -- No --> CAMEL6_2[CAMEL MT_GMSC_DISC6]; CAMEL6_2 --> ReleaseResources4[Release call resources]; ReleaseResources4 --> Idle4[Idle]; RF2 -- Yes --> WFCR3[Wait_For_MT_Call_Result]; RP3 -- Yes --> WFCR4[Wait_For_MT_Call_Result]; C --> J2((2)); +``` + +Flowchart for Process ICH\_MSC. It starts with 'Wait For Page\_Request' and branches into 'Send Info For Incoming Call negative response', 'Page MS', 'Send Info For Incoming Call Ack', 'Search For MS', and 'Complete Call'. Each branch has its own logic for handling the call, including result checks, CAMEL interactions, and resource management. + +Figure 36d: Process MT\_GMSC (sheet 4) + +![State transition diagram for Process ICH_MSC. The diagram shows various states and transitions for handling an incoming MT call. It includes states like 'Send Info For Incoming Call negative response', 'CD_Reject', 'CCBS_Set_Diagnostic_For_Release', 'UUS_ICH_Check_Support', 'Set_cause', 'Complete_Call', 'Complete_Call_In_MSC', 'Process_Call_Waiting', 'Call answered := True', 'Call established', 'Release transaction', 'CCBS_Check_Last_Call', 'Release call resources', and 'Idle'. Transitions include 'Result=Pass?', 'Result=Fail', 'Result=Reconnect?', and 'Cause=No Subscriber Reply?'. Reference boxes point to TS 23.072, 23.078, 23.083, and 23.093. A note indicates signals to/from the left are to/from the GMSC, and to/from the right are to/from the VLR.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +**Process ICH\_MSC** **ICH\_MSC3(17)** + +Process in the MSC to handle an incoming (MT) call + +``` + +stateDiagram-v2 + [*] --> Wait_For_MT_Call_Result + state "Send Info For Incoming Call negative response" as S1 + state "CD_Reject" as S2 + state "CCBS_Set_Diagnostic_For_Release" as S3 + state "UUS_ICH_Check_Support" as S4 + state "Set_cause" as S5 + state "Complete_Call" as S6 + state "Complete_Call_In_MSC" as S7 + state "Process_Call_Waiting" as S8 + state "Call answered := True" as S9 + state "Call established" as S10 + state "Release transaction" as S11 + state "CCBS_Check_Last_Call" as S12 + state "Release call resources" as S13 + state "Idle" as S14 + + Wait_For_MT_Call_Result --> S1 + Wait_For_MT_Call_Result --> S6 + Wait_For_MT_Call_Result --> S8 + + S1 --> S2 + S2 --> S3 + S3 --> S4 + S4 --> S5 + S5 --> Causen{Cause=No Subscriber Reply?} + Causen -- Yes --> S11 + Causen -- No --> CAMEL_MT_GMSC_DISC4[CAMEL MT_GMSC_DISC4] + CAMEL_MT_GMSC_DISC4 --> ResultReconnect{Result=Reconnect?} + ResultReconnect -- Yes --> SendInfoForMTReconnectedCall[Send Info For MT Reconnected Call] + SendInfoForMTReconnectedCall --> Wait_For_Reconnected_Call_Result[Wait_For_Reconnected_Call_Result] + Wait_For_Reconnected_Call_Result --> S11 + ResultReconnect -- No --> Release[Release] + Release --> S11 + + S6 --> S7 + S7 --> ResultPass{Result=Pass?} + ResultPass -- No --> Call_setup_failed[Call setup failed] + Call_setup_failed --> ToSubsFSM[To Subs_FSM] + ResultPass -- Yes --> StoreCW[Store CW Treatment indicator for this call if received in SII2] + StoreCW --> Call_answered[Call answered := True] + Call_answered --> Call_established[Call established] + Call_established --> 5((5)) + 5 --> Wait_For_MT_Call_Result + + S8 --> ResultPass2{Result=Pass?} + ResultPass2 -- No --> Call_setup_failed2[Call setup failed] + Call_setup_failed2 --> ToSubsFSM2[To Subs_FSM] + ResultPass2 -- Yes --> ResultFail{Result=Fail} + ResultFail -- Yes --> Wait_For_MT_Call_Result + ResultFail -- No --> ResultReconnect2{Result=Reconnect?} + ResultReconnect2 -- Yes --> SendInfoForMTReconnectedCall2[Send Info For MT Reconnected Call] + SendInfoForMTReconnectedCall2 --> Wait_For_Reconnected_Call_Result2[Wait_For_Reconnected_Call_Result] + Wait_For_Reconnected_Call_Result2 --> S11 + ResultReconnect2 -- No --> S11 + + S11 --> S12 + S12 --> S13 + S13 --> S14 + + Note right of S1: Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR unless marked otherwise + +``` + +See TS 23.072 + +See TS 23.078 + +See TS 23.083 + +See TS 23.093 + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR unless marked otherwise + +State transition diagram for Process ICH\_MSC. The diagram shows various states and transitions for handling an incoming MT call. It includes states like 'Send Info For Incoming Call negative response', 'CD\_Reject', 'CCBS\_Set\_Diagnostic\_For\_Release', 'UUS\_ICH\_Check\_Support', 'Set\_cause', 'Complete\_Call', 'Complete\_Call\_In\_MSC', 'Process\_Call\_Waiting', 'Call answered := True', 'Call established', 'Release transaction', 'CCBS\_Check\_Last\_Call', 'Release call resources', and 'Idle'. Transitions include 'Result=Pass?', 'Result=Fail', 'Result=Reconnect?', and 'Cause=No Subscriber Reply?'. Reference boxes point to TS 23.072, 23.078, 23.083, and 23.093. A note indicates signals to/from the left are to/from the GMSC, and to/from the right are to/from the VLR. + +Figure 36e: Process MT\_GMSC (sheet 5) + +![Flowchart for Process ICH_MSC. It starts at connector 5, checks if a CAMEL phase 4 or later control relationship exists. If 'Yes', it sets Leg1_status to Active, then calls CAMEL_ICH_LEG1_MSC and CAMEL_ICH_LEG2_MSC (both referencing TS 23.078), ending at Idle. If 'No', it goes to Wait_For_Clear.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +**Process ICH\_MSC** **ICH\_MSC4(17)** + +Process in the MSC +to handle an incoming (MT) call + +``` +graph TD; Start((5)) --> Decision{CAMEL phase 4 or later control relationship exists?}; Decision -- No --> Wait_For_Clear([Wait_For_Clear]); Decision -- Yes --> Leg1_Status[Leg1_status := Active]; Leg1_Status --> Leg1_MSC[CAMEL_ICH_LEG1_MSC (Leg1_Status)]; Leg1_MSC --> Leg2_MSC[CAMEL_ICH_LEG2_MSC]; Leg2_MSC --> Idle([Idle]); +``` + +Flowchart for Process ICH\_MSC. It starts at connector 5, checks if a CAMEL phase 4 or later control relationship exists. If 'Yes', it sets Leg1\_status to Active, then calls CAMEL\_ICH\_LEG1\_MSC and CAMEL\_ICH\_LEG2\_MSC (both referencing TS 23.078), ending at Idle. If 'No', it goes to Wait\_For\_Clear. + +**Figure 36f: Process MT\_GMSC (sheet 6)** + +![Flowchart for Process ICH_MSC showing logic for call forwarding and roaming. It includes decision points for MT Roaming Forwarding supported, MT Roaming Retry supported, and CAMEL checks. It references TS 23.079, TS 23.072, TS 23.078, and TS 23.093.](e18841eb4a995df8354a793459e12fd0_img.jpg) + +Process ICH\_MSC +ICH\_MSC5(18) + +Process in the MSC to handle an incoming (MT + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR + +``` + + graph TD + Start((1)) --> WFCR[Wait_For_MT_Call_Result] + WFCR --> SIFC[/Send Info For Incoming Call/] + SIFC --> CF[Call is to be forwarded] + SIFC --> MRFS{MT Roaming Forwarding supported} + + MRFS -- yes --> MRFIR{MT Roaming Forwarding Indicator received} + MRFIR -- Yes --> IAM[/Initial Address Message to new MSC/] + IAM --> WFM[Wait_For_MTRF_ACM] + + MRFS -- No --> CAMEL[CAMEL_Check_ORLCF_VMSC] + MRFIR -- No --> MRRS{MT Roaming Retry supported} + + MRRS -- Yes --> MRRIR{MT Roaming Retry Indicator received} + MRRIR -- Yes --> HORLCF[Handle ORLCF_VMSC] + MRRIR -- No --> CAMEL + MRRS -- No --> CAMEL + + CAMEL --> Res1{Result?} + Res1 -- VMSCCF --> Continue[Continue] + Res1 -- ORLCF --> HORLCF + + HORLCF --> Res2{Result?} + Res2 -- Accepted --> CDS[CD_Success] + Res2 -- Forwarding Failed --> CDF[CD_Failure] + + CDS --> WFR[Wait_For_Release_From_GMSC] + CDF --> WFR + + WFR --> Rel[/Release/] + Rel --> CMGD[CAMEL_MT_GMSC_DISC6] + CMGD --> CCBS[CCBS_Check_Last_Call] + CCBS --> RCR[Release call resources] + RCR --> Idle([Idle]) + + Continue --> Conn3((3)) + +``` + +**Wait\_For\_MT\_Call\_Result** +**Send Info For Incoming Call** +**MT Roaming Forwarding supported** +**MT Roaming Forwarding Indicator received** +**Initial Address Message to new MSC** +**Wait\_For\_MTRF\_ACM** +**MT Roaming Retry supported** +**MT Roaming Retry Indicator received** +**Handle ORLCF\_VMSC** (See TS 23.079) +**CAMEL\_Check\_ORLCF\_VMSC** (See TS 23.079) +**CD\_Failure** (See TS 23.072) +**CD\_Success** (See TS 23.072) +**Wait\_For\_Release\_From\_GMSC** +**CAMEL\_MT\_GMSC\_DISC6** (See TS 23.078) +**CCBS\_Check\_Last\_Call** (See TS 23.093) +**Release call resources** +**Idle** + +Flowchart for Process ICH\_MSC showing logic for call forwarding and roaming. It includes decision points for MT Roaming Forwarding supported, MT Roaming Retry supported, and CAMEL checks. It references TS 23.079, TS 23.072, TS 23.078, and TS 23.093. + +Figure 36g: Process MT\_GMSC (sheet 7) + +![Flowchart for Process ICH_MSC. It starts at connector 3, checks if forwarding type is Reconnect. If No, it calls CAMEL MT_VMSC_Notify_CF (See TS 23.078). If Result=Reconnect? is Yes, it goes to connector 4. If No, it calls CCBS_Check_Last_Call (See TS 23.093), sets redirection information, sends ACM if required, and activates CF_Process. If Result? is Fail, it releases the call via Release and CAMEL MT_GMSC_DISC4 (See TS 23.078). If Result? is Pass, it calls UUS_ICH_Set_Info_in_IAM (See TS 23.087), sends Initial Address Message to process MT_CF_MSC, calls CAMEL_Store_Destination_Address (False, True) (See TS 23.078), and checks CD. If CD_Failure, it calls CD_Failure (See TS 23.072), CCBS_Check_Last_Call (See TS 23.093), and goes to Idle. If CD_Success, it calls CD_Success (See TS 23.072) and goes to Wait_For_Forward_ACM. If Result=Reconnect? is Yes after CD_Failure, it sends info for MT Reconnected Call and goes to Wait_For_Reconnected_Call_Result.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC6(17) + +Process in the MSC to handle an incoming (MT) call + +Signals to the right are to the VLR unless marked otherwise + +``` +graph TD; 3((3)) --> D1{Type of forwarding=Reconnect?}; D1 -- Yes --> D2{Result=Reconnect?}; D1 -- No --> P1[CAMEL MT_VMSC_Notify_CF - See TS 23.078]; P1 --> D2; D2 -- Yes --> 4((4)); D2 -- No --> P2[CCBS_Check_Last_Call - See TS 23.093]; P2 --> P3[Set redirection information]; P3 --> P4[Send ACM_If_Required]; P4 --> P5[Activate CF_Process]; P5 --> D3{Result?}; D3 -- Fail --> R1{Release}; D3 -- Pass --> P6[UUS_ICH_Set_Info_in_IAM - See TS 23.087]; D3 -- Release --> P7[CAMEL MT_GMSC_DISC4 - See TS 23.078]; P6 --> M1{{Initial Address Message}}; M1 --> P8[To process MT_CF_MSC]; P6 --> P9[CAMEL_Store_Destination_Address (False, True) - See TS 23.078]; P9 --> D4{CD}; D4 -- CD_Failure --> P10[CD_Failure - See TS 23.072]; D4 -- CD_Success --> P11[CD_Success - See TS 23.072]; P10 --> P12[CCBS_Check_Last_Call - See TS 23.093]; P12 --> I1([Idle]); P11 --> W1([Wait_For_Forward_ACM]); P7 --> D5{Result=Reconnect?}; D5 -- Yes --> M2{{Send Info For MT Reconnected Call}}; M2 --> W2([Wait_For_Reconnected_Call_Result]); D5 -- No --> P10; +``` + +Flowchart for Process ICH\_MSC. It starts at connector 3, checks if forwarding type is Reconnect. If No, it calls CAMEL MT\_VMSC\_Notify\_CF (See TS 23.078). If Result=Reconnect? is Yes, it goes to connector 4. If No, it calls CCBS\_Check\_Last\_Call (See TS 23.093), sets redirection information, sends ACM if required, and activates CF\_Process. If Result? is Fail, it releases the call via Release and CAMEL MT\_GMSC\_DISC4 (See TS 23.078). If Result? is Pass, it calls UUS\_ICH\_Set\_Info\_in\_IAM (See TS 23.087), sends Initial Address Message to process MT\_CF\_MSC, calls CAMEL\_Store\_Destination\_Address (False, True) (See TS 23.078), and checks CD. If CD\_Failure, it calls CD\_Failure (See TS 23.072), CCBS\_Check\_Last\_Call (See TS 23.093), and goes to Idle. If CD\_Success, it calls CD\_Success (See TS 23.072) and goes to Wait\_For\_Forward\_ACM. If Result=Reconnect? is Yes after CD\_Failure, it sends info for MT Reconnected Call and goes to Wait\_For\_Reconnected\_Call\_Result. + +Figure 36h: Process MT\_GMSC (sheet 8) + +![State transition diagram for Process ICH_MSC. The diagram shows a vertical sequence of states and transitions: 1. Initial state (oval) leads to 'Wait_For_MT_Call_Result; Wait_For_Reconnected_Call_Result' (rectangle). 2. 'Wait_For_MT_Call_Result' leads to 'Int_Release_Call' (diamond). 3. 'Int_Release_Call' has an outgoing signal 'From gsmSSF' (rectangle) and leads to 'Abort' (diamond). 4. 'Abort' leads to 'Release' (diamond). 5. 'Release' leads to 'Release Transaction' (diamond). 6. 'Release Transaction' has an outgoing signal 'To BSS' (rectangle) and leads to 'Release call resources' (rectangle). 7. 'Release call resources' leads to 'Idle' (oval).](69467ece0a576b4c2ec3e0c89ba61527_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC7(17) + +Process in the MSC +to handle an incoming (MT) call + +Signals to/from the left +are to/from the GMSC; +signals to/from the right +are to/from the VLR +unless marked otherwise + +``` +stateDiagram-v2 + [*] --> Wait_For_MT_Call_Result + state "Wait_For_MT_Call_Result; Wait_For_Reconnected_Call_Result" as Wait_For_MT_Call_Result + Wait_For_MT_Call_Result --> Int_Release_Call + state "Int_Release_Call" as Int_Release_Call + Int_Release_Call --> From_gsmSSF + state "From gsmSSF" as From_gsmSSF + Int_Release_Call --> Abort + state "Abort" as Abort + Abort --> Release + state "Release" as Release + Release --> Release_Transaction + state "Release Transaction" as Release_Transaction + Release_Transaction --> To_BSS + state "To BSS" as To_BSS + Release_Transaction --> Release_call_resources + state "Release call resources" as Release_call_resources + Release_call_resources --> Idle + state "Idle" as Idle +``` + +State transition diagram for Process ICH\_MSC. The diagram shows a vertical sequence of states and transitions: 1. Initial state (oval) leads to 'Wait\_For\_MT\_Call\_Result; Wait\_For\_Reconnected\_Call\_Result' (rectangle). 2. 'Wait\_For\_MT\_Call\_Result' leads to 'Int\_Release\_Call' (diamond). 3. 'Int\_Release\_Call' has an outgoing signal 'From gsmSSF' (rectangle) and leads to 'Abort' (diamond). 4. 'Abort' leads to 'Release' (diamond). 5. 'Release' leads to 'Release Transaction' (diamond). 6. 'Release Transaction' has an outgoing signal 'To BSS' (rectangle) and leads to 'Release call resources' (rectangle). 7. 'Release call resources' leads to 'Idle' (oval). + +Figure 36i: Process MT\_GMSC (sheet 9) + +![Process ICH_MSC flowchart (sheet 1). The diagram shows the logic for handling an incoming (MT) call. It starts with 'Wait_For_Forward_ACM', followed by 'Address Complete' and 'Send ACM_If_Required'. A decision 'Result?' follows. If 'Pass', it goes to 'Wait_For_Forward_Answer'. If 'Answer', it goes to 'CAMEL_MT_GMSC_ANSWER'. If 'Else', it goes to 'CAMEL_MT_GMSC_ANSWER'. From 'Wait_For_Forward_Answer', it branches to 'Release', 'Release', and 'Answer'. The 'Answer' path leads to 'CAMEL_MT_GMSC_ANSWER'. From 'CAMEL_MT_GMSC_ANSWER', a decision 'Result?' follows. If 'Pass', it goes to 'Handle_COLP_Forwarding_Interaction_MSC', then 'Set COLP presentation indicator', then 'Send_Answer_If_Required', then 'Call answered := True', and finally to connector '7'. If 'Else', it goes to 'Release'. From 'Release', it goes to 'CAMEL_MT_GMSC_DISC4', then 'See TS 23.078', then 'Result-Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call', then 'Wait_For_Reconnected_Call_Result'. If 'No', it goes to 'Release', then 'Release call resources', then 'Idle'. From 'CAMEL_MT_GMSC_DISC4', it also goes to 'CAMEL_MT_GMSC_DISC6', then 'See TS 23.078', then 'Release'. From 'CAMEL_MT_GMSC_ANSWER', if 'Else', it goes to 'CAMEL_MT_GMSC_ANSWER'. From 'CAMEL_MT_GMSC_ANSWER', a decision 'Result?' follows. If 'Pass', it goes to 'Handle_COLP_Forwarding_Interaction_MSC', then 'Set COLP presentation indicator', then 'Send_Network_Connect_If_Required', and finally to connector '6'. If 'Else', it goes to 'Release', then 'Idle'. A note at the top right indicates signal directions: 'Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the process MT_CF_MSC unless marked otherwise'.](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) + +Process ICH\_MSC flowchart (sheet 1). The diagram shows the logic for handling an incoming (MT) call. It starts with 'Wait\_For\_Forward\_ACM', followed by 'Address Complete' and 'Send ACM\_If\_Required'. A decision 'Result?' follows. If 'Pass', it goes to 'Wait\_For\_Forward\_Answer'. If 'Answer', it goes to 'CAMEL\_MT\_GMSC\_ANSWER'. If 'Else', it goes to 'CAMEL\_MT\_GMSC\_ANSWER'. From 'Wait\_For\_Forward\_Answer', it branches to 'Release', 'Release', and 'Answer'. The 'Answer' path leads to 'CAMEL\_MT\_GMSC\_ANSWER'. From 'CAMEL\_MT\_GMSC\_ANSWER', a decision 'Result?' follows. If 'Pass', it goes to 'Handle\_COLP\_Forwarding\_Interaction\_MSC', then 'Set COLP presentation indicator', then 'Send\_Answer\_If\_Required', then 'Call answered := True', and finally to connector '7'. If 'Else', it goes to 'Release'. From 'Release', it goes to 'CAMEL\_MT\_GMSC\_DISC4', then 'See TS 23.078', then 'Result-Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call', then 'Wait\_For\_Reconnected\_Call\_Result'. If 'No', it goes to 'Release', then 'Release call resources', then 'Idle'. From 'CAMEL\_MT\_GMSC\_DISC4', it also goes to 'CAMEL\_MT\_GMSC\_DISC6', then 'See TS 23.078', then 'Release'. From 'CAMEL\_MT\_GMSC\_ANSWER', if 'Else', it goes to 'CAMEL\_MT\_GMSC\_ANSWER'. From 'CAMEL\_MT\_GMSC\_ANSWER', a decision 'Result?' follows. If 'Pass', it goes to 'Handle\_COLP\_Forwarding\_Interaction\_MSC', then 'Set COLP presentation indicator', then 'Send\_Network\_Connect\_If\_Required', and finally to connector '6'. If 'Else', it goes to 'Release', then 'Idle'. A note at the top right indicates signal directions: 'Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the process MT\_CF\_MSC unless marked otherwise'. + +Figure 37a: Procedure Obtain\_Routeing\_Address (sheet 1) + +![Flowchart for Procedure Obtain_Routeing_Address. It starts with 'Wait_for_Routeing_Info', followed by 'Send Routeing Info negative response'. A decision 'If MT Roaming Retry is supported and MT Roaming Retry Indicator received?' follows. If 'Yes', it goes to 'Clear RoamingRetry Supported IE' -> 'Send Routeing Info' -> 'Wait_for_Routeing_Info'. If 'No', it goes to 'Call Released?'. If 'Yes', 'Result:= Aborted'. If 'No', 'SCUDIF_negative_SRI_response_handling' -> 'See TS 23.172'. Both lead to a 'Result' merge. From 'Result', 'Pass' leads to circle '4'. 'Fail' leads to 'OR_Handle_SRI_Negative_Response_(Own_PLMN)' -> 'See TS 23.079' or 'Retry Send Routeing Info' -> 'Wait_for_Routeing_Info'. From 'OR_Handle_SRI...', a 'Result=Pass?' decision follows. If 'Yes', 'Result:=Pass' -> circle 'X'. If 'No', 'Error=Unknown subscriber?' decision. If 'Yes', 'MOBILE_NUMBER_PORTABILITY_IN_QoHR' -> 'See TS 23.066'. If 'No', 'Result=Number ported?' decision. If 'Yes', 'Routeing address:= routeing number' -> 'Result:= Routeing number' -> circle 'X'. If 'No', 'Result:=Fail' -> circle 'X'.](a5404b7275b06497eecf9b5883604753_img.jpg) + +### Procedure Obtain\_Routeing\_Address + +ORA2(6) + +Procedure in a GMSC to determine the address to which a call should be routed + +Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the HLR + +``` + + graph TD + Start([Wait_for_Routeing_Info]) --> SendNeg[Send Routeing Info negative response] + SendNeg --> Decision1{If MT Roaming Retry is supported and MT Roaming Retry Indicator received?} + + Decision1 -- Yes --> ClearIE[Clear RoamingRetry Supported IE] + ClearIE --> SendInfo[Send Routeing Info] + SendInfo --> WaitInfo1([Wait_for_Routeing_Info]) + + Decision1 -- No --> CallReleased{Call Released?} + + CallReleased -- Yes --> ResultAborted[Result:= Aborted] + + CallReleased -- No --> SCUDIF[SCUDIF_negative_SRI_response_handling] + SCUDIF --> TS23172[See TS 23.172] + + ResultAborted --> ResultMerge((Result)) + TS23172 --> ResultMerge + + ResultMerge -- Pass --> Circle4((4)) + + ResultMerge -- Fail --> ORHandle[OR_Handle_SRI_Negative_Response_(Own_PLMN)] + ORHandle --> TS23079[See TS 23.079] + + ResultMerge -- Fail --> RetrySend[Retry Send Routeing Info] + RetrySend --> WaitInfo2([Wait_for_Routeing_Info]) + + ORHandle --> ResultPass{Result=Pass?} + + ResultPass -- Yes --> ResultPassVal[Result:=Pass] + ResultPassVal --> CircleX1((X)) + + ResultPass -- No --> ErrorUnknown{Error=Unknown subscriber?} + + ErrorUnknown -- Yes --> MOBILE[MOBILE_NUMBER_PORTABILITY_IN_QoHR] + MOBILE --> TS23066[See TS 23.066] + + ErrorUnknown -- No --> ResultNumberPorted{Result=Number ported?} + + ResultNumberPorted -- Yes --> RouteingAddr[Routeing address:= routeing number] + RouteingAddr --> ResultRouteing[Result:= Routeing number] + ResultRouteing --> CircleX2((X)) + + ResultNumberPorted -- No --> ResultFail[Result:=Fail] + ResultFail --> CircleX3((X)) + +``` + +Flowchart for Procedure Obtain\_Routeing\_Address. It starts with 'Wait\_for\_Routeing\_Info', followed by 'Send Routeing Info negative response'. A decision 'If MT Roaming Retry is supported and MT Roaming Retry Indicator received?' follows. If 'Yes', it goes to 'Clear RoamingRetry Supported IE' -> 'Send Routeing Info' -> 'Wait\_for\_Routeing\_Info'. If 'No', it goes to 'Call Released?'. If 'Yes', 'Result:= Aborted'. If 'No', 'SCUDIF\_negative\_SRI\_response\_handling' -> 'See TS 23.172'. Both lead to a 'Result' merge. From 'Result', 'Pass' leads to circle '4'. 'Fail' leads to 'OR\_Handle\_SRI\_Negative\_Response\_(Own\_PLMN)' -> 'See TS 23.079' or 'Retry Send Routeing Info' -> 'Wait\_for\_Routeing\_Info'. From 'OR\_Handle\_SRI...', a 'Result=Pass?' decision follows. If 'Yes', 'Result:=Pass' -> circle 'X'. If 'No', 'Error=Unknown subscriber?' decision. If 'Yes', 'MOBILE\_NUMBER\_PORTABILITY\_IN\_QoHR' -> 'See TS 23.066'. If 'No', 'Result=Number ported?' decision. If 'Yes', 'Routeing address:= routeing number' -> 'Result:= Routeing number' -> circle 'X'. If 'No', 'Result:=Fail' -> circle 'X'. + +Figure 37b: Procedure Obtain\_Routeing\_Address (sheet 2) + +![Flowchart for Procedure Obtain_Routeing_Address. The process starts with 'Wait for_Routeing_Info', followed by 'Send Routeing Info ack' (From HLR). A decision 'Call Released?' follows. If 'Yes', it goes to 'MSRN received?'. If 'No', it goes to 'SCUDIF_Check_Service_Availability' (See TS 23.172). Both lead to 'Result?'. From 'Result?', 'Continue' leads to 'second_SRI' -> 'Network Signal Info:= less preferred service' -> 'Send Routeing Info' -> 'Wait for_Routeing_Info'. 'second_SRI' also leads to connector '1'. From 'Result?', connector '4' leads to 'CAMEL supported?'. If 'Yes', it goes to 'CAMEL_MT_GMSC_INIT' (See TS 23.078) -> 'Result= MSRN?'. If 'No', it goes to connector '1'. From 'Result= MSRN?', 'Yes' leads to connector '3', 'No' leads to 'Result= Aborted?'. From 'Result= Aborted?', 'Yes' leads to 'Result:= Aborted' -> connector '2', 'No' leads to 'Result= Leg1_only?'. From 'Result= Leg1_only?', 'Yes' leads to 'Result:= Leg1_only' -> connector 'X', 'No' leads to connector '5'. From 'MSRN received?' (top), 'Yes' leads to 'Release Resources' -> connector 'X', 'No' leads to 'Result:= Aborted' -> connector 'X'. From 'CAMEL supported?', 'No' also leads to connector '1'. From 'CAMEL_MT_GMSC_INIT', 'No' leads to connector '1'. From 'SCUDIF_Check_Service_Availability', 'No' leads to connector '2'.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +### Procedure Obtain\_Routeing\_Address + +ORA3(6) + +Procedure in a GMSC to determine the address to which a call should be routed + +``` +graph TD; Start([Wait for_Routeing_Info]) --> SendAck{{Send Routeing Info ack}}; SendAck --> FromHLR[From HLR]; SendAck --> CallReleased{Call Released?}; CallReleased -- Yes --> MSRNRec{MSRN received?}; CallReleased -- No --> SCUDIFCheck[SCUDIF_Check_Service_Availability]; SCUDIFCheck --> TS23172[See TS 23.172]; SCUDIFCheck --> Result1{Result?}; MSRNRec -- Yes --> ReleaseRes[Release Resources]; MSRNRec -- No --> ResultAborted1[Result:= Aborted]; ReleaseRes --> X1((X)); ResultAborted1 --> X2((X)); Result1 -- Continue --> secondSRI[second_SRI]; secondSRI --> NetSignal[Network Signal Info:= less preferred service]; NetSignal --> SendInfo[Send Routeing Info]; SendInfo --> WaitInfo[Wait for_Routeing_Info]; secondSRI --> C1((1)); Result1 -- 4 --> CAMELSupported{CAMEL supported?}; CAMELSupported -- Yes --> CAMELInit[CAMEL_MT_GMSC_INIT]; CAMELInit --> TS23078[See TS 23.078]; CAMELInit --> ResultMSRN{Result= MSRN?}; CAMELSupported -- No --> C1; CAMELInit -- No --> C1; ResultMSRN -- Yes --> C3_1((3)); ResultMSRN -- No --> ResultAborted2{Result= Aborted?}; ResultAborted2 -- Yes --> ResultAborted2_out[Result:= Aborted]; ResultAborted2_out --> C2((2)); ResultAborted2 -- No --> ResultLeg1{Result= Leg1_only?}; ResultLeg1 -- Yes --> ResultLeg1_out[Result:= Leg1_only]; ResultLeg1_out --> X3((X)); ResultLeg1 -- No --> C5((5)); +``` + +Flowchart for Procedure Obtain\_Routeing\_Address. The process starts with 'Wait for\_Routeing\_Info', followed by 'Send Routeing Info ack' (From HLR). A decision 'Call Released?' follows. If 'Yes', it goes to 'MSRN received?'. If 'No', it goes to 'SCUDIF\_Check\_Service\_Availability' (See TS 23.172). Both lead to 'Result?'. From 'Result?', 'Continue' leads to 'second\_SRI' -> 'Network Signal Info:= less preferred service' -> 'Send Routeing Info' -> 'Wait for\_Routeing\_Info'. 'second\_SRI' also leads to connector '1'. From 'Result?', connector '4' leads to 'CAMEL supported?'. If 'Yes', it goes to 'CAMEL\_MT\_GMSC\_INIT' (See TS 23.078) -> 'Result= MSRN?'. If 'No', it goes to connector '1'. From 'Result= MSRN?', 'Yes' leads to connector '3', 'No' leads to 'Result= Aborted?'. From 'Result= Aborted?', 'Yes' leads to 'Result:= Aborted' -> connector '2', 'No' leads to 'Result= Leg1\_only?'. From 'Result= Leg1\_only?', 'Yes' leads to 'Result:= Leg1\_only' -> connector 'X', 'No' leads to connector '5'. From 'MSRN received?' (top), 'Yes' leads to 'Release Resources' -> connector 'X', 'No' leads to 'Result:= Aborted' -> connector 'X'. From 'CAMEL supported?', 'No' also leads to connector '1'. From 'CAMEL\_MT\_GMSC\_INIT', 'No' leads to connector '1'. From 'SCUDIF\_Check\_Service\_Availability', 'No' leads to connector '2'. + +Figure 37c: Procedure Obtain\_Routeing\_Address (sheet 3) + +![Flowchart for Procedure Obtain_Routeing_Address](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +### Procedure Obtain\_Routeing\_Address + +ORA4(6) + +Procedure in a GMSC to determine the address to which a call should be routed + +``` +graph TD; Start((3)) --> SCUDIF[SCUDIF_Check_Service_Compatibility]; SCUDIF -.-> TS23.172[See TS 23.172]; SCUDIF --> CCBS[CCBS_MT_GMSC_Check_CCBS_Indicators]; CCBS -.-> TS23.093[See TS 23.093]; CCBS --> Store[Store Forwarding Interrogation Required Indicator]; Store --> MSRN_Q{MSRN contains a Routeing number?}; MSRN_Q -- No --> Routeing[Routeing address:= MSRN]; MSRN_Q -- Yes --> MNP[MNP_MT_GMSC_Check_MNP_Indicators]; MNP -.-> TS23.066[See TS 23.066]; MNP --> Result_Fail_Q{Result= Fail?}; Result_Fail_Q -- Yes --> Result_Fail[Result:= Fail]; Result_Fail_Q -- No --> Routeing_MSRN[Routeing address:= MSRN]; Routeing --> Dest[Destination address:= VMSC address]; Dest --> Result_Pass[Result:= Pass]; Routeing_MSRN --> Result_Routeing[Result:= Routeing number]; Result_Fail --> End1((X)); Result_Routeing --> End2((X)); Result_Pass --> End3((X)); +``` + +The flowchart illustrates the 'Procedure Obtain\_Routeing\_Address' within a GMSC. It begins with a connector '3' leading to 'SCUDIF\_Check\_Service\_Compatibility' (referencing TS 23.172), followed by 'CCBS\_MT\_GMSC\_Check\_CCBS\_Indicators' (referencing TS 23.093). The next step is 'Store Forwarding Interrogation Required Indicator'. A decision diamond asks 'MSRN contains a Routeing number?'. If 'No', 'Routeing address:= MSRN' is set. If 'Yes', it proceeds to 'MNP\_MT\_GMSC\_Check\_MNP\_Indicators' (referencing TS 23.066). From there, a decision diamond asks 'Result= Fail?'. If 'Yes', 'Result:= Fail' is set. If 'No', 'Routeing address:= MSRN' is set. Both 'Routeing address:= MSRN' and 'Routeing address:= VMSC address' lead to 'Result:= Pass'. All three final results ('Result:= Fail', 'Result:= Routeing number', and 'Result:= Pass') lead to terminal connectors. + +Flowchart for Procedure Obtain\_Routeing\_Address + +Figure 37d: Procedure Obtain\_Routeing\_Address (sheet 4) + +![Flowchart for Procedure Obtain_Routeing_Address. It starts at connector 5, goes to a 'Result= Fail' decision. If 'Yes', it goes to a 'Result= Fail' block and then to connector 3. If 'No', it goes to a 'Result' decision. From 'Result', 'CAMEL_FTN' leads to a 'SCUDIF_Check_Service_Compatibility' block (referencing TS 23.172) and then to connector 2. 'GSM_FTN' leads to a 'CAMEL_MT_GMSC_Notify_CF' block (referencing TS 23.078), which then leads to another 'Result' decision. From this 'Result', 'Continue' leads back to the first 'Result' decision, 'Fail' leads to the 'Result= Fail' block, and 'Reconnect' leads to a 'Reconnect := True' block and then to connector 1.](17431d8b59408f09df7552d8bdbaa015_img.jpg) + +**Procedure Obtain\_Routeing\_Address** ORA5(6) + +*Procedure in a GMSC to determine the address to which a call should be routed* + +``` +graph TD; 5((5)) --> R1{Result= Fail}; R1 -- Yes --> RF[Result= Fail]; RF --> 3((3)); R1 -- No --> R2{Result}; R2 -- CAMEL_FTN --> SC[SCUDIF_Check_Service_Compatibility]; SC -.-> TS23172[See TS 23.172]; SC --> 2((2)); R2 -- GSM_FTN --> CM[["CAMEL
MT_GMSC
Notify_CF"]]; CM -.-> TS23078[See TS 23.078]; CM --> R3{Result}; R3 -- Continue --> R2; R3 -- Fail --> RF; R3 -- Reconnect --> RT[Reconnect := True]; RT --> 1((1)); +``` + +Flowchart for Procedure Obtain\_Routeing\_Address. It starts at connector 5, goes to a 'Result= Fail' decision. If 'Yes', it goes to a 'Result= Fail' block and then to connector 3. If 'No', it goes to a 'Result' decision. From 'Result', 'CAMEL\_FTN' leads to a 'SCUDIF\_Check\_Service\_Compatibility' block (referencing TS 23.172) and then to connector 2. 'GSM\_FTN' leads to a 'CAMEL\_MT\_GMSC\_Notify\_CF' block (referencing TS 23.078), which then leads to another 'Result' decision. From this 'Result', 'Continue' leads back to the first 'Result' decision, 'Fail' leads to the 'Result= Fail' block, and 'Reconnect' leads to a 'Reconnect := True' block and then to connector 1. + +Figure 37e: Procedure Obtain\_Routeing\_Address (sheet 5) + +![Flowchart for Procedure Obtain_Routeing_Address. It starts with a connector '2', followed by 'BOR:=OR', 'Activate_CF_Process', and a 'Result?' decision. If 'Fail', it goes to 'Release' and 'Result:= Aborted'. If 'Pass', it goes to 'CCBS_MT_GMSC_Remove_Indicators_Store_FWT' (See TS 23.093), then 'Route_Permitted (OR, FTN, Reference Address)' (See TS 23.079). A 'Route permitted' decision follows. If 'False', it goes to a merge point. If 'True', it sets 'Routeing address:= FTN', 'Destination address:= FTN', 'OR:=True', and 'Result:= Forward'. A 'CAMEL phase 2 or higher supported?' decision follows the merge point. If 'No', it goes to 'CAMEL_MT_GMSC_DISC3' (See TS 23.078). If 'Yes', it goes to 'CAMEL_MT_GMSC_DISC4' (See TS 23.078). Both lead to a 'CF cancelled' merge point (To process MT_CF_MSC). From there, it sets 'Routeing address:= Reference address', 'Destination address:= Reference address', 'OR:=False', and 'Result:= Pass'.](6e9d059430baba0c363e33749f68b107_img.jpg) + +**Procedure Obtain\_Routeing\_Address** ORA6(6) + +*Procedure in a GMSC to determine the address to which a call should be routed* + +``` +graph TD; Start((2)) --> BOR[ BOR:=OR ]; BOR --> Activate[ Activate_CF_Process ]; Activate --> Result{ Result? }; Result -- Fail --> Release{{ Release }}; Release --> Aborted[ Result:= Aborted ]; Aborted --> End1(( )); Result -- Pass --> CCBS[ CCBS_MT_GMSC_Remove_Indicators_Store_FWT ]; CCBS -.-> TS1[ See TS 23.093 ]; CCBS --> RoutePerm[ Route_Permitted OR, FTN, Reference Address ]; RoutePerm -.-> TS2[ See TS 23.079 ]; RoutePerm --> RoutePermitted{ Route permitted }; RoutePermitted -- True --> RA1[ Routeing address:= FTN ]; RA1 --> DA1[ Destination address:= FTN ]; DA1 --> OR1[ OR:=True ]; OR1 --> Res1[ Result:= Forward ]; Res1 --> End2(( )); RoutePermitted -- False --> Merge1{ }; Merge1 --> CAMELPhase{ CAMEL phase 2 or higher supported? }; CAMELPhase -- No --> DISC3[ CAMEL_MT_GMSC_DISC3 ]; DISC3 -.-> TS3[ See TS 23.078 ]; CAMELPhase -- Yes --> DISC4[ CAMEL_MT_GMSC_DISC4 ]; DISC4 -.-> TS4[ See TS 23.078 ]; DISC3 --> CFCancelled{{ CF cancelled }}; DISC4 --> CFCancelled; CFCancelled -.-> ToProcess[ To process MT_CF_MSC ]; CFCancelled --> RA2[ Routeing address:= Reference address ]; RA2 --> DA2[ Destination address:= Reference address ]; DA2 --> OR2[ OR:=False ]; OR2 --> Res2[ Result:= Pass ]; Res2 --> End3(( )); +``` + +Flowchart for Procedure Obtain\_Routeing\_Address. It starts with a connector '2', followed by 'BOR:=OR', 'Activate\_CF\_Process', and a 'Result?' decision. If 'Fail', it goes to 'Release' and 'Result:= Aborted'. If 'Pass', it goes to 'CCBS\_MT\_GMSC\_Remove\_Indicators\_Store\_FWT' (See TS 23.093), then 'Route\_Permitted (OR, FTN, Reference Address)' (See TS 23.079). A 'Route permitted' decision follows. If 'False', it goes to a merge point. If 'True', it sets 'Routeing address:= FTN', 'Destination address:= FTN', 'OR:=True', and 'Result:= Forward'. A 'CAMEL phase 2 or higher supported?' decision follows the merge point. If 'No', it goes to 'CAMEL\_MT\_GMSC\_DISC3' (See TS 23.078). If 'Yes', it goes to 'CAMEL\_MT\_GMSC\_DISC4' (See TS 23.078). Both lead to a 'CF cancelled' merge point (To process MT\_CF\_MSC). From there, it sets 'Routeing address:= Reference address', 'Destination address:= Reference address', 'OR:=False', and 'Result:= Pass'. + +Figure 37f: Procedure Obtain\_Routeing\_Address (sheet 6) + +![Flowchart for Procedure Send_ACM_If_Required. It starts with a connector symbol, followed by a decision 'ACM sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to another decision 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Address Complete', then 'ACM sent := True', and finally to an exit connector. Both 'Call Progress' and the exit connector lead to the same point.](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +### Procedure Send\_ACM\_If\_Required + +SACMIR1(1) + +Procedure to send an Address Complete Message to the preceding exchange if one is required for this call + +Signals to the left are to the originating exchange + +``` +graph TD; Start([ ]) --> ACM_Sent{ACM sent}; ACM_Sent -- True --> Call_Progress{{Call Progress}}; ACM_Sent -- False --> Network_Connect_Sent{Network connect sent}; Network_Connect_Sent -- True --> Call_Progress; Network_Connect_Sent -- False --> Address_Complete{{Address Complete}}; Address_Complete --> ACM_Sent_True[ACM sent := True]; ACM_Sent_True --> Exit(( )); Call_Progress --> Exit; +``` + +Flowchart for Procedure Send\_ACM\_If\_Required. It starts with a connector symbol, followed by a decision 'ACM sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to another decision 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Address Complete', then 'ACM sent := True', and finally to an exit connector. Both 'Call Progress' and the exit connector lead to the same point. + +Figure 38: Procedure Send\_ACM\_If\_Required + +![Flowchart for Procedure Send_Answer_If_Required. It starts with an oval connector, followed by a decision diamond 'Answer sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to another decision diamond 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Answer', then 'Answer sent:= True', and finally to a circle connector. Arrows pointing left indicate signals to the originating exchange.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +### Procedure Send\_Answer\_If\_Required + +SANMIR1(1) + +Procedure to send an Answer Message to the preceding exchange if one is required for this call + +Signals to the left are to the originating exchange + +``` +graph TD; Start([ ]) --> D1{Answer sent}; D1 -- True --> CP{{Call Progress}}; D1 -- False --> D2{Network connect sent}; D2 -- True --> CP; D2 -- False --> A{{Answer}}; A --> AS[Answer sent:= True]; AS --> End(( )); CP --> End; style Start fill:none,stroke:none; style End fill:none,stroke:none; +``` + +Flowchart for Procedure Send\_Answer\_If\_Required. It starts with an oval connector, followed by a decision diamond 'Answer sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to another decision diamond 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Answer', then 'Answer sent:= True', and finally to a circle connector. Arrows pointing left indicate signals to the originating exchange. + +Figure 39: Procedure Send\_Answer\_If\_Required + +![Flowchart for Procedure Send_Network_Connect_If_Required. It starts with an oval connector, followed by a decision 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Answer sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'ACM sent'. If 'True', it goes to 'Answer', then 'Answer sent := True'. If 'False', it goes to 'Connect', then 'Connect sent := True'. Both 'Answer sent := True' and 'Connect sent := True' lead to a circle with an X (exit). A 'Call Progress' block also leads to the exit.](cc7baa8e5118f4b42c01166637c738ea_img.jpg) + +### Procedure Send\_Network\_Connect\_If\_Required + +SNCONIR1(1) + +Procedure to send a Connect Message to the preceding exchange if one is required for this call + +Signals to the left are to the originating exchange + +``` +graph TD; Start([ ]) --> D1{Network connect sent}; D1 -- True --> CP{{Call Progress}}; D1 -- False --> D2{Answer sent}; D2 -- True --> CP; D2 -- False --> D3{ACM sent}; D3 -- True --> Answer{{Answer}}; D3 -- False --> Connect{{Connect}}; Answer --> AS[Answer sent := True]; Connect --> CS[Connect sent := True]; CP --> Exit((X)); AS --> Exit; CS --> Exit; +``` + +Flowchart for Procedure Send\_Network\_Connect\_If\_Required. It starts with an oval connector, followed by a decision 'Network connect sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'Answer sent'. If 'True', it goes to 'Call Progress'. If 'False', it goes to 'ACM sent'. If 'True', it goes to 'Answer', then 'Answer sent := True'. If 'False', it goes to 'Connect', then 'Connect sent := True'. Both 'Answer sent := True' and 'Connect sent := True' lead to a circle with an X (exit). A 'Call Progress' block also leads to the exit. + +**Figure 40: Procedure Send\_Network\_Connect\_If\_Required** + +![MSC diagram for Procedure Handle_COLP_Forwarding_Interaction_MSC. The flow starts with a note about the procedure's location, followed by a start connector, an 'Initiate handling of COLP' process, a 'Wait_For_COLP_Info' state, a decision point leading to 'Release' or 'continue call handling', and finally an end connector. Callouts explain the symbols and signal directions.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +### Procedure Handle\_COLP\_Forwarding\_Interaction\_MSC + +COINT\_M1(1) + +``` +graph TD; Start(( )) --> Init[Initiate handling of COLP]; Init --> Wait[Wait_For_COLP_Info]; Wait --> Decision{ }; Decision -- Release --> ReleaseText[From originating exchange or destination exchange]; Decision -- continue --> Continue[continue call handling]; Continue --> End(((X)))); +``` + +Procedure in the GMSC or VMSC to handle the interaction between COLP and Call Forwarding + +Signals to/from the right are to/from the process COLP\_MAF039 + +MSC diagram for Procedure Handle\_COLP\_Forwarding\_Interaction\_MSC. The flow starts with a note about the procedure's location, followed by a start connector, an 'Initiate handling of COLP' process, a 'Wait\_For\_COLP\_Info' state, a decision point leading to 'Release' or 'continue call handling', and finally an end connector. Callouts explain the symbols and signal directions. + +Figure 41: Procedure Handle\_COLP\_Forwarding\_Interaction\_MSC + +![Flowchart for Procedure Activate_CF_Process. It starts with a connector, followed by 'Perform call forwarding (BOR, FTN)', then 'Wait_For_CF_Response'. A decision point follows with four branches: 1) 'Release' -> 'CF cancelled' -> 'Result= Fail' -> connector; 2) 'Perform call forwarding ack' -> 'Result= Pass' -> connector; 3) 'Perform call forwarding negative response' -> 'Result= Fail' -> connector; 4) 'Int_Release_Call' (From gsmSSF) -> 'CF cancelled' -> 'Result= Release' -> connector.](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +### Procedure Activate\_CF\_Process + +ACFP1(1) + +Procedure in the MSC to initiate the process which handles call forwarding + +Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the process MT\_CF\_MSC unless marked otherwise + +``` +graph TD; Start([ ]) --> Step1[Perform call forwarding (BOR, FTN)]; Step1 --> Step2((Wait_For_CF_Response)); Step2 --> Decision{ }; Decision --> Branch1[Release]; Decision --> Branch2[Perform call forwarding ack]; Decision --> Branch3[Perform call forwarding negative response]; Decision --> Branch4[Int_Release_Call]; Branch1 --> CF_Canc1[CF cancelled]; CF_Canc1 --> Result1[Result= Fail]; Result1 --> End1(( )); Branch2 --> Result2[Result= Pass]; Result2 --> End2(( )); Branch3 --> Result3[Result= Fail]; Result3 --> End3(( )); Branch4 --> From_gsmSSF[From gsmSSF]; Branch4 --> CF_Canc2[CF cancelled]; CF_Canc2 --> Result4[Result= Release]; Result4 --> End4(( )); +``` + +Flowchart for Procedure Activate\_CF\_Process. It starts with a connector, followed by 'Perform call forwarding (BOR, FTN)', then 'Wait\_For\_CF\_Response'. A decision point follows with four branches: 1) 'Release' -> 'CF cancelled' -> 'Result= Fail' -> connector; 2) 'Perform call forwarding ack' -> 'Result= Pass' -> connector; 3) 'Perform call forwarding negative response' -> 'Result= Fail' -> connector; 4) 'Int\_Release\_Call' (From gsmSSF) -> 'CF cancelled' -> 'Result= Release' -> connector. + +Figure 42: Procedure Activate\_CF\_Process + +![SDL diagram for Process MT_CF_MSC (sheet 1). The flow starts at an Idle state, proceeds through 'Perform call forwarding' and 'CAMEL_CF_MSC_INIT'. Decisions follow for 'Result = Leg1_only?' and 'Result = Pass?'. If 'Pass', it goes to 'CAMEL_CF_Dialled_Services'. Further decisions lead to either 'Perform call forwarding ack(FTN)' and 'Wait_For_IAM' or to 'CAMEL_OCH_MSC1'. The diagram also shows handling for 'Initial Address', 'CF cancelled', and various CAMEL-related tasks like 'CAMEL_OCH_MSC_DISC3/4'. Final states include 'Idle', 'Wait_For_IAM', 'Wait_For_ACM'.](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +**Process MT\_CF\_MSC** **MTCFMSC1(6)** + +Process in the MSC +to handle call forwarding + +Signals to/from the left +are to/from the parent process; +signals to/from the right +are to/from the destination exchange + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Perform_call_forwarding + Perform_call_forwarding --> CAMEL_CF_MSC_INIT + CAMEL_CF_MSC_INIT --> Result_Leg1_only_Decision + Result_Leg1_only_Decision --> Leg1_status_Setup : Yes + Leg1_status_Setup --> CAMEL_MT_CF_LEG1_MSC + CAMEL_MT_CF_LEG1_MSC --> Idle_State + Result_Leg1_only_Decision --> Result_Pass_Decision : No + Result_Pass_Decision --> CAMEL_CF_Dialled_Services : Yes + Result_Pass_Decision --> Perform_Call_Forwarding_negative_response : No + CAMEL_CF_Dialled_Services --> Result_Decision + Result_Decision --> Perform_call_forwarding_ack_FTN : Pass + Result_Decision --> CAMEL_OCH_MSC1 : Fail + Result_Decision --> Idle_State : Abort + Result_Decision --> Leg1_only_State : Leg1_only + Perform_call_forwarding_ack_FTN --> Wait_For_IAM + Wait_For_IAM --> Initial_Address_Input + Initial_Address_Input --> MOBILE_NUMBER_PORTABILITY + MOBILE_NUMBER_PORTABILITY --> Initial_Address_Output + Initial_Address_Output --> CAMEL_Store_Destination_Address + CAMEL_Store_Destination_Address --> Wait_For_ACM + CAMEL_OCH_MSC1 --> Result_Reconnect_Decision + Result_Reconnect_Decision --> Perform_Call_Forwarding_negative_response : No + Result_Reconnect_Decision --> Connector_2 : Yes + Perform_Call_Forwarding_negative_response --> Result_Fail_Decision + Result_Fail_Decision --> Idle_State : Yes + CF_cancelled --> CAMEL_phase_2_supported_Decision + CAMEL_phase_2_supported_Decision --> CAMEL_OCH_MSC_DISC3 : No + CAMEL_phase_2_supported_Decision --> CAMEL_OCH_MSC_DISC4 : Yes + CAMEL_OCH_MSC_DISC3 --> Idle_State + CAMEL_OCH_MSC_DISC4 --> Idle_State + +``` + +**Key elements of the diagram:** + +- States:** Idle, Wait\_For\_IAM, Wait\_For\_ACM. +- Tasks:** Perform call forwarding, CAMEL\_CF\_MSC\_INIT, Leg1\_status := Set-up, CAMEL\_MT\_CF\_LEG1\_MSC (Leg1\_status), CAMEL\_CF\_Dialled\_Services, Perform call forwarding ack(FTN), CAMEL\_OCH\_MSC1, MOBILE\_NUMBER\_PORTABILITY\_IN\_OQoD, CAMEL\_Store\_Destination\_Address (BOR, True), CAMEL\_OCH\_MSC\_DISC3, CAMEL\_OCH\_MSC\_DISC4, Perform Call Forwarding negative response. +- Decisions:** Result = Leg1\_only?, Result = Pass?, Result?, Result = Reconnect?, Result = Fail?, CAMEL phase 2 or higher supported?. +- Signals:** Initial Address (Input/Output), CF cancelled (Input). +- References:** See TS 23.078, See TS 23.066. +- Connectors:** 1, 2, 4. + +SDL diagram for Process MT\_CF\_MSC (sheet 1). The flow starts at an Idle state, proceeds through 'Perform call forwarding' and 'CAMEL\_CF\_MSC\_INIT'. Decisions follow for 'Result = Leg1\_only?' and 'Result = Pass?'. If 'Pass', it goes to 'CAMEL\_CF\_Dialled\_Services'. Further decisions lead to either 'Perform call forwarding ack(FTN)' and 'Wait\_For\_IAM' or to 'CAMEL\_OCH\_MSC1'. The diagram also shows handling for 'Initial Address', 'CF cancelled', and various CAMEL-related tasks like 'CAMEL\_OCH\_MSC\_DISC3/4'. Final states include 'Idle', 'Wait\_For\_IAM', 'Wait\_For\_ACM'. + +**Figure 43a: Process MT\_CF\_MSC (sheet 1)** + +![SDL diagram for Process MT_CF_MSC (sheet 2). The diagram shows the logic for handling call forwarding in the MSC, starting from the 'Wait_For_ACM' state. It includes branches for 'Address Complete', 'Connect', and 'Answer' signals, with various CAMEL and UUS related tasks and decision points leading to states like 'Wait_For_Answer', 'Idle', or connectors 'A' and '2'.](da85343976fdbb19f866d9ddbdad0eae_img.jpg) + +### Process MT\_CF\_MSC + +MTCFMSC2(6) + +``` + +stateDiagram-v2 + state "Wait_For_ACM" as Wait_For_ACM + state "Address Complete" as Address_Complete_In + state "Connect" as Connect_In + state "CAMEL_Start_TNRy" as CAMEL_Start_TNRy + state "UUS_MSC_Clear_UUS" as UUS_MSC_Clear_UUS_1 + state "CAMEL_CF_MSC_ALERTING" as CAMEL_CF_MSC_ALERTING + state "Result?" as Result_1 + state "Address Complete" as Address_Complete_Out + state "Wait_For_Answer" as Wait_For_Answer + state "Answer" as Answer_In + state "CAMEL_Stop_TNRy" as CAMEL_Stop_TNRy + state "CAMEL_CF_MSC_ANSWER" as CAMEL_CF_MSC_ANSWER_1 + state "Result?" as Result_2 + state "UUS_MSC_Clear_UUS" as UUS_MSC_Clear_UUS_2 + state "Answer" as Answer_Out + state "A" as A_1 + state "UUS_MSC_Clear_UUS" as UUS_MSC_Clear_UUS_3 + state "CAMEL_CF_MSC_ANSWER" as CAMEL_CF_MSC_ANSWER_2 + state "Result?" as Result_3 + state "Connect" as Connect_Out + state "A" as A_2 + state "Result?" as Result_Final + state "2" as Connector_2 + state "Release" as Release_State + state "Idle" as Idle_State + + [*] --> Wait_For_ACM + Wait_For_ACM --> Address_Complete_In + Wait_For_ACM --> Connect_In + + Address_Complete_In --> CAMEL_Start_TNRy + CAMEL_Start_TNRy --> UUS_MSC_Clear_UUS_1 + UUS_MSC_Clear_UUS_1 --> CAMEL_CF_MSC_ALERTING + CAMEL_CF_MSC_ALERTING --> Result_1 + + Result_1 --> Address_Complete_Out : Pass + Result_1 --> Address_Complete_Out : Answer + Result_1 --> Result_Final : Else + + Address_Complete_Out --> Wait_For_Answer + Wait_For_Answer --> Answer_In + Answer_In --> CAMEL_Stop_TNRy + CAMEL_Stop_TNRy --> CAMEL_CF_MSC_ANSWER_1 + CAMEL_CF_MSC_ANSWER_1 --> Result_2 + + Result_2 --> UUS_MSC_Clear_UUS_2 : Pass + Result_2 --> Result_Final : Else + UUS_MSC_Clear_UUS_2 --> Answer_Out + Answer_Out --> A_1 + + Connect_In --> UUS_MSC_Clear_UUS_3 + UUS_MSC_Clear_UUS_3 --> CAMEL_CF_MSC_ANSWER_2 + CAMEL_CF_MSC_ANSWER_2 --> Result_3 + + Result_3 --> Connect_Out : Pass + Result_3 --> Result_Final : Else + Connect_Out --> A_2 + + Result_Final --> Connector_2 : Reconnect + Result_Final --> Release_State : Release + Result_Final --> Idle_State : Fail + Release_State --> Idle_State + +``` + +*Notes in diagram:* + - Process in the MSC to handle call forwarding + - Signals to/from the left are to/from the parent process; signals to/from the right are to/from the destination exchange + - See TS 23.078 (multiple locations) + - See TS 23.087 (multiple locations) + +SDL diagram for Process MT\_CF\_MSC (sheet 2). The diagram shows the logic for handling call forwarding in the MSC, starting from the 'Wait\_For\_ACM' state. It includes branches for 'Address Complete', 'Connect', and 'Answer' signals, with various CAMEL and UUS related tasks and decision points leading to states like 'Wait\_For\_Answer', 'Idle', or connectors 'A' and '2'. + +**Figure 43b: Process MT\_CF\_MSC (sheet 2)** + +![State transition diagram for Process MT_CF_MSC. It starts at 'Wait_For_ACM, Wait_For_Answer' and branches into 'Release' (left), 'Release' (middle), and 'Int_O_Release' (right, from gsmSSF). The middle 'Release' path includes a 'CAMEL_phase_2 or higher supported?' decision, a 'Release cause= No answer from user?' check, and a 'Result= Reconnect?' decision leading to 'CAMEL_Stop_TNRy' or connector '2'. All paths lead to 'Release call resources' and then 'Idle'.](c21bad844b5cb6026c067a1f43ce67c3_img.jpg) + +### Process MT\_CF\_MSC + +MTCFMSC3(6) + +Process in the MSC to handle call forwarding + +Signals to/from the left are to/from the parent process; signals to/from the right are to/from the destination exchange unless marked otherwise + +``` +stateDiagram-v2 + [*] --> Wait_For_ACM_Wait_For_Answer : Wait_For_ACM, Wait_For_Answer + state "Wait_For_ACM, Wait_For_Answer" as Wait_For_ACM_Wait_For_Answer + state "Release" as Release_L + state "Release" as Release_M + state "Int_O_Release" as Int_O_Release + state "CAMEL_phase_2 or higher supported?" as CAMEL_P2_Supported_L + state "CAMEL_phase_2 or higher supported?" as CAMEL_P2_Supported_M + state "Release cause= No answer from user?" as Release_Cause + state "CAMEL_OCH_MSC_DISC3" as CAMEL_OCH_DISC3_L + state "CAMEL_OCH_MSC_DISC4" as CAMEL_OCH_DISC4 + state "CAMEL_OCH_MSC_DISC3" as CAMEL_OCH_DISC3_M + state "CAMEL_OCH_MSC1" as CAMEL_OCH_MSC1 + state "Result= Reconnect?" as Result_Reconnect + state "CAMEL_Stop_TNRy" as CAMEL_Stop_TNRy + state "Release" as Release_R + state "Release call resources" as Release_Resources + state "Idle" as Idle + state "3" as Connector_3 + state "2" as Connector_2 + + Note right of Wait_For_ACM_Wait_For_Answer : From gsmSSF + Note right of CAMEL_OCH_MSC1 : See TS 23.078 + Note right of CAMEL_Stop_TNRy : See TS 23.078 + + Wait_For_ACM_Wait_For_Answer --> Release_L + Wait_For_ACM_Wait_For_Answer --> Release_M + Wait_For_ACM_Wait_For_Answer --> Int_O_Release + + Release_L --> CAMEL_P2_Supported_L + CAMEL_P2_Supported_L --> No_L + CAMEL_P2_Supported_L --> Yes_L + No_L --> CAMEL_OCH_DISC3_L + Yes_L --> CAMEL_OCH_DISC4 + + Release_M --> CAMEL_P2_Supported_M + CAMEL_P2_Supported_M --> No_M + CAMEL_P2_Supported_M --> Yes_M + No_M --> CAMEL_OCH_DISC3_M + Yes_M --> Release_Cause + Release_Cause --> Yes_Cause + Release_Cause --> No_Cause + No_Cause --> Connector_3 + Yes_Cause --> CAMEL_OCH_MSC1 + + Int_O_Release --> Release_R + Release_R --> Release_Resources + + CAMEL_OCH_DISC3_L --> Release_L + CAMEL_OCH_DISC4 --> Release_L + CAMEL_OCH_DISC3_M --> Release_M + CAMEL_OCH_MSC1 --> Result_Reconnect + Result_Reconnect --> No_Reconnect + Result_Reconnect --> Yes_Reconnect + No_Reconnect --> Release_M + Yes_Reconnect --> CAMEL_Stop_TNRy + CAMEL_Stop_TNRy --> Connector_2 + + Release_L --> Release_Resources + Release_M --> Release_Resources + Connector_2 --> Release_Resources + Release_Resources --> Idle +``` + +State transition diagram for Process MT\_CF\_MSC. It starts at 'Wait\_For\_ACM, Wait\_For\_Answer' and branches into 'Release' (left), 'Release' (middle), and 'Int\_O\_Release' (right, from gsmSSF). The middle 'Release' path includes a 'CAMEL\_phase\_2 or higher supported?' decision, a 'Release cause= No answer from user?' check, and a 'Result= Reconnect?' decision leading to 'CAMEL\_Stop\_TNRy' or connector '2'. All paths lead to 'Release call resources' and then 'Idle'. + +Figure 43c: Process MT\_CF\_MSC (sheet 3) + +![State transition diagram for Process MT_CF_MSC. The process starts in 'Wait_For_Answer' state. An 'Internal' event 'TNRy expired' leads to a 'Release' state. A transition labeled '3' leads to 'CAMEL_OCH_MSC2' (See TS 23.078). From 'CAMEL_OCH_MSC2', a 'Result?' decision diamond has three paths: 'Release' (leading to a 'Release' state), 'Reconnect' (leading to a circle labeled '2'), and 'Fail' (leading to 'CAMEL_CF_Dialled_Services' (See TS 23.078)). From 'CAMEL_CF_Dialled_Services', another 'Result?' decision diamond has three paths: 'Abort' (leading back to the transition between 'Release' and 'CAMEL_OCH_MSC2'), 'Pass' (leading to a circle labeled '1'), and 'Fail' (leading to 'CAMEL_OCH_MSC1' (See TS 23.078)). From 'CAMEL_OCH_MSC1', a 'Result=Reconnect?' decision diamond has two paths: 'Yes' (leading to a circle labeled '2') and 'No' (leading to 'Perform Call Forwarding negative response' which then leads to an 'Idle' state). From the 'Fail' path of the first 'Result?' diamond, there is also a path to 'Release call resources' (See TS 23.078) which leads to an 'Idle' state. Two notes are present: 'Process in the MSC to handle call forwarding' and 'Signals to/from the left are to/from the parent process; signals to/from the right are to/from the destination exchange unless marked otherwise'.](b50f38be091844d58b11e3d47bc71e73_img.jpg) + +### Process MT\_CF\_MSC + +MTCFMSC4(6) + +``` +stateDiagram-v2 + [*] --> Wait_For_Answer + state "TNRy expired" as TNRy_expired + TNRy_expired --> Release + Release --> CAMEL_OCH_MSC2 + state "CAMEL_OCH_MSC2" as CAMEL_OCH_MSC2 + CAMEL_OCH_MSC2 --> Result1{Result?} + Result1 --> Release1[Release] + Result1 --> Reconnect1((2)) + Result1 --> Fail1[Fail] + Fail1 --> CAMEL_CF_Dialled_Services + state "CAMEL_CF_Dialled_Services" as CAMEL_CF_Dialled_Services + CAMEL_CF_Dialled_Services --> Result2{Result?} + Result2 --> Abort(( )) + Result2 --> Pass1((1)) + Result2 --> Fail2[Fail] + Fail2 --> CAMEL_OCH_MSC1 + state "CAMEL_OCH_MSC1" as CAMEL_OCH_MSC1 + CAMEL_OCH_MSC1 --> Result3{Result=Reconnect?} + Result3 --> Yes((2)) + Result3 --> No[No] + No --> Perform_Call_Forwarding_Negative_Response{Perform Call Forwarding negative response} + Perform_Call_Forwarding_Negative_Response --> Idle1[Idle] + Abort --> Release + Release --> ReleaseCallResources[Release call resources] + ReleaseCallResources --> Idle2[Idle] +``` + +State transition diagram for Process MT\_CF\_MSC. The process starts in 'Wait\_For\_Answer' state. An 'Internal' event 'TNRy expired' leads to a 'Release' state. A transition labeled '3' leads to 'CAMEL\_OCH\_MSC2' (See TS 23.078). From 'CAMEL\_OCH\_MSC2', a 'Result?' decision diamond has three paths: 'Release' (leading to a 'Release' state), 'Reconnect' (leading to a circle labeled '2'), and 'Fail' (leading to 'CAMEL\_CF\_Dialled\_Services' (See TS 23.078)). From 'CAMEL\_CF\_Dialled\_Services', another 'Result?' decision diamond has three paths: 'Abort' (leading back to the transition between 'Release' and 'CAMEL\_OCH\_MSC2'), 'Pass' (leading to a circle labeled '1'), and 'Fail' (leading to 'CAMEL\_OCH\_MSC1' (See TS 23.078)). From 'CAMEL\_OCH\_MSC1', a 'Result=Reconnect?' decision diamond has two paths: 'Yes' (leading to a circle labeled '2') and 'No' (leading to 'Perform Call Forwarding negative response' which then leads to an 'Idle' state). From the 'Fail' path of the first 'Result?' diamond, there is also a path to 'Release call resources' (See TS 23.078) which leads to an 'Idle' state. Two notes are present: 'Process in the MSC to handle call forwarding' and 'Signals to/from the left are to/from the parent process; signals to/from the right are to/from the destination exchange unless marked otherwise'. + +Figure 43d: Process MT\_CF\_MSC (sheet 4) + +![State transition diagram for Process MT_CF_MSC. The diagram shows two main parts. The top part starts with 'Wait_For_Clear' leading to three parallel 'Release' paths. The left path goes through 'CAMEL_OCH_MSC_DISC1' (See TS 23.078) to a 'Result_CAMEL_Handling?' decision. The middle path goes through 'CAMEL_OCH_MSC_DISC2' (See TS 23.078) to a 'Result_CAMEL_Handling?' decision, which then leads to a 'Result_Reconnect?' decision. The right path is an 'Int_Q_Release' from 'gsmSSF' followed by a 'Release'. All three paths converge to 'Release call resources' and then 'Idle'. The bottom part starts with a '*' state, leading to two parallel paths with '*' and '-' states, which converge to a final '-' state.](72d448a65347c51989171748789c7d4b_img.jpg) + +### Process MT\_CF\_MSC + +MTCFMSC5(6) + +Process in the MSC to handle call forwarding + +Signals to/from the left are to/from the parent process; signals to/from the right are to/from the destination exchange unless marked otherwise + +``` +stateDiagram-v2 + [*] --> Wait_For_Clear + state "Process MT_CF_MSC" as MT_CF_MSC { + [*] --> Wait_For_Clear + Wait_For_Clear --> Release1[Release] + Wait_For_Clear --> Release2[Release] + Wait_For_Clear --> Int_Q_Release[Int_Q_Release] + Int_Q_Release --> From_gsmSSF[From gsmSSF] + Release1 --> CAMEL_OCH_MSC_DISC1[CAMEL_OCH_MSC_DISC1] + CAMEL_OCH_MSC_DISC1 --> See_TS_23_078_1[See TS 23.078] + See_TS_23_078_1 --> Result_CAMEL_Handling1{Result_CAMEL_Handling?} + Result_CAMEL_Handling1 -- Yes --> Release3[Release] + Result_CAMEL_Handling1 -- No --> Release3 + Release2 --> CAMEL_OCH_MSC_DISC2[CAMEL_OCH_MSC_DISC2] + CAMEL_OCH_MSC_DISC2 --> See_TS_23_078_2[See TS 23.078] + See_TS_23_078_2 --> Result_CAMEL_Handling2{Result_CAMEL_Handling?} + Result_CAMEL_Handling2 -- Yes --> Release3 + Result_CAMEL_Handling2 -- No --> Result_Reconnect{Result_Reconnect?} + Result_Reconnect -- Yes --> 2((2)) + Result_Reconnect -- No --> Release3 + Int_Q_Release --> Release4[Release] + Release3 --> Release_call_resources[Release call resources] + Release4 --> Release_call_resources + Release_call_resources --> Idle[Idle] + } + [*] --> Asterisk1[*] + Asterisk1 --> Asterisk2[*] + Asterisk1 --> Dash1[-] + Asterisk2 --> Asterisk3[*] + Asterisk2 --> Dash2[-] + Dash1 --> Dash3[-] + Dash2 --> Dash3 +``` + +State transition diagram for Process MT\_CF\_MSC. The diagram shows two main parts. The top part starts with 'Wait\_For\_Clear' leading to three parallel 'Release' paths. The left path goes through 'CAMEL\_OCH\_MSC\_DISC1' (See TS 23.078) to a 'Result\_CAMEL\_Handling?' decision. The middle path goes through 'CAMEL\_OCH\_MSC\_DISC2' (See TS 23.078) to a 'Result\_CAMEL\_Handling?' decision, which then leads to a 'Result\_Reconnect?' decision. The right path is an 'Int\_Q\_Release' from 'gsmSSF' followed by a 'Release'. All three paths converge to 'Release call resources' and then 'Idle'. The bottom part starts with a '\*' state, leading to two parallel paths with '\*' and '-' states, which converge to a final '-' state. + +Figure 43e: Process MT\_CF\_MSC (sheet 5) + +![Flowchart for Process MT_CF_MSC. It starts at node 'A', goes to a decision 'CAMEL phase 4 or later control relationship exists?'. If 'No', it goes to 'Wait_For_Clear'. If 'Yes', it goes to 'CAMEL_MT CF_LEG2_MSC' (referencing TS 23.078), then 'Leg1_status := Active', then 'CAMEL_MT CF_LEG1_MSC (Leg1_status)' (referencing TS 23.078), and finally to 'Idle'.](3ec35c497a0765a1a885c85f214b1bef_img.jpg) + +**Process MT\_CF\_MSC** **MTCFMSC6(6)** + +Process in the MSC +to handle call forwarding + +``` +graph TD; A((A)) --> Decision{CAMEL phase 4 or later control relationship exists?}; Decision -- No --> Wait_For_Clear([Wait_For_Clear]); Decision -- Yes --> CAMEL_MT_CF_LEG2_MSC[CAMEL_MT CF_LEG2_MSC]; Note1[See TS 23.078] -.-> CAMEL_MT_CF_LEG2_MSC; CAMEL_MT_CF_LEG2_MSC --> Leg1_status[Leg1_status := Active]; Leg1_status --> CAMEL_MT_CF_LEG1_MSC[CAMEL_MT CF_LEG1_MSC (Leg1_status)]; Note2[See TS 23.078] -.-> CAMEL_MT_CF_LEG1_MSC; CAMEL_MT_CF_LEG1_MSC --> Idle([Idle]); +``` + +Flowchart for Process MT\_CF\_MSC. It starts at node 'A', goes to a decision 'CAMEL phase 4 or later control relationship exists?'. If 'No', it goes to 'Wait\_For\_Clear'. If 'Yes', it goes to 'CAMEL\_MT CF\_LEG2\_MSC' (referencing TS 23.078), then 'Leg1\_status := Active', then 'CAMEL\_MT CF\_LEG1\_MSC (Leg1\_status)' (referencing TS 23.078), and finally to 'Idle'. + +**Figure 43f: Process MT\_CF\_MSC (sheet 6)** + +![Flowchart for Macro CUG_Support_Check_GMSC](24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg) + +**Macrodefinition CUG\_Support\_Check\_GMSC** **CUG\_SC1(1)** + +Macro to check support of CUG in GMSC, if needed, and check if call can continue. + +``` +graph TD; Start([ ]) --> CUG_Info{CUG info present?}; CUG_Info -- No --> Pass((Pass)); CUG_Info -- Yes --> GMSC_Support{GMSC supports CUG?}; GMSC_Support -- No --> Pass; GMSC_Support -- Yes --> Outgoing_Access{Outgoing Access present?}; Outgoing_Access -- Yes --> Pass; Outgoing_Access -- No --> Fail((Fail)); +``` + +The flowchart illustrates the logic for the macro CUG\_Support\_Check\_GMSC. It begins with a start symbol leading to a decision diamond 'CUG info present?'. If 'No', it proceeds to a 'Pass' terminal. If 'Yes', it proceeds to a decision diamond 'GMSC supports CUG?'. If 'No', it proceeds to a 'Pass' terminal. If 'Yes', it proceeds to a decision diamond 'Outgoing Access present?'. If 'Yes', it proceeds to a 'Pass' terminal. If 'No', it proceeds to a 'Fail' terminal. + +Flowchart for Macro CUG\_Support\_Check\_GMSC + +**Figure 43bis: Macro CUG\_Support\_Check\_GMSC** + +## 7.2.2 Functional requirements of HLR + +### 7.2.2.1 Process SRI\_HLR + +Sheet 1: the procedures Check\_Parameters, Subscription\_Check\_HLR, SCUDIF\_Subscription\_Check\_HLR, Handle\_OR\_HLR\_CF and CAMEL\_HLR\_INIT can set the negative response parameter which is used by the process SRI\_HLR to construct the Send Routeing Info negative response message. This negative response parameter is global data, accessible by the process SRI\_HLR. + +Sheet 1: the procedure Handle\_OR\_HLR\_CF is specific to Support of Optimal Routeing; it is specified in 3GPP TS 23.079 [13]. If the HLR does not support Optimal Routeing, processing continues from the "No" exit of the test "Result=Forward?". + +Sheet 1: the procedure SCUDIF\_Subscription\_Check\_HLR is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. This procedure gets the result from the Subscription\_Check\_HLR procedure, and modifies it if needed. If the HLR does not support SCUDIF, the test "Result = Fail ?" applies to the result of the Subscription\_Check\_HLR procedure. + +Sheet 1: the procedure CAMEL\_HLR\_INIT is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the HLR does not support CAMEL, processing continues from the "No" exit of the test "Result=Fail?". + +Sheet 2: the procedure First\_Forwarding\_HLR can set the negative response parameter which is used by the process SRI\_HLR to construct the Send Routeing Info negative response message. This negative response parameter is global data, accessible by the process SRI\_HLR. + +Sheet 2: the procedure Domain\_Selection\_HLR is specific to domain selection for a subscriber who has subscriptions in both the CS and the IMS domain. + +NOTE: The domain selection function mentioned in this procedure is service domain selection specified in 3GPP TS 23.221 [40]. + +Sheet 2: the procedure CAMEL\_CSI\_Check\_HLR is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the HLR does not support CAMEL, processing continues from the "No" exit of the test "Result=CSI active?". + +Sheet 2: the procedure SCUDIF\_CAMEL\_CSI\_Check\_HLR is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. This procedure gets the result from the CAMEL\_CSI\_Check\_HLR procedure, and modifies it if needed. If the HLR does not support SCUDIF, the test "Result = CSI Active ?" applies to the result of the CAMEL\_CSI\_Check\_HLR procedure. If the HLR does not support CAMEL, processing continues from the "No" exit of the test "Result=CSI active?". + +Sheet 2: the test "gsmSCF Initiated Call?" is specific to CAMEL phase 4 or later. If the HLR does not support CAMEL phase 4 or later, processing continues from the "No" exit. + +Sheet 2: the test "Suppress CCBS Handling?" is specific to CAMEL phase 4 or later. If the HLR does not support CAMEL phase 4 or later, processing continues from the "No" exit. + +Sheet 2: the procedure CCBS\_Handling\_HLR is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. If the HLR does not support CCBS, processing continues from the "Yes" exit of the test "Result = OK?". + +Sheet 3: the procedure OR\_HLR\_Interrogate\_VLR is specific to Optimal Routeing. It is specified in 3GPP TS 23.079 [13]. If the HLR does not support Optimal Routeing, processing continues from the "No" exit of the test "Result=Forward". + +Sheet 3: the procedure SCUDIF\_Set\_Correct\_PLMN\_BC is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the HLR does not support SCUDIF, processing continues from the "Set\_PLMN\_BC" exit of the test "Result ?". + +Sheet 3: if the HLR does not support Network Indication of Alerting, the test "Alerting pattern required" and the task "Set Alerting Pattern" are omitted. + +Sheet 3: the procedure CLI\_HLR\_Set\_CLI is specific to Enhanced CLI Handling. It is specified in 3GPP TS 23.081 [14]. + +Sheet 5: the procedure SCUDIF\_Check\_Second\_Service\_after\_PRN is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the HLR does not support SCUDIF, processing continues from the "yes" exit of the test "Result = Continue ?". + +Sheet 5: the procedure PRN\_Error\_HLR can set the negative response parameter which is used by the process SRI\_HLR to construct the Send Routeing Info negative response message. This negative response parameter is global data, accessible by the process SRI\_HLR. + +Sheet 5: the procedure Forward\_CUG\_Check is specific to CUG. If the HLR does not support CUG, processing continues from the "Yes" exit of the test "Result=Call allowed?". + +Sheet 6: the test "Forwarding enquiry" is specific to Support of Optimal Routeing. If the HLR does not support Optimal Routeing, processing continues from the "No" exit of the test. + +Sheet 6: the procedure CAMEL\_CSI\_Check\_HLR is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the HLR does not support CAMEL, processing continues from the "No" exit of the test "Result=CSI active?". + +Sheet 6: the procedure SCUDIF\_CAMEL\_CSI\_Check\_HLR is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. This procedure gets the result from the CAMEL\_CSI\_Check\_HLR procedure, and modifies it if needed. If the HLR does not support SCUDIF, the test "Result = CSI Active ?" applies to the result of the CAMEL\_CSI\_Check\_HLR procedure. If the HLR does not support CAMEL, processing continues from the "No" exit of the test "Result=CSI active?". + +Sheet 6: the procedure SCUDIF\_Check\_Second\_Service\_before\_Negative\_Response can set the negative response parameter which is used by the process SRI\_HLR to construct the Send Routeing Info negative response message. This negative response parameter is global data, accessible by the process SRI\_HLR. + +Sheet 6: the procedure SCUDIF\_Check\_Second\_Service\_before\_Negative\_Response is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the HLR does not support SCUDIF, processing continues from the "Fail" exit of the test "Result ?". + +Sheet 7: the procedures CAMEL\_T\_CSI\_CHECK\_HLR and CAMEL\_O\_CSI\_CHECK\_HLR are specific to CAMEL; they are specified in 3GPP TS 23.078 [12]. + +Sheet 7: the procedure CAMEL\_D\_CSI\_CHECK\_HLR is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 7: the procedure SCUDIF\_Set\_Second\_Service\_when\_Forwarded is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the HLR does not support SCUDIF, processing continues from the "Yes" exit of the test "Result = Continue ?". + +Sheet 7: the procedure SCUDIF\_Check\_Second\_Service\_when\_Forwarded is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the HLR does not support SCUDIF, processing continues from the "Yes" exit of the test "Result = Continue ?". + +Sheet 7: A HLR implementing the Mobile Terminating Roaming Retry feature (see sub-clause 5.2.1) shall delay the sending of the PRN message till completion of any on-going Location Update procedure. + +### 7.2.2.2 Procedure Check\_Parameters + +If any parameters required by the rules in clause 8 are missing from the message, the procedure sets the negative response to "Data missing". If any parameter has a value which is not in the set of values expected for the parameter, the procedure sets the negative response to "Unexpected data value". + +### 7.2.2.3 Procedure Subscription\_Check\_HLR + +The HLR derives the possible PLMN bearer capability to populate the parameter in the Provide Roaming Number request according to the rules defined in 3GPP TS 29.007 [30]. + +If the HLR is able to determine the PLMN bearer capability or equivalent ISDN compatibility information to be sent to the VLR in the Provide Roaming Number request, it applies the corresponding PLMN bearer service or teleservice for handling the call. If the HLR is not able to determine any compatibility information to be sent to the VLR in the Provide Roaming Number request, it applies a default basic service according to the requirements of the operator. + +If the HLR receives Send Routeing Information from the gsmSCF and the HLR is not able to determine any compatibility information to be sent to the VLR in the Provide Roaming Number request, then the HLR shall apply basic service TS11. + +**NOTE** The information element "gsmSCF Initiated Call" in Send Routeing Information serves as an indication to the HLR that this Send Routeing Information is sent by the gsmSCF. Refer to 3GPP TS 23.078 [12]. + +It is an implementation option to carry out the check for operator determined barring of incoming calls before the check on provisioning of the requested basic service. + +The test "gsmSCF Initiated Call?" is specific to CAMEL phase 4 or later. If the HLR does not support CAMEL phase 4 or later, processing continues from the "No" exit. + +The test "Suppress CUG Handling?" is specific to CAMEL phase 4 or later. If the HLR does not support CAMEL phase 4 or later, processing continues from the "No" exit. + +The negative response "Call barred" indicates whether the reason is operator determined barring or supplementary service barring, according to the result returned by the procedure Check\_IC\_Barring. + +The negative response "CUG reject" indicates whether the reason is: + +- Incoming calls barred within CUG; +- Requested basic service violates CUG constraints; +- Subscriber not member of CUG; + +according to the cause returned by the procedure IC\_CUG\_Check. + +#### 7.2.2.4 Procedure First\_Forwarding\_HLR + +The MS is not reachable if any of the following conditions is satisfied: + +- The HLR has no location information for the subscriber. +- The subscriber record is marked as MS purged. +- The subscriber record is marked as MSC area restricted. +- The subscriber record is marked as Roaming Restricted due to Unsupported Feature. +- The subscriber is marked as deregistered because of subscription restrictions on roaming. + +#### 7.2.2.5 Procedure PRN\_Error\_HLR + +The procedure CCBS\_Report\_PRN\_Failure is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. The procedure does not return a value; the following tests are on the value of the Provide Roaming Number negative response. + +The procedure Super\_Charged\_SRI\_Error\_HLR is specific to Super-Charger; it is specified in 3GPP TS 23.116 [24]. If the HLR does not support Super-Charger, processing continues from the "No" exit of the test "Result=Purged?". + +If the HLR does not support Optimal Routeing, processing starts with the test "Negative response=Facility not supported?". + +#### 7.2.2.6 Procedure Forward\_CUG\_Check + +#### 7.2.2.7 Void + +#### 7.2.2.8 Procedure Check\_IC\_Barring + +#### 7.2.2.9 Procedure IC\_CUG\_Check + +#### 7.2.2.10 Procedure Handle\_CFU + +The test "Normal call" refers to the value of the indicator returned by the process MAF007. + +The procedure CAMEL\_CHECK\_SII2\_CDTI is specific to CAMEL Phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL Phase 3 or later, processing continues from the "Yes" exit of the test "Result = Pass?". + +#### 7.2.2.11 Procedure Handle\_CFNRc + +The test "Mobile subscriber not reachable" refers to the value of the indicator returned by the process MAF010. + +The procedure CAMEL\_CHECK\_SII2\_CDTI is specific to CAMEL Phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL Phase 3 or later, processing continues from the "Yes" exit of the test "Result = Pass?". + +#### 7.2.2.12 Procedure Domain\_Selection\_HLR + +The procedure Domain\_Selection\_HLR is specific to Domain Selection specified in 3GPP TS 23.221 [40]. + +![Flowchart for Process SRI_HLR. The process starts with an oval connector, followed by 'Idle' (oval), 'Send Routeing Info' (input/output), 'Check Parameters' (process), 'Result= Pass?' (decision), 'Subscription Check_HLR' (process), 'SCUDIF_Subscription Check_HLR' (process) with a note 'See TS 23.172', 'Result= Fail?' (decision), 'OR_HLR_CF' (process) with a note 'See TS 23.079', 'Result= Fail?' (decision), 'Result= Forward?' (decision), 'CAMEL_HLR_INIT' (process) with a note 'See TS 23.078', and 'Result= Fail?' (decision). The final decisions lead to connectors 3, 1, 2, and 1. Other connectors include 7, 6, and 1.](536768a30136cd5c2d57f46c25d1d804_img.jpg) + +**Process SRI\_HLR** + +*Process in the HLR to handle a request for routing information* + +**SRI\_HLR1(7)** + +*Signals to/from the left are to/from the GMSC or the gsmSCF; signals to/from the right are to/from the VLR* + +``` +graph TD; Start([ ]) --> Idle([Idle]); Idle --> Send[Send Routeing Info]; Send --> Check[Check Parameters]; Check --> Pass{Result= Pass?}; Pass -- Yes --> Sub[Subscription Check_HLR]; Sub --> SCUDIF[SCUDIF_Subscription Check_HLR]; SCUDIF -.-> Note1[See TS 23.172]; SCUDIF --> Fail1{Result= Fail?}; Fail1 -- Yes --> Conn6((6)); Fail1 -- No --> OR[OR_HLR_CF]; OR -.-> Note2[See TS 23.079]; OR --> Fail2{Result= Fail?}; Fail2 -- Yes --> Conn1_4((1)); Fail2 -- No --> Forward{Result= Forward?}; Forward -- Yes --> Conn2((2)); Forward -- No --> CAMEL[CAMEL_HLR_INIT]; CAMEL -.-> Note3[See TS 23.078]; CAMEL --> Fail3{Result= Fail?}; Fail3 -- Yes --> Conn1_3((1)); Fail3 -- No --> Conn3((3)); Conn7((7)) -.-> OR; Conn6 -.-> Fail1; +``` + +Flowchart for Process SRI\_HLR. The process starts with an oval connector, followed by 'Idle' (oval), 'Send Routeing Info' (input/output), 'Check Parameters' (process), 'Result= Pass?' (decision), 'Subscription Check\_HLR' (process), 'SCUDIF\_Subscription Check\_HLR' (process) with a note 'See TS 23.172', 'Result= Fail?' (decision), 'OR\_HLR\_CF' (process) with a note 'See TS 23.079', 'Result= Fail?' (decision), 'Result= Forward?' (decision), 'CAMEL\_HLR\_INIT' (process) with a note 'See TS 23.078', and 'Result= Fail?' (decision). The final decisions lead to connectors 3, 1, 2, and 1. Other connectors include 7, 6, and 1. + +Figure 44a: Process SRI\_HLR (sheet 1) + +![Flowchart for Process SRI_HLR. It starts at node 3, goes to First_Forwarding_HLR, then checks Result=Fail? and Result=Forward?. It branches based on HLR support for Domain Selection, CAMEL/SCUDIF CSI checks, gsmSCF initiated call status, and CCBS handling. It ends at nodes 1, 2, 4, 5, or 12.](245166735676c675f98f535bc4c6f0a1_img.jpg) + +### Process SRI\_HLR + +Process in the HLR to handle a request for routing information + +### SRI\_HLR2(7) + +Signals to/from the left are to/from the GMSC or the gsmSCF; signals to/from the right are to/from the VLR + +``` +graph TD; 3((3)) --> F[First_Forwarding_HLR]; F --> RF{Result=Fail?}; RF -- Yes --> HDS{HLR support Domain Selection?}; RF -- No --> RFor{Result=Forward?}; RFor -- Yes --> 2((2)); RFor -- No --> HDS_L{HLR support Domain Selection?}; HDS_L -- Yes --> DS[Domain_Selection_HLR]; DS --> RCI{Result=CS or IMS?}; RCI -- IMS --> 12((12)); RCI -- CS --> CCHL[CAMEL_CSI_Check_HLR]; CCHL --> ST23078[See TS 23.078]; CCHL --> SCCHL[SCUDIF_CAMEL_CSI_Check_HLR]; SCCHL --> ST23172[See TS 23.172]; SCCHL --> RCA{Result=CSI active?}; RCA -- Yes --> 4((4)); RCA -- No --> GIC{gsmSCF Initiated Call?}; GIC -- Yes --> SCH{Suppress CCBS Handling?}; GIC -- No --> SCH; SCH -- Yes --> 5((5)); SCH -- No --> OCHL[OCBS_Handling_HLR]; OCHL --> ST23093[See TS 23.093]; OCHL --> RFwd{Result = Forward?}; RFwd -- Yes --> 2((2)); RFwd -- No --> RO{Result = OK?}; RO -- Yes --> 5((5)); RO -- No --> 1((1)); HDS -- Yes --> DS_R[Domain_Selection_HLR]; HDS -- No --> RCI_R{Result=CS or IMS?}; RCI_R -- IMS --> 12((12)); RCI_R -- CS --> CCHL_R[CAMEL_CSI_Check_HLR]; CCHL_R --> ST23078_R[See TS 23.078]; CCHL_R --> SCCHL_R[SCUDIF_CAMEL_CSI_Check_HLR]; SCCHL_R --> ST23172_R[See TS 23.172]; SCCHL_R --> RCA_R{Result=CSI active?}; RCA_R -- Yes --> 4((4)); RCA_R -- No --> 1((1)); +``` + +Flowchart for Process SRI\_HLR. It starts at node 3, goes to First\_Forwarding\_HLR, then checks Result=Fail? and Result=Forward?. It branches based on HLR support for Domain Selection, CAMEL/SCUDIF CSI checks, gsmSCF initiated call status, and CCBS handling. It ends at nodes 1, 2, 4, 5, or 12. + +Figure 44b: Process SRI\_HLR (sheet 2) + +![Flowchart for Process SRI_HLR. It starts at connector 5, goes to OR_HLR_Interrogate_VLR (referencing TS 23.079). A decision 'Result=Fail?' follows. If Yes, it goes to connector 1. If No, it goes to 'Result=Forward?'. If Yes, it goes to connector 2. If No, it goes to SCUDIF_Set_Correct_PLMN_BC. A 'Result' triangle follows. From 'Result', 'SRI_Ack' goes to connector 4, 'Set_PLMN_BC' goes to a 'PLMN BC=NULL?' decision, and 'Continue' goes to connector 8. If 'PLMN BC=NULL?' is Yes, it goes to connector 8. If No, it goes to 'Set PLMN BC parameter', then to 'Alerting Pattern required?'. If 'Alerting Pattern required?' is Yes, it goes to 'Set Alerting Pattern', then to 'CLI_HLR_Set_CLI' (referencing TS 23.081), then to connector 8. If 'Alerting Pattern required?' is No, it goes to connector 8.](92724c769da9d46b730fde1a6dccb023_img.jpg) + +### Process SRI\_HLR + +**SRI\_HLR3(7)** + +Process in the HLR to handle a request for routing information: + +Signals to/from the left are to/from the GMSC or the gsmSCF; signals to/from the right are to/from the VLR + +``` +graph TD; 5((5)) --> OR_HLR_Interrogate_VLR[OR_HLR_Interrogate_VLR]; OR_HLR_Interrogate_VLR -.-> TS23079[See TS 23.079]; OR_HLR_Interrogate_VLR --> ResultFail{Result=Fail?}; ResultFail -- Yes --> 1((1)); ResultFail -- No --> ResultForward{Result=Forward?}; ResultForward -- Yes --> 2((2)); ResultForward -- No --> SCUDIF_Set_Correct_PLMN_BC[SCUDIF_Set_Correct_PLMN_BC]; SCUDIF_Set_Correct_PLMN_BC --> Result{Result}; Result -- SRI_Ack --> 4((4)); Result -- Set_PLMN_BC --> PLMNBCNULL{PLMN BC=NULL?}; Result -- Continue --> 8((8)); PLMNBCNULL -- Yes --> 8; PLMNBCNULL -- No --> SetPLMNBC[Set PLMN BC parameter]; SetPLMNBC --> AlertingRequired{Alerting Pattern required?}; AlertingRequired -- Yes --> SetAlerting[Set Alerting Pattern]; AlertingRequired -- No --> 8; SetAlerting --> CLI_HLR_Set_CLI[CLI_HLR_Set_CLI]; CLI_HLR_Set_CLI -.-> TS23081[See TS 23.081]; CLI_HLR_Set_CLI --> 8 +``` + +Flowchart for Process SRI\_HLR. It starts at connector 5, goes to OR\_HLR\_Interrogate\_VLR (referencing TS 23.079). A decision 'Result=Fail?' follows. If Yes, it goes to connector 1. If No, it goes to 'Result=Forward?'. If Yes, it goes to connector 2. If No, it goes to SCUDIF\_Set\_Correct\_PLMN\_BC. A 'Result' triangle follows. From 'Result', 'SRI\_Ack' goes to connector 4, 'Set\_PLMN\_BC' goes to a 'PLMN BC=NULL?' decision, and 'Continue' goes to connector 8. If 'PLMN BC=NULL?' is Yes, it goes to connector 8. If No, it goes to 'Set PLMN BC parameter', then to 'Alerting Pattern required?'. If 'Alerting Pattern required?' is Yes, it goes to 'Set Alerting Pattern', then to 'CLI\_HLR\_Set\_CLI' (referencing TS 23.081), then to connector 8. If 'Alerting Pattern required?' is No, it goes to connector 8. + +Figure 44c: Process SRI\_HLR (sheet 3) + +![Flowchart for Process SRI_HLR. It starts at connector 8, checks if pre-paging is supported in the HLR, then if it's supported in the GMSC. If not supported in the GMSC, it skips to 'Provide Roaming Number'. If supported in the GMSC, it sets pre-paging supported, then provides the roaming number, and waits for MSRN.](db7a693cf26f527ac6c0d4d41da20858_img.jpg) + +**Process SRI\_HLR** **SRI\_HLR4(7)** + +Process in the HLR to handle a request for routing information + +``` +graph TD; 8((8)) --> HLR{Pre-paging supported in HLR?}; HLR -- Yes --> GMSC{Pre-paging supported in GMSC?}; HLR -- No --> PRN{{Provide Roaming Number}}; GMSC -- Yes --> Set[Set Pre-paging supported]; GMSC -- No --> PRN; Set --> PRN; PRN --> Wait[Wait_For_MS RN]; +``` + +Flowchart for Process SRI\_HLR. It starts at connector 8, checks if pre-paging is supported in the HLR, then if it's supported in the GMSC. If not supported in the GMSC, it skips to 'Provide Roaming Number'. If supported in the GMSC, it sets pre-paging supported, then provides the roaming number, and waits for MSRN. + +Figure 44d: Process SRI\_HLR (sheet 4) + +![Flowchart for Process SRI_HLR. It starts with 'Wait_For_MSRN' leading to a decision 'Provide Roaming Number negative response'. If 'No', it goes to 'MT Roaming Retry supported and received Update Location Request?'. If 'Yes', it goes to 'Set Error=Absent Subscriber with reason mtRoamingRetry in the SRI response' then 'Send Routeing Info Negative Rsp' to 'Idle'. If 'No', it goes to 'Result=Fail?'. If 'Yes', it goes to connector '1'. If 'No', it goes to 'Forward_CUG_Check' then 'Result=Call allowed?'. If 'Yes', it goes to connector '9'. If 'No', it goes to connector '11'. From 'Result=Fail?', connector '2' leads to 'SCUDIF_Check Second_Service after_PRN'. From 'Result=Call allowed?', connector '12' leads to 'Set Routeing address' (see TS 23.292). Both 'SCUDIF_Check' and 'Set Routeing address' lead to a merge point. From the merge point, connector '4' leads to 'Send Routeing Info ack' to 'Idle', and connector '10' leads to 'MT Roaming Retry supported and received Update Location Request?'. 'SCUDIF_Check' also leads to 'Routeing address:= MSRN' then 'Provide Roaming Number ack'.](8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg) + +### Process SRI\_HLR + +SRI\_HLR5(7) + +Process in the HLR to handle a request for routeing information + +Signals to/from the left are to/from the GMSC or the gsmSCF; signals to/from the right are to/from the VLR + +``` +graph TD; Start([Wait_For_MSRN]) --> Decision1{Provide Roaming Number negative response}; Decision1 -- No --> Decision2{MT Roaming Retry supported and received Update Location Request?}; Decision1 -- Yes --> Error[Set Error=Absent Subscriber with reason mtRoamingRetry in the SRI response]; Error --> NegativeRsp{{Send Routeing Info Negative Rsp}}; NegativeRsp --> Idle1([Idle]); Decision2 -- No --> Decision3{Result=Fail?}; Decision2 -- Yes --> Error; Decision3 -- Yes --> Connector1((1)); Decision3 -- No --> ForwardCUG[Forward_CUG_Check]; ForwardCUG --> Decision4{Result=Call allowed?}; Decision4 -- Yes --> Connector9((9)); Decision4 -- No --> Connector11((11)); Decision3 -- No --> Connector2((2)); Connector2 --> SCUDIF[SCUDIF_Check Second_Service after_PRN]; SCUDIF --> Note1[See TS 23.172]; SCUDIF --> Address1[Routeing address:= MSRN]; Address1 --> Ack[Provide Roaming Number ack]; Decision4 -- No --> Connector12((12)); Connector12 --> Address2[Set Routeing address]; Address2 --> Note2[see TS 23.292]; Address2 --> Merge(( )); Address1 --> Merge; Merge --> Connector4((4)); Merge --> Connector10((10)); Connector4 --> AckRsp{{Send Routeing Info ack}}; AckRsp --> Idle2([Idle]); Connector10 --> Decision2; +``` + +Flowchart for Process SRI\_HLR. It starts with 'Wait\_For\_MSRN' leading to a decision 'Provide Roaming Number negative response'. If 'No', it goes to 'MT Roaming Retry supported and received Update Location Request?'. If 'Yes', it goes to 'Set Error=Absent Subscriber with reason mtRoamingRetry in the SRI response' then 'Send Routeing Info Negative Rsp' to 'Idle'. If 'No', it goes to 'Result=Fail?'. If 'Yes', it goes to connector '1'. If 'No', it goes to 'Forward\_CUG\_Check' then 'Result=Call allowed?'. If 'Yes', it goes to connector '9'. If 'No', it goes to connector '11'. From 'Result=Fail?', connector '2' leads to 'SCUDIF\_Check Second\_Service after\_PRN'. From 'Result=Call allowed?', connector '12' leads to 'Set Routeing address' (see TS 23.292). Both 'SCUDIF\_Check' and 'Set Routeing address' lead to a merge point. From the merge point, connector '4' leads to 'Send Routeing Info ack' to 'Idle', and connector '10' leads to 'MT Roaming Retry supported and received Update Location Request?'. 'SCUDIF\_Check' also leads to 'Routeing address:= MSRN' then 'Provide Roaming Number ack'. + +Figure 44e: Process SRI\_HLR (sheet 5) + +![Flowchart for Process SRI_HLR. It starts at connector 11, checks if forwarding is enabled. If no, it performs CAMEL and SCUDIF CSI checks. If the result is not active, it goes to connector 1. If active, it checks for service interaction violations. If a violation occurs, it sets a negative response (CUG reject) and goes to connector 1. If no violation, it performs a second service check. The final result leads to either a successful 'Send Routeing Info ack' (ending at Idle), a 'fail' state (leading to connector 6 and then 'Send Routeing Info negative response' ending at Idle), or a 'Second_Interrogation' (leading to connector 7).](9958beca8f65818eb0ff893647af94de_img.jpg) + +**Process SRI\_HLR** **SRI\_HLR6(7)** + +Process in the HLR to handle a request for routing information + +``` +graph TD; 11((11)) --> F{Forwarding enquiry?}; F -- Yes --> J1((1)); F -- No --> C1[CAMEL_CSI_Check_HLR]; C1 -.-> TS1[See TS 23.078]; C1 --> C2[SCUDIF_CAMEL_CSI_Check_HLR]; C2 -.-> TS2[See TS 23.172]; C2 --> R1{Result=CSI active?}; R1 -- No --> J1; R1 -- Yes --> SI[Called party SS interaction violation]; SI --> NR[Set negative response: CUG reject]; NR --> J1; J1 --> C3[SCUDIF_Check_Second_Service_before_negative_response]; C3 -.-> TS3[See TS 23.172]; C3 --> R2{Result?}; R2 -- Pass --> S1{Send Routeing Info ack}; S1 --> Idle1([Idle]); R2 -- fail --> J6((6)); J6 --> S2{Send Routeing Info negative response}; S2 --> Idle2([Idle]); R2 -- Second_Interrogation --> J7((7)); +``` + +Flowchart for Process SRI\_HLR. It starts at connector 11, checks if forwarding is enabled. If no, it performs CAMEL and SCUDIF CSI checks. If the result is not active, it goes to connector 1. If active, it checks for service interaction violations. If a violation occurs, it sets a negative response (CUG reject) and goes to connector 1. If no violation, it performs a second service check. The final result leads to either a successful 'Send Routeing Info ack' (ending at Idle), a 'fail' state (leading to connector 6 and then 'Send Routeing Info negative response' ending at Idle), or a 'Second\_Interrogation' (leading to connector 7). + +Figure 44f: Process SRI\_HLR (sheet 6) + +![Flowchart for Process SRI_HLR. It starts at connector 9, sets routing address to FTN, checks SCUDIF_Set_Second_Service_when_Forwarded (referencing TS 23.172), then checks 'Result=Continue?'. If No, it goes to connector 10. If Yes, it checks 'Forwarding enquiry?'. If No, it calls CAMEL_T_CSI_CHECK_HLR (referencing TS 23.078). If Yes, it calls CAMEL_O_CSI_CHECK_HLR (referencing TS 23.078). Both CAMEL calls lead to CAMEL_D_CSI_CHECK_HLR (referencing TS 23.078). After CAMEL_D, it checks SCUDIF_Check_Second_Service_when_Forwarded (referencing TS 23.172), then checks 'Result=Continue?' again. If No, it goes to connector 7. If Yes, it sends a routing info ack and goes to Idle state.](fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg) + +**Process SRI\_HLR** **SRI\_HLR7(7)** + +Process in the HLR to handle a request for routing information: + +``` +graph TD; 9((9)) --> RA["Routing address:= FTN"]; RA --> SC1["SCUDIF_Set_Second_Service_when_Forwarded"]; SC1 -.-> TS1["See TS 23.172"]; SC1 --> RC1{Result=Continue?}; RC1 -- No --> 10((10)); RC1 -- Yes --> FE{Forwarding enquiry?}; FE -- No --> CT["CAMEL_T_CSI_CHECK_HLR"]; FE -- Yes --> CO["CAMEL_O_CSI_CHECK_HLR"]; CT -.-> TS2["See TS 23.078"]; CO -.-> TS3["See TS 23.078"]; CT --> CD["CAMEL_D_CSI_CHECK_HLR"]; CO --> CD; CD -.-> TS4["See TS 23.078"]; CD --> SC2["SCUDIF_Check_Second_Service_when_Forwarded"]; SC2 -.-> TS5["See TS 23.172"]; SC2 --> RC2{Result=Continue?}; RC2 -- No --> 7((7)); RC2 -- Yes --> SRI["Send Routing Info ack"]; SRI --> Idle([Idle]); +``` + +Flowchart for Process SRI\_HLR. It starts at connector 9, sets routing address to FTN, checks SCUDIF\_Set\_Second\_Service\_when\_Forwarded (referencing TS 23.172), then checks 'Result=Continue?'. If No, it goes to connector 10. If Yes, it checks 'Forwarding enquiry?'. If No, it calls CAMEL\_T\_CSI\_CHECK\_HLR (referencing TS 23.078). If Yes, it calls CAMEL\_O\_CSI\_CHECK\_HLR (referencing TS 23.078). Both CAMEL calls lead to CAMEL\_D\_CSI\_CHECK\_HLR (referencing TS 23.078). After CAMEL\_D, it checks SCUDIF\_Check\_Second\_Service\_when\_Forwarded (referencing TS 23.172), then checks 'Result=Continue?' again. If No, it goes to connector 7. If Yes, it sends a routing info ack and goes to Idle state. + +Figure 44g: Process SRI\_HLR (sheet 7) + +![Flowchart for Procedure Check_Parameters. It starts with a connector, then checks if all required parameters are present. If No, it sets a negative response 'Data missing' and results in 'Fail'. If Yes, it checks if all parameter values are acceptable. If No, it sets a negative response 'Unexpected data value' and results in 'Fail'. If Yes, it results in 'Pass'.](3334fcca5dac808f4fd3840aba35bc2e_img.jpg) + +### Procedure Check\_Parameters + +Chk\_Par1(1) + +Procedure to check the parameters of a received message + +``` +graph TD; Start([ ]) --> D1{All required parameters present?}; D1 -- No --> N1[Set negative response: Data missing]; D1 -- Yes --> D2{All parameter values acceptable?}; D2 -- No --> N2[Set negative response: Unexpected data value]; N1 --> R1[Result:= Fail]; N2 --> R1; D2 -- Yes --> R2[Result:= Pass]; R1 --> End1(( )); R2 --> End2(( )); +``` + +Flowchart for Procedure Check\_Parameters. It starts with a connector, then checks if all required parameters are present. If No, it sets a negative response 'Data missing' and results in 'Fail'. If Yes, it checks if all parameter values are acceptable. If No, it sets a negative response 'Unexpected data value' and results in 'Fail'. If Yes, it results in 'Pass'. + +Figure 45: Procedure Check\_Parameters + +![Flowchart for Subscription_Check_HLR procedure](1bc1746388cb64bf23b356ce2365dfc2_img.jpg) + +### Procedure Subscription\_Check\_HLR + +SC\_HLR1(1) + +Procedure in the HLR to make subscription checks for a mobile-terminated call + +``` +graph TD; Start([Start]) --> MS_Known{MS known?}; MS_Known -- No --> Negative1[Set negative response: Unknown subscriber]; MS_Known -- Yes --> Number_Changed{Number changed?}; Number_Changed -- Yes --> Negative2[Set negative response: Number changed]; Number_Changed -- No --> Derive[Derive requested basic service]; Derive --> TS[See TS 29.007]; Derive --> Service_Provisioned{Requested service provisioned?}; Service_Provisioned -- No --> Negative3[Set negative response: service not provisioned]; Service_Provisioned -- Yes --> GSMSCF_1{gsmSCF Initiated Call?}; GSMSCF_1 -- No --> Negative3; GSMSCF_1 -- Yes --> Suppress_ICB{Suppress ICB?}; Suppress_ICB -- Yes --> Junction1(( )); Suppress_ICB -- No --> Check_ICB[Check_ICB_Barring]; Check_ICB --> Call_Barred{Result= Call barred?}; Call_Barred -- Yes --> Negative4[Set negative response: Call barred]; Call_Barred -- No --> GSMSCF_2{gsmSCF Initiated Call?}; GSMSCF_2 -- No --> Negative4; GSMSCF_2 -- Yes --> Suppress_CUG{Suppress CUG?}; Suppress_CUG -- Yes --> Junction1; Suppress_CUG -- No --> Check_CUG[IC_CUG_Check]; Check_CUG --> Call_Allowed{Result= Call allowed?}; Call_Allowed -- No --> Negative5[Set negative response: CUG reject]; Call_Allowed -- Yes --> Junction1; Negative1 --> Fail[Result:= Fail]; Negative2 --> Fail; Negative3 --> Fail; Negative4 --> Fail; Negative5 --> Fail; Junction1 --> Pass[Result:= Pass]; Pass --> EndPass(( )); Fail --> EndFail(( )); +``` + +The flowchart details the subscription check process in the HLR. It begins with a decision 'MS known?'. If 'No', a negative response 'Unknown subscriber' is set, leading to a 'Fail' result. If 'Yes', it checks 'Number changed?'. If 'Yes', a negative response 'Number changed' is set, leading to 'Fail'. If 'No', it proceeds to 'Derive requested basic service' (referencing TS 29.007). Next, it checks 'Requested service provisioned?'. If 'No', a negative response 'service not provisioned' is set, leading to 'Fail'. If 'Yes', it checks if 'gsmSCF Initiated Call?'. If 'No', the same negative response is set. If 'Yes', it checks 'Suppress ICB?'. If 'Yes', it proceeds to a junction. If 'No', it performs 'Check\_ICB\_Barring'. If the result is 'Call barred?', a negative response 'Call barred' is set, leading to 'Fail'. If 'No', it checks 'gsmSCF Initiated Call?' again. If 'No', the 'Call barred' negative response is set. If 'Yes', it checks 'Suppress CUG?'. If 'Yes', it proceeds to the junction. If 'No', it performs 'IC\_CUG\_Check'. If the result is 'Call allowed?', it proceeds to the junction. If 'No', a negative response 'CUG reject' is set, leading to 'Fail'. All negative responses lead to a 'Result:= Fail' state. The junction leads to a 'Result:= Pass' state. + +Flowchart for Subscription\_Check\_HLR procedure + +Figure 46: Procedure Subscription\_Check\_HLR + +![Flowchart for Procedure First_Forwarding_HLR. It starts with a connector, followed by 'Handle_CFU'. A decision 'Result= Fail?' follows. If 'Yes', it goes to 'Set negative response: Forwarding violation' and then to a 'Result:= Fail' connector. If 'No', it goes to 'Result= Forward?'. If 'Yes', it goes to 'Result:= Forward' connector. If 'No', it goes to 'MS not reachable?'. If 'Yes', it goes to 'Handle_CFNRc'. If 'No', it goes to 'Result:= Continue' connector. From 'Handle_CFNRc', a decision 'Result= Fail?' follows. If 'Yes', it goes to 'Set negative response: Forwarding violation' and then to a 'Result:= Fail' connector. If 'No', it goes to 'Result= Forward?'. If 'Yes', it goes to 'Result:= Forward' connector. If 'No', it goes to 'Set negative response: Absent subscriber' and then to a 'Result:= Fail' connector.](93bd00a00fa28558486f0664550699b1_img.jpg) + +### Procedure First\_Forwarding\_HLR + +FF\_HLR1(1) + +Procedure in the HLR +to handle call forwarding +before interrogation of the VLR + +``` +graph TD; Start([ ]) --> Handle_CFU[Handle_CFU]; Handle_CFU --> Result_Fail_1{Result= Fail?}; Result_Fail_1 -- Yes --> Set_Neg_1[Set negative response: Forwarding violation]; Set_Neg_1 --> Result_Fail_1_end([ ]); Result_Fail_1 -- No --> Result_Forward_1{Result= Forward?}; Result_Forward_1 -- Yes --> Result_Forward_1_end([ ]); Result_Forward_1 -- No --> MS_Not_Reachable{MS not reachable?}; MS_Not_Reachable -- Yes --> Handle_CFNRc[Handle_CFNRc]; MS_Not_Reachable -- No --> Result_Continue[Result:= Continue]; Handle_CFNRc --> Result_Fail_2{Result= Fail?}; Result_Fail_2 -- Yes --> Set_Neg_2[Set negative response: Forwarding violation]; Set_Neg_2 --> Result_Fail_2_end([ ]); Result_Fail_2 -- No --> Result_Forward_2{Result= Forward?}; Result_Forward_2 -- Yes --> Result_Forward_2_end([ ]); Result_Forward_2 -- No --> Set_Neg_3[Set negative response: Absent subscriber]; Set_Neg_3 --> Result_Fail_2_end; +``` + +Flowchart for Procedure First\_Forwarding\_HLR. It starts with a connector, followed by 'Handle\_CFU'. A decision 'Result= Fail?' follows. If 'Yes', it goes to 'Set negative response: Forwarding violation' and then to a 'Result:= Fail' connector. If 'No', it goes to 'Result= Forward?'. If 'Yes', it goes to 'Result:= Forward' connector. If 'No', it goes to 'MS not reachable?'. If 'Yes', it goes to 'Handle\_CFNRc'. If 'No', it goes to 'Result:= Continue' connector. From 'Handle\_CFNRc', a decision 'Result= Fail?' follows. If 'Yes', it goes to 'Set negative response: Forwarding violation' and then to a 'Result:= Fail' connector. If 'No', it goes to 'Result= Forward?'. If 'Yes', it goes to 'Result:= Forward' connector. If 'No', it goes to 'Set negative response: Absent subscriber' and then to a 'Result:= Fail' connector. + +Figure 47: Procedure First\_Forwarding\_HLR + +![Flowchart for Procedure PRN_Error_HLR. The logic handles various negative response scenarios for roaming number requests in the HLR, leading to either a failure result with specific error codes or a forwarding result.](d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg) + +### Procedure PRN\_Error\_HLR + +PRN\_E\_H1(1) + +Procedure in the HLR + to handle a negative response + for a roaming number request + +``` + +graph TD + Start([ ]) --> CCBS[CCBS_Report_PRN_Failure] + CCBS --- Note1[See TS 23.093] + CCBS --> D1{Negative response=OR not allowed??} + + D1 -- Yes --> SetOR[Set negative response: OR not allowed] + D1 -- No --> D2{Negative response=Facility not supported?} + + D2 -- Yes --> SetFac[Set negative response: Facility not supported] + D2 -- No --> D3{Negative response=Absent subscriber?} + + D3 -- Yes --> SetSysFail1[Set negative response: System failure] + D3 -- No --> D4{Negative response=No roaming number?} + + D4 -- Yes --> H_CFNRc2[Handle_CFNRc] + D4 -- No --> H_CFNRc1[Handle_CFNRc] + + H_CFNRc1 --> Res1{Result?} + Res1 -- Fail --> SetForwViol1[Set negative response: Forwarding violation] + Res1 -- Forward --> ResForw[Result:= Forward] + Res1 -- Not reachable --> SC[Super_Charged_SRI_Error_HLR] + + SC --> ResPurged{Result=Purged?} + ResPurged -- Yes --> SetForwViol1 + ResPurged -- No --> SetAbsSub[Set negative response: Absent subscriber] + + H_CFNRc2 --> Res2{Result?} + Res2 -- Forward --> ResForw + Res2 -- Fail --> SetSysFail2[Set negative response: System failure] + Res2 -- Not reachable --> SetSysFail2 + + SetOR --> ResFail[Result:= Fail] + SetFac --> ResFail + SetSysFail1 --> ResFail + SetForwViol1 --> ResFail + SetAbsSub --> ResFail + SetSysFail2 --> ResFail + + ResFail --> End1(( )) + ResForw --> End2(( )) + +``` + +Flowchart for Procedure PRN\_Error\_HLR. The logic handles various negative response scenarios for roaming number requests in the HLR, leading to either a failure result with specific error codes or a forwarding result. + +**Figure 48: Procedure PRN\_Error\_HLR** + +![Flowchart for Procedure Forward_CUG_Check. It starts with a note 'Procedure to carry out CUG authorisation check for a forwarded call'. The flow begins at a connector, leading to a decision diamond: 'CUG provisioned for forwarding subscriber against requested basic service'. If 'No', it goes to another decision diamond: 'CUG info provided in routing information request'. If 'Yes' to this, it proceeds to 'Result:= Call allowed'. If 'No', it goes to 'Result:= Call barred'. If 'Yes' to the first decision, it goes to 'Perform Forwarding CUG authorisation' (referenced as 'As defined in TS 23.085'). This leads to a decision diamond: 'CUG authorisation result'. If 'Pass', it goes to 'Result:= Call allowed' and then to 'Update CUG info' (referenced as 'As defined in TS 23.085'). If 'Fail', it goes to 'Result:= Call barred'. All three 'Result' boxes lead to a merge point marked with an 'X', which then leads to an end connector.](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) + +### Procedure Forward\_CUG\_Check + +FWD\_CUG1(1) + +``` +graph TD; Start([ ]) --> D1{CUG provisioned for forwarding subscriber against requested basic service}; D1 -- No --> D2{CUG info provided in routing information request}; D1 -- Yes --> P[Perform Forwarding CUG authorisation]; P -- "As defined in TS 23.085" --> P; D2 -- Yes --> R1[Result:= Call allowed]; D2 -- No --> R2[Result:= Call barred]; P --> D3{CUG authorisation result}; D3 -- Pass --> R3[Result:= Call allowed]; D3 -- Fail --> R4[Result:= Call barred]; R3 --> U[Update CUG info]; U -- "As defined in TS 23.085" --> U; R1 --> Merge((X)); R2 --> Merge; R4 --> Merge; Merge --> End((X)); +``` + +Procedure to carry out CUG authorisation check for a forwarded call + +CUG provisioned for forwarding subscriber against requested basic service + +CUG info provided in routing information request + +Perform Forwarding CUG authorisation + +As defined in TS 23.085 + +CUG authorisation result + +Pass + +Fail + +Result:= Call allowed + +Result:= Call barred + +Update CUG info + +As defined in TS 23.085 + +Flowchart for Procedure Forward\_CUG\_Check. It starts with a note 'Procedure to carry out CUG authorisation check for a forwarded call'. The flow begins at a connector, leading to a decision diamond: 'CUG provisioned for forwarding subscriber against requested basic service'. If 'No', it goes to another decision diamond: 'CUG info provided in routing information request'. If 'Yes' to this, it proceeds to 'Result:= Call allowed'. If 'No', it goes to 'Result:= Call barred'. If 'Yes' to the first decision, it goes to 'Perform Forwarding CUG authorisation' (referenced as 'As defined in TS 23.085'). This leads to a decision diamond: 'CUG authorisation result'. If 'Pass', it goes to 'Result:= Call allowed' and then to 'Update CUG info' (referenced as 'As defined in TS 23.085'). If 'Fail', it goes to 'Result:= Call barred'. All three 'Result' boxes lead to a merge point marked with an 'X', which then leads to an end connector. + +Figure 49: Procedure Forward\_CUG\_Check + +Figure 50: Void + +![Flowchart for Procedure Check_IC_Barring (sheet 1)](9ba75f891de20483c291538e38701d96_img.jpg) + +### Procedure Check\_IC\_Barring + +CIB1(2) + +Procedure to check call request against SS barring and ODB categories + +``` + +graph TD + Start([ ]) --> D1{ } + D1 -- Yes --> BAIC{Operator determined +BAIC imposed?} + D1 -- No --> D2{ } + + BAIC -- Yes --> Result[Result:= +Call barred +(ODB)] + BAIC -- No --> BIC_Roam{Operator determined +BIC-Roam imposed?} + + BIC_Roam -- Yes --> HPLMN_C{MS registered +in HPLMN +country?} + BIC_Roam -- No --> BIC_RoamHZ{Operator determined +BIC-RoamHZ +imposed?} + + HPLMN_C -- No --> Result + HPLMN_C -- Yes --> C1_top((1)) + + BIC_RoamHZ -- Yes --> HPLMN_Z{MS registered +in HPLMN +zone?} + BIC_RoamHZ -- No --> C1_bottom((1)) + + HPLMN_Z -- No --> Result + HPLMN_Z -- Yes --> C1_bottom + + Result --> End((X)) + +``` + +The flowchart titled 'Procedure Check\_IC\_Barring' (CIB1(2)) outlines the logic for checking a call request against SS barring and ODB categories. It starts with an entry point leading to a series of decision diamonds. The first branch checks 'Operator determined BAIC imposed?'. If Yes, the call is barred (Result:= Call barred (ODB)). If No, it checks 'Operator determined BIC-Roam imposed?'. If that is Yes, it further checks if the 'MS registered in HPLMN country?'. If the MS is not in the HPLMN country, the call is barred; otherwise, it proceeds to connector 1. If 'Operator determined BIC-Roam imposed?' was No, it checks 'Operator determined BIC-RoamHZ imposed?'. If Yes, it checks if the 'MS registered in HPLMN zone?'. If No, the call is barred; if Yes, it proceeds to connector 1. If 'Operator determined BIC-RoamHZ imposed?' was No, it also proceeds to connector 1. The 'Call barred' result leads to a termination symbol. + +Flowchart for Procedure Check\_IC\_Barring (sheet 1) + +Figure 51a: Procedure Check\_IC\_Barring (sheet 1) + +![Flowchart for procedure Check_IC_Barring. It starts with connector 1, then Initiate handling of BAIC (to process MAF022), Wait_For_BAIC_Response, Continue call handling (from process MAF022). A decision 'Call barred?' follows. If Yes, Result:= Call barred (SS barring) and exit. If No, Initiate handling of BIC-Roam (to process MAF023), Wait_For_BIC-Roam_Response, Continue call handling (from process MAF023). Another decision 'Call barred?' follows. If Yes, Result:= Call barred (SS barring) and exit. If No, Initiate handling of ACR (to process MAF024), Wait_For_ACR_Response, Continue call handling (from process MAF024). A final decision 'Call barred?' follows. If Yes, Result:= Call barred (ACR) and exit. If No, Result:= Call allowed and exit.](61b2e15aedbb8a8dffc5426c0a284eb1_img.jpg) + +procedure Check\_IC\_Barring + +CIB2(2) + +Procedure to check call request against SS barring and ODB categories + +``` +graph TD; 1((1)) --> Initiate_BAIC[Initiate handling of BAIC]; Initiate_BAIC --> To_MAF022[To process MAF022]; Initiate_BAIC --> Wait_BAIC[Wait_For_BAIC_Response]; Wait_BAIC --> Continue_BAIC[Continue call handling]; Continue_BAIC --> From_MAF022[From process MAF022]; Continue_BAIC --> Call_Barred_1{Call barred?}; Call_Barred_1 -- Yes --> Result_BAIC[Result:= Call barred (SS barring)]; Call_Barred_1 -- No --> Initiate_BIC[Initiate handling of BIC-Roam]; Initiate_BIC --> To_MAF023[To process MAF023]; Initiate_BIC --> Wait_BIC[Wait_For_BIC-Roam_Response]; Wait_BIC --> Continue_BIC[Continue call handling]; Continue_BIC --> From_MAF023[From process MAF023]; Continue_BIC --> Call_Barred_2{Call barred?}; Call_Barred_2 -- Yes --> Result_BAIC; Call_Barred_2 -- No --> Initiate_ACR[Initiate handling of ACR]; Initiate_ACR --> To_MAF024[To process MAF024]; Initiate_ACR --> Wait_ACR[Wait_For_ACR_Response]; Wait_ACR --> Continue_ACR[Continue call handling]; Continue_ACR --> From_MAF024[From process MAF024]; Continue_ACR --> Call_Barred_3{Call barred?}; Call_Barred_3 -- Yes --> Result_ACR[Result:= Call barred (ACR)]; Call_Barred_3 -- No --> Result_Allowed[Result:= Call allowed]; Result_BAIC --> Exit1(( )); Result_ACR --> Exit2(( )); Result_Allowed --> Exit3(( )); +``` + +Flowchart for procedure Check\_IC\_Barring. It starts with connector 1, then Initiate handling of BAIC (to process MAF022), Wait\_For\_BAIC\_Response, Continue call handling (from process MAF022). A decision 'Call barred?' follows. If Yes, Result:= Call barred (SS barring) and exit. If No, Initiate handling of BIC-Roam (to process MAF023), Wait\_For\_BIC-Roam\_Response, Continue call handling (from process MAF023). Another decision 'Call barred?' follows. If Yes, Result:= Call barred (SS barring) and exit. If No, Initiate handling of ACR (to process MAF024), Wait\_For\_ACR\_Response, Continue call handling (from process MAF024). A final decision 'Call barred?' follows. If Yes, Result:= Call barred (ACR) and exit. If No, Result:= Call allowed and exit. + +Figure 51b: Procedure Check\_IC\_Barring (sheet 2) + +![Flowchart for Procedure IC_CUG_Check. It starts with a call entry, checks if HLR supports CUG, then if SRI contains CUG info, then if Outgoing Access is present. Depending on these checks, it either allows the call, bars it with a cause, or waits for a response which leads to either a rejection or completion of the call.](b02ba0b73e95416eb547976f6145b169_img.jpg) + +### Procedure IC\_CUG\_Check + +IC\_CUG1(1) + +``` +graph TD; Entry([ ]) --> HLR{HLR supports CUG?}; HLR -- No --> SRI{SRI contains CUG info?}; HLR -- Yes --> Incoming[incoming call]; SRI -- No --> Allowed1[Result:= Call allowed]; SRI -- Yes --> Access{Outgoing Access present?}; Access -- No --> Barred[Result:= Call barred (cause)]; Access -- Yes --> Allowed2[Result:= Call allowed]; Incoming --> Wait[Wait_For_CUG_Response]; Wait --> Reject[/reject call (cause)/]; Wait --> Response[/response to call request/]; Wait --> Complete[/complete call (conditional CUG info)/]; Reject --> Barred; Response --> Allowed3[Result:= Call allowed]; Complete --> Allowed3; Allowed1 --> Exit(( )); Barred --> Exit; Allowed3 --> Exit; +``` + +Procedure to carry out CUG authorisation check for an incoming (MT) call + +Signals to/from the right are to/from the process CUG\_MAF015 + +Flowchart for Procedure IC\_CUG\_Check. It starts with a call entry, checks if HLR supports CUG, then if SRI contains CUG info, then if Outgoing Access is present. Depending on these checks, it either allows the call, bars it with a cause, or waits for a response which leads to either a rejection or completion of the call. + +Figure 52: Procedure IC\_CUG\_Check + +![Flowchart for Procedure Handle_CFU. The process starts with a connector, followed by CAMEL_CHECK_SII2_CDTI (referencing TS 23.078). A decision 'Result = Pass?' follows. If 'Yes', it proceeds to 'initiate handling of CFU', then 'Wait_For_CFU_Result', then 'continue call handling'. A second decision 'Error?' follows. If 'Yes', it leads to 'Result= Fail'. If 'No', it proceeds to 'Normal call?'. If 'Normal call?' is 'Yes', it leads to 'Result= Continue'. If 'Normal call?' is 'No', it leads to 'Result= Forward'. All three result boxes ('Fail', 'Forward', 'Continue') lead to a common exit connector. Callouts indicate this is an HLR procedure for unconditional call forwarding and that signals are from/to the MAF007 process.](710ff83dc4a77abbe489fbf1a462845a_img.jpg) + +### Procedure Handle\_CFU + +H\_CFU1(1) + +``` +graph TD; Start([ ]) --> CAMEL[CAMEL_CHECK_SII2_CDTI]; CAMEL --- TS[See TS 23.078]; CAMEL --> Pass{Result = Pass?}; Pass -- Yes --> Init[initiate handling of CFU]; Pass -- No --> Continue[Result= Continue]; Init --> Wait[Wait_For_CFU_Result]; Wait --> ContinueCall[continue call handling]; ContinueCall --> Error{Error?}; Error -- Yes --> Fail[Result= Fail]; Error -- No --> Normal{Normal call?}; Normal -- Yes --> Continue; Normal -- No --> Forward[Result= Forward]; Fail --> Exit(( )); Forward --> Exit; Continue --> Exit; +``` + +Procedure in the HLR to handle Call Forwarding Unconditional + +Signals to/from the right are to/from the process MAF007 + +Flowchart for Procedure Handle\_CFU. The process starts with a connector, followed by CAMEL\_CHECK\_SII2\_CDTI (referencing TS 23.078). A decision 'Result = Pass?' follows. If 'Yes', it proceeds to 'initiate handling of CFU', then 'Wait\_For\_CFU\_Result', then 'continue call handling'. A second decision 'Error?' follows. If 'Yes', it leads to 'Result= Fail'. If 'No', it proceeds to 'Normal call?'. If 'Normal call?' is 'Yes', it leads to 'Result= Continue'. If 'Normal call?' is 'No', it leads to 'Result= Forward'. All three result boxes ('Fail', 'Forward', 'Continue') lead to a common exit connector. Callouts indicate this is an HLR procedure for unconditional call forwarding and that signals are from/to the MAF007 process. + +Figure 53: Procedure Handle\_CFU + +![Flowchart for Procedure Handle_CFNRC. The process starts with a connector, followed by CAMEL_CHECK_SII2_CDTI (referencing TS 23.078). A decision 'Result = Pass?' follows. If 'Yes', it proceeds to 'initiate handling of CFNRC', then 'Wait_For_CFNRC_Result', and 'continue call handling'. If 'No', it goes to 'Result = Not reachable'. From 'continue call handling', a decision 'Error?' follows. If 'Yes', it goes to 'Result = Fail'. If 'No', it proceeds to 'Mobile subscriber not reachable?'. If 'Yes' to that, it goes to 'Result = Not reachable'. If 'No', it goes to 'Result = Forward'. All three result boxes ('Fail', 'Forward', 'Not reachable') lead to a common exit connector.](1cd38e4f2ffcae2871964fa6313a9a27_img.jpg) + +### Procedure Handle\_CFNRC + +H\_CFNRC1(1) + +``` +graph TD; Start([ ]) --> CAMEL[CAMEL_CHECK_SII2_CDTI]; CAMEL --- TS[See TS 23.078]; CAMEL --> Pass{Result = Pass?}; Pass -- No --> NotReachable[Result = Not reachable]; Pass -- Yes --> Initiate{{initiate handling of CFNRC}}; Initiate --> Wait([Wait_For_CFNRC_Result]); Wait --> Continue{{continue call handling}}; Continue --> Error{Error?}; Error -- Yes --> Fail[Result = Fail]; Error -- No --> NotReachableQ{Mobile subscriber not reachable?}; NotReachableQ -- Yes --> NotReachable; NotReachableQ -- No --> Forward[Result = Forward]; Fail --> End(( )); Forward --> End; NotReachable --> End; +``` + +Procedure in the HLR or VLR to handle Call Forwarding on Mobile Subscriber Not Reachable + +Signals to/from the right are to/from the process MAF010 + +Flowchart for Procedure Handle\_CFNRC. The process starts with a connector, followed by CAMEL\_CHECK\_SII2\_CDTI (referencing TS 23.078). A decision 'Result = Pass?' follows. If 'Yes', it proceeds to 'initiate handling of CFNRC', then 'Wait\_For\_CFNRC\_Result', and 'continue call handling'. If 'No', it goes to 'Result = Not reachable'. From 'continue call handling', a decision 'Error?' follows. If 'Yes', it goes to 'Result = Fail'. If 'No', it proceeds to 'Mobile subscriber not reachable?'. If 'Yes' to that, it goes to 'Result = Not reachable'. If 'No', it goes to 'Result = Forward'. All three result boxes ('Fail', 'Forward', 'Not reachable') lead to a common exit connector. + +Figure 54: Procedure Handle\_CFNRC + +![Flowchart for process Domain_Selection_HLR. It starts with a start symbol, followed by a 'Domain_Selection' block with a note 'refer to TS 23.221'. A decision diamond asks 'Session to be routed to IMS?'. If 'yes', it goes to 'Result:= to IMS'. If 'no', it goes to 'Result:= to CS'. Both paths lead to an end symbol.](884c44b6cb9fbe15347e0562a6085df2_img.jpg) + +process Domain\_Selection\_HLR 1(1) + +procedure in the HLR to determine how to route the session + +``` +graph TD; Start([ ]) --> DS[Domain_Selection]; DS --- Note[refer to TS 23.221]; DS --> Decision{Session to be routed to IMS?}; Decision -- yes --> ResultIMS[Result:= to IMS]; Decision -- no --> ResultCS[Result:= to CS]; ResultIMS --> End((X)); ResultCS --> End; +``` + +Flowchart for process Domain\_Selection\_HLR. It starts with a start symbol, followed by a 'Domain\_Selection' block with a note 'refer to TS 23.221'. A decision diamond asks 'Session to be routed to IMS?'. If 'yes', it goes to 'Result:= to IMS'. If 'no', it goes to 'Result:= to CS'. Both paths lead to an end symbol. + +**Figure 54A: Process Domain\_Selection\_HLR** + +## 7.2.3 Functional requirements of VLR + +### 7.2.3.1 Process PRN\_VLR + +Sheet 1: the procedure Check\_Parameters is specified in subclause 7.2.2.2. + +Sheet 1: the test "Pre-paging allowed" takes the "yes" exit if: + +- the information element "Pre-paging supported" was present in the Provide Roaming Number message; or +- as an operator option, the paging procedure can be completed before the minimum timer value for the Provide Roaming Number operation timer in the HLR has elapsed. + +Sheet 1: the procedure Check\_Reason\_In\_Serving\_Network\_Entity is specific to Super-Charger; it is specified in 3GPP TS 23.116 [24]. If the VLR does not support Super-Charger, processing continues from the "No" exit of the test "Result=Purged?". + +Sheet 1: Pre-paging is not applicable if the Provide Roaming Number request includes the MTRF Indicator. + +Sheet 2, sheet 3, sheet 6, sheet 7: the procedure CAMEL\_SET\_SOA is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. + +Sheet 2, sheet 3, sheet 6, sheet 7: the task "Store alerting pattern (if received)" is executed only if the VLR supports the feature Network Indication of Alerting. + +Sheet 2, sheet 3, sheet 6, sheet 7: the procedure CLI\_PRN\_VLR is specific to Enhanced CLI Handling. It is specified in 3GPP TS 23.081 [14]. + +Sheet 2, sheet 3, sheet 6, sheet 7: the procedure CCBS\_Handle\_PRN is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 2, sheet 4: A VLR not supporting the flag "Subscriber data dormant" shall behave as if this flag is set to false. + +Sheet 2: As an implementation option, the VLR may skip the "Authorize\_MTRF\_VLR" procedure (i.e. assume the result of that procedure takes the "Pass" exit) and allocates an MSRN before the completion of the MAP Update Location procedure with the HLR. + +Sheet 3, sheet 4: the number of unused authentication sets which triggers the VLR to request further authentication sets from the HLR is an operator option. + +Sheet 3, sheet 4: the process Fetch\_Authentication\_Sets\_VLR is specified in subclause 7.1.2.11. + +Sheet 4: the procedure Search\_For\_MS\_VLR is specified in subclause 7.3.2.3. + +Sheet 4: the test "Paging via SGSN possible" takes the "yes" exit if: + +- the Gs interface is implemented; and +- there is an association established for the MS between the MSC/VLR and the SGSN. + +Sheet 4: "Location cancelled" cause is set when VMSC receives Cancel Location while paging. + +Sheet 6: "Location cancelled with new VLR address" cause is set when VMSC receives Cancel Location with MTRF Supported And Authorized while paging and new MSC/VLR numbers have been received either in the Cancel Location or the Send Identification message. + +Sheet 7, sheet 8: the state variables PAR pending, PAR successful and Fatal PAR error are global data, accessible to the matching instance of the process ICH\_VLR, which is linked by the MSRN. + +Sheet 8: this process communicates with the matching instance of the process ICH\_VLR, which is linked by the MSRN. + +Sheet 8: the test "Fatal PAR error?" takes the "Yes" exit if: + +- the MS failed authentication; or +- the MS failed IMEI checking; or +- the HLR returned an "Unknown subscriber" error; + +during the handling of the Process Access Request. + +#### 7.2.3.2 Process Restore\_Subscriber\_Data\_VLR + +#### 7.2.3.3 Process PSI\_VLR + +Sheet 1: the procedure Check\_Parameters is specified in subclause 7.2.2.2. If the HLR requests none of location information subscriber state, MS classmark and IMEI, the VLR treats this as a missing parameter. + +Sheet 2: the test "Active retrieval required" takes the "Yes" exit if any one or more of current location, MS classmark or IMEI is indicated in the Provide Subscriber Info request. + +#### 7.2.3.4 Procedure Retrieve\_Location\_Info\_VLR + +The test "Retrieve location info from SGSN" takes the "Yes" exit if: + +- the Gs interface is implemented; and +- there is an association established between the VLR and the SGSN. + +The stored location information consists of: + +- the service area ID (for UMTS) or cell ID (for GSM) or the tracking area ID and the E-UTRAN cell ID (for E-UTRAN) of the cell in which the MS last established radio contact; +- the location number, geodetic information and geographical information derived from the service area ID or cell ID if the VLR is capable of doing so (the mapping from service area ID or cell ID to location number is network-specific and outside the scope of the UMTS and GSM standards); +- the age of the location information. + +The output signal Send MS information towards the SGSN indicates that the required information is mobile location information. + +The received location information consists of: + +- the service area ID (for UMTS) or cell ID (for GSM) received in the paging response message or in the Send MS Information ack or the tracking area ID and the E-UTRAN cell ID (for E-UTRAN) received in the SGs service request; +- the location number, geodetic information and geographical information derived from the service area ID or cell ID if the VLR is capable of doing so (the mapping from cell ID to location number is network-specific and outside the scope of the UMTS and GSM standards); + +- the age of the location information. + +The derivation of the location number, geodetic information and geographical information from the received service area ID or cell ID is a VLR operator option (the mapping from service area ID or cell ID to location number is network-specific and outside the scope of the UMTS and GSM standards). + +#### 7.2.3.5 Procedure Active\_Info\_Retrieval\_VLR + +Sheet 1: the test "Paging via SGSN possible" takes the "yes" exit if: + +- the Gs interface is implemented; and +- the VLR configuration requires paging via the SGSN during VLR restoration. + +If the SGs interface is implemented and the conditions for paging over the SGs interface as specified in subclause 5.1.2.2 of 3GPP TS 29.118 [41] are fulfilled, the VLR shall send an SGs paging request to the MME. The VLR should indicate the "SMS" service indicator in the SGs paging request if the LocationInformationEPS-Supported flag was received in the Provide Subscriber Information request; otherwise the VLR should indicate the "CS" service indicator. If the VLR indicates the "SMS" service indicator, the VLR should then send an SGs Release Request message to the MME upon receipt of the SGs Service Request message (including the tracking area ID and E-UTRAN cell ID). + +The VLR should return in the Provide Subscriber Information response the tracking area ID and E-UTRAN cell ID received from the MME if the LocationInformationEPS-Supported flag was received in the Provide Subscriber Information request and the UE uses the E-UTRAN radio access; otherwise the VLR should return the service area ID (for UMTS) or cell ID (for GSM) received from UTRAN or GERAN. + +NOTE: Using the "CS" service indicator leads the UE to fallback to GERAN or UTRAN radio access which can affect on-going PS sessions of the user, e.g. suspend on-going PS sessions if the UE fallbacks to GERAN radio access and Dual Transfer Mode is not supported, and which can cause extra Location Update signalling in the network. + +Sheet 2: the output signal Page MS towards the SGSN includes or omits the Location area identity parameter depending on the availability of this information. If it is omitted, the signal Page MS is sent to every SGSN to which the VLR is connected. + +The test "Report upon change of service area" takes the yes exit if the MSC has performed the Location Reporting Control procedure with the Request Type IE set to "change of service area" [26]. + +If the test "Report upon change of service area" takes the no exit, then the MSC shall perform a Location Reporting Control procedure with the Request Type IE set to "Direct". + +![Flowchart for Process PRN_VLR. The process starts at an 'Idle' state, receives a 'Provide Roaming Number' signal, checks parameters, and then branches based on various conditions like 'Result=Pass?', 'OR indicator present?', 'OR supported?', 'Service supported by VLR?', 'IMSI known in VLR?', 'MTRF indicator present?', 'Pre-paging supported in VLR?', 'Pre-paging allowed?', and 'Result=Purged?'. It ends at an 'Idle' state or provides a negative response.](69edc2887e907309499ac95b47ab6905_img.jpg) + +**Process PRN\_VLR** PRN\_VLR1(8) + +Process in the VLR to handle a request for a roaming number + +Signals to/from the left are to/from the HLR or the old VLR (MT Roaming Forwarding). + +``` + +graph TD + Start([Idle]) --> PRN[Provide Roaming Number] + PRN --> CheckParams[Check Parameters] + CheckParams --> ResultPass{Result=Pass?} + ResultPass -- No --> Connector1((1)) + ResultPass -- Yes --> ORIndicator{OR indicator present?} + ORIndicator -- No --> PRN + ORIndicator -- Yes --> ORSupported{OR supported?} + ORSupported -- No --> PRN + ORSupported -- Yes --> ConvertPLMN[Convert PLMN BC to basic service] + ConvertPLMN --> ServiceSupported{Service supported by VLR?} + ServiceSupported -- No --> NegativeResponse[Set negative response: Facility not supported] + NegativeResponse --> PRNNegative[Provide Roaming Number negative response] + ServiceSupported -- Yes --> PrePagingSupported{Pre-paging supported in VLR?} + PrePagingSupported -- No --> PrePagingAllowed{Pre-paging allowed?} + PrePagingAllowed -- No --> Connector2((2)) + PrePagingAllowed -- Yes --> IMSIKnown1{IMSI known in VLR?} + IMSIKnown1 -- Yes --> MTRFIndicator{MTRF indicator present?} + IMSIKnown1 -- No --> Connector4((4)) + MTRFIndicator -- Yes --> NegativeResponse1[Set negative response: Absent Subscriber] + NegativeResponse1 --> Connector1_1((1)) + MTRFIndicator -- No --> CheckReason1[Check Reason In Serving Network Entity] + CheckReason1 --> ResultPurged1{Result=Purged?} + ResultPurged1 -- No --> Connector3((3)) + ResultPurged1 -- Yes --> Connector1_2((1)) + PrePagingSupported -- Yes --> PrePagingAllowed + PrePagingAllowed -- Yes --> IMSIKnown2{IMSI known in VLR?} + IMSIKnown2 -- Yes --> Connector5((5)) + IMSIKnown2 -- No --> CheckReason2[Check Reason In Serving Network Entity] + CheckReason2 --> ResultPurged2{Result=Purged?} + ResultPurged2 -- No --> Connector5 + ResultPurged2 -- Yes --> Connector1_3((1)) + Note1[If PLMN BC was included in the Provide Roaming Number] -.-> ConvertPLMN + Note2[See TS 23.116] -.-> CheckReason2 + PRNNegative --> End([Idle]) + +``` + +Flowchart for Process PRN\_VLR. The process starts at an 'Idle' state, receives a 'Provide Roaming Number' signal, checks parameters, and then branches based on various conditions like 'Result=Pass?', 'OR indicator present?', 'OR supported?', 'Service supported by VLR?', 'IMSI known in VLR?', 'MTRF indicator present?', 'Pre-paging supported in VLR?', 'Pre-paging allowed?', and 'Result=Purged?'. It ends at an 'Idle' state or provides a negative response. + +Figure 55a: Process PRN\_VLR (sheet 1) + +![Flowchart for Process PRN_VLR. The process starts at connector 2. It checks if subscriber data is dormant. If true, it sets a negative response 'Purged MS' and goes to connector 1. If false, it checks if an MT RF indicator is present. If yes, it authorizes MT RF in the VLR and checks the result. If the result is 'Pass', it goes to connector 9. If 'Fail', it goes to connector 1. If the MT RF indicator is not present, it checks if the IMSI is detached. If true, it goes to connector 9. If false, it checks if roaming in the LA is allowed. If no, it goes to connector 9. If yes, it checks if MT Roaming Retry is supported. If no, it goes to connector 9. If yes, it checks if data is confirmed by the HLR. If false, it checks if more authentication sets are needed. If yes, it fetches authentication sets in the VLR, restores subscriber data in the VLR, and goes to connector 9. If no, it proceeds to allocate the MSRN. If data is confirmed by the HLR, it proceeds to allocate the MSRN. Next, it checks if the MSRN is available. If no, it goes to connector 9. If yes, it checks the MSC per VLR. If there is more than one MSC per VLR, it checks if the received MSC number matches the stored MSC number. If no, it checks if confirmed by radio contact. If yes, it uses the received MSC number for the MSRN. If no, it uses the stored MSC number for the MSRN. If there is only one MSC per VLR, it uses the received MSC number for the MSRN. Then it allocates the MSRN, sets the CAMEL SET_SO_A, stores compatibility info (including PLMN BC, ISDN BC, ISDN LLC & ISDN HLC), stores the alerting pattern (if received), and stores the PgA (if received and supported). It then sends CLI_PRN_VLR (See TS 23.081) and OCBS_Handle_PRN (See TS 23.093). Finally, it provides the roaming number and checks if MT Roaming Retry is supported or the MT RF indicator is present. If yes, it goes to connector 6. If no, it goes to the Idle state.](d3ca266c298aeb34b019960c6c36f187_img.jpg) + +**Process PRN\_VLR** **PRN\_VLR2(8)** + +Process in the VLR to handle a request for a roaming number + +Signals to the left are to the HLR or the old VLR (MT Roaming Forwarding). + +``` + +graph TD + Start((2)) --> SD{Subscriber data dormant} + SD -- True --> SR1[Set negative response: Purged MS] + SR1 --> End1((1)) + SD -- False --> MT{MT RF Indicator present?} + MT -- Yes --> Auth[Authorize MT RF_VLR] + Auth --> Res{Result} + Res -- Pass --> End9((9)) + Res -- Fail --> End1 + MT -- No --> IMSI{IMSI detached} + IMSI -- True --> End9 + IMSI -- False --> Roam{Roaming in LA allowed?} + Roam -- No --> End9 + Roam -- Yes --> MTRetry{MT Roaming Retry Supported} + MTRetry -- No --> End9 + MTRetry -- Yes --> DataConf{Data confirmed by HLR?} + DataConf -- False --> MoreAuth{More authentication sets needed?} + MoreAuth -- Yes --> Fetch[Fetch Authentication Sets_VLR] + Fetch --> Restore[Restore Subscriber Data_VLR] + Restore --> End9 + DataConf -- True --> MSRNAvail{MSRN available?} + MSRNAvail -- No --> End9 + MSRNAvail -- Yes --> MSCPerVLR{MSC per VLR} + MSCPerVLR -- "> 1" --> RecMSC{Received MSC number = Stored MSC number?} + RecMSC -- No --> RadioConf{Confirmed by radio contact} + RadioConf -- True --> UseRec[Use received MSC number for MSRN] + RadioConf -- False --> UseStore[Use stored MSC number for MSRN] + MSCPerVLR -- "1" --> UseRec + UseRec --> Alloc[Allocate MSRN] + UseStore --> Alloc + Alloc --> CAMEL[CAMEL SET_SO_A] + CAMEL --> StoreCompat[Store compatibility info] + StoreCompat --> StoreAlert[Store Alerting Pattern if received] + StoreAlert --> StorePgA[Store PgA if received and supported] + StorePgA --> CLI[CLI_PRN_VLR] + CLI --> TS23081[See TS 23.081] + StorePgA --> OCBS[OCBS_Handle_PRN] + OCBS --> TS23093[See TS 23.093] + StorePgA --> ProvideRoam{Provide Roaming Number ack} + ProvideRoam --> MTRetryOrMT{MT Roaming Retry Supported or MT RF Indicator present?} + MTRetryOrMT -- Yes --> End6((6)) + MTRetryOrMT -- No --> Idle[Idle] + +``` + +See TS 23.078 + +PLMN BC, ISDN BC, ISDN LLC & ISDN HLC (as available) + +Set negative response: No roaming number + +Set negative response: Absent subscriber + +Flowchart for Process PRN\_VLR. The process starts at connector 2. It checks if subscriber data is dormant. If true, it sets a negative response 'Purged MS' and goes to connector 1. If false, it checks if an MT RF indicator is present. If yes, it authorizes MT RF in the VLR and checks the result. If the result is 'Pass', it goes to connector 9. If 'Fail', it goes to connector 1. If the MT RF indicator is not present, it checks if the IMSI is detached. If true, it goes to connector 9. If false, it checks if roaming in the LA is allowed. If no, it goes to connector 9. If yes, it checks if MT Roaming Retry is supported. If no, it goes to connector 9. If yes, it checks if data is confirmed by the HLR. If false, it checks if more authentication sets are needed. If yes, it fetches authentication sets in the VLR, restores subscriber data in the VLR, and goes to connector 9. If no, it proceeds to allocate the MSRN. If data is confirmed by the HLR, it proceeds to allocate the MSRN. Next, it checks if the MSRN is available. If no, it goes to connector 9. If yes, it checks the MSC per VLR. If there is more than one MSC per VLR, it checks if the received MSC number matches the stored MSC number. If no, it checks if confirmed by radio contact. If yes, it uses the received MSC number for the MSRN. If no, it uses the stored MSC number for the MSRN. If there is only one MSC per VLR, it uses the received MSC number for the MSRN. Then it allocates the MSRN, sets the CAMEL SET\_SO\_A, stores compatibility info (including PLMN BC, ISDN BC, ISDN LLC & ISDN HLC), stores the alerting pattern (if received), and stores the PgA (if received and supported). It then sends CLI\_PRN\_VLR (See TS 23.081) and OCBS\_Handle\_PRN (See TS 23.093). Finally, it provides the roaming number and checks if MT Roaming Retry is supported or the MT RF indicator is present. If yes, it goes to connector 6. If no, it goes to the Idle state. + +Figure 55b: Process PRN\_VLR (sheet 2) + +![Flowchart for Process PRN_VLR (sheet 2). The process starts at connector 3. It checks if MSRN is available. If No, it sets a negative response and goes to connector 1. If Yes, it allocates MSRN, calls CAMEL_SET_SOA (refer to TS 23.078), creates an IMSI record, and confirms location info in HLR. If location info is not confirmed (False), it sets flags for radio contact, HLR confirmation, and IMSI detachment. Then it allocates LMSI (if used by VLR), stores compatibility info (PLMN BC, ISDN BC, ISDN LLC & ISDN HLC), and stores alerting pattern. It then reaches connector 6. From connector 6, it checks if data is confirmed by HLR. If True, it checks if more authentication sets are needed. If Yes, it provides a roaming number ack, fetches authentication sets, restores subscriber data, and goes to Idle. If False (either from connector 6 or after authentication check), it stores PgA (if received and supported), calls CLI_PRN_VLR (refer to TS 23.081), calls CCBS_Handle_PRN (refer to TS 23.093), provides a roaming number ack, fetches authentication sets, restores subscriber data, and goes to Idle.](53f1f7d17b3e7aae62169c41d2a88a77_img.jpg) + +**Process PRN\_VLR** PRN\_VLR3(8) + +Process in the VLR to handle a request for a roaming number + +Signals to the left are to the HLR. + +``` + +graph TD + 3((3)) --> MSRN{MSRN available} + MSRN -- No --> Neg[Set negative response: +No roaming number] + Neg --> 1((1)) + MSRN -- Yes --> AllocMSRN[Allocate MSRN] + AllocMSRN --> CAMEL[CAMEL_SET_SOA] + CAMEL -.-> TS23078[See TS 23.078] + CAMEL --> IMSI[Create IMSI record] + IMSI --> Loc[Location info confirmed in HLR:=] + Loc -.-> Only1[Only if >1 MSC per VLR] + Loc -- False --> Flags[Confirmed by radio contact:=False; +Data confirmed by HLR:=False; +IMSI detached:=False] + Flags --> LMSI[Allocate LMSI] + LMSI -.-> Used[If used by VLR] + LMSI --> Compat[Store compatibility info] + Compat -.-> Info[PLMN BC, ISDN BC, +ISDN LLC & ISDN HLC +(as available)] + Compat --> Alert[Store Alerting Pattern +(if received)] + Alert --> 6((6)) + 6 --> Data{Data confirmed by HLR?} + Data -- True --> MoreAuth{More authentication sets needed?} + MoreAuth -- Yes --> Ack1{Provide Roaming Number ack} + MoreAuth -- No --> Fetch[Fetch Authentication Sets_VLR] + Data -- False --> PgA[Store PgA +(if received and supported)] + PgA --> CLI[CLI_PRN_VLR] + CLI -.-> TS23081[See TS 23.081] + CLI --> CCBS[CCBS_Handle_PRN] + CCBS -.-> TS23093[See TS 23.093] + CCBS --> Ack2{Provide Roaming Number ack} + Ack1 --> Fetch + Ack2 --> Fetch + Fetch --> Restore[Restore Subscriber Data_VLR] + Restore --> Idle([Idle]) + +``` + +Flowchart for Process PRN\_VLR (sheet 2). The process starts at connector 3. It checks if MSRN is available. If No, it sets a negative response and goes to connector 1. If Yes, it allocates MSRN, calls CAMEL\_SET\_SOA (refer to TS 23.078), creates an IMSI record, and confirms location info in HLR. If location info is not confirmed (False), it sets flags for radio contact, HLR confirmation, and IMSI detachment. Then it allocates LMSI (if used by VLR), stores compatibility info (PLMN BC, ISDN BC, ISDN LLC & ISDN HLC), and stores alerting pattern. It then reaches connector 6. From connector 6, it checks if data is confirmed by HLR. If True, it checks if more authentication sets are needed. If Yes, it provides a roaming number ack, fetches authentication sets, restores subscriber data, and goes to Idle. If False (either from connector 6 or after authentication check), it stores PgA (if received and supported), calls CLI\_PRN\_VLR (refer to TS 23.081), calls CCBS\_Handle\_PRN (refer to TS 23.093), provides a roaming number ack, fetches authentication sets, restores subscriber data, and goes to Idle. + +Figure 55c: Process PRN\_VLR (sheet 3) + +![Flowchart for Process PRN_VLR. It starts at connector 4, checks if subscriber data is dormant. If true, it sets a negative response (purged MS) and goes to connector 1. If false, it checks if IMSI is detached. If yes, it goes to connector 1. If no, it checks if roaming in LA is allowed. If no, it goes to connector 1. If yes, it checks if location area ID is known. If yes, it checks if data is confirmed by HLR. If true, it searches for MS_VLR. If false, it checks if more authentication sets are needed. If yes, it fetches authentication sets, restores subscriber data, and searches for MS_VLR. If no, it goes to connector 1. If data is confirmed by HLR, it searches for MS_VLR. If location area ID is not known, it checks if paging via SGSN is possible. If yes, it sets paging via SGSN possible and pages MS with circuit-switched call type, then waits for access request. If no, it goes to connector 1. After searching for MS_VLR, if result passes, it goes to connector 1. If not, it checks if absent subscriber. If yes, it sets negative response (absent subscriber) and goes to connector 1. If no, it checks if location cancelled. If yes, it sets negative response (purged MS) and goes to connector 1. If no, it goes to connector 7.](88b0f3f4393228e9ea4d6542aef7c399_img.jpg) + +**Process PRN\_VLR** **PRN\_VLR4(8)** + +Process in the VLR to handle a request for a roaming number + +Signals to the right are to the MSC. + +``` + +graph TD + 4((4)) --> SD{Subscriber data dormant?} + SD -- True --> SNR1[Set negative response: Purged MS] + SNR1 --> 1a((1)) + SD -- False --> ID{IMSI detached?} + ID -- Yes --> 1b((1)) + ID -- No --> RL{Roaming in LA allowed?} + RL -- No --> 1c((1)) + RL -- Yes --> LID{Location area ID known?} + LID -- Yes --> DH{Data confirmed by HLR?} + DH -- True --> SFMVS[Search_For_MS_VLR] + DH -- False --> MAS{More authentication sets needed?} + MAS -- Yes --> FAS[Fetch_Authentication_Sets_VLR] + FAS --> RSD[Restore_Subscriber_Data_VLR] + RSD --> SFMVS + LID -- No --> PS{Paging via SGSN possible?} + PS -- Yes --> SP[Set Paging via SGSN possible] + SP --> PM[Page MS] + PM --> PT[Page type= circuit-switched call] + PT --> WFR[Wait_For_Access_Request] + SFMVS --> RP{Result= Pass?} + RP -- Yes --> 1d((1)) + RP -- No --> AS{Absent subscriber?} + AS -- Yes --> SNR2[Set negative response: Absent subscriber] + SNR2 --> 1e((1)) + AS -- No --> LC{Location cancelled?} + LC -- Yes --> SNR3[Set negative response: Purged MS] + SNR3 --> 1f((1)) + LC -- No --> 7((7)) + +``` + +Flowchart for Process PRN\_VLR. It starts at connector 4, checks if subscriber data is dormant. If true, it sets a negative response (purged MS) and goes to connector 1. If false, it checks if IMSI is detached. If yes, it goes to connector 1. If no, it checks if roaming in LA is allowed. If no, it goes to connector 1. If yes, it checks if location area ID is known. If yes, it checks if data is confirmed by HLR. If true, it searches for MS\_VLR. If false, it checks if more authentication sets are needed. If yes, it fetches authentication sets, restores subscriber data, and searches for MS\_VLR. If no, it goes to connector 1. If data is confirmed by HLR, it searches for MS\_VLR. If location area ID is not known, it checks if paging via SGSN is possible. If yes, it sets paging via SGSN possible and pages MS with circuit-switched call type, then waits for access request. If no, it goes to connector 1. After searching for MS\_VLR, if result passes, it goes to connector 1. If not, it checks if absent subscriber. If yes, it sets negative response (absent subscriber) and goes to connector 1. If no, it checks if location cancelled. If yes, it sets negative response (purged MS) and goes to connector 1. If no, it goes to connector 7. + +Figure 54d: Process PRN\_VLR (sheet 4) + +![Flowchart for Process PRN_VLR. It starts at connector 5, proceeds through creating an IMSI record, confirming location info in HLR, a radio contact check, allocating an LMSI, storing compatibility info, fetching authentication sets, restoring subscriber data, and searching for the MS_VLR. A decision 'Result=Pass?' follows. If 'Yes', it goes to connector 1. If 'No', it checks 'Absent subscriber?'. If 'Yes' to 'Absent subscriber?', it sets a negative response and goes to connector 1. If 'No' to 'Absent subscriber?', it goes to connector 7. There is also a 'Wait_For_Access_Request' connector.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +### Process PRN\_VLR + +PRN\_VLR5(8) + +Process in the VLR to handle a request for a roaming number + +``` +graph TD; 5((5)) --> A[Create IMSI record]; A --> B[Location info confirmed in HLR:=False]; B --- B_note[Only if >1 MSC per VLR]; B --> C[ ]; C --- C_note["Confirmed by radio contact:=False; Data confirmed by HLR:=False; IMSI detached:=False"]; C --> D[Allocate LMSI]; D --- D_note[If used by VLR]; D --> E[Store compatibility info]; E --- E_note["PLMN BC, ISDN BC, ISDN LLC & ISDN HLC (as available)"]; E --> F[Fetch Authentication_Sets_VLR]; F --> G[Restore Subscriber Data_VLR]; G --> H[Search_For_MS_VLR]; H --> I{Result=Pass?}; I -- Yes --> J((1)); I -- No --> K{Absent subscriber?}; K -- Yes --> L[Set negative response: Absent subscriber]; L --> J; K -- No --> M((7)); I --> N[Wait_For_Access_Request]; +``` + +Flowchart for Process PRN\_VLR. It starts at connector 5, proceeds through creating an IMSI record, confirming location info in HLR, a radio contact check, allocating an LMSI, storing compatibility info, fetching authentication sets, restoring subscriber data, and searching for the MS\_VLR. A decision 'Result=Pass?' follows. If 'Yes', it goes to connector 1. If 'No', it checks 'Absent subscriber?'. If 'Yes' to 'Absent subscriber?', it sets a negative response and goes to connector 1. If 'No' to 'Absent subscriber?', it goes to connector 7. There is also a 'Wait\_For\_Access\_Request' connector. + +Figure 54e: Process PRN\_VLR (sheet 5) + +![Flowchart for Process PRN_VLR (sheet 6) showing logic for roaming number allocation, paging via SGSN, and MT Roaming Forwarding support.](d0abac95583b52a3b35f74a215567334_img.jpg) + +## Process PRN\_VLR + +## PRN\_VLR6(8) + +Process in the VLR to handle a request for a roaming number + +Signals to the left are to the HLR; signals to/from the right are to/from the MSC or to/from the new VLR unless shown otherwise. + +``` + + graph TD + Wait([Wait_For_Access_Request]) + + %% Path 1: Page MS via SGSN + Wait --- PageSGSN[Page MS via SGSN] + PageSGSN --> PageMS{Page MS} + PageMS -- To SGSN --> Wait + + %% Path 2: Process Access Request + Wait --- ProcAccReq[Process Access Request] + ProcAccReq --> MSRNAvail{MSRN available?} + MSRNAvail -- No --> SetSysFail[Set negative response: System failure] + MSRNAvail -- Yes --> MSCperVLR{MSC per VLR} + + MSCperVLR -- 1 --> AllocMSRN[Allocate MSRN] + MSCperVLR -- >1 --> RecMSC{Received MSC number = Stored MSC number?} + RecMSC -- Yes --> AllocMSRN + RecMSC -- No --> ConfRadio{Confirmed by radio contact} + ConfRadio -- True --> UseStored[Use stored MSC number for MSRN] --> AllocMSRN + ConfRadio -- False --> UseRec[Use received MSC number for MSRN] --> AllocMSRN + + AllocMSRN --> CAMEL[CAMEL_SET_SOA] -- See TS 23.078 --> StoreComp[Store compatibility info] + StoreComp -- "PLMN BC, ISDN BC, ISDN LLC & ISDN HLC (as available)" --> StoreAlert[Store Alerting Pattern (if received)] + StoreAlert --> CLIPRN[CLI_PRN_VLR] -- See TS 23.081 --> CCBS[CCBS_Handle_PRN] + CCBS -- See TS 23.093 --> ProvRoamAck[Provide Roaming Number ack] + ProvRoamAck --> Exit8((8)) + + %% Path 3: Page MS negative response + Wait --- PageNeg[Page MS negative response] + PageNeg --> MTRFSupp{MT Roaming Forwarding supported?} + MTRFSupp -- No --> SetSysFail + MTRFSupp -- Yes --> LocCan{location cancelled with new VLR address?} + + LocCan -- No --> ToNewVLR[to New VLR] + LocCan -- Yes --> ProvRoamMTRF[Provide Roaming Number (MTRF Indicator)] + ProvRoamMTRF --> WaitMSRN([Wait_For_MSRN]) + WaitMSRN --> ProvRoamNegResp[Provide Roaming Number Negative Response] --> Idle([Idle]) + WaitMSRN --> ProvRoamAck2[Provide Roaming Number Ack] -- include MSRN --> ProvRoamAck3[Provide Roaming Number ack] --> Exit7((7)) + + %% Error Handling Flow + SetSysFail --> ProcAccNeg[Process Access Request negative response] + ProcAccNeg --> BusySub{Busy subscriber?} + BusySub -- Yes --> Exit7 + BusySub -- No --> AbsSub{Absent Subscriber?} + AbsSub -- Yes --> SetAbsSub[Set negative response: Absent subscriber] --> Exit1((1)) + AbsSub -- No --> SetNoRoam[Set negative response: No roaming number] --> Exit1 + +``` + +Flowchart for Process PRN\_VLR (sheet 6) showing logic for roaming number allocation, paging via SGSN, and MT Roaming Forwarding support. + +**Figure 54f: Process PRN\_VLR (sheet 6)** + +![](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +**Process PRN\_VLR** + +PRN\_VLR7(8) + +Process in the VLR to handle +a request for a roaming number + +Signals to the left +are to the HLR. + +``` + + graph TD + Start7((7)) --> MSRN_Avail{MSRN +available?} + + MSRN_Avail -- No --> SetNeg[Set negative +response: +No roaming +number] + SetNeg --> End1((1)) + + MSRN_Avail -- Yes --> MSC_VLR{MSC +per VLR} + + MSC_VLR -- 1 --> Allocate + MSC_VLR -- >1 --> RecMSC{Received MSC +number= Stored +MSC number?} + + RecMSC -- Yes --> Allocate + RecMSC -- No --> Confirmed{Confirmed by +radio contact} + + Confirmed -- False --> UseRec[Use received +MSC number +for MSRN] + Confirmed -- True --> UseStored[Use stored +MSC number +for MSRN] + + UseRec --> Allocate + UseStored --> Allocate + + Allocate[Allocate +MSRN] --> CAMEL[CAMEL_ +SET_SOA] + CAMEL --- TS078[See TS 23.078] + + CAMEL --> StoreCompat[Store +compatibility +info] + StoreCompat --- CompatInfo[PLMN BC, ISDN BC, +ISDN LLC & ISDN HLC +(as available)] + + StoreCompat --> StoreAlert[Store Alerting +Pattern +(if received)] + + StoreAlert --> CLI[CLI_PRN_ +VLR] + CLI --- TS081[See TS 23.081] + + CLI --> CCBS[CCBS_Handle_ +PRN] + CCBS --- TS093[See TS 23.093] + + CCBS --> Ack{Provide +Roaming +Number ack} + + Ack --> PAR[PAR pending:=False; +PAR successful:=False; +Fatal PAR error:=False] + + PAR --> Idle([Idle]) + +``` + +**Figure 54g: Process PRN\_VLR (sheet 7)** + +![Flowchart for Process PRN_VLR. It starts at connector 8, sets PAR pending to True, sends a Process Access Request VLR, and then checks the result. If the result is a pass, it sets PAR successful to True, PAR pending to False, reaches a PAR Completed state, waits for a call arrival, and then reaches an Idle state. If the result is not a pass, it sets PAR successful to False, PAR pending to False, and then checks for a fatal PAR error. If there is a fatal error, it sets Fatal PAR error to True and reaches a PAR Completed state. If there is no fatal error, it reaches a PAR Completed state directly. Both PAR Completed states lead to an Idle state. There are also transitions for 'Call arrived' and 'Radio connection released' leading to an Idle state.](e6df2733626a85205c1db682e6259c46_img.jpg) + +### Process PRN\_VLR + +PRN\_VLR8(8) + +Process in the VLR to handle a request for a roaming number + +Signals to/from the left are to/from the process ICH\_VLR; signals to/from the right are to/from the MSC + +``` +graph TD; Start((8)) --> P1[PAR pending:= True]; P1 --> P2[Process Access Request VLR]; P2 --> D1{Result= Pass?}; D1 -- No --> P3[PAR successful:= False]; D1 -- Yes --> P4[PAR successful:= True]; P4 --> P5[PAR pending:= False]; P5 --> D2{PAR Completed}; D2 --> P6((Wait_For_Call_Arrival)); P6 --> D3{Call arrived}; D3 --> P7[Call arrived]; P7 --> Idle1((Idle)); P3 --> P8[PAR pending:= False]; P8 --> D4{Fatal PAR error?}; D4 -- No --> D5{PAR Completed}; D4 -- Yes --> P9[Fatal PAR error:= True]; P9 --> D5; P9 --> P10[Fatal PAR error:= False]; P10 --> D5; D5 --> Idle2((Idle)); P10 --> P11[Radio connection released]; P11 --> P12[PAR successful:= False]; P12 --> P13[Fatal PAR error:= False]; P13 --> Idle1; +``` + +Flowchart for Process PRN\_VLR. It starts at connector 8, sets PAR pending to True, sends a Process Access Request VLR, and then checks the result. If the result is a pass, it sets PAR successful to True, PAR pending to False, reaches a PAR Completed state, waits for a call arrival, and then reaches an Idle state. If the result is not a pass, it sets PAR successful to False, PAR pending to False, and then checks for a fatal PAR error. If there is a fatal error, it sets Fatal PAR error to True and reaches a PAR Completed state. If there is no fatal error, it reaches a PAR Completed state directly. Both PAR Completed states lead to an Idle state. There are also transitions for 'Call arrived' and 'Radio connection released' leading to an Idle state. + +Figure 54h: Process PRN\_VLR (sheet 8) + +![State transition diagram for Process Restore_Subscriber_Data_VLR. The process starts at an initial state, moves to 'Restore Data', then 'Wait_For_Data'. From 'Wait_For_Data', it branches to 'Restore Data ack' (leading to 'Update Subscriber Data', 'Update HLR number', 'Update MS Not Reachable indicator', and 'Data confirmed by HLR:=True') and 'Restore Data negative response' (leading to a dead state). A note indicates 'If received from HLR' for the 'Update MS Not Reachable indicator' step.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +### Process Restore\_Subscriber\_Data\_VLR + +RSD\_VLR1(1) + +``` +stateDiagram-v2 + [*] --> Restore_Data + Restore_Data --> Wait_For_Data + state "Restore Data" as Restore_Data + state "Wait_For_Data" as Wait_For_Data + state "Restore Data ack" as Restore_Data_ack + state "Restore Data negative response" as Restore_Data_negative_response + state "Update Subscriber Data" as Update_Subscriber_Data + state "Update HLR number" as Update_HLR_number + state "Update MS Not Reachable indicator" as Update_MS_Not_Reachable_indicator + state "Data confirmed by HLR:=True" as Data_confirmed_by_HLR + state "*" as dead_state + + Wait_For_Data --> Restore_Data_ack + Wait_For_Data --> Restore_Data_negative_response + Restore_Data_ack --> Update_Subscriber_Data + Update_Subscriber_Data --> Update_HLR_number + Update_HLR_number --> Update_MS_Not_Reachable_indicator + Update_MS_Not_Reachable_indicator --> Data_confirmed_by_HLR + Data_confirmed_by_HLR --> dead_state + Restore_Data_negative_response --> dead_state +``` + +Process in the VLR to restore subscriber data + +Signals to/from the left are to/from the HLR + +If received from HLR + +State transition diagram for Process Restore\_Subscriber\_Data\_VLR. The process starts at an initial state, moves to 'Restore Data', then 'Wait\_For\_Data'. From 'Wait\_For\_Data', it branches to 'Restore Data ack' (leading to 'Update Subscriber Data', 'Update HLR number', 'Update MS Not Reachable indicator', and 'Data confirmed by HLR:=True') and 'Restore Data negative response' (leading to a dead state). A note indicates 'If received from HLR' for the 'Update MS Not Reachable indicator' step. + +Figure 56: Process Restore\_Subscriber\_Data\_VLR + +![Flowchart for Process PSI_VLR. It starts with an 'Idle' state, followed by 'Provide Subscriber Info' from HLR. It checks parameters, then if IMSI is known in VLR. If not known, it assumes idle and sends negative response. If known, it checks if subscriber state is requested. If not, it checks if IMSI is detached or if roaming in LA is allowed. If detached or not allowed to roam, it sets state to 'Network determined not reachable'. If roaming allowed or state requested, it checks if location info is requested. If yes, it stores location info. Finally, it either waits for MSC response, sends an ack, or assumes idle and sends negative response.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +### Process PSI\_VLR + +Process in the VLR to handle a request from the HLR for subscriber information + +PSI\_VLR1(2) + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the MSC + +``` +graph TD; Start([Idle]) --> Info[Provide Subscriber Info]; Info --> Check[Check Parameters]; Check --> Pass{Result= Pass?}; Pass -- No --> Neg[Provide Subscriber Info negative response]; Pass -- Yes --> IMSI{IMSI known in VLR?}; IMSI -- No --> Assume[Subscriber state:= Assumed idle]; IMSI -- Yes --> State{Subscriber state requested?}; State -- No --> Detach{IMSI detached?}; Detach -- Yes --> NotReach[Subscriber state:= Network determined not reachable]; Detach -- No --> Roam{Roaming in LA allowed?}; Roam -- No --> NotReach; Roam -- Yes --> Set[Set subscriber state requested]; State -- Yes --> Assume; Assume --> Neg; NotReach --> Loc{Location info requested?}; Loc -- No --> Neg; Loc -- Yes --> LocInfo[Location info:= Stored location info]; LocInfo --> Ack[Provide Subscriber Info ack]; Set --> Obtain[Obtain Subscriber Info]; Obtain --> Wait[Wait For MSC_Response]; Ack --> Idle1([Idle]); Neg --> Idle2([Idle]); +``` + +Flowchart for Process PSI\_VLR. It starts with an 'Idle' state, followed by 'Provide Subscriber Info' from HLR. It checks parameters, then if IMSI is known in VLR. If not known, it assumes idle and sends negative response. If known, it checks if subscriber state is requested. If not, it checks if IMSI is detached or if roaming in LA is allowed. If detached or not allowed to roam, it sets state to 'Network determined not reachable'. If roaming allowed or state requested, it checks if location info is requested. If yes, it stores location info. Finally, it either waits for MSC response, sends an ack, or assumes idle and sends negative response. + +Figure 57a: Process PSI\_VLR (sheet 1) + +![SDL Flowchart for Process PSI_VLR (sheet 2). The process starts at state 'Wait_For_MSC_Response'. It receives an input 'Obtain Subscriber Info ack'. It then checks 'Subscriber state received?'. If 'Yes', it performs 'Set subscriber state'. Then it checks 'Active retrieval required?'. If 'Yes', it calls procedure 'Active_Info_Retrieval_VLR'. If 'No', it checks 'Location info requested?'. If 'Yes', it calls procedure 'Retrive_Location_Info_VLR'. If 'No' to any of these branches, or after the procedures, it sends 'Provide Subscriber Info ack' and transitions to 'Idle' state.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +### Process PSI\_VLR + +PSI\_VLR2(2) + +Process in the VLR to handle a request from the HLR for subscriber information + +Signals to/from the left are to/from the HLR; signals to/from the right are to/from the MSC + +``` + +graph TD + Start([Wait_For_MSC_Response]) --> Input[/Obtain Subscriber Info ack/] + Input --> Dec1{Subscriber +state +received?} + Dec1 -- Yes --> Task1[Set +subscriber +state] + Dec1 -- No ----> Output[/Provide +Subscriber +Info ack/] + Task1 --> Dec2{Active +retrieval +required?} + Dec2 -- Yes --> Proc1[[Active_Info_ +Retrieval_ +VLR]] + Dec2 -- No --> Dec3{Location +info +requested?} + Dec3 -- Yes --> Proc2[[Retrive_ +Location_ +Info_VLR]] + Dec3 -- No ----> Output + Proc1 --> Output + Proc2 --> Output + Output --> End([Idle]) + +``` + +SDL Flowchart for Process PSI\_VLR (sheet 2). The process starts at state 'Wait\_For\_MSC\_Response'. It receives an input 'Obtain Subscriber Info ack'. It then checks 'Subscriber state received?'. If 'Yes', it performs 'Set subscriber state'. Then it checks 'Active retrieval required?'. If 'Yes', it calls procedure 'Active\_Info\_Retrieval\_VLR'. If 'No', it checks 'Location info requested?'. If 'Yes', it calls procedure 'Retrive\_Location\_Info\_VLR'. If 'No' to any of these branches, or after the procedures, it sends 'Provide Subscriber Info ack' and transitions to 'Idle' state. + +**Figure 57b: Process PSI\_VLR (sheet 2)** + +![Flowchart for Procedure Retrieve_Location_Info_VLR. It starts with a decision 'Retrieve location info from SGSN?'. If 'Yes', it sends MS information, waits for a response, and then either sends a negative response or an ack. If 'No', it stores the location info and ends. Notes indicate this is a VLR procedure and signals are from the SGSN.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +### Procedure Retrieve\_Location\_Info\_VLR + +RLI\_VLR1(1) + +``` +graph TD; Start([ ]) --> Decision{Retrieve location info from SGSN?}; Decision -- Yes --> SendMS[Send MS information]; SendMS --> Wait[Wait_For_SGSN_Response]; Wait --> SendNeg[Send MS Information negative response]; Wait --> SendAck[Send MS Information ack]; SendNeg --> StoreNeg[Location info:= Stored location info]; StoreNeg --> EndNeg(( )); SendAck --> StoreAck[Location info:= Received location info]; StoreAck --> Derive[Derive location number, geodetic information and geographical information]; Derive --> EndAck(( )); Decision -- No --> StoreNo[Location info:= Stored location info]; StoreNo --> EndNo(( )); Note1[Procedure in the VLR to retrieve location information for a subscriber]; Note2[Signals to/from the right are to/from the SGSN]; +``` + +Procedure in the VLR to retrieve location information for a subscriber + +Signals to/from the right are to/from the SGSN + +Flowchart for Procedure Retrieve\_Location\_Info\_VLR. It starts with a decision 'Retrieve location info from SGSN?'. If 'Yes', it sends MS information, waits for a response, and then either sends a negative response or an ack. If 'No', it stores the location info and ends. Notes indicate this is a VLR procedure and signals are from the SGSN. + +Figure 58: Procedure Retrieve\_Location\_Info\_VLR + +![Flowchart for Procedure Active_Info_Retrieval_VLR. The process starts with 'Set information required', followed by a decision 'Paging via SGSN possible?'. If 'No', it goes to 'Location area ID known?'. If 'Yes', it goes to 'Set paging via SGSN possible', then to 'Location area ID known?'. From 'Location area ID known?', if 'No', it goes to 'Search for MS' (with 'Page type= Active information retrieval') and then to 'Wait_For_Search_Result'. If 'Yes', it goes to 'Page MS' (with 'Page type= Active information retrieval') and then to 'Wait_For_Page_Result'.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +### Procedure Active\_Info\_Retrieval\_VLR + +AIR\_VLR1(2) + +``` +graph TD; Start([ ]) --> Step1[Set information required]; Step1 --> Decision1{Paging via SGSN possible?}; Decision1 -- No --> Decision2{Location area ID known?}; Decision1 -- Yes --> Step2[Set paging via SGSN possible]; Step2 --> Decision2; Decision2 -- No --> Search[Search for MS]; Search --> WaitSearch([Wait_For_Search_Result]); Search -.-> PageType1[Page type= Active information retrieval]; Decision2 -- Yes --> Page[Page MS]; Page --> WaitPage([Wait_For_Page_Result]); Page -.-> PageType2[Page type= Active information retrieval]; +``` + +Procedure in the VLR to retrieve the current location information for a subscriber + +Signals to/from the right are to/from the MSC + +Flowchart for Procedure Active\_Info\_Retrieval\_VLR. The process starts with 'Set information required', followed by a decision 'Paging via SGSN possible?'. If 'No', it goes to 'Location area ID known?'. If 'Yes', it goes to 'Set paging via SGSN possible', then to 'Location area ID known?'. From 'Location area ID known?', if 'No', it goes to 'Search for MS' (with 'Page type= Active information retrieval') and then to 'Wait\_For\_Search\_Result'. If 'Yes', it goes to 'Page MS' (with 'Page type= Active information retrieval') and then to 'Wait\_For\_Page\_Result'. + +Figure 59a: Procedure Active\_Info\_Retrieval\_VLR + +![Flowchart for Procedure Active_Info_Retrieval_VLR (sheet 2). The process starts with 'Wait_For_Search_Result' and branches into three paths: 'Search for MS ack', 'Search for MS negative response', and 'Search for MS via SGSN'. The first path leads to 'Roaming in LA allowed?' and then to 'Location info received?' (Yes/No), resulting in 'Location info:= Received location info' or 'Location info:= Stored location info'. The second path leads to 'Subscriber state:=Not reachable' and then to 'Location info received?' (Yes/No), resulting in 'Location info:= Received location info' or 'Location info:= Stored location info'. The third path leads to 'Page MS' and then to 'Wait_For_Search_Result'. The second part of the flowchart starts with 'Wait_For_Page_Result' and branches into three paths: 'Page MS ack', 'Page MS negative response', and 'Page MS via SGSN'. The first path leads to 'Location info received?' (Yes/No), resulting in 'Location info:= Received location info' or 'Location info:= Stored location info'. The second path leads to 'Page MS' and then to 'Wait_For_Page_Result'. The third path leads to 'Page MS' and then to 'Wait_For_Page_Result'.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +### Procedure Active\_Info\_Retrieval\_VLR + +AIR\_VLR2(2) + +Procedure in the VLR to retrieve the current location information for a subscriber + +``` +graph TD; subgraph Search; WFSR1([Wait_For_Search_Result]) --> S1[Search for MS ack]; WFSR1 --> S2[Search for MS negative response]; WFSR1 --> S3[Search for MS via SGSN]; S3 --> PMS1[Page MS]; PMS1 --> WFSR2([Wait_For_Search_Result]); S1 --> R1{Roaming in LA allowed?}; R1 -- No --> SS[Subscriber state:=Not reachable]; R1 -- Yes --> LIR1{Location info received?}; SS --> LIR2{Location info received?}; LIR1 -- Yes --> LI1[Location info:= Received location info]; LIR1 -- No --> LI2[Location info:= Stored location info]; LIR2 -- Yes --> LI3[Location info:= Received location info]; LIR2 -- No --> LI4[Location info:= Stored location info]; LI1 --> C1(( )); LI2 --> C1; LI3 --> C2(( )); LI4 --> C2; S2 --> C3(( )); end; subgraph Page; WPR1([Wait_For_Page_Result]) --> PM1[Page MS ack]; WPR1 --> PM2[Page MS negative response]; WPR1 --> PM3[Page MS via SGSN]; PM3 --> PMS2[Page MS]; PMS2 --> WPR2([Wait_For_Page_Result]); PM1 --> LIR3{Location info received?}; LIR3 -- Yes --> LI5[Location info:= Received location info]; LIR3 -- No --> LI6[Location info:= Stored location info]; LI5 --> C4(( )); LI6 --> C4; PM2 --> C5(( )); end; +``` + +Flowchart for Procedure Active\_Info\_Retrieval\_VLR (sheet 2). The process starts with 'Wait\_For\_Search\_Result' and branches into three paths: 'Search for MS ack', 'Search for MS negative response', and 'Search for MS via SGSN'. The first path leads to 'Roaming in LA allowed?' and then to 'Location info received?' (Yes/No), resulting in 'Location info:= Received location info' or 'Location info:= Stored location info'. The second path leads to 'Subscriber state:=Not reachable' and then to 'Location info received?' (Yes/No), resulting in 'Location info:= Received location info' or 'Location info:= Stored location info'. The third path leads to 'Page MS' and then to 'Wait\_For\_Search\_Result'. The second part of the flowchart starts with 'Wait\_For\_Page\_Result' and branches into three paths: 'Page MS ack', 'Page MS negative response', and 'Page MS via SGSN'. The first path leads to 'Location info received?' (Yes/No), resulting in 'Location info:= Received location info' or 'Location info:= Stored location info'. The second path leads to 'Page MS' and then to 'Wait\_For\_Page\_Result'. The third path leads to 'Page MS' and then to 'Wait\_For\_Page\_Result'. + +Figure 59b: Procedure Active\_Info\_Retrieval\_VLR (sheet 2) + +![Flowchart for Procedure Authorize_MTRF_VLR. It starts with a start symbol, followed by a decision 'On-going MAP Update Location procedure'. If 'Yes', it goes to a process 'wait for MAP Update Location response and completion of Location_Update_Completion_VLR procedure'. If 'No', it goes to a decision diamond. The decision diamond has a condition box: '"LA Allowed" flag AND Confirmed by Radio Contact AND Data Confirmed by HLR AND MM LAI valid'. If 'False', it goes to 'Result:= Fail'. If 'True', it goes to 'Result:= Pass'. Both results lead to end symbols.](8307f6b04df072c9332f9987e034272c_img.jpg) + +**Procedure Authorize\_MTRF\_VLR** AMT\_VLR1(1) + +Procedure in the VLR +to authorize an MT Roaming +Forwarding request received +in Provide Roaming Number +from old VLR + +``` +graph TD; Start([ ] --> Decision1{On-going MAP Update Location procedure}; Decision1 -- Yes --> Process[wait for MAP Update Location response and completion of Location_Update_Completion_VLR procedure]; Process --> Decision2{ }; Decision1 -- No --> Decision2; Decision2 -- False --> ResultFail[Result:= Fail]; Decision2 -- True --> ResultPass[Result:= Pass]; ResultFail --> End1([ ]); ResultPass --> End2([ ]); Condition[""LA Allowed" flag AND +Confirmed by Radio Contact AND +Data Confirmed by HLR AND +MM LAI valid"] -.-> Decision2; +``` + +Flowchart for Procedure Authorize\_MTRF\_VLR. It starts with a start symbol, followed by a decision 'On-going MAP Update Location procedure'. If 'Yes', it goes to a process 'wait for MAP Update Location response and completion of Location\_Update\_Completion\_VLR procedure'. If 'No', it goes to a decision diamond. The decision diamond has a condition box: '"LA Allowed" flag AND Confirmed by Radio Contact AND Data Confirmed by HLR AND MM LAI valid'. If 'False', it goes to 'Result:= Fail'. If 'True', it goes to 'Result:= Pass'. Both results lead to end symbols. + +Figure 59b: Procedure Authorize\_MTRF\_VLR + +### 7.2.4 Functional requirements of MSC + +#### 7.2.4.1 Process Prepaging\_MSC + +#### 7.2.4.2 Procedure Prepaging\_Page\_MS\_MSC + +The test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network. + +The test "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call. + +The signal input "MS connection established" indicates that the MS has responded to paging, or sent a CM service request for anything other than a circuit-switched call, or completed the location registration procedure. + +#### 7.2.4.3 Prepaging\_Search\_For\_MS\_MSC + +The test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network. + +The test "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call. + +The signal input "MS connection established" indicates that the MS has responded to paging, or sent a CM service request for anything other than a circuit-switched call, or completed the location registration procedure. + +#### 7.2.4.4 Process OSI\_MSC + +If the MS is engaged on a circuit-switched call, the state is busy, otherwise assumed idle. + +#### 7.2.4.5 Process RCL\_MSC + +This process runs when the MSC receives a Page MS message or a Search for MS message with a Page type indicating Active Info Retrieval. + +#### 7.2.4.6 Procedure Active\_Info\_Retrieval\_Page\_MSC + +The test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network. + +The test "GSM Access" takes the "Yes" exit if the MS is using a GSM radio access to communicate with the network. + +The test "Report on change of service area?" takes the "Yes" exit if the MSC has performed the Location Reporting Control procedure (see 3GPP TS 25.413 [27]) with the Request Type IE set to "Change of service area". + +If the test "Report on change of service area?" takes the "No" exit the MSC shall perform a Location Reporting Control procedure with the Request Type IE set to "Direct". + +#### 7.2.4.7 Procedure Active\_Info\_Retrieval\_Search\_MSC + +The test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network. + +The test "GSM Access" takes the "Yes" exit if the MS is using a GSM radio access to communicate with the network. + +The test "Report on change of service area?" takes the "Yes" exit if the MSC has performed the Location Reporting Control procedure (see 3GPP TS 25.413 [26]) with the Request Type IE set to "Change of service area". + +If the test "Report on change of service area?" takes the "No" exit the MSC shall perform a Location Reporting Control procedure with the Request Type IE set to "Direct". + +#### 7.2.4.8 Procedure Retrieve\_IMEI\_If\_Required + +If the IMEI is retrieved using an existing connection between the MS and the network (as opposed to a connection which has been set up for active information retrieval), the Release transaction signal is relayed to the MSC process which is supervising the existing connection. + +![State transition diagram for Process Prepage_MSC. The process starts at an Idle state and branches into two parallel paths: 'Page MS' and 'Search for MS'. Both paths lead to 'Prepaging' messages and then to 'Result=Pass?' decision diamonds. If 'No', the process returns to Idle. If 'Yes', both paths converge to 'Process_Access_Request_MSC'. From there, another 'Result=Pass?' decision follows. If 'No', the process returns to Idle. If 'Yes', it proceeds to 'Start radio guard timer' and then 'Wait_For_Call_Arrival'. From 'Wait_For_Call_Arrival', three outcomes are possible: 'Call arrived' (leading to 'Stop radio guard timer'), 'Radio guard timer expired' (leading to 'Release transaction' and an 'Internal' state), and 'Release transaction' (leading to 'BSS released the radio resource'). All three outcomes lead to 'Radio connection released' and finally back to the Idle state.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +### Process Prepage\_MSC + +PP\_MSC1(1) + +``` +stateDiagram-v2 + [*] --> Idle + Idle --> Page_MS : Page MS + Idle --> Search_for_MS : Search for MS + Page_MS --> Prepaging_Page_MS_MSC : Prepaging_Page_MS_MSC + Search_for_MS --> Prepaging_Search_for_MS_MSC : Prepaging_Search_for_MS_MSC + Prepaging_Page_MS_MSC --> Result_Pass_1{Result=Pass?} + Prepaging_Search_for_MS_MSC --> Result_Pass_2{Result=Pass?} + Result_Pass_1 -- No --> Idle + Result_Pass_1 -- Yes --> Process_Access_Request_MSC + Result_Pass_2 -- No --> Idle + Result_Pass_2 -- Yes --> Process_Access_Request_MSC + Process_Access_Request_MSC --> Result_Pass_3{Result=Pass?} + Result_Pass_3 -- No --> Idle + Result_Pass_3 -- Yes --> Start_radio_guard_timer : Start radio guard timer + Start_radio_guard_timer --> Wait_For_Call_Arrival + Wait_For_Call_Arrival --> Call_arrived : Call arrived + Wait_For_Call_Arrival --> Radio_guard_timer_expired : Radio guard timer expired + Wait_For_Call_Arrival --> Release_transaction : Release transaction + Radio_guard_timer_expired --> Internal + Call_arrived --> Stop_radio_guard_timer : Stop radio guard timer + Stop_radio_guard_timer --> Radio_connection_released + Radio_guard_timer_expired --> Release_transaction + Release_transaction --> BSS_released_the_radio_resource : BSS released the radio resource + BSS_released_the_radio_resource --> Radio_connection_released + Radio_connection_released --> Idle +``` + +Process in the MSC to handle a pre-paging request + +Signals to/from the left are to/from the VLR; signals to the right are to the BSS + +State transition diagram for Process Prepage\_MSC. The process starts at an Idle state and branches into two parallel paths: 'Page MS' and 'Search for MS'. Both paths lead to 'Prepaging' messages and then to 'Result=Pass?' decision diamonds. If 'No', the process returns to Idle. If 'Yes', both paths converge to 'Process\_Access\_Request\_MSC'. From there, another 'Result=Pass?' decision follows. If 'No', the process returns to Idle. If 'Yes', it proceeds to 'Start radio guard timer' and then 'Wait\_For\_Call\_Arrival'. From 'Wait\_For\_Call\_Arrival', three outcomes are possible: 'Call arrived' (leading to 'Stop radio guard timer'), 'Radio guard timer expired' (leading to 'Release transaction' and an 'Internal' state), and 'Release transaction' (leading to 'BSS released the radio resource'). All three outcomes lead to 'Radio connection released' and finally back to the Idle state. + +Figure 60: Process Prepage\_MSC + +![Flowchart for Procedure Prepaging_Page_MS_MSC. The process starts with 'Location area ID known?'. If 'No', it sets a negative response 'Unknown LAI' and ends. If 'Yes', it checks 'MS connection exists?'. If 'No', it checks if 'Paging via SGSN possible?'. If 'Yes', it pages the MS in the specified location area and starts a timer. If 'No', it pages via SGSN and starts a timer. If 'Yes' to 'MS connection exists?', it checks 'MS busy?'. If 'Yes', it sets a negative response 'Busy Subscriber' and ends. If 'No', it sets access connection status and ends with 'Result:= Pass'. Both timers lead to a junction. From the junction, four paths emerge: 1) 'Cancel Location' leads to 'Set negative response: Location Cancelled', 'Page MS negative response', and 'Result:= Fail'. 2) 'MS connection established' leads to 'Set access connection status' and 'Result:= Pass'. 3) 'Page response timer expired' leads to 'Set negative response: Absent Subscriber', 'Page MS negative response', and 'Result:= Fail'. 4) 'CM Service Request' (for circuit-switched call) leads to 'CM Service Request' (to process OCH_MSC), 'Set negative response: Busy Subscriber (NDUB)', 'Page MS negative response', and 'Result:= Fail'. All final results lead to an end junction.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +**Procedure Prepaging\_Page\_MS\_MSC** PPPMS\_M1(1) + +*Procedure in the MSC to page an MS in a specified location area* + +*Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise* + +``` +graph TD; Start([Start]) --> LAI{Location area ID known?}; LAI -- No --> NR1[Set negative response: Unknown LAI]; NR1 --> End1(( )); LAI -- Yes --> Conn{MS connection exists?}; Conn -- No --> Pgsn{Paging via SGSN possible?}; Pgsn -- No --> Page[Page]; Pgsn -- Yes --> PgsnPage[Page MS via SGSN]; Page --> StartTimer[Start Page response timer]; PgsnPage --> StartTimer; StartTimer --> Wait[Wait_For_Page_Response]; Conn -- Yes --> Busy{MS busy?}; Busy -- Yes --> NR2[Set negative response: Busy Subscriber]; Busy -- No --> Status[Set access connection status]; Status --> ResultPass1[Result:= Pass]; ResultPass1 --> End2(( )); Wait --> Junction(( )); Junction --> Cancel[Cancel Location]; Junction --> ConnEst[MS connection established]; Junction --> TimerExp[Page response timer expired]; Junction --> CMReq[CM Service Request]; Cancel --> NR3[Set negative response: Location Cancelled]; NR3 --> PageNeg[Page MS negative response]; PageNeg --> ResultFail1[Result:= Fail]; ResultFail1 --> End3(( )); ConnEst --> Status2[Set access connection status]; Status2 --> ResultPass2[Result:= Pass]; ResultPass2 --> End4(( )); TimerExp --> NR4[Set negative response: Absent Subscriber]; NR4 --> PageNeg2[Page MS negative response]; PageNeg2 --> ResultFail2[Result:= Fail]; ResultFail2 --> End5(( )); CMReq -.-> Note1[For circuit-switched call]; CMReq --> CMReq2[CM Service Request]; CMReq2 -.-> Note2[To process OCH_MSC]; CMReq2 --> NR5[Set negative response: Busy Subscriber (NDUB)]; NR5 --> PageNeg3[Page MS negative response]; PageNeg3 --> ResultFail3[Result:= Fail]; ResultFail3 --> End6(( )); +``` + +Flowchart for Procedure Prepaging\_Page\_MS\_MSC. The process starts with 'Location area ID known?'. If 'No', it sets a negative response 'Unknown LAI' and ends. If 'Yes', it checks 'MS connection exists?'. If 'No', it checks if 'Paging via SGSN possible?'. If 'Yes', it pages the MS in the specified location area and starts a timer. If 'No', it pages via SGSN and starts a timer. If 'Yes' to 'MS connection exists?', it checks 'MS busy?'. If 'Yes', it sets a negative response 'Busy Subscriber' and ends. If 'No', it sets access connection status and ends with 'Result:= Pass'. Both timers lead to a junction. From the junction, four paths emerge: 1) 'Cancel Location' leads to 'Set negative response: Location Cancelled', 'Page MS negative response', and 'Result:= Fail'. 2) 'MS connection established' leads to 'Set access connection status' and 'Result:= Pass'. 3) 'Page response timer expired' leads to 'Set negative response: Absent Subscriber', 'Page MS negative response', and 'Result:= Fail'. 4) 'CM Service Request' (for circuit-switched call) leads to 'CM Service Request' (to process OCH\_MSC), 'Set negative response: Busy Subscriber (NDUB)', 'Page MS negative response', and 'Result:= Fail'. All final results lead to an end junction. + +Figure 61: Procedure Prepaging\_Page\_MS\_MSC + +![Flowchart for Procedure Prepaging_Search_For_MS_MSC. The process starts with a decision 'MS connection exists?'. If 'Yes', it goes to 'MS busy?'. If 'Yes' to 'MS busy?', it sets a negative response 'Busy Subscriber' and results in 'Result:= Fail'. If 'No' to 'MS busy?', it sets access connection status and results in 'Result:= Pass'. If 'No' to 'MS connection exists?', it checks if 'Paging via SGSN possible?'. If 'Yes', it pages via SGSN, then pages in all location areas, starts a timer, and waits for a response. If 'No' to 'Paging via SGSN possible?', it directly pages in all location areas. Both paths lead to a decision 'MS connection established'. If 'Yes', it sets access connection status and results in 'Result:= Pass'. If 'No', it checks if 'Page response timer expired'. If 'Yes', it sets a negative response 'Absent Subscriber', pages a negative response, and results in 'Result:= Fail'. If 'No', it sends a 'CM Service Request' for circuit-switched calls and another 'CM Service Request' to process OCH_MSC. Both lead to setting a negative response 'Busy Subscriber (NDUB)', paging a negative response, and resulting in 'Result:= Fail'.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +**Procedure Prepaging\_Search\_For\_MS\_MSC** PPSMS\_M1(1) + +Procedure in the MSC to page an MS in all location areas + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR + +Paging via SGSN possible? + +In all location areas or in PgA if PgA received and supported + +``` + +graph TD + Start([Start]) --> MS_Exists{MS connection exists?} + MS_Exists -- Yes --> MS_Busy{MS busy?} + MS_Exists -- No --> Paging_SGSN{Paging via SGSN possible?} + MS_Busy -- Yes --> Set_Neg_Resp_Busy[Set negative response: Busy Subscriber] + Set_Neg_Resp_Busy --> Page_Neg_Resp[Page MS negative response] + Page_Neg_Resp --> Result_Fail_1[Result:= Fail] + MS_Busy -- No --> Set_Access_Status_1[Set access connection status] + Set_Access_Status_1 --> Result_Pass_1[Result:= Pass] + Paging_SGSN -- Yes --> Page_SGSN[Page MS via SGSN] + Page_SGSN --> Page[Page] + Paging_SGSN -- No --> Page + Page --> Start_Timer[Start Page response timer] + Start_Timer --> Wait_Response[Wait_For_Page_Response] + Wait_Response --> MS_Established{MS connection established} + MS_Established -- Yes --> Set_Access_Status_2[Set access connection status] + Set_Access_Status_2 --> Result_Pass_2[Result:= Pass] + MS_Established -- No --> Timer_Expired{Page response timer expired} + Timer_Expired -- Yes --> Set_Neg_Resp_Absent[Set negative response: Absent Subscriber] + Set_Neg_Resp_Absent --> Page_Neg_Resp_2[Page MS negative response] + Page_Neg_Resp_2 --> Result_Fail_2[Result:= Fail] + Timer_Expired -- No --> CM_SR_1{CM Service Request} + CM_SR_1 --> For_Circuit_Switched[For circuit-switched call] + CM_SR_1 --> CM_SR_2{CM Service Request} + CM_SR_2 --> To_OCH_MSC[To process OCH_MSC] + CM_SR_2 --> Set_Neg_Resp_NDUB[Set negative response: Busy Subscriber (NDUB)] + Set_Neg_Resp_NDUB --> Page_Neg_Resp_3[Page MS negative response] + Page_Neg_Resp_3 --> Result_Fail_3[Result:= Fail] + +``` + +Flowchart for Procedure Prepaging\_Search\_For\_MS\_MSC. The process starts with a decision 'MS connection exists?'. If 'Yes', it goes to 'MS busy?'. If 'Yes' to 'MS busy?', it sets a negative response 'Busy Subscriber' and results in 'Result:= Fail'. If 'No' to 'MS busy?', it sets access connection status and results in 'Result:= Pass'. If 'No' to 'MS connection exists?', it checks if 'Paging via SGSN possible?'. If 'Yes', it pages via SGSN, then pages in all location areas, starts a timer, and waits for a response. If 'No' to 'Paging via SGSN possible?', it directly pages in all location areas. Both paths lead to a decision 'MS connection established'. If 'Yes', it sets access connection status and results in 'Result:= Pass'. If 'No', it checks if 'Page response timer expired'. If 'Yes', it sets a negative response 'Absent Subscriber', pages a negative response, and results in 'Result:= Fail'. If 'No', it sends a 'CM Service Request' for circuit-switched calls and another 'CM Service Request' to process OCH\_MSC. Both lead to setting a negative response 'Busy Subscriber (NDUB)', paging a negative response, and resulting in 'Result:= Fail'. + +Figure 62: Procedure Prepaging\_Search\_For\_MS\_MSC + +![Flowchart for Process OSI_MSC. The flow starts at an oval, goes to an 'Idle' state (oval), then to 'Obtain Subscriber Info' (parallelogram), then to a decision 'Subscriber state requested?' (diamond). If 'Yes', it goes to 'Set subscriber state' (rectangle) and then to 'Obtain Subscriber Info ack' (parallelogram). If 'No', it bypasses 'Set subscriber state' and goes directly to 'Obtain Subscriber Info ack'. Finally, it returns to an 'Idle' state (oval).](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +### Process OSI\_MSC + +Process in the MSC to handle a request from the VLR for information on the subscriber's location and state + +### OSI\_MSC1(1) + +Signals to/from the left are to/from the VLR + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> OSI[Obtain Subscriber Info]; OSI --> Decision{Subscriber state requested?}; Decision -- Yes --> Set[Set subscriber state]; Set --> Ack[Obtain Subscriber Info ack]; Decision -- No --> Ack; Ack --> Idle2([Idle]); +``` + +Flowchart for Process OSI\_MSC. The flow starts at an oval, goes to an 'Idle' state (oval), then to 'Obtain Subscriber Info' (parallelogram), then to a decision 'Subscriber state requested?' (diamond). If 'Yes', it goes to 'Set subscriber state' (rectangle) and then to 'Obtain Subscriber Info ack' (parallelogram). If 'No', it bypasses 'Set subscriber state' and goes directly to 'Obtain Subscriber Info ack'. Finally, it returns to an 'Idle' state (oval). + +Figure 63: Process OSI\_MSC + +![Flowchart for Process AIR_MSC. It starts with an oval connector, leading to an 'Idle' state (oval). From 'Idle', it branches into two parallel paths: 'Search for MS' (diamond) followed by 'Active_Info_Retrieval_Search_MSC' (rectangle), and 'Page MS' (diamond) followed by 'Active_Info_Retrieval_Page_MSC' (rectangle). Both paths converge to a final 'Idle' state (oval).](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +### Process AIR\_MSC + +AIR\_MSC1(1) + +``` +graph TD; Start([ ]) --> Idle1([Idle]); Idle1 --> Search{Search for MS}; Idle1 --> Page{Page MS}; Search --> SearchProc[Active_Info_Retrieval_Search_MSC]; Page --> PageProc[Active_Info_Retrieval_Page_MSC]; SearchProc --> Idle2([Idle]); PageProc --> Idle2; +``` + +Process in the MSC to retrieve any one or more of the current location, MS classmark and IMEI of a subscriber + +Signals to/from the left are to/from the VLR + +Flowchart for Process AIR\_MSC. It starts with an oval connector, leading to an 'Idle' state (oval). From 'Idle', it branches into two parallel paths: 'Search for MS' (diamond) followed by 'Active\_Info\_Retrieval\_Search\_MSC' (rectangle), and 'Page MS' (diamond) followed by 'Active\_Info\_Retrieval\_Page\_MSC' (rectangle). Both paths converge to a final 'Idle' state (oval). + +Figure 64: Process AIR\_MSC + +![](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +Procedure Active\_Info\_Retrieval\_Page\_MSC +AIRP\_MSC1(2) + +Procedure in the MSC to page an MS in a specified location area for Active Location Retrieval + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` + + graph TD + Start([ ]) --> LA_Known{Location area ID +known?} + + LA_Known -- No --> Set_Neg_Unknown[Set negative +response: +Unknown LAI] + LA_Known -- Yes --> MS_Conn{MS +connection +exists?} + + MS_Conn -- Yes --> Ret_IMEI_1[[Retrieve_ +IMEI_If_ +Required]] + MS_Conn -- No --> Paging_SGSN{Paging via +SGSN possible?} + + Paging_SGSN -- Yes --> Page_SGSN[/Page MS +via SGSN/] + Paging_SGSN -- No --> Page_In[/Page/] + In_Spec_Loc([In specified +location area]) --> Page_In + + Page_SGSN --> Start_Timer[Start Page +response +timer] + Page_In --> Start_Timer + + Start_Timer --> Wait_Page_Resp[[Wait_For_ +Page_ +Response]] + + Wait_Page_Resp --> Timer_Exp[/Page response +timer +expired/] + Wait_Page_Resp --> MS_Estab[/MS +connection +established/] + Wait_Page_Resp --> CM_Req[/CM Service +Request/] + + Timer_Exp --> Set_Neg_Absent[Set negative +response: +Absent +subscriber] + Set_Neg_Absent --> Page_Neg_Resp[/Page MS +negative +response/] + Page_Neg_Resp --> End1((X)) + + MS_Estab --> Ret_IMEI_2[[Retrieve_ +IMEI_If_ +Required]] + Ret_IMEI_2 --> Release[Release +transaction] + Release --> Page_Ack_1[/Page MS +ack/] + Page_Ack_1 --> End2((X)) + + CM_Req --> CM_Req_Proc{CM Service +Request} + CM_Req_Proc -- For circuit-switched call --> Ret_IMEI_3[[Retrieve_ +IMEI_If_ +Required]] + CM_Req_Proc -- To process OCH_MSC --> Ret_IMEI_3 + Ret_IMEI_3 --> Page_Ack_2[/Page MS +ack/] + Page_Ack_2 --> End3((X)) + + Ret_IMEI_1 --> GSM_Access{GSM +Access?} + GSM_Access -- Yes --> Set_Neg_Unknown + GSM_Access -- No --> Loc_Req{Location +info +requested?} + + Loc_Req -- No --> Page_Ack_3[/Page MS +ack/] + Loc_Req -- Yes --> Report_Change{Report on +change of +service area?} + + Report_Change -- Yes --> Set_Neg_Unknown + Report_Change -- No --> Loc_Rep_Ctrl[/Location +Reporting +Control/] + + Loc_Rep_Ctrl --> Wait_Loc_Rep[[Wait_For_ +Location_ +Report]] + Wait_Loc_Rep --> Loc_Rep[/Location +Report/] + Loc_Rep --> Loc_Info_Assign[Location info:= +Received +location info] + Loc_Info_Assign --> Page_Ack_3 + Page_Ack_3 --> End4((X)) + + Set_Neg_Unknown --> Page_Neg_Resp_2[/Page MS +negative +response/] + Page_Neg_Resp_2 --> End5((X)) + +``` + +**Figure 65: Procedure Active\_Info\_Retrieval\_Page\_MSC** + +![Flowchart for Procedure Active_Info_Retrieval_Search_MSC. The process starts with a decision 'MS connection exists?'. If 'Yes', it goes to 'Retrieve_IMEI_If_Required'. If 'No', it goes to 'Paging via SGSN possible?'. If 'Yes' to 'Paging via SGSN possible?', it goes to 'Search for MS via SGSN'. If 'No', it goes to 'Page' (with a note 'In all location areas'). Both 'Search for MS via SGSN' and 'Page' lead to 'Start Page response timer'. From 'Start Page response timer', it goes to 'Wait_For_Page_Response'. From 'Wait_For_Page_Response', it branches into three paths: 1) 'Page response timer expired' leads to 'Set negative response: Absent subscriber' then 'Search for MS negative response'. 2) 'MS connection established' leads to 'Retrieve_IMEI_If_Required' then 'Release transaction' then 'Search for MS ack'. 3) 'CM Service Request' (for circuit-switched call) or 'CM Service Request' (to process OCH_MSC) leads to 'Retrieve_IMEI_If_Required' then 'Search for MS ack'. All three 'Search' paths lead to a circle with an 'X'. The 'Retrieve_IMEI_If_Required' path from the first decision leads to 'GSM Access?'. If 'Yes', it goes to 'Search for MS ack'. If 'No', it goes to 'Location info requested?'. If 'Yes' to 'Location info requested?', it goes to 'Report on change of service area?'. If 'Yes' to 'Report on change of service area?', it goes to 'Search for MS ack'. If 'No' to 'Report on change of service area?', it goes to 'Location Reporting Control' then 'Wait_For_Location_Report' then 'Location Report' then 'Location info:= Received location info' then 'Search for MS ack'. If 'No' to 'Location info requested?', it also goes to 'Search for MS ack'.](26d664119ad25250780f554633444e54_img.jpg) + +### Procedure Active\_Info\_Retrieval\_Search\_MSC + +AIRS\_MSC1(1) + +Procedure in the MSC to page an MS in all location areas for Active Location Retrieval + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; Start([ ]) --> D1{MS connection exists?}; D1 -- Yes --> P1[Retrieve_IMEI_If_Required]; D1 -- No --> D2{Paging via SGSN possible?}; D2 -- Yes --> P2[Search for MS via SGSN]; D2 -- No --> P3[Page]; Note1[In all location areas] --- P3; P2 --> T1[Start Page response timer]; P3 --> T1; T1 --> W1([Wait_For_Page_Response]); W1 --> D3{ }; D3 -- "Page response timer expired" --> N1[Set negative response: Absent subscriber]; N1 --> S1[Search for MS negative response]; S1 --> End1((X)); D3 -- "MS connection established" --> P4[Retrieve_IMEI_If_Required]; P4 --> R1[Release transaction]; R1 --> S2[Search for MS ack]; S2 --> End2((X)); D3 -- "CM Service Request" --> Note2[For circuit-switched call]; D3 -- "CM Service Request" --> Note3[To process OCH_MSC]; Note2 --> P5[Retrieve_IMEI_If_Required]; Note3 --> P5; P5 --> S3[Search for MS ack]; S3 --> End3((X)); P1 --> D4{GSM Access?}; D4 -- Yes --> S4[Search for MS ack]; D4 -- No --> D5{Location info requested?}; D5 -- Yes --> D6{Report on change of service area?}; D6 -- Yes --> S4; D6 -- No --> L1[Location Reporting Control]; L1 --> W2([Wait_For_Location_Report]); W2 --> L2[Location Report]; L2 --> L3[Location info:= Received location info]; L3 --> S4; D5 -- No --> S4; +``` + +Flowchart for Procedure Active\_Info\_Retrieval\_Search\_MSC. The process starts with a decision 'MS connection exists?'. If 'Yes', it goes to 'Retrieve\_IMEI\_If\_Required'. If 'No', it goes to 'Paging via SGSN possible?'. If 'Yes' to 'Paging via SGSN possible?', it goes to 'Search for MS via SGSN'. If 'No', it goes to 'Page' (with a note 'In all location areas'). Both 'Search for MS via SGSN' and 'Page' lead to 'Start Page response timer'. From 'Start Page response timer', it goes to 'Wait\_For\_Page\_Response'. From 'Wait\_For\_Page\_Response', it branches into three paths: 1) 'Page response timer expired' leads to 'Set negative response: Absent subscriber' then 'Search for MS negative response'. 2) 'MS connection established' leads to 'Retrieve\_IMEI\_If\_Required' then 'Release transaction' then 'Search for MS ack'. 3) 'CM Service Request' (for circuit-switched call) or 'CM Service Request' (to process OCH\_MSC) leads to 'Retrieve\_IMEI\_If\_Required' then 'Search for MS ack'. All three 'Search' paths lead to a circle with an 'X'. The 'Retrieve\_IMEI\_If\_Required' path from the first decision leads to 'GSM Access?'. If 'Yes', it goes to 'Search for MS ack'. If 'No', it goes to 'Location info requested?'. If 'Yes' to 'Location info requested?', it goes to 'Report on change of service area?'. If 'Yes' to 'Report on change of service area?', it goes to 'Search for MS ack'. If 'No' to 'Report on change of service area?', it goes to 'Location Reporting Control' then 'Wait\_For\_Location\_Report' then 'Location Report' then 'Location info:= Received location info' then 'Search for MS ack'. If 'No' to 'Location info requested?', it also goes to 'Search for MS ack'. + +Figure 66: Procedure Active\_Info\_Retrieval\_Search\_MSC + +![Flowchart for Procedure Retrieve_IMEI_If_Required. It starts with a connector, leading to a decision 'IMEI requested?'. If 'No', it goes to an exit connector. If 'Yes', it goes to 'Send IMEI', then 'Wait_For_IMEI'. From 'Wait_For_IMEI', it branches into two parallel paths: one for 'IMEI' (receiving) followed by 'IMEI:= Received IMEI', and another for 'Release transaction'. Both paths converge to a final connector. A note indicates signals are to/from the BSS.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +**Procedure Retrieve\_IMEI\_If\_Required** RIIR1(1) + +*Procedure in the MSC to retrieve the IMEI of the MS if requested by the VLR* + +*Signals to/from the left are to/from the BSS* + +``` +graph TD; Start([ ]) --> Decision{IMEI requested?}; Decision -- No --> Exit1(( )); Decision -- Yes --> SendIMEI[Send IMEI]; SendIMEI --> WaitIMEI([Wait_For_IMEI]); WaitIMEI --> IMEI_In[/IMEI/]; WaitIMEI --> Release1[/Release transaction/]; IMEI_In --> IMEI_Assign[IMEI:= Received IMEI]; Release1 --> Release2[/Release transaction/]; Release2 --> ToSupervising[To supervising process, if required]; IMEI_Assign --> Exit2(( )); Release2 --> Exit2 +``` + +Flowchart for Procedure Retrieve\_IMEI\_If\_Required. It starts with a connector, leading to a decision 'IMEI requested?'. If 'No', it goes to an exit connector. If 'Yes', it goes to 'Send IMEI', then 'Wait\_For\_IMEI'. From 'Wait\_For\_IMEI', it branches into two parallel paths: one for 'IMEI' (receiving) followed by 'IMEI:= Received IMEI', and another for 'Release transaction'. Both paths converge to a final connector. A note indicates signals are to/from the BSS. + +Figure 66bis: Procedure Retrieve\_IMEI\_If\_Required + +## 7.3 MT call + +### 7.3.1 Functional requirements of serving MSC + +#### 7.3.1.1 Process ICH\_MSC + +Sheet 1: the task "Release Resources" refers to any resources that may have been allocated for the call due to Pre-Paging. + +Sheet 1: the rules for converting the ISDN BC/LLC/HLC to a bearer service or teleservice are specified in 3GPP TS 29.007 [30]. + +Sheet 1: the task "Store UUS information (if received)" is executed only if the VMSC supports UUS. + +Sheet 1: the variables TCH allocated, ACM sent, Answer sent and Network connect sent are global data, accessible to the procedures Establish\_Terminating\_TCH\_If\_Required, Send\_ACM\_If\_Required, Send\_Answer\_If\_Required and Send\_Network\_Connect\_If\_Required. + +Sheet 1: the variables UUS result sent, UUS1 implicit active, UUS1 explicit active, UUS2 active, UUS3 active and UUS CF interaction are specific to UUS. They are accessible to all UUS specific procedures. + +Sheet 1: the handling starting with the input signal "Continue CAMEL handling" is specific to CAMEL phase 3 or later. If the VMSC does not support CAMEL phase 3 or later, this signal will not be received from the VLR. + +Sheet 1: the procedure CAMEL\_ICH\_MSC\_INIT is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 1: The variable "On\_Hold" is used only if the VMSC supports Call Hold. + +Sheet 1, sheet 4, sheet 9: the process CAMEL\_ICH\_LEG1\_MSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 2: the procedure Process\_Access\_Request\_MSC is specified in subclause 7.1.1.2. + +Sheet 2: the signal input Complete Call will be received in the state Wait\_For\_Page\_Request only if the MSC/VLR supports pre-paging. + +Sheet 2, sheet 3: the suggested mapping from values of the Send Info For Incoming Call negative response information element to values of the ISUP release cause (see ITU-T Recommendation Q.850 [37]) is shown in table 2. The mapping used is a matter for the network operator, depending on the telephony signalling system used. + +**Table 2: Suggested mapping of Send Info For Incoming Call (SIFIC) negative responses to ISUP release causes** + +| SIFIC negative response | ISUP release cause number | ISUP release cause name | +|----------------------------------------------------|----------------------------------|------------------------------------| +| Absent subscriber | 20 | Subscriber absent | +| Busy subscriber | 17 | User busy | +| CUG reject (Called party SS interaction violation) | 21 | Call rejected | +| Forwarding violation | 21 | Call rejected | +| Impossible call completion | 111 | Protocol error, unspecified | +| No subscriber reply | 19 | No answer from user (user alerted) | +| System failure | 111 | Protocol error, unspecified | +| Unallocated roaming number | 111 | Protocol error, unspecified | + +Sheet 2, sheet 3, sheet 6, sheet 8, sheet 10, sheet 12: the procedure CAMEL\_MT\_GMSC\_DISC4 is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 3 or later, processing continues from the "No" exit of the test "Result=Reconnect?". + +Sheet 2, sheet 5, sheet 8, sheet 10, sheet 11, sheet 12: the procedure CAMEL\_MT\_GMSC\_DISC6 is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 3: the procedure CAMEL\_MT\_GMSC\_DISC5 is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 3 or later, processing continues from the "No" exit of the test "Result=Reconnect?". + +Sheet 3: the procedure CD\_Reject is specific to Call Deflection; it is specified in 3GPP TS 23.072 [11]. + +Sheet 3: the procedure Process\_Call\_Waiting is specific to Call Waiting; it is specified in 3GPP TS 23.083 [16]. + +Sheet 3: the task "Store CW treatment indicator for this call if received in SII2" is executed only if the VMSC supports CAMEL phase 3 or later. + +Sheet 3: if the VMSC does not support CAMEL phase 3 or later, the procedure Complete\_Call\_In\_MSC and the procedure Process\_Call\_Waiting will not return a "Reconnect" result. + +Sheet 3: the processing in the branch starting with the input signal "Process Call Waiting" is specific to Call Wait. If the VMSC does not support Call Waiting, this signal will not be received from the VLR. + +Sheet 3, sheet 10: the procedure CCBS\_Set\_Diagnostic\_For\_Release is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 3, sheet 5, sheet 6, sheet 11, sheet 12, sheet 13: the procedure CCBS\_Check\_Last\_Call is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 3: the procedure UUS\_ICH\_Check\_Support is specific to UUS; it is specified in 3GPP TS 23.087 [20]. + +Sheet 4: the procedure CAMEL\_ICH\_LEG2\_MSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 9: the procedure CAMEL\_ICH\_LEG2\_CF\_MSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 5: the procedure CAMEL\_Check\_ORLCF\_VMSC is specific to CAMEL phase 2 or later; it is specified in 3GPP TS 23.078 [12]. + +- If the VLR does not support CAMEL or no CAMEL information is available for the subscriber, then ORLCF may take place ('ORLCF' result from CAMEL\_Check\_ORLCF\_VMSC). +- If CAMEL information is available for the subscriber and the GMSC supports the required CAMEL phase, then ORLCF may take place. The Resume Call Handling request shall include the relevant CAMEL information ('ORLCF' result from CAMEL\_Check\_ORLCF\_VMSC). +- If CAMEL information is available for the subscriber but the GMSC does not support the required CAMEL phase, then ORLCF shall not take place ('VMSCCF' result from CAMEL\_Check\_ORLCF\_VMSC). + +Sheet 5: the procedure Handle\_ORLCF\_VMSC is specific to Support of Optimal Routeing. It is specified in 3GPP TS 23.079 [13]. If the VMSC does not support Optimal Routeing, processing continues from the "Continue" exit of the test "Result?". + +Sheet 5, sheet 6, sheet 11: the procedures CD\_Failure and CD\_Success are specific to Call Deflection; they are specified in 3GPP TS 23.072 [11]. + +Sheet 5: If MT Roaming Forwarding is supported and the MT Roaming Forwarding Indicator is received from the VLR, the MSC stops any on-going Camel transaction. + +Sheet 6: the procedure CAMEL\_MT\_VMSC\_Notify\_CF is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 6: If the VMSC does not support CAMEL phase 3 or later, processing starts with the possible call of the procedure CCBS\_Check\_Last\_Call. + +Sheet 6: The task "set redirection information" includes the mapping of the MSISDN parameter received in the Send Info For Incoming Call ack message to the redirecting number of the IAM message and the setting of the presentation indicator of the redirecting number of the IAM message according to the value of the Redirecting presentation parameter received in the Send Info For Incoming Call ack message. + +Sheet 6: it is an operator option whether to send an Address Complete message if the VLR returns forwarding information. If the VMSC sends an Address Complete message, it shall include the called party's status field of the Backward call indicator set to "no indication". + +Sheet 6, sheet 8: the procedure Send\_ACM\_If\_Required is specified in subclause 7.2.1.3. + +Sheet 6: the procedure Activate\_CF\_Process is specified in subclause 7.2.1.7. + +Sheet 6: the procedure UUS\_ICH\_Set\_Info\_In\_IAM is specific to UUS, it is specified in 3GPP TS 23.087 [20]. + +Sheet 6: the called party address sent in the IAM to the process MT\_CF\_MSC is the Forwarded-to number received in the Perform Call Forwarding ack. + +Sheet 6: the procedure CAMEL\_Store\_Destination\_Address is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 7: The processing on this sheet is specific to CAMEL phase 3 or later. If the VMSC does not support CAMEL phase 3 or later, the input signal Int\_Release Call will not be received. + +Sheet 8: the procedure CAMEL\_MT\_GMSC\_ANSWER is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 3 or later, processing continues from the "Pass" exit of the test "Result?". + +Sheet 8: the procedure Handle\_COLP\_Forwarding\_Interaction\_MSC is specified in subclause 7.2.1.6. + +Sheet 8: the procedure Send\_Answer\_If\_Required is specified in subclause 7.2.1.4. + +Sheet 8: the procedure Send\_Network\_Connect\_If\_Required is specified in subclause 7.2.1.5. + +Sheet 8: the procedure CAMEL\_MT\_MSC\_ALERTING is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 4 or later, processing continues from the "Pass" exit of the test "Result?". + +Sheet 10: the procedure CCBS\_MT\_MSC\_Check\_Forwarding is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 11: the processing on this sheet is specific to CAMEL phase 3 or later. If the VMSC does not support CAMEL phase 3 or later, the input signal Send Info For MT Reconnected Call ack will not be received. + +Sheet 11: the procedure Handle\_ORLCF\_VMSC is specific to OR; it is specified in 3GPP TS 23.079 [13]. If the VMSC does not support OR, processing continues from the "No" exit of the test "Result = Forwarding Failed?". + +Sheet 13, sheet 14: the procedure CAMEL\_MT\_GMSC\_DISC1 is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 13, sheet 14: the procedure CAMEL\_MT\_GMSC\_DISC2 is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 3 or later, processing continues from the "No" exit of the test "Result=Reconnect?". + +Sheet 13: the procedure UUS\_MSC\_Check\_UUS1\_UII is specific to UUS; it is specified in 3GPP TS 23.087 [20]. + +Sheet 14: after the VMSC has sent an IAM to the process MT\_CF\_MSC, it acts as a transparent relay for messages received from the GMSC and the process MT\_CF\_MSC. Any message other than Address Complete, Connect, Answer or Release causes no change of state in the process ICH\_MSC. + +Sheet 15: The processing on this sheet is specific to CAMEL phase 3 or later. If the VMSC does not support CAMEL phase 3 or later, the input signal Int\_Release Call will not be received. + +Sheet 16: the procedure Process\_Hold\_Request is specific to Call Hold; it is specified in 3GPP TS 23.083[16]. + +Sheet 16: the procedure Process\_Retrieve\_request is specific to Call\_Hold; it is specified in 3GPP TS 23.083[16]. + +#### 7.3.1.2 Procedure Page\_MS\_MSC + +Sheet 1: the test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network. + +Sheet 1: for an SMS or SS page, the test "Call still exists" takes the "Yes" exit if the SMS or SS transaction which led to the page still exists. + +Sheet 1: the test "SMS or SS page" is not required for the handling of circuit-switched calls, because the VLR will always use a page type of "circuit-switched call", but the more generalized procedure Page\_MS\_MSC is equally applicable to paging for SMS delivery or network-initiated SS procedures. + +Sheet 1: If the MSC supports the option to delay Mobile Terminating CM request during a location update procedure (see 3GPP TS 24.008 [13] section 4.5.1.3.1 Mobile Terminating CM Activity): + +If location update procedure is ongoing for the MS, + +If the "follow-on" indicator is received and MSC supports "follow-on" feature, the Page\_MS\_MSC procedure should return FAIL after sending Page MS negative response (cause Busy Subscriber) to VLR. + +Otherwise, the MSC should delay the launching of Page\_MS\_MSC procedure until the location update procedure ends. + +- If the result of location update is successful and location update is not through Gs interface, then Page\_MS\_MSC procedure returns with PASS. +- If the result of location update is successful and location update is through Gs interface, then Page\_MS\_MSC continues from the beginning of the procedure. +- If the result of location update is not successful, then the procedure should return FAIL after sending Page MS negative response (cause Absent Subscriber) to VLR. + +Sheet 2: the procedure Check\_MT\_Multicall\_MSC is specific to Multicall; it is specified in 3GPP TS 23.135 [25]. If the VMSC does not support Multicall, processing continues from the "Yes" exit of the test "Result=Not provisioned?". + +Sheet 2: the test "Call in set-up" takes the "Yes" exit if the call on which the MS is engaged has not reached the established phase (called party answer). + +Sheet 2: the test "Call waiting" takes the "Yes" exit if a waiting call has been offered to the subscriber but the outcome of offering the call has not been determined. + +Sheet 2: if there is one established call, the negative response Busy Subscriber (More calls possible) includes the basic service which applies for the established call. If there are two or more established calls (the Multicall case), the negative response Busy Subscriber (More calls possible) includes the basic service list which applies for the established calls (See 3GPP TS 23.135 [25]). + +Sheet 3: the signal input "MS connection established" indicates that the MS has responded to paging, or sent a CM service request for anything other than a circuit-switched call, or completed the location registration procedure. + +Sheet 4: A MSC not implementing the MT Roaming Retry feature and the MT Roaming Forwarding feature may not immediately stop paging upon receipt of a Cancel Location message. + +#### 7.3.1.3 Procedure Search\_For\_MS\_MSC + +Sheet 1: the test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network. + +Sheet 1: for an SMS or SS page, the test "Call still exists" takes the "Yes" exit if the SMS or SS transaction which led to the page still exists. + +Sheet 1: the test "SMS or SS page" is not required for the handling of circuit-switched calls, because the VLR will always use a page type of "circuit-switched call", but the more generalized procedure Search\_For\_MS\_MSC is equally applicable to paging for SMS delivery or network-initiated SS procedures. + +Sheet 1: If the MSC supports the option to delay the Mobile Terminating CM request during a location update procedure (see 3GPP TS 24.008 [13] section 4.5.1.3.1 Mobile Terminating CM Activity): + +If location update procedure is ongoing for the MS, and if the "follow-on" indicator is received and the MSC supports the "follow-on" feature, the Search\_MS\_MSC procedure should return FAIL after sending Search MS negative response (cause Busy Subscriber) to VLR. + +Otherwise, the MSC should delay the launching of Search\_MS\_MSC procedure until location update procedure ends. + +- If the result of location update is successful and location update is not through Gs interface, then the Search\_MS\_MSC procedure returns with PASS. +- If the result of location update is successful and location update is through Gs interface, then the procedure continues from the beginning of the Page\_MS\_MSC procedure. +- If the result of the location update is not successful, then the procedure should return FAIL after sending the Search MS negative response (cause Absent Subscriber) to VLR. + +Sheet 2: the procedure Check\_MT\_Multicall\_MSC is specific to Multicall; it is specified in 3GPP TS 23.135 [25]. If the VMSC does not support Multicall, processing continues from the "Yes" exit of the test "Result=Not provisioned?". + +Sheet 2: the test "Call in set-up" takes the "Yes" exit if the call on which the MS is engaged has not reached the established phase (called party answer). + +Sheet 2: the test "Call waiting" takes the "Yes" exit if a waiting call has been offered to the subscriber but the outcome of offering the call has not been determined. + +Sheet 2: if there is one established call, the negative response Busy Subscriber (More calls possible) includes the basic service which applies for the established call. If there are two or more established calls (the Multicall case), the negative response Busy Subscriber (More calls possible) includes the basic service list which applies for the established calls (See 3GPP TS 23.135 [25]). + +Sheet 3: the signal input "MS connection established" indicates that the MS has responded to paging, or sent a CM service request for anything other than a circuit-switched call, or completed the location registration procedure. + +Sheet 4 : A MSC not implementing the MT Roaming Retry feature and the MT Roaming Forwarding feature may not immediately stop paging upon receipt of a Cancel Location message. + +#### 7.3.1.4 Procedure Complete\_Call\_In\_MSC + +Sheet 1: the procedure Set\_CLIP\_Info\_MSC is specific to CLIP. + +Sheet 1: the VMSC derives the PLMN bearer capability required for the call according to the rules defined in 3GPP TS 29.007 [30]. + +Sheet 1, sheet 2: the VMSC and the MS may negotiate the bearer capability to be used for the call by the exchange of information in the Set-up and Call Confirmed messages. + +Sheet 1: the procedure UUS\_ICH\_UUS1\_Implicit\_Active is specific to UUS, it is specified in 3GPP TS 23.087 [20]. + +Sheet 1: the procedure CCBS\_Report\_Not\_Idle is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 2: the procedure Establish\_Terminating\_TCH\_Multicall is specific to Multicall; it is specified in 3GPP TS 23.135 [25]. + +Sheet 2: the test "Result=Rejected?" can take the "Yes" exit only if the procedure Establish\_Terminating\_TCH\_Multicall was called. + +Sheet 2, sheet 3, sheet 4, sheet 5, sheet 6, sheet 7: the procedure CAMEL\_MT\_GMSC\_DISC4 is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 3 or later, processing continues from the "No" exit of the test "Result=Reconnect?". + +Sheet 2, sheet 3, sheet 6, sheet 9, sheet 10: the procedure CAMEL\_MT\_GMSC\_DISC6 is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 2, sheet 5, sheet 9: the procedure CCBS\_ICH\_MSC\_Report\_Failure is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 3, sheet 5: the procedure CCBS\_ICH\_MSC\_Report\_Success is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 3: the procedure CAMEL\_Start\_TNRy is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 3: the procedure CAMEL\_MT\_MSC\_ALERTING is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 4 or later, processing continues from the "Pass" exit of the test "Result?". + +Sheet 3, sheet 6: the procedure UUS\_ICH\_Check\_Support is specific to UUS, it is specified in 3GPP TS 23.087 [20]. If the VMSC does not support UUS, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 3: the task "UTU2Cnt:=0" is executed only if the VMSC supports UUS. + +Sheet 3: the procedure Send\_ACM\_If\_Required is specified in subclause 7.2.1.3. + +Sheet 3, sheet 6: the procedure Establish\_Terminating\_TCH\_Multicall is specific to Multicall; it is specified in 3GPP TS 23.135 [25]. If the VMSC does not support Multicall, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 4, sheet 7: the procedure Handle\_AoC\_MT\_MSC is specific to AoC. If the VMSC does not support AoC, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 4, sheet 7: the procedure CAMEL\_MT\_GMSC\_ANSWER is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 3 or later, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 4, sheet 7: the procedure Set\_COL\_Presentation\_Indicator\_MSC is specific to COLP. + +Sheet 4: the procedure Send\_Network\_Connect\_If\_Required is specified in subclause 7.2.1.5. + +Sheet 5, sheet 11: the processing in the branch starting with the input "CD Request" is specific to Call Deflection; if the VMSC does not support Call Deflection the input is discarded. + +Sheet 5, sheet 11: the procedure Handling\_CD\_MSC is specific to Call Deflection; it is specified in 3GPP TS 23.072 [11]. + +Sheet 6: the procedure CAMEL\_Stop\_TNRy is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 7: the procedure Send\_Answer\_If\_Required is specified in subclause 7.2.1.4. + +Sheet 8: the input signal "CAMEL TNRy expired" will be received only if the VMSC supports CAMEL phase 3 or later. + +Sheet 8, sheet 11: the procedure UUS\_ICH\_Check\_Forwarding is specific to UUS, it is specified in 3GPP TS 23.087 [20]. If the VMSC does not support UUS, processing continues from the "Yes" exit of the test "Result=Pass?". + +Sheet 9, sheet 10: the procedure UUS\_MSC\_Check\_UUS1\_UUI is specific to UUS; it is specified in 3GPP TS 23.087 [20]. + +Sheet 11: the procedures UUS\_MSC\_Check\_UUS2\_UUI\_to MS and UUS\_MSC\_Check\_UUS2\_UUI\_to NW are specific to UUS, they are specified in 3GPP TS 23.087 [20]. + +Sheet 11: the procedure CD\_UUS\_Interaction is specific to Call Deflection; it is specified in 3GPP TS 23.072 [11]. + +**7.3.1.5 Void** + +**7.3.1.6 Procedure Set\_CLIP\_Info\_MSC** + +The originating exchange may release the call or the MS may terminate the transaction with the network by sending a Release transaction message while a response is awaited from the process CLIP\_MAF002. The message is saved for processing after return from the procedure. + +**7.3.1.7 Void** + +**7.3.1.8 Procedure Establish\_Terminating\_TCH\_If\_Required** + +The procedure TCH\_Check is specified in subclause 7.1.1.14. + +**7.3.1.9 Procedure Handle\_AoC\_MT\_MSC** + +**7.3.1.10 Procedure Set\_COL\_Presentation\_Indicator\_MSC** + +The originating exchange may release the call or the MS may terminate the transaction with the network by sending a Release transaction message while a response is awaited from the process COLP\_MAF041. The message is saved for processing after return from the procedure. + +![State transition diagram for Process ICH_MSC. It starts at 'Idle' and branches based on incoming signals from GMSC: 'Release Resources' or 'Initial Address'. The 'Initial Address' path involves resource conversion, sending info for incoming call, waiting for a page request, and then handling CAMEL. The CAMEL handling leads to a 'Result?' decision with five outcomes: Leg1_only, Reconnect, MSRN, Aborted, and Fail. Each outcome leads to specific actions like setting status, sending info for reconnection, or releasing resources, eventually returning to 'Idle'.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC1(17) + +Process in the MSC to handle an incoming (MT) call + +Signals to/from the left are to/from the BSS; +signals to/from the right are to/from the VLR unless marked otherwise + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Release_Resources: From GMSC + Release_Resources --> Release_Resources + Release_Resources --> Release_MSRN + Release_MSRN --> Idle + + Idle --> Initial_Address: From GMSC + Initial_Address --> Convert_ISDN + Convert_ISDN --> Send_Info_Incoming_Call + Send_Info_Incoming_Call --> Wait_For_Page_Request + Wait_For_Page_Request --> Continue_CAMEL_Handling + Continue_CAMEL_Handling --> CAMEL_INIT + CAMEL_INIT --> Result? + Result? --> Leg1_only + Result? --> Reconnect + Result? --> MSRN + Result? --> Aborted + Result? --> Fail + + Leg1_only --> Leg1_status + Leg1_status --> CAMEL_LEG1_MSC + CAMEL_LEG1_MSC --> Idle + + Reconnect --> Send_Info_Reconnected_Call + Send_Info_Reconnected_Call --> Wait_For_Reconnected_Call_Result + Wait_For_Reconnected_Call_Result --> Idle + + MSRN --> Set_Suppress_VT_CSI + Set_Suppress_VT_CSI --> Send_Info_Incoming_Call + Send_Info_Incoming_Call --> Wait_For_Page_Request + Wait_For_Page_Request --> Idle + + Aborted --> Release + Fail --> Set_cause + Set_cause --> Release + Release --> Release_call_resources + Release_call_resources --> Idle + +``` + +**States and Transitions:** + +- Idle** (Initial state) + - Transition to **Release Resources** (From GMSC) → **Release Resources** → **Release MSRN** → **Idle** + - Transition to **Initial Address** (From GMSC) → **Convert ISDN BC/LLC/HLC** → **Send Info For Incoming Call** → **Wait For Page Request** → **Continue CAMEL Handling** → **CAMEL ICH\_MSC INIT** → **Result?** +- Result?** (Decision) + - Leg1\_only**: **Leg1\_status := Set-up** → **CAMEL ICH\_MSC LEG1\_MSC (Leg1\_Status)** → **Idle** + - Reconnect**: **Send Info For MT Reconnected Call** → **Wait For Reconnected Call Result** → **Idle** + - MSRN**: **Set Suppress VT-CSI** → **Send Info For Incoming Call** → **Wait For Page Request** → **Idle** + - Aborted**: **Release** → **Release call resources** → **Idle** + - Fail**: **Set cause** → **Release** → **Release call resources** → **Idle** + +**Notes:** + +- Convert ISDN BC/LLC/HLC** (if present) to bearer service/teleservice & CS BC; Store UUS information (if received) +- Wait For Page Request**: ACM sent:=False; Answer sent:=False; BOR:=False; Network connect sent:=False; TCH allocated:=False; UUS1 result sent:=False; UUS1 implicit active:=False; UUS1 explicit active:=False; UUS2 active:=False; UUS3 active:=False; UUS CF interaction:=False; Call answered := False; On\_Hold:=False +- CAMEL ICH\_MSC INIT**: See TS 23.078 +- See TS 23.078** (Note for Leg1\_only path) + +State transition diagram for Process ICH\_MSC. It starts at 'Idle' and branches based on incoming signals from GMSC: 'Release Resources' or 'Initial Address'. The 'Initial Address' path involves resource conversion, sending info for incoming call, waiting for a page request, and then handling CAMEL. The CAMEL handling leads to a 'Result?' decision with five outcomes: Leg1\_only, Reconnect, MSRN, Aborted, and Fail. Each outcome leads to specific actions like setting status, sending info for reconnection, or releasing resources, eventually returning to 'Idle'. + +Figure 67a: Process ICH\_MSC (sheet 1) + +![Flowchart for Process ICH_MSC (sheet 2).](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC2(17) + +Process in the MSC to handle an incoming (MT) call + +Signals to/from the left are to/from the GMSC; +signals to/from the right are to/from the VLR + +``` + + graph TD + Start([Wait_For_Page_Request]) + + %% Top Level Branches + Start --- B1[Send Info For Incoming Call negative response] + Start --- B2[Page MS] + Start --- B3[Send Info For Incoming Call Ack] + Start --- B4[Call is to be forwarded] + Start --- B5[Search For MS] + Start --- B6[Complete Call] + + %% Branch 1: Negative Response + B1 --> SetCause[Set cause] + SetCause --> DISC4_1[CAMEL_MT_GMSC_DISC4] + DISC4_1 --> RR1{Result= Reconnect?} + RR1 -- Yes --> SIRC[Send Info For MT Reconnected Call] + SIRC --> WRCR[Wait_For_Reconnected_Call_Result] + RR1 -- No --> Rel1[Release] + Rel1 --> RCR1[Release call resources] + RCR1 --> Idle1([Idle]) + Note1[See TS 23.078] -.-> Idle1 + + %% Branch 2: Page MS + B2 --> PMSC[Page MS_MSC] + PMSC --> RP1{Result= Pass?} + RP1 -- No --> RF1{Result= Fail?} + RF1 -- No --> DISC6_1[CAMEL_MT_GMSC_DISC6] + DISC6_1 --> RCR2[Release call resources] + RCR2 --> Idle2([Idle]) + Note2[See TS 23.078] -.-> DISC6_1 + RF1 -- Yes --> WFCR1([Wait_For_MT_Call_Result]) + RP1 -- Yes --> PAR[Process Access Request_MSC] + + %% Branch 3: Ack + B3 --> C1((1)) + + %% Branch 4: Forwarded + B4 --> PAR + + %% Branch 5: Search + B5 --> SFM[Search_For_MS_MSC] + SFM --> RP2{Result= Pass?} + RP2 -- Yes --> PAR + RP2 -- No --> RF2{Result= Fail?} + RF2 -- Yes --> WFCR2([Wait_For_MT_Call_Result]) + RF2 -- No --> DISC6_2[CAMEL_MT_GMSC_DISC6] + DISC6_2 --> RCR3[Release call resources] + RCR3 --> Idle3([Idle]) + Note3[See TS 23.078] -.-> Idle3 + + %% Branch 6: Complete + B6 --> C2((2)) + + %% Process Access Request Logic + PAR --> RP3{Result= Pass?} + RP3 -- Yes --> WFCR3([Wait_For_MT_Call_Result]) + RP3 -- No --> DISC4_2[CAMEL_MT_GMSC_DISC4] + DISC4_2 --> RR2{Result= Reconnect?} + RR2 -- Yes --> SIRC + RR2 -- No --> Rel2[Release] + Rel2 --> RCR4[Release call resources] + RCR4 --> Idle4([Idle]) + Note4[See TS 23.078] -.-> Idle4 + +``` + +Flowchart for Process ICH\_MSC (sheet 2). + +Figure 67b: Process ICH\_MSC (sheet 2) + +![Flowchart for Process ICH_MSC (sheet 3). The process starts with 'Wait_For_MT_Call_Result' leading to 'Complete Call' (connector 2). From 'Complete Call', it goes to 'Complete Call_In_MSC'. A decision 'Result= Pass?' follows. If 'No', it goes to 'Call setup failed' (To Subs_FSM). If 'Yes', it goes to 'Store CW Treatment indicator for this call if received in SII2', then 'Call answered := True', then 'Call established' (To Subs_FSM), which leads to connector 5. From connector 5, it goes to 'Wait_For_MT_Call_Result'. A decision 'Result= Fail?' follows. If 'Yes', it goes to 'Release transaction'. If 'No', it goes to 'Result= Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call', then 'Wait_For_Reconnected_Call_Result', then 'Release transaction'. If 'No', it goes to 'Release transaction'. From 'Release transaction', it goes to 'CCBS_Check_Last_Call' (See TS 23.093), then 'Release call resources', then 'Idle'. On the left side, 'Send Info For Incoming Call negative response' leads to 'CD_Reject' (See TS 23.072), 'CCBS_Set_Diagnostic_For_Release' (See TS 23.093), 'UUS_ICH_Check_Support' (See TS 23.087), 'Set cause' (To Subs_FSM), and 'Cause= No Subscriber Reply?'. If 'Yes', it goes to 'CAMEL_MT_GMSC_DISC4' (See TS 23.078). If 'No', it goes to 'Result= Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call', then 'Wait_For_Reconnected_Call_Result', then 'Release transaction'. If 'No', it goes to 'Release' (See TS 23.078). On the right side, 'Process Call Waiting' (See TS 23.083) leads to 'Process_Call_Waiting'. A decision 'Result= Pass?' follows. If 'No', it goes to 'Call setup failed' (To Subs_FSM). If 'Yes', it goes to 'Result= Fail?'. If 'Yes', it goes to 'Release transaction'. If 'No', it goes to 'Result= Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call', then 'Wait_For_Reconnected_Call_Result', then 'Release transaction'. If 'No', it goes to 'Release transaction'. A note indicates: 'Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR unless marked otherwise'.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +**Process ICH\_MSC** **ICH\_MSC3(17)** + +Process in the MSC +to handle an incoming (MT) call + +``` + +graph TD + Start([Wait_For_MT_Call_Result]) + Conn2((2)) --> CompleteCall[Complete Call] + CompleteCall --> CallIn[Complete Call_In_MSC] + CallIn --> Pass{Result= Pass?} + Pass -- No --> Fail1[Call setup failed] + Fail1 --> Subs1[To Subs_FSM] + Pass -- Yes --> CW[Store CW Treatment indicator for this call if received in SII2] + CW --> Answered[Call answered := True] + Answered --> Estab[Call established] + Estab --> Subs2[To Subs_FSM] + Estab --> Conn5((5)) + Conn5 --> WaitResult[Wait_For_MT_Call_Result] + WaitResult --> Fail2{Result= Fail?} + Fail2 -- Yes --> ReleaseTrans[Release transaction] + Fail2 -- No --> Reconnect{Result= Reconnect?} + Reconnect -- Yes --> ReconnCall[Send Info For MT Reconnected Call] + ReconnCall --> ReconnWait[Wait_For_Reconnected_Call_Result] + ReconnWait --> ReleaseTrans + Reconnect -- No --> ReleaseTrans + ReleaseTrans --> CCBS[CCBS_Check_Last_Call] + CCBS --> TS23093[See TS 23.093] + CCBS --> ReleaseRes[Release call resources] + ReleaseRes --> Idle([Idle]) + + Start --> CallNeg[Send Info For Incoming Call negative response] + CallNeg --> CD[CD_Reject] + CD --> TS23072[See TS 23.072] + CD --> CCBSRel[CCBS_Set_Diagnostic_For_Release] + CCBSRel --> TS23093_2[See TS 23.093] + CCBSRel --> UUS[UUS_ICH_Check_Support] + UUS --> TS23087[See TS 23.087] + UUS --> SetCause[Set cause] + SetCause --> Subs3[To Subs_FSM] + SetCause --> CauseNo{Cause= No Subscriber Reply?} + CauseNo -- Yes --> CAMEL4[CAMEL_MT_GMSC_DISC4] + CAMEL4 --> CAMEL5[CAMEL_MT_GMSC_DISC5] + CAMEL4 --> TS23078_1[See TS 23.078] + CAMEL5 --> TS23078_2[See TS 23.078] + CauseNo -- No --> Reconnect2{Result= Reconnect?} + Reconnect2 -- Yes --> ReconnCall2[Send Info For MT Reconnected Call] + ReconnCall2 --> ReconnWait2[Wait_For_Reconnected_Call_Result] + ReconnWait2 --> ReleaseTrans + Reconnect2 -- No --> Release[Release] + Release --> TS23078_3[See TS 23.078] + + Start --> CallWaiting[Process Call Waiting] + CallWaiting --> TS23083[See TS 23.083] + CallWaiting --> ProcessCallWaiting[Process_Call_Waiting] + ProcessCallWaiting --> Pass3{Result= Pass?} + Pass3 -- No --> Fail3[Call setup failed] + Fail3 --> Subs4[To Subs_FSM] + Pass3 -- Yes --> Fail3_2{Result= Fail?} + Fail3_2 -- Yes --> ReleaseTrans + Fail3_2 -- No --> Reconnect3{Result= Reconnect?} + Reconnect3 -- Yes --> ReconnCall3[Send Info For MT Reconnected Call] + ReconnCall3 --> ReconnWait3[Wait_For_Reconnected_Call_Result] + ReconnWait3 --> ReleaseTrans + Reconnect3 -- No --> ReleaseTrans + +``` + +Signals to/from the left are to/from the GMSC; +signals to/from the right are to/from the VLR +unless marked otherwise + +Flowchart for Process ICH\_MSC (sheet 3). The process starts with 'Wait\_For\_MT\_Call\_Result' leading to 'Complete Call' (connector 2). From 'Complete Call', it goes to 'Complete Call\_In\_MSC'. A decision 'Result= Pass?' follows. If 'No', it goes to 'Call setup failed' (To Subs\_FSM). If 'Yes', it goes to 'Store CW Treatment indicator for this call if received in SII2', then 'Call answered := True', then 'Call established' (To Subs\_FSM), which leads to connector 5. From connector 5, it goes to 'Wait\_For\_MT\_Call\_Result'. A decision 'Result= Fail?' follows. If 'Yes', it goes to 'Release transaction'. If 'No', it goes to 'Result= Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call', then 'Wait\_For\_Reconnected\_Call\_Result', then 'Release transaction'. If 'No', it goes to 'Release transaction'. From 'Release transaction', it goes to 'CCBS\_Check\_Last\_Call' (See TS 23.093), then 'Release call resources', then 'Idle'. On the left side, 'Send Info For Incoming Call negative response' leads to 'CD\_Reject' (See TS 23.072), 'CCBS\_Set\_Diagnostic\_For\_Release' (See TS 23.093), 'UUS\_ICH\_Check\_Support' (See TS 23.087), 'Set cause' (To Subs\_FSM), and 'Cause= No Subscriber Reply?'. If 'Yes', it goes to 'CAMEL\_MT\_GMSC\_DISC4' (See TS 23.078). If 'No', it goes to 'Result= Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call', then 'Wait\_For\_Reconnected\_Call\_Result', then 'Release transaction'. If 'No', it goes to 'Release' (See TS 23.078). On the right side, 'Process Call Waiting' (See TS 23.083) leads to 'Process\_Call\_Waiting'. A decision 'Result= Pass?' follows. If 'No', it goes to 'Call setup failed' (To Subs\_FSM). If 'Yes', it goes to 'Result= Fail?'. If 'Yes', it goes to 'Release transaction'. If 'No', it goes to 'Result= Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call', then 'Wait\_For\_Reconnected\_Call\_Result', then 'Release transaction'. If 'No', it goes to 'Release transaction'. A note indicates: 'Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR unless marked otherwise'. + +**Figure 67c: Process ICH\_MSC (sheet 3)** + +![Flowchart for Process ICH_MSC. It starts at node 5, checks if a CAMEL phase 4 or later control relationship exists. If 'Yes', it sets Leg1_status to Active, then calls CAMEL_ICH_LEG1_MSC (Leg1_Status) and CAMEL_ICH_LEG2_MSC (referencing TS 23.078), ending at Idle. If 'No', it goes to Wait_For_Clear.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +**Process ICH\_MSC** **ICH\_MSC4(17)** + +Process in the MSC +to handle an incoming (MT) call + +``` +graph TD; Node5((5)) --> Decision{CAMEL phase 4 or later control relationship exists?}; Decision -- Yes --> Leg1Status[Leg1_status := Active]; Leg1Status --> Leg1MSC[CAMEL_ICH_LEG1_MSC (Leg1_Status)]; Leg1MSC --> Leg2MSC[CAMEL_ICH_LEG2_MSC]; Leg2MSC --> Idle([Idle]); Decision -- No --> WaitForClear([Wait_For_Clear]); Note1[See TS 23.078] -.-> Leg1MSC; Note2[See TS 23.078] -.-> Leg2MSC; +``` + +Flowchart for Process ICH\_MSC. It starts at node 5, checks if a CAMEL phase 4 or later control relationship exists. If 'Yes', it sets Leg1\_status to Active, then calls CAMEL\_ICH\_LEG1\_MSC (Leg1\_Status) and CAMEL\_ICH\_LEG2\_MSC (referencing TS 23.078), ending at Idle. If 'No', it goes to Wait\_For\_Clear. + +**Figure 67d: Process ICH\_MSC (sheet 4)** + +![Flowchart for Process ICH_MSC (sheet 5). The process starts at connector 1, goes through Wait_For_MT_Call_Result, Send_Info_For_Incoming_Callack, and M_T_Roaming_Forwarding_supported. It branches based on 'yes' or 'No' for forwarding support. The 'yes' path goes through M_T_Roaming_Forwarding_Indicator_received, Initial_Address_Message_to_new_MSC, Wait_For_MTRF_ACM, Handle_ORLCF_VMSC, Wait_For_Release_From_GMSC, Release, CAMEL_MT_GMSC_DISC6, Release call resources, and Idle. The 'No' path goes through M_T_Roaming_Retry_supported, M_T_Roaming_Retry_Indicator_received, Handle_ORLCF_VMSC, Wait_For_Release_From_GMSC, Release, CAMEL_MT_GMSC_DISC6, CCBS_Check_Last_Call, Release call resources, and Idle. A VMSCCF block with CAMEL_Check_ORLCF_VMSC and VMSCCF_Result? decisions is also shown, leading to CD_Failure or CD_Success, and then to connector 3.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +**Process ICH\_MSC** **ICH\_MSC5(18)** + +Process in the MSC to handle an incoming (MT + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR + +``` +graph TD + 1((1)) --> WFCR[Wait_For_MT_Call_Result] + WFCR --> SIF[Send_Info_For_Incoming_Callack] + SIF --> MF[M_T_Roaming_Forwarding_supported] + MF -- yes --> MIRI[M_T_Roaming_Forwarding_Indicator_received] + MF -- No --> MRS[M_T_Roaming_Retry_supported] + MIRI -- Yes --> IAM[Initial_Address_Message_to_new_MSC] + MIRI -- No --> MF + IAM --> WFA[Wait_For_MTRF_ACM] + WFA --> H[Handle_ORLCF_VMSC] + H --> WRF[Wait_For_Release_From_GMSC] + WRF --> R1[Release] + R1 --> C1[CAMEL_MT_GMSC_DISC6] + C1 --> RC1[Release call resources] + RC1 --> I1[Idle] + MRS -- Yes --> MIRI2[M_T_Roaming_Retry_Indicator_received] + MRS -- No --> MF + MIRI2 -- Yes --> H2[Handle_ORLCF_VMSC] + MIRI2 -- No --> MF + H2 --> WRF2[Wait_For_Release_From_GMSC] + WRF2 --> R2[Release] + R2 --> C2[CAMEL_MT_GMSC_DISC6] + C2 --> CC[CCBS_Check_Last_Call] + CC --> RC2[Release call resources] + RC2 --> I2[Idle] + VMSCCF[VMSCCF] --> CV[CAMEL_Check_ORLCF_VMSC] + CV --> JR[Result?] + JR -- ORLCF --> H3[Handle_ORLCF_VMSC] + JR -- Continue --> 3((3)) + H3 --> JR2[Result?] + JR2 -- Accepted --> 3 + JR2 -- Forwarding Failed --> CF[CD_Failure] + JR2 -- Forwarding Failed --> CS[CD_Success] + CF --> WRF3[Wait_For_Release_From_GMSC] + CS --> WRF3 + WRF3 --> R3[Release] + R3 --> C3[CAMEL_MT_GMSC_DISC6] + C3 --> CC3[CCBS_Check_Last_Call] + CC3 --> RC3[Release call resources] + RC3 --> I3[Idle] +``` + +Flowchart for Process ICH\_MSC (sheet 5). The process starts at connector 1, goes through Wait\_For\_MT\_Call\_Result, Send\_Info\_For\_Incoming\_Callack, and M\_T\_Roaming\_Forwarding\_supported. It branches based on 'yes' or 'No' for forwarding support. The 'yes' path goes through M\_T\_Roaming\_Forwarding\_Indicator\_received, Initial\_Address\_Message\_to\_new\_MSC, Wait\_For\_MTRF\_ACM, Handle\_ORLCF\_VMSC, Wait\_For\_Release\_From\_GMSC, Release, CAMEL\_MT\_GMSC\_DISC6, Release call resources, and Idle. The 'No' path goes through M\_T\_Roaming\_Retry\_supported, M\_T\_Roaming\_Retry\_Indicator\_received, Handle\_ORLCF\_VMSC, Wait\_For\_Release\_From\_GMSC, Release, CAMEL\_MT\_GMSC\_DISC6, CCBS\_Check\_Last\_Call, Release call resources, and Idle. A VMSCCF block with CAMEL\_Check\_ORLCF\_VMSC and VMSCCF\_Result? decisions is also shown, leading to CD\_Failure or CD\_Success, and then to connector 3. + +Figure 67e: Process ICH\_MSC (sheet 5) + +![Flowchart for Process ICH_MSC (sheet 6). The process starts at connector 3 and branches based on 'Type of forwarding=Reconnect?'. It includes steps for CAMEL MT VMSC Notify CF, CCBS Check Last Call, Set redirection information, Send ACM If Required, Activate CF Process, Release, CAMEL MT GMSC DISC4, Initial Address Message, CAMEL Store Destination Address, CD Failure, CD Success, and ends at Idle.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC6(17) + +Process in the MSC to handle an incoming (MT) call + +Signals to the right are to the VLR unless marked otherwise + +``` +graph TD; Start((3)) --> Decision1{Type of forwarding=Reconnect?}; Decision1 -- Yes --> SendInfoForMT[Send Info For MT Reconnected Call]; Decision1 -- No --> CAMEL1[["CAMEL MT VMSC Notify CF"]]; CAMEL1 --> Decision2{Result=Reconnect?}; Decision2 -- Yes --> SendInfoForMT; Decision2 -- No --> CCBS1[["CCBS Check Last Call"]]; CCBS1 --> SetRedirection[Set redirection information]; SetRedirection --> SendACM[["Send ACM If Required"]]; SendACM --> ActivateCF[["Activate CF Process"]]; ActivateCF --> Decision3{Result?}; Decision3 -- Fail --> Release{Release}; Decision3 -- Pass --> UUS[["UUS ICH Set Info In IAM"]]; Release --> CAMEL2[["CAMEL MT GMSC DISC4"]]; UUS --> IAM[Initial Address Message]; IAM --> CAMEL3[["CAMEL Store Destination Address (False, True)"]]; CAMEL3 --> CD_Success[["CD Success"]]; CD_Success --> WaitForForwardACM[("Wait For Forward ACM")]; CAMEL2 --> Decision4{Result=Reconnect?}; Decision4 -- Yes --> SendInfoForMT; Decision4 -- No --> CD_Failure[["CD Failure"]]; CD_Failure --> CCBS2[["CCBS Check Last Call"]]; CCBS2 --> Idle[("Idle")]; SendInfoForMT --> WaitForReconnected[("Wait For Reconnected Call Result")]; +``` + +Flowchart for Process ICH\_MSC (sheet 6). The process starts at connector 3 and branches based on 'Type of forwarding=Reconnect?'. It includes steps for CAMEL MT VMSC Notify CF, CCBS Check Last Call, Set redirection information, Send ACM If Required, Activate CF Process, Release, CAMEL MT GMSC DISC4, Initial Address Message, CAMEL Store Destination Address, CD Failure, CD Success, and ends at Idle. + +Figure 67f: Process ICH\_MSC (sheet 6) + +![State transition diagram for Process ICH_MSC. The diagram shows a vertical sequence of states and transitions: 1. Initial state (oval) leads to 'Wait_For_MT_Call_Result, Wait_For_Reconnected_Call_Result' (rectangle). 2. 'Int_Release_Call' (diamond) transition from 'Wait_For_MT_Call_Result' to 'Abort' (diamond), with 'From gsmSSF' (rectangle) input. 3. 'Abort' (diamond) leads to 'Release' (diamond). 4. 'Release' (diamond) leads to 'Release Transaction' (diamond), with 'To BSS' (rectangle) output. 5. 'Release Transaction' (diamond) leads to 'Release call resources' (rectangle). 6. 'Release call resources' (rectangle) leads to 'Idle' (oval).](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC7(17) + +Process in the MSC +to handle an incoming (MT) call + +Signals to/from the left +are to/from the GMSC; +signals to/from the right +are to/from the VLR +unless marked otherwise + +``` +stateDiagram-v2 + [*] --> Wait_For_MT_Call_Result + state "Wait_For_MT_Call_Result, Wait_For_Reconnected_Call_Result" as Wait_For_MT_Call_Result + state "Int_Release_Call" as Int_Release_Call + state "Abort" as Abort + state "Release" as Release + state "Release Transaction" as Release_Transaction + state "Release call resources" as Release_call_resources + state "Idle" as Idle + + Wait_For_MT_Call_Result --> Int_Release_Call + Int_Release_Call --> Abort + Abort --> Release + Release --> Release_Transaction + Release_Transaction --> Release_call_resources + Release_call_resources --> Idle +``` + +State transition diagram for Process ICH\_MSC. The diagram shows a vertical sequence of states and transitions: 1. Initial state (oval) leads to 'Wait\_For\_MT\_Call\_Result, Wait\_For\_Reconnected\_Call\_Result' (rectangle). 2. 'Int\_Release\_Call' (diamond) transition from 'Wait\_For\_MT\_Call\_Result' to 'Abort' (diamond), with 'From gsmSSF' (rectangle) input. 3. 'Abort' (diamond) leads to 'Release' (diamond). 4. 'Release' (diamond) leads to 'Release Transaction' (diamond), with 'To BSS' (rectangle) output. 5. 'Release Transaction' (diamond) leads to 'Release call resources' (rectangle). 6. 'Release call resources' (rectangle) leads to 'Idle' (oval). + +Figure 67g: Process ICH\_MSC (sheet 7) + +![State transition diagram for Process ICH_MSC. The process starts in 'Wait_For_Forward_ACM' and transitions to 'Address Complete'. From there, it can send ACM, enter 'CAMEL_MT_MSC_ALERTING', or connect. The 'CAMEL_MT_MSC_ALERTING' state leads to a 'Result?' decision. If 'Pass', it goes to 'Wait_For_Forward_Answer'. If 'Answer', it goes to 'CAMEL_MT_GMSC_ANSWER'. If 'Else', it goes to 'CAMEL_MT_GMSC_ANSWER'. The 'Wait_For_Forward_Answer' state leads to a 'Release' or 'Answer' state. The 'Answer' state leads to 'CAMEL_MT_GMSC_ANSWER'. The 'CAMEL_MT_GMSC_ANSWER' state leads to a 'Result?' decision. If 'Pass', it goes to 'Handle_COLP_Forwarding_Interaction_MSC'. If 'Else', it goes to 'Release'. The 'Handle_COLP_Forwarding_Interaction_MSC' state leads to 'Set_COLP_presentation_indicator', then 'Send_Answer_If_Required', then 'Call_answered := True', and finally to connector '7'. The 'Call_answered := True' state also leads to connector '6'. The 'Release' state leads to 'CAMEL_MT_GMSC_DISC6', which leads to 'Release call resources', which leads to 'Idle'. The 'Release' state also leads to 'CAMEL_MT_GMSC_DISC4', which leads to 'Send_Info_For_MT_Reconnected_Call', which leads to 'Wait_For_Reconnected_Call_Result'. The 'CAMEL_MT_GMSC_ANSWER' state also leads to 'CAMEL_MT_GMSC_ANSWER', which leads to a 'Result?' decision. If 'Pass', it goes to 'Handle_COLP_Forwarding_Interaction_MSC'. If 'Else', it goes to 'Release'. The 'Handle_COLP_Forwarding_Interaction_MSC' state leads to 'Set_COLP_presentation_indicator', then 'Send_Network_Connect_If_Required', which leads to connector '6'. The 'Release' state also leads to 'Release call resources', which leads to 'Idle'.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC8(17) + +Process in the MSC to handle an incoming (MT) call + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the process MT\_CF\_MSC unless marked otherwise + +``` +stateDiagram-v2 + [*] --> Wait_For_Forward_ACM + Wait_For_Forward_ACM --> Address_Complete : Address Complete + Address_Complete --> Send_ACM_If_Required : Send ACM_If_Required + Send_ACM_If_Required --> CAMEL_MT_MSC_ALERTING : CAMEL_MT_MSC_ALERTING + CAMEL_MT_MSC_ALERTING --> Result1{Result?} + Result1 --> Wait_For_Forward_Answer : Pass + Result1 --> CAMEL_MT_GMSC_ANSWER : Answer + Result1 --> CAMEL_MT_GMSC_ANSWER : Else + Wait_For_Forward_Answer --> Release1{Release} + Wait_For_Forward_Answer --> Release2{Release} + Wait_For_Forward_Answer --> Answer1{Answer} + Answer1 --> CAMEL_MT_GMSC_ANSWER + CAMEL_MT_GMSC_ANSWER --> Result2{Result?} + Result2 --> Handle_COLP_Forwarding_Interaction_MSC1[Handle_COLP_Forwarding_Interaction_MSC] : Pass + Result2 --> Release3{Release} : Else + Handle_COLP_Forwarding_Interaction_MSC1 --> Set_COLP_presentation_indicator1[Set COLP presentation indicator] + Set_COLP_presentation_indicator1 --> Send_Answer_If_Required1[Send Answer_If_Required] + Send_Answer_If_Required1 --> Call_answered[Call answered := True] + Call_answered --> 7((7)) + Call_answered --> 6((6)) + Release3 --> CAMEL_MT_GMSC_DISC6[CAMEL_MT_GMSC_DISC6] + CAMEL_MT_GMSC_DISC6 --> Release_call_resources[Release call resources] + Release_call_resources --> Idle1[Idle] + Release3 --> CAMEL_MT_GMSC_DISC4[CAMEL_MT_GMSC_DISC4] + CAMEL_MT_GMSC_DISC4 --> Send_Info_For_MT_Reconnected_Call[Send Info For MT Reconnected Call] + Send_Info_For_MT_Reconnected_Call --> Wait_For_Reconnected_Call_Result[Wait_For_Reconnected_Call_Result] + CAMEL_MT_GMSC_ANSWER --> CAMEL_MT_GMSC_ANSWER + CAMEL_MT_GMSC_ANSWER --> Result3{Result?} + Result3 --> Handle_COLP_Forwarding_Interaction_MSC2[Handle_COLP_Forwarding_Interaction_MSC] : Pass + Result3 --> Release4{Release} : Else + Handle_COLP_Forwarding_Interaction_MSC2 --> Set_COLP_presentation_indicator2[Set COLP presentation indicator] + Set_COLP_presentation_indicator2 --> Send_Network_Connect_If_Required[Send Network_Connect_If_Required] + Send_Network_Connect_If_Required --> 6 + Release4 --> Release_call_resources + Release_call_resources --> Idle2[Idle] +``` + +State transition diagram for Process ICH\_MSC. The process starts in 'Wait\_For\_Forward\_ACM' and transitions to 'Address Complete'. From there, it can send ACM, enter 'CAMEL\_MT\_MSC\_ALERTING', or connect. The 'CAMEL\_MT\_MSC\_ALERTING' state leads to a 'Result?' decision. If 'Pass', it goes to 'Wait\_For\_Forward\_Answer'. If 'Answer', it goes to 'CAMEL\_MT\_GMSC\_ANSWER'. If 'Else', it goes to 'CAMEL\_MT\_GMSC\_ANSWER'. The 'Wait\_For\_Forward\_Answer' state leads to a 'Release' or 'Answer' state. The 'Answer' state leads to 'CAMEL\_MT\_GMSC\_ANSWER'. The 'CAMEL\_MT\_GMSC\_ANSWER' state leads to a 'Result?' decision. If 'Pass', it goes to 'Handle\_COLP\_Forwarding\_Interaction\_MSC'. If 'Else', it goes to 'Release'. The 'Handle\_COLP\_Forwarding\_Interaction\_MSC' state leads to 'Set\_COLP\_presentation\_indicator', then 'Send\_Answer\_If\_Required', then 'Call\_answered := True', and finally to connector '7'. The 'Call\_answered := True' state also leads to connector '6'. The 'Release' state leads to 'CAMEL\_MT\_GMSC\_DISC6', which leads to 'Release call resources', which leads to 'Idle'. The 'Release' state also leads to 'CAMEL\_MT\_GMSC\_DISC4', which leads to 'Send\_Info\_For\_MT\_Reconnected\_Call', which leads to 'Wait\_For\_Reconnected\_Call\_Result'. The 'CAMEL\_MT\_GMSC\_ANSWER' state also leads to 'CAMEL\_MT\_GMSC\_ANSWER', which leads to a 'Result?' decision. If 'Pass', it goes to 'Handle\_COLP\_Forwarding\_Interaction\_MSC'. If 'Else', it goes to 'Release'. The 'Handle\_COLP\_Forwarding\_Interaction\_MSC' state leads to 'Set\_COLP\_presentation\_indicator', then 'Send\_Network\_Connect\_If\_Required', which leads to connector '6'. The 'Release' state also leads to 'Release call resources', which leads to 'Idle'. + +Figure 67h: Process ICH\_MSC (sheet 8) + +![Flowchart for Process ICH_MSC. It starts at node 7, checks if a CAMEL phase 4 or later control relationship exists. If 'Yes', it sets Leg1_status to Active, then calls CAMEL_ICH_LEG1_MSC (Leg1_Status) and CAMEL_ICH_LEG2_CF_MSC (referencing TS 23.078), ending at Idle. If 'No', it goes to Wait_For_Clear.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +**Process ICH\_MSC** **ICH\_MSC9(17)** + +Process in the MSC +to handle an incoming (MT) call + +``` +graph TD; Start((7)) --> Decision{CAMEL phase 4 or later control relationship exists?}; Decision -- Yes --> Leg1_Status[Leg1_status := Active]; Leg1_Status --> Leg1_MSC[CAMEL_ICH_LEG1_MSC (Leg1_Status)]; Leg1_MSC --> Leg2_CF_MSC[CAMEL_ICH_LEG2_CF_MSC]; Leg2_CF_MSC --> Idle([Idle]); Decision -- No --> Wait_For_Clear([Wait_For_Clear]); Note1[See TS 23.078] -.-> Leg1_MSC; Note2[See TS 23.078] -.-> Leg2_CF_MSC; +``` + +Flowchart for Process ICH\_MSC. It starts at node 7, checks if a CAMEL phase 4 or later control relationship exists. If 'Yes', it sets Leg1\_status to Active, then calls CAMEL\_ICH\_LEG1\_MSC (Leg1\_Status) and CAMEL\_ICH\_LEG2\_CF\_MSC (referencing TS 23.078), ending at Idle. If 'No', it goes to Wait\_For\_Clear. + +**Figure 67i: Process ICH\_MSC (sheet 9)** + +![State transition diagram for Process ICH_MSC. The process starts at 'Wait_For_Forward_ACM'. A 'Release' signal from the left leads to another 'Release' state, then 'CAMEL_MT_GMSC_DISC6' (referencing TS 23.078). A 'Release' signal from the right leads to 'CAMEL_MT_GMSC_DISC4' (referencing TS 23.078), which then leads to a decision 'Result=Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call' (to VLR), 'Wait_For_Reconnected_Call_Result', 'Send Info For MT Reconnected Call negative response', 'Set cause', 'Release' (to right), and 'Int_Exception' (to gsmSSF). If 'No', it goes to 'CCBS_MT_MSC_Check_Forwarding' (referencing TS 23.093), then 'CCBS_Set_Diagnostic_For_Release' (referencing TS 23.093), then 'Release' (to left), and finally 'Release call resources' leading to 'Idle'.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC10(17) + +Process in the MSC to handle an incoming (MT) call + +Signals to/from the left are to/from the GMSC; +signals to/from the right are to/from the process MT\_CF\_MSC +unless marked otherwise + +``` +stateDiagram-v2 + [*] --> Wait_For_Forward_ACM + state "Release (left)" as Release_L + state "Release (right)" as Release_R + state "CAMEL_MT_GMSC_DISC6" as Disc6 + state "CAMEL_MT_GMSC_DISC4" as Disc4 + state "Result=Reconnect?" as Reconnect + state "CCBS_MT_MSC_Check_Forwarding" as CCBS_Forwarding + state "CCBS_Set_Diagnostic_For_Release" as CCBS_Diagnostic + state "Release (internal)" as Release_Int + state "Release call resources" as Release_Resources + state "Idle" as Idle + state "Send Info For MT Reconnected Call" as Send_Info + state "Wait_For_Reconnected_Call_Result" as Wait_Reconnect + state "Send Info For MT Reconnected Call negative response" as Send_Info_Neg + state "Set cause" as Set_Cause + state "Int_Exception" as Int_Exception + + Note left of Disc6: See TS 23.078 + Note right of Disc4: See TS 23.078 + Note left of CCBS_Forwarding: See TS 23.093 + Note left of CCBS_Diagnostic: See TS 23.093 + Note right of Send_Info: To VLR + Note right of Int_Exception: To gsmSSF + + Wait_For_Forward_ACM --> Release_L + Wait_For_Forward_ACM --> Release_R + Release_L --> Disc6 + Release_R --> Disc4 + Disc6 --> Release_Resources + Disc4 --> Reconnect + Reconnect -- Yes --> Send_Info + Reconnect -- No --> CCBS_Forwarding + Send_Info --> Wait_Reconnect + Wait_Reconnect --> Send_Info_Neg + Send_Info_Neg --> Set_Cause + Set_Cause --> Release_Int + Release_Int --> Int_Exception + Int_Exception --> Release_Resources + CCBS_Forwarding --> CCBS_Diagnostic + CCBS_Diagnostic --> Release_Int + Release_Int --> Release_Resources + Release_Resources --> Idle +``` + +State transition diagram for Process ICH\_MSC. The process starts at 'Wait\_For\_Forward\_ACM'. A 'Release' signal from the left leads to another 'Release' state, then 'CAMEL\_MT\_GMSC\_DISC6' (referencing TS 23.078). A 'Release' signal from the right leads to 'CAMEL\_MT\_GMSC\_DISC4' (referencing TS 23.078), which then leads to a decision 'Result=Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call' (to VLR), 'Wait\_For\_Reconnected\_Call\_Result', 'Send Info For MT Reconnected Call negative response', 'Set cause', 'Release' (to right), and 'Int\_Exception' (to gsmSSF). If 'No', it goes to 'CCBS\_MT\_MSC\_Check\_Forwarding' (referencing TS 23.093), then 'CCBS\_Set\_Diagnostic\_For\_Release' (referencing TS 23.093), then 'Release' (to left), and finally 'Release call resources' leading to 'Idle'. + +Figure 67j: Process ICH\_MSC (sheet 10) + +![Flowchart for Process ICH_MSC. It starts with 'Wait_For_Reconnected_Call_Result', followed by 'Send Info For MT Reconnected Call ack'. A decision 'Call answered' follows. If 'True', it goes to connector '4'. If 'False', it goes to 'Handle ORLCF_VMSC' (See TS 23.079). From there, a decision 'Result= Accepted?' follows. If 'No', it goes to 'Result= Forwarding Failed?'. If 'Yes', it goes to 'CD_Success' (See TS 23.072). If 'Result= Forwarding Failed?' is 'No', it goes to connector '4'. If 'Yes', it goes to 'CD_Failure' (See TS 23.072). Both 'CD_Failure' and 'CD_Success' lead to 'Wait_For_Release_From_GMSC', which then goes to 'Release', 'CAMEL_MT_GMSC_DISC6' (See TS 23.078), 'CCBS_Check_Last_Call' (See TS 23.093), 'Release call resources', and finally 'Idle'.](8269648391c59363ea61243864a2adf7_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC11(17) + +``` +graph TD; Start([Wait_For_Reconnected_Call_Result]) --> Action1[Send Info For MT Reconnected Call ack]; Action1 --> Decision1{Call answered}; Decision1 -- True --> Connector4((4)); Decision1 -- False --> Action2[Handle ORLCF_VMSC]; Action2 -.-> Note1[See TS 23.079]; Action2 --> Decision2{Result= Accepted?}; Decision2 -- No --> Decision3{Result= Forwarding Failed?}; Decision2 -- Yes --> Action3[CD_Success]; Action3 -.-> Note2[See TS 23.072]; Decision3 -- No --> Connector4; Decision3 -- Yes --> Action4[CD_Failure]; Action4 -.-> Note3[See TS 23.072]; Action3 --> Action5[Wait_For_Release_From_GMSC]; Action4 --> Action5; Action5 --> Action6[Release]; Action6 --> Action7[CAMEL_MT_GMSC_DISC6]; Action7 -.-> Note4[See TS 23.078]; Action7 --> Action8[CCBS_Check_Last_Call]; Action8 -.-> Note5[See TS 23.093]; Action8 --> Action9[Release call resources]; Action9 --> End([Idle]); +``` + +Process in the MSC to handle an incoming (MT) call + +Signals from the left are from the GMSC; signals from the right are from the VLR + +Flowchart for Process ICH\_MSC. It starts with 'Wait\_For\_Reconnected\_Call\_Result', followed by 'Send Info For MT Reconnected Call ack'. A decision 'Call answered' follows. If 'True', it goes to connector '4'. If 'False', it goes to 'Handle ORLCF\_VMSC' (See TS 23.079). From there, a decision 'Result= Accepted?' follows. If 'No', it goes to 'Result= Forwarding Failed?'. If 'Yes', it goes to 'CD\_Success' (See TS 23.072). If 'Result= Forwarding Failed?' is 'No', it goes to connector '4'. If 'Yes', it goes to 'CD\_Failure' (See TS 23.072). Both 'CD\_Failure' and 'CD\_Success' lead to 'Wait\_For\_Release\_From\_GMSC', which then goes to 'Release', 'CAMEL\_MT\_GMSC\_DISC6' (See TS 23.078), 'CCBS\_Check\_Last\_Call' (See TS 23.093), 'Release call resources', and finally 'Idle'. + +Figure 67k: Process ICH\_MSC (sheet 11) + +![Flowchart for Process ICH_MSC. It starts with 'Wait_For_MT_Call_Result', leading to 'Release' and 'Release transaction'. 'Release' leads to 'CAMEL MT_GMSC_DISC6' (See TS 23.078) and then 'Release transaction'. 'Release transaction' leads to 'CAMEL MT_GMSC_DISC4' (See TS 23.078). From 'CAMEL MT_GMSC_DISC4', it goes to 'Result=Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call' (To VLR) and then 'Wait_For_Reconnected_Call_Result'. If 'No', it goes to 'Release' and then 'CCBS_Check_Last_Call' (See TS 23.093). 'CCBS_Check_Last_Call' leads to 'Abort' (To VLR) and then 'Release call resources', which ends at 'Idle'.](32ff77da4286b58c4778033acaa10836_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC12(17) + +Process in the MSC to handle an incoming (MT) call + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the BSS unless marked otherwise + +``` +graph TD; Start([Wait_For_MT_Call_Result]) --> Release1[Release]; Start --> ReleaseTrans1[Release transaction]; Release1 --> CAMEL1[CAMEL MT_GMSC_DISC6]; CAMEL1 --- SeeTS1[See TS 23.078]; CAMEL1 --> ReleaseTrans2[Release transaction]; ReleaseTrans1 --> CAMEL2[CAMEL MT_GMSC_DISC4]; CAMEL2 --- SeeTS2[See TS 23.078]; CAMEL2 --> Reconnect{Result=Reconnect?}; Reconnect -- Yes --> SendInfo[Send Info For MT Reconnected Call]; SendInfo --- ToVLR1[To VLR]; SendInfo --> WaitReconnect([Wait_For_Reconnected_Call_Result]); Reconnect -- No --> Release2[Release]; Release2 --> CCBS[CCBS_Check_Last_Call]; CCBS --- SeeTS3[See TS 23.093]; CCBS --> Abort[Abort]; Abort --- ToVLR2[To VLR]; Abort --> ReleaseResources[Release call resources]; ReleaseResources --> Idle([Idle]); +``` + +Flowchart for Process ICH\_MSC. It starts with 'Wait\_For\_MT\_Call\_Result', leading to 'Release' and 'Release transaction'. 'Release' leads to 'CAMEL MT\_GMSC\_DISC6' (See TS 23.078) and then 'Release transaction'. 'Release transaction' leads to 'CAMEL MT\_GMSC\_DISC4' (See TS 23.078). From 'CAMEL MT\_GMSC\_DISC4', it goes to 'Result=Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call' (To VLR) and then 'Wait\_For\_Reconnected\_Call\_Result'. If 'No', it goes to 'Release' and then 'CCBS\_Check\_Last\_Call' (See TS 23.093). 'CCBS\_Check\_Last\_Call' leads to 'Abort' (To VLR) and then 'Release call resources', which ends at 'Idle'. + +Figure 67I: Process ICH\_MSC (sheet 12) + +![State transition diagram for Process ICH_MSC. It starts at 'Wait_For_Clear' and branches into 'Release' and 'Release transaction' paths. The 'Release' path leads to 'UUS_MSC_Check_UUS1_UUI' (See TS 23.087), then 'Release transaction', then 'CAMEL_MT_GMSC_DISC1' (See TS 23.078), then 'CCBS_Check_Last_Call' (See TS 23.093), then 'Release call resources', then 'Call cleared' (To Subs_FSM), and finally 'Idle'. The 'Release transaction' path leads to 'CAMEL_MT_GMSC_DISC2' (See TS 23.078), then a decision 'Result= Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call' (To VLR) and then 'Wait_For_Reconnected_Call_Result'. If 'No', it goes to 'UUS_MSC_Check_UUS1_UUI' (See TS 23.087), then 'Release', and then joins the 'CCBS_Check_Last_Call' path.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +**Process ICH\_MSC** + +**ICH\_MSC13(17)** + +Process in the MSC +to handle an incoming (MT) call + +Signals to/from the left +are to/from the GMSC; +signals to/from the right +are to/from the BSS +unless marked otherwise + +``` +stateDiagram-v2 + [*] --> Wait_For_Clear + state "Release" as Release + state "Release transaction" as Release_transaction + state "UUS_MSC_Check_UUS1_UUI" as UUS_MSC_Check_UUS1_UUI + state "CAMEL_MT_GMSC_DISC2" as CAMEL_MT_GMSC_DISC2 + state "Result= Reconnect?" as Result_Reconnect + state "CAMEL_MT_GMSC_DISC1" as CAMEL_MT_GMSC_DISC1 + state "UUS_MSC_Check_UUS1_UUI_2" as UUS_MSC_Check_UUS1_UUI + state "Release_2" as Release + state "CCBS_Check_Last_Call" as CCBS_Check_Last_Call + state "Release call resources" as Release_call_resources + state "Call cleared" as Call_cleared + state "Idle" as Idle + state "Send Info For MT Reconnected Call" as Send_Info_For_MT_Reconnected_Call + state "Wait_For_Reconnected_Call_Result" as Wait_For_Reconnected_Call_Result + + Note right of UUS_MSC_Check_UUS1_UUI: See TS 23.087 + Note right of CAMEL_MT_GMSC_DISC2: See TS 23.078 + Note right of CAMEL_MT_GMSC_DISC1: See TS 23.078 + Note right of CCBS_Check_Last_Call: See TS 23.093 + Note right of UUS_MSC_Check_UUS1_UUI_2: See TS 23.087 + + Note left of Call_cleared: To Subs_FSM + Note right of Send_Info_For_MT_Reconnected_Call: To VLR + + Wait_For_Clear --> Release + Wait_For_Clear --> Release_transaction + Release --> UUS_MSC_Check_UUS1_UUI + Release_transaction --> CAMEL_MT_GMSC_DISC2 + CAMEL_MT_GMSC_DISC2 --> Result_Reconnect + Result_Reconnect -- Yes --> Send_Info_For_MT_Reconnected_Call + Result_Reconnect -- No --> UUS_MSC_Check_UUS1_UUI_2 + UUS_MSC_Check_UUS1_UUI --> Release_transaction + UUS_MSC_Check_UUS1_UUI_2 --> Release_2 + Release_2 --> CCBS_Check_Last_Call + CCBS_Check_Last_Call --> Release_call_resources + Release_call_resources --> Call_cleared + Call_cleared --> Idle + Send_Info_For_MT_Reconnected_Call --> Wait_For_Reconnected_Call_Result +``` + +State transition diagram for Process ICH\_MSC. It starts at 'Wait\_For\_Clear' and branches into 'Release' and 'Release transaction' paths. The 'Release' path leads to 'UUS\_MSC\_Check\_UUS1\_UUI' (See TS 23.087), then 'Release transaction', then 'CAMEL\_MT\_GMSC\_DISC1' (See TS 23.078), then 'CCBS\_Check\_Last\_Call' (See TS 23.093), then 'Release call resources', then 'Call cleared' (To Subs\_FSM), and finally 'Idle'. The 'Release transaction' path leads to 'CAMEL\_MT\_GMSC\_DISC2' (See TS 23.078), then a decision 'Result= Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call' (To VLR) and then 'Wait\_For\_Reconnected\_Call\_Result'. If 'No', it goes to 'UUS\_MSC\_Check\_UUS1\_UUI' (See TS 23.087), then 'Release', and then joins the 'CCBS\_Check\_Last\_Call' path. + +Figure 67m: Process ICH\_MSC (sheet 13) + +![State transition diagram for Process ICH_MSC. The diagram shows two main parts. The top part starts with 'Wait_For_Forward_Clear' leading to two 'Release' transitions. The left 'Release' leads to another 'Release' transition, then 'CAMEL_MT_GMSC_DISC1' (linked to TS 23.078), then 'Release call resources', and finally 'Idle'. The right 'Release' leads to 'CAMEL_MT_GMSC_DISC2' (linked to TS 23.078), then a decision 'Result=Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call' (linked to To VLR) and then 'Wait_For_Reconnected_Call_Result'. If 'No', it goes to 'Release', then 'Release call resources', and finally 'Idle'. The bottom part starts with a state (linked to Wait_For_Forward_ACM, Wait_For_Forward_Answer, Wait_For_Forward_Clear), leading to two '*' transitions, then two '-' transitions, and finally a '-' state.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC14(17) + +Process in the MSC to handle an incoming (MT) call + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the process MT\_CF\_MSC unless marked otherwise + +``` +stateDiagram-v2 + [*] --> Wait_For_Forward_Clear + state "Wait_For_Forward_Clear" as Wait_For_Forward_Clear + state "Release" as Release + state "CAMEL_MT_GMSC_DISC1" as CAMEL_MT_GMSC_DISC1 + state "CAMEL_MT_GMSC_DISC2" as CAMEL_MT_GMSC_DISC2 + state "Result=Reconnect?" as Result_Reconnect + state "Release call resources" as Release_call_resources + state "Idle" as Idle + state "Send Info For MT Reconnected Call" as Send_Info_For_MT_Reconnected_Call + state "To VLR" as To_VLR + state "Wait_For_Reconnected_Call_Result" as Wait_For_Reconnected_Call_Result + state "*" as Star + state "-" as Dash + + Note left of Wait_For_Forward_Clear: Process in the MSC to handle an incoming (MT) call + Note right of CAMEL_MT_GMSC_DISC2: Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the process MT_CF_MSC unless marked otherwise + Note right of CAMEL_MT_GMSC_DISC1: See TS 23.078 + Note right of CAMEL_MT_GMSC_DISC2: See TS 23.078 + Note right of Send_Info_For_MT_Reconnected_Call: To VLR + Note right of Star: Wait_For_Forward_ACM, Wait_For_Forward_Answer, Wait_For_Forward_Clear + + Wait_For_Forward_Clear --> Release + Release --> Release + Release --> CAMEL_MT_GMSC_DISC2 + CAMEL_MT_GMSC_DISC2 --> Result_Reconnect + Result_Reconnect -- Yes --> Send_Info_For_MT_Reconnected_Call + Send_Info_For_MT_Reconnected_Call --> To_VLR + Send_Info_For_MT_Reconnected_Call --> Wait_For_Reconnected_Call_Result + Result_Reconnect -- No --> Release + Release --> Release_call_resources + Release_call_resources --> Idle + CAMEL_MT_GMSC_DISC1 --> Release_call_resources + Release_call_resources --> Idle + Star --> Dash + Dash --> Dash +``` + +State transition diagram for Process ICH\_MSC. The diagram shows two main parts. The top part starts with 'Wait\_For\_Forward\_Clear' leading to two 'Release' transitions. The left 'Release' leads to another 'Release' transition, then 'CAMEL\_MT\_GMSC\_DISC1' (linked to TS 23.078), then 'Release call resources', and finally 'Idle'. The right 'Release' leads to 'CAMEL\_MT\_GMSC\_DISC2' (linked to TS 23.078), then a decision 'Result=Reconnect?'. If 'Yes', it goes to 'Send Info For MT Reconnected Call' (linked to To VLR) and then 'Wait\_For\_Reconnected\_Call\_Result'. If 'No', it goes to 'Release', then 'Release call resources', and finally 'Idle'. The bottom part starts with a state (linked to Wait\_For\_Forward\_ACM, Wait\_For\_Forward\_Answer, Wait\_For\_Forward\_Clear), leading to two '\*' transitions, then two '-' transitions, and finally a '-' state. + +Figure 67n: Process ICH\_MSC (sheet 14) + +![State transition diagram for Process ICH_MSC. It shows two vertical state transition sequences. The left sequence starts with an initial state (oval) labeled 'Wait_For_Forward_ACM, Wait_For_Forward_Clear', leading to a transition 'Int_Release_Call' (chevron) from 'gsmSSF', then 'Release' (arrow), 'Release' (chevron), 'Release call resources' (rectangle), and ending at 'Idle' (oval). The right sequence starts with an initial state (oval) labeled 'Wait_For_Clear', leading to a transition 'Int_Release_Call' (chevron) from 'gsmSSF', then 'Release transaction' (arrow) to 'BSS', 'Release' (chevron), 'Release call resources' (rectangle), 'Call cleared' (chevron) to 'Subs_FSM', and ending at 'Idle' (oval).](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +### Process ICH\_MSC + +Process in the MSC to handle an incoming (MT) call + +### ICH\_MSC15(17) + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the process MT\_CF\_MSC unless marked otherwise + +``` +stateDiagram-v2 + [*] --> WFFACM: Wait_For_Forward_ACM, Wait_For_Forward_Clear + WFFACM --> IRC: Int_Release_Call + IRC --> R1: Release + R1 --> R2: Release + R2 --> RCR: Release call resources + RCR --> Idle1: Idle + + [*] --> WFC: Wait_For_Clear + WFC --> IRC2: Int_Release_Call + IRC2 --> RT: Release transaction + RT --> R3: Release + R3 --> RCR2: Release call resources + RCR2 --> CC: Call cleared + CC --> Idle2: Idle +``` + +State transition diagram for Process ICH\_MSC. It shows two vertical state transition sequences. The left sequence starts with an initial state (oval) labeled 'Wait\_For\_Forward\_ACM, Wait\_For\_Forward\_Clear', leading to a transition 'Int\_Release\_Call' (chevron) from 'gsmSSF', then 'Release' (arrow), 'Release' (chevron), 'Release call resources' (rectangle), and ending at 'Idle' (oval). The right sequence starts with an initial state (oval) labeled 'Wait\_For\_Clear', leading to a transition 'Int\_Release\_Call' (chevron) from 'gsmSSF', then 'Release transaction' (arrow) to 'BSS', 'Release' (chevron), 'Release call resources' (rectangle), 'Call cleared' (chevron) to 'Subs\_FSM', and ending at 'Idle' (oval). + +Figure 67o: Process ICH\_MSC (sheet 15) + +![Flowchart for Process ICH_MSC. It starts with 'Wait_For_Clear', branches into 'Hold request' and 'Retrieve request'. Both have 'Hold supported?' checks. 'Hold request' leads to 'Process_Hold_Request' (Yes) or 'Hold reject' (No). 'Retrieve request' leads to 'Process_Retrieve_Request' (Yes) or 'Retrieve reject' (No). All four paths converge to 'Wait_For_Clear'. External references point to 'See 3G TS 23.083'.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC16(17) + +Process in the MSC to handle an incoming (MT) call + +Signals to/from the left are to/from the BSS + +``` +graph TD; Start([Wait_For_Clear]) --> HReq{Hold request}; Start --> RetReq{Retrieve request}; HReq --> HSup{Hold supported?}; RetReq --> HSup2{Hold supported?}; HSup -- Yes --> PHR[Process_Hold_Request]; HSup -- No --> HRej{Hold reject}; HSup2 -- No --> Rej{Retrieve reject}; HSup2 -- Yes --> PRR[Process_Retrieve_Request]; PHR --> End([Wait_For_Clear]); HRej --> End; Rej --> End; PRR --> End; PHR -.-> Ref1[See 3G TS 23.083]; PRR -.-> Ref2[See 3G TS 23.083]; +``` + +Flowchart for Process ICH\_MSC. It starts with 'Wait\_For\_Clear', branches into 'Hold request' and 'Retrieve request'. Both have 'Hold supported?' checks. 'Hold request' leads to 'Process\_Hold\_Request' (Yes) or 'Hold reject' (No). 'Retrieve request' leads to 'Process\_Retrieve\_Request' (Yes) or 'Retrieve reject' (No). All four paths converge to 'Wait\_For\_Clear'. External references point to 'See 3G TS 23.083'. + +Figure 67p: Process ICH\_MSC (sheet 16) + +![State transition diagram for Process ICH_MSC. It starts with a 'Wait_For_Clear' state, which branches into two parallel 'ECT request' and 'MPTY request' states. Both of these lead to another 'Wait_For_Clear' state.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +### Process ICH\_MSC + +ICH\_MSC17(17) + +Process in the MSC +to handle an incoming (MT) call + +Signals from the left +are from the BSS; +signals to the right +are to the Subs\_FSM process. + +``` +stateDiagram-v2 + [*] --> Wait_For_Clear + state "ECT request" as ECT_request + state "MPTY request" as MPTY_request + state "Wait_For_Clear" as Wait_For_Clear_2 + Wait_For_Clear --> ECT_request + Wait_For_Clear --> MPTY_request + ECT_request --> Wait_For_Clear_2 + MPTY_request --> Wait_For_Clear_2 +``` + +State transition diagram for Process ICH\_MSC. It starts with a 'Wait\_For\_Clear' state, which branches into two parallel 'ECT request' and 'MPTY request' states. Both of these lead to another 'Wait\_For\_Clear' state. + +Figure 67q: Process ICH\_MSC (sheet 17) + +![State transition diagram for Process ICH_MSC. It shows two main paths: one for handling an incoming call (left side) and one for releasing resources (right side).](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +**Process ICH\_MSC** + +Process in the MSC to handle an incoming (MT) call + +**ICH\_MSC18(18)** + +Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the new MSC + +``` +stateDiagram-v2 + [*] --> Wait_For_MTRF_ACM + state "Wait_For_MTRF_ACM" as Wait_For_MTRF_ACM + state "Address Complete" as Address_Complete + state "Connect" as Connect + state "Send_ACM_If_Required" as Send_ACM_If_Required + state "Wait_For_MTRF_Answer" as Wait_For_MTRF_Answer + state "Answer" as Answer + state "Send_Answer_If_Required" as Send_Answer_If_Required + state "Call_answered := True" as Call_answered + state "Wait_For_MTRF_Clear" as Wait_For_MTRF_Clear + state "Wait_For_MTRF_ACM_Wait_for_MTRF_Answer_Wait_For_MTRF_Clear" as Wait_For_MTRF_ACM_Wait_for_MTRF_Answer_Wait_For_MTRF_Clear + state "Release" as Release + state "Release call resources" as Release_call_resources + state "Idle" as Idle + + Wait_For_MTRF_ACM --> Address_Complete + Wait_For_MTRF_ACM --> Connect + Address_Complete --> Send_ACM_If_Required + Send_ACM_If_Required --> Wait_For_MTRF_Answer + Wait_For_MTRF_Answer --> Answer + Answer --> Send_Answer_If_Required + Send_Answer_If_Required --> Call_answered + Call_answered --> Wait_For_MTRF_Clear + Connect --> Send_Network_Connect_If_Required + Send_Network_Connect_If_Required --> Call_answered + + [*] --> Wait_For_MTRF_ACM_Wait_for_MTRF_Answer_Wait_For_MTRF_Clear + Wait_For_MTRF_ACM_Wait_for_MTRF_Answer_Wait_For_MTRF_Clear --> Release + Release --> Release + Release --> Release + Release --> Release_call_resources + Release_call_resources --> Idle +``` + +State transition diagram for Process ICH\_MSC. It shows two main paths: one for handling an incoming call (left side) and one for releasing resources (right side). + +Figure 67r: Process ICH\_MSC (sheet 18) + +![](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +### Procedure Page\_MS\_MSC + +PAGE\_M1(3) + +Procedure in the MSC to page an MS in a specified location area + +Signals to/from the left are to/from the BSS; +signals to/from the right are to/from the VLR +unless marked otherwise + +``` + + graph TD + Start([ ]) --> D1{Location area ID +known?} + D1 -- No --> N1[Set negative +response: +Unknown LAI] + D1 -- Yes --> D2{Call +still +exists?} + D2 -- No --> N2[Set negative +response: +System +Failure] + D2 -- Yes --> D3{MS +connection +exists?} + D3 -- Yes --> D4{SMS or SS +page?} + D3 -- No --> S1["Clear received:= +False"] + S1 --> D5{Paging via +SGSN possible?} + D5 -- No --> S3[Page] + D5 -- Yes --> S2[Page MS +via SGSN] + S3 --> S4[Start Page +response +timer] + S2 --> S4 + S4 --> S5([Wait_For_ +Page_ +Response]) + D4 -- Yes --> S6[Set access +connection +status] + S6 --> S7["Result:= +Pass"] + S7 --> S8(( )) + D4 -- No --> S9[Request +call status] + S9 --> S10([Wait_For_ +Call_Status]) + N1 --> S11[Page MS +negative +response] + N2 --> S11 + S11 --> S12["Result:= +Fail"] + S12 --> S13(( )) + + subgraph Annotations + direction LR + S3_note[In specified +location area] -.- S3 + S9_note[To Subs_FSM] -.- S9 + end + +``` + +Figure 68a: Procedure Page\_MS\_MSC (sheet 1) + +![Flowchart for Procedure Page_MS_MSC. It starts with 'Wait_For_Call_Status', followed by 'Call status' from 'Subs_FSM'. Then 'Check_MT Multicall_MSC' (referencing TS 23.135). A decision 'Result=Offered?' follows. If 'Yes', it goes to 'Set access connection status' and 'Result:= Pass'. If 'No', it checks 'Result=More calls possible?'. If 'Yes', it goes to 'Set negative response: Busy subscriber' and 'Page MS negative response', leading to 'Result:= Fail'. If 'No', it checks 'Result=not provisioned?'. If 'Yes', it goes to 'Set negative response: Busy subscriber (NDUB)' and 'Page MS negative response', leading to 'Result:= Fail'. If 'No', it checks 'Call in setup?'. If 'Yes', it goes to 'Set negative response: Busy subscriber (NDUB)' and 'Page MS negative response', leading to 'Result:= Fail'. If 'No', it checks 'Call waiting?'. If 'Yes', it goes to 'Set negative response: Busy subscriber (NDUB)' and 'Page MS negative response', leading to 'Result:= Fail'. If 'No', it goes to 'Page MS negative response', leading to 'Result:= Fail'.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +### Procedure Page\_MS\_MSC + +PAGE\_M2(3) + +Procedure in the MSC to page an MS in a specified location area + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; Start([Wait_For_Call_Status]) --> CallStatus{Call status}; CallStatus --- SubsFSM[From process Subs_FSM]; CallStatus --> CheckMT[Check_MT Multicall_MSC]; CheckMT --- TS23135[See TS 23.135]; CheckMT --> ResultOffered{Result=Offered?}; ResultOffered -- Yes --> SetAccess[Set access connection status]; ResultOffered -- No --> MoreCallsPossible{Result=More calls possible?}; MoreCallsPossible -- Yes --> SetBusy[Set negative response: Busy subscriber]; MoreCallsPossible -- No --> NotProvisioned{Result=not provisioned?}; NotProvisioned -- Yes --> SetBusyNDUB[Set negative response: Busy subscriber (NDUB)]; NotProvisioned -- No --> CallInSetup{Call in setup?}; CallInSetup -- Yes --> SetBusyNDUB; CallInSetup -- No --> CallWaiting{Call waiting?}; CallWaiting -- Yes --> SetBusyNDUB; CallWaiting -- No --> PageMS[Page MS negative response]; SetBusy --> MoreCallsPossible; SetBusyNDUB --> MoreCallsPossible; SetBusy --> PageMS; SetBusyNDUB --> PageMS; SetAccess --> ResultPass[Result:= Pass]; PageMS --> ResultFail[Result:= Fail]; ResultPass --> EndPass(( )); ResultFail --> EndFail(( )); +``` + +Flowchart for Procedure Page\_MS\_MSC. It starts with 'Wait\_For\_Call\_Status', followed by 'Call status' from 'Subs\_FSM'. Then 'Check\_MT Multicall\_MSC' (referencing TS 23.135). A decision 'Result=Offered?' follows. If 'Yes', it goes to 'Set access connection status' and 'Result:= Pass'. If 'No', it checks 'Result=More calls possible?'. If 'Yes', it goes to 'Set negative response: Busy subscriber' and 'Page MS negative response', leading to 'Result:= Fail'. If 'No', it checks 'Result=not provisioned?'. If 'Yes', it goes to 'Set negative response: Busy subscriber (NDUB)' and 'Page MS negative response', leading to 'Result:= Fail'. If 'No', it checks 'Call in setup?'. If 'Yes', it goes to 'Set negative response: Busy subscriber (NDUB)' and 'Page MS negative response', leading to 'Result:= Fail'. If 'No', it checks 'Call waiting?'. If 'Yes', it goes to 'Set negative response: Busy subscriber (NDUB)' and 'Page MS negative response', leading to 'Result:= Fail'. If 'No', it goes to 'Page MS negative response', leading to 'Result:= Fail'. + +Figure 68b: Procedure Page\_MS\_MSC (sheet 2) + +![Flowchart for Procedure Page_MS_MSC (sheet 3). The process starts with 'Wait_For_Page_Response' and branches into four main paths: 'MS connection established', 'Release' (From GMSC), 'Page response timer expired', and 'CM Service Request' (For circuit-switched call). Each path leads to decision diamonds like 'Clear received' or 'Set negative response' (Absent Subscriber or NDUB), and finally to result states: 'Pass', 'Aborted', or 'Fail', returning to 'Wait_For_Page_Response'.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +**Procedure Page\_MS\_MSC** **PAGE\_M3(3)** + +Procedure in the MSC to page an MS in a specified location area + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` + +graph TD + Start([Wait_For_Page_Response]) --> MS_Conn_Established{MS connection established} + Start --> Release[Release] + Release --- From_GMSC[From GMSC] + Start --> Timer_Expired{Page response timer expired} + Start --> CM_Service_Request[CM Service Request] + CM_Service_Request --- For_Circuit_Switched[For circuit-switched call] + + MS_Conn_Established --> Clear_Rec_1{Clear received} + Clear_Rec_1 -- True --> Set_Access_Status[Set access connection status] + Set_Access_Status --> Result_Pass[Result:= Pass] + Result_Pass --> End1(( )) + + Clear_Rec_1 -- False --> Release_Transaction{Release transaction} + Release_Transaction --> Result_Aborted_1[Result:= Aborted] + Result_Aborted_1 --> End2(( )) + + Release --> Abort[Abort] + Abort --> Clear_Rec_2[Clear received:= True] + Clear_Rec_2 --> End3([Wait_For_Page_Response]) + + Timer_Expired --> Clear_Rec_3{Clear received} + Clear_Rec_3 -- True --> Result_Aborted_2[Result:= Aborted] + Result_Aborted_2 --> End4(( )) + + Clear_Rec_3 -- False --> Set_Neg_Absent[Set negative response: Absent Subscriber] + Set_Neg_Absent --> Page_Neg_Response_1{Page MS negative response} + Page_Neg_Response_1 --> Result_Fail_1[Result:= Fail] + Result_Fail_1 --> End5(( )) + + CM_Service_Request --> CM_Service_Request_2[CM Service Request] + CM_Service_Request_2 --- To_Process_OCH[To process OCH_MSC] + CM_Service_Request_2 --> Clear_Rec_4{Clear received} + Clear_Rec_4 -- True --> Result_Aborted_3[Result:= Aborted] + Result_Aborted_3 --> End6(( )) + + Clear_Rec_4 -- False --> Set_Neg_NDUB[Set negative response: Busy Subscriber (NDUB)] + Set_Neg_NDUB --> Page_Neg_Response_2{Page MS negative response} + Page_Neg_Response_2 --> Result_Fail_2[Result:= Fail] + Result_Fail_2 --> End7(( )) + +``` + +Flowchart for Procedure Page\_MS\_MSC (sheet 3). The process starts with 'Wait\_For\_Page\_Response' and branches into four main paths: 'MS connection established', 'Release' (From GMSC), 'Page response timer expired', and 'CM Service Request' (For circuit-switched call). Each path leads to decision diamonds like 'Clear received' or 'Set negative response' (Absent Subscriber or NDUB), and finally to result states: 'Pass', 'Aborted', or 'Fail', returning to 'Wait\_For\_Page\_Response'. + +Figure 68c: Procedure Page\_MS\_MSC (sheet 3) + +![Flowchart for Procedure Page_MS_MSC. The process starts with 'Wait_For_Page_Response', followed by 'Cancel Location'. A decision 'Clear received' follows. If 'True', it goes to 'Release transaction' and 'Result:= Aborted'. If 'False', it goes to 'Set negative response: Location Cancelled', then 'Page MS negative response', 'Result:= Fail', and finally an end symbol.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +**Procedure Page\_MS\_MSC** + +**PAGE\_M 4(4)** + +Procedure in the MSC to page an MS in a specified location area + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; A[Wait_For_Page_Response] --> B[Cancel Location]; B --> C{Clear received}; C -- True --> D[Release transaction]; C -- False --> E[Set negative response: Location Cancelled]; E --> F[Page MS negative response]; F --> G[Result:= Fail]; D --> H[Result:= Aborted]; G --> I(( )); H --> J(( )); +``` + +includes the following parameters if received in the Cancel Location message from the VLR: + +- MTRF Supported And Authorized flag +- MTRF Supported And Not Authorized flag +- new VLR number +- new LMSI + +Flowchart for Procedure Page\_MS\_MSC. The process starts with 'Wait\_For\_Page\_Response', followed by 'Cancel Location'. A decision 'Clear received' follows. If 'True', it goes to 'Release transaction' and 'Result:= Aborted'. If 'False', it goes to 'Set negative response: Location Cancelled', then 'Page MS negative response', 'Result:= Fail', and finally an end symbol. + +Figure 68d: Procedure Page\_MS\_MSC (sheet 4) + +![Flowchart for Procedure Search_For_MS_MSC. It starts with an oval connector, followed by a decision 'Call still exists?'. If 'No', it goes to 'Set negative response: System Failure' and then to an exit circle. If 'Yes', it goes to 'MS connection exists?'. If 'No', it goes to 'Clear received:= False'. If 'Yes', it goes to 'SMS or SS page?'. From 'Clear received:= False', it goes to 'Paging via SGSN possible?'. If 'No', it goes to 'Search for MS via SGSN'. If 'Yes', it goes to 'Page'. From 'SMS or SS page?', if 'Yes', it goes to 'Set access connection status' and then to 'Result:= Pass' and an exit circle. If 'No', it goes to 'Request call status', which leads to 'To Subs_FSM' and 'Wait_For_Call_Status'. From 'Page', it goes to 'Start Page response timer' and then to 'Wait_For_Search_Response'. A note 'In all location areas or in PgA if PgA received and supported' is next to 'Page'.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +**Procedure Search\_For\_MS\_MSC** **SRCH\_M1(4)** + +Procedure in the MSC to search for an MS (page in all location areas) + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` + +graph TD + Start([ ]) --> CallExists{Call still exists?} + CallExists -- No --> SetNeg[Set negative response: +System Failure] + CallExists -- Yes --> MSConn{MS connection exists?} + MSConn -- No --> ClearRec[Clear received:= +False] + MSConn -- Yes --> SMSorSS{SMS or SS page?} + ClearRec --> PagingViaSGSN{Paging via SGSN possible?} + PagingViaSGSN -- No --> SearchMSviaSGSN{Search for MS +via SGSN} + PagingViaSGSN -- Yes --> Page{Page} + SearchMSviaSGSN --> Page + Page --> StartPage[Start Page response +timer] + StartPage --> WaitSearch[Wait_For_ +Search_ +Response] + SMSorSS -- Yes --> SetAccess[Set access +connection +status] + SetAccess --> ResultPass[Result:= +Pass] + ResultPass --> ExitPass(( )) + SMSorSS -- No --> RequestCall[Request +call status] + RequestCall --> ToSubs[To Subs_FSM] + RequestCall --> WaitCall[Wait_For_ +Call_Status] + SetNeg --> SearchNeg{Search For +MS negative +response} + SearchNeg --> ResultFail[Result:= +Fail] + ResultFail --> ExitFail(( )) + +``` + +In all location areas or in PgA if PgA received and supported + +Flowchart for Procedure Search\_For\_MS\_MSC. It starts with an oval connector, followed by a decision 'Call still exists?'. If 'No', it goes to 'Set negative response: System Failure' and then to an exit circle. If 'Yes', it goes to 'MS connection exists?'. If 'No', it goes to 'Clear received:= False'. If 'Yes', it goes to 'SMS or SS page?'. From 'Clear received:= False', it goes to 'Paging via SGSN possible?'. If 'No', it goes to 'Search for MS via SGSN'. If 'Yes', it goes to 'Page'. From 'SMS or SS page?', if 'Yes', it goes to 'Set access connection status' and then to 'Result:= Pass' and an exit circle. If 'No', it goes to 'Request call status', which leads to 'To Subs\_FSM' and 'Wait\_For\_Call\_Status'. From 'Page', it goes to 'Start Page response timer' and then to 'Wait\_For\_Search\_Response'. A note 'In all location areas or in PgA if PgA received and supported' is next to 'Page'. + +Figure 69a: Procedure Search\_For\_MS\_MSC (sheet 1) + +![Flowchart for Procedure Search_For_MS_MSC. It starts with 'Wait_For_Call_Status', followed by 'Call status' from 'Subs_FSM'. Then 'Check_MT Multicall_MSC' (referencing TS 23.135). A decision 'Result=Offered?' follows. If 'Yes', it goes to 'Set access connection status' and 'Result:= Pass'. If 'No', it checks 'Result=More calls possible?'. If 'Yes', it goes to 'Set negative response: Busy Subscriber' and 'More calls possible'. If 'No', it checks 'Result=not provisioned'. If 'Yes', it goes to 'Set negative response: Busy Subscriber (NDUB)'. If 'No', it checks 'Call in setup?'. If 'Yes', it goes to 'Set negative response: Busy Subscriber (NDUB)'. If 'No', it checks 'Call waiting?'. If 'Yes', it goes to 'Set negative response: Busy Subscriber (NDUB)'. If 'No', it goes to 'Set negative response: Busy Subscriber' and 'More calls possible'. All negative response paths lead to 'Search For MS negative response', which leads to 'Result:= Fail'. Both 'Result:= Fail' and 'Result:= Pass' lead to exit symbols.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +### Procedure Search\_For\_MS\_MSC + +SRCH\_M2(3) + +Procedure in the MSC to search for an MS (page in all location areas) + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; Start([Wait_For_Call_Status]) --> CallStatus{Call status}; CallStatus -- "From process Subs_FSM" --> CallStatus; CallStatus --> CheckMT[Check_MT Multicall_MSC]; CheckMT -- "See TS 23.135" --> CheckMT; CheckMT --> ResultOffered{Result=Offered?}; ResultOffered -- Yes --> SetAccess[Set access connection status]; ResultOffered -- No --> ResultMoreCalls{Result=More calls possible?}; ResultMoreCalls -- Yes --> SetNegative1[Set negative response: Busy Subscriber]; ResultMoreCalls -- No --> ResultNotProvisioned{Result=not provisioned?}; ResultNotProvisioned -- Yes --> CallInSetup{Call in setup?}; ResultNotProvisioned -- No --> CallWaiting{Call waiting?}; CallInSetup -- Yes --> SetNegative2[Set negative response: Busy Subscriber (NDUB)]; CallInSetup -- No --> CallWaiting; CallWaiting -- Yes --> SetNegative2; CallWaiting -- No --> SetNegative1; SetNegative1 -- "More calls possible" --> SearchForMS[Search For MS negative response]; SetNegative2 --> SearchForMS; SearchForMS --> ResultFail[Result:= Fail]; SetAccess --> ResultPass[Result:= Pass]; ResultFail --> Exit1((X)); ResultPass --> Exit2((X)); +``` + +Flowchart for Procedure Search\_For\_MS\_MSC. It starts with 'Wait\_For\_Call\_Status', followed by 'Call status' from 'Subs\_FSM'. Then 'Check\_MT Multicall\_MSC' (referencing TS 23.135). A decision 'Result=Offered?' follows. If 'Yes', it goes to 'Set access connection status' and 'Result:= Pass'. If 'No', it checks 'Result=More calls possible?'. If 'Yes', it goes to 'Set negative response: Busy Subscriber' and 'More calls possible'. If 'No', it checks 'Result=not provisioned'. If 'Yes', it goes to 'Set negative response: Busy Subscriber (NDUB)'. If 'No', it checks 'Call in setup?'. If 'Yes', it goes to 'Set negative response: Busy Subscriber (NDUB)'. If 'No', it checks 'Call waiting?'. If 'Yes', it goes to 'Set negative response: Busy Subscriber (NDUB)'. If 'No', it goes to 'Set negative response: Busy Subscriber' and 'More calls possible'. All negative response paths lead to 'Search For MS negative response', which leads to 'Result:= Fail'. Both 'Result:= Fail' and 'Result:= Pass' lead to exit symbols. + +Figure 69b: Procedure Search\_For\_MS\_MSC (sheet 2) + +![Flowchart for Procedure Search_For_MS_MSC. The process starts with 'Wait_For_Search_Response' leading to a horizontal line. From this line, four main paths emerge: 1) 'MS connection established' -> 'Clear received' (True leads to 'Release transaction' -> 'Result:= Aborted'; False leads to 'Search For MS ack' -> 'Set access connection status' -> 'Result:= Pass'). 2) 'Release' (From GMSC) -> 'Abort' -> 'Clear received:= True' -> 'Wait_For_Search_Response'. 3) 'Page response timer expired' -> 'Clear received' (True leads to 'Result:= Aborted'; False leads to 'Set negative response: Absent Subscriber' -> 'Search For MS negative response' -> 'Result:= Fail'). 4) 'CM Service Request' (For circuit-switched call) -> 'CM Service Request' (To process OCH_MSC) -> 'Clear received' (True leads to 'Result:= Aborted'; False leads to 'Set negative response: Busy Subscriber (NDUB)' -> 'Search For MS negative response' -> 'Result:= Fail'). All terminal points lead to a circle with an 'X'.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +### Procedure Search\_For\_MS\_MSC + +SRCH\_M3(3) + +Procedure in the MSC to search for an MS (page in all location areas) + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; Start([Wait_For_Search_Response]) --> Junction(( )); Junction --> MS_Conn[MS connection established]; Junction --> Release[Release
From GMSC]; Junction --> Timer_Exp[Page response timer expired]; Junction --> CM_SReq_1[CM Service Request
For circuit-switched call]; MS_Conn --> CR_1{Clear received}; CR_1 -- True --> RT{Release transaction}; CR_1 -- False --> SFMA{Search For MS ack}; RT --> RA[Result:= Aborted]; SFMA --> SC[Set access connection status]; SC --> RP[Result:= Pass]; Release --> Abort[Abort]; Abort --> CRT[Clear received:= True]; CRT --> WFR([Wait_For_Search_Response]); Timer_Exp --> CR_2{Clear received}; CR_2 -- True --> RA2[Result:= Aborted]; CR_2 -- False --> SNAS[Set negative response:
Absent Subscriber]; SNAS --> SFMR{Search For MS negative response}; SFMR --> RF1[Result:= Fail]; CM_SReq_1 --> CM_SReq_2[CM Service Request
To process OCH_MSC]; CM_SReq_2 --> CR_3{Clear received}; CR_3 -- True --> RA3[Result:= Aborted]; CR_3 -- False --> NSBS[Set negative response:
Busy Subscriber (NDUB)]; NSBS --> SFMR2{Search For MS negative response}; SFMR2 --> RF2[Result:= Fail]; +``` + +Flowchart for Procedure Search\_For\_MS\_MSC. The process starts with 'Wait\_For\_Search\_Response' leading to a horizontal line. From this line, four main paths emerge: 1) 'MS connection established' -> 'Clear received' (True leads to 'Release transaction' -> 'Result:= Aborted'; False leads to 'Search For MS ack' -> 'Set access connection status' -> 'Result:= Pass'). 2) 'Release' (From GMSC) -> 'Abort' -> 'Clear received:= True' -> 'Wait\_For\_Search\_Response'. 3) 'Page response timer expired' -> 'Clear received' (True leads to 'Result:= Aborted'; False leads to 'Set negative response: Absent Subscriber' -> 'Search For MS negative response' -> 'Result:= Fail'). 4) 'CM Service Request' (For circuit-switched call) -> 'CM Service Request' (To process OCH\_MSC) -> 'Clear received' (True leads to 'Result:= Aborted'; False leads to 'Set negative response: Busy Subscriber (NDUB)' -> 'Search For MS negative response' -> 'Result:= Fail'). All terminal points lead to a circle with an 'X'. + +Figure 69c: Procedure Search\_For\_MS\_MSC (sheet 3) + +![Flowchart for Procedure Search_For_MS_MSC. The process starts with 'Wait_For_Search_Response', followed by 'Cancel Location'. A decision 'Clear received' follows. If 'True', it goes to 'Release transaction' and ends with 'Result:= Aborted'. If 'False', it goes to 'Set negative response: Location Cancelled', then 'Search for MS negative response', and ends with 'Result:= Fail'. A note on the left lists parameters for the negative response: - MTRF Supported And Authorized flag, - MTRF Supported And Not Authorized flag, - new VLR number, - new LMSI.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +**Procedure Search\_For\_MS\_MSC** + +**SRCH\_M4(4)** + +Procedure in the MSC to search for an MS (page in all location areas) + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; A[Wait_For_Search_Response] --> B[Cancel Location]; B --> C{Clear received}; C -- True --> D[Release transaction]; C -- False --> E[Set negative response: Location Cancelled]; E --> F[Search for MS negative response]; F --> G[Result:= Fail]; D --> H[Result:= Aborted]; G --> I(( )); H --> J(( )); +``` + +includes the following parameters if received in the **Cancel Location** message from the VLR: + +- MTRF Supported And Authorized flag +- MTRF Supported And Not Authorized flag +- new VLR number +- new LMSI + +Flowchart for Procedure Search\_For\_MS\_MSC. The process starts with 'Wait\_For\_Search\_Response', followed by 'Cancel Location'. A decision 'Clear received' follows. If 'True', it goes to 'Release transaction' and ends with 'Result:= Aborted'. If 'False', it goes to 'Set negative response: Location Cancelled', then 'Search for MS negative response', and ends with 'Result:= Fail'. A note on the left lists parameters for the negative response: - MTRF Supported And Authorized flag, - MTRF Supported And Not Authorized flag, - new VLR number, - new LMSI. + +Figure 69d: Procedure Search\_For\_MS\_MSC (sheet 4) + +![Flowchart for Procedure Complete_Call_In_MSC](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +### Procedure Complete\_Call\_In\_MSC + +CCI\_MSC1(11) + +Procedure in the MSC to complete an MT call on request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; Start([Start]) --> SetCLIP[Set_CLIP_Info_MSC]; SetCLIP --> DeriveBC[Derive required PLMN BC]; DeriveBC --> TS29007[See TS 29.007]; DeriveBC --> Setup{Setup}; Setup --> UUS1[UUS1_ICH_UUS1_Explicit_Active]; UUS1 --> TS23087[See TS 23.087]; UUS1 --> CCBS[CCBS_Report_Not_Idle]; CCBS --> TS23093[See TS 23.093]; CCBS --> WaitForSetup[Wait_For_Setup_Response]; WaitForSetup --> SetupFailure{Setup failure}; SetupFailure --> NegativeResponse[Set negative response: Absent Subscriber]; NegativeResponse --> CompleteNeg[Complete Call negative response]; CompleteNeg --> ResultFail[Result= Fail]; SetupFailure --> IntRelease[Int_Release_Call]; IntRelease --> GsmSSF[From gsmSSF]; ResultFail --> End((End)); +``` + +The flowchart illustrates the 'Procedure Complete\_Call\_In\_MSC'. It begins with a start symbol, followed by 'Set\_CLIP\_Info\_MSC'. Next is 'Derive required PLMN BC', which references 'See TS 29.007'. This leads to a decision diamond 'Setup'. If 'Setup' fails, it leads to 'Int\_Release\_Call' (from gsmSSF) and then to 'Result= Fail'. If 'Setup' succeeds, it leads to 'UUS1\_ICH\_UUS1\_Explicit\_Active', which references 'See TS 23.087'. This is followed by 'CCBS\_Report\_Not\_Idle', which references 'See TS 23.093'. Both lead to 'Wait\_For\_Setup\_Response'. From 'Wait\_For\_Setup\_Response', if 'Setup failure' occurs, it leads to 'Set negative response: Absent Subscriber', then 'Complete Call negative response', and finally 'Result= Fail'. If no failure, the process continues to the end symbol. + +Flowchart for Procedure Complete\_Call\_In\_MSC + +Figure 70a: Procedure Complete\_Call\_In\_MSC (sheet 1) + +![Flowchart for Procedure Complete_Call_In_MSC. It starts with 'Wait_For_Setup_Response', followed by 'Call Confirmed'. A decision 'Multicall supported in MSC?' leads to 'Establish_Terminating_TCH_If_Required' (No) or 'Establish_Terminating_TCH_Multicall' (Yes, See TS 23.135). Both lead to 'Result=Fail?'. If 'Yes', it goes to 'CAMEL_MT_GMSC_DISC4' (See TS 23.078). If 'No', it goes to 'Result=Aborted?'. If 'Yes', it goes to 'Abort'. If 'No', it goes to 'Result=Rejected?'. If 'Yes', it goes to connector '4'. If 'No', it goes to 'CAMEL_MT_GMSC_DISC6' (See TS 23.078), then 'OCBS_ICH_MSC_Report_Failure' (See TS 23.093), then 'Result:=Aborted', then connector 'X'. From 'CAMEL_MT_GMSC_DISC4', it goes to 'Result=Reconnect?'. If 'Yes', it goes to 'Result:=Reconnect', then connector 'X'. If 'No', it goes to 'Set negative response: Radio congestion', then 'Complete Call negative response', then 'Result:=Fail', then connector 'X'.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +**Procedure Complete\_Call\_In\_MSC** **CCI\_MSC2(11)** + +Procedure in the MSC to complete an MT call on request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR + +``` + +graph TD + Start([Wait_For_Setup_Response]) --> CallConfirmed{{Call Confirmed}} + CallConfirmed --> Multicall{Multicall supported in MSC?} + Multicall -- No --> EstablishTCH[Establish_Terminating_TCH_If_Required] + Multicall -- Yes --> EstablishTCHMulticall[Establish_Terminating_TCH_Multicall] + EstablishTCHMulticall -.-> TS23135[See TS 23.135] + EstablishTCH --> ResultFail{Result=Fail?} + EstablishTCHMulticall --> ResultFail + ResultFail -- Yes --> CAMEL_DISC4[CAMEL_MT_GMSC_DISC4] + CAMEL_DISC4 -.-> TS23078_1[See TS 23.078] + ResultFail -- No --> ResultAborted{Result=Aborted?} + ResultAborted -- Yes --> Abort[/Abort/] + ResultAborted -- No --> ResultRejected{Result=Rejected?} + ResultRejected -- Yes --> Connector4((4)) + ResultRejected -- No --> CAMEL_DISC6[CAMEL_MT_GMSC_DISC6] + CAMEL_DISC6 -.-> TS23078_2[See TS 23.078] + CAMEL_DISC6 --> OCBS_Report[OCBS_ICH_MSC_Report_Failure] + OCBS_Report -.-> TS23093[See TS 23.093] + OCBS_Report --> ResultAbortedFinal[Result:=Aborted] + ResultAbortedFinal --> ConnectorX1((X)) + CAMEL_DISC4 --> ResultReconnect{Result=Reconnect?} + ResultReconnect -- Yes --> ResultReconnectFinal[Result:=Reconnect] + ResultReconnectFinal --> ConnectorX2((X)) + ResultReconnect -- No --> SetNeg[Set negative response: Radio congestion] + SetNeg --> CompleteNeg[Complete Call negative response] + CompleteNeg --> ResultFailFinal[Result:=Fail] + ResultFailFinal --> ConnectorX3((X)) + +``` + +Flowchart for Procedure Complete\_Call\_In\_MSC. It starts with 'Wait\_For\_Setup\_Response', followed by 'Call Confirmed'. A decision 'Multicall supported in MSC?' leads to 'Establish\_Terminating\_TCH\_If\_Required' (No) or 'Establish\_Terminating\_TCH\_Multicall' (Yes, See TS 23.135). Both lead to 'Result=Fail?'. If 'Yes', it goes to 'CAMEL\_MT\_GMSC\_DISC4' (See TS 23.078). If 'No', it goes to 'Result=Aborted?'. If 'Yes', it goes to 'Abort'. If 'No', it goes to 'Result=Rejected?'. If 'Yes', it goes to connector '4'. If 'No', it goes to 'CAMEL\_MT\_GMSC\_DISC6' (See TS 23.078), then 'OCBS\_ICH\_MSC\_Report\_Failure' (See TS 23.093), then 'Result:=Aborted', then connector 'X'. From 'CAMEL\_MT\_GMSC\_DISC4', it goes to 'Result=Reconnect?'. If 'Yes', it goes to 'Result:=Reconnect', then connector 'X'. If 'No', it goes to 'Set negative response: Radio congestion', then 'Complete Call negative response', then 'Result:=Fail', then connector 'X'. + +Figure 70b: Procedure Complete\_Call\_In\_MSC (sheet 2) + +![Flowchart for Procedure Complete_Call_In_MSC. It starts with 'Wait_For_Alerting' leading to 'Alerting' and 'Connect' paths. The 'Alerting' path involves 'UUS_ICH_Check_Support', 'CCBS_ICH_MSC_Report_Success', 'NRCT_provided?', 'Start No Reply Call Timer', 'CAMEL_Start_TNRy', 'Send_ACM_If_Required', 'UTU2Cnt:=0', 'CAMEL_MT_MSC_ALERTING', and 'Result?' leading to 'Answer' (A), 'Release' (To GMSC), or 'Reconnect'. The 'Connect' path involves 'UUS_ICH_Check_Support', 'CCBS_ICH_MSC_Report_Success', 'Establish_Terminating_TCH_Multicall', 'Result=Pass?', 'Result=Aborted?', 'CAMEL_MT_GMSC_DISC4', 'Result=Reconnect?', 'Release', 'Abort', and 'CAMEL_MT_GMSC_DISC6'. Various 'Result=' states lead to terminal symbols.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +### Procedure Complete\_Call\_In\_MSC + +CCI\_MSC3(11) + +Procedure in the MSC to complete an MT call on request from the VLR + +Wait\_For\_Alerting + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` + + graph TD + Start((Wait_For_Alerting)) --> Alerting[Alerting] + Start --> Connect[Connect] + + Alerting --> UUS_ICH_CS[UUS_ICH_Check_Support] + UUS_ICH_CS --> Result_Pass1{Result=Pass?} + + Result_Pass1 -- No --> Junction1(( )) + Junction1 --> Junction2(( )) + + Result_Pass1 -- Yes --> CCBS_ICH_RS[CCBS_ICH_MSC_Report_Success] + CCBS_ICH_RS --> NRCT_Provided{NRCT_provided?} + + NRCT_Provided -- No --> Junction2 + NRCT_Provided -- Yes --> Start_NRT[Start No Reply Call Timer] + + Start_NRT --> CAMEL_Start_TNRy[CAMEL_Start_TNRy] + CAMEL_Start_TNRy --> Send_ACM[Send_ACM_If_Required] + + Send_ACM --> UTU2Cnt[UTU2Cnt:=0] + UTU2Cnt --> CAMEL_MT_MSC_ALERTING[CAMEL_MT_MSC_ALERTING] + + CAMEL_MT_MSC_ALERTING --> Result1{Result?} + + Result1 -- Answer --> A((A)) + Result1 -- Fail --> Release1[Release] + Release1 --> To_GMSC[To GMSC] + + Result1 -- Pass --> Wait_for_Answer[Wait_for_Answer] + + Release1 -- Release --> Result_Aborted1[Result= Aborted] + + Result1 -- Reconnect --> Junction2 + + Connect --> UUS_ICH_CS2[UUS_ICH_Check_Support] + UUS_ICH_CS2 --> Result_Pass2{Result=Pass?} + + Result_Pass2 -- No --> Junction2 + Result_Pass2 -- Yes --> CCBS_ICH_RS2[CCBS_ICH_MSC_Report_Success] + + CCBS_ICH_RS2 --> Establish_TCH[Establish_Terminating_TCH_Multicall] + + Establish_TCH --> Result_Pass3{Result=Pass?} + + Result_Pass3 -- No --> Junction3(( )) + + Result_Pass3 -- Yes --> Result_Aborted2{Result=Aborted?} + + Result_Aborted2 -- Yes --> Abort1[Abort] + + Result_Aborted2 -- No --> CAMEL_MT_GMSC_DISC4[CAMEL_MT_GMSC_DISC4] + + CAMEL_MT_GMSC_DISC4 --> Result_Reconnect{Result=Reconnect?} + + Result_Reconnect -- Yes --> Junction4(( )) + + Result_Reconnect -- No --> Release2[Release] + + Release2 --> Abort2[Abort] + + Abort2 --> CAMEL_MT_GMSC_DISC6[CAMEL_MT_GMSC_DISC6] + + CAMEL_MT_GMSC_DISC6 --> Result_Aborted3[Result= Aborted] + + Release2 -- Release --> Result_Aborted2 + + Result_Aborted2 -- No --> Junction4 + + Junction4 --> Result_Reconnect2[Result= Reconnect] + + Result_Aborted1 --> End1(( )) + Result_Aborted2 --> End2(( )) + Result_Reconnect2 --> End3(( )) + Result_Aborted3 --> End4(( )) + +``` + +Flowchart for Procedure Complete\_Call\_In\_MSC. It starts with 'Wait\_For\_Alerting' leading to 'Alerting' and 'Connect' paths. The 'Alerting' path involves 'UUS\_ICH\_Check\_Support', 'CCBS\_ICH\_MSC\_Report\_Success', 'NRCT\_provided?', 'Start No Reply Call Timer', 'CAMEL\_Start\_TNRy', 'Send\_ACM\_If\_Required', 'UTU2Cnt:=0', 'CAMEL\_MT\_MSC\_ALERTING', and 'Result?' leading to 'Answer' (A), 'Release' (To GMSC), or 'Reconnect'. The 'Connect' path involves 'UUS\_ICH\_Check\_Support', 'CCBS\_ICH\_MSC\_Report\_Success', 'Establish\_Terminating\_TCH\_Multicall', 'Result=Pass?', 'Result=Aborted?', 'CAMEL\_MT\_GMSC\_DISC4', 'Result=Reconnect?', 'Release', 'Abort', and 'CAMEL\_MT\_GMSC\_DISC6'. Various 'Result=' states lead to terminal symbols. + +Figure 70c: Procedure Complete\_Call\_In\_MSC (sheet 3) + +![Flowchart for Procedure Complete_Call_In_MSC. It starts at connector 3, goes through Handle_AoC_MT_MSC, then a decision 'Result= Pass?'. If 'No', it goes to 'CAMEL MT_GMSC_DISC4' (referencing TS 23.078) and then to connector 2. If 'Yes', it goes to 'Connect ack', then 'CAMEL MT_GMSC_ANSWER' (referencing TS 23.078), then a decision 'Result?'. From 'Result?', 'Fail' leads to 'Release' (To GMSC) and 'Result= Aborted'; 'Release' leads to 'Release' (To GMSC) and 'Result= Pass'; 'Reconnect' leads to connector 2. From connector 2, it goes to 'Set cause', then 'Release' (To GMSC), 'Abort', and 'Result= Aborted'. From 'Result= Reconnect' (from 'Result= Reconnect?' decision), it goes to 'Result= Reconnect' and then to a connector.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +### Procedure Complete\_Call\_In\_MSC + +CCI\_MSC4(11) + +Procedure in the MSC to complete an MT call on request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; 3((3)) --> HandleAoC[Handle_AoC_MT_MSC]; HandleAoC --> Pass{Result= Pass?}; Pass -- No --> Disc4[CAMEL MT_GMSC_DISC4]; Disc4 -- "See TS 23.078" --> Disc4; Disc4 --> 2((2)); Pass -- Yes --> ConnectAck{Connect ack}; ConnectAck --> Answer[CAMEL MT_GMSC_ANSWER]; Answer -- "See TS 23.078" --> Answer; Answer --> Result{Result?}; Result -- Fail --> Release1{Release}; Release1 -- "To GMSC" --> Release1; Release1 --> Aborted1[Result= Aborted]; Aborted1 --> X1((X)); Result -- Release --> Release2{Release}; Release2 -- "To GMSC" --> Release2; Release2 --> Pass2[Result= Pass]; Pass2 --> X2((X)); Result -- Reconnect --> 2; 2 --> SetCause[Set cause]; SetCause --> Release3{Release}; Release3 -- "To GMSC" --> Release3; Release3 --> Abort[Abort]; Abort --> Aborted2[Result= Aborted]; Aborted2 --> X3((X)); Pass -- Yes --> SetCOL[Set_COL_Presentation_Indicator_MSC]; SetCOL --> SendNetwork[Send_Network_Connect_If_Required]; SendNetwork -- "To GMSC" --> SendNetwork; SendNetwork --> CompleteAck{Complete Call ack}; CompleteAck --> Reconnect{Result= Reconnect?}; Reconnect -- No --> 2; Reconnect -- Yes --> ReconnectRes[Result= Reconnect]; ReconnectRes --> X4((X)); +``` + +Flowchart for Procedure Complete\_Call\_In\_MSC. It starts at connector 3, goes through Handle\_AoC\_MT\_MSC, then a decision 'Result= Pass?'. If 'No', it goes to 'CAMEL MT\_GMSC\_DISC4' (referencing TS 23.078) and then to connector 2. If 'Yes', it goes to 'Connect ack', then 'CAMEL MT\_GMSC\_ANSWER' (referencing TS 23.078), then a decision 'Result?'. From 'Result?', 'Fail' leads to 'Release' (To GMSC) and 'Result= Aborted'; 'Release' leads to 'Release' (To GMSC) and 'Result= Pass'; 'Reconnect' leads to connector 2. From connector 2, it goes to 'Set cause', then 'Release' (To GMSC), 'Abort', and 'Result= Aborted'. From 'Result= Reconnect' (from 'Result= Reconnect?' decision), it goes to 'Result= Reconnect' and then to a connector. + +Figure 70d: Procedure Complete\_Call\_In\_MSC (sheet 4) + +![State transition diagram for Procedure Complete_Call_In_MSC. The process starts at 'Wait_For_Alerting', leading to a junction point. From the junction, three paths emerge: 'Alerting failure' leading to 'CAMEL_MT_GMSC_DISC4'; '1' leading to 'Release transaction' -> 'Set cause' -> junction; and 'CD_Request' leading to 'CCBS_ICH_MSC_Report_Success'. 'CAMEL_MT_GMSC_DISC4' leads to a decision 'Result=Reconnect?'. If 'Yes', it goes to 'Result=Reconnect' -> exit. If 'No', it goes to 'CCBS_ICH_MSC_Report_Failure' -> 'Abort' -> 'Release' -> 'Result=Aborted' -> exit. 'CCBS_ICH_MSC_Report_Failure' also has a reference to 'See TS 23.093'. 'Release' has a reference to 'To GMSC'. 'CCBS_ICH_MSC_Report_Success' leads to 'Handling_CD_MSC' -> 'Complete Call negative response' -> 'Result=Fail' -> exit. 'Handling_CD_MSC' has a reference to 'See TS 23.072'. 'CCBS_ICH_MSC_Report_Success' also has a reference to 'See TS 23.093'. 'CAMEL_MT_GMSC_DISC4' has a reference to 'See TS 23.078'.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +### Procedure Complete\_Call\_In\_MSC + +CCI\_MSC5(11) + +Procedure in the MSC to complete an MT call on request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +stateDiagram-v2 + [*] --> Wait_For_Alerting + state "Wait_For_Alerting" as Wait_For_Alerting + Wait_For_Alerting --> Junction + Junction --> Alerting_failure + Junction --> One + Junction --> CD_Request + Alerting_failure --> CAMEL_MT_GMSC_DISC4 + One --> Release_transaction + Release_transaction --> Set_cause + Set_cause --> Junction + CD_Request --> CCBS_ICH_MSC_Report_Success + CAMEL_MT_GMSC_DISC4 --> Result_Reconnect_Q{Result=Reconnect?} + Result_Reconnect_Q -- Yes --> Result_Reconnect + Result_Reconnect_Q -- No --> CCBS_ICH_MSC_Report_Failure + CCBS_ICH_MSC_Report_Failure --> Abort + Abort --> Release + Release --> Result_Aborted + CCBS_ICH_MSC_Report_Success --> Handling_CD_MSC + Handling_CD_MSC --> Complete_Call_negative_response + Complete_Call_negative_response --> Result_Fail + Result_Reconnect --> Exit1(( )) + Result_Aborted --> Exit2(( )) + Result_Fail --> Exit3(( )) + Note right of CAMEL_MT_GMSC_DISC4: See TS 23.078 + Note right of CCBS_ICH_MSC_Report_Failure: See TS 23.093 + Note right of Release: To GMSC + Note right of Handling_CD_MSC: See TS 23.072 + Note right of CCBS_ICH_MSC_Report_Success: See TS 23.093 +``` + +State transition diagram for Procedure Complete\_Call\_In\_MSC. The process starts at 'Wait\_For\_Alerting', leading to a junction point. From the junction, three paths emerge: 'Alerting failure' leading to 'CAMEL\_MT\_GMSC\_DISC4'; '1' leading to 'Release transaction' -> 'Set cause' -> junction; and 'CD\_Request' leading to 'CCBS\_ICH\_MSC\_Report\_Success'. 'CAMEL\_MT\_GMSC\_DISC4' leads to a decision 'Result=Reconnect?'. If 'Yes', it goes to 'Result=Reconnect' -> exit. If 'No', it goes to 'CCBS\_ICH\_MSC\_Report\_Failure' -> 'Abort' -> 'Release' -> 'Result=Aborted' -> exit. 'CCBS\_ICH\_MSC\_Report\_Failure' also has a reference to 'See TS 23.093'. 'Release' has a reference to 'To GMSC'. 'CCBS\_ICH\_MSC\_Report\_Success' leads to 'Handling\_CD\_MSC' -> 'Complete Call negative response' -> 'Result=Fail' -> exit. 'Handling\_CD\_MSC' has a reference to 'See TS 23.072'. 'CCBS\_ICH\_MSC\_Report\_Success' also has a reference to 'See TS 23.093'. 'CAMEL\_MT\_GMSC\_DISC4' has a reference to 'See TS 23.078'. + +Figure 70e: Procedure Complete\_Call\_In\_MSC (sheet 5) + +![Flowchart for Procedure Complete_Call_In_MSC. The process starts with 'Wait for Answer' and 'Connect'. It then calls 'CAMEL_Stop_TNRy' (See TS 23.078) and 'UUS_ICH_Check_Support' (See TS 23.087). A decision 'Result= Pass?' follows. If 'No', it goes to connector '1'. If 'Yes', it calls 'Establish_Terminating_TCH_Multicall' (See TS 23.135). Another 'Result= Pass?' decision follows. If 'No', it goes to connector '5'. If 'Yes', a third decision 'Result= Aborted?' follows. If 'Yes', it goes to 'Abort' and 'Result= Aborted'. If 'No', it calls 'CAMEL_MT_GMSC_DISC4' (See TS 23.078). A 'Result= Reconnect?' decision follows. If 'Yes', it goes to 'Result= Reconnect'. If 'No', it goes to 'Release', then 'Abort' (See TS 23.078), and finally 'Result= Aborted'. All three final results lead to end symbols.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +### Procedure Complete\_Call\_In\_MSC + +CCI\_MSC6(11) + +Procedure in the MSC to complete an MT call on request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; Start([Wait for Answer]) --> Connect{{Connect}}; A((A)) --> Connect; Connect --> C1[CAMEL_Stop_TNRy]; C1 --- C1_note[See TS 23.078]; C1 --> C2[UUS_ICH_Check_Support]; C2 --- C2_note[See TS 23.087]; C2 --> D1{Result= Pass?}; D1 -- No --> 1((1)); D1 -- Yes --> C3[Establish_Terminating_TCH_Multicall]; C3 --- C3_note[See TS 23.135]; C3 --> D2{Result= Pass?}; D2 -- No --> 5((5)); D2 -- Yes --> D3{Result= Aborted?}; D3 -- Yes --> Abort1{{Abort}}; D3 -- No --> C4[CAMEL_MT_GMSC_DISC4]; C4 --- C4_note[See TS 23.078]; C4 --> D4{Result= Reconnect?}; D4 -- Yes --> ResultReconnect[Result= Reconnect]; D4 -- No --> Release{{Release}}; Release --> Abort2{{Abort}}; Abort2 --- Abort2_note[See TS 23.078]; Abort2 --> ResultAborted1[Result= Aborted]; Abort1 --> C5[CAMEL_MT_GMSC_DISC6]; C5 --> ResultAborted2[Result= Aborted]; ResultReconnect --> End1((X)); ResultAborted1 --> End2((X)); ResultAborted2 --> End3((X)); +``` + +Flowchart for Procedure Complete\_Call\_In\_MSC. The process starts with 'Wait for Answer' and 'Connect'. It then calls 'CAMEL\_Stop\_TNRy' (See TS 23.078) and 'UUS\_ICH\_Check\_Support' (See TS 23.087). A decision 'Result= Pass?' follows. If 'No', it goes to connector '1'. If 'Yes', it calls 'Establish\_Terminating\_TCH\_Multicall' (See TS 23.135). Another 'Result= Pass?' decision follows. If 'No', it goes to connector '5'. If 'Yes', a third decision 'Result= Aborted?' follows. If 'Yes', it goes to 'Abort' and 'Result= Aborted'. If 'No', it calls 'CAMEL\_MT\_GMSC\_DISC4' (See TS 23.078). A 'Result= Reconnect?' decision follows. If 'Yes', it goes to 'Result= Reconnect'. If 'No', it goes to 'Release', then 'Abort' (See TS 23.078), and finally 'Result= Aborted'. All three final results lead to end symbols. + +Figure 70f: Procedure Complete\_Call\_In\_MSC (sheet 6) + +![Flowchart for Procedure Complete_Call_In_MSC. It starts at connector 5, goes through Handle_AoC_MT_MSC, then a Result=Pass? decision. If No, it goes to CAMEL MT_GMSC_DISC4 (referencing TS 23.078). If Yes, it goes to Connect ack. From Connect ack, it goes to CAMEL MT_GMSC_ANSWER (referencing TS 23.078), then a Result? decision. If Fail, it goes to Release (To GMSC) then Result=Aborted. If Release, it goes to Result=Aborted. If Reconnect, it goes to connector 2. If Pass, it goes to Set_COL_Presentation_Indicator_MSC, then Send_Answer_If_Required (To GMSC), then Complete Call ack, then Result=Pass. From CAMEL MT_GMSC_DISC4, it goes to Result=Reconnect? decision. If Yes, it goes to connector 2. If No, it goes to Result=Reconnect. From connector 2, it goes to Set cause, then Release (To GMSC), then Abort, then Result=Aborted.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +### Procedure Complete\_Call\_In\_MSC + +CCI\_MSC7(11) + +Procedure in the MSC to complete an MT call on request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; 5((5)) --> HandleAoC[Handle_AoC_MT_MSC]; HandleAoC --> ResultPass{Result=Pass?}; ResultPass -- No --> CAMELDisc4[CAMEL MT_GMSC_DISC4]; CAMELDisc4 -.-> TS23078_1[See TS 23.078]; ResultPass -- Yes --> ConnectAck{Connect ack}; ConnectAck --> CAMELAnswer[CAMEL MT_GMSC_ANSWER]; CAMELAnswer -.-> TS23078_2[See TS 23.078]; CAMELAnswer --> Result{Result?}; Result -- Fail --> Release1{Release}; Release1 -- To GMSC --> ResultAborted1[Result=Aborted]; Result -- Release --> ResultAborted2[Result=Aborted]; Result -- Reconnect --> 2((2)); Result -- Pass --> SetCOL[Set_COL_Presentation_Indicator_MSC]; SetCOL --> SendAnswer[Send_Answer_If_Required]; SendAnswer -.-> ToGMSC1[To GMSC]; SendAnswer --> CompleteCall[Complete Call ack]; CompleteCall --> ResultPass2[Result=Pass]; CAMELDisc4 --> ResultReconnect{Result=Reconnect?}; ResultReconnect -- Yes --> 2; ResultReconnect -- No --> ResultReconnect2[Result=Reconnect]; 2 --> SetCause[Set cause]; SetCause --> Release2{Release}; Release2 -- To GMSC --> Abort[Abort]; Abort --> ResultAborted3[Result=Aborted]; ResultAborted1 --> End1((X)); ResultPass2 --> End2((X)); ResultReconnect2 --> End3((X)); ResultAborted3 --> End4((X)); +``` + +Flowchart for Procedure Complete\_Call\_In\_MSC. It starts at connector 5, goes through Handle\_AoC\_MT\_MSC, then a Result=Pass? decision. If No, it goes to CAMEL MT\_GMSC\_DISC4 (referencing TS 23.078). If Yes, it goes to Connect ack. From Connect ack, it goes to CAMEL MT\_GMSC\_ANSWER (referencing TS 23.078), then a Result? decision. If Fail, it goes to Release (To GMSC) then Result=Aborted. If Release, it goes to Result=Aborted. If Reconnect, it goes to connector 2. If Pass, it goes to Set\_COL\_Presentation\_Indicator\_MSC, then Send\_Answer\_If\_Required (To GMSC), then Complete Call ack, then Result=Pass. From CAMEL MT\_GMSC\_DISC4, it goes to Result=Reconnect? decision. If Yes, it goes to connector 2. If No, it goes to Result=Reconnect. From connector 2, it goes to Set cause, then Release (To GMSC), then Abort, then Result=Aborted. + +Figure 70g: Procedure Complete\_Call\_In\_MSC (sheet 7) + +![Flowchart for Procedure Complete_Call_In_MSC. It starts with 'Wait_for_Answer', followed by a parallel loop condition 'No Reply Call Timer expired' or 'CAMEL TN Ry expired'. Then 'UUS_ICH_Check_Forwarding' (referencing TS 23.087). A decision 'Result=Pass?' follows. If 'Yes', it proceeds to 'Set negative response: No subscriber reply', 'Complete Call negative response', 'Release transaction', and 'Result:= Fail'. If 'No', it proceeds to 'Release transaction' and then to connector '2'.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +### Procedure Complete\_Call\_In\_MSC + +CCI\_MSC8(11) + +Procedure in the MSC to complete an MT call on request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; Start([Wait_for_Answer]) --> LoopCond{No Reply Call Timer expired / CAMEL TN Ry expired}; LoopCond --> UUS[UUS_ICH_Check_Forwarding]; UUS --- Ref[See TS 23.087]; UUS --> ResultPass{Result=Pass?}; ResultPass -- Yes --> SetNeg[Set negative response: No subscriber reply]; SetNeg --> CompNeg[Complete Call negative response]; CompNeg --> Release1[Release transaction]; Release1 --> ResultFail[Result:= Fail]; ResultFail --> End((X)); ResultPass -- No --> Release2[Release transaction]; Release2 --> Connector2((2)); +``` + +Flowchart for Procedure Complete\_Call\_In\_MSC. It starts with 'Wait\_for\_Answer', followed by a parallel loop condition 'No Reply Call Timer expired' or 'CAMEL TN Ry expired'. Then 'UUS\_ICH\_Check\_Forwarding' (referencing TS 23.087). A decision 'Result=Pass?' follows. If 'Yes', it proceeds to 'Set negative response: No subscriber reply', 'Complete Call negative response', 'Release transaction', and 'Result:= Fail'. If 'No', it proceeds to 'Release transaction' and then to connector '2'. + +Figure 70h: Procedure Complete\_Call\_In\_MSC (sheet 8) + +![Flowchart for Procedure Complete_Call_In_MSC. It starts with a 'Wait_For_Setup_Response, Wait_For_Alerting' block. The flow then splits into two main paths. The left path involves 'Release transaction', 'OCBS_ICH_MSC_Report_Failure' (referencing TS 23.093), a 'User busy?' decision, 'Set negative response: Busy subscriber (UDUB)', 'Complete Call negative response', and a 'Result:= Fail' outcome. The right path involves 'Release' (from GMSC), 'CAMEL_MT_GMSC_DISC6' (referencing TS 23.078), 'OCBS_ICH_MSC_Report_Failure' (referencing TS 23.093), 'UUS_MSC_Check_UUS1_UII' (referencing TS 23.087), 'Release transaction', 'Abort', and a 'Result:= Aborted' outcome. A 'UUS_MSC_Check_UUS1_UII' block (referencing TS 23.087) and a 'Release' (to GMSC) block are also shown in the center, leading to a common junction point.](5801c19431e76330430e92a598cc7a16_img.jpg) + +### Procedure Complete\_Call\_In\_MSC + +**CCI\_MSC9(11)** + +Procedure in the MSC to complete an MT call on request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +graph TD; Start(( )) --> Wait[Wait_For_Setup_Response, Wait_For_Alerting]; Wait --> ReleaseT[Release transaction]; Wait --> Release[Release]; Release --> FromGMSC[From GMSC]; ReleaseT --> OCBS_ICH_MSC_Report_Failure_L[OCBS_ICH_MSC_Report_Failure]; OCBS_ICH_MSC_Report_Failure_L --> See_TS_23_093_L[See TS 23.093]; OCBS_ICH_MSC_Report_Failure_L --> User_busy{User busy?}; User_busy -- No --> Release_UUS[Release]; User_busy -- Yes --> Set_Neg_Response[Set negative response: Busy subscriber (UDUB)]; Set_Neg_Response --> Complete_Neg_Response[Complete Call negative response]; Complete_Neg_Response --> Result_Fail[Result:= Fail]; Release --> CAMEL_MT_GMSC_DISC6[CAMEL_MT_GMSC_DISC6]; CAMEL_MT_GMSC_DISC6 --> See_TS_23_078[See TS 23.078]; CAMEL_MT_GMSC_DISC6 --> OCBS_ICH_MSC_Report_Failure_R[OCBS_ICH_MSC_Report_Failure]; OCBS_ICH_MSC_Report_Failure_R --> See_TS_23_093_R[See TS 23.093]; OCBS_ICH_MSC_Report_Failure_R --> UUS_MSC_Check_UUS1_UII_R[UUS_MSC_Check_UUS1_UII]; UUS_MSC_Check_UUS1_UII_R --> See_TS_23_087_R[See TS 23.087]; UUS_MSC_Check_UUS1_UII_R --> ReleaseT_R[Release transaction]; ReleaseT_R --> Abort[Abort]; Abort --> Result_Aborted[Result:= Aborted]; UUS_MSC_Check_UUS1_UII_L[UUS_MSC_Check_UUS1_UII] --> See_TS_23_087_L[See TS 23.087]; UUS_MSC_Check_UUS1_UII_L --> Release_To_GMSC[Release]; Release_To_GMSC --> ToGMSC[To GMSC]; Release_To_GMSC --> Junction(( )); ReleaseT_R --> Junction; Junction --> Abort; +``` + +Flowchart for Procedure Complete\_Call\_In\_MSC. It starts with a 'Wait\_For\_Setup\_Response, Wait\_For\_Alerting' block. The flow then splits into two main paths. The left path involves 'Release transaction', 'OCBS\_ICH\_MSC\_Report\_Failure' (referencing TS 23.093), a 'User busy?' decision, 'Set negative response: Busy subscriber (UDUB)', 'Complete Call negative response', and a 'Result:= Fail' outcome. The right path involves 'Release' (from GMSC), 'CAMEL\_MT\_GMSC\_DISC6' (referencing TS 23.078), 'OCBS\_ICH\_MSC\_Report\_Failure' (referencing TS 23.093), 'UUS\_MSC\_Check\_UUS1\_UII' (referencing TS 23.087), 'Release transaction', 'Abort', and a 'Result:= Aborted' outcome. A 'UUS\_MSC\_Check\_UUS1\_UII' block (referencing TS 23.087) and a 'Release' (to GMSC) block are also shown in the center, leading to a common junction point. + +Figure 70i: Procedure Complete\_Call\_In\_MSC (sheet 9) + +![Flowchart for Procedure Complete_Call_In_MSC (sheet 10)](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +### Procedure Complete\_Call\_In\_MSC + +CCI\_MSC10(11) + +Procedure in the MSC to complete an MT call on request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` + +graph TD + Wait([Wait_For_Answer]) --> Branch1{ } + + %% Left Branch + Branch1 --> RelTrans1[Release +transaction] + RelTrans1 --> UserBusy{User +busy?} + + UserBusy -- Yes --> UUS_ICH[UUS_ICH_ +Check_ +Forwarding] + UUS_ICH -.-> TS23087_1[See TS 23.087] + UUS_ICH --> ResultPass{Result= +Pass?} + + ResultPass -- No --> UUS_MSC1[UUS_MSC_ +Check_ +UUS1_UUI] + UUS_MSC1 -.-> TS23087_2[See TS 23.087] + UUS_MSC1 --> Conn1((1)) + + ResultPass -- Yes --> SetNeg[Set negative +response: +Busy subscriber +(UDUB)] + SetNeg --> CompCallNeg[Complete +Call +negative +response] + CompCallNeg --> ResFail[Result:= +Fail] + ResFail --> End1((X)) + + %% Middle Branch + UserBusy -- No --> TS23078[See TS 23.078] + TS23078 --> CAMEL[CAMEL_ +MT_GMSC_ +DISC6] + + Branch1 --> UUS_MSC2[UUS_MSC_ +Check_ +UUS1_UUI] + UUS_MSC2 -.-> TS23087_3[See TS 23.087] + UUS_MSC2 --> RelTrans2[Release +transaction] + RelTrans2 --> ToGMSC>To GMSC] + RelTrans2 --> Abort[Abort] + Abort --> ResAbort[Result:= +Aborted] + ResAbort --> End2((X)) + + %% Right Branch + Branch1 --> FromGMSC[From GMSC] --> Release>Release] + Release --> UUS_MSC3[UUS_MSC_ +Check_ +UUS1_UUI] + UUS_MSC3 -.-> TS23087_4[See TS 23.087] + UUS_MSC3 --> RelTrans3[Release +transaction] + RelTrans3 --> CAMEL + CAMEL -.-> TS23087_5[See TS 23.087] + CAMEL --> ToGMSC + +``` + +Flowchart for Procedure Complete\_Call\_In\_MSC (sheet 10) + +**Figure 70j: Procedure Complete\_Call\_In\_MSC (sheet 10)** + +![State transition diagram for Complete_Call_In_MSC procedure. The diagram is split into two main vertical paths. The left path starts with a 'Wait_For_Answer' state, followed by a 'CD Request' signal, then a 'UUS_ICH_Check_Forwarding' process (referencing TS 23.087). A decision diamond 'Result= Pass?' follows. If 'No', it goes to 'CD_UUS_Interaction' (referencing TS 23.072) and then to connector '2'. If 'Yes', it goes to 'Handling_CD_MSC' (referencing TS 23.072), then 'Complete Call negative response', then 'Result= Fail', and finally to a failure connector. The right path starts with a state containing 'Wait_For_Alerting, Wait_For_Answer', followed by an 'Int_Release_Call' signal (from gsmSSF), an 'Abort' process, a 'Release transaction' process, a 'Release' signal (to GMSC), a 'Result= Aborted' process, and finally to a failure connector. Below these, a new sequence starts with 'Wait_For_Answer', branching into two parallel 'User to User' signal paths. The left path goes through 'UUS_MSC_Check_UUS2_UUI_to_NW' (referencing TS 23.087) and the right path goes through 'UUS_MSC_Check_UUS2_UUI_to_MS' (referencing TS 23.087). Both paths converge to a final 'Wait_For_Answer' state.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +### Procedure Complete\_Call\_In\_MSC + +CCI\_MSC11(11) + +Procedure in the MSC to complete an MT call on request from the VLR + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise + +``` +stateDiagram-v2 + [*] --> WFA1: Wait_For_Answer + WFA1 --> CD_R: CD Request + CD_R --> UICF: UUS_ICH_Check_Forwarding + UICF --> D: Result= Pass? + D -- No --> CUI: CD_UUS_Interaction + CUI --> 2 + D -- Yes --> HCM: Handling_CD_MSC + HCM --> CNR: Complete Call negative response + CNR --> RF: Result= Fail + RF --> [*] + [*] --> WFA2: Wait_For_Alerting, Wait_For_Answer + WFA2 --> IRC: Int_Release_Call + IRC --> A: Abort + A --> RT: Release transaction + RT --> Rel: Release + Rel --> RA: Result= Aborted + RA --> [*] + [*] --> WFA3: Wait_For_Answer + WFA3 --> U2U1: User to User + WFA3 --> U2U2: User to User + U2U1 --> UMN: UUS_MSC_Check_UUS2_UUI_to_NW + UMN --> WFA4: Wait_For_Answer + U2U2 --> UMS: UUS_MSC_Check_UUS2_UUI_to_MS + UMS --> WFA4 +``` + +State transition diagram for Complete\_Call\_In\_MSC procedure. The diagram is split into two main vertical paths. The left path starts with a 'Wait\_For\_Answer' state, followed by a 'CD Request' signal, then a 'UUS\_ICH\_Check\_Forwarding' process (referencing TS 23.087). A decision diamond 'Result= Pass?' follows. If 'No', it goes to 'CD\_UUS\_Interaction' (referencing TS 23.072) and then to connector '2'. If 'Yes', it goes to 'Handling\_CD\_MSC' (referencing TS 23.072), then 'Complete Call negative response', then 'Result= Fail', and finally to a failure connector. The right path starts with a state containing 'Wait\_For\_Alerting, Wait\_For\_Answer', followed by an 'Int\_Release\_Call' signal (from gsmSSF), an 'Abort' process, a 'Release transaction' process, a 'Release' signal (to GMSC), a 'Result= Aborted' process, and finally to a failure connector. Below these, a new sequence starts with 'Wait\_For\_Answer', branching into two parallel 'User to User' signal paths. The left path goes through 'UUS\_MSC\_Check\_UUS2\_UUI\_to\_NW' (referencing TS 23.087) and the right path goes through 'UUS\_MSC\_Check\_UUS2\_UUI\_to\_MS' (referencing TS 23.087). Both paths converge to a final 'Wait\_For\_Answer' state. + +Figure 70k: Procedure Complete\_Call\_In\_MSC (sheet 11) + +![MSC sequence diagram for Procedure Set_CLIP_Info_MSC. The process starts with a note about determining CLIP info, followed by an 'Initiate handling of CLIP' message. It then enters a 'Wait_For_CLIP_Info' state. A decision point follows, leading to either 'Release transaction' (From BSS), 'Continue call handling' (which leads to an exit circle), or 'Release' (From GMSC).](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +### Procedure Set\_CLIP\_Info\_MSC CAINF\_M1(1) + +``` +graph TD; Note1[Procedure in the MSC to determine the CLIP information to be sent to the MS]; Note2[Signals to/from the right are to/from the process CLIP_MAF002]; Start([Start]) --> Init[Initiate handling of CLIP]; Init --> Wait[Wait_For_CLIP_Info]; Wait --> Decision{ }; Decision --> ReleaseBSS[Release transaction - From BSS]; Decision --> Continue[Continue call handling]; Continue --> Exit(( )); Decision --> ReleaseGMSC[Release - From GMSC]; +``` + +Procedure in the MSC to determine the CLIP information to be sent to the MS + +Signals to/from the right are to/from the process CLIP\_MAF002 + +Initiate handling of CLIP + +Wait\_For\_CLIP\_Info + +Release transaction — From BSS + +Continue call handling + +Release — From GMSC + +MSC sequence diagram for Procedure Set\_CLIP\_Info\_MSC. The process starts with a note about determining CLIP info, followed by an 'Initiate handling of CLIP' message. It then enters a 'Wait\_For\_CLIP\_Info' state. A decision point follows, leading to either 'Release transaction' (From BSS), 'Continue call handling' (which leads to an exit circle), or 'Release' (From GMSC). + +Figure 71: Procedure Set\_CLIP\_Info\_MSC + +Figure 72: Void + +![Flowchart for Procedure Establish_Terminating_TCH_If_Required. It starts with TCH_Check, leading to a Result decision. If Fail, Result:= Fail. If Use existing, Result:= Pass. If Allocate, it goes to Allocate channel, then Wait_For_Allocation_Complete. If Reject, Result:= Rejected. If Aborted, Result:= Aborted. From Wait_For_Allocation_Complete, it branches to Release transaction, Allocation failure, Allocation complete, or Release. Allocation failure leads to another Release transaction, then Result:= Fail. Allocation complete leads to Result:= Pass. Release leads to Release transaction, then Result:= Aborted. All final results lead to an end connector.](5e9af8986a5845504f251d3079da8078_img.jpg) + +### Procedure Establish\_Terminating\_TCH\_If\_Required + +ETTCIR1(1) + +Procedure in the terminating VMSC to establish a Traffic Channel if one has not been established for this call + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the GMSC + +``` +graph TD; Start([ ]) --> TCH_Check[TCH_Check]; TCH_Check --> Result{Result}; Result -- Fail --> R1[Result:= Fail]; Result -- "Use existing" --> R2[Result:= Pass]; Result -- Allocate --> AC{Allocate channel}; AC --> WFC((Wait_For_Allocation_Complete)); Result -- Reject --> R3[Result:= Rejected]; Result -- Aborted --> R4[Result:= Aborted]; WFC --> RT1{Release transaction}; WFC --> AF{Allocation failure}; WFC --> ACmp{Allocation complete}; WFC --> Rel{Release}; RT1 --> AF; AF --> R5[Result:= Fail]; ACmp --> R6[Result:= Pass]; Rel --> RT2{Release transaction}; RT2 --> R7[Result:= Aborted]; R1 --> End((X)); R2 --> End; R3 --> End; R4 --> End; R5 --> End; R6 --> End; R7 --> End; +``` + +Flowchart for Procedure Establish\_Terminating\_TCH\_If\_Required. It starts with TCH\_Check, leading to a Result decision. If Fail, Result:= Fail. If Use existing, Result:= Pass. If Allocate, it goes to Allocate channel, then Wait\_For\_Allocation\_Complete. If Reject, Result:= Rejected. If Aborted, Result:= Aborted. From Wait\_For\_Allocation\_Complete, it branches to Release transaction, Allocation failure, Allocation complete, or Release. Allocation failure leads to another Release transaction, then Result:= Fail. Allocation complete leads to Result:= Pass. Release leads to Release transaction, then Result:= Aborted. All final results lead to an end connector. + +Figure 73: Procedure Establish\_Terminating\_TCH\_If\_Required + +![Flowchart for Procedure Handle_AoC_MT_MSC. It starts with a decision 'AoC(I) provisioned?'. If Yes, it goes to 'Set charging parameters' -> 'Send Charging Parameters' -> 'Result:= Pass'. If No, it goes to 'AoC(C) provisioned?'. If No, it goes to 'Set charging parameters' -> 'Send Charging Parameters' -> 'Result:= Pass'. If Yes, it goes to 'Set charging parameters' -> 'Send Charging Parameters' -> 'Start AoC acknowledgment timer' -> 'Wait_For_Charging_Parameters_Ack'. From there, three paths: 'Charging Parameters ack' -> 'Result:= Pass'; 'Release connection' -> 'Result:= Fail'; 'AoC acknowledgment timer expired' -> 'Release transaction' -> 'Result:= Fail'.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +### Procedure Handle\_AoC\_MT\_MSC + +AOCMT\_M1(1) + +Procedure in the MSC to handle AoC signalling towards the MS for an MT call! + +Signals to/from the left are to/from the BSS; signals from the right are from the AoC timer function. + +``` +graph TD; Start([ ]) --> AoCI{AoC(I) provisioned?}; AoCI -- Yes --> SetCharging1[Set charging parameters]; SetCharging1 --> SendCharging1{{Send Charging Parameters}}; AoCI -- No --> AoCC{AoC(C) provisioned?}; AoCC -- No --> SetCharging2[Set charging parameters]; SetCharging2 --> SendCharging2{{Send Charging Parameters}}; AoCC -- Yes --> SetCharging3[Set charging parameters]; SetCharging3 --> SendCharging3{{Send Charging Parameters}}; SendCharging3 --> StartTimer[Start AoC acknowledgment timer]; StartTimer --> WaitAck((Wait_For_Charging_Parameters_Ack)); WaitAck --> Ack{Charging Parameters ack}; WaitAck --> Release[Release connection]; WaitAck --> TimerExp[AoC acknowledgment timer expired]; Ack --> ResultPass[Result:= Pass]; Release --> ResultFail[Result:= Fail]; TimerExp --> ReleaseTrans[Release transaction]; ReleaseTrans --> ResultFail; ResultPass --> EndPass(( )); ResultFail --> EndFail(( )); +``` + +Flowchart for Procedure Handle\_AoC\_MT\_MSC. It starts with a decision 'AoC(I) provisioned?'. If Yes, it goes to 'Set charging parameters' -> 'Send Charging Parameters' -> 'Result:= Pass'. If No, it goes to 'AoC(C) provisioned?'. If No, it goes to 'Set charging parameters' -> 'Send Charging Parameters' -> 'Result:= Pass'. If Yes, it goes to 'Set charging parameters' -> 'Send Charging Parameters' -> 'Start AoC acknowledgment timer' -> 'Wait\_For\_Charging\_Parameters\_Ack'. From there, three paths: 'Charging Parameters ack' -> 'Result:= Pass'; 'Release connection' -> 'Result:= Fail'; 'AoC acknowledgment timer expired' -> 'Release transaction' -> 'Result:= Fail'. + +Figure 74: Procedure Handle\_AoC\_MT\_MSC + +![MSC sequence diagram for Procedure Set_COL_Presentation_Indicator_MSC. The diagram shows a vertical flow: a start symbol (oval with vertical line) -> 'Initiate handling of COLR' (arrow) -> 'Wait_For_COLR_Info' (oval with horizontal line) -> a horizontal line branching to three options: 'Release transaction' (parallelogram) labeled 'From BSS', 'Continue call handling' (arrow), and 'Release' (parallelogram) labeled 'From GMSC'. All three options lead to a single end symbol (circle with X).](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +### Procedure Set\_COL\_Presentation\_Indicator\_MSC + +COIND\_M1(1) + +``` +sequenceDiagram + participant MSC + Note left of MSC: Procedure in the MSC to determine the COL presentation indicator value + Note left of MSC: Signals to/from the right are to/from the process COLR_MAF041 + MSC->>MSC: Initiate handling of COLR + Note right of MSC: Wait_For_COLR_Info + alt Release transaction From BSS + Note left of MSC: Release transaction + Note right of MSC: From BSS + Note right of MSC: Continue call handling + alt Release From GMSC + Note left of MSC: Release + Note right of MSC: From GMSC + Note right of MSC: End + MSC->>MSC: Continue call handling +``` + +MSC sequence diagram for Procedure Set\_COL\_Presentation\_Indicator\_MSC. The diagram shows a vertical flow: a start symbol (oval with vertical line) -> 'Initiate handling of COLR' (arrow) -> 'Wait\_For\_COLR\_Info' (oval with horizontal line) -> a horizontal line branching to three options: 'Release transaction' (parallelogram) labeled 'From BSS', 'Continue call handling' (arrow), and 'Release' (parallelogram) labeled 'From GMSC'. All three options lead to a single end symbol (circle with X). + +Figure 75: Procedure Set\_COL\_Presentation\_Indicator MSC + +### 7.3.2 Functional requirements of VLR + +#### 7.3.2.1 Process ICH\_VLR + +Sheet 1: if the MSRN received in the Send Info For Incoming Call is not allocated or there is no IMSI record for the IMSI identified by the MSRN or the MS is marked as "Subscriber data dormant" (e.g. due to super-charger), this is treated as an unknown MSRN. + +Sheet 1: MT roaming retry is not triggered for an incoming call that arrives at the old VLR after the receipt of the MAP Send Identification request from the new VLR but before the receipt of the MAP Cancel Location from the HLR. The "Cancel Location received" flag enables to differentiate for a subscriber whose subscriber data is dormant whether a Cancel Location has been received or not from the HLR. + +Sheet 1: the procedure CAMEL\_ICH\_VLR is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the VLR does not support CAMEL phase 3 or later, processing continues from the possible call of the procedure CCBS\_ICH\_Set\_CCBS\_Call\_Indicator. . + +Sheet 1: If the MSRN is not allocated, "GMSC supports MT Roaming Retry" takes "No" exit. + +Sheet 1: If no IMSI record is found, the "Subscriber data dormant" check takes the "False" exit. + +Sheet 1: A VLR not supporting the flag "Subscriber data dormant" shall behave as if the flag is set to false. + +Sheet 1: the procedure CCBS\_ICH\_Set\_CCBS\_Call\_Indicator is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 1: the VLR derives the basic service required for the call according to the rules defined in 3GPP TS 29.007 [30]. + +Sheet 1, sheet 2, sheet 5: the procedure CCBS\_ICH\_VLR\_Report\_Failure is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 1, sheet 3: the procedure CCBS\_ICH\_Report\_Not\_Reachable is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 2: this process communicates with the matching instance of the process PRN\_VLR, which is linked by the MSRN. + +Sheet 2: the test "Paging via SGSN possible" takes the "yes" exit if: + +- the Gs interface is implemented; and +- there is an association established for the MS between the MSC/VLR and the SGSN. + +Sheet 3: the test "NDUB?" takes the "Yes" exit if the Page MS negative response or the Search for MS negative response had the value Busy Subscriber (NDUB). + +Sheet 3: the procedure Get\_CW\_Subscription\_Info\_VLR is specific to Call Waiting. If the VLR does not support Call Waiting, processing continues from the "No" exit of the test "CW available?". + +Sheet 3: the procedure Get\_CW\_Subscription\_Info\_Multicall\_VLR is specific to Multicall; it is specified in 3GPP TS 23.135 [34]. If the VLR does not support both Multicall and Call Waiting, processing continues from the "No" exit of the test "CW available?". + +Sheet 3: the VLR uses the basic service returned in the Page MS negative response or the Search for MS negative response Busy Subscriber (More calls possible) to determine whether call waiting is available. + +Sheet 3: the procedure Get\_LI\_Subscription\_Info\_MT\_VLR is specific to CLIP and COLR. If the VLR supports neither CLIP nor COLR, the procedure call is omitted. + +Sheet3: the procedure Get\_AoC\_Subscription\_Info\_VLR is specific to AoC; it is specified in subclause 7.1.2.15. + +Sheet 3 sheet 6: the procedure CLI\_ICH\_VLR\_Add\_CLI is specific to Enhanced CLI Handling. It is specified in 3GPP TS 23.081 [14]. + +Sheet 3: the procedure CCBS\_ICH\_Handle\_NDUB is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. If the VLR does not support CCBS, processing continues from the "Forward" exit of the test "Result". + +Sheet 3: the procedure Process\_Access\_Request\_VLR is specified in subclause 7.1.2.2. + +Sheet 3: the output signal Page MS towards the SGSN includes the Location area identity parameter. + +Sheet 3: if the VLR does not support CUG, handling continues from the "No" exit of the test "CUG info present?" + +Sheet 3: the "MT Roaming Forwarding Supported" check takes the "Yes" exit if both the MSC and the VLR support that feature. If both the MT Roaming Retry and the MT Roaming Forwarding procedures are supported, and if the conditions for using these procedures are met, the VLR can decide based on operator policy which procedure to follow. + +Sheet 3: MT Roaming Forwarding is possible towards the new VLR if the conditions defined in subclause 5.2.3 are fulfilled. If so, the old VLR sends a MAP Provide Roaming Number request to the new VLR whose address was received in the MAP Cancel Location message or the MAP Send Identification message. In addition to the requirements specified in subclause 10.2.3 of 3GPP TS 29.002 [29], the MAP Provide Roaming Number request shall not include the "OR Interrogation" parameter when being sent as part of the MT Roaming Forwarding call after successful retrieval of routing information procedure. + +Sheet 4, sheet 6: the procedure CAMEL\_CHECK\_SII2\_CDTI is specific to CAMEL Phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL Phase 3 or later, processing continues from the "Yes" exit of the test "Result = Pass?" + +Sheet 5, sheet 6: the procedure CD\_Authorization is specific to Call Deflection, it is specified in 3GPP TS 23.072 [11]. If the VLR does not support Call Deflection, processing continues from the "Yes" exit of the test "Result=Aborted?" + +Sheet 5, sheet 6: the procedure CCBS\_ICH\_Handle\_UDUB is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 6: the test "NDUB?" is executed only if the VLR supports CCBS. If the VLR does not support CCBS, processing continues from connector 5. + +Sheet 7: the procedure CCBS\_ICH\_Set\_CCBS\_Target is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. + +Sheet 7: the procedure Handle\_CFNRC is specified in subclause 7.2.2.11. + +Sheet 8: the procedure Forward\_CUG\_Check is specific to CUG; it is specified in subclause 7.2.2.6. If the VLR does not support CUG, processing continues from the "Yes" exit of the test "Result=Call allowed?" + +Sheet 8: the procedures CAMEL\_O\_CSI\_Check\_VLR, and CAMEL\_D\_CSI\_Check\_VLR are specific to CAMEL phase 3 or later; they are specified in 3GPP TS 23.078 [12]. + +#### 7.3.2.2 Void + +#### 7.3.2.3 Procedure Search\_For\_MS\_VLR + +The test "Paging via SGSN possible" takes the "yes" exit if: + +- the Gs interface is implemented; and +- the VLR configuration requires paging via the SGSN during VLR restoration. + +The output signal Page MS towards the SGSN omits the Location area identity parameter. It is sent to every SGSN to which the VLR is connected. + +#### 7.3.2.4 Procedure Get\_CW\_Subscription\_Info\_VLR + +The VMSC may abort the transaction with the VLR while a response is awaited from the process MAF013. The message is saved for processing after return from the procedure. + +#### 7.3.2.5 Procedure Get\_LI\_Subscription\_Info\_MT\_VLR + +The VMSC may abort the transaction with the VLR while a response is awaited from the process CLIP\_MAF001 or the process COLR\_MAF040. The message is saved for processing after return from the procedure. + +#### 7.3.2.6 Procedure Handle\_CFB + +The test "Normal call busy" refers to the value of the indicator returned by the process MAF008. + +The procedure CAMEL\_CHECK\_SII2\_CDTI is specific to CAMEL Phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL Phase 3 or later, processing continues from the "Yes" exit of the test "Result = Pass?". + +#### 7.3.2.7 Procedure Handle\_CFNRy + +The test "Normal call" refers to the value of the indicator returned by the process MAF009. + +![Flowchart for Process ICH_VLR (sheet 1).](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +Process ICH\_VLR + +ICH\_VLR1(8) + +Process in VLRB to handle a request for information for an incoming (MT) call + +Signals to/from the left are to/from the MSC + + + +``` + + graph TD + Start([ ]) --> Idle1([Idle]) + Idle1 --> SendInfo[/Send Info For Incoming Call/] + Idle1 --> ReleaseMSRN_In[/Release MSRN/] + + ReleaseMSRN_In --> ReleaseMSRN_Proc[Release MSRN] + ReleaseMSRN_Proc --> Idle_Rel([Idle]) + + SendInfo --> MSRNKnown{MSRN known?} + + MSRNKnown -- Yes --> CAMEL[CAMEL ICH_VLR] + CAMEL --> TS23078[See TS 23.078] + CAMEL --> ResultFail{Result= Fail?} + + ResultFail -- Yes --> Idle_Fail([Idle]) + ResultFail -- No --> CCBS_Set[CCBS_ICH_VLR_Set_CCBS_Call_Indicator] + CCBS_Set --> TS23093_1[See TS 23.093] + CCBS_Set --> DataConfirmed{Data confirmed by HLR} + + DataConfirmed -- True --> DeriveService[Derive required basic service] + DeriveService --> TS29007[See TS 29.007] + DeriveService --> SubDormant{Subscriber data dormant} + + SubDormant -- True --> IMSIDetached{IMSI detached?} + IMSIDetached -- Yes --> CCBS_NotReachable[CCBS_ICH_VLR_Report_Not_Reachable] + CCBS_NotReachable --> Conn1((1)) + + IMSIDetached -- No --> RoamingAllowed{Roaming in LA allowed?} + RoamingAllowed -- No --> Conn10((10)) + + DataConfirmed -- False --> NegResp_SysFail[Set negative response: System Failure] + NegResp_SysFail --> CCBS_ReportFail[CCBS_ICH_VLR_Report_Failure] + CCBS_ReportFail --> TS23093_2[See TS 23.093] + CCBS_ReportFail --> SendInfoNeg[/Send Info For Incoming Call negative response/] + + MSRNKnown -- No --> MTRetry{MT Roaming Retry supported} + MTRetry -- No --> GMSCSupports{GMSC supports MT Roaming Retry} + MTRetry -- Yes --> SubDormant2{Subscriber data dormant} + + GMSCSupports -- No --> SubDormant2 + SubDormant2 -- True --> CancelLoc{Cancel Location received flag = true} + SubDormant2 -- False --> NegResp_Unallocated[Set negative response: Unallocated Roaming Number] + + CancelLoc -- yes --> SetRetryInd[set MT Roaming Retry Indicator] + SetRetryInd --> SendInfoAck[/Send Info For Incoming Call Ack/] + SendInfoAck --> Idle_Ack([Idle]) + + CancelLoc -- no --> NegResp_SysFail + + NegResp_Unallocated --> SendInfoNeg + SendInfoNeg --> Idle_Neg([Idle]) + +``` + +Flowchart for Process ICH\_VLR (sheet 1). + +Figure 76a: Process ICH\_VLR (sheet 1) + +![](719ef0f734259484038b2434e5dc3f24_img.jpg) + +**Process ICH\_VLR** + +**ICH\_VLR2(8)** + +Process in VLRB to handle a request for information for an incoming (MT) call + +Signals to the left are to the VMSC; + Signals to/from the right are to/from the process PRN\_VLR. + +``` + + graph TD + 10((10)) --> Prepaging{Prepaging +supported?} + Prepaging -- No --> 11((11)) + Prepaging -- Yes --> PAR_pending{PAR +pending} + + PAR_pending -- True --> Wait_PAR[Wait_For_ +PAR_Completed] + Wait_PAR --> PAR_completed[/PAR +completed/] + PAR_completed --> PAR_successful{PAR +successful} + + PAR_pending -- False --> PAR_successful + + PAR_successful -- True --> 11 + PAR_successful -- False --> Fatal_PAR{Fatal PAR +error} + + Fatal_PAR -- True --> Set_Neg[Set negative +response: +Impossible call +completion] + Set_Neg --> CCBS_Fail[CCBS_ICH_VLR_ +Report_Failure] + CCBS_Fail -- See TS 23.093 --> CCBS_Fail + CCBS_Fail --> Send_Info[Send Info +For Incoming +Call negative +response] + Send_Info --> Idle_1([Idle]) + + Fatal_PAR -- False --> Loc_ID{Location +area ID +known?} + + Loc_ID -- No --> Search_MS[[Search_For_ +MS_VLR]] + Loc_ID -- Yes --> Paging_Possible{Paging via +SGSN possible?} + + Paging_Possible -- No --> Search_MS + Paging_Possible -- Yes --> Set_Paging[Set Paging +via SGSN +possible] + Set_Paging --> Page_MS[Page MS] + Page_MS -- Page type= +circuit-switched call --> Page_MS + Page_MS --> Wait_Access([Wait_For_ +Access_ +Request]) + + Search_MS --> Result_Pass{Result= +Pass?} + Result_Pass -- Yes --> 2((2)) + Result_Pass -- No --> Result_Fail{Result= +Fail?} + + Result_Fail -- Yes --> 2 + Result_Fail -- No --> CCBS_Fail_2[CCBS_ICH_VLR_ +Report_Failure] + CCBS_Fail_2 -- See TS 23.093 --> CCBS_Fail_2 + CCBS_Fail_2 --> Idle_2([Idle]) + + Call_Arrived[/Call +arrived/] --> 11 + +``` + +**Figure 76b: Process ICH\_VLR (sheet 2)** + +![Process ICH_VLR flowchart (sheet 3). The process starts with 'Wait_For_Access_Request' and branches based on 'Page MS negative response', 'Page MS via SGSN', and 'Abort'. It includes decision points for 'Location Cancelled?', 'Absent subscriber?', 'Busy subscriber?', 'NDUB?', 'Multicall supported in VLR?', 'CW available?', 'MT Roaming Forwarding Supported?', 'GMSC supports MT Roaming Retry', 'MT Roaming Forwarding possible toward new VLR?', and 'Set MT Roaming Retry Indicator'. It also includes actions like 'Page MS', 'To SGSN', 'CCBS_ICH_VLR_Report_Not_Reachable', 'Get_CW_Subscription_Info_VLR', 'Get_LI_Subscription_Info_MT_VLR', 'Get_AoC_Subscription_Info_VLR', 'Release', 'Forward', 'Result', 'Set MT Roaming Forwarding Indicator', 'Provide Roaming Number (IMTF Indicator)', 'Wait_For_MSRN', 'Provide Roaming Number negative response', 'Provide Roaming Number Ack', and 'Send Info For Incoming Call Ack'. The process ends at 'Idle' or connector points 1, 2, 3, 4, 5, 8, 9, 12, 13.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +**Process ICH\_VLR** ICH\_VLR3(8) + +Process in VLRB to handle a request for information for an incoming (MT) call + +Signals to/from the left are to/from the VMSC. + +``` + +graph TD + Start([Wait_For_Access_Request]) --> Branch1(( )) + Branch1 --> PMSNeg[Page MS negative response] + Branch1 --> PMSViaSGSN[Page MS via SGSN] + Branch1 --> Abort[Abort] + + PMSNeg --> LocCancelled{Location Cancelled?} + LocCancelled -- Yes --> C2((2)) + LocCancelled -- No --> Absent{Absent subscriber?} + + Absent -- Yes --> CCBSNotReachable[CCBS_ICH_VLR_Report_Not_Reachable] + CCBSNotReachable --> C1((1)) + Absent -- No --> Busy{Busy subscriber?} + + Busy -- Yes --> C3((3)) + Busy -- No --> NDUB{NDUB?} + + NDUB -- Yes --> C1 + NDUB -- No --> Multicall{Multicall supported in VLR?} + + Multicall -- Yes --> GetCW[Get_CW_Subscription_Info_VLR] + Multicall -- No --> GetLI[Get_LI_Subscription_Info_MT_VLR] + + GetCW --> CWAvail{CW available?} + CWAvail -- Yes --> C9((9)) + CWAvail -- No --> C1 + + GetLI --> GetAoC[Get_AoC_Subscription_Info_VLR] + GetAoC --> C4((4)) + + C1 --> Result{Result} + Result -- Release --> C8((8)) + Result -- Forward --> C5((5)) + + PMSViaSGSN --> ToSGSN[To SGSN] + PMSViaSGSN --> WaitForAccess[Wait_For_Access_Request] + WaitForAccess --> TS23093[See TS 23.093] + + Abort --> CBSICHVLR[CCBS_ICH_VLR_Report_Failure] + CBSICHVLR --> Idle1([Idle]) + + C12((12)) --> MTForwarding{MT Roaming Forwarding Supported?} + MTForwarding -- Yes --> MTForwardingPossible{MT Roaming Forwarding possible toward new VLR?} + MTForwarding -- No --> MTRetry{GMSC supports MT Roaming Retry} + + MTRetry -- Yes --> SetMTRetry[set MT Roaming Retry Indicator] + SetMTRetry --> SendInfoAck[Send Info For Incoming Call Ack] + SendInfoAck --> Idle2([Idle]) + + MTRetry -- No --> C13((13)) + + MTForwardingPossible -- Yes --> ProvideRoaming[Provide Roaming Number IMTF Indicator] + ProvideRoaming --> ToNewVLR[To new VLR] + ProvideRoaming --> WaitForMSRN[Wait_For_MSRN] + WaitForMSRN --> fromNewVLR[from new VLR] + fromNewVLR --> ProvideRoamingAck[Provide Roaming Number Ack] + ProvideRoamingAck --> SetMTForwarding[set MT Roaming Forwarding Indicator] + SetMTForwarding --> SendInfoAck2[Send Info For Incoming Call Ack] + SendInfoAck2 --> Idle3([Idle]) + + MTForwardingPossible -- No --> C13 + +``` + +Process ICH\_VLR flowchart (sheet 3). The process starts with 'Wait\_For\_Access\_Request' and branches based on 'Page MS negative response', 'Page MS via SGSN', and 'Abort'. It includes decision points for 'Location Cancelled?', 'Absent subscriber?', 'Busy subscriber?', 'NDUB?', 'Multicall supported in VLR?', 'CW available?', 'MT Roaming Forwarding Supported?', 'GMSC supports MT Roaming Retry', 'MT Roaming Forwarding possible toward new VLR?', and 'Set MT Roaming Retry Indicator'. It also includes actions like 'Page MS', 'To SGSN', 'CCBS\_ICH\_VLR\_Report\_Not\_Reachable', 'Get\_CW\_Subscription\_Info\_VLR', 'Get\_LI\_Subscription\_Info\_MT\_VLR', 'Get\_AoC\_Subscription\_Info\_VLR', 'Release', 'Forward', 'Result', 'Set MT Roaming Forwarding Indicator', 'Provide Roaming Number (IMTF Indicator)', 'Wait\_For\_MSRN', 'Provide Roaming Number negative response', 'Provide Roaming Number Ack', and 'Send Info For Incoming Call Ack'. The process ends at 'Idle' or connector points 1, 2, 3, 4, 5, 8, 9, 12, 13. + +Figure 76c: Process ICH\_VLR (sheet 3) + +![Flowchart for Process ICH_VLR (sheet 4). The process starts with 'Wait_For_Access_Request', followed by 'Process Access Request' and 'Process Access Request_VLR'. A decision 'Result= Pass?' follows. If 'No', it goes to 'CCBS_ICH_VLR_Report_Failure' and then 'Idle'. If 'Yes', it checks 'CUG info present?'. If 'No', it goes to 'CAMEL_CHECK_SII2_CDTI'. If 'Yes', it goes to 'Translate CUG interlock to index' (referencing TS 23.085) and then to a 'Success?' decision. From 'Success?', 'Yes' leads to 'CAMEL_CHECK_SII2_CDTI' and 'No' leads to 'Set negative response: System failure'. From 'CAMEL_CHECK_SII2_CDTI', a 'Result = Pass?' decision follows. If 'No', it goes to 'CCBS_ICH_VLR_Report_Failure' and then 'Idle'. If 'Yes', it checks 'CFNRy A&Q?'. If 'No', it goes to 'CCBS_ICH_VLR_Report_Failure' and then 'Idle'. If 'Yes', it goes to 'Provide NRCT value' and then to 'Get_L1_Subscription_Info_MT_VLR'. The flow continues through 'Get_AoC_Subscription_Info_VLR', 'CLI_ICH_VLR_Add_CLI' (referencing TS 23.081), 'Complete Call', and finally 'Wait_For_Complete_Call_Result'. A connector '3' is shown near the bottom right of the main flow.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) + +**Process ICH\_VLR** **ICH\_VLR4(8)** + +Process in VLRB to handle a request for information for an incoming (MT) call + +Signals to/from the left are to/from the VMSC. + +``` + +graph TD + Start([Wait_For_Access_Request]) --> ProcessAR[Process Access Request] + ProcessAR --> ProcessARVLR[Process Access Request_VLR] + ProcessARVLR --> ResultPass{Result= Pass?} + ResultPass -- No --> CCBSFailure1[CCBS_ICH_VLR_Report_Failure] + CCBSFailure1 --> Idle1([Idle]) + CCBSFailure1 -.-> TS23093_1[See TS 23.093] + ResultPass -- Yes --> CUGInfo{CUG info present?} + CUGInfo -- Yes --> TranslateCUG[Translate CUG interlock to index] + TranslateCUG -.-> TS23085[As defined in TS 23.085] + TranslateCUG --> Success{Success?} + Success -- No --> SetNegResponse[Set negative response: System failure] + Success -- Yes --> CAMELCheck[CAMEL_CHECK_SII2_CDTI] + CUGInfo -- No --> CAMELCheck + CAMELCheck --> ResultPass2{Result = Pass?} + ResultPass2 -- No --> CCBSFailure2[CCBS_ICH_VLR_Report_Failure] + CCBSFailure2 --> Idle2([Idle]) + CCBSFailure2 -.-> TS23093_2[See TS 23.093] + ResultPass2 -- Yes --> CFNRy{CFNRy A&Q?} + CFNRy -- No --> CCBSFailure2 + CFNRy -- Yes --> ProvideNRCT[Provide NRCT value] + ProvideNRCT --> GetL1[Get_L1_Subscription_Info_MT_VLR] + GetL1 --> GetAoC[Get_AoC_Subscription_Info_VLR] + GetAoC --> CLIAdd[CLI_ICH_VLR_Add_CLI] + CLIAdd -.-> TS23081[See TS 23.081] + CLIAdd --> CompleteCall{Complete Call} + CompleteCall --> WaitComplete([Wait_For_Complete_Call_Result]) + SetNegResponse --> CCBSFailure3[CCBS_ICH_VLR_Report_Failure] + CCBSFailure3 --> SendInfo[Send Info For Incoming Call negative response] + SendInfo --> Idle3([Idle]) + CCBSFailure3 -.-> TS23093_3[See TS 23.093] + Idle3 --> Connector3((3)) + Connector3 --> CAMELCheck + +``` + +Flowchart for Process ICH\_VLR (sheet 4). The process starts with 'Wait\_For\_Access\_Request', followed by 'Process Access Request' and 'Process Access Request\_VLR'. A decision 'Result= Pass?' follows. If 'No', it goes to 'CCBS\_ICH\_VLR\_Report\_Failure' and then 'Idle'. If 'Yes', it checks 'CUG info present?'. If 'No', it goes to 'CAMEL\_CHECK\_SII2\_CDTI'. If 'Yes', it goes to 'Translate CUG interlock to index' (referencing TS 23.085) and then to a 'Success?' decision. From 'Success?', 'Yes' leads to 'CAMEL\_CHECK\_SII2\_CDTI' and 'No' leads to 'Set negative response: System failure'. From 'CAMEL\_CHECK\_SII2\_CDTI', a 'Result = Pass?' decision follows. If 'No', it goes to 'CCBS\_ICH\_VLR\_Report\_Failure' and then 'Idle'. If 'Yes', it checks 'CFNRy A&Q?'. If 'No', it goes to 'CCBS\_ICH\_VLR\_Report\_Failure' and then 'Idle'. If 'Yes', it goes to 'Provide NRCT value' and then to 'Get\_L1\_Subscription\_Info\_MT\_VLR'. The flow continues through 'Get\_AoC\_Subscription\_Info\_VLR', 'CLI\_ICH\_VLR\_Add\_CLI' (referencing TS 23.081), 'Complete Call', and finally 'Wait\_For\_Complete\_Call\_Result'. A connector '3' is shown near the bottom right of the main flow. + +Figure 76d: Process ICH\_VLR (sheet 4) + +![Flowchart for Process ICH_VLR (sheet 5). The process starts with 'Wait_for_Complete_Call_Result'. It receives a 'Complete Call negative response'. It then checks 'Busy subscriber?'. If 'Yes', it follows 'See TS 23.093' to 'CCBS_ICH_Handle_UDUB' and ends at connector 5. If 'No', it checks 'Absent subscriber?'. If 'Yes', it follows 'See TS 23.093' to 'CCBS_ICH_VLR_Report_Failure' and ends at connector 1. If 'No', it checks 'Radio congestion?'. If 'Yes', it goes to 'CCBS_ICH_VLR_Report_Failure' and ends at connector 1. If 'No', it checks 'No subscriber reply?'. If 'Yes', it ends at connector 6. If 'No', it follows 'See TS 23.072' to 'CD_Authorization'. Then it checks 'Result= Aborted?'. If 'Yes', it sets a negative response 'Impossible call completion', sends 'Send Info For Incoming Call negative response', and goes to 'Idle'. If 'No', it checks 'Result= Fail?'. If 'Yes' or 'No', it ends at connector 7. Separately, 'Complete Call ack' and 'Abort' signals lead to 'Idle'.](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +### Process ICH\_VLR + +ICH\_VLR5(8) + +``` + +graph TD + Start1[Process in VLRB to handle a request for information for an incoming MT call] --> CompleteAck[/Complete Call ack/] + Start1 --> Abort[/Abort/] + CompleteAck --> Idle1([Idle]) + Abort --> Idle1 + + StateWait([Wait_for_Complete_Call_Result]) --> CompNeg[/Complete Call negative response/] + CompNeg --> Busy{Busy subscriber?} + + Busy -- Yes --> TS23093_1[See TS 23.093] + TS23093_1 --> UDUB[[CCBS_ICH_Handle_UDUB]] + UDUB --> Conn5((5)) + + Busy -- No --> Absent{Absent subscriber?} + Absent -- Yes --> TS23093_2[See TS 23.093] + TS23093_2 --> ReportFail[[CCBS_ICH_VLR_Report_Failure]] + ReportFail --> Conn1((1)) + + Absent -- No --> Radio{Radio congestion?} + Radio -- Yes --> ReportFail + Radio -- No --> NoReply{No subscriber reply?} + + NoReply -- Yes --> Conn6((6)) + NoReply -- No --> TS23072[See TS 23.072] + TS23072 --> CDAuth[[CD_Authorization]] + + CDAuth --> ResAborted{Result= Aborted?} + ResAborted -- Yes --> SetNeg[Set negative response: Impossible call completion] + SetNeg --> SendNeg[/Send Info For Incoming Call negative response/] + SendNeg --> Idle2([Idle]) + + ResAborted -- No --> ResFail{Result= Fail?} + ResFail -- Yes --> Conn7((7)) + ResFail -- No --> Conn7 + +``` + +Flowchart for Process ICH\_VLR (sheet 5). The process starts with 'Wait\_for\_Complete\_Call\_Result'. It receives a 'Complete Call negative response'. It then checks 'Busy subscriber?'. If 'Yes', it follows 'See TS 23.093' to 'CCBS\_ICH\_Handle\_UDUB' and ends at connector 5. If 'No', it checks 'Absent subscriber?'. If 'Yes', it follows 'See TS 23.093' to 'CCBS\_ICH\_VLR\_Report\_Failure' and ends at connector 1. If 'No', it checks 'Radio congestion?'. If 'Yes', it goes to 'CCBS\_ICH\_VLR\_Report\_Failure' and ends at connector 1. If 'No', it checks 'No subscriber reply?'. If 'Yes', it ends at connector 6. If 'No', it follows 'See TS 23.072' to 'CD\_Authorization'. Then it checks 'Result= Aborted?'. If 'Yes', it sets a negative response 'Impossible call completion', sends 'Send Info For Incoming Call negative response', and goes to 'Idle'. If 'No', it checks 'Result= Fail?'. If 'Yes' or 'No', it ends at connector 7. Separately, 'Complete Call ack' and 'Abort' signals lead to 'Idle'. + +Figure 76e: Process ICH\_VLR (sheet 5) + +![Flowchart for Process ICH_VLR. It starts at connector 4, goes through CAMEL_CHECK_SII2_CDTI (See TS 23.078), then a decision 'Result = Pass?'. If 'No', it checks 'CFNRy A&O?'. If 'Yea', it sets NRCT. Both paths lead to CLI_ICH_VLR_Add_CLI (See TS 23.081). Then 'Process Call Waiting', 'Wait_For_PCW_Result'. From there, it branches to 'Process Call Waiting ack' (leading to Idle), 'Abort' (leading to Idle), or 'Process Call Waiting negative response'. The latter leads to 'Busy subscriber?'. If 'Yes', it goes to 'NDUB?'. If 'No', it checks 'No subscriber reply?'. If 'Yes', it goes to connector 6. If 'No', it goes to CD Authorization (See TS 23.072). From CD Authorization, if 'Result= Aborted?' is 'Yes', it sets a negative response. If 'No', it checks 'Result= Fail?'. If 'Yes', it sends info for incoming call negative response and goes to Idle. If 'No', it goes to connector 7. From 'NDUB?', if 'Yes', it goes to connector 9. If 'No', it goes to CCBS_ICH_Handle_UDUB (See TS 23.093) and then to connector 5.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +### Process ICH\_VLR + +**ICH\_VLR6(8)** + +Process in VLRB to handle a request for information for an incoming (MT) call + +Signals to/from the left are to/from the VMSC. + +``` + +graph TD + 4((4)) --> CAMEL[CAMEL_CHECK_SII2_CDTI] + CAMEL --- CAMEL_REF[See TS 23.078] + CAMEL --> Pass{Result = Pass?} + Pass -- No --> CFNRy{CFNRy A&O?} + CFNRy -- Yea --> SetNRCT[Set NRCT] + SetNRCT --> CLI[CLI_ICH_VLR_Add_CLI] + CLI --- CLI_REF[See TS 23.081] + Pass -- Yez --> CLI + CLI --> PCW[Process Call Waiting] + PCW --> WPCR[Wait_For_PCW_Result] + WPCR --> PCWA[Process Call Waiting ack] + WPCR --> Abort[Abort] + WPCR --> PCWNR[Process Call Waiting negative response] + PCWA --> Idle1([Idle]) + Abort --> Idle1 + PCWNR --> Busy{Busy subscriber?} + Busy -- Yes --> NDUB{NDUB?} + Busy -- No --> NSR{No subscriber reply?} + NSR -- Yes --> 6((6)) + NSR -- No --> CD[CD Authorization] + CD --- CD_REF[See TS 23.072] + CD --> RA{Result= Aborted?} + RA -- Yes --> SNR[Set negative response: Impossible call completion] + RA -- No --> RF{Result= Fail?} + RF -- Yes --> SIF[Send Info For Incoming Call negative response] + SIF --> Idle2([Idle]) + RF -- No --> 7((7)) + NDUB -- Yes --> 9((9)) + NDUB -- No --> CCBS[CCBS_ICH_Handle_UDUB] + CCBS --- CCBS_REF[See TS 23.093] + CCBS --> 5((5)) + +``` + +Flowchart for Process ICH\_VLR. It starts at connector 4, goes through CAMEL\_CHECK\_SII2\_CDTI (See TS 23.078), then a decision 'Result = Pass?'. If 'No', it checks 'CFNRy A&O?'. If 'Yea', it sets NRCT. Both paths lead to CLI\_ICH\_VLR\_Add\_CLI (See TS 23.081). Then 'Process Call Waiting', 'Wait\_For\_PCW\_Result'. From there, it branches to 'Process Call Waiting ack' (leading to Idle), 'Abort' (leading to Idle), or 'Process Call Waiting negative response'. The latter leads to 'Busy subscriber?'. If 'Yes', it goes to 'NDUB?'. If 'No', it checks 'No subscriber reply?'. If 'Yes', it goes to connector 6. If 'No', it goes to CD Authorization (See TS 23.072). From CD Authorization, if 'Result= Aborted?' is 'Yes', it sets a negative response. If 'No', it checks 'Result= Fail?'. If 'Yes', it sends info for incoming call negative response and goes to Idle. If 'No', it goes to connector 7. From 'NDUB?', if 'Yes', it goes to connector 9. If 'No', it goes to CCBS\_ICH\_Handle\_UDUB (See TS 23.093) and then to connector 5. + +Figure 76f: Process ICH\_VLR (sheet 6) + +![Flowchart of Process ICH_VLR (sheet 7) showing handling of call forwarding results (CFB, CFNRc, CFNRy) and setting negative responses for various failure scenarios like forwarding violation, absent subscriber, or busy subscriber, eventually leading to an Idle state or specific exit points 7 and 8.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) + +### Process ICH\_VLR + +ICH\_VLR7(8) + +Process in VLRB to handle a request for information for an incoming (MT) call + +Signals to the left are to the VMSC + +``` + + graph TD + Start5((5)) --> Handle_CFB[Handle_CFB] + Handle_CFB --> ResFail5{Result=Fail?} + ResFail5 -- Yes --> SetNegFV1[Set negative response: +Forwarding Violation] + ResFail5 -- No --> ResFwd5{Result=Forward?} + ResFwd5 -- No --> Exit8((8)) + ResFwd5 -- Yes --> CCBS1[CCBS_ICH_ +Set_CCBS_ +Target] + CCBS1 -.-> TS1[See TS 23.093] + CCBS1 --> SetNegBusy[Set negative response: +Busy Subscriber] + SetNegBusy --> CCBS2[CCBS_ICH_ +Set_CCBS_ +Target] + CCBS2 -.-> TS2[See TS 23.093] + CCBS2 --> Exit7a((7)) + + Start1((1)) --> Handle_CFNRc[Handle_CFNRc] + Handle_CFNRc --> ResFail1{Result=Fail?} + ResFail1 -- Yes --> SendInfo + ResFail1 -- No --> ResFwd1{Result=Forward?} + ResFwd1 -- Yes --> Exit7b((7)) + ResFwd1 -- No --> Start6((6)) + + Start6 --> Handle_CFNRy[Handle_CFNRy] + Handle_CFNRy --> ResFail6{Result=Fail?} + ResFail6 -- Yes --> SendInfo + ResFail6 -- No --> ResFwd6{Result=Forward?} + ResFwd6 -- Yes --> Exit7c((7)) + ResFwd6 -- No --> SetNegNSR[Set negative response: +No Subscriber Reply] + SetNegNSR --> SendInfo + + SetNegFV2[Set negative response: +Forwarding Violation] --> SendInfo + SetNegAS[Set negative response: +Absent Subscriber] --> SendInfo + + SendInfo{Send Info +For Incoming +Call negative +response} --> Idle([Idle]) + + SetNegFV1 --> SendInfo + +``` + +Flowchart of Process ICH\_VLR (sheet 7) showing handling of call forwarding results (CFB, CFNRc, CFNRy) and setting negative responses for various failure scenarios like forwarding violation, absent subscriber, or busy subscriber, eventually leading to an Idle state or specific exit points 7 and 8. + +**Figure 76g: Process ICH\_VLR (sheet 7)** + +![Flowchart for Process ICH_VLR (sheet 8). The process starts at connector 7, performs a CUG check, and branches based on whether the call is allowed. If allowed, it sets forwarding info, performs CAMEL checks, sends an acknowledgement, and goes to Idle. If not allowed, it sets a CUG reject response, sends a negative response, and goes to Idle.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) + +### Process ICH\_VLR + +ICH\_VLR8(8) + +Process in VLRB to handle a request for information for an incoming (MT) call + +Signals to the left are to the VMSC. + +``` + + graph TD + Start((7)) --> CUG[Forward_CUG_Check] + CUG --> Dec{Result= +Call +allowed?} + + Dec -- Yes --> ResF[Set result: +Forward] + ResF --> SetInfo[Set +forwarding +information] + SetInfo --> CamelO[CAMEL_ +O_CSI_ +CHECK_VLR] + CamelO -.-> TS1[See TS 23.078] + CamelO --> CamelD[CAMEL_ +D_CSI_ +CHECK_VLR] + CamelD -.-> TS2[See TS 23.078] + CamelD --> SendAck[Send Info +For Incoming +Call ack] + SendAck --> Idle1([Idle]) + + Dec -- No --> NegRes[Set negative +response: +CUG reject] + NegRes --> SendNeg[Send Info +For Incoming +Call negative +response] + SendNeg --> Idle2([Idle]) + +``` + +Flowchart for Process ICH\_VLR (sheet 8). The process starts at connector 7, performs a CUG check, and branches based on whether the call is allowed. If allowed, it sets forwarding info, performs CAMEL checks, sends an acknowledgement, and goes to Idle. If not allowed, it sets a CUG reject response, sends a negative response, and goes to Idle. + +Figure 76h: Process ICH\_VLR (sheet 8) + +Figure 77: Void + +![](c07e21a8d65991db04263322f859c94f_img.jpg) + +### Procedure Search\_For\_MS\_VLR + +SRCH\_V1(1) + +*Procedure in the VLR +to search for an MS +(i.e. page in all location areas)* + +*Signals to/from the left +are to/from the MSC* + +``` + +graph TD + Start([ ]) --> Decision{Paging via +SGSN possible?} + Decision -- No --> SearchForMS[Search +For MS] + Decision -- Yes --> SetPaging[Set paging +via SGSN +possible] --> SearchForMS + + SearchForMS --> WaitForResult([Wait_For_ +Search_Result]) + + WaitForResult --> Ack{{Search +For MS ack}} + WaitForResult --> Negative{{Search +For MS negative +response}} + WaitForResult --> Abort{{Abort}} + WaitForResult --> ViaSGSN{{Search for MS +via SGSN}} + + Ack --> Update[Update +Location +Area ID] --> Pass[Result:= +Pass] --> End1(( )) + Negative --> Fail[Result:= +Fail] --> End2(( )) + Abort --> Aborted[Result:= +Aborted] --> End3(( )) + ViaSGSN --> ToSGSN>To SGSN] --> PageMS>Page MS] --> WaitForResult2([Wait_For_ +Search_Result]) + +``` + +**Notes:** + - Page type= Circuit-switched call + - PgA is sent if PgA supported and received + +**Figure 78: Procedure Search\_For\_MS\_VLR** + +![Flowchart for Procedure Get_CW_Subscription_Info_VLR. The flow starts with an oval connector, followed by a process block 'initiate handling of CW', then a decision block 'Wait_For_CW_Info'. From 'Wait_For_CW_Info', one path leads to 'process call waiting' and then to a circle connector. Another path from 'Wait_For_CW_Info' leads to 'Abort', which is labeled 'From MSC'.](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +### Procedure Get\_CW\_Subscription\_Info\_VLR + +CWI\_VLR1(1) + +``` +graph TD; Start([ ]) --> Init[initiate handling of CW]; Init --> Wait{Wait_For_CW_Info}; Wait --> Process[process call waiting]; Process --> End(( )); Wait --> Abort[Abort]; MSC[From MSC] --- Abort; +``` + +Procedure in the VLR to retrieve subscription information for the Call Waiting service + +Signals to/from the right are to/from the process MAF013 + +Flowchart for Procedure Get\_CW\_Subscription\_Info\_VLR. The flow starts with an oval connector, followed by a process block 'initiate handling of CW', then a decision block 'Wait\_For\_CW\_Info'. From 'Wait\_For\_CW\_Info', one path leads to 'process call waiting' and then to a circle connector. Another path from 'Wait\_For\_CW\_Info' leads to 'Abort', which is labeled 'From MSC'. + +Figure 79: Procedure Get\_CW\_Subscription\_Info\_VLR + +![Flowchart for Procedure Get_LI_Subscription_Info_MT_VLR](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +### Procedure Get\_LI\_Subscription\_Info\_MT\_VLR + +GLI\_MTV1(1) + +Procedure in the VLR to retrieve subscription information for the CLIP & COLR line identification services for an MT call + +``` +graph TD; Start([Start]) --> InitCLIP{{Initiate handling of CLIP}}; InitCLIP --> ToCLIP[To process CLIP_MAF001]; InitCLIP --> WaitCLIP([Wait_For_CLIP_Info]); WaitCLIP --> Decision1{ }; Decision1 --> Abort1[/Abort/]; Decision1 --> Continue1{{Continue call handling}}; Continue1 --> FromCLIP[From process CLIP_MAF001]; Continue1 --> InitCOLR{{Initiate handling of COLR}}; InitCOLR --> ToCOLR[To process COLR_MAF040]; InitCOLR --> WaitCOLR([Wait_For_COLR_Info]); WaitCOLR --> Decision2{ }; Decision2 --> Abort2[/Abort/]; Decision2 --> Continue2{{Continue call handling}}; Continue2 --> FromCOLR[From process COLR_MAF040]; Continue2 --> End((End)); +``` + +The flowchart illustrates the procedure for retrieving subscription information for CLIP and COLR services during an MT call. It begins with a start symbol, followed by the initiation of CLIP handling, which leads to process CLIP\_MAF001. The flow then enters a wait state for CLIP information. A decision point follows, leading to an 'Abort' path from the MSC or a 'Continue call handling' path from process CLIP\_MAF001. The 'Continue' path leads to the initiation of COLR handling, which leads to process COLR\_MAF040. The flow then enters a wait state for COLR information. A second decision point follows, leading to an 'Abort' path from the MSC or a 'Continue call handling' path from process COLR\_MAF040. The final 'Continue' path leads to the end symbol. + +Flowchart for Procedure Get\_LI\_Subscription\_Info\_MT\_VLR + +Figure 80: Procedure Get\_LI\_Subscription\_Info\_MT\_VLR + +![Flowchart for Procedure Handle_CFB. The process starts with a start connector, followed by a CAMEL_CHECL_SII2_CDTI block (referencing TS 23.078). It then enters a decision: Result = Pass? (Yes leads to initiate handling of CFB, then Wait_For_CFB_Result, then continue call handling; No leads to Result = Busy). From continue call handling, it checks Error? (Yes leads to Result = Fail; No leads to Normal call busy?). Normal call busy? (Yes leads to Result = Busy; No leads to Result = Forward). All three result blocks (Fail, Forward, Busy) lead to a common exit connector.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +### Procedure Handle\_CFB + +H\_CFB1(1) + +Procedure in the VLR to handle Call Forwarding on Busy + +Signals to/from the right are to/from the process MAF008 + +``` + +graph TD + Start([ ]) --> CAMEL[CAMEL_CHECL_SII2_CDTI] + CAMEL -.- Note1[See TS 23.078] + CAMEL --> Pass{Result = +Pass?} + Pass -- No --> BusyResult[Result= +Busy] + Pass -- Yes --> Init[initiate +handling +of CFB] + Init --> Wait{{Wait_For_ +CFB_Result}} + Wait --> Continue[continue +call +handling] + Continue --> Error{Error?} + Error -- Yes --> FailResult[Result= +Fail] + Error -- No --> BusyCheck{Normal +call +busy?} + BusyCheck -- Yes --> BusyResult + BusyCheck -- No --> ForwardResult[Result= +Forward] + FailResult --> End((X)) + ForwardResult --> End + BusyResult --> End + +``` + +Flowchart for Procedure Handle\_CFB. The process starts with a start connector, followed by a CAMEL\_CHECL\_SII2\_CDTI block (referencing TS 23.078). It then enters a decision: Result = Pass? (Yes leads to initiate handling of CFB, then Wait\_For\_CFB\_Result, then continue call handling; No leads to Result = Busy). From continue call handling, it checks Error? (Yes leads to Result = Fail; No leads to Normal call busy?). Normal call busy? (Yes leads to Result = Busy; No leads to Result = Forward). All three result blocks (Fail, Forward, Busy) lead to a common exit connector. + +Figure 81: Procedure Handle\_CFB + +![Flowchart for Procedure Handle_CFNRY. The process starts with a connector symbol, followed by 'initiate handling of CFNRY', 'Wait_For_CFNRY_Result', and 'continue call handling'. It then enters a loop: 'Error?' (Yes leads to 'Result:= Fail', No leads to 'Normal call?'). 'Normal call?' (Yes leads to 'Result:= No reply', No leads to 'Result:= Forward'). All three result boxes lead to a merge connector symbol.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +### Procedure Handle\_CFNRY + +H\_CFNRY1(1) + +Procedure in the VLR to handle Call Forwarding on No subscriber Reply + +Signals to/from the right are to/from the process MAF009 + +``` +graph TD; Start([ ]) --> Init[initiate handling of CFNRY]; Init --> Wait[Wait_For_CFNRY_Result]; Wait --> Continue[continue call handling]; Continue --> Error{Error?}; Error -- Yes --> Fail[Result:= Fail]; Error -- No --> Normal{Normal call?}; Normal -- Yes --> NoReply[Result:= No reply]; Normal -- No --> Forward[Result:= Forward]; Fail --> Merge(( )); NoReply --> Merge; Forward --> Merge; +``` + +Flowchart for Procedure Handle\_CFNRY. The process starts with a connector symbol, followed by 'initiate handling of CFNRY', 'Wait\_For\_CFNRY\_Result', and 'continue call handling'. It then enters a loop: 'Error?' (Yes leads to 'Result:= Fail', No leads to 'Normal call?'). 'Normal call?' (Yes leads to 'Result:= No reply', No leads to 'Result:= Forward'). All three result boxes lead to a merge connector symbol. + +Figure 82: Procedure Handle\_CFNRY + +## 7.4 Subs\_FSM + +### 7.4.1 Functional requirements of serving MSC + +#### 7.4.1.1 Process Subs\_FSM + +One instance of the process Subs\_FSM runs for each subscriber who is involved in at least one call. It monitors the state of any ongoing calls for that subscriber. The individual call control processes OCH\_MSC and ICH\_MSC submit supplementary service requests received from the MS to the process Subs\_FSM, which then responds appropriately. + +The process Subs\_FSM interacts with the processes OCH\_MSC and ICH\_MSC as specified in subclauses 7.1.1 and 7.3.1. + +Sheet 5, sheet 6, sheet 7, sheet 8, sheet 9, sheet 11, sheet 12, sheet 15: processing on this page will occur only if the VMSC supports HOLD. + +Sheet 8: the procedure Handle\_MPTY is specific to MPTY; it is specified in 3GPP TS 23.084 [17]. + +Sheet 8: the procedure Handle\_ECT\_Active is specific to ECT; it is specified in 3GPP TS 23.091 [22]. + +Sheet 10: processing on this page will occur only if the VMSC supports Multicall. + +Sheet 12: the procedure Handle\_ECT\_Alerting is specific to ECT; it is specified in 3GPP TS 23.091 [22]. + +Sheet 13, sheet 14: processing on this page will occur only if the VMSC supports both HOLD and Multicall. + +- 7.4.1.1.1 Macro Check\_Ongoing\_Calls +- 7.4.1.1.2 Macro Update\_Non\_Speech\_Calls\_Status +- 7.4.1.1.3 Macro Increment\_Call\_Counter +- 7.4.1.1.4 Macro Decrement\_Call\_Counter + +![State transition diagram for Process Subs_FSM. It starts with an initial state leading to an initialization block (Speech_Call_Cnt:=0, Non_Speech_Call_Cnt:=0, Speech_CallA:=Null, Speech_CallB:=Null, Non_Speech_Calls:=Null, OG_Call_Alerting:=False). This leads to the Idle state. From Idle, two parallel transitions occur: 'Non speech TCH required' leads to 'Non_Speech_Calls:=Setup' and 'Speech TCH required' leads to 'Speech_CallA:=Setup'. Both lead to a common 'Allocate TCH' state, which then leads to the 'Setup_Pending' state.](f7b2cf9e1b71dc4f900f3810646d3903_img.jpg) + +**Process Subs\_FSM** **SFSM1(18)** + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +``` +graph TD; Start([ ]) --> Init["Speech_Call_Cnt:=0
Non_Speech_Call_Cnt:=0
Speech_CallA:=Null
Speech_CallB:=Null
Non_Speech_Calls:=Null
OG_Call_Alerting:=False"]; Init --> Idle([Idle]); Idle --> NS_TCH{Non speech TCH required}; Idle --> S_TCH{Speech TCH required}; NS_TCH --> NS_Setup["Non_Speech_Calls:=Setup"]; S_TCH --> S_Setup["Speech_CallA:=Setup"]; NS_Setup --> AllocateTCH{Allocate TCH}; S_Setup --> AllocateTCH; AllocateTCH --> SetupPending([Setup_Pending]); +``` + +State transition diagram for Process Subs\_FSM. It starts with an initial state leading to an initialization block (Speech\_Call\_Cnt:=0, Non\_Speech\_Call\_Cnt:=0, Speech\_CallA:=Null, Speech\_CallB:=Null, Non\_Speech\_Calls:=Null, OG\_Call\_Alerting:=False). This leads to the Idle state. From Idle, two parallel transitions occur: 'Non speech TCH required' leads to 'Non\_Speech\_Calls:=Setup' and 'Speech TCH required' leads to 'Speech\_CallA:=Setup'. Both lead to a common 'Allocate TCH' state, which then leads to the 'Setup\_Pending' state. + +Figure 83a: Process Subs\_FSM (sheet 1) + +![State transition diagram for Process Subs_FSM. It starts at 'Setup_Pending' (oval), leading to a decision between 'Call established' (diamond) and 'Call setup failed' (diamond). 'Call established' leads to 'Increment_Call Counter' (rectangle), which then branches into 'Non_Speech' (leading to 'Non_Speech Calls:=Active' rectangle and 'Idle Data_Call Active' oval) and 'Speech' (leading to 'Speech_CallA:=Active' rectangle and 'Call Active' oval). 'Call setup failed' leads to an empty rectangle, which is associated with a box containing 'Speech_CallA:=Null', 'Speech_CallB:=Null', and 'Non_Speech_Calls:=Null', and finally leads to 'Idle' (oval).](38d82ffe820e339811b396206f40a201_img.jpg) + +### Process Subs\_FSM + +SFSM2(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +``` +graph TD; Start([Setup_Pending]) --> CE{Call established}; Start --> CSF{Call setup failed}; CE --> ICC[Increment_Call Counter]; CSF --> EmptyRect[]; EmptyRect --- NullBox["Speech_CallA:=Null
Speech_CallB:=Null
Non_Speech_Calls:=Null"]; ICC --> NS[Non_Speech]; ICC --> S[Speech]; NS --> NSCA[Non_Speech Calls:=Active]; S --> SCOA[Speech_CallA:=Active]; NSCA --> IDCA([Idle Data_Call Active]); SCOA --> CA([Call Active]); EmptyRect --> Idle([Idle]); +``` + +State transition diagram for Process Subs\_FSM. It starts at 'Setup\_Pending' (oval), leading to a decision between 'Call established' (diamond) and 'Call setup failed' (diamond). 'Call established' leads to 'Increment\_Call Counter' (rectangle), which then branches into 'Non\_Speech' (leading to 'Non\_Speech Calls:=Active' rectangle and 'Idle Data\_Call Active' oval) and 'Speech' (leading to 'Speech\_CallA:=Active' rectangle and 'Call Active' oval). 'Call setup failed' leads to an empty rectangle, which is associated with a box containing 'Speech\_CallA:=Null', 'Speech\_CallB:=Null', and 'Non\_Speech\_Calls:=Null', and finally leads to 'Idle' (oval). + +Figure 83b: Process Subs\_FSM (sheet 2) + +![SDL state transition diagram for Process Subs_FSM (sheet 3).](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +## Process Subs\_FSM + +## SFSM3(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +The diagram illustrates the state transitions for the Process Subs\_FSM. It begins with the state **Idle Data\_Call\_Active**. From here, three inputs are possible: +1. **Non speech TCH required**: Leads to task *Non-Speech\_Calls:=Setup*, then to decision **Allocate TCH**. +2. **Speech TCH required**: Leads to task *Speech\_CallA:=Setup*, then to decision **Allocate TCH**. +3. **Call cleared**: Leads to task *Decrement\_Call\_Counter*, then branches based on *Speech, Non\_Speech*. The *Speech, Non\_Speech* path leads to task *Check\_Ongoing\_Calls*, which branches into *Calls\_Ongoing* (returning to **Idle Data\_Call\_Active**) or *No\_Calls\_Ongoing* (leading to state **Idle**). + +From the **Allocate TCH** decision, the process enters state **Data\_Call\_Active\_Setup\_Pending**. From this state, three inputs are possible: +1. **Call cleared**: Leads to task *Decrement\_Call\_Counter*, then branches based on *Speech, Non\_Speech* to task *Check\_Ongoing\_Calls*. This branches into *Calls\_Ongoing* (returning to **Data\_Call\_Active\_Setup\_Pending**) or *No\_Calls\_Ongoing* (leading to state **Setup\_Pending**). +2. **Call established**: Leads to task *Increment\_Call\_Counter*, then branches based on *Speech* (leading to task *Speech\_CallA:=Active* and then state **Call\_Active**) or *Non\_Speech* (leading to task *Non\_Speech\_Calls:=Active* and then state **Idle Data\_Call\_Active**). +3. **Call setup failed**: Leads to task *Non\_Speech\_Calls:=Active*, then returns to state **Idle Data\_Call\_Active**. + +SDL state transition diagram for Process Subs\_FSM (sheet 3). + +Figure 83c: Process Subs\_FSM (sheet 3) + +![State transition diagram for Process Subs_FSM starting from Call_Active state. Transitions include Hold request, Non speech TCH required, Speech TCH required, and Call cleared. Call cleared leads to Decrement_Call_Counter, then Check_Ongoing_Calls. Check_Ongoing_Calls has two branches: Calls_Ongoing (leading to Ongoing speech call? decision) and No_Calls_Ongoing (leading to Idle state). Ongoing speech call? Yes leads to TCH already allocated. Ongoing speech call? No leads to Speech_CallA:=Null, then Idle_Data_Call_Active state. Speech_CallA:=Held leads to Call_Held state. Non_Speech_Calls:=Setup leads to Call_Active_Data_Call_Setup_Pending state. TCH already allocated leads to Call_Active state.](1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg) + +### Process Subs\_FSM + +SFSM4(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +``` +stateDiagram-v2 + [*] --> Call_Active + Call_Active --> Hold_request : Hold request + Call_Active --> Non_speech_TCH_required : Non speech TCH required + Call_Active --> Speech_TCH_required : Speech TCH required + Call_Active --> Call_cleared : Call cleared + Hold_request --> Hold_ack + Hold_ack --> Speech_CallA_Held : Speech_CallA:=Held + Speech_CallA_Held --> Call_Held + Non_speech_TCH_required --> Allocate_TCH + Allocate_TCH --> Non_Speech_Calls_Setup : Non_Speech_Calls:=Setup + Non_Speech_Calls_Setup --> Call_Active_Data_Call_Setup_Pending + Speech_TCH_required --> TCH_already_allocated : TCH already allocated + TCH_already_allocated --> Call_Active + Call_cleared --> Decrement_Call_Counter + Decrement_Call_Counter --> Check_Ongoing_Calls : Speech, Non_Speech + Check_Ongoing_Calls --> Calls_Ongoing : Calls_Ongoing + Check_Ongoing_Calls --> No_Calls_Ongoing : No_Calls_Ongoing + Calls_Ongoing --> Ongoing_speech_call : Ongoing speech call? + Ongoing_speech_call --> Yes : Yes + Ongoing_speech_call --> No : No + Yes --> TCH_already_allocated + No --> Speech_CallA_Null : Speech_CallA:=Null + Speech_CallA_Null --> Idle_Data_Call_Active + No_Calls_Ongoing --> Speech_CallA_Null_Both : Speech_CallA:=Null Speech_CallB:=Null + Speech_CallA_Null_Both --> Idle +``` + +State transition diagram for Process Subs\_FSM starting from Call\_Active state. Transitions include Hold request, Non speech TCH required, Speech TCH required, and Call cleared. Call cleared leads to Decrement\_Call\_Counter, then Check\_Ongoing\_Calls. Check\_Ongoing\_Calls has two branches: Calls\_Ongoing (leading to Ongoing speech call? decision) and No\_Calls\_Ongoing (leading to Idle state). Ongoing speech call? Yes leads to TCH already allocated. Ongoing speech call? No leads to Speech\_CallA:=Null, then Idle\_Data\_Call\_Active state. Speech\_CallA:=Held leads to Call\_Held state. Non\_Speech\_Calls:=Setup leads to Call\_Active\_Data\_Call\_Setup\_Pending state. TCH already allocated leads to Call\_Active state. + +Figure 83d: Process Subs\_FSM (sheet 4) + +![State transition diagram for Process Subs_FSM starting from Call_Held state. It branches into three main paths: 'Call cleared' (leading to Speech_Call_Cnt updates and Idle/Idle Data Call Active states), 'Retrieve request' (leading to a decision on non-speech calls using TCH, resulting in Reject, Ack, or Active states), and another 'Call cleared' path (leading to Speech_Call_Cnt updates and returning to Call_Held state).](d2417b04116c354deccb25d98a84a0fb_img.jpg) + +### Process Subs\_FSM + +SFSM5(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC unless marked otherwise + +``` +stateDiagram-v2 + [*] --> Call_Held + Call_Held --> C1: Call cleared + Call_Held --> C2: Call cleared + Call_Held --> R: Retrieve request + C1 --> S1: Speech_Call_Cnt := Non_Speech_Call_Cnt - 1 + S1 --> S2: Speech_CallA := Null + S2 --> D1: Non_Speech_Call_Count = 0? + D1 -- Yes --> Idle + D1 -- No --> Idle_Data_Call_Active + C2 --> S3: Speech_Call_Cnt := Non_Speech_Call_Cnt - 1 + S3 --> S4: Update_Non_Speech_Calls_Status + S4 --> Call_Held + R --> D2: Non-speech call using TCH? + D2 -- Yes --> Reject: Retrieve reject + D2 -- No --> Ack: Retrieve ack + Ack --> S5: Speech_CallA := Active + S5 --> Call_Active + Reject --> S4 +``` + +State transition diagram for Process Subs\_FSM starting from Call\_Held state. It branches into three main paths: 'Call cleared' (leading to Speech\_Call\_Cnt updates and Idle/Idle Data Call Active states), 'Retrieve request' (leading to a decision on non-speech calls using TCH, resulting in Reject, Ack, or Active states), and another 'Call cleared' path (leading to Speech\_Call\_Cnt updates and returning to Call\_Held state). + +Figure 83e: Process Subs\_FSM (sheet 5) + +![Flowchart for Process Subs_FSM starting from Call_Held state, branching into Speech TCH required and Non speech TCH required paths.](18003425d0e8638dde4acc9c5c468c5c_img.jpg) + +### Process Subs\_FSM + +SFSM6(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC unless marked otherwise + +``` +graph TD; Call_Held([Call_Held]) --> Speech_TCH_Req{Speech TCH required}; Call_Held --> Non_Speech_TCH_Req{Non speech TCH required}; Speech_TCH_Req --> TCH_Avail_1{> TCH available}; TCH_Avail_1 --> Speech_CallB_Setup[Speech_CallB:= Setup]; Speech_CallB_Setup --> Call_Held_Setup_Pending_1([Call_Held_ Setup_Pending]); Non_Speech_TCH_Req --> Non_Speech_Call_Using_TCH{Non-speech call using TCH?}; Non_Speech_Call_Using_TCH -- Yes --> Allocate_TCH{> Allocate TCH}; Non_Speech_Call_Using_TCH -- No --> TCH_Avail_2{> TCH available}; Allocate_TCH --> Non_Speech_Calls_Setup[Non_Speech_Calls:=Setup]; TCH_Avail_2 --> Non_Speech_Calls_Setup; Non_Speech_Calls_Setup --> Call_Held_Data_Call_Setup_Pending([Call_Held_ Data_Call_ Setup_Pending]); +``` + +Flowchart for Process Subs\_FSM starting from Call\_Held state, branching into Speech TCH required and Non speech TCH required paths. + +Figure 83f: Process Subs\_FSM (sheet 6) + +![State transition diagram for Process Subs_FSM. The diagram shows transitions between states Call_Held_Call_Active, Non_Speech_Calls:=Setup, Call_Held_Call_Active_Data_Call_Setup_Pending, Call_Held, and Call_Active based on various triggers and actions.](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) + +### Process Subs\_FSM + +SFSM7(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC; signals from the right are internal MSC signals unless marked otherwise + +``` +stateDiagram-v2 + [*] --> Call_Held_Call_Active + Call_Held_Call_Active --> Retrieve_request : Retrieve request + Retrieve_request --> Retrieve_reject : Retrieve reject + Retrieve_reject --> Call_Held_Call_Active + Call_Held_Call_Active --> Non_speech_TCH_required : Non speech TCH required + Non_speech_TCH_required --> Allocate_TCH : Allocate TCH + Allocate_TCH --> Non_Speech_Calls_Setup : Non_Speech_Calls:=Setup + Non_Speech_Calls_Setup --> Call_Held_Call_Active_Data_Call_Setup_Pending : Call_Held_Call_Active_Data_Call_Setup_Pending + Call_Held_Call_Active --> Hold_request : Hold request + Hold_request --> Handle_Timed_Call_Swap : Handle_Timed_Call_Swap + Handle_Timed_Call_Swap --> Result : Result? + Result --> Call_Held_Call_Active : Retr_req, T_Expr + Result --> Call_Held : Active_Cl + Result --> Call_Active : Hold_Cl + Call_Held_Call_Active --> Speech_TCH_required : Speech TCH required + Speech_TCH_required --> TCH_already_allocated : TCH already allocated + TCH_already_allocated --> Call_Held_Call_Active +``` + +The diagram illustrates the state transitions for the Process Subs\_FSM. It begins with an initial state leading to **Call\_Held\_Call\_Active**. From this state, four main transitions are possible: **Retrieve request** (leading to **Retrieve reject** and back to **Call\_Held\_Call\_Active**), **Non speech TCH required** (leading to **Allocate TCH**, then **Non\_Speech\_Calls:=Setup**, and finally **Call\_Held\_Call\_Active\_Data\_Call\_Setup\_Pending**), **Hold request** (leading to **Handle\_Timed\_Call\_Swap**), and **Speech TCH required** (leading to **TCH already allocated** and back to **Call\_Held\_Call\_Active**). The **Handle\_Timed\_Call\_Swap** state includes an internal signal **Se 3G TS 23.083** and leads to a **Result?** decision point. From **Result?**, three transitions are possible: **Retr\_req, T\_Expr** (back to **Call\_Held\_Call\_Active**), **Active\_Cl** (to **Call\_Held**), and **Hold\_Cl** (to **Call\_Active**). + +State transition diagram for Process Subs\_FSM. The diagram shows transitions between states Call\_Held\_Call\_Active, Non\_Speech\_Calls:=Setup, Call\_Held\_Call\_Active\_Data\_Call\_Setup\_Pending, Call\_Held, and Call\_Active based on various triggers and actions. + +Figure 83g: Process Subs\_FSM (sheet 7) + +![State transition diagram for Process Subs_FSM. It starts with 'Call_Held Call_Active' and branches into 'MPTY request' and 'ECT request'. 'MPTY request' leads to 'MPTY supported?' (Yes/No). 'Yes' leads to 'Handle_MPTY' (See TS 23.084) -> 'Result' -> 'End' (Non-speech call ongoing? -> Idle or Idle Data_Call_Active), 'End_Active' -> 'Call_Active', 'End_Held' -> 'Call_Held', 'Fail' -> 'Call_Held Call_Active'. 'No' leads to 'MPTY reject' -> 'Call_Held Call_Active'. 'ECT request' leads to 'ECT supported?' (Yes/No). 'No' leads to 'ECT reject' -> 'Call_Held Call_Active'. 'Yes' leads to 'Handle_ECT_Active' (See TS 23.091) -> 'Result' -> 'Pass' -> 'Idle', 'Fail' -> 'Call_Held Call_Active'.](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) + +### Process Subs\_FSM + +SFSM8(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +``` +graph TD; Start([Call_Held Call_Active]) --> MPTY_req{{MPTY request}}; Start --> ECT_req{{ECT request}}; MPTY_req --> MPTY_supp{MPTY supported?}; MPTY_supp -- Yes --> Handle_MPTY[Handle_MPTY]; MPTY_supp -- No --> MPTY_rej{{MPTY reject}}; Handle_MPTY --> ResMPTY{Result}; ResMPTY -- End --> NonSpeech{Non-speech call ongoing?}; NonSpeech -- No --> IdleMPTY([Idle]); NonSpeech -- Yes --> IdleDataMPTY([Idle Data_Call_Active]); ResMPTY -- End_Active --> CallActiveMPTY([Call_Active]); ResMPTY -- End_Held --> CallHeldMPTY([Call_Held]); ResMPTY -- Fail --> CallHeldActiveMPTY([Call_Held Call_Active]); MPTY_rej --> CallHeldActiveMPTY; ECT_req --> ECT_supp{ECT supported?}; ECT_supp -- No --> ECT_rej{{ECT reject}}; ECT_rej --> CallHeldActiveECT([Call_Held Call_Active]); ECT_supp -- Yes --> Handle_ECT_Active[Handle_ECT_Active]; Handle_ECT_Active --> ResECT{Result}; ResECT -- Pass --> IdleECT([Idle]); ResECT -- Fail --> CallHeldActiveECT +``` + +State transition diagram for Process Subs\_FSM. It starts with 'Call\_Held Call\_Active' and branches into 'MPTY request' and 'ECT request'. 'MPTY request' leads to 'MPTY supported?' (Yes/No). 'Yes' leads to 'Handle\_MPTY' (See TS 23.084) -> 'Result' -> 'End' (Non-speech call ongoing? -> Idle or Idle Data\_Call\_Active), 'End\_Active' -> 'Call\_Active', 'End\_Held' -> 'Call\_Held', 'Fail' -> 'Call\_Held Call\_Active'. 'No' leads to 'MPTY reject' -> 'Call\_Held Call\_Active'. 'ECT request' leads to 'ECT supported?' (Yes/No). 'No' leads to 'ECT reject' -> 'Call\_Held Call\_Active'. 'Yes' leads to 'Handle\_ECT\_Active' (See TS 23.091) -> 'Result' -> 'Pass' -> 'Idle', 'Fail' -> 'Call\_Held Call\_Active'. + +Figure 83h: Process Subs\_FSM (sheet 8) + +![State transition diagram for Process Subs_FSM. The diagram shows transitions between states Call_Held, Call_Active, and Call_Held. Transitions are triggered by 'Call cleared' or 'From held call' events. Actions include 'Speech_Call_Cnt := Speech_Call_Cnt - 1', 'Speech_CallA := Active', 'Speech_CallB := Null', 'Decrement_Call_Counter', and 'Update_Non_Speech_Calls_Status'. Guards 'Non_Speech' and 'Speech' are present on transitions from 'Decrement_Call_Counter'.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +### Process Subs\_FSM + +SFSM9(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC unless marked otherwise + +``` +stateDiagram-v2 + [*] --> Call_Held + Call_Held --> Call_Active : Call cleared + Call_Held --> Call_Held : From held call + Call_Held --> Call_Held : Call cleared + Call_Active --> Call_Held : Non_Speech + Call_Held --> Call_Held : Speech +``` + +The diagram illustrates the state transitions for the Process Subs\_FSM. It starts with an initial state leading to **Call\_Held**. From **Call\_Held**, a **Call cleared** event leads to **Call\_Active** via the action `Speech_Call_Cnt := Speech_Call_Cnt - 1`. Another **Call cleared** event from **Call\_Held** leads to **Call\_Held** via `Decrement_Call_Counter`. A **From held call** event from **Call\_Held** leads to **Call\_Held** via `Update_Non_Speech_Calls_Status`. From **Call\_Active**, a **Non\_Speech** transition leads to **Call\_Held** via `Speech_CallA := Active` and `Speech_CallB := Null`. From **Call\_Held**, a **Speech** transition leads to **Call\_Held** via `Speech_CallB := Null`. + +State transition diagram for Process Subs\_FSM. The diagram shows transitions between states Call\_Held, Call\_Active, and Call\_Held. Transitions are triggered by 'Call cleared' or 'From held call' events. Actions include 'Speech\_Call\_Cnt := Speech\_Call\_Cnt - 1', 'Speech\_CallA := Active', 'Speech\_CallB := Null', 'Decrement\_Call\_Counter', and 'Update\_Non\_Speech\_Calls\_Status'. Guards 'Non\_Speech' and 'Speech' are present on transitions from 'Decrement\_Call\_Counter'. + +Figure 83i: Process Subs\_FSM (sheet 9) + +![State transition diagram for Process Subs_FSM. The diagram shows transitions between states: Call_Active, Data_Call_Setup_Pending, Call_Held_Setup_Pending, and Setup_Pending. Transitions are triggered by events like 'Call established', 'Call setup failed', 'Call cleared', 'Retrieve request', and 'Hold request'. Actions include updating counters, status, and call identifiers. A decision diamond 'Non-speech call ongoing?' directs the flow based on whether a non-speech call is active.](de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg) + +### Process Subs\_FSM + +SFSM10(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +``` +stateDiagram-v2 + [*] --> Call_Active + Call_Active --> Call established + Call_Active --> Call setup failed + Call_Active --> Call cleared + Call_Active --> Retrieve request + Call_Active --> Hold request + + Call established --> Non_Speech_Call_Cnt := Non_Speech_Call_Cnt + 1 + Non_Speech_Call_Cnt := Non_Speech_Call_Cnt + 1 --> Non_Speech_Calls := Active + Non_Speech_Calls := Active --> Call_Active + + Call setup failed --> Update_Non_Speech_Calls_Status + Update_Non_Speech_Calls_Status --> Data_Call_Active_Setup_Pending + + Call cleared --> Decrement_Call_Count + Decrement_Call_Count --> Non-speech call ongoing? + Non-speech call ongoing? -- Yes --> Retrieve reject + Non-speech call ongoing? -- No --> Update_Non_Speech_Calls_Status + Update_Non_Speech_Calls_Status --> Setup_Pending + Setup_Pending --> Call_Active + + Retrieve request --> Retrieve reject + Retrieve reject --> Call_Active_Data_Call_Setup_Pending + + Hold request --> Hold ack + Hold ack --> Call_Held_Setup_Pending +``` + +State transition diagram for Process Subs\_FSM. The diagram shows transitions between states: Call\_Active, Data\_Call\_Setup\_Pending, Call\_Held\_Setup\_Pending, and Setup\_Pending. Transitions are triggered by events like 'Call established', 'Call setup failed', 'Call cleared', 'Retrieve request', and 'Hold request'. Actions include updating counters, status, and call identifiers. A decision diamond 'Non-speech call ongoing?' directs the flow based on whether a non-speech call is active. + +Figure 83j: Process Subs\_FSM (sheet 10) + +![State transition diagram for Process Subs_FSM. It starts at 'Call_Held_Setup_Pending' and branches into three main paths: 'Call setup failed', 'Call established', and 'Call cleared'. Each path involves specific state changes and decision points to reach final states like 'Call_Held', 'Call_Held_Call_Active', 'Data_Call_Active_Setup_Pending', or 'Setup_Pending'.](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) + +### Process Subs\_FSM + +SFSM11(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +``` +stateDiagram-v2 + [*] --> Call_Held_Setup_Pending + Call_Held_Setup_Pending --> Call_setup_failed + Call_Held_Setup_Pending --> Call_established + Call_Held_Setup_Pending --> Call_cleared + + Call_setup_failed --> OG_Call_Alerting_False_1[OG_Call_Alerting:=False] + OG_Call_Alerting_False_1 --> Speech_call_Yes_No{Speech call?} + Speech_call_Yes_No -- Yes --> Speech_CallB_Null_1[Speech_CallB:=Null] + Speech_call_Yes_No -- No --> Non_speech_call_ongoing{Non-speech call ongoing?} + Non_speech_call_ongoing -- Yes --> Non_Speech_Calls_Active_1[Non_Speech_Calls:=Active] + Non_speech_call_ongoing -- No --> Non_Speech_Calls_Null_1[Non_Speech_Calls:=Null] + Speech_CallB_Null_1 --> Call_Held + Non_Speech_Calls_Active_1 --> Call_Held + Non_Speech_Calls_Null_1 --> Call_Held + + Call_established --> OG_Call_Alerting_False_2[OG_Call_Alerting:=False] + OG_Call_Alerting_False_2 --> Increment_Call_Count + Increment_Call_Count --> Non_Speech_Calls_Active_2[Non_Speech_Calls:=Active] + Increment_Call_Count --> Speech_CallB_Active_2[Speech_CallB:=Active] + Non_Speech_Calls_Active_2 --> Call_Held_Call_Active + Speech_CallB_Active_2 --> Call_Held_Call_Active + + Call_cleared --> OG_Call_Alerting_False_3[OG_Call_Alerting:=False] + OG_Call_Alerting_False_3 --> Decrement_Call_Count + Decrement_Call_Count --> Speech_Non_Speech{Speech, Non_Speech} + Speech_Non_Speech --> Check_Ongoing_Calls + Check_Ongoing_Calls -- Calls_Ongoing --> Speech_call_ongoing_Yes_No{Speech call ongoing?} + Check_Ongoing_Calls -- No_Calls_Ongoing --> Speech_CallA_Setup[Speech_CallA:=Setup +Speech_CallB:=Null] + Speech_call_ongoing_Yes_No -- Yes --> Call_Held_Setup_Pending_2[Call_Held_Setup_Pending] + Speech_call_ongoing_Yes_No -- No --> Data_Call_Active_Setup_Pending + Speech_CallA_Setup --> Setup_Pending +``` + +State transition diagram for Process Subs\_FSM. It starts at 'Call\_Held\_Setup\_Pending' and branches into three main paths: 'Call setup failed', 'Call established', and 'Call cleared'. Each path involves specific state changes and decision points to reach final states like 'Call\_Held', 'Call\_Held\_Call\_Active', 'Data\_Call\_Active\_Setup\_Pending', or 'Setup\_Pending'. + +Figure 83k: Process Subs\_FSM (sheet 11) + +![State transition diagram for Process Subs_FSM. The diagram shows transitions from a 'Call_Held_Setup_Pending' state to various request states: 'Alerting in progress', 'Hold request', 'Retrieve request', and 'ECT request'. 'Alerting in progress' leads to 'OG_Call_Alerting:=True' and back to 'Call_Held_Setup_Pending'. 'Hold request' and 'Retrieve request' lead to 'Hold reject' and 'Retrieve reject' respectively, which both lead back to 'Call_Held_Setup_Pending'. 'ECT request' leads to 'ECT supported?'. If 'Yes', it goes to 'Handle_ECT_Alerting' (with a note 'See TS 23.091'), which then leads to a 'Result' decision. If 'Result' is 'Pass', it goes to 'OG_Call_Alerting:=False' and then to 'Idle'. If 'Result' is 'Fail', it goes to 'Call_Held_Setup_Pending'. If 'No', it goes to 'ECT reject', which also leads to 'Call_Held_Setup_Pending'.](c0ca823603794512478906b302176bca_img.jpg) + +### Process Subs\_FSM + +SFSM12(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +``` +stateDiagram-v2 + [*] --> Call_Held_Setup_Pending + Call_Held_Setup_Pending --> Alerting_in_progress: Alerting in progress + Call_Held_Setup_Pending --> Hold_request: Hold request + Call_Held_Setup_Pending --> Retrieve_request: Retrieve request + Call_Held_Setup_Pending --> ECT_request: ECT request + + Alerting_in_progress --> OG_Call_Alerting_True: OG_Call_Alerting:=True + OG_Call_Alerting_True --> Call_Held_Setup_Pending + + Hold_request --> Hold_reject: Hold reject + Retrieve_request --> Retrieve_reject: Retrieve reject + Hold_reject --> Call_Held_Setup_Pending + Retrieve_reject --> Call_Held_Setup_Pending + + ECT_request --> ECT_supported?: ECT supported? + ECT_supported? --> Handle_ECT_Alerting: Yes + ECT_supported? --> ECT_reject: No + Handle_ECT_Alerting --> Result: Result + Result --> OG_Call_Alerting_False: Pass + Result --> Call_Held_Setup_Pending: Fail + ECT_reject --> Call_Held_Setup_Pending + + OG_Call_Alerting_False --> Idle +``` + +State transition diagram for Process Subs\_FSM. The diagram shows transitions from a 'Call\_Held\_Setup\_Pending' state to various request states: 'Alerting in progress', 'Hold request', 'Retrieve request', and 'ECT request'. 'Alerting in progress' leads to 'OG\_Call\_Alerting:=True' and back to 'Call\_Held\_Setup\_Pending'. 'Hold request' and 'Retrieve request' lead to 'Hold reject' and 'Retrieve reject' respectively, which both lead back to 'Call\_Held\_Setup\_Pending'. 'ECT request' leads to 'ECT supported?'. If 'Yes', it goes to 'Handle\_ECT\_Alerting' (with a note 'See TS 23.091'), which then leads to a 'Result' decision. If 'Result' is 'Pass', it goes to 'OG\_Call\_Alerting:=False' and then to 'Idle'. If 'Result' is 'Fail', it goes to 'Call\_Held\_Setup\_Pending'. If 'No', it goes to 'ECT reject', which also leads to 'Call\_Held\_Setup\_Pending'. + +Figure 84I: Process Subs\_FSM (sheet 12) + +![State transition diagram for Process Subs_FSM. It starts with a state 'Call_Held_Call_Active_Data_Call_Setup_Pending'. Transitions include 'Call established' leading to 'Non_Speech_Call_Cnt := Non_Speech_Call_Cnt + 1' then 'Non_Speech_Calls := Active' then 'Call_Held_Call_Active'; 'Call setup failed' leading to 'See 3G TS 23.083' then 'Update_Non_Speech_Calls_Status' then 'Call_Held_Call_Active_Data_Call_Setup_Pending'; 'Hold request' leading to 'Handle_Timed_Call_Swap' then a 'Result' decision; 'Retrieve request' leading to 'Retrieve reject' then 'Call_Held_Call_Active_Data_Call_Setup_Pending'. The 'Result' decision has three paths: 'Retr_req_T_Expr' leading to 'Call_Held_Call_Active_Data_Call_Setup_Pending'; 'Active_Cl' leading to 'Call_Held_Setup_Pending'; 'Hold_Cl' leading to 'Call_Active_Data_Call_Setup_Pending'.](fc3e2b49a9f850951570e502393b697f_img.jpg) + +### Process Subs\_FSM + +SFSM13(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +``` +stateDiagram-v2 + [*] --> Call_Held_Call_Active_Data_Call_Setup_Pending + Call_Held_Call_Active_Data_Call_Setup_Pending --> Call_established + Call_Held_Call_Active_Data_Call_Setup_Pending --> Call_setup_failed + Call_Held_Call_Active_Data_Call_Setup_Pending --> Hold_request + Call_Held_Call_Active_Data_Call_Setup_Pending --> Retrieve_request + Call_established --> Non_Speech_Call_Cnt := Non_Speech_Call_Cnt + 1 + Non_Speech_Call_Cnt := Non_Speech_Call_Cnt + 1 --> Non_Speech_Calls := Active + Non_Speech_Calls := Active --> Call_Held_Call_Active + Call_setup_failed --> See_3G_TS_23.083 + See_3G_TS_23.083 --> Update_Non_Speech_Calls_Status + Update_Non_Speech_Calls_Status --> Call_Held_Call_Active_Data_Call_Setup_Pending + Hold_request --> Handle_Timed_Call_Swap + Handle_Timed_Call_Swap --> Result + Retrieve_request --> Retrieve_reject + Retrieve_reject --> Call_Held_Call_Active_Data_Call_Setup_Pending + Result --> Retr_req_T_Expr + Result --> Active_Cl + Result --> Hold_Cl + Retr_req_T_Expr --> Call_Held_Call_Active_Data_Call_Setup_Pending + Active_Cl --> Call_Held_Setup_Pending + Hold_Cl --> Call_Active_Data_Call_Setup_Pending +``` + +State transition diagram for Process Subs\_FSM. It starts with a state 'Call\_Held\_Call\_Active\_Data\_Call\_Setup\_Pending'. Transitions include 'Call established' leading to 'Non\_Speech\_Call\_Cnt := Non\_Speech\_Call\_Cnt + 1' then 'Non\_Speech\_Calls := Active' then 'Call\_Held\_Call\_Active'; 'Call setup failed' leading to 'See 3G TS 23.083' then 'Update\_Non\_Speech\_Calls\_Status' then 'Call\_Held\_Call\_Active\_Data\_Call\_Setup\_Pending'; 'Hold request' leading to 'Handle\_Timed\_Call\_Swap' then a 'Result' decision; 'Retrieve request' leading to 'Retrieve reject' then 'Call\_Held\_Call\_Active\_Data\_Call\_Setup\_Pending'. The 'Result' decision has three paths: 'Retr\_req\_T\_Expr' leading to 'Call\_Held\_Call\_Active\_Data\_Call\_Setup\_Pending'; 'Active\_Cl' leading to 'Call\_Held\_Setup\_Pending'; 'Hold\_Cl' leading to 'Call\_Active\_Data\_Call\_Setup\_Pending'. + +Figure 84m: Process Subs\_FSM (sheet 13) + +![State transition diagram for Process Subs_FSM. The diagram shows transitions between states based on call clearing events and subsequent processing of speech and data call counters.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +### Process Subs\_FSM + +SFSM14(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +``` +stateDiagram-v2 + [*] --> Call_Held_Call + Call_Held_Call --> Call_cleared_1 : From held call + Call_Held_Call --> Call_cleared_2 : + Call_Held_Call --> Call_cleared_3 : From active call + Call_cleared_1 --> Speech_Call_Cnt_1 : Speech_Call_Cnt := Speech_Call_Cnt - 1 + Speech_Call_Cnt_1 --> Speech_Call_A_1 : Speech_CallA := Active, Speech_CallB := Null + Speech_Call_A_1 --> Call_Active_Data_Call + Call_cleared_2 --> Speech_Call_Cnt_2 : Non_Speech_Call_Cnt := Non_Speech_Call_Cnt - 1 + Speech_Call_Cnt_2 --> Speech_call_ongoing{Speech call ongoing?} + Speech_call_ongoing -- Yes --> Call_Held_Call + Speech_call_ongoing -- No --> Speech_Call_B_2 : Speech_CallB := Null + Speech_Call_B_2 --> Setup_Pending + Call_cleared_3 --> Speech_Call_Cnt_3 : Speech_Call_Cnt := Speech_Call_Cnt - 1 + Speech_Call_Cnt_3 --> Speech_Call_A_3 : Speech_CallA := Held, Speech_CallB := Null + Speech_Call_A_3 --> Call_Held_Call +``` + +The diagram illustrates the state transitions for the Process Subs\_FSM. It starts with an initial state leading to **Call\_Held\_Call**, which also includes **Active\_Data\_Call** and **Setup\_Pending**. From **Call\_Held\_Call**, three transitions lead to **Call\_cleared** states: one from a held call, one from an active call, and one unlabeled. Each **Call\_cleared** state leads to a processing block: **Speech\_Call\_Cnt := Speech\_Call\_Cnt - 1**. The first and third lead to **Speech\_CallA := Active, Speech\_CallB := Null** and then to **Call\_Active\_Data\_Call**. The second leads to **Non\_Speech\_Call\_Cnt := Non\_Speech\_Call\_Cnt - 1** and then to a decision **Speech call ongoing?**. If **Yes**, it returns to **Call\_Held\_Call**; if **No**, it leads to **Speech\_CallB := Null** and then to **Setup\_Pending**. Finally, the third **Speech\_Call\_Cnt := Speech\_Call\_Cnt - 1** block leads to **Speech\_CallA := Held, Speech\_CallB := Null** and then back to **Call\_Held\_Call**. + +State transition diagram for Process Subs\_FSM. The diagram shows transitions between states based on call clearing events and subsequent processing of speech and data call counters. + +Figure 84n: Process Subs\_FSM (sheet 14) + +![SDL state transition diagram for Process Subs_FSM showing transitions from state Call_Held Data_Call_Setup_Pending based on various call events.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) + +Process Subs\_FSM +SFSM15(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +``` + +stateDiagram-v2 + state "Call_Held\nData_Call_Setup_Pending" as StartState + state "Call_Held" as EndHeld + state "Data_Call_Setup_Pending" as EndDataPending + state "Call_Active_\nData_Call_Setup_Pending" as EndActive + + [*] --> StartState + + StartState --> UpdateStatus1 : Call setup failed + UpdateStatus1 --> EndHeld : Update_Non_Speech_Calls_Status + + StartState --> IncCnt : Call established + IncCnt --> EndHeld : Non_Speech_Call_Cnt := Non_Speech_Call_Cnt + 1 + + StartState --> DecCnt : Call cleared + DecCnt --> UpdateStatus2 : Non_Speech_Call_Cnt := Non_Speech_Call_Cnt - 1 + UpdateStatus2 --> SpeechOngoing : Update_Non_Speech_Calls_Status + state SpeechOngoing <> + SpeechOngoing --> EndDataPending : Yes + SpeechOngoing --> SetNull : No + SetNull --> EndDataPending : Speech_CallA := Null + + StartState --> HoldReject : Hold request + HoldReject --> EndHeld : Hold reject + + StartState --> UsingTCH : Retrieve request + state UsingTCH <> + UsingTCH --> RetrieveReject : Yes + RetrieveReject --> EndHeld : Retrieve reject + UsingTCH --> RetrieveAck : No + RetrieveAck --> SetActive : Retrieve ack + SetActive --> EndActive : Speech_CallA := Active + +``` + +SDL state transition diagram for Process Subs\_FSM showing transitions from state Call\_Held Data\_Call\_Setup\_Pending based on various call events. + +Figure 84o: Process Subs\_FSM (sheet 14) + +![SDL diagram for Process Subs_FSM showing a state transition from '*' to '-' triggered by 'Request call status' and resulting in 'Call status' output.](e18841eb4a995df8354a793459e12fd0_img.jpg) + +**Process Subs\_FSM** + +**SFSM16(18)** + +Process in the serving MSC +to control the call states on a per +subscriber basis. + +Signals to/from the left are +to/from either process OCH\_MSC +or process ICH\_MSC + +``` + + graph TD + StateStart(["*"]) --> Input["Request +call status"] + Input --> Output["Call status"] + Output --> StateEnd(["-"]) + + style StateStart fill:white,stroke:black + style Input fill:white,stroke:black,shape:polygon,points:[0,0 90,0 100,50 90,100 0,100] + style Output fill:white,stroke:black,shape:polygon,points:[0,0 100,0 90,50 100,100 0,100] + style StateEnd fill:white,stroke:black + +``` + +SDL diagram for Process Subs\_FSM showing a state transition from '\*' to '-' triggered by 'Request call status' and resulting in 'Call status' output. + +**Figure 84p: Process Subs\_FSM (sheet 14)** + +![State transition diagram for Process Subs_FSM. It starts at an initial state '*' with a note 'Except for the following states: "Call Held Call Active", "Call Held Setup Pending"'. A vertical line descends from '*' to a state transition box labeled 'ECT request'. From 'ECT request', a vertical line descends to a state transition box labeled 'ECT reject'. From 'ECT reject', a vertical line descends to a final state '-'.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +### Process Subs\_FSM + +SFSM17(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +``` +graph TD; Start(( * )) --> ECT_request[ECT request]; ECT_request --> ECT_reject[ECT reject]; ECT_reject --> End(( - )); Note1[Except for the following states: "Call Held Call Active", "Call Held Setup Pending"] -.-> Start; +``` + +State transition diagram for Process Subs\_FSM. It starts at an initial state '\*' with a note 'Except for the following states: "Call Held Call Active", "Call Held Setup Pending"'. A vertical line descends from '\*' to a state transition box labeled 'ECT request'. From 'ECT request', a vertical line descends to a state transition box labeled 'ECT reject'. From 'ECT reject', a vertical line descends to a final state '-'. + +Figure 84q: Process Subs\_FSM (sheet 14) + +![State transition diagram for Process Subs_FSM. It shows a vertical sequence of four symbols: a start state (oval with *), a transition state (parallelogram with 'MPTY request'), a decision state (diamond with 'MPTY reject'), and an end state (oval with -). Arrows connect them in a downward flow.](69467ece0a576b4c2ec3e0c89ba61527_img.jpg) + +### Process Subs\_FSM + +SFSM18(18) + +Process in the serving MSC to control the call states on a per subscriber basis. + +Signals to/from the left are to/from either process OCH\_MSC or process ICH\_MSC + +Except for the following state: +"Call Held Call Active" + +``` +graph TD; Start([*]) --> MPTY_request[/MPTY request/]; MPTY_request --> MPTY_reject{MPTY reject}; MPTY_reject --> End([-]); +``` + +State transition diagram for Process Subs\_FSM. It shows a vertical sequence of four symbols: a start state (oval with \*), a transition state (parallelogram with 'MPTY request'), a decision state (diamond with 'MPTY reject'), and an end state (oval with -). Arrows connect them in a downward flow. + +Figure 84r: Process Subs\_FSM (sheet 14) + +![Flowchart for Macro Check_Ongoing_Calls](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) + +**Macrodefinition Check\_Ongoing\_Calls** COC1(1) + +Macro to check if there are any speech or non-speech calls remaining (and also update the Non\_Speech\_Calls status variable). + +``` +graph TD; Start([ ]) --> Dec1{Non_Speech_Call_Cnt}; Dec1 -- 0 --> Act1[Non_Speech_Calls:=Null]; Act1 --> Dec2{Speech_Call_Cnt}; Dec1 -- ">=1" --> End2((Calls_Ongoing)); Dec2 -- 0 --> End1((No_Calls_Ongoing)); Dec2 -- ">=1" --> End2; +``` + +The flowchart illustrates the logic for the macro Check\_Ongoing\_Calls. It begins with a start symbol (oval), leading to a decision diamond labeled 'Non\_Speech\_Call\_Cnt'. If the count is 0, it proceeds to an action box 'Non\_Speech\_Calls:=Null'. If the count is greater than or equal to 1, it proceeds directly to the end symbol 'Calls\_Ongoing'. From the action box, it proceeds to another decision diamond labeled 'Speech\_Call\_Cnt'. If the count is 0, it proceeds to the end symbol 'No\_Calls\_Ongoing'. If the count is greater than or equal to 1, it proceeds to the end symbol 'Calls\_Ongoing'. + +Flowchart for Macro Check\_Ongoing\_Calls + +**Figure 85: Macro Check\_Ongoing\_Calls** + +![Flowchart for Update_Non_Speech_Calls_Status macro. It starts with a connector, followed by a decision 'Non-speech call ongoing?'. If 'Yes', it sets 'Non_Speech_Calls:=Active'. If 'No', it sets 'Non_Speech_Calls:=Null'. Both paths lead to a final connector.](a5404b7275b06497eecf9b5883604753_img.jpg) + +**Macrodefinition Update\_Non\_Speech\_Calls\_Status** **Upd\_NSC\_Stat1(1)** + +Macro to update the Non\_Speech\_Calls variable depending on whether there are any non-speech calls ongoing or not. + +``` +graph TD; Start([ ]) --> Decision{Non-speech call ongoing?}; Decision -- Yes --> Active[Non_Speech_Calls:=Active]; Decision -- No --> Null[Non_Speech_Calls:=Null]; Active --> End(( )); Null --> End; +``` + +Flowchart for Update\_Non\_Speech\_Calls\_Status macro. It starts with a connector, followed by a decision 'Non-speech call ongoing?'. If 'Yes', it sets 'Non\_Speech\_Calls:=Active'. If 'No', it sets 'Non\_Speech\_Calls:=Null'. Both paths lead to a final connector. + +**Figure 86: Macro Update\_Non\_Speech\_Calls\_Status** + +![Flowchart for Increment_Call_Counter macro. It starts with an oval connector, leading to a decision diamond 'Speech call?'. The 'No' path leads to a process box 'Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt + 1', which then leads to a circle connector labeled 'Non_Speech'. The 'Yes' path leads to a process box 'Speech_Call_Cnt:= Speech_Call_Cnt + 1', which then leads to a circle connector labeled 'Speech'.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +### Macrodefinition Increment\_Call\_Counter + +Inc\_Call\_Cnt1(1) + +Macro to increment the correct counter depending on the type of the current call. + +``` +graph TD; Start([ ]) --> Decision{Speech call?}; Decision -- No --> Process1[Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt + 1]; Process1 --> Connector1((Non_Speech)); Decision -- Yes --> Process2[Speech_Call_Cnt:= Speech_Call_Cnt + 1]; Process2 --> Connector2((Speech)); +``` + +Flowchart for Increment\_Call\_Counter macro. It starts with an oval connector, leading to a decision diamond 'Speech call?'. The 'No' path leads to a process box 'Non\_Speech\_Call\_Cnt:= Non\_Speech\_Call\_Cnt + 1', which then leads to a circle connector labeled 'Non\_Speech'. The 'Yes' path leads to a process box 'Speech\_Call\_Cnt:= Speech\_Call\_Cnt + 1', which then leads to a circle connector labeled 'Speech'. + +Figure 87: Macro Increment\_Call\_Counter + +![Flowchart for Decrement_Call_Counter macro. It starts with an oval connector, leading to a decision diamond 'Speech call?'. If 'No', it goes to a process box 'Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt - 1' and then to a circle labeled 'Non_Speech'. If 'Yes', it goes to a process box 'Speech_Call_Cnt:= Speech_Call_Cnt - 1' and then to a circle labeled 'Speech'.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +### Macrodefinition Decrement\_Call\_Counter + +Inc\_Call\_Cnt1(1) + +Macro to decrement the correct counter depending on the type of the current call. + +``` +graph TD; Start([ ]) --> Decision{Speech call?}; Decision -- No --> Process1[Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt - 1]; Process1 --> End1((Non_Speech)); Decision -- Yes --> Process2[Speech_Call_Cnt:= Speech_Call_Cnt - 1]; Process2 --> End2((Speech)); +``` + +Flowchart for Decrement\_Call\_Counter macro. It starts with an oval connector, leading to a decision diamond 'Speech call?'. If 'No', it goes to a process box 'Non\_Speech\_Call\_Cnt:= Non\_Speech\_Call\_Cnt - 1' and then to a circle labeled 'Non\_Speech'. If 'Yes', it goes to a process box 'Speech\_Call\_Cnt:= Speech\_Call\_Cnt - 1' and then to a circle labeled 'Speech'. + +Figure 88: Macro Decrement\_Call\_Counter + +## 7.5 TO call + +### 7.5.1 Functional requirements of inter-connecting MSC + +#### 7.5.1.1 Process TO\_MSC + +Sheet 1: the procedure CAMEL\_TOC\_INIT is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "Pass" exit of the test "Result=?". The procedure call formal parameter "First" or "NotFirst" indicates whether the procedure was called earlier in the same call. + +Sheet 1, sheet 4: the procedure CAMEL\_TOC\_Dialled\_Services is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL trunk triggering, processing continues from the "Pass" exit of the test "Result?". The procedure call formal parameter "First" or "NotFirst" indicates whether the procedure was called earlier in the same call. + +Sheet 1: the procedure MOBILE\_NUMBER\_PORTABILITY\_IN\_OQoD is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10]. + +Sheet 1, sheet 2, sheet 3: the procedure CAMEL\_Store\_Destination\_Address is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 1, sheet 4: the procedure CAMEL\_OCH\_MSC\_DISC3 is specific to CAMEL phase 1; it is specified in 3GPP TS 23.078 [12]. + +Sheet 1, sheet 2, sheet 4: the procedure CAMEL\_OCH\_MSC\_DISC4 is specific to CAMEL Phase 2 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 1, sheet 7: the procedure CAMEL\_MT\_CF\_LEG1\_MSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 1, sheet 2: The variable "Return\_Place" indicates at which detection point the additional digit collection is. + +Sheet 1, sheet 2: The "inter-digit timer" is a MSC internal timer to wait for additional dialling from the incoming side. At the expiry of the timer, the MSC/gsmSSF may report digits to the gsmSCF (if the event detection point is armed). This timer is used for the SDL modelling purposes only and it may not present the actual implementations. + +Sheet 2: "Number\_of\_Digits" is the Collected\_Info specific reporting criterion. The gsmSCF specifies the criterion. The process CS\_gsmSSF sends the parameter to the TO\_MSC process. + +Sheet 2: "ST digit" is the ISUP value for a digit indicating that the Called Party Number is complete. + +Sheet 3: the procedures CAMEL\_Start\_TNRy and CAMEL\_Stop\_TNRy are specific to CAMEL phase 2 or later; they are specified in 3GPP TS 23.078 [12]. + +Sheet 3: the procedure CAMEL\_CF\_MSC\_ANSWER is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "Pass" exit of the test "Result?". + +Sheet 3: the procedure UUS\_MSC\_Clear\_UUS is specific to UUS; it is specified in 3GPP TS 23.087 [20]. + +Sheet 3: the procedure CAMEL\_CF\_MSC\_ALERTING is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL phase 4 or later, processing continues from the "Pass" exit of the test "Result?". + +Sheet 4: the procedure CAMEL\_Stop\_TNRy is specific to CAMEL phase 2 or later; it is specified in 3GPP TS 23.078 [12]. + +Sheet 4: the processing in the branch beginning with the Int\_O\_Release input will occur only if the MSC supports CAMEL. + +Sheet 5: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2 or later, and will occur only if the GMSC supports CAMEL phase 2 or later. The procedure CAMEL\_OCH\_MSC2 is specified in 3GPP TS 23.078 [12]. + +Sheet 6: the procedure CAMEL\_OCH\_MSC\_DISC1 is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "No" exit of the test "Result=CAMEL handling?". + +Sheet 6: the procedure CAMEL\_OCH\_MSC\_DISC2 is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "No" exit of the test "Result=Reconnect?". + +Sheet 6: the processing in the branch beginning with the Int\_O\_Release input will occur only if the MSC supports CAMEL. + +Sheet 6: after the process TO\_MSC has sent an IAM to the forwarded-to exchange, it acts as a relay for messages received from the parent process and the forwarded-to exchange. + +Sheet 7: the process CAMEL\_MT\_CF\_LEG2\_MSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. + +![Process TO_MSC flowchart (sheet 1) showing call handling logic for trunk originated calls. It includes states like Idle, Initial Address, and various decision points for CAMEL services and digit processing.](eabcb2f8b9acedb194571d5bc734b463_img.jpg) + +**Process TO\_MSC** TOMSC1(7) + +Process in the MSC to handle trunk originated call. + +Signals to/from the left are to/from the originating switch; signals to/from the right are to/from the destination exchange or MT\_GMSC or ICH\_MSC process depending on the called number. + +``` + +stateDiagram-v2 + [*] --> Idle + Idle --> Initial_Address + Initial_Address --> CAMEL_TOC_MSC_INIT_First + + B --> Result1 + CAMEL_TOC_MSC_INIT_First --> Result1{Result?} + + Result1 --> Leg1: Leg1 + Result1 --> Pass1: Pass + Result1 --> More_Digits1: More_Digits + Result1 --> Fail1: Fail + Result1 --> ELSE1: ELSE + + Leg1 --> Leg1_status + Leg1_status: Leg1_status := Set-up + Leg1_status --> CAMEL_TOC_LEG1_MSC + CAMEL_TOC_LEG1_MSC --> Idle_Leg1: Idle + + Pass1 --> CAMEL_TOC_Dialled_Services_First + C --> CAMEL_TOC_Dialled_Services_First + CAMEL_TOC_Dialled_Services_First --> Result2{Result?} + + Result2 --> Leg1_only: Leg1_only + Result2 --> Abort: Abort + Result2 --> Pass2: Pass + Result2 --> More_Digits2: More_Digits + Result2 --> Fail2: Fail + + Leg1_only --> 4_connector + Abort --> Idle_Abort: Idle + + Pass2 --> MNP: MOBILE_NUMBER_PORTABILITY_IN_OoD + MNP --> CAMEL_Store: CAMEL_Store_Destination_Address (False, False) + CAMEL_Store --> MSC_Coord: MSC_Coord_setup + MSC_Coord --> Wait_For_ACM + 1_connector --> MNP + + More_Digits2 --> Start_Timer2: Start Inter_Digit_timer + Start_Timer2 --> Return_Place2: Return_Place := DialledServices + Return_Place2 --> Wait_For_SAM2: Wait_For_SAM + + Fail2 --> CAMEL_OCH_MSC1 + CAMEL_OCH_MSC1 --> Result3{Result=Reconnect?} + Result3 --> Yes: Yes + Result3 --> No: No + Yes --> 2_connector + No --> Release + + More_Digits1 --> Start_Timer1: Start Inter_Digit_timer + Start_Timer1 --> Return_Place1: Return_Place := Init + Return_Place1 --> Wait_For_SAM1: Wait_For_SAM + + Fail1 --> Release + ELSE1 --> Release + Release --> Idle_End: Idle + +``` + +**Notes and References:** + +- See TS 23.078 (for CAMEL\_TOC\_MSC\_INIT (First)) +- See TS 23.078 (for CAMEL\_TOC\_LEG1\_MSC (Leg1\_status)) +- See TS 23.078 (for CAMEL\_TOC\_Dialled\_Services (First)) +- The duration is a MSC specific and/or interface specific value (for Inter\_Digit\_timer) +- See TS 23.078 (for CAMEL\_OCH\_MSC1) +- See TS 23.066 (for MOBILE\_NUMBER\_PORTABILITY\_IN\_OoD) +- See TS 23.078 (for CAMEL\_Store\_Destination\_Address) + +Process TO\_MSC flowchart (sheet 1) showing call handling logic for trunk originated calls. It includes states like Idle, Initial Address, and various decision points for CAMEL services and digit processing. + +Figure 7.5.1a: Process TO\_MSC (sheet 1) + +![Flowchart for Process TO_MSC (sheet 2). The process starts with a 'Wait_For_SAM' state. It then branches based on 'SAM' (Stop Inter_Digit_timer) or 'Inter_Digit_timer from SELF'. A decision diamond checks if '(Dialled number length >= Number_of_Digits) OR (ST digit received)'. If 'No', it starts 'Inter_Digit_timer' and returns to 'Wait_For_SAM'. If 'Yes', it calls 'CAMEL_Store_Destination_Address (False, False)'. A 'Return_Place?' decision follows, with 'Init' leading to 'CAMEL_TOC_MSC_INIT (NotFirst)' and 'Dialled_Services' leading to 'CAMEL_TOC_Dialled_Services (NotFirst)'. Both lead to connectors 'B' and 'C' respectively, with 'See TS 23.078' notes.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +**Process TO\_MSC** **TOMSC2(7)** + +Process in the MSC to handle trunk originated call. + +Signals to/from the left are to/from the originating switch; signals to/from the right are to/from the destination exchange or MT\_GMSC or ICH\_MSC process depending on the called number. + +``` +graph TD + Start([Wait_For_SAM]) --> SAM{SAM} + SAM --> Stop[Stop Inter_Digit_timer] + Stop --> Decision1{Dialled number length >= Number_of_Digits +OR +(ST digit received)} + Decision1 -- No --> Start[Start Inter_Digit_timer] + Start --> End1([Wait_For_SAM]) + Decision1 -- Yes --> CAMEL_Store[CAMEL_Store_Destination_Address (False, False)] + InterDigitTimer[Inter_Digit_timer from SELF] --> CAMEL_Store + CAMEL_Store --> ReturnPlace{Return_Place?} + ReturnPlace -- Init --> CAMEL_TOC_Init[CAMEL_TOC_MSC_INIT (NotFirst)] + ReturnPlace -- Dialled_Services --> CAMEL_TOC_Dialled[CAMEL_TOC_Dialled_Services (NotFirst)] + CAMEL_TOC_Init --> B((B)) + CAMEL_TOC_Dialled --> C((C)) +``` + +Digits are waited based on timer for modelling purposes. Once timer expires, new digits are reported to gsmSCF. There may be vendor specific differences in this issue. + +Flowchart for Process TO\_MSC (sheet 2). The process starts with a 'Wait\_For\_SAM' state. It then branches based on 'SAM' (Stop Inter\_Digit\_timer) or 'Inter\_Digit\_timer from SELF'. A decision diamond checks if '(Dialled number length >= Number\_of\_Digits) OR (ST digit received)'. If 'No', it starts 'Inter\_Digit\_timer' and returns to 'Wait\_For\_SAM'. If 'Yes', it calls 'CAMEL\_Store\_Destination\_Address (False, False)'. A 'Return\_Place?' decision follows, with 'Init' leading to 'CAMEL\_TOC\_MSC\_INIT (NotFirst)' and 'Dialled\_Services' leading to 'CAMEL\_TOC\_Dialled\_Services (NotFirst)'. Both lead to connectors 'B' and 'C' respectively, with 'See TS 23.078' notes. + +Figure 7.5.1b: Process TO\_MSC (sheet 2) + +![Flowchart for Process TO_MSC (sheet 3).](cc7baa8e5118f4b42c01166637c738ea_img.jpg) + +**Process TO\_MSC** **TOMSC3(7)** + +Process in the MSC to handle trunk originated call. + +Signals to/from the left are to/from the originating switch; signals to/from the right are to/from the destination exchange or MT\_GMSC or ICH\_MSC process depending on the called number. + + + +``` + + graph TD + Wait_For_ACM([Wait_For_ACM]) + Wait_For_ACM --> Connect_In[/Connect/] + Wait_For_ACM --> Addr_Comp_In[/Address Complete/] + + %% Left Branch from Address Complete + Addr_Comp_In --> CAMEL_Start[CAMEL_Start_TNRy] + CAMEL_Start --> UUS_Clear1[UUS_MSC_Clear_UUS] + UUS_Clear1 --> CAMEL_Alert[CAMEL_CF_MSC_ALERTING] + CAMEL_Alert --> Answer_In[/Answer/] + Answer_In --> Result_D1{Result?} + Result_D1 -- Pass --> Addr_Comp_Out[/Address Complete/] + Addr_Comp_Out --> Wait_Answer([Wait_For_Answer]) + Wait_Answer --> Answer_In2[/Answer/] + Answer_In2 --> CAMEL_Stop[CAMEL_Stop_TNRy] + CAMEL_Stop --> CAMEL_Ans1[CAMEL_CF_MSC_ANSWER] + CAMEL_Ans1 --> Result_D2{Result?} + Result_D2 -- Pass --> UUS_Clear2[UUS_MSC_Clear_UUS] + UUS_Clear2 --> Answer_Out1[/Answer/] + Answer_Out1 --> A1((A)) + + %% Right Branch from Connect + Connect_In --> SAM_In[/SAM/] + SAM_In --> CAMEL_Store[CAMEL_Store_Destination_Address +(False, False)] + CAMEL_Store --> SAM_In2[/SAM/] + SAM_In2 --> Dash_State([ - ]) + Dash_State --> UUS_Clear3[UUS_MSC_Clear_UUS] + UUS_Clear3 --> CAMEL_Ans2[CAMEL_CF_MSC_ANSWER] + CAMEL_Ans2 --> Result_D3{Result?} + Result_D3 -- Pass --> Connect_Out[/Connect/] + Connect_Out --> A2((A)) + + %% Reconnect Logic + Result_D1 -- Else --> Reconnect_D{Reconnect Result?} + Result_D2 -- Else --> Reconnect_D + Result_D3 -- Else --> Reconnect_D + + Reconnect_D -- Pass --> Conn2((2)) + Reconnect_D -- Release --> Release_Task[Release] + Reconnect_D -- Fail --> Release_Task + Release_Task --> Idle([Idle]) + + %% Callouts + subgraph Callouts + direction LR + C1[See TS 23.078] --- CAMEL_Start + C2[See TS 23.087] --- UUS_Clear1 + C3[See TS 23.078] --- CAMEL_Alert + C4[See TS 23.078] --- CAMEL_Stop + C5[See TS 23.078] --- CAMEL_Ans1 + C6[See TS 23.087] --- UUS_Clear2 + C7[See TS 23.078] --- CAMEL_Store + C8[See TS 23.087] --- UUS_Clear3 + C9[See TS 23.078] --- CAMEL_Ans2 + end + +``` + +Flowchart for Process TO\_MSC (sheet 3). + +Figure 7.5.1c: Process TO\_MSC (sheet 3) + +![Flowchart for Process TO_MSC (sheet 4). The process starts with 'Wait_For_ACM, Wait_For_Answer'. It branches into two 'Release' paths. The left path checks 'CAMEL trunk triggering supported?'. If 'No', it goes to 'CAMEL_OCH_MSC_DISC3' then 'Release'. If 'Yes', it goes to 'CAMEL_OCH_MSC_DISC4' then 'Release'. The right path checks 'CAMEL trunk triggering supported?'. If 'No', it goes to 'CAMEL_OCH_MSC_DISC3' then 'Release'. If 'Yes', it checks 'Release cause= No answer from user?'. If 'Yes', it goes to connector '3'. If 'No', it goes to 'CAMEL_OCH_MSC1' (See TS 23.078) then to 'Result= Reconnect?'. If 'No', it goes to 'Release'. If 'Yes', it goes to 'CAMEL_Stop_TNRy' (See TS 23.078) then to connector '2'. A third 'Release' path from 'From gsmSSF' via 'Int_ReleaseCall' leads to 'Release'. All 'Release' paths converge to 'Release call resources' then 'Idle'.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +**Process TO\_MSC** **TOMSC4(7)** + +Process in the MSC to handle trunk originated call. + +Signals to/from the left are to/from the originating switch; signals to/from the right are to/from the destination exchange or MT\_GMSC or ICH\_MSC process depending on the called number. + +``` +graph TD + Start([Wait_For_ACM, Wait_For_Answer]) --> Release1((Release)) + Start --> Release2((Release)) + Release1 --> CAMEL_trunk_triggered1{CAMEL trunk triggering supported?} + CAMEL_trunk_triggered1 -- No --> CAMEL_OCH_MSC_DISC3_1[CAMEL_OCH_MSC_DISC3] + CAMEL_trunk_triggered1 -- Yes --> CAMEL_OCH_MSC_DISC4_1[CAMEL_OCH_MSC_DISC4] + CAMEL_OCH_MSC_DISC3_1 --> Release3((Release)) + CAMEL_OCH_MSC_DISC4_1 --> Release4((Release)) + Release2 --> CAMEL_trunk_triggered2{CAMEL trunk triggering supported?} + CAMEL_trunk_triggered2 -- No --> CAMEL_OCH_MSC_DISC3_2[CAMEL_OCH_MSC_DISC3] + CAMEL_trunk_triggered2 -- Yes --> Release_cause{Release cause= No answer from user?} + Release_cause -- Yes --> Connector3((3)) + CAMEL_OCH_MSC_DISC3_2 --> Release5((Release)) + CAMEL_OCH_MSC_DISC3_2 --> CAMEL_OCH_MSC1_1[CAMEL_OCH_MSC1] + CAMEL_OCH_MSC1_1 --> See_TS_23_078_1[See TS 23.078] + CAMEL_OCH_MSC1_1 --> Result_Reconnect{Result= Reconnect?} + Result_Reconnect -- No --> Release6((Release)) + Result_Reconnect -- Yes --> CAMEL_Stop_TNRy_1[CAMEL_Stop_TNRy] + CAMEL_Stop_TNRy_1 --> See_TS_23_078_2[See TS 23.078] + CAMEL_Stop_TNRy_1 --> Connector2((2)) + From_gsmSSF[From gsmSSF] --> Int_ReleaseCall((Int_ReleaseCall)) + Int_ReleaseCall --> Release7((Release)) + Release3 --> Release_call_resources[Release call resources] + Release4 --> Release_call_resources + Release5 --> Release_call_resources + Release6 --> Release_call_resources + Release7 --> Release_call_resources + Release_call_resources --> Idle([Idle]) +``` + +Flowchart for Process TO\_MSC (sheet 4). The process starts with 'Wait\_For\_ACM, Wait\_For\_Answer'. It branches into two 'Release' paths. The left path checks 'CAMEL trunk triggering supported?'. If 'No', it goes to 'CAMEL\_OCH\_MSC\_DISC3' then 'Release'. If 'Yes', it goes to 'CAMEL\_OCH\_MSC\_DISC4' then 'Release'. The right path checks 'CAMEL trunk triggering supported?'. If 'No', it goes to 'CAMEL\_OCH\_MSC\_DISC3' then 'Release'. If 'Yes', it checks 'Release cause= No answer from user?'. If 'Yes', it goes to connector '3'. If 'No', it goes to 'CAMEL\_OCH\_MSC1' (See TS 23.078) then to 'Result= Reconnect?'. If 'No', it goes to 'Release'. If 'Yes', it goes to 'CAMEL\_Stop\_TNRy' (See TS 23.078) then to connector '2'. A third 'Release' path from 'From gsmSSF' via 'Int\_ReleaseCall' leads to 'Release'. All 'Release' paths converge to 'Release call resources' then 'Idle'. + +Figure 7.5.1d: Process TO\_MSC (sheet 4) + +![Flowchart for Process TO_MSC (sheet 5). The process starts with 'Wait_For_Answer', followed by 'TNRy expired' (Internal). It then proceeds to 'Release' (labeled with connector 3). Next is 'CAMEL_OCH_MSC2' (See TS 23.078). A decision 'Result?' follows with 'Release' (left), 'Reconnect' (right), and 'Fail' (down). 'Reconnect' leads to 'CAMEL_TOCL_Dialled_Services_(First)' (See TS 23.078) and connector 2. 'Fail' leads to a decision 'Result?' with 'Abort' (left), 'Pass' (right, connector 1), and 'Fail' (down). 'Abort' leads to 'Release call resources' (See TS 23.078) and 'Idle'. 'Pass' leads to 'CAMEL_OCH_MSC1'. A decision 'Result=Reconnect?' follows with 'Yes' (right, connector 1), 'No' (down), and 'Release' (left). 'No' leads to 'Release' and 'Idle'.](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) + +**Process TO\_MSC** **TOMSC5(7)** + +Process in the MSC to handle trunk originated call. + +Signals to/from the left are to/from the originating switch; signals to/from the right are to/from the destination exchange or MT\_GMSC or ICH\_MSC process depending on the called number. + +``` +graph TD; Start([Wait_For_Answer]) --> TNRy[TNRy expired]; TNRy --- Internal[Internal]; TNRy --> Release1[Release]; Release1 --> C3((3)); C3 --> CAMELOCH2[CAMEL_OCH_MSC2]; CAMELOCH2 --- TS23078_1[See TS 23.078]; CAMELOCH2 --> Result1{Result?}; Result1 -- Release --> Release2[Release]; Result1 -- Reconnect --> CAMELTOCL[CAMEL_TOCL_Dialled_Services_(First)]; CAMELTOCL --- TS23078_2[See TS 23.078]; CAMELTOCL --> C2_1((2)); Result1 -- Fail --> Result2{Result?}; Result2 -- Abort --> ReleaseCall[Release call resources]; ReleaseCall --- TS23078_3[See TS 23.078]; ReleaseCall --> Idle1([Idle]); Result2 -- Pass --> C1_1((1)); Result2 -- Fail --> CAMELOCH1[CAMEL_OCH_MSC1]; CAMELOCH1 --> Result3{Result=Reconnect?}; Result3 -- Yes --> C1_2((1)); Result3 -- No --> Release3[Release]; Release3 --> Idle2([Idle]); Result3 -- Release --> Release3; +``` + +Flowchart for Process TO\_MSC (sheet 5). The process starts with 'Wait\_For\_Answer', followed by 'TNRy expired' (Internal). It then proceeds to 'Release' (labeled with connector 3). Next is 'CAMEL\_OCH\_MSC2' (See TS 23.078). A decision 'Result?' follows with 'Release' (left), 'Reconnect' (right), and 'Fail' (down). 'Reconnect' leads to 'CAMEL\_TOCL\_Dialled\_Services\_(First)' (See TS 23.078) and connector 2. 'Fail' leads to a decision 'Result?' with 'Abort' (left), 'Pass' (right, connector 1), and 'Fail' (down). 'Abort' leads to 'Release call resources' (See TS 23.078) and 'Idle'. 'Pass' leads to 'CAMEL\_OCH\_MSC1'. A decision 'Result=Reconnect?' follows with 'Yes' (right, connector 1), 'No' (down), and 'Release' (left). 'No' leads to 'Release' and 'Idle'. + +Figure 7.5.1e: Process TO\_MSC (sheet 5) + +![State transition diagram for Process TO_MSC. It starts at 'Wait_For_Clear' and branches into three paths: 'Release' (left), 'Release' (middle, via CAMEL_OCH_MSC_DISC1/2), and 'Int_ReleaseCall' (right, from gsmSSF). All paths lead to 'Release call resources' and then 'Idle'. A second part of the diagram shows a '*' state transitioning to two parallel paths with '*' and '-' labels, converging to a '-' state.](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +**Process TO\_MSC** + +TOMSC6(7) + +Process in the MSC to handle trunk originated call. + +Signals to/from the left are to/from the originating switch; signals to/from the right are to/from the destination exchange or MT\_GMSC or ICH\_MSC process depending on the called number. + +``` +stateDiagram-v2 + [*] --> Wait_For_Clear + state "Process TO_MSC" as TO_MSC { + [*] --> Release1[Release] + Release1 --> CAMEL_OCH_MSC_DISC1[CAMEL_OCH_MSC_DISC1] + CAMEL_OCH_MSC_DISC1 --> Result_CAMEL_Handling1{Result=CAMEL Handling?} + Result_CAMEL_Handling1 -- No --> Release1 + Result_CAMEL_Handling1 -- Yes --> Release1 + Release1 --> See_TS_23_078_1[See TS 23.078] + Release1 --> Release2[Release] + Release2 --> CAMEL_OCH_MSC_DISC2[CAMEL_OCH_MSC_DISC2] + CAMEL_OCH_MSC_DISC2 --> Result_CAMEL_Handling2{Result=CAMEL Handling?} + Result_CAMEL_Handling2 -- No --> Release2 + Result_CAMEL_Handling2 -- Yes --> Result_Reconnect{Result=Reconnect?} + Result_Reconnect -- No --> Release2 + Result_Reconnect -- Yes --> 2((2)) + Release2 --> See_TS_23_078_2[See TS 23.078] + Release2 --> Release3[Release] + Int_ReleaseCall[From gsmSSF] --> Release3 + Release3 --> Release4[Release] + Release1 --> ReleaseCallResources[Release call resources] + Release2 --> ReleaseCallResources + Release3 --> ReleaseCallResources + ReleaseCallResources --> Idle[Idle] + } + state "*" as StarState { + [*] --> StarState + StarState --> StarLeft[*] + StarState --> StarRight[*] + StarLeft --> DashLeft[-] + StarRight --> DashRight[-] + DashLeft --> DashBottom[-] + DashRight --> DashBottom + } +``` + +State transition diagram for Process TO\_MSC. It starts at 'Wait\_For\_Clear' and branches into three paths: 'Release' (left), 'Release' (middle, via CAMEL\_OCH\_MSC\_DISC1/2), and 'Int\_ReleaseCall' (right, from gsmSSF). All paths lead to 'Release call resources' and then 'Idle'. A second part of the diagram shows a '\*' state transitioning to two parallel paths with '\*' and '-' labels, converging to a '-' state. + +Figure 7.5.1f: Process TO\_MSC (sheet 6) + +![Flowchart for Process TO_MSC (sheet 7). The process starts at connector 'A', which leads to a decision diamond 'CAMEL phase 4 or later control relationship exists?'. If 'No', it goes to 'Wait_For_Clear'. If 'Yes', it goes to a process box 'CAMEL_MT_CF_LEG2_MSC' (with a 'See TS 23.078' note), then to 'Leg1_status := Active' (with a note about CAMEL_MF_RECONNECT_MSC parameters), then to 'CAMEL_TOC (LEG1_MSC) (Leg1_status)' (with a 'See TS 23.078' note), and finally to 'Idle'.](da85343976fdbb19f866d9ddbdad0eae_img.jpg) + +Process TO\_MSC + +TOMSC7(7) + +Process in the MSC +to handle +trunk originated call. + +``` +graph TD; A((A)) --> D{CAMEL phase 4 or later control relationship exists?}; D -- No --> WFC([Wait_For_Clear]); D -- Yes --> P1[CAMEL_MT_CF_LEG2_MSC]; P1 --> L1[Leg1_status := Active]; L1 --> P2[CAMEL_TOC (LEG1_MSC) (Leg1_status)]; P2 --> I([Idle]); +``` + +When this process calls CAMEL\_MF\_RECONNECT\_MSC the formal call parameters "BOR" and "Forwarding" in CAMEL\_Store\_Destination\_Address shall be "False". + +Flowchart for Process TO\_MSC (sheet 7). The process starts at connector 'A', which leads to a decision diamond 'CAMEL phase 4 or later control relationship exists?'. If 'No', it goes to 'Wait\_For\_Clear'. If 'Yes', it goes to a process box 'CAMEL\_MT\_CF\_LEG2\_MSC' (with a 'See TS 23.078' note), then to 'Leg1\_status := Active' (with a note about CAMEL\_MF\_RECONNECT\_MSC parameters), then to 'CAMEL\_TOC (LEG1\_MSC) (Leg1\_status)' (with a 'See TS 23.078' note), and finally to 'Idle'. + +Figure 7.5.1g: Process TO\_MSC (sheet 7) + +# 8 Contents of messages + +This clause specifies the content of each message shown in clauses 5 and 7, except for the following messages, which are not specific to call handling: + +On the D interface (VLR-HLR): + +- Abort; +- Activate Trace Mode; +- Authentication Failure Report; +- Insert Subscriber Data; + +- Send Authentication Info; +- Send Authentication Info ack; +- Send Authentication Info negative response; + +In the tables which follow, information elements are shown as mandatory (M), conditional (C) or optional (O). A mandatory information element shall always be present. A conditional information element shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent. An optional element may be present or absent, at the discretion of the application at the sending entity. + +Some messages which are defined in this clause are used for other services or features. The specifications (referred to below as "derived specifications") for those services or features may simply refer to the present document for the definition of the message; in this case the requirements for the presence of each information element are as defined in this clause. If the specification for a service or feature requires information elements in a message additional to those specified in this clause, the requirements for the presence of the additional information elements are specified in the relevant specification. If the specification for a service or feature has different requirements for the presence of an information element in a message which is specified in this clause, then the following principles apply: + +- If the information element is shown as mandatory in this clause, it shall always be present. +- If the information element is shown as conditional or optional in this clause, but mandatory in the derived specification, it shall always be present in the context of the service or feature defined in the derived specification. +- If the information element is shown as conditional or optional in this clause, and the conditions in the derived specification require the information element to be present, it shall be present even if the conditions in this clause do not require it to be present. + +## 8.1 Messages on the B interface (MSC-VLR) + +### 8.1.1 Abort + +The following information element is required: + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------------| +| Abort reason | M | Indicates the reason for the procedure being aborted. | + +### 8.1.2 Authenticate + +The following information elements are required for authentication of a UMTS UE: + +| Information element name | Required | Description | +|--------------------------|----------|--------------------------------------------------------------------| +| RAND(I) | M | Random number challenge to be sent to the MS (3GPP TS 33.102 [32]) | +| AUTN(I) | M | Authentication token to be sent to the MS (3GPP TS 33.102 [32]) | + +The following information elements are required for authentication of a GSM MS: + +| Information element name | Required | Description | +|--------------------------|----------|----------------------------------------------------------------------| +| RAND | M | Random number challenge to be sent to the MS (3GPP TS 43.020 [1]) | +| CKSN | M | Cipher key sequence number to be sent to the MS (3GPP TS 43.020 [1]) | + +### 8.1.3 Authenticate ack + +The following information element is required for authentication of a UMTS UE: + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------| +| RES(I) | M | Result returned by the MS (3GPP TS 33.102 [32]) | + +The following information element is required for authentication of a GSM MS: + +| Information element name | Required | Description | +|--------------------------|----------|----------------------------------------------------------| +| SRES | M | Signature result returned by the MS (3GPP TS 43.020 [1]) | + +### 8.1.4 Authenticate negative response + +The negative response information element can take the following value: + +- wrong network signature. + +### 8.1.5 Call arrived + +This message contains no information elements. + +### 8.1.6 Check IMEI + +This message contains no information elements. + +### 8.1.7 Check IMEI ack + +The following information element is required: + +| Information element name | Required | Description | +|--------------------------|----------|-----------------------------------------------------------------------| +| Equipment status | M | Indicates whether the ME is black-listed, grey-listed or white-listed | + +### 8.1.8 Check IMEI negative response + +The negative response information element can take the following values: + +- System failure; +- Unknown equipment. + +### 8.1.9 Complete Call + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MSISDN | C | MSISDN of the MS for which the Complete Call is sent. Shall be present for an ordinary MO call, for an MT call and for an emergency call when the MS is registered in the VLR; otherwise shall be absent. | +| IMEI | C | IMEI of the mobile for which the Complete Call is sent. Shall be present for an emergency call when the mobile is identified only by its IMEI; otherwise shall be absent. | + +| Information element name | Required | Description | +|-------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Category | C | Category of the MS for which the Complete Call is sent. Shall be present for an ordinary MO call and for an emergency call when the MS is registered in the VLR; otherwise shall be absent. | +| PLMN bearer capability | C | Shall be present for an MT call according to the rules defined in 3GPP TS 29.007 [30]. | +| ISDN bearer capability | C | Shall be present for an MT call if it was received in the Provide Roaming Number; otherwise shall be absent. | +| ISDN low layer compatibility | C | Shall be present for an MT call if it was received in the Provide Roaming Number; otherwise shall be absent. | +| ISDN high layer compatibility | C | Shall be present for an MT call if it was received in the Provide Roaming Number; otherwise shall be absent. | +| CLIP provision | C | Indicates that CLIP is provisioned. Shall be present for an MT call if CLIP is provisioned; otherwise shall be absent. | +| CLIR override provision | C | Indicates that the CLIR override subscription option of CLIP is provisioned. Shall be present for an MT call if CLIP is provisioned with the CLIR override subscription option and the MS is registered in the HPLMN country; otherwise shall be absent. | +| CLIR provision | C | Indicates that CLIR is provisioned. Shall be present for an MO call if CLIR is provisioned; otherwise shall be absent. | +| CLIR mode | C | Indicates the mode in which CLIR is provisioned: permanent, temporary (default presentation allowed) or temporary (default presentation restricted). Shall be present for an MO call if CLIR is provisioned; otherwise shall be absent. | +| COLP provision | C | Indicates that COLP is provisioned. Shall be present for an MO call if COLP is provisioned; otherwise shall be absent. | +| COLR override provision | C | Indicates that the COLR override subscription option of COLP is provisioned. Shall be present for an MO call if COLP is provisioned with the COLR override subscription option and the MS is registered in the HPLMN country; otherwise shall be absent. | +| COLR provision | C | Indicates that COLR is provisioned. Shall be present for an MT call if COLR is provisioned; otherwise shall be absent. | +| No Reply Condition Timer | C | Value of timer to be used to determine the No subscriber reply condition. Shall be present for an MT call if the Call Forwarding on No Reply service is active and operative; otherwise shall be absent. | +| CUG index | C | For the definition of this IE, see 3GPP TS 23.085 [18]. May be present (as a network operator option) for an ordinary MO call if the call is a CUG call; shall be present for an MT call if the call is a CUG call; otherwise shall be absent. | +| CUG interlock | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present for an ordinary MO call if the call is a CUG call; otherwise shall be absent. | +| CUG outgoing access | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present for an ordinary MO call if the call is a CUG call with outgoing access; otherwise shall be absent. | +| Advice of Charge provision | C | Indicates whether Advice of Charge (Information) or Advice of Charge (Charging) is provisioned. Shall be present for an ordinary MO call or an MT call if Advice of Charge is provisioned; otherwise shall be absent. | +| Alerting Pattern | C | Shall be present for an MT call if it was received in the Provide Roaming Number and if the feature is supported by the MSC/VLR; otherwise shall be absent. | +| NAEA preferred Carrier Id | O | The preferred carrier identity identifying the carrier to be used to route the interexchange call if the call requires routing via an interexchange carrier. This parameter may be included at the discretion of the VLR operator. | + +### 8.1.10 Complete Call ack + +This message contains no information elements. + +### 8.1.11 Complete Call negative response + +The negative response information element can take the following values: + +- Absent subscriber; +- Busy subscriber; +- No subscriber reply; +- Radio congestion. + +### 8.1.12 Forward New TMSI + +The following information element is required: + +| Information element name | Required | Description | +|--------------------------|----------|----------------------------| +| TMSI | M | TMSI to be sent to the MS. | + +### 8.1.13 Forward New TMSI ack + +This message contains no information elements. + +### 8.1.14 Forward New TMSI negative response + +The negative response information element can take the following value: + +- TMSI reallocation failure. + +### 8.1.15 Obtain Subscriber Info + +The following information elements are required: + +| Information element name | Required | Description | +|----------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | IMSI of the MS for which information is required. | +| Subscriber state requested | C | Indicates that the VLR requires state information for the MS. Shall be present if state information is required; otherwise shall be absent. | + +### 8.1.16 Obtain Subscriber Info ack + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Subscriber state | C | Indicates whether the MS is busy (i.e. engaged on a circuit-switched call) or assumed idle. Shall be present if the VLR requested state information; otherwise shall be absent. | + +### 8.1.17 Page MS + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | IMSI of the MS to be paged. | +| Location area ID | M | Location area in which the MS is to be paged. | +| Page type | M | Indicates whether the paging is for a circuit-switched call, MT SMS delivery, SS activity or Active Location Retrieval. | +| Requested information | C | Indicates the information requested by the VLR – one or more of:
- Location;
- MS classmark;
- IMEI.
Shall be present if the Page type is Active Information Retrieval; otherwise shall be absent. | +| Paging via SGSN possible | C | Indicates that paging via the SGSN is possible. Shall be present if the VLR determines that the MS can be paged via the SGSN; otherwise shall be absent. | +| TMSI | O | TMSI to be broadcast to identify the MS. | +| Call Priority | O | This parameter indicates the eMLPP priority of the call (see 3GPP TS 23.067 [39]). This parameter should be present if the VLR supports the eMLPP feature and if the Call Priority was received in the MAP_PROVIDE_ROAMING_NUMBER request or in the MAP_PROVIDE_SUBSCRIBER_INFO request. | + +### 8.1.18 Page MS ack + +The following information elements are required: + +| Information element name | Required | Description | +|------------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location area ID | M | Location area in which the MS responded to the page. | +| Serving cell ID | M | Identity of the cell in which the served subscriber is located. Shall be present if the MS uses GSM radio access; otherwise shall be absent. | +| Service area ID | C | Service area identity of the cell in which the served subscriber is located. Shall be present if the MS uses UMTS radio access; otherwise shall be absent. | +| MS classmark | M | MS classmark 2 as defined in 3GPP TS 24.008 [26]. | +| IMEI (with software version) | C | IMEISV as defined in 3GPP TS 23.003 [5]. Shall be present if the IMEI was requested in the Page MS message and the MSC retrieved it from the MS; otherwise shall be absent. | + +### 8.1.19 Page MS negative response + +The negative response information element can take the following values: + +- Absent subscriber; +- Busy subscriber (More calls possible); +- Busy subscriber (NDUB); +- System failure; +- Unknown location area ID. + +The Page MS negative response Busy subscriber (More calls possible) also indicates the basic service which applies for the established call. + +### 8.1.20 Page MS via SGSN + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------| +| IMSI | M | IMSI of the MS to be paged. | +| eMLPP priority | O | Circuit-switched paging priority. | +| TMSI | O | TMSI to be broadcast to identify the MS. | +| Channel type | O | Type of channel required for the call. | + +### 8.1.21 Process Access Request + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CM service type | M | Indicates the type of access required: normal MO call, emergency call or page response. Other values (short message service and SS request) defined for this IE are not considered in the present document. | +| Access connection status | M | Indicates whether or not the connection to the MS is ciphered and whether or not it is authenticated. | +| Current location area ID | M | Identity of the location area from which the access request was received. | +| Service area ID | C | Identity of the service area (for UMTS access) in use by the served subscriber. Shall be present for UMTS access; otherwise shall be absent. | +| Serving cell ID | C | Identity of the cell (for GSM access) in use by the served subscriber. Shall be present for GSM access; otherwise shall be absent. | +| IMSI | C | IMSI of the MS requesting the access. For normal MO call or page response, one of IMSI or TMSI shall be present. For emergency call, one of IMSI, TMSI or IMEI shall be present. | +| TMSI | C | TMSI of the MS requesting the access. For normal MO call or page response, one of IMSI or TMSI shall be present. For emergency call, one of IMSI, TMSI or IMEI shall be present. | +| IMEI | C | IMEI of the MS requesting the access. For normal MO call or page response, one of IMSI or TMSI shall be present. For emergency call, one of IMSI, TMSI or IMEI shall be present. | +| CKSN | C | Cipher key sequence number of the MS requesting the access. Shall be present if TMSI is present; otherwise shall be absent. | +| CSG Id | C | Identifier of the closed subscriber group. Shall be present if the serving cell is a CSG cell or a hybrid cell. | +| Cell Access Mode | C | Indicates that the serving cell operates in Hybrid Access mode. Shall be present if the serving cell is a Hybrid cell. | + +### 8.1.22 Process Access Request ack + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | C | IMSI of the MS requesting the access. For normal MO call or page response, shall be present. For emergency call, one of IMSI or IMEI shall be present. | +| IMEI | C | IMEI of the MS requesting the access. For normal MO call or page response, shall be absent. For emergency call, one of IMSI or IMEI shall be present. | +| MSISDN | O | MSISDN of the MS requesting the access. | +| CSG Membership Status | C | Indicates the Membership status of the UE to a particular CSG. Shall be present if the serving cell is a Hybrid cell. | + +### 8.1.23 Process Access Request negative response + +The negative response information element can take the following values: + +- Roaming not allowed; +- System failure; +- Unidentified subscriber; +- Illegal equipment; +- Illegal subscriber; +- Not authorized for this CSG. + +### 8.1.24 Process Call Waiting + +The following information elements are required: + +| Information element name | Required | Description | +|-------------------------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MSISDN | M | MSISDN of the MS for which the Process Call Waiting is sent. | +| PLMN bearer capability | C | Shall be present according to the rules defined in 3GPP TS 29.007 [30]. | +| ISDN bearer capability | C | Shall be present if it was received in the Provide Roaming Number for the waiting call; otherwise shall be absent. | +| ISDN low layer compatibility | C | Shall be present if it was received in the Provide Roaming Number for the waiting call; otherwise shall be absent. | +| ISDN high layer compatibility | C | Shall be present if it was received in the Provide Roaming Number for the waiting call; otherwise shall be absent. | +| CLIP provision | C | Indicates that CLIP is provisioned. Shall be present if CLIP is provisioned; otherwise shall be absent. | +| CLIR override provision | C | Indicates that the CLIR override subscription option of CLIP is provisioned. Shall be present if CLIP is provisioned with the CLIR override subscription option and the MS is registered in the HPLMN country; otherwise shall be absent. | +| COLR provision | C | Indicates that COLR is provisioned. Shall be present if COLR is provisioned; otherwise shall be absent. | +| No Reply Condition Timer | C | Value of timer to be used to determine the No subscriber reply condition. Shall be present if the Call Forwarding on No Reply service is active and operative; otherwise shall be absent. | +| CUG index | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present if the waiting call is a CUG call; otherwise shall be absent. | +| Advice of Charge provision | C | Indicates whether Advice of Charge (Information) or Advice of Charge (Charging) is provisioned. Shall be present if Advice of Charge is provisioned; otherwise shall be absent. | + +### 8.1.25 Process Call Waiting ack + +This message contains no information elements. + +### 8.1.26 Process Call Waiting negative response + +The negative response information element can take the following values: + +- Busy subscriber (UDUB); +- Busy subscriber (NDUB); +- No subscriber reply. + +### 8.1.27 Provide IMEI + +This message contains no information elements. + +### 8.1.28 Provide IMEI ack + +The following information element is required: + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------------------------------------------| +| IMEI | M | IMEISV (as defined in 3GPP TS 23.003 [5]) of the ME involved in the access request. | + +### 8.1.29 Provide IMSI + +This message contains no information elements. + +### 8.1.30 Provide IMSI ack + +The following information element is required: + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------| +| IMSI | M | IMSI of the MS involved in the access request. | + +### 8.1.31 Radio connection released + +This message contains no information elements. + +### 8.1.32 Search For MS + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | IMSI of the MS to be paged in all location areas. | +| Page type | M | Indicates whether the paging is for a circuit-switched call, MT SMS delivery, SS activity or Active Location Retrieval. | +| Requested information | C | Indicates the information requested by the VLR – one or more of:
- Location;
- MS classmark;
- IMEI.
Shall be present if the Page type is Active Information Retrieval; otherwise shall be absent. | +| Paging via SGSN possible | C | Indicates that paging via the SGSN is possible. Shall be present if the VLR determines that the MS can be paged via the SGSN; otherwise shall be absent. | +| TMSI | O | TMSI to be broadcast to identify the MS. | +| Paging area | O | May be present if the Paging type is circuit switched call, if the Paging Area function is supported and if the paging area is available; otherwise it shall be absent. It indicates the set of Location Areas in which the MS is to be paged on the A interface if Location area ID is not known in VLR. | +| Call Priority | O | This parameter indicates the eMLPP priority of the call (see 3GPP TS 23.067 [39]). This parameter should be present if the VLR supports the eMLPP feature and if the Call Priority was received in the MAP_PROVIDE_ROAMING_NUMBER request or in the MAP_PROVIDE_SUBSCRIBER_INFO request. | + +### 8.1.33 Search For MS ack + +The following information element is required: + +| Information element name | Required | Description | +|------------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location area ID | M | Location area in which the MS responded to the page. | +| Serving cell ID | C | Identity of the cell in which the served subscriber is located. Shall be present if the MS uses GSM radio access; otherwise shall be absent. | +| Service area ID | C | Service area identity of the cell in which the served subscriber is located. Shall be present if the MS uses UMTS radio access; otherwise shall be absent. | +| MS classmark | M | MS classmark 2 as defined in 3GPP TS 24.008 [26]. | +| IMEI (with software version) | C | IMEISV as defined in 3GPP TS 23.003 [5]. Shall be present if the IMEI was requested in the Page MS message and the MSC retrieved it from the MS; otherwise shall be absent. | + +### 8.1.34 Search For MS negative response + +The negative response information element can take the following values: + +- Absent subscriber; +- Busy subscriber (More calls possible); +- Busy subscriber (NDUB); +- System failure. + +The Search For MS negative response Busy subscriber (More calls possible) also indicates the basic service which applies for the established call. + +### 8.1.35 Search for MS via SGSN + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------| +| IMSI | M | IMSI of the MS to be paged. | +| eMLPP priority | O | Circuit-switched paging priority. | +| TMSI | O | TMSI to be broadcast to identify the MS. | +| Channel type | O | Type of channel required for the call. | + +### 8.1.36 Send Info For Incoming Call + +The following information elements are required: + +| Information element name | Required | Description | +|---------------------------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MSRN | M | Mobile Station Roaming Number received in the IAM. | +| Bearer service | C | Bearer service required for the MT call. Shall be present if the MSC was able to derive a bearer service from ISDN BC/LLC/HLC information received in the IAM; otherwise shall be absent. | +| Teleservice | C | Teleservice required for the MT call. Shall be present if the MSC was able to derive a teleservice from ISDN BC/LLC/HLC information received in the IAM; otherwise shall be absent. | +| Dialled number | C | Number dialled by the calling subscriber. Shall be present if it was received in the IAM; otherwise shall be absent. | +| Number of forwarding | C | Number of times the incoming call has already been forwarded. Shall be present if it was received in the IAM; otherwise shall be absent. | +| CUG interlock | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present if it was received in the IAM; otherwise shall be absent. | +| CUG outgoing access | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present if it was received in the IAM; otherwise shall be absent. | +| MT Roaming Forwarding Supported | C | Indication that the MSC supports the MT Roaming Forwarding feature. Shall be present if the MSC supports that feature, otherwise shall be absent. | + +### 8.1.37 Send Info For Incoming Call ack + +The following information elements are required: + +| Information element name | Required | Description | +|----------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | IMSI of the B subscriber. | +| Forwarded-to number | C | E.164 number of the C subscriber. Shall be present if the call is to be forwarded other than for MT roaming retry reason. | +| Forwarding reason | C | Indication of why the call has been forwarded (on call deflection, on mobile subscriber busy, on mobile subscriber not reachable or on no subscriber reply). Shall be present if the call is to be forwarded other than for MT roaming retry reason. | +| Notification to calling party | C | Indication of whether the calling party is to be notified that the call has been forwarded. Shall be present if the call is to be forwarded other than for MT roaming retry reason. | +| Notification to forwarding party | C | Indication of whether the forwarding party is to be notified that the call has been forwarded. Shall be present if the call is to be forwarded on mobile subscriber busy or on no subscriber reply; otherwise shall be absent. | +| Forwarded-to subaddress | C | Subaddress of the C subscriber (see 3GPP TS 23.003 [5]). Shall be present if a forwarded-to subaddress is stored in the VLR in association with the forwarded-to number; otherwise shall be absent. | +| Redirecting presentation | C | Indication of whether the MSISDN of B subscriber shall be presented to the C subscriber. Shall be present if the call is to be forwarded, otherwise shall be absent. | +| MSISDN | C | E.164 number which identifies the B subscriber. It will be used to create the redirecting number presented to the C subscriber. Shall be present if the call is to be forwarded, otherwise shall be absent. | +| CUG interlock | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present if the VLR has determined that the forwarded call is to be treated as a CUG call in accordance with the rules in 3GPP TS 23.085 [18], otherwise shall be absent. | +| CUG outgoing access | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present if the VLR has determined that the forwarded call is to be treated as a CUG call with outgoing access in accordance with the rules in 3GPP TS 23.085 [18], otherwise shall be absent. | +| NAEA preferred Carrier Id | O | The preferred carrier identity identifying the carrier to be used to route the interexchange call if the forwarded call requires routing via an interexchange carrier. This parameter may be included at the discretion of the VLR operator. | +| MT Roaming Retry Indicator | C | Indication that the call is forwarded for MT roaming retry. All other forwarding parameters are not relevant if this IE is present. | +| MT Roaming Forwarding Indicator | C | Indication that the call is forwarded for MT Roaming Forwarding. All other forwarding parameters are not relevant if this IE is present. | +| MSRN for MT Roaming Forwarding | C | Mobile Station Roaming Number received in the MAP PROVIDE ROAMING NUMBER response from the new VLR. Shall be present if the MT Roaming Forwarding Indicator is present, otherwise shall be absent. | + +### 8.1.38 Send Info For Incoming Call negative response + +The negative response information element can take the following values: + +- Absent subscriber; +- Busy subscriber; +- CUG reject (Called party SS interaction violation); +- Forwarding violation; +- Impossible call completion; + +- No subscriber reply; +- System failure; +- Unallocated roaming number; + +### 8.1.39 Send Info For Outgoing Call + +The following information elements are required: + +| Information element name | Required | Description | +|------------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Called number | M | E.164 number of the call destination. | +| Bearer service | C | Bearer service required for the MO call, derived from the PLMN bearer capability information received in the set-up request from the MS. One of bearer service or teleservice shall be present. | +| Teleservice | C | Teleservice required for the MO call, derived from the PLMN bearer capability information received in the set-up request from the MS or from the emergency set-up request from the MS. One of bearer service or teleservice shall be present. | +| CUG index | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present if it was received in the set-up request from the MS. | +| Suppress preferential CUG | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present if it was received in the set-up request from the MS. | +| Suppress CUG outgoing access | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present if it was received in the set-up request from the MS. | + +### 8.1.40 Send Info For Outgoing Call negative response + +The negative response information element can take the following values: + +- Bearer service not provisioned; +- Call barred (Operator determined barring); +- Call barred (Supplementary service barring); +- CUG reject (Inconsistent access information - index incompatible with basic service); +- CUG reject (Inconsistent access information - no CUG selected); +- CUG reject (Outgoing calls barred within the CUG); +- CUG reject (Unknown CUG index); +- Teleservice not provisioned. + +#### 8.1.40A Send UESBI-lu to Access Network + +The following information element is required: + +| Information element name | Required | Description | +|------------------------------|----------|------------------------------------------| +| IMEI (with software version) | C | IMEISV as defined in 3GPP TS 23.003 [5]. | + +### 8.1.41 Start security procedures + +The following information elements are required for a UMTS connection: + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------------------------------------------------------------------------------| +| CK | M | Ciphering key to be used to cipher communication over the radio link (see 3GPP TS 33.102 [32]). | +| IK | M | Integrity key to be used to verify the integrity of messages transferred over the radio link (see 3GPP TS 33.102 [32]). | + +The following information elements are required for a GSM connection: + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Ciphering mode | M | Indicates whether ciphering of the radio connection is required, and if so which ciphering algorithm is to be used. | +| Kc | C | Ciphering key to be used if ciphering of the radio connection is required. Shall be present if the ciphering mode indicates that ciphering of the radio connection is required, otherwise shall be absent. | + +### 8.1.42 Trace subscriber activity + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|--------------------------------------------------------------------------------------| +| Trace reference | M | Reference number to be included with tracing reports which the VMSC sends to the OMC | +| Trace type | M | For the definition of this IE, see 3GPP TS 52.008 [3] | + +### 8.1.43 Use existing TMSI + +This message contains no information elements. + +### 8.1.44 Release MSRN + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|----------------------------------------------------------------------------| +| MSRN | M | Mobile Station Roaming Number received with the message RELEASE RESOURCES. | + +## 8.2 Messages on the C interface (MSC-HLR) + +### 8.2.1 Send Routeing Info + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MSISDN | M | MSISDN of the B subscriber (see 3GPP TS 23.003 [5]). | +| Alerting Pattern | C | Shall be present if received in a Connect operation from the gsmSCF; otherwise shall be absent. | +| CUG interlock | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present if the GMSC received it in the IAM and the GMSC supports CUG, otherwise shall be absent. | +| CUG outgoing access | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present if the GMSC received it in the IAM and the GMSC supports CUG, otherwise shall be absent. | +| Number of forwarding | C | Number of times the incoming call has already been forwarded. Shall be present if it was received in the IAM; otherwise shall be absent. | +| ISDN BC | C | ISDN bearer capability. Shall be present if the GMSC received it in the IAM, otherwise shall be absent. | +| ISDN LLC | C | ISDN lower layer compatibility. Shall be present if the GMSC received it in the IAM, otherwise shall be absent. | +| ISDN HLC | C | ISDN higher layer compatibility. Shall be present if the GMSC received it in the IAM, otherwise shall be absent. | +| Pre-paging supported | C | Shall be present if the GMSC supports pre-paging, otherwise shall be absent. | +| Call Priority | O | This parameter indicates the eMLPP priority of the call (see 3GPP TS 23.067 [39]). This parameter should be present if the GMSC supports the eMLPP feature and if the call is an eMLPP call. The eMLPP priority levels A and B shall be mapped to the Call priority level 0. | + +### 8.2.2 Send Routeing Info ack + +The following information elements are required: + +| Information element name | Required | Description | +|-------------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | IMSI of the B subscriber (see 3GPP TS 23.003 [5]). | +| Roaming number | C | E.164 number required to route the call to VMSCB (see 3GPP TS 23.003 [5]). Shall be present if the HLR received it in the Provide Roaming Number ack and the call is not subject to early CF, otherwise shall be absent. | +| Forwarded-to number | C | E.164 number of the C subscriber. Shall be present if the HLR has determined that the call is to be forwarded, otherwise shall be absent. | +| Forwarded-to subaddress | C | Subaddress of the C subscriber (see 3GPP TS 23.003 [5]). Shall be present if the HLR has determined that the call is to be forwarded and a forwarded-to subaddress is stored in the HLR in association with the forwarded-to number, otherwise shall be absent. | +| Notification to calling party | C | Indication of whether the calling party is to be notified that the call has been forwarded. Shall be present if the HLR has determined that the call is to be forwarded, otherwise shall be absent. | +| Forwarding reason | C | Indication of why the call has been forwarded (unconditionally or on mobile subscriber not reachable). Shall be present if the HLR has determined that the call is to be forwarded, otherwise shall be absent. | +| Redirecting presentation | C | Indication of whether the MSISDN of B subscriber shall be presented to the C subscriber. Shall be present if the HLR has determined that the call is to be forwarded, otherwise shall be absent. | +| MSISDN | C | E.164 number which identifies the B subscriber (basic MSISDN). It will be used to create the redirecting number presented to the C subscriber. Shall be present if the HLR has determined that the call is to be forwarded, otherwise shall be absent. | +| CUG interlock | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present if the HLR has determined that the call is to be treated as a CUG call in accordance with the rules in 3GPP TS 23.085 [18], otherwise shall be absent. | +| CUG outgoing access | C | For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be present if the HLR has determined that the call is to be treated as a CUG call with outgoing access in accordance with the rules in 3GPP TS 23.085 [18], otherwise shall be absent. | +| NAEA preferred Carrier Id | O | The preferred carrier identity identifying the carrier to be used to route the interexchange call if the call requires routing via an interexchange carrier. This parameter may be included at the discretion of the HLR operator. | + +### 8.2.3 Send Routeing Info negative response + +The negative response information element can take the following values: + +- Absent subscriber; +- Bearer service not provisioned; +- Call barred (Operator determined barring); +- Call barred (Supplementary service barring); +- Call barred (Anonymous Call Rejection); +- CUG reject (Called party SS interaction violation); +- CUG reject (Incoming calls barred within CUG); + +- CUG reject (Requested basic service violates CUG constraints); +- CUG reject (Subscriber not member of CUG); +- Data missing; +- Facility not supported; +- Forwarding violation +- Number changed; +- System Failure; +- Teleservice not provisioned; +- Unexpected data value; +- Unknown subscriber. + +## 8.3 Messages on the D interface (VLR-HLR) + +### 8.3.1 Provide Roaming Number + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | IMSI of the B subscriber (see 3GPP TS 23.003 [5]). | +| MSC number | M | E.164 number which identifies VMSCB (see 3GPP TS 23.003 [5]). | +| MSISDN | O | E.164 number which identifies the B subscriber.
It shall be present if the following 3 conditions are all satisfied:
1. the MSISDN is different from the basic MSISDN;
2. the subscriber has VT-CSI stored in HLR;
3. the VLR has indicated support for CAMEL Phase 3 or later.
It may be present if the HLR requires it to be included in the call data record. | +| LMSI | C | Local Mobile Subscriber Identity. Shall be present if the LMSI was sent to HLRB at location updating. | +| PLMN bearer capability | C | Information to define the PLMN bearer capability required for the call. For alternate speech/facsimile group 3 calls this information element shall contain one PLMN bearer capability, as specified in 3GPP TS 29.007 [30]. May be present if the HLR can determine the required PLMN bearer capability from ISDN compatibility information received in the Send Routeing Info message, or from the MSISDN if a multi-numbering scheme is used; otherwise shall be absent. If the ISDN BC and ISDN LLC IEs are present, the PLMN bearer capability IE shall be absent. | +| ISDN BC | C | ISDN bearer capability. May be present if the HLR received it in the Send Routeing Info message, otherwise shall be absent. If the PLMN bearer capability IE is present, the ISDN BC IE shall be absent. | +| ISDN LLC | C | ISDN lower layer compatibility. May be present if the HLR received it in the Send Routeing Info message, otherwise shall be absent. If the PLMN bearer capability IE is present, the ISDN LLC IE shall be absent. | +| ISDN HLC | C | ISDN higher layer compatibility. Shall be present if the HLR received it in the Send Routeing Info message, otherwise shall be absent. | +| Alerting Pattern | C | Shall be present if the HLR has determined an alerting category or an alerting level for the MT call configuration; otherwise shall be absent. | +| Pre-paging supported | C | Shall be present if the HLR has determined that pre-paging is supported in the GMSC and the HLR, otherwise shall be absent. | +| Paging area | O | Shall be present if the Paging Area function is supported and if the paging area is stored in HLR (see 3GPP TS 23.012); otherwise it shall be absent. It indicates the set of Location Areas in which the MS is to be paged on the A interface if Location area ID is not known in VLR. | +| Call Priority | O | This parameter indicates the eMLPP priority of the call (see 3GPP TS 23.067 [39]). This parameter should be present if the HLR supports this parameter and if the Call Priority was received in the MAP_SEND_ROUTING_INFORMATION request. | + +### 8.3.2 Provide Roaming Number ack + +The following information element is required: + +| Information element name | Required | Description | +|--------------------------|----------|----------------------------------------------------------------------------| +| Roaming number | M | E.164 number required to route the call to VMSCB (see 3GPP TS 23.003 [5]). | + +### 8.3.3 Provide Roaming Number negative response + +The negative response information element can take the following values: + +- Absent subscriber; + +- Data missing; +- Facility not supported; +- No roaming number available; +- OR not allowed; +- Unexpected data value. + +### 8.3.4 Provide Subscriber Info + +The following information elements are required: + +| Information element name | Required | Description | +|---------------------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | IMSI of the subscriber for whom information is requested (see 3GPP TS 23.003 [5]). | +| LMSI | C | Local Mobile Subscriber Identity. Shall be present if the LMSI was sent to the HLR at location updating. | +| Requested information | M | Indicates which of the following information the HLR requires:
  • - location information;
  • - subscriber state;
  • - IMEI (with software version);
  • - MS classmark.
| +| Active location retrieval requested | C | Indicates that the HLR requires active location retrieval. Shall be absent if the requested information does not indicate that the HLR requires location information. | +| Location Information in EPS Supported | C | Indicates by its presence that Location Information in EPS is supported. Shall be absent if the requested information does not indicate that the HLR requires location information.
Shall be present if the Provide Subscriber Info message is triggered by the receipt of a Any Time Interrogation Request that includes the same IE.
May be present otherwise, if the HLR requires location information and the requesting entity in the HPLMN (e.g. gsmSCF) is known to support Location Information in EPS. | +| Call Priority | O | Indicates the eMLPP priority of the call (see 3GPP TS 23.067 [39]). Should be present if the HLR supports this parameter and if the Call Priority was received in the MAP_SEND_ROUTING_INFORMATION request. | + +### 8.3.5 Provide Subscriber Info ack + +The following information elements are required: + +| Information element name | Required | Description | +|------------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location information | C | Information to define the location of the MS: see definition in subclause 8.3.5.1. Shall be present if location information was requested and is available; otherwise shall be absent. | +| Subscriber state | C | Indicates whether the MS is busy (i.e. engaged on a circuit-switched call), network determined not reachable (IMSI detached or roaming in a prohibited location area) or assumed idle. Shall be present if subscriber state was requested; otherwise shall be absent. | +| IMEI (with software version) | C | IMEISV as defined in 3GPP TS 23.003 [5]. Shall be present if the IMEI was requested, otherwise shall be absent. | +| MS classmark | C | MS classmark 2 as defined in 3GPP TS 24.008 [26]. Shall be present if the MS classmark was requested, otherwise shall be absent. | + +#### 8.3.5.1 Location information + +The compound information element Location information consists of the following subordinate information elements: + +| Information element name | Required | Description | +|-----------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Location number | C | For a definition of this information element, see ITU-T Recommendation Q.763 [35]. Shall be present if the VLR can derive it from the stored service area identity (for UMTS) or cell global identity (for GSM) or location area identity; otherwise shall be absent. The mapping from service area identity or cell ID and location area to location number is network-specific and outside the scope of the UMTS and GSM standards. | +| Service area ID | C | Service area identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact. Shall be present if the MS uses UMTS radio access and the subscriber record is marked as confirmed by radio contact; otherwise shall be absent. See subclause 7.2.3.5. | +| Cell ID | C | Cell global identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact. Shall be present if the MS uses GSM radio access and the subscriber record is marked as confirmed by radio contact; otherwise shall be absent. See subclause 7.2.3.5. | +| Geographical information | C | For a definition of this information element, see 3GPP TS 23.032 [7]. Shall be present if the VLR can derive it from the stored service area identity, cell global identity or location area identity; otherwise shall be absent. | +| Geodetic information | C | This information element corresponds to the Calling Geodetic Location defined in ITU-T Recommendation Q.763 [35]. Shall be present if the VLR can derive it from the stored service area identity, cell global identity or location area identity; otherwise shall be absent. | +| VLR number | O | E.164 number which identifies the VLR (see 3GPP TS 23.003 [5]). If the HLR receives it from the VLR it shall ignore it. | +| Age of location information | C | Measured in minutes. Shall be present if available in the MSC/VLR; otherwise shall be absent. | +| Current Location Retrieved | C | Shall be present when location information was obtained after a successful paging procedure for Active Location Retrieval. | +| E-UTRAN Cell ID | C | E-UTRAN cell global identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact. Shall be present if the MS uses E-UTRAN radio access and the subscriber record is marked as confirmed by radio contact; otherwise shall be absent. See subclause 7.2.3.5. | +| Tracking area ID | C | Tracking area identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact. Shall be present if the MS uses E-UTRAN radio access; otherwise shall be absent. See subclause 7.2.3.5. | + +### 8.3.6 Provide Subscriber Info negative response + +The negative response information element can take the following values: + +- Data missing; +- Unexpected data value. + +### 8.3.7 Restore Data + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|--------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | IMSI of the subscriber for whom data are to be restored (see 3GPP TS 23.003 [5]). | +| LMSI | O | LMSI of the subscriber for whom data are to be restored (see 3GPP TS 23.003 [5]). May be included if required by the requesting VLR. | + +### 8.3.8 Restore Data ack + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| HLR number | M | E.164 number which identifies the HLR (see 3GPP TS 23.003 [5]). | +| MS not reachable flag | C | Indicates whether the VLR should notify the HLR when the MS next establishes radio contact. Shall be present if the corresponding indicator is set in the HLR record for the subscriber; otherwise shall be absent. | + +### 8.3.9 Restore Data negative response + +The negative response information element can take the following values: + +- System failure; +- Unknown subscriber. + +## 8.4 Messages on the F interface (MSC-EIR) + +### 8.4.1 Check IMEI + +The following information element is required: + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------| +| IMEI | M | IMEI of the ME whose status is to be checked (see 3GPP TS 23.003 [5]). | + +### 8.4.2 Check IMEI ack + +The following information element is required: + +| Information element name | Required | Description | +|--------------------------|----------|-----------------------------------------------------------------------| +| Equipment status | M | Indicates whether the ME is black-listed, grey-listed or white-listed | + +### 8.4.3 Check IMEI negative response + +The negative response information element can take the following value: + +- Unknown equipment. + +## 8.5 Messages on the MSC internal interface + +This interface can carry ISUP messages received from the process MT\_GMSC or the process ICH\_MSC and to be forwarded to a destination exchange, and ISUP messages received from the destination exchange and to be forwarded to the process MT\_GMSC or the process ICH\_MSC. In addition, it carries the following inter-process messages. + +### 8.5.1 CF cancelled + +This message contains no information elements. + +### 8.5.2 Perform Call Forwarding + +The following information element is required: + +| Information element name | Required | Description | +|--------------------------|----------|-----------------------------------------------------------------------------------------------------------------| +| Forwarded-to number | M | E.164 number of the C subscriber. | +| OR call | M | Indicates whether the call which is to be forwarded was subject to basic OR as specified in 3GPP TS 23.079 [13] | + +### 8.5.3 Perform Call Forwarding ack + +The following information element is required: + +| Information element name | Required | Description | +|--------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Forwarded-to number | M | E.164 number of the C subscriber. Note: this number may be different from the Forwarded-to number received in the Perform Call Forwarding, as a result of CAMEL handling. | + +### 8.5.4 Perform Call Forwarding negative response + +The negative response information element can take the following value: + +- Call forwarding failed. + +## 8.6 Messages on the VLR internal interface + +This interface carries messages between corresponding instances of the processes PRN\_VLR and ICH\_VLR. The correlation between the process instances is done by the MSRN. + +### 8.6.1 Call arrived + +This message contains no information elements. + +### 8.6.2 PAR completed + +This message contains no information elements. + +## 8.7 Messages on the Gs interface + +### 8.7.1 Page MS + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | IMSI of the MS to be paged. | +| eMLPP priority | C | Circuit-switched paging priority. Shall be present if it was received in the Page MS via SGSN request or Search for MS via SGSN request; otherwise shall be absent. | +| TMSI | C | TMSI to be broadcast to identify the MS. Shall be present if it was received in the Page MS via SGSN request or Search for MS via SGSN request; otherwise shall be absent. | +| Location area identity | C | Location area identity of the location area where the mobile is registered, according to the subscriber data in the VLR. Shall be present if the VLR can supply it; otherwise shall be absent. | +| Channel type | C | Type of channel required for the call. Shall be present if it was received in the Page MS via SGSN request or Search for MS via SGSN request; otherwise shall be absent. | + +### 8.7.2 Send MS information + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|---------------------------------------------------| +| IMSI | M | IMSI of the MS for which information is required. | +| Information requested | M | Information required for the specified MS. | + +### 8.7.3 Send MS information ack + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------------------------------------------------------------------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| IMSI | M | IMSI of the MS for which information is required. | +| Service area ID | C | Service area ID (for UMTS access) of the cell in which the MS last established radio contact. Shall be present if the MS uses UMTS access; otherwise shall be absent. | +| Cell ID | C | Cell ID (for GSM access) of the cell in which the MS last established radio contact. Shall be present if the MS uses GSM access; otherwise shall be absent. | +| Location information age | M (note) | Time in minutes since the MS last established a radio transaction | +| NOTE: Although they are optional in the protocol, these IEs are mandatory in this context. | | | + +### 8.7.4 Send MS information negative response + +The negative response information element can take the following value: + +- No response from SGSN. + +## 8.8 Messages on the E interface (GMSC-VMSC) + +### 8.8.1 Release Resources + +The following information elements are required: + +| Information element name | Required | Description | +|--------------------------|----------|--------------------------------| +| MSRN | M | Mobile Station Roaming Number. | + +# --- Annex A (informative): Handling of an IAM at an MSC + +An MSC which receives an IAM from an originating exchange may react in three different ways: + +- It acts as a transit exchange, i.e. it relays the IAM to a destination exchange determined by analysis of the called party address, and thereafter relays other telephony signalling between the originating and destination exchange until the connection is released. This behaviour is not specific to UMTS or GSM. +- It acts as a terminating exchange, i.e. it attempts to connect the call to an MS currently registered in the service area of the MSC. +- It acts as a GMSC, i.e. it interrogates an HLR for information to route the call. If the HLR returns routeing information, the MSC uses the routeing information from the HLR to construct an IAM, which it sends to a destination exchange determined by analysis of the routeing information from the HLR. + +Sheet 1: when the MSC co-ordinating setup procedure has decided whether the MSC is to act as a terminating VMSC, a GMSC or a transit exchange, it forwards the IAM to an idle instance of the appropriate process. + +![Flowchart for MSC_coord_setup procedure. It starts with a connector, then checks if the called party address is in the MSRN range. If 'No', it checks if the incoming IAM was routed with a routing number for MNP. If 'Yes' to the first question, it goes to 'To process ICH_MSC' via 'Initial Address'. If 'No' to the first question, it checks if the HLR address is derivable. If 'Yes' to the second question, it goes to 'To process MT_GMSC' via 'Initial Address'. If 'No' to the second question, it goes to 'To destination determined by routing tables' via 'Initial Address'. All three paths converge to a final connector.](1cd38e4f2ffcae2871964fa6313a9a27_img.jpg) + +procedure MSC\_coord\_setup 1(1) + +Procedure in the MSC to handle an incoming IAM and trigger the correct application process + +``` +graph TD; Start([ ]) --> Q1{Called party address in MSRN range for this MSC?}; Q1 -- No --> Q2{Incoming IAM was routed with routing number for MNP?}; Q1 -- Yes --> ICH[To process ICH_MSC]; ICH --> IA1[Initial Address]; Q2 -- No --> Q3{HLR address derivable?}; Q2 -- Yes --> Recover[Recover ported number from IAM]; Recover -- Yes --> IA2[Initial Address]; Q3 -- No --> Dest[To destination determined by routing tables]; Dest --> IA3[Initial Address]; IA1 --> End(( )); IA2 --> End; IA3 --> End; +``` + +Flowchart for MSC\_coord\_setup procedure. It starts with a connector, then checks if the called party address is in the MSRN range. If 'No', it checks if the incoming IAM was routed with a routing number for MNP. If 'Yes' to the first question, it goes to 'To process ICH\_MSC' via 'Initial Address'. If 'No' to the first question, it checks if the HLR address is derivable. If 'Yes' to the second question, it goes to 'To process MT\_GMSC' via 'Initial Address'. If 'No' to the second question, it goes to 'To destination determined by routing tables' via 'Initial Address'. All three paths converge to a final connector. + +Figure 84a: Process MSC\_Coord (sheet 1) + +# --- Annex B (informative): Change history + +| TSG CN# | Spec | CR | Phase | New Version | Subject/Comment | +|----------|-----------|-------|-------|-------------|-----------------------------------------------------------------------------------------| +| Apr 1999 | GSM 03.18 | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.018 | | | 3.0.0 | Approved at CN#03 | +| CN#04 | 23.018 | 001 | | 3.1.0 | Notification of Call Forwarding to the gsmSCF | +| CN#05 | 23.018 | 002r4 | | 3.2.0 | Addition of the description for Pre-Paging | +| CN#05 | 23.018 | 006 | | 3.2.0 | Removal of TDP criteria from Resume Call Handling | +| CN#05 | 23.018 | 007r1 | | 3.2.0 | GMSC CAMEL phases in Provide Roaming Number | +| CN#05 | 23.018 | 023 | | 3.2.0 | Separation of success & failure cases for OR of late call forwarding | +| CN#05 | 23.018 | 024 | | 3.2.0 | Notification of Call Forwarding to the gsmSCF before activating call forwarding process | +| CN#06 | 23.018 | 004r2 | | 3.3.0 | Introduction of the Super-Charger Concept in TS 23.018 | +| CN#06 | 23.018 | 027r3 | | 3.3.0 | Introduction of CAMEL Phase 3 | +| CN#07 | 23.018 | 025r7 | | 3.4.0 | Addition of the description for Multicall | +| CN#07 | 23.018 | 026r2 | | 3.4.0 | Alternative solution for ALR | +| CN#07 | 23.018 | 030 | | 3.4.0 | Correction of the SDL diagrams for Pre-paging | +| CN#07 | 23.018 | 032r1 | | 3.4.0 | Inclusion of D-CSI check in HLR/VLR | +| CN#07 | 23.018 | 033 | | 3.4.0 | Initialization of Backward Call indicator | +| CN#07 | 23.018 | 034 | | 3.4.0 | Correction of the result of the procedure CAMEL ICH MSC INIT | +| CN#07 | 23.018 | 037 | | 3.4.0 | Clarification of N-CSI in Core NW | +| CN#07 | 23.018 | 039r2 | | 3.4.0 | Replacement of references to GSM with references to UMTS | +| CN#07 | 23.018 | 043r1 | | 3.4.0 | Clarification of NPDB error detection and MNP specific call handling | +| CN#07 | 23.018 | 044 | | 3.4.0 | Setting the Destination Address for MO calls | +| CN#07 | 23.018 | 047 | | 3.4.0 | O-CSI and D-CSI checks for ORLCF calls | +| CN#07 | 23.018 | 048 | | 3.4.0 | Correction of CF Notification | +| CN#07 | 23.018 | 049 | | 3.4.0 | Introduction of Authentication Failure Report | +| CN#07 | 23.018 | 050r3 | | 3.4.0 | ISUP release cause value | +| CN#08 | 23.018 | 045r1 | | 3.5.0 | Correction of CAMEL Incoming Call Handling | +| CN#08 | 23.018 | 051r4 | | 3.5.0 | Improvement of Active Retrieval of Location Information procedure | +| CN#08 | 23.018 | 052r2 | | 3.5.0 | North American Service Provider Number Portability impacts for MNP | +| CN#09 | 23.018 | 053 | | 3.6.0 | Correction of connector numbering in process ICH MSC | +| CN#09 | 23.018 | 054 | | 3.6.0 | Correction of the SDL diagram for Pre-paging | +| CN#09 | 23.018 | 056 | | 3.6.0 | Correction to process ICH_VLR | +| CN#09 | 23.018 | 057r3 | | 3.6.0 | Handling of the Call Diversion Treatment Indicator | +| CN#09 | 23.018 | 059r1 | | 3.6.0 | Modifications to procedure obtain routeing address. | +| CN#09 | 23.018 | 060 | | 3.6.0 | Corrections to process ICH_VLR | +| CN#09 | 23.018 | 061r2 | | 3.6.0 | Update of CAMEL references | +| CN#09 | 23.018 | 063r1 | | 3.6.0 | Correction of procedure Obtain_Routeing_Address for the reconnect case | +| CN#09 | 23.018 | 055r4 | R4 | 4.0.0 | Inclusion of call hold in basic call handling. | +| CN#10 | 23.018 | 064 | Rel-4 | 4.1.0 | Tidying up of Process Subs_FSM and inter-process signals | +| CN#11 | 23.018 | 065 | Rel-4 | 4.2.0 | Incorporation of MPTY and ECT into the Subs_FSM process | +| CN#11 | 23.018 | 067 | Rel-4 | 4.2.0 | Removal of CW descriptions | +| CN#11 | 23.018 | 069 | Rel-4 | 4.2.0 | Paging not via the SGSN correction | +| CN#12 | 23.018 | 074 | Rel-4 | 4.3.0 | Initialization of variable to monitor activation of CSI's | +| CN#12 | 23.018 | 072 | Rel-5 | 5.0.0 | Handling of MultiCall in MPTY procedure | + +| TSG CN# | Spec | CR | Phase | New Version | Subject/Comment | +|---------|--------|--------|-------|-------------|-------------------------------------------------------------------------| +| CN#13 | 23.018 | 077 | Rel-5 | 5.1.0 | Addition of missing process
Update Location_VLR | +| CN#13 | 23.018 | | Rel-5 | 5.1.0 | Editorial clean up | +| CN#14 | 23.018 | 081 | Rel-5 | 5.2.0 | Handling of Reconnect on Leg2 Disconnect | +| CN#14 | 23.018 | 091r2 | Rel-5 | 5.2.0 | Corrections in the ATI mechanism description | +| CN#15 | 23.018 | 082r2 | Rel-5 | 5.3.0 | Introduction of CAMEL Phase 4 | +| CN#15 | 23.018 | 088r2 | Rel-5 | 5.3.0 | Handling of CUG calls in non-supporting networks | +| CN#15 | 23.018 | 093r1 | Rel-5 | 5.3.0 | MSISDN in Provide Roaming Number in case of MSP | +| CN#15 | 23.018 | 098 | Rel-5 | 5.3.0 | Correction on the Active Location Retrieval description | +| CN#15 | 23.018 | 100r1 | Rel-5 | 5.3.0 | Transferring the MS classmark & IMEI to the gsmSCF | +| CN#17 | 23.018 | 109r1 | Rel-5 | 5.4.0 | Determining the basic service for MT calls | +| CN#17 | 23.018 | 110 | Rel-5 | 5.4.0 | Minor corrections to Process ICH_MSC | +| CN#17 | 23.018 | 111 | Rel-5 | 5.4.0 | Setting of Leg1_Status variable | +| CN#18 | 23.018 | 112r1 | Rel-5 | 5.5.0 | Clarification of requirements for the presence of IEs in messages | +| CN#19 | 23.018 | 118 | Rel-5 | 5.6.0 | Correction in the ATI mechanism description | +| CN#20 | 23.018 | 115r2 | Rel-5 | 5.7.0 | Stopping No_Answer timer in the case of forwarding notification | +| CN#20 | 23.018 | 122 | Rel-5 | 5.7.0 | Release Result from CAMEL_MT_GMSC_Notify_CF | +| CN#20 | 23.018 | 124 | Rel-5 | 5.7.0 | Addition of procedure to retrieve UE-specific behaviour data | +| CN#21 | 23.018 | 128 | Rel-5 | 5.8.0 | Corrections to "Early UE" handling | +| CN#21 | 23.018 | 133 | Rel-5 | 5.8.0 | HLR Interrogation for SCUDIF calls | +| CN#21 | 23.018 | 132 | Rel-6 | 6.0.0 | Removal of SIWF material | +| CN#22 | 23.018 | 126r1 | Rel-6 | 6.1.0 | Collective CR for Rel-6 Enhanced Dialled Services | +| CN#22 | 23.018 | 135 | Rel-6 | 6.2.0 | Incorrect implementation of CR 133 | +| CN#22 | 23.018 | 137 | Rel-6 | 6.2.0 | Default Basic Service for gsmSCF-initiated calls | +| CN#25 | 23.018 | 141r1 | Rel-6 | 6.3.0 | Pre-Paging Resource Optimization | +| CN#25 | 23.018 | 143r1 | Rel-6 | 6.3.0 | Add "CAMEL_Stop_TNRy" in Procedure OG_Call_Setup_MSC (sheet 4) | +| CN#27 | 23.018 | 144 | Rel-6 | 6.4.0 | Management Based Activation Impacts | +| CT#28 | 23.018 | 145r1 | Rel-7 | 7.0.0 | Trunk Originated CAMEL triggering - SDLs | +| CT#29 | 23.018 | 146 | Rel-7 | 7.1.0 | Trunk Originated CAMEL: Inter-digit timer stop/reset SDL correction | +| CT#30 | 23.018 | 0147 | Rel-7 | 7.2.0 | Incorrect References | +| CT#33 | 23.018 | 0150 | Rel-7 | 7.3.0 | Correction to the IC_CUG_Check Procedure | +| CT#34 | 23.018 | 0155 | Rel-7 | 7.4.0 | Optional Suppress Terminating Services Bit String in SRI | +| CT#36 | 23.018 | 0157r4 | Rel-7 | 7.5.0 | Mobile Termination whilst the MS is moving to another MSC | +| CT#36 | 23.018 | 0159 | Rel-7 | 7.5.0 | PLMN BC in PRN for alternate speech/fax - alignment with TS 29.007 | +| CT#37 | 23.018 | 0160 | Rel-7 | 7.6.0 | Procedure Check_OG_Barring | +| | | 0162 | | | Missing SRIack negative response to ISUP release cause mapping in GMSC | +| CT#40 | 23.018 | 0163r2 | Rel-8 | 8.0.0 | Paging optimization with A/lu flex | +| CT#41 | 23.018 | 0164r1 | Rel-8 | 8.1.0 | eMLPP Priority in MAP SRI, PRN and PSI request | +| CT#42 | 23.018 | | Rel-8 | 8.1.1 | Copyright Notification updated | +| CT#45 | 23.018 | 0166 | Rel-8 | 8.2.0 | PSI negative response | +| CT#46 | | - | - | 9.0.0 | Update to Rel-9 version (MCC) | +| CT#47 | 23.018 | 0167r4 | Rel-9 | 9.1.0 | Mobile Termination on Pre-paging whilst the MS is moving to another MSC | +| CT#49 | 23.018 | 0168r2 | Rel-9 | 9.2.0 | SRI Negative Response Error | +| CT#49 | 23.018 | 0170 | Rel-9 | 9.2.0 | Correction for SMS via SGs charging | +| | 23.018 | | Rel-9 | 9.2.1 | History table version numbers corrected | + +| TSG CN# | Spec | CR | Phase | New Version | Subject/Comment | +|---------|--------|--------|--------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| CT#50 | 23.018 | 0171 | Rel-10 | 10.0.0 | MT Roaming Retry | +| CT#51 | 23.018 | 0174r2 | Rel-10 | 10.1.0 | Mobile Terminating Roaming Forwarding | +| CT#51 | 23.018 | 0173 | Rel-10 | 10.1.0 | MT Roaming Retry and Super Charger | +| CT#52 | 23.018 | 0180 | Rel-10 | 10.2.0 | Paging optimization with A/lu flex | +| CT#52 | 23.018 | 0175r3 | Rel-10 | 10.2.0 | Mobile Terminating Roaming Forwarding for Pre-paging | +| CT#52 | 23.018 | 0176 | Rel-10 | 10.2.0 | New LMSI handling for MTRF | +| CT#52 | 23.018 | 0177r1 | Rel-10 | 10.2.0 | SDL changes for MTRF after retrieval of routeing information | +| CT#52 | 23.018 | | | 10.2.1 | Editorial correction of overlapping CRs C4-111418 and C4-111415 implementation after CT#52. 5.2.4 was re-numbered as figure 4d in order to align with previous figure number in serction 5.2.3. | +| CT#53 | 23.018 | 0181r1 | Rel-11 | 11.0.0 | Addition of Anonymous Call Rejection in the CS domain | +| CT#53 | 23.018 | 0182r2 | Rel-11 | 11.0.0 | HLR/HSS domain selection function alignment with Stage 2 requirement | +| CT#54 | 23.018 | 0188r1 | Rel-11 | 11.1.0 | Provide Subscriber Information handling for UE under LTE | +| CT#54 | 23.018 | 0183r1 | Rel-11 | 11.1.0 | Cause code mapping | +| CT#54 | 23.018 | 0185 | Rel-11 | 11.1.0 | CSG access control in CS domain | +| CT#55 | 23.018 | 0189r4 | Rel-11 | 11.2.0 | Termination of VT-CSI Dialogue during MTRR and MTRF Procedures | +| CT#56 | 23.018 | 0190r1 | Rel-11 | 11.3.0 | MTRF upon establishment of SGs association | +| CT#56 | 23.018 | 0191r1 | Rel-11 | 11.3.0 | Subclause number correction on MTRF | +| CT#59 | 23.018 | 0195r3 | Rel-11 | 11.4.0 | MTRF for normal 2G and 3G MT call | +| CT#59 | 23.018 | 0193r1 | Rel-12 | 12.0.0 | MTRR for normal 2G/3G MT call | +| CT#59 | 23.018 | 0196r1 | Rel-12 | 12.0.0 | MTRF for normal 2G and 3G MT call | +| CT#60 | 23.018 | 0197 | Rel-12 | 12.1.0 | MM Abort intead of CM Service Reject after CM service acceptance | +| CT#61 | 23.018 | 0198r2 | | 12.2.0 | MTRF Optimal Routing when the GMSC and new MSC/VLR are the same node | +| CT#70 | 23.018 | - | Rel-13 | 13.0.0 | Update to Rel-13 version (MCC) | +| 2017-03 | 23.018 | - | Rel-14 | 14.0.0 | Update to Rel-14 version (MCC) | +| 2018-06 | 23.018 | - | Rel-15 | 15.0.0 | Update to Rel-15 version (MCC) | +| 2020-07 | - | - | Rel-16 | 16.0.0 | Update to Rel-16 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23042/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg b/marked/Rel-16/23_series/23042/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af14d6ddb278203d6d4994e274e40ff4ee24baa9 --- /dev/null +++ b/marked/Rel-16/23_series/23042/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c010747a0405c4da55f98e2d974a69bd1adb6dc61346bbee460097fb757c7c7 +size 26381 diff --git a/marked/Rel-16/23_series/23042/raw.md b/marked/Rel-16/23_series/23042/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..0d8c76b2671407467ca08f4ff0298215cb37ab22 --- /dev/null +++ b/marked/Rel-16/23_series/23042/raw.md @@ -0,0 +1,2269 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| Introduction ..... | 6 | +| 1 Scope..... | 8 | +| 2 References..... | 8 | +| 2.1 Normative references ..... | 8 | +| 2.2 Informative references..... | 8 | +| 3 Abbreviations ..... | 8 | +| 4 Algorithms ..... | 8 | +| 4.1 Huffman Coding..... | 9 | +| 4.2 Character Groups..... | 10 | +| 4.3 UCS2..... | 10 | +| 4.4 Keywords ..... | 11 | +| 4.5 Punctuation..... | 11 | +| 4.6 Character Sets..... | 11 | +| 5 Compressed Data Streams ..... | 11 | +| 5.1 Structure ..... | 12 | +| 5.2 Compression Header ..... | 12 | +| 5.2.1 Compression Header - Octet 1 ..... | 12 | +| 5.2.2 Compression Header - Octets 2 to n..... | 13 | +| 5.2.2.1 Compression Header reserved extension types and values ..... | 15 | +| 5.2.3 Identifying unique parameter sets..... | 15 | +| 5.3 Compressed Data..... | 15 | +| 5.4 Compression Footer ..... | 17 | +| 6 Compression processes ..... | 17 | +| 6.1 Overview ..... | 17 | +| 6.1.1 Compression..... | 18 | +| 6.1.2 Decompression ..... | 19 | +| 6.2 Character sets ..... | 20 | +| 6.2.1 Initialization..... | 20 | +| 6.2.2 Character set conversion..... | 21 | +| 6.2.3 Character case conversion ..... | 21 | +| 6.3 Punctuation processing..... | 21 | +| 6.3.1 Initialization..... | 22 | +| 6.3.2 Compression..... | 23 | +| 6.3.3 Decompression ..... | 24 | +| 6.4 Keywords ..... | 24 | +| 6.4.1 Dictionaries..... | 24 | +| 6.4.2 Groups ..... | 25 | +| 6.4.3 Matches..... | 27 | +| 6.4.4 Initialization..... | 28 | +| 6.4.5 Compression..... | 28 | +| 6.4.6 Decompression ..... | 29 | +| 6.5 UCS2..... | 29 | +| 6.5.1 Initialization..... | 29 | +| 6.5.2 Compression..... | 29 | +| 6.5.3 Decompression ..... | 29 | +| 6.6 Character group processing..... | 29 | +| 6.6.1 Character Groups..... | 30 | +| 6.6.2 Initialization..... | 31 | +| 6.6.3 Compression..... | 31 | +| 6.6.4 Decompression ..... | 33 | +| 6.7 Huffman coding..... | 33 | +| 6.7.1 Initialization Overview ..... | 34 | +| 6.7.2 Initialization..... | 35 | +| 6.7.3 Build Tree..... | 36 | + +6.7.4 Update Tree .....36 +6.7.5 Add New Node .....36 +6.7.6 Compression .....37 +6.7.7 Decompression .....37 + +| | | | +|-------------------------------|----------------------------------------------------------|-----------| +| 7 | Test Vectors ..... | 37 | +| Annex A (normative): | German Language parameters ..... | 39 | +| A.1 | Compression Language Context..... | 39 | +| A.2 | Punctuators..... | 39 | +| A.3 | Keyword Dictionaries ..... | 40 | +| A.4 | Character Groups ..... | 44 | +| A.5 | Huffman Initializations ..... | 46 | +| Annex B (normative): | English language parameters ..... | 50 | +| B.1 | Compression Language Context..... | 50 | +| B.2 | Punctuators..... | 50 | +| B.3 | Keyword Dictionaries ..... | 51 | +| B.4 | Character Groups ..... | 55 | +| B.5 | Huffman Initializations ..... | 57 | +| Annex C (normative): | Italian Language parameters ..... | 61 | +| Annex D (normative): | French Language parameters ..... | 62 | +| Annex E (normative): | Spanish Language parameters..... | 63 | +| Annex F (normative): | Dutch Language parameters..... | 64 | +| Annex G (normative): | Swedish Language parameters ..... | 65 | +| Annex H (normative): | Danish Language parameters ..... | 66 | +| Annex J (normative): | Portuguese Language parameters ..... | 67 | +| Annex K (normative): | Finnish Language parameters..... | 68 | +| Annex L (normative): | Norwegian Language parameters..... | 69 | +| Annex M (normative): | Greek Language parameters..... | 70 | +| Annex N (normative): | Turkish Language parameters..... | 71 | +| Annex P (normative): | Reserved ..... | 72 | +| Annex Q (normative): | Reserved ..... | 73 | +| Annex R (normative): | Default Parameters for Unspecified Language ..... | 74 | +| R.1 | Compression Language Context..... | 74 | +| R.2 | Punctuators..... | 74 | +| R.3 | Keyword Dictionaries ..... | 74 | +| R.4 | Character Groups ..... | 74 | +| R.5 | Huffman Initializations ..... | 75 | +| Annex S (informative): | Change history..... | 76 | + +# --- Foreword + +This Technical Specification has been produced by the 3GPP. + +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 x.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; + +# --- Introduction + +This clause introduces the concepts and mechanisms involved in the compression and decompression of a stream of data. + +# Overview + +Central to the compression of a stream of data and the subsequent recovery of the original data is the that both sender and receiver have information that not only describes the content of the data stream, but how the stream is encoded. + +For example, a simple rule such as "it's 8 bit data" is enough to transport any character value in the range 0 to 255 with 8 bits being required for each and every character. In contrast if both sender and receive know that some characters are more frequent than others, then the more frequent might be encoded in fewer bits while the less frequent in more - resulting in a net reduction of the total number of bits used to express the data stream. + +This knowledge of the nature of the data stream can be established in two ways. Either both sender and receiver can agree some key aspects of the data stream *prior* to it being processed or key aspects of the data can be garnered *dynamically* during its processing. + +The disadvantage of an approach based on "prior information" is that it must be known. It can either be carried as a header to the data stream, in which case it adds to the net size of the compressed stream. Or it can be fixed and known to the (de)compression algorithm itself in which case compression performance degrades as a given stream diverges in nature from these fixed and known states. In contrast, the disadvantage of "dynamic information" is that it must be discovered; typically this means a greater processing requirement for the (de)compressor. It also implies that compression performance is initially poor as the algorithm has to "learn" about the data stream before it can apply this knowledge. It will also require greater working memory to store its knowledge about the data stream. + +The choice of compression algorithms is always a balancing of compression rate (in terms of fewer output bits), working memory requirements of the (de)compressor and CPU bandwidth. For the compression of SMS messages, there is the additional requirement that it should work well (in terms of compression rate) even on short data streams. + +Compression / Decompression is an optional feature but when implemented, the only mandatory requirement is 'Raw Untrained Dynamic Huffman' . The default initialisation for the Huffman Encoder / Decoder operating in the Raw Untrained Dynamic Huffman mode are defined in annex R. (See also subclause 4.1.) + +i.e. There is no need for any pre-defined attributes such as language dependency to be included. This is of particular significance for entities such as an MS which may have memory storage constraints. + +# --- 1 Scope + +The present document introduces the concepts and mechanisms involved in the compression and decompression of a stream of data. + +# --- 2 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*. + +## 2.1 Normative references + +- [1] 3GPP TS 23.038: "Alphabets and language-specific information". + +## 2.2 Informative references + +- [2] "The Data Compression Handbook 2nd Edition" by Mark Nelson and Jean-Loup Gailly, published by M&T Books, ISBN 1-22851-434-1. + +# --- 3 Abbreviations + +For the purposes of the present document, the following abbreviations apply. + +| | | +|-------|-------------------------------| +| CD | Compressed Data | +| CDS | Compressed Data Stream | +| CDSL | Compressed Data Stream Length | +| CF | Compression Footer | +| CG-ID | Character Group ID | +| CH | Compression Header | +| CLC | Compression Language Context | +| HI-ID | Huffman initialization ID | +| KD-ID | Keyword Dictionary ID | +| PU-ID | PUnctuator ID | + +# --- 4 Algorithms + +The compression algorithm comprises a number of components that may be combined in a variety of configurations. The discrete algorithms are discussed in the following subclauses. + +## 4.1 Huffman Coding + +The base compression algorithm is a Huffman coder, whereby characters in the input stream are represented in the output stream by bit sequences of variable length. This length is inversely proportional to the frequency with which the character occurs in the input stream. + +**This is the only component of the whole compression algorithm that can be expected to be included in any implementation, all other components are optional.** + +There are two possible approaches here: + +- a) the (de)coder can be "pre-loaded" with a character frequency distribution, thus improving compression rate for streams that approximate to this distribution; or +- b) the (de)coder can adapt the frequency distribution it uses to (de)code characters based on the incidence of previous characters within the input stream. + +In both cases, the character frequency distribution is represented in a "tree" structure, an example of which is shown in figure 1. + +![Figure 1: Character frequency distribution tree diagram. The root node is 'Root Node f=72'. It branches into 'Node f=32' (left) and 'E f=40' (right). 'Node f=32' branches into 'Node f=12' (left) and 'Node f=20' (right). 'Node f=12' branches into 'Node f=6' (left) and 'R f=6' (right). 'Node f=20' branches into 'A f=10' (left) and 'O f=10' (right). 'Node f=6' branches into 'Node f=2' (left) and 'T f=4' (right). 'Node f=2' branches into 'Z f=1' (left) and 'W f=1' (right).](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) + +``` + +graph TD + Root["Root Node f=72"] --> Node32["Node f=32"] + Root --> E["E f=40"] + Node32 --> Node12["Node f=12"] + Node32 --> Node20["Node f=20"] + Node12 --> Node6["Node f=6"] + Node12 --> R["R f=6"] + Node20 --> A["A f=10"] + Node20 --> O["O f=10"] + Node6 --> Node2["Node f=2"] + Node6 --> T["T f=4"] + Node2 --> Z["Z f=1"] + Node2 --> W["W f=1"] + +``` + +Figure 1: Character frequency distribution tree diagram. The root node is 'Root Node f=72'. It branches into 'Node f=32' (left) and 'E f=40' (right). 'Node f=32' branches into 'Node f=12' (left) and 'Node f=20' (right). 'Node f=12' branches into 'Node f=6' (left) and 'R f=6' (right). 'Node f=20' branches into 'A f=10' (left) and 'O f=10' (right). 'Node f=6' branches into 'Node f=2' (left) and 'T f=4' (right). 'Node f=2' branches into 'Z f=1' (left) and 'W f=1' (right). + +**Figure 1: Character frequency distribution** + +The tree represents the characters Z, W, T, R, A, O and E which have frequencies of 1, 1, 4, 6, 10, 10 and 40 respectively. The characters may be coded as variable length bit streams by starting at the "character node" and ascending to the "root node". At each stage, if a left hand path is traversed, a 0 bit is emitted and if a right hand path is traversed a 1 bit is emitted. Thus the infrequent Z and W would require 5 bits, whereas the most frequent character E requires just 1 bit. The resulting bit stream is decoded by starting at the "root node" and descending the tree, to the left or right depending on the value of the current bit, until a "character node" is reached. + +It is a requirement that at any time the trees expressing the character frequencies shall be identical for both coder and decoder. This can be achieved in a number of ways. + +Firstly, both coder and decoder could use a fixed and pre-agreed frequency distribution that includes all possible characters but as noted above, this use of "prior information" suffers when a given input stream has a significantly different character frequency distribution. + +Secondly, the coder may calculate the character frequency distribution for the entire input stream and prepend this information to the encoded bit stream. The decoder would then generate the appropriate tree prior to processing the bitstream. This approach offers good compression, especially if the character frequency information may itself be compressed in some manner. Approaches of this type are common but the cost of the prepended information for a potentially small data stream makes it less attractive. + +Thirdly, extend the algorithm such that although both coder and decoder start with known frequency distributions, and subsequently adapt these distributions to reflect the addition of each character in the input stream. One possibility is to have initial distributions that encompass all possible characters so that all that is required, as each input character is processed, is to increment the appropriate frequency and update the tree. However, the inclusion of all *possible* characters in the initial distribution means that the tree is relatively slow to adapt, making this approach less appropriate for short messages. An alternative is to have an initial distribution that does not include all possible characters and to add new characters to the distribution if, and when, they occur in the input stream. + +To achieve the latter approach, the concept of a "special" character is required. A "special" character is one whose value is outside the range of the character set being used (e.g. 256 if the character set has a range 0 to 255). These characters therefore do not form part of the input stream being conveyed, but their existence in the compressed stream signals the need for the decoder to adjust its behaviour. Here a "special" character is used to signal that the following n bits (where n is a fixed value) represent a new character that needs to be added to the frequency distribution. In the example above this would be done by replacing the "character" node containing the character Z with a new node that had as its children the "character" nodes for Z and for the new character. + +This is the approach taken here. It provides considerable flexibility, effectively enabling all of the foregoing approaches. The specific approach to be used for a given message is signalled in the header. + +The algorithm uses an additional optimization in that 2 special characters are defined, one meaning that a 7-bit literal follows and the other for 8-bit characters. So for example: + +- The initial tree can contain just the "new character follows" special character(s). In this case, the input stream "AAA" would result in: +[1 bit = new character(7bit) special][7 bits = "A"][2 bits = "A"][1 bit = "A"] +- As can be seen from the above there is quite a high cost in adding a new character (the "special" plus literal). So if the initial tree contains a small subset of the generally most frequently used characters, the cost of character addition can be avoided for these characters. +- Given that we can signal in the header a specific initial frequency distribution, there is no reason why this distribution cannot contain all possible characters and frequency adaptation enabled or disabled as appropriate. + +A detailed description of Huffman coding can be found in Chapter 4 of "The Data Compression Handbook 2nd Edition" by Mark Nelson and Jean-Loup Gailly, published by M&T Books, ISBN 1-22851-434-1. + +## 4.2 Character Groups + +Character grouping is an optional component that can effect an increase in compression performance of the Huffman coder. This technique groups characters that may be expected to occur together within the input stream and signals transitions between the groups rather than each individual character. + +The algorithm derives benefit by; + +- a) reducing the need to add new characters to the frequency distribution; and +- b) using a smaller overall tree. For example, assume that there is no pre-loaded distribution and a stream comprised the characters "abcdefABCDEF". + +The capital letters can be encoded more efficiently by signalling the transition to "upper case" and then coding the extant lower case characters rather than introducing 6 new characters. "Special" characters are used to signal transitions between groups of characters. + +## 4.3 UCS2 + +Input streams comprising 16bit UCS2 information are handled in a manner similar to Character groups. Both coder and decoder maintain knowledge of "the current" Basic Multilingual Plane row for characters in the input stream and the row octet itself is then omitted from the output stream for sequences of characters within that row. Transitions between rows are signalled in the output stream by a "special" character. + +Support for UCS2 is optional. + +## 4.4 Keywords + +The algorithm optionally supports the concept of dictionaries - essentially a list of key words or phrases of up to 255 characters in length. Dictionaries need to be known to both the coder and the decoder. The input stream is matched against entries in the dictionary and matching characters in the stream are replaced with a reference to the dictionary entry. + +Again "special" characters are used to signal that the following sequence of bits describe a reference to a dictionary entry. So for example, if a dictionary contains the phrases "Please" and "meeting", an input stream "Please cancel the monthly meeting" would be rendered as: + +[keyword special][10 bits = "Please"][.....][keyword special][10 bits = "meeting"] + +Dictionary matches for long strings can result in very high compression rates. + +## 4.5 Punctuation + +The punctuation processor is distinct from the other algorithms in that it is non-symmetric so the decompressed stream may not be identical to the original. Its use is therefore mainly applicable to input streams comprising human readable sentences where it is sufficient to preserve the meaning of the content, but not the exact format. It is also applicable when the input stream is a "standard sentence" that is known to produce a symmetric result. The punctuation processor is applied before (on coding) and after (on decoding) any of the other algorithms. Its functions are: + +- to remove leading and trailing spaces from the input stream; +- to replace repeated spaces within the stream with a single space; +- to remove (on coding) and insert (on decoding) spaces following certain punctuation characters; +- to decapitalize (on coding) and capitalize (on decoding) the first character of the stream, the first character following an appropriate punctuation character or a paragraph symbol and capitalized single character words such as "I"; +- to remove (on coding) and insert (on decoding) a full stop if it is the last character of the stream. + +The use of the punctuation processor is optional. + +## 4.6 Character Sets + +The use of pre-loaded frequencies, key word dictionaries and the punctuation processor all require that a consistent character set is used by both coder and decoder. As there can be no assumption that the same character will be have the same value (or even be available) on the devices used to send and receive a compressed message, the algorithms are specified to operate on a known character set *to* which (prior to coding) and *from* which (post decoding) a device needs to convert an input stream to render it in the native character set of the device. + +**The handling of character sets is mandatory for all implementations.** + +# --- 5 Compressed Data Streams + +This clause provides: + +- A detailed specification of the algorithms and data structures that implement compression and decompression mechanisms. + +## 5.1 Structure + +A Compressed Data Stream (CDS) comprises three key components: + +- a Compression Header (CH) containing a variable number of octets, the content of which defines the nature of the compressed data; +- the Compressed Data (CD) which is a bit stream of variable length; +- a Compression Footer (CF) which is used to signal the number of bits in the last octet of the CDS that form part of the compressed data. + +## 5.2 Compression Header + +The Compression Header (CH) comprises a variable number of octets that define the nature of the compressed data. + +The compression header allows for a wide range of compression alternatives, however of these alternatives only one is defined as the basic mandatory form of compression that shall be supported by all implementations. This is the use of the basic Huffman algorithm initialized with no prior knowledge of character distribution. This case can be signalled directly by setting a single octet(octet 1) for the compression header with the value of 120 (decimal). + +### 5.2.1 Compression Header - Octet 1 + +The first CH octet is mandatory and is defined as follows: + +**Table 1: CH octet** + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Description | +|---|---|---|---|---|---|---|---|------------------------------------------------------------| +| 0 | | | | | | | | There is no subsequent CH octet | +| 1 | | | | | | | | A further CH octet follows | +| | n | n | n | n | | | | The "Compression Language Context" this is described below | +| | | | | | 0 | | | Punctuation processing disabled | +| | | | | | 1 | | | Punctuation processing enabled | +| | | | | | | 0 | | Keyword processing disabled | +| | | | | | | 1 | | Keyword processing enabled | +| | | | | | | | 0 | Character group processing disabled | +| | | | | | | | 1 | Character group processing enabled | + +As noted in clause 4, the compression algorithms can be configured to operate in a variety of ways and may rely on end-to-end knowledge of "prior" information such as which key word dictionary is to be used. + +A requirement that all configuration information be explicitly stated in the CH is less efficient (in terms of compression ratio) than if a default configuration is known and only variations from this need be signalled. However, a major determinant of configuration is the language in which the original message to be compressed is composed. For example, different keyword dictionaries would be required for French and opposed to German and character frequency distributions for English texts may vary greatly from those for Swedish texts. From this it can be seen that a universal "default" configuration would be of little value. + +To address this, the Compression Language Context (CLC) allows a default configuration to be specified for each of the languages defined in 3GPP TS 23.038 [1] in relation to the Cell Broadcast Data Coding Scheme as follows: + +- The CLC in bits 6 to 3 of the CH specify the language as per 3GPP TS 23.038 [1] in the case where bits 7 to 4 of the Cell Broadcast Data Coding Scheme octet are set to 0000. +- If and when required, higher order bits of the CLC can be signalled by a subsequent CH octet as described below. +- The CLC value 1111 (language unspecified) will indicate a "default" configuration that is language independent. This is specified in annex R and involves the basic Huffman (de-)coding with no initial character frequency distribution, see example below. + +**Table 2: Huffman (de-)coding with no initial character frequency distribution** + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Description | +|---|---|---|---|---|---|---|---|---------------------------------| +| 0 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | Basic Huffman (de-)coding only. | + +### 5.2.2 Compression Header - Octets 2 to n + +Any second and subsequent CH octets are used to vary the configuration defaults established by the CLC. These octets all comprise a continuation bit followed by a Type, Value structure as follows: + +**Table 3: Value structure** + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Description | +|---|---|---|---|---|---|---|---|-------------| +|---|---|---|---|---|---|---|---|-------------| + +| | | | | | | | | | +|---|---|---|---|---|---|---|---|---------------------------------| +| 0 | | | | | | | | There is no subsequent CH octet | +| 1 | | | | | | | | A further CH octet follows | +| | n | n | n | | | | | CH Extension Type | +| | | | | n | n | n | n | CH Extension Value | + +The bits of the semi-octet CH Extension value are interpreted left to right, MSB to LSB. If the CH contains more than one octet of the same CH Extension type, the CH Extension value of a subsequent CH octet, is interpreted as being next most significant semi-octet of the composite value being signalled. + +For example if the CLC in CH octet 1 indicates that the default Huffman Initialization ID is 1 (decimal) and the required HI-ID is 37 (decimal), then the following octets (in the range 2 to n) would also be required in the CH. + +**Table 4: CH extension octets (Example)** + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Description | +|---|---|---|---|---|---|---|---|---------------------------------------------------------| +| 1 | 0 | 1 | 1 | 0 | 1 | 0 | 1 | The default HI-ID is replaced with the value 0101 | +| 0 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | The current HI-ID value (0101) is extended to 0010 0101 | + +The following values are defined for the CH Extension Type: + +**000** Extend CLC. The CH Extension Value contains higher order bits that are to be pre-pended to the current CLC value. + +**NOTE:** for 1st occurrence of the Extend CLC CH Extension Type in the CH, the value for the CLC specified in CH octet 1 is *not* replaced but rather the process of "extension" begins directly. Thus is the CLC to be used is 18, octets 1 and 2 of the CH would contain: + +**Table 5: CLC extension (Example)** + +| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Description | +|---|---|---|---|---|---|---|---|-----------------------------------------------------| +| 1 | 0 | 0 | 1 | 0 | | | | The least significant semi-octet of the CLC is 0010 | +| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | The CLC value (0010) is extended to 0001 0010 | + +**001** Change Character Set. The CLC defines a default character set (UCS2 or otherwise) within which compression will operate. The Change Character Set CH Extension Type indicates that this should be overridden by the character set specified by the CH Extension Value. If a CH contains more than one Change Character Set CH Extension Type octet, the CH Extension Value contained in subsequent CH octets of this type contains higher order bits and are to be pre-pended to the value of the new character set. + +The following Character Sets are defined: + +**0000** No character set defined. To be used where original message content is binary data and compression is solely via Huffman coding with no initial frequency training and thus there is no requirement to ensure consistent use of character set by coder and decoder. + +**0001** GSM 7 bit default alphabet (3GPP TS 23.038 [1]) + +**0010** Codepage 437 + +**0011** Codepage 850 + +All other values are reserved - see section 5.2.2.1 + +A Change Character Set to UCS2 codepoint is not defined here. Where the CLC indicates a character set other than UCS2 and there is a need to change to UCS2 then this is achieved using the Change UCS2 row parameter described below. + +- 010** Change UCS2 Row. The CLC defines a default character set (UCS2 or otherwise) within which compression will operate. The Change UCS2 Row CH Extension Type indicates that this should be overridden by the use of UCS2 *and* the UCS2 row value for the first character in the input stream is that specified by the CH Extension Value. If a CH contains more than one Change UCS2 Row CH Extension Type octet, the CH Extension Value contained in subsequent CH octets of this type contains higher order bits for the initial UCS2 Row value and are to be pre-pended to the current value. + +**NOTE:** Change UCS2 Row CH Extension Type octet effectively overrides any prior Change Character Set CH Extension Type octet and vice versa so these types are logically mutually exclusive within a given CH. + +- 011** Change Huffman Initialization. The CLC defines a default set of parameters for the initialization of the Huffman (de)coder. The Change Huffman Initialization CH Extension Type indicates that this should be overridden by the set of initialization parameters identified by the Huffman Initialization ID contained in the CH Extension Value. If a CH contains more than one Change Huffman Initialization CH Extension Type octet, the CH Extension Value contained in subsequent CH octets of this type contains higher order bits for the initial Huffman Initialization ID value and are to be pre-pended to the current value. + +- 100** Change Keyword Dictionary. The CLC defines a default set of parameters for the initialization of the Keyword (de)coder. The Change Keyword Dictionary CH Extension Type indicates that this should be overridden by the set of initialization parameters identified by the Keyword Dictionary ID contained in the CH Extension Value. If a CH contains more than one Change Keyword Dictionary CH Extension Type octet, the CH Extension Value contained in subsequent CH octets of this type contains higher order bits for the initial Keyword Dictionary ID value and are to be pre-pended to the current value. + +- 101** Change Punctuation. The CLC defines a default set of parameters for the initialization of the punctuation (de)coder. The Change Punctuation CH Extension Type indicates that this should be overridden by the set of initialization parameters identified by the Punctuation ID contained in the CH Extension Value. If a CH contains more than one Punctuation CH Extension Type octet, the CH Extension Value contained in subsequent CH octets of this type contains higher order bits for the initial Punctuation ID value and are to be pre-pended to the current value. + +- 110** Change Character Group. The CLC defines a default set of parameters for the initialization of the Character Group (de)coder. The Change Character Group CH Extension Type indicates that this should be overridden by the set of initialization parameters identified by the Character Group ID contained in the CH Extension Value. If a CH contains more than one Change Character Group CH Extension Type octet, the CH Extension Value contained in subsequent CH octets of this type contains higher order bits for the initial Character Group ID value and are to be pre-pended to the current value. + +- 111** Reserved, see section 5.2.2.1 + +#### 5.2.2.1 Compression Header reserved extension types and values + +Any currently undefined values in the range 0 to 255 decimal are reserved. + +Values above 255 are available for user to user requirements. + +### 5.2.3 Identifying unique parameter sets + +The four component compression algorithms (Huffman, Keywords, Character Groups and Punctuation) may all have a variety of initialization options. For each algorithm, a given set of initialization options needs to be identified for the processing of a given input stream. + +Initialization and operation of the algorithms depends not only on the language in which the original source text is composed but also the character set (UCS2 or otherwise) that is to be used during processing. Thus the Huffman Initialization ID (HI-ID), Keyword Dictionary ID (KD-ID), Punctuation ID (PU-ID) and Character Group ID (CG-ID) only define unique values within the context of a given character set (the default established by the CLC or subsequently amended via Change Character Set or Change UCS2 Row CH Extension types) and within the context of the language indicated by the CLC. + +## 5.3 Compressed Data + +The Compressed Data (CD) is a stream bits of variable length that represent either an encoding of the content original input stream or control information indication that the operation of some algorithm should vary in some manner. + +Control information is signalled within the CD by Huffman encoded symbols (characters) whose value is greater than 255 decimal. Huffman encoded symbols in the range 0 to 255 are of course characters from the original input stream. + +The following control symbols are defined: + +**Table 6: Compressed Data: control symbols** + +| Decimal value | Significance | +|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 256 |

New 7 bit character.

On encoding, if a character (octet) from the input stream in the range 0 to 127 does not exist in the Huffman tree, then the New 7 bit character symbol is Huffman encoded to the CD and bits 6 to 0 of the original octet are copied unchanged to the CD. The Huffman tree would then be updated to include the new character as described in the sections below.

On decoding the New 7 bit character symbol, the symbol itself is discarded and the next 7 bits of the CD are copied unchanged to bits 6-0 of the octet to be output, bit 7 of which is zero. The Huffman tree would then be updated to include the new character.

| +| 257 |

New 8 bit character.

The operation of this is identical to that of the New 7 bit character except that on encoding, the input character is in the range 128-255 and on decoding, bit 7 of the output character is set to 1.

| +| 258 |

Keyword.

This symbol (Huffman encoded) prefixes a sequence of bits of variable length in the CD that define a representation of characters in the uncompressed stream by an entry in a keyword dictionary.

On encoding, if a sequence of characters in the input stream can be represented by an entry in a keyword dictionary, the Keyword symbol is Huffman encoded to the CD followed by the bit sequence describing the keyword entry (this is described below). On decoding the Keyword symbol, the symbol itself is discarded and the bit sequence describing the keyword entry is passed to the Keyword processor to recovery the original character sequence to be placed in the output stream.

| +| 259 to 265 |

Character Group Transitions.

These symbols signal transitions between groups of characters defined within the Character Group processor. For example, if 2 groups are defined to be the lower case and upper case characters then the input stream:
"abcdefABCDEF" would become "abcdef<Change Group>abcdef"

On encoding, Character Group Transition symbols are generated by the Character Group processor and simply passed to the Huffman processor for encoding.

On decoding a Character Group Transition symbol, it is simply passed from the Huffman processor to the Character Group processor which takes the appropriate action based its current state and the group transition indicated.

| +| 266 |

New UCS2 Row.

On encoding, if the next UCS2 character in the input stream has a "row octet" of a different value to that of the previous character in the input stream, the New UCS2 Row symbol is Huffman encoded to the CD and the 8 bit of the new row octet are copied unchanged to the CD. The new row octet is stored by the UCS2 processor as the "current row octet" and subsequent input characters within the current row are Huffman encoded as the 8 bit value of the character within the "current row".

On decoding the New UCS2 Row symbol, the symbol is discarded and the next 8 bits are read from the CD and stored by the UCS2 processor as the "current row octet". Subsequent UCS2 characters are decoded by treating the 8 bit character values decoded by the Huffman processor as characters within the "current row".

| + +## 5.4 Compression Footer + +Although Compressed Data Stream Length (CDSL) - the total number of octets that contain the CDS - is known, the CD element of the CDS is a bit stream and therefore may not end on an octet boundary. The Compression Footer (CF) is used to indicate the end of the CD as follows: + +- Calculate the number of meaningful bits in the last octet of the CD (i.e. total CD bits modulo 8). +- If the number of meaningful bits is $>0$ and $<6$ store the number of meaningful bits in bits 2 to 0 of the last octet. Otherwise extend the CD by adding 1 octet and store the number of meaningful bits in bits 2 to 0 of this new octet. In the case where the number of meaningful bits is 8 then bits 2 to 0 of the new octet are set to zero. + +For example if there are 4 meaningful bits in the last CD octet, the CF will be constructed to occupy the shaded area in table 7. + +**Table 7: CF with $>0$ and $<6$ meaningful bits in last octet (Example)** + +| | | | | | | | | | +|---|---|---|---|---|---|---|---|---| +| 0 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| X | X | X | X | X | | 1 | 0 | 0 | + +Alternatively if there are 6 meaningful bits in the last CD octet, a new octet needs to be added. The CF will be constructed to occupy the shaded area in table 8. + +**Table 8: CF with $>5$ meaningful bits in last octet (Example)** + +| | | | | | | | | | | | | | | | | | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 0 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| X | X | X | X | X | X | X | | | | | | | | 1 | 1 | 0 | + +If there are 8 meaningful bits in the last CD octet, a new octet needs to be added. The CF will be constructed to occupy the shaded area in table 8a. + +**Table 8a: CF with 8 meaningful bits in last octet (Example)** + +| | | | | | | | | | | | | | | | | | +|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| +| 0 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | +| X | X | X | X | X | X | X | X | X | | | | | | 0 | 0 | 0 | + +In all the tables above, the bits in the shaded area which have no bit value defined are set according to the particular bearer being used to transport compressed data. e.g. CBS. Where no particular reference is made regarding the value of those bits they may be set to any value. + +# 6 Compression processes + +This clause defines the detailed operation of the various compression algorithms. + +## 6.1 Overview + +This subclause describes how the various compression algorithms are combined. + +### 6.1.1 Compression + +**Table 9: Compression** + +| | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | 1) The nature of the compression to be performed.
2) The input stream of characters to be compressed. | +| Step 1 | Construct the Compression Header so as to fully describe the nature of the compression to be performed as requested by higher software layers.

Note that it is the responsibility of higher software layers that use the compression algorithms to ensure that only those aspects of the compression algorithms that are supported by a particular implementation are requested. | +| Step 2 | Initialize as defined by the CH the following components:
1) Character Set Converter
2) Punctuation Processor
3) Keyword Processor
4) UCS2 Processor
5) Character Group Processor
6) Huffman Processor | +| Step 3 | If the Character set in which input stream is composed is different from that specified in the CH, convert the input stream so that it is rendered in the Character set (UCS2 or otherwise) specified in the CH.

Note that if characters in the input stream cannot be rendered in the character set specified in the CH, it is the responsibility of higher software layers that use the compression algorithms to detect this situation and take appropriate action. | +| Step 4 | If the Punctuation Processor is enabled, use it to encode the character set converted input stream produced by Step 3 above. | +| Step 5 | Set the current character position to the start of the character stream produced as the output of Step 4 above. | +| Step 6 | If the Keyword processor is not enabled goto Step 7.

Examine the sequence of characters starting at the current character position in the input stream and determine if they can be represented by an entry in the keyword dictionary.

If an appropriate keyword is not found goto Step 7.

If the Character Group processor is enabled, pass it the Keyword symbol and Huffman encode to the CD the sequence of symbols output by it.

Huffman encode the Keyword symbol to the CD and then copy the bit sequence describing the keyword entry to the CD.

Goto Step 10. | +| Step 7 | If the input stream is not UCS2 goto Step 8.

If the character at the current character position in the input stream has a different UCS2 row octet from the previous character Huffman encode the New UCS2 Row symbol to the CD and then copy the new row octet to the CD.

Remove the row octet from the character at the current character position in the input stream which will subsequently be treated as an 8 bit value. | +| Step 8 | If the Character Group processor is not enabled goto Step 9.

Pass the character at the current character position in the input stream to the Character Group processor and Huffman encode to the CD the sequence of symbols output by it.
Goto Step 10. | +| Step 9 | Huffman encode the character at the current character position in the input stream. | +| Step 10 | Increment the current character position by the number of input characters processed in steps 6 to 9 above.

If the entire input stream has not been processed goto Step 6 above. | +| Step 11 | Construct the Compression Footer. | +| Output | The completed Compressed Data Stream.

Note that the possibility exists that the CDS may be larger than the original input stream. In this case it is the responsibility of higher software layers that use the compression algorithms to detect this situation and take appropriate action. | + +### 6.1.2 Decompression + +**Table 10: Decompression** + +| | | +|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | The Compressed Data Stream | +| Step 1 |

Interpret the Compression Header to determine the nature of the decompression to be performed.

Note that it is the responsibility of higher software layers that use the decompression algorithms to handle appropriately the case where the nature of the decompression to be performed is not supported by a particular implementation.

| +| Step 2 |

Initialize as defined by the CH the following components:

  1. 1) Character Set Converter
  2. 2) Punctuation Processor
  3. 3) Keyword Processor
  4. 4) UCS2 Processor
  5. 5) Character Group Processor
  6. 6) Huffman Processor
| +| Step 3 | Interpret the Compression Footer to determine the total number of significant bits in the Compressed Data (CD). Set the total number of bits processed to zero. | +| Step 4 | Read bits from the CD passing them to the Huffman decoder to generate the "current symbol". The bits should be read in the order bit 7 to bit 0 within each CD octet. CD octets are processed in the order 1 to n. | +| Step 5 |

If the Keyword processor is not enabled, goto Step 6.

If the "current symbol" is the Keyword symbol, read the bit sequence describing the keyword entry from the CD. Pass the keyword entry description to the Keyword processor for decoding and add the resulting sequence of characters representing the keyword to the output stream.

Goto Step 9.

| +| Step 6 |

If the Character Group processor is not enabled goto Step 7.

If the "current symbol" is a Character Group Transition symbol, pass it to the Character Group processor so that the current group can be updated and goto Step 9.

If the value of the "current symbol" is in the range 0 to 255 (i.e. not a control symbol), pass the "current symbol" to the Character Group processor and set the new value of the "current symbol" to that returned by the Character Group processor.

| +| Step 7 |

If the output stream is not UCS2 goto Step 8.

If the "current symbol" is the New USC2 Row symbol, read the new "current UCS2 row octet" from the CD and goto Step 9.

Pre-pend the "current UCS2 row octet" to the 8 bit value of the "current symbol" to produce a 16 bit UCS2 character.

| +| Step 8 | Add the "current symbol" to the output stream. | +| Step 9 |

Increment the total number of bits processed by the number of bits read from the CD in steps 4 to 8 above.

If the total number of bits processed is less than the total number of significant bits in the CD goto Step 4.

| +| Step 10 | If the Punctuation Processor is enabled, use it to decode output stream produced by steps 3 to 9 above. | +| Step 11 |

If the Character set (UCS2 or otherwise) specified in the CH, is different from that required by higher level software layers, convert the output stream produced by step 10 above so that it is rendered in the Character set (UCS2 or otherwise) required by higher level software layers.

Note that if characters in the stream cannot be converted, it is the responsibility of higher software layers that use the compression algorithms to detect this situation and take appropriate action.

| +| Output | The decompressed original input stream. | + +## 6.2 Character sets + +The need for character set conversion arises in that a number of the compression algorithms operate on the basis of "prior information" about the nature of human readable texts. For example Huffman frequency initializations may specify the an initial relative frequency for the letter "e" as opposed to the letter "x". Similarly, a keyword dictionary may contain the word "meeting". + +Consider the case where a keyword dictionary contains the entry "€10,000" composed using the Code Page 850 character set. If an input stream containing the string "€10,000" also composed in Code Page 850 is processed, the string will be replace in the CD by a reference to the keyword entry. In contrast if the input string is composed using the GSM 7 bit default alphabet (3GPP TS 23.038 [1]) than a match between the input string and the keyword entry will not be found as the value of the "€" symbol in Code Page 850 is 156 decimal whereas in the GSM 7 bit default alphabet it is 2 decimal. + +There can be no assumption that higher level software layers responsible for composing the original input stream to be compressed and displaying the resulting decompressed output stream use the same character set. + +Thus: + +- The character set used to compose initialization parameter sets and used for the compression of a given input stream shall be the same for both compression and decompression. +- Where an input stream is composed using a character set that is different from that used for compression it shall be converted prior to compression. +- Where an output stream is required in a character set that is different from that used for compression it shall be converted after decompression. + +There is an additional requirement in that a number of the compression algorithms perform upper / lower case conversions upon the characters within the character set used for compression. The mapping between "lower" and "upper" case characters needs to therefore be known. + +### 6.2.1 Initialization + +Initialization of character set conversion processing will typically involve identifying and loading the appropriate tables to a) convert between character sets and b) convert between upper and lower case characters. + +As the character set(s) in which uncompressed data is required to be rendered is largely an implementation specific matter, so is the precise specification of the tables to convert these to/from the character set specified for compression. However, they need to be sufficient to support the following functions: + +### 6.2.2 Character set conversion + +**Table 11: Character set conversion** + +| | | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | 1) The value of the source character.
2) The character set in which the source character is rendered.
3) The character set in which the source character is to be rendered. | +| Output | 1) The value of the converted character.
2) A Boolean value indicating whether a successful conversion has been performed. | +| Process |

If the source character can be rendered in the target character set, its value in the target characterset is returned and a successful conversion is indicated.

Otherwise, the value of the source character is returned unchanged, a conversion failure is indicated and higher software layers need to take appropriate action.

For example:

  • - The character "A", 65 decimal in Code Page 850 is rendered in the GSM 7 bit default alphabet also as 65 decimal so this value is returned and a successful conversion is indicated.
  • - The character "£", 156 decimal in Code Page 850 is rendered in the GSM 7 bit default alphabet as 1 decimal so the value 1 is returned and a successful conversion is indicated.
  • - The character "Û" 234 decimal in Code Page 850 cannot be rendered in the GSM 7 bit default alphabet so the value 234 is returned unchanged and a conversion failure is indicated.
| + +### 6.2.3 Character case conversion + +Conversion between upper and lower case for characters within the character set used for compression will also typically be supported by conversion tables that indicate for each character in the character set, the value of any lower case or upper case equivalent character such that the following function can be supported. + +**Table 12: Character case conversion** + +| | | +|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | 1) The value of the source character.
2) The case (lower or upper) in which the source character is to be rendered. | +| Output | 1) The value of the case converted character. | +| Process |

If the character can be rendered in the case requested and the value of this case converted character is different from that of the source character, the value of the case converted character is returned.

Otherwise (i.e. the source character is already in the requested case or the character does not have upper and lower case equivalents), the value of the source character is returned unchanged.

| + +## 6.3 Punctuation processing + +The punctuation processor achieves compression by using the "prior information" that the uncompressed stream is human readable and is constructed of sentences that conform to a known set of punctuation rules. Essentially this means that certain characters within the input stream, of themselves imply information about subsequent characters and this may therefore be omitted from the compressed stream. In this way the algorithm achieves some significant compression in a very simple manner. + +However, because the algorithm operates on information about sentence structure rather than the exact sequence of characters used to render this, it is non-symmetric. In other words, although the overall meaning of the human readable input stream is preserved between compression and decompression, the exact sequence of characters is not. Higher level software layers or even user inspection may therefore be required to determine if the use of this processor is appropriate for a given input stream. + +In addition to the ability to handle the conversion of characters between upper and lower case (as described in the previous subclause), the processor requires that certain characters (expressed in the character set to be used for compression) are assigned special attributes. These are: + +**Table 13: special attributes** + +| Attribute | Description | +|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| PU-IWS |

Inter-word separator. A character with this attribute is that typically used to separate words within the input stream.

Only one character in the character set may have this attribute.

This attribute is typically set for the "space" character (32 decimal).

| +| PU-LST |

Last Sentence Terminator. A character with this attribute is that typically used to terminate the last sentence in the input stream.

Only one character in the character set may have this attribute.

This attribute is typically set for the "." full stop character (46 decimal).

| +| PU-WSF |

Word Separator Follows. A character with this attribute is expected to be followed by one or more characters which have the PU-IWS attribute set.

Any number of characters within the character set may have this attribute.

Examples of characters that would normally have this attribute set are the exclamation mark (!), comma (,), full stop (.), colon (;), semi-colon (:) and question mark (?).

| +| PU-UCF |

Upper Case Follows. A character with this attribute is expected to be followed by an upper case character such as occurs at the start of a sentence or paragraph.

Any number of characters within the character set may have this attribute.

Typically, characters with this attribute set will also have the PU-WSF attribute set. Examples are the exclamation mark (!), full stop (.), and question mark (?).

Other examples associated with new paragraphs might include the carriage return (13 decimal) and line feed (10 decimal) symbols.

| +| PU-UCW |

Upper Case Word. A character with this attribute set is expected to be upper case if it is a word i.e. if it is both preceded and succeeded by character with the PU-IWS attribute set.

Any number of characters within the character set may have this attribute.

An example in the English language is the letter "I".

| +| PU-NSI |

No Separator Insertion. A character with this attribute set does not have the PU-IWS attribute set but is none the less expected to be preceded by a character for which the PU-WSF attribute is set.

Any number of characters within the character set may have this attribute.

Typically, characters with this attribute set will be numeric digits so that the case can be resolved where characters which have the PU-WSF attribute set such as comma (,) and full stop (.) can be used in number formatting as in the case of the string "£10,000.25".

| + +### 6.3.1 Initialization + +Initialization of the punctuation processor will typically involve loading a table containing the combination of attributes defined for each character in the character set to be used for compression for the language defined by the CLC. + +### 6.3.2 Compression + +For compression, the punctuation processor operates as follows: + +**Table 14: compression punctuation processor** + +| | | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | The input stream of characters to be compressed, rendered in the appropriate character set. | +| Step 1 | Set the current character position to the start of the input stream. | +| Step 2 | Determine the attributes of the current character.

If some previous character in the input stream has not had the PU-IWS attribute set goto Step 3.

If the current character has the PU-IWS attribute set goto Step 8.

Convert the current character to lower case and store the returned value as that of the "previous character". Store the attributes of the current character as those of the "previous character" after clearing any PU-UCW attribute.

Goto Step 8. | +| Step 3 | If the previous character has the PU-WSF attribute and the current character has the PU-IWS attribute goto Step 8.

Otherwise clear the PU-WSF attribute for the "previous character". | +| Step 4 | If the previous character has the PU-UCF attribute, convert the current character to lower case and clear the PU-UCF attribute for the "previous character". | +| Step 5 | If the previous character has the PU-UCW attribute and the current character has the PU-IWS attribute, convert the previous character to lower case. | +| Step 6 | If the previous character has the PU-IWS attribute and the current character has the PU-IWS attribute, goto Step 8.

Otherwise add the previous character to the output stream and set the value of the previous character to that of the current character. | +| Step 7 | If the current character has the PU-UCW attribute and the previous character attributes do not contain the PU-IWS attribute, clear the PU-UCW attribute for the current character.

Set the attributes for the "previous character" to those of the current character. | +| Step 8 | If the current character is the last character in the input stream and if some previous character in the input stream has not had the PU-IWS attribute set and if the previous character attributes contain neither the PU-IWS nor the PU-LST attribute, add the previous character to the output stream. | +| Step 9 | If the current character is not the last character in the input stream, read the next character from the input stream, set the current character to this value and goto Step 2. | +| Output | The de-punctuated data stream. | + +### 6.3.3 Decompression + +For decompression, the punctuation processor operates as follows: + +**Table 15: decompression punctuation processor** + +| | | +|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | The de-punctuated stream of characters to be punctuated, rendered in the character set used for compression. | +| Step 1 | Set the current character position to the start of the de-punctuated stream. | +| Step 2 | Determine the attributes of the current character.

If the current character is the first character in the stream, convert it to upper case and goto Step 8. | +| Step 3 | If the current character has the PU-IWS attribute and the "previous character" attributes has the PU-UCW attribute, convert the stored value of the "previous character" to upper case. | +| Step 4 | If the "previous character" attributes contain the PU-UCF attribute, and the current character was not generated by Step 10 below, convert the current character to upper case and clear the PU-UCF attribute for the "previous character" attributes. | +| Step 5 | If the "previous character" was generated as a result of Step 10 and the current character contains the PU-NSI attribute goto Step 7. | +| Step 6 | Add the "previous character" value to the output stream. | +| Step 7 | If "previous character" attributes contain the PU-IWS attribute and the current character has the PU-UCW attribute, add the PU-UCW attribute to those of the "previous character". Otherwise clear any PU-UCW attribute stored for the "previous character". | +| Step 8 | Set the value of the "previous character" to be that of the current character. | +| Step 9 | If the attributes of the current character contain the PU-UCF attribute set this attribute for the "previous character". | +| Step 10 | If the attributes of the current character contain the PU-WSF attribute and the current character is not the last character in the de-punctuated stream, insert the character containing the PU-IWS attribute at the position following the current character in the de-punctuated stream. | +| Step 11 | If the current character is not the last character in the de-punctuated stream, read the next character from the stream, set the current character to this value and goto Step 2. | +| Step 12 | Add the previous character to the output stream.

If the current character attributes do not contain the PU-UCF attribute or the previous character value equals that of the character which has the PU-LST attribute set, add the character which has the PU-LST attribute set to the output stream. | +| Output | The punctuated data stream. | + +## 6.4 Keywords + +The operation of the Keyword processor is controlled by the set of parameters defined by a Keyword Dictionary that is uniquely defined (within a CLC) by the value of the Keyword Dictionary ID (KD-ID) specified in the CH. + +### 6.4.1 Dictionaries + +A Keyword Dictionary specifies the following items: + +#### 1) Character Set ID + +This is the character set in which the dictionary is composed and shall therefore be equal to the character set to be used for compression as specified in the CH. + +#### 2) Match Options + +This is a collection of bit flags that control how text in the input stream is to be matched against key word dictionary entries. These are described in the table below in which Bit 0 is considered to be the least significant bit of the Match Options value. + +**Table 16: Match options** + +| Bit | Description | +|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | If set, input stream text shall exactly match the dictionary entry. | +| 1 | If set, input stream text may match the lower case conversion of a dictionary entry. | +| 2 | If set, input stream text may match the upper case conversion of a dictionary entry. | +| 3 | If set, input stream text may match the upper case conversion of the 1st character of a dictionary entry followed by the lower case conversion of the remaining characters of the dictionary entry. | +| 4 | If set, input stream text may match a dictionary entry prefixed by the keyword prefix characters (if any) described below. | +| 5 | If set, input stream text may match a dictionary entry suffixed by the keyword suffix characters (if any) described below. | +| 6 | If set, input stream text may match a part of a dictionary entry. A partial match occurs when, a dictionary entry contains n characters and a match is found with the first m characters where m is less than n. | +| 7- | All other bits are reserved. | + +#### 3) Keyword Prefix + +The 1st octet is the Keyword Prefix Length which specifies the number of characters that form the prefix string. The length octet is followed by the actual characters of the prefix string. + +#### 4) Keyword Suffix + +The 1st octet is the Keyword Suffix Length which specifies the number of characters that form the suffix string. The length octet is followed by the actual characters of the suffix string. + +#### 5) Keyword Threshold + +This value determines the minimum number of characters in the input stream that needs to be replaced by a full match with a keyword entry. For a partial match the value of the threshold needs to be incremented by 2. + +If a match occurs involving fewer characters than that specified by the threshold, keyword substitution does not take place. + +#### 6) Maximum Partial Match Length + +This value determines the maximum number of characters in the input stream that needs to be replaced by a partial match with a keyword entry. + +If a partial match occurs involving fewer characters than that specified by this value, keyword substitution does not take place. + +#### 7) Key Word Group List + +The actual key word dictionary entries are not directly specified within the Keyword Dictionary. Instead, a set of key word dictionary entries is explicitly identified by a Key Word Group ID - an octet value that is unique within the language specified by the CLC. This approach allows the same set of keyword dictionary entries to be used in conjunction with different values for the parameters specified within the Keyword Dictionary and for Keyword Dictionaries to be defined that combine multiple Key Word Groups. + +The 1st octet of the Key Word Group List specifies the number of Key Word Group IDs that follow, each of the following octets specifies a Key Word Group ID. + +### 6.4.2 Groups + +A Keyword Group specifies the following items: + +#### 1) Character Set ID + +This is the character set in which the keyword dictionary entries are composed and shall therefore be equal to the character set to be used for compression as specified in the CH. + +#### 2) Number of Entries + +The value specifies the number of keyword dictionary entries contained in the Keyword Group. + +#### 3) Keyword Entry + +The 1st octet is the Keyword Entry Length which specifies the number of characters that form the keyword entry string. The length octet is followed by the actual characters of the entry string. + +The sequence of entries within a dictionary needs to be known by both coder and decoder. Thus keyword entries in a Keyword Group needs to be sorted in ascending sequence of the actual characters of the entry string. Furthermore if a dictionary defines multiple Keyword Groups, the combined set of entries needs to be resorted as part of initialization of the Keyword processor so that the ascending alphanumeric sequence of entries is achieved for all entries in the combined set. + +A further requirement is that all entries in the combined set shall be unique. + +### 6.4.3 Matches + +A Keyword Match specifies how a sequence of characters in the input stream is represented by a keyword dictionary entry. A Keyword Match is a bit stream that is interpreted left to right as described on the table below wherein Bit 0 refers to the most significant, left most bit. + +**Table 17:** + +| Bits | Description | +|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 to N 1 |

Case conversion.

If bit 0 of the Dictionary Match Options is set (i.e. Exact matching is enabled), the Case conversion bits are omitted and the Keyword Match starts with the Keyword Entry ID described below.

Otherwise, if the match involves a lower case conversion, a single Case conversion bit with value 0 is used.

Otherwise, 2 case conversion bits are used with the following value:
10 Upper Case.
11 1st character Upper case, remainder Lower case.

| +| N 1 +1 to N 2 |

Keyword Entry ID.

This value represents the position in the list of keyword dictionary entries of the entry with which a match has been found. A value of 0 indicates the first entry.

The number of bits used to express the Keyword Entry ID is minimum number of bits required to represent the total number of keyword dictionary entries defined for the Keyword Dictionary minus 1.

| +| N 2 +1 to N 3 |

Prefix Match.

If bit 4 of the Dictionary Match Options is set (i.e. Prefix matching is enabled), a single bit is used to indicate whether a prefix match applies (1) or not (0).

If prefix matching is not enabled, this bit is omitted from the Keyword Match.

| +| N 3 +1 to N 4 |

Partial Match.

If bit 6 of the Dictionary Match Options is set (i.e. Partial matching is enabled), a single bit is used to indicate whether a partial match has occurred (1) or not (0).

If partial matching is not enabled, this bit is omitted from the Keyword Match.

If partial matching is enabled and a full match has occurred, no further bits are required to describe the match.

If partial matching is enabled and a partial match has occurred, it is necessary to encode the length of the partial match as follows:

The partial match length equals the total number of characters in the input stream represented by the Keyword Match (excluding any characters represented by any prefix and suffix matches) less the value of the partial match threshold (i.e. Keyword Threshold +2).

If the partial match length is less than 8 a single bit (0) is added to the bit stream to indicate this fact followed by 3 bits containing the partial match length.

Otherwise a single bit (1) is added to the bit stream to indicate that more than 3 bits follow containing the partial match length. In this case the number of bits used to represent the partial match length is the minimum number of bits required to represent the value (Maximum Partial Match Length - (Keyword Threshold +2))

| +| N 4 +1 to N 5 |

Suffix Match.

If bit 5 of the Dictionary Match Options is set (i.e. Suffix matching is enabled), a single bit is used to indicate whether a suffix match applies (1) or not (0).

If suffix matching is not enabled, this bit is omitted from the Keyword Match.

| + +### 6.4.4 Initialization + +Initialization of the Keyword processor involves loading the various parameters specified by the KD-ID contained in the CH. + +As noted above, if the dictionary is composed on more than 1 Keyword Group, the combined set of keyword entries needs to be resorted so that the full set conforms to an ascending alphanumeric sequence. + +Clearly, as it is the total combined and sorted set of keyword entries that is required, implementors may choose to construct this from the component keyword groups at run time or to produce such a combination and use it directly as indicated by the constituent keyword group ID's. + +### 6.4.5 Compression + +For compression, the Keyword processor operates as follows: + +**Table 18: compression Keyword processor** + +| | | +|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | A offset into the input stream of characters from which a matching keyword is to be found. | +| Step 1 | Set the current character position to the input offset. | +| Step 2 |

If Prefix matching is not enabled goto Step 3.

If the string starting at the current character position exactly matches Keyword Prefix, record this fact and increment the current character position by the length of the prefix string.

| +| Step 3 |

Identify the Keyword Entry ID and if enabled Case Conversion and Partial Match details for the longest match (i.e. that where by the greatest number of characters in the input stream are represented) between a dictionary entry and the string starting at the current character position subject to the following rules:

  1. 1) An exact match shall be greater than or equal to the Keyword Threshold to be considered.
  2. 2) A partial match shall be greater than or equal to the Keyword Threshold +2 to be considered.
  3. 3) If more than 1 partial match of equal length is found, the one with the greater Keyword Entry ID is used.
  4. 4) If an exact match and a partial match are found, the length of the partial match shall be at least 2 greater than that of the exact match for it to be used.
  5. 5) Although the case of more than 1 exact match of equal length being found is not possible as entries are unique, should such a case arise, the one with the greater Keyword Entry ID is used.

If the longest match is a partial match with length greater than the Maximum Partial Match Length, the match length is limited to the Maximum Partial Match Length.

If no match has been found goto Step 5.

| +| Step 4 |

If Suffix matching is not enabled goto Step 5.

If the string starting at the current character position exactly matches Keyword Prefix, record this fact and increment the current character position by the length of the prefix string.

| +| Step 5 | If a matching keyword has been found, construct the Keyword Match bitstream. | +| Output | A Keyword Match bitstream or an indication that no suitable match is available. | + +### 6.4.6 Decompression + +For decompression, the Keyword processor operates as follows: + +**Table 19: decompression Keyword processor** + +| | | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | A Keyword Match bitstream. | +| Step 1 | Interpret the Keyword Match bitstream to determine if there is a Prefix match. If so add the Keyword Prefix string to the string to be output. | +| Step 2 | Interpret the Keyword Match bitstream to identify the dictionary entry or part thereof as indicated by any Partial Match details.

Perform any case conversion (indicated by the Keyword Match bitstream) on the dictionary entry string and add the resulting string to the string to be output. | +| Step 3 | Interpret the Keyword Match bitstream to determine if there is a Suffix match. If so add the Keyword Suffix string to the string to be output. | +| Output | The character string represented by the input Keyword Match bitstream. | + +## 6.5 UCS2 + +### 6.5.1 Initialization + +Initialization of the USC2 processor involves storing the default UCS2 row as specified by the CH. + +### 6.5.2 Compression + +For compression, the UCS2 processor operates as follows: + +**Table 20:** + +| | | +|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | A 16 bit UCS2 character value. | +| Step 1 | If the row octet of the input character is different from the "current UCS2 row" store the row octet of the input character as the new "current UCS2 row". | +| Output | A Boolean value indicating whether the current UCS2 row has been changed. | + +### 6.5.3 Decompression + +For decompression, the USC2 processor needs to set and sense the "current UCS2 row" as required by the higher level software described in subclause 6.1.2 above. + +## 6.6 Character group processing + +The operation of the Character Group processor is controlled by the set of parameters defined by a Character Group that is uniquely defined (within a CLC) by the value of the Character Group ID (CG-ID) specified in the CH. + +Character grouping operates by defining 2 or more subsets (groups) of characters within the character set used for compression with the following properties: + +- Each sub set contains the same number of characters. +- One subset (referred to as Group 0 or the "base group") contains the characters expected to have higher frequencies in a input stream than those of the characters in other subsets. +- Input stream are expected to contain contiguous sequences of characters belonging to a single group. + +Compression is achieved by assigning a 1:1 mapping between the characters in the base group and those in the other groups and when appropriate signalling a transition between groups and then continuing to encode base group characters. This has the effect of improving the performance of the Huffman encoder by reducing the need to add new characters to the tree and by maintaining a smaller overall tree with a more distinct frequency distribution. + +For example, assume that we have a character set that comprises just the numeric digits 0 to 9 and the letters A to B and 3 groups containing the digits 1 to 3, 4 to 6 and 0 and 7 to 9. The digits 1 to 3 are considered to be the most frequent and + +are therefore the base group. The digit 0 is defined to exist in all the groups and the letters A and B do not occur in any group. + +Encoding and decoding of characters is achieved using the various items in table 21. + +**Table 21: Encoding and decoding of characters** + +| Item | Element | | | | | | | | | | | | Comment | +|-----------|---------|---|---|---|---|---|---|---|---|---|----|----|-------------------------| +| Value | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | Decimal character value | +| Character | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | A | B | Character symbol | +| Group 0 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | Bit flags for Group 0 | +| Group 1 | 1 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | Bit flags for Group 1 | +| Group 2 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 | 0 | Bit flags for Group 2 | +| Fold 0 | 0 | 1 | 2 | 3 | 1 | 2 | 3 | 1 | 2 | 3 | A | B | Group 0 Conversions | +| Fold 1 | 0 | 4 | 5 | 6 | 4 | 5 | 6 | 7 | 8 | 9 | A | B | Group 1 Conversions | +| Fold 2 | 0 | 7 | 8 | 9 | 4 | 5 | 6 | 7 | 8 | 9 | A | B | Group 2 Conversions | + +The items Group 0, Group 1 and Group 2 simply enable the determination of whether a given character is a member of the given group by checking the value of the Group x element associated with the value of the character. + +The elements of the Fold 0 item associated with the members of a given group represent the characters within Group 0 to which the characters of the given group are mapped. For example character 4 in Group 1 is mapped to character 1 in Group 0. + +The elements of the Fold 1 and Fold 2 items provide the reverse mapping in that the elements associated with membership of Group 0 represent the characters in Groups 1 or 2 that are associated with the Group 0 characters. + +Thus if the "current group" is Group x, a character with value c can be encoded as follows: + +- If c is a member of Group x or not a member of any group, element c of Fold 0 is output. +- If c is not a member of Group x it can be output as a "literal" which is element c of Fold y where Group y has c as a member alternatively a change of group can be signalled. + +Similarly, if the "current group" is Group x, a character with value c can be decoded as follows: + +- If c is a member of Group x or x is not 0 then, element c of Fold x is output. +- Otherwise the value c is output unchanged. + +The detailed operation of the Character Group processor (described below) primarily extends these simple rules to optimize the case where a choice between a "literal" or a group change arises. + +### 6.6.1 Character Groups + +A Character Group specifies the following items: + +#### 1) Character Set ID + +This is the character set in which the character group is composed and shall therefore be equal to the character set to be used for compression as specified in the CH. + +#### 2) Number of Groups + +This value specifies the number of groups to be defined. The maximum value is 8. + +#### 3) Group Transition Controls + +Group transitions are signalled through the use of the Character Group Transition symbols in the decimal range 259 to 265. + +If the Number of Groups is N, (N-1) Character Group Transition symbols shall be specified such that if the "current group" is x one Character Group Transition symbol is allocated to signify a transition to each of the other (N-1) groups. + +#### 4) Fold Tables + +These are the inter-group character conversion tables described above. One is required for each group defined. + +#### 5) Group Membership + +This is an array of octets, one for each character in the character set. The 1st octet in the array contains bit flags indicating the group membership of the character value 0 and so on. + +Within each octet, bit 0 (least significant) indicates membership of Group 0, bit 1 that of Group 1 and so on. + +### 6.6.2 Initialization + +Initialization of the Character Group processor involves loading the various parameters specified by the CG-ID contained in the CH. + +Additionally on initialization, the "current group" is assumed to be Group 0. + +### 6.6.3 Compression + +For compression, the Character Group processor operates as follows: + +**Table 22: compression Character Group processor** + +| | | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | 1) A single symbol to be encoded.
2) An indication that this is the last symbol to be encoded. | +| Step 1 | Set the number of output symbols to zero. | +| Step 2 | If the input symbol is not the Keyword symbol, goto Step 3.

If a previous input symbol is being held, add this as a "literal" to the output sequence by calculating the value of the element indicated by the value of the previous symbol in the fold table associated with the group of the previous symbol and increment the number of output symbols and clear the previous symbol.

Goto Step 9. | +| Step 3 | If the input symbol is a member of no group or a member of the current group, set the group for the input symbol to be the current group.

Otherwise, if a previous input symbol is being held and the input symbol is a member of the group of the previous symbol, set the group for the input symbol to be that of the previous symbol.

Otherwise, test the input symbol for membership of each group in ascending order of groups starting with group 0 and set the group for the input symbol to be that for which membership is first detected. | +| Step 4 | If a previous input symbol is not being held goto Step 5.

If the input symbol group equals the previous symbol group:
  • - Add the Character Group Transition symbol that indicates a transition from the current group to the previous symbol group to the output sequence and increment the number of output symbols.
  • - Set the current group to the previous symbol group.
  • - Encode the previous symbol by calculating the value of the element indicated by the value of the previous symbol in the fold table associated with the base group and add this value to the output sequence and increment the number of output symbols.
  • - Encode the input symbol by calculating the value of the element indicated by the value of the input symbol in the fold table associated with the base group and add this value to the output sequence and increment the number of output symbols.
  • - Clear the previous symbol.
  • - Goto Step 9.
Otherwise, encode the previous symbol as a "literal" by calculating the value of the element indicated by the value of the previous symbol in the fold table associated with the group of the previous symbol group and add this value to the output sequence and increment the number of output symbols and clear the previous symbol. | +| Step 5 | If the input symbol group is the base group and the current group is not the base group, add the Character Group Transition symbol that indicates a transition from the current group to the base group to the output sequence and increment the number of output symbols. Set the current group to be the base group. | +| Step 6 | If the input symbol group is the base group or the current group:
  • - Encode the input symbol by calculating the value of the element indicated by the value of the input symbol in the fold table associated with the base group and add this value to the output sequence and increment the number of output symbols.
  • - Goto Step 9.
| +| Step 7 | If the input symbol is the last symbol to be encoded:
  • - Encode the input symbol as a "literal" by calculating the value of the element indicated by the value of the input symbol in the fold table associated with the group of the input symbol and add this value to the output sequence and increment the number of output symbols.
  • - Goto Step 9.
| +| Step 8 | Set the previous symbol to be the value of the input symbol and set the group for the previous symbol to be that of the input symbol. | +| Step 9 | Output the number of output symbols and the associated symbols. | +| Output | A count of the number of encoded symbols output and a sequence of encoded symbols. | + +### 6.6.4 Decompression + +For decompression, the Character Group processor operates as follows: + +**Table 23: Decompression Character Group processor** + +| | | +|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | A single symbol to be decoded. | +| Step 1 | If the symbol is a Character Group Transition symbol, update the "current group" to be that indicated by the Character Group Transition.

Goto Step 3. | +| Step 2 | If the input symbol is a member of the "current group" or the "current group" is not the base group, calculate the value of the decoded symbol as that given by the element indicated by the value of the input symbol in the fold table associated with the "current group".

Otherwise set the value of the decoded symbol to that of the input symbol. | +| Step 3 | If a decoded symbol has been generated indicate this fact. | +| Output | The decoded symbol or an indication that no symbol has been generated. | + +## 6.7 Huffman coding + +As described in subclause 4.2, Huffman encoding requires the set of characters that may be encoded to be represented within a binary tree structure. The tree is constructed of "nodes" which have the following properties: + +- A Parent node. A node that has no parent is the "root" node. +- Up to 2 Child nodes. A node that has no children is a "leaf" node. +- Character value. If the node is a leaf node it represents a character represented within the tree. +- Weight. If the node is a leaf node, the weight is the frequency with which the associated character has occurred in the input stream. Otherwise the weight is simply the sum of the weights of the nodes children. + +Typically, a tree will be implemented as an array of node structures and parent / child details for a given node will be represented by the index of the appropriate node within the array. + +Every node in the tree (except the root node or in the case where the tree contains just a single leaf node) has a "sibling" - the other node that shares the same parent node. + +For the binary tree to be a Huffman tree its construction needs to display a further property. This is that the nodes can be listed in ascending order of weight and in so doing every node is adjacent to its sibling in the list. This property needs to be preserved at all times - when the tree is initially created, when a new leaf node is added to the tree to represent a new character and when the frequency of a leaf node is incremented as a new instance of that character is processed. + +The ordering of nodes is also significant in that it will determine which of the siblings is the "left-hand" as opposed to "right-hand" of the sibling pair. Encoding a symbol involves navigating the tree from leaf to root and emitting a bit to the encoded stream the value of which depends on whether the current node is the left or right hand sibling. If the node is a left hand node, the bit value is 0 and if it is a right hand node, the bit value is 1. Assuming that the 1st element of the array of nodes has an index value of 0, this means that left hand nodes will have even numbered indices and right hand nodes will have odd numbered indices. + +Node weights are assumed to be 16 bit unsigned values and this means that the potential exists for these values to overflow. To handle this case, the algorithm defines a maximum weight value for the root node. If this is to be exceeded, the weights of all leaf nodes are divided by 2 and the tree is rebuilt. The maximum value for the root weight is defined to be 8000 (hex). + +Although the bit sequence representing the encoded symbol is discovered in the order of traversing the tree from leaf to root, for decoding the bit sequence needs to be processed in the order that describes the navigation of the tree from root to leaf. Thus the entire encoding bit sequence needs to be collected in some temporary variable and emitted to the output stream in reverse order. For example if the passage from leaf to root is described by the sequence 010011, the bits added to the output stream would be 110010. The need to collect the bits in a temporary variable also introduces the potential for this value to overflow. Given the maximum value for the root node weight described above, a 32bit variable is suitable of containing all possible bit sequences. + +If a symbol that does not already exist in the tree is to be encoded, either the "New 7bit Character" or the "New 8bit Character" is encoded, the lower 7 bits of the new character value are then added literally to the out put stream and the new character needs to be added to the tree. This is done by splitting the "lightest" node (the first node in the list ordered by ascending weight) such that it becomes a parent node whose right hand child is the leaf node that was originally represented by the node being split and the left hand child is a new leaf node representing the new character. The new leaf is initially created with a weight of 0 but this is immediately updated as described below. + +If a new symbol has been added to the tree or a new instance of an existing symbol processed, the weight for the associated leaf node needs to be incremented and the tree updated to preserve the "sibling" property. + +The tree is updated in the following manner. If the node a position x in the ascending weight ordered list has had its weight incremented by 1, the list needs to be scanned from position x in ascending weight order to identify the node at position y such that the node at position (y+1) is the first node encountered that has a weight greater than or equal to the new weight of the node at position x. The nodes at x and y are then "swapped" in terms of their position in the list and their parents while maintaining all other attributes. This process of weight increment and swapping is then repeated for the parent of the node at position y until the root node is reached. + +The operation of the Huffman processor is controlled by the set of parameters defined by a Huffman Initialization that is uniquely defined (within a CLC) by the value of the Huffman Initialization ID (HI-ID) specified in the CH. + +### 6.7.1 Initialization Overview + +A Huffman Initialization specifies the following items: + +#### 1) Character Set ID + +This is the character set in which the Huffman Initialization is composed and shall therefore be equal to the character set to be used for compression as specified in the CH. + +#### 2) Options + +This is a collection of bit flags that control how the processor is to operate. These are described in table 24 in which Bit 0 is considered to be the least significant bit of the Match Options value. + +**Table 24: collection of bit flags** + +| Bit | Description | +|-----|-------------------------------------------------------------------------------------------------------------------------------------------------| +| 0 | If set, weights for leaf nodes representing control symbols (other than New 7 bit character and New 8 bit character symbols) are to be updated. | +| 1 | If set, weights for leaf nodes representing control symbols are to be updated. | +| 2 | All other bits are reserved. | + +#### 3) The Character Group ID with which these initializations may operate. + +#### 4) Number of initial symbol frequencies + +2 values representing the cases where the Character Group processor is enabled or disabled. + +These are counts of the number of characters or control symbols for which there are following initial frequencies defined. + +As this initializations will vary significantly depending on whether the Character Group processor is enabled 2 sets of initializations are provided to cover both cases. + +#### 5) Initial frequencies + +Two sets of initialization values are supplied as described above. + +Any control symbol that may occur when processing an input stream needs to be represented within the tree, prior to the first character of the input stream being processed. These symbols shall therefore be handled by the initialization process. This is achieved by : + +- The frequency initialization *data* will always include all control symbols that *might* occur for any stream. Thus the New 7bit character, New 8bit character, New UCS2 Row and Keyword symbols will always be included and if the initialization set is that for the case where the specified Character Group ID is enabled, the associated Character Group Transition symbols will also be included. +- For a given input stream, the frequency initialization *process* (described in subclause 6.7.2 below) will determine whether a control symbol contained in the frequency initialization *data* can occur in the input stream based on the information contained in the CH. If it is determined that a control symbol contained in the frequency initialization *data* can NOT occur in the input stream, this symbol will not be added to the Huffman tree. + +Frequency initialization data comprises the value of the character or symbol and the initial frequency for that symbol. + +- The order in which character or symbol values and their associated initial frequencies are stated is significant and this order must be preserved when these items are loaded as part of the Huffman Initialisation process. Frequency Initialisation data must be stated in ascending order of character or symbol initial frequency. + +### 6.7.2 Initialization + +Initialization of the Huffman processor involves loading the various parameters specified by the HI-ID contained in the CH. + +The appropriate set of frequency initialization data is selected depending on whether the Character Group processor is enabled. + +Leaf nodes are created for each symbol for which a frequency initialization is specified, subject to the following rules: + +- Leaf nodes must be created within the array of Huffman tree nodes in exactly the same ascending order in which they are stated in the Huffman Initialisation data. +- If the character set specified for compression is the GSM 7 bit default alphabet, leaf nodes are not created for the New 8bit Character and the New UCS2 Row symbols. +- If the character set specified for compression is not UCS2 a leaf node is not created for the New UCS2 Row symbol. +- If the Keyword processor is disabled, no leaf node is created for the Keyword symbol. + +The initial tree is then built as described below - rescaling is not indicated. + +### 6.7.3 Build Tree + +To build the tree, the Huffman processor operates as follows: + +**Table 25: Build Tree, Huffman processor operation** + +| | | +|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | 1) The array of Huffman tree nodes.
2) A Boolean value indicating whether frequencies need to be rescaled as a result of the root node weight becoming the maximum value. | +| Step 1 | Assemble all leaf nodes, preserving their ascending weight order at the start of the node array. This is achieved by setting the "current node" and "assembled leaf" node position to the base of the array. If the current node is a leaf node, set the symbol and frequency associated with assembled leaf node to those of the current node and increment the assembled leaf node position. Increment the current node position and repeat this process until the current node becomes the root node.

If rescaling is requested recalculate each leaf node weight as $(\text{current weight} + 1) / 2$ .

Set the current node to the start of the array. | +| Step 2 | Create a parent node for the current node and the next node and insert it into the array at position x where the node at position $(x+1)$ is the first node with a weight greater than that of the newly created node.

If the newly created node is not the root node, increment the current node by 2 and goto Step 2. | +| Output | A completed Huffman tree. | + +### 6.7.4 Update Tree + +To update the tree, the Huffman processor operates as follows: + +**Table 26: Update Tree, Huffman processor operation** + +| | | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | The symbol whose frequency is to be incremented by 1. | +| Step 1 | If the weight of the root node +1 is greater than $0 \times 8000$ build the tree indicating that resealing is required. | +| Step 2 | Increment the weight of the leaf node associated with the input symbol by 1 and "swap" it with the node at position y such that the node at position $(y+1)$ is the first node encountered in the order list that has a weight greater than or equal to the new weight of the incremented leaf node.

Repeat this process of weight increment and "swap" for the parent of the node at position y until the node at position y becomes the root node. | +| Output | An updated Huffman tree. | + +### 6.7.5 Add New Node + +To add a new node, the Huffman processor operates as follows: + +**Table 27: Add New Node, Huffman processor operation** + +| | | +|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | The symbol to be added to the tree. | +| Step 1 | Splitting the "lightest" node (the first node in the list ordered by ascending weight) such that it becomes a parent node whose right hand child is the leaf node that was originally represented by the node being split and the left hand child is a new leaf node representing the new input symbol. The new leaf node is initially created with a weight of 0. | +| Step 2 | Update the tree (as above) passing the new symbol as the input parameter. | +| Output | An updated Huffman tree. | + +### 6.7.6 Compression + +For compression, the Huffman processor operates as follows: + +**Table 28: Compression, Huffman processor operation** + +| | | +|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | A character from the input stream or control symbol. | +| Step 1 | If there is no existing leaf node for the input symbol set the "source" symbol to be either the New 7bit or New 8bit symbol depending on the value of the input symbol.
Otherwise set the source symbol to be the input symbol. | +| Step 2 | Traverse the tree from the leaf node associated with the source symbol to the root node while generating the Huffman bit sequence. | +| Step 3 | Reverse the generated Huffman bit sequence and add it to the output bitstream. | +| Step 4 | If the source symbol equals the input symbol goto Step 5.

Add the lower 7 bits of the input symbol to the output bitstream.

Add a new node for the input symbol.

Update the tree for the input symbol.

Goto Output. | +| Step 5 | If the input symbol value is less than 256 and bit 0 of the Huffman Initialization Options value is set, update the tree for the input symbol and goto Output. | +| Step 6 | If the input symbol value is greater than or equal 256 and bit 1 of the Huffman Initialization Options value is set, update the tree for the input symbol. | +| Output | A Huffman bitstream. | + +### 6.7.7 Decompression + +For decompression, the Huffman processor operates as follows: + +**Table 29: Decompression, Huffman processor operation** + +| | | +|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Input | A bit stream. | +| Step 1 | Traverse the tree from the root node to a leaf node as indicated by the value of the bits read from the front of the input bitstream. | +| Step 2 | If the symbol associated with the leaf node identified in step 1 is neither the New 7bit nor New 8bit symbol, goto Step 3.

Set the lower 7 bits of the output symbol to be next 7 bits read from the input bitstream and set bit 7 as indicated.

Add a new node for the output symbol.

Update the tree for the output symbol.

Goto Output. | +| Step 3 | Set the output symbol to the symbol associated with the leaf node from Step 1. | +| Step 4 | If the output symbol value is less than 256 and bit 0 of the Huffman Initialization Options value is set, update the tree for the output symbol and goto Output. | +| Step 5 | If the input symbol value is greater than or equal 256 and bit 1 of the Huffman Initialization Options value is set update the tree for the output symbol. | +| Output | A decoded symbol. | + +# 7 Test Vectors + +In order to assist implementors of the compression algorithm described in this specification, a suite of test vectors and 'help' information are available in electronic format. The test vectors are supplied on a single diskette attached to this specification. + +These test vectors provide checks for most of the commonly expected parameter value variants in this specification and may be updated as the need arises. + +# --- Annex A (normative): German Language parameters + +## A.1 Compression Language Context + +**CLC Value: 0 (decimal)** + +**This specifies the following items as defaults:** + +- | | | +|------------------------------|----------------------------------------------| +| 1) Language | German | +| 2) Character set | Character Set ID 3 (decimal) = Code Page 850 | +| 3) Punctuation ID | 0 (decimal) | +| 4) Keyword Dictionary ID | 0 (decimal) | +| 5) Character Group ID | 1 (decimal) | +| 6) Huffman Initialization ID | 1 (decimal) | + +## --- A.2 Punctuations + +### **Punctuation ID 0 (decimal)** + +This punctuation ID has the special meaning that no punctuation is defined (or therefore enabled) and the value of bit 2 of octet 1 of the CH is always to be interpreted as zero. + +### **Punctuation ID 1 (decimal)** + +The punctuation is rendered in Character Set ID 3 (decimal) = Code Page 850. + +The following characters have punctuation attributes set: + +**Table A.1: punctuation attributes set:** + +| Char | Value | PU-IWS | PU-LST | PU-WSF | PU-UCF | PU-UCW | PU-NSI | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------|---------------|---------------|---------------|---------------|---------------| +| | 010 | 0 | 0 | 0 | 1 | 0 | 0 | +| | 013 | 0 | 0 | 0 | 1 | 0 | 0 | +| | 032 | 1 | 0 | 0 | 0 | 0 | 0 | +| ! | 033 | 0 | 0 | 1 | 1 | 0 | 0 | +| , | 044 | 0 | 0 | 1 | 0 | 0 | 0 | +| . | 046 | 0 | 1 | 1 | 1 | 0 | 0 | +| 0 | 048 | 0 | 0 | 0 | 0 | 0 | 1 | +| 1 | 049 | 0 | 0 | 0 | 0 | 0 | 1 | +| 2 | 050 | 0 | 0 | 0 | 0 | 0 | 1 | +| 3 | 051 | 0 | 0 | 0 | 0 | 0 | 1 | +| 4 | 052 | 0 | 0 | 0 | 0 | 0 | 1 | +| 5 | 053 | 0 | 0 | 0 | 0 | 0 | 1 | +| 6 | 054 | 0 | 0 | 0 | 0 | 0 | 1 | +| 7 | 055 | 0 | 0 | 0 | 0 | 0 | 1 | +| 8 | 056 | 0 | 0 | 0 | 0 | 0 | 1 | +| 9 | 057 | 0 | 0 | 0 | 0 | 0 | 1 | +| : | 058 | 0 | 0 | 1 | 0 | 0 | 0 | +| ; | 059 | 0 | 0 | 1 | 0 | 0 | 0 | +| ? | 063 | 0 | 0 | 1 | 1 | 0 | 0 | +| NOTE: The characters "" are used to represent the "space" character, the characters "" the "line feed" character and "" the "carriage return" character. | | | | | | | | + +### **Punctuation ID >1 (decimal)** + +No other punctuators are defined and all other values are reserved. + +## A.3 Keyword Dictionaries + +### **Keyword Dictionary ID 0 (decimal)** + +This Keyword Dictionary ID has the special meaning that no Keyword Dictionary is defined (or therefore enabled) and the value of bit 1 of octet 1 of the CH is always to be interpreted as zero. + +### **Keyword Dictionary ID 1 (decimal)** + +The Keyword Dictionary is rendered in Character Set ID 3 (decimal) = Code Page 850. + +The Match Options value is 94 (decimal) indicating the following: + +- Partial matching is enabled. +- Suffix matching is not enabled. +- Prefix matching is enabled. +- 1st char upper case, remainder lower case matching is enabled. +- Upper case matching is enabled. + +- Lower case matching is enabled. +- Exact matching is not enabled. + +The Keyword Prefix Length is 1 and the prefix string contains a single character with value 32 decimal (a space). + +The Keyword Suffix Length is 0. + +The Keyword Threshold value is 4. + +The Maximum Partial Match Length value is 20 (decimal). + +The Key Word Group List contains only 1 Key Word Group ID. The value of this Key Word Group ID is 0. + +### **Keyword Dictionary ID >1 (decimal)** + +No other Keyword Dictionaries are defined and all other values are reserved. + +### **Key Word Group ID 0 (decimal)** + +The entries within this Key Word Group are rendered in Character Set ID 3 (decimal) = Code Page 850. + +The Number of Entries value is 128 (decimal). + +The entries are defined in table A.2 wherein the characters "" are used to represent the "space" character of decimal value 32. + +#### **Table A.2: Key Word Group ID 0 (decimal)** + +| Entry ID | Entry Length | Entry String | +|----------|--------------|-----------------| +| 1 | 5 | Abend | +| 2 | 7 | Abholen | +| 3 | 6 | Alles | +| 4 | 10 | Angekommen | +| 5 | 9 | Angerufen | +| 6 | 7 | Anrufen | +| 7 | 7 | Antwort | +| 8 | 6 | Anzahl | +| 9 | 6 | Arbeit | +| 10 | 5 | Auch | +| 11 | 8 | Bekommen | +| 12 | 8 | Bescheid | +| 13 | 6 | Besser | +| 14 | 5 | Bitte | +| 15 | 7 | Brauche | +| 16 | 5 | Dabei | +| 17 | 6 | Damit | +| 18 | 5 | Danke | +| 19 | 5 | Dann | +| 20 | 8 | Dienstag | +| 21 | 5 | Doch | +| 22 | 10 | Donnerstag | +| 23 | 8 | Dringend | +| 24 | 10 | Eigentlich | +| 25 | 7 | Einfach | +| 26 | 6 | Einmal | +| 27 | 7 | Empfang | +| 28 | 7 | Endlich | +| 29 | 11 | Erfolgreich | +| 30 | 9 | Eröffnung | +| 31 | 8 | Erhalten | +| 32 | 10 | Erreichbar | +| 33 | 5 | Essen | +| 34 | 6 | Etwas | +| 35 | 6 | Fahren | +| 36 | 10 | Feierabend | +| 37 | 6 | Fertig | +| 38 | 7 | Freitag | +| 39 | 6 | Freund | +| 40 | 5 | Gegen | +| 41 | 5 | Gehen | +| 42 | 5 | Geht | +| 43 | 6 | Gerade | +| 44 | 8 | Gespräch | +| 45 | 7 | Gestern | +| 46 | 6 | Glaube | +| 47 | 6 | Gleich | +| 48 | 6 | Grüsse | +| 49 | 5 | Guten | +| 50 | 5 | Haben | +| 51 | 6 | Hallo | +| 52 | 6 | Heute | +| 53 | 12 | Hoffentlich | +| 54 | 6 | Immer | +| 55 | 6 | Jetzt | +| 56 | 6 | Kaufen | +| 57 | 6 | Können | +| 58 | 5 | Komme | +| 59 | 6 | Konnte | +| 60 | 5 | Konto | +| 61 | 5 | Lange | +| 62 | 7 | Langsam | +| 63 | 6 | Lassen | + +| Entry ID | Entry Length | Entry String | +|----------|--------------|----------------| +| 64 | 6 | Laufen | +| 65 | 7 | Leider | +| 66 | 6 | Letzte | +| 67 | 5 | Liebe | +| 68 | 6 | Machen | +| 69 | 5 | Macht | +| 70 | 6 | Melden | +| 71 | 6 | Mittag | +| 72 | 8 | Mittwoch | +| 73 | 6 | Montag | +| 74 | 6 | Morgen | +| 75 | 7 | Nachher | +| 76 | 10 | Nachmittag | +| 77 | 9 | Nachricht | +| 78 | 5 | Nacht | +| 79 | 9 | Natürlich | +| 80 | 5 | Nicht | +| 81 | 6 | Nummer | +| 82 | 7 | Nutzung | +| 83 | 5 | Pause | +| 84 | 7 | Problem | +| 85 | 7 | Rückruf | +| 86 | 8 | Rechnung | +| 87 | 5 | Reden | +| 88 | 7 | Richtig | +| 89 | 5 | Sagen | +| 90 | 7 | Samstag | +| 91 | 8 | Schlafen | +| 92 | 8 | Schlecht | +| 93 | 7 | Schnell | +| 94 | 6 | Schon | +| 95 | 5 | Schön | +| 96 | 7 | Schreib | +| 97 | 6 | Schule | +| 98 | 5 | Sehen | +| 99 | 6 | Sicher | +| 100 | 6 | Sofort | +| 101 | 7 | Sonntag | +| 102 | 5 | Sonst | +| 103 | 6 | Später | +| 104 | 6 | Stunde | +| 105 | 7 | Telefon | +| 106 | 6 | Termin | +| 107 | 5 | Total | +| 108 | 7 | Treffen | +| 109 | 7 | Trinken | +| 110 | 10 | Unterwegs | +| 111 | 6 | urlaub | +| 112 | 9 | Vergessen | +| 113 | 7 | Versuch | +| 114 | 11 | Vielleicht | +| 115 | 14 | Wahrscheinlich | +| 116 | 5 | Wann | +| 117 | 6 | Warum | +| 118 | 6 | Wegen | +| 119 | 5 | Wenn | +| 120 | 6 | Werden | +| 121 | 7 | Wichtig | +| 122 | 6 | Wieder | +| 123 | 8 | Wirklich | +| 124 | 6 | Wissen | +| 125 | 5 | Woche | +| 126 | 10 | Wochenende | + +| Entry ID | Entry Length | Entry String | +|----------|--------------|--------------| +| 127 | 6 | Zurück | +| 128 | 8 | Zusammen | + +### Key Word Group ID >0 (decimal) + +No other Key Word Groups are defined and all other values are reserved. + +## A.4 Character Groups + +### Character Group ID 0 (decimal) + +This Character Group ID has the special meaning that no Character Group is defined (or therefore enabled) and the value of bit 0 of octet 1 of the CH is always to be interpreted as zero. + +### Character Group ID 1 (decimal) + +The Character Group is rendered in Character Set ID 3 (decimal) = Code Page 850. + +The Number of Groups value is 3. + +There are 2 Group Transition symbols used these have the decimal values 259 and 260. Their use in signalling transitions between the 3 groups are shown in the table A.3. + +**Table A.3: Character Group ID 1 (decimal)** + +| Current Group | New Group | | | +|---------------|-----------|-----|-----| +| | 0 | 1 | 2 | +| 0 | | 260 | 259 | +| 1 | 260 | | 259 | +| 2 | 260 | 259 | | + +The fold tables and Group Membership bit flags are set out in the following table A.4. + +#### **Table A.4: fold tables and Group Membership bit flags** + +| Char | Value | Group 0
Fold
Table | Group 1
Fold
Table | Group 2
Fold Table | Group 2
Member | Group 1
Member | Group 0
Member | +|------|-------|--------------------------|--------------------------|-----------------------|-------------------|-------------------|-------------------| +| | 032 | 032 | 032 | 032 | 1 | 1 | 1 | +| ! | 033 | 033 | 033 | 033 | 1 | 1 | 1 | +| " | 034 | 034 | 034 | 012 | 1 | 1 | 1 | +| # | 035 | 107 | 035 | 035 | 1 | 0 | 0 | +| \$ | 036 | 113 | 035 | 035 | 1 | 0 | 0 | +| % | 037 | 118 | 037 | 037 | 1 | 0 | 0 | +| & | 038 | 112 | 038 | 038 | 1 | 0 | 0 | +| ' | 039 | 111 | 039 | 039 | 1 | 0 | 0 | +| ( | 040 | 119 | 040 | 040 | 1 | 0 | 0 | +| ) | 041 | 098 | 041 | 041 | 1 | 0 | 0 | +| * | 042 | 109 | 042 | 042 | 1 | 0 | 0 | +| + | 043 | 103 | 043 | 043 | 1 | 0 | 0 | +| , | 044 | 044 | 044 | 044 | 1 | 1 | 1 | +| - | 045 | 097 | 045 | 045 | 1 | 0 | 0 | +| . | 046 | 046 | 046 | 046 | 1 | 1 | 1 | +| / | 047 | 102 | 047 | 047 | 1 | 0 | 0 | +| 0 | 048 | 110 | 048 | 048 | 1 | 0 | 0 | +| 1 | 049 | 101 | 049 | 049 | 1 | 0 | 0 | +| 2 | 050 | 105 | 050 | 050 | 1 | 0 | 0 | +| 3 | 051 | 104 | 051 | 051 | 1 | 0 | 0 | +| 4 | 052 | 114 | 052 | 052 | 1 | 0 | 0 | +| 5 | 053 | 100 | 053 | 053 | 1 | 0 | 0 | +| 6 | 054 | 108 | 054 | 054 | 1 | 0 | 0 | +| 7 | 055 | 115 | 055 | 055 | 1 | 0 | 0 | +| 8 | 056 | 117 | 056 | 056 | 1 | 0 | 0 | +| 9 | 057 | 099 | 057 | 057 | 1 | 0 | 0 | +| : | 058 | 116 | 058 | 058 | 1 | 0 | 0 | +| ; | 059 | 121 | 059 | 059 | 1 | 0 | 0 | +| < | 060 | 106 | 060 | 060 | 1 | 0 | 0 | +| = | 061 | 120 | 061 | 061 | 1 | 0 | 0 | +| > | 062 | 122 | 062 | 062 | 1 | 0 | 0 | +| ? | 063 | 063 | 063 | 063 | 1 | 1 | 1 | +| A | 065 | 097 | 065 | 065 | 0 | 1 | 0 | +| B | 066 | 098 | 066 | 066 | 0 | 1 | 0 | +| C | 067 | 099 | 067 | 067 | 0 | 1 | 0 | +| D | 068 | 100 | 068 | 068 | 0 | 1 | 0 | +| E | 069 | 101 | 069 | 069 | 0 | 1 | 0 | +| F | 070 | 102 | 070 | 070 | 0 | 1 | 0 | +| G | 071 | 103 | 071 | 071 | 0 | 1 | 0 | +| H | 072 | 104 | 072 | 072 | 0 | 1 | 0 | +| I | 073 | 105 | 073 | 073 | 0 | 1 | 0 | +| J | 074 | 106 | 074 | 074 | 0 | 1 | 0 | +| K | 075 | 107 | 075 | 075 | 0 | 1 | 0 | +| L | 076 | 108 | 076 | 076 | 0 | 1 | 0 | +| M | 077 | 109 | 077 | 077 | 0 | 1 | 0 | +| N | 078 | 110 | 078 | 078 | 0 | 1 | 0 | +| O | 079 | 111 | 079 | 079 | 0 | 1 | 0 | +| P | 080 | 112 | 080 | 080 | 0 | 1 | 0 | +| Q | 081 | 113 | 081 | 081 | 0 | 1 | 0 | +| R | 082 | 114 | 082 | 082 | 0 | 1 | 0 | +| S | 083 | 115 | 083 | 083 | 0 | 1 | 0 | +| T | 084 | 116 | 084 | 084 | 0 | 1 | 0 | +| U | 085 | 117 | 085 | 085 | 0 | 1 | 0 | +| V | 086 | 118 | 086 | 086 | 0 | 1 | 0 | +| W | 087 | 119 | 087 | 087 | 0 | 1 | 0 | +| X | 088 | 120 | 088 | 088 | 0 | 1 | 0 | +| Y | 089 | 121 | 089 | 089 | 0 | 1 | 0 | +| Z | 090 | 122 | 090 | 090 | 0 | 1 | 0 | +| a | 097 | 097 | 065 | 045 | 0 | 0 | 1 | +| b | 098 | 098 | 066 | 041 | 0 | 0 | 1 | +| c | 099 | 099 | 067 | 057 | 0 | 0 | 1 | + +| Char | Value | Group 0 Fold Table | Group 1 Fold Table | Group 2 Fold Table | Group 2 Member | Group 1 Member | Group 0 Member | +|------|-------|--------------------|--------------------|--------------------|----------------|----------------|----------------| +| d | 100 | 100 | 068 | 053 | 0 | 0 | 1 | +| e | 101 | 101 | 069 | 049 | 0 | 0 | 1 | +| f | 102 | 102 | 070 | 047 | 0 | 0 | 1 | +| g | 103 | 103 | 071 | 043 | 0 | 0 | 1 | +| h | 104 | 104 | 072 | 051 | 0 | 0 | 1 | +| i | 105 | 105 | 073 | 050 | 0 | 0 | 1 | +| j | 106 | 106 | 074 | 060 | 0 | 0 | 1 | +| k | 107 | 107 | 075 | 035 | 0 | 0 | 1 | +| l | 108 | 108 | 076 | 054 | 0 | 0 | 1 | +| m | 109 | 109 | 077 | 042 | 0 | 0 | 1 | +| n | 110 | 110 | 078 | 048 | 0 | 0 | 1 | +| o | 111 | 111 | 079 | 039 | 0 | 0 | 1 | +| p | 112 | 112 | 080 | 038 | 0 | 0 | 1 | +| q | 113 | 113 | 081 | 036 | 0 | 0 | 1 | +| r | 114 | 114 | 082 | 052 | 0 | 0 | 1 | +| s | 115 | 115 | 083 | 055 | 0 | 0 | 1 | +| t | 116 | 116 | 084 | 058 | 0 | 0 | 1 | +| u | 117 | 117 | 085 | 056 | 0 | 0 | 1 | +| v | 118 | 118 | 086 | 037 | 0 | 0 | 1 | +| w | 119 | 119 | 087 | 040 | 0 | 0 | 1 | +| x | 120 | 120 | 088 | 061 | 0 | 0 | 1 | +| y | 121 | 121 | 089 | 059 | 0 | 0 | 1 | +| z | 122 | 122 | 090 | 062 | 0 | 0 | 1 | + +NOTE: The characters "" are used to represent the "space" character. + +Characters with any other value in the range 0 to 255 are not a member of any group and therefore the fold table values will be equal to the character value in all cases. + +### Character Group ID >1 (decimal) + +No other Character Groups are defined and all other values are reserved. + +## A.5 Huffman Initializations + +### Huffman Initialization ID 0 (decimal) + +The Huffman Initialization is rendered in Character Set ID 3(decimal) = Code Page 850. + +The Options value indicates that both character and control symbol updating are enabled. + +As described in subclause 6.7.1, the tables below include initialization values for *all* control symbols that *might* occur in conjunction with the use of this Huffman Initialization. However, initialization values for control symbols that *cannot* occur for a *particular* use of this Huffman Initialization are identified as part of the Huffman initialization process and are *not* added to the Huffman tree as described in subclause 6.7.2. + +The Character Group ID value is 1. + +#### **Character Group Processing is disabled:** + +The number of frequency initializations is 4. + +The initial frequencies are: + +**Table A.5: Character Group Processing is disabled: initial frequencies** + +| Symbol | Value | Frequency | +|--------------|-------|-----------| +| New UCS2 Row | 266 | 1 | +| Keyword | 258 | 1 | +| New 8bit | 257 | 1 | +| New 7bit | 256 | 1 | + +#### **Character Group Processing is enabled:** + +The number of frequency initializations is 6. + +The initial frequencies are: + +**Table A.6: Character Group Processing is enabled: initial frequencies** + +| Symbol | Value | Frequency | +|--------------|-------|-----------| +| New UCS2 Row | 266 | 1 | +| Change CG1 | 260 | 1 | +| Change CG0 | 259 | 1 | +| Keyword | 258 | 1 | +| New 8bit | 257 | 1 | +| New 7bit | 256 | 1 | + +### **Huffman Initialization ID 1 (decimal)** + +The Huffman Initialization is rendered in Character Set ID 3 (decimal) = Code Page 850. + +The Options value indicates that both character and control symbol updating are enabled. + +As described in subclause 6.7.1, the tables below include initialization values for *all* control symbols that *might* occur in conjunction with the use of this Huffman Initialization. However, initialization values for control symbols that *cannot* occur for a *particular* use of this Huffman Initialization are identified as part of the Huffman initialization process and are *not* added to the Huffman tree as described in subclause 6.7.2. + +The Character Group ID value is 1. + +#### **Character Group Processing is disabled:** + +The number of frequency initializations is 32. + +The initial frequencies are: + +**Table A.7: Character Group Processing is disabled: initial frequencies** + +| Symbol | Value | Frequency | +|--------------|-------|-----------| +| New UCS2 Row | 266 | 00001 | +| q | 113 | 00001 | +| x | 120 | 00001 | +| y | 121 | 00001 | +| j | 106 | 00001 | +| v | 118 | 00001 | +| p | 112 | 00001 | +| New 8bit | 257 | 00002 | +| z | 122 | 00002 | +| | 46 | 00003 | +| k | 107 | 00003 | +| f | 102 | 00003 | +| w | 119 | 00003 | +| Keyword | 258 | 00004 | +| b | 98 | 00004 | +| g | 103 | 00004 | +| o | 111 | 00005 | +| m | 109 | 00006 | +| l | 108 | 00006 | +| u | 117 | 00007 | +| c | 99 | 00007 | +| d | 100 | 00007 | +| New 7bit | 256 | 00009 | +| r | 114 | 00009 | +| t | 116 | 00009 | +| s | 115 | 00010 | +| h | 104 | 00010 | +| a | 97 | 00012 | +| i | 105 | 00013 | +| n | 110 | 00014 | +| e | 101 | 00021 | +| | 32 | 00032 | + +NOTE: In the above table, the characters "" are used to represent the "space" character. + +#### **Character Group Processing is enabled:** + +The number of frequency initializations is 34. + +The initial frequencies are: + +**Table A.8: Character Group Processing is enabled: initial frequencies** + +| Symbol | Value | Frequency | +|--------------|-------|-----------| +| New UCS2 Row | 266 | 00001 | +| q | 113 | 00001 | +| x | 120 | 00001 | +| y | 121 | 00001 | +| j | 106 | 00001 | +| v | 118 | 00001 | +| p | 112 | 00001 | +| New 8bit | 257 | 00002 | +| z | 122 | 00002 | +| Change CG0 | 259 | 00002 | +| . | 46 | 00003 | +| k | 107 | 00003 | +| f | 102 | 00003 | +| w | 119 | 00003 | +| Keyword | 258 | 00004 | +| Change CG1 | 260 | 00004 | +| b | 98 | 00004 | +| g | 103 | 00004 | +| o | 111 | 00005 | +| m | 109 | 00006 | +| l | 108 | 00006 | +| u | 117 | 00007 | +| c | 99 | 00007 | +| d | 100 | 00007 | +| New 7bit | 256 | 00009 | +| r | 114 | 00009 | +| t | 116 | 00009 | +| s | 115 | 00010 | +| h | 104 | 00010 | +| a | 97 | 00012 | +| i | 105 | 00013 | +| n | 110 | 00014 | +| e | 101 | 00021 | +| | 32 | 00032 | + +Note in the above table, the characters "" are used to represent the "space" character. + +### **Huffman Initialization ID >1 (decimal)** + +No other Huffman Initializations are defined and all other values are reserved. + +# --- Annex B (normative): English language parameters + +## B.1 Compression Language Context + +**CLC Value: 1 (decimal)** + +**This specifies the following items as defaults:** + +- | | | +|------------------------------|----------------------------------------------| +| 1) Language | English | +| 2) Character set | Character Set ID 2 (decimal) = Code page 437 | +| 3) Punctuation ID | 1 (decimal) | +| 4) Keyword Dictionary ID | 0 (decimal) | +| 5) Character Group ID | 1 (decimal) | +| 6) Huffman Initialization ID | 1 (decimal) | + +## --- B.2 Punctuators + +### **Punctuation ID 0 (decimal)** + +This punctuation ID has the special meaning that no punctuation is defined (or therefore enabled) and the value of bit 2 of octet 1 of the CH is always to be interpreted as zero. + +### **Punctuation ID 1 (decimal)** + +The punctuation is rendered in Character Set ID 2 (decimal) = Code Page 437. + +The following characters have punctuation attributes set: + +**Table B.1: punctuation attributes set:** + +| Char | Value | PU-IWS | PU-LST | PU-WSF | PU-UCF | PU-UCW | PU-NSI | +|-------------|--------------|---------------|---------------|---------------|---------------|---------------|---------------| +| | 010 | 0 | 0 | 0 | 1 | 0 | 0 | +| | 013 | 0 | 0 | 0 | 1 | 0 | 0 | +| | 032 | 1 | 0 | 0 | 0 | 0 | 0 | +| ! | 033 | 0 | 0 | 1 | 1 | 0 | 0 | +| , | 044 | 0 | 0 | 1 | 0 | 0 | 0 | +| . | 046 | 0 | 1 | 1 | 1 | 0 | 0 | +| 0 | 048 | 0 | 0 | 0 | 0 | 0 | 1 | +| 1 | 049 | 0 | 0 | 0 | 0 | 0 | 1 | +| 2 | 050 | 0 | 0 | 0 | 0 | 0 | 1 | +| 3 | 051 | 0 | 0 | 0 | 0 | 0 | 1 | +| 4 | 052 | 0 | 0 | 0 | 0 | 0 | 1 | +| 5 | 053 | 0 | 0 | 0 | 0 | 0 | 1 | +| 6 | 054 | 0 | 0 | 0 | 0 | 0 | 1 | +| 7 | 055 | 0 | 0 | 0 | 0 | 0 | 1 | +| 8 | 056 | 0 | 0 | 0 | 0 | 0 | 1 | +| 9 | 057 | 0 | 0 | 0 | 0 | 0 | 1 | +| : | 058 | 0 | 0 | 1 | 0 | 0 | 0 | +| ; | 059 | 0 | 0 | 1 | 0 | 0 | 0 | +| ? | 063 | 0 | 0 | 1 | 1 | 0 | 0 | +| ¡ | 073 | 0 | 0 | 0 | 0 | 1 | 0 | + +NOTE: The characters "" are used to represent the "space" character, the characters "" the "line feed" character and "" the "carriage return" character. + +### **Punctuation ID >1 (decimal)** + +No other punctuation are defined and all other values are reserved. + +## **B.3 Keyword Dictionaries** + +### **Keyword Dictionary ID 0 (decimal)** + +This Keyword Dictionary ID has the special meaning that no Keyword Dictionary is defined (or therefore enabled) and the value of bit 1 of octet 1 of the CH is always to be interpreted as zero. + +### **Keyword Dictionary ID 1 (decimal)** + +The Keyword Dictionary is rendered in Character Set ID 2 (decimal) = Code Page 437. + +The Match Options value is 94 (decimal) indicating the following: + +- Partial matching is enabled. +- Suffix matching is not enabled. +- Prefix matching is enabled. +- 1st char upper case, remainder lower case matching is enabled. + +- Upper case matching is enabled. +- Lower case matching is enabled. +- Exact matching is not enabled. + +The Keyword Prefix Length is 1 and the prefix string contains a single character with value 32 decimal (a space). + +The Keyword Suffix Length is 0. + +The Keyword Threshold value is 4. + +The Maximum Partial Match Length value is 46 (decimal). + +The Key Word Group List contains only 1 Key Word Group ID. The value of this Key Word Group ID is 0. + +### **Keyword Dictionary ID >1 (decimal)** + +No other Keyword Dictionaries are defined and all other values are reserved. + +### **Key Word Group ID 0 (decimal)** + +The entries within this Key Word Group are rendered in Character Set ID 2 (decimal) = Code Page 437. + +The Number of Entries value is 128 (decimal). + +The entries are defined in table B.2 wherein the characters "" are used to represent the "space" character of decimal value 32. + +#### **Table B.2: Key Word Group ID 0 (decimal)** + +| Entry ID | Entry Length | Entry String | +|----------|--------------|--------------| +| 1 | 5 | About | +| 2 | 9 | Afternoon | +| 3 | 5 | Again | +| 4 | 6 | Agenda | +| 5 | 6 | Agreed | +| 6 | 4 | And | +| 7 | 11 | Appointment | +| 8 | 4 | Are | +| 9 | 7 | Arrange | +| 10 | 6 | Arrive | +| 11 | 6 | Attend | +| 12 | 9 | Available | +| 13 | 4 | Away | +| 14 | 7 | Because | +| 15 | 6 | Before | +| 16 | 7 | Benefit | +| 17 | 8 | Business | +| 18 | 4 | But | +| 19 | 4 | Call | +| 20 | 6 | Can't | +| 21 | 6 | Cancel | +| 22 | 6 | Commit | +| 23 | 7 | Company | +| 24 | 8 | Complete | +| 25 | 7 | Confirm | +| 26 | 7 | Contact | +| 27 | 10 | Convenient | +| 28 | 5 | Could | +| 29 | 7 | Deliver | +| 30 | 6 | Demand | +| 31 | 10 | Department | +| 32 | 6 | Dinner | +| 33 | 7 | Discuss | +| 34 | 6 | Don't | +| 35 | 5 | Exist | +| 36 | 6 | Flight | +| 37 | 4 | For | +| 38 | 7 | Forward | +| 39 | 6 | Friday | +| 40 | 5 | From | +| 41 | 5 | Going | +| 42 | 7 | Goodbye | +| 43 | 8 | Hardware | +| 44 | 5 | Have | +| 45 | 4 | Hear | +| 46 | 5 | Hello | +| 47 | 4 | Help | +| 48 | 4 | Home | +| 49 | 5 | Hotel | +| 50 | 4 | How | +| 51 | 9 | Immediate | +| 52 | 9 | Important | +| 53 | 11 | Information | +| 54 | 4 | Its | +| 55 | 5 | Later | +| 56 | 6 | Letter | +| 57 | 7 | Machine | +| 58 | 5 | Make | +| 59 | 6 | Manage | +| 60 | 7 | Meeting | +| 61 | 7 | Message | +| 62 | 6 | Mobile | +| 63 | 6 | Monday | + +| Entry ID | Entry Length | Entry String | +|----------|--------------|--------------| +| 64 | 7 | Morning | +| 65 | 5 | Need | +| 66 | 6 | Office | +| 67 | 5 | Other | +| 68 | 6 | Passed | +| 69 | 8 | Personal | +| 70 | 5 | Phone | +| 71 | 6 | Please | +| 72 | 8 | Possible | +| 73 | 4 | Post | +| 74 | 8 | Postpone | +| 75 | 5 | Price | +| 76 | 8 | Priority | +| 77 | 7 | Product | +| 78 | 7 | Project | +| 79 | 5 | Quick | +| 80 | 7 | Receive | +| 81 | 9 | Reference | +| 82 | 7 | Regards | +| 83 | 8 | Remember | +| 84 | 6 | Return | +| 85 | 4 | Ring | +| 86 | 8 | Saturday | +| 87 | 4 | Send | +| 88 | 7 | Service | +| 89 | 6 | Should | +| 90 | 5 | Since | +| 91 | 8 | Software | +| 92 | 4 | Soon | +| 93 | 5 | Speak | +| 94 | 5 | Still | +| 95 | 7 | Subject | +| 96 | 7 | Success | +| 97 | 6 | Sunday | +| 98 | 4 | Talk | +| 99 | 9 | Telephone | +| 100 | 5 | Thank | +| 101 | 4 | That | +| 102 | 4 | The | +| 103 | 5 | Them | +| 104 | 5 | There | +| 105 | 5 | They | +| 106 | 5 | Think | +| 107 | 4 | This | +| 108 | 8 | Thursday | +| 109 | 5 | Today | +| 110 | 8 | Tomorrow | +| 111 | 7 | Tonight | +| 112 | 5 | Total | +| 113 | 6 | Travel | +| 114 | 7 | Tuesday | +| 115 | 6 | Until | +| 116 | 6 | Update | +| 117 | 6 | Urgent | +| 118 | 5 | Using | +| 119 | 4 | Want | +| 120 | 9 | Wednesday | +| 121 | 7 | Weekend | +| 122 | 7 | Welcome | +| 123 | 5 | When | +| 124 | 6 | Where | +| 125 | 4 | Will | +| 126 | 5 | Would | + +| Entry ID | Entry Length | Entry String | +|----------|--------------|--------------| +| 127 | 9 | Yesterday | +| 128 | 4 | You | + +### Key Word Group ID >0 (decimal) + +No other Key Word Groups are defined and all other values are reserved. + +## B.4 Character Groups + +### Character Group ID 0 (decimal) + +This Character Group ID has the special meaning that no Character Group is defined (or therefore enabled) and the value of bit 0 of octet 1 of the CH is always to be interpreted as zero. + +### Character Group ID 1 (decimal) + +The Character Group is rendered in Character Set ID 2 (decimal) = Code Page 437. + +The Number of Groups value is 3. + +There are 2 Group Transition symbols used these have the decimal values 259 and 260. Their use in signalling transitions between the 3 groups are shown in the table B.3. + +**Table B.3: Character Group ID 1 (decimal)** + +| Current Group | New Group | | | +|---------------|-----------|-----|-----| +| | 0 | 1 | 2 | +| 0 | | 260 | 259 | +| 1 | 260 | | 259 | +| 2 | 260 | 259 | | + +The fold tables and Group Membership bit flags are set out in the following table B.4. + +#### **Table B.4: fold tables and Group Membership bit flags** + +| Char | Value | Group 0
Fold
Table | Group 1
Fold
Table | Group 2
Fold Table | Group 2
Member | Group 1
Member | Group 0
Member | +|------|-------|--------------------------|--------------------------|-----------------------|-------------------|-------------------|-------------------| +| | 012 | 034 | 012 | 012 | 1 | 0 | 0 | +| | 032 | 032 | 032 | 032 | 1 | 1 | 1 | +| ! | 033 | 118 | 033 | 033 | 1 | 0 | 0 | +| " | 034 | 034 | 034 | 012 | 0 | 1 | 1 | +| # | 035 | 102 | 035 | 035 | 1 | 0 | 0 | +| % | 037 | 113 | 037 | 037 | 1 | 0 | 0 | +| & | 038 | 111 | 038 | 038 | 1 | 0 | 0 | +| ' | 039 | 039 | 039 | 039 | 1 | 1 | 1 | +| ( | 040 | 116 | 040 | 040 | 1 | 0 | 0 | +| ) | 041 | 117 | 041 | 041 | 1 | 0 | 0 | +| * | 042 | 110 | 042 | 042 | 1 | 0 | 0 | +| + | 043 | 119 | 043 | 043 | 1 | 0 | 0 | +| , | 044 | 044 | 044 | 062 | 0 | 1 | 1 | +| - | 045 | 120 | 045 | 045 | 1 | 0 | 0 | +| . | 046 | 046 | 046 | 046 | 1 | 1 | 1 | +| / | 047 | 114 | 047 | 047 | 1 | 0 | 0 | +| 0 | 048 | 101 | 048 | 048 | 1 | 0 | 0 | +| 1 | 049 | 097 | 049 | 049 | 1 | 0 | 0 | +| 2 | 050 | 105 | 050 | 050 | 1 | 0 | 0 | +| 3 | 051 | 099 | 051 | 051 | 1 | 0 | 0 | +| 4 | 052 | 112 | 052 | 052 | 1 | 0 | 0 | +| 5 | 053 | 100 | 053 | 053 | 1 | 0 | 0 | +| 6 | 054 | 107 | 054 | 054 | 1 | 0 | 0 | +| 7 | 055 | 104 | 055 | 055 | 1 | 0 | 0 | +| 8 | 056 | 103 | 056 | 056 | 1 | 0 | 0 | +| 9 | 057 | 109 | 057 | 057 | 1 | 0 | 0 | +| : | 058 | 098 | 058 | 058 | 1 | 0 | 0 | +| ; | 059 | 106 | 059 | 059 | 1 | 0 | 0 | +| < | 060 | 122 | 060 | 060 | 1 | 0 | 0 | +| = | 061 | 121 | 061 | 061 | 1 | 0 | 0 | +| > | 062 | 044 | 062 | 062 | 1 | 0 | 0 | +| ? | 063 | 063 | 063 | 093 | 0 | 1 | 1 | +| A | 065 | 097 | 065 | 065 | 0 | 1 | 0 | +| B | 066 | 098 | 066 | 066 | 0 | 1 | 0 | +| C | 067 | 099 | 067 | 067 | 0 | 1 | 0 | +| D | 068 | 100 | 068 | 068 | 0 | 1 | 0 | +| E | 069 | 101 | 069 | 069 | 0 | 1 | 0 | +| F | 070 | 102 | 070 | 070 | 0 | 1 | 0 | +| G | 071 | 103 | 071 | 071 | 0 | 1 | 0 | +| H | 072 | 104 | 072 | 072 | 0 | 1 | 0 | +| I | 073 | 105 | 073 | 073 | 0 | 1 | 0 | +| J | 074 | 106 | 074 | 074 | 0 | 1 | 0 | +| K | 075 | 107 | 075 | 075 | 0 | 1 | 0 | +| L | 076 | 108 | 076 | 076 | 0 | 1 | 0 | +| M | 077 | 109 | 077 | 077 | 0 | 1 | 0 | +| N | 078 | 110 | 078 | 078 | 0 | 1 | 0 | +| O | 079 | 111 | 079 | 079 | 0 | 1 | 0 | +| P | 080 | 112 | 080 | 080 | 0 | 1 | 0 | +| Q | 081 | 113 | 081 | 081 | 0 | 1 | 0 | +| R | 082 | 114 | 082 | 082 | 0 | 1 | 0 | +| S | 083 | 115 | 083 | 083 | 0 | 1 | 0 | +| T | 084 | 116 | 084 | 084 | 0 | 1 | 0 | +| U | 085 | 117 | 085 | 085 | 0 | 1 | 0 | +| V | 086 | 118 | 086 | 086 | 0 | 1 | 0 | +| W | 087 | 119 | 087 | 087 | 0 | 1 | 0 | +| X | 088 | 120 | 088 | 088 | 0 | 1 | 0 | +| Y | 089 | 121 | 089 | 089 | 0 | 1 | 0 | +| Z | 090 | 122 | 090 | 090 | 0 | 1 | 0 | +| [ | 091 | 108 | 091 | 091 | 1 | 0 | 0 | +| ] | 093 | 063 | 093 | 093 | 1 | 0 | 0 | +| a | 097 | 097 | 065 | 049 | 0 | 0 | 1 | + +| Char | Value | Group 0
Fold
Table | Group 1
Fold
Table | Group 2
Fold Table | Group 2
Member | Group 1
Member | Group 0
Member | +|------|-------|--------------------------|--------------------------|-----------------------|-------------------|-------------------|-------------------| +| b | 098 | 098 | 066 | 058 | 0 | 0 | 1 | +| c | 099 | 099 | 067 | 051 | 0 | 0 | 1 | +| d | 100 | 100 | 068 | 053 | 0 | 0 | 1 | +| e | 101 | 101 | 069 | 048 | 0 | 0 | 1 | +| f | 102 | 102 | 070 | 035 | 0 | 0 | 1 | +| g | 103 | 103 | 071 | 056 | 0 | 0 | 1 | +| h | 104 | 104 | 072 | 055 | 0 | 0 | 1 | +| i | 105 | 105 | 073 | 050 | 0 | 0 | 1 | +| j | 106 | 106 | 074 | 059 | 0 | 0 | 1 | +| k | 107 | 107 | 075 | 054 | 0 | 0 | 1 | +| l | 108 | 108 | 076 | 091 | 0 | 0 | 1 | +| m | 109 | 109 | 077 | 057 | 0 | 0 | 1 | +| n | 110 | 110 | 078 | 042 | 0 | 0 | 1 | +| o | 111 | 111 | 079 | 038 | 0 | 0 | 1 | +| p | 112 | 112 | 080 | 052 | 0 | 0 | 1 | +| q | 113 | 113 | 081 | 037 | 0 | 0 | 1 | +| r | 114 | 114 | 082 | 047 | 0 | 0 | 1 | +| s | 115 | 115 | 083 | 156 | 0 | 0 | 1 | +| t | 116 | 116 | 084 | 040 | 0 | 0 | 1 | +| u | 117 | 117 | 085 | 041 | 0 | 0 | 1 | +| v | 118 | 118 | 086 | 033 | 0 | 0 | 1 | +| w | 119 | 119 | 087 | 043 | 0 | 0 | 1 | +| x | 120 | 120 | 088 | 045 | 0 | 0 | 1 | +| y | 121 | 121 | 089 | 061 | 0 | 0 | 1 | +| z | 122 | 122 | 090 | 060 | 0 | 0 | 1 | +| £ | 156 | 115 | 156 | 156 | 1 | 0 | 0 | + +NOTE: The characters "" are used to represent the "space" character. + +Characters with any other value in the range 0 to 255 are not a member of any group and therefore the fold table values will be equal to the character value in all cases. + +### Character Group ID >1 (decimal) + +No other Character Groups are defined and all other values are reserved. + +## B.5 Huffman Initializations + +### Huffman Initialization ID 0 (decimal) + +The Huffman Initialization is rendered in Character Set ID 2 (decimal) = Code Page 437. + +The Options value indicates that both character and control symbol updating are enabled. + +As described in subclause 6.7.1, the tables below include initialization values for *all* control symbols that *might* occur in conjunction with the use of this Huffman Initialization. However, initialization values for control symbols that *cannot* occur for a *particular* use of this Huffman Initialization are identified as part of the Huffman initialization process and are *not* added to the Huffman tree as described in subclause 6.7.2. + +The Character Group ID value is 1. + +#### Character Group Processing is disabled: + +The number of frequency initializations is 4. + +The initial frequencies are: + +**Table B.5: Character Group Processing is disabled: initial frequencies** + +| Symbol | Value | Frequency | +|--------------|-------|-----------| +| New UCS2 Row | 266 | 1 | +| Keyword | 258 | 1 | +| New 8bit | 257 | 1 | +| New 7bit | 256 | 1 | + +#### **Character Group Processing is enabled:** + +The number of frequency initializations is 6. + +The initial frequencies are: + +**Table B.6: Character Group Processing is enabled: initial frequencies** + +| Symbol | Value | Frequency | +|--------------|-------|-----------| +| New UCS2 Row | 266 | 1 | +| Change CG1 | 260 | 1 | +| Change CG0 | 259 | 1 | +| Keyword | 258 | 1 | +| New 8bit | 257 | 1 | +| New 7bit | 256 | 1 | + +### **Huffman Initialization ID 1 (decimal)** + +The Huffman Initialization is rendered in Character Set ID 2 (decimal) = Code Page 437. + +The Options value indicates that both character and control symbol updating are enabled. + +As described in subclause 6.7.1, the tables below include initialization values for *all* control symbols that *might* occur in conjunction with the use of this Huffman Initialization. However, initialization values for control symbols that *cannot* occur for a *particular* use of this Huffman Initialization are identified as part of the Huffman initialization process and are *not* added to the Huffman tree as described in subclause 6.7.2. + +The Character Group ID value is 1. + +#### **Character Group Processing is disabled:** + +The number of frequency initializations is 32. + +The initial frequencies are: + +**Table B.7: Character Group Processing is disabled: initial frequencies** + +| Symbol | Value | Frequency | +|--------------|-------|-----------| +| New UCS2 Row | 266 | 00001 | +| z | 122 | 00001 | +| Keyword | 258 | 00001 | +| q | 113 | 00001 | +| j | 106 | 00003 | +| x | 120 | 00003 | +| New 7bit | 256 | 00003 | +| New 8bit | 257 | 00003 | +| v | 118 | 00008 | +| w | 119 | 00010 | +| b | 098 | 00010 | +| y | 121 | 00011 | +| f | 102 | 00011 | +| u | 117 | 00012 | +| . | 046 | 00014 | +| m | 109 | 00016 | +| g | 103 | 00017 | +| k | 107 | 00017 | +| h | 104 | 00018 | +| d | 100 | 00024 | +| p | 112 | 00029 | +| c | 099 | 00029 | +| i | 105 | 00030 | +| r | 114 | 00038 | +| l | 108 | 00038 | +| s | 115 | 00040 | +| n | 110 | 00048 | +| t | 116 | 00050 | +| o | 111 | 00055 | +| | 032 | 00060 | +| a | 097 | 00066 | +| e | 101 | 00079 | + +NOTE: In the above table, the characters "" are used to represent the "space" character. + +#### **Character Group Processing is enabled:** + +The number of frequency initializations is 34. + +The initial frequencies are: + +**Table B.8: Character Group Processing is enabled: initial frequencies** + +| Symbol | Value | Frequency | +|--------------|-------|-----------| +| New UCS2 Row | 266 | 00001 | +| Change CG1 | 260 | 00001 | +| z | 122 | 00001 | +| Keyword | 258 | 00001 | +| q | 113 | 00002 | +| j | 106 | 00003 | +| x | 120 | 00003 | +| New 7bit | 256 | 00003 | +| New 8bit | 257 | 00003 | +| v | 118 | 00008 | +| w | 119 | 00010 | +| b | 098 | 00010 | +| Change CG0 | 259 | 00010 | +| y | 121 | 00011 | +| f | 102 | 00013 | +| u | 117 | 00013 | +| . | 046 | 00015 | +| m | 109 | 00017 | +| g | 103 | 00017 | +| k | 107 | 00019 | +| h | 104 | 00020 | +| d | 100 | 00026 | +| p | 112 | 00030 | +| c | 099 | 00030 | +| i | 105 | 00031 | +| r | 114 | 00040 | +| l | 108 | 00040 | +| s | 115 | 00045 | +| n | 110 | 00050 | +| t | 116 | 00053 | +| o | 111 | 00054 | +| | 032 | 00058 | +| a | 097 | 00064 | +| e | 101 | 00077 | + +Note in the above table, the characters "" are used to represent the "space" character. + +### **Huffman Initialization ID >1 (decimal)** + +No other Huffman Initializations are defined and all other values are reserved. + +# --- Annex C (normative): Italian Language parameters + +Annex under development + +# --- Annex D (normative): French Language parameters + +Annex under development + +# --- Annex E (normative): Spanish Language parameters + +Annex under development + +# --- Annex F (normative): Dutch Language parameters + +Annex under development + +# --- Annex G (normative): Swedish Language parameters + +Annex under development + +# --- Annex H (normative): Danish Language parameters + +Annex under development + +# --- Annex J (normative): Portuguese Language parameters + +Annex under development + +# --- Annex K (normative): Finnish Language parameters + +Annex under development + +# --- Annex L (normative): Norwegian Language parameters + +Annex under development + +# --- Annex M (normative): Greek Language parameters + +Annex under development + +# --- Annex N (normative): Turkish Language parameters + +Annex under development + +# --- Annex P (normative): Reserved + +Annex under development + +# --- Annex Q (normative): Reserved + +Annex under development + +# --- Annex R (normative): Default Parameters for Unspecified Language + +## R.1 Compression Language Context + +**CLC Value: 15 (decimal)** + +This specifies the following items as defaults: + +| | | +|-----------------------------------------|---------------------------------------------------------| +| 1) Language | Unspecified | +| 2) Character set
bitdefault alphabet | Character Set ID 1 (decimal) = 3GPP TS 23.038 [1] GSM 7 | +| 3) Punctuator ID | 0 (decimal) | +| 4) Keyword Dictionary ID | 0 (decimal) | +| 5) Character Group ID | 0 (decimal) | +| 6) Huffman Initialization ID | 0 (decimal) | + +## --- R.2 Punctuators + +**Punctuator ID 0 (decimal)** + +This punctuator ID has the special meaning that no punctuator is defined (or therefore enabled) and the value of bit 2 of octet 1 of the CH is always to be interpreted as zero. + +**Punctuator ID >0 (decimal)** + +No other punctuators are defined and all other values are reserved. + +## --- R.3 Keyword Dictionaries + +**Keyword Dictionary ID 0 (decimal)** + +This Keyword Dictionary ID has the special meaning that no Keyword Dictionary is defined (or therefore enabled) and the value of bit 1 of octet 1 of the CH is always to be interpreted as zero. + +**Keyword Dictionary ID >0 (decimal)** + +No other Keyword Dictionaries are defined and all other values are reserved. + +## --- R.4 Character Groups + +**Character Group ID 0 (decimal)** + +This Character Group ID has the special meaning that no Character Group is defined (or therefore enabled) and the value of bit 0 of octet 1 of the CH is always to be interpreted as zero. + +**Character Group ID >0 (decimal)** + +No other Character Groups are defined and all other values are reserved. + +## --- R.5 Huffman Initializations + +**Huffman Initialization ID 0 (decimal)** + +Only control symbols are included in this initialization. Its rendition is therefore independent of character set. + +The Options value indicates that both character and control symbol updating are enabled. + +As described in subclause 6.7.1, the tables below include initialization values for *all* control symbols that *might* occur in conjunction with the use of this Huffman Initialization. However, initialization values for control symbols that *cannot* occur for a *particular* use of this Huffman Initialization are identified as part of the Huffman initialization process and are *not* added to the Huffman tree as described in subclause 6.7.2. + +#### **Character Group Processing is always disabled:** + +The number of frequency initializations is 4. + +The initial frequencies are: + +**Table R.1: Character Group Processing is always disabled: initial frequencies** + +| Symbol | Value | Frequency | +|--------------|-------|-----------| +| New UCS2 Row | 266 | 1 | +| Keyword | 258 | 1 | +| New 8bit | 257 | 1 | +| New 7bit | 256 | 1 | + +#### **Character Group Processing can not be enabled therefore:** + +The number of frequency initializations is 0. + +### **Huffman Initialization ID >0 (decimal)** + +No other Huffman Initializations are defined and all other values are reserved. + +# Annex S (informative): Change history + +| TSG# | TDoc | VERS | NEW_VERS | CR | R
E
V | REL | CAT | WORKITEM | SUBJECT | +|------|----------|--------|----------|-----|-------------|--------|-----|----------|------------------------------------------------------------------------------| +| T#4 | | | 3.0.0 | New | | | | | Creation of 3GPP 23.042 out of GSM 03.42 v.7.1.0 | +| T#6 | TP-99237 | 3.0.0 | 3.1.0 | 001 | | R99 | F | TEI | Adaptations for UMTS | +| T#11 | - | 3.1.0 | 4.0.0 | - | | Rel-4 | | | Upgrade to Rel-4 | +| | | 4.0.0 | 4.0.1 | | | Rel-4 | | | 2001-10: Replacement of erroneous R99 test vector file by correct Rel-4 one. | +| T#16 | - | 4.0.1 | 5.0.0 | - | | Rel-5 | | | Upgrade to Rel-5 | +| T#26 | - | 5.0.0 | 6.0.0 | - | | Rel-6 | | | Upgrade to Rel-6 | +| | | 6.0.0 | 7.0.0 | | | Rel-7 | | | Upgrade to Rel-7 | +| | | 7.0.0 | 8.0.0 | | | Rel-8 | | | Upgrade to Rel-8 | +| | | 8.0.0 | 9.0.0 | | | Rel-9 | | | Upgrade to Rel-9 | +| | | 9.0.0 | 10.0.0 | | | Rel-10 | | | Upgrade to Rel-10 | +| | | 10.0.0 | 11.0.0 | | | Rel-11 | | | Upgrade to Rel-11 | +| | | 11.0.0 | 12.0.0 | | | Rel-12 | | | Upgrade to Rel-12 | +| | | 12.0.0 | 13.0.0 | | | Rel-13 | | | Upgrade to Rel-13 | + +| Change history | | | | | | | | +|----------------|---------|------|----|-----|-----|--------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2017-03 | CT-75 | - | - | - | - | Update to Rel-14 version (MCC) | 14.0.0 | +| 2018-06 | SA-80 | - | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2020-07 | SA-88e | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23072/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23072/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..482836912245cf3f42965a672b37535a5e933050 --- /dev/null +++ b/marked/Rel-16/23_series/23072/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be33b849973a8d2e0ce94457b4eb6c4877e90e06284491cc5c0762acef9cb4b2 +size 139723 diff --git a/marked/Rel-16/23_series/23072/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23072/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa42606a2938029ff428b5afd3c31df474f112c9 --- /dev/null +++ b/marked/Rel-16/23_series/23072/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f9d6d1ca9434850483836336b589426fa859b321ad664b547b6accfbd86cf60 +size 65499 diff --git a/marked/Rel-16/23_series/23072/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/Rel-16/23_series/23072/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f4291886590521225b2ae9ccd78cec81bdedcf6 --- /dev/null +++ b/marked/Rel-16/23_series/23072/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:306ba63673d72995214c240dde2af91cb7cf2b0b107d2cdce120345dba7466c5 +size 42401 diff --git a/marked/Rel-16/23_series/23072/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23072/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d9ba41eb80f469c2390348ed86f04f5a15038c8 --- /dev/null +++ b/marked/Rel-16/23_series/23072/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:07a25b235527277f1f1d3d30f278960dfb632011500564dad6a14511c3b5873c +size 68985 diff --git a/marked/Rel-16/23_series/23072/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23072/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f8acb21f78fa24dd3a9f10989bb4153fd8730a81 --- /dev/null +++ b/marked/Rel-16/23_series/23072/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03357ae50cf4eec2de9ca6eaffeefe4acc32c0afd8bc85901b091fce6a812b28 +size 60821 diff --git a/marked/Rel-16/23_series/23072/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23072/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..06e28468595062d61494839580b93c2195741758 --- /dev/null +++ b/marked/Rel-16/23_series/23072/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ccc34dad6eb4bddebf928b6f17fa4e52066e5a7172138ef146a2c42de3b986f +size 65217 diff --git a/marked/Rel-16/23_series/23072/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23072/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..842219f6da12d5885a35990e5d4fa25c8d00adc8 --- /dev/null +++ b/marked/Rel-16/23_series/23072/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:00e68a1d6490eaf27351a2cd22490f8472ab148ec164e111234c417f8bf038e8 +size 65154 diff --git a/marked/Rel-16/23_series/23072/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23072/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2018bd2a67b0c38e8736b51c11efb2213b7fc87 --- /dev/null +++ b/marked/Rel-16/23_series/23072/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e9282b561140a39498c06c63bc42463697c93d8c065db2564ee9bdd9e8276ee1 +size 104117 diff --git a/marked/Rel-16/23_series/23072/f6d72d7c790e7f585532140f3971639a_img.jpg b/marked/Rel-16/23_series/23072/f6d72d7c790e7f585532140f3971639a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c7a7bd9976c006acd74bdd361b8bbf4fdd68ec0 --- /dev/null +++ b/marked/Rel-16/23_series/23072/f6d72d7c790e7f585532140f3971639a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e25b713b4cc308a8eea8bb1de3f771b01e0f196d4cf1b8489f1b0c1ef2fc9420 +size 104239 diff --git a/marked/Rel-16/23_series/23072/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23072/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a37ef5925517d9bbd2ae7d6e220b30ba39b00bcd --- /dev/null +++ b/marked/Rel-16/23_series/23072/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34b03420d8fe71c61651d260500f4b91932177b0bb5b1a5b92f8b1725583bb8c +size 67696 diff --git a/marked/Rel-16/23_series/23072/raw.md b/marked/Rel-16/23_series/23072/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..1140ed1c15affaef7d67684c57cb1a34d27ecffd --- /dev/null +++ b/marked/Rel-16/23_series/23072/raw.md @@ -0,0 +1,608 @@ + + + + + + +# 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?'. If No, Result := Fail. If Yes, 'CD provisioned?'. If No, Result := Fail. If Yes, 'Number of max diversions reached?'. If Yes, Result := Fail. If No, 'BAOC A&O'. If Yes, set negative resp: call barred. If No, GAMEL_Check_CD_Interaction is called. Then 'Result = Pass?'. If No, 'DTN valid?'. If No, Result := Fail. If Yes, 'DTN is a special service code?'. If Yes, set negative resp: DTN is a special service code. If No, 'DTN is own basic MSISDN'. If Yes, set negative resp: DTN is own number. If No, Result := Fail. If 'Result = Pass?' is Yes 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 --> R2[Result := Fail] + R2 --> E2(( )) + D2 -- Yes --> D3{CD provisioned?} + D3 -- No --> R2 + D3 -- Yes --> D4{Number of max diversions reached?} + D4 -- Yes --> R2 + D4 -- No --> D5{BAOC A&O} + D5 -- Yes --> S2[set negative resp: call barred] + D5 -- No --> G2[GAMEL_Check_CD_Interaction] + G2 --> D6{Result = Pass?} + D6 -- No --> D7{DTN valid?} + D7 -- No --> R2 + D7 -- Yes --> D8{DTN is a special service code?} + D8 -- Yes --> S3[set negative resp: DTN is a special service code] + D8 -- No --> D9{DTN is own basic MSISDN} + D9 -- Yes --> S4[set negative resp: DTN is own number] + D9 -- No --> R2 + S2 --> Join1(( )) + S3 --> Join1 + S4 --> Join1 + Join1 --> R2 + D6 -- Yes --> C2((2)) + S2 --> C2 + S3 --> C2 + S4 --> 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?'. If No, Result := Fail. If Yes, 'CD provisioned?'. If No, Result := Fail. If Yes, 'Number of max diversions reached?'. If Yes, Result := Fail. If No, 'BAOC A&O'. If Yes, set negative resp: call barred. If No, GAMEL\_Check\_CD\_Interaction is called. Then 'Result = Pass?'. If No, 'DTN valid?'. If No, Result := Fail. If Yes, 'DTN is a special service code?'. If Yes, set negative resp: DTN is a special service code. If No, 'DTN is own basic MSISDN'. If Yes, set negative resp: DTN is own number. If No, Result := Fail. If 'Result = Pass?' is Yes 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 'Yes', it goes to 'Result:= Pass'. If 'No', it goes to 'Result:= Fail'. 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 -- Yes --> Pass[Result:= Pass]; Decision -- No --> Fail[Result:= Fail]; Pass --> Merge(( )); Fail --> 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 'Yes', it goes to 'Result:= Pass'. If 'No', it goes to 'Result:= Fail'. 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 '(Not Provisioned, Not Applicable, Not Active, Not Induced)'. The right state contains '(Provisioned, Not Applicable, Active and Operative, Not Induced)'. A top arrow labeled 'Provision' points from the left state to the right state. A bottom 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 '(Not Provisioned, Not Applicable, Not Active, Not Induced)'. The right state contains '(Provisioned, Not Applicable, Active and Operative, Not Induced)'. A top arrow labeled 'Provision' points from the left state to the right state. A bottom arrow labeled 'Withdrawal' points from the right state to the left state. + +Figure 6.2: Procedure CD\_Reject + +![SDL Diagram for Procedure CD_Failure](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([ ]) --> Decision{CD in +progress} + Decision -- No --> End((X)) + Decision -- Yes --> Task[Set negative +response: +forwarding failure] + Task --> Signal1{{CD Request +negative +response}} + Signal1 --> Signal2{{Release +transaction}} + Signal2 --> End + +``` + +SDL Diagram for Procedure CD\_Failure + +**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). Two callout boxes provide additional context: one on the top left states 'Procedure in the MSC to handle the interaction scenario with UUS', and one on the top right states 'Signals to/from the left are to/from the BSS'. + +Flowchart for Procedure CD\_UUS\_Interaction + +Figure 6.4: Procedure CD\_UUS\_Interaction + +![Flowchart for Procedure CD_Success](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +**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 + +``` +graph TD; Start([ ]) --> Decision{CD in progress}; Decision -- No --> End((X)); 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 an oval connector symbol, leading to a decision diamond labeled 'CD in progress'. If the answer is 'No', the flow proceeds to a circular connector symbol with an 'X'. If the answer is 'Yes', the flow proceeds to a rectangular process block labeled 'CD\_Notify\_SS\_Invocation'. This is followed by a pentagonal decision symbol labeled 'CD Request ack', which then leads to another pentagonal decision symbol labeled 'Release transaction'. Both decision symbols lead to the same circular connector symbol with an 'X' at the bottom. + +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. The process starts with a decision 'neg. resp. = CD?'. If 'No', it goes to 'Result := Abort'. If 'Yes', it goes to 'CAMEL_CHECK_SII2_CDTI' (refer to TS 23.078). From there, it checks 'Result = Pass?'. If 'No', it goes to 'Result := Fail'. If 'Yes', it checks 'CD provisioned?'. If 'No', it goes to 'Result := Fail'. If 'Yes', it checks 'Number of mac diversions reached?'. If 'Yes', it goes to 'Result := Fail'. If 'No', it checks 'BAOC A&O'. If 'Yes', it goes to 'set negative resp: call barred'. If 'No', it goes to 'CAMEL_Check_CD_Interaction'. From 'CAMEL_Check_CD_Interaction', it checks 'Result = Pass?'. If 'No', it goes to 'Result := Fail'. If 'Yes', it goes to connector '2'. If 'No' from 'CD provisioned?', it goes to 'set negative resp: forwarding violation'. If 'No' from 'Number of mac diversions reached?', it goes to 'set negative resp: service not subscribed'. Both lead to 'Result := Fail'. From connector '2', it checks 'DTN valid?'. If 'No', it goes to 'set negative resp: number invalid'. If 'Yes', it checks 'DTN is a special service code?'. If 'Yes', it goes to 'set negative resp: DTN is a special service code'. If 'No', it checks 'DTN is own basic MSISDN'. If 'Yes', it goes to 'set negative resp: DTN is own number'. If 'No', it goes to connector '1'. All three 'set negative resp' boxes lead to 'Result := Fail'.](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] + neg_resp_CD -- Yes --> CAMEL_CHECK_SII2_CDTI[CAMEL_CHECK_SII2_CDTI] + CAMEL_CHECK_SII2_CDTI --> CAMEL_CHECK_SII2_CDTI_note[See TS 23.078] + CAMEL_CHECK_SII2_CDTI --> Result_Pass_1{Result = Pass?} + Result_Pass_1 -- No --> Fail_1[Result := Fail] + Result_Pass_1 -- Yes --> CD_provisioned{CD provisioned?} + CD_provisioned -- No --> Fail_1 + CD_provisioned -- Yes --> Number_diversions{Number of mac diversions reached?} + Number_diversions -- Yes --> Fail_1 + Number_diversions -- No --> BAOC_AO{BAOC A&O} + BAOC_AO -- Yes --> set_resp_barred[set negative resp: call barred] + BAOC_AO -- No --> CAMEL_Check_CD_Interaction[CAMEL_Check_CD_Interaction] + CAMEL_Check_CD_Interaction --> Result_Pass_2{Result = Pass?} + Result_Pass_2 -- No --> Fail_2[Result := Fail] + Result_Pass_2 -- Yes --> Connector_2((2)) + Connector_2 --> DTN_valid{DTN valid?} + DTN_valid -- No --> set_resp_invalid[set negative resp: number invalid] + DTN_valid -- Yes --> DTN_special{DTN is a special service code?} + DTN_special -- Yes --> set_resp_special[set negative resp: DTN is a special service code] + DTN_special -- No --> DTN_own{DTN is own basic MSISDN} + DTN_own -- Yes --> set_resp_own[set negative resp: DTN is own number] + DTN_own -- No --> Connector_1((1)) + set_resp_barred --> Fail_2 + set_resp_invalid --> Fail_2 + set_resp_special --> Fail_2 + set_resp_own --> Fail_2 + set_resp_barred --> Fail_1 + set_resp_forwarding[set negative resp: forwarding violation] --> Fail_1 + set_resp_subscribed[set negative resp: service not subscribed] --> Fail_1 + +``` + +Flowchart for Procedure CD\_Authorization. The process starts with a decision 'neg. resp. = CD?'. If 'No', it goes to 'Result := Abort'. If 'Yes', it goes to 'CAMEL\_CHECK\_SII2\_CDTI' (refer to TS 23.078). From there, it checks 'Result = Pass?'. If 'No', it goes to 'Result := Fail'. If 'Yes', it checks 'CD provisioned?'. If 'No', it goes to 'Result := Fail'. If 'Yes', it checks 'Number of mac diversions reached?'. If 'Yes', it goes to 'Result := Fail'. If 'No', it checks 'BAOC A&O'. If 'Yes', it goes to 'set negative resp: call barred'. If 'No', it goes to 'CAMEL\_Check\_CD\_Interaction'. From 'CAMEL\_Check\_CD\_Interaction', it checks 'Result = Pass?'. If 'No', it goes to 'Result := Fail'. If 'Yes', it goes to connector '2'. If 'No' from 'CD provisioned?', it goes to 'set negative resp: forwarding violation'. If 'No' from 'Number of mac diversions reached?', it goes to 'set negative resp: service not subscribed'. Both lead to 'Result := Fail'. From connector '2', it checks 'DTN valid?'. If 'No', it goes to 'set negative resp: number invalid'. If 'Yes', it checks 'DTN is a special service code?'. If 'Yes', it goes to 'set negative resp: DTN is a special service code'. If 'No', it checks 'DTN is own basic MSISDN'. If 'Yes', it goes to 'set negative resp: DTN is own number'. If 'No', it goes to connector '1'. All three 'set negative resp' boxes lead to 'Result := Fail'. + +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-CS1) 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): + +| 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 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 + +| TSG CN# | Spec | CR | | New Version | Subject/Comment | +|----------|-----------|-------|---------|-------------|----------------------------------------------------| +| Apr 1999 | GSM 03.72 | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.072 | | | 3.0.0 | Approved at CN#03 | +| CN#05 | 23.072 | 001 | | 3.1.0 | Approved at CN#05 | +| CN#05 | 23.072 | 003 | | 3.1.0 | Approved at CN#05 | +| CN#06 | 23.072 | 002r1 | | 3.2.0 | Approved at CN#06 | +| CN#09 | 23.072 | 004 | | 3.3.0 | Transfer of Procedure Check_CD_SII2 to TS 23.078 | +| CN#09 | 23.072 | 005 | | 3.3.0 | Handling of the Call Diversion Treatment Indicator | +| CN#11 | 23.072 | | Rel-4 | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 23.072 | | Rel-4 | 4.0.1 | References updated | +| CN#16 | 23.072 | | Rel-5 | 5.0.0 | Release 5 after CN#16 | +| CN#26 | 23.072 | | Rel-6 | 6.0.0 | Release 6 after CN#26 | +| CT#36 | 23.072 | | Rel-7 | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.072 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.072 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.072 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 23.072 | - | Rel-11 | 11.0.0 | Update to Rel-11 version (MCC) | +| 2014-09 | 23.072 | - | Rel-12 | 12.0.0 | Update to Rel-12 version (MCC) | +| 2015-12 | 23.072 | - | Rel-13 | 13.0.0 | Update to Rel-13 version (MCC) | +| 2017-03 | 23.072 | - | Rel-14 | 14.0.0 | Update to Rel-14 version (MCC) | +| 2018-06 | 23.072 | - | Rel-15 | 15.0.0 | Update to Rel-15 version (MCC) | +| 2020-07 | 23.072 | - | Rel-16 | 16.0.0 | Update to Rel-16 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23081/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23081/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..634c9141e7481a39d3624ebed999e23dac39a092 --- /dev/null +++ b/marked/Rel-16/23_series/23081/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5df3ecec065c0cd964ca54ebf2cdd59db92d413cfcbeecfb5c2cfdcd48fe9725 +size 103950 diff --git a/marked/Rel-16/23_series/23081/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23081/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bb48438e73ec1dcfd63c6e77360eac59e7d43bf --- /dev/null +++ b/marked/Rel-16/23_series/23081/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9e30c723305040ba29f588a80643a7328587d5f909fd6a487b0f157c03638c0 +size 104654 diff --git a/marked/Rel-16/23_series/23081/08441fa90c5fd11994626f662ac13f19_img.jpg b/marked/Rel-16/23_series/23081/08441fa90c5fd11994626f662ac13f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a32cb9982eb8305efc1f7a4772facb6af047e65 --- /dev/null +++ b/marked/Rel-16/23_series/23081/08441fa90c5fd11994626f662ac13f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1876ca6ee62e407c6bdb59d415d1d990cba7853ab65c66318f76275d87c9d896 +size 11265 diff --git a/marked/Rel-16/23_series/23081/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23081/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ebfa7f1ba9c6d3d2976e6aeac351aca5c22211a --- /dev/null +++ b/marked/Rel-16/23_series/23081/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e53aa332e7f0cbdc91bfc15e18e182b58d829f2e23dfe4f43a0f8c0f78bd5b9 +size 130123 diff --git a/marked/Rel-16/23_series/23081/1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg b/marked/Rel-16/23_series/23081/1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea52056f94d04c576056a39f5fc77af56125b13f --- /dev/null +++ b/marked/Rel-16/23_series/23081/1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02fcc9fe1a22b5ec833d152d006169c48c88fb7461563d6cbbbeabea997ef6ba +size 23302 diff --git a/marked/Rel-16/23_series/23081/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23081/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b7debd7a3426eec61a6989b6897a87efc89a7971 --- /dev/null +++ b/marked/Rel-16/23_series/23081/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f8285a7e2e128d8dd9c04d1eb19eee1999615ce4ecc8f90c90a8c2912350845 +size 97042 diff --git a/marked/Rel-16/23_series/23081/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23081/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e53ed99e36f6cf9892f0363555fa03fe09408055 --- /dev/null +++ b/marked/Rel-16/23_series/23081/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fda591789660db55a6114b61cefcc91b571028e43c20fc7a01ea6be2fe07f752 +size 33166 diff --git a/marked/Rel-16/23_series/23081/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23081/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ad2c451fb71c0e286766fcb6994bb7f7a8faca9 --- /dev/null +++ b/marked/Rel-16/23_series/23081/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:893f0bc049c25926b03db56e9f60c446ffb0a804ddbe6dc8ac5385a348765012 +size 31221 diff --git a/marked/Rel-16/23_series/23081/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/Rel-16/23_series/23081/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a8be6167f99b885612f92398b15ed058da01f490 --- /dev/null +++ b/marked/Rel-16/23_series/23081/392a79ccd95e682ccd08f35ab2e64144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e0d7681b26f09d13a57c7816c02005837069af62ad2a4d1b3df4cf67e1db19d +size 33791 diff --git a/marked/Rel-16/23_series/23081/40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg b/marked/Rel-16/23_series/23081/40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26893a5dbda4da211b0f5968798fe78af21b4a24 --- /dev/null +++ b/marked/Rel-16/23_series/23081/40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fb73d4099bac7e1cbcc4c050857a31874e712b09d148200271fcf9dac962bee +size 32416 diff --git a/marked/Rel-16/23_series/23081/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg b/marked/Rel-16/23_series/23081/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07c0075b0518ac410818e581c2fff3ea71ebfd40 --- /dev/null +++ b/marked/Rel-16/23_series/23081/4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:573b83f36412ff723562c8d0178aa845d4dfa70730892975732a174bee0d0bab +size 23319 diff --git a/marked/Rel-16/23_series/23081/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-16/23_series/23081/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b4048a527752b87b2df7398739d783e2252e9c9 --- /dev/null +++ b/marked/Rel-16/23_series/23081/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b62dbbc6a09564024462fcdc30bde583f54b769627e6027ac50c1bed2e3d89c +size 40585 diff --git a/marked/Rel-16/23_series/23081/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23081/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7d4a0bba3681569ff7ac38efca84ee6fedb7849 --- /dev/null +++ b/marked/Rel-16/23_series/23081/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29f0fddadc9f88ac1898b90726728b514634c72d91fb60a53b9368fa885e0aea +size 106214 diff --git a/marked/Rel-16/23_series/23081/5fbb4f0de01736f1293333e599410c99_img.jpg b/marked/Rel-16/23_series/23081/5fbb4f0de01736f1293333e599410c99_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28e36a32e959196ab4cd628161cd4bafc1f466ea --- /dev/null +++ b/marked/Rel-16/23_series/23081/5fbb4f0de01736f1293333e599410c99_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa54e526a1820a05141d0d3c614b697352eb975c2ad9ab72fe812e66aa3e26bf +size 6281 diff --git a/marked/Rel-16/23_series/23081/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/23_series/23081/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39ea4902ab20ee2d1a7ea5bcf92f71ad76219a6a --- /dev/null +++ b/marked/Rel-16/23_series/23081/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5ac25aca8165a7555316950357ac57303b946ec0ad93e4b209dd4c7bc1dd449 +size 83292 diff --git a/marked/Rel-16/23_series/23081/6a5c8326029e6290e69a5f43d6ed4548_img.jpg b/marked/Rel-16/23_series/23081/6a5c8326029e6290e69a5f43d6ed4548_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab1dd1180532ec168ff2c6ee8028880b6301b26d --- /dev/null +++ b/marked/Rel-16/23_series/23081/6a5c8326029e6290e69a5f43d6ed4548_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:191ead4c57ecd78cd05ef70ba4f3e7298d9f75516157e2be7cca4bb84316b513 +size 23904 diff --git a/marked/Rel-16/23_series/23081/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/Rel-16/23_series/23081/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..86c17523314151d24c847c9ed6f3210cc8e1f565 --- /dev/null +++ b/marked/Rel-16/23_series/23081/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db5df34c495d5ce75d3be5ec987624b93d6be0030aa541c7b081626f26fb01d1 +size 6360 diff --git a/marked/Rel-16/23_series/23081/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23081/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee45cfd9452277b641f8cf4fc1af6a03e3102ce7 --- /dev/null +++ b/marked/Rel-16/23_series/23081/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:000978e7e2163dd8f0c8d3daa917a3f6fb02feb3c63cd8e0683dd044f8339659 +size 82319 diff --git a/marked/Rel-16/23_series/23081/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23081/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..056fe757058def023a4420a24a372bba8e5149aa --- /dev/null +++ b/marked/Rel-16/23_series/23081/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85955ba846c9c490177115f4b5bac4fcf7d06c93635dd0f6b727ecfe7536eb1f +size 65264 diff --git a/marked/Rel-16/23_series/23081/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23081/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ad2c451fb71c0e286766fcb6994bb7f7a8faca9 --- /dev/null +++ b/marked/Rel-16/23_series/23081/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:893f0bc049c25926b03db56e9f60c446ffb0a804ddbe6dc8ac5385a348765012 +size 31221 diff --git a/marked/Rel-16/23_series/23081/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23081/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aaff287f1cb6a15fe563f5730c9a7e16436d716f --- /dev/null +++ b/marked/Rel-16/23_series/23081/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a65ae381460d30de1b48cfd3c419a77a34dca8b803298ca909b850302c56713 +size 39867 diff --git a/marked/Rel-16/23_series/23081/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23081/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..44ae9e6121cc4811d19d9bd3dd6f49158a653257 --- /dev/null +++ b/marked/Rel-16/23_series/23081/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b0921d702e235aac2abc460af9121ad55281fc960175816b7b271d18ac88317 +size 53424 diff --git a/marked/Rel-16/23_series/23081/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23081/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbc71bd2b19a02b494c3a9e99872b27dc8a8dd58 --- /dev/null +++ b/marked/Rel-16/23_series/23081/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:400d95995bd722b2237c200bd9145d9aee046e08ed9037ffc8ac82a3591264d2 +size 67355 diff --git a/marked/Rel-16/23_series/23081/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23081/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f0024ad40275102b04ab199fd5f407dd3424849 --- /dev/null +++ b/marked/Rel-16/23_series/23081/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:09a59c4cb69cc8bb64d4674eb541f48495487f3ea0231aa651153701f804565a +size 131995 diff --git a/marked/Rel-16/23_series/23081/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23081/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..71fb21e43d84ddf8cce8098a66ed8c1e3cf02820 --- /dev/null +++ b/marked/Rel-16/23_series/23081/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:330e40543cbdbc198d3f8c7108f244d576fdebbd313697e2161acbd3d37e10e2 +size 102839 diff --git a/marked/Rel-16/23_series/23081/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23081/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..069e67d44392c0fa49e6dafe6ee1e27e66d13748 --- /dev/null +++ b/marked/Rel-16/23_series/23081/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebfa7333aff1c6f0494a9b161cc1be3e820dc08f3cdacbe545364f9725ededac +size 86264 diff --git a/marked/Rel-16/23_series/23081/ddc7460821484f1ae2835c67955c554c_img.jpg b/marked/Rel-16/23_series/23081/ddc7460821484f1ae2835c67955c554c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cc3ce7063997f58513a7b4205e4d8972da3c151 --- /dev/null +++ b/marked/Rel-16/23_series/23081/ddc7460821484f1ae2835c67955c554c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f328f8a1230073ff8cd323dec2a5748a67f6a9dbc8441f2bc673dd10b4ed5841 +size 33907 diff --git a/marked/Rel-16/23_series/23081/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/23_series/23081/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3639a57830f73dec6a6cf825bff68fbf0fd716a1 --- /dev/null +++ b/marked/Rel-16/23_series/23081/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ffb4a2bee1a3fac5898204fd4fc569f2d62ec4719ebde1aac16f5ea3638963c +size 131667 diff --git a/marked/Rel-16/23_series/23081/e159e9f78612406820a4d40e26e01413_img.jpg b/marked/Rel-16/23_series/23081/e159e9f78612406820a4d40e26e01413_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2010b37a7a92234bb2b7f6ae70582820094efa71 --- /dev/null +++ b/marked/Rel-16/23_series/23081/e159e9f78612406820a4d40e26e01413_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a9df58f4ee2635ab4ec20d504ffc86fe7519f4e380d4843a9a5398da297cdb52 +size 1718 diff --git a/marked/Rel-16/23_series/23081/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23081/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b74e49255e58d213c11ec5d2600e17c080c69c6 --- /dev/null +++ b/marked/Rel-16/23_series/23081/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1329571884ba937a81473a3b43ed0c5d12668d8bc64f0e6e0d5f97eff7846816 +size 23097 diff --git a/marked/Rel-16/23_series/23081/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23081/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6299561d96ebf2e0951e49e80c486f2bf690f59a --- /dev/null +++ b/marked/Rel-16/23_series/23081/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70a5af1b3ca20b09df3d24dc54eceb9c7c0d7ce81d987cb91c0ecbb96603822a +size 147099 diff --git a/marked/Rel-16/23_series/23081/ead623e6a8ec701df64567695a57d01c_img.jpg b/marked/Rel-16/23_series/23081/ead623e6a8ec701df64567695a57d01c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..581629ee79935f6864d192cbb9c1ff186d039368 --- /dev/null +++ b/marked/Rel-16/23_series/23081/ead623e6a8ec701df64567695a57d01c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b877d1c04b097d85a8e9a669645373170aef9089f79d137b70a8b204984bd65 +size 31383 diff --git a/marked/Rel-16/23_series/23081/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23081/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2fe53766b46d768a8c309029dd11c3637798f37 --- /dev/null +++ b/marked/Rel-16/23_series/23081/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfe3d8d6bc63d4475a5fa2b3f3f1d58e55c56a2fc6c1a6b4bd57c32b497c2410 +size 111362 diff --git a/marked/Rel-16/23_series/23081/eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg b/marked/Rel-16/23_series/23081/eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68b5e1269457a7ca0095064e5fc986a173279aba --- /dev/null +++ b/marked/Rel-16/23_series/23081/eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0eb6e668d1dd3016f31bb83c258ca0f0e27eab63348bbb1aa593820d8e73c9a +size 1692 diff --git a/marked/Rel-16/23_series/23081/raw.md b/marked/Rel-16/23_series/23081/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..2397bfbefc4daa35a93a0e9b7bbdceb355c561ed --- /dev/null +++ b/marked/Rel-16/23_series/23081/raw.md @@ -0,0 +1,1416 @@ + + + + + + +# 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' follows. If 'no', it goes to 'set override category = no'. If 'yes', a decision 'override category' follows. If 'no', it goes to 'set override category = no'. If 'yes', it goes to 'set override category = yes'. All three 'set' blocks 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_Country{called subscriber in HPLMN country}; HPLMN_Country -- no --> SetOverrideNo[set override category = no]; HPLMN_Country -- yes --> Override_Cat{override category}; Override_Cat -- no --> SetOverrideNo; Override_Cat -- 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' follows. If 'no', it goes to 'set override category = no'. If 'yes', a decision 'override category' follows. If 'no', it goes to 'set override category = no'. If 'yes', it goes to 'set override category = yes'. All three 'set' blocks 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[set PI = number not available] + CLIP_Provisioned -- Yes --> CLI_available{CLI available} + CLI_available -- No --> End2[set PI = number not available] + 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_Available + Override_Category1 -- No --> Additional_CLI_Available2{additional CLI available} + Additional_CLI_Available2 -- Yes --> CLI_Override[CLI in case of override category] + Additional_CLI_Available2 -- No --> End3[pass CLI] + Additional_CLI_Available -- Yes --> Pass_Additional_CLI1[pass additional CLI] + Additional_CLI_Available -- No --> PI_Restricted_Net{PI = presentation restricted by network?} + PI_Restricted_Net -- Yes --> Override_Category2{override category} + PI_Restricted_Net -- No --> End4[Set PI = number not available] + Override_Category2 -- Yes --> Set_PI_Restricted[Set PI = presentation restricted] + Override_Category2 -- No --> End4 + Set_PI_Restricted --> Pass_CLI1[pass CLI] + Pass_Additional_CLI1 --> Continue[Continue Call Handling] + End3 --> Continue + End4 --> Continue + Pass_CLI1 --> Continue + Pass_Additional_CLI2[pass additional CLI] --> Continue + End2 --> Continue + End1 --> 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 -- No --> Q3{CoNC = interworking with other services?}; Q2 -- Yes --> SetCoNC4[Set CoNC = Reject by user]; Q3 -- Yes --> SetCoNC3[Set CoNC = Interworking with other services]; Q3 -- No --> Q4{CoNC = Coin line/payphone?}; Q4 -- Yes --> SetCoNC2[Set CoNC = Coin line/payphone]; Q4 -- No --> Q5{CoNC = Unavailable?}; Q5 -- Yes --> SetCoNC1[Set CoNC = Unavailable]; Q5 -- No --> End; SetCoNC1 --> End; SetCoNC2 --> End; SetCoNC3 --> End; SetCoNC4 --> 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 'No' at this point, it goes to the end connector. If 'Yes', it goes to the process 'Set CoNC = Reject by user'. 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 goes to the end connector. All four process boxes ('Set CoNC = Unavailable', 'Set CoNC = Coin line/payphone', 'Set CoNC = Interworking with other services', and 'Set CoNC = Reject by user') lead to a common horizontal line that terminates at the end connector. A note box in the top right corner contains the text 'CoNC : Cause of no CLI'. + +Flowchart for Procedure Cause\_of\_no\_CLI + +Figure 1.4: Procedure Cause\_of\_no\_CLI + +#### Procedure CLI\_MT\_GMSC + +1(1) + +![Note icon](e159e9f78612406820a4d40e26e01413_img.jpg) + +A small icon representing a note or a piece of paper with a folded top-right corner. + +Note icon + +![Flowchart showing a process step: Add Calling Party Number and Generic Number to the SRI](08441fa90c5fd11994626f662ac13f19_img.jpg) + +``` + +graph TD + Start([ ]) --> Process[ ] + Process --> End((X)) + Process --- Note[Add Calling Party Number and Generic Number to the SRI] + +``` + +A flowchart consisting of three vertically aligned symbols: a start symbol (a rounded rectangle with vertical lines on the sides), a process symbol (a rectangle), and an end symbol (a circle with an 'X'). The start symbol is connected to the process symbol by a vertical line. The process symbol is connected to the end symbol by a vertical line. To the right of the process symbol, there is a text box containing the text "Add Calling Party Number and Generic Number to the SRI", which is connected to the process symbol by a horizontal line. + +Flowchart showing a process step: Add Calling Party Number and Generic Number to the SRI + +**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 Procedure CLI_HLR_Set_CLI](ddc7460821484f1ae2835c67955c554c_img.jpg) + +``` + +graph TD + Start([ ]) --> D1{Subscriber roaming +outside home +country} + D1 -- No --> End((X)) + D1 -- Yes --> D2{Sending of CLI +information allowed +to destination NW} + D2 -- No --> End + D2 -- Yes --> D3{CLI information +received from GMSC} + 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 to a Provide Roaming Number message. It begins with a start symbol (a rounded rectangle with a vertical line) leading to the first decision diamond: "Subscriber roaming outside home country". If the answer is "No", the flow proceeds to an end symbol (a circle with an "X"). If "Yes", it moves to the second decision: "Sending of CLI information allowed to destination NW". A "No" here also leads to the end symbol. A "Yes" leads to the third decision: "CLI information received from GMSC". Again, a "No" leads to the end symbol. If "Yes", the process moves to a task box: "Add Calling Party Number and Generic Number to the PRN", which then concludes at the end symbol. + +Flowchart for Procedure CLI\_HLR\_Set\_CLI + +**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 the parameter **(SI+PI+CoNC+LI+aSI+aPI+aLI)**. +- MSCb** sends an **info req** message to **VLRb** (labeled **MAF 001**). +- VLRb** sends an **info ack** message to **MSCb** (labeled **MAF002**). +- MSCb** sends a **set-up** message to **MSb** containing the parameter **(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 the parameter **(SI+PI+CoNC+LI+aSI+aPI+aLI)**. +- GMSC** sends an **SRI** message to **HLRb**. +- HLRb** sends a response to **GMSC** containing the parameter **(SI+PI+LI+aSI+aPI+aLI)**. +- GMSC** sends a **PRN** message to **VLRb**. +- VLRb** sends a response to **HLRb** containing the parameter **(SI+PI+LI+aSI+aPI+aLI)**. +- HLRb** sends a **PRN ack** message to **VLRb**. +- VLRb** sends an **SRI ack** message to **GMSC**. +- GMSC** sends a **set-up** message to **MSCb** containing the parameter **(SI+PI+CoNC+LI+aSI+aPI+aLI)**. +- MSCb** sends an **info req** message to **VLRb** (labeled **MAF 001**). +- VLRb** sends an **info ack** message to **MSCb** (labeled **MAF 002**). +- MSCb** sends a **set-up** message to **MSba** containing the parameter **(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:
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:
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:
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:
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:
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 illustrating the 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. + +Diagram illustrating the 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 illustrating the 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. + +Diagram illustrating the 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 shown but not used 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 shown but not used 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 --> Prov{CLIR +provisioned} + Prov -- no --> SetNotProv[set provision +indication = +not provisioned] + Prov -- yes --> SetProv[set provision +indication = +provisioned] + SetProv --> SubOpt{subscription +option = +permanent} + SubOpt -- yes --> SetModePerm[set mode +indication = +permanent] + SubOpt -- no --> TempDef{temporary +mode default = +pres. restricted} + TempDef -- yes --> SetModeTempRestr[mode indication = +temporary +(pres. restricted)] + TempDef -- no --> SetModeTempAllow[mode indication = +temporary +(pres. allowed)] + + SetModeTempRestr --> Continue[/continue +call +handling/] + SetModeTempAllow --> Continue + SetModePerm --> Continue + SetNotProv --> 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 --> ErrorNotification{{Error Notification}}; Present_CLI_note1_1 -- No --> Merge1(( )); 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 --> Merge2(( )); Present_CLI_note1_2 -- No --> Restrict_CLI_note2_2; Restrict_CLI_note2_2 -- Yes --> SetPI_restricted1[Set PI = presentation restricted]; Restrict_CLI_note2_2 -- No --> SetPI_allowed2[Set PI = Presentation allowed]; SetPI_restricted1 --> Cause_of_no_CLI_CLIR1[Cause_of no_CLI_CLIR]; SetPI_allowed2 --> Cause_of_no_CLI_CLIR2[Cause_of no_CLI_CLIR]; Cause_of_no_CLI_CLIR1 --> Merge3(( )); Cause_of_no_CLI_CLIR2 --> Merge3; Merge3 --> ContinueCall{Continue Call Handling}; ContinueCall --> 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](26d664119ad25250780f554633444e54_img.jpg) + +### Procedure Cause\_of\_no\_CLI\_CLIR + +1(1) + +``` +graph TD; Start([ ]) --> Q1{Cause of no CLI supported?}; Q1 -- No --> End(( )); Q1 -- Yes --> Q2{rejected by user?}; Q2 -- Yes --> SetCoNC1[Set CoNC = reject by user]; Q2 -- No --> Q3{interacted with other services?}; Q3 -- Yes --> SetCoNC2[Set CoNC = interaction with other services]; Q3 -- No --> Q4{coin line/ payphone?}; Q4 -- Yes --> SetCoNC3[Set CoNC = coin line/payphone]; Q4 -- No --> Q5{Unavailable?}; Q5 -- Yes --> SetCoNC4[Set CoNC = unavailable]; Q5 -- No --> SetCoNC3; SetCoNC1 --> Join(( )); SetCoNC2 --> Join; SetCoNC3 --> Join; SetCoNC4 --> Join; Join --> End; +``` + +The flowchart titled 'Procedure Cause\_of\_no\_CLI\_CLIR' (1(1)) starts with a connector symbol (oval with a vertical line). It proceeds to a decision diamond: 'Cause of no CLI supported?'. If 'No', it ends at a connector symbol (circle with an X). If 'Yes', it proceeds to the next decision diamond: 'rejected by user?'. If 'Yes', it leads to a process box 'Set CoNC = reject by user'. If 'No', it proceeds to the next decision diamond: 'interacted with other services?'. If 'Yes', it leads to a process box 'Set CoNC = interaction with other services'. If 'No', it proceeds to the next decision diamond: 'coin line/ payphone?'. If 'Yes', it leads to a process box 'Set CoNC = coin line/payphone'. If 'No', it proceeds to the next decision diamond: 'Unavailable?'. If 'Yes', it leads to a process box 'Set CoNC = unavailable'. If 'No', it leads to the same process box 'Set CoNC = coin line/payphone'. All four process boxes ('Set CoNC = reject by user', 'Set CoNC = interaction with other services', 'Set CoNC = coin line/payphone', and 'Set CoNC = unavailable') lead to a common junction (circle with an X), which then leads to the final connector symbol (circle with an X). + +Flowchart for Procedure Cause\_of\_no\_CLI\_CLIR + +Figure 2.6: Procedure Cause\_of\_no\_CLI\_CLIR + +![Sequence diagram for Figure 2.7 showing information flow for calling line identification restriction in permanent or temporary mode with the default value 'presentation restricted'.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant MSCb/LE + MS->>MSC: set-up + Note over MS,MSC: ** + MSC->>VLR: info request + Note right of VLR: MAF +003 + VLR->>MSC: info acknowledge + Note right of MSC: MAF +004 + MSC->>MSCb/LE: set-up + Note over MSC,MSCb/LE: (SI, PI=restricted, CoNC, +LI:Calling party number) + +``` + +Sequence diagram for Figure 2.7 showing information flow for calling line identification restriction in permanent or temporary mode with the default value 'presentation restricted'. + +**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 when CLIR is provisioned in temporary mode with default value 'presentation restricted'.](392a79ccd95e682ccd08f35ab2e64144_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant MSCb/LE + MS->>MSC: set-up + Note over MS,MSC: (present CLI) +** + MSC->>VLR: info request + Note right of VLR: MAF +003 + VLR->>MSC: info acknowledge + Note right of MSC: MAF +004 + MSC->>MSCb/LE: set-up + Note over MSC,MSCb/LE: (SI, PI=pres allowed, LI) + +``` + +Sequence diagram for Figure 2.8 showing information flow for allowing presentation of the CLI when CLIR is provisioned in temporary mode with default value 'presentation restricted'. + +**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 showing information flow 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 003. 3. The VLR responds with an 'info acknowledge' to the MSC, identified by MAF 004. 4. Finally, the MSC sends a 'set-up' message to the MSCb/LE, including parameters (SI, PI=pres allowed, LI). + +Sequence diagram showing information flow 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 showing information flow 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 003. 3. The VLR responds with an 'info acknowledge' to the MSC, identified by MAF 004. 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 showing information flow 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 + direction LR + State1: (Not Provisioned, +Not Applicable, +Not Active, +Not Induced) + State2: (Provisioned, +Not Applicable, +Active and Operative, +Not Induced) + State1 --> State2 : Provision + State2 --> State1 : Withdrawal + +``` + +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).](6a5c8326029e6290e69a5f43d6ed4548_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note left of MS: MS requests COLP status + MS->>MSC: Interrogate COLP + MSC->>VLR: Interrogate COLP + VLR-->>MSC: Acknowledge + MSC-->>MS: Release Complete +``` + +The diagram shows a sequence of messages between four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence is as follows: 1. The MS sends an 'Interrogate COLP' message to the MSC. 2. The MSC sends an 'Interrogate COLP' message to the VLR. 3. The VLR sends an 'Acknowledge' message back to the MSC. 4. The MSC sends a 'Release Complete' message back to the MS. The HLR is shown as a separate entity on the right, not involved in this specific sequence. + +Sequence diagram illustrating the interrogation of connected line identification presentation (COLP). + +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[continue call handling]; provisioned -- yes --> available{COL available}; available -- no --> setPI[set PI = number not available]; available -- yes --> restricted{presentation restricted}; restricted -- yes --> override{override category}; restricted -- no --> additional{additional COL available}; override -- yes --> inCase{COL in case of override category}; override -- no --> continue; inCase --> passAdd[pass additional COL]; inCase -- COL --> passCOL[pass COL]; inCase -- additional COL --> passAdd; additional -- yes --> passAdd; additional -- no --> passCOL; setPI --> continue; passAdd --> continue; passCOL --> continue; continue --> 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 'connected number received'. If 'no', it goes to 'continue call handling'. If 'yes', it checks if '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 'connected number received'. If 'no', it goes to 'continue call handling'. If 'yes', it checks if '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 between MSa, MSCa, VLRa, MSCb/LE, and MSb/TE. The diagram illustrates the exchange of messages like set-up, info req, info ack, and answer with various parameters (OR1-OR5, SI, PI, LI, aSI, aLI).](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) + MSCa-->>MSa: answer MAF006 OR1:N + Note right of MSCa: OR1:Y + MSCa-->>MSa: answer OR1:Y OR2:c + Note right of MSCa: OR1:Y + MSCa-->>MSa: (PI) + Note right of MSCa: OR1:Y OR2:b OR3:N + MSCa-->>MSa: answer + Note right of MSCa: OR1:Y OR2:b OR3:Y OR4:N + MSCa-->>MSa: (PI) + Note right of MSCa: OR1:Y OR2:b OR3:Y OR4:Y OR5:a + MSCa-->>MSa: answer + Note right of MSCa: OR1:Y OR2:b OR3:Y OR4:Y OR5:b + MSCa-->>MSa: (aSI+PI+aLI) + Note right of MSCa: OR1:Y OR2:a OR4:N + MSCa-->>MSa: answer + Note right of MSCa: OR1:Y OR2:a OR4:Y + MSCa-->>MSa: (SI+PI+LI) + Note right of MSCa: OR1:Y OR2:a OR4:Y + MSCa-->>MSa: answer + Note right of MSCa: (aSI+PI+aLI) + +``` + +Sequence diagram showing information flow for connected line identification presentation between MSa, MSCa, VLRa, MSCb/LE, and MSb/TE. The diagram illustrates the exchange of messages like set-up, info req, info ack, and answer with various parameters (OR1-OR5, SI, PI, LI, aSI, aLI). + +**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 of 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. The flow starts with 'idle', followed by 'initiate handling of COLR'. A decision diamond 'COLR provisioned' follows. If 'yes', it goes to 'set PI = presentation restricted'. If 'no', it goes to 'set PI = presentation allowed'. Both paths lead to 'continue call handling', which then leads to '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 --> setPIrestricted[set PI = presentation restricted]; provisioned -- no --> setPIallowed[set PI = presentation allowed]; setPIrestricted --> continue[continue call handling]; setPIallowed --> continue; continue --> idle2([idle]); +``` + +COLR: Connected Line Identification Restriction. +PI: Presentation Indicator. + +Flowchart for Process COLR\_MAF041. The flow starts with 'idle', followed by 'initiate handling of COLR'. A decision diamond 'COLR provisioned' follows. If 'yes', it goes to 'set PI = presentation restricted'. If 'no', it goes to 'set PI = presentation allowed'. Both paths lead to 'continue call handling', which then leads to '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. Lifelines: MS/TE, MSC/LE, VLRb, MSCb, MSb. The process involves a 'set-up' message from MS/TE to MSC/LE, which then forwards it to MSCb via VLRb. MSCb checks the VLRb for information (info req/info ack) and then sends a 'set-up' to MSb. MSb returns an 'answer' with subaddress '**'. MSCb then sends two 'answer' messages back to MSC/LE, one with (SI+PI+LI) and another with (SI+PI+LI), along with MAF041 and OR1/OR2 parameters.](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: info ack + Note right of VLRb: MAF 040 + MSCb->>MSb: set-up + MSb-->>MSCb: answer ** + Note right of MSCb: MAF041 +OR1:N +OR2:a + MSCb->>MSC/LE: answer (SI+PI+LI) + Note right of MSCb: OR1:Y +OR2:b + MSCb->>MSC/LE: answer (SI+PI+LI) + +``` + +Sequence diagram showing information flow for connected line identification restriction from MS/TE to MSb. Lifelines: MS/TE, MSC/LE, VLRb, MSCb, MSb. The process involves a 'set-up' message from MS/TE to MSC/LE, which then forwards it to MSCb via VLRb. MSCb checks the VLRb for information (info req/info ack) and then sends a 'set-up' to MSb. MSb returns an 'answer' with subaddress '\*\*'. MSCb then sends two 'answer' messages back to MSC/LE, one with (SI+PI+LI) and another with (SI+PI+LI), along with MAF041 and OR1/OR2 parameters. + +**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: + +- a) the HPLMN supports COLR, and COLR is provisioned for the subscriber; +- b) the HPLMN supports COLR, but COLR is not provisioned for the subscriber; +- c) the HPLMN does not support COLR. + +In case a) the VPLMN must apply the COLR subscription as indicated by the data sent by the HPLMN. + +In case b) the VPLMN must not apply COLR. + +In case c) the VPLMN must apply an implicit COLR subscription. + +To allow the VPLMN to make this distinction, the HLR and VLR behave as follows: + +- If the HLR supports COLR, but COLR is not provisioned for the subscriber, the HLR shall inform the VLR that COLR is not provisioned. +- If the VLR supports COLR, but the HLR does not support COLR, the VLR shall behave in the same way as if COLR was provisioned for the subscriber, i.e. the connected line identity shall not be displayed to the calling subscriber unless the calling subscriber has COLR override capability. When interrogating the service status the subscriber shall be informed that COLR is provided to him and is active. + +# Annex A (informative): Mapping of CLI + +This annex defines the mapping rules of CLI parameters received via the NW-NW interface to CLI parameters to be sent to the MS. + +| | Information received over the NW-NW interface | | | | | Information sent to the MS | | | +|--------------------------------------------|-----------------------------------------------|---------------|-----------------------------------|--------------------------|--------------------------------|----------------------------|------------------------------------|--------------------------------| +| | presentation indicator | line identity | additional presentation indicator | additional line identity | Cause of No CLI | presentation indicator | line identity | Cause of No CLI | +| CLIP not 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 | +| CLIP provisioned with override category | - | - | - | - | - | not available | - | - | +| | not available | - | - | - | - | not available | - | - | +| | allowed | digits | - | - | - | allowed | digits of line identity | - | +| | allowed | digits | + | digits | - | allowed | digits of additional line identity | - | +| | restricted | digits | - | - | - | restricted | digits of line identity | - | +| | restricted | digits | + | digits | - | restricted | NOTE 1 | - | +| | restricted | digits | + | digits | unavailable | restricted | NOTE 1 | unavailable | +| | restricted | digits | + | digits | reject by user | restricted | NOTE 1 | reject by user | +| | restricted | digits | + | digits | interaction with other service | restricted | NOTE 1 | interaction with other service | +| | restricted | digits | + | digits | payphone | restricted | NOTE 1 | payphone | +| | restricted | digits | - | - | unavailable | restricted | digits of line identity | unavailable | +| | restricted | digits | - | - | reject by user | restricted | digits of line identity | reject by user | +| | restricted | digits | - | - | interaction with other service | restricted | digits of line identity | interaction with other service | +| | restricted | digits | - | - | payphone | restricted | digits of line identity | payphone | +| | restricted by network | digits | - | - | - | restricted | digits of line identity | - | +| | restricted by network | digits | allowed | digits | - | allowed | digits of additional line identity | - | + +- parameter not present + +\* parameter absent or present, if present it may have any value + ++ parameter present, it may have any value + +NOTE 1: Network Option to send either digits of the line identity or digits of additional line identity applies. + +# Annex B (informative): Change history + +| TSG CN# | Spec | CR | | New Version | Subject/Comment | +|----------|-----------|--------|---------|-------------|---------------------------------------------------------------| +| Apr 1999 | GSM 03.81 | | | | Transferred to 3GPP CN1 | +| CN#03 | 23.081 | | R99 | 3.0.0 | Approved at CN#03 | +| | 23.081 | | R99 | 3.0.1 | Upgrade of references from 2G to 3G | +| CN#08 | 23.081 | | R99 | 3.1.0 | Enhanced handling of presentation indicators for CLIP | +| CN#11 | 23.081 | | Rel-4 | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 23.081 | | Rel-5 | 5.0.0 | Release 5 after CN#16 | +| CN#17 | 23.081 | 0006 | Rel-5 | 5.1.0 | Correction of 'Cause of no CLI' handling in SDLs | +| CN#19 | 23.081 | 0007r1 | Rel-5 | 5.2.0 | Correction to interworking between CLIP enhancement and CAMEL | +| CN#25 | 23.081 | 0008 | Rel-6 | 6.0.0 | Editorial correction of table definition | +| CT#36 | 23.081 | | Rel-7 | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.081 | | Rel-8 | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.081 | - | Rel-9 | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.081 | - | Rel-10 | 10.0.0 | Update to Rel-10 version (MCC) | +| 2011-12 | 23.081 | 0009 | Rel-11 | 11.0.0 | CLI interactions with ACR | +| 2014-09 | 23.081 | - | Rel-12 | 12.0.0 | Update to Rel-12 version (MCC) | +| 2015-12 | 23.081 | - | Rel-13 | 13.0.0 | Update to Rel-13 version (MCC) | +| 2017-03 | 23.081 | - | Rel-14 | 14.0.0 | Update to Rel-14 version (MCC) | +| 2018-06 | 23.081 | - | Rel-15 | 15.0.0 | Update to Rel-15 version (MCC) | +| 2020-07 | 23.081 | - | Rel-16 | 16.0.0 | Update to Rel-16 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23086/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23086/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc087fab509fec403dd74d5f7d46f98bce101476 --- /dev/null +++ b/marked/Rel-16/23_series/23086/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b98b93f229e0153ea4b8408daccbd1c1fb654612abd73a57ebe098e769b42247 +size 83424 diff --git a/marked/Rel-16/23_series/23086/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/marked/Rel-16/23_series/23086/41a438d7e4adc17c3a4005e7c9500091_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c63a2919d0755dcbbfb95c2a06210b82441e644b --- /dev/null +++ b/marked/Rel-16/23_series/23086/41a438d7e4adc17c3a4005e7c9500091_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02c7a9cf3e3012bdaf62b707e365008f47ff2a0b37463c5c531247b8c9775a49 +size 32245 diff --git a/marked/Rel-16/23_series/23086/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23086/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..042eccc385983b8fdcf9f4f0cd0e31d99b54fbc2 --- /dev/null +++ b/marked/Rel-16/23_series/23086/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42a995c89c673d93ce0d9ba1dbb0f0550097ccc64f57295b17779d202e4d8d0a +size 100205 diff --git a/marked/Rel-16/23_series/23086/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/23_series/23086/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..524b0f559cc8e234eaa3ae74f61b14c015489bad --- /dev/null +++ b/marked/Rel-16/23_series/23086/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:877a6e81fd4472c256710a7c92aa50b2c2eee1bf07633b7e88d46c25e7e15816 +size 62947 diff --git a/marked/Rel-16/23_series/23086/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23086/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d16222dc2071a4161312d1ee85109f3a89176f6a --- /dev/null +++ b/marked/Rel-16/23_series/23086/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:836c7ff19fdf3d65b45e2e9a5a7d952d761d60a84af79d3514a8e152d0dd0870 +size 103119 diff --git a/marked/Rel-16/23_series/23086/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23086/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cff121845b431233836c318d84e0b186f0bdb5b8 --- /dev/null +++ b/marked/Rel-16/23_series/23086/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e17e2f65f647d1b059e3940c14d2425c41105613b2778d028be95ba6d7d74018 +size 105466 diff --git a/marked/Rel-16/23_series/23086/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23086/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9764fdacc98cc79d20584c080fe5a74cb43c4e3f --- /dev/null +++ b/marked/Rel-16/23_series/23086/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b47a9d84142b4331a98f861db940a640ae43dbfe6ddbf102e130db5d34d5691d +size 75459 diff --git a/marked/Rel-16/23_series/23086/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-16/23_series/23086/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee2bd4c9bc9ce5492ee39e6d29bb4dec8c72444e --- /dev/null +++ b/marked/Rel-16/23_series/23086/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aab17af56ad36e565516671f6ed973b8962df689b0711685200500d22e5d10e0 +size 33028 diff --git a/marked/Rel-16/23_series/23086/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23086/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..037b9a69dd1a46bc17ea4ed1b9253f540e7a5c8c --- /dev/null +++ b/marked/Rel-16/23_series/23086/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d9092d77a3d94df793ba4f69902d8deaf5d52a9abe452abe963791f9b20d302 +size 120384 diff --git a/marked/Rel-16/23_series/23086/raw.md b/marked/Rel-16/23_series/23086/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f041fbaf6d8a496eddadbcfe2d7778fc38b783bc --- /dev/null +++ b/marked/Rel-16/23_series/23086/raw.md @@ -0,0 +1,553 @@ + + + + + + +# --- Contents + +| | | +|-----------------------------------------------------------------------|-----------| +| Foreword ..... | 4 | +| 0 Scope..... | 5 | +| 0.1 References ..... | 5 | +| 0.2 Abbreviations ..... | 5 | +| 1 Advice of Charge (Information) (AoCI)..... | 5 | +| 1.1 Advice of Charge (Information) MSC SDL diagram..... | 5 | +| 1.2 Advice of Charge (Information) mobile equipment SDL diagram ..... | 6 | +| 1.3 Advice of Charge (Information) information flow diagram ..... | 6 | +| 1.4 Information stored in the HLR ..... | 9 | +| 1.5 State transition model..... | 10 | +| 1.6 Transfer of Information from HLR to VLR ..... | 10 | +| 1.7 Information stored in the VLR ..... | 10 | +| 1.8 Handover ..... | 10 | +| 2 Advice of Charge (Charging) (AoCC)..... | 10 | +| 2.1 Advice of Charge (Charging) MSC SDL diagram..... | 10 | +| 2.2 Advice of Charge (Charging) mobile equipment SDL diagram ..... | 11 | +| 2.3 Advice of Charge (Charging) information flow diagram..... | 11 | +| 2.4 AoCC subscriber roaming requirements ..... | 11 | +| 2.5 Information stored in the HLR ..... | 15 | +| 2.6 State transition model..... | 16 | +| 2.7 Transfer of Information from HLR to VLR ..... | 16 | +| 2.8 Information stored in the VLR ..... | 16 | +| 2.9 Handover ..... | 16 | +| Annex A (normative): Information stored in the MSC..... | 17 | +| Annex B (informative): Change history..... | 18 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +The present document defines the stage 2 of the Advice of Charge (AoC) supplementary services 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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- 0 Scope + +The present document gives the stage 2 description of the Advice of Charge (AoC) supplementary services. + +The charging supplementary services currently defined are: + +- Advice of Charge (Information) (AoCI) (clause 1); +- Advice of Charge (Charging) (AoCC) (clause 2). + +## 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 TR 21.905: "Vocabulary for 3GPP Specifications ". +- [2] 3GPP TS 22.024: "Description of Charge Advice Information (CAI)". +- [3] 3GPP TS 22.086: "Advice of Charge (AoC) Supplementary Services; Stage 1". +- [4] 3GPP TS 23.011: "Technical Realization of Supplementary Services - General Aspects". + +## 0.2 Abbreviations + +Abbreviations used in the present document are listed in 3GPP TR 21.905 [1]. + +# --- 1 Advice of Charge (Information) (AoCI) + +## 1.1 Advice of Charge (Information) MSC SDL diagram + +The SDL diagram for the Advice of Charge (Information) supplementary service within the MSC is given in figure 1.1. + +NOTE 1: AoC (Information) is not applicable to emergency calls. + +NOTE 2: The request of generation of the Charge Advice Information (CAI) applies to AoC initiation or charge modification. + +## 1.2 Advice of Charge (Information) mobile equipment SDL diagram + +The SDL diagram for the Advice of Charge (Information) supplementary service within the mobile equipment is given in figure 1.2. This SDL indicates when charging calculations are started, amended and stopped, within the mobile equipment. The mobile equipment should start charging calculations as soon as possible after receiving the charging information. Charging calculations should be amended by the mobile equipment in accordance with GSM 02.24. + +NOTE: The point at which the charging calculations are amended can occur before or after sending the AoC Acknowledge. + +Charging calculations are stopped when the call ends for any reason. + +The reception of the CAI shall be acknowledged only if the MS supports the AoCI functionality specified in GSM 02.24 and GSM 02.86, however the network does not action this acknowledgement in the AoC (Information) case. + +## 1.3 Advice of Charge (Information) information flow diagram + +The Advice of Charge (Information) information flow diagrams are shown in figure 1.3. + +![SDL diagram for Process AoCI_MSC showing the flow of Charge Advice Information (CAI). The sequence starts with an initial state, followed by a state 'call in progress or call set up in progress'. A transition 'request generation of CAI' leads to a state 'generate CAI', which then leads to a transition 'send CAI', and finally to a state 'continue call or call set up'. A note indicates that the request applies to AoC initiation or charge modification. Another note defines CAI as Charge Advice Information.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +Process AoCI\_MSC 386\_11(1) + +``` +stateDiagram-v2 + [*] --> State1 + State1 --> State2: call in progress or call set up in progress + State2 --> State3: request generation of CAI + State3 --> State4: generate CAI + State4 --> State5: send CAI + State5 --> State6: continue call or call set up +``` + +Request of generation of CAI applies to AoC initiation or charge modification. + +CAI: Charge Advice Information + +SDL diagram for Process AoCI\_MSC showing the flow of Charge Advice Information (CAI). The sequence starts with an initial state, followed by a state 'call in progress or call set up in progress'. A transition 'request generation of CAI' leads to a state 'generate CAI', which then leads to a transition 'send CAI', and finally to a state 'continue call or call set up'. A note indicates that the request applies to AoC initiation or charge modification. Another note defines CAI as Charge Advice Information. + +Figure 1.1: SDL diagram of advice of charge (information) in the MSC + +![SDL diagram of advice of charge (information) in the mobile equipment. The diagram shows three main state transitions starting from 'AoC active'. Path 1: 'call set up in progress' -> 'charging information' -> 'start charge calculations' -> 'AoC acknowledge' -> 'AoC active'. Path 2: 'call ends' -> 'stop charge calculations' -> 'clear call'. Path 3: 'charging information' -> 'AoC acknowledge' -> 'amend charging calculations' -> 'AoC active'. A note indicates that 'amend charging calculations' can occur before or after sending the 'AoC acknowledge'.](d0abac95583b52a3b35f74a215567334_img.jpg) + +Process AoCI\_ME 386\_12(1) + +``` +stateDiagram-v2 + [*] --> AoC_active + state "AoC active" as AoC_active + AoC_active --> call_set_up_in_progress : call set up in progress + call_set_up_in_progress --> charging_information_1 : charging information + charging_information_1 --> start_charge_calculations : start charge calculations + start_charge_calculations --> AoC_acknowledge_1 : AoC acknowledge + AoC_acknowledge_1 --> AoC_active + AoC_active --> call_ends : call ends + call_ends --> stop_charge_calculations : stop charge calculations + stop_charge_calculations --> clear_call : clear call + AoC_active --> charging_information_2 : charging information + charging_information_2 --> AoC_acknowledge_2 : AoC acknowledge + AoC_acknowledge_2 --> amend_charging_calculations : amend charging calculations + amend_charging_calculations --> AoC_active +``` + +Point at which charging calculations are amended can occur before or after sending the AoC acknowledge. + +SDL diagram of advice of charge (information) in the mobile equipment. The diagram shows three main state transitions starting from 'AoC active'. Path 1: 'call set up in progress' -> 'charging information' -> 'start charge calculations' -> 'AoC acknowledge' -> 'AoC active'. Path 2: 'call ends' -> 'stop charge calculations' -> 'clear call'. Path 3: 'charging information' -> 'AoC acknowledge' -> 'amend charging calculations' -> 'AoC active'. A note indicates that 'amend charging calculations' can occur before or after sending the 'AoC acknowledge'. + +Figure 1.2: SDL diagram of advice of charge (information) in the mobile equipment + +![Sequence diagrams showing information flow for Advice of Charge (Information) between MS, MSC, and VLR.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates four sequence scenarios for Advice of Charge (Information) involving the Mobile Station (MS), Mobile Switching Center (MSC), and Visitor Location Register (VLR). + +**Successful MS originated call set-up with AoC (Information)** + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MS: Successful MS originated call set-up with AoC (Information) + MS->>MSC: set-up + MSC->>VLR: send information + VLR->>MSC: o/g call set-up + MSC->>VLR: complete call + VLR->>MSC: B answer + MSC->>MS: charging information + MS->>MSC: AoC acknowledge + +``` + +**Successful MS terminated call set-up with AoC (Information)** + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + Note left of MSC: Successful MS terminated call set-up with AoC (Information) + MSC->>VLR: IAM + VLR->>MSC: send information + MSC->>VLR: i/c call set-up + VLR->>MSC: complete call + MSC->>MS: B answer + MS->>MSC: charging information + MSC->>MS: AoC acknowledge + +``` + +**MS unable to charge, AoCI, originated and terminated call set-up** + +``` + +sequenceDiagram + participant MS + participant MSC + Note left of MSC: MS unable to charge, AoCI, originated and terminated call set-up + MSC->>MS: charging information + +``` + +**Charge modification, AoC (Information)** + +``` + +sequenceDiagram + participant MS + participant MSC + Note left of MSC: Charge modification, AoC (Information) + MSC->>MS: charging information + MS->>MSC: AoC acknowledge + +``` + +Sequence diagrams showing information flow for Advice of Charge (Information) between MS, MSC, and VLR. + +Figure 1.3: Information flow for Advice of Charge (Information) + +## 1.4 Information stored in the HLR + +AoCI may have the following logical states (refer to GSM 03.11 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 AoCI (which shall be one of the valid states listed above) on a per subscriber basis. + +## 1.5 State transition model + +The following figure shows the successful cases of transition between the applicable logic states of AoCI. 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 AoCI diagram showing two states and two transitions.](daa4a6fa7e2ba1954258f86b4928eb32_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 AoCI. 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 AoCI diagram showing two states and two transitions. + +**Figure 1.4: State transition model for AoCI** + +## 1.6 Transfer of Information from HLR to VLR + +If the provisioning state for AoCI is "Provisioned" then when the served subscriber registers on a VLR the HLR shall send that VLR information about the logical state of AoCI. + +If the logical state of AoCI is changed while a subscriber is registered on a VLR, then the HLR shall inform the VLR of the new logical state of AoCI. + +## 1.7 Information stored in the VLR + +For the supplementary service AoCI the VLR shall store the service state information received from the HLR. + +## 1.8 Handover + +Handover will have no impact on AoC control procedure. + +# 2 Advice of Charge (Charging) (AoCC) + +## 2.1 Advice of Charge (Charging) MSC SDL diagram + +The SDL diagram for the Advice of Charge (Charging) supplementary service within the MSC is given in figure 2.1. At invocation of the Advice of Charge (Charging) supplementary service the network shall send the "Charging" MS the CAI. The network shall allow the call to proceed whilst waiting for an acknowledgement of the CAI. The waiting period is governed by Timer T(AoC). On expiry of T(AoC) the network shall initiate call clearing. + +NOTE 1: AoC (Charging) is not applicable to emergency calls. + +NOTE 2: The request of generation of CAI applies to AoC initiation or charge modification. + +## 2.2 Advice of Charge (Charging) mobile equipment SDL diagram + +The SDL diagram for the Advice of Charge (Charging) supplementary service within the mobile equipment is given in figure 2.2. The SDL indicates when charging calculations are started, amended and stopped, within the mobile equipment. The mobile equipment should start charging calculations as soon as possible after receiving the charging information. Charging calculations should be amended by the mobile equipment in accordance with GSM 02.24. + +NOTE: The point at which charging calculations are amended can occur before or after sending the AoC Acknowledge. + +Charging calculations are stopped when the call ends for any reason. + +The reception of the CAI shall be acknowledged only if the MS supports the AoCC functionality specified in GSM 02.24 and GSM 02.86. + +For mobile originated calls, the MS shall prevent a call set-up attempt if the ACM value is equal to or greater than ACMmax. + +For mobile terminated calls, a call set-up attempt shall be allowed even if the ACM value is equal to or greater than ACMmax. In this case, when the MS detects that this is a chargeable call and that the ACM value is equal to or greater than ACMmax then the call shall be released. + +During an active call, when the MS detects that ACM is equal to or greater than ACMmax then the MS shall release the call. + +## 2.3 Advice of Charge (Charging) information flow diagram + +The Advice of Charge (Charging) information flow diagrams are shown in figure 2.3. + +## 2.4 AoCC subscriber roaming requirements + +When an AoCC subscriber first roams into an MSC area not supporting AoCC, or the subscription is given to him while he is roaming in an MSC area not supporting AoCC the following applies: + +The HLR shall indicate to the VLR that roaming is restricted in this MSC area due to unsupported feature, and it prevents further mobile terminated traffic. In this case the MS is not reachable. + +When entering an AoCC supporting area the AoCC related roaming restriction shall be removed in the HLR. + +When AoCC is withdrawn the AoCC related roaming restriction shall be removed in the HLR and VLR. This is independent from roaming restrictions due to other reasons. + +![SDL diagram for advice of charge (charging) in the MSC. The diagram shows two main state transitions starting from 'call in progress or call set up in progress'. The left path involves generating and sending CAI, starting a timer, and waiting for acknowledgment. The right path branches into 'AoC acknowledge', 'timer T(AoC) expired', or 'call cleared', leading to either 'call in progress' or 'idle' states.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +Process AoCC\_MSC 386\_21(1) + +``` +stateDiagram-v2 + [*] --> call_in_progress_or_set_up_in_progress : call in progress or call set up in progress + call_in_progress_or_set_up_in_progress --> request_generation_of_CAI : request generation of CAI + note right of request_generation_of_CAI : Request of generation of CAI applies to AoC initiation or charge modification. + request_generation_of_CAI --> generate_CAI : generate CAI + generate_CAI --> send_CAI : send CAI + send_CAI --> start_timer_T_AoC : start timer T(AoC) + start_timer_T_AoC --> wait_for_AoC_acknowledge : wait for AoC acknowledge + wait_for_AoC_acknowledge --> AoC_acknowledge : AoC acknowledge + wait_for_AoC_acknowledge --> timer_T_AoC_expired : timer T(AoC) expired + wait_for_AoC_acknowledge --> call_cleared : call cleared + AoC_acknowledge --> stop_timer_T_AoC_1 : stop timer T(AoC) + stop_timer_T_AoC_1 --> call_in_progress : call in progress + timer_T_AoC_expired --> clear_call : clear call + call_cleared --> stop_timer_T_AoC_2 : stop timer T(AoC) + clear_call --> idle : idle + stop_timer_T_AoC_2 --> idle +``` + +CAI: Charge Advice Information + +SDL diagram for advice of charge (charging) in the MSC. The diagram shows two main state transitions starting from 'call in progress or call set up in progress'. The left path involves generating and sending CAI, starting a timer, and waiting for acknowledgment. The right path branches into 'AoC acknowledge', 'timer T(AoC) expired', or 'call cleared', leading to either 'call in progress' or 'idle' states. + +Figure 2.1: SDL diagram of advice of charge (charging) in the MSC + +![SDL diagram of advice of charge (charging) in the mobile equipment.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Process AoCC\_ME + +386\_22(1) + +``` + +stateDiagram-v2 + [*] --> call_set_up_in_progress + call_set_up_in_progress --> charging_information_1 + charging_information_1 --> CAI_0_1 + CAI_0_1 --> AoC_acknowledge_1 : yes + CAI_0_1 --> ACM_ge_ACMmax_1 : no + AoC_acknowledge_1 --> AoC_inactive_1 + AoC_inactive_1 --> charging_information_2 + charging_information_2 --> CAI_0_2 + CAI_0_2 --> AoC_acknowledge_2 : yes + CAI_0_2 --> call_ends_1 : no + call_ends_1 --> clear_call_1 + + ACM_ge_ACMmax_1 --> clear_call_2 : yes + ACM_ge_ACMmax_1 --> start_charge_calculations : no + start_charge_calculations --> AoC_acknowledge_3 + AoC_acknowledge_3 --> AoC_active_1 + + AoC_active_1 --> ACM_ge_ACMmax_2 + AoC_active_1 --> call_ends_2 + AoC_active_1 --> charging_information_3 + + ACM_ge_ACMmax_2 --> stop_charge_calculations_1 : yes + stop_charge_calculations_1 --> clear_call_3 + + call_ends_2 --> stop_charge_calculations_2 + stop_charge_calculations_2 --> clear_call_4 + + charging_information_3 --> CAI_0_3 + CAI_0_3 --> AoC_acknowledge_4 : yes + AoC_acknowledge_4 --> stop_charge_calculations_3 + stop_charge_calculations_3 --> AoC_inactive_2 + + CAI_0_3 --> AoC_acknowledge_5 : no + AoC_acknowledge_5 --> amend_charging_calculations + amend_charging_calculations --> AoC_active_2 + +``` + +*A mobile originated call set-up shall not be allowed if ACM ≥ ACMmax* + +*Point at which charging calculations are amended can occur before or after sending the AoC acknowledge.* + +SDL diagram of advice of charge (charging) in the mobile equipment. + +**Figure 2.2: SDL diagram of advice of charge (charging) in the mobile equipment** + +![Sequence diagrams showing information flow for Advice of Charge (Charging) between MS, MSC, and VLR for three scenarios: successful originated call, successful terminated call, and charge modification.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram illustrates three sequence interactions between a Mobile Station (MS), a Mobile Switching Center (MSC), and a Visitor Location Register (VLR) for Advice of Charge (AoC) charging. + +**Successful MS originated call set-up with AoC (Charging)** + +- The MS sends a **set-up** message to the MSC. +- The MSC sends **send information** to the VLR. +- The VLR responds with **o/g call set-up** to the MSC. +- The MSC sends **complete call** to the VLR. +- The VLR sends **B answer** back to the MSC. +- The MSC sends **charging information** to the MS. +- The MS responds with **AoC acknowledge** to the MSC. +- Internal MSC actions: **Start timer T(AoC)** and **Stop timer T(AoC)**. + +**Successful MS terminated call set-up with AoC (Charging)** + +- The MSC sends **IAM** to the VLR. +- The VLR responds with **send information** to the MSC. +- The MSC sends **i/c call set-up** to the VLR. +- The VLR sends **complete call** to the MSC. +- The MSC sends **B answer** to the MS. +- The MSC sends **charging information** to the MS. +- The MS responds with **AoC acknowledge** to the MSC. +- Internal MSC actions: **Start timer T(AoC)** and **Stop timer T(AoC)**. + +**Charge modification, AoC (Charging)** + +- The MSC sends **charging information** to the MS. +- The MS responds with **AoC acknowledge** to the MSC. +- Internal MSC actions: **Start timer T(AoC)** and **Stop timer T(AoC)**. + +Sequence diagrams showing information flow for Advice of Charge (Charging) between MS, MSC, and VLR for three scenarios: successful originated call, successful terminated call, and charge modification. + +Figure 2.3 (sheet 1 of 2): Information flow for Advice of Charge (Charging) + +![Sequence diagrams showing information flow for Advice of Charge (Charging) between MS, MSC, and VLR for successful originated, successful terminated, and charge modification scenarios.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +The diagram consists of three sequence diagrams illustrating the interaction between a Mobile Station (MS), a Mobile Switching Center (MSC), and a Visitor Location Register (VLR) for Advice of Charge (AoC) charging scenarios. + +**Successful MS originated call set-up with AoC (Charging)** + +- The MS sends a **set-up** message to the MSC. +- The MSC sends a **send information** message to the VLR. +- The VLR responds with **o/g call set-up** and **complete call** messages to the MSC. +- The MSC sends a **B answer** message to the MS. +- The MSC sends **charging information** to the MS. +- The MS responds with an **AoC acknowledge** message to the MSC. +- Internal MSC actions include **Start timer T(AoC)** and **Stop timer T(AoC)**. + +**Successful MS terminated call set-up with AoC (Charging)** + +- The MSC receives an **IAM** message from an external source. +- The MSC sends a **send information** message to the VLR. +- The VLR responds with **i/c call set-up** and **complete call** messages to the MSC. +- The MSC sends a **B answer** message to the MS. +- The MSC sends **charging information** to the MS. +- The MS responds with an **AoC acknowledge** message to the MSC. +- Internal MSC actions include **Start timer T(AoC)** and **Stop timer T(AoC)**. + +**Charge modification, AoC (Charging)** + +- The MSC sends **charging information** to the MS. +- The MS responds with an **AoC acknowledge** message to the MSC. +- Internal MSC actions include **Start timer T(AoC)** and **Stop timer T(AoC)**. + +Sequence diagrams showing information flow for Advice of Charge (Charging) between MS, MSC, and VLR for successful originated, successful terminated, and charge modification scenarios. + +Figure 2.3 (sheet 2 of 2): Information flow for Advice of Charge (Charging) + +## 2.5 Information stored in the HLR + +AoCC may have the following logical states (refer to GSM 03.11 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 AoCC (which shall be one of the valid states listed above) on a per subscriber basis. + +## 2.6 State transition model + +The following figure shows the successful cases of transition between the applicable logic states of AoCC. 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 AoCC diagram](41a438d7e4adc17c3a4005e7c9500091_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 AoCC. 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 AoCC diagram + +Figure 2.4: State transition model for AoCC + +## 2.7 Transfer of Information from HLR to VLR + +If the provisioning state for AoCC is "Provisioned" then when the served subscriber registers on a VLR the HLR shall send that VLR information about the logical state of AoCC. + +If the logical state of AoCC is changed while a subscriber is registered on a VLR, then the HLR shall inform the VLR of the new logical state of AoCC. + +## 2.8 Information stored in the VLR + +For the supplementary service AoCC the VLR shall store the service state information received from the HLR. + +## 2.9 Handover + +Handover will have no impact on AoC control procedure. + +# --- Annex A (normative): Information stored in the MSC + +The MSC shall have access to the following tables to enable the call handling function to generate the Charge Advice Information (CAI), see GSM 02.24. The table will give the CAI element values corresponding to service request, call destination, type of day and the time of day. + +- | | | +|-------------------------------------------|--------------| +| - Units per interval table | (e1 values); | +| - Seconds per internal table | (e2 values); | +| - Scaling factor table | (e3 values); | +| - Unit increment table | (e4 values); | +| - Units per data interval table | (e5 values); | +| - Segments per data interval table | (e6 values); | +| - Initial seconds per time interval table | (e7 values). | + +# Annex B (informative): Change history + +| TSG CN# | Spec | CR | Rev | Phase | Cat | New Ver | Subject/Comment | +|----------|-----------|------|-----|--------|-----|---------|--------------------------------------| +| Apr 1999 | GSM 03.86 | | | R97 | | | Transferred to 3GPP CN1 | +| CN#03 | 23.086 | | | R99 | | 3.0.0 | Approved at CN#03 | +| | 23.086 | | | R99 | | 3.0.1 | Reference list updated from 2G to 3G | +| CN#09 | 23.086 | 001 | 1 | R99 | F | 3.1.0 | SDL refresh | +| CN#11 | 23.086 | | | Rel-4 | | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 23.086 | | | Rel-5 | | 5.0.0 | Release 5 after CN#16 | +| CN#26 | 23.086 | | | Rel-6 | | 6.0.0 | Release 6 after CN#26 | +| CT#30 | 23.086 | 0002 | | Rel-6 | | 6.1.0 | Incorrect References | +| CT#36 | 23.086 | | | Rel-7 | | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.086 | | | Rel-8 | | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.086 | - | - | Rel-9 | | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.086 | - | - | Rel-10 | | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 23.086 | - | - | Rel-11 | | | Update to Rel-11 version (MCC) | +| 2014-09 | 23.086 | - | - | Rel-12 | | 12.0.0 | Update to Rel-12 version (MCC) | +| 2015-12 | 23.086 | - | - | Rel-13 | | 13.0.0 | Update to Rel-13 version (MCC) | +| 2017-03 | 23.086 | - | - | Rel-14 | | 14.0.0 | Update to Rel-14 version (MCC) | +| 2018-06 | 23.086 | - | - | Rel-15 | - | 15.0.0 | Update to Rel-15 version (MCC) | +| 2020-07 | 23.086 | - | - | Rel-16 | - | 16.0.0 | Update to Rel-16 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23087/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23087/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..404f19a8891f2fd5155b8047b6a5d8f6c1a776b0 --- /dev/null +++ b/marked/Rel-16/23_series/23087/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:027a0a71dce273601301a8c1c8d9dabfaffb87e8c3ce8f16cc684ef77f813ab9 +size 64380 diff --git a/marked/Rel-16/23_series/23087/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/23_series/23087/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b180f45e46397155bd57ad99d8f01c42c561ea83 --- /dev/null +++ b/marked/Rel-16/23_series/23087/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cf576588f4f88c8c0f13063e6e4fc9a260ec5332212a02e4b0878abe2534289 +size 103309 diff --git a/marked/Rel-16/23_series/23087/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23087/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6254c734aadc80aed2db5dc8a5124482c1529411 --- /dev/null +++ b/marked/Rel-16/23_series/23087/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b430ce2d0d52d1861087e36439aada2d130a6b50fe7277f57d37a3e4a830e44 +size 134020 diff --git a/marked/Rel-16/23_series/23087/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23087/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0b0f51831b3ff2b0798a4a1c6cb21b620c5f6e27 --- /dev/null +++ b/marked/Rel-16/23_series/23087/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:32aeb63ea0c570090d5341ccb57ff875fec4f816c5a7067d0387e3a4369b2e79 +size 101839 diff --git a/marked/Rel-16/23_series/23087/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/23_series/23087/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49ecbc2ba239f1bc8e74f1d8ea5bfc2de656cd7f --- /dev/null +++ b/marked/Rel-16/23_series/23087/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d6ddb01dab0d1b2a0b7a9c37c6d77860abd8e7b0a9bef0517ba4f177e5d8692 +size 63411 diff --git a/marked/Rel-16/23_series/23087/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23087/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ca616d10bbcd8fb8e615c2c5554331352f1249d --- /dev/null +++ b/marked/Rel-16/23_series/23087/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a7e6244bbc29827c8b0095ab94a4ac8552927f0d45f26a77726c6a51d2f8277 +size 128516 diff --git a/marked/Rel-16/23_series/23087/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23087/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..894348da11d38b9f51ff1f17cd516284576ec7af --- /dev/null +++ b/marked/Rel-16/23_series/23087/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:237fef4d5015747431357f035e62f954a41d82ea2d6ca9cfec72f02db9732486 +size 71093 diff --git a/marked/Rel-16/23_series/23087/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/marked/Rel-16/23_series/23087/392a79ccd95e682ccd08f35ab2e64144_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b14230bc0878e02ec852db944b7c228f305cb4a9 --- /dev/null +++ b/marked/Rel-16/23_series/23087/392a79ccd95e682ccd08f35ab2e64144_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c29a8c9bba1be93e3f1dca0ba072b67ad967fb792d24bd594078fbbb9aa1e1e1 +size 95263 diff --git a/marked/Rel-16/23_series/23087/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/23_series/23087/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..606d78c4bec711b9c72e019e8c8de9d8aad79211 --- /dev/null +++ b/marked/Rel-16/23_series/23087/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fac0aeb9681b17b51db3d22081efeb5ad2ecf19036d7a4a78919b76aa873a79f +size 90205 diff --git a/marked/Rel-16/23_series/23087/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/23_series/23087/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..339e734989e55efccb1de7aba564dec8297d8c0c --- /dev/null +++ b/marked/Rel-16/23_series/23087/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa76c66e006cb1572ce853f479e01a1d8ebc01f39296bc341def384ec5ac992c +size 93877 diff --git a/marked/Rel-16/23_series/23087/552328a9daaf3bc0069424b500025880_img.jpg b/marked/Rel-16/23_series/23087/552328a9daaf3bc0069424b500025880_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1df0f39384654a283e240a08af1149a5be541b3a --- /dev/null +++ b/marked/Rel-16/23_series/23087/552328a9daaf3bc0069424b500025880_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4240a6fcb5fb4cc04033150ddfaa983c9502683579c251219df14b3dc8fd20ba +size 66448 diff --git a/marked/Rel-16/23_series/23087/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/23_series/23087/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f609d705ad7d76bdd8df074ea88bc02a7543dbc7 --- /dev/null +++ b/marked/Rel-16/23_series/23087/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec70aef5ef1a3bb5d92be38c4800990f039b282fc9f0e2310b2522cc8f752e66 +size 62842 diff --git a/marked/Rel-16/23_series/23087/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/23_series/23087/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e0fbd1e766191e3c35d2f6d3bd032989ad9ab4e --- /dev/null +++ b/marked/Rel-16/23_series/23087/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eeb573763f6f2fddc920ce92c8c9f6087334a0078d6207cd8f3fdcbc129b4a8e +size 71906 diff --git a/marked/Rel-16/23_series/23087/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg b/marked/Rel-16/23_series/23087/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2bd261b68afa47db99fb4bed5f80620178fb69b9 --- /dev/null +++ b/marked/Rel-16/23_series/23087/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a6cd8e2886d6819279ef5084450a280caa5f8047682e34d8242a6aa26dd2a2c +size 86034 diff --git a/marked/Rel-16/23_series/23087/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/marked/Rel-16/23_series/23087/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..484455ebe56fb3467e29eecac1259cdf8ce821c5 --- /dev/null +++ b/marked/Rel-16/23_series/23087/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8e7155640b324cc7a035aa360e4eaba7412f8d85ab30805afd9894c52fedf31 +size 60010 diff --git a/marked/Rel-16/23_series/23087/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23087/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc07bbc1fb3d673ef68b7ffbad380588d12e2cac --- /dev/null +++ b/marked/Rel-16/23_series/23087/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a6ba14775e80cf04fa247fa3e5a63ccd8f2d4154473f38324c487604f4570c2 +size 72156 diff --git a/marked/Rel-16/23_series/23087/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/23_series/23087/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c13608fa90870f9bbe8f19eca20e8cc9e4347b7 --- /dev/null +++ b/marked/Rel-16/23_series/23087/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ca516550ca7030b471fbd332e99332fa2f0a50baf91cfcb99e35c578805af2c +size 73013 diff --git a/marked/Rel-16/23_series/23087/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23087/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ba5fd68fbbaa9064a932035794914a470e97792 --- /dev/null +++ b/marked/Rel-16/23_series/23087/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4823f90375b27559f8ae8169a918684acd66c10d3a9f40215ca72a98a462fbd2 +size 128454 diff --git a/marked/Rel-16/23_series/23087/84db9bf6e93779b67aa320d1dfd38d91_img.jpg b/marked/Rel-16/23_series/23087/84db9bf6e93779b67aa320d1dfd38d91_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee9c5072930929db126cdfd942a37c8873b0ad70 --- /dev/null +++ b/marked/Rel-16/23_series/23087/84db9bf6e93779b67aa320d1dfd38d91_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bdc29b3aa68862c11ce824a26b1450039a983402b5fd5bb41e762c1f727e83ee +size 32848 diff --git a/marked/Rel-16/23_series/23087/853f59c89931a666c07903b31d098277_img.jpg b/marked/Rel-16/23_series/23087/853f59c89931a666c07903b31d098277_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dbbfa2b0e6919af24bffcac6236aa7036c51a40 --- /dev/null +++ b/marked/Rel-16/23_series/23087/853f59c89931a666c07903b31d098277_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:46ce932a68dff8c5d89460d0f2ae41433d7fd90e71d0416f7437b40a7d644661 +size 59916 diff --git a/marked/Rel-16/23_series/23087/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/23_series/23087/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5fbc417541ec6231285562201c9f661b4da6efdc --- /dev/null +++ b/marked/Rel-16/23_series/23087/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:509eb97aa869f05a8c02a27b438629d859955aa0eb58465c90cbdf2ae5a67dcf +size 99865 diff --git a/marked/Rel-16/23_series/23087/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/23_series/23087/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c64b465dc0bd61b5f0b6c3feeb3421818e643f0 --- /dev/null +++ b/marked/Rel-16/23_series/23087/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fab33760872a6f7937fbaa05eca0b877631443b4a85487d6f2adc3b6f823376c +size 113479 diff --git a/marked/Rel-16/23_series/23087/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/23_series/23087/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7ae12c7c9b82f22a8de8aa8461527e22ad5a6b3 --- /dev/null +++ b/marked/Rel-16/23_series/23087/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:776c2557c78c210aabd50f92b5fe0cbbda2cc536934c8c437865a4afd9113e2c +size 67078 diff --git a/marked/Rel-16/23_series/23087/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23087/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0dcadac7d269d73200cb4b4543e304b7e1630917 --- /dev/null +++ b/marked/Rel-16/23_series/23087/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f49ab022296bb2f50e19dbd6a4a959b35ab939979fe57fd5106d2cb072c46537 +size 86581 diff --git a/marked/Rel-16/23_series/23087/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-16/23_series/23087/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d2125c7acbd9551a86075c6e3a682a242ea6fa47 --- /dev/null +++ b/marked/Rel-16/23_series/23087/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acfe321c4a79a22c231a064f0362b58faa8d08080b4595ada77052edec99c746 +size 104555 diff --git a/marked/Rel-16/23_series/23087/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23087/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..918b4f60ab061cb1f0cec9a8f7fe147e79c1727d --- /dev/null +++ b/marked/Rel-16/23_series/23087/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe8a072db735a7652c818e2dfada23fbb51df74b4474c23a77c8262d4a85d9cf +size 109622 diff --git a/marked/Rel-16/23_series/23087/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-16/23_series/23087/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..147d1e7420f804b599620ef0def9a32da2ff5e79 --- /dev/null +++ b/marked/Rel-16/23_series/23087/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b774880332d1a4ccafca754cd03fa64e67d55be71b5a5211f599d33f0ebdd5fb +size 58751 diff --git a/marked/Rel-16/23_series/23087/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23087/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9e95eed678aaac808923898e528d2a9b71c2fb2 --- /dev/null +++ b/marked/Rel-16/23_series/23087/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98f5d4ad11a1c3effff293cd7841bac492fd075b7c621fc230a27467e7a5028b +size 120891 diff --git a/marked/Rel-16/23_series/23087/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23087/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f70bceeff80082572bd15291a3411db6b3df3f34 --- /dev/null +++ b/marked/Rel-16/23_series/23087/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b7780015e1ad33e63a868e8c42819b0a2cdf3576f98fa15b74f1f298a5ad31b5 +size 54899 diff --git a/marked/Rel-16/23_series/23087/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/23_series/23087/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa1cf3f04c3b41bcbcef83a1a07b6c3a19f11fa5 --- /dev/null +++ b/marked/Rel-16/23_series/23087/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4cfc278820121cad8eea15b86ad03234139b1221c5bec8f8eb5c2e24503f1029 +size 99224 diff --git a/marked/Rel-16/23_series/23087/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23087/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8afb289f27dfa563f9e7fdbf373748d6d6d81f02 --- /dev/null +++ b/marked/Rel-16/23_series/23087/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7bb7bfc9ae6b6915a1621bd67bcfedc027a8aa792dec2b032115e0e5215e270d +size 110878 diff --git a/marked/Rel-16/23_series/23087/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-16/23_series/23087/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ee18a1d2f186320c9fc9232a69218090a330012 --- /dev/null +++ b/marked/Rel-16/23_series/23087/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97a8a7d105cfa53676cebdef055cdea82c428b75afe09ee1f57bc01deef0620d +size 108296 diff --git a/marked/Rel-16/23_series/23087/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-16/23_series/23087/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c76bafb4aaa54c600e736856cfe72e3afb53e66a --- /dev/null +++ b/marked/Rel-16/23_series/23087/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de7ae78cd4c51e2f5f897b6dd4840df37dabe55b3d3ea01b696bd7ea29b5d19d +size 103518 diff --git a/marked/Rel-16/23_series/23087/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23087/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea6d640ca6e45adbf81b9d22142e77535df12e7f --- /dev/null +++ b/marked/Rel-16/23_series/23087/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4b37270a377762b3862388600b7c5da41ba3624538e0c35868f73f934a560235 +size 104714 diff --git a/marked/Rel-16/23_series/23087/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/23_series/23087/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84baadfc63c80e1e90a1e1e2349689156276654e --- /dev/null +++ b/marked/Rel-16/23_series/23087/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4c44c2b5ae92b54f6d08076d8e4fb36869d6f1fb145c230af775b1dc20df40a +size 58665 diff --git a/marked/Rel-16/23_series/23087/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/marked/Rel-16/23_series/23087/e29665b8abcea967ef289c6aff07ae4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a7c1b0f35a451ea1b79f9d143ecd0909c35342a --- /dev/null +++ b/marked/Rel-16/23_series/23087/e29665b8abcea967ef289c6aff07ae4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c78641225c3d1a1ef5ed6eb1b1386e5bd7e7b5f8d0e94a51d3ce4ab47d1f010 +size 69638 diff --git a/marked/Rel-16/23_series/23087/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23087/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50c8eeef01fc0d6376362d212110994999061f5b --- /dev/null +++ b/marked/Rel-16/23_series/23087/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6dd2d7d07165ae7cb306a6f39ed7cc22f462582ff5d6559768631c5d09d737d6 +size 93924 diff --git a/marked/Rel-16/23_series/23087/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23087/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..48e80e59cea1ad8b59b243ae4007a618f3b2b2ba --- /dev/null +++ b/marked/Rel-16/23_series/23087/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e6b2f5685e5b12ff32884043c33b7d78b0e14466375d8dce17aeb7028bd23a3b +size 120206 diff --git a/marked/Rel-16/23_series/23087/raw.md b/marked/Rel-16/23_series/23087/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..94dfaabae2174b0ab773c05f9f2bd2a611144e05 --- /dev/null +++ b/marked/Rel-16/23_series/23087/raw.md @@ -0,0 +1,1641 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 7 | +| 4 General..... | 7 | +| 4.1 Activation of UUS components ..... | 7 | +| 4.1.1 Implicit request..... | 7 | +| 4.1.2 Explicit request..... | 8 | +| 4.1.3 UUS required option..... | 8 | +| 5 Handling of User-to-user signalling..... | 8 | +| 5.1 Timers..... | 8 | +| 5.2 Information flows of UUS services..... | 9 | +| 5.2.1 Service 1 (UUS1) ..... | 9 | +| 5.2.1.1 Flow control..... | 9 | +| 5.2.1.2 Information flows ..... | 10 | +| 5.2.1.2.1 Implicit activation ..... | 11 | +| 5.2.1.2.2 Explicit activation ..... | 12 | +| 5.2.2 Service 2 (UUS2) ..... | 13 | +| 5.2.2.1 Flow control..... | 13 | +| 5.2.2.2 Information flows ..... | 13 | +| 5.2.3 Service 3 (UUS3) ..... | 15 | +| 5.2.3.1 Flow control..... | 15 | +| 5.2.3.2 Information flows ..... | 16 | +| 5.3 Messages and their contents..... | 19 | +| 5.3.1 Information elements used in the messages ..... | 19 | +| 5.3.2 Messages between MS and MSC ..... | 19 | +| 5.3.3 Messages between MSC and VLR (B interface)..... | 20 | +| 5.3.4 Messages between MSC – MSC (E interface) ..... | 20 | +| 6 Interaction with other supplementary services..... | 21 | +| 6.1 Call forwarding unconditional (CFU)..... | 21 | +| 6.2 Call forwarding on mobile subscriber busy (CFB)..... | 21 | +| 6.3 Call forwarding on no reply (CFNRy)..... | 21 | +| 6.4 Call forwarding on mobile subscriber not reachable (CFNRc)..... | 21 | +| 6.5 Call waiting (CW)..... | 21 | +| 6.6 Call hold (HOLD) ..... | 22 | +| 6.7 Completion of calls to busy subscribers (CCBS)..... | 22 | +| 6.8 Explicit call transfer (ECT)..... | 22 | +| 6.9 Multi party service (MPTY)..... | 22 | +| 6.10 Advice of charge (AoC) ..... | 22 | +| 6.11 Barring of outgoing calls (BAOC)..... | 22 | +| 6.12 Barring of outgoing international calls (BOIC) ..... | 22 | +| 6.13 Barring of outgoing international calls except those directed to the home PLMN country (BOIC-exHC) ..... | 22 | +| 6.14 Barring of incoming calls (BAIC)..... | 22 | +| 6.15 Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam)..... | 22 | +| 6.16 Call deflection (CD)..... | 23 | +| 7 Interaction with other network features ..... | 23 | +| 7.1 Customised Applications for Mobile network Enhanced Logic (CAMEL) ..... | 23 | +| 7.2 Support for Optimal Routeing(SOR) ..... | 23 | +| 8 Interworking with other networks..... | 23 | +| 8.1 Interworking with GSM PLMN/ISDN network supporting only a maximum User-user information element length of 35 octets..... | 23 | + +| | | | +|------------------------|-------------------------------------------------------|----| +| 8.2 | Interworking with non-ISDN network ..... | 23 | +| 9 | Network entity functions..... | 24 | +| 9.1 | Originating network processes ..... | 24 | +| 9.1.1 | Procedures in MSC ..... | 24 | +| 9.1.2 | Procedures in VLR ..... | 28 | +| 9.2 | Terminating network processes..... | 29 | +| 9.2.1 | Procedures in GMSC ..... | 29 | +| 9.2.2 | Procedures in MSC ..... | 30 | +| 9.3 | Procedures common in serving and remote networks..... | 36 | +| 9.4 | Processes used during Active Call ..... | 46 | +| 9.4.1 | Process and procedures in serving MSC ..... | 46 | +| 9.4.2 | Process and procedures in serving VLR..... | 52 | +| 9.4.3 | Process and procedures in remote MSC ..... | 53 | +| 10 | Information stored in the HLR and in the VLR ..... | 57 | +| 10.1 | Information stored in the HLR ..... | 57 | +| 10.2 | Transfer of information from HLR to VLR ..... | 57 | +| 10.3 | Information stored in the VLR ..... | 57 | +| 11 | State transition model..... | 57 | +| 12 | Handover..... | 57 | +| Annex A (informative): | Change history..... | 58 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- 1 Scope + +The present document gives the stage 2 description of the User-to-User signalling supplementary services. + +The User-to-user supplementary service is divided into 3 different services: + +- Service 1 (UUS1) +- Service 2 (UUS2) +- Service 3 (UUS3) + +# --- 2 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 22.087: "User-to-user signalling (UUS); Stage 1". +- [3] 3GPP TS 23.018: "Basic Call Handling – Technical Realization". +- [4] 3GPP TS 23.078: "CAMEL Stage 2". +- [5] 3GPP TS 23.079: "Support for Optimal Routeing (SOR) – Technical Realization". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply. + +**Burst parameter:** parameter indicating the absolute maximum number of UUS 3 service related user information messages that can be sent at intervals indicated by the value of timer T2-UUS3 + +**Remote network:** network of the remote subscriber + +**Remote subscriber:** for service 1 and 2 the remote subscriber is the called party of a call to which the served subscriber activates the UUS supplementary service. For service 3 the remote subscriber can be either the called or the calling party of an established call to whom the use of the UUS supplementary service is requested by the served subscriber + +**Served subscriber:** subscriber who has a provision of the UUS supplementary service and who activates the UUS supplementary service. For service 1 and 2 the served subscriber is always the calling subscriber, for service 3 either the calling or the called subscriber can be the served subscriber + +**Serving network:** network of the served subscriber + +**User-to-User Information (UUI):** information transferred by using the UUS supplementary service + +**UUS Service:** UUS services (Service 1, 2 and 3) are components of the UUS supplementary service. If the UUS supplementary service is provided to a subscriber, he can handle the UUS services independently within a call + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|-------|-----------------------------------| +| ACM | Address Complete Message | +| ANM | ANswer Message | +| CON | CONnect | +| CPG | Call ProGress | +| IAM | Initial Address Message | +| MS | Mobile Station | +| REL | RELease | +| SIFOC | Send Info For Outgoing Call | +| SRI | Send Routing Info | +| UUI | User-to-User Information | +| UUS | User-to-User Signalling | +| UUS1 | User-to-User Signalling Service 1 | +| UUS2 | User-to-User Signalling Service 2 | +| UUS3 | User-to-User Signalling Service 3 | + +Further GSM related abbreviations are listed in GSM 01.04. + +# --- 4 General + +The UUS supplementary service allows the transfer of UUI to a remote subscriber over the signalling channel in association with a call to this subscriber. The UUS supplementary service is divided in Service 1, Service 2 and Service 3. + +The UUS Service 1 allows the transfer of UUI embedded within Call Control messages. + +The UUS Service 2 allows the transfer of UUI with a specific User-to-user message after the served subscriber has received an address complete indication and prior to the answer indication from the B-side. + +The UUS Service 3 allows the transfer of UUI with a specific User-to-user message during an active call. + +For the use of the UUS supplementary service in GSM PLMNs the support of UUS capabilities within the inter-exchange signalling system (e.g. ISUP) is necessary. However this is out of scope of the present document. + +## 4.1 Activation of UUS components + +If any of the UUS Services 1, 2 or 3 shall be used within a call, the UUS capabilities have to be activated by the served subscriber either when initiating this outgoing call (Service 1, 2 and 3) or during an established call (Service 3). + +The UUS capabilities for a call can be requested by means of an implicit request or an explicit request. UUS Service 1 can be requested either implicitly or explicitly. Service 2 and 3 can only be requested explicitly. + +### 4.1.1 Implicit request + +The UUS1 service is activated implicitly by the presence of UUI in the set-up request from the mobile station. The network shall transfer the received UUI transparently to the B-side. For the purpose of UUS service 1 implicitly requested, no explicit check for the availability of UUS capabilities at the destination network has to be performed by the originating network. + +If the calling subscriber has UUS 1 provisioned and implicitly requested, the network shall transfer all UUI contained in call control messages. + +If the calling subscriber has UUS1 not provisioned, the contained UUI shall be discarded by the serving MSC. The call shall be established without further restrictions. + +The served subscriber shall not be informed whether the implicit request was successful or not. + +### 4.1.2 Explicit request + +Any UUS Service can be explicitly activated by the served subscriber within the set-up request initiating a mobile originated call. In addition UUS Service 3 can be activated during an established call with a Facility message. A UUS Service 1 request can be accompanied by appropriate UUI. + +The network shall check for the availability of UUS capabilities for the call by passing the UUS request and the eventually accompanied UUI to the remote side. If a UUS Service is available for the call an appropriate "UUS provided" indication for this UUS Service shall be sent within the first backward message from the remote side. + +A UUS Service shall not be activated for the call if a "UUS not provided" indication or no indication about the availability of this UUS Service is received from the remote side. + +Service 3 can be explicitly activated during an active call by both parties. This may lead to a collision of activation requests. The collision of activation requests occurs when there is an outstanding request for service 3 and a subsequent request is received from the remote user. The entity (user or network) that observes the collision shall reject the second request with Facility message. This leads to the rejection of both requests. + +### 4.1.3 UUS required option + +As an option at call set-up the served subscriber can specify whether the requested UUS Service is required or not required for the call. If service 1 is implicitly requested or if service 3 is requested during the call, it cannot be requested as required. + +If the served subscriber has specified that one of the UUS services is required for the call and this UUS service can not be activated by the network, the call attempt of the served subscriber shall be cleared. + +If the served subscriber has specified that one of the UUS services is not required for the call and this UUS service can not be activated by the network, the call establishment shall be continued. + +# 5 Handling of User-to-user signalling + +## 5.1 Timers + +UUS related timers are needed only for UUS service 3. Timers T1-UUS3, T3-UUS3 and T4-UUS3 are used only when UUS service 3 is requested during an active call. + +**Table 5.1: UUS Timers** + +| Timer | Name | Value | Run at | Started | Stopped | Expiry | +|---------|---------------------------|-------|---------------------------------------------------------------|-----------------------------------------------------|--------------------------------------------------------------------|--------------------------------------------------------------------| +| T1-UUS3 | Remote network control | 10s | MSC of the remote subscriber | UUS3 service request sent to the remote subscriber | Answer to UUS3 service request received from the remote subscriber | Rejection of UUS3 service is sent toward the requesting network | +| T2-UUS3 | UUS3 flow control | 10s | MSC of the served subscriber and MSC of the remote subscriber | The MSC receives service acceptance | When UUS3 service is deactivated | Flow control parameter is incremented. Timer is restarted. Note 1. | +| T3-UUS3 | Served subscriber control | 10s | MS of the served subscriber | UUS3 service request sent to the requesting network | Acceptance to UUS3 service received from requesting network | Consider UUS3 service as not activated | +| T4-UUS3 | Serving network control | 10s | MSC of the served subscriber | UUS3 service request sent to the remote network | Acceptance to UUS3 service received from remote network | Rejection of UUS3 service is sent toward the served subscriber | + +NOTE: If a user information message has been discarded due to flow control, a congestion control message shall be sent to the user. + +## 5.2 Information flows of UUS services + +### 5.2.1 Service 1 (UUS1) + +#### 5.2.1.1 Flow control + +No specific flow control is needed to restrict the amount of messages sent for either implicit or explicit UUS service 1 as the user-to-user information is transferred in call control messages. + +#### 5.2.1.2 Information flows + +![Flowchart for Process MAF043 showing information flows for UUS1. The process starts at 'Idle', proceeds to 'Activation UUS1 request', then checks if 'UUS1 provisioned'. If 'no', it goes to 'Set indication = UUS1 not available'. If 'yes', it goes to 'set indication = UUS1 available'. Both paths lead to 'continue call handling', which then returns to 'Idle'.](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +Process MAF043 + +387\_1(1) + +User-to-user signalling Service 1 authorisations examinations (VLR) + +``` +graph TD; Idle1([Idle]) --> Activation[Activation UUS1 request]; Activation --> Provisioned{UUS1 provisioned}; Provisioned -- no --> SetNotAvailable[Set indication = UUS1 not available]; Provisioned -- yes --> SetAvailable[set indication = UUS1 available]; SetNotAvailable --> Continue{continue call handling}; SetAvailable --> Continue; Continue --> Idle2([Idle]); +``` + +Flowchart for Process MAF043 showing information flows for UUS1. The process starts at 'Idle', proceeds to 'Activation UUS1 request', then checks if 'UUS1 provisioned'. If 'no', it goes to 'Set indication = UUS1 not available'. If 'yes', it goes to 'set indication = UUS1 available'. Both paths lead to 'continue call handling', which then returns to 'Idle'. + +Figure 5.2.1.2: MAF043 + +##### 5.2.1.2.1 Implicit activation + +![Sequence diagram showing information flow for UUS1 implicit request (mobile to mobile call) between MSa, MSCa, VLRa, GMSCb, HLRb, MSCb, and MSb.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +``` + +sequenceDiagram + participant MSa + participant MSCa + participant VLRa + participant GMSCb + participant HLRb + participant MSCb + participant MSb + + Note left of MSa: Note: UUI* User-to-user information required for requesting the UUS service +UUI User-to-user information can be sent optionally + + MSa->>MSCa: Set-up + Note right of MSa: UUI* + MSCa->>VLRa: SIFOC + Note right of MSCa: UUI* + VLRa->>MSCa: Complete call + MSCa->>GMSCb: IAM + Note right of MSCa: UUI* + GMSCb->>HLRb: SRI + HLRb->>GMSCb: SRI ack + GMSCb->>MSCb: IAM + Note right of GMSCb: UUI* + MSCb->>MSb: Set-up + Note right of MSCb: UUI* + MSb->>MSCb: Alert + Note right of MSb: UUI + MSCb->>GMSCb: ACM/ANM/CPG + Note right of MSCb: UUI + GMSCb->>MSCa: ACM/ANM/CPG + Note right of GMSCb: UUI + MSCa->>MSa: Alert + Note right of MSCa: UUI + GMSCb->>MSCb: CON + Note right of GMSCb: UUI + MSCb->>MSCa: CON + Note right of MSCb: UUI + MSCa->>MSa: Connect + Note right of MSCa: UUI + MSa->>MSCa: Disconnect + Note right of MSa: UUI + MSCa->>GMSCb: REL + Note right of MSCa: UUI + GMSCb->>MSCb: REL + Note right of GMSCb: UUI + MSCb->>MSb: Disconnect + Note right of MSCb: UUI + +``` + +Sequence diagram showing information flow for UUS1 implicit request (mobile to mobile call) between MSa, MSCa, VLRa, GMSCb, HLRb, MSCb, and MSb. + +Note: UUI\* User-to-user information required for requesting the UUS service + UUI User-to-user information can be sent optionally + +Figure 5.2.1.2.1.1: Information flow for UUS1 implicit request (mobile to mobile call) + +##### 5.2.1.2.2 Explicit activation + +![Sequence diagram showing information flow for UUS 1 explicit request (mobile to mobile call) between MSa, MSCa, VLRA, GMSCb, HLRb, MSCb, and MSb.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +``` + +sequenceDiagram + participant MSa + participant MSCa + participant VLRA + participant GMSCb + participant HLRb + participant MSCb + participant MSb + + Note left of MSa: Note: + Note left of MSa: S1 UUS Service 1 + Note left of MSa: UUI User-to-user information can be sent optionally + Note left of MSa: r,nr requested, not required + Note left of MSa: p provided + + MSa->>MSCa: Set-up + Note right of MSa: S1=r,nr; UUI + MSCa->>VLRA: SIFOC + VLRA->>MSCa: Complete call + MSCa->>GMSCb: IAM + Note right of MSCa: S1=r,nr; UUI + GMSCb->>HLRb: SRI + HLRb->>GMSCb: SRI ack + GMSCb->>MSCb: IAM + Note right of GMSCb: S1=r,nr; UUI + MSCb->>MSb: Set-up + Note right of MSCb: S1=r,nr; UUI + MSb->>MSCb: Alert + Note right of MSb: S1=p; UUI + MSCb->>GMSCb: ACM/ANM/CPG + Note right of MSCb: S1=p; UUI + GMSCb->>HLRb: CON + Note right of GMSCb: UUI + HLRb->>GMSCb: CON + Note right of HLRb: UUI + GMSCb->>MSCa: CON + Note right of GMSCb: UUI + MSCa->>MSa: Connect + Note right of MSCa: UUI + MSa->>MSCa: Disconnect + Note right of MSa: UUI + MSCa->>GMSCb: REL + Note right of MSCa: UUI + GMSCb->>MSCb: REL + Note right of GMSCb: UUI + MSCb->>MSb: Disconnect + Note right of MSCb: UUI + +``` + +Sequence diagram showing information flow for UUS 1 explicit request (mobile to mobile call) between MSa, MSCa, VLRA, GMSCb, HLRb, MSCb, and MSb. + +Note: + S1 UUS Service 1 + UUI User-to-user information can be sent optionally + r,nr requested, not required + p provided + +Figure 5.2.1.2.2.1: Information flow for UUS 1 explicit request (mobile to mobile call) + +### 5.2.2 Service 2 (UUS2) + +#### 5.2.2.1 Flow control + +Up to two UUI messages can be sent in each direction. If either party tries to send more than two UUI messages, they are discarded. + +#### 5.2.2.2 Information flows + +![Flowchart for Process MAF044 showing information flows for UUS2. The process starts at an 'Idle' state, receives an 'Activation UUS2 request', checks if 'UUS2 provisioned'. If 'no', it goes to 'Set indication = UUS2 not available'. If 'yes', it goes to 'set indication = UUS2 available'. Both paths lead to 'continue call handling', which then returns to an 'Idle' state.](853f59c89931a666c07903b31d098277_img.jpg) + +Process MAF044 + +387\_5(1) + +User-to-user signalling authorisation examination (VLR) + +``` +graph TD; Idle1([Idle]) --> Request{Activation UUS2 request}; Request --> Provisioned{UUS2 provisioned}; Provisioned -- no --> NotAvailable[Set indication = UUS2 not available]; Provisioned -- yes --> Available[set indication = UUS2 available]; NotAvailable --> Continue{continue call handling}; Available --> Continue; Continue --> Idle2([Idle]); +``` + +Flowchart for Process MAF044 showing information flows for UUS2. The process starts at an 'Idle' state, receives an 'Activation UUS2 request', checks if 'UUS2 provisioned'. If 'no', it goes to 'Set indication = UUS2 not available'. If 'yes', it goes to 'set indication = UUS2 available'. Both paths lead to 'continue call handling', which then returns to an 'Idle' state. + +Figure 5.2.2.2: MAF044 + +![Sequence diagram showing information flow for UUS2 explicit request (mobile to mobile call) between MSa, MSCa, VLRa, GMSCb, HLRb, MSCb, and MSb. The diagram illustrates the exchange of messages like Set-up, SIFOC, IAM, SRI, ACM/ANM/CPG, User info, UUI, and CON.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant MSa + participant MSCa + participant VLRa + participant GMSCb + participant HLRb + participant MSCb + participant MSb + + Note left of MSa: Note: S2 UUS Service 2 +UUI User-to-user information +r,nr requested, not required +p provided + + MSa->>MSCa: Set-up +MSCa->>VLRa: SIFOC +VLRa->>MSCa: Complete call +MSCa->>GMSCb: IAM +GMSCb->>HLRb: SRI +HLRb->>GMSCb: SRI ack +GMSCb->>MSCb: IAM +MSCb->>MSb: Set-up +MSb->>MSCb: S2=r,nr +MSCb->>MSb: Alert +MSb->>MSCb: S2=p +MSCb->>GMSCb: ACM/ANM/CPG +GMSCb->>HLRb: S2=p +HLRb->>GMSCb: User info +GMSCb->>MSCb: User info +MSCb->>MSb: User info +MSb->>MSCb: UUI +MSCb->>GMSCb: User info +GMSCb->>HLRb: UUI +HLRb->>GMSCb: User info +GMSCb->>MSCa: CON +MSCa->>MSa: Connect +MSa->>MSCa: User info +MSCa->>MSa: UUI + +``` + +Sequence diagram showing information flow for UUS2 explicit request (mobile to mobile call) between MSa, MSCa, VLRa, GMSCb, HLRb, MSCb, and MSb. The diagram illustrates the exchange of messages like Set-up, SIFOC, IAM, SRI, ACM/ANM/CPG, User info, UUI, and CON. + +Figure 5.2.2.2.1: Information flow for UUS2 explicit request (mobile to mobile call) + +### 5.2.3 Service 3 (UUS3) + +#### 5.2.3.1 Flow control + +Network flow control mechanisms shall exist after the connection has been established in order to restrict the amount of UUI sent in each direction. A burst capability of sending N messages shall immediately be available to each user, where N initially equals the value of the burst parameter X. The value of N shall be decremented by one for every message sent by the user and incremented by Y at regular intervals of T2-UUS3 (see table 5.1). The value of N shall be limited to a maximum of X. + +The value of the burst parameter X shall be 16. + +The value of the replenishment parameter Y shall be 8. + +Network flow control shall be performed only by the sending user's network. + +If the MSC receives UUI messages from the MS at a rate which exceeds the flow control limit, it shall discard the UUI messages that cannot be handled and respond to the first discarded UUI message with a congestion control message. + +When the flow control restrictions are removed, an indication that further UUI messages can be accepted shall be given. See the Processes *Serving\_MSC\_Handle\_UUS\_In\_Active\_Call* and *Remote\_MSC\_Handle\_UUS\_In\_Active\_Call*. + +#### 5.2.3.2 Information flows + +![Flowchart for Process MAF045: Idle -> Activation UUS3 request -> UUS3 provisioned (yes/no) -> set indication = UUS3 available / Set indication = UUS3 not available -> continue call handling -> Idle](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) + +Process MAF045 + +387\_7(1) + +User-to-user signalling service 3 related authorisation examination (VLR) + +``` +graph TD; Idle1([Idle]) --> Request{Activation UUS3 request}; Request --> Provisioned{UUS3 provisioned}; Provisioned -- yes --> Available[set indication = UUS3 available]; Provisioned -- no --> NotAvailable[Set indication = UUS3 not available]; Available --> Continue{continue call handling}; NotAvailable --> Continue; Continue --> Idle2([Idle]); +``` + +Flowchart for Process MAF045: Idle -> Activation UUS3 request -> UUS3 provisioned (yes/no) -> set indication = UUS3 available / Set indication = UUS3 not available -> continue call handling -> Idle + +Figure 5.2.3.2: MAF045 + +![Sequence diagram showing information flow for UUS3 explicit request during call establishment (mobile to mobile call) between MSa, MSCa, VLRa, GMSCb, HLRb, MSCb, and MSb.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant MSa + participant MSCa + participant VLRa + participant GMSCb + participant HLRb + participant MSCb + participant MSb + + MSa->>MSCa: Set-up (S3=r,nr) + MSCa->>VLRa: SIFOC + VLRa->>MSCa: Complete call + MSCa->>GMSCb: IAM (S3=r,nr) + GMSCb->>HLRb: SRI + HLRb->>GMSCb: SRI ack + GMSCb->>MSCb: IAM (S3=r,nr) + MSCb->>MSb: Set-up (S3=r,nr) + MSb->>MSCb: Alert + MSCb->>GMSCb: ACM/ANM/CPG + GMSCb->>MSCa: ACM/ANM/CPG + MSCa->>MSa: Alert + MSb->>MSCb: Connect (S3=p) + MSCb->>GMSCb: CON (S3=p) + GMSCb->>MSCa: CON (S3=p) + MSCa->>MSa: Connect (S3=p) + MSa->>MSCa: User info (UUI) + MSCa->>GMSCb: User info (UUI) + GMSCb->>MSCb: User info (UUI) + MSCb->>MSb: User info (UUI) + MSb->>MSCb: User info (UUI) + MSCb->>GMSCb: User info (UUI) + GMSCb->>MSCa: User info (UUI) + MSCa->>MSa: User info (UUI) + MSb->>MSCb: Disconnect + MSCb->>GMSCb: REL + GMSCb->>MSCa: REL + MSCa->>MSa: Disconnect + +``` + +Note: + S3       UUS Service 3 + UUI     User-to-user information + r,nr    requested, not required + p       provided + +Sequence diagram showing information flow for UUS3 explicit request during call establishment (mobile to mobile call) between MSa, MSCa, VLRa, GMSCb, HLRb, MSCb, and MSb. + +**Figure 5.2.3.2.1: Information flow for UUS3 explicit request during call establishment (mobile to mobile call)** + +![](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant MSa + participant MSCa + participant VLRa + participant GMSCb + participant HLRb + participant MSCb + participant MSb + + Note over MSa, MSb: Active call A-B + MSa->>MSCa: Facility (S3=r) + MSCa->>VLRa: Uus act + VLRa-->>MSCa: Uus act ack + MSCa->>GMSCb: Facility (S3=r) + GMSCb->>MSCb: Facility (S3=r) + MSCb->>MSb: Facility (S3=r) + MSb->>MSCb: Facility (S3=p) + MSCb->>GMSCb: Facility (S3=p) + GMSCb->>MSCa: Facility (S3=p) + MSCa->>MSa: Facility (S3=p) + MSa->>MSCa: User info (UUI) + MSCa->>GMSCb: User info (UUI) + GMSCb->>MSCb: User info (UUI) + MSCb->>MSb: User info (UUI) + MSb->>MSCb: User info (UUI) + MSCb->>GMSCb: User info (UUI) + GMSCb->>MSCa: User info (UUI) + MSCa->>MSa: User info (UUI) + MSa->>MSCa: Disconnect + MSCa->>GMSCb: REL + GMSCb->>MSCb: REL + MSCb->>MSb: Disconnect + +``` + +Note: + S3       UUS Service 3 + UUI     User-to-user information + r         requested + p         provided + +**Figure 5.2.3.2.2: Information flow for UUS3 explicit request during active call (mobile to mobile call)** + +## 5.3 Messages and their contents + +This subclause contains the detailed description of the information flows used by UUS. + +Each Information Element, IE is marked as (M) Mandatory, (C) Conditional, or (O) Optional. A mandatory information element shall always be present. A conditional information element shall be present if certain conditions are fulfilled; if those conditions are not fulfilled it shall be absent. An optional information element may be present or absent, at the discretion of the application at the sending entity. This categorisation is a functional classification, i.e. stage 2 information and not a stage 3 classification to be used for the protocol. + +The stage 2 and stage 3 message and information element names are not necessarily identical. + +### 5.3.1 Information elements used in the messages + +The following UUS specific constructed information elements are used in the messages. + +**Table 5.3.1.1: UUS specific information elements** + +| Parent Information Element | Child Information Element name | Information element Required | Information element description | +|----------------------------|--------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| UUS options | UUS1 | C | The information element is present if UUS1 service is requested; otherwise it shall be absent. It may contain the following values:
- Required
- Not Required | +| | UUS2 | C | The information element is present if UUS2 service is requested; otherwise it shall be absent. It may contain the following values:
- Required
- Not Required | +| | UUS3 | C | The information element is present if UUS3 service is requested; otherwise it shall be absent. It may contain the following values:
- Required
- Not Required | +| UUS provision | UUS1 | C | If UUS1 services is requested and provisioned the information element is present, otherwise it shall be absent. | +| | UUS2 | C | If UUS2 services is requested and provisioned the information element is present, otherwise it shall be absent. | +| | UUS3 | C | If UUS3 services is requested and provisioned the information element is present, otherwise it shall be absent. | + +### 5.3.2 Messages between MS and MSC + +Call control messages (Setup, Alert, Connect, Disconnect, Release and Release Complete, refer to GSM 04.08) may carry UUS service activation request and response. They can carry also UUI for UUS1. + +Facility message, refer to GSM 04.08, can carry UUS service 3 activation request and response. + +Dedicated User-To-User message, refer to GSM 04.08, carries UUI for UUS service 2 and 3. + +These messages are used both in serving and remote networks. + +### 5.3.3 Messages between MSC and VLR (B interface) + +These messages are used in the serving network. + +**Table 5.3.3.1: Messages between MSC and VLR** + +| Message | Message sender | Information element name | Information element Required | Information element description | +|-----------------------------------------------|----------------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Send Info For Outgoing Call | MSC | - | - | Refer to GSM 03.18. | +| | | UUS options | C | In addition:
The information element is present if MS A requested UUS service; otherwise it shall be absent. The structure of UUS options is defined in table 5.3.1.1 | +| Send Info For Outgoing Call negative response | VLR | - | - | Refer to GSM 03.18 | +| | | UUS reject | C | In addition:
The information element is present, if required UUS service was requested by MS A and service is not provided, otherwise it shall be absent. | +| Complete Call | VLR | - | - | Refer to GSM 03.18 | +| | | UUS provision | C | In addition:
The information element is present if MS A requested UUS service(s); otherwise it shall be absent. The structure of UUS Provision is defined in table 5.3.1.1 | +| Send Info For UUS3 | MSC | - | - | The message is sent when UUS3 service is requested during active call. NOTE: This message is used in serving and remote MSCs. | +| Send Info For UUS3 Ack | VLR | UUS provision | C | The information element is present if UUS3 service is provisioned; otherwise it shall be absent | + +### 5.3.4 Messages between MSC – MSC (E interface) + +These messages are used in the remote network when UUS is supported in remote MSC in conjunction of SOR, refer to GSM 03.79. + +**Table 5.3.4.1: Messages between MSC – MSC** + +| Message | Message sender | Information element name | Information element Required | Information element description | +|----------------------|----------------|--------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Resume Call Handling | MSCB | - | - | Refer to GSM 03.79. | +| | | UUS1 Service request | C | In addition:
The information element is present if UUS1 Service was requested in the original call and remote MSC supports UUS service; otherwise it shall be absent. | +| | | UUS2 Service request | C | The information element is present if UUS2 Service was requested in the original call and remote MSC supports UUS service; otherwise it shall be absent | +| | | UUS3 Service request | C | The information element is present if UUS3 Service was requested in the original call and remote MSC supports UUS service; otherwise it shall be absent. | +| | | UUS1 UUI | C | The information element is present if UUS1 UUI was present in the original call and remote MSC supports UUS service; otherwise it shall be absent. | +| | | UUS CF interaction | C | The information element is present if the remote subscriber has accepted UUS1 service request and call forwarding or call deflection has been activated after that; otherwise it shall be absent. | + +# --- 6 Interaction with other supplementary services + +GSM 02.87 specifies interaction of UUS with other supplementary services. Additional details are provided in this clause. + +## 6.1 Call forwarding unconditional (CFU) + +No impact. + +## 6.2 Call forwarding on mobile subscriber busy (CFB) + +No impact, if CFB is invoked due to a NDUB condition or due to UDUB before an alerting message was received from the mobile station. + +If CFB is invoked due to a UDUB indication from the B forwarding subscriber the same interaction as for CFNRy shall apply. + +## 6.3 Call forwarding on no reply (CFNRy) + +If UUS Service 1 is implicitly requested for a call to a subscriber who has Call Forwarding on no reply active and operative, the forwarding MSC shall store the UUI. If CFNRy is invoked, the stored UUI shall be forwarded with the call. + +If UUS Service 1 is explicitly requested as not required for a call to a subscriber who has Call Forwarding on no reply active and operative, the forwarding MSC shall store UUS 1 service request and UUI, if any. If the forwarding user accepts the UUS1 supplementary service request in the Alerting message, the CFNRy supplementary service can be invoked and the stored UUS1 service request and UUI, if any, shall be forwarded with the call. If the forwarding user rejects the UUS1 supplementary service request or does not include a response related to it in the Alerting message, then the CFNRy supplementary service can be invoked but the UUS1 service request and UUI, if any, shall not be forwarded with the call. + +If UUS Service 1 is explicitly requested as required for a call to a subscriber who has Call Forwarding on no reply active and operative and the no reply condition timer expires, the remote MSC shall release the call towards the calling subscriber. + +If Call Forwarding on no reply is invoked for a call for which UUS Service 2 was requested as not required, UUS Service 2 shall not be requested for the forwarding leg, i.e. UUS 2 is no longer available for the call. + +Call Forwarding on no reply shall not be invoked if UUS Service 2 was requested required for the initial mobile terminated call. + +If UUS Service 3 is requested for a call to a subscriber who has Call Forwarding on no reply active and operative, the forwarding MSC shall store the UUS3 request. If CFNRy is invoked the UUS3 request shall be forwarded with the call. + +For further details refer to procedures UUS\_ICH\_Check\_Forwarding and UUS\_MSC\_Clear\_UUS. + +## 6.4 Call forwarding on mobile subscriber not reachable (CFNRc) + +No impact. + +## 6.5 Call waiting (CW) + +No impact. + +## 6.6 Call hold (HOLD) + +No impact. + +## 6.7 Completion of calls to busy subscribers (CCBS) + +Requests for the activation of the UUS supplementary service contained in the original call request shall be maintained along with other call information used for the CCBS supplementary service. + +The network shall also store any UUI containing in the original call request and use this stored UUI in the CCBS call. + +## 6.8 Explicit call transfer (ECT) + +When calls are transferred as a result of invocation of explicit call transfer supplementary service, the UUS supplementary service activated on either of the calls prior to the invocation of the explicit call transfer supplementary service shall be cancelled by the network. + +No specific notification shall be sent to the users on the resulting call when the UUS supplementary service is no longer activated. + +The users on the resulting call can request service 3 again, if required. + +## 6.9 Multi party service (MPTY) + +No impact. + +## 6.10 Advice of charge (AoC) + +No impact. + +## 6.11 Barring of outgoing calls (BAOC) + +No impact. + +## 6.12 Barring of outgoing international calls (BOIC) + +No impact. + +## 6.13 Barring of outgoing international calls except those directed to the home PLMN country (BOIC-exHC) + +No impact. + +## 6.14 Barring of incoming calls (BAIC) + +No impact. + +## 6.15 Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam) + +No impact. + +## 6.16 Call deflection (CD) + +If Call Deflection is invoked before alerting there is no impact. + +If Call Deflection is invoked after alerting the same interactions as for Call forwarding on no reply shall apply. + +# --- 7 Interaction with other network features + +## 7.1 Customised Applications for Mobile network Enhanced Logic (CAMEL) + +No impact. + +## 7.2 Support for Optimal Routeing(SOR) + +The invocation of Optimal Routeing in case of late call forwarding shall have no impact on the interactions of UUS with the call forwarding supplementary services as defined in clause 6. + +The UUS request, UUI and UUS CF interaction indicator, if any, shall be added to the Resume Call Handling message in remote MSC when SOR late call forwarding is applied. For details refer to the procedure UUS\_ICH\_Handle\_LCF in SDLs and the procedure Handle\_ORLCF\_VMSC (see GSM 03.79). + +The UUS request and UUI, if any, shall be copied from the Resume Call Handling message to the IAM in GMSC when SOR late call forwarding is applied. For details refer to the procedure UUS\_GMSC\_Check\_Forwarding in SDLs and the procedure OR\_Handle\_RCH (see GSM 03.79). + +If UUS CF interaction indicator was present in Resume Call Handling message, the presence of UUS1 Service acceptance and UUI, if any, shall be modified during call setup time. For further details refer to the procedure MT\_CF\_MSC (see GSM 03.18) and UUS\_MSC\_Clear\_UUS. + +# --- 8 Interworking with other networks + +## 8.1 Interworking with GSM PLMN/ISDN network supporting only a maximum User-user information element length of 35 octets + +If interworking occurs with a network supporting only a maximum of User-user information element length of 35 octets, no notification shall be given to the calling user or called user sending the user information. + +## 8.2 Interworking with non-ISDN network + +In the case of interworking with non-ISDN network or with a non-ISDN called user, a progress indicator information element indicating #1 "call is not end-to-end ISDN; further progress information may be available in-band" or #2 "destination address is non-ISDN", respectively, is sent to the calling user as part of basic call. + +This progress information shall serve as indication that the requested service cannot be guaranteed. + +# --- 9 Network entity functions + +## 9.1 Originating network processes + +### 9.1.1 Procedures in MSC + +Figure 9.1.1.1 Procedure UUS\_OCH\_Check\_Setup + +This procedure is called when Setup is received from A-subscriber. It sets requested UUS service options into SIFOC message. + +Figure 9.1.1.2 Procedure UUS\_OCH\_Set\_Info\_In\_IAM + +Requested UUS service options and possible UUS1 data is copied in IAM. The procedure is controlled by the Complete Call message parameters from the VLR. + +Figure 9.1.1.3 Procedure UUS\_OCH\_Set\_Alert\_And\_Connect\_Param + +In this procedure UUS related parameters are checked and set into the Alerting/Connect message that is sent to A-subscriber. If any of the UUS services is requested as required and positive service acknowledgement is not received from the remote end, the check will fail and the call will be cleared. + +![Flowchart for Procedure UUS_OCH_Check_Setup. It starts with a connector, then checks if UUS1, UUS2, and UUS3 are requested. If requested, it checks if they are required. Depending on the result, it sets the parameter to 'required' or 'not required' in SIFOC. The flowchart ends with an exit connector. A note indicates this procedure runs in the MSC to set UUS specific parameters. Another note indicates 'Either implicit or explicit request' for the UUS1 requested check.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Procedure UUS\_OCH\_Check\_Setup 1(1) + +``` +graph TD; Start([ ]) --> UUS1_Req{UUS1 requested}; UUS1_Req -- No --> UUS2_Req{UUS2 requested}; UUS1_Req -- Yes --> UUS1_ReqAsReq{Requested as required}; UUS1_ReqAsReq -- No --> SetUUS1_NotReq[Set UUS1 "not required" to SIFOC]; UUS1_ReqAsReq -- Yes --> SetUUS1_Req[Set UUS1 "required" to SIFOC]; SetUUS1_Req --> Join1(( )); SetUUS1_NotReq --> Join1; Join1 --> UUS2_Req; UUS2_Req -- No --> UUS3_Req{UUS3 requested}; UUS2_Req -- Yes --> UUS2_ReqAsReq{Requested as required}; UUS2_ReqAsReq -- No --> SetUUS2_NotReq[Set UUS2 "not required" to SIFOC]; UUS2_ReqAsReq -- Yes --> SetUUS2_Req[Set UUS2 "required" to SIFOC]; SetUUS2_Req --> Join2(( )); SetUUS2_NotReq --> Join2; Join2 --> UUS3_Req; UUS3_Req -- No --> End(( )); UUS3_Req -- Yes --> UUS3_ReqAsReq{Requested as required}; UUS3_ReqAsReq -- No --> SetUUS3_NotReq[Set UUS3 "not required" to SIFOC]; UUS3_ReqAsReq -- Yes --> SetUUS3_Req[Set UUS3 "required" to SIFOC]; SetUUS3_Req --> Join3(( )); SetUUS3_NotReq --> Join3; Join3 --> End; +``` + +This procedure is running in the MSC and sets the UUS specific parameters to SIFOC message + +Either implicit or explicit request + +Flowchart for Procedure UUS\_OCH\_Check\_Setup. It starts with a connector, then checks if UUS1, UUS2, and UUS3 are requested. If requested, it checks if they are required. Depending on the result, it sets the parameter to 'required' or 'not required' in SIFOC. The flowchart ends with an exit connector. A note indicates this procedure runs in the MSC to set UUS specific parameters. Another note indicates 'Either implicit or explicit request' for the UUS1 requested check. + +Figure 9.1.1.1: Procedure UUS\_OCH\_Check\_Setup + +![Flowchart for Procedure UUS_OCH_Set_Info_In_IAM. The process starts with a connector symbol and checks if UUS1 is requested. If no, it checks if UUS1 is provisioned. If not provisioned, it exits. If provisioned, it checks if it's an implicit request. If yes, it sets UUS1 implicit active to True and copies UUS data to IAM. If no, it checks if requested as required. If yes, it sets S1:=r,r and copies S1 to IAM. If no, it sets S1:=r,nr and copies S1 to IAM. After copying S1, it checks if UUS1 data is present. If yes, it copies UUS data to IAM. Both paths lead to a junction. From the junction, it checks if UUS2 is requested. If yes, it checks if UUS2 is provisioned. If provisioned, it checks if requested as required. If yes, it sets S2:=r,r and copies S2 to IAM. If no, it sets S2:=r,nr and copies S2 to IAM. Both paths lead to connector 1. From connector 1, it checks if UUS3 is requested. If yes, it checks if UUS3 is provisioned. If provisioned, it checks if requested as required. If yes, it sets S3:=r,r and copies S3 to IAM. If no, it sets S3:=r,nr and copies S3 to IAM. Both paths lead to a final connector symbol.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +### Procedure UUS\_OCH\_Set\_Info\_In\_IAM + +1(1) + +This procedure is running in the MSC and it sets the UUS specific parameters to the IAM message + +S1 = UUS Service 1 +S2 = UUS Service 2 +S3 = UUS Service 3 +r,nr = requested, not required +r,r = requested, required + +``` +graph TD; Start([ ]) --> UUS1_Req{UUS1 requested}; UUS1_Req -- No --> UUS1_Prov{UUS1 provisioned}; UUS1_Prov -- No --> End1(( )); UUS1_Prov -- Yes --> Implicit{Implicit request}; Implicit -- No --> ReqAsReq{Requested as required}; ReqAsReq -- No --> S1_nr[S1:=r,nr]; ReqAsReq -- Yes --> S1_r[S1:=r,r]; S1_nr --> CopyS1[Copy S1 to IAM]; S1_r --> CopyS1; CopyS1 --> UUS1_Data{UUS1 data present}; UUS1_Data -- No --> Junction(( )); UUS1_Data -- Yes --> CopyUUS1[Copy UUS data to IAM]; Implicit -- Yes --> UUS1_Imm[UUS1 implicit active:=True]; UUS1_Imm --> CopyUUS1; CopyUUS1 --> Junction; Junction --> UUS2_Req{UUS2 requested}; UUS2_Req -- No --> Junction; UUS2_Req -- Yes --> UUS2_Prov{UUS2 provisioned}; UUS2_Prov -- No --> Junction; UUS2_Prov -- Yes --> ReqAsReq2{Requested as required}; ReqAsReq2 -- No --> S2_nr[S2:=r,nr]; ReqAsReq2 -- Yes --> S2_r[S2:=r,r]; S2_nr --> CopyS2[Copy S2 to IAM]; S2_r --> CopyS2; CopyS2 --> Junction; Junction --> Connector1((1)); Connector1 --> UUS3_Req{UUS3 requested}; UUS3_Req -- No --> End2(( )); UUS3_Req -- Yes --> UUS3_Prov{UUS3 provisioned}; UUS3_Prov -- No --> End2; UUS3_Prov -- Yes --> ReqAsReq3{Requested as required}; ReqAsReq3 -- No --> S3_nr[S3:=r,nr]; ReqAsReq3 -- Yes --> S3_r[S3:=r,r]; S3_nr --> CopyS3[Copy S3 to IAM]; S3_r --> CopyS3; CopyS3 --> End2; +``` + +Flowchart for Procedure UUS\_OCH\_Set\_Info\_In\_IAM. The process starts with a connector symbol and checks if UUS1 is requested. If no, it checks if UUS1 is provisioned. If not provisioned, it exits. If provisioned, it checks if it's an implicit request. If yes, it sets UUS1 implicit active to True and copies UUS data to IAM. If no, it checks if requested as required. If yes, it sets S1:=r,r and copies S1 to IAM. If no, it sets S1:=r,nr and copies S1 to IAM. After copying S1, it checks if UUS1 data is present. If yes, it copies UUS data to IAM. Both paths lead to a junction. From the junction, it checks if UUS2 is requested. If yes, it checks if UUS2 is provisioned. If provisioned, it checks if requested as required. If yes, it sets S2:=r,r and copies S2 to IAM. If no, it sets S2:=r,nr and copies S2 to IAM. Both paths lead to connector 1. From connector 1, it checks if UUS3 is requested. If yes, it checks if UUS3 is provisioned. If provisioned, it checks if requested as required. If yes, it sets S3:=r,r and copies S3 to IAM. If no, it sets S3:=r,nr and copies S3 to IAM. Both paths lead to a final connector symbol. + +Figure 9.1.1.2: Procedure UUS\_OCH\_Set\_Info\_In\_IAM + +![Flowchart for Procedure UUS_OCH_Set_Alert_And_Connect_Param. It starts with a connector, then checks if UUS1 is requested. If yes, it calls UUS_MSC_Check_UUS1. If no, it checks if UUS2 is requested. If UUS2 is requested, it calls UUS_MSC_Check_UUS2. If no, it checks if UUS3 is requested. If UUS3 is requested, it calls UUS_MSC_Check_UUS3. If no, it calls UUS_MSC_Check_UUS1_UUI. The process then results in either 'Pass' or 'Fail' and ends at a connector.](26d664119ad25250780f554633444e54_img.jpg) + +Procedure UUS\_OCH\_Set\_Alert\_And\_Connect\_Param 1(1) + +``` +graph TD; Start([ ]) --> UUS1{UUS1 requested}; UUS1 -- Yes --> UUS1_MSC[UUS_MSC_Check_UUS1]; UUS1 -- No --> UUS2{UUS2 requested}; UUS2 -- Yes --> UUS2_MSC[UUS_MSC_Check_UUS2]; UUS2 -- No --> UUS3{UUS3 requested}; UUS3 -- Yes --> UUS3_MSC[UUS_MSC_Check_UUS3]; UUS3 -- No --> UUS1_UUI[UUS_MSC_Check_UUS1_UUI]; UUS1_MSC --> UUS2; UUS2_MSC --> UUS3; UUS3_MSC --> UUS1_UUI; UUS1_UUI --> Result{Result := Pass / Fail}; Result -- Pass --> End([X]); Result -- Fail --> End; +``` + +This procedure is running in the MSC and it sets the UUS parameters to the call control messages directed back to the initiating MS + +Flowchart for Procedure UUS\_OCH\_Set\_Alert\_And\_Connect\_Param. It starts with a connector, then checks if UUS1 is requested. If yes, it calls UUS\_MSC\_Check\_UUS1. If no, it checks if UUS2 is requested. If UUS2 is requested, it calls UUS\_MSC\_Check\_UUS2. If no, it checks if UUS3 is requested. If UUS3 is requested, it calls UUS\_MSC\_Check\_UUS3. If no, it calls UUS\_MSC\_Check\_UUS1\_UUI. The process then results in either 'Pass' or 'Fail' and ends at a connector. + +Figure 9.1.1.3: Procedure UUS\_OCH\_Set\_Alert\_And\_Connect\_Param + +### 9.1.2 Procedures in VLR + +Figure 9.1.2.1 Procedure UUS\_OCH\_Check\_Provision. + +This procedure is called in the VLR during subscription checks for an outgoing call. It sets requested UUS service provision information in Complete call message. If any of the UUS services is requested as required and the service is not provided to the subscription, the check will fail and the call will be cleared. + +![Flowchart for Procedure UUS_OCH_Check_Provision. The process starts with a connector symbol and enters a loop for UUS1. It checks if UUS1 is requested. If no, it skips to the UUS2 check. If yes, it checks if UUS1 is provisioned. If not provisioned, it checks if UUS1 is required. If required, the result is Fail. If not required, it skips to the UUS2 check. If provisioned, it sets UUS1 'provisioned' to Complete Call and then checks UUS2. The same logic applies to UUS2 and UUS3. If all checks pass, the result is Pass. A note indicates this procedure runs in the VLR for UUS specific provisioning checks.](392a79ccd95e682ccd08f35ab2e64144_img.jpg) + +Procedure UUS\_OCH\_Check\_Provision 1(1) + +``` +graph TD + Start([ ]) --> UUS1_Req{UUS1 requested} + UUS1_Req -- No --> UUS2_Req{UUS2 requested} + UUS1_Req -- Yes --> UUS1_Prov{UUS1 provisioned} + UUS1_Prov -- No --> UUS1_Reqd{UUS1 required} + UUS1_Reqd -- Yes --> Fail[Result := Fail] + UUS1_Reqd -- No --> UUS2_Req + UUS1_Prov -- Yes --> SetUUS1[Set UUS1 "provisioned" to Complete Call] + SetUUS1 --> UUS2_Req + UUS2_Req -- No --> UUS3_Req{UUS3 requested} + UUS2_Req -- Yes --> UUS2_Prov{UUS2 provisioned} + UUS2_Prov -- No --> UUS2_Reqd{UUS2 required} + UUS2_Reqd -- Yes --> Fail + UUS2_Reqd -- No --> UUS3_Req + UUS2_Prov -- Yes --> SetUUS2[Set UUS2 "provisioned" to Complete Call] + SetUUS2 --> UUS3_Req + UUS3_Req -- No --> Pass[Result := Pass] + UUS3_Req -- Yes --> UUS3_Prov{UUS3 provisioned} + UUS3_Prov -- No --> UUS3_Reqd{UUS3 required} + UUS3_Reqd -- Yes --> Fail + UUS3_Reqd -- No --> Pass + UUS3_Prov -- Yes --> SetUUS3[Set UUS3 "provisioned" to Complete Call] + SetUUS3 --> Pass + Fail --> SetNeg[Set negative response := UUS Reject] + SetNeg --> Fail + Pass --> End([ ]) + Fail --> End +``` + +This procedure is running in the VLR and it does the UUS specific provisioning checks + +Flowchart for Procedure UUS\_OCH\_Check\_Provision. The process starts with a connector symbol and enters a loop for UUS1. It checks if UUS1 is requested. If no, it skips to the UUS2 check. If yes, it checks if UUS1 is provisioned. If not provisioned, it checks if UUS1 is required. If required, the result is Fail. If not required, it skips to the UUS2 check. If provisioned, it sets UUS1 'provisioned' to Complete Call and then checks UUS2. The same logic applies to UUS2 and UUS3. If all checks pass, the result is Pass. A note indicates this procedure runs in the VLR for UUS specific provisioning checks. + +Figure 9.1.2.1: Procedure UUS\_OCH\_Check\_Provision + +## 9.2 Terminating network processes + +### 9.2.1 Procedures in GMSC + +Figure 9.2.1.1 Procedure UUS\_GMSC\_Check\_Forwarding. + +This procedure is called when Resume Call Handling message is received from the remote MSC. If the message contains UUS related information, that is copied to the subsequent IAM message. + +![Flowchart for Procedure UUS_GMSC_Check_Forwarding](e29665b8abcea967ef289c6aff07ae4c_img.jpg) + +Procedure UUS\_GMSC\_Check\_Forwarding + +1(1) + +``` +graph TD; Start([ ]) --> D1{UUS data received in RCH message?}; D1 -- No --> End1(( )); D1 -- Yes --> D2{UUS CF interaction set in RCH message?}; D2 -- No --> End2(( )); D2 -- Yes --> P1[UUS CF interaction := True]; P1 --> P2[Add received UUS information to IAM]; P2 --> End3(( )); +``` + +This procedure is running in the GMSC and it checks whether UUS specific data shall be forwarded in the optimal routing case + +The flowchart illustrates the procedure UUS\_GMSC\_Check\_Forwarding. It begins with a start symbol (oval with vertical lines) leading to a decision diamond: "UUS data received in RCH message?". If the answer is "No", the process ends at a connector symbol (circle with an X). If the answer is "Yes", it proceeds to another decision diamond: "UUS CF interaction set in RCH message?". If the answer is "No", the process ends at another connector symbol. If the answer is "Yes", it proceeds to a process box: "UUS CF interaction := True", which then leads to a process box: "Add received UUS information to IAM", which finally leads to a third connector symbol. + +Flowchart for Procedure UUS\_GMSC\_Check\_Forwarding + +Figure 9.2.1.1: Procedure UUS\_GMSC\_Check\_Forwarding + +### 9.2.2 Procedures in MSC + +Figure 9.2.2.1 Procedure UUS\_ICH\_Check\_Support. + +This procedure is called after Alerting/Connect message is received from B-subscriber. It checks whether UUS service is possible and if not whether the call setup can be continued. + +Figure 9.2.2.2 Procedure UUS\_ICH\_Check\_Forwarding. + +This procedure is called when no reply is received from B-subscriber. It checks whether call forwarding is allowed from UUS service point of view. + +Figure 9.2.2.3 Procedure UUS\_ICH\_Handle\_LCF. + +This procedure is used to add UUS information to Resume Call Handling message when Optimal Routeing late call forwarding is supported. + +Figure 9.2.2.4 Procedure UUS\_ICH\_Set\_Info\_In\_IAM. + +This procedure is used to add UUS specific information to forwarded call IAM message. + +Figure 9.2.2.5 Procedure UUS\_ICH\_UUS1\_Implicit\_Active. + +This procedure is used to set UUS1 implicit service active at the remote MSC when only UUI for service 1 is received. + +![Flowchart for Procedure UUS_ICH_Check_Support. It starts with a connector, then checks if UUS1 is requested. If No, it calls UUS_MSC_Check_UUS1. If Yes, it proceeds to check if UUS2 is requested. If UUS2 is requested and Yes, it calls UUS_MSC_Check_UUS2. If No, it proceeds to check if UUS3 is requested. If UUS3 is requested and Yes, it calls UUS_MSC_Check_UUS3. If No, it proceeds to Set UUS options to first backward message. If UUS1 is requested and Yes, it proceeds to Set UUS options to first backward message. After Set UUS options, it calls UUS_MSC_Check_UUS1_UUI. Finally, it results in Pass or Fail.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +### Procedure UUS\_ICH\_Check\_Support + +1(1) + +``` +graph TD; Start(( )) --> UUS1_Req{UUS1 requested}; UUS1_Req -- No --> UUS1_MSC[UUS_MSC_Check_UUS1]; UUS1_Req -- Yes --> UUS2_Req{UUS2 requested}; UUS1_MSC -- Pass --> UUS2_Req; UUS2_Req -- No --> UUS3_Req{UUS3 requested}; UUS2_Req -- Yes --> UUS2_MSC[UUS_MSC_Check_UUS2]; UUS2_Req -- Fail --> UUS3_Req; UUS2_MSC -- Pass --> UUS3_Req; UUS3_Req -- No --> SetOptions[Set UUS options to first backward message]; UUS3_Req -- Yes --> UUS3_MSC[UUS_MSC_Check_UUS3]; UUS3_MSC -- Pass --> SetOptions; UUS3_Req -- Fail --> SetOptions; SetOptions --> UUS1_UUI[UUS_MSC_Check_UUS1_UUI]; UUS1_UUI --> Result[Result:= Pass]; Result --> End(( )); SetOptions --> UUS1_UUI; UUS1_UUI --> Result[Result:= Fail]; Result --> End(( )); +``` + +This procedure is running in the MSC and it checks UUS related parameters + +S1 = UUS Service 1 +p = service is provided by the remote MS + +From the originating GMSC + +From the originating GMSC + +From the originating GMSC + +NOTE: UUS options is never set for implicit UUS1 service + +Flowchart for Procedure UUS\_ICH\_Check\_Support. It starts with a connector, then checks if UUS1 is requested. If No, it calls UUS\_MSC\_Check\_UUS1. If Yes, it proceeds to check if UUS2 is requested. If UUS2 is requested and Yes, it calls UUS\_MSC\_Check\_UUS2. If No, it proceeds to check if UUS3 is requested. If UUS3 is requested and Yes, it calls UUS\_MSC\_Check\_UUS3. If No, it proceeds to Set UUS options to first backward message. If UUS1 is requested and Yes, it proceeds to Set UUS options to first backward message. After Set UUS options, it calls UUS\_MSC\_Check\_UUS1\_UUI. Finally, it results in Pass or Fail. + +Figure 9.2.2.1: Procedure UUS\_ICH\_Check\_Support + +![Flowchart for Procedure UUS_ICH_Check_Forwarding. It starts with a connector, then checks if UUS1 is present. If no, it goes to Result:= Fail. If yes, it checks for an explicit request. If no, it goes to Result:= Fail. If yes, it checks if requested as required. If no, it goes to Result:= Fail. If yes, it checks if UUS1 explicit active. If true, it sets UUS CF interaction := True. If false, it clears stored UUS1 service request (and UUI). Both lead to checking if UUS2 is present. If UUS2 is not present, it goes to Result:= Fail. If UUS2 is present, it checks if requested as required. If yes, it goes to Result:= Fail. If no, it clears stored UUS2 service request and goes to Result:= Pass. If UUS2 requested as required is yes, it goes to Result:= Pass.](dd5771673aececa53d42ece89218299d_img.jpg) + +Procedure UUS\_ICH\_Check\_Forwarding + +1(1) + +``` +graph TD; Start([ ]) --> UUS1_present{UUS1 present}; UUS1_present -- No --> Fail1[Result:= Fail]; UUS1_present -- Yes --> Explicit_request{Explicit request}; Explicit_request -- No --> Fail2[Result:= Fail]; Explicit_request -- Yes --> Requested_required1{requested as required}; Requested_required1 -- No --> Fail3[Result:= Fail]; Requested_required1 -- Yes --> UUS1_active{UUS1 explicit active?}; UUS1_active -- True --> Set_CF[UUS CF interaction := True]; UUS1_active -- False --> Clear_UUS1[Clear stored UUS1 service request (and UUI)]; Set_CF --> UUS2_present{UUS2 present}; Clear_UUS1 --> UUS2_present; UUS2_present -- No --> Fail4[Result:= Fail]; UUS2_present -- Yes --> Requested_required2{requested as required}; Requested_required2 -- No --> Clear_UUS2[Clear stored UUS2 service request]; Requested_required2 -- Yes --> Fail5[Result:= Fail]; Clear_UUS2 --> Pass1[Result:= Pass]; Pass1 --> End1(( )); Fail4 --> End2(( )); Fail5 --> End3(( )); Pass2[Result:= Pass] --> End4(( )); +``` + +This procedure is running in the MSC and it checks whether UUS can be forwarded and if call forwarding is allowed. +NOTE: UUS CF interaction flag is set if UUS1 service request response was sent to the serving nw and CF happens after that + +Flowchart for Procedure UUS\_ICH\_Check\_Forwarding. It starts with a connector, then checks if UUS1 is present. If no, it goes to Result:= Fail. If yes, it checks for an explicit request. If no, it goes to Result:= Fail. If yes, it checks if requested as required. If no, it goes to Result:= Fail. If yes, it checks if UUS1 explicit active. If true, it sets UUS CF interaction := True. If false, it clears stored UUS1 service request (and UUI). Both lead to checking if UUS2 is present. If UUS2 is not present, it goes to Result:= Fail. If UUS2 is present, it checks if requested as required. If yes, it goes to Result:= Fail. If no, it clears stored UUS2 service request and goes to Result:= Pass. If UUS2 requested as required is yes, it goes to Result:= Pass. + +Figure 9.2.2.2: Procedure UUS\_ICH\_Check\_Forwarding + +![Flowchart for Procedure UUS_ICH_Handle_LCF. It starts with a connector symbol, followed by a decision 'UUS data stored?'. If 'No', it bypasses the 'Add UUS information to RCH message' block. If 'Yes', it proceeds to 'Add UUS information to RCH message'. Next is a decision 'UUS CF interaction = True?'. If 'No', it bypasses the 'Add UUS CF information flag to RCH message' block. If 'Yes', it proceeds to 'Add UUS CF information flag to RCH message'. Both paths lead to an end connector symbol. A note in the top right corner states: 'This procedure is running in the MSC and it checks whether UUS will be forwarded in the optimal routing case'.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +Procedure UUS\_ICH\_Handle\_LCF + +1(1) + +``` +graph TD; Start([ ]) --> D1{UUS data stored?}; D1 -- No --> D2{UUS CF interaction = True?}; D1 -- Yes --> P1[Add UUS information to RCH message]; P1 --> D2; D2 -- No --> End(( )); D2 -- Yes --> P2[Add UUS CF information flag to RCH message]; P2 --> End; +``` + +This procedure is running in the MSC and it checks whether UUS will be forwarded in the optimal routing case + +Flowchart for Procedure UUS\_ICH\_Handle\_LCF. It starts with a connector symbol, followed by a decision 'UUS data stored?'. If 'No', it bypasses the 'Add UUS information to RCH message' block. If 'Yes', it proceeds to 'Add UUS information to RCH message'. Next is a decision 'UUS CF interaction = True?'. If 'No', it bypasses the 'Add UUS CF information flag to RCH message' block. If 'Yes', it proceeds to 'Add UUS CF information flag to RCH message'. Both paths lead to an end connector symbol. A note in the top right corner states: 'This procedure is running in the MSC and it checks whether UUS will be forwarded in the optimal routing case'. + +Figure 9.2.2.3: Procedure UUS\_ICH\_Handle\_LCF + +![Flowchart for Procedure UUS_ICH_Set_Info_In_IAM. The process starts with a connector symbol, leading to a decision diamond. The left side of the diamond is labeled 'UUS information received, stored and not cleared'. The 'No' branch bypasses the next step. The 'Yes' branch leads to a process box 'Add UUS information to IAM', which then leads to an exit connector symbol.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +Procedure UUS\_ICH\_Set\_Info\_In\_IAM + +1(1) + +``` +graph TD; Start([ ]) --> Decision{ }; Decision -- No --> Exit(( )); Decision -- Yes --> Process[Add UUS information to IAM]; Process --> Exit; NoteLeft[UUS information received, stored and not cleared]; NoteRight[This procedure is running in the MSC and it checks whether UUS will be added to the IAM message in the call forwarding case]; +``` + +UUS information received, stored and not cleared + +No + +Yes + +Add UUS information to IAM + +This procedure is running in the MSC and it checks whether UUS will be added to the IAM message in the call forwarding case + +Flowchart for Procedure UUS\_ICH\_Set\_Info\_In\_IAM. The process starts with a connector symbol, leading to a decision diamond. The left side of the diamond is labeled 'UUS information received, stored and not cleared'. The 'No' branch bypasses the next step. The 'Yes' branch leads to a process box 'Add UUS information to IAM', which then leads to an exit connector symbol. + +Figure 9.2.2.4: Procedure UUS\_ICH\_Set\_Info\_In\_IAM + +![Flowchart for Procedure UUS_ICH_UUS1_Implicit_Active. It starts with a connector symbol, followed by a decision diamond 'UUS1 implicit request?'. If 'Yes', it goes to a process box 'UUS1 implicit active := True'. If 'No', it bypasses the process box. Both paths lead to an exit connector symbol. A note in the top right corner states: 'This procedure is running in the MSC and it sets the implicit UUS1 active when UUI is send'.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +Procedure UUS\_ICH\_UUS1\_Implicit\_Active + +1(1) + +``` +graph TD; Start([ ]) --> Decision{UUS1 implicit request?}; Decision -- Yes --> Process[UUS1 implicit active := True]; Decision -- No --> Exit(( )); Process --> Exit; +``` + +This procedure is running in the MSC and it sets the implicit UUS1 active when UUI is send + +Flowchart for Procedure UUS\_ICH\_UUS1\_Implicit\_Active. It starts with a connector symbol, followed by a decision diamond 'UUS1 implicit request?'. If 'Yes', it goes to a process box 'UUS1 implicit active := True'. If 'No', it bypasses the process box. Both paths lead to an exit connector symbol. A note in the top right corner states: 'This procedure is running in the MSC and it sets the implicit UUS1 active when UUI is send'. + +Figure 9.2.2.5: Procedure UUS\_ICH\_UUS1\_Implicit\_Active + +## 9.3 Procedures common in serving and remote networks + +Figure 9.3.1 Procedure UUS\_MSC\_Check\_UUS1\_UUI. + +This procedure is used to check whether it is allowed to pass UUI for UUS1 from MS to network or vice versa. + +Figure 9.3.2 Procedure UUS\_MSC\_Check\_UUS2\_UUI\_to\_MS. + +This procedure is used to check whether it is allowed to pass User-To-User messages for UUS2 from network to MS. + +Figure 9.3.3 Procedure UUS\_MSC\_Check\_UUS2\_UUI\_to\_NW. + +This procedure is used to check whether it is allowed to pass User-To-User messages for UUS2 from MS to network. + +Figure 9.3.4 Procedure UUS\_MSC\_Check\_UUS3\_UUI\_to\_MS. + +This procedure is used to check whether it is allowed to pass User-To-User messages for UUS3 from network to MS. + +Figure 9.3.5 Procedure UUS\_MSC\_Check\_UUS3\_UUI\_to\_NW. + +This procedure is used to check whether it is allowed to pass User-To-User messages for UUS3 from MS to network. + +Figure 9.3.6 Procedure UUS\_MSC\_Clear\_UUS. + +This procedure is used to handle the call forwarding interaction with UUS when call control messages are received from the forwarded-to NW. + +Figure 9.3.7 Macrodefinition UUS\_MSC\_Check\_UUS1. + +Macro used in procedures UUS\_OCH\_Set\_Alert\_And\_Connect\_Param and UUS\_ICH\_Check\_Support. It checks whether UUS service 1 is supported. + +Figure 9.3.8 Macrodefinition UUS\_MSC\_Check\_UUS2. + +Macro used in procedures UUS\_OCH\_Set\_Alert\_And\_Connect\_Param and UUS\_ICH\_Check\_Support. It checks whether UUS service 2 is supported. + +Figure 9.3.9 Macrodefinition UUS\_MSC\_Check\_UUS3. + +Macro used in procedures UUS\_OCH\_Set\_Alert\_And\_Connect\_Param and UUS\_ICH\_Check\_Support. It checks whether UUS service 3 is supported. + +![Flowchart for Procedure UUS_MSC_Check_UUS1_UUI. It starts with a connector symbol, leading to a decision diamond 'UUS1 implicit active = True?'. If 'No', it goes to another decision diamond 'UUS1 explicit active = True?'. If 'Yes' to 'UUS1 explicit active = True?', it proceeds to 'Pass UUI'. If 'No' to 'UUS1 explicit active = True?', it goes to a third decision diamond 'UUI received?'. If 'Yes' to 'UUI received?', it proceeds to 'Pass UUI'. If 'No' to 'UUI received?', it bypasses 'Pass UUI'. Both 'Yes' from 'UUS1 implicit active = True?' and the bypass from 'UUI received?' lead to the 'Pass UUI' block. The flowchart ends with an exit connector symbol.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +Procedure UUS\_MSC\_Check\_UUS1\_UUI + +1(1) + +``` +graph TD; Start([ ]) --> D1{UUS1 implicit active = True?}; D1 -- No --> D2{UUS1 explicit active = True?}; D1 -- Yes --> PassUUI[Pass UUI]; D2 -- Yes --> PassUUI; D2 -- No --> D3{UUI received?}; D3 -- Yes --> PassUUI; D3 -- No --> PassUUI; PassUUI --> End((X)); +``` + +This procedure is running in the MSC and it checks whether UUI can be passed over + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange unless otherwise marked. + +Flowchart for Procedure UUS\_MSC\_Check\_UUS1\_UUI. It starts with a connector symbol, leading to a decision diamond 'UUS1 implicit active = True?'. If 'No', it goes to another decision diamond 'UUS1 explicit active = True?'. If 'Yes' to 'UUS1 explicit active = True?', it proceeds to 'Pass UUI'. If 'No' to 'UUS1 explicit active = True?', it goes to a third decision diamond 'UUI received?'. If 'Yes' to 'UUI received?', it proceeds to 'Pass UUI'. If 'No' to 'UUI received?', it bypasses 'Pass UUI'. Both 'Yes' from 'UUS1 implicit active = True?' and the bypass from 'UUI received?' lead to the 'Pass UUI' block. The flowchart ends with an exit connector symbol. + +Figure 9.3.1: Procedure UUS\_MSC\_Check\_UUS1\_UUI + +![Flowchart for Procedure UUS_MSC_Check_UUS2_UUI_to_MS. The flow starts with a start symbol (oval), leading to a decision diamond 'UUS2 active = true?'. If 'Yes', it goes to a 'User To User' process block. If 'No', it bypasses the process block. Both paths lead to an end symbol (circle with X).](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +Procedure UUS\_MSC\_Check\_UUS2\_UUI\_to\_MS + +1(1) + +``` +graph TD; Start([ ]) --> Decision{UUS2 active = true?}; Decision -- Yes --> Process{{User To User}}; Decision -- No --> End((X)); Process --> End; +``` + +This procedure is running in the MSC and it checks whether UUI can be passed over + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange unless otherwise marked. + +Flowchart for Procedure UUS\_MSC\_Check\_UUS2\_UUI\_to\_MS. The flow starts with a start symbol (oval), leading to a decision diamond 'UUS2 active = true?'. If 'Yes', it goes to a 'User To User' process block. If 'No', it bypasses the process block. Both paths lead to an end symbol (circle with X). + +Figure 9.3.2: Procedure UUS\_MSC\_Check\_UUS2\_UUI\_to\_MS + +![Flowchart for Procedure UUS_MSC_Check_UUS2_UUI_to_NW. The flow starts at a connector, goes to a decision 'UUS2 active = True?'. If 'No', it goes to another decision 'UTU2Cnt' with a label '2'. If 'Yes', it goes to a decision 'UTU2Cnt' with a label '<2'. If '<2' is true, it goes to a process 'UTU2Cnt := UTU2Cnt + 1', then to a 'User To User' block, and finally to an exit connector. If 'No' from the first decision or if the second 'UTU2Cnt' decision is false, it goes directly to the exit connector.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +Procedure UUS\_MSC\_Check\_UUS2\_UUI\_to\_NW + +1(1) + +This procedure is running in the MSC and it checks whether UUI can be passed over. In addition it handles UUS2 flow control + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange unless otherwise marked. + +``` +graph TD; Start([ ]) --> D1{UUS2 active = True?}; D1 -- No --> D2{UTU2Cnt}; D1 -- Yes --> D3{UTU2Cnt}; D2 -- 2 --> Exit((X)); D3 -- "<2" --> P1[UTU2Cnt := UTU2Cnt + 1]; P1 --> U1[/User To User/]; U1 --> Exit; D3 -- No --> Exit; +``` + +Flowchart for Procedure UUS\_MSC\_Check\_UUS2\_UUI\_to\_NW. The flow starts at a connector, goes to a decision 'UUS2 active = True?'. If 'No', it goes to another decision 'UTU2Cnt' with a label '2'. If 'Yes', it goes to a decision 'UTU2Cnt' with a label '<2'. If '<2' is true, it goes to a process 'UTU2Cnt := UTU2Cnt + 1', then to a 'User To User' block, and finally to an exit connector. If 'No' from the first decision or if the second 'UTU2Cnt' decision is false, it goes directly to the exit connector. + +Figure 9.3.3: Procedure UUS\_MSC\_Check\_UUS2\_UUI\_to\_NW + +![Flowchart for Procedure UUS_MSC_Check_UUS3_UUI_to_MS. It starts with a start symbol, followed by a decision diamond 'UUS3 active = true?'. If 'Yes', it goes to a 'User To User' block and then to an end symbol. If 'No', it bypasses the 'User To User' block and goes directly to the end symbol. There are three callout boxes: one empty, one explaining the procedure's purpose, and one explaining signal directions.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +Procedure UUS\_MSC\_Check\_UUS3\_UUI\_to\_MS + +1(1) + +``` +graph TD; Start([ ]) --> Decision{UUS3 active = true?}; Decision -- Yes --> UserToUser{{User To User}}; UserToUser --> End((X)); Decision -- No --> End; +``` + +This procedure is running in the MSC and it checks whether UUI can be passed over + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange unless otherwise marked. + +Flowchart for Procedure UUS\_MSC\_Check\_UUS3\_UUI\_to\_MS. It starts with a start symbol, followed by a decision diamond 'UUS3 active = true?'. If 'Yes', it goes to a 'User To User' block and then to an end symbol. If 'No', it bypasses the 'User To User' block and goes directly to the end symbol. There are three callout boxes: one empty, one explaining the procedure's purpose, and one explaining signal directions. + +Figure 9.3.4: Procedure UUS\_MSC\_Check\_UUS3\_UUI\_to\_MS + +![Flowchart for Procedure UUS_MSC_Check_UUS3_UUI_to_NW. The process starts with a connector symbol, followed by a decision 'UUS3 active = True?'. If 'No', it goes to an exit connector. If 'Yes', it goes to a decision 'N > 0?'. If 'No', it goes to a decision 'Congestion control sent?'. If 'Yes', it goes to a process 'N := N - 1', then 'User To User', then to the exit connector. If 'Congestion control sent?' is 'True', it goes to the exit connector. If 'False', it goes to a process 'Congestion control sent := True', then to the exit connector. There are three callout boxes: one explaining the procedure's purpose, one explaining signal directions, and one explaining the 'Congestion Control' process.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +Procedure UUS\_MSC\_Check\_UUS3\_UUI\_to\_NW + +1(1) + +``` +graph TD; Start([ ]) --> UUS3{UUS3 active = True?}; UUS3 -- No --> End(( )); UUS3 -- Yes --> Ngt0{N > 0?}; Ngt0 -- No --> CongestionSent{Congestion control sent?}; Ngt0 -- Yes --> Ndec{N := N - 1}; Ndec --> UserToUser[/User To User/]; UserToUser --> End; CongestionSent -- True --> End; CongestionSent -- False --> CongestionSet{Congestion control sent := True}; CongestionSet --> End; +``` + +This procedure is running in the MSC and it checks whether UUI can be passed over. In addition it handles UUS3 flow control + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange unless otherwise marked. + +Inform the MS that it is not allowed to send any UUIs + +Flowchart for Procedure UUS\_MSC\_Check\_UUS3\_UUI\_to\_NW. The process starts with a connector symbol, followed by a decision 'UUS3 active = True?'. If 'No', it goes to an exit connector. If 'Yes', it goes to a decision 'N > 0?'. If 'No', it goes to a decision 'Congestion control sent?'. If 'Yes', it goes to a process 'N := N - 1', then 'User To User', then to the exit connector. If 'Congestion control sent?' is 'True', it goes to the exit connector. If 'False', it goes to a process 'Congestion control sent := True', then to the exit connector. There are three callout boxes: one explaining the procedure's purpose, one explaining signal directions, and one explaining the 'Congestion Control' process. + +Figure 9.3.5: Procedure UUS\_MSC\_Check\_UUS3\_UUI\_to\_NW + +![Flowchart for Procedure UUS_MSC_Clear_UUS. It starts with a connector symbol, leading to a decision diamond 'UUS CF interaction = True'. If 'No', it goes to an exit connector. If 'Yes', it goes to a process box 'Clear received (if any) S1', then to another decision diamond 'Received msg was Answer or Connect?'. If 'Yes', it goes to the exit connector. If 'No', it goes to a process box 'Clear received (if any) UUI', which then leads to the exit connector.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Procedure UUS\_MSC\_Clear\_UUS + +1(1) + +This procedure is running in the MSC and it handles CFNRy and UUS interaction when the MSC is receiving call control messages from forwarded-to NW. + +S1 = UUS1 Service response + +``` +graph TD; Start([ ]) --> D1{UUS CF interaction = True}; D1 -- No --> Exit((X)); D1 -- Yes --> P1[Clear received (if any) S1]; P1 --> D2{Received msg was Answer or Connect?}; D2 -- Yes --> Exit; D2 -- No --> P2[Clear received (if any) UUI]; P2 --> Exit; +``` + +Flowchart for Procedure UUS\_MSC\_Clear\_UUS. It starts with a connector symbol, leading to a decision diamond 'UUS CF interaction = True'. If 'No', it goes to an exit connector. If 'Yes', it goes to a process box 'Clear received (if any) S1', then to another decision diamond 'Received msg was Answer or Connect?'. If 'Yes', it goes to the exit connector. If 'No', it goes to a process box 'Clear received (if any) UUI', which then leads to the exit connector. + +Figure 9.3.6: Procedure UUS\_MSC\_Clear\_UUS + +![Flowchart for Macrodefinition UUS_MSC_Check_UUS1. The process starts with a decision 'UUS1 result sent?'. If 'True', it goes to 'Do not send S1' and then to a 'Pass' terminal. If 'False', it goes to 'Alert received?'. If 'Alert received?' is 'No', it goes to 'Connect received?'. If 'Alert received?' is 'Yes', it goes to 'explicit request?'. If 'explicit request?' is 'Yes', it goes to 'S1 received?'. If 'S1 received?' is 'Yes', it goes to 'UUS1 result sent := True' and then to 'Pass received S1'. If 'S1 received?' is 'No', it goes to 'Do not send S1' and then to a 'Pass' terminal. From 'Pass received S1', it goes to 'S1=np?'. If 'S1=np?' is 'Yes', it goes to 'UUS1 explicit active:=True' and then to 'UUS1 Required?'. If 'UUS1 Required?' is 'Yes', it goes to a 'Fail' terminal. If 'UUS1 Required?' is 'No', it goes to 'Do not send S1' and then to a 'Pass' terminal. If 'S1=np?' is 'No', it goes to 'UUS1 Required?' and then to a 'Fail' terminal. From 'Connect received?', if 'Yes', it goes to 'explicit request?'. If 'explicit request?' is 'Yes', it goes to 'UUS1 result sent := True' and then to 'S1 received?'. If 'S1 received?' is 'Yes', it goes to 'Pass received S1' and then to 'S1=np?'. If 'S1 received?' is 'No', it goes to 'S1:=np' and then to 'S1=np?'. If 'S1=np?' is 'Yes', it goes to 'UUS1 explicit active:=True' and then to 'UUS1 Required?'. If 'UUS1 Required?' is 'Yes', it goes to a 'Fail' terminal. If 'UUS1 Required?' is 'No', it goes to 'Do not send S1' and then to a 'Pass' terminal. If 'S1=np?' is 'No', it goes to 'UUS1 Required?' and then to a 'Fail' terminal. If 'Connect received?' is 'No', it goes to 'Do not send S1' and then to a 'Pass' terminal. A note in the top right corner states: 'np = service is not provided by network or remote end'.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +Macrodefinition UUS\_MSC\_Check\_UUS1 + +1(1) + +``` +graph TD; Start([Start]) --> D1{UUS1 result sent?}; D1 -- True --> S1[Do not send S1]; D1 -- False --> D2{Alert received?}; D2 -- No --> D3{Connect received?}; D2 -- Yes --> D4{explicit request?}; D4 -- Yes --> D5{S1 received?}; D4 -- No --> S1; D5 -- Yes --> S2[UUS1 result sent := True]; S2 --> S3[Pass received S1]; S3 --> D6{S1=np?}; D6 -- Yes --> S4[UUS1 explicit active:=True]; S4 --> D7{UUS1 Required?}; D7 -- Yes --> F1((Fail)); D7 -- No --> S1; D6 -- No --> D7; D7 -- Yes --> F2((Fail)); D3 -- Yes --> D8{explicit request?}; D8 -- Yes --> S5[UUS1 result sent := True]; S5 --> D9{S1 received?}; D9 -- Yes --> S6[Pass received S1]; S6 --> D10{S1=np?}; D10 -- Yes --> S7[UUS1 explicit active:=True]; S7 --> D11{UUS1 Required?}; D11 -- Yes --> F3((Fail)); D11 -- No --> S1; D10 -- No --> D11; D11 -- Yes --> F4((Fail)); D3 -- No --> S1; Note[np = service is not provided by network or remote end]; +``` + +Flowchart for Macrodefinition UUS\_MSC\_Check\_UUS1. The process starts with a decision 'UUS1 result sent?'. If 'True', it goes to 'Do not send S1' and then to a 'Pass' terminal. If 'False', it goes to 'Alert received?'. If 'Alert received?' is 'No', it goes to 'Connect received?'. If 'Alert received?' is 'Yes', it goes to 'explicit request?'. If 'explicit request?' is 'Yes', it goes to 'S1 received?'. If 'S1 received?' is 'Yes', it goes to 'UUS1 result sent := True' and then to 'Pass received S1'. If 'S1 received?' is 'No', it goes to 'Do not send S1' and then to a 'Pass' terminal. From 'Pass received S1', it goes to 'S1=np?'. If 'S1=np?' is 'Yes', it goes to 'UUS1 explicit active:=True' and then to 'UUS1 Required?'. If 'UUS1 Required?' is 'Yes', it goes to a 'Fail' terminal. If 'UUS1 Required?' is 'No', it goes to 'Do not send S1' and then to a 'Pass' terminal. If 'S1=np?' is 'No', it goes to 'UUS1 Required?' and then to a 'Fail' terminal. From 'Connect received?', if 'Yes', it goes to 'explicit request?'. If 'explicit request?' is 'Yes', it goes to 'UUS1 result sent := True' and then to 'S1 received?'. If 'S1 received?' is 'Yes', it goes to 'Pass received S1' and then to 'S1=np?'. If 'S1 received?' is 'No', it goes to 'S1:=np' and then to 'S1=np?'. If 'S1=np?' is 'Yes', it goes to 'UUS1 explicit active:=True' and then to 'UUS1 Required?'. If 'UUS1 Required?' is 'Yes', it goes to a 'Fail' terminal. If 'UUS1 Required?' is 'No', it goes to 'Do not send S1' and then to a 'Pass' terminal. If 'S1=np?' is 'No', it goes to 'UUS1 Required?' and then to a 'Fail' terminal. If 'Connect received?' is 'No', it goes to 'Do not send S1' and then to a 'Pass' terminal. A note in the top right corner states: 'np = service is not provided by network or remote end'. + +Figure 9.3.7: Macrodefinition UUS\_MSC\_Check\_UUS1 + +![Flowchart for Macrodefinition UUS_MSC_Check_UUS2. The process starts with a connector, followed by 'Alert received?' (Yes/No), 'S2 received?' (Yes/No), 'Pass received S2' or 'S2:=np', 'S2 = np?' (Yes/No), 'UUS2 active :=True', 'UUS2 Required?' (Yes/No), and finally 'Fail' or 'Pass'.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +Macrodefinition UUS\_MSC\_Check\_UUS2 + +1(1) + +``` +graph TD; Start([ ]) --> Alert{Alert received?}; Alert -- No --> Pass((Pass)); Alert -- Yes --> S2{S2 received?}; S2 -- No --> S2_np[S2:=np]; S2 -- Yes --> Pass_S2[Pass received S2]; Pass_S2 --> S2_np_check{S2 = np?}; S2_np --> S2_np_check; S2_np_check -- No --> UUS2_active[UUS2 active :=True]; S2_np_check -- Yes --> UUS2_Required{UUS2 Required?}; UUS2_active --> UUS2_Required; UUS2_Required -- No --> Pass; UUS2_Required -- Yes --> Fail((Fail)); +``` + +np = service is not provided by network or remote end + +Flowchart for Macrodefinition UUS\_MSC\_Check\_UUS2. The process starts with a connector, followed by 'Alert received?' (Yes/No), 'S2 received?' (Yes/No), 'Pass received S2' or 'S2:=np', 'S2 = np?' (Yes/No), 'UUS2 active :=True', 'UUS2 Required?' (Yes/No), and finally 'Fail' or 'Pass'. + +Figure 9.3.8: Macrodefinition UUS\_MSC\_Check\_UUS2 + +![Flowchart for Macrodefinition UUS_MSC_Check_UUS3. The process starts with an oval connector, followed by a decision 'Connect received?'. If 'No', it goes to a decision 'S3 received?'. If 'Yes' to 'S3 received?', it ends at 'Pass'. If 'No', it ends at 'Fail'. If 'Yes' to 'Connect received?', it goes to a decision 'S3 received?'. If 'No', it goes to a process 'S3:=np'. If 'Yes', it goes to a process 'Pass received S3'. Both processes lead to a decision 'S3 = np'. If 'Yes' to 'S3 = np', it goes to a process 'UUS3 active :=True'. Both 'S3:=np' and 'UUS3 active :=True' lead to a decision 'UUS3 Required?'. If 'Yes' to 'UUS3 Required?', it ends at 'Fail'. If 'No', it ends at 'Pass'. A note indicates 'np = service is not provided by network or remote end'.](8269648391c59363ea61243864a2adf7_img.jpg) + +Macrodefinition UUS\_MSC\_Check\_UUS3 + +1(1) + +``` +graph TD; Start([ ]) --> D1{Connect received?}; D1 -- No --> D2{S3 received?}; D1 -- Yes --> D3{S3 received?}; D2 -- Yes --> End1((Pass)); D2 -- No --> End2((Fail)); D3 -- No --> P1[S3:=np]; D3 -- Yes --> P2[Pass received S3]; P1 --> D4{S3 = np}; P2 --> D4; D4 -- Yes --> P3[UUS3 active :=True]; D4 -- No --> D5{UUS3 Required?}; P3 --> D5; D5 -- Yes --> End3((Fail)); D5 -- No --> End4((Pass)); Note[np = service is not provided by network or remote end]; +``` + +Flowchart for Macrodefinition UUS\_MSC\_Check\_UUS3. The process starts with an oval connector, followed by a decision 'Connect received?'. If 'No', it goes to a decision 'S3 received?'. If 'Yes' to 'S3 received?', it ends at 'Pass'. If 'No', it ends at 'Fail'. If 'Yes' to 'Connect received?', it goes to a decision 'S3 received?'. If 'No', it goes to a process 'S3:=np'. If 'Yes', it goes to a process 'Pass received S3'. Both processes lead to a decision 'S3 = np'. If 'Yes' to 'S3 = np', it goes to a process 'UUS3 active :=True'. Both 'S3:=np' and 'UUS3 active :=True' lead to a decision 'UUS3 Required?'. If 'Yes' to 'UUS3 Required?', it ends at 'Fail'. If 'No', it ends at 'Pass'. A note indicates 'np = service is not provided by network or remote end'. + +Figure 9.3.9: Macrodefinition UUS\_MSC\_Check\_UUS3 + +## 9.4 Processes used during Active Call + +There are different processes running for UUS3 during active call in serving and remote network. However, this differentiation does not implicitly mean that call originator's network is serving network. The differentiation is based on which party initiates the UUS3 service. Thus, serving network process shall be used on initiator's side and remote network process on the opposite end. + +### 9.4.1 Process and procedures in serving MSC + +Figure 9.4.1.1 Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call + +This process is used to check UUS3 activation during active call, handle UUS3 flow control and interaction with ECT supplementary service. The process starts during the call setup and checks the content of the Connect message in order to start the UUS3 flow control correctly. If the UUS3 is not activated the process stays in the Idle state and waits UUS3 activation request from the MS. + +Figure 9.4.1.2 Procedure UUS\_MSC\_Check\_UUS3\_Activation + +This procedure is used to handle the dialogue towards the serving VLR when provisioning check is done. + +![State transition diagram for Process Serving_MSC_Handle_UUS_In_Active_Call. The diagram shows the logic for handling UUS3 activation during an active call. It starts with Congestion control sent := False, then IDLE state. It branches into Facility and Connect (from GSM 03.18 processes). Facility leads to UUS_MSC_Check_UUS3_Activation, which results in Result? (Aborted, Fail, Pass). Pass leads to Start T4-UUS3, then Facility, then Wait_For_Activation_Response. Fail leads to S3:=np, then Facility, then IDLE. Aborted leads to an error state. Connect leads to another Connect state, then UUS3_active=True? (No, Yes). Yes leads to X:=16, N:=X, Y:=8 (UUS3 flow control parameters), then Start T2-UUS3, then Active_Call. No leads to IDLE.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call 1(4) + +``` +stateDiagram-v2 + [*] --> Congestion_control_sent + Congestion_control_sent : Congestion control sent := False + Congestion_control_sent --> IDLE + IDLE --> Facility + IDLE --> Connect + Note right of Connect: From GSM 03.18 processes + Facility --> UUS_MSC_Check_UUS3_Activation + UUS_MSC_Check_UUS3_Activation --> Result? + Result? -- Aborted --> [*] + Result? -- Fail --> S3_np + S3_np : S3:=np + S3_np --> Facility + Facility --> IDLE + Result? -- Pass --> Start_T4_UUS3 + Start_T4_UUS3 : Start T4-UUS3 + Start_T4_UUS3 --> Facility + Facility --> Wait_For_Activation_Response + Connect --> Connect2 + Connect2 --> UUS3_active_True + UUS3_active_True : UUS3 active=True? + UUS3_active_True -- No --> IDLE + UUS3_active_True -- Yes --> Flow_Control + Flow_Control : X:=16, N:=X, Y:=8 + Note right of Flow_Control: UUS3 flow control parameters + Flow_Control --> Start_T2_UUS3 + Start_T2_UUS3 : Start T2-UUS3 + Start_T2_UUS3 --> Active_Call +``` + +This process is running in the serving MSC. It handles UUS3 during the active call + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked. + +p = provided i.e. UUS3 service is provided +np = not provided i.e. UUS3 service is not provided + +State transition diagram for Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call. The diagram shows the logic for handling UUS3 activation during an active call. It starts with Congestion control sent := False, then IDLE state. It branches into Facility and Connect (from GSM 03.18 processes). Facility leads to UUS\_MSC\_Check\_UUS3\_Activation, which results in Result? (Aborted, Fail, Pass). Pass leads to Start T4-UUS3, then Facility, then Wait\_For\_Activation\_Response. Fail leads to S3:=np, then Facility, then IDLE. Aborted leads to an error state. Connect leads to another Connect state, then UUS3\_active=True? (No, Yes). Yes leads to X:=16, N:=X, Y:=8 (UUS3 flow control parameters), then Start T2-UUS3, then Active\_Call. No leads to IDLE. + +Figure 9.4.1.1: Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call (sheet 1) + +![State transition diagram for Process Serving_MSC_Handle_UUS_In_Active_Call. The diagram shows two main vertical paths. The left path starts with 'Wait_For_Activation_Response', followed by a 'Facility' state, 'Stop T4-UUS3' action, a decision 'S3=p?'. If 'Yes', it goes to 'UUS3 active :=True', then an action block 'X:=16, N:=X, Y:=8' (labeled 'UUS3 flow control parameters'), then a 'Facility' state, 'Start T2-UUS3' action, and finally 'Wait_For_UUI'. If 'No' from the decision, it goes to the right path. The right path starts with 'T4-UUS3 expiry' state, followed by a 'Facility' state, and finally 'IDLE'. There are three callout boxes: one explaining the process runs in the serving MSC, one explaining signal directions (left for BSS, right for exchange), and one defining 'p' (provided) and 'np' (not provided) for UUS3 service.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +### Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call 2(4) + +``` +stateDiagram-v2 + [*] --> Wait_For_Activation_Response + state "Facility" as Facility_L + state "T4-UUS3 expiry" as T4_UUS3_Expiry + state "Stop T4-UUS3" as Stop_T4_UUS3 + state "S3=p?" as S3_p + state "UUS3 active :=True" as UUS3_Active + state "X:=16, N:=X, Y:=8" as Flow_Control + state "Facility" as Facility_R + state "Start T2-UUS3" as Start_T2_UUS3 + state "IDLE" as IDLE + state "Wait_For_UUI" as Wait_For_UUI + + Wait_For_Activation_Response --> Facility_L + Facility_L --> Stop_T4_UUS3 + Stop_T4_UUS3 --> S3_p + S3_p --> T4_UUS3_Expiry : No + S3_p --> UUS3_Active : Yes + UUS3_Active --> Flow_Control + Flow_Control --> Facility_L + Facility_L --> Start_T2_UUS3 + Start_T2_UUS3 --> Wait_For_UUI + T4_UUS3_Expiry --> Facility_R + Facility_R --> IDLE +``` + +This process is running in the serving MSC. It handles UUS3 during the active call + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked. + +p = provided i.e. UUS3 service is provided +np = not provided i.e. UUS3 service is not provided + +UUS3 flow control parameters + +State transition diagram for Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call. The diagram shows two main vertical paths. The left path starts with 'Wait\_For\_Activation\_Response', followed by a 'Facility' state, 'Stop T4-UUS3' action, a decision 'S3=p?'. If 'Yes', it goes to 'UUS3 active :=True', then an action block 'X:=16, N:=X, Y:=8' (labeled 'UUS3 flow control parameters'), then a 'Facility' state, 'Start T2-UUS3' action, and finally 'Wait\_For\_UUI'. If 'No' from the decision, it goes to the right path. The right path starts with 'T4-UUS3 expiry' state, followed by a 'Facility' state, and finally 'IDLE'. There are three callout boxes: one explaining the process runs in the serving MSC, one explaining signal directions (left for BSS, right for exchange), and one defining 'p' (provided) and 'np' (not provided) for UUS3 service. + +Figure 9.4.1.1: Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call (sheet 2) + +![UML Sequence diagram for Process Serving_MSC_Handle_UUS_In_Active_Call. The diagram shows four lifelines starting from a '*' lifeline. Lifeline 1: 'Release transaction' (outward) -> 'Release transaction' (inward) -> End. A note 'To GSM 03.18 processes' is attached to the inward message. Lifeline 2: 'Release transaction' (outward) -> 'Release transaction' (inward) -> End. A note 'From GSM 03.18 processes' is attached to the outward message. Lifeline 3: 'NOTIFY (ECT)' (outward) -> 'NOTIFY (ECT)' (inward) -> Action block -> 'IDLE' (lifeline). The action block contains: UUS1 implicit active := False, UUS1 explicit active := False, UUS2 active := False, UUS3 active := False, Stop T2-UUS3. Lifeline 4: 'NOTIFY (ECT)' (outward) -> 'NOTIFY (ECT)' (inward). A note at the top right explains signal directions. A note at the top center explains the process's role. A small note box is at the top left.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call 3(4) + +This process is running in the serving MSC. It handles UUS3 during the active call + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked. + +From GSM 03.18 processes + +To GSM 03.18 processes + +Release transaction + +Release transaction + +NOTIFY (ECT) + +NOTIFY (ECT) + +UUS1 implicit active := False +UUS1 explicit active := False +UUS2 active := False +UUS3 active := False +Stop T2-UUS3 + +IDLE + +UML Sequence diagram for Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call. The diagram shows four lifelines starting from a '\*' lifeline. Lifeline 1: 'Release transaction' (outward) -> 'Release transaction' (inward) -> End. A note 'To GSM 03.18 processes' is attached to the inward message. Lifeline 2: 'Release transaction' (outward) -> 'Release transaction' (inward) -> End. A note 'From GSM 03.18 processes' is attached to the outward message. Lifeline 3: 'NOTIFY (ECT)' (outward) -> 'NOTIFY (ECT)' (inward) -> Action block -> 'IDLE' (lifeline). The action block contains: UUS1 implicit active := False, UUS1 explicit active := False, UUS2 active := False, UUS3 active := False, Stop T2-UUS3. Lifeline 4: 'NOTIFY (ECT)' (outward) -> 'NOTIFY (ECT)' (inward). A note at the top right explains signal directions. A note at the top center explains the process's role. A small note box is at the top left. + +Figure 9.4.1.1: Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call (sheet 3) + +![Flowchart for Process Serving_MSC_Handle_UUS_In_Active_Call. It starts with 'Active_Call', branches into 'User To User' (UUS MCH and MSC checks), 'T2-UUS3 expiry' (checking N=0, N=N+Y, congestion control), and another 'User To User' (UUS MSC check). It ends with 'Active_Call'.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +### Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call + +4(4) + +``` +graph TD + AC1([Active_Call]) --> U1[User To User] + AC1 --> U2[User To User] + AC1 --> T2[T2-UUS3 expiry] + U1 --> U1M[UUS_MCH Check_UUS3_UUI To MS] + U1M --> U2M[UUS_MSC Check_UUS3_UUI To NW] + U2 --> U2M + T2 --> N0{N = 0?} + N0 -- No --> NY1[N := N + Y] + N0 -- Yes --> NY2[N := N + Y] + NY2 --> CC{Congestion control sent?} + CC -- False --> NY1 + CC -- True --> CC1{Congestion Control} + CC1 --> CC1M[Congestion control sent := False] + NY1 --> NX{N > X?} + NX -- Yes --> NX1[N := X] + NX -- No --> NY1 + NX1 --> NY1 + CC1M --> NY1 + NY1 --> ST2[Start T2-UUS3] + ST2 --> AC2([Active_Call]) +``` + +**Notes:** + +- This process is running in the serving MSC. It handles UUS3 during the active call +- Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked. +- Inform MS that it is allowed to send UUIs + +Flowchart for Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call. It starts with 'Active\_Call', branches into 'User To User' (UUS MCH and MSC checks), 'T2-UUS3 expiry' (checking N=0, N=N+Y, congestion control), and another 'User To User' (UUS MSC check). It ends with 'Active\_Call'. + +Figure 9.4.1.1: Process Serving\_MSC\_Handle\_UUS\_In\_Active\_Call (sheet 4) + +![Flowchart for Procedure UUS_MSC_Check_UUS3_Activation. The process starts with a connector, followed by 'Send_Info_For_UUS3', then 'Wait_For_Answer'. A decision point follows: if 'UUS3 provisioned?' is 'Yes', it goes to 'Result:= Pass'; if 'No', it goes to 'Result:= Fail'. If neither, it proceeds to 'Send_Info_For_UUS3_Ack', then 'Wait_For_Ack'. From 'Wait_For_Ack', it branches: 'Release transaction' (From BSS to GSM 03.18) leads to 'Result:= Aborted'; 'Release transaction' (From GSM 03.18 to BSS) leads to 'Send_Info_For_UUS3_Ack'; 'Send_Info_For_UUS3_Ack' leads to 'Result:= Pass'. All results lead to a connector.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +Procedure UUS\_MSC\_Check\_UUS3\_Activation + +1(1) + +``` +graph TD; Start(( )) --> SendInfo[Send_Info_For_UUS3]; SendInfo --> WaitAnswer[Wait_For_Answer]; WaitAnswer --> Decision{UUS3 provisioned?}; Decision -- Yes --> ResultPass[Result:= Pass]; Decision -- No --> ResultFail[Result:= Fail]; Decision -- Neither --> SendInfoAck[Send_Info_For_UUS3_Ack]; SendInfoAck --> WaitAck[Wait_For_Ack]; WaitAck --> ReleaseBSS[Release transaction]; ReleaseBSS -- "From BSS" --> ToGSM[To GSM 03.18]; ReleaseBSS --> ResultAborted[Result:= Aborted]; WaitAck --> ReleaseGSM[Release transaction]; ReleaseGSM -- "From GSM 03.18" --> ToBSS[To BSS]; ReleaseGSM --> SendInfoAck2[Send_Info_For_UUS3_Ack]; SendInfoAck2 --> ResultPass; ResultAborted --> EndAborted(( )); ResultPass --> EndPass(( )); ResultFail --> EndFail(( )); +``` + +This procedure is running in the MSC and it checks UUS3 activation during active call + +Signals to/from the right are to/from the VLR unless otherwise marked. + +Flowchart for Procedure UUS\_MSC\_Check\_UUS3\_Activation. The process starts with a connector, followed by 'Send\_Info\_For\_UUS3', then 'Wait\_For\_Answer'. A decision point follows: if 'UUS3 provisioned?' is 'Yes', it goes to 'Result:= Pass'; if 'No', it goes to 'Result:= Fail'. If neither, it proceeds to 'Send\_Info\_For\_UUS3\_Ack', then 'Wait\_For\_Ack'. From 'Wait\_For\_Ack', it branches: 'Release transaction' (From BSS to GSM 03.18) leads to 'Result:= Aborted'; 'Release transaction' (From GSM 03.18 to BSS) leads to 'Send\_Info\_For\_UUS3\_Ack'; 'Send\_Info\_For\_UUS3\_Ack' leads to 'Result:= Pass'. All results lead to a connector. + +Figure 9.4.1.2: Procedure UUS\_MSC\_Check\_UUS3\_Activation + +### 9.4.2 Process and procedures in serving VLR + +Figure 9.4.2.1 Process Serving\_VLR\_Handle\_UUS\_In\_Active\_Call + +This process is running in the serving VLR. If the UUS3 activation request comes during the active call, this process is used to check whether the service is provisioned to the subscriber. + +![Flowchart for Process Serving_VLR_Handle_UUS_In_Active_Call. The flow starts at an unlabeled oval, goes to an IDLE state, then to a Send_Info For_UUS3 process. A decision diamond asks 'UUS3 provisioned?'. If 'Yes', it goes to 'Set UUS provisioned' and then to 'Send_Info For_UUS3 Ack'. If 'No', it bypasses 'Set UUS provisioned' and goes directly to 'Send_Info For_UUS3 Ack'. Both paths lead to a final IDLE state. There are two callout boxes: one stating 'This process is running in the VLR and it checks the UUS3 provisioning status' and another stating 'Signals to/from left are to/from MSC unless otherwise marked'.](552328a9daaf3bc0069424b500025880_img.jpg) + +Process Serving\_VLR\_Handle\_UUS\_In\_Active\_Call 1(1) + +``` +graph TD; Start([ ]) --> IDLE1([IDLE]); IDLE1 --> SendInfo[Send_Info For_UUS3]; SendInfo --> Decision{UUS3 provisioned?}; Decision -- Yes --> SetUUS[Set UUS provisioned]; Decision -- No --> SendAck{Send_Info For_UUS3 Ack}; SetUUS --> SendAck; SendAck --> IDLE2([IDLE]); +``` + +This process is running in the VLR and it checks the UUS3 provisioning status + +Signals to/from left are to/from MSC unless otherwise marked + +Flowchart for Process Serving\_VLR\_Handle\_UUS\_In\_Active\_Call. The flow starts at an unlabeled oval, goes to an IDLE state, then to a Send\_Info For\_UUS3 process. A decision diamond asks 'UUS3 provisioned?'. If 'Yes', it goes to 'Set UUS provisioned' and then to 'Send\_Info For\_UUS3 Ack'. If 'No', it bypasses 'Set UUS provisioned' and goes directly to 'Send\_Info For\_UUS3 Ack'. Both paths lead to a final IDLE state. There are two callout boxes: one stating 'This process is running in the VLR and it checks the UUS3 provisioning status' and another stating 'Signals to/from left are to/from MSC unless otherwise marked'. + +Figure 9.4.2.1: Process Serving\_VLR\_Handle\_UUS\_In\_Active\_Call + +### 9.4.3 Process and procedures in remote MSC + +Figure 9.4.3.1 Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call + +This process is running in the remote MSC. It is used for checking whether UUS3 UUI's can be passed on and control the flow control for UUS3. The process starts during the call setup and checks the content of the Connect message in order to start the UUS3 flow control correctly. If the UUS3 is not activated the process stays in the Idle state and waits UUS3 activation request from the NW. + +![Flowchart for Process Remote_MSC_Handle_UUS_In_Active_Call. It starts at an IDLE state, branches on Facility and Connect messages. The Connect path leads to a decision 'UUS3 active=True?'. If Yes, it sets variables X=16, N:=X, Y:=8, starts T2_UUS3, and enters Active_Call. If No, it returns to IDLE. The Facility path leads to another Facility symbol, then Start T1_UUS3, and finally Wait_For_Activation_Response. Callouts explain the process's role and signal directions.](753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg) + +Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call 1(4) + +``` +graph TD; Start([ ]) --> IDLE1([IDLE]); IDLE1 --> Facility1{Facility}; IDLE1 --> Connect1{Connect}; Connect1 --> Connect2[Connect]; Connect2 -.-> ToGSM[To GSM 03.18 processes]; Connect2 --> UUS3Active{UUS3 active=True?}; UUS3Active -- Yes --> Assign[X:=16
N:=X
Y:=8]; Assign --> StartT2[Start T2_UUS3]; StartT2 --> ActiveCall([Active_Call]); UUS3Active -- No --> IDLE2([IDLE]); Facility1 --> Facility2[Facility]; Facility2 --> StartT1[Start T1_UUS3]; StartT1 --> WaitForResponse([Wait_For_Activation_Response]); +``` + +This process is running in the remote MSC and it handles UUS3 flow control + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked. + +Flowchart for Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call. It starts at an IDLE state, branches on Facility and Connect messages. The Connect path leads to a decision 'UUS3 active=True?'. If Yes, it sets variables X=16, N:=X, Y:=8, starts T2\_UUS3, and enters Active\_Call. If No, it returns to IDLE. The Facility path leads to another Facility symbol, then Start T1\_UUS3, and finally Wait\_For\_Activation\_Response. Callouts explain the process's role and signal directions. + +Figure 9.4.3.1: Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call (sheet 1) + +![State transition diagram for Process Remote_MSC_Handle_UUS_In_Active_Call. It starts at Wait_For_Activation_Response, leading to a Facility state. From Facility, it goes to Stop T1-UUS3, then to a decision S3=p?. If Yes, it sets UUS3 active:= True, initializes X=16, N=X, Y=8, then goes to Facility, Start T2-UUS3, and finally Wait_For_UUI. If No, it goes to T1-UUS3 expiry, then S3:= np, then to Facility, and finally IDLE.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +### Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call + +2(4) + +This process is running in the remote MSC and it handles UUS3 flow control + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked. + +p = provided i.e. UUS3 service is provided +np = not provided i.e. UUS3 service is not provided + +``` +stateDiagram-v2 + [*] --> Wait_For_Activation_Response + Wait_For_Activation_Response --> Facility + Facility --> Stop_T1_UUS3: Stop T1-UUS3 + Stop_T1_UUS3 --> S3_p?: S3=p? + S3_p?: Yes --> UUS3_active_True: UUS3 active:= True + UUS3_active_True --> Init_X_N_Y: X := 16, N := X, Y := 8 + Init_X_N_Y --> Facility + Facility --> Start_T2_UUS3: Start T2-UUS3 + Start_T2_UUS3 --> Wait_For_UUI + S3_p?: No --> T1_UUS3_expiry: T1-UUS3 expiry + T1_UUS3_expiry --> S3_np: S3 := np + S3_np --> Facility + Facility --> IDLE +``` + +State transition diagram for Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call. It starts at Wait\_For\_Activation\_Response, leading to a Facility state. From Facility, it goes to Stop T1-UUS3, then to a decision S3=p?. If Yes, it sets UUS3 active:= True, initializes X=16, N=X, Y=8, then goes to Facility, Start T2-UUS3, and finally Wait\_For\_UUI. If No, it goes to T1-UUS3 expiry, then S3:= np, then to Facility, and finally IDLE. + +Figure 9.4.3.1: Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call (sheet 2) + +![Flowchart for Process Remote_MSC_Handle_UUS_In_Active_Call. It starts with an 'Active_Call' terminal, leading to three parallel paths: 'User To User' (UUS_MSC Check_UUS3 UUI to MS), 'User To User' (UUS_MSC Check_UUS3 UUI to NW), and 'T2-UUS3 expiry'. The 'T2-UUS3 expiry' path leads to a decision 'N = 0?'. If 'Yes', it goes to 'N := N + Y' and then to 'Congestion control sent?'. If 'No', it goes to 'N := N + Y' and then to 'N > X?'. Both 'Congestion control sent?' and 'N > X?' have 'True' and 'False' branches. The 'True' branches lead to 'Congestion Control' (with a note 'Inform MS that it is allowed to send UUIs') and 'Congestion control sent := False'. The 'False' branches lead to 'Start T2-UUS3'. All paths eventually lead to the 'Start T2-UUS3' block, which then leads to the 'Active_Call' terminal.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +**Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call** 3(4) + +Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked. + +p = provided i.e. UUS3 service is provided +np = + +This process is running in the remote MSC and it handles UUS3 flow control + +``` +graph TD; A1([Active_Call]) --> B1[User To User]; A1 --> B2[User To User]; A1 --> B3[T2-UUS3 expiry]; B1 --> C1[UUS_MSC Check_UUS3 UUI to MS]; B2 --> C2[UUS_MSC Check_UUS3 UUI to NW]; B3 --> D1{N = 0?}; D1 -- Yes --> E1[N := N + Y]; D1 -- No --> E2[N := N + Y]; E1 --> F1{Congestion control sent?}; E2 --> F2{N > X?}; F1 -- True --> G1{Congestion Control}; F1 -- False --> H1[Start T2-UUS3]; G1 --> I1[Congestion control sent := False]; I1 --> H1; F2 -- Yes --> G2[N := X]; F2 -- No --> H1; G2 --> H1; H1 --> A2([Active_Call]); +``` + +Inform MS that it is allowed to send UUIs + +Flowchart for Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call. It starts with an 'Active\_Call' terminal, leading to three parallel paths: 'User To User' (UUS\_MSC Check\_UUS3 UUI to MS), 'User To User' (UUS\_MSC Check\_UUS3 UUI to NW), and 'T2-UUS3 expiry'. The 'T2-UUS3 expiry' path leads to a decision 'N = 0?'. If 'Yes', it goes to 'N := N + Y' and then to 'Congestion control sent?'. If 'No', it goes to 'N := N + Y' and then to 'N > X?'. Both 'Congestion control sent?' and 'N > X?' have 'True' and 'False' branches. The 'True' branches lead to 'Congestion Control' (with a note 'Inform MS that it is allowed to send UUIs') and 'Congestion control sent := False'. The 'False' branches lead to 'Start T2-UUS3'. All paths eventually lead to the 'Start T2-UUS3' block, which then leads to the 'Active\_Call' terminal. + +Figure 9.4.3.1: Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call (sheet 3) + +![State transition diagram for Process Remote_MSC_Handle_UUS_In_Active_Call. The process starts in a state labeled 'Wait_For_Activation_Response_Active_Call'. It then branches into four parallel actions: 'Release transaction' (labeled 'From GSM 03.18 processes'), 'Release transaction' (labeled 'To GSM 03.18 processes'), 'NOTIFY (ECT)', and 'NOTIFY (ECT)'. All four actions lead to a common state labeled 'IDLE'. A note indicates that UUS1 implicit/explicit active, UUS2 active, and UUS3 active are all set to False, and T2-UUS3 is stopped. Another note explains that signals to the left are to/from the BSS and signals to the right are to/from the destination/originating exchange. A third note states that this process runs in the remote MSC and handles UUS3 flow control.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +### Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call + +4(4) + +``` +stateDiagram-v2 + [*] --> Wait_For_Activation_Response_Active_Call + state "Wait_For_Activation_Response_Active_Call" as Wait_For_Activation_Response_Active_Call + state "Release transaction" as Release_transaction_1 + state "Release transaction" as Release_transaction_2 + state "NOTIFY (ECT)" as NOTIFY_1 + state "NOTIFY (ECT)" as NOTIFY_2 + state "IDLE" as IDLE + + Wait_For_Activation_Response_Active_Call --> Release_transaction_1 + Wait_For_Activation_Response_Active_Call --> Release_transaction_2 + Wait_For_Activation_Response_Active_Call --> NOTIFY_1 + Wait_For_Activation_Response_Active_Call --> NOTIFY_2 + + Release_transaction_1 --> IDLE + Release_transaction_2 --> IDLE + NOTIFY_1 --> IDLE + NOTIFY_2 --> IDLE +``` + +**Notes:** + +- This process is running in the remote MSC and it handles UUS3 flow control +- Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked. +- UUS1 implicit active := False +UUS1 explicit active := False +UUS2 active := False +UUS3 active := False +Stop T2-UUS3 + +State transition diagram for Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call. The process starts in a state labeled 'Wait\_For\_Activation\_Response\_Active\_Call'. It then branches into four parallel actions: 'Release transaction' (labeled 'From GSM 03.18 processes'), 'Release transaction' (labeled 'To GSM 03.18 processes'), 'NOTIFY (ECT)', and 'NOTIFY (ECT)'. All four actions lead to a common state labeled 'IDLE'. A note indicates that UUS1 implicit/explicit active, UUS2 active, and UUS3 active are all set to False, and T2-UUS3 is stopped. Another note explains that signals to the left are to/from the BSS and signals to the right are to/from the destination/originating exchange. A third note states that this process runs in the remote MSC and handles UUS3 flow control. + +Figure 9.4.3.1: Process Remote\_MSC\_Handle\_UUS\_In\_Active\_Call (sheet 4) + +# 10 Information stored in the HLR and in the VLR + +## 10.1 Information stored in the HLR + +The following logical states are applicable for each of the 3 Services of the User-to-user supplementary service (refer to GSM 03.11 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 each of the 3 services of the UUS supplementary service (which shall be one of the valid states listed above) on a per subscriber basis. + +## 10.2 Transfer of information from HLR to VLR + +If the provisioning state for the UUS services is "Provisioned" then when the subscriber registers on a VLR the HLR shall send that VLR information about the logical state of these UUS services. + +If the logical state of the UUS services is changed while a subscriber is registered on a VLR then the HLR shall inform the VLR of the new logical state of the UUS services. + +## 10.3 Information stored in the VLR + +For the supplementary service UUS the VLR shall store the service state information received from the HLR. + +# 11 State transition model + +Figure 11.1 shows the successful cases of transition between the applicable logical states of the service. The state changes are caused by actions of the service provider. + +![State transition model diagram showing two states and two transitions.](84db9bf6e93779b67aa320d1dfd38d91_img.jpg) + +``` + +stateDiagram-v2 + [*] --> State1 : (Not Provisioned, Not Registered, Not Active, Not Induced) + State1 --> State2 : Provision + State2 --> State1 : Withdrawal + state " (Not Provisioned, Not Registered, Not Active, Not Induced) " as State1 + state " (Provisioned, Not Registered, Active and Operative, Not Induced) " as State2 + +``` + +The diagram illustrates the state transition model for the service. It consists of two states represented by ovals and two transitions represented by curved arrows. The left state is labeled "(Not Provisioned, Not Registered, Not Active, Not Induced)". The right state is labeled "(Provisioned, Not Registered, 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 diagram showing two states and two transitions. + +Figure 11.1: State transition model + +# 12 Handover + +Handover will have no impact on the control procedures and the operation of the service. + +# Annex A (informative): Change history + +| TSG CN# | Spec | CR | Rev | Phase | Cat | New Ver | Subject/Comment | +|----------|-----------|-----|-----|--------|-----|---------|----------------------------------| +| Apr 1999 | GSM 03.87 | | | R98 | | | Transferred to 3GPP CN1 | +| CN#03 | 23.087 | | | R99 | | 3.0.0 | Approved at CN#03 | +| | 23.087 | | | R99 | | 3.0.1 | References updated from 2G to 3G | +| CN#09 | 23.087 | 001 | 1 | R99 | F | 3.1.0 | SDL refresh | +| CN#11 | 23.087 | | | Rel-4 | | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 23.087 | | | Rel-5 | | 5.0.0 | Release 5 after CN#16 | +| CN#26 | 23.087 | | | Rel-6 | | 6.0.0 | Release 6 after CN#26 | +| CT#36 | 23.087 | | | Rel-7 | | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.087 | | | Rel-8 | | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.087 | - | - | Rel-9 | | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.087 | - | - | Rel-10 | | 10.0.0 | Update to Rel-10 version (MCC) | +| 2012-09 | 23.087 | - | - | Rel-11 | | 11.0.0 | Update to Rel-11 version (MCC) | +| 2014-09 | 23.087 | - | - | Rel-12 | | 12.0.0 | Update to Rel-12 version (MCC) | +| 2015-12 | 23.087 | - | - | Rel-13 | | 13.0.0 | Update to Rel-13 version (MCC) | +| 2017-03 | 23.087 | - | - | Rel-14 | | 14.0.0 | Update to Rel-14 version (MCC) | +| 2018-06 | 23.087 | - | - | Rel-15 | - | 15.0.0 | Update to Rel-15 version (MCC) | +| 2020-07 | 23.087 | - | - | Rel-16 | - | 16.0.0 | Update to Rel-16 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23088/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23088/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95c16f904ab37fbdc8267cc097593bcb3cc67b10 --- /dev/null +++ b/marked/Rel-16/23_series/23088/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d865b64e630ec8afddecb3fca3b444298f3247383b7f5f030aa019285a52880 +size 77588 diff --git a/marked/Rel-16/23_series/23088/02d0c8a07c481d880b73a25d02050fad_img.jpg b/marked/Rel-16/23_series/23088/02d0c8a07c481d880b73a25d02050fad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..779f02b94a6d697e1354b59829ca73f84059360d --- /dev/null +++ b/marked/Rel-16/23_series/23088/02d0c8a07c481d880b73a25d02050fad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88f2d66734e0d454c1f850eaffadd2cf527808f9958cac87dbb2fbb288983769 +size 52409 diff --git a/marked/Rel-16/23_series/23088/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23088/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3fc72657239e917105322c29622b53e245cfd086 --- /dev/null +++ b/marked/Rel-16/23_series/23088/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc305d2231239f95509f8da436d091ce7ef1ae6b97b284a4987c455aabaa4f0a +size 83546 diff --git a/marked/Rel-16/23_series/23088/088921fa3f5a44c8551815122517eefd_img.jpg b/marked/Rel-16/23_series/23088/088921fa3f5a44c8551815122517eefd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d49551e0f80be9d841e54388db9aa2332b248a9 --- /dev/null +++ b/marked/Rel-16/23_series/23088/088921fa3f5a44c8551815122517eefd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebb940eeae5d7ad439b94e1072dee7af6f8c04502fd2141d90b3b6edcea02d0d +size 47415 diff --git a/marked/Rel-16/23_series/23088/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23088/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fff62742dfa71cdcaeeb4e1142d2eafef6b5601b --- /dev/null +++ b/marked/Rel-16/23_series/23088/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d29705dc98b9dbafd85cb0097209758fbd70c6986c8355b4b78894195df4e6ba +size 66530 diff --git a/marked/Rel-16/23_series/23088/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23088/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..991005e5d8281e4e7e15dc76c5cab4a234bb20fe --- /dev/null +++ b/marked/Rel-16/23_series/23088/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b9f936cfe6b1bab43513009f6d8c16c7fb7c7dd8161b381fbaf6695891639d3 +size 87136 diff --git a/marked/Rel-16/23_series/23088/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23088/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9af8b6ca3848bdf91bb09f66516ed42ef9470108 --- /dev/null +++ b/marked/Rel-16/23_series/23088/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ca0f2db5c6d091b6ecd5ef70cf2a477d3062c11c935280c21423a234db56dda +size 55900 diff --git a/marked/Rel-16/23_series/23088/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23088/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5cf86706037951cef25b82a1f39cdd4524bf3d84 --- /dev/null +++ b/marked/Rel-16/23_series/23088/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e7d7e82aa295ae2d1662043485378155d28febe1cd671ad90f3ac978aa742d0 +size 58256 diff --git a/marked/Rel-16/23_series/23088/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23088/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2cfca376fcfdad262200395f34b0cd5ce3c3ccf0 --- /dev/null +++ b/marked/Rel-16/23_series/23088/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0367a915aa40669e1df8eb69676c56284ae561ba62fe081134197bc6421f11d9 +size 80542 diff --git a/marked/Rel-16/23_series/23088/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23088/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e075516899cfee6b4d2cef24b67a96cafe87be1f --- /dev/null +++ b/marked/Rel-16/23_series/23088/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7efbb3790718bb1c5122e79e9915ea5badd7c312f5f27ec2b111437857cf81a +size 122387 diff --git a/marked/Rel-16/23_series/23088/6361dfaef83c9ffc3b147e1627ba76a1_img.jpg b/marked/Rel-16/23_series/23088/6361dfaef83c9ffc3b147e1627ba76a1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c89e706bcaa51ef4faea9b510d50da51684f562e --- /dev/null +++ b/marked/Rel-16/23_series/23088/6361dfaef83c9ffc3b147e1627ba76a1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:000cfe3035992a6b9f2bde7f21967d46cd366da708ff4ab76f1ed5afec48a732 +size 51301 diff --git a/marked/Rel-16/23_series/23088/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/23_series/23088/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bef51ab214d6b7dd39a9c72da9fe09645cbb1a00 --- /dev/null +++ b/marked/Rel-16/23_series/23088/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:504804de1351c9c1077670a81bd114ea94deffa937a94abd94f7929387590013 +size 72516 diff --git a/marked/Rel-16/23_series/23088/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/Rel-16/23_series/23088/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..019d918ffcaf290091e724f5817252c50aea493f --- /dev/null +++ b/marked/Rel-16/23_series/23088/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3abc924cf9c9ef77730fff88933b26ac2dbed38d3d3c6b9d6fcf4c80d967e9b2 +size 31221 diff --git a/marked/Rel-16/23_series/23088/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/marked/Rel-16/23_series/23088/73dff6b45b2b9ffd384bab3235f869af_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fd2b7e4c08ce0d05cc68291c2b7ae783bcc81d80 --- /dev/null +++ b/marked/Rel-16/23_series/23088/73dff6b45b2b9ffd384bab3235f869af_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4056f85b214e7fa041971d0d137e0bcdba0cd1d42716cd6da6e1335e89439c38 +size 145868 diff --git a/marked/Rel-16/23_series/23088/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23088/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..019100288be803547c6a4a840e91aa2eac44864b --- /dev/null +++ b/marked/Rel-16/23_series/23088/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7e9091cfc0992337576a166a2c8a48412e999afb0367b5c22a4d5789f7062c9f +size 61381 diff --git a/marked/Rel-16/23_series/23088/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23088/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b419db2a5719052192f3302deab37890ab7e17f2 --- /dev/null +++ b/marked/Rel-16/23_series/23088/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b410c20e58b1733479971221adee52ee9c0513ccaa68edc1acbb2ad75ff8846 +size 85636 diff --git a/marked/Rel-16/23_series/23088/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23088/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2da6bf1b50089626a02781d0f852b423b972b61 --- /dev/null +++ b/marked/Rel-16/23_series/23088/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dcbc03bc45abc20458d024741425aac2666074bb4b063669c8207abd01a3389c +size 42207 diff --git a/marked/Rel-16/23_series/23088/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23088/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50944166ea1c87f87e47f5e6c3a1a6221b2ff7a7 --- /dev/null +++ b/marked/Rel-16/23_series/23088/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:be0d5fa49908108b1e03242b04b6d2f9b81f28194aefd5cb92c155834efb41e6 +size 54716 diff --git a/marked/Rel-16/23_series/23088/a734898ce18e972938949637c32a34f4_img.jpg b/marked/Rel-16/23_series/23088/a734898ce18e972938949637c32a34f4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..860063b2578b0c6a8fea8f797c855f3ecf50206f --- /dev/null +++ b/marked/Rel-16/23_series/23088/a734898ce18e972938949637c32a34f4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:358f42bf686115934d04062bc676914c7cadbbdf33af5c03b72dee6344e85fdb +size 27925 diff --git a/marked/Rel-16/23_series/23088/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23088/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6ffe3c3da0baef9b9f3eeac09649b435b601713 --- /dev/null +++ b/marked/Rel-16/23_series/23088/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a0c21849c22e09a0f61d9dd1ec626574c10ba6b071b19d5a1660942c2df45c6a +size 52611 diff --git a/marked/Rel-16/23_series/23088/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23088/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51bb402177f518711328b9ff06bdf8f71de57dc7 --- /dev/null +++ b/marked/Rel-16/23_series/23088/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:08f2ff7ef0f4eaa40b623d533e2741ed5a309c36d454bc7be805839b62996eca +size 60125 diff --git a/marked/Rel-16/23_series/23088/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23088/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb3b86ef7a3fc91a873247a4cb8e40c7de2b25d8 --- /dev/null +++ b/marked/Rel-16/23_series/23088/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c1bf143080dfece7475a4fc1c537fb3c544075174bba267d69ee139edb4b48e +size 65646 diff --git a/marked/Rel-16/23_series/23088/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/23_series/23088/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5d4b9d7d15e1822d48e2a65a66a89ac89607e43f --- /dev/null +++ b/marked/Rel-16/23_series/23088/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5253be79150309ff9b90001df14dc7ed0fc5b11382e7df5424c5885a475ba39 +size 38560 diff --git a/marked/Rel-16/23_series/23088/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23088/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28ed60d115fa2f66fa6387f37b995d2a35cf5de9 --- /dev/null +++ b/marked/Rel-16/23_series/23088/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5fc31caaa92748ea1829314a77a401d3aee8e2be0965709271eddf658e5532c +size 54726 diff --git a/marked/Rel-16/23_series/23088/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/marked/Rel-16/23_series/23088/e9d825d87c5f85c8dba0664eace96ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..759119536db04d070575f720c539f3efdfac0876 --- /dev/null +++ b/marked/Rel-16/23_series/23088/e9d825d87c5f85c8dba0664eace96ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35f7341c57ad762e6bb237aab838e7c03e86f60247684ad62a39fabaca18f6bd +size 25183 diff --git a/marked/Rel-16/23_series/23088/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23088/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64481d94e42429977b7adc4f5e3b8a72825e1c82 --- /dev/null +++ b/marked/Rel-16/23_series/23088/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:339c9484ae3de28ee4c6cadaa83b3dfa2b5e9da789f07b321561b9eb3af0077b +size 53230 diff --git a/marked/Rel-16/23_series/23088/raw.md b/marked/Rel-16/23_series/23088/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ae1b54528f419d3ea1d210cd33a2089e07cbc83d --- /dev/null +++ b/marked/Rel-16/23_series/23088/raw.md @@ -0,0 +1,1442 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword .......................................................................................................................................................................... | 5 | +| 1 Scope.................................................................................................................................................................. | 6 | +| 2 References.......................................................................................................................................................... | 6 | +| 3 Abbreviations ..................................................................................................................................................... | 7 | +| 4 Cross-Phase compatibility.................................................................................................................................. | 7 | +| 5 Data stored in the HLR for all call barring services .......................................................................................... | 7 | +| 6 Barring of outgoing calls.................................................................................................................................... | 7 | +| 6.1 Handling of barring of outgoing calls .......................................................................................................... | 7 | +| 6.1.0 Applicability .......................................................................................................................................... | 7 | +| 6.1.1 Registration............................................................................................................................................ | 7 | +| 6.1.2 Activation .............................................................................................................................................. | 8 | +| 6.1.2.1 General............................................................................................................................................ | 8 | +| 6.1.2.2 Interactions between barring of outgoing call programs ................................................................ | 8 | +| 6.1.2.3 Interactions with call forwarding supplementary services .............................................................. | 8 | +| 6.1.3 Deactivation.......................................................................................................................................... | 12 | +| 6.1.4 Interrogation .......................................................................................................................................... | 13 | +| 6.2 Functions and information flows.................................................................................................................. | 14 | +| 6.3 Information stored in the HSS/HLR.............................................................................................................. | 19 | +| 6.4 State transition model.................................................................................................................................... | 21 | +| 6.5 Transfer of information from HSS/HLR to VLR/SGSN/MME.................................................................... | 22 | +| 6.6 Information stored in the VLR/SGSN/MME ................................................................................................ | 22 | +| 6.7 Handover ...................................................................................................................................................... | 22 | +| 6.8 Cross Phase compatibility ............................................................................................................................ | 22 | +| 6.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber.................................. | 22 | +| 6.8.2 HLR only support Phase 1 updating of subscriber information .......................................................... | 22 | +| 6.9 Interworking with VLR or SGSN or MME not supporting Call Barring .................................................... | 22 | +| 7 Barring of incoming calls other than Anonymous Call Rejection .................................................................... | 23 | +| 7.1 Handling of barring of incoming calls .......................................................................................................... | 23 | +| 7.1.0 Applicability .......................................................................................................................................... | 23 | +| 7.1.1 Registration............................................................................................................................................ | 23 | +| 7.1.2 Activation .............................................................................................................................................. | 23 | +| 7.1.2.1 General............................................................................................................................................ | 23 | +| 7.1.2.2 Interactions between barring of incoming call programs ................................................................ | 23 | +| 7.1.2.3 Interactions with call forwarding supplementary services .............................................................. | 23 | +| 7.1.3 Deactivation.......................................................................................................................................... | 27 | +| 7.1.4 Interrogation .......................................................................................................................................... | 28 | +| 7.2 Functions and information flows.................................................................................................................. | 28 | +| 7.3 Information stored in the HSS/HLR.............................................................................................................. | 32 | +| 7.4 State transition model.................................................................................................................................... | 33 | +| 7.5 Transfer of information from HSS/HLR to VLR/SGSN/MME.................................................................... | 34 | +| 7.6 Information stored in the VLR/SGSN/MME ................................................................................................ | 34 | +| 7.7 Handover ...................................................................................................................................................... | 34 | +| 7.8 Cross Phase compatibility ............................................................................................................................ | 34 | +| 7.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber.................................. | 34 | +| 7.8.2 HLR only supports Phase 1 updating of subscriber information .......................................................... | 35 | +| 8 Anonymous Call Rejection ................................................................................................................................ | 36 | +| 8.1 General .......................................................................................................................................................... | 36 | +| 8.2 Procedures ...................................................................................................................................................... | 36 | +| 8.2.1 Provision and withdrawal ...................................................................................................................... | 36 | +| 8.2.2 Registration and erasure ........................................................................................................................ | 36 | +| 8.2.3 Activation and deactivation.................................................................................................................... | 36 | +| 8.2.3.1 General............................................................................................................................................ | 36 | +| 8.2.3.2 Interactions with other incoming call barring programs................................................................ | 36 | +| 8.2.3.3 Logical states in the HLR for the ACR supplementary service...................................................... | 37 | + +| | | | +|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|----| +| 8.2.4 | Invocation .................................................................................................................................... | 37 | +| 8.2.4.1 | General........................................................................................................................................ | 37 | +| 8.2.4.2 | Terminating Network Information flow ................................................................................... | 38 | +| 8.2.4.2a | Originating Network behaviour ............................................................................................. | 38 | +| 8.2.4.3 | Mobile Additional Function...................................................................................................... | 39 | +| 8.2.5 | Interrogation .................................................................................................................................... | 40 | +| 8.2.6 | Exceptional procedures ................................................................................................................... | 41 | +| 8.3 | Interactions with other supplementary services ............................................................................... | 41 | +| 8.4 | Interactions with other network features and services ..................................................................... | 41 | +| 8.4.1 | Operator Determined Barring (ODB)....................................................................................... | 41 | +| 8.4.2 | Optimal Routeing ..................................................................................................................... | 41 | +| Annex A (informative): | Change history.......................................................................................................................... | 42 | + +# --- Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- 1 Scope + +The present document gives the stage 2 description of the call barring services. + +The possibility for a mobile subscriber to have certain categories of calls barred originated from or terminated at his access: + +- Barring of outgoing calls (clause 1): +- Barring of all outgoing calls (BAOC) (Barring program 1); + - Barring of outgoing international calls (BOIC) (Barring program 2); + - Barring of outgoing international calls EXCEPT those directed to the home PLMN country +(BOIC-exHC) (Barring program 3). +- Barring of incoming calls (clause 2): +- Barring of all incoming calls (BAIC) (Barring program 1); + - Barring of incoming calls when roaming outside the home PLMN country +(BIC-Roam) (Barring program 2); + - Anonymous Call Rejection (ACR) (Barring program 3). + +NOTE: The call barring program "incoming calls when roaming outside the home PLMN country" (clause 2) is only relevant if as a general rule the called mobile subscriber pays the charges for the forwarded part of the call from his home PLMN country to any other country. + +# --- 2 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: "3G Vocabulary". +- [2] 3GPP TS 22.082: "Call Forwarding (CF) Supplementary Services - Stage 1". +- [3] 3GPP TS 23.011: "Technical realization of supplementary services". +- [4] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3 - Stage 2". +- [5] 3GPP TS 23.081: "Line identification Supplementary Services; Stage 2". +- [6] 3GPP TS 22.004: "General on supplementary services". +- [7] 3GPP TS 23.090: "Unstructured Supplementary Service Data (USSD) - Stage 2". +- [8] 3GPP TS 22.088: "Call Barring (CB) supplementary services – Stage 1". +- [9] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [10] 3GPP TS 23.088: "Call Barring (CB) Supplementary Services; Stage 2". + +# --- 3 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 apply. + +# --- 4 Cross-Phase compatibility + +For the following supplementary services, a number of changes exist between the present document and the Phase 1 specification: + +- Barring of outgoing calls; +- Barring of incoming calls. + +The main body of the present document assumes that all network entities comply with this version of the service. In each case an additional subclause (subclauses 6.6 and 7.6) defines the additional requirements for when one or more network entities or the MS complies with the Phase 1 specifications for the supplementary service procedures. + +# --- 5 Data stored in the HLR for all call barring services + +The following data are stored in the HLR in common for all call barring services other than ACR: + +- The "notification to CSE flag". This flag applies for all call barring services. When the data for any Call Barring are changed, the HLR checks this flag. If the flag is set, the change is reported to the gsmSCF(s) defined by the gsmSCF address list. See 3GPP TS 23.078 [4]. +- The "gsmSCF address list", which is a list of gsmSCF addresses to which Notification on Change of Subscriber Data is to be sent. This list applies to all call barring services. See TS 23.078. + +# --- 6 Barring of outgoing calls + +## 6.1 Handling of barring of outgoing calls + +### 6.1.0 Applicability + +The user control defined in this section is only applicable in CS domain. + +For MME, only MMEs supporting the SMS in MME option described in 3GPP TS 23.272 [10] may handle barring of MO SMS. + +### 6.1.1 Registration + +If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", he has to register a password at provision time. Furthermore the served mobile subscriber can change the password by an appropriate control procedure at any time. The control procedure consists of three steps: first, the old password has to be provided. Secondly, the new password has to be given, after which it has to be verified by providing it once more, see 3G TS 23.011. + +If the served mobile subscriber at provision time has selected the subscription option "control of barring services by the service provider" an attempt to register a password will be denied and the served mobile subscriber should receive a notification. + +The subscriber can register a new password, thus causing the previous registration to be overridden, see 3G TS 23.011. + +### 6.1.2 Activation + +#### 6.1.2.1 General + +If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password" the supplementary service is activated if the subscriber provides the following information to the network: + +- 1) password; +- 2) information as to whether the activation applies to all basic services or a specific basic service group; +- 3) selected barring program. + +Activation can take place with an appropriate control procedure by the subscriber. + +If the served mobile subscriber at provision time has selected the subscription option "control of barring services by the service provider", the supplementary service cannot be activated by the subscriber. The activation has to be performed by the service provider. An attempt to activate the service will be denied and the served mobile subscriber should receive a notification. + +If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", and if a wrong password is entered to activate the service the supplementary service will not be activated and the served mobile subscriber is notified. + +The information flow for activation of barring of outgoing calls is shown in figure 6.4. For more details see 3G TS 23.011. + +#### 6.1.2.2 Interactions between barring of outgoing call programs + +In case the served mobile subscriber activates barring of outgoing international calls except those directed to the home PLMN country and this service is not supported by the PLMN in which the served mobile subscriber currently roams, the VPLMN will activate barring of outgoing international calls instead. The SDL diagram in figure 6.1 shows the function to be performed in the VLR in order to deal with this interaction. This function is performed upon receiving the "insert subscriber data" message from the HLR. + +In case the mobile subscriber activates one of the call barring programs and another call barring program was already activated, this program will be deactivated and the requested call barring program will be activated. The SDL diagram in figure 6.2 shows the function to be performed in the HLR in order to deal with this interaction between call barring programs. + +#### 6.1.2.3 Interactions with call forwarding supplementary services + +This section is not applicable for SMS. + +For interactions with call forwarding supplementary services see 3G TS 22.082. + +The SDL diagram in figure 6.3 shows the function to be performed in the HLR in order to deal with the interactions with call forwarding supplementary services. + +![SDL Flowchart for Process BO1 showing the logic for changing barring of outgoing international calls. It includes states for idle, an activation signal, a decision on support, a task to change settings, and an acknowledgement signal.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +Process BO1 + +388\_11(1) + +``` + +graph TD + Start[ ] --> Idle1([idle]) + Idle1 --> Activate[/activate +BOIC-exHC/] + Activate --> Supported{BOIC-exHC +supported} + Supported -- no --> Change[change into +BOIC] + Supported -- yes --> Acknowledge[/acknowledge/] + Change --> Acknowledge + Acknowledge --> Idle2([idle]) + + style Start fill:none,stroke:none + +``` + +BOIC-exHC: Barring of Outgoing International Calls +                     except those directed to the home PLMN country. + BOIC:           Barring of Outgoing International Calls. + +SDL Flowchart for Process BO1 showing the logic for changing barring of outgoing international calls. It includes states for idle, an activation signal, a decision on support, a task to change settings, and an acknowledgement signal. + +**Figure 6.1: BO1 Possible change of barring of outgoing international calls except those directed to the home PLMN country into barring of outgoing international calls** + +![Flowchart for Process BO2 showing the interaction between call barring programs. The process starts at an 'idle' state, proceeds to 'register outgoing barring program', then checks if 'other program active'. If 'yes', it goes to 'deactivate other outgoing barring program' before continuing. If 'no', it proceeds directly to 'activate outgoing barring program'. Both paths lead to 'activate outgoing barring program', which then leads to 'acknowledge' and back to an 'idle' state.](e6df2733626a85205c1db682e6259c46_img.jpg) + +Process BO2 + +388\_12(1) + +``` +graph TD; idle1([idle]) --> register[register outgoing barring program]; register --> active{other program active}; active -- yes --> deactivate[deactivate other outgoing barring program]; deactivate --> activate[activate outgoing barring program]; active -- no --> activate; activate --> acknowledge{{acknowledge}}; acknowledge --> idle2([idle]); +``` + +Flowchart for Process BO2 showing the interaction between call barring programs. The process starts at an 'idle' state, proceeds to 'register outgoing barring program', then checks if 'other program active'. If 'yes', it goes to 'deactivate other outgoing barring program' before continuing. If 'no', it proceeds directly to 'activate outgoing barring program'. Both paths lead to 'activate outgoing barring program', which then leads to 'acknowledge' and back to an 'idle' state. + +Figure 6.2: BO2 Interaction between call barring programs + +![Flowchart for Process BO3 showing interactions between call forwarding services (CFU, CCF, ftm) and barring programs (BAOC, BOIC, BOIC-exHC).](5a4e62bead259c258d069fd3663ea670_img.jpg) + +**Process BO3** 388\_13(1) + +``` +graph TD; idle1([idle]) --> BAOC[activate BAOC]; idle1 --> BOIC[activate BOIC]; idle1 --> BOICexHC[activate BOIC-exHC]; BAOC --> anyCF{any CF active and operative}; anyCF -- yes --> setResult1[set result = denied]; anyCF -- no --> BOIC; BOIC --> CFU1{CFU active and operative}; CFU1 -- yes --> ftm1{ftn in HPLMN country}; CFU1 -- no --> CCF1{CCF active and operative}; CCF1 -- yes --> ftm2{ftn in VPLMN country}; CCF1 -- no --> setResult2[set result = accepted]; ftm2 -- yes --> setResult3[set result = denied]; ftm2 -- no --> setResult4[set result = accepted]; ftm1 -- yes --> setResult4; ftm1 -- no --> setResult3; BOICexHC --> CFU2{CFU active and operative}; CFU2 -- yes --> ftm3{ftn in HPLMN country}; CFU2 -- no --> CCF2{CCF active and operative}; CCF2 -- yes --> ftm4{ftn in VPLMN country}; CCF2 -- no --> ftm5{ftn in HPLMN country}; ftm4 -- yes --> setResult5[set result = denied]; ftm4 -- no --> setResult4; ftm5 -- yes --> setResult4; ftm5 -- no --> setResult6[set result = denied]; setResult1 --> acknowledge{acknowledge}; setResult2 --> acknowledge; setResult3 --> acknowledge; setResult4 --> acknowledge; setResult5 --> acknowledge; setResult6 --> acknowledge; acknowledge --> idle2([idle]); +``` + +BOIC-exHC: Barring of Outgoing International Calls except those directed to the home PLMN country. +BOIC: Barring of Outgoing International Calls. +BAOC: Barring of All Outgoing Calls. +CF: Call Forwarding. +CCF: "Conditional" Call Forwarding. +CFU: Call Forwarding Unconditional. +ftn: forwarded-to number. + +Flowchart for Process BO3 showing interactions between call forwarding services (CFU, CCF, ftm) and barring programs (BAOC, BOIC, BOIC-exHC). + +**Figure 6.3: BO3 Interaction between call forwarding supplementary services and barring of outgoing calls programs** + +![Sequence diagram for activation of barring of outgoing calls between MS, MSC, VLR, and HLR.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + Note right of HLR: PW1 + MS->>MSC: Activate BX + MSC->>VLR: Activate BX + VLR->>HLR: Activate BX + HLR->>VLR: Get password + VLR->>MSC: Get password + MSC->>MS: Password + VLR->>HLR: Password + Note right of HLR: PW2 +BO2 +BO3 + HLR->>VLR: Acknowledge + VLR->>MSC: Acknowledge + MSC->>MS: Release complete + Note left of MS: \Facility +``` + +The diagram illustrates the activation of barring of outgoing calls. It begins with the MS sending an 'Activate BX' message to the MSC. The MSC then forwards this to the VLR, which in turn sends it to the HLR. The HLR responds with a 'Get password' message to the VLR, which is passed on to the MSC and then to the MS. The MS returns a 'Password' to the MSC, which is forwarded to the VLR and then to the HLR. The HLR sends an 'Acknowledge' message back through the VLR and MSC to the MS. Finally, the MSC sends a 'Release complete' message to the MS, with a '\Facility' parameter. Labels PW1, PW2, BO2, and BO3 are associated with the HLR's processing steps. + +Sequence diagram for activation of barring of outgoing calls between MS, MSC, VLR, and HLR. + +Figure 6.4: Activation of barring of outgoing calls + +NOTE: BX indicates any of the barring programs. PW1 and PW2 indicate password handling programs, see 3G TS 23.011. + +### 6.1.3 Deactivation + +The procedure for activation, described in subclause 1.1.2.1, is valid also correspondingly for deactivation with the addition that a barring supplementary service, i.e. the Outgoing barring service, or All barring services can be signalled. + +The information flow for deactivation of barring of outgoing calls is shown in figure 6.5. For more details see 3G TS 23.011. + +![Sequence diagram for Deactivation of barring of outgoing calls](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +This sequence diagram illustrates the interaction for deactivating barring of outgoing calls. It involves four lifelines: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The process begins with the MS sending a 'Deactivate BO' message to the MSC. The MSC then forwards this to the VLR, which in turn sends it to the HLR. The HLR responds with 'PW1' (Password handling program 1). The VLR then sends a 'Get password' request to the HLR, which returns the password as 'PW2'. The VLR sends this 'Password' back to the MSC, which then sends it to the MS. The MS sends an 'Acknowledge' back to the MSC, which then sends it to the VLR. Finally, the MS sends a 'Release complete' message to the MSC, which includes the '\Facility' parameter. + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + Note right of HLR: PW1 + MS->>MSC: Deactivate BO + MSC->>VLR: Deactivate BO + VLR->>HLR: Deactivate BO + HLR-->>VLR: PW1 + VLR->>HLR: Get password + HLR-->>VLR: PW2 + VLR->>MSC: Password + MSC->>MS: Password + MS->>MSC: Acknowledge + MSC->>VLR: Acknowledge + MS->>MSC: Release complete + Note left of MSC: \Facility +``` + +Sequence diagram for Deactivation of barring of outgoing calls + +**Figure 6.5: Deactivation of barring of outgoing calls** + +NOTE: BO indicates the general code for barring of outgoing calls. PW1 and PW2 indicate password handling programs, see 3G TS 23.011. + +### 6.1.4 Interrogation + +The interrogation procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return a list of all basic services to which the given barring program is active. + +The information flow for interrogation of barring of outgoing calls is shown in figure 6.6. + +![Sequence diagram for Interrogation of barring of outgoing calls](e9d825d87c5f85c8dba0664eace96ef4_img.jpg) + +This sequence diagram illustrates the interaction for interrogating barring of outgoing calls. It involves four lifelines: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The process begins with the MS sending an 'Interrogate BX' message to the MSC. The MSC then forwards this to the VLR. The VLR responds with an 'Acknowledge' message to the MSC. Finally, the MS sends a 'Release complete' message to the MSC, which includes the '\Facility' parameter. + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + MS->>MSC: Interrogate BX + MSC->>VLR: Interrogate BX + VLR-->>MSC: Acknowledge + MS->>MSC: Release complete + Note left of MSC: \Facility +``` + +Sequence diagram for Interrogation of barring of outgoing calls + +**Figure 6.6: Interrogation of barring of outgoing calls** + +NOTE: BX indicates any of the barring programs. + +## 6.2 Functions and information flows + +The following Mobile Additional Functions have been identified: + +### MAF017 + +Barring of all outgoing calls related authorizations examination. + +The ability of a PLMN component to determine the authorizations relating to barring of all outgoing calls. See figure 6.7. + +Location: VLR/SGSN/MME + +### MAF018 + +Barring of outgoing international calls related authorizations examination. + +The ability of a PLMN component to determine the authorizations relating to barring of outgoing international calls. See figure 6.8. In case of SMS, the Service Centre Address is used to determine whether SMS transfer is international or not. + +Location: VLR/SGSN/MME + +### MAF020 + +Barring of outgoing international calls except those directed to the home PLMN country related authorizations examination. + +The ability of a PLMN component to determine the authorizations relating to barring of outgoing international calls except those directed to the home PLMN country. See figure 6.9. In case of SMS, the Service Centre Address is used to determine whether the destination is in HPLMN country or not. + +Location: VLR/SGSN/MME + +The information flow for barring of outgoing circuit switched calls in CS domain is shown in figure 6.10A. The information flow for barring of MO SMS is shown in figure 6.10B. + +![Flowchart for Process MAF017: Barring of All Outgoing Calls. The process starts at 'idle', goes to 'initiate handling of BAOC', then checks if it's an 'emergency call'. If 'yes', it skips to 'continue call handling'. If 'no', it checks if 'activated for basic service'. If 'no', it sets 'barring indicator = 'no'' and then proceeds to 'continue call handling'. If 'yes', it sets 'barring indicator = 'yes'', then proceeds to 'continue call handling'. The process ends at 'idle'.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +Process MAF017 388\_17(1) + +``` + +graph TD + Start([idle]) --> Init[initiate handling of BAOC] + Init --> Emergency{emergency call} + Emergency -- yes --> Continue[continue call handling] + Emergency -- no --> Activated{activated for basic service} + Activated -- yes --> SetYes[set barring indicator = 'yes'] + Activated -- no --> SetNo[set barring indicator = 'no'] + SetYes --> Continue + SetNo --> Continue + Continue --> End([idle]) + +``` + +BAOC: Barring of All Outgoing Calls. + +Flowchart for Process MAF017: Barring of All Outgoing Calls. The process starts at 'idle', goes to 'initiate handling of BAOC', then checks if it's an 'emergency call'. If 'yes', it skips to 'continue call handling'. If 'no', it checks if 'activated for basic service'. If 'no', it sets 'barring indicator = 'no'' and then proceeds to 'continue call handling'. If 'yes', it sets 'barring indicator = 'yes'', then proceeds to 'continue call handling'. The process ends at 'idle'. + +NOTE: Emergency call check is applied only at VLR. + +**Figure 6.7: MAF017 Barring of all outgoing calls related authorisations examination (VLR/SGSN/MME)** + +![Flowchart for Process MAF018: Barring of all outgoing international calls related authorisations examination.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Process MAF018 388\_18(1) + +``` + +graph TD + Start([idle]) --> Init[initiate handling of BOIC] + Init --> Emergency{emergency call} + Emergency -- yes --> SetNo[set barring indicator = 'no'] + Emergency -- no --> International{international call} + International -- no --> SetNo + International -- yes --> Activated{activated for basic service} + Activated -- no --> SetNo + Activated -- yes --> SetYes[set barring indicator = 'yes'] + SetYes --> Continue[continue call handling] + SetNo --> Continue + Continue --> End([idle]) + +``` + +BOIC: Barring of Outgoing International Calls. + +Flowchart for Process MAF018: Barring of all outgoing international calls related authorisations examination. + +NOTE: Emergency call check is applied only at VLR. + +**Figure 6.8: MAF018 Barring of all outgoing international calls related authorisations examination (VLR/SGSN/MME)** + +![Flowchart for Process MAF020. The process starts at an 'Idle' state, then moves to 'initiate handling of BOIC-exHC'. It checks if it's an 'emergency call'; if 'yes', it sets the barring indicator to 'no'. If 'no', it checks for 'SMS'; if 'yes', it loops back to 'continue call handling'. If 'no' for SMS, it checks if it's an 'international call'; if 'no', it sets the barring indicator to 'no'. If 'yes' for international call, it checks if the 'destination in HPLMN country'; if 'yes', it sets the barring indicator to 'no'. If 'no', it checks if 'activated for basic service'; if 'no', it sets the barring indicator to 'no'. If 'yes', it sets the barring indicator to 'yes'. All paths eventually lead to 'continue call handling' and then back to 'Idle'.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Process MAF020 + +388\_19(1) + +``` + +graph TD + Start([Idle]) --> Init[initiate handling +of BOIC-exHC] + Init --> EC{emergency +call} + EC -- yes --> SetNo[set barring +indicator = +'no'] + EC -- no --> SMS{SMS} + SMS -- yes --> Continue[continue +call +handling] + SMS -- no --> IC{international +call} + IC -- no --> SetNo + IC -- yes --> Dest{destination +in HPLMN +country} + Dest -- yes --> SetNo + Dest -- no --> Activated{activated +for basic +service} + Activated -- yes --> SetYes[set barring +indicator = +'yes'] + Activated -- no --> SetNo + SetYes --> Continue + SetNo --> Continue + Continue --> End([Idle]) + +``` + +BOIC-exHC: Barring of Outgoing International Calls +except those to the home PLMN country. + +Flowchart for Process MAF020. The process starts at an 'Idle' state, then moves to 'initiate handling of BOIC-exHC'. It checks if it's an 'emergency call'; if 'yes', it sets the barring indicator to 'no'. If 'no', it checks for 'SMS'; if 'yes', it loops back to 'continue call handling'. If 'no' for SMS, it checks if it's an 'international call'; if 'no', it sets the barring indicator to 'no'. If 'yes' for international call, it checks if the 'destination in HPLMN country'; if 'yes', it sets the barring indicator to 'no'. If 'no', it checks if 'activated for basic service'; if 'no', it sets the barring indicator to 'no'. If 'yes', it sets the barring indicator to 'yes'. All paths eventually lead to 'continue call handling' and then back to 'Idle'. + +NOTE: Emergency call check is applied only at VLR. + +**Figure 6.9: MAF020 Barring of outgoing international calls except those directed to the home PLMN country related authorisations examination (VLR/SGSN/MME)** + +![Sequence diagram for Figure 6.10A showing information flow for barring of outgoing circuit switched calls between MS, MSC, VLR, and MSC/LE.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant MSC/LE + + Note right of VLR: MAF017 +MAF018 +MAF020 + + MS->>MSC: set-up + MSC->>VLR: information request + Note right of VLR: MAF017 +MAF018 +MAF020 + VLR-->>MSC: information acknowledge + Note right of MSC: OR1 +Y + MSC->>MS: call reject + Note right of MS: (cause) + Note right of MSC: OR1 +N + MSC->>MSC/LE: set-up + Note right of MSC: CONTINUE AS NORMAL CALL ESTABLISHMENT + +``` + +Sequence diagram for Figure 6.10A showing information flow for barring of outgoing circuit switched calls between MS, MSC, VLR, and MSC/LE. + +NOTE: OR1: call barred Y: yes +N: no + +**Figure 6.10A: Information flow for barring of outgoing circuit switched calls** + +![Sequence diagram for Figure 6.10B showing information flow for barring of MO SMS between MS, SGSN or MSC/VLR or MME, and IW-MSC.](a734898ce18e972938949637c32a34f4_img.jpg) + +``` + +sequenceDiagram + participant MS + participant SGSN or MSC/VLR or MME + participant IW-MSC + + Note right of SGSN: MAF017 +MAF018 +MAF020 + + MS->>SGSN: Message Transfer + Note right of SGSN: MAF017 +MAF018 +MAF020 + Note right of SGSN: OR1 +Y + SGSN-->>MS: Failure Report + Note right of SGSN: OR1 +N + SGSN->>IW-MSC: Forward Short Message + +``` + +Sequence diagram for Figure 6.10B showing information flow for barring of MO SMS between MS, SGSN or MSC/VLR or MME, and IW-MSC. + +NOTE: OR1: call barred Y: yes +N: no + +**Figure 6.10B: Information flow for barring of MO SMS** + +## 6.3 Information stored in the HSS/HLR + +For all call barring supplementary services in the HSS/HLR must be stored: + +- the subscription option "control of barring services" on per subscriber basis. + +This subscription option takes one of the following values: + +- by subscriber using password; +- by the service provider. + +If the subscription option "control of barring services" has been set to "by subscriber using password" for barring of outgoing calls in the HLR must be stored on per subscriber basis: + +- the registration parameter "call barring password". + +The password is valid for all basic services to which barring of outgoing calls applies; + +- the status parameter "wrong password attempts counter" associated with the password. + +Note that the subscription option and the call barring password are parameters which are associated with all call barring services. + +**The outgoing calls barring program may have the following logical states (refer to 3G TS 23.011 for an explanation of the notation):** + +| Provisioning State | Registration State | Activation State | HSS/HLR Induction State | +|---------------------------|---------------------------|-------------------------|--------------------------------| +| (Not Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Not Applicable, | Active and Operative, | Not Induced) | +| (Not Provisioned, | Not Applicable, | Not Active, | Induced) | +| (Provisioned, | Not Applicable, | Not Active, | Induced) | +| (Provisioned, | Not Applicable, | Active and Operative, | Induced) | + +The activation and HSS/HLR induction states may be different for each applicable elementary basic service group. + +The provisioning state shall be on a per subscriber basis, and hence the same for all basic service groups. + +The HSS/HLR shall also store the logical state of the outgoing calls barring program (which shall be one of the valid states listed above) for each applicable elementary basic service group. + +## 6.4 State transition model + +The following figure shows the successful cases of transition between the applicable logical states of the barring of outgoing call program. The state changes are either caused by actions of the service provider, the mobile user or the network. + +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 diagram. + +The diagram only shows operations on an elementary basic service group. + +![State transition model for BAOC, BOIC and BOIC-exHC. The diagram shows six logical states and their transitions including Provision, Withdrawal, Activation, Deactivation, Network Induced, and Network Induced Ended.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) + +The diagram illustrates the state transition model for BAOC, BOIC and BOIC-exHC. It consists of six states represented by ovals and transitions represented by arrows. + +- State 1 (Top):** (Not Provisioned, Not Applicable, Not Active, Not Induced) +- State 2 (Middle Left):** (Provisioned, Not Applicable, Not Active, Not Induced) +- State 3 (Middle Right):** (Provisioned, Not Applicable, Active and Operative, Not Induced) +- State 4 (Lower Left):** (Provisioned, Not Applicable, Not Active, Induced) +- State 5 (Lower Right):** (Provisioned, Not Applicable, Active and Operative, Induced) +- State 6 (Bottom):** (Not Provisioned, Not Applicable, Not Active, Induced) + +Key Transitions: + +- Provision:** Transitions from State 1 to State 2, and from State 6 to State 4. +- Withdrawal:** Transitions from State 2 to State 1, State 3 to State 1, State 4 to State 6, and State 5 to State 6. +- Activation:** Transitions from State 2 to State 3, and State 4 to State 5. +- Deactivation:** Transitions from State 3 to State 2, and State 5 to State 4. +- Network Induced:** Transitions from State 2 to State 4, State 3 to State 5, and State 1 to State 6. +- Network Induced Ended:** Transitions from State 4 to State 2, State 5 to State 3, and State 6 to State 1. + +State transition model for BAOC, BOIC and BOIC-exHC. The diagram shows six logical states and their transitions including Provision, Withdrawal, Activation, Deactivation, Network Induced, and Network Induced Ended. + +**Figure 6.11: State transition model for BAOC, BOIC and BOIC-exHC** + +## 6.5 Transfer of information from HSS/HLR to VLR/SGSN/MME + +If the provisioning state for the outgoing calls barring program is "Provisioned" then when the subscriber registers on a VLR/SGSN/MME, the HSS/HLR shall send that VLR/SGSN/MME information about the logical state of the program for all relevant elementary basic service groups. Only SMS is relevant for SGSN and MME. + +If the HSS/HLR induction state for the outgoing calls barring program is "Induced" then when the subscriber registers on a VLR/SGSN/MME, the HSS/HLR shall send that VLR/SGSN/MME information about the logical state of the program for all relevant elementary basic service groups. + +If the logical state of the outgoing calls barring program is changed while a subscriber is registered on a VLR/SGSN/MME then for the affected basic service groups, the HSS/HLR shall inform the VLR/SGSN/MME of the new logical state of the program. + +The affected basic service group for SGSN and MME is only SMS. + +## 6.6 Information stored in the VLR/SGSN/MME + +For each barring of outgoing calls program the VLR/SGSN/MME shall store the service state information received from the HSS/HLR. + +## 6.7 Handover + +Handover will have no impact on the control procedures and the operation of the service. + +## 6.8 Cross Phase compatibility + +### 6.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber + +In response to a Barring of outgoing calls interrogation request, if the MS or any network element involved is of Phase 1, only information concerning basic service groups for which the activation state has the value "Active and Operative" will be returned. + +### 6.8.2 HLR only support Phase 1 updating of subscriber information + +If the VLR receives the SS-status parameter from a Phase 1 HLR it shall act as if it has received the SS-Status parameter with the values shown in the following: + +- 1) Activated => P bit = 1, R bit = 0 or 1, A bit = 1, Q bit = 0; +- 2) Deactivated => P bit = 1, R bit = 0 or 1, A bit = 0, Q bit = 0 or 1. + +## 6.9 Interworking with VLR or SGSN or MME not supporting Call Barring + +When the serving VLR/SGSN/MME does not support call barring, the HLR/HSS may pass to the VLR/SGSN/MME ODB data to bar outgoing circuit switched call or/and MO SMS. + +# 7 Barring of incoming calls other than Anonymous Call Rejection + +## 7.1 Handling of barring of incoming calls + +### 7.1.0 Applicability + +The user control defined in this section is only applicable in CS domain. + +For MME, only MMEs supporting the SMS in MME option described in 3GPP TS 23.272 [10] may handle barring of MT SMS. + +### 7.1.1 Registration + +If the served mobile subscriber at provision time has selected the subscription option "control of barring services by subscriber using password", he has to register a password at provision time. Furthermore the served mobile subscriber can change the password by an appropriate control procedure at any time. The control procedure consists of three steps: first, the old password has to be provided. Secondly, the new password has to be given, after which it has to be verified by providing it once more, see 3G TS 23.011. + +If the served mobile subscriber at provision time has selected the subscription option "control of barring services by the service provider" an attempt to register a password will be denied and the served mobile subscriber should receive a notification. + +The subscriber can register a new password, thus causing the previous registration to be overridden, see 3G TS 23.011. + +### 7.1.2 Activation + +#### 7.1.2.1 General + +The procedure for activation of Barring of outgoing calls, described in subclause 1.1.2.1, is valid also for activation of Barring of incoming calls. + +The information flow for activation of barring of incoming calls is shown in figure 7.3. For more details see 3G TS 23.011. + +#### 7.1.2.2 Interactions between barring of incoming call programs + +If the mobile subscriber activates barring of all incoming calls and barring of incoming calls when roaming outside the home PLMN country was already activated, barring of incoming calls when roaming outside the home PLMN country will be deactivated and barring of all incoming calls will be activated. + +The SDL diagram in figure 7.1 shows the function to be performed in the HLR in order to deal with this interaction between call barring services. + +See subclause 8.2.3.2 for the interactions with the ACR supplementary service. + +#### 7.1.2.3 Interactions with call forwarding supplementary services + +This section is not applicable for SMS. + +For interactions with call forwarding supplementary services see 3G TS 22.082. + +The SDL diagram in figure 7.2 shows the function to be performed in the HLR in order to deal with the interactions with call forwarding services. + +![SDL Flowchart for Process BI1 showing the logic for activating call barring programs. It includes states, inputs, decisions, and tasks.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +Process BI1 + +388\_21(1) + +``` + +graph TD + Start([idle]) --> Input[activate +incoming +barring program] + Input --> Decision{other +program +active} + Decision -- yes --> Task1[deactivate +other +program] + Decision -- no --> Task2[activate +requested +program] + Task1 --> Task2 + Task2 --> Output[acknowledge] + Output --> End([idle]) + +``` + +SDL Flowchart for Process BI1 showing the logic for activating call barring programs. It includes states, inputs, decisions, and tasks. + +**Figure 7.1: BI1 Interaction between call barring programs** + +![Flowchart for Process BI2 showing interactions between call forwarding and barring services. It starts at 'idle', branches into 'activate BAIC' and 'activate BIC-Roam', then through various decision diamonds for 'any CF active and operative', 'CFU active and operative', 'CCF active and operative', and 'roaming outside HPLMN country', leading to 'set result = denied', 'set result = accepted', and finally 'acknowledge' back to 'idle'.](26d664119ad25250780f554633444e54_img.jpg) + +Process BI2 + +388\_22(1) + +``` +graph TD; idle1([idle]) --> activateBAIC[/activate BAIC/]; idle1 --> activateBICRoam[/activate BIC-Roam/]; activateBAIC --> anyCF{any CF active and operative}; anyCF -- no --> setResultDenied1[set result = denied]; anyCF -- yes --> setResultAccepted[set result = accepted]; activateBICRoam --> CFU{CFU active and operative}; CFU -- yes --> setResultDenied2[set result = denied]; CFU -- no --> CCF{CCF active and operative}; CCF -- no --> setResultAccepted; CCF -- yes --> roaming{roaming outside HPLMN country}; roaming -- no --> setResultAccepted; roaming -- yes --> setResultDenied2; setResultDenied1 --> acknowledge{acknowledge}; setResultAccepted --> acknowledge; setResultDenied2 --> acknowledge; acknowledge --> idle2([idle]); +``` + +CF: Call Forwarding. +CCF: "Conditional" Call Forwarding. +BAIC: Barring of All Incoming Calls. +BIC-Roam: Barring of Incoming Calls when Roaming outside the home PLMN country. + +Flowchart for Process BI2 showing interactions between call forwarding and barring services. It starts at 'idle', branches into 'activate BAIC' and 'activate BIC-Roam', then through various decision diamonds for 'any CF active and operative', 'CFU active and operative', 'CCF active and operative', and 'roaming outside HPLMN country', leading to 'set result = denied', 'set result = accepted', and finally 'acknowledge' back to 'idle'. + +Figure 7.2: BI2 Interaction between call forwarding supplementary services and barring of incoming calls programs + +![Sequence diagram showing the activation of barring of incoming calls between MS, MSC, VLR, and HLR.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + Note right of HLR: PW1 + MS->>MSC: Activate BX + MSC->>VLR: Activate BX + VLR->>HLR: Activate BX + HLR-->>VLR: Get password + VLR-->>MSC: Get password + MSC-->>MS: Get password + MS->>MSC: Password + MSC->>VLR: Password + VLR->>HLR: Password + Note right of HLR: PW2 +BI1 +BI2 + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note left of MS: \Facility +``` + +The sequence diagram illustrates the interaction for activating barring of incoming calls. It starts with the MS sending an 'Activate BX' message to the MSC. The MSC then forwards this to the VLR, which in turn sends it to the HLR. The HLR responds with a 'Get password' message that cascades back through the VLR and MSC to the MS. The MS replies with the 'Password', which is then passed back up the chain from MSC to VLR to HLR. The HLR sends an 'Acknowledge' message back down the chain. Finally, the MSC sends a 'Release complete' message to the MS, accompanied by a '\Facility' parameter. On the HLR side, 'PW1' is noted after the initial activation, and 'PW2', 'BI1', and 'BI2' are noted after the password exchange. + +Sequence diagram showing the activation of barring of incoming calls between MS, MSC, VLR, and HLR. + +Figure 7.3: Activation of barring of incoming calls + +NOTE: BX indicates any of the barring programs. +PW1 and PW2 indicate password handling programs, see 3G TS 23.011. + +### 7.1.3 Deactivation + +The procedure for activation of Barring of outgoing calls, described in subclause 1.1.2.1, is valid also correspondingly for deactivation of Barring of incoming calls with the addition that a barring supplementary service, i.e. the Incoming barring service, or All barring services can be signalled. + +The information flow for deactivation of barring of incoming calls is shown in figure 7.4. For more details see 3G TS 23.011. + +![Sequence diagram showing the deactivation of barring of incoming calls between MS, MSC, VLR, and HLR.](088921fa3f5a44c8551815122517eefd_img.jpg) + +``` + +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + + MS->>MSC: Deactivate BI + MSC->>VLR: Deactivate BI + VLR->>HLR: Deactivate BI + Note right of HLR: PW1 + HLR-->>VLR: Get password + VLR-->>MSC: Get password + MSC-->>MS: Get password + MS->>MSC: Password + MSC->>VLR: Password + VLR->>HLR: Password + Note right of HLR: PW2 + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note left of MS: \Facility + +``` + +The diagram illustrates the sequence of messages for deactivating barring of incoming calls. It involves four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence starts with the MS sending a 'Deactivate BI' message to the MSC. The MSC then forwards this to the VLR, which in turn sends it to the HLR. At the HLR, a password handling program PW1 is triggered. The HLR responds with a 'Get password' message, which is passed back through the VLR and MSC to the MS. The MS replies with a 'Password' message, which is again passed back through the MSC and VLR to the HLR. At the HLR, another password handling program PW2 is triggered. The HLR then sends an 'Acknowledge' message back through the VLR and MSC. Finally, the MSC sends a 'Release complete' message to the MS, which includes a '\Facility' parameter. + +Sequence diagram showing the deactivation of barring of incoming calls between MS, MSC, VLR, and HLR. + +**Figure 7.4: Deactivation of barring of incoming calls** + +NOTE: BI indicates the general code for barring of incoming calls. + PW1 and PW2 indicate password handling programs, see 3G TS 23.011. + +### 7.1.4 Interrogation + +The interrogation procedure enables the mobile subscriber to obtain information about the data stored in the PLMN. After having requested this procedure the network shall return a list of all basic services to which the given program is active. + +The information flow for interrogation of barring of incoming calls is shown in figure 7.5. + +![Sequence diagram showing the interrogation of barring of incoming calls between MS, MSC, VLR, and HLR.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +``` +sequenceDiagram + participant MS + participant MSC + participant VLR + participant HLR + MS->>MSC: Interrogate BX + MSC->>VLR: Interrogate BX + VLR->>HLR: Interrogate BX + HLR-->>VLR: Acknowledge + VLR-->>MSC: Acknowledge + MSC-->>MS: Release complete + Note over MS,MSC: \Facility +``` + +Sequence diagram showing the interrogation of barring of incoming calls between MS, MSC, VLR, and HLR. + +**Figure 7.5: Interrogation of barring of incoming calls** + +NOTE: BX indicates any of the barring programs. + +## 7.2 Functions and information flows + +The following Mobile Additional Functions have been identified: + +### MAF022 + +Barring of all incoming calls related authorizations examination + +The ability of a PLMN component to determine the authorizations relating to barring of incoming calls. See figure 7.6. + +Location: HSS/HLR + +### MAF023 + +Barring of incoming calls when roaming outside the home PLMN country related authorizations examination + +The ability of a PLMN component to determine the authorizations relating to barring of incoming calls when roaming outside the home PLMN country. See figure 7.7. + +Location: HSS/HLR + +The information flow for barring of incoming circuit switched calls is shown in figure 7.8A. The information flow for barring of MT SMS is shown in figure 7.8B. + +![Flowchart for Process MAF022: Barring of all incoming circuit switched calls and MT SMS related authorisations examination (HSS/HLR).](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +Process MAF022 388\_26(1) + +``` +graph TD; Start([idle]) --> Initiate[initiate handling of BAIC]; Initiate --> Decision{activated for basic service}; Decision -- yes --> SetYes[set barring indicator = 'yes']; Decision -- no --> SetNo[set barring indicator = 'no']; SetYes --> Continue{continue call handling}; SetNo --> Continue; Continue --> End([idle]); Note[BAIC: Barring of All Incoming Calls.] +``` + +The flowchart illustrates the process for MAF022, titled 'Barring of all incoming circuit switched calls and MT SMS related authorisations examination (HSS/HLR)'. It begins with an 'idle' state, followed by 'initiate handling of BAIC'. A decision diamond asks if the service is 'activated for basic service'. If 'yes', it proceeds to 'set barring indicator = 'yes''. If 'no', it proceeds to 'set barring indicator = 'no''. Both paths lead to a 'continue call handling' decision, which then leads to the final 'idle' state. A note indicates that BAIC stands for 'Barring of All Incoming Calls.'. + +Flowchart for Process MAF022: Barring of all incoming circuit switched calls and MT SMS related authorisations examination (HSS/HLR). + +**Figure 7.6: MAF022 Barring of all incoming circuit switched calls and MT SMS related authorisations examination (HSS/HLR)** + +![Flowchart for Process MAF023: Barring of incoming circuit switched calls and MT SMS when roaming outside the home PLMN country related authorisations examination (HSS/HLR).](dd5771673aececa53d42ece89218299d_img.jpg) + +Process MAF023 + +388\_27(1) + +``` + +graph TD + Start([idle]) --> Init[initiate +handling +of BIC-Roam] + Init --> Roaming{roaming +abroad} + Roaming -- yes --> Activated{activated +for basic +service} + Roaming -- no ----> SetNo[set barring +indicator = +'no'] + Activated -- yes --> SetYes[set barring +indicator = +'yes'] + Activated -- no --> SetNo + SetYes --> Continue{continue +call +handling} + SetNo --> Continue + Continue --> End([idle]) + +``` + +BIC-Roam: Barring of Incoming Calls when roaming +outside the home PLMN country. + +Flowchart for Process MAF023: Barring of incoming circuit switched calls and MT SMS when roaming outside the home PLMN country related authorisations examination (HSS/HLR). + +**Figure 7.7: MAF023 Barring of incoming circuit switched calls and MT SMS when roaming outside the home PLMN country related authorisations examination (HSS/HLR)** + +![Sequence diagrams showing information flow for barring of incoming circuit switched calls. The top diagram involves MSa, MSCa, HLRb, MSCb, and MSb. The bottom diagram involves TE, LE, HLRb, MSCb, and MSb. Both diagrams show a 'set-up' message followed by an 'info req' to the HLR, which responds with 'info ack' containing MAFO22/MAFO23. The LE/MSCa then checks OR1 status. If OR1 is Y (yes), it sends a 'call reject' with a cause to the MSa/TE. If OR1 is N (no), it sends a 'set-up' message to MSCb, which then sends a 'set-up' to MSb. Both diagrams conclude with 'CONTINUE AS NORMAL CALL ESTABLISHMENT'.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +sequenceDiagram + participant MSa + participant MSCa + participant HLRb + participant MSCb + participant MSb + + MSa->>MSCa: set-up + MSCa->>HLRb: info req + Note right of HLRb: MAFO22 +MAFO23 + HLRb-->>MSCa: info ack + + alt OR1 Y + MSCa-->>MSa: call reject (cause) + else OR1 N + MSCa->>MSCb: set-up + MSCb->>MSb: set-up + end + + Note over MSCa, MSb: CONTINUE AS NORMAL CALL ESTABLISHMENT + +``` + +``` + +sequenceDiagram + participant TE + participant LE + participant HLRb + participant MSCb + participant MSb + + TE->>LE: set-up + LE->>HLRb: info req + Note right of HLRb: MAFO22 +MAFO23 + HLRb-->>LE: info ack + + alt OR1 Y + LE-->>TE: call reject (cause) + else OR1 N + LE->>MSCb: set-up + MSCb->>MSb: set-up + end + + Note over LE, MSb: CONTINUE AS NORMAL CALL ESTABLISHMENT + +``` + +Sequence diagrams showing information flow for barring of incoming circuit switched calls. The top diagram involves MSa, MSCa, HLRb, MSCb, and MSb. The bottom diagram involves TE, LE, HLRb, MSCb, and MSb. Both diagrams show a 'set-up' message followed by an 'info req' to the HLR, which responds with 'info ack' containing MAFO22/MAFO23. The LE/MSCa then checks OR1 status. If OR1 is Y (yes), it sends a 'call reject' with a cause to the MSa/TE. If OR1 is N (no), it sends a 'set-up' message to MSCb, which then sends a 'set-up' to MSb. Both diagrams conclude with 'CONTINUE AS NORMAL CALL ESTABLISHMENT'. + +NOTE: info req: information request + info ack: information acknowledge + OR1: call barred Y: yes + N: no. + +**Figure 7.8A: Information flow for barring of incoming circuit switched calls** + +![Sequence diagram showing information flow for barring of MT SMS between SC, SMS-GMSC, HSS/HLR, and SGSN or MSC/VLR or MME.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant SC + participant SMS-GMSC + participant HSS/HLR + participant SGSN or MSC/VLR or MME + + SC->>SMS-GMSC: Message Transfer + SMS-GMSC->>HSS/HLR: Info req + Note right of HSS/HLR: MAF022 +MAF023 + HSS/HLR-->>SMS-GMSC: Info ack + Note over SMS-GMSC: OR1 +Y + SMS-GMSC->>SC: Failure Report + Note over SMS-GMSC: OR1 +N + SMS-GMSC->>SGSN or MSC/VLR or MME: Forward Short Message + Note over SMS-GMSC, SGSN or MSC/VLR or MME: Continue as normal SMS transfer + +``` + +Sequence diagram showing information flow for barring of MT SMS between SC, SMS-GMSC, HSS/HLR, and SGSN or MSC/VLR or MME. + +NOTE: info req: information request +info ack: information acknowledge +OR1: call barred Y: yes +N: no. + +**Figure 7.8B: Information flow for barring of MT SMS** + +## 7.3 Information stored in the HSS/HLR + +For all call barring supplementary services in the HSS/HLR must be stored: + +- the subscription option "control of barring services" on per subscriber basis. + +This subscription option takes one of the following values: + +- by subscriber using password; +- by the service provider. + +If the subscription option "control of barring services" has been set to "by subscriber using password" for barring of incoming calls in the HLR must be stored on a per subscriber basis: + +- the registration parameter "call barring password". + +The password is valid for all basic services to which barring of incoming calls applies; + +- the status parameter "wrong password attempts counter" associated with the password. + +Note that the subscription option and the call barring password are parameters which are associated with all call barring services. + +**The incoming calls barring program may have the following logical states (refer to 3G TS 23.011 for an explanation of the notation):** + +| Provisioning State | Registration State | Activation State | HSS/HLR Induction State | +|--------------------|--------------------|-----------------------|-------------------------| +| (Not Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Not Applicable, | Not Active, | Not Induced) | +| (Provisioned, | Not Applicable, | Active and Operative, | Not Induced) | + +**The program of barring of incoming call when roaming outside the home PLMN country may also have the following logical state:** + +| Provisioning State | Registration State | Activation State | HSS/HLR Induction State | +|--------------------|--------------------|-----------------------|-------------------------| +| (Provisioned, | Not Applicable, | Active and Quiescent, | Not Induced) | + +The activation and HSS/HLR induction states may be different for each applicable elementary basic service group. + +The provisioning state shall be on a per subscriber basis, and hence the same for all basic service groups. + +The HSS/HLR shall also store the logical state of the incoming calls barring program (which shall be one of the valid states listed above) for each applicable elementary basic service group. + +## 7.4 State transition model + +The following figures show the successful cases of transition between the applicable logical states of the call barring program. The state changes are either caused by actions of the service provider, the mobile user or the network. + +Note that error cases are not shown in the diagrams 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 diagrams. + +The diagrams only show operations on an elementary basic service group. + +![State transition model for BAIC diagram showing three states and their transitions.](6361dfaef83c9ffc3b147e1627ba76a1_img.jpg) + +``` + +stateDiagram-v2 + [*] --> S1 : Provision + S1 --> S2 : Withdrawal + S2 --> S1 : Deactivation + S2 --> S3 : Activation + S3 --> S1 : Withdrawal + S3 --> S2 : Withdrawal + + state "S1: (Not Provisioned, Not Applicable, Not Active, Not Induced)" as S1 + state "S2: (Provisioned, Not Applicable, Not Active, Not Induced)" as S2 + state "S3: (Provisioned, Not Applicable, Active and Operative, Not Induced)" as S3 + +``` + +The diagram illustrates the state transition model for BAIC. It consists of three states represented by ovals: + + +- Top State:** (Not Provisioned, Not Applicable, Not Active, Not Induced) +- Bottom Left State:** (Provisioned, Not Applicable, Not Active, Not Induced) +- Bottom Right State:** (Provisioned, Not Applicable, Active and Operative, Not Induced) + + Transitions are as follows: + + +- An arrow labeled **Provision** points from the Top State to the Bottom Left State. +- An arrow labeled **Withdrawal** points from the Bottom Left State back to the Top State. +- An arrow labeled **Deactivation** points from the Bottom Right State to the Bottom Left State. +- An arrow labeled **Activation** points from the Bottom Left State to the Bottom Right State. +- An arrow labeled **Withdrawal** points from the Bottom Right State back to the Top State. +- An arrow labeled **Withdrawal** points from the Bottom Right State back to the Bottom Left State. + +State transition model for BAIC diagram showing three states and their transitions. + +**Figure 7.9: State transition model for BAIC** + +![State transition model for BIC-Roam diagram showing four states and their transitions.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` + +stateDiagram-v2 + [*] --> S1 : Provision + S1 --> S2 : Withdrawal + S2 --> S1 : Deactivation + S2 --> S3 : Activation + S3 --> S1 : Withdrawal + S3 --> S4 : SS-I + S4 --> S3 : SS-I/E + S4 --> S1 : Deactivation + S4 --> S2 : Withdrawal + S4 --> S1 : Withdrawal + + state " (Not Provisioned, Not Applicable, Not Active, Not Induced) " as S1 + state " (Provisioned, Not Applicable, Not Active, Not Induced) " as S2 + state " (Provisioned, Not Applicable, Active and Operative, Not Induced) " as S3 + state " (Provisioned, Not Applicable, Active and Quiescent, Not Induced) " as S4 + +``` + +The diagram illustrates the state transition model for BIC-Roam. It consists of four states represented by ovals: + + +- Top State:** (Not Provisioned, Not Applicable, Not Active, Not Induced) +- Left State:** (Provisioned, Not Applicable, Not Active, Not Induced) +- Right State:** (Provisioned, Not Applicable, Active and Operative, Not Induced) +- Bottom State:** (Provisioned, Not Applicable, Active and Quiescent, Not Induced) + + Transitions are as follows: + + +- An arrow labeled **Provision** points from the top state to the left state. +- An arrow labeled **Withdrawal** points from the left state to the top state. +- An arrow labeled **Deactivation** points from the left state to the right state. +- An arrow labeled **Activation** points from the right state to the left state. +- An arrow labeled **Withdrawal** points from the right state to the top state. +- An arrow labeled **SS-I** points from the right state to the bottom state. +- An arrow labeled **SS-I/E** points from the bottom state to the right state. +- An arrow labeled **Deactivation** points from the bottom state to the left state. +- An arrow labeled **Withdrawal** points from the bottom state to the top state. + +State transition model for BIC-Roam diagram showing four states and their transitions. + +**Figure 7.10: State transition model for BIC-Roam** + +NOTE: SS-I: SS Interaction started or Subscriber in HPLMN country. + SS-I/E: SS Interaction ended or Subscriber not in HPLMN country. + +## 7.5 Transfer of information from HSS/HLR to VLR/SGSN/MME + +No information is transferred from HSS/HLR to VLR/SGSN/MME for the incoming calls barring program. + +## 7.6 Information stored in the VLR/SGSN/MME + +No information is stored in the VLR/SGSN/MME. + +## 7.7 Handover + +Handover will have no impact on the control procedures and the operation of the service. + +## 7.8 Cross Phase compatibility + +### 7.8.1 MS, MSC, VLR or HLR only support Phase 1 control of SS by the subscriber + +In response to a Barring of incoming calls interrogation request, if the MS or any network element involved is of Phase 1, only information concerning basic service groups for which Barring of incoming calls is active will be returned. + +In Phase 1 the state active and quiescent is not used in the HLR. + +In Phase 2 the HLR will support the quiescent state. + +As this quiescent state is only relevant within the HLR a Phase 1 MSC/VLR and a Phase 1 MS can support the Phase 2 interrogation even if the service becomes quiescent, i.e. there is no functional cross Phase compatibility problem. + +Note that the interrogation result received by the user will be in Phase 1 and 2 a list of basic services. The only difference is that in Phase 1 it contains the active basic services irrespective of whether it is operative or quiescent. + +### 7.8.2 HLR only supports Phase 1 updating of subscriber information + +In Phase 1 the VLR stores the activation status also for barring of incoming calls. + +In Phase 2 no information is stored in the VLR in case of barring of incoming calls. The VLR may receive subscription information for barring of incoming calls from a Phase 1 HLR. In this case the VLR shall ignore this information. + +# 8 Anonymous Call Rejection + +## 8.1 General + +Anonymous Call Rejection (ACR) is a supplementary service of the CS domain that allows a mobile subscriber to reject incoming calls from users who have restricted the presentation of their calling line identity according to the CLIR supplementary service (see 3GPP TS 23.081 [5]). + +The ACR supplementary service shall reject all calls with CLI marked "presentation restricted" according to CLIR. The calls shall be rejected regardless of the current state (e.g. free or busy) of the served subscriber's access. The called mobile subscriber shall not be alerted. + +The ACR supplementary service shall not reject calls terminated for the mobile subscriber without a CLI or when the CLI presentation is not available, is allowed, or is restricted by the network. + +The ability of the mobile subscriber to set-up outgoing calls shall remain unaffected. + +The calling user shall be given an appropriate indication that the call has been rejected due to the application of the ACR supplementary service. + +The telecom services to which ACR applies are defined in 3GPP TS 22.004 [6]. The service may be valid for all incoming calls or just associated with a specific basic service group. + +## 8.2 Procedures + +### 8.2.1 Provision and withdrawal + +The ACR supplementary service may be provisioned to or withdrawn from a subscription by administrative actions in the HLR. The HLR shall update the subscription information accordingly. This is transparent to the VLR and thus does not require any transfer of updated subscription information to the VLR. + +### 8.2.2 Registration and erasure + +Not applicable. + +### 8.2.3 Activation and deactivation + +#### 8.2.3.1 General + +When provisioned in the subscription, the mobile subscriber should be able to activate or deactivate the ACR supplementary service by USSD procedure (see 3GPP TS 23.090 [7]). The USSD strings to be used to activate or deactivate the service are operator specific and should be operator configurable in the HLR. + +The mobile subscriber may be able to activate or deactivate ACR per basic service group, subject to the capabilities of the HLR. An activation or deactivation request without any specific basic service group information shall be interpreted as applying to all basic service groups (applicable to ACR). + +Calls that are on-going at the time the ACR supplementary service is activated shall not be affected. Any new incoming call not allowed by the ACR supplementary service shall be barred. + +#### 8.2.3.2 Interactions with other incoming call barring programs + +ACR may be active simultaneously with Barring of incoming calls when roaming outside of the home PLMN country (BIC-Roam) but can not be active simultaneously with Barring of all incoming calls (BAIC), per basic service group. The HLR shall ensure that exclusive barring programs are not active simultaneously per basic service group. The activation of one specific barring program will override an already active exclusive one (i.e. the old one shall be permanently deactivated). + +If ACR and BIC-Roam are active simultaneously for a specific basic service group, BIC-Roam shall apply when the mobile subscriber is roaming outside the HPLMN. + +#### 8.2.3.3 Logical states in the HLR for the ACR supplementary service + +Table 8.2.3.3.1 shows the logical states that the ACR supplementary service may have in the HLR (see 3GPP TS 23.011 [3] for an explanation of the notation). + +**Table 8.2.3.3.1: Logical states in the HLR for the ACR supplementary service** + +| Provisioning State | Registration State | Activation State | HLR Induction State | +|--------------------|--------------------|----------------------|---------------------| +| Not Provisioned | Not Applicable | Not Active | Not Induced | +| Provisioned | Not Applicable, | Not Active | Not Induced | +| Provisioned | Not Applicable | Active and Operative | Not Induced | + +The activation state may be different for each applicable elementary basic service group. + +The provisioning state shall be on a per subscriber basis, and hence the same for all basic service groups. + +Figure 8.2.3.3.1 shows the successful cases of transition between the applicable logical states of the ACR supplementary service. The state changes are either caused by actions of the service provider or the mobile user. Error cases are not shown in the diagram as they normally do not cause a state change. The diagrams only show operations on an elementary basic service group. + +![State transition model for ACR. The diagram shows three states represented by ovals: (Not Provisioned, Not Applicable, Not Active, Not Induced) at the top, (Provisioned, Not Applicable, Not Active, Not Induced) at the bottom left, and (Provisioned, Not Applicable, Active and Operative, Not Induced) at the bottom right. Transitions are: Provision (top to bottom left), Withdrawal (bottom left to top), Deactivation (bottom right to bottom left), Activation (bottom left to bottom right), and Withdrawal (bottom right to top).](02d0c8a07c481d880b73a25d02050fad_img.jpg) + +``` + +stateDiagram-v2 + [*] --> State1 : (Not Provisioned, Not Applicable, Not Active, Not Induced) + State1 --> State2 : (Provisioned, Not Applicable, Not Active, Not Induced) : Provision + State2 --> State1 : Withdrawal + State2 --> State3 : (Provisioned, Not Applicable, Active and Operative, Not Induced) : Activation + State3 --> State2 : Deactivation + State3 --> State1 : Withdrawal + +``` + +State transition model for ACR. The diagram shows three states represented by ovals: (Not Provisioned, Not Applicable, Not Active, Not Induced) at the top, (Provisioned, Not Applicable, Not Active, Not Induced) at the bottom left, and (Provisioned, Not Applicable, Active and Operative, Not Induced) at the bottom right. Transitions are: Provision (top to bottom left), Withdrawal (bottom left to top), Deactivation (bottom right to bottom left), Activation (bottom left to bottom right), and Withdrawal (bottom right to top). + +**Figure 8.2.3.3.1: State transition model for ACR** + +### 8.2.4 Invocation + +#### 8.2.4.1 General + +When the ACR supplementary service has been activated, then the ACR supplementary service shall automatically be invoked by the HLR. If the HLR receives a request for routing information for a call directed to a mobile subscriber who is subject to ACR for the corresponding basic service group, the HLR shall return a negative response to the request for routing information, with the indication that the call is rejected because of ACR, if the calling line identity is marked as "presentation restricted" according to the CLIR supplementary service. ACR shall not be invoked for incoming calls that do not have their CLI or that have their CLI marked "not available", "presentation allowed" or "presentation restricted by network". + +Upon receipt of that indication, the GMSC shall connect the call to a recorded announcement determined by the network operator or/and should relay this error indication to the calling user. + +#### 8.2.4.2 Terminating Network Information flow + +The information flow for rejection of an anonymous MT call is shown in figure 8.2.4.2.1. It applies to a mobile terminating call with CLI marked "presentation restricted", if the HLR and the GMSC supports the ACR supplementary service and the called mobile subscriber has activated ACR for the corresponding basic service group. + +![Sequence diagram showing the information flow for rejection of an anonymous MT call. The diagram involves four entities: GMSC, HLR, MSC/VLR, and MS (B). The process starts with an incoming call to the GMSC. The GMSC sends a 'Send routing Info request' to the HLR. The HLR responds with 'Provide Roaming Number' to the MSC/VLR, which then sends a 'response (MSRN)' back to the GMSC. A dashed box labeled 'Call not barred' encloses this initial exchange. Below this, a blue bar indicates the 'Normal MT call procedure'. Following this, a dashed box labeled 'Call barred' contains the rejection steps: the HLR sends a 'Reject (cause= ACR)' message to the GMSC; the GMSC then performs an 'announcement' and 'Call clearing'.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +``` + +sequenceDiagram + participant GMSC + participant HLR + participant MSC/VLR + participant MS (B) + + Note left of GMSC: Incoming call + GMSC->>HLR: 1. Send routing Info request + Note right of HLR: Call not barred + HLR->>MSC/VLR: Provide Roaming Number + MSC/VLR->>GMSC: response (MSRN) + Note over GMSC, HLR, MSC/VLR, MS (B): Normal MT call procedure + Note right of HLR: Call barred + HLR->>GMSC: 2. Reject (cause= ACR) + Note left of GMSC: 3. announcement + Note left of GMSC: 4. Call clearing + +``` + +Sequence diagram showing the information flow for rejection of an anonymous MT call. The diagram involves four entities: GMSC, HLR, MSC/VLR, and MS (B). The process starts with an incoming call to the GMSC. The GMSC sends a 'Send routing Info request' to the HLR. The HLR responds with 'Provide Roaming Number' to the MSC/VLR, which then sends a 'response (MSRN)' back to the GMSC. A dashed box labeled 'Call not barred' encloses this initial exchange. Below this, a blue bar indicates the 'Normal MT call procedure'. Following this, a dashed box labeled 'Call barred' contains the rejection steps: the HLR sends a 'Reject (cause= ACR)' message to the GMSC; the GMSC then performs an 'announcement' and 'Call clearing'. + +**Figure 8.2.4.2.1: Information flow for rejection of an anonymous MT call** + +1. Upon receipt of an incoming call, the GMSC sends a MAP Send Routing Information request to the HLR. A GMSC that supports the ACR supplementary service shall pass to the HLR the Additional Signal Info IE including the CLI information if available as specified for the CLI supplementary service in 3GPP TS 23.081 [5] subclause 1.2.3. +2. Upon receipt of the MAP Send Routing Information request, an HLR that supports the ACR supplementary service shall return an SRI negative response with a cause indicating Anonymous Call Rejection if the mobile subscriber has activated ACR for the corresponding basic service group and the calling line identity is marked as "presentation restricted" according to the CLIR supplementary service. + +The HLR shall determine whether the calling line identity is marked as "presentation restricted" using the 'Address presentation restricted indicator' of the Calling Party Number IE if received in the Additional Signal Info IE. + +3. Upon receipt of a SRI negative response with the cause indicating Anonymous Call Rejection, the GMSC shall signal to the originating network that in-band information is available due to anonymous call rejection ("call rejected due to feature at destination") and play a specific in-band announcement towards the calling user to signal that the call has been rejected due to the application of the ACR supplementary service. +4. After the announcement has been completed, the GMSC shall initiate the call release with a cause indicating normal call release. + +#### 8.2.4.2a Originating Network behaviour + +Upon receipt of the indication from the terminating network that in-band information is available, the originating MSC server shall request the MGW to through-connect the bearer terminations so that the bearer is backward through-connected unless already done. This allows the calling user to hear the announcement played by the terminating network when it rejects an anonymous call. + +Upon receipt of a call release request with a cause indicating that the call has been rejected due to anonymous call rejection ("call rejected due to feature at destination"), the originating MSC may play an announcement towards the calling user to signal that the call has been rejected due to anonymous call rejection. If no local announcement is played, the originating MSC shall signal an appropriate cause (e.g. "call rejected due to feature at destination", "call rejected") when releasing the call towards the calling user. This allows the calling user to know why the call is rejected when an + +external terminating network rejects an anonymous call without providing in-band information towards the originating network. + +NOTE: The support of cause 24 "call rejected due to feature at destination" was introduced into 3GPP TS 24.008 [9] from Rel-10 which means that some UEs will not recognise this and will treat as "Normal, unspecified". + +#### 8.2.4.3 Mobile Additional Function + +The following Mobile Additional Function has been identified: + +#### MAF024 + +ACR related authorizations examination + +The ability of a PLMN component to determine the authorizations relating to ACR. See figure 8.2.4.3.1. + +Location: HLR + +![Flowchart for Process MAF024: Anonymous Call Rejection related authorisations examination (HLR). The process starts at 'Idle', proceeds to 'initiate handling of ACR', then checks if 'ACR activated for basic service'. If 'No', it goes to 'set barring indicator = 'no''. If 'yes', it checks if 'CL marked as "presentation restricted"?'. If 'No', it goes to 'set barring indicator = 'no''. If 'yes', it goes to 'set barring indicator = 'yes''. Both 'set barring indicator' paths lead to 'continue call handling', which then returns to 'Idle'.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +Process MAF024 + +Process in the HLR to check ACR + +MAF024(1) + +Signals to/from the left are to/from the HLR procedure Check\_IC\_Barring + +``` +graph TD; Idle1([Idle]) --> Init[initiate handling of ACR]; Init --> ACR{ACR activated for basic service}; ACR -- No --> SetNo[set barring indicator = 'no']; ACR -- yes --> CL{CL marked as 'presentation restricted'?}; CL -- No --> SetNo; CL -- yes --> SetYes[set barring indicator = 'yes']; SetYes --> Continue{continue call handling}; SetNo --> Continue; Continue --> Idle2([Idle]); +``` + +Flowchart for Process MAF024: Anonymous Call Rejection related authorisations examination (HLR). The process starts at 'Idle', proceeds to 'initiate handling of ACR', then checks if 'ACR activated for basic service'. If 'No', it goes to 'set barring indicator = 'no''. If 'yes', it checks if 'CL marked as "presentation restricted"?'. If 'No', it goes to 'set barring indicator = 'no''. If 'yes', it goes to 'set barring indicator = 'yes''. Both 'set barring indicator' paths lead to 'continue call handling', which then returns to 'Idle'. + +Figure 8.2.4.3.1: MAF024 Anonymous Call Rejection related authorisations examination (HLR) + +### 8.2.5 Interrogation + +When provisioned in the subscription, the mobile subscriber should be able to interrogate the network to determine the status of the ACR supplementary service by USSD procedure (see 3GPP TS 23.090 [7]). The USSD string to be used to interrogate the status of the service is operator specific and should be operator configurable in the HLR. + +### 8.2.6 Exceptional procedures + +If the mobile subscriber attempts to activate, deactivate or interrogates the ACR supplementary service and the HLR can not comply to the request, the HLR shall reject the request. + +Possible reasons for rejection are: + +- the ACR supplementary service is not subscribed to. + +## 8.3 Interactions with other supplementary services + +See 3GPP TS 22.088 [8] subclause 2.6. + +## 8.4 Interactions with other network features and services + +### 8.4.1 Operator Determined Barring (ODB) + +The call shall be barred if the incoming call to the mobile subscriber is determined to be barred by either the Operator Determined Barring service or the ACR supplementary service. + +### 8.4.2 Optimal Routeing + +The calling user may not get an indication that the call is rejected due to the application of the ACR supplementary service if the GMSC does not support the ACR supplementary service. + +# Annex A (informative): Change history + +| TSG CN# | Spec | CR | Rev | Phase | Cat | New Ver | Subject/Comment | +|----------|-----------|------|-----|--------|-----|---------|---------------------------------------------------------------------------------------| +| Apr 1999 | GSM 03.88 | | | R97 | | | Transferred to 3GPP CN1 | +| CN#03 | 23.088 | | | R99 | | 3.0.0 | Approved at CN#03 | +| CN#07 | 23.088 | 001 | 1 | R99 | | 3.1.0 | Introduction of 'Notification to CSE flag' to the call barring supplementary service. | +| CN#09 | 23.088 | 002 | 1 | R99 | F | 3.2.0 | SDL refresh | +| CN#11 | 23.088 | | | Rel-4 | | 4.0.0 | Release 4 after CN#11 | +| CN#16 | 23.088 | | | Rel-5 | | 5.0.0 | Release 5 after CN#16 | +| CN#19 | 23.088 | 003 | 1 | Rel-6 | | 6.0.0 | Introducing SMS Call Barring in PS domain | +| CT#36 | 23.088 | | | Rel-7 | | 7.0.0 | Upgraded unchanged from Rel-6 | +| CT#42 | 23.088 | | | Rel-8 | | 8.0.0 | Upgraded unchanged from Rel-7 | +| CT#46 | 23.088 | - | - | Rel-9 | | 9.0.0 | Update to Rel-9 version (MCC) | +| 2011-03 | 23.088 | - | - | Rel-10 | | 10.0.0 | Update to Rel-10 version (MCC) | +| CT#53 | 23.088 | 0004 | 2 | Rel-11 | B | 11.0.0 | Addition of Anonymous Call Rejection in the CS domain | +| CT#54 | 23.088 | 0005 | 1 | Rel-11 | B | 11.1.0 | Originating & Terminating network Information Flows | +| CT#62 | 23.088 | 0006 | 1 | Rel-11 | F | 11.2.0 | SMSC Usage Restriction in Roaming | +| - | 23.088 | | | Rel-11 | | 11.2.1 | Change History updated to include CR#0006r1 | +| CT#63 | 23.088 | 0007 | 1 | Rel-11 | F | 11.3.0 | Call barring services with the SMS in MME option | +| 2014-09 | 23.088 | - | - | Rel-12 | | 12.0.0 | Update to Rel-12 version (MCC) | +| 2015-12 | 23.088 | - | - | Rel-13 | | 13.0.0 | Update to Rel-13 version (MCC) | +| 2017-03 | 23.088 | - | - | Rel-14 | | 14.0.0 | Update to Rel-14 version (MCC) | +| 2018-06 | 23.088 | - | - | Rel-15 | - | 15.0.0 | Update to Rel-15 version (MCC) | +| 2020-07 | 23.088 | - | - | Rel-16 | - | 16.0.0 | Update to Rel-16 version (MCC) | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23101/34f788b0e5bc8af774fa5561c22e6d01_img.jpg b/marked/Rel-16/23_series/23101/34f788b0e5bc8af774fa5561c22e6d01_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..621f0d59b0c23d599ca22a0737d87ebcaaf7654b --- /dev/null +++ b/marked/Rel-16/23_series/23101/34f788b0e5bc8af774fa5561c22e6d01_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:79ee63de4f16ad1d260aae8a245541b7b04751674c5d92f3a9e1bc0f7ffc0712 +size 23427 diff --git a/marked/Rel-16/23_series/23101/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23101/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..84cc34b711c4d9a7ba239688d44bbf86a6d90b5c --- /dev/null +++ b/marked/Rel-16/23_series/23101/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab7f9cc057ca3d4ed0dba055e6febde6fbf950b537fb73725b3c9bb0549ba721 +size 65686 diff --git a/marked/Rel-16/23_series/23101/5d76c2e9976aaf97001ee189908830fb_img.jpg b/marked/Rel-16/23_series/23101/5d76c2e9976aaf97001ee189908830fb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b2e013c3c8a78aee278aa49dc83117ee295b138 --- /dev/null +++ b/marked/Rel-16/23_series/23101/5d76c2e9976aaf97001ee189908830fb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:45be01cc1604ada83710c85e8305a98e9c7bf093c2f1f15a54a5e0ddeeb9250c +size 65323 diff --git a/marked/Rel-16/23_series/23101/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/marked/Rel-16/23_series/23101/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd9489e208d2b45ba13cde12ccd0375ca45cb3c6 --- /dev/null +++ b/marked/Rel-16/23_series/23101/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7853624c66fe8dd4dc7a247919db6d2e77976333e69a449e6a8532a58807b81c +size 56310 diff --git a/marked/Rel-16/23_series/23101/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23101/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..618dc17b574a054c758870d6dc88d7e585f0bf8c --- /dev/null +++ b/marked/Rel-16/23_series/23101/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ef83d36bf0f8cb012fea0a7b8fee2e6855bdd8f217aa728333ff34a0b845d68 +size 11968 diff --git a/marked/Rel-16/23_series/23101/raw.md b/marked/Rel-16/23_series/23101/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..26ce71f39b1073dc585e2b878b8069e095b84044 --- /dev/null +++ b/marked/Rel-16/23_series/23101/raw.md @@ -0,0 +1,361 @@ + + + + + + +# Contents + +| | | +|------------------------------------------------------|----| +| Foreword ..... | 4 | +| Introduction ..... | 4 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions, symbols and abbreviations..... | 5 | +| 3.1 Definitions..... | 5 | +| 3.2 Symbols..... | 5 | +| 3.3 Abbreviations ..... | 5 | +| 4 General..... | 6 | +| 5 Domains in UMTS..... | 6 | +| 5.1 Domain split ..... | 7 | +| 5.2 User equipment Domain..... | 7 | +| 5.2.1 Mobile equipment Domain..... | 8 | +| 5.2.2 USIM Domain ..... | 8 | +| 5.3 Infrastructure Domain ..... | 8 | +| 5.3.1 Access Network Domain..... | 8 | +| 5.3.2 Core Network Domain ..... | 9 | +| 5.3.2.1 Serving Network Domain ..... | 9 | +| 5.3.2.2 Home Network Domain..... | 9 | +| 5.3.2.3 Transit Network Domain ..... | 9 | +| 6 Functional Communication between UMTS domains..... | 9 | +| 6.1 Transport stratum ..... | 11 | +| 6.2 Access Stratum..... | 12 | +| 6.3 Serving Stratum..... | 12 | +| 6.4 Home Stratum ..... | 12 | +| 6.5 Application Stratum ..... | 13 | +| Annex A (informative): Change History..... | 14 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- Introduction + +UMTS will support a wide range of applications with different quality of service profiles. At present many of these applications are not possible to predict. Also the usage of the different applications are difficult to predict i.e. it is not possible to optimise UMTS to only one set of applications. One conclusion of this is that UMTS must be built in such a way that it is flexible and possible to evolve so it will have a long technical lifetime. Therefore a modular approach is recommended when defining the network parts of UMTS. This is in line with the recommendation from GMM. In this context a module represents a part of a UMTS network i.e. one or several physical network nodes that together implements some functionality. The modular approach should also make UMTS possible to implement efficiently in different environments. + +# --- 1 Scope + +This TS defines the basic physical and functional separation of UMTS. The contents of this specification is limited to those features that are common to all UMTS networks independent of their origin. It identifies and names the reference points and functional groupings appearing at this level. + +# --- 2 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] ETSI SR 001 687: ETSI Global Multimedia Mobility (GMM) report. +- [2] UMTS 22.01: "Universal Mobile Telecommunications System (UMTS): Service aspects; Service principles". +- [3] 3GPP TS 24.002: "GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +Terms introduced in this document: + +**Domain:** The highest-level group of physical entities. Reference points are defined between domains. + +**Stratum:** Grouping of protocols related to one aspect of the services provided by one or several domains. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|------|-----------------------------------------------------------------------------------------| +| Cu | Reference point between USIM and ME | +| Iu | Reference point between Access and Serving Network domains | +| Uu | Reference point between User Equipment and Infrastructure domains, UMTS radio interface | +| [Yu] | Reference point between Serving and Transit Network domains | +| [Zu] | Reference point between Serving and Home Network domains | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|--------------------------------------------------| +| USIM | User Services Identity Module | +| ME | Mobile Equipment | +| MT | Mobile Termination | +| MExE | Mobile Station Application Execution Environment | +| TE | Terminal Equipment | + +# 4 General + +The general UMTS architecture is modelled, at a high level, from both physical and functional viewpoints. The physical aspects are modelled using the domain concept and the functional aspects are modelled using the strata concept. + +The two views are introduced separately and then the mapping between the views is discussed. + +This specification shows at a basic level physical and functional separations to allow a UMTS network to fit within the context of the IMT-2000 family of networks. It does not attempt to develop aspects of a UMTS network that are highly specific to that implementation. + +# 5 Domains in UMTS + +The following figure shows the basic domains in UMTS as described in this clause. + +![Diagram of UMTS domains and reference points. The diagram shows a horizontal sequence of components: USIM, Mobile Equipment (ME), Access Network, Serving Network, and Transit Network. Reference points are marked between them: Cu (USIM/ME), Uu (ME/Access), Iu (Access/Serving), [Yu] (Serving/Transit), and [Zu] (Serving/Home Network Domain). These components are grouped into larger domains: USIM Domain, Mobile Equipment Domain, Access Network Domain, Core Network Domain (which includes Serving and Transit), User Equipment Domain (USIM and ME), and Infrastructure Domain (Access, Serving, and Transit). A vertical double-headed arrow on the right indicates the Home Network Domain.](5d76c2e9976aaf97001ee189908830fb_img.jpg) + +Diagram of UMTS domains and reference points. The diagram shows a horizontal sequence of components: USIM, Mobile Equipment (ME), Access Network, Serving Network, and Transit Network. Reference points are marked between them: Cu (USIM/ME), Uu (ME/Access), Iu (Access/Serving), [Yu] (Serving/Transit), and [Zu] (Serving/Home Network Domain). These components are grouped into larger domains: USIM Domain, Mobile Equipment Domain, Access Network Domain, Core Network Domain (which includes Serving and Transit), User Equipment Domain (USIM and ME), and Infrastructure Domain (Access, Serving, and Transit). A vertical double-headed arrow on the right indicates the Home Network Domain. + +NOTE: The domains identified in the figure will generally result from an evolution of existing network infrastructures. The core network domain may result from evolutions of existing network infrastructures, e.g., a GSM infrastructure, a N-ISDN infrastructure, a B-ISDN infrastructure or a PDN infrastructure. The evolution of these infrastructures may be performed via the use of IWUs, hidden within the domains shown in the figure. + +**Figure 1:UMTS domains and reference points** + +| | | +|------|-------------------------------------------------------------------------------------------| +| Cu | = Reference point between USIM and ME | +| Iu | = Reference point between Access and Serving Network domains | +| Uu | = Reference point between User Equipment and Infrastructure domains, UMTS radio interface | +| [Yu] | = Reference point between Serving and Transit Network domains | +| [Zu] | = Reference point between Serving and Home Network domains | + +## 5.1 Domain split + +A basic architectural split is between the user equipment (terminals) and the infrastructure. This results in two domains: + +the **User Equipment Domain** and the **Infrastructure domain**. + +User equipment is the equipment used by the user to access UMTS services. User equipment has a radio interface to the infrastructure. The infrastructure consists of the physical nodes which perform the various functions required to terminate the radio interface and to support the telecommunication services requirements of the users. The infrastructure is a shared resource that provides services to all authorised end users within its coverage area. + +The reference point between the user equipment domain and the infrastructure domain is termed the "Uu" reference point (UMTS radio interface). + +NOTE: The description assumes an access interface based on UTRA. However, the physical and functional separation described in this document is general and is applicable also if other access technologies are used. + +## 5.2 User equipment Domain + +This domain encompasses a variety of equipment types with different levels of functionality. These equipment types are referred to as user equipment (terminals), and they may also be compatible with one or more existing access (fixed or radio) interfaces e.g. dual mode UMTS-GSM user equipment. The user equipment may include a removable smart card that may be used in different user equipment types. The user equipment is further sub-divided in to the **Mobile Equipment Domain (ME)** and the **User Services Identity Module Domain (USIM)**. + +The reference point between the ME and the USIM is termed the "Cu" reference point. + +For the purpose of UMTS Cellular networks the following definition applies: + +User Equipment is a device allowing a user access to network services. For the purpose of 3GPP specifications the interface between the UE and the network is the radio interface. A User Equipment can be subdivided into a number of domains, the domains being separated by reference points. Currently defined domains are the USIM and ME Domains. The ME Domain can further be subdivided into several components showing the connectivity between multiple functional groups. These groups can be implemented in one or more hardware devices. An example of such a connectivity is the TE - MT interface. Further, an occurrence of User Equipment is an MS for GSM as defined in TS 24.002 [3]. + +The figure below shows the Functional Model for the User Equipment, UE. + +![Functional Model for the User Equipment diagram](34f788b0e5bc8af774fa5561c22e6d01_img.jpg) + +The diagram illustrates the functional model for User Equipment (UE). A large outer rectangle is labeled 'UE' in its bottom right corner. Inside this rectangle, on the left, is a square box labeled 'USIM'. On the right, there is a larger rectangle labeled 'ME' in its bottom right corner. Inside the 'ME' rectangle, there are two stacked rectangular boxes: the top one is labeled 'MT' in its bottom right corner, and the bottom one is labeled 'TE' in its bottom right corner. + +Functional Model for the User Equipment diagram + +**Figure 1a: Functional Model for the User Equipment** + +The 07- and 27-series refer to physical instances of this Functional Model. The figure below shows an example of a physical configuration as it could be used in these specifications. The boxes, in this figure, refer to physical elements. The names within brackets are just provided to map the functional blocks from the figure above onto physical elements. + +![Figure 1b: Example of physical configuration. A diagram showing a 'Handset (MT)' box containing a 'UICC (USIM)' box. A line connects the 'Handset (MT)' box to a 'PC (TE)' box. The connection line is labeled with the reference point 'R'.](d0abac95583b52a3b35f74a215567334_img.jpg) + +``` + +graph TD + subgraph Handset [Handset (MT)] + UICC[UICC (USIM)] + end + Handset --- R((R)) + R --- PC[PC (TE)] + +``` + +Figure 1b: Example of physical configuration. A diagram showing a 'Handset (MT)' box containing a 'UICC (USIM)' box. A line connects the 'Handset (MT)' box to a 'PC (TE)' box. The connection line is labeled with the reference point 'R'. + +**Figure 1b: Example of physical configuration** + +### 5.2.1 Mobile equipment Domain + +The Mobile Equipment performs radio transmission and contains applications. The mobile equipment may be further sub-divided into several entities, e.g. the one which performs the radio transmission and related functions, **Mobile Termination**, MT, and the one which contains the end-to-end application or (e.g. laptop connected to a mobile phone), **Terminal Equipment**, TE. This separation is used in the description of the functional communication in figure 3 but no reference point is defined in this specification. + +### 5.2.2 USIM Domain + +The USIM contains data and procedures which unambiguously and securely identify itself. These functions are typically embedded in a stand alone smart card. This device is associated to a given user, and as such allows to identify this user regardless of the ME he uses. + +## 5.3 Infrastructure Domain + +The Infrastructure domain is further split into the **Access Network Domain**, which is characterised by being in direct contact with the User Equipment and the **Core Network Domain**. This split is intended to simplify/assist the process of de-coupling access related functionality from non-access related functionality and is in line with the modular principle adopted for the UMTS. + +The Access Network Domain comprises roughly the functions specific to the access technique, while the functions in the Core network domain may potentially be used with information flows using any access technique. This split allows for different approaches for the Core Network Domain, each approach specifying distinct types of Core Networks connectable to the Access Network Domain, as well as different access techniques, each type of Access Network connectable to the Core Network Domain. + +The reference point between the access network domain and the core network domain is termed the "Iu" reference point. + +NOTE: The split into the User Equipment Domain, the Access Network Domain and the Core Network Domain is consistent with the GMM report. + +### 5.3.1 Access Network Domain + +The Access Network Domain consists of the physical entities which manage the resources of the access network and provides the user with a mechanism to access the core network domain. + +Additional reference points within the access domain may be identified in other specifications. + +### 5.3.2 Core Network Domain + +The Core Network Domain consists of the physical entities which provide support for the network features and telecommunication services. The support provided includes functionality such as the management of user location information, control of network features and services, the transfer (switching and transmission) mechanisms for signalling and for user generated information. + +[Note: Much more could/should be written about the reference points between the core network and other networks]. + +The core network domain is sub-divided into the **Serving Network Domain**, the **Home Network Domain** and the **Transit Network Domain**. + +The reference point between the serving network domain and the home network domain is termed the [Zu] reference point. + +The reference point between the serving network domain and the transit network domain is termed the [Yu] reference point. + +Additional sub-divisions and reference points within the core network domain may be identified in other specifications. + +#### 5.3.2.1 Serving Network Domain + +The serving network domain is the part of the core network domain to which the access network domain that provides the user's access is connected. It represents the core network functions that are local to the user's access point and thus their location changes when the user moves. The serving network domain is responsible for routing calls and transport user data/information from source to destination. It has the ability to interact with the home domain to cater for user specific data/services and with the transit domain for non user specific data/services purposes. + +#### 5.3.2.2 Home Network Domain + +The home network domain represents the core network functions that are conducted at a permanent location regardless of the location of the user's access point. + +The USIM is related by subscription to the home network domain. The home network domain therefore contains at least permanently user specific data and is responsible for management of subscription information. It may also handle home specific services, potentially not offered by the serving network domain. + +NOTE: Most of the functionality associated with the service provider role according to the UMTS role model (ref UMTS 22.01), is normally contained within the home network domain. + +#### 5.3.2.3 Transit Network Domain + +The transit network domain is the core network part located on the communication path between the serving network domain and the remote party. If, for a given call, the remote party is located inside the same network as the originating UE, then no particular instance of the transit domain is activated. + +# --- 6 Functional Communication between UMTS domains + +The following strata have been identified within UMTS: + +- Application stratum; +- Home stratum; +- Serving stratum and +- Transport stratum + +The following figures show the interactions between the UMTS domains. Two figures are used to reflect the path diversion between the flows exchanged between serving and home domains on one side and between serving and transit on the other side. + +Figure 2 below shows the interactions between the USIM, MT/ME, Access Network, Serving Network and Home Network domains. Figure 3 shows the interactions between TE, MT, Access Network, Serving Network, Transit Network domains and the Remote Party. The Home Stratum only involves domains from figure 2, the Application Stratum only involves domains from figure 3. The Serving and Transport Strata involve domains from figures 2 and 3, so part of them are duplicated in the two figures + +The direct flows between non-contiguous domains (i.e. between domains non directly interconnected) are transparently transported across all the domains and interfaces located on the communication path between these end domains. E.g. + +the USIM-Home Network flows are transparently transported through USIM-MT, MT-Access Network, Access Network-Serving Network and Serving Network-Home Network interfaces, and relayed without interpretation by MT, Access Network and Serving Network domains. + +The dotted lines indicates that the protocol used is not specific to UMTS, in some cases different protocols are possible. However, to provide easy roaming capabilities, it is desirable to agree upon the protocols used. The definition of these protocols is outside the scope of the UMTS specifications. + +![Diagram showing functional flows between USIM, MT/ME, Access Network, Serving Network and Home Network domains across four strata: Home, Serving, Transport, and Access.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) + +The diagram illustrates functional flows across four strata, represented by horizontal ovals, between five vertical entities: USIM, MT/ME, Access Network Domain, Serving Network Domain, and Home Network Domain. + +- Home Stratum:** The top oval. It contains three horizontal double-headed arrows: "USIM - MT" (between USIM and MT/ME), "MT - SN" (between MT/ME and Serving Network Domain), and "SN - HN" (between Serving Network Domain and Home Network Domain). A longer arrow labeled "USIM - HN" spans from USIM to Home Network Domain. +- Serving Stratum:** The second oval. It contains two horizontal double-headed arrows: "USIM - MT" (between USIM and MT/ME) and "MT - SN" (between MT/ME and Serving Network Domain). +- Transport Stratum:** The third oval. It contains a horizontal double-headed arrow labeled "MT - AN" (between MT/ME and Access Network Domain). +- Access Stratum:** The bottom oval, nested within the Transport Stratum. It contains a horizontal double-headed arrow labeled "AN - SN" (between Access Network Domain and Serving Network Domain). + +Vertical lines connect the strata. Dotted lines extend from the USIM and Home Network Domain interfaces at the bottom of the Transport Stratum. + +Diagram showing functional flows between USIM, MT/ME, Access Network, Serving Network and Home Network domains across four strata: Home, Serving, Transport, and Access. + +**Figure 2: Functional flows between the USIM, MT/ME, Access Network, Serving Network and Home Network domains** + +![Figure 3: Functional flow between TE, MT, Access Network, Serving Network, Transit Network domains and the Remote Party. The diagram shows three stacked strata: Application Stratum, 'Serving Stratum', and 'Transport Stratum'. The Application Stratum contains 'Application' and spans from TE to Remote Party. The 'Serving Stratum' contains 'TE - MT' and 'MT - SN' and spans from TE to Remote Party. The 'Transport Stratum' contains 'Access Stratum' (MT - AN and AN - SN) and spans from MT to Remote Party. Vertical lines represent the boundaries of the domains: Mobile Equipment Domain (TE), MT, Access Network Domain, Serving Network Domain, Transit Network Domain, and Remote Party.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +The diagram illustrates the functional flow across different strata and network domains. At the top, the **Application Stratum** is shown as a shaded oval containing the label **Application**. A dashed horizontal line with arrows at both ends spans from the **TE** (Mobile Equipment) to the **Remote Party**. Below this is the **"Serving Stratum"**, another shaded oval. It contains two segments: **TE - MT** (from TE to MT) and **MT - SN** (from MT to SN). A solid horizontal line with arrows spans from **TE** to **Remote Party**. The bottom stratum is the **"Transport Stratum"**, a shaded oval containing the **"Access Stratum"**, which is itself a shaded oval. The **"Access Stratum"** contains two segments: **MT - AN** (from MT to AN) and **AN - SN** (from AN to SN). A dashed horizontal line with arrows spans from **MT** to **Remote Party**. Vertical lines mark the boundaries of the domains: **TE** (Mobile Equipment Domain), **MT**, **Access Network Domain**, **Serving Network Domain**, **Transit Network Domain**, and **Remote Party**. + +Figure 3: Functional flow between TE, MT, Access Network, Serving Network, Transit Network domains and the Remote Party. The diagram shows three stacked strata: Application Stratum, 'Serving Stratum', and 'Transport Stratum'. The Application Stratum contains 'Application' and spans from TE to Remote Party. The 'Serving Stratum' contains 'TE - MT' and 'MT - SN' and spans from TE to Remote Party. The 'Transport Stratum' contains 'Access Stratum' (MT - AN and AN - SN) and spans from MT to Remote Party. Vertical lines represent the boundaries of the domains: Mobile Equipment Domain (TE), MT, Access Network Domain, Serving Network Domain, Transit Network Domain, and Remote Party. + +**Figure 3: Functional flow between TE, MT, Access Network, Serving Network, Transit Network domains and the Remote Party** + +The "Remote Party" represents the remote end entity (user or machine) and is included in the figure to show the end-to-end character of the communication, the specification of the remote party is outside the scope of the UMTS specifications. + +## 6.1 Transport stratum + +This stratum supports the transport of user data and network control signalling from other strata through UMTS. The transport stratum includes consideration of the physical transmission format used for transmission and also: + +- mechanisms for error correction and recovery; +- mechanisms to encrypt data over the radio interface and in the infrastructure part if required; +- mechanisms for adaptation of data to use the supported physical format (if required); and +- mechanisms to "transcode" data to make efficient use of, e.g., the radio interface (if required). + +It may also include resource allocation and routing local to the different interfaces. + +The **Access Stratum**, which is specific to UMTS, is the part of the transport stratum located between the edge node of the serving core network domain and the MT ('MT-Access Network' and 'Access Network-Serving Network' arrows in figure 2 and 3). + +## 6.2 Access Stratum + +This is the functional groupings consisting of the parts in the infrastructure and in the user equipment and the protocols between these parts being specific to the access technique (i.e. the way the specific physical media between the User Equipment and the Infrastructure is used to carry information). The access stratum provides services related to the transmission of data over the radio interface and the management of the radio interface to the other parts of UMTS. + +The access stratum includes the following protocols: + +- Mobile Termination - Access Network +This protocol supports transfer of detailed radio-related information to co-ordinate the use of radio resources between the MT and the access network. +- Access Network - Serving Network +This protocol supports the access from the serving network to the resources provided by the access network. It is independent of the specific radio structure of the access network. + +## 6.3 Serving Stratum + +This stratum consists of protocols and functions to route and transmit data/information, user or network generated, from source to destination. The source and destination may be within the same or different networks. Functions related to telecommunication services and are located in this stratum. + +The serving stratum includes the following protocols: + +- USIM - Mobile Termination +This protocol supports access to subscriber-specific information for support of functions in the user equipment domain. +- Mobile Termination - Serving Network +This protocol supports access from the MT to the services provided by the serving network domain. +- Terminal Equipment- Mobile Termination +This protocol support exchange of control information between the TE and the MT. + +## 6.4 Home Stratum + +This stratum contains the protocols and functions related to the handling and storage of subscription data and possibly home network specific services. It also includes functions to allow domains other than the home network domain to act on behalf of the home network. Functions related to subscription data management, customer care, including billing and charging, mobility management and authentication are located in this stratum. + +The home stratum includes the following protocols: + +- USIM - Home Network +This protocol supports co-ordination of subscriber-specific information between the USIM and the home network. +- USIM - MT +This protocol provides the MT with access to user specific data and resources necessary to perform actions on behalf of the home network. +- MT - Serving Network +This protocol supports user specific data exchanges between the MT and the Serving Network. +- Serving Network - Home Network +This protocol provides the serving network with access to home network data and resources necessary to perform its actions on behalf of the home network, e.g., to support the users communications, services and features (including VHE). + +## 6.5 Application Stratum + +This stratum represents the application process itself, provided to the end-user. It includes end-to-end protocols and functions which make use of services provided by the home, serving and transport strata and infrastructure to support services and/or value added services. + +The functions and protocols within the application stratum may adhere to GSM/UMTS standards such as MExE or may be outside the scope of the UMTS standards. However, the definition of the services provided by the other strata, and the interfaces to them, is within the scope of the standards + +End-to-end functions are applications which are consumed by users at the edge of/outside the overall network. The applications may be accessed by authenticated users who are authorised to access such applications. The users may access the applications by using any of the variety of available user equipment. + +# --- Annex A (informative): Change History + +| Change history | | | | | | | | +|----------------|--------|----------|----|-----|--------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2004-12 | SA#26 | | | | Created version 6.0.0 | 5.0.1 | 6.0.0 | +| 2007-06 | SP-36 | - | - | - | Update to Rel-7 version (MCC) | 6.0.0 | 7.0.0 | +| 2008-12 | SP-42 | - | - | - | Update to Rel-8 version (MCC) | 7.0.0 | 8.0.0 | +| 2009-12 | SP-46 | - | - | - | Update to Rel-9 version (MCC) | 8.0.0 | 9.0.0 | +| 2011-03 | SP-51 | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | SP-65 | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2015-12 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | - | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | +| 2018-06 | SP-80 | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | SP-88E | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23139/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg b/marked/Rel-16/23_series/23139/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40a2abc864eda382dace7004ff7bcbe4f8e7e503 --- /dev/null +++ b/marked/Rel-16/23_series/23139/08c7a76a7786bd08b99dd4cb41583ef4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3c1d4582e2f330508371dccea110aa0beb3b07cb4d23dc7c389c663ad9e7bd7a +size 108635 diff --git a/marked/Rel-16/23_series/23139/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-16/23_series/23139/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c2cf4a63154c1c66073fefd50fa22b874f623759 --- /dev/null +++ b/marked/Rel-16/23_series/23139/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e40bfa7765bc39c7dbe8a972058602cdf6a116af8f6229a353c378200a4126b7 +size 118960 diff --git a/marked/Rel-16/23_series/23139/09955ff8214ffb6947951fc0f60eb6ab_img.jpg b/marked/Rel-16/23_series/23139/09955ff8214ffb6947951fc0f60eb6ab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f847b7cb3eda0b035590f85f4f939ac124155ca --- /dev/null +++ b/marked/Rel-16/23_series/23139/09955ff8214ffb6947951fc0f60eb6ab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10631fe1377107df6728071a03f6b4ef93766669c517a1b6c42d69166fba1653 +size 60180 diff --git a/marked/Rel-16/23_series/23139/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/Rel-16/23_series/23139/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a4a650c6eca1dc505583908a5dec53a3e40c91ee --- /dev/null +++ b/marked/Rel-16/23_series/23139/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0fc694410f662d142dfae0d315afb1a03475a853181e3748a67eefe221d857c +size 51585 diff --git a/marked/Rel-16/23_series/23139/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-16/23_series/23139/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea946369be0bf91bd673750c2de577509d0ca01b --- /dev/null +++ b/marked/Rel-16/23_series/23139/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:578280d679ef4012e3beeba0ec75d0fb04b841360c741bf4d78676010bb8de2e +size 78929 diff --git a/marked/Rel-16/23_series/23139/0f7871077bba48a2c97f7859a5edda0d_img.jpg b/marked/Rel-16/23_series/23139/0f7871077bba48a2c97f7859a5edda0d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b8d4a8b606e343a63d8999d46b7353a7d86b7f4 --- /dev/null +++ b/marked/Rel-16/23_series/23139/0f7871077bba48a2c97f7859a5edda0d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dc389bca44ec3f2cf118f02fd5b16fad613a99a41637232cdc784e47dbbaf2d7 +size 82285 diff --git a/marked/Rel-16/23_series/23139/10b0dda884baae493ad958422d11b552_img.jpg b/marked/Rel-16/23_series/23139/10b0dda884baae493ad958422d11b552_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef102633e2d2ec9e6ffbfe0545e17fdfcdc0da9a --- /dev/null +++ b/marked/Rel-16/23_series/23139/10b0dda884baae493ad958422d11b552_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:716e72baee0dba91779337b4ecb00b700ea0004acbba1241db6afd232aaad579 +size 107636 diff --git a/marked/Rel-16/23_series/23139/1399c76ef88f22b70d05ed3f781d3c48_img.jpg b/marked/Rel-16/23_series/23139/1399c76ef88f22b70d05ed3f781d3c48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81f0f56be391eff512747edfa5b137758323934e --- /dev/null +++ b/marked/Rel-16/23_series/23139/1399c76ef88f22b70d05ed3f781d3c48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e2cf4887e53f699fc3033f842e67eb8b8bce4f5c13f27a57518b7e5311fd790 +size 95066 diff --git a/marked/Rel-16/23_series/23139/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/23_series/23139/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae84bb06f46d9680e156b9f89184e16a7bd13412 --- /dev/null +++ b/marked/Rel-16/23_series/23139/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9316608c5b9e4bc9b08f97e06aee104522573b4ba2d7b12ea05ac22ea58b3016 +size 96538 diff --git a/marked/Rel-16/23_series/23139/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg b/marked/Rel-16/23_series/23139/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc398f885536cfdaa4aee6faa44af6a3c9b1af33 --- /dev/null +++ b/marked/Rel-16/23_series/23139/18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aca8642fdd274ac489a4d65f6dc3852f711c27a5f9d4960536a56e184a629276 +size 85321 diff --git a/marked/Rel-16/23_series/23139/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23139/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..917293615f46af83b69f1576b15a64eb5e85e9b0 --- /dev/null +++ b/marked/Rel-16/23_series/23139/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8fa15279ceb148b0b49a4afee8c99c7aac8992144f6023ba659468b08eb99dd +size 133051 diff --git a/marked/Rel-16/23_series/23139/1c79f31a718d63814feb28ab46f64f19_img.jpg b/marked/Rel-16/23_series/23139/1c79f31a718d63814feb28ab46f64f19_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e3153906fb2421ba1f3692f16873195959c719c7 --- /dev/null +++ b/marked/Rel-16/23_series/23139/1c79f31a718d63814feb28ab46f64f19_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cfa7b9da5a6602838dcb07dee731a6cbf300d0bfff52067bfdbfd0adf292486c +size 62136 diff --git a/marked/Rel-16/23_series/23139/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23139/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af96652f12fa380dd9540a955ffcd6b96d4da7fe --- /dev/null +++ b/marked/Rel-16/23_series/23139/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:827eee24881d75b5b360d53b2cbd6877825b3c667768de8690338d72075838c8 +size 69196 diff --git a/marked/Rel-16/23_series/23139/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23139/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6328d571bf083fc5db6d5aa53aee199cbcd7caa2 --- /dev/null +++ b/marked/Rel-16/23_series/23139/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ade72cea10da9601ab08e7b6d76e20b989d2caacb2abc7af543b6c5c5532eae2 +size 100648 diff --git a/marked/Rel-16/23_series/23139/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23139/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ad8e5ace0457b8082406c336935ecbc60927756 --- /dev/null +++ b/marked/Rel-16/23_series/23139/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:88b1e572c804a6ff26c0eb996dc68428e2b2401543775596e12963be5cbb9e30 +size 106415 diff --git a/marked/Rel-16/23_series/23139/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/23_series/23139/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1511a0f04894a0f98e3cb0a9e85e062a9db753da --- /dev/null +++ b/marked/Rel-16/23_series/23139/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20249cfd5e922135a5b8f52a1fa238558e4cff1c613b5b47aef8b71ce0efef06 +size 31975 diff --git a/marked/Rel-16/23_series/23139/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/23_series/23139/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7042646d44b561240967edf100b5fb2a98857ca4 --- /dev/null +++ b/marked/Rel-16/23_series/23139/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77c20a392b5515a069ba65964a7523b0d9f899d5bae8122a28a0e1058f134b7c +size 102649 diff --git a/marked/Rel-16/23_series/23139/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23139/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59207d5df3f26976aa8cbde6a000dd9554c628b6 --- /dev/null +++ b/marked/Rel-16/23_series/23139/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55c6f5adbe1bfd15dd025eec4feacbd5eeb36c1ce06471c94e6794fc6b0bf036 +size 98111 diff --git a/marked/Rel-16/23_series/23139/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23139/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a781dd23a28cabfcad245a6874b1d1e1d5aab78c --- /dev/null +++ b/marked/Rel-16/23_series/23139/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2162bbe38f91471b6fe31f13a00e9c11db0eafa8d5eec48cd82a2e833cdc4c0 +size 69030 diff --git a/marked/Rel-16/23_series/23139/4537891530c9f6f139a2e1ebf544edc4_img.jpg b/marked/Rel-16/23_series/23139/4537891530c9f6f139a2e1ebf544edc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a1e64bf1dd0be6cb1280284f5a7a886e0f00649 --- /dev/null +++ b/marked/Rel-16/23_series/23139/4537891530c9f6f139a2e1ebf544edc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc7f774accd3949382f57e998e66e87368ff027a71feff408c033830e4435b04 +size 88513 diff --git a/marked/Rel-16/23_series/23139/4842f073775fb1e84d101c02fd74e59e_img.jpg b/marked/Rel-16/23_series/23139/4842f073775fb1e84d101c02fd74e59e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c952826aba64e640b1162ddf7b67857a6b5c466 --- /dev/null +++ b/marked/Rel-16/23_series/23139/4842f073775fb1e84d101c02fd74e59e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4b2bbe14fc66fb9d28b2090f532a18ea4f8a588715e9aebab6b26663d72c29b +size 101368 diff --git a/marked/Rel-16/23_series/23139/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/Rel-16/23_series/23139/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..521bc2d482ce00c502555397753d7511cee57b13 --- /dev/null +++ b/marked/Rel-16/23_series/23139/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fa4209e6f239ce602be78507dc0d37301f659442aa192976c36b75df45876ead +size 75923 diff --git a/marked/Rel-16/23_series/23139/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/Rel-16/23_series/23139/4b87467ad9642943235f48f7d4b59449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8c185ed4b1a46b897890629b8cfb6f0d5fd21d4f --- /dev/null +++ b/marked/Rel-16/23_series/23139/4b87467ad9642943235f48f7d4b59449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d42747968404e6455ca47582daec92cd5e2837651474cf9979da5b97d6d27586 +size 56451 diff --git a/marked/Rel-16/23_series/23139/508bc574df81fa8d3027a374f6d155fc_img.jpg b/marked/Rel-16/23_series/23139/508bc574df81fa8d3027a374f6d155fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7776456446b3907a27fd29b831cdf01cae78669 --- /dev/null +++ b/marked/Rel-16/23_series/23139/508bc574df81fa8d3027a374f6d155fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bda33861a76e57df59ce9b8118e2f3041bfd4ccd9012de8e81a65734f7ccc745 +size 96344 diff --git a/marked/Rel-16/23_series/23139/523ab7b925beb555f88b2e1e1336974f_img.jpg b/marked/Rel-16/23_series/23139/523ab7b925beb555f88b2e1e1336974f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f86a85df1b98744ca38253ebc50fc858fff81835 --- /dev/null +++ b/marked/Rel-16/23_series/23139/523ab7b925beb555f88b2e1e1336974f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a5c345e35f2360b1b24cfe403b8c67ccc44c17ec86d99ada0e72ab4194b4f381 +size 59921 diff --git a/marked/Rel-16/23_series/23139/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/23_series/23139/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5ad4f12738fc1c177d2c4fb82e4c82bc892ff103 --- /dev/null +++ b/marked/Rel-16/23_series/23139/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec24b74b76af3937a2d2af3b999ad8d86a9b373ad9fa2438b70754915b34c2fd +size 115394 diff --git a/marked/Rel-16/23_series/23139/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-16/23_series/23139/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..301bc1e33da4cfe77bfac8ac9480c5ad3e7f91dd --- /dev/null +++ b/marked/Rel-16/23_series/23139/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26e717ec208e0093ec7fdd15f6138ba0454a4e5e63288137f74abecf6295ac92 +size 62381 diff --git a/marked/Rel-16/23_series/23139/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/23_series/23139/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07cdb14a9e6c421da0094e54498102704e402864 --- /dev/null +++ b/marked/Rel-16/23_series/23139/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4603df6f20eee30712774c42b4575d24ab2c98224a0b32bd3e4883bf9e97fd8 +size 134835 diff --git a/marked/Rel-16/23_series/23139/59121d561a4158609b4c354b9ffd0605_img.jpg b/marked/Rel-16/23_series/23139/59121d561a4158609b4c354b9ffd0605_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9d2df30fad555865f7e9dc6b462f85039483a29a --- /dev/null +++ b/marked/Rel-16/23_series/23139/59121d561a4158609b4c354b9ffd0605_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af81a3414971fc3e62084d9a0fc824b17a6ebe3c03990a3cda27fa294314a641 +size 73583 diff --git a/marked/Rel-16/23_series/23139/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-16/23_series/23139/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ec2c2528a187dba607dc61f171f518c94c5aa3a --- /dev/null +++ b/marked/Rel-16/23_series/23139/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f6aaac720d42ac402b06bd08dfa84c6ab53036b212d382da0e88b16f91e580e5 +size 32549 diff --git a/marked/Rel-16/23_series/23139/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg b/marked/Rel-16/23_series/23139/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c6f53ff7f9b235156ca9c076adf709d540456e1 --- /dev/null +++ b/marked/Rel-16/23_series/23139/65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:160049525c30064796ef8537ec3d348ed3915ef9d4fe3a49d584279c23423d4e +size 75489 diff --git a/marked/Rel-16/23_series/23139/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/23_series/23139/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd9f7e6cdd795ad09aed81b0bff9a8f6010c45ea --- /dev/null +++ b/marked/Rel-16/23_series/23139/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cdca8848e82f641c97701cd39bcfc56d6f23ce20dfa8a7a7e18591f5fdc0de1 +size 98794 diff --git a/marked/Rel-16/23_series/23139/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-16/23_series/23139/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef25be5efa5c1b952fb1195487351038506f9a14 --- /dev/null +++ b/marked/Rel-16/23_series/23139/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7f428abcf0fa30ad98552fbbc0ef2e415f98ae372ae3147e49c241df154ffdd +size 89394 diff --git a/marked/Rel-16/23_series/23139/69e5f1993021af230d08c08aac97d9df_img.jpg b/marked/Rel-16/23_series/23139/69e5f1993021af230d08c08aac97d9df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e400fb37c3ab35e473cbaace31791f15339da217 --- /dev/null +++ b/marked/Rel-16/23_series/23139/69e5f1993021af230d08c08aac97d9df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7baa71625ec85588308d4f313ffae8d3074304b7ea22cac048dc89bd880febdf +size 128874 diff --git a/marked/Rel-16/23_series/23139/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23139/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ef912ffcf585cf4b66423c22a7de9f5be3711584 --- /dev/null +++ b/marked/Rel-16/23_series/23139/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7f43e0a0cc939bd10911913231b87dd83387a0758716034ca81bb699d4db918e +size 75506 diff --git a/marked/Rel-16/23_series/23139/7b2d685b805535c1e94aee1365753b92_img.jpg b/marked/Rel-16/23_series/23139/7b2d685b805535c1e94aee1365753b92_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fb9c6bf200d2b76673b474a8f655a252b95d17ac --- /dev/null +++ b/marked/Rel-16/23_series/23139/7b2d685b805535c1e94aee1365753b92_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:789d42d616aafc9d5906ad77be2b29ea5a81e44757b2c4f77bd32f0c7a985851 +size 73681 diff --git a/marked/Rel-16/23_series/23139/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23139/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23b2fdcbecb4790f3c386ac45de321b07e55a2f6 --- /dev/null +++ b/marked/Rel-16/23_series/23139/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed633ceb4d375f24a20cc20f86b05fd8aa992dd7a8dc3d779f7593f48eb72e76 +size 125649 diff --git a/marked/Rel-16/23_series/23139/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/23_series/23139/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c96ea7f51d130f5bdd3917bea9c5cd96f6a31d12 --- /dev/null +++ b/marked/Rel-16/23_series/23139/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23cb3a118dfb68f8b84977284b443f5e758ea4b341178ebec1b4cdfe01b77ae0 +size 82447 diff --git a/marked/Rel-16/23_series/23139/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23139/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..36d1e3d1b446ac32e4bc007540488cd23dcdaed9 --- /dev/null +++ b/marked/Rel-16/23_series/23139/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84ac05895ebd96383f47e96cca326cc68c60d7b7a9933b1a7980aae1708daf0c +size 86974 diff --git a/marked/Rel-16/23_series/23139/854cb86f664ff62fd23e7607cfeb5727_img.jpg b/marked/Rel-16/23_series/23139/854cb86f664ff62fd23e7607cfeb5727_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02df91246457c3ed0b5d021e9eb1406bdd2c246a --- /dev/null +++ b/marked/Rel-16/23_series/23139/854cb86f664ff62fd23e7607cfeb5727_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9929d4ebc07c5fb3070df398bd44ce067872ff3c4a9487389e478dccc22c5e9 +size 110116 diff --git a/marked/Rel-16/23_series/23139/8d66c9c295023a1380f9986d3663bb1e_img.jpg b/marked/Rel-16/23_series/23139/8d66c9c295023a1380f9986d3663bb1e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3adece8bbc782a665bceaba880abf95054659d23 --- /dev/null +++ b/marked/Rel-16/23_series/23139/8d66c9c295023a1380f9986d3663bb1e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:775aa441a4d450e4cfd842ff5a4c314a750f8612132102a51775e98d9c6b8a76 +size 97818 diff --git a/marked/Rel-16/23_series/23139/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/Rel-16/23_series/23139/8fa679f79a1bb1f527cba9f29e784e89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12e39f77c077f9ab9927b3bea5f08e211b70d524 --- /dev/null +++ b/marked/Rel-16/23_series/23139/8fa679f79a1bb1f527cba9f29e784e89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e0db5b3ff7c19c5589f5f2409d7b0edb58c6b2550730d034a2a06008efc821d6 +size 110103 diff --git a/marked/Rel-16/23_series/23139/8fe84519a7da727cc2a27873b3389a52_img.jpg b/marked/Rel-16/23_series/23139/8fe84519a7da727cc2a27873b3389a52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60a2368ee94fb65b68f05a97b553e918ec9b57e8 --- /dev/null +++ b/marked/Rel-16/23_series/23139/8fe84519a7da727cc2a27873b3389a52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a479ea45f282c34c04d86639c4225a9818def560e1a5550f4a0161cf67e9024 +size 108657 diff --git a/marked/Rel-16/23_series/23139/901755bf86813427f3a32efa0363a27c_img.jpg b/marked/Rel-16/23_series/23139/901755bf86813427f3a32efa0363a27c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..283a951cc6b8ab8396e2a86b8f81d820c10a40c4 --- /dev/null +++ b/marked/Rel-16/23_series/23139/901755bf86813427f3a32efa0363a27c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7191c6141dd856555ba4515cc107479ba34c4dfd97eb64cc7ec1bbf58f769327 +size 71789 diff --git a/marked/Rel-16/23_series/23139/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/23_series/23139/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3434c286c9e5f9c8663c91759c7ed3704f38c985 --- /dev/null +++ b/marked/Rel-16/23_series/23139/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7e0b4773455975d0c54282e94950a203575e231993ebc500148ffb3bec4cd03 +size 82596 diff --git a/marked/Rel-16/23_series/23139/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23139/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..037bb3926023d2b8ff885159d0953957f1756c57 --- /dev/null +++ b/marked/Rel-16/23_series/23139/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bc421d9ad15f7bb83499233413db7951e93438dce90979d7e04d28374b48897 +size 90279 diff --git a/marked/Rel-16/23_series/23139/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/23_series/23139/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e363e05ebf6761106a9cfffb36d683ca7af2ae5d --- /dev/null +++ b/marked/Rel-16/23_series/23139/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a35ce620dad5eb34b28e8cd52c07da970be7ab8efa33a5aeb16e3af480cce6b +size 71983 diff --git a/marked/Rel-16/23_series/23139/9f51a76cae7309a296cbc6997941eb3f_img.jpg b/marked/Rel-16/23_series/23139/9f51a76cae7309a296cbc6997941eb3f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e58fa84eea0b32e3e83ca09663ab2334f2c147e6 --- /dev/null +++ b/marked/Rel-16/23_series/23139/9f51a76cae7309a296cbc6997941eb3f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f9987daadba8d630ecdb34a251dcb66f5dafe77e352282f421f55688f68f490 +size 60898 diff --git a/marked/Rel-16/23_series/23139/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23139/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20eba0308ab8937cbbab843c0713a174e2be4601 --- /dev/null +++ b/marked/Rel-16/23_series/23139/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fac68db1cfe2d689e9c26b286e63c8e239c860c7a15ce32f40ab5dae56c6e83 +size 122002 diff --git a/marked/Rel-16/23_series/23139/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23139/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25ea39988cf0b36954d87942217debf1a7c25584 --- /dev/null +++ b/marked/Rel-16/23_series/23139/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29838ede918e7585a20a4dbdfc0ebb40195983629cc4075d4d3eb194d8d2672f +size 123220 diff --git a/marked/Rel-16/23_series/23139/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Rel-16/23_series/23139/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eee681bd7e6862a1172492268f25c9ff63099561 --- /dev/null +++ b/marked/Rel-16/23_series/23139/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6bf2b9001fb7dff908e9f23dc7b096c17c76489692a7c2eff6e9a414f5c4c09f +size 96877 diff --git a/marked/Rel-16/23_series/23139/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/23_series/23139/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc8537fda1d6d5ffa8e72be7ac2d02e4787d0c61 --- /dev/null +++ b/marked/Rel-16/23_series/23139/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c9513cfb9a50660727442ecd8ef875b455df5d1c04a2ac12fb9727fa74ba4db +size 102274 diff --git a/marked/Rel-16/23_series/23139/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23139/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5001251a948a0b2d16326c4ba7a115401eb6954e --- /dev/null +++ b/marked/Rel-16/23_series/23139/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:239d39d6276dc3befb5df1ff2e884ad9145307baea4eb2b2e32e69d53854a305 +size 70592 diff --git a/marked/Rel-16/23_series/23139/bc6f20871b4f01c61470306c304fc9fe_img.jpg b/marked/Rel-16/23_series/23139/bc6f20871b4f01c61470306c304fc9fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..522e2de39c50fb772cf3c4d22a2ddb74ef641ef1 --- /dev/null +++ b/marked/Rel-16/23_series/23139/bc6f20871b4f01c61470306c304fc9fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78a78d5080824cec844fe35c3bef203ce6071743303436ac356825c32c4a71cc +size 97267 diff --git a/marked/Rel-16/23_series/23139/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Rel-16/23_series/23139/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83dd0b9ee2478aeaabc1f3e1ed7c1e26b2d10a64 --- /dev/null +++ b/marked/Rel-16/23_series/23139/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1b01080f9e1cf8550f93bca8d866dfdf8ad006991be2204ec19f8c17a1e6116 +size 116455 diff --git a/marked/Rel-16/23_series/23139/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg b/marked/Rel-16/23_series/23139/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8dba582a7edd017d596a4ed38c7d40c9fc795ab --- /dev/null +++ b/marked/Rel-16/23_series/23139/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a460fda8f1c13a106b5756129e7af7c73a664bc15e15e7a1b468fd7fa42a9d3d +size 161323 diff --git a/marked/Rel-16/23_series/23139/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23139/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac05aedc193b2756131a5ca5161092e466ccbf7c --- /dev/null +++ b/marked/Rel-16/23_series/23139/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4b7bf3161688d9b8d8f7c2398567bc678f88cd4df11617575f66e4fcbf17953 +size 44040 diff --git a/marked/Rel-16/23_series/23139/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/Rel-16/23_series/23139/d26959f4514c26ca19c3d6f00da85956_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82bd75c3da64ae8f554e3f3ea27bff430ec8ec9b --- /dev/null +++ b/marked/Rel-16/23_series/23139/d26959f4514c26ca19c3d6f00da85956_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:89bbb2981d2dc6f647065dd3ca88881d5e4c82208e719387ff19fe97ffed2279 +size 88851 diff --git a/marked/Rel-16/23_series/23139/d6c377ae3e619ff992bd3647dbf43593_img.jpg b/marked/Rel-16/23_series/23139/d6c377ae3e619ff992bd3647dbf43593_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3c9bb4cdf90fc914f82f446b227715edaa705055 --- /dev/null +++ b/marked/Rel-16/23_series/23139/d6c377ae3e619ff992bd3647dbf43593_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0610f024f4c53f9de12b1075a324c9c5acc58ce5c2062121522a1bf2a41fa258 +size 85959 diff --git a/marked/Rel-16/23_series/23139/e1476fd216f6cf773e262013fb4aba7d_img.jpg b/marked/Rel-16/23_series/23139/e1476fd216f6cf773e262013fb4aba7d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..efbe89350d2153a980ab817c6d78cefe74355cfd --- /dev/null +++ b/marked/Rel-16/23_series/23139/e1476fd216f6cf773e262013fb4aba7d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:feb02820517e8c437b9c357b8bd58428aaf501f078e27fdd9612fca9e4c3cf98 +size 86152 diff --git a/marked/Rel-16/23_series/23139/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-16/23_series/23139/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..31f83d190cd60813312d9ea39145ab9abe884866 --- /dev/null +++ b/marked/Rel-16/23_series/23139/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21a44a947212830c566fec274230c829d7a9017ff1c149089ba3a6101979e6d5 +size 85250 diff --git a/marked/Rel-16/23_series/23139/e90987faabad6a6665cd8ed1151dc474_img.jpg b/marked/Rel-16/23_series/23139/e90987faabad6a6665cd8ed1151dc474_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7020122cb9b7d7961d36d08dd63435a67825c717 --- /dev/null +++ b/marked/Rel-16/23_series/23139/e90987faabad6a6665cd8ed1151dc474_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3368e3d6cf70a8641a2b529b9b422be4a347d38d408e4f8e12c812814baab3ca +size 103425 diff --git a/marked/Rel-16/23_series/23139/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23139/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e630c884a3f875053b6979aad1f6ba65277544c --- /dev/null +++ b/marked/Rel-16/23_series/23139/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ca7c193b4be61cff79602ed7531c8c65dbbeafb8ba4f3179c24bb4edc8fe9b9 +size 70086 diff --git a/marked/Rel-16/23_series/23139/ec31af936fa94a6917bf19f154df8ac3_img.jpg b/marked/Rel-16/23_series/23139/ec31af936fa94a6917bf19f154df8ac3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..343d96fa4116caf1e0910cc50d34d12410bea3c5 --- /dev/null +++ b/marked/Rel-16/23_series/23139/ec31af936fa94a6917bf19f154df8ac3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:156aaa981ba1ae3a2aaa857ab20c1c103699c6998c42e81a27c2542553d9ec40 +size 64330 diff --git a/marked/Rel-16/23_series/23139/ef5f5c6665b6ae13660ede412333ba45_img.jpg b/marked/Rel-16/23_series/23139/ef5f5c6665b6ae13660ede412333ba45_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d35ad149e1a9d8659f9633cd0d8fd285dabf7d7 --- /dev/null +++ b/marked/Rel-16/23_series/23139/ef5f5c6665b6ae13660ede412333ba45_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c41076a8f311d2693e92d212167ac654738c5dd2ed0ead17f40c7606de06c64e +size 88390 diff --git a/marked/Rel-16/23_series/23139/f142b022cfc716cd967297f027efe647_img.jpg b/marked/Rel-16/23_series/23139/f142b022cfc716cd967297f027efe647_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..281320a7d588bd04c21a9ce2fc5000b113756b7c --- /dev/null +++ b/marked/Rel-16/23_series/23139/f142b022cfc716cd967297f027efe647_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:604dd39ebf62633ebd27d09138129246578e5c98bafa8897ab9a3b5fdc62aff7 +size 127414 diff --git a/marked/Rel-16/23_series/23139/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-16/23_series/23139/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89ce2985ef690c0cfc6bcfeecd87cb8647d86a31 --- /dev/null +++ b/marked/Rel-16/23_series/23139/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:786c7ffbf29b4e92c25ca3097317a13de065efb30a5172486959b1560591ba3e +size 101812 diff --git a/marked/Rel-16/23_series/23139/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/23_series/23139/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a5bf33bde81754215989b677e9c819b04088d70 --- /dev/null +++ b/marked/Rel-16/23_series/23139/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a2d143d8caecdad42048725ac8ed657feaf1d02457c4e8c87437b89624cd71b4 +size 101591 diff --git a/marked/Rel-16/23_series/23139/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23139/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a77688946a9ded634bff4b76e1cefdd65abb5418 --- /dev/null +++ b/marked/Rel-16/23_series/23139/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:85c1a5c0522124f4b893347279d6d585295049ca9e421ba0a955c1db90294f99 +size 124059 diff --git a/marked/Rel-16/23_series/23139/ffb6acd27b8e3a54392840948a75869f_img.jpg b/marked/Rel-16/23_series/23139/ffb6acd27b8e3a54392840948a75869f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5500ad358b716f585e82b0010b45d6b2ffc49d6d --- /dev/null +++ b/marked/Rel-16/23_series/23139/ffb6acd27b8e3a54392840948a75869f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:735f9e148a273a0ff0ab595bdcd4511ef105d8c7190357a1fcbe237ebbd7f8fa +size 171452 diff --git a/marked/Rel-16/23_series/23139/raw.md b/marked/Rel-16/23_series/23139/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..f7f3efb7c5cfac4444460ba358f4b2ea08fdb1f2 --- /dev/null +++ b/marked/Rel-16/23_series/23139/raw.md @@ -0,0 +1,2514 @@ + + + + +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 9 | +| 4 Architecture model and requirements ..... | 9 | +| 4.1 Architectural requirements and assumptions ..... | 9 | +| 4.2 Architecture for Fixed Broadband Access network interworking using WLAN access..... | 10 | +| 4.2.1 General ..... | 10 | +| 4.2.2 Non-roaming architecture for EPC-routed traffic ..... | 11 | +| 4.2.3 Roaming architecture for EPC-routed traffic ..... | 14 | +| 4.2.4 Architecture for non-seamless WLAN offload by the Fixed Broadband Access network ..... | 19 | +| 4.3 Architecture for Fixed Broadband Access network interworking using H(e)NB..... | 26 | +| 4.3.1 General ..... | 26 | +| 4.3.2 Non Roaming Architecture..... | 27 | +| 4.3.3 Roaming Architecture - Home Routed..... | 27 | +| 4.3.4 Roaming Architecture - Visited Access/Local Breakout ..... | 28 | +| 5 Network Element, and Reference point ..... | 29 | +| 5.1 Network Elements..... | 29 | +| 5.1.1 3GPP network elements ..... | 29 | +| 5.1.1.1 ePDG..... | 29 | +| 5.1.1.2 PCRF..... | 30 | +| 5.1.1.3 3GPP AAA Server ..... | 30 | +| 5.1.1.4 3GPP AAA Proxy..... | 30 | +| 5.1.2 BBF network elements ..... | 30 | +| 5.2 Reference Points..... | 30 | +| 6 Policy and QoS interworking..... | 31 | +| 6.1 General ..... | 31 | +| 6.1.1 Principles for EPC-routed traffic..... | 31 | +| 6.1.2 Principles for Non-seamless WLAN-offload traffic ..... | 31 | +| 6.2 Application of PCC to Fixed Broadband Access interworking ..... | 32 | +| 6.3 QoS solution for 3GPP and Fixed Broadband Access Interworking ..... | 32 | +| 6.3.1 Generic ..... | 32 | +| 6.3.2 Downlink..... | 34 | +| 6.3.2.1 EPC routed traffic ..... | 34 | +| 6.3.2.2 NS-WLAN offloaded traffic ..... | 34 | +| 6.3.3 Uplink..... | 34 | +| 6.3.4 DSCP remapping..... | 35 | +| 6.3.5 Correlating admission control with DSCP marking..... | 36 | +| 6.3.6 Multiple IPSec Child SAs support ..... | 36 | +| 6.4 Authentication and Security procedures for 3GPP and Fixed Broadband access interworking ..... | 36 | +| 7 Functional Description and Procedures for Fixed Broadband Access network over S2b ..... | 37 | +| 7.1 General ..... | 37 | +| 7.2 Initial Attach..... | 37 | +| 7.3 UE/ePDG-initiated Detach Procedure and UE-Requested PDN Disconnection ..... | 39 | +| 7.4 HSS/AAA-initiated Detach Procedure..... | 40 | +| 7.5 UE-initiated Connectivity to Additional PDN ..... | 41 | +| 7.6 Network-Initiated Dynamic PCC for EPC-routed Traffic ..... | 41 | +| 7.7 Network-Initiated Dynamic PCC for NS-WLAN offloaded traffic..... | 42 | +| 7.8 PDN GW initiated Resource Allocation Deactivation..... | 43 | +| 7.9 Handover from 3GPP Access to Fixed Broadband Access with GTP or PMIPv6 on S2b ..... | 44 | +| 7.10 Handover from Fixed broadband Access with GTP or PMIPv6 on S2b to 3GPP Access..... | 46 | +| 7.11 IPSec tunnel modified ..... | 47 | + +| | | | +|--------|------------------------------------------------------------------------------------------------------------------------------------|----| +| 8 | Functional Description and Procedures for Fixed Broadband Access network over S2c ..... | 48 | +| 8.1 | Introduction ..... | 48 | +| 8.2 | Procedures for trusted Fixed Broadband Access network over S2c ..... | 48 | +| 8.2.1 | Initial Attach with DSMIPv6 on S2c to trusted Fixed Broadband Access..... | 48 | +| 8.2.2 | UE-initiated Detach Procedure and UE-Requested PDN Disconnection with DSMIPv6 on S2c in trusted Fixed Broadband Access ..... | 49 | +| 8.2.3 | HSS-initiated Detach Procedure with DSMIPv6 on S2c in trusted Fixed Broadband Access ..... | 50 | +| 8.2.4 | PDN GW-initiated PDN disconnection Procedure with DSMIPv6 on S2c in trusted Fixed Broadband Access..... | 52 | +| 8.2.5 | E-UTRAN to Trusted Fixed Broadband Access Handover with DSMIPv6 on S2c ..... | 52 | +| 8.2.6 | Handover from Trusted Fixed Broadband Access with DSMIPv6 over S2c to 3GPP Access ..... | 54 | +| 8.2.7 | Network-Initiated Dynamic PCC for DSMIPv6 on S2c when accessing trusted Fixed Broadband Access for EPC-routed Traffic ..... | 54 | +| 8.2.8 | Network-Initiated Dynamic PCC for DSMIPv6 on S2c when accessing trusted Fixed Broadband Access for NS-WLAN offloaded Traffic ..... | 55 | +| 8.2.9 | UE-Initiated Connectivity to Additional PDN with DSMIPv6 on S2c over trusted Fixed Broadband Access..... | 55 | +| 8.2.10 | Activation of enhanced security for S2c..... | 56 | +| 8.2.11 | UE local IP address update on S2c over trusted Fixed Broadband Access..... | 57 | +| 8.3 | Procedures for untrusted Fixed Broadband Access network over S2c ..... | 58 | +| 8.3.1 | Initial Attach with DSMIPv6 on S2c to untrusted Fixed Broadband Access..... | 58 | +| 8.3.2 | UE-initiated Detach Procedure and UE-Requested PDN Disconnection with DSMIPv6 on S2c in untrusted Fixed Broadband Access ..... | 59 | +| 8.3.3 | HSS-initiated Detach Procedure with DSMIPv6 on S2c in untrusted Fixed Broadband Access..... | 60 | +| 8.3.4 | PDN GW-initiated PDN disconnection Procedure with DSMIPv6 on S2c in untrusted Fixed Broadband Access ..... | 60 | +| 8.3.5 | E-UTRAN to untrusted Fixed Broadband Access Handover with DSMIPv6 on S2c..... | 61 | +| 8.3.6 | Handover from Untrusted Fixed Broadband Access with DSMIPv6 over S2c to 3GPP Access..... | 63 | +| 8.3.7 | Network-Initiated Dynamic PCC for S2c when accessing untrusted Fixed Broadband Access for EPC-routed Traffic ..... | 63 | +| 8.3.8 | Network-Initiated Dynamic PCC for S2c when accessing untrusted Fixed Broadband Access for NS-WLAN offloaded Traffic..... | 64 | +| 8.3.9 | UE-Initiated Connectivity to Additional PDN with DSMIPv6 on S2c over untrusted Fixed Broadband Access ..... | 64 | +| 8.3.10 | IPSec tunnel modified on S2c over untrusted Fixed Broadband Access ..... | 65 | +| 9 | Functional Description and Procedures for Fixed Broadband Access network using H(e)NB ..... | 66 | +| 9.1 | Procedures for Fixed Broadband Access network using HeNB ..... | 66 | +| 9.1.1 | E-UTRAN Initial Attach and UE requested PDN connection Establishment..... | 66 | +| 9.1.2 | Detach procedure for E-UTRAN..... | 68 | +| 9.1.3 | Network initiated bearer activation, modification and deactivation..... | 68 | +| 9.1.4 | UE requested bearer resource modification..... | 69 | +| 9.1.5 | Service Request and Handover Procedures ..... | 70 | +| 9.2 | Procedures for Fixed Broadband Access network using HeNB - PMIP..... | 72 | +| 9.2.1 | Initial E-UTRAN Attach with PMIP-based S5/S8 ..... | 72 | +| 9.2.2 | Detach for PMIP-based S5/S8..... | 73 | +| 9.2.3 | Dedicated Bearer Procedures for E-UTRAN Access with PMIP-based S5/S8..... | 74 | +| 9.2.4 | HSS-Initiated Subscribed QoS Modification ..... | 74 | +| 9.2.5 | MME-initiated Dedicated Bearer Deactivation..... | 75 | +| 9.2.6 | UE-initiated Resource Request and Release ..... | 76 | +| 9.2.7 | UE requested PDN connectivity..... | 76 | +| 9.2.8 | Service Request and Handover Procedures ..... | 78 | +| 9.3 | Procedures for Fixed Broadband Access network using HNB for PS services ..... | 79 | +| 9.3.1 | PDP Context Activation ..... | 79 | +| 9.3.2 | Secondary PDP Context Activation and PDP Context Modification Procedure..... | 80 | +| 9.3.3 | Detach, PDP Context and EPS-Bearer Deactivation Procedures..... | 81 | +| 9.3.4 | Service Request and Handover Procedures ..... | 82 | +| 9.4 | 3GPP HNB procedure - CS support..... | 83 | +| 9.4.0 | General ..... | 83 | +| 9.4.1 | S15 session establishment at HNB registration..... | 84 | +| 9.4.2 | HNB GW initiated S15 session modification..... | 84 | +| 9.4.3 | S15 session termination..... | 86 | + +9.4.4 PCRF initiated S15 session modification..... 87 + +Annex A (informative): Change history..... 88 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- 1 Scope + +This document specifies the Stage 2 system description for the interworking between a 3GPP system and a Fixed Broadband Access network defined by Broadband Forum to provide the IP connectivity to a 3GPP UE using a WLAN and a H(e)NB connected to a Fixed Broadband Access network. + +The specification covers the system description mobility, Policy, QoS aspects between 3GPP and a Fixed Broadband Access network as well as the respective interactions with the PCC frameworks. This document specifies the detailed extension to EPC defined in TS 23.401 [2] and TS 23.402 [3] for supporting Fixed Broadband Access Network. The extension to PCC framework are specified in TS 23.203 [4]. + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.401: "GPRS Enhancements for E-UTRAN Access". +- [3] 3GPP TS 23.402: "Architecture enhancements for Non-3GPP Accesses". +- [4] 3GPP TS 23.203: "Policy and charging control architecture". +- [5] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)". +- [6] Broadband Forum TR-203: "Interworking between Next Generation Fixed and 3GPP Wireless Access", August 2012. +- [7] Broadband Forum TR-058: " Multi-service Architecture and Framework Requirements " September 2003. +- [8] Broadband Forum TR-101: "Migration to Ethernet-based DSL Aggregation" April 2006. +- [9] 3GPP TS 23.261: "IP Flow Mobility and seamless WLAN offload ". +- [10] Broadband Forum TR-145: "Multi-service Broadband Network Functional Modules and Architecture", November 2012. +- [11] Broadband Forum TR-134 Corrigendum 1: "Broadband Policy Control Framework (BPCF)", January 2013. +- [12] 3GPP TS 25.467: "UTRAN architecture for 3G Home Node B (HNB); Stage 2". +- [13] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [14] 3GPP TS 22.220: "Service requirements for Home Node B (HNB) and Home eNode B (HeNB)". +- [15] 3GPP TS 33.320: "Security of Home Node B (HNB) / Home evolved Node B (HeNB)". +- [16] 3GPP TS 33.210: "Network Domain Security; IP network layer security". +- [17] 3GPP TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)". + +- [18] IETF RFC 4555: "IKEv2 Mobility and Multihoming Protocol (MOBIKE)". +- [19] 3GPP TS 29.274: "General Packet Radio Service (GPRS); Evolved GPRS Tunnelling Protocol (eGTP) for EPS". +- [20] Broadband Forum TR-092: "Broadband Remote Access Server (BRAS) Requirements", August 2004. +- [21] Broadband Forum TR-124 Issue 2: "Functional Requirements for Broadband RG Devices". +- [22] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [23] 3GPP TS 33.402: "Security aspects of non-3GPP accesses". +- [24] 3GPP TS 23.003: "Numbering, addressing and identification". +- [25] 3GPP TS 29.273: "3GPP EPS AAA interfaces". +- [26] Broadband Forum TR-059: "Architecture Requirements for the Support of QoS-Enabled IP Service", September 2003. +- [27] IETF RFC 4301: "Security Architecture for the Internet Protocol". +- [28] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling.". +- [29] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)". +- [30] Broadband Forum TR-291: "Nodal Requirements for Interworking between Next Generation Fixed and 3GPP Wireless Access", March 2014. +- [31] IETF RFC 4186 (January 2006): "Extensible Authentication Protocol Method for GSM Subscriber Identity Modules (EAP-SIM)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**3GPP Femto:** Refers to the HNB and HeNB NEs as defined by 3GPP. The HNB GW is always required for the HNB architecture while the HeNB GW is option for the HeNB. + +**UE local IP address** is defined as: either the public IP address assigned to the UE connected to a BBF access network via a WLAN by the BBF domain in the no-NAT case, or the public IP address assigned by the BBF domain to the NATed RG that is used for this UE. + +**H(e)NB local IP address** is defined as: either the public IP address assigned to the H(e)NB by the BBF domain in the no-NAT case, or the public IP address assigned by the BBF domain to the NATed RG that is used for this H(e)NB. + +**Non-seamless WLAN offload (NSWO)** is a capability of a UE supporting routing specific IP flows over the WLAN access without traversing the EPC as defined in TS 23 402 [3], clause 4.1.5. + +**EPC-routed:** User plane traffic that is routed via a PDN GW in EPC as part of a PDN Connection. EPC-routed applies to non-roaming, roaming with traffic home-routed and roaming with traffic local break-out cases. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|-------------|-------------------------------------------------| +| ANDSF | Access Network Discovery and Selection Function | +| AF | Application Function | +| BBF | Broadband Forum | +| BRAS | Broadband Remote Access Server | +| BNG | Broadband Network Gateway | +| BPCF | Broadband Policy Control Function | +| DSCP | Differentiated Services (Diffserv) Code Point | +| DSMIPv6 | Dual-Stack MIPv6 | +| EPC | Evolved Packet Core | +| ePDG | Evolved Packet Data Gateway | +| EPS | Evolved Packet System | +| H-ANDSF | Home-ANDSF | +| MME | Mobility Management Entity | +| NSWO | Non-seamless WLAN offload | +| PCRF | Policy and Charging Rules Function | +| P-GW | PDN Gateway | +| PMIP/PMIPv6 | Proxy Mobile IP version 6 | +| RG | Residential Gateway | +| SeGW | Security Gateway | +| S-GW | Serving GW | +| TDF | Traffic Detection Function | +| V-ANDSF | Visited-ANDSF | + +# --- 4 Architecture model and requirements + +## 4.1 Architectural requirements and assumptions + +The interworking architecture is based on EPC reference architecture defined in TS 23.401 [2] and TS 23 402 [3] and on BBF access network defined by BBF TR-291 [30], BBF TR-058 [7], BBF TR-101 [8], BBF TR-134 [11], and BBF TR-203 [6] excluding EAP-SIM (RFC 4186 [31]) functionality. + +The interworking architecture supports trusted and untrusted model for the host-based mobility (S2c) and the untrusted model for the network based mobility (S2b). The trusted/untrusted Non-3GPP access network detection is performed as defined in clause 4.1.4 of TS 23 402 [3]. + +The reference architecture defined in TS 23 402 Rel-11 clause 16 for Trusted WLAN using GTP s2a is applicable to the scenario where the Fixed Broadband / BBF Access network is considered as a trusted WLAN access. For such Fixed Broadband / BBF Access interworking deployments, in this version of the specification, the interactions between the EPC and the Fixed Broadband / BBF Access network consists only in S2a, STa interfaces and are not further detailed in this document. The detailed functional split within a Fixed Broadband / BBF Access network, the support of P2P link between the UE and the TWAG and the mapping between the S2a bearer QoS information received via S2a and Fixed Broadband Access specific parameters are outside 3GPP scope. + +The architecture supports a UE simultaneously connected to the EPC via more than one access network for the same PDN connection as defined in TS 23.261 [9]. + +The architecture supports a UE that is capable of routing simultaneously active PDN connections to different APNs through different access networks as defined in TS 23.401 [2] and TS 23 402 [3]. + +The architecture supports the scenario of a single network operator deploying both the 3GPP EPC and the BBF access network and the scenario of two network operators one deploying the 3GPP EPC network and one deploying only the Broadband Forum Access network. Furthermore the architecture supports the roaming scenario between two PLMN operators. + +The architecture supports local breakout of traffic in the EPC network whether a roaming subscriber is accessing the EPC via a 3GPP or a non-3GPP access network according to the design principles described in clause 4.1 of TS 23.401 [2]. + +The support of HeNB is based on reference architecture defined in TS 23.401 [2] and TS 36.300 [13], for the support of HNB in TS 23.060 [22] and TS 25.467 [12]. + +The architecture supports both offline and online charging in the 3GPP domain for the EPC routed traffic by means of accounting/charging information collected in 3GPP network elements. + +The architecture supports STa/SWa reference points based accounting for the 3GPP UEs when traffic is NSWO in the Fixed Broadband Access network based on the assumption that the BBF network is able to collect per user accounting data for NSWO traffic of 3GPP UEs (i.e. BNG is able to recognize the traffic of individual 3GPP UEs), and periodically report this data via the STa/SWa reference points. If both EPC routed and NSWO are simultaneously provided to a UE, accounting information sent by BBF over SWa/STa shall allow distinguishing the accounting information for EPC routed traffic from that for NSWO traffic. This shall be supported based on Fixed Broadband Access accounting capabilities + +NOTE 1: As defined in BBF TR-203 [6] the Fixed Broadband Access may send over SWa/STa accounting information for both EPC routed and NSWO. + +NOTE 2: The online charging may be supported with limitation due to support of AAA RADIUS based accounting in the BBF network. It is assumed that the BBF does not need to be aware of whether online or offline charging is performed in the 3GPP domain + +For S2b, the PCRF discovery function may select different PCRFs for PDN connection(s) for the UE in the PDN GW and for the IP session for NSWO traffic for the UE in the Fixed Broadband Access. + +For S2c, the PCRF discovery function selects the same PCRF for all PDN connections for a certain IMSI and may select a different PCRF for IP-CAN session establishment over S9a for NSWO traffic. + +There may be multiple TDFs deployed. If a TDF is used for traffic offloaded to the Fixed Broadband Access, the TDF selected for the NSWO traffic from the UE in the Fixed Broadband Access and that for the EPC routed traffic on SGi may or may not be the same. + +In this Release, the policy interworking for user charging for NSWO traffic is only supported for scenarios without NAT in the Fixed Broadband Access domain. + +## 4.2 Architecture for Fixed Broadband Access network interworking using WLAN access + +### 4.2.1 General + +The figure 4.2.2-1, 4.2.2-2 and 4.2.2-3 show the reference architecture for the non-roaming scenario and with the traffic routed to the mobile core network. The figure 4.2.3-1, 4.2.3-2 and 4.2.3-3 show the reference architecture for the roaming scenario with the traffic routed to the home network. The figure 4.2.3-5, 4.2.3-6 and 4.2.3-7 show the reference architecture for the roaming scenario with the local breakout in Visited PLMN. + +The figure 4.2.4-1 and 4.2.4-2 show the reference architecture for the NSWO with AF in 3GPP operator's network; the figure 4.2.4-3 and 4.2.4-4 show the reference architecture for the NSWO with AF ("BBF AF") in BBF domain; the figure 4.2.4-5 and 4.2.4-6 show the reference architecture for NSWO with TDF. The non-seamless traffic is routed to an external network directly from BBF network. + +The following considerations apply to interfaces and reference points where they occur in figures in this clause: + +- S5 and S8 can be GTP-based or PMIP-based. +- Gxc is used only in the case of PMIP variant of S5 or S8. +- S9 is used between the H-PCRF and V-PCRF in roaming scenario +- the reference points internal to the Fixed Broadband access network are defined or are under definition by Broadband Forum and are out of the scope of this specification. + +NOTE 1: SWu shown in Figure 4.2.2-1, 4.2.3-1 and 4.2.3-4 also applies to architectural reference for untrusted scenario in Figures 4.2.2-3, 4.2.3-3 and 4.2.3-6 for the untrusted scenario with S2c but is not shown for simplicity. + +The ANDSF is not shown in any of the following figures, but it may be used in all architectural variants, according to the principles defined in TS 23 402 [3]. + +### 4.2.2 Non-roaming architecture for EPC-routed traffic + +![Diagram of Non-roaming architecture for EPC-routed traffic showing connections between HPLMN, VPLMN, and Customer Premise Network components.](d26959f4514c26ca19c3d6f00da85956_img.jpg) + +The diagram illustrates the non-roaming architecture for EPC-routed traffic, organized into three horizontal layers separated by dashed red lines: + +- HPLMN (Home PLMN):** + - Contains the **HSS** (Home Subscriber Server). + - The **MME** (Mobility Management Entity) is connected to the HSS via the **S6a** interface. + - The **PDN Gateway** (PDN GW) is connected to the MME via the **S5** interface and to the **hPCRF** (PDN Connectivity Network Resource Function) via the **Gx** interface. + - The **hPCRF** is connected to the **Operator's IP Services** (e.g., IMS, PSS, etc.) via the **Rx** and **SGi** interfaces. +- VPLMN (Visited PLMN):** + - Contains various access networks: **E-UTRAN**, **UTRAN**, and **GERAN**. + - E-UTRAN** connects to the **MME** via the **S1-MME** interface. + - UTRAN** connects to the **SGSN** via the **S4** interface, which then connects to the **MME** via the **S10** interface. + - GERAN** connects to the **vMSC** via the **Iu-PS** and **Iu-CS** interfaces. + - The **vMSC** connects to the **HNB GW** (Home NodeB Gateway). + - Both the **HNB GW** and a **HeNB GW** (Home eNodeB Gateway) connect to the **Serving Gateway** (SGW) via the **S1-U** interface. + - The **SGW** connects to the **MME** via the **S1-U** interface and to the **vPCRF** via the **S8** interface. + - The **vPCRF** is connected to the **hPCRF** via the **S9** interface. + - An interface labeled **Gxc (Only for PMIP based S8)** is shown between the **SGW** and the **vPCRF**. +- BBF defined access and network:** + - The **SeGW** (Secure Gateway) connects the **HNB GW** to the **BRAS/BNG** (Broadband Remote Access Server / Broadband Network Gateway). + - The **BRAS/BNG** connects to the **AN (e.g. DSLAM/ONT)** (Access Network). + - The **AN** connects to the **RC** (Residential Gateway). + - The **RC** is connected to **3GPP Femto** and **BBF Device** components. + +Additional interfaces shown include **S15** between the **HNB GW** and the **vPCRF**, and **S9a** between the **vPCRF** and the **BPCF** (Bearer Path Control Function). + +Diagram of Non-roaming architecture for EPC-routed traffic showing connections between HPLMN, VPLMN, and Customer Premise Network components. + +**Figure 4.2.2-1: Non-Roaming Architecture for untrusted Fixed Broadband access network based on S2b** + +NOTE 1: The reference architecture is applicable when the 3GPP and Fixed Broadband access networks belongs to the same network operator or to different network operators. + +![Network architecture diagram showing connections between HPLMN, VPLMN, and Customer Premise Network. Components include HSS, MME, E-UTRAN, UTRAN, GERAN, SGSN, HNB GW, v MSC, Serving Gateway, HeNB GW, PDN Gateway, vPCRF, Operator's IP Services, BPCF, BRAS/BNG, AN (e.g DSLAM/ONT), RG, 3GPP Femto, and BBF Device. Interfaces shown include S10, S11, S1-MME, S1-U, S4, S5, S6a, S9, S15, Gx, Gxc, Rx, SGi, S9a, and Lu-PS/Lu-CS.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +The diagram illustrates a non-roaming architecture for trusted fixed broadband access network based on S2c. It is divided into three main network domains by horizontal dashed red lines: + +- HPLMN (Home PLMN):** Contains the HSS, MME, and vPCRF. The HSS is connected to the MME via the S6a interface. The MME is connected to the vPCRF via the S9 interface. +- VPLMN (Visited PLMN):** Contains the E-UTRAN, UTRAN, GERAN, SGSN, HNB GW, v MSC, Serving Gateway, HeNB GW, PDN Gateway, and SeGW. + - E-UTRAN, UTRAN, and GERAN are connected to the MME via S1-MME and to the SGSN via S4. + - HNB GW is connected to the v MSC via Lu-CS and to the SGSN via Lu-PS. It also connects to the SeGW. + - Serving Gateway is connected to the MME via S1-U and to the PDN Gateway via S5. It also connects to the HeNB GW and the SeGW. + - PDN Gateway is connected to the vPCRF via the Gx interface and to the BPCF via the S5 interface. + - SeGW is connected to the HNB GW and the BPCF. + - A note indicates "Gxc (Only for PMIP based S5)" between the Serving Gateway and the PDN Gateway. +- BBF defined access and network:** Contains the BPCF, BRAS/BNG, and AN (e.g DSLAM/ONT). The BPCF is connected to the PDN Gateway via the S9a interface and to the BRAS/BNG. The BRAS/BNG is connected to the AN. +- Customer Premise Network:** Contains the RG, 3GPP Femto, and BBF Device. The RG is connected to the AN and to both the 3GPP Femto and the BBF Device. + +Other components and interfaces include: + +- Operator's IP Services (e.g. IMS, PSS):** Connected to the vPCRF via the Rx interface and to the PDN Gateway via the SGi interface. +- hPCRF:** Connected to the vPCRF via the S9 interface. + +Network architecture diagram showing connections between HPLMN, VPLMN, and Customer Premise Network. Components include HSS, MME, E-UTRAN, UTRAN, GERAN, SGSN, HNB GW, v MSC, Serving Gateway, HeNB GW, PDN Gateway, vPCRF, Operator's IP Services, BPCF, BRAS/BNG, AN (e.g DSLAM/ONT), RG, 3GPP Femto, and BBF Device. Interfaces shown include S10, S11, S1-MME, S1-U, S4, S5, S6a, S9, S15, Gx, Gxc, Rx, SGi, S9a, and Lu-PS/Lu-CS. + +Figure 4.2.2-2: Non-Roaming Architecture for trusted Fixed Broadband access network based on S2c + +NOTE 2: The reference architecture is applicable when both 3GPP and Fixed Broadband network belongs to the same network operator or to different network operators. + +NOTE 3: The connection between the BRAS/BNG and PDN Gateway is IP transport connection. + +![Diagram of Non-Roaming Architecture for untrusted Fixed Broadband access network based on S2c. It shows traffic flow from Voice, Video, and Internet through a Mobile Terminal, Residential Gateway, Fixed Access Node, BNG, ePDG, and finally to the PDN-GW. Annotations explain QoS handling at various points.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +The diagram illustrates the network architecture for untrusted fixed broadband access. On the left, three traffic sources (Voice, Video, and Internet) enter a Mobile Terminal. From the Mobile Terminal, traffic flows through a Residential Gateway, a Fixed Access Node, a BNG, an ePDG, and finally to a PDN-GW. The Mobile Terminal, BNG, and ePDG are highlighted with dashed circles. The Residential Gateway, Fixed Access Node, and PDN-GW are highlighted with solid rectangles. The traffic path is shown as a thick grey line. Annotations with leader lines point to specific components: 'Reflective QoS installs packet filters and DSCP marking for UL traffic in the UE' points to the Mobile Terminal; 'Ensuring QoS here (e.g., on WIFI) is out of scope' points to the link between the Mobile Terminal and the Residential Gateway; 'RG honors the DSCP marking set by the UE' points to the Residential Gateway; and 'Packet filters (TFTs). PDN GW performs DSCP marking in down-link based on QCI of packet.' points to the PDN-GW. + +Diagram of Non-Roaming Architecture for untrusted Fixed Broadband access network based on S2c. It shows traffic flow from Voice, Video, and Internet through a Mobile Terminal, Residential Gateway, Fixed Access Node, BNG, ePDG, and finally to the PDN-GW. Annotations explain QoS handling at various points. + +**Figure 4.2.2-3: Non-Roaming Architecture for untrusted Fixed Broadband access network based on S2c** + +NOTE 4: The reference architecture is applicable when both 3GPP and Fixed Broadband network belongs to the same network operator or to different network operators. + +### 4.2.3 Roaming architecture for EPC-routed traffic + +![Diagram of Roaming Architecture for untrusted Fixed Broadband access network based on S2b - Home routed traffic. It shows traffic flow from Voice, Video, and Internet sources through a Mobile Terminal, Residential Gateway, Fixed Access Node, and BNG. Annotations explain QoS handling at each stage: Reflective QoS in the UE, DSCP marking by the BNG, and DSCP honoring by the RG. A note indicates that ensuring QoS on WiFi is out of scope.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +Voice + +Video + +Internet + +Reflective QoS installs packet filters and DSCP marking for UL traffic in the UE + +BNG performs DSCP marking in downlink based on the QoS information received via R interface + +Mobile Terminal + +Residential Gateway + +Fixed Access Node + +BNG + +Ensuring QoS here (e.g. on WIFI) is out if scope + +RG honors the DSCP marking set by the UE + +Diagram of Roaming Architecture for untrusted Fixed Broadband access network based on S2b - Home routed traffic. It shows traffic flow from Voice, Video, and Internet sources through a Mobile Terminal, Residential Gateway, Fixed Access Node, and BNG. Annotations explain QoS handling at each stage: Reflective QoS in the UE, DSCP marking by the BNG, and DSCP honoring by the RG. A note indicates that ensuring QoS on WiFi is out of scope. + +**Figure 4.2.3-1: Roaming Architecture for untrusted Fixed Broadband access network based on S2b - Home routed traffic** + +NOTE 1: The reference architecture is applicable when both 3GPP and Fixed Broadband network belongs to the same VPLMN network operator or to different network operators. + +![Sequence diagram showing Roaming Architecture for trusted Fixed Broadband access network using S2c - Home Routed. It includes lifelines for UE, RG, BNG, AAA proxy, BPCF, ePDG, PDN GW, vPCRF, 3GPP AAA Proxy, hPCRF, HSS/AAA, and TDF. The diagram is divided into 'Fixed Broadband Access Network' and 'Roaming Scenarios'. Steps include: 1. 3GPP-based access authentication (EAP-AKA), 2. Local IP address assignment, 3. Trigger, 4. Indication of IP-CAN session Establishment, 5. TDF session establishment (for NS-WLAN offloaded traffic), 6. PDN connection setup, 7. ePDG-initiated Gateway Control Session Establishment, 8. PCRF-initiated Gateway Control Session Establishment, 9. policy interaction.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +The diagram illustrates the signaling sequence for a roaming architecture. It begins with the UE sending a 3GPP-based access authentication (EAP-AKA) request to the AAA proxy. The AAA proxy responds with a local IP address assignment. A trigger is then sent from the BNG to the BPCF, which in turn sends an indication of IP-CAN session establishment to the vPCRF. The vPCRF initiates a TDF session establishment for NS-WLAN offloaded traffic. A dashed line separates the initial setup from the PDN connection setup, which follows the specifications in TS 23.402, clause 7.2.1 or 7.2.4. Below this, the ePDG initiates a Gateway Control Session Establishment with the vPCRF, and the vPCRF initiates another Gateway Control Session Establishment with the hPCRF. Finally, a policy interaction occurs between the BNG and the BPCF. + +Sequence diagram showing Roaming Architecture for trusted Fixed Broadband access network using S2c - Home Routed. It includes lifelines for UE, RG, BNG, AAA proxy, BPCF, ePDG, PDN GW, vPCRF, 3GPP AAA Proxy, hPCRF, HSS/AAA, and TDF. The diagram is divided into 'Fixed Broadband Access Network' and 'Roaming Scenarios'. Steps include: 1. 3GPP-based access authentication (EAP-AKA), 2. Local IP address assignment, 3. Trigger, 4. Indication of IP-CAN session Establishment, 5. TDF session establishment (for NS-WLAN offloaded traffic), 6. PDN connection setup, 7. ePDG-initiated Gateway Control Session Establishment, 8. PCRF-initiated Gateway Control Session Establishment, 9. policy interaction. + +**Figure 4.2.3-2: Roaming Architecture for trusted Fixed Broadband access network using S2c - Home Routed** + +NOTE 2: The reference architecture is applicable when both 3GPP and Fixed Broadband network belongs to the same VPLMN network operator or to different network operators. + +NOTE 3: The connection between the BRAS/BNG and PDN Gateway is an IP transport connection. + +![Roaming Architecture for untrusted Fixed Broadband access network using S2c - Home Routed diagram](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +The diagram illustrates the roaming architecture for an untrusted Fixed Broadband access network using S2c - Home Routed. It shows the interaction between various network elements across different domains. + +**Fixed Broadband Access Network (FBA) Elements:** UE, RG, BNG, BPCF, AAA Proxy. These are connected via an **IKEv2 tunnel** (highlighted in yellow). + +**PDN Elements:** ePDG, PDN GW. The ePDG connects to the UE via an **IKEv2 tunnel** and to the PDN GW via a **PMIP or GTP tunnel** (highlighted in green). + +**Roaming Scenarios:** 3GPP AAA Proxy, vPCRF, hPCRF, TDF. These elements are involved in the roaming process. + +**Sequence of Procedures:** + +1. PDN disconnection procedure as specified in TS 23.402, Figure 7.4.1.1-1 or 7.4.3.1-1 +2. ePDG-Initiated Gateway Control Session Termination +3. Gateway Control and QoS Rules Provision procedure or PCRF-Initiated Gateway Control Session Termination Procedure +4. Fixed Broadband Access specific resource release procedure +5. Indication of IP-CAN session termination procedure +6. TDF session termination procedure (offloaded traffic) + +Roaming Architecture for untrusted Fixed Broadband access network using S2c - Home Routed diagram + +**Figure 4.2.3-3: Roaming Architecture for untrusted Fixed Broadband access network using S2c - Home Routed** + +NOTE 4: The reference architecture is applicable when both 3GPP and Fixed Broadband network belongs to the same VPLMN network operator or to different network operators. + +![Roaming Architecture diagram for untrusted Fixed Broadband access network using S2b – Local breakout in V-PLMN. The diagram shows a sequence of messages between a UE, Fixed Broadband Access, ePDG, PDN GW, BGPP AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' contains the PDN GW, BGPP AAA Proxy, vPCRF, and hPCRF. Step 1, 'Detach Indication', is a message from the BGPP AAA Proxy to the ePDG. Step 2, 'The procedures as Figure 7.3-1', is a block representing subsequent interactions. Step 3, 'Detach Ack', is a message from the PDN GW to the HSS/AAA.](8307f6b04df072c9332f9987e034272c_img.jpg) + +Roaming Architecture diagram for untrusted Fixed Broadband access network using S2b – Local breakout in V-PLMN. The diagram shows a sequence of messages between a UE, Fixed Broadband Access, ePDG, PDN GW, BGPP AAA Proxy, vPCRF, hPCRF, and HSS/AAA. A shaded area labeled 'Roaming Scenarios' contains the PDN GW, BGPP AAA Proxy, vPCRF, and hPCRF. Step 1, 'Detach Indication', is a message from the BGPP AAA Proxy to the ePDG. Step 2, 'The procedures as Figure 7.3-1', is a block representing subsequent interactions. Step 3, 'Detach Ack', is a message from the PDN GW to the HSS/AAA. + +**Figure 4.2.3-4: Roaming Architecture for untrusted Fixed Broadband access network using S2b – Local breakout in V-PLMN** + +NOTE 5: The two Rx instances in Figure 4.2.3-4 apply to different application functions in the HPLMN and VPLMN. + +NOTE 6: The reference architecture is applicable when both 3GPP and Fixed Broadband network belongs to the same VPLMN network operator or to different network operators. + +![Sequence diagram showing UE, ePDG, PDN GW1, and PDN GW2. Step 1: Initial S2b Attach as in Fig 7.2-1 between UE and PDN GW1 via ePDG. Step 2: S2b Attach to additional PDNs as in Figure . 7.2-1 between UE and PDN GW2 via ePDG.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +The diagram illustrates a sequence of two network attachment processes. At the top, four rectangular boxes represent network elements: 'UE' (User Equipment), 'ePDG' (evolved PDG), 'PDN GW1' (PDN Gateway 1), and 'PDN GW2' (PDN Gateway 2). Vertical lines extend downwards from each box. Step 1, labeled '1. Initial S2b Attach as in Fig 7.2-1', is shown between the UE and PDN GW1. A horizontal line connects the UE's vertical line to the ePDG's, and another horizontal line connects the ePDG's to the PDN GW1's. A large chevron shape encloses this part of the sequence. Step 2, labeled '2. S2b Attach to additional PDNs as in Figure . 7.2-1', is shown between the UE and PDN GW2. A horizontal line connects the UE's vertical line to the ePDG's, and a much longer horizontal line connects the ePDG's to the PDN GW2's. This part of the sequence is also enclosed in a large chevron shape. At the bottom of each vertical line, there is a small horizontal tick mark. + +Sequence diagram showing UE, ePDG, PDN GW1, and PDN GW2. Step 1: Initial S2b Attach as in Fig 7.2-1 between UE and PDN GW1 via ePDG. Step 2: S2b Attach to additional PDNs as in Figure . 7.2-1 between UE and PDN GW2 via ePDG. + +**Figure 4.2.3-5: Roaming Architecture for trusted Fixed Broadband access network using S2c – Local breakout in V-PLMN** + +NOTE 7: The reference architecture is applicable when both 3GPP and Fixed Broadband network belongs to the same VPLMN network operator or to different network operators. + +NOTE 8: The two Rx instances in Figure 4.2.3-5 apply to different application functions in the HPLMN and VPLMN. + +NOTE 9: The connection between the BRAS/BNG and PDN Gateway is a IP transport connection. + +![Figure 4.2.3-6: Roaming Architecture for untrusted Fixed Broadband access network using S2c – Local breakout in V-PLMN. The diagram shows a UE connected to a Fixed Broadband Access Network (containing RG, BNG, AAA proxy, BPCF) via an IPsec Tunnel. The IPsec Tunnel connects to an ePDG, which is connected to a PDN GW. The PDN GW is connected to a 3GPP AAA Proxy, which is connected to a vPCRF, which is connected to an hPCRF, which is connected to an HSS/AAA. The diagram illustrates five signaling procedures: 1. Gateway Control and QoS Rules provision procedure (between ePDG and PDN GW), 2. Access specific mechanism for admission control, etc (between UE and BNG), 3. IP-CAN Session Modification (between PDN GW and vPCRF), 4. The Dedicated bearer activation/deactivation/update procedure with GTP based S2b is specified in TS 23.402, figure 7.9.2-1, 7.10-1, 7.11.1-1 (between PDN GW and vPCRF), and 5. IP-CAN Session Modification (between PDN GW and hPCRF).](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) + +Figure 4.2.3-6: Roaming Architecture for untrusted Fixed Broadband access network using S2c – Local breakout in V-PLMN. The diagram shows a UE connected to a Fixed Broadband Access Network (containing RG, BNG, AAA proxy, BPCF) via an IPsec Tunnel. The IPsec Tunnel connects to an ePDG, which is connected to a PDN GW. The PDN GW is connected to a 3GPP AAA Proxy, which is connected to a vPCRF, which is connected to an hPCRF, which is connected to an HSS/AAA. The diagram illustrates five signaling procedures: 1. Gateway Control and QoS Rules provision procedure (between ePDG and PDN GW), 2. Access specific mechanism for admission control, etc (between UE and BNG), 3. IP-CAN Session Modification (between PDN GW and vPCRF), 4. The Dedicated bearer activation/deactivation/update procedure with GTP based S2b is specified in TS 23.402, figure 7.9.2-1, 7.10-1, 7.11.1-1 (between PDN GW and vPCRF), and 5. IP-CAN Session Modification (between PDN GW and hPCRF). + +**Figure 4.2.3-6: Roaming Architecture for untrusted Fixed Broadband access network using S2c – Local breakout in V-PLMN** + +NOTE 10: The reference architecture is applicable when both 3GPP and Fixed Broadband network belongs to the same VPLMN network operator or to different network operators. + +NOTE 11: The two Rx instances in Figure 4.2.3-6 apply to different application functions in the HPLMN and VPLMN. + +### 4.2.4 Architecture for non-seamless WLAN offload by the Fixed Broadband Access network + +Figure 4.2.4-1, 4.2.4-2, 4.2.4-3, 4.2.4-4, 4.2.4-5, and 4.2.4-6 show the reference architectures for NSWO. The non-seamless traffic is routed to an external network directly from BBF network. + +Although this clause describes only NSWO architecture scenarios, both NSWO and EPC-routed can co-exist during the network operation. + +#### Architecture scenario A: AF in 3GPP operator's network + +![Network architecture diagram showing the flow from IP service through various network elements like TDF, BRAS/BNG, AN, RG, WiFi AP, and BBF Device to a UE, with corresponding PCRF and AAA components in the HPLMN and VPLMN.](523ab7b925beb555f88b2e1e1336974f_img.jpg) + +The diagram illustrates the network architecture for a non-roaming scenario where the AF is within the 3GPP operator's network. It is divided into three main domains: EPC HPLMN (top), EPC VPLMN (middle), and BBF defined access and network (bottom), with a Customer Premises Network (CPN) at the very bottom. + - **EPC HPLMN:** Contains H-PCRF and 3GPP AAA Server. + - **EPC VPLMN:** Contains V-PCRF and 3GPP AAA Proxy. + - **BBF defined access and network:** Contains BRAS/BNG, BPCF, and BBF AAA (proxy). + - **Customer Premises Network:** Contains AN (e.g. DSLAM/ONT), RG, WiFi AP, and BBF Device. + - **External:** A 'Network to offload to (any NW)' containing an 'IP service' is connected to a TDF. + - **Interfaces:** S9 between H-PCRF and V-PCRF; S9d between 3GPP AAA Server and 3GPP AAA Proxy; Sd between TDF and V-PCRF; S9a between V-PCRF and BPCF; SWa/STa between 3GPP AAA Proxy and BBF AAA (proxy); R between BRAS/BNG and BPCF; V between BRAS/BNG and AN; U between AN and RG. + - **UE:** User Equipment connected to the WiFi AP. + +Network architecture diagram showing the flow from IP service through various network elements like TDF, BRAS/BNG, AN, RG, WiFi AP, and BBF Device to a UE, with corresponding PCRF and AAA components in the HPLMN and VPLMN. + +Figure 4.2.4-1: NSWO for 3GPP domain supporting the AF – non-roaming scenario + +![Network architecture diagram showing the NSWO for 3GPP domain supporting the AF - roaming scenario. It illustrates the flow from EPC HPLMN through EPC VPLMN, BBF defined access and network, and Customer Premises Network to a UE.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +The diagram illustrates a network architecture for a 3GPP domain supporting an AF - roaming scenario. It is divided into four main domains separated by dashed lines: + +- EPC HPLMN (Home PLMN):** Contains **H-PCRF** and **3GPP AAA Server**. The H-PCRF is connected to the V-PCRF in the VPLMN via the **S9** interface. The 3GPP AAA Server is connected to the 3GPP AAA Proxy via the **SWd** interface. +- EPC VPLMN (Visited PLMN):** Contains **V-PCRF** and **3GPP AAA Proxy**. The V-PCRF is connected to the TDF (Traffic Detection Function) via the **Sd** interface. The 3GPP AAA Proxy is connected to the BBF AAA (proxy) via the **SWa/STa** interface. +- BBF defined access and network:** Contains **BRAS/BNG**, **BPCF**, and **BBF AAA (proxy)**. The BRAS/BNG is connected to the BPCF via the **R** interface. The BPCF is connected to the BBF AAA (proxy) via the **S9a** interface. The BRAS/BNG is also connected to the AN (e.g. DSLAM/ONT) via the **V** interface. +- Customer Premises Network:** Contains **RG** (Residential Gateway), **WiFi AP**, and **BBF Device**. The RG is connected to the AN via the **U** interface. The RG is also connected to the WiFi AP and the BBF Device. + +External components include: + +- Network to offload to (any NW):** A circle representing an external network, connected to the TDF. +- IP service:** A circle representing an IP service, connected to the TDF. +- UE (User Equipment):** Connected to the WiFi AP. + +Network architecture diagram showing the NSWO for 3GPP domain supporting the AF - roaming scenario. It illustrates the flow from EPC HPLMN through EPC VPLMN, BBF defined access and network, and Customer Premises Network to a UE. + +Figure 4.2.4-2: NSWO for 3GPP domain supporting the AF – roaming scenario + +In this architecture scenario the AF is located in the 3GPP domain. + +#### Architecture scenario B: AF ("BBF AF") in BBF domain + +![Architecture diagram showing the flow from EPC HPLMN through EPC VPLMN and BBF defined access to a Customer Premises Network, including components like H-PCRF, V-PCRF, BRAS/BNG, and various AAA servers.](09955ff8214ffb6947951fc0f60eb6ab_img.jpg) + +The diagram illustrates the network architecture for a non-roaming scenario involving 3GPP and BBF domains. It is organized into three main vertical sections representing different network layers: + +- EPC HPLMN (Home PLMN):** Contains the **H-PCRF** and a **3GPP AAA Server**. These are connected to the EPC VPLMN via **S9** (for PCRF) and **SWd** (for AAA) interfaces. +- EPC VPLMN (Visited PLMN):** Contains the **V-PCRF** and a **3GPP AAA Proxy**. The V-PCRF is connected to the H-PCRF via S9 and to the BBF AAA (proxy) via **S9a**. The 3GPP AAA Proxy is connected to the 3GPP AAA Server via SWd and to the BBF AAA (proxy) via **SWa/STa**. The V-PCRF is also connected to a **TDF** (Traffic Detection Function) via an **Sd** interface. The TDF is connected to an external **Network to offload to (any NW)** which provides **IP service**. +- BBF defined access and network / Customer Premises Network:** This section contains the **BRAS/BNG**, **AN (e.g DSLAM/ONT)**, **RG**, **WiFi AP**, and **BBF Device**. The BRAS/BNG is connected to the V-PCRF via an **Sd** interface and to the BBF AAA (proxy) via an **R** interface. The BRAS/BNG is also connected to the AN. The AN is connected to the RG via a **U** interface. The RG is connected to both the WiFi AP and the BBF Device. The WiFi AP is connected to the **UE** (User Equipment). + +Architecture diagram showing the flow from EPC HPLMN through EPC VPLMN and BBF defined access to a Customer Premises Network, including components like H-PCRF, V-PCRF, BRAS/BNG, and various AAA servers. + +Figure 4.2.4-3: NSWO for 3GPP over BBF domain supporting the AF – non-roaming scenario + +![Architecture diagram for NSWO for 3GPP over BBF domain supporting the AF – roaming scenario. The diagram shows a hierarchy of network domains: EPC HPLMN at the top, EPC VPLMN in the middle, and BBF defined access and network and Customer Premises Network at the bottom. Key components include H-PCRF, 3GPP AAA Server, V-PCRF, 3GPP AAA Proxy, TDF, BRAS/BNG, AN (e.g. DSLAM/ONT), BPCF, BBF AAA (proxy), RG, WiFi AP, BBF Device, and UE. Reference points S9, S9d, S9a, SWa/STa, Sd, R, V, U, and G/E are indicated between the components.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Architecture diagram for NSWO for 3GPP over BBF domain supporting the AF – roaming scenario. The diagram shows a hierarchy of network domains: EPC HPLMN at the top, EPC VPLMN in the middle, and BBF defined access and network and Customer Premises Network at the bottom. Key components include H-PCRF, 3GPP AAA Server, V-PCRF, 3GPP AAA Proxy, TDF, BRAS/BNG, AN (e.g. DSLAM/ONT), BPCF, BBF AAA (proxy), RG, WiFi AP, BBF Device, and UE. Reference points S9, S9d, S9a, SWa/STa, Sd, R, V, U, and G/E are indicated between the components. + +**Figure 4.2.4-4: NSWO for 3GPP over BBF domain supporting the AF – roaming scenario** + +In this architecture scenario the AF ("BBF AF") is located in the BBF domain. + +NOTE: The "BBF AF" and E/G reference point are out of 3GPP scope. + +In this architecture scenario Rx signalling is supported over the S9a reference point. + +The following assumptions are made about functionality in the BBF Access Network: + +- The BPCF needs to map the request received over E/G (with UE local IP address) to the right IP-CAN session over S9a (i.e. session binding in BPCF) in order to find the right PCRF. +- The BPCF maps the signalling received from the BBF AF via G/E reference point in BBF domain to Rx signalling over S9a reference point. + +#### Architecture scenario C: TDF + +![Architecture diagram for NSWO with TDF - non-roaming scenario. It shows a hierarchy of network domains: EPC HPLMN (top), EPC VPLMN (middle), BBF defined access and network (bottom), and Customer Premises Network (bottom-most). Key components include H-PCRF, 3GPP AAA Server, V-PCRF, 3GPP AAA Proxy, TDF, BRAS/BNG, BPCF, BBF AAA (proxy), AN (e.g. DSLAM/ONT), RG, WiFi AP, BBF Device, and UE. Interfaces are labeled S9, S9a, S9d, S9a/S1a, Sd, R, V, U, and X. An 'IP service' is shown connected to the TDF, and a 'Network to offload to (any NW)' is also connected to the TDF.](4b87467ad9642943235f48f7d4b59449_img.jpg) + +Architecture diagram for NSWO with TDF - non-roaming scenario. It shows a hierarchy of network domains: EPC HPLMN (top), EPC VPLMN (middle), BBF defined access and network (bottom), and Customer Premises Network (bottom-most). Key components include H-PCRF, 3GPP AAA Server, V-PCRF, 3GPP AAA Proxy, TDF, BRAS/BNG, BPCF, BBF AAA (proxy), AN (e.g. DSLAM/ONT), RG, WiFi AP, BBF Device, and UE. Interfaces are labeled S9, S9a, S9d, S9a/S1a, Sd, R, V, U, and X. An 'IP service' is shown connected to the TDF, and a 'Network to offload to (any NW)' is also connected to the TDF. + +Figure 4.2.4-5: NSWO with TDF – non-roaming scenario + +![Figure 4.2.4-6: NSWO with TDF – roaming scenario. This is a network architecture diagram showing the flow of traffic and control signals between different network domains. At the top, the EPC HPLMN contains H-PCRF and 3GPP AAA Server. Below it, the EPC VPLMN contains V-PCRF and 3GPP AAA Proxy. A dashed red line separates these from the lower part. In the lower part, the BBF defined access and network contains BRAS/BNG, BPCF, and BBF AAA (proxy). The Customer Premises Network contains RG, WiFi AP, and BBF Device. A UE is connected to the WiFi AP. A TDF is connected to the IP service and the BRAS/BNG. Interfaces shown include S8, SWd, Sd, S9a, SWa/S11a, R, V, U, and X. The TDF is also connected to the Network to offload to (any NW).](26d664119ad25250780f554633444e54_img.jpg) + +Figure 4.2.4-6: NSWO with TDF – roaming scenario. This is a network architecture diagram showing the flow of traffic and control signals between different network domains. At the top, the EPC HPLMN contains H-PCRF and 3GPP AAA Server. Below it, the EPC VPLMN contains V-PCRF and 3GPP AAA Proxy. A dashed red line separates these from the lower part. In the lower part, the BBF defined access and network contains BRAS/BNG, BPCF, and BBF AAA (proxy). The Customer Premises Network contains RG, WiFi AP, and BBF Device. A UE is connected to the WiFi AP. A TDF is connected to the IP service and the BRAS/BNG. Interfaces shown include S8, SWd, Sd, S9a, SWa/S11a, R, V, U, and X. The TDF is also connected to the Network to offload to (any NW). + +**Figure 4.2.4-6: NSWO with TDF – roaming scenario** + +In this architecture alternative: + +- Multiple TDFs may be deployed +- Sd is an intra-operator interface. This architecture variant is therefore limited to the case where the BBF domain and 3GPP domain are owned by the same operator. +- For roaming scenarios the TDF belongs to and is controlled by the VPLMN. +- For the solicited application reporting mode, the PCRF shall initiate the Sd interface triggered by S9a establishment, taking into account subscription data (verified by using e.g. IMSI, received from the BPCF). +- Home routed traffic (tunnelled using SWu, S2c) will not be subjected for packet inspection by the TDF. +- Policies for roaming users may be locally configured in the V-PCRF and/or TDF. + +The following assumptions are made regarding functionality in the BBF Access Network: + +- The BBF network routes the offloaded traffic subject to packet inspection and the offloaded traffic not subject to packet inspection via the same TDF, or +- The BBF network may be configured in such a way that the traffic determined to be subject to packet inspection is routed via the TDF. Traffic that is not subject to for packet inspection may physically bypass the TDF. + +Editor's note: The support of differentiating routing handling for the traffic is subjected for packet inspection and the traffic not subjected for packet inspection by BBF access network requires further study in Broadband Forum. + +## 4.3 Architecture for Fixed Broadband Access network interworking using H(e)NB + +### 4.3.1 General + +The architecture diagrams highlight the S9a interface between the PCRF and the BBF PCF (BPCF) for Femto access to support use cases and requirements per BBF TR-203 [6], TS 22.220 [14] and TS 22.278 [5]. + +The function of the S9a interface is to convey sufficient information to the BPCF to enable it to identify the BBF network elements the 3GPP Femto connects to, and perform admission control based on the bandwidth requirements and QoS attributes of a new or modified UE service data flow(s) (via the 3GPP Femto). + +The reference architecture focuses on the policy management aspects of the 3GPP-BBF interworking. + +NOTE 1: The assumption is that the BBF BNG may be enhanced to support new functionality such as provisioning of policies from the BPCF. + +NOTE 2: The connection between the BRAS/BNG and the SeGW is IP transport connection. + +NOTE 3: When the 3GPP and Fixed Broadband access networks belong to different Service Providers security arrangement are analogous to those between the H-PCRF and the V-PCRF, and can be based on TS 33.210 [16] or TS 33.310 [17]. + +### 4.3.2 Non Roaming Architecture + +![Diagram of Non Roaming Architecture showing connections between various network elements like HSS, MME, Serving Gateway, PDN Gateway, PCRF, BPCF, BRAS/BNG, AN, RG, 3GPP Femto, and BBF Device across different network layers (Evolved Packet System, BBF defined access and network, Customer Premise Network).](e90987faabad6a6665cd8ed1151dc474_img.jpg) + +The diagram illustrates the Non Roaming Architecture, organized into three horizontal layers separated by dashed red lines: + +- Evolved Packet System (Top Layer):** + - Radio Access Networks:** E-UTRAN, UTRAN, and GERAN are connected to an **MME** via S1-MME interfaces. + - MME:** Connected to the **HSS** via S10 and S6a interfaces. It also connects to the **Serving Gateway** via S1-U. + - Serving Gateway:** Connected to the **PDN Gateway** via S5. It also connects to a **HeNB GW** (dashed box) via S4 and to an **HNB GW** via S1-U. + - PDN Gateway:** Connected to the **PCRF** via Gx and Gxc (Only for PMIP based S5) interfaces. It connects to **Operator's IP Services (e.g. IMS, PSS)** via SGi. + - PCRF:** Connected to the **Operator's IP Services** via Rx and to the **BPCF** via S9a. + - HNB GW:** Connected to the **MSC** via Iu-PS and Iu-CS interfaces. It connects to the **SeGW** via S15. + - SeGW:** Connects to the **BPCF**. +- BBF defined access and network (Middle Layer):** + - BPCF:** Receives connections from the **PDN Gateway** (S9a) and the **SeGW** (S15). + - BRAS/BNG:** Connected to the **BPCF** and to an **AN (e.g. DSLAM/ONT)**. +- Customer Premise Network (Bottom Layer):** + - RG:** Connected to the **AN (e.g. DSLAM/ONT)** and to a **3GPP Femto** and a **BBF Device**. + +Diagram of Non Roaming Architecture showing connections between various network elements like HSS, MME, Serving Gateway, PDN Gateway, PCRF, BPCF, BRAS/BNG, AN, RG, 3GPP Femto, and BBF Device across different network layers (Evolved Packet System, BBF defined access and network, Customer Premise Network). + +Figure 4.3.2-1: Non-Roaming Architecture + +NOTE 1 The reference architecture is applicable when both 3GPP and Fixed Broadband network belong to the same network operator or to different network operators. + +NOTE 2: There is only one S15 session for all UEs connected to a HNB. + +### 4.3.3 Roaming Architecture - Home Routed + +The GTP version of the architecture for the macro network does not require V-PCRF in the connection because the HPLMN does not provision QoS rules in the VPLMN. Since there is no V-PCRF in VPLMN the solution relies on the H-PCRF to initiate the Gateway Control Session over S9 to a selected V-PCRF that, in turn, initiates the Gateway Control Session over S9a with the BPCF. The HPLMN may provision policies in the VPLMN that take into account the fact that the UE connects to a 3GPP Femto. + +![Roaming Architecture - Home Routed Traffic diagram showing connections between HPLMN, VPLMN, and Customer Premise Network components.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +The diagram illustrates the 'Roaming Architecture - Home Routed Traffic' across three network domains separated by dashed red lines: + +- HPLMN (Home PLMN):** Contains the HSS, PDN Gateway, hPCRF, and Operator's IP Services (e.g. IMS, PSS, etc.). +- VPLMN (Visited PLMN):** Contains the MME, Serving Gateway, vPCRF, SeGW, HNB GW, HeNB GW, SGSN, VMSC, and various radio access networks (E-UTRAN, UTRAN, GERAN). +- BBF defined access and network:** Contains the BRAS/BNG, BPCF, and AN (e.g. DSLAM/ONT). +- Customer Premise Network:** Contains the RG, 3GPP Femto, and BBF Device. + +Key interfaces and connections include: + +- S6a between HSS and MME. +- S10 between MME and SGSN. +- S1-U between E-UTRAN and Serving Gateway. +- S4 between SGSN and Serving Gateway. +- S1-MME between GERAN/UTRAN and MME. +- S8 between Serving Gateway and PDN Gateway. +- Gx between PDN Gateway and hPCRF. +- S9 between hPCRF and vPCRF. +- Gxc (Only for PMIP based S8) between Serving Gateway and vPCRF. +- S15 between SeGW and vPCRF. +- S9a between vPCRF and BPCF. +- Rx between hPCRF and Operator's IP Services. +- SGi between PDN Gateway and Operator's IP Services. +- Iu-PS between VMSC and HNB GW. +- Iu-CS between VMSC and HNB GW. + +Roaming Architecture - Home Routed Traffic diagram showing connections between HPLMN, VPLMN, and Customer Premise Network components. + +**Figure 4.3.3-1: Roaming Architecture - Home Routed Traffic** + +NOTE 1: The reference architecture is applicable when both 3GPP VPLMN and Fixed Broadband network belong to the same network operator or to different network operators. + +NOTE 2: There is only one S15 session for all UEs connected to a HNB. + +### 4.3.4 Roaming Architecture - Visited Access/Local Breakout + +The H-PCRF does need to be aware if the UE is connected via the 3GPP Femto in the VPLMN unless Home operators require provisioning of HPLMN policies in the VPLMN. + +![Figure 4.3.4-1: Roaming Architecture - Visited Access/ Local Breakout. This diagram illustrates the network architecture for roaming, divided into three main sections by horizontal dashed red lines. The top section, labeled HPLMN, contains the HSS, hPCRF, and Operator's IP Services (e.g., IMS, PSS). The middle section, labeled VPLMN, includes the MME, Serving Gateway, PDN Gateway, HeNB GW, HNB GW, v MSC, SeGW, BPCF, BRAS/BNG, and AN (e.g., DSLAM/ONT). The bottom section, labeled Customer Premise Network, includes the RG, 3GPP Femto, and BBF Device. Various reference points (S10, S1-MME, S1-U, S4, S5, S6a, S7, S8, S9, S11, S12, S13, S14, S15, S16, S17, S18, S19, S20, S21, S22, S23, S24, S25, S26, S27, S28, S29, S30, S31, S32, S33, S34, S35, S36, S37, S38, S39, S40, S41, S42, S43, S44, S45, S46, S47, S48, S49, S50) are shown connecting these elements. The diagram also indicates 'Gxc (Only for PMIP based S5)', 'Gx', 'Rx', 'SGi', and 'S9a' reference points. The BPCF is connected to the 'BBF defined access and network'.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +Figure 4.3.4-1: Roaming Architecture - Visited Access/ Local Breakout. This diagram illustrates the network architecture for roaming, divided into three main sections by horizontal dashed red lines. The top section, labeled HPLMN, contains the HSS, hPCRF, and Operator's IP Services (e.g., IMS, PSS). The middle section, labeled VPLMN, includes the MME, Serving Gateway, PDN Gateway, HeNB GW, HNB GW, v MSC, SeGW, BPCF, BRAS/BNG, and AN (e.g., DSLAM/ONT). The bottom section, labeled Customer Premise Network, includes the RG, 3GPP Femto, and BBF Device. Various reference points (S10, S1-MME, S1-U, S4, S5, S6a, S7, S8, S9, S11, S12, S13, S14, S15, S16, S17, S18, S19, S20, S21, S22, S23, S24, S25, S26, S27, S28, S29, S30, S31, S32, S33, S34, S35, S36, S37, S38, S39, S40, S41, S42, S43, S44, S45, S46, S47, S48, S49, S50) are shown connecting these elements. The diagram also indicates 'Gxc (Only for PMIP based S5)', 'Gx', 'Rx', 'SGi', and 'S9a' reference points. The BPCF is connected to the 'BBF defined access and network'. + +**Figure 4.3.4-1: Roaming Architecture - Visited Access/ Local Breakout** + +NOTE 1: The reference architecture is applicable when both 3GPP VPLMN and Fixed Broadband network belong to the same network operator or to different network operators. + +NOTE 2: There is only one S15 session for all UEs connected to a HNB. + +# 5 Network Element, and Reference point + +## 5.1 Network Elements + +### 5.1.1 3GPP network elements + +The 3GPP network elements are defined in details in TS 23.401 [2], TS 23.402 [3] and TS 23.203 [4]. + +#### 5.1.1.1 ePDG + +The details of functionality of ePDG are described TS 23.402 [3]. + +The following enhancements are applicable: To support initiation of a Gateway Control Session over S9a from the PCRF when using untrusted access procedures, the ePDG is enhanced to transport UE Local IP address, UDP port number(s) for the UE connected to WLAN to the PCRF via the Gxb\* in untrusted S2c and S2b PMIP-based or via the S2b reference points in case of S2b GTP-based. + +#### 5.1.1.2 PCRF + +The enhancement of PCRF for supporting interworking with BBF Policy Framework is described in TS 23.203 [4] Annex P. + +#### 5.1.1.3 3GPP AAA Server + +The 3GPP AAA Server is within the 3GPP network. The 3GPP AAA Server is defined in TS 23 402 [3] and TS 29.273 [25]. + +In order to support offline and online charging for Non-seamless-WLAN offloaded traffic in Broadband Fixed Access network, the 3GPP AAA Server is enhanced to exchange accounting messages from 3GPP AAA proxy in roaming scenario or from BBF AAA proxy in non-roaming scenario. The 3GPP AAA Server reports per-user charging/accounting information about NS-WLAN offloaded traffic to the HPLMN Charging System. + +#### 5.1.1.4 3GPP AAA Proxy + +The 3GPP AAA Proxy is within the 3GPP network. The 3GPP AAA Proxy is defined in TS 23 402 [3] and TS 29.273 [25]. + +In order to support offline and online charging for Non-Seamless WLAN offloaded traffic in Broadband Fixed Access network, the 3GPP AAA Proxy in VPLMN is enhanced to relay accounting data received from the BBF AAA Proxy in fixed domain to the 3GPP AAA Server in HPLMN. The 3GPP AAA Proxy is further enhanced to report per-user charging/accounting information to the VPLMN Charging System for inter-operator settlement for roaming users. + +### 5.1.2 BBF network elements + +The BBF network elements BRAS, BNG, RG, BBF AAA proxy, BPCF are defined in details in BBF TR-058 [7], BBF TR-101 [8], BBF TR-145 [10] and BBF TR-134 [11]. The BBF device represents any devices defined by Broadband Forum or supported by Fixed Broadband Access, as a PC, Media centre, etc., and they are considered outside the scope of 3GPP. + +The definition of enhancements for BBF AAA for 3GPP interworking and for BPCF to support Policy & QoS interworking with mobile networks is specified in BBF TR-134 [11] and BBF TR-203 [6] + +## 5.2 Reference Points + +The reference points S1-MME, S1-U, S3, S4, S5, S6a, S8, S10, S11 are defined in TS 23.401 [2]. The reference points S2c, S6b, SWx, SWd, SWm, SWn, SWu, SGi, Gxc are defined in TS 23 402 [3]. The reference point Rx and Sd are defined in TS 23.203 [4]. + +- Gx** For purpose of BBF interworking it transfers the UE/H(e)NB Local IP address and the UDP port number if NAT/NAPT is detected in the BBF access network at which the H(e)NB is connected to. +- Gxb\*** It connects the ePDG with the PCRF and transports UE Local IP address, UDP port number(s) for the UE connected to WLAN. It is used in untrusted S2c and S2b-PMIP case .This information triggers the PCRF to initiate the Gateway Control Session over S9a. +- S2b** For purpose of BBF interworking it transfers UE Local IP address and UDP port number(s) in cases of S2b-GTP. This information triggers the PCRF to initiate the Gateway Control Session establishment over S9a towards the BPCF. +- S15** It supports the initiation, modification and termination of sessions between the HNB GW and PCRF to support CS sessions. This interface triggers the PCRF to request allocation of resources in the Fixed Broadband access network for CS sessions. +- S9** For BBF interworking for WLAN UE roaming with home routed access and S2b/Gx being used to trigger the PCRF to initiate the Gateway Control Session establishment over S9a, or for BBF interworking using GTP Home Routed Traffic for H(e)NB, the S9 interface is enhanced to carry from the H-PCRF to the V-PCRF the UE/H(e)NB Local IP address and the UDP port number if NAT/NAPT is detected in the Fixed Broadband access network at which the H(e)NB is connected to. + +- S9a** For purpose of BBF interworking it provides transfer of dynamic QoS control policies (QoS) from the Home PCRF to the BBF Policy Control function (BPCF) and in roaming scenario from the Visited PCRF and to the BBF Policy Control function (BPCF). Furthermore the S9a carry from the H-PCRF/V-PCRF the UE/H(e)NB local IP address, UDP port number(s) and/or FQDN of Fixed Broadband access network at which the H(e)NB is connected to. The S9a is based on enhancement of S9 reference point for supporting interworking with BBF Policy Framework. +- SWa** For purpose of BBF interworking it connects the BBF AAA proxy with the 3GPP AAA Server/Proxy and transports access authentication, authorization and accounting information in a secure manner. The transport of accounting information is applicable only to non-seamless WLAN offloaded traffic. +- STa** For purpose of BBF interworking it connects the BBF AAA proxy with the 3GPP AAA Server/Proxy and transports access authentication, authorization, mobility parameters and accounting information in a secure manner. The transport of accounting information is applicable only to non-seamless WLAN offloaded traffic. + +The Reference points within the BBF access network are defined in BBF TR 058 [7], BBF TR-101 [8], BBF TR-145 [10] and BBF TR-134 [11] and they are considered out of the scope of 3GPP. + +# --- 6 Policy and QoS interworking + +## 6.1 General + +### 6.1.1 Principles for EPC-routed traffic + +Policy control for EPC routed traffic is provided when either 3GPP access authentication or tunnel based authentication is performed. + +Multi Access PDN Connectivity for WLAN access located in a Fixed Broadband Access Network implies that a 3GPP UE with multi access PDN connectivity capabilities can connect to WLAN access located in a Fixed Broadband Access Network as described in TS 23.401 [2] and TS 23 402 [3]. + +Integrity and confidentiality protection for S2c trusted scenarios can be optionally activated by the UE or the PDN GW as defined in TS 23 402 [3]. In the case of confidentiality protection the Fixed Broadband Access Network does not have visibility of the inner header, similarly to what happens to the untrusted S2c case. However, given that DSCP of the outer header is used for packet differentiation, the procedures to support interworking with Fixed Broadband Access Network do not need to change due to the activation of confidentiality protection. + +If the H(e)NB is located behind a NATed RG the H(e)NB local IP address is provided to the H(e)NB by the SeGW as part of the set up of the security tunnel with the SeGW using IKEv2 signalling. + +A new HNB local IP address is provided by the SeGW to the HNB then included in Iu signalling (refer to the definition of INITIAL UE MESSAGE message, RELOCATION COMPLETE message and ENHANCED RELOCATION COMPLETE REQUEST message in TS 25.413 [28]) to the SGSN. + +A new HeNB local IP address is provided by the SeGW to the H(e)NB then included in S1 signalling (refer to the definition of INITIAL UE MESSAGE message, HANDOVER NOTIFY message and PATH SWITCH REQUEST message in TS 36.413 [29]) to the MME. + +### 6.1.2 Principles for Non-seamless WLAN-offload traffic + +Policy control for NS-WLAN offloaded traffic is provided only if 3GPP access authentication is performed. + +Policies for a UE's NS-WLAN offloaded traffic are sent from the EPC Network to the Fixed Broadband access network via S9a. + +Policy interworking via S9a for NS-WLAN offloaded traffic in this release is supported for scenarios without NAT in the BBF domain, + +For architecture scenario A in clause 4.2.4, the PCRF shall bind the request from AF with an existing IP-CAN session established over S9a using the UE local IP address received from AF and if available the subscriber ID (e.g. IMSI). + +For architecture variant B in clause 4.2.4, it is assumed that BPCF binds the request from AF with an existing IP-CAN Session established over S9a using the UE local IP address received from AF and if available the subscriber ID (e.g. IMSI). + +For architecture variant C in clause 4.2.4, in solicited application reporting mode, the PCRF shall start the Sd session with the TDF when an indication of IP-CAN session establishment is received over S9a for the UE local IP address. In unsolicited application reporting mode, the TDF notifies the PCRF of the detected service using the Sd interface. + +The UE may simultaneously have one or more connection(s) to the EPC and a connection to NS-WLAN using the same local IP address. In order to allow the BNG to distinguish and to enforce separated QoS control for EPC routed traffic (tunnelled using SWu, S2c) and for NSWO traffic, the PCRF shall send the destination IP address of the IPSec outer IP header, i.e. the ePDG IP address (for S2b and untrusted S2c access), and PDN GW IP address(es) (for trusted S2c) and the UDP source port number (for used by IPSec tunnel traffic) to the BPCF. + +## 6.2 Application of PCC to Fixed Broadband Access interworking + +Fixed Broadband Access networks that support BBF Policy Framework and EPC network that supports the PCC interworked via procedures specified in TS 23.203 [4], Annex P. + +## 6.3 QoS solution for 3GPP and Fixed Broadband Access Interworking + +### 6.3.1 Generic + +This clause describes how to detect and classify IP packets for the purpose of QoS treatment in the Fixed Broadband Access network. The solution is based on DSCP marking of packets traversing the Fixed Broadband Access network. The Fixed Broadband Access network (e.g. BNG) makes packet classification based on the DSCP of the incoming packets. The solution assumes functionality in the BBF domain, all these functions are out-of-scope for 3GPP; also, these functions may or may not be implemented depending on the agreement between 3GPP and Fixed Broadband Access operator, these functions are described for information only. + +Fixed Broadband Access network currently supports the DSCP marking as specified in BBF TR-092 [20] for BRAS, in BBF TR-101 [8] for Access Nodes and Aggregation Nodes and in BBF TR-124 Issues 2 [21] for the RG. + +![Diagram showing packet classification and forwarding treatment in a 3GPP-Fixed Broadband Access interworking scenario. It illustrates traffic flow from Voice, Video, and Internet sources through a Mobile Terminal, Residential Gateway, Fixed Access Node, BNG, ePDG, and finally to the PDN-GW. Annotations explain QoS handling at various points: UE installs filters for UL traffic, RG honors DSCP marking, and PDN GW performs DSCP marking in down-link based on QCI.](e1476fd216f6cf773e262013fb4aba7d_img.jpg) + +The diagram illustrates the packet flow and QoS handling in a 3GPP-Fixed Broadband Access interworking scenario. On the left, traffic from Voice, Video, and Internet sources enters the Mobile Terminal. A callout indicates that 'Reflective QoS installs packet filters and DSCP marking for UL traffic in the UE'. The traffic then passes through a Residential Gateway (RG), with a note that 'RG honors the DSCP marking set by the UE'. A dashed circle around the RG and Mobile Terminal has a callout stating 'Ensuring QoS here (e.g., on WIFI) is out of scope'. The traffic continues through a Fixed Access Node to the BNG (Broadband Network Gateway). From the BNG, it goes through the ePDG (PDN Gateway) and finally to the PDN-GW. A callout for the PDN-GW states 'Packet filters (TFTs). PDN GW performs DSCP marking in down-link based on QCI of packet.' The diagram uses icons for each network element and lines to represent the data paths. + +Diagram showing packet classification and forwarding treatment in a 3GPP-Fixed Broadband Access interworking scenario. It illustrates traffic flow from Voice, Video, and Internet sources through a Mobile Terminal, Residential Gateway, Fixed Access Node, BNG, ePDG, and finally to the PDN-GW. Annotations explain QoS handling at various points: UE installs filters for UL traffic, RG honors DSCP marking, and PDN GW performs DSCP marking in down-link based on QCI. + +**Figure 6.3.1-1: Packet classification and packet forwarding treatment in a 3GPP-Fixed Broadband Access interworking scenario for traffic routed to EPC** + +![Diagram illustrating packet classification and packet forwarding treatment in a 3GPP-Fixed Broadband Access interworking scenario for NS-WLAN offload traffic. The diagram shows traffic flow from Voice, Video, and Internet sources through a Mobile Terminal (UE), a Residential Gateway (RG), a Fixed Access Node, and a BNG. Annotations explain that Reflective QoS in the UE installs packet filters and DSCP marking for UL traffic, the RG honors the DSCP marking, and the BNG performs DSCP marking in the downlink based on QoS information received via the R interface. A note indicates that ensuring QoS in the UE (e.g., on WiFi) is out of scope.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +The diagram illustrates the flow of traffic from Voice, Video, and Internet sources through a Mobile Terminal (UE), a Residential Gateway (RG), a Fixed Access Node, and a BNG. Annotations indicate that Reflective QoS in the UE installs packet filters and DSCP marking for UL traffic, the RG honors the DSCP marking, and the BNG performs DSCP marking in the downlink based on QoS information received via the R interface. A note indicates that ensuring QoS in the UE (e.g., on WiFi) is out of scope. + +Diagram illustrating packet classification and packet forwarding treatment in a 3GPP-Fixed Broadband Access interworking scenario for NS-WLAN offload traffic. The diagram shows traffic flow from Voice, Video, and Internet sources through a Mobile Terminal (UE), a Residential Gateway (RG), a Fixed Access Node, and a BNG. Annotations explain that Reflective QoS in the UE installs packet filters and DSCP marking for UL traffic, the RG honors the DSCP marking, and the BNG performs DSCP marking in the downlink based on QoS information received via the R interface. A note indicates that ensuring QoS in the UE (e.g., on WiFi) is out of scope. + +**Figure 6.3.1-2: Packet classification and packet forwarding treatment in a 3GPP-Fixed Broadband Access interworking scenario for NS-WLAN offload traffic** + +The figure 6.3.1-1 and the figure 6.3.1-2 are simplified and the intermediate transport network entities in both figures are not shown. The details of traffic handling in the Fixed Broadband Access domain are out of 3GPP scope. + +In order to support QoS in Fixed Broadband Access: + +- The BPCF needs to map the QoS information (QCI, bit rates, ARP) received over S9a to access-specific parameters applicable in the Fixed Broadband Access network as specified in TR-203 [6]. +- The BRAS/BNG can perform QoS treatment and QoS remapping based on DSCP value of the outer IP header as specified in BBF TR-059 [26]. For NS-WLAN offload traffic, the BRAS/BNG can support per-flow DSCP marking on each packet based on the QoS information received via R interface. +- The RG can perform QoS treatment and QoS remapping based on DSCP value of the outer IP header based on pre-provisioned rules in the RG as specified in BBF TR-059 [26]. +- For both EPC routed traffic and NS-WLAN offload traffic cases, if the UE implements reflective QoS and the Fixed Broadband Access network needs to be protected from a misbehaving UE, Fixed Broadband Access needs to implement protective measures (e.g. per-UE bandwidth limitation in the RG or in the BNG). +- The decision to apply Reflective QoS is performed as part of the AAA signalling for UE authentication. The 3GPP AAA takes the decision to apply Reflective QoS based on the capabilities of the UE, the type of access and local policies then informs the UE. +- If the UE supports Reflective QoS then the UE shall indicate support of reflective QoS to the 3GPP AAA server during the authentication procedure using EAP-AKA signalling. +- In response to the UE indication, the 3GPP AAA may provide an indication to the UE on whether Reflective QoS shall be applied during the UE authentication procedure using EAP-AKA signalling. + - When access authentication is performed the BBF AAA informs the 3GPP AAA that the UE is attached via BBF-defined Fixed Broadband access network in over STa/SWa and the UE shall perform UE reflective QoS on all traffic of the attached network. The UE shall disable the reflective QoS if the UE is detached or moves away from the attached Fixed Broadband access network. + - When authentication is performed as part of IKEv2 signalling the 3GPP AAA determines if the UE is connected via a BBF-defined WLAN access based on UE Local IP address received in EAP-AKA signalling over SWm or S6b and the UE shall perform UE reflective QoS on the tunnelled traffic of the attached network. The UE shall disable the reflective QoS if the tunnel established by using the IKEv2 signalling is released. + +**NOTE:** In this Release there is no procedure defined to support activation and deactivation of Reflective QoS towards the UE when moving from one BBF defined Fixed Broadband Access network into another BBF defined Fixed Broadband Access network. + +### 6.3.2 Downlink + +#### 6.3.2.1 EPC routed traffic + +For the WLAN case, the P-GW in the 3GPP domain sets a per-flow DSCP marking on each packet outer header, as defined in TS 23 402 [3]. In un-trusted scenarios where traffic is sent in an IPSec tunnel from ePDG to the UE, the ePDG shall copy that marking to the new outer header unless DSCP remapping is performed as defined in clause 6.3.4. + +For the H(e)NB case, the P-GW in the 3GPP domain sets a per-flow DSCP marking on each packet outer header, as defined in TS 23.401 [2]. The SeGW shall copy that marking to the new outer header. + +NOTE 1: DSCP remapping performed as defined in clause 6.3.4 may apply. + +The BRAS/BNG located in between the H(e)NB and the SeGW/H(e)NB GW and between the UE and ePDG/PDN GW, may perform QoS treatment and QoS remapping based on DSCP value of the outer IP header. + +For the control plane in the H(e)NB case, the QoS associated with control plane traffic (e.g. H(e)NB management traffic, Iu/S1 messages) could be preconfigured in the relevant network entity (e.g. H(e)MS, MME/SGSN) for downlink. The relevant message traffic thus may be marked with the appropriate DSCP according to the preconfigured QoS. The SeGW shall copy this DSCP if it exists from the inner header to the outer header. + +NOTE 2: It is assumed that the MME/SGSN set the DSCP value of signalling traffic independently whether there is H(e)NB or not. + +#### 6.3.2.2 NS-WLAN offloaded traffic + +The BNG/BRAS in the BBF domain may set a per-flow DSCP marking on each packet header. Alternatively, for operator deployments when the BNG is not at the network edge, the BNG may perform QoS treatment based on the DSCP value of the packet IP header. + +### 6.3.3 Uplink + +For the WLAN case, including EPC-routed traffic and NS-WLAN offload traffic, DSCP marking may be performed by the UE by means of reflective QoS. The UE creates a 5-tuple rule from the corresponding downlink 5-tuple derived from the downlink IP traffic. It associates that uplink rule with the DSCP received in corresponding downlink 5-tuple. Each uplink packet matching that uplink rule is marked with the associated DSCP. + +For IP flows initiated from the UE, uplink packets will not be marked until a marked downlink packet is received with the downlink n-tuple that matches the received uplink n-tuple. + +Some clarifications to the function of reflective QoS in the UE (this describes only the logical function for the reflective QoS marking, the implementation might be differently): + +- For each incoming downlink IP packet the UE checks if a DSCP marking rule for the n-tuple of this IP packet exists. If the rule does not exist, then a new marking rule is added. Otherwise, the DSCP value and the time stamp for this marking rule are set. +- The uplink n-tuple in each marking rule is made from the downlink n-tuple of that rule by swapping address (and port) destination and source. +- For each outgoing IP packet the UE checks if a marking rule for this IP packet exists. If the n-tuple of the packet matches the uplink n-tuple of a marking rule, then the DSCP value of the packet is set to the DSCP value of that marking rule. The time stamp for that rule is set. +- For tunnelled scenarios, the n-tuples correspond to the n-tuples of the inner header of the packet. In all scenarios, the DSCP value of the marking rule is the DSCP value of the outer header of the packet. This in both downlink and uplink direction. +- A marking rule is removed when a certain period of time has passed since the time stamp. +- The function of reflective QoS will overwrite DSCP markings set by the UE application. + +The Fixed Broadband Access implements bandwidth limitation on a per-line granularity. However, at this point in time, Fixed Broadband Access does not implement per-device bandwidth limitation in the RG. Therefore, the UE may take more uplink resources between RG and PDN GW than it was entitled to by S9a admission control (e.g. the UE might + +set the DSCP incorrectly). Fixed Broadband Access might implement a number of mechanisms to protect the Fixed Broadband Access network from a misbehaving UE : + +- The RG might have pre-configured rules to allow only 3GPP UEs to set DSCP. Distinguishing 3GPP UE from other devices might for example be based on authentication (always EAP-AKA for 3GPP UEs) or from packet destination address (always ePDG/P-GW for S2b/S2c). +- The BNG may enforce UE bandwidth limitation based on the information (including QoS rules) received over S9a via the BPCF. These rules may have a different granularity as determined suitable for the Fixed Broadband Access network (e.g. in a scenario with user place confidentiality protection). The granularity may be on a per UE and DSCP or per UE and IP flow basis. + +For the H(e)NB case, DSCP marking is performed by the H(e)NB according to the QoS information of the EPS bearer/PDP context. The H(e)NB shall copy the marking to the outer header. Based on H(e)NB configuration either the QCI mapping or the Reflective QoS may be used. + +The RG and BNG located in between the H(e)NB and the SeGW/H(e)NB GW and between the UE and ePDG/PDN GW may perform QoS treatment and QoS remapping based on DSCP value of the outer IP header. + +For the control plane in the H(e)NB case, the QoS associated with control plane traffic (e.g. H(e)NB management traffic, Iu/S1 messages) could be preconfigured in the H(e)NB for uplink. The H(e)NB marks the relevant message traffic with the appropriate DSCP according to the preconfigured QoS. It then copies the DSCP from the inner header to the outer header to ensure the correct QoS treatment in the tunnel before it gets into it. + +### 6.3.4 DSCP remapping + +This clause is only applied to EPC routed traffic case. + +Since different domains and operators might use different DSCP values, the scheme above only works if there are agreed re-mappings of the DSCP values. E.g., there might be an edge router in inter-operator domain boundaries that re-maps the DSCPs. + +It is assumed that there are appropriate inter-operator agreements (e.g. SLAs) in place to ensure that such re-mapping is consistent and predictable. If there is no such inter-operator agreement, the DSCP re-mapping may not be consistent and predictable. + +### 6.3.5 Correlating admission control with DSCP marking + +NOTE: This clause is applied to both EPC routed case and NS WLAN-offload traffic case. + +In Fixed Broadband Access the admission control decision may be performed by the BPCF or be delegated by the BPCF to another Fixed Broadband Access node. Based on the admission control decision, the BPCF accepts or rejects the request received over S9a. The Fixed Broadband Access operator may also want to ensure that the traffic for a specific UE is not exceeding the traffic agreed by admission control and communicated over S9a. In order to do so, the BPCF may provide policies to the BNG. These policies are based on the QoS Rules received over S9a but may have a different granularity as determined suitable for the Fixed Broadband Access network. + +Regardless of the access method used, the BPCF shall be able to translate QCI received in QoS Rules on S9a into the DSCP that the BNG will see. To do this, the BPCF shall know the relation between QCIs and DSCPs for the traffic that enters the Fixed Broadband Access domain. The QCI to DSCP mapping used in BBF access network is under BBF responsibility. + +The correlation function mentioned above is Fixed Broadband Access-internal and therefore out-of-scope for 3GPP. + +### 6.3.6 Multiple IPSec Child SAs support + +This clause is only applied to EPC-routed case. + +RFC 4301 [27] clarifies that if different classes of traffic (distinguished by DSCP bits) are sent on the same IPSec Security Association (SA) and if the receiver is employing the optional anti-replay feature available in both AH and ESP; this could result in inappropriate discarding of lower priority packets due to the windowing mechanism used by this feature. If this anti-replay feature is implemented then the ePDG/SeGW (downlink) and UE/H(e)NB (uplink) should map IP flows of different DSCP to different child SA to avoid this problem. + +When the UE initial access through S2b, or S2c with extended security enabled or when H(e)NB power on, depending on the operator's policy, multiple IPSec child SAs with or without different DSCP are established between UE and ePDG or between H(e)NB and the SeGW. Both the uplink and downlink IP flows should be encapsulated and transferred within the appropriate child SA identified by the DSCP, if security association for different DSCP values are established, as described in RFC 4301 [27]. + +When a right child SA is not found a new child SA shall be created by the ePDG/SeGW (downlink) and UE/H(e)NB (uplink). + +The increase of the anti-replay window size can also be used but it does not guarantee that packets will not be discarded. + +## 6.4 Authentication and Security procedures for 3GPP and Fixed Broadband access interworking + +The following procedures are defined for authentication of a 3GPP UE via a Fixed Broadband Access network as specified in TS 33.402 [23]: + +- 3GPP-based access authentication. This assumes that the Fixed Broadband Access network supports 3GPP EAP-based access authentication and forwards EAP signalling messages between the UE and EPC. +- Tunnel authentication procedures for SWu. This authentication is transparent to the Fixed Broadband Access network. +- Authentication for S2c (DSMIPv6). This authentication is transparent to the Fixed Broadband Access network. + +In procedure 1, the permanent user identity (i.e. an IMSI in EPC root NAI format as defined by TS 23.003 [24]) shall be provided upon successful authentication in the reply from 3GPP AAA to Fixed Broadband Access AAA, for both STa and SWa. The BPCF shall initiate an IP-CAN Session over S9a towards the PCRF for the UE as defined in clauses 7 and 8 and in TS 23.203 [4]. + +In procedure 2 and 3, a Gateway Control Session over S9a for this UE shall be triggered by the PCRF as defined in clauses 7 and 8 and in TS 23.203 [4]. + +Translation between RADIUS and Diameter is performed in the Fixed Broadband Access as described in TR-203 [6]. + +# --- 7 Functional Description and Procedures for Fixed Broadband Access network over S2b + +## 7.1 General + +The call flow figures in the subsequent clauses are based on TS 23.402 [3]. The home routed roaming, LBO and non-roaming scenarios are depicted. In the LBO case, the 3GPP AAA Proxy acts as an intermediary, forwarding messages from the 3GPP AAA Server in the HPLMN to the PDN GW in the VPLMN and vice versa. Messages between the PDN GW in the VPLMN and the hPCRF in the HPLMN are forwarded by the vPCRF in the VPLMN. In the non-roaming case, the vPCRF and the 3GPP AAA Proxy are not involved. + +The optional PCRF interaction steps between the gateways/BPCF and the PCRF in all the procedures only occur if dynamic policy provisioning is deployed. Otherwise the gateways may employ the policies statically configured in the gateways and Fixed Broadband Access may employ Fixed Broadband Access local policies. + +## 7.2 Initial Attach + +This clause specifies the additional procedures at the UE's initial attachment to a Fixed Broadband access network via PMIPv6 or GTPv2 based S2b interface, for the UE to establish the first PDN connection over the Fixed Broadband Access with S2b, and/or for the UE to have offloaded traffic via Fixed Broadband Access. + +NOTE 1: It is up to stage 3 to optimize S9a procedures for Non-Seamless WLAN offloaded traffic and EPC routed traffic handled by the same PCRF. + +This procedure establishes a session between the BPCF and the PCRF to provision policy decisions for NS-WLAN offloaded traffic and/or to provision policy decisions for EPC routed traffic. + +![Sequence diagram for Initial attachment (Figure 7.2-1). The diagram shows interactions between UE, RG, BNG, AAA proxy, BPCF, ePDG, PDN GW, vPCRF, 3GPP AAA Proxy, hPCRF, HSS/AAA, and TDF. It is divided into 'Fixed Broadband Access Network' and 'Roaming Scenarios'. Steps include: 1. 3GPP-based access authentication (EAP-AKA); 2. Local IP address assignment; 3. Trigger; 4. Indication of IP-CAN session Establishment; 5. TDF session establishment (for NS-WLAN offloaded traffic); 6. PDN connection setup; 7. ePDG-initiated Gateway Control Session Establishment; 8. PCRF-initiated Gateway Control Session Establishment; 9. policy interaction.](08c7a76a7786bd08b99dd4cb41583ef4_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RG + participant BNG + participant AAA_proxy as AAA proxy + participant BPCF + participant ePDG + participant PDN_GW as PDN GW + participant vPCRF + participant 3GPP_AAA_Proxy as 3GPP AAA Proxy + participant hPCRF + participant HSS_AAA as HSS/AAA + participant TDF + + Note left of RG: Fixed Broadband Access Network + Note right of 3GPP_AAA_Proxy: Roaming Scenarios + + UE->>3GPP_AAA_Proxy: 1. 3GPP-based access authentication (EAP-AKA) + 3GPP_AAA_Proxy-->>BNG: + BNG->>UE: 2. Local IP address assignment + BNG->>BPCF: 3. Trigger + BPCF->>vPCRF: 4. Indication of IP-CAN session Establishment + vPCRF->>TDF: 5. TDF session establishment (for NS-WLAN offloaded traffic) + Note over UE, TDF: 6. PDN connection setup as specified in TS 23.402, clause 7.2.1 or 7.2.4 + ePDG->>vPCRF: 7. ePDG-initiated Gateway Control Session Establishment + vPCRF->>ePDG: 8. PCRF-initiated Gateway Control Session Establishment + BPCF->>AAA_proxy: 9. policy interaction + +``` + +Sequence diagram for Initial attachment (Figure 7.2-1). The diagram shows interactions between UE, RG, BNG, AAA proxy, BPCF, ePDG, PDN GW, vPCRF, 3GPP AAA Proxy, hPCRF, HSS/AAA, and TDF. It is divided into 'Fixed Broadband Access Network' and 'Roaming Scenarios'. Steps include: 1. 3GPP-based access authentication (EAP-AKA); 2. Local IP address assignment; 3. Trigger; 4. Indication of IP-CAN session Establishment; 5. TDF session establishment (for NS-WLAN offloaded traffic); 6. PDN connection setup; 7. ePDG-initiated Gateway Control Session Establishment; 8. PCRF-initiated Gateway Control Session Establishment; 9. policy interaction. + +**Figure 7.2-1: Initial attachment** + +NOTE 2 In the roaming case, step 7 terminates at the V-PCRF. + +If dynamic policy provisioning over S9a is not deployed, the optional steps 3, 4, 5, 7 and 8 do not occur. Instead, the Fixed Broadband Access Network may employ local policies. + +For NS-WLAN offloaded traffic, the local IP session for the UE in Fixed Broadband Access is handled as an IP-CAN session by the PCRF. For EPC-routed traffic, the IP-CAN session for the PDN Connection in the PDN GW is created via Gx procedures. In addition, a Gateway Control Session is established between the BPCF and the PCRF corresponding to the EPC-routed IP-CAN session in the PCRF. + +The Fixed Broadband Access domain has local policies that indicate as part of the inter-operator agreements, both if policy control for NSWO is provided and the NSWO-APN for subscribers for a given HPLMN. + +NOTE 3: Dynamic provisioning from the HPLMN of either an indication of policy control for NS-WLAN traffic and what the NSWO-APN is for the subscriber of a certain PLMN is out of the scope of this Release. + +1. The UE may perform the 3GPP based (EAP) access authentication procedure involving the Fixed Broadband Access network as specified in TS 23 402 [3] clause 7.2.1 step 1. As part of this step, the permanent user identity (IMSI) is provided from the 3GPP AAA Server to the Fixed Broadband Access network and an indication to apply Reflective QoS is provided to the UE.. +2. The UE receives a local IP address from the Fixed Broadband Access Network. How this is done is out of 3GPP scope, but it may involve IP address assignment by an RG or a BNG. + +The steps in 3, 4 and 5 describe PCC signalling to provision policies for NS-WLAN offloaded traffic and are only triggered when 3GPP access authentication is performed and the BPCF receives the IMSI and the Fixed Broadband Access allocated UE local IP address. + +3. Triggered by steps 1 and 2, the BPCF is informed about the UE accessing over Fixed Broadband Access. How this is done is out of 3GPP scope. +4. When the BPCF receives the trigger and policy interworking with PCRF is supported, if local policies indicate that policy control for NS-WLAN offloaded traffic is provided for subscribers from that PLMN, the BPCF sends + +an indication of IP-CAN session establishment for NS-WLAN offloaded traffic as specified in TS 23.203 [4]. The BPCF includes the IMSI, IP-CAN type, UE local IP address and the NSWO-APN in the message to the PCRF. The PCRF acknowledges the IP-CAN session establishment if HPLMN operator policies enable policy control for NS-WLAN offloaded traffic for this user as specified in TS 23.203 [4]. + +5. Triggered by the successful establishment of the IP-CAN session for the UE local IP address in step A2, the V-PCRF (roaming) and the PCRF (non-roaming) may establish a session with the TDF to provision ADC Rules for that UE local IP address (if applicable and when solicited application reporting mode applies). + +The steps in 6, 7 and 8 describe PCC signalling to provision policies for EPC routed traffic. Step 7 is only applicable when S2b PMIPv6 is used. + +6. The description of the PDN connection setup procedure is the same as for steps 2-9 in TS 23 402 [3], clause 7.2.1 or for steps A.1-E.1 in TS 23 402 [3] clause 7.2.4, with the following additions when S2b-GTP is used: The UE local IP address and optionally UDP source port number (if NAT is detected) are also included in the Create Session Request message. The UE local IP address and optionally UDP source port number (if NAT is detected) are forwarded to the PCRF in IP-CAN Session Establishment procedure, an indication to apply Reflective QoS is provided to the UE as part of the IKEv2 tunnel establishment. +7. Triggered by the IKEv2 tunnel establishment in step 3 and by the indication that the UE is connected via a WLAN connected to fixed broadband access from 3GPP AAA, the ePDG initiates Gxb\* session establishment with the PCRF by using Gateway Control Session establishment procedure as specified in TS 23.203 [4]. The ePDG includes the IMSI, APN, IP-CAN type, UE IP address allocated by EPC, the UE local IP address and optionally UDP source port number (if NAT is detected). + +NOTE 4: The 3GPP AAA determines if the UE is connected via a WLAN connected to a fixed broadband access on UE Local IP address received in EAP-AKA signalling over SWm. + +8. This step may be triggered by step 6 or step 7. + +When triggered by step 6, the PCRF (for non-roaming case), the V-PCRF (for visited access) or the H-PCRF (for home routed) initiates Gateway Control Session establishment with the BPCF. The V-PCRF (for home routed) proxies the Gateway Control Session Establishment request to the BPCF: IMSI and UE local IP address and port needs to be included in the Gateway Control Session Establishment request message. + +When triggered by step 7, the PCRF (for non-roaming case) and the V-PCRF (for home routed and visited access roaming case) initiates Gateway Control Session establishment request over S9a with the BPCF. IMSI and UE local IP address and port needs to be included in the Gateway Control Session Establishment request message over S9a. + +9. The BPCF may interact with the BNG, e.g. to download policies, as defined by Fixed Broadband Access Policy Framework specifications BBF TR-134 [11] and BBF TR-203 [6]. This step is out of 3GPP scope. + +## 7.3 UE/ePDG-initiated Detach Procedure and UE-Requested PDN Disconnection + +This clause is related to the case when the UE has one or more PDN connection(s) established via a Fixed Broadband access network via PMIPv6 or GTPv2 based S2b interface and the Detach Procedures is initiated by UE or ePDG, or the UE-requested PDN disconnection procedure is triggered. It is also related to the case when the UE has no PDN connection(s) established via a Fixed Broadband access network. + +The UE can initiate the Detach procedure, e.g. when the UE is power off. The ePDG may initiate the Detach procedure due to administration reason or the IKEv2 tunnel releasing. + +As part of the Detach procedure for multiple PDN connectivity, steps 1 to 3 of this procedure shall be repeated for each PDN connected. + +This procedure terminates both the IP-CAN session and the Gateway Control Session(s) over S9a between the BPCF and the PCRF. + +![Sequence diagram of UE/ePDG-initiated detach procedure or UE-requested PDN disconnection procedure. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BPCF, AAA Proxy), ePDG, PDN GW, and Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF, TDF). The process starts with a PDN disconnection procedure (Step 1) involving IKEv2 and PMIP or GTP tunnels. Subsequent steps involve Gateway Control Session Termination (Step 2), Gateway Control and QoS Rules Provision or PCRF-Initiated Gateway Control Session Termination (Step 3), Fixed Broadband Access specific resource release (Step 4), Indication of IP-CAN session termination (Step 5), and TDF session termination for offloaded traffic (Step 6).](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +Sequence diagram of UE/ePDG-initiated detach procedure or UE-requested PDN disconnection procedure. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BPCF, AAA Proxy), ePDG, PDN GW, and Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF, TDF). The process starts with a PDN disconnection procedure (Step 1) involving IKEv2 and PMIP or GTP tunnels. Subsequent steps involve Gateway Control Session Termination (Step 2), Gateway Control and QoS Rules Provision or PCRF-Initiated Gateway Control Session Termination (Step 3), Fixed Broadband Access specific resource release (Step 4), Indication of IP-CAN session termination (Step 5), and TDF session termination for offloaded traffic (Step 6). + +**Figure 7.3-1: UE/ePDG-initiated detach procedure or UE-requested PDN disconnection procedure** + +NOTE 1: In the roaming case, the Step 2 terminates at the V-PCRF. + +If dynamic policy provisioning over S9a is not deployed, the optional steps 2, 3, 5 and 6 do not occur. Instead, the Fixed Broadband Access network may employ Fixed Broadband Access local policies. + +1. The description of the IKEv2 tunnel and the PMIPv6 or GTPv2 tunnel releasing procedure is same as TS 23 402 [3], clause 7.4.1.1 or 7.4.3.1. + +The steps in 2 and 3 describe PCC signalling to remove policies for EPC routed traffic. + +2. Triggered by the IKEv2 tunnel releasing in step 1, the ePDG executes Gateway Control Session termination procedure with the PCRF as specified in TS 23.203 [4]. This step is only applicable when S2b PMIPv6 is used. +3. Triggered by the Gateway Control Session termination received from ePDG or by the IP-CAN session termination over Gx, the PCRF (for non-roaming case) and the V-PCRF (for home routed and visited access roaming case for S2b-PMIP) and the H-PCRF (for home routed and visited access roaming case for S2b-GTPv2) executes a Gateway Control and QoS Rules Provision procedure with the BPCF or, if this is the last PDN Connection for the UE, a PCRF-Initiated Gateway Control Session Termination Procedure with the BPCF would be performed as specified in TS 23.203 [4]. This step is applicable when either S2b based PMIPv6 or GTPv2 are used. +4. Fixed Broadband Access specific resource release procedure may be executed, as defined by Fixed Broadband Access Policy Framework specifications BBF TR-134 [11] and BBF TR-203 [6]. This step is out of the scope of 3GPP. + +The steps in 5 and 6 describe PCC signalling to remove policies for NS-WLAN offloaded traffic. Step 5 may be triggered by the notification to the BPCF that the IMSI is not authenticated any longer (e.g. re-authentication time out) and/or the UE local IP address was released using Fixed Broadband Access procedures. + +5. The BPCF sends an indication of IP-CAN session termination to the PCRF as described in TS 23.203 [4]. +6. Triggered by previous step, the PCRF (for non-roaming case) and the V-PCRF (for roaming cases) terminates the TDF session for the UE local IP address (if applicable). + +## 7.4 HSS/AAA-initiated Detach Procedure + +This procedure is applicable if the UE accesses a Fixed Broadband Access network with GTPv2 or PMIPv6 based S2b interface. And the HSS initiates the detach procedure e.g. when the user's subscription is removed. The 3GPP AAA Server can initiate the procedure, e.g. instruction from O&M, timer for re-authentication/re-authorization expired. + +![Sequence diagram of the HSS/AAA-initiated detach procedure. The diagram shows the interaction between UE, Fixed Broadband Access, ePDG, PDN GW, 3GPP AAA Proxy, vPCRF, hPCRF, and HSS/AAA. Step 1: HSS/AAA sends a '1. Detach Indication' to the ePDG. Step 2: A block labeled '2. The procedures as Figure 7.3-1' indicates the main procedure. Step 3: The ePDG sends a '3. Detach Ack' back to the HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes the 3GPP AAA Proxy, vPCRF, and hPCRF.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +Sequence diagram of the HSS/AAA-initiated detach procedure. The diagram shows the interaction between UE, Fixed Broadband Access, ePDG, PDN GW, 3GPP AAA Proxy, vPCRF, hPCRF, and HSS/AAA. Step 1: HSS/AAA sends a '1. Detach Indication' to the ePDG. Step 2: A block labeled '2. The procedures as Figure 7.3-1' indicates the main procedure. Step 3: The ePDG sends a '3. Detach Ack' back to the HSS/AAA. A shaded area labeled 'Roaming Scenarios' includes the 3GPP AAA Proxy, vPCRF, and hPCRF. + +Figure 7.4-1: HSS/AAA-initiated detach procedure + +For connectivity to multiple PDNs, Step 2 shall be repeated for each PDN the UE is connected to. Step 2 can occur in parallel for each PDN. + +1. The description of this step is the same as for step 1 in TS 23 402 [3], clause 7.4.2.1. +2. This description of the detach procedure is same as clause 7.3. +3. The description of this step is the same as for step 3 in TS 23 402 [3], clause 7.4.2.1. + +NOTE: The HSS/AAA may also send a detach indication message to the PDN GW. The PDN GW does not remove the PMIPv6 or GTPv2 tunnels on S2b, since the ePDG is responsible for removing the PMIPv6 or GTPv2 tunnels on S2b. The PDN GW acknowledges the receipt of the detach indication message to the HSS/AAA. + +## 7.5 UE-initiated Connectivity to Additional PDN + +This clause is related to the case when the UE has an established PDN connection via a Fixed Broadband Access Network using GTPv2 or PMIPv6 based S2b and wishes to establish one or more additional PDN connections over the same access. Since GTPv2 or PMIPv6 is used to establish connectivity with the additional PDN, the UE shall establish a separate SWu instance (i.e. a separate IPSec tunnel) for each additional PDN. + +The description of supporting additional PDN connections with PMIPv6 based S2b is same as it is specified in TS 23 402 [3], clause 7.6.1. The description of supporting additional PDN connections with GTPv2 based S2b is same as it is specified in TS 23 402 [3], clause 7.6.3. + +![Sequence diagram showing UE-initiated connectivity to additional PDN over a Fixed Broadband Access Network. The diagram shows four entities: UE, ePDG, PDN GW1, and PDN GW2. Step 1 is 'Initial S2b Attach as in Fig 7.2-1' from UE to PDN GW1. Step 2 is 'S2b Attach to additional PDNs as in Figure . 7.2-1' from UE to PDN GW2.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +``` + +sequenceDiagram + participant UE + participant ePDG + participant PDN_GW1 as PDN GW1 + participant PDN_GW2 as PDN GW2 + Note left of UE: 1. Initial S2b Attach as in Fig 7.2-1 + UE->>PDN_GW1: + Note left of UE: 2. S2b Attach to additional PDNs as in Figure . 7.2-1 + UE->>PDN_GW2: + +``` + +Sequence diagram showing UE-initiated connectivity to additional PDN over a Fixed Broadband Access Network. The diagram shows four entities: UE, ePDG, PDN GW1, and PDN GW2. Step 1 is 'Initial S2b Attach as in Fig 7.2-1' from UE to PDN GW1. Step 2 is 'S2b Attach to additional PDNs as in Figure . 7.2-1' from UE to PDN GW2. + +**Figure 7.5-1: UE-initiated connectivity to additional PDN over a Fixed Broadband Access Network** + +1. The UE has performed the Initial S2b Attach procedure as defined in clause 7.2 and has an established PDN connection. +2. The UE repeats the procedure of clause 7.2, steps 6-9 for each additional PDN the UE wants to connect to, with the following exceptions: + - The IKEv2 tunnel establishment procedure for each additional PDN connection is initiated with the ePDG that was selected in step 1 in clause 7.2. + - For network supporting multiple mobility protocols, if there was any dynamic IPMS decision in step 1 in clause 7.2, the AAA/HSS enforces the same IPMS decision for each additional PDN connection. + - In Step 8, if no Gateway Control session over S9a for this UE, then the PCRF initiates the Gateway Control Session Establishment procedure with the BPCF. Otherwise, the PCRF provide new QoS rules corresponding to the new PDN connection to the BPCF using the Gateway Control and QoS Rules Provisioning procedure. + +## 7.6 Network-Initiated Dynamic PCC for EPC-routed Traffic + +This procedure is applicable if the UE accesses via a Fixed Broadband Access network with GTPv2 or PMIPv6 based S2b interface for the EPC-routed traffic. And if dynamic PCC is deployed, the procedure given in Figure 7.6-1 is used by the PCRF to provision rules to the Fixed Broadband Access and for the Fixed Broadband Access to enforce the policy by controlling the resources and configuration in the access. This procedure is applicable only when the UE is already attached the Fixed Broadband Access network access and the PCRF is capable to discover the BPCF for the Fixed Broadband Access serving the UE. The access specific procedure executed in the Fixed Broadband Access is out of scope of this specification. In case 2b, defined in clause 7.1 of TS 23.203 [4] when UE connecting via Fixed Broadband Access access no QoS Rules should be provisioned to the ePDG. + +![Sequence diagram of Network-initiated dynamic policy control procedure. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, AAA proxy, BPCF), ePDG, PDN GW, Roaming Scenarios (3GPP AAA Proxy, VPCRF, HPCRF), and HSS/AAA. The UE connects to the Fixed Broadband Access Network via an IPsec Tunnel. The Fixed Broadband Access Network connects to the ePDG via a GTP or PMIP tunnel. The ePDG connects to the PDN GW. The PDN GW connects to the Roaming Scenarios. The Roaming Scenarios connect to the HSS/AAA. The sequence of messages is: 1. Gateway Control and QoS Rules provision procedure (from BPCF to PDN GW); 2. Access specific mechanism for admission control, etc (within Fixed Broadband Access Network); 3. IP-CAN Session Modification (from PDN GW to BPCF); 4. The Dedicated bearer activation/deactivation/update procedure with GTP based S2b is specified in TS 23.402, figure 7.9.2-1, 7.10-1, 7.11.1-1 (from PDN GW to BPCF); 5. IP-CAN Session Modification (from PDN GW to BPCF).](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +Sequence diagram of Network-initiated dynamic policy control procedure. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, AAA proxy, BPCF), ePDG, PDN GW, Roaming Scenarios (3GPP AAA Proxy, VPCRF, HPCRF), and HSS/AAA. The UE connects to the Fixed Broadband Access Network via an IPsec Tunnel. The Fixed Broadband Access Network connects to the ePDG via a GTP or PMIP tunnel. The ePDG connects to the PDN GW. The PDN GW connects to the Roaming Scenarios. The Roaming Scenarios connect to the HSS/AAA. The sequence of messages is: 1. Gateway Control and QoS Rules provision procedure (from BPCF to PDN GW); 2. Access specific mechanism for admission control, etc (within Fixed Broadband Access Network); 3. IP-CAN Session Modification (from PDN GW to BPCF); 4. The Dedicated bearer activation/deactivation/update procedure with GTP based S2b is specified in TS 23.402, figure 7.9.2-1, 7.10-1, 7.11.1-1 (from PDN GW to BPCF); 5. IP-CAN Session Modification (from PDN GW to BPCF). + +**Figure 7.6-1: Network-initiated dynamic policy control procedure** + +If dynamic policy provisioning over S9a is not deployed, the optional step 1 does not occur. Instead, the Fixed Broadband Access network may employ Fixed Broadband Access local policies. + +1. The PCRF (for non-roaming case) and the V-PCRF (for home routed and visited access roaming case) initiates the Gateway Control and QoS Rules Provision Procedure with the BPCF over S9a as specified in TS 23.203 [4]. In roaming scenario, the H-PCRF will initiate the procedure over S9 towards the V-PCRF and the V-PCRF in turns initiates the procedure over S9a towards the BPCF. +2. The Fixed Broadband Access Network performs admission control based on the QoS rules provisioned to it, and establishes all necessary resources and configuration in the Fixed Broadband Access network. The details of this step are out of the scope of this specification. +3. The PCRF sends PCC Rules to the PDN GW. This corresponds to the initial steps of the PCRF-Initiated IP-CAN Session Modification procedure as defined in TS 23.203 [4]. +4. The step only available when GTP S2b is used. P-GW initiates GTP bearer activation/deactivation/update procedure as defined in TS 23.402, figure 7.9.2-1, 7.10-1, 7.11.1-1. +5. If the dynamic policy control procedure was triggered by a PCC Rules Provision message from the PCRF, the PDN GW replies with a provisioning acknowledgement message to the PCRF and later informs the PCRF whether the requested PCC Rules could be enforced after the completion of IP CAN bearer signalling. + +## 7.7 Network-Initiated Dynamic PCC for NS-WLAN offloaded traffic + +This procedure is applicable if the UE accesses via a Fixed Broadband Access network, traffic is offloaded by the BNG where dynamic PCC is deployed. The purpose of the procedures is to provision PCC Rules over S9a for offloaded traffic in the Fixed Broadband Access. The Fixed Broadband Access is able to perform admission control and to provision policy rules in the BNG for the purpose to identify traffic based on the UE's local IP address in order to enforce QoS. + +![Sequence diagram for Figure 7.7-1: Network-initiated dynamic policy control procedure for offloaded traffic.](8269648391c59363ea61243864a2adf7_img.jpg) + +``` + + sequenceDiagram + participant UE + subgraph Fixed Broadband Access Network + RG + BNG + AAA_proxy[AAA proxy] + BPCF + end + participant ePDG + participant PDN_GW[PDN GW] + subgraph Roaming Scenarios + AAA_Proxy_3GPP[3GPP AAA Proxy] + vPCRF + hPCRF + end + participant AF_TDF[AF/TDF] + + Note over AF_TDF: 1a. AF Session signalling + Note over BPCF, hPCRF: 1b. Session Information sent over S9a + Note over AF_TDF: 1c. TDF Session signalling + Note over vPCRF, hPCRF: 2. PCRF generates QoS Rules for the offloaded traffic based on the service information provided in step 1 + Note over BPCF, vPCRF: 3. PCRF-init IP-CAN session modification + Note over RG, BPCF: 4. Access specific mechanism for admission control, translation into relevant QoS parameters + +``` + +Sequence diagram for Figure 7.7-1: Network-initiated dynamic policy control procedure for offloaded traffic. + +**Figure 7.7-1: Network-initiated dynamic policy control procedure for offloaded traffic** + +- This procedure only applies if dynamic policy provisioning over S9a is deployed. Steps 1a, 1b and 1c are corresponding to architecture scenarios A, B and C and all of them are optional. + - 1a. For variant A, the service information is received by PCRF (non-roaming case) or H-PCRF(roaming case) over Rx interface. + - 1b. For variant B, service information for a 3GPP UE identified by the UE's local IP address or the IMSI is received by BPCF which will then send it over S9a to the PCRF (non-roaming case), or to V-PCRF and the V-PCRF in turns forward them to the H-PCRF(roaming case). + - 1c. For variant C, the service information is received by the PCRF (non-roaming case) or V-PCRF (roaming case) over Sd interface. +- PCRF generates PCC Rules for the offloaded traffic based on the service information provided in step 1. +- Triggered by step 2. The PCRF (for non-roaming case) and the V-PCRF (for roaming case) initiates the PCRF-initiated IP-CAN session modification procedure with the BPCF over S9a to provision PCC Rules for the UE's local IP address. In roaming scenario, the H-PCRF will initiate the procedure over S9 towards the V-PCRF which in turns initiates the procedure over S9a towards the BPCF. +- The Fixed Broadband Access Network performs admission control based on the provisioned PCC Rules, and establishes all necessary resources and configuration in the Fixed Broadband Access network. The details of this step are out of the scope of this specification. + +## 7.8 PDN GW initiated Resource Allocation Deactivation + +This procedure is applicable if the UE accesses a Fixed Broadband Access network with GTPv2 or PMIPv6 based S2b interface. And the PDN GW initiated the resource releasing procedure, for example, due to IP-CAN session modification requests from the PCRF or due to handover from Fixed Broadband Access network to 3GPP. When it is performed due to a handover, the connections associated with the PDN address are released, but the PDN address is kept in the PDN GW. + +![Sequence diagram for PDN GW Initiated Bearer Deactivation. The diagram shows interactions between UE, RG, BNG, BPCF, AAA Proxy, ePDG, PDN GW, AAA Proxv, vPCRF, and hPCRF. The process is divided into four steps: 1. PDN GW initiated Bearer Deactivation procedure; 2. Gateway Control Session Termination (optional); 3. Gateway Control and QoS Rules Provision procedure or PCRF-Initiated Gateway Control Session Termination Procedure (optional); 4. Access specific mechanism to release resources. A 'Fixed Broadband Access Network' box contains UE, RG, BNG, BPCF, and AAA Proxy. A 'Roaming Scenarios' box contains AAA Proxv, vPCRF, and hPCRF. Step 2 is shown as a dashed box with a circle, indicating it's optional and may occur at different points in the sequence.](32ff77da4286b58c4778033acaa10836_img.jpg) + +Sequence diagram for PDN GW Initiated Bearer Deactivation. The diagram shows interactions between UE, RG, BNG, BPCF, AAA Proxy, ePDG, PDN GW, AAA Proxv, vPCRF, and hPCRF. The process is divided into four steps: 1. PDN GW initiated Bearer Deactivation procedure; 2. Gateway Control Session Termination (optional); 3. Gateway Control and QoS Rules Provision procedure or PCRF-Initiated Gateway Control Session Termination Procedure (optional); 4. Access specific mechanism to release resources. A 'Fixed Broadband Access Network' box contains UE, RG, BNG, BPCF, and AAA Proxy. A 'Roaming Scenarios' box contains AAA Proxv, vPCRF, and hPCRF. Step 2 is shown as a dashed box with a circle, indicating it's optional and may occur at different points in the sequence. + +**Figure 7.8-1: PDN GW Initiated Bearer Deactivation** + +NOTE 1: In the roaming case, the Step 2 terminates at the V-PCRF. + +If dynamic policy provisioning over S9a is not deployed, the optional steps 2 and 3 do not occur. Instead, the Fixed Broadband Access network may employ Fixed Broadband Access local policies. + +Step 2 is only applicable when S2b PMIPv6 is used. + +1. The description of the step is the same as it is in TS 23 402 [3], clause 7.9.1 or 7.9.2 with following exceptions: + - The step 4 in clause 7.9.1 or step 3b in clause 7.9.2 is not executed. +2. Triggered by the IPSec tunnel termination, the ePDG terminates the Gxb\* session. This step is only applicable when S2b PMIPv6 is used and Gxb\* was used to trigger initiation of the S9a session from PCRF. This step may occur at any time. + +NOTE 2: Step 2 may occur before or after steps 3-5. Step 2 does not trigger step 3. + +3. Triggered by step 1, the PCRF (for non-roaming case) and the V-PCRF (for the home routed and visited access roaming case) executes a Gateway Control and QoS Rules Provision procedure or, if this is the last PDN Connection for the UE over Fixed Broadband Access, a PCRF-Initiated Gateway Control Session Termination Procedure with the BPCF. In roaming scenario, for the case when GTP is used on S2b, the H-PCRF will initiate the procedure over S9 towards the V-PCRF and the V-PCRF in turns initiates the procedure over S9a towards the BPCF. +4. The resources may be released in the Fixed Broadband Access, according to an access specific release mechanism. The details of this step are out of the scope of this specification. + +## 7.9 Handover from 3GPP Access to Fixed Broadband Access with GTP or PMIPv6 on S2b + +This clause shows the combined call flow for a handover from 3GPP Access with GTPv2 or PMIPv6 based S5/S8 interface to a Fixed Broadband Access network via GTPv2 or PMIPv6 based S2b interface. In addition, the procedures + +for the IP session establishment for NS-WLAN offload using the Fixed Broadband Access network are also integrated into the combined procedures. + +![Sequence diagram titled 'Handover from 3GPP Access to Fixed Broadband Access'. It shows interactions between UE, Fixed Broadband Access Network (RG, BNG, AAA proxy, BPCF, ePDG), Serving GW, PDN GW, and Roaming Scenarios (3GPP AAA Proxy, VPCRF, hPCRF, HSS/AAA, TDF). The sequence includes: 1. Radio bearer and S1 bearer (highlighted in yellow), 2. UE discovers BBF Access and initiates HO, 3. 3GPP-based access authentication (EAP-AKA), 4. Local IP address assignment, 5. IP-CAN Session establishment, 6. PDN connection setup and Gateway Control Session establishment, 7. Policy interaction, 8. UE-initiated Connectivity to Additional PDN, 9. 3GPP EPS Bearer release.](f142b022cfc716cd967297f027efe647_img.jpg) + +Sequence diagram titled 'Handover from 3GPP Access to Fixed Broadband Access'. It shows interactions between UE, Fixed Broadband Access Network (RG, BNG, AAA proxy, BPCF, ePDG), Serving GW, PDN GW, and Roaming Scenarios (3GPP AAA Proxy, VPCRF, hPCRF, HSS/AAA, TDF). The sequence includes: 1. Radio bearer and S1 bearer (highlighted in yellow), 2. UE discovers BBF Access and initiates HO, 3. 3GPP-based access authentication (EAP-AKA), 4. Local IP address assignment, 5. IP-CAN Session establishment, 6. PDN connection setup and Gateway Control Session establishment, 7. Policy interaction, 8. UE-initiated Connectivity to Additional PDN, 9. 3GPP EPS Bearer release. + +**Figure 7.9-1: Handover from 3GPP Access to Fixed Broadband Access** + +If dynamic policy provisioning over S9a is not deployed, the optional steps 5, 7 and 8 do not occur. Instead, the Fixed Broadband Access network may employ local policies. + +For connectivity to multiple PDNs, step 8 shall be repeated for each PDN the UE is connected to. Step 8 can occur in parallel for each PDN. Other impacts related to the handover for multiple PDNs are described in TS 23 402 [3] clause 8.1. + +Handover is only applicable to the EPC-routed PDN connections. For the NS-WLAN offloaded traffic, a new IP session in fixed broadband access network will be established. + +- 1-2. The description of these steps are is same as for steps 1-2 in TS 23 402 [3], clause 8.2.3. +- 3-4. The description of these steps is the same as for steps 1-2 in Figure 7.2-1. +- 5. This step describes PCC signalling to provision policies for offloaded traffic and are only triggered when the BPCF receives the IMSI and the allocated UE local IP address using Fixed Broadband Access procedures. The description of this step is the same as for steps 3-5 in Figure 7.2-1. +- 6. The description of PDN Connection setup and Gateway Control Session setup is the same as for steps 3-5 in Figure 7.2-1 with following additions: + - Step 3 in Figure 7.2-1 is mandatory when performing handover from E-UTRAN to Fixed Broadband Access. + - If the UE supports IP address preservation during the handover, the UE shall include its address (IPv4 address or IPv6 prefix /address or both) allocated when it's attached to 3GPP Access into the CFG\_Request sent to the ePDG during IKEv2 message exchange. The ePDG shall include the received UE address in the + +Create Session Request message or Proxy Binding Request message, and set the HO flag when sending to the PDN GW. + +- 7. The description of this step is the same as for step 6 in Figure 7.2-1. +- 8. For connectivity to multiple PDNs, the UE establishes connectivity to each PDN that is being transferred from 3GPP access, besides the PDN connection that was established in the steps 5-6, by executing the UE-initiated Connectivity to Additional PDN procedure specified in clause 7.5. +- 9. The description of this step is the same as for steps 11 in TS 23 402 [3], clause 8.2.3. + +## 7.10 Handover from Fixed broadband Access with GTP or PMIPv6 on S2b to 3GPP Access + +This clause shows the combined call flows for a handover from Fixed Broadband Access network via GTPv2 or PMIPv6 based S2b interface to a 3GPP Access (GERAN, UTRAN, E-UTRAN) with GTPv2 or PMIPv6 based S5/S8 interface. + +This clause contains the procedure steps that vary between the GTP and PMIP variant of S5 and S8 for the TAU with MME and Serving GW change procedure defined in TS 23.401 [2], clause 5.3.3.1 as well as Inter-eNodeB Handover with CN Node Relocation described in TS 23.401 [2], clause 5.5.1.2. + +![Sequence diagram for handover from Fixed Broadband Access to 3GPP Access. The diagram shows the interaction between UE, Fixed Broadband Access Network (RG, BNG, AAA proxy, BPCF), ePDG, Serving GW, PDN GW, 3GPP AAA Proxy, vPCRF, hPCRF, HSS/AAA, and TDF. The process is divided into three main steps: 1. GTP or PMIPv6 Tunnel(s) establishment, 2. Non-3GPP EPS Bearer Release, and 3. Release of NSWO resources in Fixed Broadband Access and termination of IP-CAN session for NSWO. A 'Roaming Scenarios' box highlights the 3GPP AAA Proxy, vPCRF, and hPCRF components.](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +Sequence diagram for handover from Fixed Broadband Access to 3GPP Access. The diagram shows the interaction between UE, Fixed Broadband Access Network (RG, BNG, AAA proxy, BPCF), ePDG, Serving GW, PDN GW, 3GPP AAA Proxy, vPCRF, hPCRF, HSS/AAA, and TDF. The process is divided into three main steps: 1. GTP or PMIPv6 Tunnel(s) establishment, 2. Non-3GPP EPS Bearer Release, and 3. Release of NSWO resources in Fixed Broadband Access and termination of IP-CAN session for NSWO. A 'Roaming Scenarios' box highlights the 3GPP AAA Proxy, vPCRF, and hPCRF components. + +Figure 7.10-1: Handover from Fixed Broadband Access to 3GPP Access + +For connectivity to multiple PDNs the same behaviour as described in clause 8.2.1.1 also applies to this procedure. + +- 1. The UE uses Fixed broadband Access and is being served by PDN GW. + - A. This step is the same as defined in TS 23 402, clause: + - 8.2.1.1, step 2 to 17 for HO from PMIPv6 on S2b to E-UTRAN with GTP on S5/S8 + - 8.2.1.2, step 2 to 18 for HO from PMIPv6 on S2b to E-UTRAN with PMIPv6 on S5/S8 + - 8.2.1.3, step 2 to 16 for HO from PMIPv6 on S2b to UTRAN/GERAN with GTP-based S5/S8 + - 8.2.1.4, step 2 to 18 for HO from PMIPv6 on S2b to UTRAN/GERAN with PMIPv6 on S5/S8 + - 8.6.1.1, steps in (C) for HO from GTP on S2b to E-UTRAN with GTP on S5/S8 + - 8.6.1.2, steps in (D) for HO from GTP on S2b to UTRAN/GERAN with GTP on S5/S8 +- 2. The PDN GW shall initiate resource allocation deactivation procedure in the Fixed Broadband Access as defined in clause 7.7 +- 3. If the NS-WLAN offloaded connection is released (e.g. if the UE moves out of WLAN coverage), the Fixed Broadband Access executes the access specific resource release procedure and initiates termination of the IP-CAN session for NS-WLAN offloaded traffic as described in steps 4-6 in clause 7.3 + +## 7.11 IPSec tunnel modified + +This clause is related to the case where the IPSec tunnel between the UE and the ePDG has been modified due to the UE initiated IPSec tunnel update procedure, or the UE local IP address updating. The IPSec tunnel modification procedure is assumed that GTP based or PMIPv6 based S2b is used. This procedure is only applicable if MOBIKE is supported by the UE. + +![Sequence diagram titled 'IPSec tunnel modified' showing the interaction between UE, BBF Access Network (RG, BNG, BBF AAA proxy, BPCF), ePDG, PDN GW, vPCRF, hPCRF, and HSS/AAA. The diagram illustrates the steps for updating an IPSec tunnel, including MOBIKE address updates and optional Gateway Control and QoS Rules provision procedures (A and B).](69e5f1993021af230d08c08aac97d9df_img.jpg) + +The diagram illustrates the sequence of messages for an IPSec tunnel modification. It starts with the UE sending a '2. UE local IP address re-assignment' message to the ePDG. The ePDG then sends a '3. MOBIKE update address' message to the UE. The diagram is divided into two main sections: (A) and (B). Section (A) shows the 'Gateway Control and QoS Rules update procedure' and 'Gateway Control and QoS Rules provision procedure' between the ePDG and the PCRF (vPCRF or hPCRF). Section (B) shows the 'Modify Bearer Request' and 'Modify Bearer Response' between the ePDG and the PDN GW, followed by the 'Gateway Control and QoS Rules provision procedure' between the PDN GW and the PCRF. The final state shows the UE with a new local IP address and the ePDG with an updated IPSec tunnel. + +Sequence diagram titled 'IPSec tunnel modified' showing the interaction between UE, BBF Access Network (RG, BNG, BBF AAA proxy, BPCF), ePDG, PDN GW, vPCRF, hPCRF, and HSS/AAA. The diagram illustrates the steps for updating an IPSec tunnel, including MOBIKE address updates and optional Gateway Control and QoS Rules provision procedures (A and B). + +Figure 7.11-1: IPSec tunnel modified + +If dynamic policy provisioning over S9a is not deployed, the optional step A2 and B4 do not occur. Instead, the Fixed Broadband Access network may employ Fixed Broadband Access local policies. + +1. UE attaches to EPC from BBF access network via ePDG, as described in figure 7.2-1. The IPSec tunnel is established between ePDG and UE; the PMIPv6 or GTP tunnel is established between the PDN GW and ePDG + 2. The BBF Access Network may assign a new local IP address to the UE. + 3. UE initiated IPSec tunnel update procedure, which may be as a result of UE IP address for IPSec tunnel expired or released. MOBIKE update address message exchanges. And optionally, MOBIKE address verification, initiated by ePDG, is send to UE as described in MOBIKE [18]. +- A. These steps are only applicable when S2b PMIPv6 is used. +- A.1. The ePDG initiates Gxb\* session modification with the PCRF. The ePDG includes the UE local IP address and optionally the UDP source port number (if NAT is detected) in the message to the PCRF. + - A.2. Triggered by step A.1, the PCRF (for non-roaming case) and the V-PCRF (for home routed and visited access roaming case) initiates the Gateway Control and QoS Rules Provision Procedure with the BPCF over S9a as specified in TS 23.203 [4]. +- B. These steps are only applicable when S2b GTP is used. +- B.1. The ePDG sends Modify bearer request message with the UE local IP address and optionally the UDP source port number (if NAT is detected) to P-GW. + +- B2. The PCEF initiated IP-CAN session modification procedure is triggered. +- B3. The P-GW responds with Modify Bearer Response message to the ePDG. +- B4. Triggered by the PCC Rule provisioning to the PCEF, the PCRF (for non-roaming case) and the V-PCRF (for the home routed and visited access roaming case) initiates the Gateway Control and QoS Rules Provision Procedure with the BPCF over S9a as specified in TS 23.203 [4]. In roaming scenario, the H-PCRF will initiate the procedure over S9 towards the V-PCRF and the V-PCRF in turns initiates the procedure over S9a towards the BPCF. + +# --- 8 Functional Description and Procedures for Fixed Broadband Access network over S2c + +## 8.1 Introduction + +The description for the PCC procedures applicable for S2c untrusted and trusted scenarios including the NS-WLAN offloaded traffic. The IP session for the UE in Fixed Broadband Access is handled as an IP-CAN session by the PCRF. For EPC-routed traffic, the IP-CAN session for the PDN Connection in the PDN GW is created via Gx procedures. In addition a Gateway Control Session is established between the BPCF and the PCRF corresponding to the EPC-routed IP-CAN session in the PCRF. + +NOTE: It is up to stage 3 to optimize S9a procedures for Non-Seamless WLAN offloaded traffic and EPC routed traffic handled by the same PCRF. + +The home routed roaming, LBO and non-roaming scenarios are depicted in the figure. + +- In the LBO case, the 3GPP AAA Proxy acts as an intermediary, forwarding messages from the 3GPP AAA Server in the HPLMN to the PDN GW in the VPLMN and vice versa. Messages between the PDN GW in the VPLMN and the hPCRF in the HPLMN are forwarded by the vPCRF in the VPLMN. +- In the non-roaming case, the vPCRF and the 3GPP AAA Proxy are not involved. + +## 8.2 Procedures for trusted Fixed Broadband Access network over S2c + +### 8.2.1 Initial Attach with DSMIPv6 on S2c to trusted Fixed Broadband Access + +This clause specifies the additional procedures at the UE's initial attachment to a Fixed Broadband Access which is considered a trusted access to EPC, for the UE to establish the first PDN connection over the Fixed Broadband Access with S2c, and/or for the UE to have offloaded traffic via Fixed Broadband Access. + +This procedure establishes a session between the BPCF and the PCRF to provision policy decisions for NS-WLAN offloaded traffic and/or to provision policy decisions for EPC routed traffic. + +![Sequence diagram for Initial attachment with DSMIPv6 when S2c is used for roaming, non-roaming and LBO. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BBF AAA proxy, BPCF), PDN GW, Roaming Scenarios (vPCRF, 3GPP AAA Proxy, hPCRF), HSS/AAA, and TDF. Steps include 3GPP-based access authentication, local IP address assignment, trigger, indication of IP-CAN session establishment, TDF session establishment, PDN connection setup, PCRF initiated Gateway Control Session Establishment, and policy interaction.](8d66c9c295023a1380f9986d3663bb1e_img.jpg) + +``` + +sequenceDiagram + participant UE + subgraph Fixed Broadband Access Network + RG + BNG + BBF AAA proxy + BPCF + end + participant PDN GW + subgraph Roaming Scenarios + vPCRF + 3GPP AAA Proxy + hPCRF + end + participant HSS AAA + participant TDF + + Note left of UE: 1. 3GPP-based access authentication (EAP-AKA) as specified in TS 23.402 + UE->>HSS AAA: 1. 3GPP-based access authentication (EAP-AKA) as specified in TS 23.402 + HSS AAA-->>UE: 1. 3GPP-based access authentication (EAP-AKA) as specified in TS 23.402 + Note left of UE: 2. Local IP address assignment + UE->>BNG: 2. Local IP address assignment + BNG-->>UE: 2. Local IP address assignment + Note left of BNG: 3. Trigger + BNG->>BPCF: 3. Trigger + BPCF-->>BNG: 3. Trigger + Note left of BPCF: 4. Indication of IP-CAN session Establishment + BPCF->>PDN GW: 4. Indication of IP-CAN session Establishment + PDN GW-->>BPCF: 4. Indication of IP-CAN session Establishment + Note left of PDN GW: 5. TDF session establishment (for NS-WLAN offloaded traffic) + PDN GW->>TDF: 5. TDF session establishment (for NS-WLAN offloaded traffic) + TDF-->>PDN GW: 5. TDF session establishment (for NS-WLAN offloaded traffic) + Note left of PDN GW: 6. PDN connection setup as specified in TS 23.402, Figure 6.3-1 steps 4-7 + PDN GW->>HSS AAA: 6. PDN connection setup as specified in TS 23.402, Figure 6.3-1 steps 4-7 + HSS AAA-->>PDN GW: 6. PDN connection setup as specified in TS 23.402, Figure 6.3-1 steps 4-7 + Note left of PDN GW: 7. PCRF initiated Gateway Control Session Establishment + PDN GW->>vPCRF: 7. PCRF initiated Gateway Control Session Establishment + vPCRF-->>PDN GW: 7. PCRF initiated Gateway Control Session Establishment + Note left of vPCRF: 8. policy interaction + vPCRF->>BPCF: 8. policy interaction + BPCF-->>vPCRF: 8. policy interaction + +``` + +Sequence diagram for Initial attachment with DSMIPv6 when S2c is used for roaming, non-roaming and LBO. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BBF AAA proxy, BPCF), PDN GW, Roaming Scenarios (vPCRF, 3GPP AAA Proxy, hPCRF), HSS/AAA, and TDF. Steps include 3GPP-based access authentication, local IP address assignment, trigger, indication of IP-CAN session establishment, TDF session establishment, PDN connection setup, PCRF initiated Gateway Control Session Establishment, and policy interaction. + +**Figure 8.2.1-1: Initial attachment with DSMIPv6 when S2c is used for roaming, non-roaming and LBO** + +If dynamic policy provisioning over S9a is not deployed, the optional steps 3, 4, 5, 7 and 8 do not occur. Instead, the Fixed Broadband Access Network may employ local policies. + +1. The description of this step is the same as clause 7.2, step 1. +2. The description of this step is the same as clause 7.2 step 2. The UE local IP address is used as CoA in S2c signalling. + +The steps in 3, 4 and 5 describe PCC Signalling for NS-WLAN offloaded traffic, the triggered is described in clause 7.2. + +3. The description of this step is the same as step 3 in clause 7.2. +4. This description of this step is the same as step 4 in clause 7.2. +5. This description of this step is the same as step 5 in clause 7.2. +6. The description of this step is the same as for steps 4-7 in TS 23 402 [3], clause 6.3, with the following information: The UE local IP address (i.e. CoA) and optionally UDP source port number of the DSMIPv6 binding update signalling (if NAT is detected) are forwarded to the PCRF in step 6 of TS 23 402 [3], clause 6.3 (i.e. IP-CAN session establishment procedure). + +The step in 7 PCC signalling to provision policies for EPC routed traffic. + +7. The description of this step is the same as step 8 in clause 7.2 for GTP case. The UE local IP address is used as CoA in S2c signalling. +8. The description of this step is the same as step 9 in clause 7.2. + +### 8.2.2 UE-initiated Detach Procedure and UE-Requested PDN Disconnection with DSMIPv6 on S2c in trusted Fixed Broadband Access + +The procedure in this clause applies to UE-initiated detach procedures (e.g. triggered by power-off), and to the UE-requested PDN disconnection procedure. + +In the case when UE has multiple PDN connections, this detach procedure shall be repeated for each PDN connection. + +This clause also covers the termination of the IP-CAN session for UE's offloaded traffic initiated by the Fixed Broadband Access network. + +![Sequence diagram of UE-initiated detach procedure with DSMIPv6 on trusted s2c. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BPCF, BBF AAA Proxy), PDN GW, Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF, HSS/AAA, TDF), and TDF. The procedure consists of five steps: 1. UE-initiated PDN disconnection; 2. Gateway Control and QoS Rules Provision or PCRF-Initiated Gateway Control Session Termination; 3. Fixed Broadband resource release; 4. Indication of IP-CAN session termination; 5. TDF session termination (optional).](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +The diagram illustrates the sequence of messages for a UE-initiated detach procedure. The entities involved are: + +- UE**: User Equipment +- Fixed Broadband Access Network**: Contains RG (Residential Gateway), BNG (Broadband Network Gateway), BPCF (Broadband Policy Control Function), and BBF AAA Proxy. +- PDN GW**: PDN Gateway +- Roaming Scenarios**: Contains 3GPP AAA Proxy, vPCRF (Visited PCRF), hPCRF (Home PCRF), HSS/AAA, and TDF (Traffic Detection Function). + +The sequence of steps is: + +- 1- UE-initiated PDN disconnection procedure in Trusted Non-3GPP Access Network as specified in TS 23.402, figure 6.5.2-1 steps 1-4 and 6,**: Initiated by the UE. +- 2. Gateway Control and QoS Rules Provision procedure or PCRF-Initiated Gateway Control Session Termination Procedure**: Optional step between BPCF and vPCRF/hPCRF. +- 3. Fixed Broadband resource release procedure**: Occurs within the Fixed Broadband Access Network. +- 4. Indication of IP-CAN session termination procedure**: Optional step between BPCF and vPCRF/hPCRF. +- 5. TDF session termination procedure (offloaded traffic)**: Optional step between vPCRF/hPCRF and TDF. + +Sequence diagram of UE-initiated detach procedure with DSMIPv6 on trusted s2c. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BPCF, BBF AAA Proxy), PDN GW, Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF, HSS/AAA, TDF), and TDF. The procedure consists of five steps: 1. UE-initiated PDN disconnection; 2. Gateway Control and QoS Rules Provision or PCRF-Initiated Gateway Control Session Termination; 3. Fixed Broadband resource release; 4. Indication of IP-CAN session termination; 5. TDF session termination (optional). + +**Figure 8.2.2-1: UE-initiated detach procedure with DSMIPv6 on trusted s2c** + +If dynamic policy provisioning is not deployed, the optional steps 2, 4 and 5 do not occur. Instead, the Fixed Broadband Access network may employ local policies. + +1. The descriptions of these steps are the same as UE-initiated PDN disconnection procedure in trusted non-3GPP access network as specified in TS 23 402 [3], figure 6.5.2-1 steps 1-4 and 6. +2. Triggered by the IP-CAN session termination, if this is not the last PDN connection for the UE, the PCRF executes a Gateway Control and QoS Rules Provision procedure; otherwise, if this is the last PDN connection for the UE, a PCRF-Initiated Gateway Control Session Termination Procedure with the BPCF over S9a. +3. The description of this step is the same as clause 7.3 step 4. +4. The description of this step is the same as clause 7.3 step 5. +5. The description of this step is the same as clause 7.3 step 6. + +### **8.2.3 HSS-initiated Detach Procedure with DSMIPv6 on S2c in trusted Fixed Broadband Access** + +The procedure in this clause applies to Detach Procedures, initiated by HSS. + +![Sequence diagram for HSS-initiated detach procedure with DSMIPv6 on trusted s2c. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BPCF, BBF AAA Proxy), PDN GW, Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF), HSS/AAA, and TDF. The procedure consists of five steps: 1. AAA/HSS-initiated S2c detach procedure; 2. Gateway Control and QoS Rules Provision or PCRF-Initiated Gateway Control Session Termination; 3. Fixed Broadband resource release; 4. Indication of IP-CAN session termination; 5. TDF session termination (optional).](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +The diagram illustrates the HSS-initiated detach procedure with DSMIPv6 on trusted s2c. It features the following components and steps: + +- UE**: User Equipment. +- Fixed Broadband Access Network**: Contains **RG** (Residential Gateway), **BNG** (Broadband Network Gateway), **BPCF** (PDN Connectivity Function), and **BBF AAA Proxy**. +- PDN GW**: PDN Gateway. +- Roaming Scenarios**: Includes **3GPP AAA Proxy**, **vPCRF** (PDN Connectivity Function), and **hPCRF** (PDN Connectivity Function). +- HSS/AAA**: Home Subscriber Server / AAA server. +- TDF**: Traffic Detection Function (optional). + +The sequence of operations is as follows: + +- 1. AAA/HSS-initiated S2c detach procedure in Trusted Non-3GPP Access Network as specified in TS 23.402, figure 6.5.3-1 steps 1-5**: The process begins with the HSS/AAA initiating the detach procedure. +- 2. Gateway Control and QoS Rules Provision procedure or PCRF-Initiated Gateway Control Session Termination Procedure**: This is an optional step involving the vPCRF/hPCRF and BPCF. +- 3. Fixed Broadband resource release procedure**: The Fixed Broadband Access Network releases resources. +- 4. Indication of IP-CAN session termination procedure**: The BPCF indicates session termination to the vPCRF/hPCRF. +- 5. TDF session termination procedure (offloaded traffic)**: This is an optional step involving the TDF. + +Sequence diagram for HSS-initiated detach procedure with DSMIPv6 on trusted s2c. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BPCF, BBF AAA Proxy), PDN GW, Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF), HSS/AAA, and TDF. The procedure consists of five steps: 1. AAA/HSS-initiated S2c detach procedure; 2. Gateway Control and QoS Rules Provision or PCRF-Initiated Gateway Control Session Termination; 3. Fixed Broadband resource release; 4. Indication of IP-CAN session termination; 5. TDF session termination (optional). + +**Figure 8.2.3-1: HSS-initiated detach procedure with DSMIPv6 on trusted s2c** + +If dynamic policy provisioning over S9a is not deployed, the optional step 2, 4 and 5 do not occur. Instead, the Fixed Broadband Access network may employ Fixed Broadband Access local policies. + +1. The description of these steps are the same as for steps 1-5 in TS 23 402 [3], clause 6.5.3. +2. Triggered by the IP-CAN session termination, the PCRF executes a Gateway Control and QoS Rules Provision procedure or, if this is the last PDN Connection for the UE, a PCRF-Initiated Gateway Control Session Termination Procedure with the BPCF over S9a. +3. The description of this step is the same as clause 7.3 step 4. +4. The description of this step is the same as clause 7.3 step 5. +5. The description of this step is the same as clause 7.3 step 6. + +### 8.2.4 PDN GW-initiated PDN disconnection Procedure with DSMIPv6 on S2c in trusted Fixed Broadband Access + +The procedure in this clause applies to PDN disconnection procedure initiated by PDN GW. + +![Sequence diagram showing the PDN GW-initiated PDN disconnection procedure. Lifelines include UE, RG, BNG, BPCF, BBF AAA Proxy (grouped as Fixed Broadband Access Network), PDN GW, 3GPP AAA Proxy, vPCRF, hPCRF, HSS/AAA, and TDF (grouped as Roaming Scenarios). The procedure consists of five steps: 1. PDN GW-initiated PDN Disconnection Procedure in Trusted Non-3GPP Access Network; 2. Gateway Control and QoS Rules Provision procedure or PCRF-Initiated Gateway Control Session Termination Procedure; 3. Fixed Broadband resource release procedure; 4. Indication of IP-CAN session termination procedure; 5. TDF session termination procedure (offloaded traffic).](aeb2a26a07219661191294dba528067a_img.jpg) + +Sequence diagram showing the PDN GW-initiated PDN disconnection procedure. Lifelines include UE, RG, BNG, BPCF, BBF AAA Proxy (grouped as Fixed Broadband Access Network), PDN GW, 3GPP AAA Proxy, vPCRF, hPCRF, HSS/AAA, and TDF (grouped as Roaming Scenarios). The procedure consists of five steps: 1. PDN GW-initiated PDN Disconnection Procedure in Trusted Non-3GPP Access Network; 2. Gateway Control and QoS Rules Provision procedure or PCRF-Initiated Gateway Control Session Termination Procedure; 3. Fixed Broadband resource release procedure; 4. Indication of IP-CAN session termination procedure; 5. TDF session termination procedure (offloaded traffic). + +**Figure 8.2.4-1: PDN GW-initiated PDN disconnection procedure with DSMIPv6 on trusted S2c** + +If dynamic policy provisioning over S9a is not deployed, the optional step 2, 4 and 5 do not occur. Instead, the Fixed Broadband Access network may employ Fixed Broadband Access local policies. + +1. The description of these steps are the same as for steps 1-4 in TS 23 402 [3], clause 6.5.4. +2. Triggered by the IP-CAN session termination, the PCRF executes a Gateway Control and QoS Rules Provision procedure or, if this is the last PDN Connection for the UE, a PCRF-Initiated Gateway Control Session Termination Procedure with the BPCF over S9a. +3. The description of this step is the same as clause 7.3 step 4. +4. The description of this step is the same as clause 7.3 step 5. +5. The description of this step is the same as clause 7.3 step 6. + +### 8.2.5 E-UTRAN to Trusted Fixed Broadband Access Handover with DSMIPv6 on S2c + +This clause shows the combined call flow for a handover when a UE moves from an E-UTRAN to a trusted Fixed Broadband Access network. In addition, the procedures for the IP session establishment for NS-WLAN offload using the Fixed Broadband Access network are also integrated into the combined procedures. + +![Sequence diagram illustrating E-UTRAN to Trusted Fixed Broadband Access Handover with DSMIPv6 on s2c. The diagram shows the interaction between a UE, Fixed Broadband Access Network (RG, BNG, BBF AAA proxy, BPCF), MME, Serving GW, PDN GW, and Roaming Scenarios (3GPP AAA Proxy, VPCRF, hPCRF, HSS/AAA, TDF). The process involves 8 steps: 1. Radio bearer and S1 bearer establishment; 2. UE discovers BBF Access and initiates HO; 3. 3GPP-based access authentication (EAP-AKA); 4. Address assignment; 5. IP-CAN Session establishment; 6. PDN connection setup and Gateway Control Session establishment; 7. policy interaction; 8. 3GPP EPS Bearer release.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +The diagram is a sequence diagram titled "E-UTRAN to Trusted Fixed Broadband Access Handover with DSMIPv6 on s2c". It depicts the following components and steps: + +- UE**: User Equipment +- Fixed Broadband Access Network**: Contains **RG** (Residential Gateway), **BNG** (Broadband Network Gateway), **BBF AAA proxy**, and **BPCF** (Bandwidth Policy Control Function). +- MME**: Mobility Management Entity +- Serving GW**: Serving Gateway +- PDN GW**: PDN Gateway +- Roaming Scenarios**: Contains **3GPP AAA Proxy**, **VPCRF** (PDN Connectivity Function), **hPCRF** (Home PDN Connectivity Function), **HSS/AAA**, and **TDF** (Traffic Detection Function). + +The sequence of operations is as follows: + +- 1. Radio bearer and S1 bearer**: Initial connection between UE and MME. +- 2. UE discovers BBF Access and initiates HO**: UE sends a message to the MME to start the handover process. +- 3. 3GPP-based access authentication (EAP-AKA) as specified in TS 23.402**: Authentication between UE and the network. +- 4. Address assignment**: The network assigns an IP address to the UE. +- 5. IP-CAN Session establishment as specified in Figure 8.2.1-1, steps 3-5**: Establishment of an IP session between the UE and the PDN GW. +- 6. PDN connection setup and Gateway Control Session establishment as specified in figure 8.1.1-1, steps 3-4**: Setup of the PDN connection and control sessions. +- 7. policy interaction**: Policy interaction between the BPCF and the PDN GW. +- 8. 3GPP EPS Bearer release**: Release of the original 3GPP EPS bearer. + +Sequence diagram illustrating E-UTRAN to Trusted Fixed Broadband Access Handover with DSMIPv6 on s2c. The diagram shows the interaction between a UE, Fixed Broadband Access Network (RG, BNG, BBF AAA proxy, BPCF), MME, Serving GW, PDN GW, and Roaming Scenarios (3GPP AAA Proxy, VPCRF, hPCRF, HSS/AAA, TDF). The process involves 8 steps: 1. Radio bearer and S1 bearer establishment; 2. UE discovers BBF Access and initiates HO; 3. 3GPP-based access authentication (EAP-AKA); 4. Address assignment; 5. IP-CAN Session establishment; 6. PDN connection setup and Gateway Control Session establishment; 7. policy interaction; 8. 3GPP EPS Bearer release. + +**Figure 8.2.5-1: E-UTRAN to Trusted Fixed Broadband Access Handover with DSMIPv6 on s2c** + +Both the roaming and non-roaming scenarios are depicted in the figure. + +If dynamic policy provisioning over S9a is not deployed, the optional steps 5 and 7 do not occur. Instead, the Fixed Broadband Access network may employ local policies. + +Handover is only applicable to the EPC-routed PDN connections. For the NS-WLAN offloaded traffic, a new IP session in fixed broadband access network will be established. + +For connectivity to multiple PDNs, steps B.1 to 6 shall be repeated for each PDN. + +- 1-2. The description of these steps is the same as for steps 1-2 in TS 23 402 [3], clause 8.4.2.1. +- 3-4. The description of these steps is the same as for steps 1-2 in Figure 8.2.1-1. +5. This steps describe PCC signalling to provision policies for offloaded traffic and are only triggered when the BPCF receives the IMSI and the allocated UE local IP address using Fixed Broadband Access procedures. The description of this step is the same as for steps 3-5 in Figure 8.2.1-1. +6. The description of PDN Connection setup and Gateway Control Session setup are the same as for step 3-4 in Figure 8.2.1-1 with following addition: + - Step 4 in Figure 8.2.1-1 is mandatory when performing handover from E-UTRAN to Fixed Broadband Access. +7. The description of this step is the same as for step 5 in Figure 8.2.1-1. +8. The description of this step is the same as for step 12 in TS 23 402 [3], clause 8.4.2. + +### 8.2.6 Handover from Trusted Fixed Broadband Access with DSMIPv6 over S2c to 3GPP Access + +In this scenario, the session starts in a trusted Fixed Broadband Access system using DSMIPv6 over S2c and subsequently, the session hands over to a 3GPP access system. + +![Sequence diagram for Handover from Trusted Fixed Broadband Access with DSMIPv6 over S2c to 3GPP Access](508bc574df81fa8d3027a374f6d155fc_img.jpg) + +``` + +sequenceDiagram + participant UE + box "Fixed Broadband Access Network" + participant RG + participant BNG + participant AAA_proxy as AAA proxy + participant BPCF + end + participant ePDG + participant SGW as Serving GW + participant PGW as PDN GW + box "Roaming Scenarios" + participant AAA_Proxy_3GPP as 3GPP AAA Proxy + participant vPCRF + end + participant hPCRF + participant HSS_AAA as HSS/AAA + participant TDF + + Note over UE, PGW: 1. DSMIPv6 Tunnel + rect rgb(255, 255, 255) + Note over UE, TDF: 2. 3GPP Attach and Bearer Setup + end + UE->>PGW: 3. Binding Update (DSMIPv6 deregistration with lifetime=0) + PGW->>UE: 3. Binding Acknowledgement + Note over BPCF, hPCRF: 4. PCRF initiated Gateway Control Session Termination Procedure + Note over RG, BNG: 5. Access specific mechanism to release resources + rect rgb(255, 255, 255) + Note over UE, PGW: 6. Release of NSWO resources in Fixed Broadband Access and termination of IP-CAN session for NSWO + end + +``` + +The diagram shows the signaling flow for handover. Step 1 shows an existing DSMIPv6 tunnel between UE and PDN GW. Step 2 is a large block representing the 3GPP Attach and Bearer Setup. Step 3 involves Binding Update and Acknowledgement between UE and PDN GW. Step 4 is a dashed box indicating PCRF-initiated termination between BPCF and PCRFs. Step 5 is a dashed box for access-specific resource release in the Fixed Broadband network. Step 6 is a final block for releasing NSWO resources. + +Sequence diagram for Handover from Trusted Fixed Broadband Access with DSMIPv6 over S2c to 3GPP Access + +**Figure 8.2.6-1: Fixed Broadband Access with S2c (DSMIPv6) to 3GPP access handover** + +If dynamic policy provisioning over S9a is not deployed, the optional step 4 does not occur. Instead, the Fixed Broadband Access network may employ local policies. + +1. The UE uses a Fixed Broadband Access system. It has a DSMIPv6 session with the PDN GW. +- 2-3. The description of these steps is the same as for step 2-3 in TS 23 402, clause 8.4.1. +4. The PCRF (for non-roaming case) and the V-PCRF (for the home routed and visited access roaming case) executes a Gateway Control and QoS Rules Provision procedure or, if this is the last PDN Connection for the UE over Fixed Broadband Access, a PCRF-Initiated Gateway Control Session Termination Procedure with the BPCF. In roaming scenario, for the case when GTP is used on S2b, the H-PCRF will initiate the procedure over S9 towards the V-PCRF and the V-PCRF in turns initiates the procedure over S9a towards the BPCF. This procedure is triggered by the PCEF-Initiated IP-CAN Session Modification Procedure with the PCRF, occurring as a result of step 2. +5. The resources may be released in the Fixed Broadband Access, according to an access specific release mechanism. The details of this step are out of the scope of this specification. +6. If the NS-WLAN offloaded connection is released (e.g. if the UE moves out of WLAN coverage), the Fixed Broadband Access executes the access specific resource release procedure and initiates termination of the IP-CAN session for NS-WLAN offloaded traffic as described in steps 3-5 in clause 8.1.2. + +### 8.2.7 Network-Initiated Dynamic PCC for DSMIPv6 on S2c when accessing trusted Fixed Broadband Access for EPC-routed Traffic + +This procedure is applicable if the UE accesses over a Fixed Broadband Access network which is considered trusted. + +![Sequence diagram showing network-initiated dynamic policy control procedure in Trusted BBF IP Access for DSMIPv6 on S2c. The diagram illustrates interactions between a UE, a Fixed Broadband Access Network (containing RG, BNG, AAA proxy, and BPCF), a PDN GW, Roaming Scenarios (containing 3GPP AAA Proxy, vPCRF, and hPCRF), and an HSS/AAA. Four steps are shown: 1. Gateway Control and QoS Rules provision (from BPCF to vPCRF), 2. Access specific mechanism for admission control, etc (from BPCF to UE), 3. IP-CAN Session Modification (from vPCRF to PDN GW), and 4. IP-CAN Session Modification (from hPCRF to PDN GW).](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +Sequence diagram showing network-initiated dynamic policy control procedure in Trusted BBF IP Access for DSMIPv6 on S2c. The diagram illustrates interactions between a UE, a Fixed Broadband Access Network (containing RG, BNG, AAA proxy, and BPCF), a PDN GW, Roaming Scenarios (containing 3GPP AAA Proxy, vPCRF, and hPCRF), and an HSS/AAA. Four steps are shown: 1. Gateway Control and QoS Rules provision (from BPCF to vPCRF), 2. Access specific mechanism for admission control, etc (from BPCF to UE), 3. IP-CAN Session Modification (from vPCRF to PDN GW), and 4. IP-CAN Session Modification (from hPCRF to PDN GW). + +**Figure 8.2.7-1: Network-initiated dynamic policy control procedure in Trusted BBF IP Access for DSMIPv6 on S2c** + +This procedure concerns both the non-roaming (as Figure 4.2.2-3) and roaming case (as Figure 4.2.3-3). In the roaming case, the vPCRF in the VPLMN forwards messages between the BPCF and the hPCRF in the HPLMN. In the case of Local Breakout (as Figure 4.2.3-6), the vPCRF forwards messages sent between the PDN GW and the hPCRF. In the non-roaming case, the vPCRF is not involved at all. + +The optional interaction steps between the gateways and the PCRF in the procedures, step 1 and 3, only occur if dynamic policy provisioning is deployed. Otherwise Fixed Broadband Access network may employ BBF local policies. + +1-3. The description of these steps is the same as for steps 1-3 in clause 7.6. + +4. The PCEF acknowledges the provisioning of PCC Rules in the PCEF. For details please refer to TS 23.203 [4]. + +### 8.2.8 Network-Initiated Dynamic PCC for DSMIPv6 on S2c when accessing trusted Fixed Broadband Access for NS-WLAN offloaded Traffic + +The information flow of "Network-Initiated Dynamic PCC for DSMIPv6 on S2c when accessing trusted Fixed Broadband Access for offloaded Traffic" is same as S2b case, which is defined in clause 7.7. + +### 8.2.9 UE-Initiated Connectivity to Additional PDN with DSMIPv6 on S2c over trusted Fixed Broadband Access + +This clause is related to the case when the UE has an established PDN connection and wishes to establish one or more additional PDN connections. + +There can be more than one PDN connection per APN if the PDN GW supports that feature. + +![Sequence diagram showing UE-initiated connectivity to additional PDN. The diagram includes three main entities: UE, PDN GW1, and PDN GW2. Step 1 is an 'Initial S2c Attach as in figure 8.2.1-1' between UE and PDN GW1. Step 2 is an 'S2c Attach to additional PDNs as in figure 8.2.1-1' between UE and PDN GW2.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +Sequence diagram showing UE-initiated connectivity to additional PDN. The diagram includes three main entities: UE, PDN GW1, and PDN GW2. Step 1 is an 'Initial S2c Attach as in figure 8.2.1-1' between UE and PDN GW1. Step 2 is an 'S2c Attach to additional PDNs as in figure 8.2.1-1' between UE and PDN GW2. + +**Figure 8.2.9-1: UE-Initiated connectivity to additional PDN from Trusted Non-3GPP IP Access with DSMIPv6 on S2c** + +1. The UE has performed the Initial S2c attach procedure as defined in clause 8.2.1 and has an established PDN connection. +2. The UE repeats the procedure steps 3-5 of clause 8.2.1, Figure 8.2.1-1 for each additional PDN the UE wants to connect to. +- In Step 7, if no Gateway Control session over S9a for this UE, then the PCRF initiates the Gateway Control Session Establishment procedure with the BPCF. Otherwise, the PCRF provide new QoS rules corresponding to the new PDN connection to the BPCF using the Gateway Control and QoS Rules Provisioning procedure. + +### 8.2.10 Activation of enhanced security for S2c + +This clause is related to the case that UE creates the child SA to protect the user plane traffic exchanged over the S2c tunnel when the UE is in a trusted Fixed Broadband access. + +![Sequence diagram for activation of enhanced security for S2c. It shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BBF AAA proxy, BPCF), PDN GW, Roaming Scenarios (vPCRF, 3GPP AAA Proxy, hPCRF), and HSS/AAA. Step 1 is 'Initial attach procedure with S2c according to clause 8.1.1'. Step 2 is 'Child SA establishment as specified in TS 23.402, Figure 6.16.1-1 steps 2-4'. Step 3 is 'Gateway Control and QoS Rules Provisioning Procedure'. Step 4 is 'policy interaction'.](65d47e1d0e5982c00e9bd116b89e2b6a_img.jpg) + +Sequence diagram for activation of enhanced security for S2c. It shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BBF AAA proxy, BPCF), PDN GW, Roaming Scenarios (vPCRF, 3GPP AAA Proxy, hPCRF), and HSS/AAA. Step 1 is 'Initial attach procedure with S2c according to clause 8.1.1'. Step 2 is 'Child SA establishment as specified in TS 23.402, Figure 6.16.1-1 steps 2-4'. Step 3 is 'Gateway Control and QoS Rules Provisioning Procedure'. Step 4 is 'policy interaction'. + +**Figure 8.2.10-1 Activation of enhanced security for S2c** + +1. The UE has performed the Initial S2c attach procedure as defined in clause 8.2.1 and has an established PDN connection. +2. The UE repeats the procedure steps 2-4 of clause 6.16.1, Figure 6.16.1-1 to establish the child SA with the following additions: UDP source port number of IPSec tunnel as according to RFC 5996 is included in IP-CAN session modification. + +3. The Gateway Control and QoS Rules provision procedure is initiated by the PCRF towards the BPCF as specified in TS 23.203 [4] Annex P, with the following additions: UDP source port number of IPSec tunnel as according to RFC 5996. +4. The BPCF may interact with the BNG, e.g. to download policies, as defined by Fixed Broadband Access Policy Framework specifications BBF TR-134 [11] and BBF TR-203 [6]. This step is out of 3GPP scope. + +### 8.2.11 UE local IP address update on S2c over trusted Fixed Broadband Access + +This clause is related to the case where the UE local IP address, e.g. the CoA in the DSMIP procedure, is updated. + +![Sequence diagram for UE local IP address update on S2c over trusted Fixed Broadband Access. The diagram shows the interaction between the UE, BBF Access Network (RG, BNG, BBF AAA proxy, BPCF), PDN GW, Roaming Scenarios (vPCRF, hPCRF), and HSS/AAA. The process starts with an attach procedure, followed by a DSMIP tunnel establishment. When the UE's local IP address changes, it sends a DSMIPv6 Binding Update to the PDN GW, which responds with a Binding Acknowledgement. The PDN GW then triggers a PCEF-initiated IP-CAN Session Modification Procedure and a Gateway Control and QoS Rules provision procedure.](ef5f5c6665b6ae13660ede412333ba45_img.jpg) + +``` + +sequenceDiagram + participant UE + subgraph BBF_Access_Network [BBF Access Network] + participant RG + participant BNG + participant AAA [BBF AAA proxy] + participant BPCF + end + participant PDN_GW [PDN GW] + subgraph Roaming_Scenarios [Roaming Scenarios] + participant vPCRF + participant hPCRF + end + participant HSS_AAA [HSS/AAA] + + Note over UE, PDN_GW: 1. Attach procedure described in figure 8.2.1-1 + Note over UE, PDN_GW: DSMIP tunnel + Note over UE: 2. UE local IP address re-assignment + UE->>PDN_GW: 3. DSMIPv6 Binding Update + PDN_GW-->>UE: 5. DSMIPv6 Binding Acknowledgement + PDN_GW->>vPCRF: 4. PCEF-initiated IP-CAN Session Modification Procedure + vPCRF->>hPCRF: 6. Gateway Control and QoS Rules provision procedure + +``` + +Sequence diagram for UE local IP address update on S2c over trusted Fixed Broadband Access. The diagram shows the interaction between the UE, BBF Access Network (RG, BNG, BBF AAA proxy, BPCF), PDN GW, Roaming Scenarios (vPCRF, hPCRF), and HSS/AAA. The process starts with an attach procedure, followed by a DSMIP tunnel establishment. When the UE's local IP address changes, it sends a DSMIPv6 Binding Update to the PDN GW, which responds with a Binding Acknowledgement. The PDN GW then triggers a PCEF-initiated IP-CAN Session Modification Procedure and a Gateway Control and QoS Rules provision procedure. + +**Figure 8.2.11-1: UE local IP address changes on S2c over trusted Fixed Broadband Access** + +If dynamic policy provisioning over S9a is not deployed, the optional step 4 and 6 do not occur. Instead, the Fixed Broadband Access network may employ local policies. + +1. UE attaches to EPC from BBF access network as described in clause 8.2.1. The IPSec tunnel and DSMIP tunnel are established between P-GW and UE. +2. The description of this step is the same as step 2 in clause 7.11. +3. Upon a change of the UE's CoA, the UE sends the DSMIPv6 Binding Update message to the P-GW. In this step the P-GW gets the updated UE local IP address (i.e. the UE's CoA if no NAT is deployed or the NATed CoA when NAT is deployed) and optionally the UDP source port number (if NAT is detected) of the DSMIPv6 binding update signalling. +4. The description of this step is the same as step B.2 in clause 7.11. +5. P-GW replies with the DSMIPv6 Binding Acknowledgement message to UE. +6. The description of this step is the same as step B.4 in clause 7.11. + +## 8.3 Procedures for untrusted Fixed Broadband Access network over S2c + +### 8.3.1 Initial Attach with DSMIPv6 on S2c to untrusted Fixed Broadband Access + +This clause is related to the case when the UE attaches to a Fixed Broadband Access which is considered untrusted and S2c procedures are used when the UE establishes the first PDN connection over the Fixed Broadband Access with S2b, or when the UE has only the offloaded traffic via Fixed Broadband Access. + +This procedure establishes a session between the BPCF and the PCRF to provision policy decisions for NS-WLAN offloaded traffic or to provision policy decisions for EPC routed traffic. + +![Sequence diagram for Initial attachment when S2c is used for roaming, non-roaming and LBO. The diagram shows interactions between UE, RG, BNG, AAA proxy, BPCF, ePDG, PDN GW, V-PCRF, 3GPP AAA Proxy, hPCRF, HSS/AAA, and TDF. It is divided into 'Fixed Broadband Access Network' and 'Roaming Scenarios'.](10b0dda884baae493ad958422d11b552_img.jpg) + +The sequence diagram illustrates the initial attachment process. It begins with the UE sending a 3GPP-based access authentication (EAP-AKA) to the AAA proxy. The AAA proxy responds with a local IP address assignment. The BNG then triggers the BPCF, which sends an indication of IP-CAN session establishment to the V-PCRF. The V-PCRF initiates a TDF session establishment for NS-WLAN offloaded traffic. A dashed box labeled '6. PDN connection setup as specified in TS 23.402, clause 7.3, step 2-10' follows. Below this, the ePDG initiates a Gateway Control Session Establishment Procedure, which is followed by the PCRF-initiated Gateway Control Session Establishment. Finally, a policy interaction occurs between the BPCF and the BNG. + +Sequence diagram for Initial attachment when S2c is used for roaming, non-roaming and LBO. The diagram shows interactions between UE, RG, BNG, AAA proxy, BPCF, ePDG, PDN GW, V-PCRF, 3GPP AAA Proxy, hPCRF, HSS/AAA, and TDF. It is divided into 'Fixed Broadband Access Network' and 'Roaming Scenarios'. + +Figure 8.3.1-1: Initial attachment when S2c is used for roaming, non-roaming and LBO + +NOTE: In the roaming case step 7 terminates at the V-PCRF. + +If dynamic policy provisioning over S9a is not deployed, the optional steps 3, 4, 5, 7 and 8 do not occur. + +- 1. The description of this step is the same as step 1 in clause 7.2. +- 2. The description of this step is the same as step 2 in clause 7.2. + +The steps in 3, 4 and 5 describe PCC Signalling for NS-WLAN offloaded traffic, the trigger is described in clause 7.2. + +- 3. The description of this step is the same as step 3 in clause 7.2. +- 4. This description of this step is the same as step 4 in clause 7.2. +- 5. This description of this step is the same as step 5 in clause 7.2. + +Steps 6, 7 and 8 describe PCC signalling to provision policies for EPC routed traffic. + +- 6. The description of the PDN connection setup procedure is the same as for steps 2-10 in TS 23 402 [3], clause 7.3 +- 7. The description of this step is the same as step 7 in clause 7.2. +- 8. This description of this step is the same as step 8 in clause 7.2. +- 9. This description of this step is the same as step 9 in clause 7.2. + +### 8.3.2 UE-initiated Detach Procedure and UE-Requested PDN Disconnection with DSMIPv6 on S2c in untrusted Fixed Broadband Access + +The procedure in this clause applies to UE-initiated detach procedures (e.g. UE power-off), initiated by UE, and to the UE-requested PDN disconnection procedure. The UE can initiate the Detach procedure, e.g. when the UE is power off. For multiple PDN connectivity, this detach procedure shall be repeated for each PDN connected. + +This clause covers also the termination of the IP-CAN session for UE's NS-WLAN offloaded traffic initiated by the Fixed Broadband Network. + +![Sequence diagram showing the UE-initiated detach procedure with DSMIPv6 on untrusted S2c. The diagram includes entities: UE, Fixed Broadband Access Network (RG, BNG, BPCF, BBF AAA Proxy), ePDG, PDN GW, Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF), HSS/AAA, and TDF. The procedure consists of six steps: 1. UE-initiated PDN disconnection procedure in unTrusted Non-3GPP Access Network; 2. Gateway control session termination procedure; 3. Gateway Control and QoS Rules Provision procedure or PCRF-Initiated Gateway Control Session Termination Procedure; 4. BBF specific resource release procedure; 5. Indication of IP-CAN session termination procedure; 6. TDF session termination procedure (offloaded traffic).](4842f073775fb1e84d101c02fd74e59e_img.jpg) + +Sequence diagram showing the UE-initiated detach procedure with DSMIPv6 on untrusted S2c. The diagram includes entities: UE, Fixed Broadband Access Network (RG, BNG, BPCF, BBF AAA Proxy), ePDG, PDN GW, Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF), HSS/AAA, and TDF. The procedure consists of six steps: 1. UE-initiated PDN disconnection procedure in unTrusted Non-3GPP Access Network; 2. Gateway control session termination procedure; 3. Gateway Control and QoS Rules Provision procedure or PCRF-Initiated Gateway Control Session Termination Procedure; 4. BBF specific resource release procedure; 5. Indication of IP-CAN session termination procedure; 6. TDF session termination procedure (offloaded traffic). + +Figure 8.3.2-1: UE-initiated detach procedure with DSMIPv6 on untrusted S2c + +NOTE: In the roaming case, the Step 2 terminates at the V-PCRF. + +If dynamic policy provisioning is not deployed, the optional steps 2, 3, 5 and 6 do not occur. Instead, the Fixed Broadband Access network may employ local policies. + +1. The description of this step is the same as UE-initiated PDN disconnection procedure in untrusted Non-3GPP Access Network as specified in TS 23 402, figure 7.5.2-1 steps 1-4 and 6; +2. The PCRF initiates Gateway Control Session termination procedure with the ePDG over Gxb\*, if the last PDN connection is terminated for that UE. +3. Triggered by the IP-CAN session termination in step 1, the PCRF executes a Gateway Control and QoS Rules Provision procedure or, if this is the last PDN Connection for the UE, a PCRF-Initiated Gateway Control Session Termination Procedure with the BPCF. +4. The description of this step is the same as clause 7.3 step 4. +5. The description of this step is the same as clause 7.3 step 5. +6. The description of this step is the same as clause 7.3 step 6. + +### 8.3.3 HSS-initiated Detach Procedure with DSMIPv6 on S2c in untrusted Fixed Broadband Access + +The procedure in this clause applies to Detach Procedures, initiated by HSS. + +![Sequence diagram of HSS-initiated detach procedure with DSMIPv6 on untrusted s2c. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BPCF, BBF AAA Proxy), ePDG, PDN GW, Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF), HSS/AAA, and TDF. The procedure consists of six steps: 1. HSS initiated PDN connection disconnection; 2. Gateway control session termination (optional); 3. Gateway Control and QoS Rules Provision or Termination (optional); 4. BBF specific resource release; 5. Indication of IP-CAN session termination (optional); 6. TDF session termination (optional, offloaded traffic).](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +Sequence diagram of HSS-initiated detach procedure with DSMIPv6 on untrusted s2c. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BPCF, BBF AAA Proxy), ePDG, PDN GW, Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF), HSS/AAA, and TDF. The procedure consists of six steps: 1. HSS initiated PDN connection disconnection; 2. Gateway control session termination (optional); 3. Gateway Control and QoS Rules Provision or Termination (optional); 4. BBF specific resource release; 5. Indication of IP-CAN session termination (optional); 6. TDF session termination (optional, offloaded traffic). + +Figure 8.3.3-1: HSS-initiated detach procedure with DSMIPv6 on untrusted s2c + +NOTE: In the roaming case, the Step 2 terminates at the V-PCRF. + +If dynamic policy provisioning over S9a is not deployed, the optional steps 2, 3, 5 and 6 do not occur. Instead, the Fixed Broadband Access network may employ local policies. + +1. The description of this step is the same as for steps 1-5 in TS 23 402 [3], clause 7.5.3. +2. If the last PDN connections is released, PCRF initiates Gxb\* session termination procedure. +3. Triggered by the IP-CAN session termination in step 1, the PCRF executes a Gateway Control and QoS Rules Provision procedure or, if this is the last PDN Connection for the UE, a PCRF-Initiated Gateway Control Session Termination Procedure with the BPCF. +4. The description of this step is the same as clause 7.3 step 4. +5. The description of this step is the same as clause 7.3 step 5. +6. The description of this step is the same as clause 7.3 step 6. + +### 8.3.4 PDN GW-initiated PDN disconnection Procedure with DSMIPv6 on S2c in untrusted Fixed Broadband Access + +The procedure in this clause applies to PDN disconnection procedure initiated by PDN GW. + +![Sequence diagram of PDN GW-initiated PDN disconnection procedure with DSMIPv6 on untrusted s2c. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BPCF, BBF AAA Proxy), ePDG, PDN GW, Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF), HSS/AAA, and TDF. The procedure consists of six steps: 1. PDN GW initiated PDN connection disconnection; 2. Gateway control session termination procedure; 3. Gateway Control and QoS Rules Provision procedure or PCRF-Initiated Gateway Control Session Termination Procedure; 4. BBF specific resource release procedure; 5. Indication of IP-CAN session termination procedure; 6. TDF session termination procedure (offloaded traffic).](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +Sequence diagram of PDN GW-initiated PDN disconnection procedure with DSMIPv6 on untrusted s2c. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BPCF, BBF AAA Proxy), ePDG, PDN GW, Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF), HSS/AAA, and TDF. The procedure consists of six steps: 1. PDN GW initiated PDN connection disconnection; 2. Gateway control session termination procedure; 3. Gateway Control and QoS Rules Provision procedure or PCRF-Initiated Gateway Control Session Termination Procedure; 4. BBF specific resource release procedure; 5. Indication of IP-CAN session termination procedure; 6. TDF session termination procedure (offloaded traffic). + +**Figure 8.3.4-1: PDN GW-initiated PDN disconnection procedure with DSMIPv6 on untrusted s2c** + +NOTE: In the roaming case, the Step 2 terminates at the V-PCRF. + +If dynamic policy provisioning over S9a is not deployed, the optional steps 2, 3, 5 and 6 do not occur. Instead, the Fixed Broadband Access network may employ local policies. + +1. The description of this step is the same as for steps 1-4 in TS 23 402 [3], clause 7.5.4. +2. If the last PDN connections is released, PCRF initiates Gxb\* session termination procedure. +3. Triggered by the IP-CAN session termination in step 1, the PCRF executes a Gateway Control and QoS Rules Provision procedure or, if this is the last PDN Connection for the UE, a PCRF-Initiated Gateway Control Session Termination Procedure with the BPCF. +4. The description of this step is the same as clause 7.3 step 4 +5. The description of this step is the same as clause 7.3 step 5. +6. The description of this step is the same as clause 7.3 step 6. + +### 8.3.5 E-UTRAN to untrusted Fixed Broadband Access Handover with DSMIPv6 on S2c + +This clause shows the combined call flow for a handover when a UE moves from an E-UTRAN to an untrusted Fixed Broadband Access network. In addition, the procedures for the IP session establishment for NS-WLAN offload using the Fixed Broadband Access network are also integrated into the combined procedures. + +![Sequence diagram for E-UTRAN to untrusted Fixed Broadband Access Handover with DSMIPv6 on s2c. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BBF AAA proxy, BPCF), ePDG, MME, Serving GW, PDN GW, and Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF, HSS/AAA, TDF). Steps include: 1. Radio bearer and S1 bearer establishment; 2. UE discovers BBF Access and initiates HO; 3. 3GPP-based access authentication (EAP-AKA); 4. Address assignment; 5. IP-CAN Session establishment; 6. PDN connection setup and Gateway Control Session establishment; 7. policy interaction; 8. 3GPP EPS Bearer release.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +Sequence diagram for E-UTRAN to untrusted Fixed Broadband Access Handover with DSMIPv6 on s2c. The diagram shows interactions between UE, Fixed Broadband Access Network (RG, BNG, BBF AAA proxy, BPCF), ePDG, MME, Serving GW, PDN GW, and Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF, HSS/AAA, TDF). Steps include: 1. Radio bearer and S1 bearer establishment; 2. UE discovers BBF Access and initiates HO; 3. 3GPP-based access authentication (EAP-AKA); 4. Address assignment; 5. IP-CAN Session establishment; 6. PDN connection setup and Gateway Control Session establishment; 7. policy interaction; 8. 3GPP EPS Bearer release. + +**Figure 8.3.5-1: E-UTRAN to untrusted Fixed Broadband Access Handover with DSMIPv6 on s2c** + +Both the roaming and non-roaming scenarios are depicted in the figure. + +If dynamic policy provisioning over S9a is not deployed, the optional steps 5 and 7 do not occur. Instead, the Fixed Broadband Access network may employ local policies. + +Handover is only applicable to the EPC-routed PDN connections. For the NS-WLAN offloaded traffic, a new IP session in fixed broadband access network is established. + +For connectivity to multiple PDN steps 5 to 6 shall be repeated for each PDN connection. + +- 1-2. This step is the same as steps 1-3 in TS 23 402 [3], clause 8.4.3, with the following addition: As part of the 3GPP-based authentication, the permanent user identity (IMSI) is provided from the 3GPP AAA Server to the Fixed Broadband Access network +- 3-4. The description of these steps is the same as for step 2 in Figure 8.3.1-1. +- 5. This step describes PCC signalling to provision policies for offloaded traffic and is only triggered when the BPCF receives the IMSI and the allocated UE local IP address using Fixed Broadband Access procedures. The description of this step is the same as for steps 3-5 in Figure 8.3.1-1. +- 6. The description of PDN Connection setup and Gateway Control Session setup are the same as for step 3-5 in Figure 8.3.1-1 with following addition: + - Step 3 in Figure 8.3.1-1 is mandatory when performing handover from E-UTRAN to Fixed Broadband Access. +- 7. The description of this step is the same as for step 5 in Figure 8.2.1-1 +- 8. The description of this step is the same as for step 11 in TS 23 402 [3], clause 8.4.3. + +### 8.3.6 Handover from Untrusted Fixed Broadband Access with DSMIPv6 over S2c to 3GPP Access + +In this scenario, the session starts in an untrusted Fixed Broadband Access system using DSMIPv6 over S2c and subsequently, the session hands over to a 3GPP access system. + +![Sequence diagram for Fixed Broadband Access with S2c (DSMIPv6) to 3GPP access handover.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RG + participant BNG + participant AAA_proxy as AAA proxy + participant BPCF + participant ePDG + participant SGW as Serving GW + participant PGW as PDN GW + participant AAA_Proxy_3GPP as 3GPP AAA Proxy + participant vPCRF + participant hPCRF + participant HSS_AAA as HSS/AAA + participant TDF + + Note over UE, ePDG: 1. SWu tunnel + Note over UE, PGW: 1. DSMIPv6 Tunnel + rect rgb(255, 255, 255) + Note over UE, PGW: 2. 3GPP Attach and Bearer Setup + end + UE->>PGW: 3. Binding Update (DSMIPv6 deregistration with lifetime=0) + PGW->>UE: 3. Binding Acknowledgement + hPCRF-->>PGW: 4. PCRF initiated Gateway Control Session Termination Procedure + Note over RG, BPCF: 5. Access specific mechanism to release resources + rect rgb(255, 255, 255) + Note over UE, PGW: 6. Release of NSWO resources in Fixed Broadband Access and termination of IP-CAN session for NSWO + end + +``` + +The diagram shows the handover process from Fixed Broadband Access to 3GPP access. It involves a Fixed Broadband Access Network (RG, BNG, AAA proxy, BPCF) and core network elements (ePDG, Serving GW, PDN GW) along with roaming scenario entities (3GPP AAA Proxy, vPCRF, hPCRF, HSS/AAA, TDF). +Step 1 shows established SWu and DSMIPv6 tunnels. +Step 2 is the 3GPP Attach and Bearer Setup. +Step 3 involves Binding Update and Acknowledgement between UE and PDN GW. +Step 4 is an optional PCRF-initiated termination procedure. +Step 5 is a local resource release mechanism. +Step 6 is the final release of NSWO resources and termination of the IP-CAN session. + +Sequence diagram for Fixed Broadband Access with S2c (DSMIPv6) to 3GPP access handover. + +**Figure 8.3.6-1: Fixed Broadband Access with S2c (DSMIPv6) to 3GPP access handover** + +If dynamic policy provisioning over S9a is not deployed, the optional step 4 does not occur. Instead, the Fixed Broadband Access network may employ local policies. + +- The UE uses a Fixed Broadband Access system. It has a SWu session with the ePDG and a DSMIPv6 session with the PDN GW. +- 2-5. The description of these steps is the same as for steps 2-6 in clause 8.2.6. +6. If the NS-WLAN offloaded connection is released (e.g. if the UE moves out of WLAN coverage), the Fixed Broadband Access executes the access specific resource release procedure and initiates termination of the IP-CAN session for NS-WLAN offloaded traffic as described in steps 4-6 in clause 8.2.2. + +### 8.3.7 Network-Initiated Dynamic PCC for S2c when accessing untrusted Fixed Broadband Access for EPC-routed Traffic + +This procedure is applicable if the UE accesses over a Fixed Broadband Access network which is considered untrusted. + +![Sequence diagram showing network-initiated dynamic policy control procedure in un-trusted BBF IP Access for DSMIPv6 on S2c. The diagram includes lifelines for UE, Fixed Broadband Access Network (RG, BNG, AAA proxy, BPCF), ePDG, PDN GW, Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF), and HSS/AAA. Four steps are shown: 1. Gateway Control and QoS Rules provision procedure, 2. Access specific mechanism for admission control, etc, 3. IP-CAN Session Modification, and 4. IP-CAN Session Modification.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +The diagram illustrates the network-initiated dynamic policy control procedure. It features several lifelines: UE, Fixed Broadband Access Network (containing RG, BNG, AAA proxy, and BPCF), ePDG, PDN GW, Roaming Scenarios (containing 3GPP AAA Proxy, vPCRF, and hPCRF), and HSS/AAA. The sequence of interactions is as follows: + + +- 1. Gateway Control and QoS Rules provision procedure:** A dashed double-headed arrow between the BPCF and the PDN GW. +- 2. Access specific mechanism for admission control, etc:** A box below the BPCF, with a dashed double-headed arrow between the BPCF and the PDN GW. +- 3. IP-CAN Session Modification:** A dashed double-headed arrow between the PDN GW and the vPCRF. +- 4. IP-CAN Session Modification:** A dashed double-headed arrow between the vPCRF and the hPCRF. + +Sequence diagram showing network-initiated dynamic policy control procedure in un-trusted BBF IP Access for DSMIPv6 on S2c. The diagram includes lifelines for UE, Fixed Broadband Access Network (RG, BNG, AAA proxy, BPCF), ePDG, PDN GW, Roaming Scenarios (3GPP AAA Proxy, vPCRF, hPCRF), and HSS/AAA. Four steps are shown: 1. Gateway Control and QoS Rules provision procedure, 2. Access specific mechanism for admission control, etc, 3. IP-CAN Session Modification, and 4. IP-CAN Session Modification. + +**Figure 8.3.7-1: Network-initiated dynamic policy control procedure in un-trusted BBF IP Access for DSMIPv6 on S2c** + +This procedure concerns both the non-roaming (as Figure 4.2-3) and roaming case (as Figure 4.2-6). In the roaming case, the vPCRF in the VPLMN forwards messages between the BPCF and the hPCRF in the HPLMN. In the case of Local Breakout (as Figure 4.2-9), the vPCRF forwards messages sent between the PDN GW and the hPCRF. In the non-roaming case, the vPCRF is not involved at all. + +The optional interaction steps between the gateways and the PCRF in the procedures, step 1 and 3, only occur if dynamic policy provisioning is deployed. Otherwise Fixed Broadband Access network may employ BBF local policies. + +1-3. The description of these steps is the same as for steps 1-3 in clause 7.6. + +4. The PCEF acknowledges the provisioning of PCC Rules in the PCEF. For details please refer to TS 23.203 [4]. + +### 8.3.8 Network-Initiated Dynamic PCC for S2c when accessing untrusted Fixed Broadband Access for NS-WLAN offloaded Traffic + +The information flow of "Network-Initiated Dynamic PCC for DSMIPv6 on S2c when accessing untrusted Fixed Broadband Access for offloaded Traffic" is same as S2b case, which is defined in clause 7.7. + +### 8.3.9 UE-Initiated Connectivity to Additional PDN with DSMIPv6 on S2c over untrusted Fixed Broadband Access + +This clause is related to the case when the UE has an established PDN connection and wishes to establish one or more additional PDN connections. + +Since DSMIPv6 is used to establish connectivity with the additional PDN, the UE does not need to establish a separate SWu instance (i.e. a separate IPSec tunnel) for each additional PDN. + +There can be more than one PDN connection per APN if the PDN GW supports that feature. + +![Sequence diagram showing UE-initiated connectivity to additional PDN from untrusted Non-3GPP IP Access with DSMIPv6 on S2c. The diagram involves three entities: UE, PDN GW1, and PDN GW2. Step 1 shows the UE sending an 'Initial S2c Attach' message to PDN GW1. Step 2 shows the UE sending an 'S2c Attach to additional PDNs' message to PDN GW2.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` +sequenceDiagram + participant UE + participant PDN GW1 + participant PDN GW2 + Note left of UE: 1. Initial S2c Attach as in Figure 8.2.1-1 + UE->>PDN GW1: 1. Initial S2c Attach + Note left of UE: 2. S2c Attach to additional PDNs as in Figure 8.3.1-1 + UE->>PDN GW2: 2. S2c Attach to additional PDNs +``` + +Sequence diagram showing UE-initiated connectivity to additional PDN from untrusted Non-3GPP IP Access with DSMIPv6 on S2c. The diagram involves three entities: UE, PDN GW1, and PDN GW2. Step 1 shows the UE sending an 'Initial S2c Attach' message to PDN GW1. Step 2 shows the UE sending an 'S2c Attach to additional PDNs' message to PDN GW2. + +**Figure 8.3.9-1: UE-Initiated connectivity to additional PDN from untrusted Non-3GPP IP Access with DSMIPv6 on S2c** + +1. The UE has performed the Initial S2c attach procedure as defined in clause 8.3.1 and has an established PDN connection. +2. The UE repeats the procedure steps 6-9 of clause 8.3.1, Figure 8.3.1-1 (Initial attachment when S2c is used for roaming, non-roaming and LBO) for each additional PDN the UE wants to connect to. For network supporting multiple mobility protocols, if there was any dynamic IPMS decision in step 1, the AAA/HSS enforces the same IPMS decision for each additional PDN connection. + - In Step 8, if no Gateway Control session over S9a for this UE, then the PCRF initiates the Gateway Control Session Establishment procedure with the BPCF. Otherwise, the PCRF provide new QoS rules corresponding to the new PDN connection to the BPCF using the Gateway Control and QoS Rules Provisioning procedure. + +### 8.3.10 IPSec tunnel modified on S2c over untrusted Fixed Broadband Access + +This clause is related to the case where the IPSec tunnel between the UE and the ePDG has been modified due to the UE initiated IPSec tunnel update procedure or a UE local IP address update. This procedure is only applicable if MOBIKE is supported by the UE. + +![Sequence diagram showing IPsec tunnel modification on S2c over untrusted Fixed Broadband Access. Lifelines include UE, RG, BNG, BBF AAA proxy, BPCF (grouped as BBF Access Network), ePDG, PDN GW, vPCRF, hPCRF (grouped as Roaming Scenarios), and HSS/AAA. The diagram illustrates five steps: 1. Attach procedure, 2. UE local IP address re-assignment, 3. MOBIKE update address, 4. Gateway Control and QoS Rules update procedure, and 5. Gateway Control and QoS Rules provision procedure. It shows the transition from an initial IPsec tunnel to an updated one.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +Sequence diagram showing IPsec tunnel modification on S2c over untrusted Fixed Broadband Access. Lifelines include UE, RG, BNG, BBF AAA proxy, BPCF (grouped as BBF Access Network), ePDG, PDN GW, vPCRF, hPCRF (grouped as Roaming Scenarios), and HSS/AAA. The diagram illustrates five steps: 1. Attach procedure, 2. UE local IP address re-assignment, 3. MOBIKE update address, 4. Gateway Control and QoS Rules update procedure, and 5. Gateway Control and QoS Rules provision procedure. It shows the transition from an initial IPsec tunnel to an updated one. + +**Figure 8.3.10-1: IPSec tunnel modified on S2c over untrusted Fixed Broadband Access** + +If dynamic policy provisioning over S9a is not deployed, the optional step 4 and 5 do not occur. Instead, the Fixed Broadband Access network may employ local policies. + +1. UE attaches to EPC from untrusted BBF access network via ePDG, as described in clause 8.3.1. The IPsec tunnel is established between ePDG and UE; another IPsec tunnel is established between the PDN GW and UE. This clause only defines the outer IPsec tunnel (between the UE and ePDG) modification. +2. The description of this step is the same as step 2 in clause 7.11. +3. The description of this step is the same as step 3 in clause 7.11. +4. The description of this step is the same as step A.1 in clause 7.11. +5. The description of this step is the same as step A.2 in clause 7.11. + +# 9 Functional Description and Procedures for Fixed Broadband Access network using H(e)NB + +## 9.1 Procedures for Fixed Broadband Access network using HeNB + +### 9.1.1 E-UTRAN Initial Attach and UE requested PDN connection Establishment + +This clause is related to the case when the UE performs initial attachment or UE requests connectivity to an additional PDN to the E-UTRAN network via a HeNB. The HeNB is already registered in the network. + +The HeNB sends the HeNB local IP address and the UDP port if NAT/NAPT is detected in the fixed Broadband access networks to the MME in UE associated S1 signalling (refer to the definition of Initial UE Message in TS 36.413 [29]). + +![Sequence diagram of UE Attach and UE requested PDN connection Establishment procedure via HeNB. The diagram shows interactions between UE, HeNB, Fixed Broadband Access (RG, BNG, BPCF), SeGW, HeNB GW, MME, S-GW, P-GW, and PCRF.](5801c19431e76330430e92a598cc7a16_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HeNB + box "Fixed Broadband Access" + participant RG + participant BNG + participant BPCF + end + participant SeGW + participant HeNB GW + participant MME + participant S-GW + participant P-GW + participant PCRF + + HeNB->>MME: 1. HeNB connected + UE->>MME: 2. Attach Request / PDN connectivity Request + Note over UE, PCRF: 3. Initial Attach case, refer to the description of steps 3 to 13 of TS 23.401 E-UTRAN Initial Attach procedure Figure 5.3.2.1-1; UE requested PDN connectivity case, refer to the description of steps 2 to 3 of TS 23.401 UE requested PDN connectivity procedure, Figure 5.10.2-1 + MME->>P-GW: 4. IP-CAN session establishment/modification + PCRF->>BPCF: 5. PCRF initiated Gateway Control Session establishment/QoS Rules provisioning + P-GW->>MME: 6. IP-CAN session establishment/modification Ack + Note over UE, PCRF: 7. Initial Attach case, steps 15 to 26 of 23.401 E-UTRAN Initial Attach procedure Figure 5.3.2.1-1; UE requested PDN connectivity case, step 5-16 of TS 23.401 UE requested PDN connectivity procedure, Figure 5.10.2-1 + +``` + +Sequence diagram of UE Attach and UE requested PDN connection Establishment procedure via HeNB. The diagram shows interactions between UE, HeNB, Fixed Broadband Access (RG, BNG, BPCF), SeGW, HeNB GW, MME, S-GW, P-GW, and PCRF. + +**Figure 9.1.1: UE Attach and UE requested PDN connection Establishment procedure via HeNB** + +1. The HeNB is already registered in the network. +2. The description of this step is the same as for step 1 and 2 in TS 23.401 [2], clause 5.3.2.1 (Initial attach case), or is the same as for step 1 in TS 23.401 [2], clause 5.10.2 (UE requested PDN connection Establishment case) with the addition that HeNB includes the following additional information: the HeNB local IP address and the UDP port if NAT/NAPT is detected in the S1 signalling (refer to the definition of Initial UE Message in TS 36.413 [29]) and sends them to MME. +3. This step is the same as steps 3-13 in TS 23.401 [2] clause 5.3.2.1 (Initial attach case) or steps 2-3 in TS 23.401 [2] clause 5.10.2 (UE requested PDN connection Establishment case), with the following additional information included in Create Session Request message sending between MME and S-GW, and between S-GW and P-GW: HeNB Local IP address and the UDP port if NAT/NAPT is detected. +4. The PDN GW initiates the IP-CAN session establishment/modification procedure with the PCRF per TS 23.203 [4]. The message includes the IMSI, the HeNB local IP address and the UDP port if NAT/NAPT is detected. +5. The PCRF sends the Gateway Control Session establishment/QoS Rules provisioning message to the BPCF according to TS 23.203 [4]. The message includes the IMSI, HeNB local IP address and UDP port if NAT/NAPT is detected. + +Once this step completes the PCRF is aware the fact that the UE is connected to the network via a 3GPP H(e)NB and checks first whether sufficient resources are available in the BBF access before it provisions PCC rules at the PCEF. + +6. The PCRF acknowledges the IP-CAN session establishment/modification. +7. This step is the same as steps 15-26 in TS 23.401 [2] clause 5.3.2.1 (Initial attach case) or steps 5-16 in TS 23.401 [2] clause 5.10.2 (UE requested PDN connection Establishment case) with the following additions: If the H(e)NB local IP address and UDP port number change reporting triggers are received from the PCRF, the PDN GW should set the H(e)NB local IP address and UDP port number Information Reporting accordingly. If the H(e)NB local IP address and UDP port number Reporting Request is received for this PDN connection, then the MME shall report to the PCEF/PCRF changes of HeNB local IP address and/or port (if available). + +### 9.1.2 Detach procedure for E-UTRAN + +This clause is related to detach procedure for E-UTRAN, and contains the following cases: UE-initiated Detach procedure, MME-initiated Detach procedure, and HSS-initiated Detach procedure. + +![Sequence diagram for Detach Procedure via HeNB- UE camping on E-UTRAN. The diagram shows interactions between UE, HeNB, Fixed Broadband Access (RG, BNG, BPCF, SeGW), HeNB GW, MME, S-GW, P-GW, HSS, and PCRF. The procedure consists of five numbered steps: 1. Initial detach request/cancel location request; 2. UE/MME/HSS initiated steps; 3. IP-CAN session termination; 4. Gateway Control Session termination / QoS Rules provisioning; 5. Final UE/MME/HSS initiated steps.](bfca6639dd4b8480f2d96d2b61c806d9_img.jpg) + +The diagram illustrates the sequence of messages for the detach procedure. The entities involved are UE, HeNB, Fixed Broadband Access (containing RG, BNG, BPCF, and SeGW), HeNB GW, MME, S-GW, P-GW, HSS, and PCRF. The procedure is divided into five steps: + +1. UE-initiated Detach case, the UE sends a detach request message to MME, which can be referred to step 1 of figure 5.3.8.2-1, TS 23.401; MME-initiated Detach case, the MME sends a detach request message to UE, which can be referred to step 1 of figure 5.3.8.3-1, TS 23.401; HSS-initiated Detach case, the HSS sends a cancel location request message to MME, which can be referred to step 1 of figure 5.3.8.4-1, TS 23.401. + +2. UE-initiated Detach case, refer to steps 2-7 of TS 23.401, figure 5.3.8.2-1; MME-initiated Detach case, refer to steps 2-7 of TS 23.401, figure 5.3.8.3-1; HSS-initiated Detach case, refer to steps 1b - 5 of TS 23.401, figure 5.3.8.4-1. + +3. IP-CAN session termination (between P-GW and PCRF). + +4. Gateway Control Session termination / QoS Rules provisioning procedure (between PCRF and P-GW). + +5. UE-initiated Detach case, refer to steps 9-13 of TS 23.401, figure 5.3.8.2-1; MME-initiated Detach case, refer to steps 9-12 of TS 23.401, figure 5.3.8.3-1; HSS-initiated Detach case, refer to steps 7-10 of TS 23.401, figure 5.3.8.4-1. + +Sequence diagram for Detach Procedure via HeNB- UE camping on E-UTRAN. The diagram shows interactions between UE, HeNB, Fixed Broadband Access (RG, BNG, BPCF, SeGW), HeNB GW, MME, S-GW, P-GW, HSS, and PCRF. The procedure consists of five numbered steps: 1. Initial detach request/cancel location request; 2. UE/MME/HSS initiated steps; 3. IP-CAN session termination; 4. Gateway Control Session termination / QoS Rules provisioning; 5. Final UE/MME/HSS initiated steps. + +**Figure 9.1.2: Detach Procedure via HeNB- UE camping on E-UTRAN** + +1. UE-initiated Detach case, the UE sends a detach request message to MME, which can be referred to step 1 of figure 5.3.8.2-1, TS 23.401 [2]; MME-initiated Detach case, the MME sends a detach request message to UE, which can be referred to step 1 of figure 5.3.8.3-1, TS 23.401 [2]; HSS-initiated Detach case, the HSS sends a cancel location request message to MME, which can be referred to step 1 of figure 5.3.8.4-1, TS 23.401 [2]. +2. UE-initiated Detach case, refer to steps 2-7 per TS 23.401 [2], figure 5.3.8.2-1; MME-initiated Detach case, refer to steps 2-7 per TS 23.401 [2], figure 5.3.8.3-1; HSS-initiated Detach case, refer to steps 1b - 5 per TS 23.401 [2], figure 5.3.8.4-1. +3. The P-GW initiates the IP-CAN session termination procedure with the PCRF per TS 23.203 [4]. +- 4 The PCRF initiates the Gateway Control session termination procedure according to TS 23.203 [4]. The PCRF sends the QoS Rules Provisioning procedure when there is one or more Gx sessions linked to the S9a session. +5. UE-initiated Detach case, refer to steps 9-13 per TS 23.401 [2], figure 5.3.8.2-1; MME-initiated Detach case, refer to steps 9-12 per TS 23.401 [2], figure 5.3.8.3-1; HSS-initiated Detach case, refer to steps 7-10 per TS 23.401 [2], figure 5.3.8.4-1. + +### 9.1.3 Network initiated bearer activation, modification and deactivation + +This clause is related to Network initiated Bearer operation procedure and contains the following cases: Dedicated bearer activation, Bearer modification with bearer QoS update, and Bearer deactivation. + +![Sequence diagram for Network initiated Bearer activation, modification, and deactivation for HeNB. The diagram shows interactions between UE, HeNB, Fixed Broadband Access (RG, BNG, BPCF, SeGW), HeNB GW, MME, S-GW, P-GW, HSS, and PCRF. Step 1: Gateway Control and QoS Rules provisioning procedure from PCRF to BPCF. Step 2: PCRF-initiated IP-CAN session modification from PCRF to P-GW. Step 3: A box containing details for Dedicated bearer activation, Bearer modification with bearer QoS update, and Bearer deactivation cases, referring to TS 23.401.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +Sequence diagram for Network initiated Bearer activation, modification, and deactivation for HeNB. The diagram shows interactions between UE, HeNB, Fixed Broadband Access (RG, BNG, BPCF, SeGW), HeNB GW, MME, S-GW, P-GW, HSS, and PCRF. Step 1: Gateway Control and QoS Rules provisioning procedure from PCRF to BPCF. Step 2: PCRF-initiated IP-CAN session modification from PCRF to P-GW. Step 3: A box containing details for Dedicated bearer activation, Bearer modification with bearer QoS update, and Bearer deactivation cases, referring to TS 23.401. + +**Figure 9.1.3 Network initiated Bearer activation, modification, and deactivation for HeNB** + +1. The PCRF initiates the GW Control and QoS Provisioning procedure with the BPCF to request BPCF to reserve resource for traffic flow (Dedicated bearer activation), or to request allocation of resources in the BBF access network (Bearer modification with bearer QoS update), or to de-allocate resources in the BBF access network (Bearer deactivation). The message includes the QoS rules (SDF, QCI, ARP, GBR, MBR) according to TS 23.203 [4]. +2. The PCRF initiates the IP-CAN session modification procedure with the P-GW/PCEF according to TS 23.203 [4]. +3. Dedicated bearer activation case, refer to steps 2-11 according to TS 23.401 [2], 5.4.1; Bearer modification with bearer QoS update case, refer to steps 2-11 according to TS 23.401 [2], figure 5.4.2.1; Bearer deactivation case, refer to steps 2-9 according to TS 23.401 [2], figure 5.4.4.1. + +NOTE: Step 1 may be triggered by service resource request from AF. + +### 9.1.4 UE requested bearer resource modification + +This procedure is executed per TS 23.401 [2], clause 5.4.5 when the PCRF determines that the UE's request result in allocation/de-allocation of resources in the BBF access. + +![Sequence diagram for UE requested bearer resource modification. Lifelines: UE, HeNB, RG, BNG, Fixed Broadband Access (BPCF), SeGW, HeNB GW, MME, S-GW, P-GW, PCRF. The diagram shows 6 steps: 1. UE to MME: Request Bearer Resource Modification; 2. MME to P-GW: Steps 2-3 according to TS 23.401, figure 5.4.5-1; 3. P-GW to PCRF: IP-CAN session modification; 4. PCRF to BPCF: GW Control and QoS Rules provision; 5. PCRF to P-GW: IP-CAN session modification ackn; 6. P-GW to MME: steps 5-6 according to TS 23.401, figure 5.4.5-1.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +Sequence diagram for UE requested bearer resource modification. Lifelines: UE, HeNB, RG, BNG, Fixed Broadband Access (BPCF), SeGW, HeNB GW, MME, S-GW, P-GW, PCRF. The diagram shows 6 steps: 1. UE to MME: Request Bearer Resource Modification; 2. MME to P-GW: Steps 2-3 according to TS 23.401, figure 5.4.5-1; 3. P-GW to PCRF: IP-CAN session modification; 4. PCRF to BPCF: GW Control and QoS Rules provision; 5. PCRF to P-GW: IP-CAN session modification ackn; 6. P-GW to MME: steps 5-6 according to TS 23.401, figure 5.4.5-1. + +Figure 9.1.4: UE requested bearer resource modification + +1. The description of this step is the same as for step 1 in TS 23.401 [2], clause 5.4.5. +2. The description of this step is the same as for step 2-3 in TS 23.401 [2], clause 5.4.5. +3. The P-GW initiates the IP-CAN session modification procedure with the PCRF per TS 23.203 [4]. +4. The PCRF initiates the Gateway Control QoS Rules provision procedure with the BPCF to request allocation/de-allocation of BBF access network resources according to TS 23.203 [4]. +5. The PCRF acknowledges the IP-CAN session establishment/modification. +6. The description of this step is the same as for step 5-6 in TS 23.401 [2], clause 5.4.5. + +### 9.1.5 Service Request and Handover Procedures + +This clause specifies the Service Request and Handover Procedures with updating the following information to fixed broadband access network: the HeNB local IP address and the UDP port if NAT/NAPT is detected. + +This clause contains the following cases: + +- UE initiated Service Request( clause 5.3.4.1, TS 23.401 [2]) +- X2-based handover without Serving GW relocation(clause 5.5.1.1.2, TS 23.401 [2]), +- X2-based handover with Serving GW relocation(clause 5.5.1.1.3, TS 23.401 [2]), +- S1-based handover (clause 5.5.1.2.2 , TS 23.401 [2]), +- inter-RAT Handover from UTRAN Iu Mode to E-UTRAN (clause 5.5.2.2.2, TS 23.401 [2]), +- inter-RAT handover from GERAN A/Gb Mode to E-UTRAN(clause 5.5.2.4.2, TS 23.401 [2]). + +The MME shall report changes in HeNB local IP address and/or port to the PCEF/PCRF if + +- the PCRF has subscribed to reporting of changes of the local H(e)NB IP address and UDP port number; and +- the UE moves from one (e)NB to a HeNB, or from one HeNB to another HeNB with the fixed network backhaul changed, or the UE moves from a HeNB to a (e)NB. + +The MME does not update the PCEF/PCRF in particular when the UE enter connected mode if there is no change in HeNB local IP address and UDP port number, or when the UE enters idle mode. + +If the S-GW needs to update the PCEF/PCRF (e.g. send a Modify Bearer Request over S5/S8) for any other reasons not listed above (e.g. time zone change, S-GW relocation), the S-GW shall include the current values for H(e)NB local IP address and UDP port if the UE is accessing the network from a HeNB. + +This following call flow only shows the changed steps, and the steps without change can be referred to the corresponding clauses in TS 23.401 [2]. + +![Sequence diagram showing Service Request and Handover Procedures. Lifelines include UE, S-eNB/HeNB, T-eNB/HeNB, RG, BNG, Fixed Broadband Access (BPCF), SeGW, Target MME, Source MME, Target S-GW, Source S-GW, P-GW, and PCRF. The diagram illustrates steps 1 through 8, with steps 5 and 7 being dashed lines representing optional or specific procedures.](d6c377ae3e619ff992bd3647dbf43593_img.jpg) + +The diagram is a sequence diagram titled 'Service Request and Handover Procedures'. It shows the interaction between various network elements: UE, S-eNB/HeNB, T-eNB/HeNB, RG, BNG, Fixed Broadband Access (containing BPCF), SeGW, Target MME, Source MME, Target S-GW, Source S-GW, P-GW, and PCRF. The sequence of messages is as follows: + + +- 1. Triggers: Initiated by UE, S-eNB/HeNB, or T-eNB/HeNB. +- 2. S1 Message: Sent from T-eNB/HeNB to Target MME. +- 3. Create Session Request: Sent from Target MME to Target S-GW. +- 4. PCEF initiated IP-CAN session modification: Sent from P-GW to PCRF. +- 5. PCRF-Initiated Gateway control session establishment or Gateway Control and QoS Rules provisioning procedure: A dashed line interaction between PCRF and P-GW. +- 6. PCEF initiated IP-CAN session modification Ack: Sent from PCRF to P-GW. +- 7. Gateway control session termination: A dashed line interaction between PCRF and P-GW. +- 8. Corresponding procedure as in TS 23.401: A final step indicated at the bottom. + +Sequence diagram showing Service Request and Handover Procedures. Lifelines include UE, S-eNB/HeNB, T-eNB/HeNB, RG, BNG, Fixed Broadband Access (BPCF), SeGW, Target MME, Source MME, Target S-GW, Source S-GW, P-GW, and PCRF. The diagram illustrates steps 1 through 8, with steps 5 and 7 being dashed lines representing optional or specific procedures. + +Figure 9.1.5: Service Request and Handover Procedures + +1. UE initiated Service request procedure, or intra-EUTRAN Handover procedure, or inter-RAT handover is initiated, which can be referred to the descriptions of the corresponding clause4 in TS 23.401 [2]. +2. This step is the same as that in TS 23.401 [2], with the addition that target HeNB includes the following additional information: the target HeNB local IP address and the UDP port if NAT/NAPT is detected in the S1 message and sends them to MME. For the service request case, the S1 message carrying the "NAS: Service request" from UE to MME is Initial UE Message; for the X2 based handover case, the S1 message is the Path Switch Request message; for the S1 based handover or the inter-RAT handover, the S1 message is the Handover Notify Message. +3. This step is the same as that in TS 23.401 [2], with the following additional information included in create session request message or Modify bearer Request message sending between MME and S-GW, and Modify Bearer Request Message sending between S-GW and P-GW (when a Modify Bearer Request message needs to be sent over S5/S8): target HeNB Local IP address and the UDP port if NAT/NAPT is detected. +4. The P-GW sends IP-CAN session modification request message to the PCRF including the Target HeNB local IP address and the UDP port if NAT/NAPT is detected as defined in TS 23.203 [4]. + +If the Modify bearer Request message received by P-GW in step 3 contains none of the additional information: HeNB Local IP address and the UDP port if NAT/NAPT is detected. The P-GW determines that the UE leaves femto cell and will inform this event to PCRF. + +5. If the UE moves from eNB to a HeNB, the PCRF will initiate PCRF-initiated Gateway control session establishment procedure as defined in TS 23.203 [4] if the UE is the first UE attaching the target HeNB for that PCRF; if the UE moves from one HeNB to another HeNB without fixed network backhaul changed or if the UE moves to a new HeNB and there has been one Gateway Control Session for that HeNB, the PCRF will initiate Gateway control and QoS rule provisioning procedure with BPCF as defined in TS 23.203 [4]. The HeNB local IP address and the UDP port if NAT/NAPT is detected shall be included in the PCRF-Initiated Gateway control session establishment procedure and in Gateway Control and QoS rule provisioning procedure. +6. The PCRF acknowledges the IP-CAN session modification. + +- 7. If UE moves from one HeNB to eNB, the PCRF will terminate the old Gateway control session if this is the last UE under the source HeNB for that PCRF; if the UE moves from eNB to a HeNB, or the UE moves from one HeNB to another HeNB without fixed network backhaul changed, or there are other UEs attached the source HeNB, this step will be skipped. +- 8. This step can refer to the corresponding procedure as in TS 23.401 [2]. + +NOTE: The interaction between the BPCF and the BNG is out of scope. + +## 9.2 Procedures for Fixed Broadband Access network using HeNB - PMIP + +### 9.2.1 Initial E-UTRAN Attach with PMIP-based S5/S8 + +This clause is related to the case when the UE performs initial attachment to the E-UTRAN network via a HeNB. The HeNB is already registered in the network. + +The HeNB sends the HeNB local IP address and UDP port if NAT/NAPT is detected to the MME in UE associated S1 signalling (refer to the definition of Initial UE Message in TS 36.413 [29]). + +![Sequence diagram for Initial E-UTRAN attach with PMIP-based S5/S8. Lifelines: UE, HeNB, RG, BNG, BPCF, MME, S-GW, P-GW, vPCRF, hPCRF, HSS/AAA. The diagram shows HeNB registration followed by the attach procedure (step 1) and subsequent gateway control session establishment steps (C.1 to C.6).](854cb86f664ff62fd23e7607cfeb5727_img.jpg) + +The sequence diagram illustrates the interaction for an initial E-UTRAN attach with PMIP-based S5/S8. The lifelines are UE, HeNB, RG, BNG, BPCF, MME, S-GW, P-GW, vPCRF, hPCRF, and HSS/AAA. A dashed box labeled 'Fixed Broadband Access' contains RG, BNG, and BPCF. A shaded area labeled 'Roaming Scenarios' contains vPCRF and hPCRF. The process starts with 'HeNB registration' from HeNB to MME. Step 1 is 'Attach procedure as in TS 23.402, Figure 5.2-1'. This is followed by a series of control session establishment steps: C.1 Gateway Control Session Establishment Procedure (dashed box between S-GW and vPCRF), C.2 Proxy Binding Update (arrow from S-GW to P-GW), C.3 GW Control Session Establishment (dashed box between BPCF and vPCRF), C.4 Proxy Binding Ack (arrow from P-GW to S-GW), C.5 Gateway Control and QoS Rules Provision Procedure (dashed box between S-GW and vPCRF), and C.6 IP-CAN Session Establishment Procedure (dashed box between P-GW and vPCRF). The process concludes with another 'Attach procedure as in TS 23.402, Figure 5.2-1' from MME to UE. + +Sequence diagram for Initial E-UTRAN attach with PMIP-based S5/S8. Lifelines: UE, HeNB, RG, BNG, BPCF, MME, S-GW, P-GW, vPCRF, hPCRF, HSS/AAA. The diagram shows HeNB registration followed by the attach procedure (step 1) and subsequent gateway control session establishment steps (C.1 to C.6). + +Figure 9.2.1-1 : Initial E-UTRAN attach with PMIP-based S5/S8 + +This procedure is the same as described in TS 23 402 [3], clause 5.2 with the modification of the existing steps and addition of the new step described below. + +- 1. This step is the same as for attach procedures as in TS 23 402[3], figure 5.2-1, with the exception as defined for the corresponding steps for GTP case, clause 9.1.1. + +- C.1 The S-GW initiates the Gateway control session establishment procedure with the PCRF, and the following additional information: the HeNB local IP address and the UDP port if NAT/NAPT is detected needs to be forwarded to the PCRF during this procedure. +- C.3 The PCRF sends the Gateway Control Session establishment/QoS Rules provisioning message to the BPCF according to TS 23.203 [4]. The message includes the IMSI, HeNB local IP address and UDP port if NAT/NAPT is detected. + +Once this procedure completes the PCRF is aware the fact that the UE is connected to the network via the a 3GPP Femto and checks first whether sufficient resources are available in the BBF access before it provisions QoS and PCC rules at the BBER and PCEF, respectively. + +### 9.2.2 Detach for PMIP-based S5/S8 + +The procedure in this clause provides the PMIPv6-based S5/S8 variants to all E-UTRAN Detach Procedures, including UE, MME or HSS initiated detach procedure (TS 23.401 [2] clause 5.3.8). + +![Sequence diagram for E-UTRAN Detach Procedure for PMIP-based S5/S8. The diagram shows the interaction between UE, HeNB, RG, BNG, BPCF, MME, Serving GW, PDN GW, vPCRF, hPCRF, and HSS/AAA. A dashed box labeled 'Fixed Broadband Access' contains RG, BNG, and BPCF. A shaded area labeled 'Roaming Scenario' contains vPCRF and hPCRF. The procedure starts with a 'Detach procedure as per TS 23.402 Figure 5.3, before step A.1'. Step A.1 is 'Gateway Control Session Termination Procedure' between Serving GW and vPCRF. Step A.2 is 'Proxy Binding Update' from Serving GW to PDN GW. Step A.3 is 'PCEF-Initiated IP-CAN Session Termination Procedure' between PDN GW and vPCRF. Step A.4 is 'Gateway Control Session Termination/QoS rules Provisioning Procedure' between vPCRF and BPCF. Step A.5 is 'Proxy Binding Ack' from PDN GW to Serving GW. The procedure ends with 'Detach procedure as TS 23.402 Figure 5.3, after step A.4'.](1399c76ef88f22b70d05ed3f781d3c48_img.jpg) + +Sequence diagram for E-UTRAN Detach Procedure for PMIP-based S5/S8. The diagram shows the interaction between UE, HeNB, RG, BNG, BPCF, MME, Serving GW, PDN GW, vPCRF, hPCRF, and HSS/AAA. A dashed box labeled 'Fixed Broadband Access' contains RG, BNG, and BPCF. A shaded area labeled 'Roaming Scenario' contains vPCRF and hPCRF. The procedure starts with a 'Detach procedure as per TS 23.402 Figure 5.3, before step A.1'. Step A.1 is 'Gateway Control Session Termination Procedure' between Serving GW and vPCRF. Step A.2 is 'Proxy Binding Update' from Serving GW to PDN GW. Step A.3 is 'PCEF-Initiated IP-CAN Session Termination Procedure' between PDN GW and vPCRF. Step A.4 is 'Gateway Control Session Termination/QoS rules Provisioning Procedure' between vPCRF and BPCF. Step A.5 is 'Proxy Binding Ack' from PDN GW to Serving GW. The procedure ends with 'Detach procedure as TS 23.402 Figure 5.3, after step A.4'. + +**Figure 9.2.2-1: E-UTRAN Detach Procedure for PMIP-based S5/S8** + +This procedure is the same as described in TS 23 402 [3], clause 5.3 with the addition of the new step described below. + +- A.4. The PCRF initiates the Gateway Control session termination/ QoS Rules Provisioning procedure with BPCF according to TS 23.203 [4]. + +NOTE: The interaction between the BPCF and the BNG is out of scope. + +### 9.2.3 Dedicated Bearer Procedures for E-UTRAN Access with PMIP-based S5/S8 + +The dedicated bearer procedure for a PMIP based S5/S8 is based on TS 23 402 [3], clause 5.4.1 It applies to dedicated bearer activation/modification/deactivation procedures. + +![Sequence diagram for Figure 9.2.3-1: Dedicated Resource Allocation/Deallocation Procedure, UE in Active Mode. The diagram shows interactions between UE, H(e)N, RG, BNG, BPCF, MME, S-GW, PDN GW, vPCRF, and hPCRF. A 'Fixed Broadband Access' group contains RG, BNG, and BPCF. A 'Roaming Scenario' group contains vPCRF and hPCRF. The sequence starts with a 'Dedicated bearer procedure according to TS 23.401, Figure 5.4.{1,3}-1 and 5.4.2.1-1 and 5.4.4.1-1, between (A) and (B)'. This is followed by 'A.0 Gateway Control and QoS Rules provisioning Term/Proc' between BPCF and vPCRF. Then 'A.1. Gateway Control and QoS Policy Rules Provision Procedure - begin' between vPCRF and hPCRF. Next is 'B.1. Gateway Control and QoS Policy Rules Provision Procedure - end' between hPCRF and vPCRF. Finally, 'B.2 PCC Rules Provision Procedure' is shown between vPCRF and hPCRF.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +Sequence diagram for Figure 9.2.3-1: Dedicated Resource Allocation/Deallocation Procedure, UE in Active Mode. The diagram shows interactions between UE, H(e)N, RG, BNG, BPCF, MME, S-GW, PDN GW, vPCRF, and hPCRF. A 'Fixed Broadband Access' group contains RG, BNG, and BPCF. A 'Roaming Scenario' group contains vPCRF and hPCRF. The sequence starts with a 'Dedicated bearer procedure according to TS 23.401, Figure 5.4.{1,3}-1 and 5.4.2.1-1 and 5.4.4.1-1, between (A) and (B)'. This is followed by 'A.0 Gateway Control and QoS Rules provisioning Term/Proc' between BPCF and vPCRF. Then 'A.1. Gateway Control and QoS Policy Rules Provision Procedure - begin' between vPCRF and hPCRF. Next is 'B.1. Gateway Control and QoS Policy Rules Provision Procedure - end' between hPCRF and vPCRF. Finally, 'B.2 PCC Rules Provision Procedure' is shown between vPCRF and hPCRF. + +**Figure 9.2.3-1: Dedicated Resource Allocation/Deallocation Procedure, UE in Active Mode** + +This procedure is the same as described in TS 23 402 [3], clause 5.4.1 with the addition of the new step described below: + +- A.0 The PCRF initiates the GW Control and QoS Provisioning procedure with the BPCF to request or de-allocate resources in the BBF access network. The message to request resources includes the QoS Information (SDF, QCI, ARP, GBR, MBR) according to TS 23.203 [4]. + +### 9.2.4 HSS-Initiated Subscribed QoS Modification + +The HSS triggers a change to the default bearer QoS attributes that, depending on the decision of the PCRF, may impact the resources allocated in the BBF access. + +The HSS Initiated Subscribed QoS Modification for a PMIP-based S5/S8 is depicted in TS 23 402 [3], Figure 5.4.3.2-1. + +![Sequence diagram for Figure 9.2.4-1: HSS-initiated Subscribed QoS Modification. The diagram shows interactions between UE, eNB, RG, BNG, BPCF, MME, S-GW, P-GW, vPCRF, hPCRF, and HSS. A 'Fixed Broadband Access' group contains RG, BNG, and BPCF. A 'Roaming Scenario' group contains vPCRF and hPCRF. The sequence starts with 'Procedure according to TS 23.401, Figure 5.4.2.2-1, before Step (A)'. This is followed by 'A.1 GW Control and QoS Policy Rules Request Procedure - begin' between S-GW and vPCRF. Then 'A.2 Gateway Control and QoS Rules provisioning Term/Proc' between BPCF and vPCRF. Next is 'A.3 PCC Rules Provision Procedure' between vPCRF and hPCRF. Then 'B.1 Gateway Control and QoS Policy Rules Request Procedure - end' between hPCRF and vPCRF. Finally, 'B.2 PCC Rules Provision Procedure' is shown between vPCRF and hPCRF. A 'Bearer procedure according to TS 23.401, Figure 5.4.2.2-1, between steps (A) and (B)' is indicated between the initial procedure and step A.1.](8fe84519a7da727cc2a27873b3389a52_img.jpg) + +Sequence diagram for Figure 9.2.4-1: HSS-initiated Subscribed QoS Modification. The diagram shows interactions between UE, eNB, RG, BNG, BPCF, MME, S-GW, P-GW, vPCRF, hPCRF, and HSS. A 'Fixed Broadband Access' group contains RG, BNG, and BPCF. A 'Roaming Scenario' group contains vPCRF and hPCRF. The sequence starts with 'Procedure according to TS 23.401, Figure 5.4.2.2-1, before Step (A)'. This is followed by 'A.1 GW Control and QoS Policy Rules Request Procedure - begin' between S-GW and vPCRF. Then 'A.2 Gateway Control and QoS Rules provisioning Term/Proc' between BPCF and vPCRF. Next is 'A.3 PCC Rules Provision Procedure' between vPCRF and hPCRF. Then 'B.1 Gateway Control and QoS Policy Rules Request Procedure - end' between hPCRF and vPCRF. Finally, 'B.2 PCC Rules Provision Procedure' is shown between vPCRF and hPCRF. A 'Bearer procedure according to TS 23.401, Figure 5.4.2.2-1, between steps (A) and (B)' is indicated between the initial procedure and step A.1. + +**Figure 9.2.4-1 HSS-initiated Subscribed QoS Modification** + +This procedure is the same as described in TS 23 402 [3], clause 5.4.3.2 with the addition of the new step described below: + +- A.2. The PCRF initiates the GW Control and QoS Provisioning procedure with the BPCF to either request allocation/de-allocation of BBF resources. The message includes the QoS Information (QCI, ARP, GBR, MBR) according to TS 23.203 [4]. + +### 9.2.5 MME-initiated Dedicated Bearer Deactivation + +This clause contains the procedure steps that vary between the GTP and PMIP variant of S5 and S8 for the procedure defined in TS 23.401 [2], clause 5.4.4.2 for -MME initiated dedicated bearer deactivation. + +![Sequence diagram for MME-initiated Dedicated Bearer Deactivation. The diagram shows the interaction between UE, eNB, RG, BNG, BPCF, MME, S-GW, PDN GW, vPCRF, and hPCRF. A dashed box labeled 'Fixed Broadband Access' contains RG, BNG, and BPCF. A shaded area labeled 'Roaming Scenarios' contains vPCRF and hPCRF. The sequence starts with a message from MME to S-GW: 'Dedicated bearer deactivation procedure according to TS 23.401, Figure 5.4.4.2-1, before Steps (A)'. From S-GW, three dashed arrows point to PDN GW: 'A.1 GW Control and QoS Rules Request Procedure', 'A.2 Gateway Control and QoS Rules provisioning Proc', and 'A.3 PCC Rules Provision Procedure'. From PDN GW, a dashed arrow points to vPCRF. At the bottom, a box spans from UE to PDN GW with the text: 'Dedicated bearer deactivation procedure according to TS 23.401, Figure 5.4.4.2-1, between Steps (A) and (B)'.](0f7871077bba48a2c97f7859a5edda0d_img.jpg) + +Sequence diagram for MME-initiated Dedicated Bearer Deactivation. The diagram shows the interaction between UE, eNB, RG, BNG, BPCF, MME, S-GW, PDN GW, vPCRF, and hPCRF. A dashed box labeled 'Fixed Broadband Access' contains RG, BNG, and BPCF. A shaded area labeled 'Roaming Scenarios' contains vPCRF and hPCRF. The sequence starts with a message from MME to S-GW: 'Dedicated bearer deactivation procedure according to TS 23.401, Figure 5.4.4.2-1, before Steps (A)'. From S-GW, three dashed arrows point to PDN GW: 'A.1 GW Control and QoS Rules Request Procedure', 'A.2 Gateway Control and QoS Rules provisioning Proc', and 'A.3 PCC Rules Provision Procedure'. From PDN GW, a dashed arrow points to vPCRF. At the bottom, a box spans from UE to PDN GW with the text: 'Dedicated bearer deactivation procedure according to TS 23.401, Figure 5.4.4.2-1, between Steps (A) and (B)'. + +**Figure 9.2.5-1: MME-initiated Dedicated Bearer Deactivation** + +This procedure is the same as described in TS 23 402 [3], clause 5.4.5.3 with the addition of the new step described below: + +- A.2 The PCRF initiates the GW Control and QoS Provisioning procedure with the BPCF to either request de-allocation of BBF resources for the affected QoS rule(s) according to TS 23.203 [4]. + +### 9.2.6 UE-initiated Resource Request and Release + +This procedure is executed per TS 23 402 [3], clause 5.5, with modifications, when the PCRF determines that the UE's request result in allocation/de-allocation of resources in the BBF access. + +![Sequence diagram for UE-initiated resource request/release with PMIP-based S5/S8. The diagram shows interactions between UE, Fixed Broadband Access (RG, BNG, BPCF), Serving GW, PDN GW, vPCRF, and hPCRF. A shaded area labeled 'Roaming Scenarios' covers the vPCRF and hPCRF lifelines. The sequence starts with a UE request, followed by Gateway Control and QoS Rules Request (A.1), Gateway Control and QoS Rules provisioning Proc (A.2), a Dedicated bearer activation/modification procedure, Gateway Control and QoS Policy Rules Request (B.1), and PCC Rules Provision Procedure (B.2).](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +The diagram illustrates a sequence of interactions between the following entities: UE, Fixed Broadband Access (comprising RG, BNG, and BPCF), Serving GW, PDN GW, and PCRF (vPCRF and hPCRF in roaming scenarios). Key steps include: + +- UE requested bearer resource modification procedure according to TS 23.401 Figure 5.4.5-1 before Step A. +- A.1 Gateway Control and QoS Rules Request - begin (between Serving GW and PCRF). +- A.2 Gateway Control and QoS Rules provisioning Proc (between PCRF and BPCF). +- Dedicated bearer activation/modification procedure according to TS 23.401, Figure 5.4.{1, 2.1, 2.2, 3}-1 between Step A and B; or Dedicated bearer deactivation procedure as per figure 5.4.4.1-1 from Steps 3a to Step 8a. +- B.1 Gateway Control and QoS Policy Rules Request - end (between Serving GW and PCRF). +- B.2 PCC Rules Provision Procedure (between PDN GW and PCRF). + +Sequence diagram for UE-initiated resource request/release with PMIP-based S5/S8. The diagram shows interactions between UE, Fixed Broadband Access (RG, BNG, BPCF), Serving GW, PDN GW, vPCRF, and hPCRF. A shaded area labeled 'Roaming Scenarios' covers the vPCRF and hPCRF lifelines. The sequence starts with a UE request, followed by Gateway Control and QoS Rules Request (A.1), Gateway Control and QoS Rules provisioning Proc (A.2), a Dedicated bearer activation/modification procedure, Gateway Control and QoS Policy Rules Request (B.1), and PCC Rules Provision Procedure (B.2). + +**Figure 9.2.6-1: UE-initiated resource request/release with PMIP-based S5/S8** + +This procedure is the same as described in TS 23 402 [3], clause 5.5 with the addition of the new step described below. + +The UE requests to add, delete or modify filter and may include the QCI and GBR if needed. Depending on the decision of the PCRF new BBF resource may be required. For instance, the PCRF may decide to initiate the activation of a new dedicated bearer. + +- A.2. The PCRF initiates the GW Control and QoS Provisioning procedure with the BPCF to, depending on the UE's request, either request allocation/de-allocation of BBF resources. If resources are de-allocated the message includes the QoS rule affected. If additional BBF resources are required then the PCRF includes the QoS rule and QoS Information (SDF, QCI, ARP, GBR, MBR) according to TS 23.203 [4]. + +NOTE: The interaction between the BPCF and the BNG is out of scope. + +### 9.2.7 UE requested PDN connectivity + +The UE requested PDN connectivity procedure for E-UTRAN is depicted in figure 5.6.1-1, TS 23 402 [3]. The procedure allows the UE connected to a HeNB to request for connectivity to an additional PDN over E-UTRAN. + +![Sequence diagram for UE requested PDN connectivity with PMIP-based S5 or S8. The diagram shows interactions between UE, HeNB, Fixed Broadband Access (RG, BNG, BPCF), MME, S-GW, PDN GW, Roaming Scenarios vPCRF, hPCRF, and HSS/AAA. It is divided into three main phases: before step (A), between step (A) and step (B), and after step (B). Phase 'before step (A)' includes Alt. A with sub-procedures A.1 through A.5. Phase 'between step (A) and step (B)' includes Alt. B with sub-procedures B.1 through B.4. Phase 'after step (B)' shows the R-session establishment between BNG and PDN GW.](ffb6acd27b8e3a54392840948a75869f_img.jpg) + +Sequence diagram for UE requested PDN connectivity with PMIP-based S5 or S8. The diagram shows interactions between UE, HeNB, Fixed Broadband Access (RG, BNG, BPCF), MME, S-GW, PDN GW, Roaming Scenarios vPCRF, hPCRF, and HSS/AAA. It is divided into three main phases: before step (A), between step (A) and step (B), and after step (B). Phase 'before step (A)' includes Alt. A with sub-procedures A.1 through A.5. Phase 'between step (A) and step (B)' includes Alt. B with sub-procedures B.1 through B.4. Phase 'after step (B)' shows the R-session establishment between BNG and PDN GW. + +**Figure 9.2.7-1: UE requested PDN connectivity with PMIP-based S5 or S8** + +This procedure is the same as described in TS 23 402 [3], clause 5.6.1 with modification of the existing steps and the addition of the new step described below. + +The procedure is executed when the UE requests an additional PDN connection or re-establishes an existing one after a HO. + +- This step is the same as for PDN connectivity procedures as in TS 23.401 [2], figure 5.10.2-1 before step (A), with the exception as defined for the corresponding steps for GTP case, clause 9.1.1. + +- The description of this step is the same as step C.1 in clause 9.2.1. + +If Alt.A is selected then the PCRF executes step A.4. + +- The PCRF initiates the GW Control and QoS Provisioning procedure with the BPCF to modify BBF resources associated with an existing QoS rules or to request new BBF resources. In either case the message includes the QoS Information (SDF, QCI, ARP, GBR, MBR) according to TS 23.203 [4]. + +If Alt.B is selected then the PCRF executes step B.3. + +- The PCRF initiates the GW Control and QoS Provisioning procedure with the BPCF to modify BBF resources associate with an existing QoS rule. The message includes the QoS Information (SDF, QCI, ARP, GBR, MBR) according to TS 23.203 [4]. + +NOTE: The interaction between the BPCF and the BNG is out of scope. + +### 9.2.8 Service Request and Handover Procedures + +This clause specifies the Service Request and Handover Procedures with updating the following information to Fixed Broadband Access network: the HeNB local IP address and the UDP port if NAT/NAPT is detected. + +This clause is similar to clause 9.1.5, with the difference that the S5/8 interface is PMIP-based. This following call flow only shows the description on S5/S8 interfaces and Gx/Gxx/S9a interfaces. + +![Sequence diagram for Service Request and Handover Procedures-S5/S8 PMIP-based. The diagram shows interactions between UE, Source eNB/HeNB, Target eNB/HeNB, RG, BNG, SeGW, BPCF, Target MME, Source MME, Target SGW, Source SGW, PDN GW, and PCRF. The sequence is divided into six numbered steps: 1. Steps 1-3 of Service Request and Handover Procedures (clause 9.1.10); 2. Gateway Control Session Establishment or Gateway Control and QoS Rule Request Procedure (Target SGW to PCRF); 3. PCRF initiated Gateway Control Session Establishment or Gateway Control and QoS Rule Provisioning Procedure (PCRF to Target SGW); 4. Procedures as defined in TS 23.402 (Target SGW to PDN GW); 5. Gateway Session Termination Procedure (PCRF to Target SGW); 6. Step 8 of Service Request and Handover Procedure (clause 9.1.10).](bc6f20871b4f01c61470306c304fc9fe_img.jpg) + +Sequence diagram for Service Request and Handover Procedures-S5/S8 PMIP-based. The diagram shows interactions between UE, Source eNB/HeNB, Target eNB/HeNB, RG, BNG, SeGW, BPCF, Target MME, Source MME, Target SGW, Source SGW, PDN GW, and PCRF. The sequence is divided into six numbered steps: 1. Steps 1-3 of Service Request and Handover Procedures (clause 9.1.10); 2. Gateway Control Session Establishment or Gateway Control and QoS Rule Request Procedure (Target SGW to PCRF); 3. PCRF initiated Gateway Control Session Establishment or Gateway Control and QoS Rule Provisioning Procedure (PCRF to Target SGW); 4. Procedures as defined in TS 23.402 (Target SGW to PDN GW); 5. Gateway Session Termination Procedure (PCRF to Target SGW); 6. Step 8 of Service Request and Handover Procedure (clause 9.1.10). + +**Figure 9.2.8-1: Service Request and Handover Procedures-S5/S8 PMIP-based** + +1. UE initiated Service request procedure, or intra-EUTRAN Handover procedure, or inter-RAT handover is initiated, which can be referred to the corresponding descriptions of clause 9.1.5, Service Request and Handover Procedures (GTP case). +2. The (target) S-GW initiates the Gateway control session establishment (with S-GW relocated) procedure or Gateway Control and QoS Rule Request procedure (without S-GW relocated) with the PCRF, and the following additional information: the HeNB local IP address and the UDP port if NAT/NAPT is detected needs to be forwarded to the PCRF during this procedure. + +If the Create Session Request message (with S-GW relocated) or Modify bearer Request message (without S-GW relocated) received by S-GW in step 1 contains none of the additional information: HeNB Local IP address and the UDP port if NAT/NAPT is detected The S-GW determines that the UE leaves femto cell and will inform this event to PCRF. + +3. The description of this step is the same as step 5 in clause 9.1.5. +4. This step is the same as the corresponding steps defined in handover procedures for PMIP-based S5/S8 interface clause 5.7, and UE-triggered Service Request for PMIP-based S5/S8, clause 5.9, TS 23 402 [3]. The description of this step is the same as step 7 in clause 9.1.5. +5. This step can refer to the corresponding procedure as in clause 9.1.5. + +NOTE: The description is the same as note 2 and note 3 in clause 9.1.5. + +## 9.3 Procedures for Fixed Broadband Access network using HNB for PS services + +### 9.3.1 PDP Context Activation + +The HNB is already registered in the network. The HNB GW sends the HNB local IP address and the UDP port number if NAT/NAPT is detected to the SGSN in the [RANAP] INITIAL UE MESSAGE message (for the message refer to TS 25.413 [28]). + +Depicted in Figure 9.3.1-1 is the PDP Context Activation procedure. + +![Sequence diagram showing the PDP Context Activation Procedure for EPS-connected 3G access. Lifelines include UE, HNB, RG, BNG, Fixed Broadband Access (BPCF), HNB GW, SGSN, S-GW, P-GW, and PCRF. The process starts with '0. HNB connected' and ends with '8. Activate PDP Context Accept'.](18dbea0ac6b7ad13e47afda3ddd53b64_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HNB + participant RG + participant BNG + participant FBA as Fixed Broadband Access (BPCF) + participant HNB_GW as HNB GW + participant SGSN + participant S_GW as S-GW + participant P_GW + participant PCRF + Note right of HNB: SeGW + + Note over HNB, HNB_GW: 0. HNB connected + HNB_GW->>SGSN: 1. Activate PDP Context Request + SGSN->>S_GW: 2. Create Session Request + S_GW->>P_GW: 3. IP-CAN session establishment + P_GW->>PCRF: 4. PCRF-Initiated Gateway Control Session Establishment + PCRF->>P_GW: 5. IP-CAN session establishment Ack + P_GW->>SGSN: 6. Create Session Response + Note over HNB, SGSN: 7. Procedures according to TS 23.060 [22], Figure 64 from step 5 to 8 + SGSN->>UE: 8. Activate PDP Context Accept + +``` + +Sequence diagram showing the PDP Context Activation Procedure for EPS-connected 3G access. Lifelines include UE, HNB, RG, BNG, Fixed Broadband Access (BPCF), HNB GW, SGSN, S-GW, P-GW, and PCRF. The process starts with '0. HNB connected' and ends with '8. Activate PDP Context Accept'. + +**Figure 9.3.1-1: PDP Context Activation Procedure for EPS-connected 3G access** + +- 0. The HNB connected. The HNB GW received the HNB Local IP address and the UDP port number if NAT/NAPT is detected. +- 1. This step is the same as step 1 in TS 23.060 [22] clause 9.2.2.1, with the addition that the HNB GW includes in the [RANAP] INITIAL UE MESSAGE message the HNB Local IP address and the UDP port number if NAT/NAPT is detected. +- 2. This step is the same as step A in TS 23.060 [22] clause 9.2.2.1A, with the addition that the S4-SGSN also includes HNB Local IP address and the UDP port number if NAT/NAPT is detected in the Create Session Request sent to the S-GW and in turn to P-GW. +- 3. The P-GW sends the IP-CAN session establishment request to the PCRF according to TS 23.203 [4]. The message includes HNB Local IP address and the UDP port number if NAT/NAPT is detected. +- 4. The PCRF sends the Gateway Control Session establishment message to the BPCF according to TS 23.203 [4]. The message includes the IMSI, HNB local IP address, the UDP port number if NAT/NAPT is detected. + +Once this step completes the PCRF is aware the fact that the UE is connected to the network via a 3GPP H(e)NB and checks first whether sufficient resources are available in the BBF access before it provisions PCC rules at the P-GW. + +- 5. The PCRF acknowledges the IP-CAN session establishment ack to the P-GW. +- 6. This step is the same as step D in TS 23.060 [22] clause 9.2.2.1A Figure 64a with the following additions. If the local H(e)NB IP address and UDP port number information change reporting triggers are received from the PCRF, the PDN GW should set the H(e)NB local IP address and UDP port number reporting accordingly. If the + +H(e)NB local IP address and UDP port number Reporting Request is received for this PDP context, then the SGSN shall report to the PCEF/PCRF changes of HNB local IP address and/or port (if available). + +7-8. Steps 7 and 8 are the same as steps 4-9 in TS 23.060 [22] clause 9.2.2.1 Figure 64. + +**Editor's note:** In order to handle mobility from macro cells, the tunnel information needs to be added in other RANAP messages (RELOCATION COMPLETE and INITIAL UE MESSAGE). + +### 9.3.2 Secondary PDP Context Activation and PDP Context Modification Procedure + +This procedure is executed when secondary PDP context is activated and QoS needs to be allocated to it or when PDP context/bearer is modified and its QoS needs to be updated. This clause contains the following cases: + +- Secondary PDP Context Activation Procedure, PDP Creation part, using S4 (TS 23.060 [22], clause 9.2.2.1.1A). +- Network Requested Secondary PDP Context Activation Procedure using S4 (TS 23.060 [22], clause 9.2.2.3A). +- SGSN-Initiated EPS Bearer Modification Procedure using S4 (TS 23.060 [22], clause 9.2.3.1A and clause 9.2.3.1B). +- P-GW Initiated EPS Bearer Modification Procedure, using S4 (TS 23.060 [22], clause 9.2.3.2A). +- UE-Initiated EPS Bearer Modification Procedure using S4 (TS 23.060 [22], clause 9.2.3.3A , clause 9.2.3.3B and clause 9.2.3.3C). + +Depicted in Figure 9.3.2-1 is the corresponding procedure. It only shows the changed steps, and the steps without change can be referred to the corresponding clauses in TS 23.060 [22]. + +![Sequence diagram for Secondary PDP context Activation or PDP Context Modification Procedure for EPS-connected 3G access. The diagram shows interactions between UE, HNB, RG, BNG, Fixed Broadband Access (SeGW, BPCF), HNB GW, SGSN, S-GW, P-GW, and PCRF. Step 1 is a common procedure. Step 2 is 'GW Control and QoS Rule Provisioning' from PCRF to BPCF. Step 3 is 'IP-CAN session modification' from PCRF to P-GW. Step 4 is another common procedure.](ec31af936fa94a6917bf19f154df8ac3_img.jpg) + +The diagram illustrates the sequence of messages for the Secondary PDP context Activation or PDP Context Modification Procedure. The entities involved are UE, HNB, RG, BNG, Fixed Broadband Access (containing SeGW and BPCF), HNB GW, SGSN, S-GW, P-GW, and PCRF. The sequence is as follows: + +1. Corresponding procedure as in TS 23.060 (a wide bar spanning from UE to P-GW). +2. GW Control and QoS Rule Provisioning (dashed arrows from PCRF to BPCF). +3. IP-CAN session modification (dashed arrows from PCRF to P-GW). +4. Corresponding procedure as in TS 23.060 (a wide bar spanning from UE to P-GW). + +Sequence diagram for Secondary PDP context Activation or PDP Context Modification Procedure for EPS-connected 3G access. The diagram shows interactions between UE, HNB, RG, BNG, Fixed Broadband Access (SeGW, BPCF), HNB GW, SGSN, S-GW, P-GW, and PCRF. Step 1 is a common procedure. Step 2 is 'GW Control and QoS Rule Provisioning' from PCRF to BPCF. Step 3 is 'IP-CAN session modification' from PCRF to P-GW. Step 4 is another common procedure. + +**Figure 9.3.2-1: Secondary PDP context Activation or PDP Context Modification Procedure for EPS-connected 3G access** + +1. This step is the same as the corresponding procedure in TS 23.060 [22]. + +For UE-Initiated secondary PDP context activation procedure, refer to steps A and B in TS 23.060 [22], clause 9.2.2.1.1A. For UE-Initiated bearer modification procedure, refer to clause 9.2.3.3A, Figure 72c. For SGSN-Initiated bearer modification procedure, refer to steps A and B in clause 9.2.3.1A, Figure 70c. For all cases, the P-GW sends a QoS authorization request to the PCRF. + +2. The PCRF initiates Gateway control and QoS rule provision procedure with the BPCF in order to update the resources allocation in the BBF access network as per TS 23.203 [4], Annex P.7.4.1. +3. IP-CAN session modification procedure is performed by the PCRF to provide PCC rule(s) to the P-GW. + +- The execution and response part of UE-Initiated secondary PDP context activation are the same as steps C to F in TS 23.060 [22], clause 9.2.2.1.1A. For network requested secondary PDP context activation, refer to clause 9.2.2.3A. For UE-Initiated bearer modification procedure, refer to clause 9.2.3.3B and clause 9.2.3.3C. For SGSN-Initiated bearer modification procedure, refer to steps C and D in clause 9.2.3.1A. For P-GW or PCRF-Initiated bearer modification procedure, refer to clause 9.2.3.2A. + +### 9.3.3 Detach, PDP Context and EPS-Bearer Deactivation Procedures + +This procedure is executed when the PDP context or EPS-bearer is released. This clause contains the following cases: + +- SGSN interaction during Detach Procedure when using S4 (clause 6.6.3, TS 23.060 [22]) +- UE and SGSN Initiated PDN connection Deactivation Procedure using S4 (clause 9.2.4.1A.1, TS 23.060 [22]) +- UE and SGSN Initiated Bearer Deactivation Procedure (clause 9.2.4.1A.2, TS 23.060 [22]) +- P-GW initiated Bearer Deactivation Procedure using S4 (clause 9.2.4.3A and clause 9.2.4.3B, TS 23.060 [22]) + +Depicted in Figure 9.3.4-1 is the Detach or PDP Context/Bearer Deactivation procedure. It only shows the changed steps, and the steps without change can be referred to the corresponding clauses in TS 23.060 [22]. + +![Sequence diagram of PDP Context/Bearer Deactivation Procedure for EPS-connected 3G access. The diagram shows interactions between UE, HNB, RG, BNG, Fixed Broadband Access (SeGW, BPCF), HNB GW, SGSN, S-GW, P-GW, and PCRF. The procedure is divided into four steps: 1. Corresponding procedure as in TS 23.060; 2. IP-CAN session modification/termination (P-GW to PCRF); 3. GW Control and QoS Rule Provisioning / GW Control session termination (P-GW to BPCF); 4. Corresponding procedure as in TS 23.060.](59121d561a4158609b4c354b9ffd0605_img.jpg) + +Sequence diagram of PDP Context/Bearer Deactivation Procedure for EPS-connected 3G access. The diagram shows interactions between UE, HNB, RG, BNG, Fixed Broadband Access (SeGW, BPCF), HNB GW, SGSN, S-GW, P-GW, and PCRF. The procedure is divided into four steps: 1. Corresponding procedure as in TS 23.060; 2. IP-CAN session modification/termination (P-GW to PCRF); 3. GW Control and QoS Rule Provisioning / GW Control session termination (P-GW to BPCF); 4. Corresponding procedure as in TS 23.060. + +**Figure 9.3.3-1: PDP Context/Bearer Deactivation Procedure for EPS-connected 3G access** + +- This step is the same as the corresponding procedure in TS 23.060 [22]. (For Detach procedure, refer to steps A and B in clause 6.6.3; For UE or SGSN initiated PDN connection deactivation, refer to steps A and B in clause 9.2.4.1A.1; For UE or SGSN initiated bearer deactivation, refer to steps A and B in clause 9.2.4.1A.2). +- For the UE detaches from the network or the PDN connection deactivation case, the P-GW initiates IP-CAN session termination with the PCRF. Otherwise, the P-GW initiates IP-CAN session modification with the PCRF. +- The PCRF initiates the Gateway Control and QoS Rule provision procedure or the Gateway control session termination with the BPCF in order to release resources in the BBF access network as per Annex P.7.4.1, TS 23.203 [4]. +- This step can refer to the corresponding procedure as in TS 23.060 [22]. For Detach procedure, refer to Steps C and D in clause 6.6.3. For UE or SGSN initiated bearer deactivation, refer to Steps C to F in clause 9.2.4.1A.2. For UE or SGSN initiated PDN connection deactivation, refer to Steps C and D in clause 9.2.4.1A.1. For P-GW or PCRF initiated bearer deactivation, refer to clause 9.2.4.3A and clause 9.2.4.3B. + +### 9.3.4 Service Request and Handover Procedures + +This clause specifies the Service Request and Handover Procedures with updating the following information to fixed broadband access network: the HNB local IP address and the UDP port if NAT/NAPT is detected. + +This clause contains the following cases: + +- Inter SGSN Routeing Area Update and Combined Inter SGSN RA / LA Update using S4 (TS 23.060 [22], clause 6.9.1.2.2a). +- Routeing Area Update Procedure using S4 (TS 23.060 [22], clause 6.9.2.1a). +- Serving RNS Relocation Procedure, Combined Hard Handover and SRNS Relocation Procedure, and Combined Cell / URA Update and SRNS Relocation Procedure Using S4 (TS 23.060 [22], clause 6.9.2.2.1a). +- Enhanced Serving RNS Relocation Procedure using S4 (TS 23.060 [22], clause 6.9.2.2.5a). +- UE Initiated Service Request Procedure Using S4 (TS 23.060 [22], clause 6.12.1A). +- Iu mode to A/Gb mode Intra SGSN Change using S4 (TS 23.060 [22], clause 6.13.1.1.2). +- A/Gb mode to Iu mode Intra-SGSN Change using S4 (TS 23.060 [22], clause 6.13.1.2.2). +- Iu mode to A/Gb mode Inter-SGSN Change using S4 (TS 23.060 [22], clause 6.13.2.1.2). +- A/Gb mode to Iu mode Inter-SGSN Change using S4 (TS 23.060 [22], clause 6.13.2.2.2). + +Depicted in Figure 9.3.5-1 is the service request or handover procedure. It only shows the changed steps, and the steps without change can be referred to the corresponding clauses in TS 23.060 [22]. + +![Sequence diagram for Service Request and Handover Procedures for EPS-connected 3G access. The diagram shows interactions between UE, S-NB/HNB, T-NB/HNB, RG, BNG, Fixed Broadband Access (SeGW, BPCF), Target SGSN, Source SGSN, Target S-GW, Source S-GW, P-GW, and PCRF. The sequence starts with '1. Triggers' from the UE. Step 2a shows 'Create session request/modify bearer request' from Target SGSN to Target S-GW. Step 2b shows 'Modify bearer request' from Target S-GW to P-GW. Step 3 shows 'PCEF initiated IP-CAN session modification' from P-GW to PCRF. Step 4 shows 'PCRF-Initiated Gateway control session establishment or Gateway Control and QoS Rules provisioning procedure' between PCRF and P-GW. Step 5 shows 'PCEF initiated IP-CAN session modification Ack' from PCRF to P-GW. Step 6 shows 'Gateway control session termination' from P-GW to Target S-GW. Step 7 is a placeholder for 'Corresponding procedure as in TS 23.060'.](4537891530c9f6f139a2e1ebf544edc4_img.jpg) + +Sequence diagram for Service Request and Handover Procedures for EPS-connected 3G access. The diagram shows interactions between UE, S-NB/HNB, T-NB/HNB, RG, BNG, Fixed Broadband Access (SeGW, BPCF), Target SGSN, Source SGSN, Target S-GW, Source S-GW, P-GW, and PCRF. The sequence starts with '1. Triggers' from the UE. Step 2a shows 'Create session request/modify bearer request' from Target SGSN to Target S-GW. Step 2b shows 'Modify bearer request' from Target S-GW to P-GW. Step 3 shows 'PCEF initiated IP-CAN session modification' from P-GW to PCRF. Step 4 shows 'PCRF-Initiated Gateway control session establishment or Gateway Control and QoS Rules provisioning procedure' between PCRF and P-GW. Step 5 shows 'PCEF initiated IP-CAN session modification Ack' from PCRF to P-GW. Step 6 shows 'Gateway control session termination' from P-GW to Target S-GW. Step 7 is a placeholder for 'Corresponding procedure as in TS 23.060'. + +**Figure 9.3.4-1: Service Request and Handover Procedures for EPS-connected 3G access** + +1. UE initiated Service request procedure or Handover procedure, which can be referred to the descriptions of the corresponding clause in TS 23.060 [22], with the addition that target HNB sends the target HNB local IP address and the UDP port if NAT/NAPT is detected to the target SGSN in the [RANAP] RELOCATION COMPLETE message or ENHANCED RELOCATION COMPLETE REQUEST message (for the messages refer to TS 25.413 [28]). +2. Step 2a and 2b are the same as that in TS 23.060 [22]: + - 2a. If there is a change in S-GW, the target SGSN sends the Create session request message to the target S-GW. If the S-GW is not changed, the (target) SGSN sends the modify bearer request message to the S-GW. The following information may be included: target HNB Local IP address and the UDP port if NAT/NAPT is detected. + - 2b. The (target) S-GW sends the modify bearer request message to the P-GW, based on conditions specified in TS 23.401 [2] (e.g. the S-GW is changed) or if the following information is received in step 2a: target HNB Local IP address and the UDP port if NAT/NAPT is detected. + +3. The P-GW sends IP-CAN session modification request message to the PCRF including the Target HNB local IP address and the UDP port if NAT/NAPT is detected as defined in TS 23.203 [4], Annex P.7.4.1. + +If the Modify bearer Request message received by P-GW in step 3 contains none of the additional information: HNB Local IP address and the UDP port if NAT/NAPT is detected., the P-GW determines that the UE leaves the H(e)NB and will inform this event to PCRF. + +4. If the UE moves from macro NB to a HNB, or the PCRF will initiate PCRF-initiated Gateway control session establishment procedure as defined in TS 23.203 [4] if the UE is the first UE attaching the target HNB; if the UE moves from one HNB to another HNB without fixed network backhaul changed or if the UE moves to a new HNB and there has been one Gateway Control Session for that HNB, the PCRF will initiate Gateway control and QoS rule provisioning procedure with BPCF as defined in TS 23.203 [4]. The HNB local IP address, the UDP port if NAT/NAPT is detected, shall be included in the PCRF-Initiated Gateway control session establishment procedure and in Gateway Control and QoS rule provisioning procedure. +5. The PCRF acknowledges the IP-CAN session modification. +6. If UE moves from one HNB to macro cell, the PCRF will terminate the old Gateway control session if this is the last UE under the source HNB; if the UE moves from macro NB to a HNB, or the UE moves from one HNB to another HNB without fixed network backhaul changed, or there are other UEs attached the source HNB, this step will be skipped. +7. This step can refer to the corresponding procedure as in TS 23.060 [22]. + +NOTE: The interaction between the BPCF and the BNG is out of scope. + +## 9.4 3GPP HNB procedure - CS support + +### 9.4.0 General + +The CS service is provided by the serving network. Therefore, in the roaming case the HNB GW is connected to the V-PCRF and the V-PCRF connects to the BPCF via the S9a interface. + +### 9.4.1 S15 session establishment at HNB registration + +![Sequence diagram for S15 Session Establishment at HNB registration. Lifelines: HNB, RG, BNG, Fixed Broadband Access (BPCF), SeGW, HNB GW, v/PCRF, MSC. The process involves local IP assignment, IPSec establishment, HNB registration, S15 session request/ack, and PCRF-initiated gateway control session establishment.](7b2d685b805535c1e94aee1365753b92_img.jpg) + +``` + +sequenceDiagram + participant HNB + participant RG + participant BNG + participant FBA as Fixed Broadband Access (BPCF) + participant SeGW + participant HNB_GW as HNB GW + participant vPCRF as v/PCRF + participant MSC + + Note left of HNB: 1. Local IP address assignment + Note left of HNB: 2. IPSec Establishment (according to TS 33.320) + Note left of HNB: 3. HNB Registration (according to TS 25.467) + HNB_GW->>vPCRF: 4. S15 Session establishment request + vPCRF-->>HNB_GW: 5. S15 Session establishment ack + Note right of vPCRF: 6. PCRF-Initiated Gateway Control Session Establishment + +``` + +Sequence diagram for S15 Session Establishment at HNB registration. Lifelines: HNB, RG, BNG, Fixed Broadband Access (BPCF), SeGW, HNB GW, v/PCRF, MSC. The process involves local IP assignment, IPSec establishment, HNB registration, S15 session request/ack, and PCRF-initiated gateway control session establishment. + +Figure 9.4.1-1: S15 Session Establishment + +- 1) When the HNB powers on, it receives a local IP address from the BBF Access Network. HNB Local IP address assignment by BBF is out of 3GPP scope. +- 2) The HNB establish IPSec tunnel with SeGW as defined in TS 33.320 [15]. +- 3) The HNB initiates the Registration to HNB GW including HNB IP address, HNB local IP address, and the UDP port number(s) if NAT/NAPT is detected per TS 25.467 [12]. +- 4) The HNB GW initiates the establishment of the S15 session with the v/PCRF and sends the including information about the HNB such as, HNB local IP address and the UDP port number(s) if NAT/NAPT is detected. +- 5) The PCRF responds to the S15 session establishment request. +- 6) The PCRF initiates the Gateway Control session Establishment to establish Gateway Control Session and sends the HNB local IP address and optionally the UDP port number(s) if NAT/NAPT is detected to the BPCF according to TS 23.203 [4], Annex P. + +### 9.4.2 HNB GW initiated S15 session modification + +This procedure is executed when the first UE or a subsequent UE connecting to a HNB requests a CS call. + +![Sequence diagram for HNB GW initiated S15 session modification. Lifelines: UE, HNB, RG, BNG, Fixed Broadband Access (BPCF), SeGW, HNB GW, v/PCRF, MSC. The sequence starts with UE sending a SETUP message to MSC. MSC sends a RAB Assignment Request to HNB. HNB GW intercepts this and sends a Session Modification Request to v/PCRF. v/PCRF initiates Gateway Control & QoS Rule Provisioning with BPCF. v/PCRF sends a Session Modification Response to HNB GW. HNB GW then sends a RAB Assignment Request to HNB. HNB sends a RAB Assignment Response to HNB GW.](901755bf86813427f3a32efa0363a27c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant HNB + participant RG + participant BNG + participant BPCF as Fixed Broadband Access + participant SeGW + participant HNB_GW as HNB GW + participant vPCRF as v/PCRF + participant MSC + + Note right of BPCF: Fixed Broadband Access + UE->>MSC: 1. SETUP + MSC->>HNB: 2. RAB Assignment Request + HNB->>HNB_GW: + HNB_GW->>vPCRF: 3. Session Modification Request + vPCRF->>BPCF: 4. PCRF-Initiated Gateway Control & QoS Rule Provisioning + vPCRF->>HNB_GW: 5. Session Modification Response + HNB_GW->>HNB: 6. RAB Assignment Request + HNB->>HNB_GW: 7. RAB Assignment Response + +``` + +Sequence diagram for HNB GW initiated S15 session modification. Lifelines: UE, HNB, RG, BNG, Fixed Broadband Access (BPCF), SeGW, HNB GW, v/PCRF, MSC. The sequence starts with UE sending a SETUP message to MSC. MSC sends a RAB Assignment Request to HNB. HNB GW intercepts this and sends a Session Modification Request to v/PCRF. v/PCRF initiates Gateway Control & QoS Rule Provisioning with BPCF. v/PCRF sends a Session Modification Response to HNB GW. HNB GW then sends a RAB Assignment Request to HNB. HNB sends a RAB Assignment Response to HNB GW. + +Figure 9.4.2-1: HNB GW initiated S15 session modification + +NOTE: This flow does not include all the steps associated with CS call setup. + +- 1) The UE initiates call setup to the MSC using a SETUP message. +- 2) The MSC sends a RAB Assignment Request message towards the HNB. +- 3) The HNB GW intercepts the RAB assignment message and sends the S15 session modification message to the PCRF that includes the HNB Local IP address, the UDP port number(s) if NAT/NAPT is detected and the QoS information derived from the RAB message. +- 4) The PCRF initiates the GW Control and QoS Rules Provisioning procedure according to TS 23.203 [4], Annex P. +- 5) The PCRF responds with the outcome of the authorisation request .If no resources are available then the HNB GW rejects the RAB assignment and initiates the "RAB assignment failure" procedure. +- 6) The HNB GW sends the RAB assignment message to the HNB. + +7) The remainder of the call setup procedure completes. + +### 9.4.3 S15 session termination + +![Sequence diagram for S15 session release showing interactions between UE, HNB, RG, BNG, SeGW, BPCF, HNB GW, PCRF, and MSC. The diagram includes three numbered steps: 1. HNB De-Registration, 2. Session Termination, and 3. PCRF-Initiated Gateway Control Session Termination.](9f51a76cae7309a296cbc6997941eb3f_img.jpg) + +The diagram illustrates the S15 session release procedure. It features lifelines for UE, HNB, RG, BNG, SeGW, BPCF, HNB GW, PCRF, and MSC. A dashed box labeled 'Fixed Broadband Access' encloses the RG, BNG, and BPCF. The sequence of messages is as follows: + +- 1. HNB De-Registration (according to TS 25.467)**: A message from the HNB GW to the HNB. +- 2. Session Termination**: A message from the HNB GW to the PCRF. +- 3. PCRF-Initiated Gateway Control Session Termination**: A message from the PCRF to the BPCF. + +Sequence diagram for S15 session release showing interactions between UE, HNB, RG, BNG, SeGW, BPCF, HNB GW, PCRF, and MSC. The diagram includes three numbered steps: 1. HNB De-Registration, 2. Session Termination, and 3. PCRF-Initiated Gateway Control Session Termination. + +**Figure 9.4.3-1: S15 session Release** + +- 1) The HNB GW initiates/receives a Deregistration request for the HNB per TS 25.467 [12]. +- 2) The HNB GW requests S15 session termination to the PCRF. +- 3) The PCRF initiates the GW control session termination over S9a toward the BPCF per TS 23.203 [4], Annex P and the PCRF acknowledges the request for termination of S15 session. + +### 9.4.4 PCRF initiated S15 session modification + +![Sequence diagram for PCRF initiated S15 session modification](1c79f31a718d63814feb28ab46f64f19_img.jpg) + +The diagram illustrates a sequence of messages between network elements. At the top, a dashed box labeled 'Fixed Broadband Access' contains the elements RG, BNG, and BPCF. To the left of this box are UE and HNB. To the right are HNB GW, v/PCRF, and MSC. A SeGW is positioned below the Fixed Broadband Access box. The sequence of messages is as follows: 1. A large arrow labeled '1. BPCF-Initiated Gateway Control & QoS Rule request' points from the BPCF to the v/PCRF. 2. An arrow labeled '2. S15 Session Modification Request' points from the v/PCRF to the HNB GW. 3. An arrow labeled '3. S15 Session Modification Response' points from the HNB GW to the v/PCRF. 4. A wide horizontal bar at the bottom, spanning from the HNB to the MSC, is labeled '4. RAB modification'. + +Sequence diagram for PCRF initiated S15 session modification + +**Figure 9.4.4-1: PCRF initiated S15 session modification** + +- 1) The BPCF initiates Gateway Control and QoS Rule Request to report QoS Rule failure to (v)PCRF, which can be referred to the corresponding description in step 1 of TS 23.203 [4], clause P.8.4. +- 2) The (v)PCRF sends the S15 session modification request message to the HNB GW. The (v)PCRF includes the report identifying the QoS Rules that failed and a reason derived from the BPCF. +- 3) The BPCF response the S15 session modification to the (v)PCRF. +- 4) Based the trigger got in step 2, the HNB GW initiates the RAB modification which is outside the scope of the present document. + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|--------|-----------|------|-----|-----|-----------------------------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | +| 2012-03 | SP-55 | - | - | - | - | MCC Editorial update to version 11.0.0 after TSG SA Approval (Release 11) | 2.0.0 | 11.0.0 | +| 2012-06 | SP-56 | SP-120241 | 0001 | 1 | F | Some corrections to the functional description and procedures | 11.0.0 | 11.1.0 | +| 2012-06 | SP-56 | SP-120241 | 0002 | 2 | F | Correction to UE reflective QoS notification | 11.0.0 | 11.1.0 | +| 2012-06 | SP-56 | SP-120241 | 0004 | 2 | F | Clarification of accounting requirement and assumptions | 11.0.0 | 11.1.0 | +| 2012-06 | SP-56 | SP-120241 | 0007 | 2 | F | Corrections on TS 23.139 | 11.0.0 | 11.1.0 | +| 2012-06 | SP-56 | SP-120241 | 0008 | 3 | F | UE local IP address update procedure for S2c case | 11.0.0 | 11.1.0 | +| 2012-06 | SP-56 | SP-120241 | 0016 | 1 | F | SeGW DL DSCP Marking for EPC Routed Traffic | 11.0.0 | 11.1.0 | +| 2012-09 | SP-57 | SP-120478 | 0020 | 1 | F | Correction to untrusted S2c procedure | 11.1.0 | 11.2.0 | +| 2012-09 | SP-57 | SP-120478 | 0024 | 1 | F | Notification of PGW IP address in case of PDN disconnection | 11.1.0 | 11.2.0 | +| 2012-09 | SP-57 | SP-120478 | 0027 | - | F | Corrections of wrong references | 11.1.0 | 11.2.0 | +| 2012-12 | SP-58 | SP-120755 | 0032 | 2 | F | Correction to UE reflective QoS notification | 11.2.0 | 11.3.0 | +| 2013-03 | SP-59 | SP-130082 | 0037 | 2 | F | PCRF initiated S15 session modification | 11.3.0 | 11.4.0 | +| 2013-03 | SP-59 | SP-130082 | 0039 | 1 | F | Alignment of BBAI H(e)NB Local IP Address Signalling with RAN WG3 decisions | 11.3.0 | 11.4.0 | +| 2013-06 | SP-60 | SP-130228 | 0043 | 1 | B | Conclusion on S2a for P4C TI | 11.4.0 | 12.0.0 | +| 2014-09 | SP-65 | SP-140425 | 0045 | 1 | F | Correction of figure of DSCP Marking | 12.0.0 | 12.1.0 | +| 2015-03 | SP-67 | SP-150109 | 0046 | - | F | Corrections to BBF related references | 12.1.0 | 12.2.0 | +| 2015-12 | SP-70 | SP-150602 | 0047 | 1 | F | Removal of support of EAP-SIM | 12.2.0 | 12.3.0 | +| 2015-12 | - | - | - | - | - | Update to Rel-13 version (MCC) | 12.3.0 | 13.0.0 | +| 2017-03 | - | - | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | +| 2018-06 | SP-80 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | SP-88E | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23214/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/23_series/23214/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..23e51bcd5ef603b5bccb1b6ee8d26e61eb68dc9f --- /dev/null +++ b/marked/Rel-16/23_series/23214/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e49b5dcc274266cb0287a6cc9c90e35484c38083204d24aae0020b5d2920b594 +size 41664 diff --git a/marked/Rel-16/23_series/23214/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg b/marked/Rel-16/23_series/23214/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf78f61843008b888253f4b439cce87161d1b3b9 --- /dev/null +++ b/marked/Rel-16/23_series/23214/0d0897dd7f03672d186db9d56ea0d6f5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ad65257b6f0ad352a4d6dc1f0a992da72edd9e6a9ed7c067162f74cd873b9e1c +size 124265 diff --git a/marked/Rel-16/23_series/23214/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-16/23_series/23214/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..096906d345ff4a5067d1040b3e457a9d53fc93a4 --- /dev/null +++ b/marked/Rel-16/23_series/23214/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f62cd7377598cdef59c0a8688e923cae6b2200def6873eced0891a4d2782eec9 +size 346461 diff --git a/marked/Rel-16/23_series/23214/165508b2526a29efbae96fa16d525d28_img.jpg b/marked/Rel-16/23_series/23214/165508b2526a29efbae96fa16d525d28_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f357084f050eb1508b46e4452c941ea2e24a54ca --- /dev/null +++ b/marked/Rel-16/23_series/23214/165508b2526a29efbae96fa16d525d28_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59d3348d5bfd40c43af4dae58f43cbc533d9db2112cef438ede8aacbc0198451 +size 31122 diff --git a/marked/Rel-16/23_series/23214/17f0cf80b9c38adb460d4ca836960da7_img.jpg b/marked/Rel-16/23_series/23214/17f0cf80b9c38adb460d4ca836960da7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2782d1ec810aa7b8856be5d9e68217eb172a756c --- /dev/null +++ b/marked/Rel-16/23_series/23214/17f0cf80b9c38adb460d4ca836960da7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84f312246eeefedfe3c554047a4957e9c1d37133c6a228ccf49ec4ad863a609f +size 207755 diff --git a/marked/Rel-16/23_series/23214/1f1614411edea7edfc86c839a608e1fc_img.jpg b/marked/Rel-16/23_series/23214/1f1614411edea7edfc86c839a608e1fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c722d22d3aa415d58297e0f33db0843a8ba0a9c7 --- /dev/null +++ b/marked/Rel-16/23_series/23214/1f1614411edea7edfc86c839a608e1fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7852a8fb03f193f6906b2a026de4cafe6aa65bae26d8fc2e0203e02dca8927ef +size 84732 diff --git a/marked/Rel-16/23_series/23214/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23214/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3097033ee99261b7ae3f8141fea0045b318f6f9c --- /dev/null +++ b/marked/Rel-16/23_series/23214/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:255c0345709f74319e46047ca24723bf23a9443ac461758cde605054a8c45845 +size 213299 diff --git a/marked/Rel-16/23_series/23214/39536a630fa74c3bcfd1670ee2152809_img.jpg b/marked/Rel-16/23_series/23214/39536a630fa74c3bcfd1670ee2152809_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf1d5cc4f48916b1a02381245c75eeba8f05c430 --- /dev/null +++ b/marked/Rel-16/23_series/23214/39536a630fa74c3bcfd1670ee2152809_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5195e088713c406720d2c728a3af8ad1c4a703093d60baf2110e75f6a7c2fa42 +size 56260 diff --git a/marked/Rel-16/23_series/23214/3dea2a7c8e1120f769d0bc8ee347340d_img.jpg b/marked/Rel-16/23_series/23214/3dea2a7c8e1120f769d0bc8ee347340d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cb12d7c808b2e5674eaf28726476cb66231e0a9 --- /dev/null +++ b/marked/Rel-16/23_series/23214/3dea2a7c8e1120f769d0bc8ee347340d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:486a8f6f4090fc5120688e0abc78ff6c34040e219ffe6dcd16d86913122dae6d +size 22250 diff --git a/marked/Rel-16/23_series/23214/40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg b/marked/Rel-16/23_series/23214/40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df06557f5a6f2e6a29314f99f42e16f93ba94e40 --- /dev/null +++ b/marked/Rel-16/23_series/23214/40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d5fc9926b03cb8f4b1424f266473be994649cf03bd3d5d7fb1a5798d9cfa23c +size 41665 diff --git a/marked/Rel-16/23_series/23214/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-16/23_series/23214/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e58f711f1c02f5121138d1fb470392d889739073 --- /dev/null +++ b/marked/Rel-16/23_series/23214/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c9f1c1e202247c6ddcdd610a0f6f4949d8a0773b84df2838affee314f7c1f24 +size 333066 diff --git a/marked/Rel-16/23_series/23214/4b8c5ecb492fd759c766fe8950fafe67_img.jpg b/marked/Rel-16/23_series/23214/4b8c5ecb492fd759c766fe8950fafe67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4cae732115da7ef1521ee87b8b29e5097471901e --- /dev/null +++ b/marked/Rel-16/23_series/23214/4b8c5ecb492fd759c766fe8950fafe67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:024015dbc3b52512dc3bacb3aec668073f8ea144383e4e877464f5ebcdd11e44 +size 48057 diff --git a/marked/Rel-16/23_series/23214/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/23_series/23214/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..89a8cc2668c7d617a498f00d0825eeaff9a2ed5b --- /dev/null +++ b/marked/Rel-16/23_series/23214/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:71c7bc673b7dff1cc51a3e3d633c40058a9733f9d5d2e2ce08476b4746e07160 +size 59856 diff --git a/marked/Rel-16/23_series/23214/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/23_series/23214/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f23e770db301242179e8e792ceaa780c6c9bd23 --- /dev/null +++ b/marked/Rel-16/23_series/23214/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e02e8b2c7a5a87ddb79871e7d80829865932adb2b8cd475041250dbbd0bae9a1 +size 9413 diff --git a/marked/Rel-16/23_series/23214/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/23_series/23214/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4074eb2148617c3041a7d4a8b585759f3bad9b1 --- /dev/null +++ b/marked/Rel-16/23_series/23214/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64f0958b56960ec38ba378c80d097d14a8504ab506e76f1b1da9e96f248d390d +size 5809 diff --git a/marked/Rel-16/23_series/23214/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/23_series/23214/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae863c54839f0b6ac0124cc7bc6546cacedb33f4 --- /dev/null +++ b/marked/Rel-16/23_series/23214/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:753eea7c61917892be4c8ecb1d65732378de91b66aa4b127510e5b930394a8e2 +size 225093 diff --git a/marked/Rel-16/23_series/23214/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-16/23_series/23214/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..432fde4bb29039c0e07cf2a04d753872c140f1f2 --- /dev/null +++ b/marked/Rel-16/23_series/23214/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a70cc8445cf21a6148809af08014a5b987759e07762978f70157bbdb02e1db99 +size 190920 diff --git a/marked/Rel-16/23_series/23214/6984a27b2b89e0995d5216ec29b41d1c_img.jpg b/marked/Rel-16/23_series/23214/6984a27b2b89e0995d5216ec29b41d1c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2715f49a61b585e187d5d887810ce7eb965f2ee8 --- /dev/null +++ b/marked/Rel-16/23_series/23214/6984a27b2b89e0995d5216ec29b41d1c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:39a602ef207b2718746ff9830532d4455d89a43c5400c99ff9b9d869b9820d8d +size 202446 diff --git a/marked/Rel-16/23_series/23214/762a17cd79880dbca172bcbbe9375223_img.jpg b/marked/Rel-16/23_series/23214/762a17cd79880dbca172bcbbe9375223_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ecd5033b4b2beb2ebd90dd9823837381baa66cc --- /dev/null +++ b/marked/Rel-16/23_series/23214/762a17cd79880dbca172bcbbe9375223_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:567e21740d1a54ac0393ec7eb2eaec564bf70df5f87b8039d10aff6784cb5885 +size 72431 diff --git a/marked/Rel-16/23_series/23214/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23214/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afa0b368e22af5386fb0e6fa7e93da39a5d393d7 --- /dev/null +++ b/marked/Rel-16/23_series/23214/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97df97fafbaa2c748d240af886ff2e4e0b556be23c089787f16da78c1241b8de +size 40777 diff --git a/marked/Rel-16/23_series/23214/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/23_series/23214/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f0d48b9012c15103008235bba817eada9153b8b --- /dev/null +++ b/marked/Rel-16/23_series/23214/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c178399e11496b4621e190165c515c1dcca498aa6f6a146f11200c27e15204d1 +size 52085 diff --git a/marked/Rel-16/23_series/23214/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/23_series/23214/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e0e73dee1817a7bb8a27f50f7e3829dcb2e3059a --- /dev/null +++ b/marked/Rel-16/23_series/23214/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ef2ad2fccec8d29fb33d940ad623790832686031307c622ca85b8e690159f6f +size 251962 diff --git a/marked/Rel-16/23_series/23214/86692d82da6655813b5acf58a767a38c_img.jpg b/marked/Rel-16/23_series/23214/86692d82da6655813b5acf58a767a38c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e80a9aa33318fc3e738620af7ba533c761b83170 --- /dev/null +++ b/marked/Rel-16/23_series/23214/86692d82da6655813b5acf58a767a38c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb83a6b0465f23b6d504cd98a78b9eb1b01fd9ace60d62110a0a473d4ee25f21 +size 54753 diff --git a/marked/Rel-16/23_series/23214/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg b/marked/Rel-16/23_series/23214/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..95b59558ff4250c66f585dd27c0df7be90f2f289 --- /dev/null +++ b/marked/Rel-16/23_series/23214/8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e9de8c93df3d99fb93b82dc7f68f6be296470fdad3e1d6590c1b36c69175426 +size 55291 diff --git a/marked/Rel-16/23_series/23214/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/23_series/23214/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66c56351951fd39c6f945d6c4766d1ebd61cd617 --- /dev/null +++ b/marked/Rel-16/23_series/23214/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6387e03b0c905a3e6b53992844db59559fd5890851c7e5267c9cd213fb0f7002 +size 59226 diff --git a/marked/Rel-16/23_series/23214/9e9104f9ba7eec1259a7893c6380ca1b_img.jpg b/marked/Rel-16/23_series/23214/9e9104f9ba7eec1259a7893c6380ca1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21f1bf3ffb7e2870bfbf85facc9232048b5c176b --- /dev/null +++ b/marked/Rel-16/23_series/23214/9e9104f9ba7eec1259a7893c6380ca1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7875654ffcfa281677d756e0d76be1761d40db5b7f6c7f2dc78ca40d6330c6cf +size 61341 diff --git a/marked/Rel-16/23_series/23214/9edb407536d4d4d4a6ac391527af047c_img.jpg b/marked/Rel-16/23_series/23214/9edb407536d4d4d4a6ac391527af047c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9bb724d147d26c49bf3136d085f918cabae138f6 --- /dev/null +++ b/marked/Rel-16/23_series/23214/9edb407536d4d4d4a6ac391527af047c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:595e619db63d1d9ec2f63a6d15544897a5b3e32446766489ee7d41adf5bdaa87 +size 58429 diff --git a/marked/Rel-16/23_series/23214/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-16/23_series/23214/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7697ab7efea5d9cd3d7c52884e1f610bbc26603 --- /dev/null +++ b/marked/Rel-16/23_series/23214/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c42685ae05a3c454ae8ddf1cfcbc8c760bafdab0149cf47eb75b4af5db4f095 +size 181341 diff --git a/marked/Rel-16/23_series/23214/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23214/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..441693ad9465d353dcdf0045b6dcca275874847a --- /dev/null +++ b/marked/Rel-16/23_series/23214/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6b00deecdd18ce5cb4d5a8acaab1d9d230fdb43a374c3526cc222ba81dc4cda +size 99217 diff --git a/marked/Rel-16/23_series/23214/a234352dfaccdc24745c88eef7724cc6_img.jpg b/marked/Rel-16/23_series/23214/a234352dfaccdc24745c88eef7724cc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9562b6eb8dc7666d3efa0efcc36dfde3f4f5679 --- /dev/null +++ b/marked/Rel-16/23_series/23214/a234352dfaccdc24745c88eef7724cc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11166160b98436c8aba98cadbea770b2496fcb412b9f9db7edd80522fc440f21 +size 54737 diff --git a/marked/Rel-16/23_series/23214/a78db21022e0687c18d97ed547dd7ecb_img.jpg b/marked/Rel-16/23_series/23214/a78db21022e0687c18d97ed547dd7ecb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbea1c60af2ac71cc4610529ce5b3565aa3907ea --- /dev/null +++ b/marked/Rel-16/23_series/23214/a78db21022e0687c18d97ed547dd7ecb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1194e91d2dc5a09edbc57f9bfdfcb2a90d25781de2b18ae11b5f1054ae3c7588 +size 51594 diff --git a/marked/Rel-16/23_series/23214/b06a4c871dfd0ce034cf801519d0039a_img.jpg b/marked/Rel-16/23_series/23214/b06a4c871dfd0ce034cf801519d0039a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac07a73c3dcbf21bfe8ef75529254b9dcc72aa08 --- /dev/null +++ b/marked/Rel-16/23_series/23214/b06a4c871dfd0ce034cf801519d0039a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a7ade56457381398f90dd3dab7a779d83d4ac8b424bf1a35dcfd94354c8b8fa +size 141204 diff --git a/marked/Rel-16/23_series/23214/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/23_series/23214/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..13371fc69a2c4c7bb08bae92c8a606301470e242 --- /dev/null +++ b/marked/Rel-16/23_series/23214/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8af5cacff27c4e8c1e7c0de1d6567a0a130882af253c18c699c2bac279192a4f +size 126913 diff --git a/marked/Rel-16/23_series/23214/b63f41ca262d8ce9ef8affb62607f32b_img.jpg b/marked/Rel-16/23_series/23214/b63f41ca262d8ce9ef8affb62607f32b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d3876ea4e050c05d38ca94249e7926562f207e3 --- /dev/null +++ b/marked/Rel-16/23_series/23214/b63f41ca262d8ce9ef8affb62607f32b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:976b8dd79e427c767a6c5cf7dc42ff6805b6f75a5552ece85e9919c19d63a0c3 +size 101859 diff --git a/marked/Rel-16/23_series/23214/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg b/marked/Rel-16/23_series/23214/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d19e8108ce679b102d6908bc15ec9a136b03911 --- /dev/null +++ b/marked/Rel-16/23_series/23214/b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:63175bef615d0d6df107b33137bccc444566f4b77e767d88cfb9e36ebb70ab5e +size 54839 diff --git a/marked/Rel-16/23_series/23214/c85b57b2414f341860dfc338e1cf2509_img.jpg b/marked/Rel-16/23_series/23214/c85b57b2414f341860dfc338e1cf2509_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..74aa501cf198b647e3f3e27bcf89a73c22a5583c --- /dev/null +++ b/marked/Rel-16/23_series/23214/c85b57b2414f341860dfc338e1cf2509_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:278a5e8779c69b2e8d54324e610e8835df6d2ee0016c9a774ddba88fd6188f1d +size 40577 diff --git a/marked/Rel-16/23_series/23214/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23214/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bf66daa72474df581ee3c4f576cf9ef0d4a30ac --- /dev/null +++ b/marked/Rel-16/23_series/23214/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:656fd58c3a2d640ed89058b6bb67b3da2f200024c6b4a7bd4efb0c25acb0240b +size 186691 diff --git a/marked/Rel-16/23_series/23214/d04f4b76a3f7aa0ff51714fb1f71d9d3_img.jpg b/marked/Rel-16/23_series/23214/d04f4b76a3f7aa0ff51714fb1f71d9d3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b344606df5e788121dbde987224beff8eeeed39e --- /dev/null +++ b/marked/Rel-16/23_series/23214/d04f4b76a3f7aa0ff51714fb1f71d9d3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b87d1a19daf34b121ec7739e26dba219997e8c7911b4160e8e0f700933bee422 +size 131959 diff --git a/marked/Rel-16/23_series/23214/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/marked/Rel-16/23_series/23214/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9a3a9f202d3a7963e5fdc3b58f14edf65df67bcf --- /dev/null +++ b/marked/Rel-16/23_series/23214/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5a6d889d1a42bb5d949edfe0aff00e5fe6dedfaeafdeebdb24b6220adfe5b886 +size 34474 diff --git a/marked/Rel-16/23_series/23214/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-16/23_series/23214/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bae83dbef378c8671a96aeeab11f69ee56e498d0 --- /dev/null +++ b/marked/Rel-16/23_series/23214/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a1df7c08b769a5db5157656e2b6a828b089e33b7790757b14eb3678494be4e20 +size 139234 diff --git a/marked/Rel-16/23_series/23214/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/23_series/23214/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4a2bf113ac90da1bdb823c15f38cc15d03d72ac9 --- /dev/null +++ b/marked/Rel-16/23_series/23214/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1297302eb98981b523591b09bcb7efc8e28e903b24a8a12ab116bdaabaaf6c7f +size 263570 diff --git a/marked/Rel-16/23_series/23214/raw.md b/marked/Rel-16/23_series/23214/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ec8170146671d4652bade6badad57f80261a172a --- /dev/null +++ b/marked/Rel-16/23_series/23214/raw.md @@ -0,0 +1,2880 @@ + + +# 3GPP TS 23.214 V16.2.0 (2020-09) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for control and user plane separation of EPC nodes; Stage 2 (Release 16)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, consisting of the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic element consisting of three curved lines, resembling a signal strength indicator or a stylized wave. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the letters "3GPP" in a stylized, bold, black font. The "3" and "G" are connected at the top by a single horizontal line. Below the "P" is a red graphic element consisting of three curved lines, resembling a signal strength indicator or a stylized wave. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 Architecture model and concepts..... | 8 | +| 4.1 General concepts ..... | 8 | +| 4.2 Architecture reference model..... | 9 | +| 4.2.1 Non-roaming and roaming architectures ..... | 9 | +| 4.2.2 Combined SGW/PGW architecture..... | 9 | +| 4.2.3 Reference points ..... | 10 | +| 4.3 High level functions ..... | 10 | +| 4.3.1 General ..... | 10 | +| 4.3.2 Functional split of SGW, PGW and TDF..... | 12 | +| 4.3.2.1 Functional split of SGW ..... | 12 | +| 4.3.2.2 Functional split of PGW ..... | 14 | +| 4.3.2.3 Functional split of TDF..... | 16 | +| 4.3.3 User Plane Function selection ..... | 18 | +| 4.3.4 SGW-C Partitioning ..... | 18 | +| 4.4 Network elements..... | 19 | +| 4.4.1 General ..... | 19 | +| 4.4.2 SGW control plane function..... | 19 | +| 4.4.3 SGW user plane function..... | 19 | +| 4.4.4 PGW control plane function..... | 19 | +| 4.4.5 PGW user plane function..... | 19 | +| 4.4.6 TDF control plane function ..... | 20 | +| 4.4.7 TDF user plane function..... | 20 | +| 5 Functional description..... | 20 | +| 5.1 General ..... | 20 | +| 5.2 Traffic detection..... | 20 | +| 5.2.1 General ..... | 20 | +| 5.2.2 Traffic detection information..... | 20 | +| 5.3 Charging and usage monitoring handling ..... | 21 | +| 5.3.1 General ..... | 21 | +| 5.3.2 Activation of usage reporting in UP function..... | 22 | +| 5.3.3 Reporting of usage information towards CP function ..... | 22 | +| 5.3.4 PGW Pause of Charging..... | 23 | +| 5.4 GTP-U IP address and TEIDu allocation..... | 23 | +| 5.4.1 General ..... | 23 | +| 5.4.2 Void..... | 23 | +| 5.4.3 F-TEIDu allocation / release in the UP function ..... | 23 | +| 5.5 UE IP address management (allocation, renewal and release)..... | 23 | +| 5.6 Control of user plane forwarding ..... | 24 | +| 5.6.1 General ..... | 24 | +| 5.6.2 Control of user plane forwarding ..... | 25 | +| 5.6.3 Format of forwarded user plane data..... | 25 | +| 5.7 UE's permanent identifier usage..... | 25 | +| 5.8 Functionality of sending of "end marker" ..... | 26 | +| 5.8.1 UP function constructing the "end marker" packets..... | 26 | +| 5.8.2 CP function constructing the "end marker" packets..... | 26 | +| 5.9 Idle state packet SGW buffering function..... | 26 | +| 5.9.1 General ..... | 26 | +| 5.9.2 Buffering in CP function ..... | 27 | + +| | | | +|-----------|-------------------------------------------------------------------|----| +| 5.9.3 | Buffering in UP function ..... | 27 | +| 5.9.3.1 | General..... | 27 | +| 5.9.3.2 | Delay Downlink Packet Notification..... | 27 | +| 5.9.3.3 | Extended buffering ..... | 27 | +| 5.9.3.4 | Throttling ..... | 28 | +| 5.10 | Bearer and APN policing ..... | 28 | +| 5.11 | PCC/ADC related functions..... | 28 | +| 5.11.1 | Activation/Deactivation of predefined PCC/ADC rules ..... | 28 | +| 5.11.2 | Enforcement of dynamic PCC/ADC rules ..... | 29 | +| 5.11.3 | Redirection ..... | 29 | +| 5.11.4 | Support of SDCI..... | 30 | +| 5.12 | User Plane function selection..... | 30 | +| 5.12.1 | General ..... | 30 | +| 5.12.2 | Selection of PGW-U ..... | 30 | +| 5.12.3 | Selection of SGW-U ..... | 31 | +| 5.12.4 | Selection of a combined SGW/PGW-U ..... | 31 | +| 5.12.5 | Selection of TDF-U ..... | 32 | +| 5.12.5.1 | Solicited application reporting mode ..... | 32 | +| 5.12.5.2 | Unsolicited application reporting mode..... | 32 | +| 6 | Information flows..... | 32 | +| 6.1 | General ..... | 32 | +| 6.2 | Sx Session Management Procedures..... | 33 | +| 6.2.1 | General ..... | 33 | +| 6.2.2 | Sx Session Establishment Procedure..... | 33 | +| 6.2.3 | Sx Session Modification Procedure..... | 34 | +| 6.2.4 | Sx Session Termination Procedure..... | 34 | +| 6.3 | Updates to procedures in other specifications..... | 35 | +| 6.3.1 | Updates to procedures specified in TS 23.401 [2]..... | 35 | +| 6.3.1.2 | Procedures with SGW change ..... | 38 | +| 6.3.1.2.1 | General ..... | 38 | +| 6.3.1.2.2 | Type 1..... | 38 | +| 6.3.1.2.3 | Type 2..... | 40 | +| 6.3.1.3 | Procedures with eNB F-TEIDu update..... | 42 | +| 6.3.1.4 | Procedures with release of eNB F-TEIDu ..... | 43 | +| 6.3.1.5 | Procedures when downlink data is buffered in the UP function..... | 44 | +| 6.3.1.6 | Procedures with release of PDN connection..... | 45 | +| 6.3.1.7 | Procedures with modification of bearer ..... | 47 | +| 6.3.2 | Updates to procedures specified in TS 23.203 [3]..... | 49 | +| 6.3.2.1 | IP-CAN session establishment..... | 49 | +| 6.3.2.2 | IP-CAN session termination ..... | 50 | +| 6.3.2.3 | IP-CAN session modification ..... | 50 | +| 6.3.2.4 | Management of PFDs ..... | 51 | +| 6.3.3 | Updates to procedures specified in TS 23.402 [4]..... | 52 | +| 6.3.3.1 | Procedures with GTP based S2b establishment..... | 52 | +| 6.3.3.2 | Procedures with GTP based S2a establishment..... | 53 | +| 6.3.3.3 | Procedures with GTP based S2b release..... | 54 | +| 6.3.3.4 | Procedures with GTP based S2a release..... | 54 | +| 6.3.3.5 | Procedures with dedicated bearer activation by PGW ..... | 55 | +| 6.3.3.6 | Procedures with bearer deactivation by PGW ..... | 56 | +| 6.3.3.7 | Procedures with bearer modification ..... | 56 | +| 6.3.3.8 | Procedures with handover from non-3GPP access ..... | 57 | +| 6.3.3.9 | Procedures with handover from 3GPP access ..... | 59 | +| 6.3.4 | Updates to procedures specified in TS 23.060 [5]..... | 59 | +| 6.3.4.1 | Procedures with PDN connection deactivation ..... | 59 | +| 6.3.4.1.1 | Procedures with SGSN terminating S4 interface ..... | 59 | +| 6.3.4.1.2 | Procedures with SGSN terminating Gn/Gp interface ..... | 63 | +| 6.3.4.2 | Procedures with PDN connection modification..... | 65 | +| 6.3.4.2.1 | Procedures with SGSN terminating S4 interface ..... | 65 | +| 6.3.4.2.2 | Procedures with SGSN terminating Gn/Gp interface ..... | 73 | +| 6.3.4.3 | Procedures with PDN connection establishment..... | 77 | +| 6.4 | Sx Reporting Procedures..... | 78 | + +| | | | +|---------------------------------------------------|----------------------------------------------------|-----------| +| 6.4.1 | General ..... | 78 | +| 6.4.2 | Sx Session Level Reporting Procedure ..... | 78 | +| 6.5 | Sx Management Procedures..... | 79 | +| 6.5.1 | General ..... | 79 | +| 6.5.2 | Sx PFD management Procedure..... | 79 | +| 6.5.3 | Sx Association Setup Procedure..... | 80 | +| 6.5.4 | Sx Association Update Procedure ..... | 80 | +| 6.5.5 | Sx Association Release Procedure ..... | 80 | +| 7 | Parameters..... | 80 | +| 7.1 | Parameters for Sx session management ..... | 80 | +| 7.2 | Session context..... | 81 | +| 7.3 | Packet Detection Rule ..... | 81 | +| 7.4 | Usage Reporting Rule ..... | 84 | +| 7.5 | Forwarding Action Rule..... | 85 | +| 7.6 | QoS Enforcement Rule..... | 87 | +| 7.7 | Usage Report generated by UP function..... | 89 | +| 7.8 | Functional description..... | 90 | +| 7.8.1 | General ..... | 90 | +| 7.8.2 | PDN connection and TDF session level context ..... | 91 | +| 7.8.3 | Bearer related context..... | 91 | +| 7.8.4 | Measurement key related context..... | 91 | +| 7.9 | Parameters for Sx management..... | 92 | +| 7.9.1 | Parameters for PFD management..... | 92 | +| Annex A (informative): Change history..... | | 93 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- 1 Scope + +The present document specifies the overall stage 2 level functionality for control and user plane separation of EPC's SGW, PGW and TDF. This enables a flexible placement of the separated control plane and user plane functions for supporting diverse deployment scenarios (e.g. central or distributed user plane function) without affecting the overall functionality provided by these EPC entities. + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [3] 3GPP TS 23.203: "Policy and charging control architecture". +- [4] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses". +- [5] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [6] 3GPP TS 29.060: "GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface". +- [7] 3GPP TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3". +- [8] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging". +- [9] 3GPP TS 32.240: "Charging architecture and principles". +- [10] 3GPP TS 33.107: "3G security; Lawful interception architecture and functions". +- [11] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points". +- [12] 3GPP TS 29.244: "Interface between the Control Plane and the User Plane of EPC Nodes; Stage 3". +- [13] 3GPP TS 28.708: "Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1], TS 23.401 [2], TS 23.203 [3] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**F-TEID:** as defined in clause 8.22 of TS 29.274 [7]. + +**F-TEIDu:** The F-TEID of a GTP-u tunnel. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.401 [2], TS 23.203 [3] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|-------------|---------------------------------------------------| +| CP function | Control Plane function | +| PGW | PDN Gateway | +| PGW-C | PDN Gateway Control plane function | +| PGW-U | PDN Gateway User plane function | +| SGW | Serving Gateway | +| SGW-C | Serving Gateway Control plane function | +| SGW-U | Serving Gateway User plane function | +| TDF | Traffic Detection Function | +| TDF-C | Traffic Detection Function Control plane function | +| TDF-U | Traffic Detection Function User plane function | +| UP function | User Plane function | + +# --- 4 Architecture model and concepts + +## 4.1 General concepts + +The architecture and functionality for control and user plane separation of SGW, PGW and TDF is based on the following concepts: + +- Interworking with networks not applying control and user plane separation is possible (i.e. in case of roaming scenarios); +- Split network entities can interwork with network entities that are not split within the same network; +- Split network entities have no requirement to update UE, and Radio Access Network; +- The SGW/PGW selection function of the MME/ePDG/TWAN described in TS 23.401 [2] and TS 23.402 [4] is used for the selection of the respective CP function; +- The configuration based mechanism (in PGW or PCRF) described in TS 23.203 [3] is used for the selection of the CP function of the TDF; +- A CP function can interface with one or more UP functions (e.g. to enable independent scalability of CP functions and UP functions). + +## 4.2 Architecture reference model + +### 4.2.1 Non-roaming and roaming architectures + +This clause defines the complementary aspects of the architecture reference models specified in TS 23.401 [2] clause 4.2 and TS 23.402 [4] clauses 4.2.2 and 4.2.3 for GTP-based interfaces when SGW, PGW and TDF control and user planes are separated. + +For S2a, S2b, S5 and S8 reference points, this architecture reference model is only supported with GTP-based interfaces. PMIP-based interfaces and S2c interface are not supported. + +Figure 4.2.1-1 shows the architecture reference model in the case of separation between control plane and user plane. This architecture reference model covers non-roaming as well as home routed and local breakout roaming scenarios. + +![Figure 4.2.1-1: Architecture reference model with separation of user plane and control plane for non-roaming and roaming scenarios. The diagram shows three main functional entities: Serving Gateway-C (Control Plane), PDN Gateway-C (Control Plane), and TDF-C (Control Plane) in the top row, and their corresponding User Plane entities: Serving Gateway-U, PDN Gateway-U, and TDF-U in the bottom row. The control plane entities are interconnected by various reference points: S11, S4-C, S2b-C, S2a-C, Gn/Gp-C, S5/8-C, Gx, Gy, Gz, Gw, S6b, Sd, Gyn, Gwn, and Gzn. The user plane entities are interconnected by Sxa, Sxb, Sxc, S12, S11-U, S4-U, S1-U, S5/8-U, Gn/Gp-U, S2a-U, S2b-U, SGi, and SGI. The PDN Gateway-U is connected to Operator's IP Services (e.g. IMS, PSS etc.).](a234352dfaccdc24745c88eef7724cc6_img.jpg) + +Figure 4.2.1-1: Architecture reference model with separation of user plane and control plane for non-roaming and roaming scenarios. The diagram shows three main functional entities: Serving Gateway-C (Control Plane), PDN Gateway-C (Control Plane), and TDF-C (Control Plane) in the top row, and their corresponding User Plane entities: Serving Gateway-U, PDN Gateway-U, and TDF-U in the bottom row. The control plane entities are interconnected by various reference points: S11, S4-C, S2b-C, S2a-C, Gn/Gp-C, S5/8-C, Gx, Gy, Gz, Gw, S6b, Sd, Gyn, Gwn, and Gzn. The user plane entities are interconnected by Sxa, Sxb, Sxc, S12, S11-U, S4-U, S1-U, S5/8-U, Gn/Gp-U, S2a-U, S2b-U, SGi, and SGI. The PDN Gateway-U is connected to Operator's IP Services (e.g. IMS, PSS etc.). + +**Figure 4.2.1-1: Architecture reference model with separation of user plane and control plane for non-roaming and roaming scenarios** + +NOTE 1: The -C or -U suffix appended to S2a, S2b, S5 and S8 existing reference points only indicate the control plane and user plane components of those interfaces. + +NOTE 2: The architecture in figure 4.2.1-1 only depicts the case when the CP and UP functions of all SGW, PGW and TDF nodes are split. However, the other cases when the CP and UP function of only one of these nodes is split while the CP and UP function of the other interfacing node is not split, e.g. PGW's control plane and user plane is split while SGW's control plane and user plane is not split, are also supported. The split architecture of a node does not put any architectural requirements on the peer nodes with which it interfaces. + +NOTE 3: TDF is an optional functional entity. + +NOTE 4: Additional interfaces/reference points are documented in TS 23.401 [2], TS 23.402 [4], TS 23.060 [5] and TS 23.203 [3]. + +NOTE 5: For a roaming architecture with local breakout, the Gx interface is defined between the PGW-C and PCRF in the visited network. + +NOTE 6: S11-U is the interface between MME and SGW-U, supporting CP CIoT EPS Optimisation (see TS 23.401 [2]). + +### 4.2.2 Combined SGW/PGW architecture + +The usage of a combined SGW/PGW documented in TS 23.401 [2] remains possible in a deployment with separated control and user planes. This is enabled by supporting an Sx interface with a common parameter structure for non- + +combined and combined cases. Figure 4.2.2-1 shows the architecture reference model for a combined SGW/PGW in the case of separation between control plane and user plane. + +![Figure 4.2.2-1: Architecture reference model with separation of user plane and control plane for a combined SGW/PGW. The diagram shows two main components: 'Combined SGW/PGW-C' (Control Plane) and 'Combined SGW/PGW-U' (User Plane). The Control Plane is connected to various interfaces: S11, S4-C, S2b-C, S2a-C, Gn/Gp-C, Gx, Gy, Gz, Gw, and S6b. The User Plane is connected to S12, S11-U, S4-U, S1-U, Sx/Sxb, and SGi. The Control Plane and User Plane are connected to each other via the 'Combined Sx/Sxb' interface.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) + +Figure 4.2.2-1: Architecture reference model with separation of user plane and control plane for a combined SGW/PGW. The diagram shows two main components: 'Combined SGW/PGW-C' (Control Plane) and 'Combined SGW/PGW-U' (User Plane). The Control Plane is connected to various interfaces: S11, S4-C, S2b-C, S2a-C, Gn/Gp-C, Gx, Gy, Gz, Gw, and S6b. The User Plane is connected to S12, S11-U, S4-U, S1-U, Sx/Sxb, and SGi. The Control Plane and User Plane are connected to each other via the 'Combined Sx/Sxb' interface. + +**Figure 4.2.2-1: Architecture reference model with separation of user plane and control plane for a combined SGW/PGW** + +NOTE 1: The combined Sx/Sxb shown in figure 4.2.2-1 only covers the functionality of Sxa and Sxb. + +NOTE 2: S11-U is the interface between MME and combined SGW/PGW-U, supporting CP CIoT EPS Optimisation (see TS 23.401 [2]). + +### 4.2.3 Reference points + +This clause defines the complementary reference points of the architecture reference models specified in TS 23.401 [2] clause 4.2 and TS 23.402 [4] clauses 4.2.2 and 4.2.3 for GTP-based interfaces when SGW, PGW and TDF control and user planes are separated. + +The reference points added to the reference points defined in TS 23.401 [2], TS 23.402 [4] and TS 23.203 [3] are the following ones: + +- Sxa:** Reference point between SGW-C and SGW-U. +- Sxb:** Reference point between PGW-C and PGW-U. +- Sxc:** Reference point between TDF-C and TDF-U. + +## 4.3 High level functions + +### 4.3.1 General + +This clause documents the existing functionality of SGW, PGW and TDF as described in TS 23.401 [2], TS 23.402 [4] and TS 23.203 [3]. + +**Table 4.3.1-1: Existing functionality of SGW, PGW and TDF** + +| Main functionality | Sub-functionality | SGW | PGW | TDF | +|------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|-----| +| A. Session management (default & dedicated bearer establishment, bearer modification, bearer deactivation) | 1. Resource management for bearer resources | X | X | | +| | 2. IP address and TEID assignment for GTP-U | X | X | | +| | 3. Packet forwarding | X | X | | +| | 4. Transport level packet marking | X | X | | +| B. UE IP address management | 1. IP address allocation from local pool | | X | | +| | 2. DHCPv4 / DHCPv6 client | | X | | +| | 3. DHCPv4 / DHCPv6 server | | X | | +| | 4. Router advertisement, router solicitation, neighbour advertisement, neighbour solicitation (as in RFC 4861) | | X | | +| C. Support for UE mobility | 1. Forwarding of "end marker" (as long as user plane to source eNB exists) | X | | | +| | 2. Sending of "end marker" after switching the path to target node | X | X | | +| | 3. Forwarding of buffered packet | X | | | +| | 4. Change of target GTP-U endpoint within 3GPP accesses | X | X | | +| | 5. Change of target GTP-U endpoint between 3GPP and non-3GPP access | | X | | +| D. S1-Release / Buffering / Downlink Data Notification | 1. ECM-IDLE mode DL packet buffering; Triggering of Downlink Data Notification message generation per bearer (multiple, if DL packet received on higher ARP than previous DDN); Inclusion of DSCP of packet in DDN message for Paging Policy Differentiation | X | | | +| | 2. Delay Downlink Data Notification Request (if terminating side replies to uplink data after UE service request before SGW gets updated) | X | | | +| | 3. Extended buffering of downlink data when the UE is in a power saving state and not reachable (high latency communication); dropping of downlink data (if MME has requested SGW to throttle downlink low priority traffic and if the downlink data packet is received on such a bearer (see clause 4.3.7.4.1a)). | X | | | +| | 4. PGW pause of charging procedure based on operator policy/configuration the SGW (failed paging, abnormal radio link release, number/fraction of packets/bytes dropped at SGW) | X | X | | +| E. Bearer/APN policing | 1. UL/DL APN-AMBR enforcement | | X | X | +| | 2. UL/DL bearer MBR enforcement (for GBR bearer) | | X | | +| | 3. UL/DL bearer MBR enforcement (for nonGBR bearer on Gn/Gp interface) | | X | | +| F. PCC related functions | 1. Service detection (DPI, IP-5-tuple) | | X | X | +| | 2. Bearer binding (bearer QoS & TFT) | | X | | +| | 3. UL bearer binding verification and mapping of DL traffic to bearers | | X | | +| | 4. UL and DL service level gating | | X | X | +| | 5. UL and DL service level MBR enforcement | | X | X | +| | 6. UL and DL service level charging (online & offline, per charging key) | | X | X | +| | 7. Usage monitoring | | X | X | +| | 8. Event reporting (including application detection) | | X | X | +| | 9. Request for forwarding of event reporting | | | X | + +| | | | | | +|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|---|---|---| +| | 10. Redirection | | X | X | +| | 11. FMSS handling | | X | X | +| | 12. PCC support for NBIFOM | | X | | +| | 13. DL DSCP marking for application indication | | | X | +| | 14. Predefined PCC/ADC rules activation and deactivation | | X | X | +| | 15. PCC support for SDCI | | X | X | +| G. NBIFOM | Non-PCC aspects of NBIFOM | X | X | | +| H. Inter-operator accounting (counting of volume and time) | 1. Accounting per UE and bearer | X | X | | +| | 2. Interfacing OFCS through reference points specified in TS 32.240 [9] | X | X | X | +| I. Load/overload control functions | Exchange of load/overload control information and actions during peer node overload | X | X | | +| J. Lawful interception | Interfacing LI functions through reference points specified in TS 33.107 [10] and performing LI functionality | X | X | | +| K. Packet screening function | | | X | | +| L. Restoration and recovery | | X | X | X | +| M. RADIUS / Diameter on SGi | | | X | | +| N. OAM interfaces | | X | X | X | +| O. GTP bearer and path management | Generation of echo request, handling of echo response, echo request timeout and Error Indication message | X | X | | + +### 4.3.2 Functional split of SGW, PGW and TDF + +#### 4.3.2.1 Functional split of SGW + +The following table describes the functionality of the SGW-C and the SGW-U. + +All functionality performed by the SGW-U is controlled from the SGW-C and thus even if it is marked below as a SGW-U functionality only, there will be corresponding control functionality in the SGW-C. + +NOTE: Functionality not marked for SGW-U is either only provided by SGW-C or does not require any specific SGW-U behaviour. + +For interfaces not listed in the table below, Figure 4.2.1-1 describes whether they are terminated in SGW-C or SGW-U. + +Table 4.3.2-1: Functional split of SGW + +| Main functionality | Sub-functionality | SGW-C | SGW-U | Comments | +|------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|----------------------------------------| +| A. Session management (default & dedicated bearer establishment, bearer modification, bearer deactivation) | 1. Resource management for bearer resources | X | X | See clause 5.10 | +| | 2. IP address and TEID assignment for GTP-U | X | X | See clause 5.4 | +| | 3. Packet forwarding | | X | | +| | 4. Transport level packet marking | | X | | +| C. Support for UE mobility | 1. Forwarding of "end marker" (as long as user plane to source eNB exists) | | X | | +| | 2. Sending of "end marker" after switching the path to target node | X | X | See clause 5.8 | +| | 3. Forwarding of buffered packet | X | X | See clause 5.9 | +| | 4. Change of target GTP-U endpoint within 3GPP accesses | X | | | +| | 5. Change of target GTP-U endpoint between 3GPP and non-3GPP access | | | N/A | +| D. S1-Release / Buffering / Downlink Data Notification | 1. ECM-IDLE mode DL packet buffering; Triggering of Downlink Data Notification message generation per bearer (multiple, if DL packet received on higher ARP than previous DDN); Inclusion of DSCP of packet in DDN message for Paging Policy Differentiation | X | X | See clause 5.9 | +| | 2. Delay Downlink Data Notification Request (if terminating side replies to uplink data after UE service request before SGW gets updated) | X | | | +| | 3. Extended buffering of downlink data when the UE is in a power saving state and not reachable (high latency communication); dropping of downlink data (if MME has requested SGW to throttle downlink low priority traffic and if the downlink data packet is received on such a bearer (see clause 4.3.7.4.1a)). | X | X | See clause 5.9 | +| | 4. PGW pause of charging procedure based on operator policy/configuration the SGW (failed paging, abnormal radio link release, number/fraction of packets/bytes dropped at SGW) | X | | See clause 5.3.4 | +| G. NBIFOM | Non-PCC aspects of NBIFOM | X | | | +| H. Inter-operator accounting (counting of volume and time) | 1. Accounting per UE and bearer | | X | See clause 5.3 | +| | 2. Interfacing OFCS through reference points specified in TS 32.240 [9] | X | | See clause 5.3 | +| I. Load/overload control functions | Exchange of load/overload control information and actions during peer node overload | | | As defined in CT WG4 TS 29.244 [12] | +| J. Lawful interception | Interfacing LI functions through reference points specified in TS 33.107 [10] and performing LI functionality | X | X | As defined in SA WG3-LI TS 33.107 [10] | +| L. Restoration and recovery | | | | As defined in CT WG4 TS 29.244 [12] | +| N. OAM interfaces | | | | As defined in SA WG5 TS 28.708 [13] | +| O. GTP bearer and path management | Generation of echo request, handling of echo response, echo request timeout and Error Indication message | | | As defined in CT WG4 TS 29.244 [12] | + +#### 4.3.2.2 Functional split of PGW + +The following table describes the functionality of the PGW-C and the PGW-U. + +All functionality performed by the PGW-U is controlled from the PGW-C and thus even if it is marked below as a PGW-U functionality only there will be corresponding control functionality in the PGW-C. + +NOTE: Functionality not marked for PGW-U is either only provided by PGW-C or does not require any specific PGW-U behaviour. + +For interfaces not listed in the table below, Figure 4.2.1-1 describes whether they are terminated in the PGW-C or the PGW-U. + +**Table 4.3.2-2: Functional split of PGW** + +| Main functionality | Sub-functionality | PGW-C | PGW-U | Comments | +|------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|-------|------------------| +| A. Session management (default & dedicated bearer establishment, bearer modification, bearer deactivation) | 1. Resource management for bearer resources | X | X | See clause 5.10 | +| | 2. IP address and TEID assignment for GTP-U | X | X | See clause 5.4 | +| | 3. Packet forwarding | | X | | +| | 4. Transport level packet marking | | X | | +| B. UE IP address management | 1. IP address allocation from local pool | X | | See clause 5.5 | +| | 2. DHCPv4 / DHCPv6 client | X | | See clause 5.5 | +| | 3. DHCPv4 / DHCPv6 server | X | | See clause 5.5 | +| | 4. Router advertisement, router solicitation, neighbour advertisement, neighbour solicitation (as in RFC 4861) | X | | See clause 5.5 | +| C. Support for UE mobility | 1. Forwarding of "end marker" (as long as user plane to source eNB exists) | | | N/A | +| | 2. Sending of "end marker" after switching the path to target node | X | X | See clause 5.8 | +| | 3. Forwarding of buffered packet | | | N/A | +| | 4. Change of target GTP-U endpoint within 3GPP accesses | X | | | +| | 5. Change of target GTP-U endpoint between 3GPP and non-3GPP access | X | | | +| D. S1-Release / Buffering / Downlink Data Notification | 1. ECM-IDLE mode DL packet buffering; Triggering of Downlink Data Notification message generation per bearer (multiple, if DL packet received on higher ARP than previous DDN); Inclusion of DSCP of packet in DDN message for Paging Policy Differentiation | | | N/A | +| | 2. Delay Downlink Data Notification Request (if terminating side replies to uplink data after UE service request before SGW gets updated) | | | N/A | +| | 3. Extended buffering of downlink data when the UE is in a power saving state and not reachable (high latency communication); dropping of downlink data (if MME has requested SGW to throttle downlink low priority traffic and if the downlink data packet is received on such a bearer (see 4.3.7.4.1a)). | | | N/A | +| | 4. PGW pause of charging procedure based on operator policy/configuration the SGW (failed paging, abnormal radio link release, number/fraction of packets/bytes dropped at SGW) | X | | See clause 5.3.4 | +| E. Bearer/APN policing | 1. UL/DL APN-AMBR enforcement | | X | | +| | 2. UL/DL bearer MBR enforcement (for GBR bearer) | | X | | +| | 3. UL/DL bearer MBR enforcement (for nonGBR bearer on Gn/Gp interface) | | X | | +| | 1. Service detection (DPI, IP-5-tuple) | | X | | +| | 2. Bearer binding (bearer QoS & TFT) | X | | | +| | 3. UL bearer binding verification and mapping of DL traffic to bearers | | X | See clause 5.2 | +| | 4. UL and DL service level gating | | X | | +| | 5. UL and DL service level MBR enforcement | | X | | +| | 6. UL and DL service level charging (online & offline, per charging key) | X | X | See clause 5.3 | +| | 7. Usage monitoring | X | X | See clause 5.3 | + +| | | | | | +|------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|---|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| F. PCC related functions | 8. Event reporting (including application detection) | X | X | Note: User-plane related events such as application detection reporting supported in UP function, while control-plane related events such as RAT change etc. supported only in CP function. | +| | 9. Request for forwarding of event reporting | | | N/A | +| | 10. Redirection | X | X | See clause 5.11.3 | +| | 11. FMSS handling | | X | | +| | 12. PCC support for NBIFOM | X | | | +| | 13. DL DSCP marking for application indication | | | N/A | +| | 14. Predefined PCC/ADC rules activation and deactivation | X | X | See clause 5.11.1 | +| | 15. PCC support for SDCI | X | X | See clause 5.11.4 | +| G. NBIFOM | Non-PCC aspects of NBIFOM | X | | | +| H. Inter-operator accounting (counting of volume and time) | 1. Accounting per UE and bearer | | X | See clause 5.3 | +| | 2. Interfacing OFCS through reference points specified in TS 32.240 [9] | X | | See clause 5.3 | +| I. Load/overload control functions | Exchange of load/overload control information and actions during peer node overload | | | As defined in CT WG4 TS 29.244 [12] | +| J. Lawful interception | Interfacing LI functions through reference points specified in TS 33.107 [10] and performing LI functionality | X | X | As defined in SA WG3-LI TS 33.107 [10] | +| K. Packet screening function | | | X | | +| L. Restoration and recovery | | | | As defined in CT WG4 TS 29.244 [12] | +| M. RADIUS / Diameter on SGi | | X | X | See clause 5.5 | +| N. OAM interfaces | | | | As defined in SA WG5 TS 28.708 [13] | +| O. GTP bearer and path management | Generation of echo request, handling of echo response, echo request timeout and Error Indication message | | | As defined in CT WG4 TS 29.244 [12] | + +#### 4.3.2.3 Functional split of TDF + +The following table describes the functionality of the TDF-C and the TDF-U. + +All functionality performed by the TDF-U is controlled from the TDF-C and thus even if it is marked below as a TDF-U functionality only there will be corresponding control functionality in the TDF-C. + +For interfaces not listed in the table below, Figure 4.2.1-1 describes whether they are terminated in the TDF-C or TDF-U. + +Table 4.3.2-3: Functional split of TDF + +| Main functionality | Sub-functionality | TDF-C | TDF-U | Comments | +|------------------------------------------------------------|-------------------------------------------------------------------------------------|-------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E. Bearer/APN policing | 1. UL/DL APN-AMBR enforcement | | X | Not identical to APN-AMBR enforcement as it a) covers every flow in TDF session and b) does not cover other TDF sessions of the UE to the same APN | +| | 2. UL/DL bearer MBR enforcement (for GBR bearer) | | | N/A | +| | 3. UL/DL bearer MBR enforcement (for nonGBR bearer on Gn/Gp interface) | | | N/A | +| F. PCC related functions | 1. Service detection (DPI, IP-5-tuple) | | X | | +| | 2. Bearer binding (bearer QoS & TFT) | | | N/A | +| | 3. UL bearer binding verification and mapping of DL traffic to bearers | | | N/A | +| | 4. UL and DL service level gating | | X | | +| | 5. UL and DL service level MBR enforcement | | X | | +| | 6. UL and DL service level charging (online & offline, per charging key) | X | X | See clause 5.3 | +| | 7. Usage monitoring | X | X | See clause 5.3 | +| | 8. Event reporting (including application detection) | X | X | Note: User-plane related events such as application detection reporting supported in UP function, while control-plane related events such as RAT change etc. supported only in CP function. | +| | 9. Request for forwarding of event reporting | X | | | +| | 10. Redirection | X | X | See clause 5.11.3 | +| | 11. FMSS handling | | X | | +| | 12. PCC support for NBIFOM | | | N/A | +| | 13. DL DSCP marking for application indication | | X | | +| | 14. Predefined PCC/ADC rules activation and deactivation | X | X | See clause 5.11.1 | +| | 15. PCC support for SDCI | X | X | See clause 5.11.4 | +| H. Inter-operator accounting (counting of volume and time) | 1. Accounting per UE and bearer | | | N/A | +| | 2. Interfacing OFCS through reference points specified in TS 32.240 [9] | X | | See clause 5.3 | +| I. Load/overload control functions | Exchange of load/overload control information and actions during peer node overload | | | As defined in CT WG4 TS 29.244 [12] | +| L. Restoration and recovery | | | | As defined in CT WG4 TS 29.244 [12] | +| N. OAM interfaces | | | | Not defined by SA WG5 | + +### 4.3.3 User Plane Function selection + +The CP function of a functional entity performs selection of its respective UP function considering parameters such as UE's location information, capability of the UP function and features required for an UE. Additionally, the selection of UP function shall consider UP function deployment scenarios such as centrally located UP function and distributed UP functions located close to or at the RAN site. The selection of UP function shall also allow deployment of UP functions with different capabilities, e.g. UP functions supporting no or a subset of optional functionalities. + +For standalone CP functions: + +- SGW's CP function shall select SGW's UP function; +- PGW's CP function shall select PGW's UP function; +- TDF's CP function shall select TDF's UP function. + +Combined SGW/PGW's CP function should select either combined SGW/PGW UP function or standalone SGW UP and PGW UP functions. + +For details, refer to clause 5.12. + +### 4.3.4 SGW-C Partitioning + +If the SGW-U service area is smaller than the SGW-C service area, the SGW-C can be partitioned into multiple SGW-C partitions. Each of the SGW-C partition is aligned with the corresponding SGW-U service area. The MME treats the SGW-C partition as legacy SGW. + +NOTE 1: There is only one Sxa reference point between one SGW-C and one SGW-U. + +NOTE 2: This ensures that the TAI List allocated by the MME will only contain TAs that have connectivity to the SGW-U function serving the UE in case the MME uses the service area of the SGW-C partition when constructing the TAI List (and it cannot be assured that there is "full mesh" IP connectivity between the eNBs and the SGW-U function outside the SGW-U Service Area). + +NOTE 3: If more than one SGW-U is selected to serve a given UE, these SGW-U's need to cover an area including at least the service area of the SGW-C. + +## 4.4 Network elements + +### 4.4.1 General + +SGW-C and SGW-U jointly provide functionality equivalent to the functionality provided by SGW as defined by the TS 23.401 [2]. + +PGW-C and PGW-U jointly provide functionality equivalent to the functionality provided by PGW as defined by the TS 23.401 [2] and TS 23.402 [4], and the PCEF as defined by the TS 23.203 [3]. + +TDF-C and TDF-U jointly provide functionality equivalent to the functionality provided by TDF as defined by the TS 23.203 [3]. + +The clause 4.3.2 defines how the functional control and user plane split is done and which functionality SGW-C, SGW-U, PGW-C, PGW-U, TDF-C, TDF-U correspondingly support. + +### 4.4.2 SGW control plane function + +The SGW control plane function (SGW-C) provides the functionality of the SGW as defined by TS 23.401 [2] except for the functions that are performed by the SGW-U as described in table 4.3.2-1. + +In addition, the SGW-C is responsible for selecting the SGW-U (as described in clause 4.3.3) and for controlling the SGW-U with respect to the functions described in table 4.3.2-1. + +### 4.4.3 SGW user plane function + +The SGW user plane function (SGW-U) provides the functionality described in this TS. The functions that are performed by the SGW-U are listed in table 4.3.2-1 together with a reference to a detailed functional description in clause 5 for some of them. The control parameters relevant for the SGW-U are described in clause 7. + +NOTE: The standard allows certain functionalities to be supported in both SGW-C and SGW-U. For details refer to clause 5. + +### 4.4.4 PGW control plane function + +The PGW control plane function (PGW-C) provides the functionality of the PGW as defined by TS 23.401 [2] and TS 23.402 [4], and the PCEF as defined by the TS 23.203 [3] except for the functions that are performed by the PGW-U as described in table 4.3.2-2. + +In addition, the PGW-C is responsible for selecting the PGW-U (as described in clause 4.3.3) and for controlling the PGW-U with respect to the functions described in table 4.3.2-2. + +### 4.4.5 PGW user plane function + +The PGW user plane function (PGW-U) provides the functionality described in this TS. The functions that are performed by the PGW-U are listed in table 4.3.2-2 together with a reference to a detailed functional description in clause 5 for some of them. The control parameters relevant for the PGW-U are described in clause 7. + +NOTE: The standard allows certain functionalities to be supported in both PGW-C and PGW-U. For details refer to clause 5. + +### 4.4.6 TDF control plane function + +The TDF control plane function (TDF -C) provides the functionality of the TDF as defined by TS 23.203 [3] except for the functions that are performed by the TDF -U as described in table 4.3.2-3. + +In addition, the TDF -C is responsible for selecting the TDF -U (as described in clause 4.3.3) and for controlling the TDF -U with respect to the functions described in table 4.3.2-3. + +### 4.4.7 TDF user plane function + +The TDF user plane function (TDF -U) provides the functionality described in this TS. The functions that are performed by the TDF -U are listed in table 4.3.2-3 together with a reference to a detailed functional description in clause 5 for some of them. The control parameters relevant for the TDF-U are described in clause 7. + +NOTE: The standard allows certain functionalities to be supported in both TDF-C and TDF-U. For details refer to clause 5. + +# --- 5 Functional description + +## 5.1 General + +This clause contains detailed functional descriptions for some of the functions provided by the UP function of SGW, PGW and TDF (whether a function has to be supported by a functional entity is defined in clause 4.3.2). It is documented how the respective CP function instructs its corresponding UP function and which control parameters are used. + +## 5.2 Traffic detection + +### 5.2.1 General + +This clause describes the detection process at the UP function that identifies the packets belonging to a bearer, service data flow or IP-CAN/TDF session. + +The CP function is responsible for instructing the UP function about how to detect user data traffic belonging to a Packet Detection Rule (PDR). The other parameters provided within a PDR describe how the UP function shall treat a packet that matches the detection information. + +### 5.2.2 Traffic detection information + +The CP function controls the traffic detection at the UP function by providing detection information for every PDR. Detection information is a combination of: + +- UE IP address; +- F-TEIDu; +- SDF filters as defined in TS 23.203 [3]; +- Application ID (referring to an application detection filter) as defined in TS 23.203 [3]. + +The following Table 5.2.2-1 lists the possible combinations of the traffic detection information for the different UP functions and usage scenarios. + +**Table 5.2.2-1: Detection information for the different UP functions and usage scenarios** + +| Usage scenario | UP function | Detection information for UL | Detection information for DL | Description | +|----------------|-------------|-----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------| +| 1 | SGW-U | Local F-TEIDu (access side) | Local F-TEIDu (core side) | Detection of traffic belonging to a bearer | +| 2 | PGW-U | Local F-TEIDu (access side) + uplink SDF filter(s)/application ID (NOTE 2) | UE IP address as destination + downlink SDF filter(s)/application ID | Detection of traffic belonging to a service data flow + UL bearer binding verification (based on F-TEIDu in UL filter) | +| 3 | PGW-U | Local F-TEID (access side) + UE IP address as source + uplink SDF filter(s)/application ID (NOTE 2) | UE IP address as destination + downlink SDF filter(s)/application ID | Usage scenario 2 + Packet screening (based on UE IP as source in UL filter) | +| 4 | PGW-U | Local F-TEID (access side) (NOTE 1) | - | Detection of remaining traffic, e.g. with wrong UE IP address or on wrong bearer, for measurement and discarding. | +| 5 | PGW-U | - | UE IP address as destination (NOTE 1) | Detection of remaining traffic, e.g. not matching any other detection information, for discarding. | +| 6 | PGW-U | - | Downlink SDF filter(s)/application ID (NOTE 2) | Detection of RADIUS, Diameter and DHCP signalling traffic on SGi. | +| 7 | TDF-U | UE IP address as source + uplink SDF filter(s)/application ID | UE IP address as destination + downlink SDF filter(s)/application ID | Detection of traffic belonging to a service data flow | +| 8 | TDF-U | UE IP address as source (NOTE 1) | UE IP address as destination (NOTE 1) | Detecting of remaining traffic (i.e. not matching any other PDR) belonging to a TDF session | + +NOTE 1: A PDR with such detection information should have the lowest precedence amongst all the PDRs installed for this Sx session. + +NOTE 2: The detection of traffic related to UE IP address allocation as well as RADIUS, Diameter and DHCP signalling traffic on SGi can be accomplished using SDF filter(s) or an application ID (referring to an application detection filter). + +## 5.3 Charging and usage monitoring handling + +### 5.3.1 General + +If functional split of SGW into SGW-C and SGW-U is supported, the overall functionality of offline charging support as defined by TS 23.401 [2] and TS 32.251 [8] shall be preserved. + +If functional split of PGW into PGW-C and PGW-U is supported, the overall functionality of online and offline charging as defined by TS 32.251 [8], and of usage monitoring control as defined by TS 23.401 [2], TS 23.203 [3] shall be preserved. + +If functional split of TDF into TDF-C and TDF-U is supported, the overall functionality of online and offline charging as defined by TS 32.251 [8], and of usage monitoring control as defined by TS 23.203 [3] shall be preserved. + +The following principles shall apply in case of a functional split: + +- The Gx, Sd, Gy, Gyn, Gz, Gzn interfaces as well as the interface between SGW and OFCS shall be terminated in the CP function (SGW-C/PGW-C/TDF-C). This implies that the CP function shall support those interfaces towards OCS/OFCS and PCRF, based on information received at the corresponding CP function as well as gathered user-plane related information received from the UP function as further described below. +- There is no impact on PCRF, OCS and OFCS compared to non-split architecture. +- All bearer/traffic flow level, session level and subscriber related information remains at the CP function, and only usage information is requested from UP function. + +### 5.3.2 Activation of usage reporting in UP function + +Triggered by the PCC/ADC rules received from the PCRF or preconfigured information available at PGW-C/TDF-C/SGW-C, as well as from the OCS for online charging via Credit-Control session mechanisms, the CP function (PGW-C/TDF-C/SGW-C) shall provide Usage Reporting Rules to the UP function (PGW-U/TDF-U/SGW-U) for controlling how usage reporting is performed. + +The CP function shall request the report of the relevant usage information for Usage Monitoring, based on Monitoring Keys and triggers which are specified in TS 23.203 [3] and TS 29.212 [11]. Each Usage Reporting Rule requested for usage monitoring control is associated with the PDR(s) whose traffic is to be accounted under this rule. The CP function shall generate the Usage Reporting Rule for each Monitoring-key within the active PCC/ADC rule(s), either preconfigured or received from the PCRF, and also shall keep the mapping between them. Multiple Usage Reporting Rules may be associated with the same PDR. + +The CP function shall request the report of the relevant usage information for offline and online charging, based on Charging keys and additional triggers which are specified in TS 32.251 [8]. Each Usage Reporting Rule requested for offline or online charging is associated with the PDR(s) whose traffic is to be accounted under this rule. The CP function shall generate the Usage Reporting Rule for each Charging key or Sponsor Identity (if applicable) within the active PCC/ADC rule(s), either preconfigured or received from the PCRF, and also shall keep the mapping between them. Multiple Usage Reporting Rules may be associated with the same PDR. + +The CP function shall also provide reporting trigger events to the UP function for when to report usage information. The reporting trigger events (e.g. triggers, threshold information etc.) shall be supported for the session (IP-CAN/TDF) level reporting as well as on Rule level basis as determined by the CP function. The triggers may be provided as a volume, time or event to cater for the different charging/usage monitoring models supported by the TS 23.203 [3] for usage monitoring and by TS 32.251 [8] for offline and online charging. The CP function shall decide on the thresholds value(s) based on allowance received from PCRF, OCS or based on local configuration. + +In some cases, the same Usage Reporting Rule can be used for different purposes (for both usage monitoring and charging), e.g. in case the same set of PDR(s), measurement method, trigger event, threshold, etc. apply. Similarly a reported measurement can be used for different purposes by the CP function. + +### 5.3.3 Reporting of usage information towards CP function + +The UP function shall support reporting of usage information to the CP function. The UP function shall be capable to support reporting based on different triggers, including: + +- Periodic reporting with period defined by the CP function. +- Usage thresholds provided by the CP function. +- Report on demand received from the CP function. + +The CP function shall make sure that the multiple granularity levels required by the reporting keys in the Usage Reporting rules satisfy the following aggregation levels without requiring a knowledge of the granularity levels by the UP function: + +- Session level reporting (IP-CAN/TDF session); +- Bearer (for charging)/traffic flow (for both charging and usage monitoring) level reporting as defined by the reporting keys in the Usage Reporting Rule (see the description above). + +Based on the mapping between Monitoring-key and PCC/ADC rule stored at the CP function, the CP function shall combine the reported information with session and subscriber related information which is available at the CP function, for Usage Monitoring reporting over the corresponding Gx, Sd interfaces. + +Based on the mapping between Rating Group or Sponsor Identity and PCC/ADC rule stored at the CP function, the CP function shall combine the reported information with session and subscriber related information which is available at the CP function, for offline and online charging reporting over the corresponding Gy, Gyn, Gz, Gzn interfaces. + +This functionality is specified in TS 32.240 [9]. + +The usage information shall be collected in the UP function and reported to the CP function as defined in 5.3.3, based on Monitoring Keys and triggers which are specified in TS 23.203 [3] and TS 29.212 [11]. + +### 5.3.4 PGW Pause of Charging + +When the UE moves to ECM-IDLE state and the SGW-C decides to activate buffering in SGW-U for the session, it shall also instruct the SGW-U to measure the number of packets/bytes that are buffered or discarded in SGW-U and the criteria for reporting within the Usage Reporting Rule. + +Once the trigger of reporting is met, the SGW-U shall inform the SGW-C by reporting usage information. + +The SGW-C can then inform the PGW-C as described in TS 23.401 [2]. + +When the PGW-C determines to stop the charging and usage monitoring actions for the PDN connection, it shall indicate the PGW-U to stop collecting the usage information. + +PGW-C sends an Sx session modification request message to the PGW-U and modifies all the Usage Reporting Rules within the PDN connection to indicate the usage collection shall be stopped. When PGW-C determines to continue the charging action for the PDN connection, it sends an Sx session modification request message to the PGW-U and modifies all the Usage Reporting Rules within the PDN connection to indicate the usage collection shall be resumed. + +NOTE: The support for PGW pause of charging is optional as described in TS 23.401 [2], and used only if both the SGW-C and the PGW-C support this feature. + +## 5.4 GTP-U IP address and TEIDu allocation + +### 5.4.1 General + +Allocation and release of F-TEIDu is performed by SGW and PGW when a bearer needs to be established or released. If functional split into SGW-C/PGW-C and SGW-U/PGW-U is supported, F-TEIDu allocation and release is done in the UP function, as described in clause 5.4.3 below. + +The support of F-TEIDu allocation by the UP function is mandatory. + +### 5.4.2 Void + +### 5.4.3 F-TEIDu allocation / release in the UP function + +The SGW-U, the SGW-U shall manage the SGW F-TEIDu space, including ensuring that the allocated F-TEIDu(s) are unique as described in TS 29.060 [6]. In case of bearer activation, the SGW-C shall request SGW-U to allocate F-TEIDu(s) for the applicable SGW-U reference points and provide them to the SGW-C. The SGW-C shall provide the F-TEIDu(s) to other network entities as described in TS 23.401 [2] in order to complete the bearer establishment. In case of bearer deactivation, the SGW-C shall request SGW-U to release F-TEIDu(s) for the bearer. + +The PGW-U shall manage the PGW F-TEIDu space, including ensuring that the allocated F-TEIDu(s) are unique as described in TS 29.060 [6]. In case of bearer activation, the PGW-C shall request PGW-U to allocate F-TEIDu(s) for the applicable PGW-U reference points and provide them to the PGW-C. The PGW-C shall provide the F-TEIDu(s) to other network entities as described in TS 23.401 [2] and TS 23.402 [4] in order to complete the bearer establishment. In case of bearer deactivation, the PGW-C shall request PGW-U to release F-TEIDu(s) for the bearer. + +## 5.5 UE IP address management (allocation, renewal and release) + +The UE IP address management includes allocation and release of the UE IP address as well as renewal of the allocated IP address, where applicable. + +The UE IP address management shall be performed by the PGW-C. As part of this functionality, various UE IP address management mechanisms as defined in TS 23.401 [2] clause 5.3.1 are supported by the PGW-C. The PGW-C shall process the UE IP address management related messages, maintain the corresponding state information and provide the response messages to the UE. In case the UE IP address is obtained from the external PDN, additionally, the PGW-C + +shall also send the allocation, renewal and release related request messages to the external PDN and maintain the corresponding state information. The PGW-U shall support forwarding of the UE IP address management related messages to the PGW-C, when they are received via the user plane signalling from the UE or from the external PDN. + +When PGW-C performs IPv4 address allocation via default bearer activation and release via PDN connection release ( TS 23.401 [2] clause 5.3.1.2.1), no special functionality is required from the PGW-U. + +For the other UE IP address management mechanisms, the UE sends the IP address management related request messages via the user plane signalling. Hence the PGW-U is required to forward these request messages to the PGW-C for processing. Once these request messages are processed by the PGW-C, the PGW-C sends response messages to the UE via the user plane signalling. Hence the PGW-C is required to forward these response messages to the PGW-U so that it can be relayed to the UE. Correspondingly, following functionality is required to be supported by the PGW-C and PGW-U: + +- For IPv6 default prefix management via IPv6 stateless address autoconfiguration ( TS 23.401 [2] clause 5.3.1.2.2): PGW-C shall configure PGW-U to forward Router Solicitation and Neighbor Solicitation messages from the UE to the PGW-C. The PGW-C shall forward Router Advertisement and Neighbor Advertisement messages to the PGW-U for relaying them to the UE. +- For IPv6 parameter configuration via stateless DHCPv6 ( TS 23.401 [2] clause 5.3.1.2.3): PGW-C shall configure PGW-U to forward all the DHCPv6 messages from the UE to the PGW-C. The PGW-C shall forward the DHCPv6 response messages to the PGW-U for relaying them to the UE. +- For IPv4 address management and parameter configuration DHCPv4 ( TS 23.401 [2] clause 5.3.1.2.4): PGW-C shall configure PGW-U to forward all the DHCPv4 messages from the UE to the PGW-C. The PGW-C shall forward the DHCPv4 response messages to PGW-U for relaying them to the UE. +- For IPv6 prefix management via IPv6 prefix delegation ( TS 23.401 [2] clause 5.3.1.2.6): PGW-C shall configure PGW-U to forward all the DHCPv6 messages from the UE to the PGW-C. The PGW-C shall forward the DHCPv6 response messages to PGW-U for relaying them to the UE. + +In addition to the above, when the UE IP address is obtained from the external PDN, following functionality is required to be supported by the PGW-C and PGW-U: + +- For UE IP address from AAA server in the external PDN: If the AAA server in the external PDN is reachable only via the PGW-U the PGW-C shall configure the PGW-U to forward all the Diameter or RADIUS messages from the AAA server in the external PDN to the PGW-C. And the PGW-C shall forward the Diameter or RADIUS messages to the PGW-U for relaying them to the AAA server in the external PDN. +- For UE IP address from DHCPv4/v6 server in the external PDN: If the DHCPv4/v6 server in the external PDN is reachable only via the PGW-U the PGW-C shall configure the PGW-U to forward all the DHCPv4/v6 messages from the DHCPv4/v6 server in the external PDN to the PGW-C. And the PGW-C shall forward the DHCPv4/v6 messages to the PGW-U for relaying them to the DHCPv4/v6 server in the external PDN. + +NOTE: If the AAA server or the DHCPv4/v6 server in the external PDN is reachable directly, then the PGW-C communicates with it directly, without involving the PGW-U. + +## 5.6 Control of user plane forwarding + +### 5.6.1 General + +One of the main tasks of the Sx interface is to enable the CP function to instruct the UP function about how to forward user data traffic. There are several different user plane forwarding scenarios supported. Some scenarios are applicable to SGW only or PGW only, while other scenarios are applicable to SGW and PGW or PGW and TDF. A non-exhaustive list of forwarding scenarios is provided in Table 5.6.2-1 below. + +The CP function shall be able to provide the UP with instructions for at least the following behaviors: forward, forward with end marker. The CP function shall also be able to request multiple sets of forwarding instructions to be performed in sequence, e.g. forward to the DL side and forward to the CP function for the purpose of duplication. + +### 5.6.2 Control of user plane forwarding + +The CP function controls user-plane packet forwarding for traffic detected by a PDR by providing FAR(s) with instructions to the UP function, including: + +- Forwarding operation information; +- Forwarding target information. + +The details of the forwarding target and operation will depend on the scenario and is described in Table 5.6.2-1 below. The following forwarding functionality is required by the UP function (more than one forwarding scenario can be active for the same traffic): + +- Apply GTP-U bearer related handling, i.e. encapsulation, de-capsulation or both. (This covers scenario 1 in the table below). +- Forward the traffic to the CP function (This covers scenario 2, 3, 4 in the table below). +- Apply locally configured policy for traffic steering. (This covers scenario 5 in the table below). + +Further details on the forwarding related information are provided in clause 7.5. + +**Table 5.6.2-1: Forwarding information for different scenarios** + +| | Scenario description | Forwarding target and operation | Applicable to | +|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|---------------| +| 1 | Forwarding of user-plane between UE and PDN, including mapping onto GTP-U tunnels and mapping between GTP-U tunnels | GTP-U encapsulation information (F-TEID) | SGW, PGW | +| 2 | Forwarding of user-plane packets from UE and CP function (e.g. RS/RA, DHCPv4/v6, traffic subject to HTTP redirect etc) | Information that the CP function is source/target (CP function IP address) | PGW | +| 3 | Forwarding of packets from the external PDN / SGi and the CP function (e.g. for RADIUS, Diameter and DHCP signalling, traffic subject to HTTP redirect etc) | Information that the CP function is source/target (CP function IP address) | PGW | +| 4 | Forwarding of packets subject to buffering in CP function | Information that the CP function is source/target (CP function IP address) | SGW | +| 5 | Forwarding of packets between the UP function and the SGi-LAN for Flexible Mobile Service Chaining | Reference to a predefined traffic steering configuration (e.g. Traffic-Steering Policy identifier) | PGW, TDF | + +### 5.6.3 Format of forwarded user plane data + +For forwarding between the CP function and UP function the user plane packet is forwarded via an Sx-u tunnel by encapsulating the user-plane packet using GTP-U protocol that allows the receiving entity to identify which PDN Connection and which bearer the traffic belongs to. In the direction from the CP function to UP function for forwarding towards the UE or PDN, the UP encapsulation protocol also shall contain information that allows the UP function to identify whether the UE or PDN is targeted. + +NOTE: The Sx-u tunnel may be established per bearer of a PDN connection, or per PDN or per UP function. The details of Sx-u tunnel are defined in TS 29.244 [12]. + +## 5.7 UE's permanent identifier usage + +For the scenarios requiring UE's permanent identity at the UP function, e.g. UP function performing http header enrichment in a trusted environment, the UE's permanent identity may be provided from the CP function to the UP function in a container, instead of in an Sx parameter. + +NOTE: In an untrusted environment in which the UE's permanent identity cannot be provided, due to e.g. to fulfil the privacy requirements, the session identifier is used between the CP function and UP function for correlating UE's session related events. + +## 5.8 Functionality of sending of "end marker" + +Sending of "end marker" is a functionality which involve SGW-C and SGW-U, and PGW-C and PGW-U. As part of the functionality, constructing of end marker packets can either be done in the CP function or in the UP function, as described in clauses 5.8.1 and 5.8.2. Whether constructing of end marker packets is performed by CP function or UP function is determined by network configuration. + +### 5.8.1 UP function constructing the "end marker" packets + +In case of eNodeB relocation during handover procedure without SGW-U change, SGW-C shall indicate the SGW-U to switch the S1 path(s) by sending an Sx session modification request message with the new F-TEID-u of eNodeB and in addition, provide an indication to the SGW-U to send the end marker packet(s) on the old path. + +On receiving this indication, the SGW-U shall construct end marker packet(s) and send it for each S1 GTP-U tunnel towards the source eNodeB after sending the last PDU on the old path. + +In case of SGW-U relocation during handover procedure, PGW-C shall indicate the PGW-U to switch the S5/S8 path(s) by sending an Sx session modification request message (bearer ID, new F-TEID of SGW-U) and in addition, provide an indication to the PGW-U to send the end marker packet(s) on the old path. + +On receiving this indication, the PGW-U shall construct end marker packet(s) and send it for each S5/S8 GTP-U tunnel towards the source SGW-U after sending the last PDU on the old path. + +On receiving the end marker packet(s) on S5/S8 GTP-U tunnel, SGW-U shall forward the end marker packet(s) and send it for each S1 GTP-U tunnel towards the source eNodeB. + +### 5.8.2 CP function constructing the "end marker" packets + +In case of eNodeB relocation during handover procedure without SGW-U change, SGW-C shall indicate the SGW-U to switch the S1 path(s) by sending an Sx session modification request message (bearer ID, new F-TEID of eNodeB). After sending the last PDU on the old path, SGW-U shall replace the old F-TEID with the new one and responds with an Sx session modification response message to acknowledge the success of path switch. + +When the path switch is finished, SGW-C constructs the end marker packet(s) and sends it to the SGW-U. SGW-U then forwards the packet(s) to the source eNodeB. + +In case of SGW-U relocation during handover procedure, PGW-C shall indicate the PGW-U to switch the S5/S8 path(s) by sending an Sx session modification request message (bearer ID, new F-TEID of SGW-U). After sending the last PDU on the old S5/S8 path, PGW-U shall replace the old F-TEID with the new one and responds with an Sx session modification response message to acknowledge the success of path switch. + +When the path switch is finished, PGW-C constructs the end marker packet(s) and sends it to PGW-U. PGW-U then forwards the packet(s) to the source SGW-U. + +## 5.9 Idle state packet SGW buffering function + +### 5.9.1 General + +Buffering of the UE's data packets for the UE in idle or power saving mode can be performed in SGW-U or SGW-C. + +The support of buffering in the SGW-U is mandatory and the SGW-C shall support buffering by the SGW-U. + +The support of buffering in the SGW-C is optional and the SGW-U optionally supports buffering by the SGW-C. An exception is that in a dedicated core network serving UEs which may enter power saving mode or apply eDRX, e.g. NB-IoT UEs, the SGW-C shall support buffering capability. + +When buffering is supported in both SGW-C and SGW-U, the SGW-C decides on a per UE session basis (e.g. based on local configuration and other information such as UE capability) to perform buffering in either the SGW-C or the SGW-U. + +### 5.9.2 Buffering in CP function + +When the UE moves to ECM-IDLE state, if the SGW-C supports buffering capability and decides to activate buffering, the SGW-C shall inform the SGW-U to stop sending data packets to eNodeB and start forwarding the downlink data packets towards the SGW-C. + +When the UE transition to the ECM-CONNECTED state, the SGW-C shall update the SGW-U via Sxa interface with the F-TEIDu of the eNodeB. If there are buffered packets available and their buffering duration has not expired, the SGW-C shall forward those packets to the SGW-U outside of the control plane signalling (see clause 5.6.3 "Format of forwarded user plane data") to relay them to the UE. These packets are then forwarded by the SGW-U to the eNodeB. + +### 5.9.3 Buffering in UP function + +#### 5.9.3.1 General + +The SGW-C shall be able to provide the SGW-U with instructions for at least the following behaviors: buffer without reporting the arrival of first downlink packet, buffer with reporting the arrival of first downlink packet, drop packets. + +When the UE moves to ECM-IDLE state, if the SGW-C does not support buffering capability, or if the SGW-C supports buffering capability and decides to activate buffering in SGW-U for the session, the SGW-C shall inform the SGW-U, via an Sx session modification. The SGW-C decides whether buffering timers are handled by the SGW-U or by the SGW-C. The activation of buffering implicitly stops sending data to the eNodeB/RNC/SGSN. + +After starting the buffering, when the first downlink packet arrives on any bearer, SGW-U shall inform the SGW-C. SGW-U sends an Sx reporting message to the SGW-C unless specified otherwise and identifies the S5/S8 bearer on which the downlink packet was received. + +On receiving this reporting message, the SGW-C decides whether to send a Downlink Data Notification message to the MME as defined in TS 23.401 [2]. + +At the UE transition to ECM-CONNECTED state, the SGW-C shall update the SGW-U via Sxa interface with the F-TEIDu of the eNodeB/RNC/SGSN. The buffered data packets, if any, are then forwarded to the eNodeB/RNC/SGSN by the SGW-U. + +In case of SGW-U relocation, buffered data packets are transferred from the old SGW-U to the new SGW-U. + +#### 5.9.3.2 Delay Downlink Packet Notification + +According to clause 5.3.4.2 of TS 23.401 [2], the MME/SGSN may inform the SGW that for all UEs served by the MME/SGSN, the Downlink Packet Data Notification shall be delayed for a period D. + +If the parameter D is handled by the SGW-U, the SGW-C shall include the parameter D in the Sx session establishment for new Sx sessions, in the Sx session modification for Sx sessions which are not in buffering state (when transitioning these sessions to the buffering state), and in the next Sx report ack message for Sx sessions already in buffering state. The SGW-U shall then delay the sending of subsequent Sx reporting upon next DL data arrival. + +If the parameter D is handled by the SGW-C, there is no special handling compared to clause 5.9.3.1. When the SGW-U reports the arrival of a DL data packet, the SGW-C shall delay the sending of the Downlink Data Notification to the MME by parameter D delay. + +#### 5.9.3.3 Extended buffering + +According to clauses 5.3.4.3 and 5.7.3 of TS 23.401 [2], the MME/SGSN invoking extended buffering indicates it to the Serving GW in the Downlink Data Notification Ack message, includes a DL Buffering Duration time and optionally a DL Buffering Suggested Packet Count. + +If the MME/SGSN included the DL Suggested Packet Count, the SGW-C shall include the DL Suggested Packet Count in the Sx reporting Ack message. + +If the DL Data Buffer Expiration Time is handled by the SGW-U, the SGW-C includes it in the Sx reporting Ack message and requests the SGW-U to buffer DL data packets. When the SGW-U receives the DL Data Buffer Expiration Time, the SGW-U buffers the DL data packets without reporting the arrival of the first DL data packet until the DL + +Data Buffer Expiration Time expires. When the DL Data Buffer Expiration Time expires, the SGW-U shall discard the buffered DL packets and shall restart buffering DL data packets with reporting the arrival of the first DL data packet. + +If the DL Data Buffer Expiration Time is handled by the SGW-C, the SGW-C requests the SGW-U to buffer the DL data packets without reporting the arrival of the first DL data packet. When the DL Data Buffer Expiration Time expires, the SGW-C requests the SGW-U to drop the buffered data packets and to start buffering the DL data packets with reporting of the arrival of the first DL data packet, via an Sx Session Modification. + +If the DL Suggested Packet Count was included in the request from the SGW-C, the SGW-U buffers the DL data packets up to the number of packets indicated by the DL Suggested Packet Count. + +#### 5.9.3.4 Throttling + +According to clause 4.3.7.4.1a of TS 23.401 [2], the MME/SGSN can request the SGWs to selectively reduce the number of Downlink Data Notification requests it sends for downlink non-priority traffic received for UEs in idle mode according to a throttling factor and for a throttling delay specified in the Downlink Data Notification Ack message. + +Throttling mechanism by which the MME uses Downlink Data Notification Acknowledgement messages DL low priority traffic Throttling parameters, is handled by the SGW-C as follows: + +- On receiving Downlink Data Notification Acknowledgement from the MME/SGSN, the SGW-C determines which bearers are subject to the throttling of Downlink Data Notification requests on the basis of the bearer's ARP priority level and the operator policy. +- Upon receipt of an Sx report notifying the arrival of DL data packets on those bearers, the SGW-C decides whether or not to send a DDN to MME based on the requested throttling factor. The SGW-C may indicate in the Sx Report Ack whether SGW-U shall discard the buffered packet and may also indicate whether SGW-U shall notify when additional DL packets arrive. +- The throttling delay timer and throttling factor are handled by the SGW-C and not provided to SGW-U. + +## 5.10 Bearer and APN policing + +ARP is used for admission control (i.e. retention and pre-emption of the bearer). The value of ARP is not required to be provided to the UP function. + +For every bearer, SGW-C/PGW-C shall use the QCI and optionally, the ARP priority level, to determine the transport level packet marking and provide the transport level packet marking to the SGW-U/PGW-U. + +PGW-C shall provide the APN-AMBR value together with a QoS Enforcement Rule correlation ID (as described in clause 7.6) to PGW-U so that the PGW-U can enforce the APN-AMBR across all IP-CAN sessions of the UE to the same APN at the PGW-U. + +SGW-C/PGW-C shall provide the GBR and MBR value for each GBR bearer of the PDN connection to the SGW-U/PGW-U. When the Gn/Gp interface is used by the PGW-U, PGW-C shall also provide the MBR value to the PGW-U for each non-GBR bearer of the PDN connection on the Gn/Gp interface. + +TDF-C shall provide the TDF session MBR value to TDF-U to be applied to the TDF session of the UE. + +## 5.11 PCC/ADC related functions + +### 5.11.1 Activation/Deactivation of predefined PCC/ADC rules + +A predefined PCC/ADC rule is configured in the CP function. + +The traffic detection filters required in the UP function can be configured either in the CP function and provided to the UP function, as service data flow filter(s), or be configured in the UP function, as the application detection filter identified by an application identifier. For the latter case, the application identifier has to be configured in the CP function and the UP function. + +The traffic steering policy information can be only configured in the UP function, together with traffic steering policy identifier(s), while the CP function has to be configured with the traffic steering policy identifier(s). + +Policies for traffic handling in the UP function, which are referred by some identifiers corresponding to the parameters of a PCC/ADC rule, can be configured in the UP function. These traffic handling policies are configured as predefined QER(s), FAR(s) and URR(s). + +When a predefined PCC/ADC rule is activated/deactivated by the PCRF, PGW-C/TDF-C shall decide what information has to be provided to the PGW-U/TDF-U to enforce the rule based on where the traffic detection filters (i.e. service data flow filter(s) or application detection filter), traffic steering policy information and the policies used for the traffic handling in the UP function are configured and where they are enforced: + +- If the predefined PCC/ADC rule contains an application identifier for which corresponding application detection filters are configured in the UP function, the PGW-C/TDF-C shall provide a corresponding application identifier to the UP function; +- If the predefined PCC/ADC rule contains traffic steering policy identifier(s), the PGW-C/TDF-C shall provide a corresponding traffic steering policy identifier(s) to the UP function; +- If the predefined PCC/ADC rule contains service data flow filter(s), the PGW-C/TDF-C shall provide them to the PGW-U/TDF-U; +- If the predefined PCC/ADC rule contains some parameters for which corresponding policies for traffic handling in the UP function are configured in the UP function, the PGW-C/TDF-C shall activate those traffic handling policies via their rule ID(s). + +The CP function shall maintain the mapping between a PCC/ADC rule received over Gx/Sd and the flow level PDR rule(s) used on Sx. + +### 5.11.2 Enforcement of dynamic PCC/ADC rules + +The application detection filters required in the UP function can be configured either in the CP function and provided to the UP function as the service data flow filter, or be configured in the UP function identified by an application identifier. + +When receiving a dynamic PCC/ADC rule from the PCRF which contains an application identifier and/or parameters for traffic handling in the UP function: + +- if the application detection filter is configured in the PGW-C/TDF-C, the PGW-C/TDF-C shall provide it in the service data flow filter to the UP function, as well as parameters for traffic handling in the UP function received from the dynamic PCC/ADC rule; +- otherwise, the application detection filters is configured in UP function, the PGW-C/TDF-C shall provide to PGW-U/TDF-U with the application identifier and the parameters for traffic handling in the UP function as required based on the dynamic PCC/ADC rule. + +The CP function shall maintain the mapping between a PCC/ADC rule received over Gx/Sd and the flow level PDR(s) used on Sx. + +### 5.11.3 Redirection + +The uplink application's traffic redirection may be enforced either in the PGW-C/TDF-C (as specified in 5.4.2 Control of user plane forwarding) or directly in the UP function. The redirect destination may be provided in the dynamic PCC/ADC rule or be preconfigured, either in the CP function or in the UP function. + +When receiving redirect information (redirection enabled/disabled and redirect destination) within a dynamic PCC/ADC rule or being activated/deactivated by the PCRF for the predefined redirection policies, PGW-C/TDF-C shall decide whether to provide and what information to be provided to the UP function based on where the redirection is enforced and where the redirect destination is acquired/preconfigured. When redirection is enforced in the UP function and the redirect destination is acquired from the dynamic PCC/ADC rule or is configured in the CP function, CP function shall provide the redirect destination to the UP function. When redirection is enforced in the CP function, CP function shall instruct the UP function to forward applicable user plane traffic to the CP function. + +### 5.11.4 Support of SDCI + +PFDF shall provide PFD(s) to the PGW-C/TDF-C on the request of PGW-C/TDF-C (pull mode) or on the request of PFD management from SCEF (push mode), as described in TS 23.203 [3]. The PGW-C/TDF-C shall provide the PFD(s) to the PGW-U/TDF-U, on which the Application ID corresponding to the PFD(s) is active. + +The PGW-C/TDF-C supports the procedures for Gw/Gwn as specified in TS 23.203 [3], for management of PFDs. PFD(s) is cached in the PGW-C/TDF-C, and the PGW-C/TDF-C maintains a caching timer associated to the PFD(s). When the caching timer expires and there's no active PCC/ADC rule that refers to the corresponding application identifier, the PGW-C/TDF-C informs the PGW-U/TDF-U to remove the PFD(s) identified by the application identifier using the PFD management message. + +When a PDR is provided for an Application ID corresponding to the PFD(s) that are not already provided to the PGW-U/TDF-U, the PGW-C/TDF-C shall provide the PFD(s) to the PGW-U/TDF-U (if there are no PFD(s) cached, the PGW-C/TDF-C retrieves them from the PFDF as specified in TS 23.203 [3]). When any update of the PFD(s) is received from PFDF by PGW-C/TDF-C (using "push" or "pull" mode), and there are still active PDRs in PGW-U/TDF-U for the Application ID, the PGW-C/TDF-C shall provision the updated PFD set corresponding to the Application ID to the PGW-U/TDF-U using the PFD management message. + +NOTE 1: PGW-C/TDF-C should assure not to overload Sx signalling while managing PFD(s) to the UP function, e.g. forwarding the PFD(s) to the right UP function where the PFD(s) is enforced. + +When the PGW-U/TDF-U receives the updated PFD(s) from either the same or different PGW-C/TDF-C for the same application identifier, the latest received PFD(s) shall overwrite any existing PFD(s) stored in the UP function. + +NOTE 2: For the case a single UP function is controlled by multiple CP functions, the conflict of PFD(s) corresponding to the same application identifier provided by different CP functions should be avoided by operator enforcing a well-planned PFDF and CP/UP function deployment. + +When a PFD is removed/modified and this PFD was used to detect application traffic related to an application identifier in a PDR of an Sx session and the PGW-U/TDF-U has reported the application start as described in clause 6.4.2 to the PGW-C/TDF-C for the application instance corresponding to this PFD, the PGW-U/TDF-U shall report the application stop to the PGW-C/TDF-C for the corresponding application instance identifier if the removed/modified PFD in PGW-U/TDF-U results in that the stop of the application instance is not being able to be detected. + +If the PFDs are managed by local O&M procedures, PFD retrieval is not used; otherwise, the PFDs retrieved from PFDF override any PFDs pre-configured in the PGW-C/TDF-C. When all the PFDs retrieved from the PFDF for an application identifier are removed, the pre-configured PFDs are used. The PGW-C/TDF-C shall provide either the PFDs retrieved from PFDF or the pre-configured PFDs for an application identifier to the PGW-U/TDF-U as specified in clause 6.5.2. + +## 5.12 User Plane function selection + +### 5.12.1 General + +The selection of the UP function (SGW-U, PGW-U, TDF-U, combined SGW/PGW-U) is performed by its respective CP function (SGW-C, PGW-C, TDF-C, combined SGW/PGW-C). + +The UP function's capabilities shall be signalled during the initial connection establishment between the CP function and the UP function. + +The CP function shall be made dynamically aware on the UP function load and relative static capacity for which it has an established Sx session as specified in the clauses below. + +The exact set of parameters used for the selection mechanism is deployment specific and controlled by the operator configuration, e.g. UE capabilities such as the UE support for dual connectivity with NR, and, the UE's location information may be used for selecting UP function in some deployments while may not be used in other deployments. + +### 5.12.2 Selection of PGW-U + +For PGW-U selection, the PGW-C shall be able to consider the following parameters: + +- the PGW-U's dynamic load, at the node level (the PGW-C may then derive the load at the APN level); +- the PGW-U's relative static capacity (among PGW-U's supporting the same APN); +- the PGW-U location configured in the PGW-C and the UE location information provided by the MME/SGSN in order to select the appropriate PGW-U, e.g. for SIPTO above RAN service; +- the capability of the UP function and the functionality required for the particular UE session: An appropriate UP function can be selected by matching the functionality and features required for an UE (which can be derived from the information received over S11/S4/S5/S8 (e.g. APN, mapped UE Usage Type, UE location information, UE capabilities (e.g. UE support for dual connectivity with NR)) or from the PCRF (e.g. need to perform DPI)) with the capabilities of the UP function so as to fulfil the service for the UE, e.g. if L7 based traffic detection is needed then an UP function supporting corresponding functionality needs to be selected. +- to enable APN-AMBR enforcement, whether a PDN connection already exists for the same UE and APN, in which case the same PGW-U shall be selected; + +The criteria for PGW-U selection may include load balancing between PGW-U's. + +The PGW-C may support the Sx Load Control feature. + +In order to allow the PGW-C to select a PGW-U according to above parameters: + +- the SGW-C shall provide the relevant UE's capabilities when available (e.g. UE support for dual connectivity with NR) over the S5/S8 interface. +- the SGW-C may provide the mapped UE Usage Type over the S5 interface. + +### 5.12.3 Selection of SGW-U + +For SGW-U selection, the SGW-C shall be able to consider the following parameters: + +- the SGW-U location (e.g. SGW Service Area) and the UE location information, provided by the MME/SGSN in order to select a UP function close to the UE's point of attachment; +- the SGW-U's dynamic load; +- the SGW-U's relative static capacity (versus other SGW-U's); +- the capability of the UP function and the functionality required for the particular UE session: An appropriate UP function can be selected by matching the functionalities and features required for an UE (which can be derived from the information received over S11/S4 (e.g. individual CIoT capabilities, UE Usage Type, the APN (for selection of combined SGW/PGW), UE capabilities (e.g. UE support for dual connectivity with NR)) with the capabilities of the UP function so as to fulfil the service requirement for the UE then a UP function supporting corresponding functionality needs to be selected. + +The criteria for SGW-U selection may include load balancing between SGW-U's. + +The SGW-C may support the Sx Load Control feature. + +In order to allow the SGW-C to select a SGW-U according to the above parameters: + +- the MME/SGSN shall provide the location of the UE (i.e. ECGI, eNB or TAI for E-UTRAN, and RAI or RNC-ID for UTRAN), the APN (for selection of a combined SGW/PGW), relevant UE capabilities when available (e.g. UE support for dual connectivity with NR) and may provide the mapped UE Usage Type in the Create Session Request over the S11/S4 interface; + +NOTE: MME sets the UE support for dual connectivity with NR indication when the UE indicates support for NR and there is no Access Restriction for NR for the UE (see TS 23.401 [2] clause 4.3.2a). + +### 5.12.4 Selection of a combined SGW/PGW-U + +A combined SGW/PGW-C selects the SGW-U and PGW-U as defined respectively in clauses 5.12.3 and 5.12.4, with the following addition: + +- The SGW-C determines that it is a combined SGW/PGW-C entity the same way as in the non-split case; +- The combined SGW/PGW-C may optimize UP function selection by selecting the best couple of SGW-U and PGW-U for the requested APN, among all candidate couples of (SGW-U, PGW-U), instead of selecting independently the SGW-U first and then the PGW-U (which may result in selecting non-co-located SGW-U and PGW-U). + +### 5.12.5 Selection of TDF-U + +#### 5.12.5.1 Solicited application reporting mode + +TDF-C shall select TDF-U at PDN connection establishment (TDF session establishment). + +The selection may be based on the following parameters: + +- the TDF-U's dynamic load; +- the TDF-U's relative static capacity; +- the capability of the UP function and the functionalities and the capabilities required for the particular UE session: An appropriate UP function can be selected by matching the functionalities and features required for the UE from the PCRF. + +The criteria for TDF-U selection includes load balancing between TDF-U's. + +The TDF-C may support the Sx Load Control feature. + +#### 5.12.5.2 Unsolicited application reporting mode + +The selection of TDF-U for the unsolicited application reporting is performed by TDF-C during the Sx management procedure, using the information configured in TDF-C. + +NOTE: TDF-C provides the instructions for application detection and reporting to the TDF-U during the Sx session management procedure. TDF-U shall communicate with the TDF-C (using the same Sx session) when application reporting is necessary, based on instructions provided by TDF-C. + +# --- 6 Information flows + +Editor's note: This clause will document the Sx information flows and their usage for the various existing procedures. + +## 6.1 General + +This clause defines the procedures that are used for the interaction between SGW-C and SGW-U, PGW-C and PGW-U, TDF-C and TDF-U, and documents how these procedures shall be embedded into existing procedures of TS 23.401 [2], TS 23.402 [4], TS 23.060 [5] and TS 23.203 [3]. + +NOTE: TS 23.401 [2], TS 23.402 [4], TS 23.060 [5] and TS 23.203 [3] do not reflect control and user plane separation of SGW, PGW or TDF and thus the procedures in these specifications do not show the interaction between the respective CP function and UP function. In case of any discrepancies, the procedures defined in TS 23.401 [2], TS 23.402 [4], TS 23.060 [5] and TS 23.203 [3] apply. + +## 6.2 Sx Session Management Procedures + +### 6.2.1 General + +Sx session management procedures are used to control the functionality of the UP function, which involve SGW, PGW or TDF. The CP function can create, update and remove the Sx session context (i.e. the parameters related to a PDN connection, IP-CAN session, TDF session or TDF in unsolicited reporting mode) in the UP function. + +The following Sx session management procedures exist: Sx session establishment procedure, Sx session modification procedure and Sx session termination procedure. All of them are initiated by the CP function. + +### 6.2.2 Sx Session Establishment Procedure + +The Sx session establishment procedure is used to create the initial Sx session context for a PDN connection, IP-CAN session, TDF session or TDF in unsolicited reporting mode at the UP function. The CP function assigns a new Session ID and provides it to the UP function. The Session ID is stored by both entities and used to identify the Sx session context during their interaction. The CP function stores also the relation between the Session ID and PDN connection, IP-CAN session, TDF session or TDF in unsolicited reporting mode and can then correlate events reported by the UP function to them. + +During PDN connection establishment, the Sx session establishment procedure is executed between SGW-C and SGW-U as well as PGW-C and PGW-U. The Sx session context comprises the parameters for the default as well as every dedicated bearer of the PDN connection. In addition, the Sx session context for the PGW-U comprises IP-CAN session related parameters. + +During SGW-U relocation, the Sx session establishment procedure is executed between SGW-C and the target SGW-U. The Sx session context comprises the parameters for the default as well as every dedicated bearer of the PDN connection. + +During TDF session establishment, the Sx session establishment procedure is executed between TDF-C and TDF-U. The Sx session context comprises TDF session related parameters. + +For a TDF in unsolicited reporting mode, the Sx session establishment procedure is executed between TDF-C and the TDF-U selected during Sx management procedure. The Sx session context comprises the instructions for application detection and reporting in unsolicited reporting mode. + +![Sequence diagram of the Sx session establishment procedure between UP and CP functions.](40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg) + +``` +sequenceDiagram + participant CP function + participant UP function + Note right of CP function: 1. Trigger to establish new PDN connection or TDF session + CP function->>UP function: 2. Sx Session Establishment Request + UP function->>CP function: 3. Sx Session Establishment Response + Note right of CP function: 4. Interaction with other network entity +``` + +The diagram illustrates the Sx session establishment procedure between the UP function and the CP function. It starts with the CP function receiving a trigger to establish a new PDN connection or TDF session. The CP function then sends an Sx Session Establishment Request to the UP function. The UP function responds with an Sx Session Establishment Response. Finally, the CP function interacts with other network entities. + +Sequence diagram of the Sx session establishment procedure between UP and CP functions. + +Figure 6.2.2-1 Sx session establishment procedure + +NOTE: In case of a TDF in unsolicited reporting mode, the procedure is triggered by TDF configuration and step 1 and 4 do not apply. + +1. CP function receives the trigger to establish a new PDN connection or TDF session from a peer CP function, an MME or a PCRF. +2. The CP function sends an Sx session establishment request message to the UP function that contains the structured control information which defines how the UP function needs to behave. + +3. The UP function responds with an Sx session establishment response message containing any information that the UP function has to provide to the CP function in response to the control information received. +4. The CP function interacts with the network entity which triggered this procedure (e.g. a peer CP function, an MME or a PCRF). + +### 6.2.3 Sx Session Modification Procedure + +The Sx session modification procedure is used to update the Sx session context of an existing PDN connection, IP-CAN session, TDF session or TDF in unsolicited reporting mode at the UP function. + +The Sx session modification procedure is executed between SGW-C and SGW-U whenever PDN connection related parameters have to be modified, as well as between PGW-C and PGW-U whenever PDN connection or IP-CAN session related parameters have to be modified. + +The Sx session modification procedure is executed between TDF-C and TDF-U whenever TDF session related parameters have to be modified. + +For a TDF in unsolicited reporting mode, the Sx session modification procedure is executed between TDF-C and TDF-U whenever instructions for application detection and reporting have to be modified. + +![Sequence diagram of the Sx session modification procedure between UP function and CP function.](c85b57b2414f341860dfc338e1cf2509_img.jpg) + +``` +sequenceDiagram + participant CP function + participant UP function + Note right of CP function: 1. Trigger to modify PDN connection or TDF session + CP function->>UP function: 2. Sx Session Modification Request + UP function-->>CP function: 3. Sx Session Modification Response + Note right of CP function: 4. Interaction with other network entity +``` + +Sequence diagram of the Sx session modification procedure between UP function and CP function. + +Figure 6.2.3-1 Sx session modification procedure + +NOTE: In case of a TDF in unsolicited reporting mode, the procedure is triggered by TDF configuration and step 1 and 4 do not apply. + +1. CP function receives the trigger to modify the existing PDN connection or TDF session from a peer CP function, an MME or a PCRF. +2. The CP function sends an Sx session modification request message to the UP function that contains the update for the structured control information which defines how the UP function needs to behave. +3. The UP function identifies the Sx session context to be modified by the Session ID. Then, the UP function updates the parameters of this Sx session context according to the list of parameters sent by the CP function. The UP function responds with an Sx session modification response message containing any information that the UP function has to provide to the CP function in response to the control information received. +4. The CP function interacts with the network entity which triggered this procedure (e.g. a peer CP function, an MME or a PCRF). + +### 6.2.4 Sx Session Termination Procedure + +The Sx session termination procedure is used to remove the Sx session context of an existing PDN connection, IP-CAN session, TDF session or TDF in unsolicited reporting mode at the UP function. + +![Sequence diagram of the Sx session termination procedure between UP and CP functions.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +``` + +sequenceDiagram + participant CP function + participant UP function + Note right of CP function: 1. Trigger to terminate PDN connection or TDF session + CP function->>UP function: 2. Sx Session Termination Request + UP function-->>CP function: 3. Sx Session Termination Response + Note right of CP function: 4. Interaction with other network entity + +``` + +The diagram illustrates the Sx session termination procedure. It involves two main entities: the UP function and the CP function. The sequence of events is as follows: + + +- The CP function receives a trigger to terminate a PDN connection or TDF session (shown in a box above the CP function lifeline). +- The CP function sends an "Sx Session Termination Request" message to the UP function. +- The UP function responds with an "Sx Session Termination Response" message to the CP function. +- The CP function then interacts with other network entities (shown in a box below the CP function lifeline). + +Sequence diagram of the Sx session termination procedure between UP and CP functions. + +**Figure 6.2.4-1 Sx session termination procedure** + +NOTE: In case of a TDF in unsolicited reporting mode, the procedure is triggered by TDF configuration and step 1 and 4 do not apply. + +1. CP function receives the trigger to terminate the existing PDN connection or TDF session from a peer CP function, an MME or a PCRF. +2. The CP function sends an Sx session termination request message to the UP function. +3. The UP function identifies the Sx session context to be terminated by the Session ID and removes the whole session context. The UP function responds with an Sx session termination response message containing any information that the UP function has to provide to the CP function. +4. The CP function interacts with the network entity which triggered this procedure (e.g. a peer CP function, an MME or a PCRF). + +## 6.3 Updates to procedures in other specifications + +### 6.3.1 Updates to procedures specified in TS 23.401 [2] + +#### 6.3.1.1 Procedures with PDN connection establishment + +This clause defines interactions between the CP and UP function during the following procedures: + +- E-UTRAN initial attach (TS 23.401 [2] clause 5.3.2.1) +- UE requested PDN connectivity (TS 23.401 [2] clause 5.10.2) + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The new SGW-C selects a new SGW-U and creates an Sx session. +- The new PGW-C selects a new PGW-U and creates an Sx session. +- The old SGW-C releases the existing Sx session from the old SGW-U. +- The old PGW-C releases the existing Sx session from the old PGW-U. +- The SGW-C modifies the SGW-U to update with the F-TEIDu of the eNodeB and the PGW-U. + +![Sequence diagram showing the interaction between CP and UP functions during PDN connection establishment. The diagram includes lifelines for UE, RAN, MME, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. It details steps for E-UTRAN initial attach, session termination, session establishment, and session modification between the CP (MME, SGW-C, PGW-C) and UP (SGW-U, PGW-U) functions.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) + +The sequence diagram illustrates the interaction between Control Plane (CP) and User Plane (UP) functions during PDN connection establishment. The lifelines involved are: UE, RAN, MME, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. + +The diagram is organized into several sections corresponding to different attach and connectivity request scenarios: + +- 1. E-UTRAN initial attach** (Figure 5.3.2.1-1 steps 1-7): This section shows the initial session termination and establishment between Old SGW-C and Old SGW-U (steps 2a, 2b, 3a, 3b). +- 4. E-UTRAN initial attach** (Figure 5.3.2.1-1 steps 8-10): This section shows the session termination and establishment between Old SGW-C and Old SGW-U (steps 5a, 5b, 6a, 6b). +- 7. E-UTRAN initial attach** (UE requested PDN connectivity): This section covers two cases: + - Figure 5.3.2.1-1 steps 11-12: Session establishment between New SGW-C and New SGW-U (steps 8a, 8b). + - Figure 5.10.2-1 steps 1-2: (No specific message exchange shown in this diagram for this case). +- 9. E-UTRAN initial attach** (UE requested PDN connectivity): This section covers two cases: + - Figure 5.3.2.1-1 steps 13-14: Session establishment between PGW-C and PGW-U (steps 10a, 10b). + - Figure 5.10.2-1 steps 3-4: (No specific message exchange shown in this diagram for this case). +- 11. E-UTRAN initial attach** (UE requested PDN connectivity): This section covers two cases: + - Figure 5.3.2.1-1 steps 15: Session modification between New SGW-C and New SGW-U (steps 12a, 12b). + - Figure 5.10.2-1 steps 5: (No specific message exchange shown in this diagram for this case). +- 13. E-UTRAN initial attach** (UE requested PDN connectivity): This section covers two cases: + - Figure 5.3.2.1-1 steps 16-23: Session modification between New SGW-C and New SGW-U (steps 14a, 14b). + - Figure 5.10.2-1 steps 6-13: (No specific message exchange shown in this diagram for this case). +- 15. E-UTRAN initial attach** (UE requested PDN connectivity): This section covers two cases: + - Figure 5.3.2.1-1 steps 23a: Session modification between PGW-C and PGW-U (steps 16a, 16b). + - Figure 5.10.2-1 steps 13a: (No specific message exchange shown in this diagram for this case). +- 17. E-UTRAN initial attach** (UE requested PDN connectivity): This section covers two cases: + - Figure 5.3.2.1-1 steps 24-26: (No specific message exchange shown in this diagram for this case). + - Figure 5.10.2-1 steps 14-16: (No specific message exchange shown in this diagram for this case). + +Sequence diagram showing the interaction between CP and UP functions during PDN connection establishment. The diagram includes lifelines for UE, RAN, MME, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. It details steps for E-UTRAN initial attach, session termination, session establishment, and session modification between the CP (MME, SGW-C, PGW-C) and UP (SGW-U, PGW-U) functions. + +Figure 6.3.1.1-1: Interaction between CP and UP function during PDN connection establishment + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. + +For all the steps below upon receiving a Sx Session Termination Request, the SGW-U or PGW-U releases all associated resources including the F-TEIDu allocated for the Sx session. + +- 2a. The SGW-C may send an Sx Session Termination Request to the SGW-U to release the Sx session. +- 2b. The SGW-U sends an Sx Session Termination Response to the SGW-C confirming the release of the Sx session. +- 3a. The PGW-C may send an Sx Session Termination Request to the PGW-U to release the Sx session. +- 3b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session. +4. The relevant steps of the procedure as specified in the figure above are executed. +- 5a. The SGW-C may send an Sx Session Termination Request to the SGW-U to release the Sx session. +- 5b. The SGW-U sends an Sx Session Termination Response to the SGW-C confirming the release of the Sx session. +- 6a. The PGW-C may send an Sx Session Termination Request to the PGW-U to release the Sx session. +- 6b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session. +7. The relevant steps of the procedure as specified in the figure above are executed. +- 8a. The SGW-C shall select new SGW-U as specified in clause 5.12. The SGW-C sends an Sx Session Establishment Request to the selected SGW-U for creating an Sx session for the UE. +- 8b. The SGW-U allocates F-TEIDu for the default bearer. The SGW-U sends an Sx Session Establishment Response to the SGW-C confirming the successful creation of the Sx session. It includes the F-TEIDu it has allocated. +9. The relevant steps of the procedure as specified in the figure above are executed. +- 10a. The PGW-C shall select new PGW-U as specified in clause 5.12. The PGW-C sends an Sx Session Establishment Request to the selected PGW-U for creating an Sx session for the UE. +- 10b. The PGW-U allocates F-TEIDu for the bearer. The PGW-U sends an Sx Session Establishment Response to the PGW-C confirming the successful creation of the Sx session. It includes the F-TEIDu it has allocated. +11. The relevant steps of the procedure as specified in the figure above are executed. +- 12a. The SGW-C sends Session Modification Request to the SGW-U. The SGW-C shall include the F-TEIDu of the default bearer received from the PGW. +- 12b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the success of the Sx session modification. +13. The relevant steps of the procedure as specified in the figure above are executed. +- 14a. The SGW-C sends an Sx Session Modification Request to the SGW-U. The SGW-C shall include the F-TEIDu of the default bearer received from the eNodeB. +- 14b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the success of the Sx session modification. +15. The relevant steps of the procedure as specified in the figure above are executed. +- 16a. If the Handover Indication is included in step 15, the PGW-C updates the old PGW-U session corresponding to the non-3GPP access by sending "Sx session modification request" message to the PGW-U (session ID) and instructs the PGW-U to start routing the downlink packets to the SGW/SGW-U. +- 16b. The PGW-U sends "Sx session modification response" message to the PGW-C. +17. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.1.2 Procedures with SGW change + +##### 6.3.1.2.1 General + +This clause covers the following two types of procedures involving SGW change: + +- Type 1: Procedures in which only Create Session Request message is sent from MME/SGSN to SGW-C during SGW change. +- Type 2: Procedures in which Create Session Request message followed by Modify Bearer Request message are sent from MME/SGSN to SGW-C during SGW change. + +##### 6.3.1.2.2 Type 1 + +This clause defines interactions between the CP and UP function during the following procedures: + +- Tracking Area Update procedure with Serving GW change (TS 23.401 [2] clause 5.3.3.1). +- Routing Area Update with MME interaction and with SGW change (TS 23.401 [2] clause 5.3.3.6). +- X2-based handover with Serving GW relocation (TS 23.401 [2] clause 5.5.1.1.3). +- MME triggered Serving GW relocation (TS 23.401 [2] clause 5.10.4). + +**Editor's Note: "Tracking Area Update procedure with Serving GW change and data forwarding" (TS 23.401 [2] clause 5.3.3.1A) is FFS.** + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The new SGW-C selects a new SGW-U and creates an Sx session. +- The PGW-C modifies the PGW-U to update with the F-TEIDu(s) of the new SGW-U. +- The old SGW-C releases the existing Sx session from the old SGW-U. + +![Sequence diagram showing the interaction between CP and UP functions during procedures with SGW change (Type 1).](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +The diagram illustrates the interaction between various network functions (UE, RAN, MME, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, PCRF) during procedures with SGW change (Type 1). The sequence is divided into several steps: + +- 1. Tracking Area Update procedure with Serving GW change:** This block contains four sub-procedures: + - Routing Area Update with MME interaction and with SGW change (Figure 5.3.3.6-1, steps 1-7, or) + - X2-based handover with Serving GW relocation (Figure 5.5.1.1.3-1, steps 1-2, or) + - MME triggered Serving GW relocation (Figure 5.10.4-1, steps 1-2) +- 2. Sx Session Establishment Request:** The New SGW-C sends this request to the New SGW-U. +- 3. Sx Session Establishment Response:** The New SGW-U responds to the New SGW-C. +- 4. Tracking Area Update procedure with Serving GW change:** This block contains four sub-procedures: + - Routing Area Update with MME interaction and with SGW change (Figure 5.3.3.6-1, steps 9, or) + - X2-based handover with Serving GW relocation (Figure 5.5.1.1.3-1, steps 3a, or) + - MME triggered Serving GW relocation (Figure 5.10.4, steps 3a) +- 5. Sx Session Modification Request:** The PGW-C sends this request to the PGW-U. +- 6. Sx Session Modification Response:** The PGW-U responds to the PGW-C. +- 7. Tracking Area Update procedure with Serving GW change:** This block contains four sub-procedures: + - Routing Area Update with MME interaction and with SGW change (Figure 5.3.3.6-1, steps 10-16, or) + - X2-based handover with Serving GW relocation (Figure 5.5.1.1.3-1, steps 3b-7a, or) + - MME triggered Serving GW relocation (Figure 5.10.4, steps 3b-6a) +- 8. Sx Session Termination Request:** The Old SGW-C sends this request to the Old SGW-U. +- 9. Sx Session Termination Response:** The Old SGW-U responds to the Old SGW-C. +- 10. Tracking Area Update procedure with Serving GW change:** This block contains four sub-procedures: + - Routing Area Update with MME interaction and with SGW change (Figure 5.3.3.6-1, steps 17 onwards, or) + - X2-based handover with Serving GW relocation (Figure 5.5.1.1.3-1, steps 7b onwards, or) + - MME triggered Serving GW relocation (Figure 5.10.4, steps 6b onwards) + +Sequence diagram showing the interaction between CP and UP functions during procedures with SGW change (Type 1). + +**Figure 6.3.1.2.2-1: Interaction between CP and UP function during procedures with SGW change (Type 1)** + +- Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- The new SGW-C shall select new SGW-U as specified in clause 5.12. The new SGW-C sends Sx Session Establishment Request to the selected SGW-U for creating an Sx session for the UE. +- The SGW-U allocates an F-TEIDu for each and every bearer received in the Sx Session Establishment Request. The new SGW-U sends Sx Session Establishment Response to the new SGW-C confirming the successful creation of the Sx session. It includes the F-TEIDu it has allocated for each and every bearer. +- The relevant steps of the procedure as specified in the figure above are executed. +- The PGW-C sends an Sx Session Modification Request to the PGW-U. The PGW-C shall include the F-TEIDu(s) of the new SGW-U. Additionally, based on the interaction with the PCRF, the PGW-C may also update other Sx parameters for the PDN connection. +- The PGW-U sends Sx Session Modification Response to the PGW-C confirming the success of the Sx session modification. +- The relevant steps of the procedure as specified in the figure above are executed. +- The old SGW-C sends Sx Session Termination Request to the old SGW-U to release the Sx session. + +9. The old SGW-U sends Sx Session Termination Response to the old SGW-C confirming the release of the Sx session. +10. The relevant steps of the procedure as specified in the figure above are executed. + +##### 6.3.1.2.3 Type 2 + +This clause defines interactions between the CP and UP function during the following procedures: + +- S1-based handover, normal (TS 23.401 [2] clause 5.5.1.2.2). +- E-UTRAN to UTRAN Iu mode Inter RAT handover (TS 23.401 [2] clause 5.5.2.1). +- UTRAN Iu mode to E-UTRAN Inter RAT handover (TS 23.401 [2] clause 5.5.2.2). +- E-UTRAN to GERAN A/Gb mode Inter RAT handover (TS 23.401 [2] clause 5.5.2.3). +- GERAN A/Gb mode to E-UTRAN Inter RAT handover (TS 23.401 [2] clause 5.5.2.4). + +**Editor's Note:** Most of the above procedures involve establishment and release of indirect data forwarding tunnel at the source and the target SGW. It is FFS if this needs to be supported in the CP and UP split architecture. + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The new SGW-C selects a new SGW-U and creates an Sx session. +- The SGW-C modifies the Sx session at SGW-U to update the F-TEIDu(s) of the eNB. +- The PGW-C modifies the PGW-U to update with the F-TEIDu(s) of the new SGW-U. +- The old SGW-C releases the existing Sx session from the old SGW-U. + +![Sequence diagram showing interaction between CP and UP function during procedures with SGW change (Type 2). The diagram involves UE, RAN, MME, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. It details steps for S1-based handover and various Inter RAT handovers, including Sx Session Establishment, Modification, and Termination requests/responses between the SGW and PGW components.](8269648391c59363ea61243864a2adf7_img.jpg) + +| UE | RAN | MME | New SGW-C | New SGW-U | Old SGW-C | Old SGW-U | PGW-C | PGW-U | HSS | PCRF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|-------------------------------------------------------------------------------------|-----------|--------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-------|-----|------| +| 1. S1-based handover, normal
E-UTRAN to UTRAN Iu mode Inter RAT handover
UTRAN Iu mode to E-UTRAN Inter RAT handover
E-UTRAN to GERAN A/Gb mode Inter RAT handover
GERAN A/Gb mode to E-UTRAN Inter RAT handover | | | | | Figure 5.5.1.2.2-1
Figure 5.5.2.1.2-1
Figure 5.5.2.2.2-1
Figure 5.5.2.3.2-1
Figure 5.5.2.4.2-1 | steps 1-4
steps 1-4
steps 1-4
steps 1-4
steps 1-4 | or
or
or
or
or | | | | +| | | | → 2. Sx Session Establishment Request →
← 3. Sx Session Establishment Response ← | | | | | | | | +| 4. S1-based handover, normal
E-UTRAN to UTRAN Iu mode Inter RAT handover
UTRAN Iu mode to E-UTRAN Inter RAT handover
E-UTRAN to GERAN A/Gb mode Inter RAT handover
GERAN A/Gb mode to E-UTRAN Inter RAT handover | | | | | Figure 5.5.1.2.2-1
Figure 5.5.2.1.2/3-1
Figure 5.5.2.2.2/3-1
Figure 5.5.2.3.2/3-1
Figure 5.5.2.4.2/3-1 | steps 4a-15
steps 4a-7
steps 4a-8
steps 4a-9
steps 4a-8 | or
or
or
or
or | | | | +| | | | → 5. Sx Session Modification Request →
← 6. Sx Session Modification Response ← | | | | | | | | +| 7. S1-based handover, normal
E-UTRAN to UTRAN Iu mode Inter RAT handover
UTRAN Iu mode to E-UTRAN Inter RAT handover
E-UTRAN to GERAN A/Gb mode Inter RAT handover
GERAN A/Gb mode to E-UTRAN Inter RAT handover | | | | | Figure 5.5.1.2.2-1
Figure 5.5.2.1.3-1
Figure 5.5.2.2.3-1
Figure 5.5.2.3.3-1
Figure 5.5.2.4.3-1 | steps 16
steps 8
steps 9
steps 10
steps 9 | or
or
or
or
or | | | | +| | | | | | | | → 8. Sx Session Modification Request →
← 9. Sx Session Modification Response ← | | | | +| 10. S1-based handover, normal
E-UTRAN to UTRAN Iu mode Inter RAT handover
UTRAN Iu mode to E-UTRAN Inter RAT handover
E-UTRAN to GERAN A/Gb mode Inter RAT handover
GERAN A/Gb mode to E-UTRAN Inter RAT handover | | | | | Figure 5.5.1.2.2-1
Figure 5.5.2.1.3-1
Figure 5.5.2.2.3-1
Figure 5.5.2.3.3-1
Figure 5.5.2.4.3-1 | steps 16a-19c
steps 8a-11
steps 9a-12
steps 10a-14
steps 9a-13 | or
or
or
or
or | | | | +| | | | | | → 11. Sx Session Termination Request →
← 12. Sx Session Termination Response ← | | | | | | +| 13. S1-based handover, normal
E-UTRAN to UTRAN Iu mode Inter RAT handover
UTRAN Iu mode to E-UTRAN Inter RAT handover
E-UTRAN to GERAN A/Gb mode Inter RAT handover
GERAN A/Gb mode to E-UTRAN Inter RAT handover | | | | | Figure 5.5.1.2.2-1
Figure 5.5.2.1.3-1
Figure 5.5.2.2.3-1
Figure 5.5.2.3.3-1
Figure 5.5.2.4.3-1 | steps 19d onwards
steps 11a onwards
steps 12a onwards
steps 14a onwards
steps 13a onwards | or
or
or
or
or | | | | + +Sequence diagram showing interaction between CP and UP function during procedures with SGW change (Type 2). The diagram involves UE, RAN, MME, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. It details steps for S1-based handover and various Inter RAT handovers, including Sx Session Establishment, Modification, and Termination requests/responses between the SGW and PGW components. + +**Figure 6.3.1.2.3-1: Interaction between CP and UP function during procedures with SGW change (Type 2)** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. The new SGW-C shall select new SGW-U as specified in clause 5.12. The new SGW-C sends an Sx Session Establishment Request to the selected SGW-U for creating an Sx session for the UE. Usage Monitoring Rules may also be included in case of home-routed roaming scenario and if the inter-operator charging is required. +3. The SGW-U allocates F-TEIDu for each and every bearer received. The new SGW-U sends an Sx Session Establishment Response to the new SGW-C confirming the successful creation of the Sx session. It includes the F-TEIDu it has allocated for each and every bearer. +4. The relevant steps of the procedure as specified in the figure above are executed. +5. The SGW-C sends an Sx Session Modification Request to the SGW-U. It shall include the F-TEIDu of the eNB. +6. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the successful modification of the Sx session. +7. The relevant steps of the procedure as specified in the figure above are executed. + +8. The PGW-C sends an Sx Session Modification Request to the PGW-U. The PGW-C shall include the F-TEIDu of the new SGW-U. Additionally, based on the interaction with the PCRF, the PGW-C may also update other Sx parameters for the PDN connection. +9. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the success of the Sx session modification. +10. The relevant steps of the procedure as specified in the figure above are executed. +11. The old SGW-C sends an Sx Session Termination Request to the old SGW-U to release the Sx session. +12. The old SGW-U sends an Sx Session Termination Response to the old SGW-C confirming the release of the Sx session. +13. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.1.3 Procedures with eNB F-TEIDu update + +In this clause, interactions between the CP and UP function during the following procedures are considered: + +- UE triggered Service Request (TS 23.401 [2] clause 5.3.4.1). +- Connection Resume procedure (TS 23.401 [2] clause 5.3.5A). +- E-UTRAN initiated E-RAB modification procedure (TS 23.401 [2] clause 5.4.7). +- X2-based handover without Serving GW relocation (TS 23.401 [2] clause 5.5.1.1.2). +- S1-based handover without Serving GW change (TS 23.401 [2] clause 5.5.1.2.2). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The SGW-C modifies the Sx session at SGW-U to update the F-TEIDu(s) of the eNB. +- Based on the interaction with the PCRF, the PGW-C may modify the PGW-U to update other Sx parameters. + +![](0d0897dd7f03672d186db9d56ea0d6f5_img.jpg) + +| UE | RAN | MME | SGW-C | SGW-U | PGW-C | PGW-U | HSS | PCRF | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|-------------------------------------|---------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------|-----|------| +| 1. UE triggered Service Request
Connection Resume procedure
E-UTRAN initiated E-RAB modification procedure
X2-based handover without Serving GW relocation
S1-based handover without Serving GW change | | | | | | | | | +| | | | | Figure 5.3.4.1-1
Figure 5.3.5A-1
Figure 5.4.7-1
Figure 5.5.1.1.2-1
Figure 5.5.1.2.2-1 | steps 1-8
steps 1-7
steps 1-2
steps 1-2
steps 1-15 | or
or
or
or | | | +| | | | 2. Sx Session Modification Request | | | | | | +| | | | 3. Sx Session Modification Response | | | | | | +| 4. UE triggered Service Request
Connection Resume procedure
E-UTRAN initiated E-RAB modification procedure
X2-based handover without Serving GW relocation
S1-based handover without Serving GW change | | | | | | | | | +| | | | | Figure 5.3.4.1-1
Figure 5.3.5A-1
Figure 5.4.7-1
Figure 5.5.1.1.2-1
Figure 5.5.1.2.2-1 | steps 9
steps 8 onwards
steps 3 onwards
steps 3a
steps 16 onwards | or
or
or
or | | | +| | | | | | 5. Sx Session Modification Request | | | | +| | | | | | 6. Sx Session Modification Response | | | | +| 7. UE triggered Service Request
X2-based handover without Serving GW relocation | | | | | | | | | +| | | | | Figure 5.3.4.1-1
Figure 5.5.1.1.2-1 | steps 10 onwards
steps 3b onwards | or | | | + +**Figure 6.3.1.3-1: Interaction between CP and UP function during procedures with eNB F-TEIDu update** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. + +2. The SGW-C sends an Sx Session Modification Request to the SGW-U. It shall include the new F-TEIDu of the eNB. Additionally, for the following procedures extra steps may apply: + - UE triggered Service Request: If the buffering of the data packets in the idle mode is performed in the SGW-C and if those buffered packets are still valid (e.g. data packets for which the buffering duration hasn't expired yet), then SGW-C shall also provide those data packets to the SGW-U (as specified in clause 5.12) so that it can be sent to the eNB. +3. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the successful modification of the Sx session. +4. The relevant steps of the procedure as specified in the figure above are executed. +5. Based on the interaction with the PCRF, the PGW-C may update other Sx parameters for the PDN connection. Correspondingly, the PGW-C sends an Sx Session Modification Request to the PGW-U. +6. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the success of the Sx session modification. +7. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.1.4 Procedures with release of eNB F-TEIDu + +This clause defines interactions between the CP and UP function during the following procedures: + +- Connection Suspend procedure (TS 23.401 [2] clause 5.3.4A). +- S1 release procedure (TS 23.401 [2] clause 5.3.5). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The SGW-C modifies the SGW-U to release the eNB F-TEIDu. Additionally, the SGW-C configures the SGW-U so that the downlink data packets can be buffered either in the SGW-C or in the SGW-U. + +![Sequence diagram showing interactions between UE, RAN, MME, SGW-C, SGW-U, PGW-C, PGW-U, HSS, and PCRF for Connection Suspend and S1 release procedures. The diagram is divided into two main horizontal sections. The top section covers steps 1 and 2, where the MME initiates the procedure, and the SGW-C sends an Sx Session Modification Request to the SGW-U. The bottom section covers steps 3 onwards, where the SGW-U responds and subsequent steps occur. Arrows indicate the flow of messages between the Control Plane (CP) and User Plane (UP) functions.](9edb407536d4d4d4a6ac391527af047c_img.jpg) + +| UE | RAN | MME | SGW-C | SGW-U | PGW-C | PGW-U | HSS | PCRF | +|---------------------------------------------------------|-----|-----|------------------------------------|-------------------------------------|------------------------------------|----------|-----|------| +| 1. Connection Suspend procedure
S1 release procedure | | | Figure 5.3.4A-1
Figure 5.3.5-1 | | steps 1-2
steps 1-2 | or
or | | | +| | | | 2. Sx Session Modification Request | | | | | | +| | | | | 3. Sx Session Modification Response | | | | | +| 4. Connection Suspend procedure
S1 release procedure | | | Figure 5.3.4A-1
Figure 5.3.5-1 | | steps 3 onwards
steps 3 onwards | or | | | + +Sequence diagram showing interactions between UE, RAN, MME, SGW-C, SGW-U, PGW-C, PGW-U, HSS, and PCRF for Connection Suspend and S1 release procedures. The diagram is divided into two main horizontal sections. The top section covers steps 1 and 2, where the MME initiates the procedure, and the SGW-C sends an Sx Session Modification Request to the SGW-U. The bottom section covers steps 3 onwards, where the SGW-U responds and subsequent steps occur. Arrows indicate the flow of messages between the Control Plane (CP) and User Plane (UP) functions. + +**Figure 6.3.1.4-1: Interaction between CP and UP function during procedures with release of eNB F-TEIDu** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. The SGW-C sends an Sx Session Modification Request to the SGW-U. It shall indicate the SGW-U to release the eNB F-TEIDu. Additionally, the SGW-C decides if the buffering of the downlink data packets shall be done in CP or the UP function, as specified in clause 5.9) and correspondingly informs the SGW-U for as follows: + - If the downlink data packets are to be buffered in the SGW-C, the SGW-C shall configure the SGW-U to forward the downlink data packets for all the bearers of the UE to the SGW-C, as specified in clause 5.6. + - If the downlink data packets are to be buffered in the SGW-U, the SGW-C shall indicate the same to SGW-U. Additionally, the following applies: + +- if the Paging Policy Differentiation feature (as specified in TS 23.401 [2] clause 4.9) is supported by the SGW-C and SGW-U and based on operator's policy if it is required to be activated for this UE, the SGW-C shall include an indication to provide the DSCP in TOS (IPv4) / TC (IPv6) value from the IP header of the first downlink data packet of each bearer. + - if the PDN GW Pause Charging procedure (as specified in TS 23.401 [2] clause 5.3.6A) is supported by the SGW-C and SGW-U and based on operator's policy if it is required to be activated for this UE, the SGW-C may provide the number/fraction of packets/bytes drop threshold value. When this threshold is reached, the SGW-U is required to provide an indication to the SGW-C. +- The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the successful modification of the Sx session. + - The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.1.5 Procedures when downlink data is buffered in the UP function + +This clause defines interactions between the CP and UP function when the UE is in idle mode and buffering of the downlink data is performed in the UP function, during the following procedures: + +- Network Triggered Service Request (TS 23.401 [2] clause 5.3.4.3). +- PDN GW Pause of Charging procedure (TS 23.401 [2] clause 5.3.6A). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The SGW-U notifies the SGW-C that the first downlink data packet was received for a bearer. + +NOTE: A bearer is identified in the SGW-U as a combination of PDR(s) and FAR(s). + +- The SGW-U notifies the SGW-C that the drop threshold was reached. + +![Sequence diagram showing interactions between UE, RAN, MME, SGW-C, SGW-U, PGW-C, PGW-U, HSS, and PCRF for Network Triggered Service Request and PDN GW Pause of Charging procedures.](762a17cd79880dbca172bcbbe9375223_img.jpg) + +The diagram illustrates the interaction between the Control Plane (CP) and User Plane (UP) functions when downlink data is buffered in the UP function. It shows two parallel procedures: Network Triggered Service Request and PDN GW Pause of Charging procedure. + +| UE | RAN | MME | SGW-C | SGW-U | PGW-C | PGW-U | HSS | PCRF | +|----|-----|-----|----------------------------------------------------------------------------|-------|-------------------------------------|------------------------------------|-----|------| +| | | | 1. Network Triggered Service Request
PDN GW Pause of Charging procedure | | Figure 5.3.4.3-1
Figure 5.3.6A-1 | steps 1
steps 1 | or | | +| | | | 2. Sx report | | | | | | +| | | | 3. Network Triggered Service Request
PDN GW Pause of Charging procedure | | Figure 5.3.4.3-1
Figure 5.3.6A-1 | steps 2
steps 2 | or | | +| | | | 4. Sx report Ack | | | | | | +| | | | 5. Network Triggered Service Request
PDN GW Pause of Charging procedure | | Figure 5.3.4.3-1
Figure 5.3.6A-1 | steps 3 onwards
steps 3 onwards | or | | + +Sequence diagram showing interactions between UE, RAN, MME, SGW-C, SGW-U, PGW-C, PGW-U, HSS, and PCRF for Network Triggered Service Request and PDN GW Pause of Charging procedures. + +**Figure 6.3.1.5-1: Interaction between CP and UP when downlink data is buffered in the UP function** + +- Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- When the downlink data is received, the SGW-U starts buffering it. + +On arrival of the first downlink data packet for a bearer, the SGW-U shall send an Sx report message (first packet indication) to the SGW-C. If the Paging Policy Differentiation feature (as specified in TS 23.401 [2] clause 4.9) is supported by the SGW-U and if it is activated by the SGW-C for this Sx session, the SGW-U shall also include the DSCP in TOS (IPv4) / TC (IPv6) value from the IP header of the downlink data packet. + +If the SGW-C has provided the number/fraction of packets/bytes drop threshold value during the procedure with release of eNB F-TEIDu (clause 6.3.1.4), the SGW-U shall monitor that threshold. Once the threshold is reached the SGW-U shall send an Sx report message (drop threshold reached) to the SGW-C. + +- The relevant steps of the procedure as specified in the figure above are executed. + +4. The SGW-C sends an Sx report Ack message to the SGW-U. Additionally, for the following procedures the following applies: + - Network Triggered Service Request: If DL Buffering Duration time and DL Buffering Suggested Packet Counts were received from the MME/SGSN (refer to step no. 2 of TS 23.401 [2] clause 5.3.4.3) by the SGW-C then SGW-C shall include the same in the Sx report Ack message. +5. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.1.6 Procedures with release of PDN connection + +This clause defines interactions between the CP and UP function during the following procedures: + +- UE-initiated Detach procedure for E-UTRAN (TS 23.401 [2] clause 5.3.8.2.1). +- UE-initiated Detach procedure for GERAN/UTRAN with ISR activated (TS 23.401 [2] clause 5.3.8.2.2). +- MME-initiated Detach procedure (TS 23.401 [2] clause 5.3.8.3). +- SGSN-initiated Detach procedure with ISR activated (TS 23.401 [2] clause 5.3.8.3A). +- HSS-initiated Detach procedure (TS 23.401 [2] clause 5.3.8.4). +- UE or MME requested PDN disconnection (TS 23.401 [2] clause 5.10.3). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The SGW-C terminates the Sx session at the SGW-U. +- The PGW-C terminates the Sx session at the PGW-U. + +![](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +| UE | RAN | MME | SGW-C | SGW-U | PGW-C | PGW-U | HSS | PCRF | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|---------------------------------------------------------------------------|-------------------------------------------------------------------------|-------------------------------------------------------------------------|-------|-----|------| +| 1. UE-initiated Detach procedure for E-UTRAN      Figure 5.3.8.2-1      steps 1-5      or
UE-initiated Detach procedure for GERAN/UTRAN
with ISR activated                                      Figure 5.3.8.2-2      steps 1-5      or
MME-initiated Detach procedure                      Figure 5.3.8.3-1      steps 1-5      or
SGSN-initiated Detach procedure with ISR activated Figure 5.3.8.3A-1      steps 1-5      or
HSS-initiated Detach procedure                      Figure 5.3.8.4-1      steps 1-3      or
UE or MME requested PDN disconnection      Figure 5.10.3-1      steps 1-2 | | | | | | | | | +| | | | 2. Sx Session Modification Request
3. Sx Session Modification Response | | | | | | +| 4. UE-initiated Detach procedure for E-UTRAN      Figure 5.3.8.2-1      steps 6      or
UE-initiated Detach procedure for GERAN/UTRAN
with ISR activated                                      Figure 5.3.8.2-2      steps 6      or
MME-initiated Detach procedure                      Figure 5.3.8.3-1      steps 6      or
SGSN-initiated Detach procedure with ISR activated Figure 5.3.8.3A-1      steps 6      or
HSS-initiated Detach procedure                      Figure 5.3.8.4-1      steps 4      or
UE or MME requested PDN disconnection      Figure 5.10.3-1      steps 3 | | | | | | | | | +| | | | | | 5. Sx Session Termination Request
6. Sx Session Termination Response | | | | +| 7. UE-initiated Detach procedure for E-UTRAN      Figure 5.3.8.2-1      steps 7 onwards      or
UE-initiated Detach procedure for GERAN/UTRAN
with ISR activated                                      Figure 5.3.8.2-2      steps 7 onwards      or
MME-initiated Detach procedure                      Figure 5.3.8.3-1      steps 7 onwards      or
SGSN-initiated Detach procedure with ISR activated Figure 5.3.8.3A-1      steps 7 onwards      or
HSS-initiated Detach procedure                      Figure 5.3.8.4-1      steps 5 onwards      or
UE or MME requested PDN disconnection      Figure 5.10.3-1      steps 4 onwards | | | | | | | | | +| | | | | 8. Sx Session Termination Request
9. Sx Session Termination Response | | | | | + +**Figure 6.3.1.6-1: Interaction between CP and UP function during release of PDN connection** + +- Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- The SGW-C sends an Sx Session Modification Request to the SGW-U. SGW-C shall indicate SGW-U to stop counting uplink packets for the affected bearers. SGW-C shall also indicate the SGW-U to discard uplink packets received from eNodeB for the affected bearers. +- The SGW-U sends an Sx Session Modification Response to the SGW-C. +- The relevant steps of the procedure as specified in the figure above are executed. +- The PGW-C sends an Sx Session Termination Request to the PGW-U. +- The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the successful termination of the Sx session. Additionally, if the usage reporting is configured by the PGW-C (as specified in clause 5.3.2) the PGW-U shall provide the usage report(s) for the PDN connection (as specified in clause 5.3.3) to the PGW-C. +- The relevant steps of the procedure as specified in the figure above are executed. +- The SGW-C sends an Sx Session Termination Request to the SGW-U. +- The SGW-U sends an Sx Session Termination Response to the SGW-C confirming the successful termination of the Sx session. Additionally, if the usage reporting is configured by the SGW-C (as specified in clause 5.3.2) the SGW-U shall provide the usage report(s) for the PDN connection (as specified in clause 5.3.3) to the SGW-C. + +#### 6.3.1.7 Procedures with modification of bearer + +This clause defines interactions between the CP and UP function during the following procedures: + +- Dedicated bearer activation (TS 23.401 [2] clause 5.4.1). +- PDN GW initiated bearer modification with bearer QoS update (TS 23.401 [2] clause 5.4.2.1). +- PDN GW initiated bearer modification without bearer QoS update (TS 23.401 [2] clause 5.4.3). +- PDN GW initiated bearer deactivation (TS 23.401 [2] clause 5.4.4.1). +- HSS Initiated Subscribed QoS Modification (TS 23.401 [2] clause 5.4.2.2). +- MME Initiated Dedicated Bearer Deactivation (TS 23.401 [2] clause 5.4.4.2). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The PGW-C modifies the Sx session at the PGW-U. +- The SGW-C modifies the Sx session at the SGW-U. + +![](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +| UE | RAN | MME | SGW-C | SGW-U | PGW-C | PGW-U | HSS | PCRF | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|-------|------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|----------------------------|-----|------| +| 1. Dedicated bearer activation
PDN GW initiated bearer deactivation
MME initiated Dedicated Bearer Deactivation | | | | Figure 5.4.1-1
Figure 5.4.4.1-1
Figure 5.4.4.2-1 | steps 1
steps 1
steps 0-4 | or
or | | | +| | | | | | 2. Sx Session Modification Request | | | | +| | | | | | 3. Sx Session Modification Response | | | | +| 4. Dedicated bearer activation
PDN GW initiated bearer deactivation
MME initiated Dedicated Bearer Deactivation | | | | Figure 5.4.1-1
Figure 5.4.4.1-1
Figure 5.4.4.2-1 | steps 2
steps 2
steps 5 | or
or | | | +| | | | | | 5. Sx Session Modification Request | | | | +| | | | | | 6. Sx Session Modification Response | | | | +| 7. Dedicated bearer activation
PDN GW initiated bearer modification with bearer QoS update
HSS Initiated Subscribed QoS Modification
PDN GW initiated bearer deactivation
MME initiated Dedicated Bearer Deactivation | | | | Figure 5.4.1-1
Figure 5.4.2.1-1
Figure 5.4.2.2-1
Figure 5.4.4.1-1
Figure 5.4.4.2-1 | steps 3-10
steps 1-10
steps 1-6
steps 3-8
steps 6-8 | or
or
or
or | | | +| | | | | | 8. Sx Session Modification (or Termination) Request | | | | +| | | | | | 9. Sx Session Modification (or Termination) Response | | | | +| 10. Dedicated bearer activation
PDN GW initiated bearer modification with bearer QoS update
HSS Initiated Subscribed QoS Modification
PDN GW initiated bearer modification without bearer QoS update
PDN GW initiated bearer deactivation
MME initiated Dedicated Bearer Deactivation | | | | Figure 5.4.1-1
Figure 5.4.2.1-1
Figure 5.4.2.2-1
Figure 5.4.3-1
Figure 5.4.4.1-1
Figure 5.4.4.2-1 | steps 11
steps 11
steps 7
steps 1-9
steps 9
steps 9 | or
or
or
or
or | | | +| | | | | | 11. Sx Session Modification (or Termination) Request | | | | +| | | | | | 12. Sx Session Modification (or Termination) Response | | | | +| 13. Dedicated bearer activation
PDN GW initiated bearer modification with bearer QoS update
HSS Initiated Subscribed QoS Modification
PDN GW initiated bearer modification without bearer QoS update
PDN GW initiated bearer deactivation | | | | Figure 5.4.1-1
Figure 5.4.2.1-1
Figure 5.4.2.2-1
Figure 5.4.3-1
Figure 5.4.4.1-1 | steps 12
steps 12
steps 8
steps 10
steps 10 | or
or
or
or | | | + +**Figure 6.3.1.7-1: Interaction between CP and UP function during modification of bearer** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. The PGW-C sends an Sx Session Modification Request to the PGW-U. For "Dedicated bearer activation", PGW-C indicates PGW-U to allocate F-TEID for the new dedicated bearer. For "PDN GW/MME initiated bearer deactivation procedure", PGW-C shall indicate PGW-U to stop counting and stop forwarding downlink packets for the affected bearer(s). +3. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the successful modification of the Sx session. +4. The relevant steps of the procedure as specified in the figure above are executed. +5. The SGW-C may send an Sx Session Modification Request to the SGW-U. For "Dedicated bearer activation", SGW-C indicates SGW-U to allocate F-TEID for the new dedicated bearer. + +6. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the successful modification of the Sx session. +7. The relevant steps of the procedure as specified in the figure above are executed. +8. The SGW-C sends an Sx Session Modification Request to the SGW-U. For dedicated bearer activation procedure, the SGW-C shall include the F-TEIDu of the activated bearer received from the eNodeB. For PDN GW/HSS initiated bearer modification with bearer QoS update procedure, SGW-C provides updated QoS parameters to SGW-U. For PDN GW/MME initiated bearer deactivation procedure, SGW-C shall indicate SGW-U to remove the PDR(s) for the affected bearer(s). + +If the default bearer belonging to a PDN connection is deactivated, the SGW-C sends an Sx Session Termination Request to the SGW-U. + +9. The SGW-U sends an Sx Session Modification Response or an Sx Session Termination Response to the SGW-C confirming the successful modification or termination of the Sx session. +10. The relevant steps of the procedure as specified in the figure above are executed. +11. The PGW-C sends an Sx Session Modification Request to the PGW-U. For dedicated bearer activation procedure, the PGW-C shall include the F-TEIDu of the activated bearer received from the SGW. For PDN GW/HSS initiated bearer modification with bearer QoS update procedure, PGW-C provides updates according to the changed QoS parameters and TFT (if applicable) to PGW-U. For "PDN GW initiated bearer modification without bearer QoS update" procedure, PGW-C provides updates according to the changed APN-AMBR and/or TFT to PGW-U. For PDN GW/MME initiated bearer deactivation procedure, PGW-C shall indicate PGW-U to remove the PDR(s) for the affected bearer(s). + +If the default bearer belonging to a PDN connection is deactivated, the PGW-C sends an Sx Session Termination Request to the PGW-U. + +12. The PGW-U sends an Sx Session Modification Response or an Sx Session Termination Response to the PGW-C confirming the successful modification or termination of the Sx session. +13. The relevant steps of the procedure as specified in the figure above are executed. + +### 6.3.2 Updates to procedures specified in TS 23.203 [3] + +#### 6.3.2.1 IP-CAN session establishment + +This clause defines interactions between the CP and UP function during the following procedures: + +- IP-CAN session establishment (TS 23.203 [3] clause 7.2) + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The new TDF-C selects a new TDF-U and creates Sx session. +- The TDF-C modifies the TDF-U to update Sx parameters. + +![Sequence diagram showing interactions between CP and UP functions for IP-CAN session establishment. The diagram includes lifelines for BBERF, PCEF, TDF-C, TDF-U, TSSF, V-PCRF, H-PCRF, SPR, and OCS. It is divided into two main sections: '1. IP-CAN Session Establishment' (steps 1-10) and '4. IP-CAN Session Establishment' (steps 11-19). In the first section, TDF-C sends a '2.Sx Session Establishment Request' to TDF-U, and TDF-U responds with a '3.Sx Session Establishment Response'. The second section is labeled 'Figure 7.2-1 steps 11-19'.](4b8c5ecb492fd759c766fe8950fafe67_img.jpg) + +| BBERF | PCEF | TDF-C | TDF-U | TSSF | V-PCRF | H-PCRF | SPR | OCS | +|----------------------------------------------------------|------|------------------------------------|-------------------------------------|------|--------|--------|-----|-----| +| 1. IP-CAN Session Establishment Figure 7.2-1 steps 1-10 | | | | | | | | | +| | | 2.Sx Session Establishment Request | 3.Sx Session Establishment Response | | | | | | +| 4. IP-CAN Session Establishment Figure 7.2-1 steps 11-19 | | | | | | | | | + +Sequence diagram showing interactions between CP and UP functions for IP-CAN session establishment. The diagram includes lifelines for BBERF, PCEF, TDF-C, TDF-U, TSSF, V-PCRF, H-PCRF, SPR, and OCS. It is divided into two main sections: '1. IP-CAN Session Establishment' (steps 1-10) and '4. IP-CAN Session Establishment' (steps 11-19). In the first section, TDF-C sends a '2.Sx Session Establishment Request' to TDF-U, and TDF-U responds with a '3.Sx Session Establishment Response'. The second section is labeled 'Figure 7.2-1 steps 11-19'. + +Figure 6.3.2.1-1: Interaction between CP and UP function with IP-CAN session establishment + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. For the solicited application reporting, the PCRF requests the TDF to establish the relevant session towards PCRF and provides ADC Rules to the TDF. The TDF-C selects a new TDF-U as specified in clause 5.12 and sends an Sx Session Establishment Request to the TDF-U to establish the Sx session. +3. The TDF-U sends an Sx Session Establishment Response to the TDF-C confirming the successful creation of the Sx session. +4. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.2.2 IP-CAN session termination + +This clause defines interactions between the CP and UP function during the following procedures: + +- IP-CAN session termination (TS 23.203 [3] clause 7.3). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The TDF-C releases the existing Sx session from the TDF-U. + +![Sequence diagram showing interactions between CP and UP functions for IP-CAN session termination. The diagram includes lifelines for BBERF, PCEF, TDF-C, TDF-U, TSSF, V-PCRF, H-PCRF, OCS, SPR, RCAF, and AF. It details four steps: 1. UE initiated IP-CAN Session termination (Figure 7.3.1-1 steps 1-9); 2. GW(PCEF) initiated IP-CAN Session termination (Figure 7.3.2-1 step 1-11); 3. Sx Session Termination Request/Response between TDF-C and TDF-U; 4. UE initiated IP-CAN Session termination (Figure 7.3.1-1 steps 10-23) and GW(PCEF) initiated IP-CAN Session termination (Figure 7.3.2-1 step 12-24).](9e9104f9ba7eec1259a7893c6380ca1b_img.jpg) + +| BBERF | PCEF | TDF-C | TDF-U | TSSF | V-PCRF | H-PCRF | OCS | SPR | RCAF | AF | +|-------------------------------------------------------------------------|------|---------------------------------------------|-------|------|--------|--------|-----|-----|------|----| +| 1. UE initiated IP-CAN Session termination Figure 7.3.1-1 steps 1-9 | | | | | | | | | | | +| GW(PCEF) initiated IP-CAN Session termination Figure 7.3.2-1 step 1-11 | | | | | | | | | | | +| | | 2.Sx Session
--Termination-- Request --> | | | | | | | | | +| | | <--Termination-- Response | | | | | | | | | +| 4. UE initiated IP-CAN Session termination Figure 7.3.1-1 steps 10-23 | | | | | | | | | | | +| GW(PCEF) initiated IP-CAN Session termination Figure 7.3.2-1 step 12-24 | | | | | | | | | | | + +Sequence diagram showing interactions between CP and UP functions for IP-CAN session termination. The diagram includes lifelines for BBERF, PCEF, TDF-C, TDF-U, TSSF, V-PCRF, H-PCRF, OCS, SPR, RCAF, and AF. It details four steps: 1. UE initiated IP-CAN Session termination (Figure 7.3.1-1 steps 1-9); 2. GW(PCEF) initiated IP-CAN Session termination (Figure 7.3.2-1 step 1-11); 3. Sx Session Termination Request/Response between TDF-C and TDF-U; 4. UE initiated IP-CAN Session termination (Figure 7.3.1-1 steps 10-23) and GW(PCEF) initiated IP-CAN Session termination (Figure 7.3.2-1 step 12-24). + +**Figure 6.3.2.2-1: Interaction between CP and UP function with IP-CAN session termination** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. If there is an active Sd session between TDF and PCRF, TDF-C sends an Sx Session Termination Request to the TDF-U to release the Sx session. +3. The TDF-U sends an Sx Session Termination Response to the TDF-C confirming the release of the Sx session +4. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.2.3 IP-CAN session modification + +This clause defines interactions between the CP and UP function during the following procedures: + +- IP-CAN session modification ( TS 23.203 [3] clause 7.4). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The TDF-C modifies the TDF-U to update Sx parameters. +- The PGW-C modifies the PGW-U to update Sx parameters. + +![Sequence diagram showing interactions between BBERF, PCEF (PGW-U), PGW-C, TDF-C, TDF-U, TSSF, V-PCRF, H-PCRF, OCS, and AF for IP-CAN session modification. The diagram is divided into three main sections: 1. IP-CAN Session Modification; GW (PCEF) initiated (steps 1-13), 2. IP-CAN Session Modification; PCRF initiated (steps 1-7), and 3. IP-CAN Session Modification; GW (PCEF) initiated (steps 14-19) and IP-CAN Session Modification; PCRF initiated (step 8-15). The final section shows steps 20-24 for GW (PCEF) initiated and step 16-20 for PCRF initiated.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +The diagram illustrates the interaction between CP and UP functions for IP-CAN session modification. It features ten lifelines: BBERF, PCEF (PGW-U), PGW-C, TDF-C, TDF-U, TSSF, V-PCRF, H-PCRF, OCS, and AF. The sequence is as follows: + +- 1. IP-CAN Session Modification; GW (PCEF) initiated** (Figure 7.4.1-1 steps 1-13): This section includes two sub-sequences. The first shows TDF-C sending a 2.Sx Session Modification Request to TDF-U, and TDF-U responding with a 3.Sx Session Modification Response. The second shows PCEF sending a 4.IP-CAN Session Modification Request to PGW-C, which then sends a 5.Sx Session Modification Request to PCEF. PCEF responds with a 6.Sx Session Modification Response to PGW-C. +- IP-CAN Session Modification; PCRF initiated** (Figure 7.5 steps 1-7): This section shows the PCRF initiating the modification process. +- 4. IP-CAN Session Modification; GW (PCEF) initiated** (Figure 7.4.1-1 steps 14-19) and **IP-CAN Session Modification; PCRF initiated** (Figure 7.5 step 8-15): This section continues the modification process, with PCEF sending another 4.IP-CAN Session Modification Request to PGW-C. +- 7. IP-CAN Session Modification; GW (PCEF) initiated** (Figure 7.4.1-1 steps 20-24) and **IP-CAN Session Modification; PCRF initiated** (Figure 7.5 step 16-20): This final section shows the completion of the modification process. + +Sequence diagram showing interactions between BBERF, PCEF (PGW-U), PGW-C, TDF-C, TDF-U, TSSF, V-PCRF, H-PCRF, OCS, and AF for IP-CAN session modification. The diagram is divided into three main sections: 1. IP-CAN Session Modification; GW (PCEF) initiated (steps 1-13), 2. IP-CAN Session Modification; PCRF initiated (steps 1-7), and 3. IP-CAN Session Modification; GW (PCEF) initiated (steps 14-19) and IP-CAN Session Modification; PCRF initiated (step 8-15). The final section shows steps 20-24 for GW (PCEF) initiated and step 16-20 for PCRF initiated. + +**Figure 6.3.2.3: Interaction between CP and UP function with IP-CAN session modification** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. For the TDF solicited application reporting, and PCRF provides new ADC decisions to the TDF, TDF-C sends an Sx Session Modification Request to the TDF-U to update Sx parameters. +3. The TDF-U sends an Sx Session Modification Response to the TDF-C confirming update of Sx session. +4. The relevant steps of the procedure as specified in the figure above are executed. +5. PCRF provides the updated PCC rules, and PGW-C may send an Sx Session Modification Request to the PGW-U to update Sx parameters. +6. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update of Sx session. +7. The relevant steps of the procedure as specified in the figure above are executed. + +NOTE: If PCEF determines to trigger the procedures defined in TS 23.401 [2], e.g. modify bearer request, steps 5 and 6 are combined with the Sx Session Modification in the corresponding call flows described in clause 6.3.1.7. + +#### 6.3.2.4 Management of PFDs + +This clause defines interactions between the CP and UP function during the following procedures: + +- Procedures for management of PFDs (TS 23.203 [3] clause 7.12). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The PGW-C/TDF-C provision/update/remove the PFD (s) to the PGW-U/TDF-U. + +![Sequence diagram showing interaction between PGW-C / TDF-C, PGW-U / TDF-U, and PFDF for PFD management. Step 1: PFD retrieval or management by PCEF/TDF. Step 2: PFD management request from PGW-C/TDF-C to PGW-U/TDF-U. Step 3: PFD management response from PGW-U/TDF-U to PGW-C/TDF-C.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +Sequence diagram showing interaction between PGW-C / TDF-C, PGW-U / TDF-U, and PFDF for PFD management. Step 1: PFD retrieval or management by PCEF/TDF. Step 2: PFD management request from PGW-C/TDF-C to PGW-U/TDF-U. Step 3: PFD management response from PGW-U/TDF-U to PGW-C/TDF-C. + +Figure 6.3.2.4-1: Interaction between CP and UP function with PFD management + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. When there's any change to the PFD (s) due to pull mode or push mode procedure, the PGW-C/TDF-C sends PFD management request to the PGW-U/TDF-U to provision/update/remove the PFD (s). +3. PGW-U/TDF-U acknowledges by responding with PFD management response message. + +### 6.3.3 Updates to procedures specified in TS 23.402 [4] + +#### 6.3.3.1 Procedures with GTP based S2b establishment + +This clause defines interactions between the CP and UP function during the following procedures: + +- GTP based S2b for roaming, non-roaming and LBO ( TS 23.402 [4] clause 7.2.4). +- Emergency services over GTP based S2b ( TS 23.402 [4] clause 7.2.5). +- UE-initiated connectivity to additional PDN from Un-trusted Non-3GPP IP Access with GTP ( TS 23.402 [4] clause 7.6.3). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The new PGW-C selects a new PGW-U and creates an Sx session. + +![Sequence diagram showing interaction between UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF for GTP based S2b establishment. Step 1: PDN connection establishment. Step 2: Sx Session Establishment Request from PGW-C to PGW-U. Step 3: Sx Session Establishment Response from PGW-U to PGW-C. Step 4: PDN connection establishment.](86692d82da6655813b5acf58a767a38c_img.jpg) + +Sequence diagram showing interaction between UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF for GTP based S2b establishment. Step 1: PDN connection establishment. Step 2: Sx Session Establishment Request from PGW-C to PGW-U. Step 3: Sx Session Establishment Response from PGW-U to PGW-C. Step 4: PDN connection establishment. + +Figure 6.3.3.1-1: Interaction between CP and UP function with GTP based S2b establishment + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. The PGW-C shall select new PGW-U as specified in clause 5.12. The PGW-C sends an Sx Session Establishment Request to the selected PGW-U for creating an Sx session for the UE. + +3. The PGW-U allocates F-TEIDu for the default bearer. The PGW-U sends an Sx Session Establishment Response to the PGW-C confirming the successful creation of the Sx session. It includes the F-TEIDu it has allocated for the default bearer. +4. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.3.2 Procedures with GTP based S2a establishment + +This clause defines interactions between the CP and UP function during the following procedures: + +- UE-Initiated Connectivity to PDN in WLAN on GTP S2a (TS 23.402 [4] clause 16.8.1). +- WLAN on GTP S2a for roaming, LBO and non-roaming scenarios (TS 23.402 [4] clause 16.2.1). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The new PGW-C selects a new PGW-U and creates an Sx session. + +![Sequence diagram showing interactions between CP and UP functions for GTP based S2a establishment. The diagram is divided into two main parts, (A) and (B), representing different scenarios. Part (A) shows steps 1-5, where the UE initiates connectivity, and the New SGW-C selects a New SGW-U. The PGW-C sends an Sx Session Establishment Request to the PGW-U, which responds. Part (B) shows steps 6-11, where the UE initiates connectivity, and the PGW-C sends an Sx Session Establishment Request to the PGW-U, which responds. Both parts include steps for PDN connection establishment and Sx session establishment.](b06a4c871dfd0ce034cf801519d0039a_img.jpg) + +The diagram illustrates the interaction between various network functions for GTP based S2a establishment. The functions involved are: UE, TWAN, MME, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. The diagram is split into two vertical sections, (A) and (B). Section (A) covers steps 1 to 5, involving PDN connection establishment and Sx Session Establishment. Section (B) covers steps 6 to 11, also involving PDN connection establishment and Sx Session Establishment. Each step is associated with a figure reference (e.g., Figure 16.2.1-1 or Figure 16.8.1-1) and a set of steps (e.g., Steps: 1-2 or Steps: 1). The Sx Session Establishment Request and Response messages are shown between the PGW-C and PGW-U. + +Sequence diagram showing interactions between CP and UP functions for GTP based S2a establishment. The diagram is divided into two main parts, (A) and (B), representing different scenarios. Part (A) shows steps 1-5, where the UE initiates connectivity, and the New SGW-C selects a New SGW-U. The PGW-C sends an Sx Session Establishment Request to the PGW-U, which responds. Part (B) shows steps 6-11, where the UE initiates connectivity, and the PGW-C sends an Sx Session Establishment Request to the PGW-U, which responds. Both parts include steps for PDN connection establishment and Sx session establishment. + +**Figure 6.3.3.2-1: Interaction between CP and UP function with GTP based S2a establishment** + +- 1-2. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +3. The PGW-C shall select new PGW-U as specified in clause 5.12 The PGW-C sends an Sx Session Establishment Request to the selected PGW-U for creating Sx session for the UE. +4. The PGW-U allocates F-TEIDu for the default bearer. The PGW-U sends an Sx Session Establishment Response to the PGW-C confirming the successful creation of the Sx session. It includes the F-TEIDu it has allocated for the default bearer. +- 5-7. The HSS/AAA is also made aware of the PGW-C identity at this time. The relevant steps of the procedure as specified in the figure above are then executed. + +The following steps are relevant only for "WLAN on GTP S2a for roaming, LBO and non-roaming scenarios" where TWAG using the layer 3 attach request (i.e. a DHCPv4 message) is sent by the UE as the attach trigger. + +These steps are executed only if steps 3-7 shown in figure 16.2.1-1 are omitted where TWAP sends the layer 2 attach trigger to the TWAG. + +8. The PGW-C shall select new PGW-U as specified in clause 5.12. The PGW-C sends an Sx Session Establishment Request to the selected PGW-U for creating Sx session for the UE. +9. The PGW-U allocates F-TEIDu for the bearer. The PGW-U sends an Sx Session Establishment Response to the PGW-C confirming the successful creation of the Sx session. It includes the F-TEIDu it has allocated for the default bearer. + +10-11. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.3.3 Procedures with GTP based S2b release + +This clause defines interactions between the CP and UP function during the following procedures: + +- UE/ePDG-initiated detach procedure with GTP on S2b (TS 23.402 [4] clause 7.4.3.1). +- HSS/AAA-initiated detach procedure with GTP on S2b (TS 23.402 [4] clause 7.4.4.1). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The PGW-C releases the existing Sx session from the PGW-U. + +![Sequence diagram showing interactions between CP and UP functions for GTP based S2b release. The diagram includes lifelines for UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. It details four steps: 1. Release of PDN connection (referencing Figure 7.4.3-1 and 7.4.4-1), 2. Sx Session Termination Request from PGW-C to PGW-U, 3. Sx Session Termination Response from PGW-U to PGW-C, and 4. Release of PDN connection (referencing Figure 7.4.3-1 and 7.4.4-1).](b7fd98a4fcc4990a613abfc31c5bdb5e_img.jpg) + +The diagram is a sequence diagram illustrating the interaction between the Control Plane (CP) and User Plane (UP) functions for GTP based S2b release. The lifelines involved are: UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. The sequence of events is as follows: + +1. Release of PDN connection (referencing Figure 7.4.3-1 and 7.4.4-1). This step involves interactions between the UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. The steps are labeled as A-A.1 or A-A.1. +2. Sx Session Termination Request: PGW-C sends a request to PGW-U. +3. Sx Session Termination Response: PGW-U sends a response to PGW-C. +4. Release of PDN connection (referencing Figure 7.4.3-1 and 7.4.4-1). This step involves interactions between the UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. The steps are labeled as A2-B.1 or A2-B.1. + +Sequence diagram showing interactions between CP and UP functions for GTP based S2b release. The diagram includes lifelines for UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. It details four steps: 1. Release of PDN connection (referencing Figure 7.4.3-1 and 7.4.4-1), 2. Sx Session Termination Request from PGW-C to PGW-U, 3. Sx Session Termination Response from PGW-U to PGW-C, and 4. Release of PDN connection (referencing Figure 7.4.3-1 and 7.4.4-1). + +**Figure 6.3.3.3-1: Interaction between CP and UP function with release of GTP based S2b** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. The PGW-C sends an Sx Session Termination Request to the PGW-U to release the Sx session. +3. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session. +4. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.3.4 Procedures with GTP based S2a release + +This clause defines interactions between the CP and UP function during the following procedures: + +- UE/TWAN Initiated Detach and UE/TWAN requested PDN Disconnection on GTP S2a (TS 23.402 [4] clause 16.3.1.1). +- UE/TWAN-Initiated Detach in WLAN on GTP S2a (TS 23.402 [4] clause 16.7.1.1). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The PGW-C releases the existing Sx session from the PGW-U. + +![Sequence diagram showing interaction between CP and UP function with release of GTP based S2a. The diagram includes lifelines for UE, TWAN, MME, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. It details two scenarios for S2a release: 1. UE or TWAN triggered detach (Steps 1-2) and 2. UE or TWAN triggered detach (Steps 3-6).](7ed5d5770331f31ade15439a21c31425_img.jpg) + +The diagram illustrates the interaction between the Control Plane (CP) and User Plane (UP) functions for the release of GTP based S2a. The lifelines involved are UE, TWAN, MME, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. The process is divided into two main scenarios: + +- 1. UE or TWAN triggered detach:** This scenario corresponds to Figure 16.3.1.1-1 and Figure 16.7.1.1-1. It involves Steps 1-2. The UE or TWAN initiates the detach process, which triggers a series of messages between the MME, SGWs, and PGW-C. +- 2. Sx Session Termination Request:** The PGW-C sends an Sx Session Termination Request to the PGW-U. +- 3. Sx Session Termination Response:** The PGW-U responds with an Sx Session Termination Response to the PGW-C. +- 4. UE or TWAN triggered detach:** This scenario corresponds to Figure 16.3.1.1-1 and Figure 16.7.1.1-1. It involves Steps 3-6. This part of the process completes the detach and session release. + +Sequence diagram showing interaction between CP and UP function with release of GTP based S2a. The diagram includes lifelines for UE, TWAN, MME, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. It details two scenarios for S2a release: 1. UE or TWAN triggered detach (Steps 1-2) and 2. UE or TWAN triggered detach (Steps 3-6). + +**Figure 6.3.3.4-1: Interaction between CP and UP function with release of GTP based S2a** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. The PGW-C sends an Sx Session Termination Request to the PGW-U to release the Sx session. +3. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session. +4. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.3.5 Procedures with dedicated bearer activation by PGW + +This clause defines interactions between the CP and UP function during the following procedures: + +- Dedicated S2b Bearer Activation Procedure with GTP on S2b (TS 23.402 [4] clause 7.10). +- Dedicated S2a Bearer Activation Procedure with GTP on S2a (TS 23.402 [4] clause 16.5). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The PGW-C modifies the existing Sx session for activating new dedicated bearer. + +![Sequence diagram showing interaction between CP and UP function with dedicated bearer activation by PGW. The diagram includes lifelines for UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. It details two scenarios for bearer activation: 1. Activation of S2a/S2b bearer (Step 1) and 2. Activation of S2a/S2b bearer (Steps 2-4).](a78db21022e0687c18d97ed547dd7ecb_img.jpg) + +The diagram illustrates the interaction between the Control Plane (CP) and User Plane (UP) functions for dedicated bearer activation by PGW. The lifelines involved are UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. The process is divided into two main scenarios: + +- 1. Activation of S2a/S2b bearer:** This scenario corresponds to Figure 7.10-1 and Figure 16.5-1. It involves Step 1. The PGW-C initiates the activation procedure based on a PCC decision provision from the PCRF. +- 2. Sx Session Modification Request:** The PGW-C sends an Sx Session Modification Request to the PGW-U to activate the new dedicated bearer. +- 3. Sx Session Modification Response:** The PGW-U responds with an Sx Session Modification Response to the PGW-C, confirming the successful modification and providing TEIDs. +- 4. Activation of S2a/S2b bearer:** This scenario corresponds to Figure 7.10-1 and Figure 16.5-1. It involves Steps 2-4. This part of the process completes the bearer activation. + +Sequence diagram showing interaction between CP and UP function with dedicated bearer activation by PGW. The diagram includes lifelines for UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. It details two scenarios for bearer activation: 1. Activation of S2a/S2b bearer (Step 1) and 2. Activation of S2a/S2b bearer (Steps 2-4). + +**Figure 6.3.3.5-1: Interaction between CP and UP function with dedicated bearer activation by PGW** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. The PGW-C initiates dedicated bearer activation procedure based on the PCC decision provision (QoS policy) message received from the PCRF. It uses received QoS policy to assign the EPS Bearer QoS, i.e., it assigns the values to the bearer level QoS parameters QCI, ARP, GBR and MBR. The PGW-C sends an Sx Session Modification Request to the existing PGW-U for activating new dedicated bearer for the UE. +3. The PGW-U shall allocate TEIDs for the new bearer(s). The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the successful modification of the Sx session. It shall include the TEIDs it has allocated for the new bearer(s). +4. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.3.6 Procedures with bearer deactivation by PGW + +This clause defines interactions between the CP and UP function during the following procedures: + +- PDN GW Initiated Bearer Deactivation with GTP on S2b (TS 23.402 [4] clause 7.9.2). +- PDN GW Initiated Bearer Deactivation with GTP on S2a (TS 23.402 [4] clause 16.4.1). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The PGW-C modifies the existing Sx session for deactivating the dedicated bearer. + +![Sequence diagram showing interactions between UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF for bearer deactivation. The diagram is divided into two main horizontal sections. The top section, labeled '1. Deactivation of S2a/S2b bearer', shows a message flow from PGW-C to PGW-U (Step 1: Sx Session Modification Request) and a return message (Step 1: Sx Session Modification Response). The bottom section, labeled '4. Deactivation of S2a/S2b bearer', shows a more complex flow involving multiple steps (2-6 or 2-8) between PGW-C and PGW-U. References to Figure 7.9.2-1, Figure 16.4.1-1, and TS 23.402 clauses are included.](39536a630fa74c3bcfd1670ee2152809_img.jpg) + +Sequence diagram showing interactions between UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF for bearer deactivation. The diagram is divided into two main horizontal sections. The top section, labeled '1. Deactivation of S2a/S2b bearer', shows a message flow from PGW-C to PGW-U (Step 1: Sx Session Modification Request) and a return message (Step 1: Sx Session Modification Response). The bottom section, labeled '4. Deactivation of S2a/S2b bearer', shows a more complex flow involving multiple steps (2-6 or 2-8) between PGW-C and PGW-U. References to Figure 7.9.2-1, Figure 16.4.1-1, and TS 23.402 clauses are included. + +**Figure 6.3.3.6-1: Interaction between CP and UP function with bearer deactivation by PGW-C** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. The PGW-C initiates bearer deactivation procedure based on IP-CAN modifications encountered by the PCRF when the dynamic PCC is deployed. The PGW-C sends an Sx Session Modification Request to the existing PGW-U for deactivating the dedicated bearer for the UE. +3. The PGW-U de-allocates the TEIDs for the dedicated bearer and sends an Sx Session Modification Response to the PGW-C confirming the successful modification of the Sx session. +4. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.3.7 Procedures with bearer modification + +This clause defines interactions between the CP and UP function during the following procedures: + +- S2b Bearer Modification Procedure with GTP on S2b (TS 23.402 [4] clause 7.11.1). +- HSS Initiated Subscribed QoS Modification (TS 23.402 [4] clause 7.11.2). +- PDN GW-initiated S2a Bearer Modification Procedure with GTP on S2a (TS 23.402 [4] clause 16.6.1). +- HSS Initiated Subscribed QoS Modification (TS 23.402 [4] clause 16.6.2). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The PGW-C modifies the existing Sx session for modification of the existing bearer. + +![Sequence diagram showing interaction between CP and UP function with bearer modification. The diagram illustrates four main steps: 1. Modification of S2a/S2b bearer, 2. Sx Session Modification Request, 3. Sx Session Modification Response, and 4. Modification of S2a/S2b bearer. The entities involved are UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. Step 1 involves multiple sub-steps (Figure 7.11.1-1, Figure 7.11.2-1, Figure 16.6.1-1, Figure 16.6.2-1) with corresponding steps 1, 1-2, 1, and 1. Step 2 is the request from PGW-C to PGW-U. Step 3 is the response from PGW-U to PGW-C. Step 4 involves multiple sub-steps (Figure 7.11.1-1, Figure 7.11.2-1, Figure 16.6.1-1, Figure 16.6.2-1) with corresponding steps 2-4, 3-6, 2-5, and 2-7.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +Sequence diagram showing interaction between CP and UP function with bearer modification. The diagram illustrates four main steps: 1. Modification of S2a/S2b bearer, 2. Sx Session Modification Request, 3. Sx Session Modification Response, and 4. Modification of S2a/S2b bearer. The entities involved are UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. Step 1 involves multiple sub-steps (Figure 7.11.1-1, Figure 7.11.2-1, Figure 16.6.1-1, Figure 16.6.2-1) with corresponding steps 1, 1-2, 1, and 1. Step 2 is the request from PGW-C to PGW-U. Step 3 is the response from PGW-U to PGW-C. Step 4 involves multiple sub-steps (Figure 7.11.1-1, Figure 7.11.2-1, Figure 16.6.1-1, Figure 16.6.2-1) with corresponding steps 2-4, 3-6, 2-5, and 2-7. + +**Figure 6.3.3.7-1: Interaction between CP and UP function with bearer modification** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. The PGW-C initiates dedicated bearer modification procedure based on the PCC decision provision (QoS policy) message received from the PCRF. It uses this QoS policy to determine that a service data flow shall be aggregated to or removed from an active bearer or that the authorized QoS of a service data flow has changed. The PGW-C sends an Sx Session Modification Request to the existing PGW-U for modification of the existing bearer for the UE. +3. The PGW-U updates the Sx parameters and sends an Sx Session Modification Response to the PGW-C confirming the successful modification of the Sx session. +4. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.3.8 Procedures with handover from non-3GPP access + +This clause defines interactions between the CP and UP function during the following procedures: + +- Handover from Trusted Non-3GPP IP Access to E-UTRAN with GTP on S2a or S2b and GTP on S5/S8 interfaces (TS 23.402 [4] clause 8.2.1.1 and clause 16.11). +- Handover from Trusted Non-3GPP IP Access to UTRAN/GERAN with GTP on S2a and GTP based S5/S8 (TS 23.402 [4] clause 8.2.1.3 and clause 16.11). +- Handover from Untrusted Non-3GPP IP Access to E-UTRAN with GTP on S2b and GTP on S5/S8 interfaces (TS 23.402 [4] clause 8.6.1.1). +- Handover from Untrusted Non-3GPP IP Access to UTRAN/GERAN with GTP on S2b and GTP on S5/S8 interfaces (TS 23.402 [4] clause 8.6.1.2). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The SGW-C selects a SGW-U and creates an Sx session. +- The SGW-C modifies the existing Sx session for modification of the bearer. +- The PGW-C selects a PGW-U and creates an Sx session. +- The PGW-C modifies the existing Sx session for modification of the bearer. + +![Sequence diagram showing the interaction between CP and UP functions with handover from non-3GPP access. The diagram illustrates the flow of messages between UE, Non-3GPP Access, ePDG, SGW-C, SGW-U, PGW-C, PGW-U, HSS, and PCRF for PDN session establishment and modification steps.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +| UE | Non-3GPP Access | ePDG | SGW-C | SGW-U | PGW-C | PGW-U | HSS | PCRF | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------|-------|--------------------------------------|-------|--------------------------------------|-----|------| +| 1. Establishment of new PDN session
Clause 16.11
Figure 8.6.1.1-1
Figure 8.6.1.2-1
Steps: 1-6 for E-UTRAN, steps 1-8 for UTRAN/GERAN
Steps: 1-6
Steps: 1-8
or | | | | | | | | | +| | | | | 2. Sx Session Establishment Request | | | | | +| | | | | 3. Sx Session Establishment Response | | | | | +| 4. Establishment of new PDN session
Clause 16.11
Figure 8.6.1.1-1
Figure 8.6.1.2-1
Steps: 7-8 for E-UTRAN, steps 9-10 for UTRAN/GERAN
Steps: 7-8
Steps: 9-10
or | | | | | | | | | +| | | | | | | 5. Sx Session Modification Request | | | +| | | | | | | 6. Sx Session Modification Response | | | +| 7. Modification of the PDN session
Clause 16.11
Figure 8.6.1.1-1
Figure 8.6.1.2-1
Steps: 9-12 for E-UTRAN, steps 11-13 for UTRAN/GERAN
Steps: 9-12
Steps: 11-13
or | | | | | | | | | +| | | | | 8. Sx Session Modification Request | | | | | +| | | | | 9. Sx Session Modification Response | | | | | +| 10. Modification of the PDN session
Clause 16.11
Figure 8.6.1.1-1
Figure 8.6.1.2-1
Step: 13 for E-UTRAN, step 14 For UTRAN/GERAN
Step: 13
Step: 14
or | | | | | | | | | +| | | | | | | 11. Sx Session Modification Request | | | +| | | | | | | 12. Sx Session Modification Response | | | +| 13. Modification of the PDN session
Clause 16.11
Figure 8.6.1.1-1
Figure 8.6.1.2-1
Steps: 14-18
Steps: 15-17
or | | | | | | | | | + +Sequence diagram showing the interaction between CP and UP functions with handover from non-3GPP access. The diagram illustrates the flow of messages between UE, Non-3GPP Access, ePDG, SGW-C, SGW-U, PGW-C, PGW-U, HSS, and PCRF for PDN session establishment and modification steps. + +Figure 6.3.3.8-1: Interaction between CP and UP function with handover from non-3GPP access + +- Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- The SGW-C shall select SGW-U as specified in clause 5.12 when the request with a Handover Indication information. The SGW-C sends Sx Session Establishment Request to the selected SGW-U for creating Sx session for the UE. +- The SGW-U allocates F-TEIDu for all received bearers. The SGW-U sends Sx Session Establishment Response to the SGW-C confirming the successful creation of the Sx session. It includes the F-TEIDu it has allocated for each and every bearer. +- The relevant steps of the procedure as specified in the figure above are executed. Since Handover Indication is included, the PGW-C may execute a PCEF-Initiated IP-CAN Session Modification Procedure with the PCRF. +- The PGW-C sends an Sx Session Modification Request to the PGW-U for modifying the Sx session for the UE. +- The PGW-U allocates F-TEIDu for all received bearers. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the successful modification of the Sx session. It includes the F-TEIDu it has allocated for each and every bearer. +- The relevant steps of the procedure as specified in the figure above are executed. +- The SGW-C sends an Sx Session Modification Request after Radio and Access bearers are established at the SGW-C. + +9. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the successful modification of the Sx session. +10. The relevant steps of the procedure as specified in the figure above are executed. +11. The PGW-C sends an Sx Session Modification Request to prompt the PGW-U to tunnel packets from non 3GPP IP access to 3GPP access system and immediately start routing packets to the SGW-U for the default and any dedicated EPS bearers established. +12. The PGW-U sends an Sx Session Modification Response to the PGW-C. +13. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.3.9 Procedures with handover from 3GPP access + +This clause defines interactions between the CP and UP function during the following procedures: + +- Handover from 3GPP Access to Untrusted Non-3GPP IP Access with GTP on S2b (TS 23.402 [4] clause 8.6.2.1). +- Handover in single-connection mode from 3GPP access to Trusted WLAN on GTP S2a for roaming and non-roaming scenarios (TS 23.402 [4] clause 16.10.1.1). + +During the above procedures following is the nature of interactions between the CP and UP function: + +- The new PGW-C selects a new PGW-U and creates an Sx session. + +![Sequence diagram showing interactions between CP and UP functions during handover from 3GPP access. The diagram includes lifelines for UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. It details the PDN connection establishment and Sx session modification steps.](8afb16b644b2fe89d5c34251c3e6bf0c_img.jpg) + +The diagram illustrates the interaction between the Control Plane (CP) and User Plane (UP) functions during a handover from 3GPP access. The lifelines involved are: UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. + +The sequence of events is as follows: + +1. PDN connection establishment: This step is initiated by the UE and involves interactions between the UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. The relevant steps are Figure 8.6.2.1-1 and Figure 16.10.1.1-1. The steps are numbered 1-B1 or 0-4. +2. Sx Session Modification Request: The PGW-C sends this request to the PGW-U. +3. Sx Session Modification Response: The PGW-U sends this response to the PGW-C. +4. PDN connection establishment (continued): This step continues from the previous one, involving the same lifelines. The relevant steps are Figure 8.6.2.1-1 and Figure 16.10.1.1-1. The steps are numbered B2-9 onward or 5-11. + +Sequence diagram showing interactions between CP and UP functions during handover from 3GPP access. The diagram includes lifelines for UE, Non-3GPP Access, ePDG, New SGW-C, New SGW-U, Old SGW-C, Old SGW-U, PGW-C, PGW-U, HSS, and PCRF. It details the PDN connection establishment and Sx session modification steps. + +**Figure 6.3.3.9-1: Interaction between CP and UP function with handover from 3GPP access** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +2. The PGW-C allocates F-TEIDu for each and every bearer. Then the PGW-C sends an Sx Session Establishment Request to the selected PGW-U for modifying the Sx session for the UE. +3. The PGW-U allocates F-TEIDu for all received bearers. The PGW-U sends an Sx Session Establishment Response to the PGW-C confirming the successful modification of the Sx session. It includes the F-TEIDu it has allocated for each and every bearer. +4. The relevant steps of the procedure as specified in the figure above are executed. + +### 6.3.4 Updates to procedures specified in TS 23.060 [5] + +#### 6.3.4.1 Procedures with PDN connection deactivation + +##### 6.3.4.1.1 Procedures with SGSN terminating S4 interface + +This clause defines interactions between the CP and UP function during the following procedures related to the deactivation of a PDN connection: + +###### Group 1: + +- Combined GPRS / IMSI Attach procedure: + - Including steps specific for S4 SGSN: Combined GPRS / IMSI Attach procedure, Delete Bearer by the new SGSN, using S4, and Combined GPRS / IMSI Attach procedure, Delete Bearer by the old SGSN, using S4. +- MS-Initiated Combined GPRS / IMSI Detach Procedure. +- SGSN-Initiated GPRS Detach Procedure. +- HLR-Initiated GPRS Detach Procedure: + - Including steps specific for S4 SGSN: SGSN interaction during Detach Procedure when using S4. +- MS Initiated Bearer Deactivation Procedure for A/Gb mode (with Teardown Ind). +- MS Initiated Bearer Deactivation Procedure for Iu mode (with Teardown Ind). +- SGSN-initiated Bearer Deactivation Procedure (with Teardown Ind): + - Including steps specific for S4 SGSN: MS- and SGSN Initiated PDN connection Deactivation Procedure using S4. + +###### Group 2: + +- GGSN-initiated PDP Context Deactivation Procedure (with Teardown Ind): + - Including steps specific for S4 SGSN: PDN GW-initiated Bearer Deactivation Procedure using S4, part 1 and part 2. + +During the above procedures, following is the nature of interactions between the CP and UP function: + +- The SGW-C releases the existing Sx session from SGW-U. +- The PGW-C releases the existing Sx session from PGW-U. +- The SGW-C modifies the existing Sx session for SGW-U. +- The PGW-C modifies the existing Sx session for PGW-U. + +![Sequence diagram showing interaction between CP and UP functions with PDN connection deactivation Group 1. The diagram illustrates various procedures involving MS, RAN, New SGSN, Old SGSN, SGW-C, SGW-U, PGW-C, PGW-U, EIR, New MSC/VLR, HLR, and Old MSC/VLR. It includes steps for Combined GPRS / IMSI Attach, Session Modification, Session Termination, and Detach procedures.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +The diagram is a sequence diagram titled "Figure 6.3.4.1.1-1: Interaction between CP and UP function with PDN connection deactivation Group 1". It shows the interaction between various network elements over time. The elements are: MS, RAN, New SGSN, Old SGSN, SGW-C, SGW-U, PGW-C, PGW-U, EIR, New MSC/VLR, HLR, and Old MSC/VLR. The diagram is divided into several numbered sections, each representing a different procedure or a group of steps. Section 1 is the "Combined GPRS / IMSI Attach procedure" (Figure 22 step 1-5, Figure 22A step 6a). Section 2a and 2b show SGW-C sending a Session Modification Request to SGW-U and receiving a response. Section 2c shows the "Combined GPRS / IMSI Attach procedure, Delete Bearer by the new SGSN, using S4" (Figure 22A step 6b). Section 3a and 3b show PGW-C sending a Session Termination Request to PGW-U and receiving a response. Section 3c shows the "Combined GPRS / IMSI Attach procedure, Delete Bearer by the new SGSN, using S4" (Figure 22A step 6c). Section 3d and 3e show SGW-C sending a Session Termination Request to SGW-U and receiving a response. Section 4 lists various procedures: MS-Initiated Combined GPRS / IMSI Detach Procedure (Figure 23 step 1, Figure 25A step A), SGSN-Initiated GPRS Detach Procedure (Figure 24 step 1, Figure 25A step A), HLR-Initiated GPRS Detach Procedure (Figure 25 step 1-2, Figure 25A step A), MS Initiated Bearer Deactivation Procedure for A/Gb mode (Figure 74 step 1-2, Figure 74a step A), MS Initiated Bearer Deactivation Procedure for Iu mode (Figure 75 step 1-3, Figure 74a step A), and SGSN-initiated Bearer Deactivation Procedure (Figure 74a step A). Section 5a and 5b show SGW-C sending a Session Modification Request to SGW-U and receiving a response. Section 6 lists procedures: Combined GPRS / IMSI Attach Procedure (Figure 22B step 7d2 or Figure 25A step B), SGSN interaction when using S4 (Figure 25A step B), and MS-and SGSN Initiated PDN connection Deactivation Procedure using S4 (Figure 74a step B). Section 7a and 7b show PGW-C sending a Session Termination Request to PGW-U and receiving a response. Section 8 lists procedures: Combined GPRS / IMSI Attach Procedure (Figure 22B step 7e1 or Figure 25A step C), SGSN interaction when using S4 (Figure 25A step C), MS-and SGSN Initiated PDN connection Deactivation Procedure using S4 (Figure 74a step C). Section 9a and 9b show SGW-C sending a Session Termination Request to SGW-U and receiving a response. Section 10 lists procedures: Combined GPRS / IMSI Attach procedure (Figure 22 step 7f-12), MS-Initiated Combined GPRS / IMSI Detach Procedure (Figure 23 step 3-6), SGSN-Initiated GPRS Detach Procedure (Figure 24 step 3-5), HLR-Initiated GPRS Detach Procedure (Figure 25 step 4-7), MS Initiated Bearer Deactivation Procedure for A/Gb mode (Figure 74 step 4-6), MS Initiated Bearer Deactivation Procedure for Iu mode (Figure 75 step 4-5), and SGSN-initiated PDP Context Deactivation Procedure (Figure 76 step 2-4). + +Sequence diagram showing interaction between CP and UP functions with PDN connection deactivation Group 1. The diagram illustrates various procedures involving MS, RAN, New SGSN, Old SGSN, SGW-C, SGW-U, PGW-C, PGW-U, EIR, New MSC/VLR, HLR, and Old MSC/VLR. It includes steps for Combined GPRS / IMSI Attach, Session Modification, Session Termination, and Detach procedures. + +**Figure 6.3.4.1.1-1: Interaction between CP and UP function with PDN connection deactivation Group 1** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- 2a. The SGW-C sends an Sx Session Modification Request to the SGW-U to modify the Sx session. SGW-C shall request SGW-U to stop counting uplink packets for the affected bearers. SGW-C shall also request the SGW-U to discard uplink packets received from eNodeB for the affected bearers. +- 2b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the modification of the Sx session. +- 2c. The relevant steps of the procedure as specified in the figure above are executed. +- 3a. The PGW-C may send an Sx Session Termination Request to the PGW-U to release the Sx session. +- 3b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session. +- 3c. The relevant steps of the procedure as specified in the figure above are executed. + +- 3d. The SGW-C may send an Sx Session Termination Request to the SGW-U to release the Sx session. +- 3e. The SGW-U sends an Sx Session Termination Response to the SGW-C confirming the release of the Sx session. +4. The relevant steps of the procedure as specified in the figure above are executed. +- 5a. The SGW-C may send an Sx Session Modification Request to the SGW-U in detach and Bearer Deactivation procedures. SGW-C shall indicate SGW-U to stop counting uplink packets for the affected bearers. SGW-C shall also indicate the SGW-U to discard uplink packets received from eNodeB for the affected bearers. +- 5b. The SGW-U sends an Sx Session Modification Response to the SGW-C. +6. The relevant steps of the procedure as specified in the figure above are executed. +- 7a. The PGW-C may send an Sx Session Termination Request to the PGW-U to release the Sx session. +- 7b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session. +8. The relevant steps of the procedure as specified in the figure above are executed. +- 9a. The SGW-C may send an Sx Session Termination Request to the SGW-U to release the Sx session. +- 9b. The SGW-U sends an Sx Session Termination Response to the SGW-C confirming the release of the Sx session. +10. The relevant steps of the procedure as specified in the figure above are executed. + +![Sequence diagram showing the interaction between CP and UP functions with PDN connection deactivation Group 2. The diagram illustrates the flow of messages between MS, RAN, SGSN, SGW-C, SGW-U, PGW-C, and PGW-U during various steps of the PDP context deactivation procedure.](1f1614411edea7edfc86c839a608e1fc_img.jpg) + +The sequence diagram illustrates the interaction between Control Plane (CP) and User Plane (UP) functions during PDN connection deactivation. The entities involved are MS, RAN, SGSN, SGW-C, SGW-U, PGW-C, and PGW-U. The procedure is divided into several steps, with some steps involving sub-messages between CP and UP functions. + +- Step 1:** GGSN initiated PDP Context Deactivation Procedure (Figure 77a step A). This step involves the SGSN, SGW-C, SGW-U, PGW-C, and PGW-U. +- Step 2:** PGW-C sends an Sx Session Modification Request (2a) to the PGW-U, and the PGW-U responds with an Sx Session Modification Response (2b). +- Step 4:** GGSN initiated PDP Context Deactivation Procedure (Figure 77 step 2, Figure 77b step A). This step involves the MS, RAN, SGSN, SGW-C, SGW-U, PGW-C, and PGW-U. +- Step 5:** SGW-C sends an Sx Session Termination Request (5a) to the SGW-U, and the SGW-U responds with an Sx Session Termination Response (5b). +- Step 6:** GGSN initiated PDP Context Deactivation Procedure (Figure 77b step B). This step involves the SGW-C, SGW-U, PGW-C, and PGW-U. +- Step 7:** PGW-C sends an Sx Session Termination Request (7a) to the PGW-U, and the PGW-U responds with an Sx Session Termination Response (7b). +- Step 8:** GGSN initiated PDP Context Deactivation Procedure (Figure 77 step 4-5). This step involves the MS, RAN, and SGSN. + +Sequence diagram showing the interaction between CP and UP functions with PDN connection deactivation Group 2. The diagram illustrates the flow of messages between MS, RAN, SGSN, SGW-C, SGW-U, PGW-C, and PGW-U during various steps of the PDP context deactivation procedure. + +**Figure 6.3.4.1.1-2: Interaction between CP and UP function with PDN connection deactivation Group 2** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- 2a. The PGW-C sends an Sx Session Modification Request to the PGW-U when it initiates bearer deactivation procedure. PGW-C shall indicate PGW-U to stop counting downlink packets for the affected bearers. PGW-C shall also indicate the PGW-U to discard downlink packets received for the affected bearers. +- 2b. The PGW-U sends an Sx Session Modification Response to the PGW-C. +- 3a. Void. + +- 3b. Void. +4. The relevant steps of the procedure as specified in the figure above are executed. +- 5a. The SGW-C sends an Sx Session Termination Request to the SGW-U to release the Sx session. +- 5b. The SGW-U sends an Sx Session Termination Response to the SGW-C confirming the release of the Sx session. +6. The relevant steps of the procedure as specified in the figure above are executed. +- 7a. The PGW-C sends an Sx Session Termination Request to the PGW-U to release the Sx session. +- 7b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session. +8. The relevant steps of the procedure as specified in the figure above are executed. + +##### 6.3.4.1.2 Procedures with SGSN terminating Gn/Gp interface + +This clause defines interactions between the CP and UP function during the following procedures related to the deactivation of a PDN connection: + +###### Group 1: + +- Combined GPRS / IMSI Attach procedure. +- MS-Initiated Combined GPRS / IMSI Detach Procedure. +- SGSN-Initiated GPRS Detach Procedure. +- HLR-Initiated GPRS Detach Procedure. +- MS Initiated PDP Context Deactivation Procedure for A/Gb mode (with Teardown Ind). +- MS Initiated PDP Context Deactivation Procedure for Iu mode (with Teardown Ind). +- SGSN-initiated PDP Context Deactivation Procedure (with Teardown Ind). + +###### Group 2: + +- GGSN-initiated PDP Context Deactivation Procedure (with Teardown Ind). + +During the above procedures, following is the nature of interactions between the CP and UP function: + +- The PGW-C releases the existing Sx session from PGW-U. + +![Sequence diagram showing interaction between CP and UP functions with PDN connection deactivation Group 1. The diagram illustrates the flow of messages between MS, RAN, New SGSN, Old SGSN, PGW-C, PGW-U, EIR, New MSC/VLR, and Old MSC/VLR across five main steps. Step 1 is a combined GPRS/IMSI attach procedure. Step 2 involves Sx session termination between PGW-C and PGW-U. Step 3 lists various detach and PDP context deactivation procedures. Step 4 involves another Sx session termination between PGW-C and PGW-U. Step 5 lists another set of detach and PDP context deactivation procedures.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +| MS | RAN | New SGSN | Old SGSN | PGW-C | PGW-U | EIR | New MSC/VLR | Old MSC/VLR | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|----------|----------|------------------------------------|-------|-----|-------------|-------------| +| 1. Combined GPRS / IMSI Attach procedure Figure 22 step 1-6 | | | | | | | | | +| | | | | 2a.Sx Session Termination Request | | | | | +| | | | | 2b.Sx Session Termination Response | | | | | +| 3. Combined GPRS / IMSI Attach procedure Figure 22 step 7a-7e or
MS-Initiated Combined GPRS / IMSI Detach Procedure Figure 23 step 1-2 or
SGSN-Initiated GPRS Detach Procedure Figure 24 step 1-2 or
HLR-Initiated GPRS Detach Procedure Figure 25 step 1-3 or
MS Initiated PDP Context Deactivation Procedure for A/Gb mode Figure 74 step 1-3 or
MS Initiated PDP Context Deactivation Procedure for Iu mode Figure 75 step 1-3 or
SGSN-initiated PDP Context Deactivation Procedure Figure 76 step 1 | | | | | | | | | +| | | | | 4a.Sx Session Termination Request | | | | | +| | | | | 4b.Sx Session Termination Response | | | | | +| 5. Combined GPRS / IMSI Attach procedure Figure 22 step 7f-12 or
MS-Initiated Combined GPRS / IMSI Detach Procedure Figure 23 step 3-6 or
SGSN-Initiated GPRS Detach Procedure Figure 24 step 3-5 or
HLR-Initiated GPRS Detach Procedure Figure 25 step 4-7 or
MS Initiated PDP Context Deactivation Procedure for A/Gb mode Figure 74 step 4-6 or
MS Initiated PDP Context Deactivation Procedure for Iu mode Figure 75 step 4-5 or
SGSN-initiated PDP Context Deactivation Procedure Figure 76 step 2-4 | | | | | | | | | + +Sequence diagram showing interaction between CP and UP functions with PDN connection deactivation Group 1. The diagram illustrates the flow of messages between MS, RAN, New SGSN, Old SGSN, PGW-C, PGW-U, EIR, New MSC/VLR, and Old MSC/VLR across five main steps. Step 1 is a combined GPRS/IMSI attach procedure. Step 2 involves Sx session termination between PGW-C and PGW-U. Step 3 lists various detach and PDP context deactivation procedures. Step 4 involves another Sx session termination between PGW-C and PGW-U. Step 5 lists another set of detach and PDP context deactivation procedures. + +**Figure 6.3.4.1.2-1: Interaction between CP and UP function with PDN connection deactivation Group 1** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- 2a. The PGW-C may send an Sx Session Termination Request to the PGW-U to release the Sx session. +- 2b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session. +3. The relevant steps of the procedure as specified in the figure above are executed. +- 4a. The PGW-C may send an Sx Session Termination Request to the PGW-U to release the Sx session. +- 4b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session. +5. The relevant steps of the procedure as specified in the figure above are executed. + +![Sequence diagram showing the interaction between CP and UP functions for PDN connection deactivation. The diagram involves five entities: MS, RAN, SGSN, PGW-C, and PGW-U. The process is divided into three main steps: 1. GGSN initiated PDP Context Deactivation Procedure (Figure 77 step 1), 3. GGSN initiated PDP Context Deactivation Procedure (Figure 77 step 2-3), and 5. GGSN initiated PDP Context Deactivation Procedure (Figure 77 step 4-5). Step 1 involves PGW-C sending an Sx Session Modification Request to PGW-U and receiving a response. Step 2-3 involves PGW-C sending an Sx Session Termination Request to PGW-U and receiving a response. Step 4-5 is a continuation of the GGSN initiated procedure.](5801c19431e76330430e92a598cc7a16_img.jpg) + +``` + +sequenceDiagram + participant MS + participant RAN + participant SGSN + participant PGW-C + participant PGW-U + + Note right of SGSN: 1. GGSN initiated PDP Context Deactivation Procedure Figure 77 step 1 + PGW-C->>PGW-U: 2a.Sx Session Modification Request + PGW-U-->>PGW-C: 2b.Sx Session Modification Response + + Note right of SGSN: 3. GGSN initiated PDP Context Deactivation Procedure Figure 77 step 2-3 + PGW-C->>PGW-U: 4a.Sx Session Termination Request + PGW-U-->>PGW-C: 4b.Sx Session Termination Response + + Note right of SGSN: 5. GGSN initiated PDP Context Deactivation Procedure Figure 77 step 4-5 + +``` + +Sequence diagram showing the interaction between CP and UP functions for PDN connection deactivation. The diagram involves five entities: MS, RAN, SGSN, PGW-C, and PGW-U. The process is divided into three main steps: 1. GGSN initiated PDP Context Deactivation Procedure (Figure 77 step 1), 3. GGSN initiated PDP Context Deactivation Procedure (Figure 77 step 2-3), and 5. GGSN initiated PDP Context Deactivation Procedure (Figure 77 step 4-5). Step 1 involves PGW-C sending an Sx Session Modification Request to PGW-U and receiving a response. Step 2-3 involves PGW-C sending an Sx Session Termination Request to PGW-U and receiving a response. Step 4-5 is a continuation of the GGSN initiated procedure. + +**Figure 6.3.4.1.2-2: Interaction between CP and UP function with PDN connection deactivation Group 2** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- 2a. The PGW-C sends an Sx Session Modification Request to the PGW-U when it initiates bearer deactivation procedure. PGW-C shall indicate PGW-U to stop counting downlink packets for the affected bearers. PGW-C shall also indicate the PGW-U to discard downlink packets received for the affected bearers. +- 2b. The PGW-U sends an Sx Session Modification Response to the PGW-C. +3. The relevant steps of the procedure as specified in the figure above are executed. +- 4a. The PGW-C sends an Sx Session Termination Request to the PGW-U to release the Sx session. +- 4b. The PGW-U sends an Sx Session Termination Response to the PGW-C confirming the release of the Sx session. +5. The relevant steps of the procedure as specified in the figure above are executed. + +#### 6.3.4.2 Procedures with PDN connection modification + +##### 6.3.4.2.1 Procedures with SGSN terminating S4 interface + +This clause defines interactions between the CP and UP function during the following procedures related to the modification of a PDN connection. + +Group 1 Procedures for Location Management, Handover, Service Request and Inter-System Change: + +- Inter SGSN Routeing Area Update Procedure: + - Including steps specific for S4 SGSN: Inter SGSN Routeing Area Update and Combined Inter SGSN RA / LA Update using S4. +- Combined RA / LA Update in the Case of Inter SGSN RA Update Procedure: + - Including steps specific for S4 SGSN: Inter SGSN Routeing Area Update and Combined Inter SGSN RA / LA Update using S4. +- Iu mode RA Update Procedure: + - Including steps specific for S4 SGSN: Routeing Area Update Procedure using S4. + +- SRNS Relocation Procedure. +- Combined Hard Handover and SRNS Relocation Procedure. +- Combined Cell / URA Update and SRNS Relocation Procedure: + - Including steps specific for S4 SGSN: Serving RNS Relocation Procedure, Combined Hard Handover and SRNS Relocation Procedure, and Combined Cell / URA Update and SRNS Relocation Procedure Using S4. +- Enhanced Serving RNS Relocation: + - Including steps specific for S4 SGSN: Enhanced Serving RNS Relocation Procedure using S4. +- MS Initiated Service Request Procedure. +- Network Initiated Service Request Procedure: + - Including steps specific for S4 SGSN: UE Initiated Service Request Procedure Using S4. +- Iu mode to A/Gb mode Intra SGSN Change: + - Including steps specific for S4 SGSN: Iu mode to A/Gb mode Intra SGSN Change using S4. +- A/Gb mode to Iu mode Intra SGSN Change: + - Including steps specific for S4 SGSN: A/Gb mode to Iu mode Intra-SGSN Change using S4. +- Iu mode to A/Gb mode Inter-SGSN Change: + - Including steps specific for S4 SGSN: Iu mode to A/Gb mode Inter-SGSN Change using S4. +- A/Gb mode to Iu mode Inter SGSN Change: + - Including steps specific for S4 SGSN: A/Gb mode to Iu mode Inter-SGSN Change using S4. +- GPRS Paging Procedure (A/Gb mode): + - S4 specific handling in Paging response for GPRS Downlink Transfer with no established user plane on S4. + +###### Group 2 UE/SGSN initiated PDN connection modification: + +- Secondary PDP Context Activation Procedure for A/Gb mode. +- Secondary PDP Context Activation Procedure for Iu mode: + - Including steps specific for S4 SGSN: Secondary PDP Context Activation Procedure, PDP Creation part, using S4. +- MS-Initiated PDP Context Modification Procedure, A/Gb mode. +- MS-Initiated PDP Context Modification Procedure, Iu mode. +- SGSN-Initiated PDP Context Modification Procedure, A/Gb mode. +- SGSN-Initiated PDP Context Modification Procedure, Iu mode: + - Including steps specific for S4 SGSN: Request part of SGSN-Initiated EPS Bearer Modification Procedure using S4, and Update part of SGSN-Initiated EPS Bearer Modification Procedure using S4. +- MS Initiated PDP Context Deactivation Procedure for A/Gb mode (without Teardown Ind). +- MS Initiated PDP Context Deactivation Procedure for Iu mode (without Teardown Ind). +- SGSN-initiated PDP Context Deactivation Procedure (without Teardown Ind): + - Steps specific for S4 SGSN: MS-and SGSN Initiated Bearer Deactivation Procedure. + +###### Group 3 PGW initiated PDN connection modification: + +- Network Requested Secondary PDP Context Activation Procedure using S4. +- GGSN-Initiated PDP Context Modification Procedure: + - Including steps specific for S4 SGSN: PGW-Initiated Bearer Modification Procedure, A/Gb mode. +- GGSN-Initiated PDP Context Modification Procedure: + - Including steps specific for S4 SGSN: PGW-Initiated Bearer Modification Procedure, Iu mode. +- GGSN-initiated PDP Context Deactivation Procedure (without Teardown Ind): + - Including steps specific for S4 SGSN: PGW-initiated Bearer Deactivation Procedure. + +During the above procedures, following is the nature of interactions between the CP and UP function: + +- The SGW-C informs the SGW-U to modify the Sx session. +- The PGW-C informs the PGW-U to modify the Sx session. + +![Sequence diagram showing interaction between CP and UP functions for PDN connection modification. It includes lifelines for MS, RAN, New SGSN, Old SGSN, SGW-C, SGW-U, PGW-C, PGW-U, EIR, New MSC/VLR, HLR, and Old MSC/VLR. The diagram shows three main blocks of procedures (1, 2c, 4) separated by Sx Session Modification Request/Response messages (2a/2b between SGW-C/U and 3a/3b between PGW-C/U).](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +``` + + MS RAN New SGSN Old SGSN SGW-C SGW-U PGW-C PGW-U EIR New MSC/VLR HLR Old MSC/VLR + | | | | | | | | | | | | + +--------------------------------------------------------------------------------------+ + | 1. Inter SGSN Routeing Area Update Procedure Figure 33 step 1-5, Figure 33b step 6A or | + | Combined RA / LA Update in Case of Inter SGSN RA... Figure 35 step 1-5, Figure 33b step 6A or | + | Iu mode RA Update Procedure Figure 36 step 1-8, Figure 36b step 9A or | + | SRNS Relocation Procedure Figure 39 step 1-12, Figure 39b step A or | + | ... (and other procedures) ... | + +--------------------------------------------------------------------------------------+ + | | | | | | | | | | | | + | | | | | 2a. Sx Session Modification Request | | | + | | | | |------------------------------------->| | | + | | | | | 2b. Sx Session Modification Response | | | + | | | | |<-------------------------------------| | | + | | | | | | | | | | | | + +-----------------------------------------+ | | | | | | + | 2c. Inter SGSN Routeing Area Update... | | | | | | | + | ... (list of procedures) ... | | | | | | | + +-----------------------------------------+ | | | | | | + | | | | | | | | | | | | + | | | | | | | 3a. Sx Session Modification Request | + | | | | | | |----------------------->| | | + | | | | | | | 3b. Sx Session Modification Response | + | | | | | | |<-----------------------| | | + | | | | | | | | | | | | + +--------------------------------------------------------------------------------------+ + | 4. Inter SGSN Routeing Area Update Procedure Figure 33b step 6C-6D, Fig 33 step 7-12 or | + | ... (list of procedures and figure steps) ... | + +--------------------------------------------------------------------------------------+ + +``` + +Sequence diagram showing interaction between CP and UP functions for PDN connection modification. It includes lifelines for MS, RAN, New SGSN, Old SGSN, SGW-C, SGW-U, PGW-C, PGW-U, EIR, New MSC/VLR, HLR, and Old MSC/VLR. The diagram shows three main blocks of procedures (1, 2c, 4) separated by Sx Session Modification Request/Response messages (2a/2b between SGW-C/U and 3a/3b between PGW-C/U). + +**Figure 6.3.4.2.1-1: Interaction between CP and UP function with PDN connection modification, Group 1** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- 2a. The SGW-C may send an Sx Session Modification Request to the SGW-U to update the Sx session. +- 2b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the update the Sx session. +- 2c. The relevant steps of the procedure as specified in the figure above are executed. + +- 3a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. +- 3b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session. +4. The relevant steps of the procedure as specified in the figure above are executed. + +NOTE 1: Step 2a/2b happens when SGW-C receives request message from S4 SGSN, and step 3a/3b happens when PGW-C receives request message from SGW-C. + +![](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +| MS | RAN | SGSN | SGW-C | SGW-U | PGW-C | PGW-U | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|------|-------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| 1. Secondary PDP Context Activation Procedure for A/Gb mode
Secondary PDP Context Activation Procedure for Iu mode
SGSN-Initiated PDP Context Modification Procedure, A/Gb mode
SGSN-Initiated PDP Context Modification Procedure, Iu mode
MS-Initiated PDP Context Modification Procedure, A/Gb mode
MS-Initiated PDP Context Modification Procedure, Iu mode
MS Initiated PDP Context Deactivation Procedure for A/Gb mode
MS Initiated PDP Context Deactivation Procedure for Iu mode
SGSN-initiated PDP Context Deactivation Procedure | | | | | Figure 65 step 1, Figure 66a step A-C or
Figure 66 step 1, Figure 66a step A-C or
Figure 70a, Figure 70c step A-D or
Figure 70b, Figure 70c step A-D or
Figure 72a step 1, Figures 72c/72d step A-B or
Figure 72b step 1, Figures 72c/72d step A-B or
Figure 74 step 1-2, Figure 74b step A-B or
Figure 75 step 1-2, Figure 74b step A-B or
Figure 74b step A-B | | +| | | | | | 2a.Sx Session Modification Request
2b.Sx Session Modification Response | | +| 3. Secondary PDP Context Activation Procedure for A/Gb mode
Secondary PDP Context Activation Procedure for Iu mode
MS Initiated PDP Context Deactivation Procedure for A/Gb mode
MS Initiated PDP Context Deactivation Procedure for Iu mode
SGSN-initiated PDP Context Deactivation Procedure | | | | | Figure 65, Figure 66a step D or
Figure 66, Figure 66a step D or
Figure 74, Figure 74b step C or
Figure 75, Figure 74b step C or
Figure 76, Figure 74b step C | | +| | | | | | 4a.Sx Session Modification Request
4b.Sx Session Modification Response | | +| 5. Secondary PDP Context Activation Procedure for A/Gb mode
Secondary PDP Context Activation Procedure for Iu mode
SGSN-Initiated PDP Context Modification Procedure, A/Gb mode
SGSN-Initiated PDP Context Modification Procedure, Iu mode
MS-Initiated PDP Context Modification Procedure, A/Gb mode
MS-Initiated PDP Context Modification Procedure, Iu mode
MS Initiated PDP Context Deactivation Procedure for A/Gb mode
MS Initiated PDP Context Deactivation Procedure for Iu mode
SGSN-initiated PDP Context Deactivation Procedure | | | | | Figure 65 step 7, Figure 66a step E or
Figure 66 step 7, Figure 66a step E or
Figure 70a step 3, 6-8, Figure 70d step A or
Figure 70b step 3, 6-8, Figure 70d step A or
Figure 72a Step 4, 7, Figure 72e step A or
Figure 72b step 5, 7, Figure 72e step A or
Figure 74 step 4-6, Figure 74b step D-E or
Figure 75 step 4-5, Figure 74b step D-E or
Figure 76 step 2-4, Figure 74b step D-E | | +| | | | | | 6a.Sx Session Modification Request
6b.Sx Session Modification Response | | +| 7. Secondary PDP Context Activation Procedure for A/Gb mode
Secondary PDP Context Activation Procedure for Iu mode
SGSN-Initiated PDP Context Modification Procedure, A/Gb mode
SGSN-Initiated PDP Context Modification Procedure, Iu mode
MS-Initiated PDP Context Modification Procedure, A/Gb mode
MS-Initiated PDP Context Modification Procedure, Iu mode
MS Initiated PDP Context Deactivation Procedure for A/Gb mode
MS Initiated PDP Context Deactivation Procedure for Iu mode
SGSN-initiated PDP Context Deactivation Procedure | | | | | Figure 65, Figure 66a step F or
Figure 66, Figure 66a step F or
Figure 70a, Figure 70d step B or
Figure 70b, Figure 70d step B or
Figure 72a, Figure 72e step B or
Figure 72b, Figure 72e step B or
Figure 74, Figure 74b step F or
Figure 75, Figure 74b step F or
Figure 76, Figure 74b step F | | +| | | | | | 8a.Sx Session Modification Request
8b.Sx Session Modification Response | | + +**Figure 6.3.4.2.1-2: Interaction between CP and UP function with PDN connection modification, Group 2** + +- Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. For "Secondary PDP Context Activation Procedure", PGW-C may request PGW-U to allocate F-TEID for the dedicated bearer. For "MS- or SGSN- Initiated PDP Context Deactivation Procedure", PGW-C shall request PGW-U to stop counting and stop forwarding packets for the affected bearers. + +- 2b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session. +3. The relevant steps of the procedure as specified in the figure above are executed. +- 4a. The SGW-C may send an Sx Session Modification Request to the SGW-U to update the Sx session. For "Secondary PDP Context Activation Procedure", SGW-C requests SGW-U to allocate F-TEID for the dedicate bearer. For "MS- or SGSN Initiated PDP Context Deactivation Procedure", SGW-C shall request SGW-U to stop counting and stop forwarding packets for the affected bearers. +- 4b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the update the Sx session. +5. The relevant steps of the procedure as specified in the figure above are executed. +- 6a. The SGW-C may send an Sx Session Modification Request to the SGW-U to update the Sx session. For "Secondary PDP Context Activation Procedure", the SGW-C shall include the F-TEIDu of the activated bearer received from the S4 SGSN or RNC. For "MS- or SGSN- initiated PDP Context Modification" with bearer QoS update procedure, SGW-C provides updated QoS parameters to SGW-U. For "MS- or SGSN Initiated PDP Context Deactivation Procedure", SGW-C shall request SGW-U to remove the PDR for the affected bearers. +- 6b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the update the Sx session. +7. The relevant steps of the procedure as specified in the figure above are executed. +- 8a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. For "Secondary PDP Context Activation Procedure", the PGW-C shall include the F-TEIDu of the activated bearer received from the SGW. For "MS- or SGSN- Initiated PDP Context Deactivation Procedure", the PGW-C shall request PGW-U to remove the PDR for the affected bearers. +- 8b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session. + +NOTE 2: Step 2a/2b happens before PGW-C sends request message to SGW-C, and step 8a/8b happens when PGW-C receives response message from SGW-C. + +NOTE 3: Step 4a/4b happens when SGW-C receives request message from PGW-C, and step 6a/6b happens when SGW-C receives response message from S4 SGSN. + +![Sequence diagram showing interaction between CP and UP functions with PDN connection modification. The diagram includes steps 1 through 8, with sub-steps 2a, 2b, 3a, 3b, 4, 5a, 5b, 6, 7a, 7b, and 8. The entities involved are MS, RAN, SGSN, SGW-C, SGW-U, PGW-C, and PGW-U. The diagram is organized into a table with three columns: Step Number, Description, and Figure Reference.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +| Step | Description | Figure Reference | +|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| +| 1. | Network Requested Secondary PDP Context Activation Procedure using S4
GGSN-Initiated PDP Context Modification Procedure, A/Gb mode
GGSN-Initiated PDP Context Modification Procedure, Iu mode
GGSN-initiated PDP Context Deactivation Procedure | Figure 69c step 1 or
Figure 71a, Figure 71c, step A or
Figure 71b, Figure 71c, step A or
Figure 77, Figure 77a step A-B | +| 2a. | Sx Session Modification Request | | +| 2b. | Sx Session Modification Response | | +| 3a. | Sx Session Modification Request | | +| 3b. | Sx Session Modification Response | | +| 4. | Network Requested Secondary PDP Context Activation Procedure using S4
GGSN-Initiated PDP Context Modification Procedure, A/Gb mode
GGSN-Initiated PDP Context Modification Procedure, Iu mode
GGSN-initiated PDP Context Deactivation Procedure | Figure 69c step 2-7 or
Figure 71a step 2-5, Figure 71c step B-C or
Figure 71b step 2-5, Figure 71c step B-C or
Figure 77 step 2, Figure 77b step A | +| 5a. | Sx Session Modification Request | | +| 5b. | Sx Session Modification Response | | +| 6. | Network Requested Secondary PDP Context Activation Procedure using S4
GGSN-Initiated PDP Context Modification Procedure, A/Gb mode
GGSN-Initiated PDP Context Modification Procedure, Iu mode
GGSN-initiated PDP Context Deactivation Procedure | Figure 69c step 8 or
Figure 71a, Figure 71c step D or
Figure 71b, Figure 71c step D or
Figure 77, Figure 77b step B | +| 7a. | Sx Session Modification Request | | +| 7b. | Sx Session Modification Response | | +| 8. | Network Requested Secondary PDP Context Activation Procedure using S4
GGSN-initiated PDP Context Deactivation Procedure | Figure 69c step 9 or
Figure 77, step 4-5 | + +Sequence diagram showing interaction between CP and UP functions with PDN connection modification. The diagram includes steps 1 through 8, with sub-steps 2a, 2b, 3a, 3b, 4, 5a, 5b, 6, 7a, 7b, and 8. The entities involved are MS, RAN, SGSN, SGW-C, SGW-U, PGW-C, and PGW-U. The diagram is organized into a table with three columns: Step Number, Description, and Figure Reference. + +**Figure 6.3.4.2.1-3: Interaction between CP and UP function with PDN connection modification, Group 3** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- 2a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. For "Network Requested Secondary PDP Context Activation Procedure", PGW-C may request PGW-U to allocate F-TEID for the dedicated bearer. For "GGSN Initiated PDP Context Deactivation Procedure", PGW-C shall request PGW-U to stop counting and stop forwarding packets for the affected bearers. +- 2b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session. +- 3a. The SGW-C may send an Sx Session Modification Request to the SGW-U to update the Sx session. For "Network Requested Secondary PDP Context Activation Procedure", SGW-C requests SGW-U to allocate F-TEID for the dedicated bearer. For "GGSN Initiated PDP Context Deactivation Procedure", SGW-C shall request SGW-U to stop counting and stop forwarding packets for the affected bearers. +- 3b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the update the Sx session. +4. The relevant steps of the procedure as specified in the figure above are executed. + +- 5a. The SGW-C may send an Sx Session Modification Request to the SGW-U to update the Sx session. For "Network Requested Secondary PDP Context Activation Procedure", the SGW-C shall include the F-TEIDu of the activated bearer received from the S4 SGSN or RNC. For "GGSN initiated PDP Context Modification" with bearer QoS update, SGW-C provides updated QoS parameters to SGW-U. For "GGSN Initiated PDP Context Deactivation Procedure", SGW-C shall request SGW-U to remove the PDR for the affected bearers. + - 5b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the update the Sx session. + 6. The relevant steps of the procedure as specified in the figure above are executed. + - 7a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. For "Network Requested Secondary PDP Context Activation Procedure", the PGW-C shall include the F-TEIDu of the activated bearer received from the SGW. For "GGSN initiated PDP Context Modification" with bearer QoS update, PGW-C provides updated QoS parameters to PGW-U. For "GGSN Initiated PDP Context Deactivation Procedure", the PGW-C shall request PGW-U to remove the PDR for the affected bearers. + - 7b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session. +- NOTE 4: Step 2a/2b happens before PGW-C sends request message to SGW-C, and step 7a/7b happens when PGW-C receives response message from SGW-C. +- NOTE 5: Step 3a/3b happens when SGW-C receives request message from PGW-C, and step 5a/5b happens when SGW-C receives response message from S4 SGSN. + +##### 6.3.4.2.2 Procedures with SGSN terminating Gn/Gp interface + +This clause defines interactions between the CP and UP function during the following procedures related to the modification of a PDN connection. + +Group 1 Procedures for Location Management, Handover, Service Request and Inter-System Change: + +- Inter SGSN Routeing Area Update Procedure. +- Combined RA / LA Update in the Case of Inter SGSN RA Update Procedure. +- Iu mode RA Update Procedure. +- SRNS Relocation Procedure. +- Combined Hard Handover and SRNS Relocation Procedure. +- Combined Cell / URA Update and SRNS Relocation Procedure. +- Enhanced Serving RNS Relocation. +- MS Initiated Service Request Procedure. +- Network Initiated Service Request Procedure. +- Iu mode to A/Gb mode Intra SGSN Change. +- A/Gb mode to Iu mode Intra SGSN Change. +- Iu mode to A/Gb mode Inter-SGSN Change. +- A/Gb mode to Iu mode Inter SGSN Change. +- GPRS Paging Procedure (A/Gb mode). + +Group 2 UE/SGSN initiated PDN connection modification: + +- Secondary PDP Context Activation Procedure for A/Gb mode. +- Secondary PDP Context Activation Procedure for Iu mode. +- SGSN-Initiated PDP Context Modification Procedure, A/Gb mode. + +- SGSN-Initiated PDP Context Modification Procedure, Iu mode. +- MS-Initiated PDP Context Modification Procedure, A/Gb mode. +- MS-Initiated PDP Context Modification Procedure, Iu mode. +- MS Initiated PDP Context Deactivation Procedure for A/Gb mode (without Teardown Ind). +- MS Initiated PDP Context Deactivation Procedure for Iu mode (without Teardown Ind). +- SGSN-initiated PDP Context Deactivation Procedure (without Teardown Ind). + +Group 3 PGW initiated PDN connection modification: + +- Network Requested Secondary PDP Context Activation Procedure using Gn +- GGSN-Initiated PDP Context Modification Procedure for A/Gb mode +- GGSN-Initiated PDP Context Modification Procedure for Iu mode +- GGSN-initiated PDP Context Deactivation Procedure + +During the above procedures, following is the nature of interactions between the CP and UP function: + +- The PGW-C informs the PGW-U to modify the Sx session. + +![](6984a27b2b89e0995d5216ec29b41d1c_img.jpg) + +| MS | RAN | New
SGSN | Old
SGSN | PGW-C | PGW-U | EIR | New
MSC/VLR | Old
MSC/VLR | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-------------|-------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|----------------| +| 1. Inter SGSN Routeing Area Update Procedure
Combined RA / LA Update in the Case of Inter SGSN RA Update Procedure
Iu mode RA Update Procedure
SRNS Relocation Procedure
Combined Hard Handover and SRNS Relocation Procedure
Combined Cell / URA Update and SRNS Relocation Procedure
Enhanced Serving RNS Relocation
MS Initiated Service Request Procedure using Gn/Gp
Network Initiated Service Request Procedure
Iu mode to A/Gb mode Intra SGSN Change
A/Gb mode to Iu mode Intra SGSN Change
Iu mode to A/Gb mode Inter-SGSN Change
A/Gb mode to Iu mode Inter SGSN Change
GPRS Paging Procedure (A/Gb mode) | | | | | Figure 33 step 1-6
Figure 35 step 1-6
Figure 36 step 1-9
Figure 39 step 1-13
Figure 42 step 1-13
Figure 43 step 1-13
Figure 44a2 step 1-3
Figure 50 step 1-7
Figure 51 step 1-7
Figure 52 step 1-6a,
Figure 53 step 1-11a,
Figure 54 step 1-10
Figure 55 step 1-8
Figure 56 step 1-5 | | or
or
or
or
or
or
or
or
or
or
or
or
or
or | | +| | | | | 2a. Sx Session Modification Request → | | | | | +| | | | | ← 2b. Sx Session Modification Response | | | | | +| 3. Inter SGSN Routeing Area Update Procedure
Combined RA / LA Update in the Case of Inter SGSN RA Update Procedure
Iu mode RA Update Procedure
SRNS Relocation Procedure
Combined Hard Handover and SRNS Relocation Procedure
Combined Cell / URA Update and SRNS Relocation Procedure
Enhanced Serving RNS Relocation
MS Initiated Service Request Procedure using Gn/Gp
Network Initiated Service Request Procedure
Iu mode to A/Gb mode Intra SGSN Change
A/Gb mode to Iu mode Intra SGSN Change
Iu mode to A/Gb mode Inter-SGSN Change
A/Gb mode to Iu mode Inter SGSN Change | | | | | Figure 33
Figure 35
Figure 36
Figure 39
Figure 42
Figure 43
Figure 44a2
Figure 50
Figure 51
Figure 52
Figure 53
Figure 54
Figure 55 | step 7-12
step 7-16
step 10-20
step 14-15
step 14-15
step 14-15
step 4-6
step 8
step 8
step 7-15
step 12-13
step 11-22
step 9-20a | or
or
or
or
or
or
or
or
or
or
or
or
or | | + +Figure 6.3.4.2.2-1: Interaction between CP and UP function with PDN connection modification, Group 1 + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- 2a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. +- 2b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session. +3. The relevant steps of the procedure as specified in the figure above are executed. + +NOTE 1: Step 2a/2b happens when PGW-C receives request message from GnSGSN. + +![](17f0cf80b9c38adb460d4ca836960da7_img.jpg) + +| MS | RAN | SGSN | PGW-C | PGW-U | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| +| 1. Secondary PDP Context Activation Procedure for A/Gb mode
Secondary PDP Context Activation Procedure for Iu mode
SGSN-Initiated PDP Context Modification Procedure, A/Gb mode
SGSN-Initiated PDP Context Modification Procedure, Iu mode
MS-Initiated PDP Context Modification Procedure, A/Gb mode
MS-Initiated PDP Context Modification Procedure, Iu mode
MS Initiated PDP Context Deactivation Procedure for A/Gb mode
MS Initiated PDP Context Deactivation Procedure for Iu mode
SGSN-initiated PDP Context Deactivation Procedure | | | Figure 65 step 1-3
Figure 66 step 1-3
Figure 70a step 1-2
Figure 70b, step 1-2
Figure 72a Step 1-3
Figure 72b step 1-3
Figure 74 step 1-3
Figure 75 step 1-3
Figure 76 step 1 | or | +| | | | 2a.Sx Session Modification Request | → | +| | | | 2b.Sx Session Modification Response | ← | +| 3.Secondary PDP Context Activation Procedure for A/Gb mode
Secondary PDP Context Activation Procedure for Iu mode
SGSN-Initiated PDP Context Modification Procedure, A/Gb mode
SGSN-Initiated PDP Context Modification Procedure, Iu mode
MS-Initiated PDP Context Modification Procedure, A/Gb mode
MS-Initiated PDP Context Modification Procedure, Iu mode | | | Figure 65 step 5-6
Figure 66 step 4-6
Figure 70a step 3-5
Figure 70b step 3-5
Figure 72a Step 4-6
Figure 72b step 4-6 | or | +| | | | 4a.Sx Session Modification Request | → | +| | | | 4b.Sx Session Modification Response | ← | +| 5.Secondary PDP Context Activation Procedure for A/Gb mode
Secondary PDP Context Activation Procedure for Iu mode
SGSN-Initiated PDP Context Modification Procedure, A/Gb mode
SGSN-Initiated PDP Context Modification Procedure, Iu mode
MS-Initiated PDP Context Modification Procedure, A/Gb mode
MS-Initiated PDP Context Modification Procedure, Iu mode
MS Initiated PDP Context Deactivation Procedure for A/Gb mode
MS Initiated PDP Context Deactivation Procedure for Iu mode
SGSN-initiated PDP Context Deactivation Procedure | | | Figure 65 step 7
Figure 66 step 7
Figure 70a step 6-8
Figure 70b step 6-8
Figure 72a step 7
Figure 72b step 7
Figure 74 step 4-6
Figure 75 step 4-6
Figure 76 step 2-4 | or | + +**Figure 6.3.4.2.2-2: Interaction between CP and UP function with PDN connection modification, Group 2** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- 2a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. For "Secondary PDP Context Activation Procedure", PGW-C requests PGW-U to allocate F-TEID for the dedicated bearer. For "MS- and SGSN- Initiated PDP Context Deactivation Procedure", the PGW-C shall request PGW-U to remove the PDR for the affected bearers. +- 2b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session. +3. The relevant steps of the procedure as specified in the figure above are executed. + +- 4a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. +- 4b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session. +5. The relevant steps of the procedure as specified in the figure above are executed. + +NOTE 2: Step 2a/2b and step 4a/4b happen when PGW-C receives request message from GnSGSN. + +![Sequence diagram showing interaction between MS, RAN, SGSN, PGW-C, and PGW-U for PDN connection modification. The diagram is divided into five numbered steps. Step 1: GGSN-Initiated PDP Context Modification/Deactivation. Step 2: PGW-C sends Sx Session Modification Request to PGW-U, PGW-U responds. Step 3: Network Requested Secondary PDP Context Activation or GGSN-Initiated PDP Context Modification/Deactivation. Step 4: PGW-C sends Sx Session Modification Request to PGW-U, PGW-U responds. Step 5: GGSN-initiated PDP Context Deactivation. References to Figures 71a, 71b, 69, and 77 are provided for specific steps.](b63f41ca262d8ce9ef8affb62607f32b_img.jpg) + +| | | | | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|------|----------------------------------------|-------| +| MS | RAN | SGSN | PGW-C | PGW-U | +| 1. GGSN-Initiated PDP Context Modification Procedure, A/Gb mode      Figure 71a step 1      or
GGSN-Initiated PDP Context Modification Procedure, Iu mode              Figure 71b step 1      or
GGSN-initiated PDP Context Deactivation Procedure                      Figure 77 step 1 | | | | | +| | | | 2a. Sx Session Modification Request → | | +| | | | ← 2b. Sx Session Modification Response | | +| 3. Network Requested Secondary PDP Context Activation Procedure using Gn      Figure 69 step 1-3b      or
GGSN-Initiated PDP Context Modification Procedure, A/Gb mode              Figure 71a step 2-6      or
GGSN-Initiated PDP Context Modification Procedure, Iu mode              Figure 71b step 2-6      or
GGSN-initiated PDP Context Deactivation Procedure                      Figure 77 step 2-3 | | | | | +| | | | 4a. Sx Session Modification Request → | | +| | | | ← 4b. Sx Session Modification Response | | +| 5. GGSN-initiated PDP Context Deactivation Procedure                      Figure 77 step 4-5 | | | | | + +Sequence diagram showing interaction between MS, RAN, SGSN, PGW-C, and PGW-U for PDN connection modification. The diagram is divided into five numbered steps. Step 1: GGSN-Initiated PDP Context Modification/Deactivation. Step 2: PGW-C sends Sx Session Modification Request to PGW-U, PGW-U responds. Step 3: Network Requested Secondary PDP Context Activation or GGSN-Initiated PDP Context Modification/Deactivation. Step 4: PGW-C sends Sx Session Modification Request to PGW-U, PGW-U responds. Step 5: GGSN-initiated PDP Context Deactivation. References to Figures 71a, 71b, 69, and 77 are provided for specific steps. + +**Figure 6.3.4.2.2-3: Interaction between CP and UP function with PDN connection modification, Group 3** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. +- 2a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. For "GGSN Initiated PDP Context Deactivation Procedure", PGW-C shall request PGW-U to stop counting and stop forwarding packets for the affected bearers. +- 2b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session. +3. The relevant steps of the procedure as specified in the figure above are executed. +- 4a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. For "Network Requested Secondary PDP Context Activation Procedure", the PGW-C shall include the F-TEIDu of the activated bearer received from the GnSGSN. For "GGSN Initiated PDP Context Deactivation Procedure", the PGW-C shall request PGW-U to remove the PDR for the affected bearers. +- 4b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the update the Sx session. +5. The relevant steps of the procedure as specified in the figure above are executed. + +NOTE 3: Step 2a/2b happens when PGW-C sends request message to GnSGSN, and step 4a/4b happens when PGW-C receives response message from GnSGSN for GGSN initiated PDP Context Modification/Deactivation Procedure, or request message for Network Requested Secondary PDP Context Activation. + +#### 6.3.4.3 Procedures with PDN connection establishment + +This clause defines interactions between the CP and UP function during the following procedures related to the establishment of a PDN connection: + +- IPv6 Stateless Address Autoconfiguration Procedure. +- PDP Context Activation Procedure for A/Gb mode. +- PDP Context Activation Procedure for Iu mode. + +During the procedures involving S4 listed above, following is the nature of interactions between the CP and UP function: + +- The SGW-C informs the SGW-U to create the Sx session. +- The PGW-C informs the PGW-U to create the Sx session. +- The SGW-C informs the SGW-U to modify the Sx session. +- The PGW-C informs the PGW-U to modify the Sx session. + +![Sequence diagram showing interactions between CP and UP functions for PDN connection establishment. The diagram includes lifelines for MS, RAN, BSS, SGSN, SGW-C, SGW-U, PGW-C, and PGW-U. It details steps for IPv6 address autoconfiguration, PDP context activation, and Sx session management (establishment and modification) between control plane (CP) and user plane (UP) entities.](d04f4b76a3f7aa0ff51714fb1f71d9d3_img.jpg) + +The diagram illustrates the interaction between CP and UP functions across several steps: + +- Step 1:** Stateless IPv6 Address Autoconfiguration, PDP Context Activation Procedure for A/Gb mode, or PDP Context Activation Procedure for Iu mode. This step is initiated by the MS and involves the RAN, BSS, and SGSN. Reference figures: Figure 62 step 1-4, Figure 64a step A-D or Figure 63 step 1-4, Figure 64a step A-D or Figure 64 step 1-4, Figure 64a step A-D. +- Step 2a:** SGW-C sends an Sx Session Establishment Request to SGW-U. +- Step 2b:** SGW-U sends an Sx Session Establishment Response to SGW-C. +- Step 3a:** PGW-C sends an Sx Session Establishment Request to PGW-U. +- Step 3b:** PGW-U sends an Sx Session Establishment Response to PGW-C. +- Step 4:** PDP Context Activation Procedure for A/Gb mode or PDP Context Activation Procedure for Iu mode. This step involves the SGSN, SGW-C, SGW-U, PGW-C, and PGW-U. Reference figures: Figure 63 step 7-8, Figure 64b step A-B or Figure 64 step 5-8, Figure 64b step A-B. +- Step 5a:** SGW-C sends an Sx Session Modification Request to SGW-U. +- Step 5b:** SGW-U sends an Sx Session Modification Response to SGW-C. +- Step 6a:** PGW-C sends an Sx Session Modification Request to PGW-U. +- Step 6b:** PGW-U sends an Sx Session Modification Response to PGW-C. +- Step 7:** PDP Context Activation Procedure for A/Gb mode or PDP Context Activation Procedure for Iu mode. This step involves the SGSN, SGW-C, SGW-U, PGW-C, and PGW-U. Reference figures: Figure 63 step 9 or Figure 64 step 9. + +Sequence diagram showing interactions between CP and UP functions for PDN connection establishment. The diagram includes lifelines for MS, RAN, BSS, SGSN, SGW-C, SGW-U, PGW-C, and PGW-U. It details steps for IPv6 address autoconfiguration, PDP context activation, and Sx session management (establishment and modification) between control plane (CP) and user plane (UP) entities. + +**Figure 6.3.4.3-1: Interaction between CP and UP function with PDN connection establishment** + +1. Procedure as listed in this step is initiated as specified in the relevant clauses of this specification. The relevant steps of the procedure as specified in the figure above are executed. Steps in Figure 64a are specific for S4 SGSN. + +For the case that Gn/Gp SGSN interconnects with PGW-C, steps 2a/2b or 5a/5b are skipped. + +- 2a. The SGW-C sends an Sx Session Establishment Request to the SGW-U to create the Sx session. +- 2b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the Sx session creation. +- 3a. The PGW-C sends an Sx Session Establishment Request to the PGW-U to create the Sx session. + +- 3b. The PGW-U sends an Sx Session Establishment Response to the PGW-C confirming the Sx session creation. +4. The relevant steps of the procedure as specified in the figure above are executed. Steps in Figure 64b are specific for S4 SGSN. +- 5a. The SGW-C may send an Sx Session Modification Request to the SGW-U to update the Sx session. +- 5b. The SGW-U sends an Sx Session Modification Response to the SGW-C confirming the Sx session update. +- 6a. The PGW-C may send an Sx Session Modification Request to the PGW-U to update the Sx session. +- 6b. The PGW-U sends an Sx Session Modification Response to the PGW-C confirming the Sx session update. +7. The relevant steps of the procedure as specified in the figure above are executed. + +NOTE 1: For the case that SGSN interconnects with SGW via S4 reference point, steps 2a/2b or 5a/5b happens when SGW-C receives request message from SGSN, and steps 3a/3b or 6a/6b happens when PGW-C receives request message from SGW. + +NOTE 2: For the case that Gn/Gp SGSN interconnects with PGW-C, steps 3a/3b or 6a/6b happens when PGW-C receives request message from Gn/Gp SGSN. + +## 6.4 Sx Reporting Procedures + +### 6.4.1 General + +The Sx reporting procedure is used by the UP function of SGW, PGW or TDF to report events to the CP function. + +The following Sx reporting procedures exist: Sx session level reporting and Sx node level reporting. Both are initiated by the CP function. + +### 6.4.2 Sx Session Level Reporting Procedure + +This procedure is used by the UP function to report events related to an Sx session for an individual PDN connection IP-CAN session, TDF session or TDF in unsolicited reporting mode. The triggers for event reporting were configured on the UP function during Sx session management procedures by the CP function (excluding the Sx session termination procedure). + +![Sequence diagram of Sx Session Level Reporting procedure](3dea2a7c8e1120f769d0bc8ee347340d_img.jpg) + +``` +sequenceDiagram + participant UP function + participant CP function + Note left of UP function: 1. Trigger to report event + UP function->>CP function: 2. Sx Report + CP function-->>UP function: 3. Sx Report ACK +``` + +The diagram illustrates the Sx Session Level Reporting procedure. It features two vertical lifelines: 'UP function' on the left and 'CP function' on the right. The sequence of interactions is as follows: 1. A box labeled '1. Trigger to report event' is positioned on the UP function lifeline. 2. An arrow labeled '2. Sx Report' points from the UP function to the CP function. 3. A return arrow labeled '3. Sx Report ACK' points from the CP function back to the UP function. + +Sequence diagram of Sx Session Level Reporting procedure + +Figure 6.4.2-1: Sx Session Level Reporting procedure + +1. The UP function detects that an event has to be reported. The reporting triggers involve the following cases: + - (1) Usage report (by SGW-U, PGW-U and TDF-U). +Usage information shall be collected in the UP function and reported to the CP function as defined in clause 5.3 and clause 7.4. + - (2) Start of traffic detection (by PGW-U and TDF-U). + +When traffic detection is requested by PGW-C/TDF-C, and the start of traffic is detected for a PDR, the PGW-U/TDF-U shall report the start of traffic detection to the PGW-C/TDF-C and indicate the PDR rule ID. + +#### (3) Stop of traffic detection (by PGW-U and TDF-U). + +When traffic detection is requested by PGW-C/TDF-C, and the end of traffic is detected for a PDR, the PGW-U/TDF-U shall report the stop of traffic detection to the PGW-C/TDF-C and indicate the PDR rule ID. + +#### (4) Detection of 1st Downlink Data for Idle-Mode UE (by SGW-U) + +When SGW-U receives the downlink packet but no S1-bearer for transmission and the buffering is performed by SGW-U, it shall report the detection of 1st downlink data to SGW-C, for the purpose of paging the UE. SGW-U shall also report the DSCP of the packet when instructed by SGW-C (e.g. in case the Paging Policy Differentiation function as described in TS 23.401 [2] is enabled at the SGW-C). + +- The UP function sends an Sx report message (Session ID, list of [Reporting trigger, Measurement information]) to the CP function. + +The Reporting trigger parameter contains the name of the event which triggered the report and the Measurement information parameter contains the actual information the CP function requested to be informed about. + +- The CP function identifies the Sx session context based on the received Session ID and applies the reported information for the corresponding PDN connection IP-CAN session, TDF session or TDF in unsolicited reporting mode. The CP function responds with an Sx report ACK message. + +## 6.5 Sx Management Procedures + +### 6.5.1 General + +Sx management procedures are used by the CP function to manage the UP function independent of any Sx session. + +NOTE: The terminology defined in TS 29.244 [12] is used for the procedures and messages related to the Sx management procedures. + +Editor's note: More procedures may be added after stage 3 finalize the work on Sx management procedures. + +### 6.5.2 Sx PFD management Procedure + +The Sx PFD management procedure is used by the PGW-C or TDF-C to provision or remove all PFD(s) belonging to an Application ID in the UP function as described in clause 5.11.4. PFD sets belonging to different Application IDs can be managed with the same PFD management request message. + +The Sx PFD management procedure is a node level procedure, i.e. independent of any Sx session. + +![Sequence diagram of the Sx PFD Management Procedure. The diagram shows two lifelines: PGW-C / TDF-C (left) and PGW-U / TDF-U (right). Step 1: A box on the PGW-C / TDF-C lifeline contains the text '1. Trigger to provision or remove the set of PFDs belonging to an Application ID'. Step 2: An arrow labeled '2. PFD management request' points from the PGW-C / TDF-C lifeline to the PGW-U / TDF-U lifeline. Step 3: An arrow labeled '3. PFD management response' points from the PGW-U / TDF-U lifeline back to the PGW-C / TDF-C lifeline.](165508b2526a29efbae96fa16d525d28_img.jpg) + +``` + +sequenceDiagram + participant PGW-C / TDF-C + participant PGW-U / TDF-U + Note left of PGW-C / TDF-C: 1. Trigger to provision or remove the set of PFDs belonging to an Application ID + PGW-C / TDF-C->>PGW-U / TDF-U: 2. PFD management request + PGW-U / TDF-U-->>PGW-C / TDF-C: 3. PFD management response + +``` + +Sequence diagram of the Sx PFD Management Procedure. The diagram shows two lifelines: PGW-C / TDF-C (left) and PGW-U / TDF-U (right). Step 1: A box on the PGW-C / TDF-C lifeline contains the text '1. Trigger to provision or remove the set of PFDs belonging to an Application ID'. Step 2: An arrow labeled '2. PFD management request' points from the PGW-C / TDF-C lifeline to the PGW-U / TDF-U lifeline. Step 3: An arrow labeled '3. PFD management response' points from the PGW-U / TDF-U lifeline back to the PGW-C / TDF-C lifeline. + +Figure 6.5.2-1: Sx PFD Management Procedure + +- The CP function is triggered to provision or remove the PFD set belonging to an Application ID as described in clause 5.11.4. + +2. The CP function sends a PFD management request message to the UP function (containing the parameters described in clause 7.9.1) to provision/remove the PFD set corresponding to the Application ID. +3. The UP function acknowledges by responding with a PFD management response message. + +### 6.5.3 Sx Association Setup Procedure + +The Sx Association Setup procedure is used to setup an association between the CP function and the UP function which enables the CP function to subsequently interact with the UP function, e.g. to establish Sx Sessions. + +The setup of an Sx association may be initiated by the CP function or the UP function as described TS 29.244 [12], clause 6.2.6. The CP function and the UP function shall support the Sx association setup initiated by the CP function. The CP function and the UP function may additionally support the Sx association setup initiated by the UP function. + +The CP function should only establish an Sx association with a UP function that supports F-TEID allocation at the UP function. + +### 6.5.4 Sx Association Update Procedure + +The Sx Association Update procedure is used to modify an existing Sx association between the CP function and the UP function. It may be initiated by the UP function or by the CP function, as described TS 29.244 [12], clause 6.2.7. + +### 6.5.5 Sx Association Release Procedure + +The Sx Association Release procedure is used to terminate the Sx association between the CP function and the UP function due to e.g. OAM reasons. The Sx Association Release procedure can be only initiated by the CP function, as described TS 29.244 [12], clause 6.2.8. + +# --- 7 Parameters + +## 7.1 Parameters for Sx session management + +These parameters are used to control the functionality of the UP function related to an individual PDN connection, IP-CAN session, TDF session or TDF in unsolicited reporting mode as well as to inform about events occurring at the UP function. As the functionality of the respective UP functions differs, most parameters are specific to one or two of the reference points Sxa (between SGW-C and SGW-U), Sxb (PGW-C and PGW-U) and Sxc (TDF-C and TDF-U). + +The Sx session management procedures however will use the relevant parameters in the same way for all Sx reference points: the Sx session establishment procedure as well as the Sx session modification procedure provide the control parameters to the UP function, the Sx session termination procedure removes all control parameters related to an Sx session and the Sx session level reporting procedure informs the CP function about events related to the Sx session that are detected by the UP function. + +The parameters over Sx provided from CP function to UP function are grouped into session related parameters and four different rules, one "detection" rule and three different "enforcement" rules: + +- Packet Detection Rule (PDR), with information describing what packets should receive a certain treatment (e.g. forwarding and other types of enforcement). +- Forwarding Action Rule (FAR), contains information on whether forwarding, dropping or buffering is to be applied to a packet. +- Usage Reporting Rule (URR), contains information that defines a certain measurement and how it shall be reported. +- QoS Enforcement Rule (QER), contains information related to QoS enforcement of traffic. + +The UP function provides parameters over Sx to the CP function sending a Usage Report. + +## 7.2 Session context + +The session context comprises the session related parameters and all PDRs, URRs, QERs and FARs with the same Session ID. + +The following table describes the session related parameters provided over Sx. + +**Table 7.2-1: Session related parameters** + +| Attribute | Description | Comment | Applicability | | | +|------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------|-----| +| | | | SGW | PDN GW | TDF | +| Session ID | Uniquely identifies a session. | This session corresponds to a PDN connection for SGW, a PDN connection and an IP-CAN session for PGW, TDF session for TDF or a TDF in unsolicited reporting mode. | X | X | X | + +## 7.3 Packet Detection Rule + +The following table describes the Packet Detection Rule (PDR) containing information required to classify a packet arriving at the UP function. There is at least one PDR per direction, e.g. UL direction or DL direction. + +**Table 7.3-1: Attributes within Packet Detection Rule** + +| Attribute | | Description | Comment | Applicability | | | +|------------------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------|-----| +| | | | | SGW | PDN GW | TDF | +| Session ID | | Identifies the session associated to this PDR | | X | X | X | +| Rule ID | | Unique identifier to identify this information. | | X | X | X | +| Precedence | | Determines the order, in which the detection information of all rules is applied | | | X | X | +| Packet detection information | Source interface | Contains the values "access side", "core side", "CP function" or "SGi-LAN". | Identifies whether the rule applies to incoming packets from the access side (i.e. up-link), the core side (i.e. down-link), the CP function (the packet from CP function) or the SGi-LAN side (the packet has experienced SGi-LAN Service Functions). | X | X | X | +| | UE IP address | One IPv4 address and/or one IPv6 prefix with prefix length | Combination of UE IP address (together with Network instance, if necessary), F-TEID, SDF filters, application ID for traffic detection:
SGW UL: Local F-TEID
SGW DL: Local F-TEID

PGW UL: Local F-TEID + UE IP address + SDF/application.ID
PGW DL: UE IP address + SDF/application ID

TDF UL (solicited mode): UE IP address + SDF/application ID
TDF DL (solicited mode): UE IP address + SDF/application ID
TDF UL/DL (unsolicited mode): application ID | | X | X | +| | Network instance | Identifies the Network instance associated with the incoming packet. (NOTE 1). | | X | X | X | +| | Local F-TEID | | | X | X | | +| | List of SDF Filter(s) | | | | X | X | +| | Application ID | | | | X | X | +| Outer header removal | | Instructs the UP function to remove one or more outer header(s) (e.g. IP+UDP+GTP) from the incoming packet. | Any extension header shall be stored for this packet. | X | X | | +| Forwarding Action Rule ID | | The Forwarding Action Rule ID identifies a forwarding action that has to be applied. | | X | X | X | +| List of Usage Reporting Rule ID(s) | | Every Usage Reporting Rule ID identifies a measurement action that has to be applied. | | X | X | X | +| List of QoS Enforcement Rule ID(s) | | Every QoS Enforcement Rule ID identifies a QoS enforcement action that has to be applied. | | X | X | X | + +NOTE 1: The Network instance is needed e.g. in the following cases: + +- PGW/TDF-U supports multiple APN with overlapping IP addresses; +- PGW-U is connected to SGWs in different IP domains; +- SGW-U is connected to PGWs in different IP domains; +- SGW-U is connected to eNodeBs in different IP domains. + +## 7.4 Usage Reporting Rule + +The following table describes the Usage Reporting Rule (URR) that defines how a packet shall be accounted as well as when and how to report the measurements. + +**Table 7.4-1: Attributes within Usage Reporting Rule** + +| Attribute | Description | Comment | Applicability | | | +|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------|-----| +| | | | SGW | PDN GW | TDF | +| Session ID | Identifies the session associated to this URR | | X | X | X | +| Rule ID | Unique identifier to identify this information. | | X | X | X | +| Reporting triggers | One or multiple of the events can be activated for the generation and reporting of the usage report. | Applicable events include: Start/stop of traffic detection with/without application instance identifier and deduced SDF filter reporting; Deletion of last PDR for a URR; Periodic measurement threshold reached; Volume/Time/Event measurement threshold reached; Immediate report requested; Measurement of incoming UL traffic; Measurement of discarded DL traffic. | X | X | X | +| Periodic measurement threshold | Defines the point in time for sending a periodic report for this URR key (e.g. timeofday) | This allows generation of periodic usage report for e.g. offline charging. It can also be used for realizing the Monitoring time of the usage monitoring feature. It can also be used for realizing the Quota-Idle-Timeout, i.e. to enable the CP function to check whether any traffic has passed during this time. | X | X | X | +| Volume measurement threshold | Value in terms of uplink and/or downlink and/or total byte-count when the measurement report is to be generated. | | X | X | X | +| Time measurement threshold | Value in terms of the time duration (e.g. in seconds) when the measurement report is to be generated. | | X | X | X | +| Event measurement threshold | Number of events (identified according to a locally configured policy) after which the measurement report is to be generated. | | | X | X | +| Inactivity detection time | Defines the period of time after which the time measurement shall stop, if no packets are received. | Timer corresponding to this duration is restarted at the end of each transmitted packet. | | X | X | +| Event based reporting | Points to a locally configured policy which is identifies event(s) trigger for generating usage report. | | | X | X | + +| | | | | | | +|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---| +| Linked URR ID | Points to one or more other URR ID. | This enables the generation of a combined Usage Report for this and other URRs by triggering their reporting. See clause 5.2.2.4, TS 29.244 [12]. | | X | X | +| Measurement method | Indicates the method for measuring the network resources usage, i.e. the data volume, duration, combined volume/duration, or event. | | X | X | X | +| Measurement information | Indicates specific conditions to be applied for measurements. | It is used to request:
  • - measurement before QoS enforcement, and/or
  • - to pause or set to active a measurement as for the Pause of charging, and/or
  • - to request reduced reporting for application start/stop events.
| X | X | X | + +## 7.5 Forwarding Action Rule + +The following table describes the Forwarding Action Rule (FAR) that defines how a packet shall be forwarded, including packet encapsulation/decapsulation and forwarding destination. + +Table 7.5-1: Attributes within Forwarding Action Rule + +| Attribute | Description | Comment | Applicability | | | +|------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------|-----| +| | | | SGW | PDN GW | TDF | +| Session ID | Identifies the session associated to this FAR | | X | X | X | +| Rule ID | Unique identifier to identify this information. | | X | X | X | +| Network instance | Identifies the Network instance associated with the outgoing packet. (NOTE 1). | | X | X | X | +| Destination interface | Contains the values "access side", "core side", "CP function", or "SGi-LAN". | Identifies the interface for outgoing packets towards the access side (i.e. down-link), the core side (i.e. up-link), the CP function side (i.e. towards CP function) or the SGi-LAN side (i.e. towards SGi-LAN). | X | X | X | +| Outer header creation | Instructs the UP function to add an outer header (IP+UDP+GTP) to the outgoing packet | Contains the F-TEIDu of peer entity (e.g. eNB, SGW, PGW, CP function). Any extension header stored for this packet shall be added. | X | X | | +| Send end marker packet(s) | Instructs the UP function to construct end marker packet(s) and send them out as described in clause 5.8.1. | This parameter should be sent together with the "out header creation" parameter of the new F-TEID-u. | X | X | | +| Transport level marking | Transport level packet marking in the uplink and downlink, e.g. setting the DiffServ Code Point. | | X | X | | +| Forwarding policy | Reference to a preconfigured traffic forwarding treatment for FMSS or http redirection (NOTE 2) | Contains TSP ID or Redirect Destination and values for the forwarding behaviour (always, after measurement report (for termination action "redirect")) | | X | X | +| Container for header enrichment | Contains information to be used by the UP function for header enrichment | Only relevant for the uplink direction | | X | X | +| Buffer Control Information | Instructs the UP function on how to perform buffering | See clause 5.2.4 in TS 29.244 [12]. | X | | | +| Delay Downlink Packet Notification Information | D parameter | See clause 5.9.3 | X | | | +| Extended buffering Information | DL Data Buffer Expiration Time | See clause 5.9.3 | X | | | +| | DL Suggested Packet Count | See clause 5.9.3 | | | | + +NOTE 1: Needed e.g. in case: + +- PGW/TDF-U supports multiple APN with overlapping IP addresses; +- PGW-U is connected to SGWs in different IP domains; +- SGW-U is connected to PGWs in different IP domains; +- SGW UP-U is connected to eNodeBs in different IP domains. + +NOTE 2: The TSP ID action is enforced before the Outer header creation actions. + +## 7.6 QoS Enforcement Rule + +The following table describes the QoS Enforcement Rule (QER) that defines how a packet shall be treated in terms of bit rate limitation and packet marking for QoS purposes. All Packet Detection Rules that refer to the same QER share the same QoS resources, e.g. MBR. + +**Table 7.6-1: Attributes within QoS Enforcement Rule** + +| Attribute | Description | Comment | Applicability | | | +|-------------------------------------|----------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------|-----| +| | | | SGW | PDN GW | TDF | +| Session ID | Identifies the session associated to this QER | | X | X | X | +| Rule ID | Unique identifier to identify this information. | | X | X | X | +| QoS Enforcement Rule correlation ID | An identity allowing the UP function to correlate multiple Sessions for the same UE and APN. | Is used to correlate QoS Enforcement Rules for APN-AMBR enforcement | | X | | +| Gate status UL/DL | Instructs the UP function to let the flow pass or to block the flow | Values are: open, close, close after measurement report (for termination action "discard") | | X | X | +| Maximum bitrate | The uplink/downlink maximum bitrate to be enforced for the packets. | This field may e.g. contain any one of:
- APN-AMBR (for a QER that is referenced by all relevant Packet Detection Rules of all PDN Connections to an APN)
- TDF session MBR (for a QER that is referenced by all Packet Detection Rules of a TDF Session)
- bearer MBR (for a QER that is referenced by all Packet Detection Rules of a bearer)
- SDF MBR (for a QER that is referenced by the uplink/downlink Packet Detection Rule of a SDF) | | X | X | +| Guaranteed bitrate | The uplink/downlink guaranteed bitrate authorized for the packets. | This field contains:
- bearer GBR (for a QER that is referenced by all Packet Detection Rules of a bearer) | X | X | | +| Down-link flow level marking | Flow level packet marking in the downlink. | For PGW, this is for controlling the SCI marking in the GTP extension header (for service indication towards GERAN as described in TS 23.060 [5]).
For TDF, this is for controlling the DSCP marking for application indication. | | X | X | + +| | | | | | | +|-------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|---|--| +| Packet rate | Number of packets per time interval to be enforced. | This field contains any one of:
- downlink packet rate for Serving PLMN Rate Control (the QER is referenced by all PDRs of the UE belonging to PDN connections using CLoT EPS Optimizations as described in TS 23.401 [2])
- uplink/downlink packet rate for APN Rate Control (the QER is referenced by all PDRs of the UE belonging to PDN connections to the same APN using CLoT EPS Optimizations as described in TS 23.401 [2]). | | X | | +|-------------|-----------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|---|--| + +## 7.7 Usage Report generated by UP function + +The UP function sends the usage report to inform the CP function about the measurement of an active URR or about the detection of application traffic of an active Packet Detection Rule. For each URR, the usage report may be generated repeatedly, i.e. as long as any one of the valid event triggers applies. A final usage report is sent for a URR when it is no longer active, i.e. either the URR is removed or all the references to this URR in any of the Packet Detection Rules belonging to the Sx session. + +Following attributes can be included in the usage report: + +Table 7.7-1: Attributes within Usage Report + +| Attribute | Description | Comment | Applicability | | | +|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------|-----| +| | | | SGW | PDN GW | TDF | +| Session ID | Uniquely identifies a session. | This corresponds to a PDN connection for SGW and PGW or a TDF session for TDF | X | X | X | +| Rule ID | Uniquely identifies the Packet Detection Rule or Usage Reporting Rule within a session which triggered the report | Packet Detection Rule is only indicated when Reporting trigger is Detection of 1st DL packet on bearer (SGW) or Start/stop of traffic detection (PGW/TDF). Usage Reporting Rule is indicated for all other Reporting triggers. | X | X | X | +| Reporting trigger | Identifies the trigger for the usage report. | Applicable values are:
Detection of 1st DL packet on bearer (only for SGW);
Start/stop of traffic detection with/without application instance identifier and deduced SDF filter reporting (only for PGW and TDF);
Deletion of last PDR for a URR;
Periodic measurement threshold reached;
Volume/Time/Event measurement threshold reached;
Immediate report requested;
Measurement of incoming UL traffic (only for PGW);
Measurement of discarded DL traffic (only for SGW). | X | X | X | +| Start time | Provides the timestamp, in terms of absolute time, when the collection of the information provided within Usage-Information is started. | Not sent when Reporting trigger is Start/stop of traffic detection | X | X | X | +| End time | Provides the timestamp, in terms of absolute time, when the information provided within Usage-Information is generated. | Not sent when Reporting trigger is Start/stop of traffic detection | X | X | X | +| Measurement information | Defines the measured volume/time/events for this URR. | Contains DSCP of received packet when Reporting trigger is Detection of 1 st DL packet on bearer (as described in TS 23.401 [2])
Contains application instance identifier and deduced SDF filter when Reporting trigger is Start/stop of traffic detection with application instance identifier and deduced SDF filter reporting (including deduced UE IP address for TDF in unsolicited mode)
Not sent when Reporting trigger is Start/stop of traffic detection without application instance identifier and deduced SDF filter reporting | X | X | X | + +## 7.8 Functional description + +### 7.8.1 General + +This clause describes how the CP function provides information over Sx to realize forwarding, reporting etc on different aggregation levels. + +### 7.8.2 PDN connection and TDF session level context + +The PDN connection or TDF session level context is realized over Sx by generating a Usage Reporting Rule and a QoS Enforcement Rule. + +To apply PDN Connection or TDF session level reporting and MBR enforcement, the CP function provides over Sx: + +- A URR that describes the reporting requirement for the PDN Connection or TDF session. +- A QER that describes the QoS enforcement actions that apply, i.e. a QER with APN-AMBR value (in case of PGW) or a QER with TDF session MBR (in case of TDF). + +For session level reporting, the CP function includes references to the URR (i.e. URR Rule ID) in each Packet Detection Rule activated for the PDN Connection or TDF session. In case of PDN Connection or TDF session level usage monitoring where some SDF(s) are excluded, the CP function only includes a reference to the URR in those Packet Detection Rules that shall be included in the report. + +For APN-AMBR policing, the CP function includes references (Rule ID) to the QER containing the APN-AMBR value in each Packet Detection Rule for non GBR traffic activated for the PDN Connection. The CP function shall apply the same QER for all Packet Detection Rules for non GBR traffic associated with any of the active PDN Connections of the same APN. + +For TDF session MBR policing, the CP function includes references (Rule ID) to the QER containing the TDF session MBR value in each Packet Detection Rule activated for the TDF session. + +### 7.8.3 Bearer related context + +The bearer context is realized over Sx by generating one or two Forwarding Action Rules, a Usage Reporting Rule and a QoS Enforcement Rule that correspond to the bearer. In particular, the CP function may provide to the UP function for each active bearer: + +- A Usage Reporting Rule that describes the reporting requirement for the bearer, including reporting events, measurement type etc for the bearer reports. +- A QoS Enforcement Rule that describe the QoS enforcement actions that apply to the bearer, including the bearer MBR. +- Forwarding Action Rules describe the forwarding behaviour for the bearer. One Forwarding Action Rule is required for the downlink direction (in case of PGW or SGW) and one for the uplink direction (in case of SGW). + +NOTE: The CP function maintains the association between the EPS Bearer ID and the rules on Sx corresponding to bearer level enforcement and reports. There is no need to provide a Bearer ID to the UP function. + +The CP function associates, based on the bearer binding decisions, every Packet Detection Rule that is activated for a bearer with the URR, QER and FARs applicable for the this bearer by including references (Rule IDs) in the PDR: + +- For bearer level reporting, the CP function includes a reference (Rule ID) to the URR for the bearer. +- For bearer level policing, the CP function includes a reference (Rule ID) to the QER for the bearer. +- For forwarding of packets over a bearer (GTP-U encapsulation), the CP function includes a reference (Rule ID) to the FAR the bearer. This is done per direction (UL and DL). + +### 7.8.4 Measurement key related context + +The CP function provides a Usage Reporting Rule for each usage report that needs to be provided by the UP function. The CP function maintains a mapping between the Charging Key and/or Monitoring Key applicable for a SDF and the Measurement Key of the URR provided over Sx. For example, the CP function may provide one URR for each Charging Key and one URR for each Monitoring Key or may decide to provide a single URR for a Charging Key and a Monitoring Key in case there is complete overlap in the measurement requirements. Other mappings are also possible as determined by the CP function and is not limited by the standard as long as the reporting requirements from the CP function towards the OFCS/OCS and PCRF are fulfilled. + +To associate traffic covered by a Packet Detection Rule with one or more measurement keys on Sx, the CP function includes in the Packet Detection Rule a reference to each URR (Rule ID) that is applicable for the traffic covered by the PDR. + +## 7.9 Parameters for Sx management + +### 7.9.1 Parameters for PFD management + +The PGW-C/TDF-C can manage PFD sets in the applicable PGW-U/TDF-U independent of the Sx session. The management (provision or remove) of multiple PFD sets belonging to different Application IDs can be done with the same PFD management request message. + +**Table 7.9-1: Attributes within PFD management request message** + +| Attribute | Description | Comment | Applicability | | | +|----------------|------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|--------|-----| +| | | | SGW | PDN GW | TDF | +| PFD(s) | Extension to the application detection filter | The provisioning of PFD(s) for an Application ID results in the removal of all PFD(s) stored in the PGW-U/TDF-U for this Application ID and the usage of all newly provided PFD(s) for this Application ID | | X | X | +| Application ID | Application identifier which the PFD(s) is associated with | The provisioning of an Application ID without PFD(s) results in the removal of all stored PFD(s) corresponding to this Application ID | | X | X | + +# Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------|---------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2016-09 | SP-73 | SP-160665 | - | - | - | MCC Editorial update for presentation to TSG SA#73 for information and approval | 1.0.0 | | +| 2016-09 | SP-73 | - | - | - | - | MCC Editorial update for publication after TSG SA#73 approval | 14.0.0 | | +| 2016-12 | SP-74 | SP-160815 | 0002 | 2 | F | Corrections to User Plane selection function | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0003 | 5 | F | Corrections to buffering in the user plane | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0004 | 8 | F | Sx parameter corrections | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0005 | 4 | B | SDCI support | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0006 | 3 | F | Update to PCC/ADC related functions | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0007 | 2 | F | Update to UP Selection Section | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0008 | 2 | F | Text updates for TS 23.401 call flows | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0009 | 2 | F | Text updates for TS 23.402 call flows | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0010 | 2 | B | Buffering and F-TEIDu Allocation | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0012 | 3 | F | Support of PGW Pause of Charging | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0013 | 3 | F | Sx Session Level Reporting Procedure update | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0014 | 3 | F | TDF-U selection in case of unsolicited reporting | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0017 | 4 | F | Corrections of Sx parameters | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0019 | - | F | Parameter alignment and corrections for traffic detection clause | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0020 | 2 | F | Parameter alignment and corrections for forwarding section | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0021 | 2 | F | Alignment of function split clause | 14.1.0 | | +| 2016-12 | SP-74 | SP-160815 | 0022 | 3 | F | Clarification on the SGW-C partitions for a given UE | 14.1.0 | | +| 2017-03 | SP-75 | SP-170046 | 0026 | 2 | F | Correction to enforcement of dynamic PCC/ADC rule | 14.2.0 | | +| 2017-03 | SP-75 | SP-170046 | 0027 | 2 | F | Corrections to Sx parameters | 14.2.0 | | +| 2017-03 | SP-75 | SP-170046 | 0028 | 4 | F | Session management procedure for TDF in unsolicited mode | 14.2.0 | | +| 2017-03 | SP-75 | SP-170052 | 0029 | 1 | C | TS 23.214 support for transport level packet marking | 14.2.0 | | +| 2017-03 | SP-75 | SP-170046 | 0032 | 1 | F | Updates Procedures in TS 23.060. | 14.2.0 | | +| 2017-06 | SP-76 | SP-170366 | 0033 | 1 | F | Clean up and stage 3 alignment | 14.3.0 | | +| 2017-06 | SP-76 | SP-170366 | 0034 | 2 | F | Corrections and clean up for 23.401 related message flows | 14.3.0 | | +| 2017-06 | SP-76 | SP-170366 | 0035 | 1 | F | Addition of Sx node level procedures | 14.3.0 | | +| 2017-06 | SP-76 | SP-170366 | 0036 | - | F | Clarification on pre-defined PCC rules | 14.3.0 | | +| 2017-06 | SP-76 | SP-170366 | 0038 | - | F | Corrections and clean up for 23.203 related message flows | 14.3.0 | | +| 2017-06 | SP-76 | SP-170366 | 0039 | 1 | F | Corrections and clean up for 23.060 related message flows | 14.3.0 | | +| 2017-06 | SP-76 | SP-170366 | 0040 | - | F | Corrections and clean up for 23.402 related message flows | 14.3.0 | | +| 2017-09 | SP-77 | SP-170717 | 0041 | 2 | F | Sx PDN Instance | 14.4.0 | | +| 2017-09 | SP-77 | SP-170717 | 0042 | 2 | F | Update on activation of predefined PCC/ADC rules | 14.4.0 | | +| 2017-09 | SP-77 | SP-170717 | 0043 | - | F | Description on Sx-u tunnel | 14.4.0 | | +| 2017-09 | SP-77 | SP-170717 | 0044 | 1 | F | Corrections on PFD management | 14.4.0 | | +| 2017-09 | SP-77 | SP-170717 | 0045 | - | F | Correlation of Sx Session and UE Context | 14.4.0 | | +| 2017-09 | SP-77 | SP-170717 | 0046 | 2 | F | Update of the Procedures Specified in TS 23.401. | 14.4.0 | | +| 2017-09 | SP-77 | SP-170717 | 0048 | 3 | F | Clarification of Procedures Specified in TS 23.060. | 14.4.0 | | +| 2017-09 | SP-77 | SP-170728 | 0047 | 2 | B | Enable SGW-C & PGW-C selection of UPF to take UE's NR capabilities into account | 15.0.0 | | +| 2017-12 | SP-78 | SP-170913 | 0050 | 1 | A | Interface between MME and SGW-U for IoT data transmission | 15.1.0 | | +| 2017-12 | SP-78 | SP-170913 | 0052 | 2 | A | Removal of PMIP-based procedures specified | 15.1.0 | | +| 2017-12 | SP-78 | SP-170920 | 0055 | 1 | F | Correcting the condition for selection of SGW-U for NR as secondary RAT | 15.1.0 | | +| 2017-12 | SP-78 | SP-170940 | 0057 | 2 | A | Update of the Procedures Specified in TS 23.060. | 15.1.0 | | +| 2018-03 | SP-79 | SP-180086 | 0060 | 1 | A | Update of the Procedures Specified in TS 23.060. | 15.2.0 | | +| 2018-03 | SP-79 | SP-180086 | 0062 | - | A | Update to Procedures Specified in TS 23.401 | 15.2.0 | | +| 2018-03 | SP-79 | SP-180086 | 0064 | 1 | A | Correction of SDF Filter Description in PDR Table | 15.2.0 | | +| 2018-06 | SP-80 | SP-180472 | 0066 | 1 | A | Update of Sx parameter tables | 15.3.0 | | +| 2018-09 | SP-81 | SP-180711 | 0068 | 2 | A | Application detection report when the PFDs are removed | 15.4.0 | | +| 2018-12 | SP-82 | SP-181081 | 0070 | 1 | A | Addition of reference to SA WG5 OAM specification | 15.5.0 | | +| 2019-06 | SP-84 | SP-190406 | 0071 | 1 | F | Corrections for the activation of usage reporting in the UP function | 16.0.0 | | +| 2019-06 | SP-84 | SP-190406 | 0072 | - | F | Clarifications for 23.401 procedures | 16.0.0 | | +| 2020-07 | SP-88E | SP-200429 | 0073 | - | F | Clarification on the F-TEIDu allocation and release | 16.1.0 | | +| 2020-07 | SP-88E | SP-200429 | 0074 | 1 | F | Clarification of TEID allocation by gateway user plane | 16.1.0 | | +| 2020-09 | SP-89E | SP-200686 | 0075 | 1 | F | Corrections to CUPS Session/Bearer deactivation procedures | 16.2.0 | | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23240/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23240/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..634ae8bbab91d7fa9c3f6af1e1b7bccfe29f4048 --- /dev/null +++ b/marked/Rel-16/23_series/23240/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ee68ad2083da7224a394a51adeda81f4007716d44a786a62cd77a6d408265cb +size 36401 diff --git a/marked/Rel-16/23_series/23240/6470d350326789d5306eabcb76533951_img.jpg b/marked/Rel-16/23_series/23240/6470d350326789d5306eabcb76533951_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a84177a7119c385d6197cc039784ecf4e8ab4185 --- /dev/null +++ b/marked/Rel-16/23_series/23240/6470d350326789d5306eabcb76533951_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:280a336fdf6f2747b2be42d42f55af571df3d351c253702d35b52e20cddad326 +size 90621 diff --git a/marked/Rel-16/23_series/23240/68d8089266ace7197304b43dcaf5d08e_img.jpg b/marked/Rel-16/23_series/23240/68d8089266ace7197304b43dcaf5d08e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a08ef081d4f73e265250bb75af5cb59ea2ebe391 --- /dev/null +++ b/marked/Rel-16/23_series/23240/68d8089266ace7197304b43dcaf5d08e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f65bcd1e42fcdf199f00ca28ebd3cdc716ec6b7035ffa87316e46199ad0e5916 +size 43264 diff --git a/marked/Rel-16/23_series/23240/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23240/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03dc3fab0aa78135ef0847d614bf0fd01b7c247b --- /dev/null +++ b/marked/Rel-16/23_series/23240/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e82e23c52f465b31baa8444ca3d3898046580932ddfad889ad960ba3bf030c2a +size 113261 diff --git a/marked/Rel-16/23_series/23240/94fd137860c16c8dfd75512f10161fe8_img.jpg b/marked/Rel-16/23_series/23240/94fd137860c16c8dfd75512f10161fe8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60295db54ab60085deee9ec6216dfa3dfc590344 --- /dev/null +++ b/marked/Rel-16/23_series/23240/94fd137860c16c8dfd75512f10161fe8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:66ef5e140b79d1976af57829b27d6904cff90a0e4f3e51d8ff15b71e0bddb456 +size 28832 diff --git a/marked/Rel-16/23_series/23240/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23240/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e7d0db17231d62c9ef18c4d0484414237ae2a92a --- /dev/null +++ b/marked/Rel-16/23_series/23240/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95243991e340f947aa5659646735bd7836ff1cc266d72e3244297d380f62db61 +size 101735 diff --git a/marked/Rel-16/23_series/23240/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg b/marked/Rel-16/23_series/23240/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0e9ccf2c700f77db0565fd84e9777159ec7cb85 --- /dev/null +++ b/marked/Rel-16/23_series/23240/b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:204b505bd99fd00c9eb3acc4342fe7504f2983b30da72deb18ad6d282add42dc +size 32701 diff --git a/marked/Rel-16/23_series/23240/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/marked/Rel-16/23_series/23240/c2fc2621e8206d24427b56bcb2398fc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..463b859f4e444e6a8df13f83e4c36c4f7812014f --- /dev/null +++ b/marked/Rel-16/23_series/23240/c2fc2621e8206d24427b56bcb2398fc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b8fd5ab5cb77c1adc14057879f14f8e0547cd9c7e50a116d7071ddd9f4ad241b +size 34532 diff --git a/marked/Rel-16/23_series/23240/dbe553cf16dd14073b89a8263a428664_img.jpg b/marked/Rel-16/23_series/23240/dbe553cf16dd14073b89a8263a428664_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1e2dfd654d314115918331ad70831a7cfa71d346 --- /dev/null +++ b/marked/Rel-16/23_series/23240/dbe553cf16dd14073b89a8263a428664_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:95f75707d8e4f3e749f3805273338a081b799a426028043058eaaa1b57e207ff +size 62152 diff --git a/marked/Rel-16/23_series/23240/raw.md b/marked/Rel-16/23_series/23240/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..a17a47a125c7e0b99ef4a5b9d1eaf84839cf86be --- /dev/null +++ b/marked/Rel-16/23_series/23240/raw.md @@ -0,0 +1,1121 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions, symbols and abbreviations..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Symbols..... | 7 | +| 3.3 Abbreviations ..... | 7 | +| 4 Reference Architecture ..... | 7 | +| 4.1 GUP Functionalities ..... | 7 | +| 4.1.1 Harmonized access interface ..... | 7 | +| 4.1.2 Single point of access ..... | 7 | +| 4.1.3 Authentication of profile access ..... | 7 | +| 4.1.4 Authorization of profile access..... | 7 | +| 4.1.5 Privacy control..... | 8 | +| 4.1.6 Synchronization of data storage ..... | 8 | +| 4.1.7 Access of profile from visited network ..... | 8 | +| 4.1.8 Location of Profile Components ..... | 8 | +| 4.1.9 Charging for profile access..... | 8 | +| 4.2 GUP functional entities ..... | 9 | +| 4.2.1 GUP Server..... | 10 | +| 4.2.1.1 Single point of access ..... | 11 | +| 4.2.1.2 Location of profile components ..... | 12 | +| 4.2.1.3 Authentication of profile request..... | 12 | +| 4.2.1.4 Authorization of profile request..... | 12 | +| 4.2.1.5 Synchronization of profile components ..... | 12 | +| 4.2.1.6 Additional functionality..... | 12 | +| 4.2.2 Repository Access Function (RAF)..... | 12 | +| 4.2.3 GUP Data Repository ..... | 13 | +| 4.2.4 Reference Points ..... | 13 | +| 4.2.5 Applications..... | 13 | +| 4.2.6 Message flow of using GUP..... | 13 | +| 4.3 Rg reference point procedures..... | 15 | +| 4.3.1 Create procedure..... | 16 | +| 4.3.2 Delete procedure..... | 17 | +| 4.3.2a List procedure ..... | 17 | +| 4.3.3 Modify procedure ..... | 18 | +| 4.3.4 Query procedure ..... | 19 | +| 4.3.5 Subscribe procedure ..... | 20 | +| 4.3.6 Unsubscribe procedure ..... | 21 | +| 4.3.7 Notify procedure..... | 21 | +| 4.3.8 Common information definitions ..... | 22 | +| 4.3.8.1 Requestor data..... | 22 | +| 4.3.8.2 Redirection data ..... | 22 | +| 4.3.9 Error handling and common error types..... | 22 | +| 4.4 Rp reference point procedures..... | 23 | +| 4.4.1 Create Component procedure ..... | 23 | +| 4.4.2 Delete Component procedure ..... | 24 | +| 4.4.2a List Data procedure ..... | 24 | +| 4.4.3 Modify Data procedure..... | 25 | +| 4.4.4 Read Data procedure ..... | 26 | +| 4.4.5 Subscribe To Data procedure ..... | 26 | +| 4.4.6 Unsubscribe To Data procedure ..... | 27 | +| 4.4.7 Notify Data procedure ..... | 28 | +| 4.4.8 Define Data procedure..... | 28 | + +4.4.9 Common information definitions ..... 28 +4.4.9.1 Requestor data..... 28 +4.4.10 Error handling and common error types..... 29 +5 GUP information model..... 29 +**Annex A (informative): Examples of 3GPP Generic User Profile usage ..... 32** +**Annex B (informative): 3GPP Generic User Profile candidates..... 33** +Annex C (informative): Change history..... 34 + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- Introduction + +The fact of having several domains within the 3GPP mobile system (e.g. Circuit-Switched, Packet-Switched, IP Multimedia Subsystem) and access technologies (e.g. GERAN, UTRAN and WLAN) introduces a wide distribution of data associated with the user. Further, the new functions both in terminals and networks mean that the data related to users, services and user equipment will be increased greatly. This causes difficulties for users, subscribers, network operators and value added service providers to create, access and manage the user-related data located in different entities. + +The objective of specifying the 3GPP Generic User Profile is to provide a conceptual description to enable harmonized usage of the user-related information located in different entities. Technically the 3GPP Generic User Profile provides an architecture, data description and interface with mechanisms to handle the data. + +# --- 1 Scope + +The present document defines the stage 2 architecture description to the 3GPP Generic User Profile (GUP), which includes the elements necessary to realise the stage 1 requirements in TS 22.240 [1]. + +The present document includes the GUP reference architecture with descriptions of functional entities, and their interfaces and procedures, as well as the high-level information model for the GUP data. + +# --- 2 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 22.240: "Stage 1 Service Requirement for the 3GPP Generic User Profile (GUP)". +- [2] Liberty Discovery Service Specification, . +- [3] Liberty ID-WSF SOAP Binding Specification, . +- [4] Liberty ID-WSF Data Services Template, . +- [5] Liberty ID-WSF Security and Privacy Overview, . +- [6] Liberty ID-WSF Security Mechanisms, . +- [7] 3GPP TS 23.141: "Presence Service; Architecture and functional description". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document the following definitions apply: + +**3GPP Generic User Profile (GUP):** The 3GPP Generic User Profile is the collection of user related data which affects the way in which an individual user experiences services and which may be accessed in a standardized manner as described in this specification. + +**GUP Component:** A GUP component is logically an individual part of the Generic User Profile. + +**Data Element:** the indivisible unit of Generic User Profile information. + +**Data Element Group:** A pre-defined set of Data Elements and/or other Data Element Groups closely related to each other. One or more Data Element Groups can constitute the GUP Component. + +**Data Description Method:** A method describing how to define the data contained in the Generic User Profile. + +## 3.2 Symbols + +For the purposes of the present document the following symbols apply: + +| | | +|----|-----------------------------------------------------------------------------------------------------------------------| +| Rg | Reference Point between Applications and the GUP Server. | +| Rp | Reference Point between the GUP Server and GUP Data Repositories, and between Applications and GUP Data Repositories. | + +## 3.3 Abbreviations + +For the purposes of the present document the following abbreviations apply: + +| | | +|-------|----------------------------| +| FFS | For Further Study | +| GUP | 3GPP Generic User Profile | +| HPLMN | Home PLMN | +| LCS | Location services | +| OSA | Open Service Access | +| PLMN | Public Land Mobile Network | +| RAF | Repository Access Function | +| UE | User Equipment | +| XML | eXtensible Markup Language | + +# --- 4 Reference Architecture + +## 4.1 GUP Functionalities + +### 4.1.1 Harmonized access interface + +The GUP harmonized access interface is the interface which can be used by the GUP suppliers and GUP consumers to access, manage and transfer the profile data. This application layer interface is independent of the profile structure. + +### 4.1.2 Single point of access + +There exists for each Profile a single point of access, which knows the location of the various components of the Profile. A discovery service, e.g. Liberty Discovery Service Specification [2] may be used to get the contact reference information for this access point if not known by other means. + +### 4.1.3 Authentication of profile access + +A GUP functionality exists that is responsible to authenticate applications. Authentication is a vital function to be passed before any kind of access to GUP data is granted. GUP shall adopt generic mechanisms such as used for the OSA framework approach. More specifically GUP shall use authentication mechanisms from Liberty Alliance Project as specified in Liberty ID-WSF Security and Privacy Overview [5], Liberty Discovery Service [2] and Liberty ID-WSF Security Mechanisms [6]. + +### 4.1.4 Authorization of profile access + +A GUP functionality exists that is responsible to authorise applications to access GUP data based on User specific or common privacy rules. All attempts to access the GUP data are to be authorized according to the defined policies which shall include the requestor information, the requested data, the target subscriber and the performed operation, or some of those. + +GUP shall use authorization mechanisms from Liberty Alliance Project as specified in Liberty ID-WSF Security and Privacy Overview [5] and Liberty ID-WSF Security Mechanisms [6]. + +The GUP data structures need to satisfy the requirement to provide the authorization information on the different levels: profile, component or data element. In addition to the generic authorization data, additional service specific data may be defined (e.g. for LCS). The same applies for the authorization decision logic. The execution of the authorization logic leads to a decision whether a requestor is allowed to make the request at all, and additionally to which part of data the requestor has the appropriate access rights with regard to the nature of the request. + +GUP provides mechanisms for the different GUP entities for managing the authorization data. + +Both HPLMN based applications and non-HPLMN based applications are expected to send requests to the GUP Server. The GUP server shall have functionality to apply different authorization criteria, policy control and load control to HPLMN and non-HPLMN applications. Policy control and load control are out of the scope of the present document. + +### 4.1.5 Privacy control + +The tight connection of authentication, authorization and subscriber specific privacy requirements results in privacy control. Privacy control implies a centralized management for access rights including the subscriber's privacy requirements. + +GUP shall use privacy control mechanisms and other privacy related features from Liberty Alliance Project as specified in Liberty ID-WSF Security and Privacy Overview [5] and Liberty ID-WSF Security Mechanisms [6]. + +### 4.1.6 Synchronization of data storage + +The GUP data repository holds the master copy of the GUP component data. Applications or GUP server may copy (i.e. read) the component data or request synchronization. The present document defines how the data is requested and sent. What is thereafter done with the data by the application or GUP server is beyond the scope of the present document. + +Synchronization means that the changes to the master copy of the data are propagated to the entities that request synchronization. The synchronization request specifies which data are monitored for changes. It is also possible to request that all changes are reported. + +Synchronization may cause heavy processing load to the involved entities, thus some policies are required in the implementations but those are not specified for the time being. However the GUP interfaces should carry sufficient data for enabling the load control mechanisms to work. + +The entity under a heavy processing load has the responsibility to handle the error cases and conditions and to reach the synchronization as fast as possible. All the unresolved errors or load balancing actions that affect synchronization shall be reported. + +### 4.1.7 Access of profile from visited network + +Access to GUP from a visited network shall follow the single point of access principle. + +### 4.1.8 Location of Profile Components + +A GUP functionality exists that keeps information where GUP data are located. + +### 4.1.9 Charging for profile access + +The GUP Server shall be capable of providing charging information, e.g. to enable transaction/event based charging. + +Some GUP Data Repositories may provide charging information, while other GUP Data Repositories do not provide charging information. + +Mechanisms are needed to permit the GUP Server to know which GUP Data Repositories are (and are not) producing their own charging information. When the GUP Data Repository is capable of producing charging information, mechanisms are needed for the correlation of the charging information produced by GUP Server and GUP Data Repository. + +The charging information may also be used for other event logging, customer care, privacy auditing, etc. functions. + +## 4.2 GUP functional entities + +The GUP reference architecture as shown in Figure 4.1 consists of: + +- GUP Server; +- Repository Access Function (RAF); +- GUP Data Repositories; +- Rg and Rp reference points; +- Applications. + +![Figure 4.1: GUP reference architecture diagram](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg) + +The diagram illustrates the GUP reference architecture. At the top, a stack of three rectangles labeled 'Applications' is connected via a double-headed arrow labeled 'Rg' to a box labeled 'GUP Server'. Below the 'GUP Server' is a box labeled 'RAF'. A vertical line labeled 'Rp' connects the 'GUP Server' to the 'RAF' box. Below the 'RAF' box is another box labeled 'GUP Data Repository'. A vertical line connects the 'RAF' box to the 'GUP Data Repository' box. There are three vertical ellipses between the 'RAF' and 'GUP Data Repository' boxes, indicating multiple instances of each. A long vertical arrow points from the 'GUP Data Repository' box back up to the 'Applications' box at the top. + +Figure 4.1: GUP reference architecture diagram + +Figure 4.1: GUP reference architecture + +An example of mapping the GUP reference architecture to current infrastructure environment is shown in Figure 4.2. + +![Figure 4.2: An example of mapping the GUP reference architecture to current infrastructure environment diagram](dbe553cf16dd14073b89a8263a428664_img.jpg) + +The diagram shows the mapping of the GUP reference architecture to a current infrastructure environment. At the top, three boxes are shown: 'Application in UE', 'Application in HPLMN (e.g. SMSC, etc.)', and 'Application in 3rd party SP'. The 'Application in UE' box is connected to a 'GUP Server' box via a line labeled 'Rg'. The 'Application in HPLMN' and 'Application in 3rd party SP' boxes are connected to the 'GUP Server' box via a dashed line. A legend indicates that the dashed line represents communication that can take place directly between the 'Application in HPLMN' and 'GUP Data Repositories'. Below the 'GUP Server' box is a line labeled 'Rp'. Below this line are three boxes labeled 'RAF'. The first 'RAF' box contains 'HPLMN Nodes (e.g. HSS/HLR/VLR, PPR, etc.)'. The second 'RAF' box contains 'Application Servers (e.g. IMS AppServer, etc.)'. The third 'RAF' box contains 'Management Servers (e.g. CRM, etc.)'. Vertical lines connect the 'GUP Server' box to each of the three 'RAF' boxes. + +Figure 4.2: An example of mapping the GUP reference architecture to current infrastructure environment diagram + +Figure 4.2: An example of mapping the GUP reference architecture to current infrastructure environment + +### 4.2.1 GUP Server + +The GUP Server is a functional entity providing a single point of access to the Generic User Profile data of a particular subscriber. The reference architecture does not specify or limit the physical location of the GUP Server enabling flexibility in the implementations. However, the GUP Server shall be located in the home operator network of the targeted subscriber. + +The GUP Server includes the following main functionalities: + +- Single point of access for reading and managing generic user profile data of a particular subscriber. + +- Location of Profile Components. +- Authentication of profile requests. +- Authorization of profile requests. +- Synchronization of Profile Components. + +The GUP Server may support two modes of operation: + +- **Proxy mode** (see figure 4.3). The Application requests user related data located in the GUP Data Repositories from the GUP Server. After taking care of needed actions specified for the GUP Server (and depending on the type of the request) the GUP Server makes requests to the corresponding GUP Data Repositories and receives responses from them. Finally the Application gets a response to the original request from the GUP Server. Depending on the type of the request also possible subsequent responses are delivered through the GUP Server. +- **Redirect mode** (see figure 4.4). The Application requests user related data located in the GUP Data Repositories from the GUP Server. After taking care of needed actions specified for the GUP Server (and depending on the type of the request) the GUP Server returns to the Application the information (e.g. address of GUP Data Repository(s)) to allow the Application to request the information from the GUP Data Repositories. The Application then directly requests the information from the GUP Data Repositories. + +The Proxy mode is the default mode of operation. Redirect capability and preference for the applied mode may be indicated by the application with the Requestor data parameter when accessing the GUP Server. The GUP Server decides which mode is selected for the different requests. In addition to the Requestor data parameter, the decision is based on the capabilities of the GUP Server and the related Repository Access Functions (RAF) as well as on the service configuration and policy data in the GUP Server related to the particular application. These service configuration and policy data are out of the scope of GUP standardisation. If the Redirect mode is not supported by the GUP Server the response is always sent according to the Proxy mode. + +![Diagram illustrating the GUP Server acting as a Proxy Server. A Requestor sends a request (a) to the GUP Server, which then sends a locate (b) to the GUP Data Repository. The GUP Data Repository returns a request (c) and response (d) to the GUP Server, which finally sends a response (e) back to the Requestor.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) + +``` +graph TD; Requestor[Requestor] -- "a) request" --> GUPServer[GUP Server]; GUPServer -- "b) locate" --> GUPDataRepository1[GUP Data Repository]; GUPServer -- "b) locate" --> GUPDataRepository2[GUP Data Repository]; GUPDataRepository1 -- "c) request" --> GUPServer; GUPDataRepository1 -- "d) response" --> GUPServer; GUPDataRepository2 -- "c) request" --> GUPServer; GUPDataRepository2 -- "d) response" --> GUPServer; GUPServer -- "e) response" --> Requestor; +``` + +Diagram illustrating the GUP Server acting as a Proxy Server. A Requestor sends a request (a) to the GUP Server, which then sends a locate (b) to the GUP Data Repository. The GUP Data Repository returns a request (c) and response (d) to the GUP Server, which finally sends a response (e) back to the Requestor. + +Figure 4.3: GUP Server acting as a Proxy Server + +![Sequence diagram showing the GUP Server acting as a Redirect Server. A Requestor sends a 'request' (a) to a GUP Server, which responds with a 'locate' (b) and a 'response' (c). The Requestor then sends a 'request' (d) to two GUP Data Repositories, which respond with 'response' (e) to the Requestor.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` +sequenceDiagram + participant Requestor + participant GUP Server + Note right of GUP Server: b) locate + Requestor->>GUP Server: a) request + GUP Server-->>Requestor: c) response + Note right of Requestor: d) request +e) response + Requestor->>GUP Data Repository 1: d) request + Requestor->>GUP Data Repository 2: d) request + GUP Data Repository 1-->>Requestor: e) response + GUP Data Repository 2-->>Requestor: e) response +``` + +Sequence diagram showing the GUP Server acting as a Redirect Server. A Requestor sends a 'request' (a) to a GUP Server, which responds with a 'locate' (b) and a 'response' (c). The Requestor then sends a 'request' (d) to two GUP Data Repositories, which respond with 'response' (e) to the Requestor. + +**Figure 4.4: GUP Server acting as a Redirect Server.** + +#### 4.2.1.1 Single point of access + +The GUP Server shall accept data management related requests from the applications via the Rg reference point, and either convey the corresponding GUP component specific requests to GUP Data Repositories via Rp reference point or redirect the Application to convey the requests to the GUP Data Repositories. Note that one data request from an application to the GUP Server can cause sending of several GUP Data Repository requests by the GUP Server or Application. Also mapping to proprietary interfaces instead of Rp is possible in implementations. + +In Proxy mode the GUP Server shall receive the results of the requests from GUP Data Repositories and deliver the results back to the requestor (Application). In case of responses from several GUP Data Repositories the GUP Server shall combine separate XML documents received from the repositories and deliver the composed information to the requestor. In redirect mode the Application will receive the results of the requests from the GUP Data Repositories. + +#### 4.2.1.2 Location of profile components + +The GUP Server stores information about the GUP Components and the locations of data repositories of GUP Components related to each subscriber. Thus e.g. the separate GUP components composing the whole User Profile of a certain subscriber can be located and identified. The application shall be able to affect where a new GUP Component is created by the GUP Server. It is beyond this specification how the GUP server gets the component locations in the cases when it is not involved in the creation of those components. + +#### 4.2.1.3 Authentication of profile request + +The GUP Server shall make sure that the application requesting user profile data is properly authenticated. The authentication is based on the identification of the requesting application and/or the identification of the possible subscriber requesting the user profile data. The GUP Server may rely on the authentication made by other trusted entities. + +#### 4.2.1.4 Authorization of profile request + +The GUP Server shall take care of the authorization of the access to the user profile data. The authorization itself may be handled by a separate entity in the network, or alternatively by the RAF or GUP Data Repository. The authorization shall be based on the requestor information, the requested data, the target subscriber and the performed operation, or some of them. The authorization rules of the requested data shall be defined at least in the GUP Component level in GUP Server. (Note that the authorization may be based on also on finer granularity of the data content.) It shall be possible to manage the authorization data via the Rg and Rp reference points. + +#### 4.2.1.5 Synchronization of profile components + +In proxy mode, the GUP Server shall convey the data synchronization requests from the applications to the RAFs in the same way as the other profile requests. Also the related change notifications from the RAFs are passed on to the requesting application. This requires that some kind of book keeping about the synchronization requests implemented. In redirect mode the GUP server shall redirect the Application to the RAFs in the same way as the other profile requests. + +The GUP Server may store a copy of the actual data from the GUP Data Repository, but it is up to the local policy of the GUP Server. + +#### 4.2.1.6 Additional functionality + +The GUP Server may take part in the charging of the data management operations concerning the profile. + +The GUP Server may take part in the rate and/or size limiting of the data operations towards the profile. + +The GUP Server may utilise a discovery service to register its contact reference information. + +### 4.2.2 Repository Access Function (RAF) + +The Repository Access Function (RAF) realizes the harmonized access interface. It hides the implementation details of the data repositories from the GUP infrastructure. The RAF performs protocol and data transformation where needed. + +The protocol between the RAF and the GUP data repository is out of the standardization scope. It is recommended that the protocol used should support GUP requirements. + +The RAF may take part in the authorization of access to such GUP information, which are under the control of the RAF. In addition, the authorization data may be managed via the Rp reference point. + +### 4.2.3 GUP Data Repository + +Each GUP Data Repository stores the primary master copy of one or several profile components. The RAF provides for the standardized access to the GUP Data Repository. The storage formats or the interface between the RAF and GUP Data Repository are not specified by GUP. It is presumed that the RAF and the GUP Data Repository are usually co-located in the same network element. + +The GUP Data Repository may contain also the authorization data depending on the authorization model and architecture. + +### 4.2.4 Reference Points + +Reference Points in the GUP Reference Architecture: + +#### 1. Reference point Rg + +This reference point shall allow applications to create, read, modify and delete any user profile data using the harmonized access interface. The GUP Server locates the data repositories responsible of the storage of the requested profile component(s) and in case of proxy mode carries out the requested operation on the data. The reference point Rg shall support interworking to other mechanisms that support parts of the user profile outside the scope of 3GPP e.g. Liberty ID-WSF SOAP Binding Specification [3] and Liberty ID-WSF Data Services Template [4]. + +In the redirect mode, the GUP Server returns the locations of the GUP Data Repositories and the application can then send the requested operations via reference point Rp directly to the corresponding GUP Data Repositories. + +The reference point Rg carries user related data, and therefore shall be protected by security mechanisms. + +#### 2. Reference point Rp + +This reference point shall allow the GUP Server or applications, excluding external applications (e.g. located in a third party application or in the UE), to create, read, modify and delete user profile data using the harmonized access interface. Rp is an intra-operator reference point. External applications and third party GUP data repositories shall be connected to the GUP Server only using the Rg reference point. + +The reference point Rp carries user related data, and therefore shall be protected by security mechanisms. + +### 4.2.5 Applications + +The applications that may apply GUP reference points Rg and Rp may be targeted for different purposes e.g. for value added services or subscription management. Both operator's own applications and third party applications are covered. The latter ones shall apply Rg reference point. + +Additionally the applications may utilise a discovery service to discover the contact reference information if not found out by other means. A discovery service e.g., as specified in Liberty Discovery Service Specification [2], may also act as Trusted Authority providing essential security related information (e.g. preferences in terms of peer entity and message authentication mechanism to be used and authentication and/or authorization assertions). Different policies may be followed in the use of discovery service. It may be used by different applications in different ways: per each operation, occasionally or not at all. In general terms, third party applications belonging to external security domains shall use a discovery service as a normal step, but in operator's services it may not be needed at all. + +Applications have different authorization rights to the GUP data of different subscribers as agreed between the parties. + +### 4.2.6 Message flow of using GUP + +For an application requesting GUP data component(s) a message flow is described in the following: + +- The application requests a GUP component(s) via Single Point of Access (Rg) from the GUP server. The application will indicate if it can support the Redirect mode. +- The GUP server authenticates the application. Note that also separate authentication services may be applied. +- The GUP Server identifies the level of authorization the Application is allowed to access the GUP data. +- The GUP Server identifies the location of the GUP component(s). + +At this point the GUP Server may (see figure 4.5 below) + +- Access the GUP component(s) by means of the Harmonized Access Interface (Rp) or by other means outside the scope of GUP. +- Respond to the application with the result of the request, optionally combining results from different GUP data repositories. + +Or, depending on GUP data repositories choice and if the application has indicated that it can support the Redirect mode (see figure 4.6 below) + +- Respond to the application with reference(s) to the component(s) and additionally authorization credentials with limited lifetime. Note that authorization credentials from other sources are not excluded. +- The application uses the reference(s) and the authorization credentials to access GUP data repositories by means of the Rp reference point. + +Privacy rules may stay together with the data it applies to at the data repository where the data is stored. In this case this privacy rules shall apply. Optionally, the GUP Server may apply additional privacy rules. However the GUP Server must never "bypass" existing privacy rules. + +The following figures show the message flows for both cases as described. + +![Sequence diagram showing the message flow for an Application requesting GUP data components in Proxy mode. Lifelines: Application, GUP Server, RAF, GUP Data Repository. The process involves authentication, data element requests (A and B), and final component composition.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` +sequenceDiagram + participant Application + participant GUP Server + participant RAF + participant GUP Data Repository + + Note right of GUP Server: Rg + Note right of RAF: Rp + Note right of GUP Data Repository: vendor-specific interface + + Application->>GUP Server: GUP request + GUP Server->>GUP Server: Authenticate the application and check authorisation. + GUP Server->>GUP Server: Identify and localise data elements. + GUP Server->>RAF: Request GUP data element A + RAF->>GUP Data Repository: Request GUP data element A + GUP Data Repository->>RAF: Deliver GUP data element A + RAF->>GUP Server: Deliver GUP data element A + GUP Server->>RAF: Request GUP data element B + RAF->>GUP Data Repository: Request GUP data element B + GUP Data Repository->>RAF: Deliver GUP data element B + RAF->>GUP Server: Deliver GUP data element B + GUP Server->>GUP Server: Compose GUP component = data element A + data element B + GUP Server->>Application: Deliver GUP component +``` + +The sequence diagram illustrates the interaction for requesting GUP data components in Proxy mode. It begins with the Application sending a 'GUP request' to the GUP Server. The GUP Server performs internal steps: 'Authenticate the application and check authorisation.' and 'Identify and localise data elements.' It then sends a 'Request GUP data element A' to the RAF. The RAF forwards this as 'Request GUP data element A' to the GUP Data Repository, which responds with 'Deliver GUP data element A'. The RAF then delivers this to the GUP Server. The same process repeats for 'data element B'. Finally, the GUP Server performs 'Compose GUP component = data element A + data element B' and sends 'Deliver GUP component' back to the Application. Interface labels 'Rg', 'Rp', and 'vendor-specific interface' are shown at the bottom of their respective lifelines. + +Sequence diagram showing the message flow for an Application requesting GUP data components in Proxy mode. Lifelines: Application, GUP Server, RAF, GUP Data Repository. The process involves authentication, data element requests (A and B), and final component composition. + +Figure 4.5: An Example of Application requesting GUP data component(s) message flow (Proxy mode) + +![Sequence diagram showing the message flow for an Application requesting GUP data component(s) in Redirect mode. The diagram involves four lifelines: Application, GUP Server, RAF, and GUP Data Repository. The process starts with a GUP request from the Application to the GUP Server. The GUP Server authenticates and checks authorization, then identifies and localizes data elements. It delivers references and authorization credentials for data elements A and B to the Application. The Application then requests GUP data element A from the RAF. The RAF verifies authorization credentials, requests GUP data element A from the GUP Data Repository, receives it, and delivers it to the Application. Next, the Application requests GUP data element B from the RAF. The RAF verifies authorization credentials, requests GUP data element B from the GUP Data Repository, receives it, and delivers it to the Application. Reference points Rg, Rp, and vendor-specific interface are indicated at the bottom.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant Application + participant GUP Server + participant RAF + participant GUP Data Repository + + Note right of GUP Server: Authenticate the application and check authorisation. +Identify and localise data elements. + + Application->>GUP Server: GUP request + GUP Server-->>Application: Deliver references and authorisation credentials for data elements A and B + Application->>RAF: Request GUP data element A + Note right of RAF: Verify authorisation credentials + RAF->>GUP Data Repository: Request GUP data element A + GUP Data Repository-->>RAF: Deliver GUP data element A + RAF-->>Application: Deliver GUP data element A + Application->>RAF: Request GUP data element B + Note right of RAF: Verify authorisation credentials + RAF->>GUP Data Repository: Request GUP data element B + GUP Data Repository-->>RAF: Deliver GUP data element B + RAF-->>Application: Deliver GUP data element B + + Note left of Application: Rg + Note left of RAF: Rp + Note left of GUP Data Repository: vendor-specific interface + +``` + +Sequence diagram showing the message flow for an Application requesting GUP data component(s) in Redirect mode. The diagram involves four lifelines: Application, GUP Server, RAF, and GUP Data Repository. The process starts with a GUP request from the Application to the GUP Server. The GUP Server authenticates and checks authorization, then identifies and localizes data elements. It delivers references and authorization credentials for data elements A and B to the Application. The Application then requests GUP data element A from the RAF. The RAF verifies authorization credentials, requests GUP data element A from the GUP Data Repository, receives it, and delivers it to the Application. Next, the Application requests GUP data element B from the RAF. The RAF verifies authorization credentials, requests GUP data element B from the GUP Data Repository, receives it, and delivers it to the Application. Reference points Rg, Rp, and vendor-specific interface are indicated at the bottom. + +**Figure 4.6: An Application requesting GUP data component(s) message flow (Redirect mode)** + +## 4.3 Rg reference point procedures + +This clause defines the procedures applied in the Rg reference point between the applications and the GUP Server. This reference point supports also third party profile access. Rg can be used e.g. to create the whole user profile or some components in it, to read any piece of data in the profile or to modify those. There are means to authorise all requests and protect the user's privacy in all operations. Rg is applied to control the data stored in the different GUP components identified by a resource identity and the component type. The resource identity contains either a subscriber identity or a generic component identification, which is given to components that are not bound to a single subscriber. + +There are the following procedures: + +- Create +- Delete +- Modify +- List +- Query +- Subscribe +- Unsubscribe + +- Notify + +Instead of proxying the requests (or handling them by itself) the GUP Server may also apply the redirect mode of operation for applications that support redirect mode, which implies that the GUP Server responds to the request with the redirection information such as redirection address and authorisation assertions. Redirection can be made with Create, Delete, Modify, Query and Subscribe procedures. + +### 4.3.1 Create procedure + +Create procedure is used by the application to create a new user profile or new components to an existing profile. The procedure is always related to a single resource identity which is given in the request. Additionally the Create procedure shall carry the component types and the data to be created to each component. At least one component shall be provided. Creation of the first component implies profile creation. The component type identifies what data are concerned i.e. not just the data typing. It is presumed that the profile data structure is already known by the both parties. No new type of data can be defined by this procedure, only the data contents are provided. Furthermore the application shall provide the necessary data for authentication and authorization of this create function (e.g. credentials, assertions and identifications). + +The outcome of the procedure shall be provided in a separate response message. If the requestor data indicated that the application is able to receive redirect instructions, the GUP server may decide to return redirect instructions based on policies set by the operator in the GUP server. After this response the procedure is terminated without any other specified results or retained information in the GUP Server. + +**Table 4.1: Request data of Create procedure** + +| Parameter | Description | Use | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Resource Identity | Specifies the resource identity with its type (e.g. SIP URI public ID). | Mandatory | +| Component data | Specifies which components are addressed and provides the data for those. There may be several Component data elements corresponding to several created components. At least one element must be present. See the table below for the more detailed contents. | Mandatory | +| Requestor data | Specifies the data related to the requestor. These data may be used as input in the authentication and authorization process. E.g. end user and application identification, credentials or privacy policy information. | Optional | + +**Table 4.2: Contents of Component data parameter** + +| Parameter | Description | Use | +|----------------|--------------------------------------------------------------------------------------------------------------------|-----------| +| Component type | Specifies the type of the created component. The Component type identifies the applied component data definitions. | Mandatory | +| Data | Specifies the GUP component data according to the specified Component type. | Mandatory | + +**Table 4.3: Response data of Create procedure** + +| Parameter | Description | Use | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Redirection data | Specifies the redirection instructions and assertions. | Optional | +| Status | Indicates whether:
1. The procedure was carried out successfully,
2. The request was redirected, or
3. A failure was detected.
For the proxy mode 1 or 3 can be indicated. For the redirect mode 2 or 3 can be indicated. The possible failure is described in sufficient detail. | Mandatory (like the response itself) | + +### 4.3.2 Delete procedure + +Delete procedure is used by the application to remove a profile or selected GUP components from the repository. The attached resource identity and the component type are specified. If no component type is provided, the whole user + +profile identified by the resource identity will be deleted. The application shall provide the necessary data for authentication and authorization purposes (e.g. credentials, assertions and identifications). + +The outcome of the procedure shall be provided in a separate response message. If the requestor data indicated that the application is able to receive redirect instructions, the GUP server may decide to return redirect instructions based on policies set by the operator in the GUP server. After this response the procedure is terminated without any other specified results or retained information in the GUP Server. + +**Table 4.4: Request data of Delete procedure** + +| Parameter | Description | Use | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Resource identity | Specifies the resource identity with its type (e.g. SIP URI public ID). | Mandatory | +| Component types | Specifies the types of the components. | Optional | +| Requestor data | Specifies the data related to the requestor. These data may be used as input in the authentication and authorization process. E.g. end user and application identification, credentials or privacy policy information. | Optional | + +**Table 4.5: Response data of Delete procedure** + +| Parameter | Description | Use | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Redirection data | Specifies the redirection instructions and assertions. | Optional | +| Status | Indicates whether:
1. The procedure was carried out successfully,
2. The request was redirected, or
3. A failure was detected.
For the proxy mode 1 or 3 can be indicated. For the redirect mode 2 or 3 can be indicated. The possible failure is described in sufficient detail. | Mandatory (like the response itself) | + +### 4.3.2a List procedure + +List procedure is used by the application to list the existing profile items in the various GUP Data Repositories, and it is needed to handle large number of items. Different search criteria may be given as input. Only the references (i.e. resource identities and component types) are returned by the procedure. The listing may optionally operate sequentially, and then only a selected number of items is returned in one listing. The application shall provide the necessary data for authentication and authorization purposes (e.g. credentials, assertions and identifications). + +The outcome of the procedure shall be provided in a separate response message. + +**Table 4.5a: Request data of List procedure** + +| Parameter | Description | Use | +|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Search criteria | Specifies which profiles are to be listed. The criteria may include at least resource identity (or part of it) and/or component type. | Mandatory | +| Requestor data | Specifies the data related to the requestor. These data may be used as input in the authentication and authorization process. E.g. end user and application identification, credentials or privacy policy information. | Optional | + +**Table 4.5b: Response data of List procedure** + +| Parameter | Description | Use | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| Listing data | Provides the listed data (several elements). See the table below for the contents of a single element. | Mandatory | +| End indication | Indicates that the end of list has been reached. | Optional | +| Status | Indicates whether:
1. The procedure was carried out successfully,
2. The request was redirected, or
3. A failure was detected.
For the proxy mode 1 or 3 can be indicated. For the redirect mode 2 or 3 can be indicated. The possible failure is described in sufficient detail. | Mandatory | + +**Table 4.5c: Contents of Listing data parameter** + +| Parameter | Description | Use | +|-------------------|-------------------------------------------------------------------------------------------------------------|------------| +| Resource identity | Specifies the resource identity with its type (e.g. SIP URI public ID). | Mandatory | +| Component types | Specifies the component types which are linked to the Resource identity and match with the search criteria. | Mandatory | + +### 4.3.3 Modify procedure + +Modify procedure is used by the application to change the data in the GUP components. Also adding and deleting data is possible by Modify procedure, but it cannot create a new component. The modified data are identified by the resource identity and the data reference. The modification may concern the whole component or any lower level piece of data referenced in the procedure invocation. The contents for the entire referenced data shall be provided. Several individual changes to different components can be made with one procedure invocation. It must be noted that if modification of one component fails, the other changes cannot always be rolled back (implementation specific feature). However the response data shall specify which modifications were not accomplished. It is also possible to add more similar type of data elements to an existing array type of element. The requestor shall provide the necessary data for authentication and authorization purposes (e.g. credentials, assertions and identifications). + +The outcome of the procedure shall be provided in a separate response message. If the requestor data indicated that the application is able to receive redirect instructions, the GUP server may decide to return redirect instructions based on policies set by the operator in the GUP server. After this response the procedure is terminated without any other specified results or retained information in the GUP Server. + +**Table 4.6: Request data of Modify procedure** + +| Parameter | Description | Use | +|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| Resource identity | Specifies the resource identity with its type (e.g. SIP URI public ID). | Mandatory | +| Modification data | Specifies which data are addressed and how those are changed. There may be several Modification data items corresponding to several individual modifications. These modifications may concern the same or different components. See the table below for the contents of one modification. | Mandatory | +| Requestor data | Specifies the data related to the requestor. These data may be used as input in the authentication and authorization process. E.g. end user and application identification, credentials or privacy policy information. | Optional | + +**Table 4.7: Contents of Modification data parameter** + +| Parameter | Description | Use | +|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Data reference | Specifies which data are modified or expanded. The reference identifies both the component type and the possible deeper level data reference. The reference must be unique in a way that it refers only to one data item. | Mandatory | +| New data | Specifies the data to be stored in the GUP component. It is expected that all the data elements in the referenced data structure are given. | Mandatory | +| Overwrite indication | Specifies if the data are added to the existing data or replaces those. Default action is "insert". | Optional | + +**Table 4.8: Response data of Modify procedure** + +| Parameter | Description | Use | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Redirection data | Specifies the redirection instructions and assertions. | Optional | +| Status | Indicates whether:
1. The procedure was carried out successfully,
2. The request was redirected, or
3. A failure was detected.
For the proxy mode 1 or 3 can be indicated. For the redirect mode 2 or 3 can be indicated. The possible failure is described in sufficient detail. | Mandatory (like the response itself) | + +### 4.3.4 Query procedure + +Query procedure is used by the application to retrieve the data in the user profile or its specific components. The queried data are identified by the resource identity and the data reference. The data retrieval may concern the whole profile, component or any parts of a component as referenced in the invocation. The requestor shall provide the necessary data for authentication and authorization purposes (e.g. credentials, assertions and identifications). + +The retrieved data shall be provided in a separate response message. If the requestor data indicated that the application is able to receive redirect instructions, the GUP server may decide to return redirect instructions based on policies set by the operator in the GUP server. After this response the procedure is terminated without any other specified results or retained information in the GUP Server. + +**Table 4.9: Request data of Query procedure** + +| Parameter | Description | Use | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Resource identity | Specifies the resource identity with its type (e.g. SIP URI public ID). | Mandatory | +| Data references | Specifies which data are read. The data reference identifies the component type and the deeper level reference (if the whole component is not meant to be read). Multiple references may be given. It is also possible to refer to the profile root which implies that the whole profile data are queried. | Mandatory | +| Requestor data | Specifies the data related to the requestor. These data may be used as input in the authentication and authorization process. E.g. end user and application identification, credentials or privacy policy information. | Optional | + +**Table 4.10: Response data of Query procedure** + +| Parameter | Description | Use | +|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Data | Contains the retrieved data as indicated by the Data references. | Mandatory | +| Redirection data | Specifies the redirection instructions and assertions. | Optional | +| Status | Indicates whether:
1. The procedure was carried out successfully,
2. The request was redirected, or
3. A failure was detected.
For the proxy mode 1 or 3 can be indicated. For the redirect mode 2 or 3 can be indicated. The possible failure is described in sufficient detail. | Mandatory | + +### 4.3.5 Subscribe procedure + +Subscribe procedure is used by the application to request notifications about changes in the GUP component data. The subscribed data are identified by the resource identity and the data reference. Furthermore the application can identify which elements are to be monitored for changes if it is not interested in all changes. Data synchronization can be performed by Subscribe and Notify procedures. The GUP Server returns the identification of the subscription request to provide means for the application to link the notifications of Notify procedure to the related subscribe requests. With Subscribe procedure an application can also request a list of all its subscriptions to notifications from the GUP Server. The GUP Server shall provide all the application's subscriptions to notifications in the response message. + +A filtering data parameter is defined to facilitate performance optimization. This may be left partly vendor/operator specific. The requestor shall provide the necessary data for authentication and authorization purposes (e.g. credentials, assertions and identifications). + +The outcome of the procedure shall be provided in a separate response message. If the requestor data indicated that the application is able to receive redirect instructions, the GUP server may decide to return redirect instructions based on policies set by the operator in the GUP server. After this response the procedure is terminated without any other specified results or retained information in the GUP Server. + +**Table 4.11: Request data of Subscribe procedure** + +| Parameter | Description | Use | +|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Resource identity | Specifies the resource identity with its type (e.g. SIP URI public ID).
This parameter may be absent only when List of subscriptions parameter is present, otherwise this parameter shall always be present. | Conditional | +| Notification Reference | Specifies the call-back address of the Requestor. The GUP server shall send the notifications to this address. | Mandatory | +| List of subscriptions | Indicates that the application requests the list of all its subscriptions from the GUP server. | Optional | +| Data references | Specifies which data are monitored for changes. The reference identifies both the component type and the possible deeper level data reference. Multiple references may be given. Any change within the referenced data structure causes a notification to be sent. If the parameter is absent, all modifications are notified. | Optional | +| Requestor data | Specifies the data related to the requestor. These data may be used as input in the authentication and authorization process. E.g. end user and application identification, credentials or privacy policy information. | Optional | +| Filter data | Specifies additional conditions for sending notifications to optimize the performance e.g. when immediate synchronization is not required. The parameter specifies also whether the initial data values are requested to be reported. | Optional | + +**Table 4.12: Response data of Subscribe procedure** + +| Parameter | Description | Use | +|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| +| Invoke identifications | Contains the invoke identification assigned by the GUP Server for this request.
When the application has requested the list of all its subscriptions, this parameter will contain all the invoke identifications assigned by the GUP Server to the application. | Mandatory (unless the request is redirected or fails) | +| Redirection data | Specifies the redirection instructions and assertions. | Optional | +| Status | Indicates whether:
1. The procedure was carried out successfully,
2. The request was redirected, or
3. A failure was detected.
For the proxy mode 1 or 3 can be indicated. For the redirect mode 2 or 3 can be indicated. The possible failure is described in sufficient detail. | Mandatory (like the response itself) | + +### 4.3.6 Unsubscribe procedure + +Unsubscribe procedure is used by the application to cancel one or several existing subscriptions. The outcome of the procedure shall be provided in a separate response message. + +**Table 4.13: Request data of Unsubscribe procedure** + +| Parameter | Description | Use | +|------------------------|---------------------------------------------------------------------------------------------------|-----------| +| Invoke identifications | Specifies one or several invoke identifications assigned by the GUP Server for the subscriptions. | Mandatory | + +**Table 4.14: Response data of Unsubscribe procedure** + +| Parameter | Description | Use | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Status | Indicates whether the procedure was carried out successfully or whether some failure was detected.
The possible errors are described in sufficient detail. | Mandatory (like the response itself) | + +### 4.3.7 Notify procedure + +Notify procedure is invoked by the GUP Server when the data which was identified in Subscribe procedure changes or when the invoked Subscribe procedure requested sending of all the initial values of the referenced data. The procedure identifies the changed data and provides the new values. + +The outcome of the procedure shall be provided in a separate response message. + +**Table 4.15: Request data of Notify procedure** + +| Parameter | Description | Use | +|-----------------------|-----------------------------------------------------------------------------------------------------------|-----------| +| Invoke identification | Specifies the invoke identification assigned by the GUP Server for this subscription. | Mandatory | +| Notified data | Specifies which data are reported together with the data itself. Multiple pieces of data may be provided. | Mandatory | + +**Table 4.16: Response data of Notify procedure (optional)** + +| Parameter | Description | Use | +|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| +| Status | Indicates whether the procedure was carried out successfully or whether some failure was detected.
The possible errors are described in sufficient detail. | Mandatory (however the whole response is optional) | + +### 4.3.8 Common information definitions + +The information elements that are applied in several procedures of Rg reference point are described in this clause. + +#### 4.3.8.1 Requestor data + +The Requestor data contain the information that the sender of the request provides in order to facilitate the authentication and authorization functions. The access control and user privacy functions work based on these data. Also an unspecified Additional info parameter is defined to carry data e.g. for monitoring or accounting purposes. All the elements are optional. However at least one shall be present if the parameter is applied. + +**Table 4.17: Requestor data** + +| Element | Description | Use | +|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Subscriber identification | Specifies the end user being served. | Optional | +| Application identification | Specifies the application being served. The GUP Server has to link the Application identification to the actual sender of the request by the appropriate means taking into account the applied security measures and domains. | Optional | +| Credentials | Contains authentication information. | Optional | +| Authorization assertion | Contains the assertion for authorization. The nature of the assertion must be for one time use to prevent replay and cut-and-paste attacks. E.g. digest or signature mechanisms may be applied. | Optional | +| Privacy policy | Information about the applied privacy policy. | Optional | +| Redirection indications | Specifies if the application being served is able to handle returned redirect requests or if it specifically desires to apply the redirect mode. However the GUP Server decides which mode is used. If the parameter is missing, it is presumed that no such capability exists with the application. | Optional | +| Additional info | Additional unspecified information related to the requestor or request. | Optional | + +#### 4.3.8.2 Redirection data + +The Redirection data is returned to the requester if redirection is called for. These data contain the address where the request is to be redirected to and the authorisation assertions optionally provided by the GUP Server, which may this way carry out at least part of the authorisation on behalf of the RAF (or Data Repository). The RAF (or the GUP Data Repository) takes the final decision whether the authorisation is accepted or not. + +**Table 4.17a: Redirection data** + +| Element | Description | Use | +|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------| +| Redirection address | Specifies the address (e.g. URI) where the request is to be redirected. | Optional | +| Authorisation assertion | Contains the assertion for authorisation. This may be placed in the Requestor data item in the subsequent requests over Rp reference point. | Optional | + +### 4.3.9 Error handling and common error types + +The basic principle in error handling is that all errors in carrying out the procedures lead to complete abortion of the requested operation. However if e.g. multiple modifications with separate data references are made with one procedure invocation, it is possible that part of these are completed even if some would fail. The procedure error responses identify the error type together with more detailed information about the cause of the error. + +The common error types which can be applied to all procedures contain: + +**Table 4.18: Common error types** + +| Error | Description | +|------------------------|-----------------------------------------------------| +| Invalid operation | The operation is invalid or unsupported. | +| Invalid parameter | The given parameter of the operation is invalid. | +| Unauthorized operation | There was no authority for the requested operation. | +| Data unavailable | The requested data were not available. | +| Unexpected error | An unexpected error condition was met. | +| Authentication error | The authentication of the requestor has failed. | + +## 4.4 Rp reference point procedures + +This clause defines the procedures applied in the Rp reference point. The application or GUP server acts as the active requestor towards the Repository Access Function (RAF) entities e.g. to read or modify the data. It is assumed that the both ends share initially the same data structure definitions. Rp is applied to control the data stored in the different user profile components identified by a resource identity and the component type. The resource identity contains either a subscriber identity or a generic component identification which is given to components that are not bound to a single subscriber. + +There are the following procedures: + +- Create Component +- Delete Component +- Modify Data +- List Data +- Read Data +- Subscribe To Data +- Unsubscribe To Data +- Notify Data +- Define Data + +### 4.4.1 Create Component procedure + +Create Component procedure is used by the application to add a new profile component in the contacted repository. The attached resource identity and the created component type are specified along with the created data. The component type identifies what data are concerned i.e. not just the data typing. It is presumed that the profile data structure is already known by the both parties. No new type of data can be defined by this procedure, only the data contents are provided. The requestor shall provide the necessary data for authorization purposes (e.g. assertions and identifications). + +This procedure is synchronous in nature but it is also possible to define a separate response message. + +**Table 4.19: Request data of Create Component procedure** + +| Parameter | Description | Use | +|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Resource Identity | Specifies the resource identity with its type (e.g. SIP URI public ID). | Mandatory | +| Component type | Specifies the type of the created component. This is needed because several types may be supported by one RAF. The Component type identifies the applied component data definitions. | Mandatory | +| Requestor data | Specifies the data related to the requestor. These data may be used as input in the authorization process. E.g. end user and application identification. See clause 4.4.9. | Optional | +| Component data | Specifies the profile component data according to the specified Component type. | Mandatory | + +**Table 4.20: Response data of Create Component procedure** + +| Parameter | Description | Use | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Status | Indicates whether the procedure was carried out successfully or whether some failure was detected. The possible errors are described in sufficient detail. | Mandatory (like the response itself) | + +### 4.4.2 Delete Component procedure + +Delete Component procedure is used by the application to remove a profile component from the contacted repository. The attached resource identity and the component type is specified. The requestor shall provide the necessary data for authorization purposes (e.g. assertions and identifications). + +This procedure is synchronous in nature but it is also possible to define a separate response message. + +**Table 4.21: Request data of Delete Component procedure** + +| Parameter | Description | Use | +|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| Resource identity | Specifies the resource identity with its type (e.g. SIP URI public ID). | Mandatory | +| Component type | Specifies the type of the component. | Mandatory | +| Requestor data | Specifies the data related to the requestor. These data may be used as input in the authorization process. E.g. end user and application identification. See clause 4.4.9. | Optional | + +**Table 4.22: Response data of Delete Component procedure** + +| Parameter | Description | Use | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Status | Indicates whether the procedure was carried out successfully or whether some failure was detected. The possible errors are described in sufficient detail. | Mandatory (like the response itself) | + +### 4.4.2a List Data procedure + +List Data procedure is used by the application to list the existing profile items in the various GUP Data Repositories, and it is needed to handle large number of items. Different search criteria may be given as input. Only the references (i.e. resource identities and component types) are returned by the procedure. The listing may optionally operate sequentially, and then only a selected number of items is returned in one listing. The application shall provide the necessary data for authentication and authorization purposes (e.g. credentials, assertions and identifications). + +The outcome of the procedure shall be provided in a separate response message. + +**Table 4.22a: Request data of List Data procedure** + +| Parameter | Description | Use | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| Search criteria | Specifies which profiles are to be listed. The criteria may include at least resource identity (or part of it) and/or component type. | Mandatory | +| Requestor data | Specifies the data related to the requestor. These data may be used as input in the authentication and authorization process. E.g. end user and application identification, credentials or privacy policy information. | Optional | + +**Table 4.22b: Response data of List Data procedure** + +| Parameter | Description | Use | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| Listing data | Provides the listed data (several elements). See the table below for the contents of a single element. | Mandatory | +| End indication | Indicates that the end of list has been reached. | Optional | +| Status | Indicates whether the procedure was carried out successfully or whether some failure was detected. The possible errors are described in sufficient detail. | Mandatory | + +**Table 4.22c: Contents of Listing data parameter** + +| Parameter | Description | Use | +|-------------------|-------------------------------------------------------------------------------------------------------------|-----------| +| Resource identity | Specifies the resource identity with its type (e.g. SIP URI public ID). | Mandatory | +| Component types | Specifies the component types which are linked to the resource identity and match with the search criteria. | Mandatory | + +### 4.4.3 Modify Data procedure + +Modify Data procedure is used by the application to change the data in a profile component. The component is identified by the resource identity and the component type. The modification may concern the whole component or any lower level piece of data referenced in the procedure invocation. The contents for the entire referenced data shall be provided. Several individual changes to the component can be made with one procedure invocation. It is also possible to add more similar type of data elements to an existing array type of element. The requestor shall provide the necessary data for authorization purposes (e.g. assertions and identifications). + +This procedure is synchronous in nature but it is also possible to define a separate response message. + +**Table 4.23: Request data of Modify Data procedure** + +| Parameter | Description | Use | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Resource identity | Specifies the resource identity with its type (e.g. SIP URI public ID). | Mandatory | +| Component type | Specifies the type of the component. | Mandatory | +| Modified data | Specifies which data are addressed and how those are changed. There may be several modified data items corresponding to several individual modifications. See the table below for the contents of one modification. | Mandatory | +| Requestor data | Specifies the data related to the requestor. These data may be used as input in the authorization process. E.g. end user and application identification. See clause 4.4.9. | Optional | + +**Table 4.24: Contents of Modified data parameter** + +| Parameter | Description | Use | +|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| Data reference | Specifies which data are modified or expanded. The reference may indicate the whole component or any deeper level piece of data. The reference must be unique in a way that it refers only to one data item. | Mandatory | +| New data | Specifies the data to be stored in the profile component. It is expected that all the data elements in the referenced data structure are given. | Mandatory | +| Overwrite indication | Specifies if the data are added to the existing data or replaces those. Default action is "insert". | Optional | + +**Table 4.25: Response data of Modify Data procedure** + +| Parameter | Description | Use | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Status | Indicates whether the procedure was carried out successfully or whether some failure was detected. The possible errors are described in sufficient detail. | Mandatory (like the response itself) | + +### 4.4.4 Read Data procedure + +Read Data procedure is used by the application to retrieve the data in a profile component. The component is identified by the resource identity and the component type. The data retrieval may concern the whole component or any parts of it as referenced in the invocation. The requestor shall provide the necessary data for authorization purposes (e.g. assertions and identifications). + +**Table 4.26: Request data of Read Data procedure** + +| Parameter | Description | Use | +|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| Resource identity | Specifies the resource identity with its type (e.g. SIP URI public ID). | Mandatory | +| Component type | Specifies the type of the component. | Mandatory | +| Data references | Specifies which data are read. The data reference may point to a piece of data on any level in the data structure (also to the whole component). Multiple references may be given. | Mandatory | +| Requestor data | Specifies the data related to the requestor. These data may be used as input in the authorization process. E.g. end user and application identification. See clause 4.4.9. | Optional | + +**Table 4.27: Response data of Read Data procedure** + +| Parameter | Description | Use | +|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Data | Contains the retrieved data as indicated by the Data references. All the data under the referenced one are returned. Multiple packets of data are given if so requested. | Mandatory | +| Status | Indicates whether the procedure was carried out successfully or whether some failure was detected. The possible errors are described in sufficient detail. | Mandatory (like the response itself) | + +This procedure is synchronous in nature but it is also possible to define a separate response message. + +### 4.4.5 Subscribe To Data procedure + +Subscribe To Data procedure is used by the application to request notifications about changes in the profile component data. The component is identified by the resource identity and the component type. Furthermore the application can identify which elements are to be monitored for changes if it is not interested in all changes. Data synchronization can be performed by Subscribe To Data and Notify Data procedures. The RAF returns the identification of the subscription request to provide means for the application to link the notifications of Notify Data procedure to the related subscribe requests. With Subscribe To Data procedure an application can also request a list of all its subscriptions to notifications from the RAF. The RAF shall provide all the application's subscriptions to notifications in the response message. + +A filtering data parameter is defined to facilitate performance optimization. This may be left partly vendor/operator specific. The requestor shall provide the necessary data for authorization purposes (e.g. assertions and identifications). + +**Table 4.28: Request data of Subscribe To Data procedure** + +| Parameter | Description | Use | +|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Resource identity | Specifies the resource identity with its type (e.g. SIP URI public ID).
This parameter may be absent only when List of subscriptions parameter is present, otherwise this parameter shall always be present. | Conditional | +| Notification Reference | Specifies the call-back address of the Requestor. The RAF shall send the notifications to this address. | Mandatory | +| List of subscriptions | Indicates that the application requests the list of all its subscriptions from the RAF. | Optional | +| Component type | Specifies the type of the component. | Mandatory | +| Data references | Specifies which data are monitored for changes. Multiple references may be given. Any change within the referenced data structure causes a notification to be sent. If the parameter is absent, all modifications are notified. | Optional | +| Requestor data | Specifies the data related to the requestor. These data may be used as input in the authorization process. E.g. end user and application identification. See clause 4.4.9. | Optional | +| Filter data | Specifies additional conditions for sending notifications to optimize the performance e.g. when immediate synchronization is not required. The parameter specifies also whether the initial data values are requested to be reported. | Optional | + +**Table 4.29: Response data of Subscribe To Data procedure** + +| Parameter | Description | Use | +|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Invoke identifications | Contains the invoke identification assigned by the RAF for this request.
When the application has requested the list of all its subscriptions, this parameter will contain all the invoke identifications assigned by the RAF to the application. | Mandatory | +| Status | Indicates whether the procedure was carried out successfully or whether some failure was detected. The possible errors are described in sufficient detail. | Mandatory (like the response itself) | + +### 4.4.6 Unsubscribe To Data procedure + +Unsubscribe To Data procedure is used by the application to cancel one or several existing subscriptions. + +**Table 4.30: Request data of Unsubscribe To Data procedure** + +| Parameter | Description | Use | +|------------------------|--------------------------------------------------------------------------------------------|-----------| +| Invoke identifications | Specifies one or several invoke identifications assigned by the RAF for the subscriptions. | Mandatory | + +**Table 4.31: Response data of Unsubscribe To Data procedure** + +| Parameter | Description | Use | +|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| +| Status | Indicates whether the procedure was carried out successfully or whether some failure was detected. The possible errors are described in sufficient detail. | Mandatory (like the response itself) | + +### 4.4.7 Notify Data procedure + +Notify Data procedure is invoked by the RAF when the data which was identified in Subscribe To Data procedure changes or when the invoked Subscribe To Data procedure requested sending of all the initial values of the referenced data. The procedure identifies the changed data and provides the new values. + +**Table 4.32: Request data of Notify Data procedure** + +| Parameter | Description | Use | +|-----------------------|-----------------------------------------------------------------------------------------------------------|------------| +| Invoke identification | Specifies the invoke identification assigned by the RAF for this subscription. | Mandatory | +| Notified data | Specifies which data are reported together with the data itself. Multiple pieces of data may be provided. | Mandatory | + +**Table 4.33: Response data of Notify Data procedure (optional)** + +| Parameter | Description | Use | +|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| +| Status | Indicates whether the procedure was carried out successfully or whether some failure was detected. The possible errors are described in sufficient detail. | Mandatory (however the whole response is optional) | + +### 4.4.8 Define Data procedure + +Define Data procedure is used by the application to define new data elements to the profile component data structure. The names and types for the new data are specified. This procedure facilitates extension of the profile data with new, proprietary data. Subsequently these data can be handled by the above described procedures e.g. modified by the Modify Data procedure. + +### 4.4.9 Common information definitions + +The information elements that are applied in several procedures are described in this clause. + +#### 4.4.9.1 Requestor data + +The Requestor data contain the information that the sender of the request provides in order to facilitate the authorization functions. The access control and user privacy functions work based on these data. Also an unspecified Additional info parameter is defined to carry data e.g. for monitoring or accounting purposes. All the elements are optional. However at least one shall be present if the parameter is applied. + +**Table 4.34: Requestor data** + +| Element | Description | Use | +|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| +| Subscriber identification | Specifies the end user being served. | Optional | +| Application identification | Specifies the application being served. The RAF has to link the Application identification to the actual sender of the request by the appropriate means taking into account the applied security measures and domains. | Optional | +| Authorization assertion | Contains the assertion for authorization. The nature of the assertion must be for one time use to prevent replay and cut-and-paste attacks. E.g. digest or signature mechanisms may be applied. The provisioning of the assertions or any related shared secrets is beyond Rp reference point specifications. | Optional | +| Additional info | Additional unspecified information related to the requestor or request. | Optional | + +### 4.4.10 Error handling and common error types + +The basic principle in error handling is that all errors in carrying out the procedures lead to complete abortion of the requested operation. The procedure error responses identify the error type together with more detailed information about the cause of the error. + +The common error types which can be applied to all procedures contain: + +**Table 4.35: Common error types** + +| Error | Description | +|------------------------|-----------------------------------------------------| +| Invalid operation | The operation is invalid or unsupported. | +| Invalid parameter | The given parameter of the operation is invalid. | +| Unauthorized operation | There was no authority for the requested operation. | +| Data unavailable | The requested data were not available. | +| Unexpected error | An unexpected error condition was met. | +| Authentication error | The authentication of the requestor has failed. | + +# 5 GUP information model + +A Generic User Profile consists of a number of independent GUP Components. However, a GUP Component may contain (i.e. reference) other GUP components e.g. to enable reuse of data. + +The GUP Component has a unique identity within the Generic User Profile. In addition to the component type the component identity contains either a subscriber identity or more generic identification depending on which kind of component is in question. A GUP Component can be retrieved through one RAF, and it may consist of a number of GUP Components, Data Element Groups and/or Data Elements. + +A GUP Component contains zero or more Data Element Groups. The Data Element Group contains indivisible Data Elements and/or Data Element Groups. The nested Data Elements Groups allow deeper hierarchical structures. The Data Element Group in the lowest hierarchical level contains one or more Data Elements. The Data Element Groups inside a GUP Component may be of the same or different types. + +Alternatively the GUP Component may contain zero or more Data Elements without the Data Element Groups. A GUP component shall have at least one Data Element Group or Data Element. + +A Composite Datatype is used to define the structure of the whole GUP Component. The structure includes definition about what kind of Data Element Groups and/or which Data Elements belong to the defined GUP Component as well as the data types and valid values of the data. + +The UML Class Diagram below illustrates the basic concepts of the GUP Information Model. + +![UML Class Diagram illustrating the basic concepts of the GUP Information Model. The diagram shows four classes: Generic User Profile, GUP Component, Data Element group, and Data Element, along with Composite Datatype. Generic User Profile (1) has a composition relationship with GUP Component (*). GUP Component (1) has a composition relationship with Data Element group (0..*). GUP Component (1) has a composition relationship with Data Element (0..*). GUP Component (1) has a composition relationship with Composite Datatype (0..*). Data Element group (1) has a composition relationship with Data Element (1..*). Data Element group (1) has a composition relationship with Data Element group (0..*). GUP Component has an attribute 'Identity'. Data Element group has an attribute 'Group type'.](68d8089266ace7197304b43dcaf5d08e_img.jpg) + +``` + +classDiagram + class GenericUserProfile["Generic User Profile"] + class GUPComponent["GUP Component"] { + Identity + } + class DataElementGroup["Data Element group"] { + Group type + } + class DataElement["Data Element"] + class CompositeDatatype["Composite Datatype"] + + GenericUserProfile "1" *-- "*" GUPComponent + GUPComponent "1" *-- "0..*" DataElementGroup + GUPComponent "1" *-- "0..*" DataElement + GUPComponent "1" *-- "0..*" CompositeDatatype + DataElementGroup "1" *-- "1..*" DataElement + DataElementGroup "1" *-- "0..*" DataElementGroup + +``` + +UML Class Diagram illustrating the basic concepts of the GUP Information Model. The diagram shows four classes: Generic User Profile, GUP Component, Data Element group, and Data Element, along with Composite Datatype. Generic User Profile (1) has a composition relationship with GUP Component (\*). GUP Component (1) has a composition relationship with Data Element group (0..\*). GUP Component (1) has a composition relationship with Data Element (0..\*). GUP Component (1) has a composition relationship with Composite Datatype (0..\*). Data Element group (1) has a composition relationship with Data Element (1..\*). Data Element group (1) has a composition relationship with Data Element group (0..\*). GUP Component has an attribute 'Identity'. Data Element group has an attribute 'Group type'. + +**Figure 5.1: The basic concepts of GUP** + +GUP defines an Authorisation Component, which is just like any other GUP Component. This implies that the same capabilities as for any GUP Component (e.g. identities and structure) are also applied to the Authorisation Component. The Authorisation Component is able to reference any element of the GUP Information Model and define the + +authorisation regarding those elements. The Authorisation Component may be either subscriber specific or common to several subscribers and/or elements of the GUP Information Model. + +Note that any GUP Component may include additional data items, which are used (e.g. by RAF) for the authorisation purposes but those are seen as a part of the data specific to a certain GUP Component, and thus not a part of the generic authorisation specified by GUP. + +Figure 5.2 presents an example structure of Generic User Profile with the terms used in the UML Class Diagram. Note that the data structure may be also deeper than shown in the example figure, e.g., the Data Element Groups might consist of nested Data Element Groups. + +![Figure 5.2: Example structure of GUP information. A hierarchical tree diagram showing the structure of a Generic User Profile. The root node is 'Generic User Profile'. It branches into three main components: 'GUP Component 1', 'GUP Component 2', and 'GUP Component 3'. 'GUP Component 1' branches into 'Data Element group A' and 'Data Element B'. 'Data Element group A' branches into 'Data Element AA' and 'Data Element AB'. 'GUP Component 2' branches into 'Data Element C' and 'Data Element D'. 'GUP Component 3' branches into 'Data Element group E' and 'GUP Component 123'. 'Data Element group E' branches into 'Data Element group EA' and 'Data Element F'. 'Data Element group EA' branches into 'Data Element EAA' and 'Data Element EAB'.](6470d350326789d5306eabcb76533951_img.jpg) + +``` +graph TD; GUP[Generic User Profile] --- GC1[GUP Component 1]; GUP --- GC2[GUP Component 2]; GUP --- GC3[GUP Component 3]; GC1 --- DEG_A[Data Element group A]; GC1 --- DE_B[Data Element B]; DEG_A --- DE_AA[Data Element AA]; DEG_A --- DE_AB[Data Element AB]; GC2 --- DE_C[Data Element C]; GC2 --- DE_D[Data Element D]; GC3 --- DEG_E[Data Element group E]; GC3 --- GC123[GUP Component 123]; DEG_E --- DEG_EA[Data Element group EA]; DEG_E --- DE_F[Data Element F]; DEG_EA --- DE_EAA[Data Element EAA]; DEG_EA --- DE_EAB[Data Element EAB]; +``` + +Figure 5.2: Example structure of GUP information. A hierarchical tree diagram showing the structure of a Generic User Profile. The root node is 'Generic User Profile'. It branches into three main components: 'GUP Component 1', 'GUP Component 2', and 'GUP Component 3'. 'GUP Component 1' branches into 'Data Element group A' and 'Data Element B'. 'Data Element group A' branches into 'Data Element AA' and 'Data Element AB'. 'GUP Component 2' branches into 'Data Element C' and 'Data Element D'. 'GUP Component 3' branches into 'Data Element group E' and 'GUP Component 123'. 'Data Element group E' branches into 'Data Element group EA' and 'Data Element F'. 'Data Element group EA' branches into 'Data Element EAA' and 'Data Element EAB'. + +**Figure 5.2: Example structure of GUP information** + +One purpose of the example structure is to clarify the intended relation between the UML Class Diagram and the hierarchical structure of GUP in terms of XML. Use of XML fulfils the requirements for the architectural structure of the GUP information model. + +Each Generic User Profile consists of one or several GUP Components depending on the nature of the user related data. GUP Components are independent XML documents. The Generic User Profile is thus formed of a number of XML documents. + +Each GUP Component consists of GUP Components, Data Elements and/or Data Element Groups as defined in the component specific definitions. In XML terms the Data Elements are XML elements. The Data Element Group is a structured XML element with an arbitrarily deep data structure. + +# Annex A (informative): Examples of 3GPP Generic User Profile usage + +## Example 1: GUP Usage with Subscription Management + +An application is accessing targeted subscriber's subscription data (HSS GUP Component) stored in the HSS. It is assumed that RAF is implemented in the HSS and the targeted HSS GUP Component has been created by using the Create Component procedure. The application in this case can be e.g. a Subscription Management application, a service application or any third party application that is interested in the subscription data of a specific subscriber in operator A's network. + +The example of the interworking interface diagram is shown in Figure A.2. In this example GUP Server is working in the proxy mode of operation. + +![Figure A.2: An Example of the Interworking Diagram between GUP and an Application. The diagram shows a sequence of interactions between Application A, GUP Server, HSS 1, and HSS 2. Step 1: Application A sends an Rg message to GUP Server. Step 2: GUP Server sends an Rp message to HSS 1. Step 3: GUP Server sends an Rp message to HSS 2. Step 4: HSS 1 sends an Rp message to GUP Server. Step 5: GUP Server sends an Rg message to Application A.](94fd137860c16c8dfd75512f10161fe8_img.jpg) + +``` + +sequenceDiagram + participant Application A + participant GUP Server + participant HSS 1 + participant HSS 2 + Note right of GUP Server: Step 2 + Application A->>GUP Server: Step 1 (Rg) + GUP Server->>HSS 1: Step 3 (Rp) + GUP Server->>HSS 2: Step 4 (Rp) + HSS 1->>GUP Server: Step 5 (Rp) + GUP Server->>Application A: Step 1 (Rg) + +``` + +Figure A.2: An Example of the Interworking Diagram between GUP and an Application. The diagram shows a sequence of interactions between Application A, GUP Server, HSS 1, and HSS 2. Step 1: Application A sends an Rg message to GUP Server. Step 2: GUP Server sends an Rp message to HSS 1. Step 3: GUP Server sends an Rp message to HSS 2. Step 4: HSS 1 sends an Rp message to GUP Server. Step 5: GUP Server sends an Rg message to Application A. + +**Figure A.2: An Example of the Interworking Diagram between GUP and an Application** + +The interworking steps between the Application, GUP Server and HSS are summarised below: + +Step 1: Application A invokes a Query procedure to the GUP Server including the targeted subscriber's public user identity joe.doe@operatorA.com in the Resource Identity parameter. The HSS GUP Component will be included in the Data Reference parameter clarifying the targeted data (component type) that the application is interested in. Also specific data (i.e. XML Data Element) within one GUP Component can be requested. Application A's identity is included in the Requestor data parameter for the identification and authorisation purposes of the request. + +Step 2: GUP Server authenticates the application and authorises the request with the result that Application A is allowed to access the HSS GUP Component of the subscriber joe.doe@operatorA.com. + +Step 3: GUP Server locates the target GUP Data Repository (RAF address), i.e. that the HSS GUP Component of the subscriber joe.doe@operatorA.com is located in the HSS 1, and invokes Read data procedure to HSS 1. + +Step 4: HSS 1 makes an internal query by using the public user identity joe.doe@operatorA.com and returns a response to Read data procedure to the GUP Server including the requested HSS GUP Component data of the subscriber joe.doe@operatorA.com. + +Step 5: GUP Server passes the received response to Query procedure further to Application A. + +The GUP Server may retrieve authorisation GUP Components from a RAF, if it does not hold sufficient information by itself to carry out the authorisation. + +If necessary, e.g. when the application requests several GUP Components, or the whole profile including several GUP components in different repositories, GUP Server can invoke several requests to various RAFs and combine responses to one response when returning a response to the application. + +# Annex B (informative): 3GPP Generic User Profile candidates + +This table lists the Generic User Profile candidates grouped per GUP access. It gives for each data access, the supplier, the consumer and the data repository. The applied categorization of the data in the table does not imply similar GUP component structure. + +| GUP access | Supplier | Data repository | Description of the data | Consumer | +|-----------------------------------------------------------|----------------|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| +| General user data for IMS | AS manager | AS | ISIM subscriber data for IMS:
- Private & Public SIP URI of the user
- Settings back up/restore
- Preferences (e.g. languages)
- Phone books
- Buddy list
- Available services
- Service capabilities
- Active service profile | S-CSCF | +| MMS VASP applications

Ref TS 23.141 [7] | AS manager | AS | MMS application specific data:
- Authorization
- Confidentiality
- Charging information
- Message distribution | MMS server | +| Privacy control settings of the user | AS manager | AS | Privacy control data of the user:
- Privacy settings for standardized service like Presence
- Privacy setting of non standardized services | UE-ISIM | +| PLMN specific user information | O&M | HSS | PLMN specific user information:
- User addresses (e.g. MSISDNs, URLs)
- WAP parameters (e.g. standard WAP gateway)
- GPRS parameters
- Preferred access technologies (e.g. UTRAN, GERAN, WLAN etc...) | S-CSCF
AS | +| Authorized and subscribed service information for CS & PS | O&M
HSS-HLR | HSS-HLR | Authorized and subscribed service information:
- Subscriber ID (IMSI, MSISDNs)
- General subscription information
- Subscription restrictions
- Basic & Supplementary services
- Charging plans
- Operator determined barring data is FFS
- SMS subscription
- MMS subscription | MSC/VLR
GMSC
SGSN
GGSN
MMS server | +| CSE handling of user subscriptions for CS & PS | CSE | HSS-HLR | - Forwarding & barring information
- CAMEL subscription information | CSE | +| Authorized and subscribed service information for IMS | O&M | HSS | Authorized and subscribed service information:
- IM Subscriber ID (Private User ID, Public ID)
- Subscribed media
- Billing policy
- Initial filter criteria
- Service keys & triggering aspects
- Authorized services that the subscriber may subscribe to
- Services the subscriber actually has subscribed to | S-CSCF
AS | +| CAMEL services for IMS | O&M | HSS-HLR | CAMEL subscription information for IMS | IM-SSF | + +# Annex C (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|-----|-----|--------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2003-06 | SA#20 | SP-030310 | | | Raised to v.6.0.0 after approval at SA#20 | 2.0.0 | 6.0.0 | +| 2003-09 | SA#21 | SP-030381 | 001 | 1 | Rg reference point compliance with Liberty Alliance Project ID-WSF | 6.0.0 | 6.1.0 | +| 2003-09 | SA#21 | SP-030381 | 002 | 1 | Introduction of discovery service | 6.0.0 | 6.1.0 | +| 2003-09 | SA#21 | SP-030381 | 003 | 1 | Corrections to Rg reference point descriptions | 6.0.0 | 6.1.0 | +| 2003-09 | SA#21 | SP-030381 | 004 | 1 | Removal of GMLC as example | 6.0.0 | 6.1.0 | +| 2003-12 | SA#22 | SP-030659 | 007 | 1 | Selection of the GUP Server mode of operation | 6.1.0 | 6.2.0 | +| 2003-12 | SA#22 | SP-030659 | 009 | 1 | Notification Reference | 6.1.0 | 6.2.0 | +| 2003-12 | SA#22 | SP-030659 | 010 | 2 | Subscribe Operation, Subscription Status | 6.1.0 | 6.2.0 | +| 2003-12 | SA#22 | SP-030659 | 011 | 1 | GUP information model improvement | 6.1.0 | 6.2.0 | +| 2003-12 | SA#22 | SP-030659 | 012 | 1 | GUP Annex B terminal Capability negotiation for IMS | 6.1.0 | 6.2.0 | +| 2004-03 | SA#23 | SP-040038 | 006 | 4 | Adding a listing function | 6.2.0 | 6.3.0 | +| 2004-03 | SA#23 | SP-040038 | 013 | 2 | Rg reference point alignment with Liberty ID-WSF | 6.2.0 | 6.3.0 | +| 2004-03 | SA#23 | SP-040038 | 014 | | Generalizing the subscriber identity term to resource identity | 6.2.0 | 6.3.0 | +| 2004-03 | SA#23 | SP-040038 | 015 | 1 | Authorization enhancements | 6.2.0 | 6.3.0 | +| 2004-03 | SA#23 | SP-040038 | 016 | | Authorization model alignment with GUP Information Model | 6.2.0 | 6.3.0 | +| 2004-06 | SA#24 | SP-040321 | 017 | 1 | GUP Server in Home operator network | 6.3.0 | 6.4.0 | +| 2004-06 | SA#24 | SP-040321 | 018 | 1 | Rp Intra-operator interface | 6.3.0 | 6.4.0 | +| 2004-06 | SA#24 | SP-040321 | 019 | 1 | GUP Authentication failure | 6.3.0 | 6.4.0 | +| 2004-06 | SA#24 | SP-040321 | 020 | | Removal of editor's note on existing profile components | 6.3.0 | 6.4.0 | +| 2004-06 | SA#24 | SP-040321 | 021 | 1 | Addition of an example in Annex A | 6.3.0 | 6.4.0 | +| 2004-06 | SA#24 | SP-040321 | 022 | 2 | Clarification of requirement for component location management | 6.3.0 | 6.4.0 | +| 2004-09 | SA#25 | SP-040525 | 024 | 1 | Addition of missing security aspects | 6.4.0 | 6.5.0 | +| 2004-12 | SA#26 | SP-040757 | 025 | | Removal of UE as GUP Data Repository | 6.5.0 | 6.6.0 | +| 2005-03 | SA#27 | SP-050109 | 026 | | Use of Discovery Service as Trusted Authority | 6.6.0 | 6.7.0 | +| 2007-06 | SP-36 | - | - | - | Update to Rel-7 version (MCC) | 6.7.0 | 7.0.0 | +| 2008-12 | SP-42 | - | - | - | Update to Rel-8 version (MCC) | 7.0.0 | 8.0.0 | +| 2008-12 | SP-46 | - | - | - | Update to Rel-9 version (MCC) | 8.0.0 | 9.0.0 | +| 2011-03 | SP-51 | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | SP-65 | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2015-12 | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | - | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | +| 2018-06 | SP-80 | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | SP-88E | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23246/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Rel-16/23_series/23246/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01ba65fc169d6d72d0b92e40e411d87b6c7936fd --- /dev/null +++ b/marked/Rel-16/23_series/23246/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b567762a08dbe52f64f861c35b34a00796858981416a872aa4a013c20ac0333c +size 43093 diff --git a/marked/Rel-16/23_series/23246/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-16/23_series/23246/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5b82a04634377bc350c8bf834e79eba83d9f819 --- /dev/null +++ b/marked/Rel-16/23_series/23246/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8216799ec4dc1168fb11d2f08728eb9057d6d7720582478cca21c6c6ee66d8d2 +size 68771 diff --git a/marked/Rel-16/23_series/23246/0997dbaa9dfecedd60029d70b53327b8_img.jpg b/marked/Rel-16/23_series/23246/0997dbaa9dfecedd60029d70b53327b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a47fa9c5045402608e1e76b184f4ab02ef0265bc --- /dev/null +++ b/marked/Rel-16/23_series/23246/0997dbaa9dfecedd60029d70b53327b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1d9c6d379a918d9ae24a603e9a7d6e4d7cfa7d32cbf28c1544091b97abf07d6 +size 66740 diff --git a/marked/Rel-16/23_series/23246/0f1767577a073167eb9628d72034e083_img.jpg b/marked/Rel-16/23_series/23246/0f1767577a073167eb9628d72034e083_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60e8fe79dcbb5ade95da640f60806522830352c5 --- /dev/null +++ b/marked/Rel-16/23_series/23246/0f1767577a073167eb9628d72034e083_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e641242253e83579dc81267623688fdb81d372e9fc297b8438571309244555e5 +size 46714 diff --git a/marked/Rel-16/23_series/23246/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23246/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..293589d66838d46e8981e1d22b20aa5c645ae72e --- /dev/null +++ b/marked/Rel-16/23_series/23246/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ecda2198eac67f3c08e2dc1241c9d7cc0a98b9408445be83f2ca39c922c13af +size 21250 diff --git a/marked/Rel-16/23_series/23246/382a9c9e4816bd229191ab4591424dd8_img.jpg b/marked/Rel-16/23_series/23246/382a9c9e4816bd229191ab4591424dd8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..df0caf55f95a2e1635ddea83d8cebf8a4bf85623 --- /dev/null +++ b/marked/Rel-16/23_series/23246/382a9c9e4816bd229191ab4591424dd8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49b56bc24ac1a968be9d898285a1257ba97c5b3c51f5d269841d4d2ef7948486 +size 109279 diff --git a/marked/Rel-16/23_series/23246/39536a630fa74c3bcfd1670ee2152809_img.jpg b/marked/Rel-16/23_series/23246/39536a630fa74c3bcfd1670ee2152809_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa8aaf2948052e6adf88afd2c722c808f3fce7b1 --- /dev/null +++ b/marked/Rel-16/23_series/23246/39536a630fa74c3bcfd1670ee2152809_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77ecdc4d02923f2c51452e3876dfaf0dfbdcd6465e52b6cc8d3db8e83dbd57d3 +size 14310 diff --git a/marked/Rel-16/23_series/23246/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/23_series/23246/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..385160c4c3893d6b13abd9ee63642f460a5cfc2a --- /dev/null +++ b/marked/Rel-16/23_series/23246/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:035d32e42547b069ee06e6e5bfafda5df37aee83154b06ede95e3ed117a2a57f +size 118255 diff --git a/marked/Rel-16/23_series/23246/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23246/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ec78fb40dbb3d7b083f557dd8f0dde42f268df5 --- /dev/null +++ b/marked/Rel-16/23_series/23246/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:523776e1c3110ee43c2f3f29dccbb3f4751be3665da033c3058e02fefe378891 +size 101399 diff --git a/marked/Rel-16/23_series/23246/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/23_series/23246/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a7103cf891cba4cf4013f5ad93ee24e0755032a0 --- /dev/null +++ b/marked/Rel-16/23_series/23246/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a33295a90818e5b6fac67ae028dce8a9cac0bea52abe26a5bfd6e50b74da7fd +size 103565 diff --git a/marked/Rel-16/23_series/23246/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/23_series/23246/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88ca813d77ba5a0a961036c3b9b9326f7ee0c424 --- /dev/null +++ b/marked/Rel-16/23_series/23246/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6d15789b37d0a60a5c72dcbf4ed1dd35170b5bc611a8476ff14873cdb23895e +size 174124 diff --git a/marked/Rel-16/23_series/23246/822e033872d5ab16e861571f47b81ba7_img.jpg b/marked/Rel-16/23_series/23246/822e033872d5ab16e861571f47b81ba7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..52159ce999c5b008d18e4f2e0d725229ce4ac73f --- /dev/null +++ b/marked/Rel-16/23_series/23246/822e033872d5ab16e861571f47b81ba7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f0af6cad9930bb46494c4796d45faf579c3ef0affdbde3ba33ec72e3d5dfea74 +size 63611 diff --git a/marked/Rel-16/23_series/23246/8269648391c59363ea61243864a2adf7_img.jpg b/marked/Rel-16/23_series/23246/8269648391c59363ea61243864a2adf7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..91cf6b9a10e54603c30cbe5a1836b57ac842d865 --- /dev/null +++ b/marked/Rel-16/23_series/23246/8269648391c59363ea61243864a2adf7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd436d8fbae955219164bf21bff2bcad7f0081a7fe280bdbea9233a9b2ba5f45 +size 68877 diff --git a/marked/Rel-16/23_series/23246/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23246/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a92fbee7a51904ad15559e6ed23aa8f6eea0ee75 --- /dev/null +++ b/marked/Rel-16/23_series/23246/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:78ad0c99083aee1e7e6242ddad77508b1028ae2783db5e70dcb4d398af556c45 +size 61426 diff --git a/marked/Rel-16/23_series/23246/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/marked/Rel-16/23_series/23246/9a14684f8ae1345c6efea6f5994c730c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5dbf0ef46921e6f937b13c82d6dc12acbd7c88d9 --- /dev/null +++ b/marked/Rel-16/23_series/23246/9a14684f8ae1345c6efea6f5994c730c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ae4df46f48417e16a24ace6f304ce2401a35f52072b54aa3060b74e17917213a +size 68100 diff --git a/marked/Rel-16/23_series/23246/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/23_series/23246/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c96128a82e8d51c54d5a06f52ea4c4b35d52f25b --- /dev/null +++ b/marked/Rel-16/23_series/23246/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cca8790cb06eb03abe0e73d68be1d0def5e864902726340ff5e210baa724720d +size 159403 diff --git a/marked/Rel-16/23_series/23246/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg b/marked/Rel-16/23_series/23246/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0eed629cf556d1a49b7e2610020c5e0a018b2837 --- /dev/null +++ b/marked/Rel-16/23_series/23246/9cbc1ebd80813fc36e499f7d70ed6881_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1741bca8bf2abc6acef0c95387fd2f9f1e74417fd72261f11732339eaa37f78 +size 57081 diff --git a/marked/Rel-16/23_series/23246/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/23_series/23246/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9f2c941cbb387550ec17a24a72cd850bbf80f99 --- /dev/null +++ b/marked/Rel-16/23_series/23246/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:42efd32142abd5ab5ca9eb878b29f1c8d2a4da3cd876d849999a711765cc7f42 +size 40621 diff --git a/marked/Rel-16/23_series/23246/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/marked/Rel-16/23_series/23246/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..399209f2c7fe6ad866e29b83b31b861af07b88e7 --- /dev/null +++ b/marked/Rel-16/23_series/23246/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e057894fd4d3f8b573a7cf6271162627534abb62a5c0c1bdbe81dfd663974fb6 +size 60479 diff --git a/marked/Rel-16/23_series/23246/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23246/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..642fe48e52a954f00e18918254cee813f59e19e5 --- /dev/null +++ b/marked/Rel-16/23_series/23246/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:711db63dfcccce03437ea7508e2ccea5cb78de0f090f66252355c3cb7b70a72e +size 105090 diff --git a/marked/Rel-16/23_series/23246/a4bfa2343d75076b79f7e33d93915e00_img.jpg b/marked/Rel-16/23_series/23246/a4bfa2343d75076b79f7e33d93915e00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cbfe55edfa21e8b4bb15e56040e88870336cb7a6 --- /dev/null +++ b/marked/Rel-16/23_series/23246/a4bfa2343d75076b79f7e33d93915e00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2442f51cd475ebc5af97bd4a7eb7940719e8f5b0d0311e9878e88c3a42800d6b +size 68995 diff --git a/marked/Rel-16/23_series/23246/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/23_series/23246/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae52261f08e77088d851dfccea7bce0825113eea --- /dev/null +++ b/marked/Rel-16/23_series/23246/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de85630854e56988313062ce76a5badc219a6d9fef897379140d316adff92c40 +size 57572 diff --git a/marked/Rel-16/23_series/23246/cc468dcda006ef315536400517a09ad3_img.jpg b/marked/Rel-16/23_series/23246/cc468dcda006ef315536400517a09ad3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..218eae2abc0e2f3ae370f00ea5c46920e4bec31a --- /dev/null +++ b/marked/Rel-16/23_series/23246/cc468dcda006ef315536400517a09ad3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d44bb33ee977f8ba564669a19aa6a9959cf689d4c6fbe7a9cd97467c6714133 +size 80353 diff --git a/marked/Rel-16/23_series/23246/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg b/marked/Rel-16/23_series/23246/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f1b8e3a8cc98b4704fa6ffe69e6377e5fabed8e7 --- /dev/null +++ b/marked/Rel-16/23_series/23246/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a16b41337a90e5f71223aee07fd3748b682ef6f286c7db3765bde8ac486d20c +size 65661 diff --git a/marked/Rel-16/23_series/23246/db5deafdae53dbc7d5972957f708c691_img.jpg b/marked/Rel-16/23_series/23246/db5deafdae53dbc7d5972957f708c691_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9e8ef1b3a15c59e86d8d9c27256d5cb9803eba34 --- /dev/null +++ b/marked/Rel-16/23_series/23246/db5deafdae53dbc7d5972957f708c691_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b452946e64287bc38b22fe1319e001e2d909dcd0f8d1f615f6da3bade9009ec2 +size 15989 diff --git a/marked/Rel-16/23_series/23246/e636d7ccca0ad14c6b95201404324823_img.jpg b/marked/Rel-16/23_series/23246/e636d7ccca0ad14c6b95201404324823_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e21ba066376526b36e264dfee9dfc3d6d0a6ef06 --- /dev/null +++ b/marked/Rel-16/23_series/23246/e636d7ccca0ad14c6b95201404324823_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c33bd0c4792f85fbdc60ea7708ed649e4517894d468c72547ced0a7e9e2b725 +size 44986 diff --git a/marked/Rel-16/23_series/23246/e94cbc0895c6914a2bb53f150ab7495e_img.jpg b/marked/Rel-16/23_series/23246/e94cbc0895c6914a2bb53f150ab7495e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5900c711c708e518270486522db30c4a20279d17 --- /dev/null +++ b/marked/Rel-16/23_series/23246/e94cbc0895c6914a2bb53f150ab7495e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a67d4ed831c9719e98c3e9fee02aeeac5d3e4b9f920086a8b6d65560623f9823 +size 62050 diff --git a/marked/Rel-16/23_series/23246/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg b/marked/Rel-16/23_series/23246/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97a5282afce74b272c64189011b50ad6a5bb4300 --- /dev/null +++ b/marked/Rel-16/23_series/23246/fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c1ddb53d019a1092491a62dd26ef49b7f07fe6353a160e0fa1fe79b016ec2d1d +size 47205 diff --git a/marked/Rel-16/23_series/23246/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23246/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..878b243528ea15f612c76639b1b431a169a4013f --- /dev/null +++ b/marked/Rel-16/23_series/23246/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03fda5a27eb4b51c396c041c0e8531156a45721622ea021b3048cf02d929c001 +size 87112 diff --git a/marked/Rel-16/23_series/23246/raw.md b/marked/Rel-16/23_series/23246/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..49df730c3a081dc973b2156541107fcee85f284e --- /dev/null +++ b/marked/Rel-16/23_series/23246/raw.md @@ -0,0 +1,2622 @@ + + + + + + +# Contents + +| | | +|----------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 9 | +| 4 MBMS Architecture..... | 9 | +| 4.1 Overview ..... | 9 | +| 4.2 Reference Architecture Model ..... | 10 | +| 4.2.1 GPRS ..... | 10 | +| 4.2.2 EPS ..... | 10 | +| 4.3 MBMS Specific Reference points..... | 11 | +| 4.3.1 Gmb ..... | 11 | +| 4.3.1a SGmb..... | 11 | +| 4.3.2 Mz..... | 11 | +| 4.3.3 Reference Points for Evolved Packet System..... | 12 | +| 4.4 MBMS Service Provision..... | 12 | +| 4.4.1 MULTICAST MODE ..... | 12 | +| 4.4.1.1 Subscription ..... | 14 | +| 4.4.1.2 Service announcement..... | 14 | +| 4.4.1.3 Joining..... | 15 | +| 4.4.1.4 Session Start..... | 15 | +| 4.4.1.5 MBMS notification..... | 15 | +| 4.4.1.6 Data transfer..... | 15 | +| 4.4.1.7 Session Stop..... | 15 | +| 4.4.1.8 Leaving ..... | 15 | +| 4.4.2 Multicast Mode timeline..... | 15 | +| 4.4.2.1 Period between Service Announcement and Session Start..... | 15 | +| 4.4.2.2 Period between Service Announcement and Service Subscription ..... | 15 | +| 4.4.2.3 Period between Service Announcement and Joining..... | 16 | +| 4.4.2.4 Period between Joining and Session Start ..... | 16 | +| 4.4.2.5 Period between Session Start and First Data Arrival..... | 16 | +| 4.4.2.6 Period between Session Start and Session Stop..... | 16 | +| 4.4.2.7 Session Update..... | 16 | +| 4.4.3 BROADCAST MODE ..... | 16 | +| 4.4.3.1 Service announcement ..... | 18 | +| 4.4.3.1a UE local service activation ..... | 18 | +| 4.4.3.2 Session Start..... | 18 | +| 4.4.3.3 MBMS notification..... | 18 | +| 4.4.3.4 Data transfer..... | 18 | +| 4.4.3.5 Session Stop..... | 19 | +| 4.4.3.6 Session Update..... | 19 | +| 4.4.4 Broadcast Mode timeline..... | 19 | +| 4.4.4.1 Period between Service Announcement and Session Start..... | 19 | +| 4.4.4.2 Period between Session Start and First Data Arrival..... | 19 | +| 4.4.4.3 Period between Session Start and Session Stop..... | 19 | +| 5 Functional Entities To Support MBMS ..... | 19 | +| 5.0 General ..... | 19 | +| 5.1 Broadcast-Multicast Service Centre (BM-SC)..... | 19 | +| 5.1.0 General ..... | 19 | +| 5.1.1 Membership Function..... | 20 | +| 5.1.2 Session and Transmission Function ..... | 20 | +| 5.1.3 Proxy and Transport Function ..... | 21 | +| 5.1.4 Service Announcement Function ..... | 21 | +| 5.1.4a MBMS Security Function..... | 22 | + +| | | | +|---------|------------------------------------------------------------------------------------------------|----| +| 5.1.5 | MBMS Content Transfer for the same MBMS User Service for GPRS and EPS ..... | 22 | +| 5.1.5.1 | General..... | 22 | +| 5.1.5.2 | Separate MBMS Bearer Services for the same MBMS User Service ..... | 22 | +| 5.1.5.3 | Same MBMS Bearer Service for the same MBMS User Service..... | 23 | +| 5.1.6 | Location Dependent Content Transfer for the same MBMS User Service (Broadcast Mode only) ..... | 23 | +| 5.1.7 | MBMS User Service Consumption Reporting (Broadcast mode only) ..... | 23 | +| 5.2 | User Equipment..... | 24 | +| 5.3 | UTRAN/GERAN ..... | 24 | +| 5.4 | SGSN..... | 24 | +| 5.5 | GGSN ..... | 25 | +| 5.6 | MBMS Data Sources and Content Provider ..... | 25 | +| 5.7 | Other Functional Element ..... | 25 | +| 5.7.1 | Void ..... | 25 | +| 5.7.2 | CBC ..... | 26 | +| 5.7.3 | Void ..... | 26 | +| 5.8 | Void..... | 26 | +| 5.9 | Functional Elements for the Evolved Packet System..... | 26 | +| 5.9.1 | MBMS GW ..... | 26 | +| 5.9.2 | MBMS Control plane function..... | 27 | +| 5.9.3 | E-UTRAN..... | 27 | +| 6 | MBMS Attributes and Parameters ..... | 27 | +| 6.1 | MBMS UE Context..... | 27 | +| 6.2 | MBMS Bearer Context..... | 28 | +| 6.3 | Quality-of-Service ..... | 31 | +| 6.3.1 | Quality-of-Service for GPRS ..... | 31 | +| 6.3.2 | Quality-of-Service for EPS..... | 32 | +| 6.3.3 | MBMS QoS distribution tree..... | 33 | +| 6.4 | Temporary Mobile Group Identity ..... | 34 | +| 6.5 | IP Multicast distribution..... | 34 | +| 6.5.1 | General ..... | 34 | +| 6.5.2 | IP Multicast distribution for GERAN Iu-mode and UTRAN for GPRS..... | 34 | +| 6.5.3 | IP Multicast distribution for E-UTRAN and UTRAN for EPS..... | 35 | +| 7 | Architectural Aspects of MBMS User Services ..... | 35 | +| 7.1 | Alternative User Service Support..... | 36 | +| 7.2 | Avoid overload in SGSN, GGSN and BM-SC caused by Joining..... | 36 | +| 7.3 | Access aspects of MBMS user services ..... | 36 | +| 7.4 | MBMS operation on Demand..... | 36 | +| 7.5 | Enhanced TV services support over E-UTRAN ..... | 36 | +| 8 | MBMS Procedures..... | 37 | +| 8.1 | MBMS Notification..... | 37 | +| 8.1.1 | Iu mode notification (UTRAN and GERAN) for GPRS ..... | 37 | +| 8.1.2 | A/Gb mode notification (GERAN) ..... | 38 | +| 8.2 | MBMS Multicast Service Activation..... | 38 | +| 8.2.1 | Void ..... | 40 | +| 8.3 | MBMS Session Start Procedure ..... | 40 | +| 8.3.0 | General ..... | 40 | +| 8.3.1 | MBMS Session Start Procedure for GERAN and UTRAN for GPRS ..... | 41 | +| 8.3.2 | MBMS Session Start Procedure for E-UTRAN and UTRAN for EPS..... | 42 | +| 8.4 | MBMS Registration Procedure ..... | 45 | +| 8.5 | MBMS Session Stop Procedure ..... | 47 | +| 8.5.0 | General ..... | 47 | +| 8.5.1 | MBMS Session Stop Procedure for GERAN and UTRAN for GPRS..... | 47 | +| 8.5.2 | MBMS Session Stop Procedure for E-UTRAN and UTRAN for EPS ..... | 48 | +| 8.6 | MBMS De-Registration Procedure ..... | 49 | +| 8.6.0 | Common MBMS De-Registration procedure..... | 49 | +| 8.6.1 | BM-SC initiated MBMS De-Registration Procedure..... | 50 | +| 8.7 | MBMS Multicast Service Deactivation ..... | 51 | +| 8.8 | MBMS Session Update procedure..... | 53 | +| 8.8.1 | General ..... | 53 | +| 8.8.2 | SGSN initiated Session Update for GERAN and UTRAN for MBMS Multicast service ..... | 54 | + +| | | | +|-------------------------------|------------------------------------------------------------------------------------------------------------------------|-----------| +| 8.8.3 | BM-SC initiated Session Update for GERAN and UTRAN for MBMS Broadcast service ..... | 54 | +| 8.8.4 | BM-SC initiated Session Update for EPS with E-UTRAN and UTRAN ..... | 55 | +| 8.9 | MBMS UE Context Synchronisation Procedure..... | 58 | +| 8.9a | MBMS feature support indication..... | 58 | +| 8.10 | Inter SGSN Routeing Area Update ..... | 59 | +| 8.10a | Inter-system Intra-SGSN change ..... | 60 | +| 8.11 | Inter SGSN Serving RNS Relocation Procedure ..... | 60 | +| 8.12 | MBMS Broadcast Service Activation..... | 62 | +| 8.13 | MBMS Broadcast service de-activation..... | 62 | +| 8.14 | Void..... | 62 | +| 8.15 | MBMS UE Linking/De-linking mechanism ..... | 62 | +| 8.16 | MBMS Service Request Procedure..... | 63 | +| 8.17 | Notification in case of parallel services ..... | 64 | +| 8.17.1 | Notification of incoming CS domain call during an ongoing MBMS session..... | 64 | +| 8.17.2 | Notification of additional MBMS session during an ongoing MBMS session ..... | 64 | +| 8.17.3 | Notification of Mobile Terminating PS data during an ongoing MBMS session ..... | 64 | +| 8.17.4 | Notification of MBMS session during an ongoing CS or PS domain "connection" ..... | 64 | +| 9 | Security ..... | 65 | +| 10 | Charging requirement ..... | 65 | +| 10.1 | General ..... | 65 | +| 10.2 | Bearer level charging for MBMS..... | 65 | +| 10.3 | Application level charging for MBMS..... | 65 | +| 10.4 | Generation of charging records in the VPLMN ..... | 66 | +| 11 | Roaming Support for MBMS user services ..... | 66 | +| 11.1 | Scenarios description..... | 66 | +| 11.2 | Scenario signalling flow..... | 66 | +| 11.2.1 | APN selection..... | 66 | +| Annex A (Informative): | Void..... | 68 | +| Annex B (Informative): | Void..... | 69 | +| Annex C (normative): | TV services delivery using unicast mode & switching between broadcast & unicast modes for E-UTRAN ..... | 70 | +| Annex D (normative): | Shared MBMS Network over E-UTRAN..... | 72 | +| D.1 | General..... | 72 | +| D.2 | Architecture..... | 72 | +| D.2.1 | Architecture for per PLMN MBSFN synchronization area ..... | 72 | +| D.2.2 | Reference Points..... | 73 | +| D.2.3 | UE Aspects..... | 74 | +| D.2.4 | TMGI for shared MBMS networks..... | 74 | +| Annex E (normative): | UE behaviour in Receive Only Mode ..... | 75 | +| Annex C (Informative): | Change history..... | 77 | + +# --- Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- 1 Scope + +The present document describes the stage 2 description (architectural solution and functionalities) for the MBMS Bearer Service, which includes, together with MBMS User Services defined in TS 26.346 [7], all the elements necessary to realise the stage 1 requirements in TS 22.146 [2] and TS 22.246 [6]. This document encompasses both GPRS and EPS. + +The present document also includes considerations on the manner in which User Services should make use of the MBMS Bearer Service described herein. It should be noted that the specification of MBMS User Services in TS 26.346 [7] takes precedence over User Service aspects described in this document. + +The present document includes information applicable to network operators, service providers and manufacturers. + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.146: "Multimedia Broadcast/Multicast Service; Stage 1". +- [3] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture". +- [4] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)". +- [5] 3GPP TS 33.246: "Security of Multimedia Broadcast/Multicast Service". +- [6] 3GPP TS 22.246: "Multimedia Broadcast/Multicast Service (MBMS) user services". +- [7] 3GPP TS 26.346: "MBMS: Protocols and Codecs". +- [8] void. +- [9] void. +- [10] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network". +- [11] 3GPP TS 43.246: "Technical Specification Group GSM/EDGE Radio Access Network; Multimedia Broadcast Multicast Service (MBMS) in the GERAN". +- [12] 3GPP TS 23.125: "Overall high level functionality and architecture impacts of flow based charging; Stage 2". +- [13] 3GPP TS 23.003: "Numbering, addressing and identification". +- [14] 3GPP TS 32.422: "Subscriber and equipment trace; Trace control and Configuration Management (CM)". +- [15] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [16] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN Access". + +- [17] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN)". +- [18] 3GPP TS 25.446: "MBMS synchronisation protocol (SYNC)". +- [19] IETF RFC 3376: "Internet Group Management Protocol, Version 3". +- [20] IETF RFC 3810: "Multicast Listener Discovery Version 2 (MLDv2) for IPv6". +- [21] IETF RFC 4607: "Source-Specific Multicast for IP". +- [22] IETF RFC 4604: "Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source specific Multicast". +- [23] 3GPP TS 23.203: "Policy and charging control architecture". +- [24] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE)". +- [25] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures". +- [26] 3GPP TS 23.007: "Restoration procedures". +- [27] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE); MB2 reference point; Stage 3". +- [28] 3GPP TS 36.444: "M3 Application Protocol (M3AP)". +- [29] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications". +- [30] 3GPP TS 22.101: "Service aspects; Service principles". +- [31] 3GPP TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions defined in TR 21.905 [1] and TS 22.146 [2] and the following apply: + +**MBMS Service Announcement:** Mechanism to allow users to be informed about the MBMS user services available. + +**MBMS Bearer Service:** the service provided by the PS Domain to MBMS User Services to deliver IP multicast datagrams to multiple receivers using minimum network and radio resources. + +**MBMS User Service:** the MBMS service provided to the end user by means of the MBMS Bearer Service and possibly other capabilities. + +**MBMS Service Area:** The area within which data of a specific MBMS session are sent. Each individual MBMS session of an MBMS Bearer Service may be sent to a different MBMS Service Area. This MBMS Service Area is the same or a subset of the Multicast or Broadcast Service Area as defined in TS 22.146 [2]. An MBMS Service Area smaller than the Multicast or Broadcast Service Area is typically used for localized services. + +**MBMS over a Single Frequency Network:** See TS 25.346 [10]. + +**Receive Only Mode:** A UE configuration option that allows a UE to receive only eMBMS broadcast service without the need to access and register with the PLMN offering the eMBMS service. A UE configured to operate in Receive Only Mode receives MBMS service only on a standardised TMGI value range. The UE uses the acquired system information to receive MBMS broadcast. Use of Receive Only Mode does not require USIM for the UE. + +**Shared MBMS Network:** A network shared by multiple PLMNs that provides MBMS services. The Shared MBMS network consists of the following shared network elements: BM-SC(s) and MBMS-GW(s). The shared MBMS network may also include eNB(s), MCE(s), and shared MME(s) for MBMS operation. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations in TR 21.905 [1] and TS 22.146 [2] apply. + +| | | +|--------|------------------------------------------| +| EPS | Evolved Packet System | +| C-TEID | Common TEID | +| MBSFN | MBMS over a Single Frequency Network | +| MCE | Multi-cell/Multicast Coordination Entity | +| SSM | Source Specific Multicast | +| TMGI | Temporary Mobile Group Identity | +| TPF | Traffic Plane Function | +| SMN | Shared MBMS Network | + +# --- 4 MBMS Architecture + +## 4.1 Overview + +MBMS is a point-to-multipoint service in which data is transmitted from a single source entity to multiple recipients. Transmitting the same data to multiple recipients allows network resources to be shared. + +The MBMS bearer service offers two modes: + +- Broadcast Mode; +- Multicast Mode. + +Broadcast Mode is supported for EPS and GPRS, and Multicast Mode is supported for GPRS. MBMS for EPS supports E-UTRAN and UTRAN. MBMS for GPRS supports UTRAN and GERAN. + +MBMS architecture enables the efficient usage of radio-network and core-network resources, with an emphasis on radio interface efficiency. + +MBMS is realised by the addition of a number of new capabilities to existing functional entities of the 3GPP architecture and by addition of a number of new functional entities. + +The existing PS Domain functional entities (GGSN, SGSN, MME, E-UTRAN, UTRAN, GERAN and UE) are enhanced to provide the MBMS Bearer Service. In the EPS a functional entity MBMS GW exists at the edge between the CN and the BM-SC. In the bearer plane, this service provides delivery of IP Multicast datagrams from the Gi and SGi-mb reference points to UEs with a specified Quality of Service. In the control plane, this service provides mechanisms for: + +- managing the MBMS bearer service activation status of UEs (in the case of multicast mode); +- outsourcing authorisation decisions to the MBMS User Service (i.e. to the BM-SC) (in the case of multicast mode); +- providing control of session initiation/modification/termination by the MBMS User Service and managing bearer resources for the distribution of MBMS data (in the case or multicast and broadcast modes). + +A particular instance of the MBMS Bearer Service is identified by an IP Multicast Address and an APN Network Identifier. A TMGI also can be used to identify one MBMS Bearer Service inside one PLMN. + +For GPRS the boundary of the MBMS Bearer Service is the Gmb and Gi reference points as shown in Figure 1 below. The former provides access to the control plane functions and the latter the bearer plane. For EPS the boundary is the SGmb and the SGi-mb as shown in figure 1b below. + +A functional entity, the Broadcast Multicast Service Centre (BM-SC) provides a set of functions for MBMS User Services. BM-SC functions for different MBMS User Services may be supported from the same or different physical network elements. + +## 4.2 Reference Architecture Model + +### 4.2.1 GPRS + +![Reference architecture for GPRS to support the MBMS bearer service with GERAN and UTRAN. The diagram shows a UE connected to UTRAN (via Uu) and GERAN (via Um). UTRAN connects to SGSN (via Iu), which connects to HLR (via Gr) and GGSN TPF (via Gn/Gp). GERAN connects to SGSN (via Iu/Gb) and GGSN TPF (via Gmcc). GGSN TPF connects to BM-SC (via Gmb). BM-SC connects to Content Provider / Multicast Broadcast Source (via Gi) and to Other PLMN (via Mz). A dashed line separates the internal network from the PDN (e.g., Internet).](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +Reference architecture for GPRS to support the MBMS bearer service with GERAN and UTRAN. The diagram shows a UE connected to UTRAN (via Uu) and GERAN (via Um). UTRAN connects to SGSN (via Iu), which connects to HLR (via Gr) and GGSN TPF (via Gn/Gp). GERAN connects to SGSN (via Iu/Gb) and GGSN TPF (via Gmcc). GGSN TPF connects to BM-SC (via Gmb). BM-SC connects to Content Provider / Multicast Broadcast Source (via Gi) and to Other PLMN (via Mz). A dashed line separates the internal network from the PDN (e.g., Internet). + +Note 1: Network entities and reference points solely used by the MBMS user service (e.g. for service announcement as described in clause 4.4.1.2) are not shown in this figure. + +Note 2: Gp applies only when SGSN and GGSN are in different PLMNs. + +Note 3: the Iu/Gn reference point above is a direct tunnel according to clause 5.6.2.2, figure 6b in TS 23.060 [15] with IP multicast based addressing according to RFC 4607 [21]. + +**Figure 1a: Reference architecture for GPRS to support the MBMS bearer service with GERAN and UTRAN** + +### 4.2.2 EPS + +![Reference architecture for Evolved Packet System with E-UTRAN and UTRAN (MBMS Broadcast Mode only). The diagram shows a UE connected to E-UTRAN (via Uu) and UTRAN (via Uu). E-UTRAN connects to MME (via M3) and MBMS GW (via M1). UTRAN connects to SGSN (via Iu), which connects to MBMS GW (via Sn). MME connects to PDN Gateway (via Sm). PDN Gateway connects to MBMS Bearer Service (via SGi). MBMS GW connects to MBMS Bearer Service (via SGmb) and MBMS User Service (via SGi-mb). MBMS Bearer Service and MBMS User Service are part of the BM-SC, which connects to Content Provider.](fc69ceb1dee1da7e33bd6c38fc4ceab9_img.jpg) + +Reference architecture for Evolved Packet System with E-UTRAN and UTRAN (MBMS Broadcast Mode only). The diagram shows a UE connected to E-UTRAN (via Uu) and UTRAN (via Uu). E-UTRAN connects to MME (via M3) and MBMS GW (via M1). UTRAN connects to SGSN (via Iu), which connects to MBMS GW (via Sn). MME connects to PDN Gateway (via Sm). PDN Gateway connects to MBMS Bearer Service (via SGi). MBMS GW connects to MBMS Bearer Service (via SGmb) and MBMS User Service (via SGi-mb). MBMS Bearer Service and MBMS User Service are part of the BM-SC, which connects to Content Provider. + +**Figure 1b: Reference architecture for Evolved Packet System with E-UTRAN and UTRAN (MBMS Broadcast Mode only)** + +NOTE 1: In addition to MBMS Bearers (over SGmb/SGi-mb), the BM-SC may use EPS Bearers (over SGi) to realize an MBMS User Service as specified in TS 26.346 [7]. + +NOTE 2: The MCE (see TS 36.300 [17]) is not shown in the figure. + +NOTE 3: MBMS service over Gn-SGSN is supported when the MBMS-GW is co-located with the PDN GW and this PDN GW has the necessary GGSN functions to control the MBMS Bearer Service over Gn. + +## 4.3 MBMS Specific Reference points + +### 4.3.1 Gmb + +Signalling between GGSN and BM-SC is exchanged at Gmb reference point. This represents the network side boundary of the MBMS Bearer Service from a control plane perspective. This includes user specific Gmb signalling and MBMS bearer service specific signalling. + +MBMS bearer service specific Gmb signalling: + +- The GGSN establishes the MBMS bearer context and registers at BM-SC. +- The GGSN or the BM-SC releases the MBMS bearer context and de-registers the GGSN from the BM-SC. +- The BM-SC indicates session start, update and stop to the GGSN including session attributes like QoS and MBMS service area. + +User specific Gmb signalling: + +- The BM-SC authorises the user specific MBMS multicast service activation (join) at the GGSN. +- The GGSN reports to the BM-SC the successful user specific MBMS multicast activation (join) to allow the BM-SC to synchronise the BM-SC MBMS UE context with the MBMS UE contexts in the SGSN and GGSN. +- The GGSN reports to the BM-SC when a user specific MBMS multicast service is released or deactivated (e.g. at implicit detach). The GGSN makes this report in order to synchronise the BM-SC MBMS UE context with the MBMS UE contexts in the SGSN and GGSN. + +The BM-SC initiates the deactivation of a user specific MBMS bearer service when the MBMS user service is terminated. + +BM-SC functions for different MBMS bearer services may be provided by different physical network elements. Further, MBMS bearer service specific and user specific signalling for the same MBMS bearer service may also be provided by different physical network elements. To allow this distribution of BM-SC functions, the Gmb protocol must support the use of proxies to correctly route the different signalling interactions in a manner which is transparent to the GGSN. + +### 4.3.1a SGmb + +The SGmb reference point has similar functions with the Gmb interface in control plane except for the Multicast Mode related functions. Specifically, + +MBMS bearer service specific SGmb signalling: + +- The BM-SC indicates session start, update and stop to the MBMS-GW including session attributes like QoS and MBMS service area, and some of attributes may be different from them in Gmb. + +### 4.3.2 Mz + +Mz is the roaming variant of the Gmb reference point with the same functionality as described under Gmb, i.e. with MBMS bearer and User specific signalling. + +MBMS bearer and User specific Mz signalling is used between a BM-SC in the visited PLMN and a BM-SC in the home PLMN when MBMS services from the home PLMN are offered by the visited PLMN. + +User specific signalling is used between a BM-SC in the visited PLMN and a BM-SC in the home PLMN when the visited PLMN offers MBMS user services to roaming users. This user specific Mz signalling provides home PLMN authorisation for MBMS user services that are provided by the visited PLMN. This mechanism supports only MBMS user service classes that are offered by the visited and by the home PLMN. + +Mz may use proxying capabilities as described for Gmb, e.g. to proxy signalling between BM-SCs. An APN may be included in the signalling between BM-SCs, which is used to select an appropriate GGSN to access the MBMS service aiming for an optimized routing, resource saving, or operator policy. + +NOTE: For EPS, the Mz reference point is not supported in this release. + +### 4.3.3 Reference Points for Evolved Packet System + +NOTE: The below listed reference points are applicable for the E-UTRAN and UTRAN MBMS Broadcast Mode (with or without counting) only. + +- M1:** It is the reference point between MBMS GW and E-UTRAN/UTRAN for MBMS data delivery. IP Multicast is used on this interface to forward data. +- M3:** It is the reference point for the control plane between MME and E-UTRAN. +- Sm:** It is the reference point for the control plane between MME and MBMS GW. +- Sn:** It is the reference point between MBMS GW and SGSN (S4 based) for the control plane and for MBMS data delivery. Point-to-point mode is used on this interface to forward data.. +- SGi-mb:** It is the reference point between BM-SC and MBMS GW function for MBMS data delivery. +- SGmb:** It is the reference point for the control plane between BM-SC and MBMS GW. + +Protocol assumption: + +- The Sm reference point is based on GTPv2-C. +- The Sn reference point is based on GTPv2-C and GTPv1-U. +- The M1 reference point is based on GTPv1-U. + +## 4.4 MBMS Service Provision + +### 4.4.1 MULTICAST MODE + +Reception of an MBMS MULTICAST service is enabled by certain procedures that are illustrated in the Figure below. + +![A vertical flowchart showing the phases of MBMS Multicast service provision. The phases are: Subscription, Service announcement, Joining, Session start, MBMS notification, Data transfer, Session Stop, and Leaving. A large blue downward-pointing arrow is at the bottom.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` +graph TD; A[Subscription] --> B[Service announcement]; B --> C[Joining]; C --> D[Session start]; D --> E[MBMS notification]; E --> F[Data transfer]; F --> G[Session Stop]; G --> H[Leaving]; H --> I[Large Blue Downward Arrow] +``` + +A vertical flowchart showing the phases of MBMS Multicast service provision. The phases are: Subscription, Service announcement, Joining, Session start, MBMS notification, Data transfer, Session Stop, and Leaving. A large blue downward-pointing arrow is at the bottom. + +**Figure 2: Phases of MBMS Multicast service provision** + +The phases subscription, joining and leaving are performed individually per user. The other phases are performed for a service, i.e. for all users interested in the related service. The sequence of phases may repeat, e.g. depending on the need to transfer data. Also subscription, joining, leaving, service announcement as well as MBMS notification may run in parallel to other phases. + +This is illustrated with the following example of timeline: + +![Figure 3: Timeline example. A sequence diagram showing the interaction between UE1, UE2, Service 1, and the Transfer of data over time. UE1 and UE2 have events for subscription and service join/leave. Service 1 has events for start/stop announcements and sessions. The bottom bar shows data transfer blocks for UE1 and UE2. Callouts indicate that subscription and service join can happen at any time, and red 'X' marks indicate that service leave and stop announcement cannot occur while a session is active.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +The diagram illustrates a timeline example for MBMS service delivery. It consists of four horizontal timelines: UE1 events, UE2 events, Service 1 events, and Transfer of data. + +UE1 events: A black dot for 'subscription to service1' and a green dot for 'User service join'. A red 'X' over a red dot indicates a 'service leave' event is invalid while a session is active. + +UE2 events: A black dot for 'subscription to service1' and a green dot for 'User service join'. A red 'X' over a red dot indicates a 'service leave' event is invalid while a session is active. + +Service 1 events: A blue circle for 'Start Service 1 announcement', a green dot for '1st Session start', a red dot for '1st session stop', a green dot for 'Service 1 Session 2', and a blue circle for 'Stop Service 1 announcement'. + +Transfer of data: A blue bar at the bottom shows data transfer blocks. Callouts indicate: 'Data sent to UE1', 'Data sent to UE1 and UE2', 'Data sent to UE1 and UE2', and 'Data sent to UE2'. + +Timing: A dashed green line indicates an 'Idle period of seconds' between the start of the first session and the first data transfer. Green double-headed arrows indicate 'Data transfer' periods. A black double-headed arrow labeled 'Service 1 session1' spans from the first session start to the first session stop. + +Callouts: 'Subscription can be at any time' and 'Service join by the user can be at any time' point to the initial events on the UE timelines. Red 'X' marks indicate that service leave and stop announcement cannot occur while a session is active. + +Figure 3: Timeline example. A sequence diagram showing the interaction between UE1, UE2, Service 1, and the Transfer of data over time. UE1 and UE2 have events for subscription and service join/leave. Service 1 has events for start/stop announcements and sessions. The bottom bar shows data transfer blocks for UE1 and UE2. Callouts indicate that subscription and service join can happen at any time, and red 'X' marks indicate that service leave and stop announcement cannot occur while a session is active. + +Figure 3: Timeline example + +#### 4.4.1.1 Subscription + +Establishes the relationship between the user and the service provider, which allows the user to receive the related MBMS multicast service. + +Service Subscription is the agreement of a user to receive service(s) offered by the operator. Subscription information is recorded in the BM-SC. Subscription information and other BM-SC functionality may be on separate entities, which is enabled by proxy capability of the Gmb interface. + +NOTE: procedures for the subscription phase are out of scope of this specification. + +#### 4.4.1.2 Service announcement + +MBMS user service announcement/discovery mechanisms shall allow users to request or be informed about the range of MBMS user services available. This includes operator specific MBMS user services as well as services from content providers outside of the PLMN. Service announcement is used to distribute to users information about the service, parameters required for service activation (e.g. IP multicast address(es)) and possibly other service related parameters (e.g. service start time). + +Operators/service providers may consider several service discovery mechanisms. This could include standard mechanisms such as SMS, or depending on the capability of the terminal, applications that encourage user interrogation. The method chosen to inform users about MBMS user services may have to account for the user's location, (e.g. current cell, in the HPLMN or VPLMN). Users who have not already subscribed to a MBMS user service should also be able to discover MBMS user services. + +The following could be considered useful for MBMS user service announcement mechanisms (not exhaustive): + +- SMS Cell Broadcast to advertise MBMS Multicast and Broadcast user services; +- MBMS Broadcast mode to advertise MBMS Multicast and Broadcast user Services; +- MBMS Multicast mode to advertise MBMS Multicast user Services; + +- PUSH mechanism (WAP, SMS-PP, MMS); +- URL (HTTP, FTP). + +The details of the MBMS service announcement mechanisms are out of scope of this specification, but MBMS shall allow the utilisation of solutions using IETF protocols. + +Service announcement is further defined within MBMS User Service specifications TS 26.346 [7]. + +#### 4.4.1.3 Joining + +Joining (i.e. MBMS multicast activation by the user) is the process by which a subscriber joins (becomes a member of) a multicast group, i.e. the user indicates to the network that he/she wants to receive Multicast mode data of a specific MBMS bearer service. An MBMS user service may also be carried by more than one MBMS bearer service. In that case the MBMS user service part in the UE initiates the relevant MBMS bearer services to receive the service (see clause 8.2). + +#### 4.4.1.4 Session Start + +Session Start is the point at which the BM-SC is ready to send data. This can be identified with the start of a "Multicast session" as defined in TS 22.146 [2]. Session Start occurs independently of activation of the service by the user – i.e. a given user may activate the service before or after Session Start. Session Start is the trigger for bearer resource establishment for MBMS data transfer. If an MBMS user service is carried by more than one MBMS bearer service, a Session Start message is sent for each MBMS bearer service. In that case the UE may need to initiate the reception of multiple relevant MBMS bearer services to receive the MBMS user service. + +#### 4.4.1.5 MBMS notification + +Informs the UEs about forthcoming (and potentially about ongoing) MBMS multicast data transfer. + +#### 4.4.1.6 Data transfer + +It is the phase when MBMS data are transferred to the UEs. + +#### 4.4.1.7 Session Stop + +It is the point at which the BM-SC determines that there will be no more data to send for some period of time – this period being long enough to justify removal of bearer resources associated with the session. At Session Stop, the bearer resources are released. + +#### 4.4.1.8 Leaving + +Leaving (i.e. MBMS multicast deactivation by the user) is the process by which a subscriber leaves (stops being a member of) a multicast group, i.e. the user no longer wants to receive Multicast mode data of a specific MBMS bearer service. + +### 4.4.2 Multicast Mode timeline + +#### 4.4.2.1 Period between Service Announcement and Session Start + +The service announcement may contain a schedule of Session Start times and may be sent some time before the service is due to start. So, this time period could be hours, days or even weeks. + +#### 4.4.2.2 Period between Service Announcement and Service Subscription + +Service Subscription can be done anytime before or after Service announcement. + +#### 4.4.2.3 Period between Service Announcement and Joining + +The Joining time is chosen by the user and/or UE possibly in response to a Service Announcement. Users will typically join at the time of their choosing so that the period between announcement and joining may be very long or very short. In order to avoid overload situations being caused by many users attempting to join in a short period of time, the UE shall be able to use parameters sent by the BM-SC in the service announcement to randomise the joining time. + +#### 4.4.2.4 Period between Joining and Session Start + +Some MBMS bearer services may be 'always on'. In this case, Joining can take place immediately after Service Announcement and possibly many hours before, or after, Session Start. + +In other cases, if a Session Start time is known, Joining may take place immediately before Session Start or after Session Start. For these services, the announcement may contain some indication of a time period which users and UEs should use to choose a time to Join the MBMS bearer service. + +#### 4.4.2.5 Period between Session Start and First Data Arrival + +Session Start indicates that the transmission is about to start. The time delay between a Session Start indication and actual data should be long enough for the network actions required at Session Start to take place e.g. provision of service information to the UTRAN, establishment of the bearer plane. + +Session Start may be triggered by an explicit notification from the BM-SC. In the case of bearer plane resources which are set-up after the start of session data transmission, the network is not required to buffer the session data and loss of data can be assumed. + +#### 4.4.2.6 Period between Session Start and Session Stop + +When the BM-SC knows that there is no more data to be sent for a "long idle period", it should indicate Session Stop to the network, causing the release of bearer resources. However, if this idle period with no data is short, this may not be appropriate as it brings more signalling and processing. + +The duration of this "long idle period" is implementation dependent. The order of magnitude should be defined to take into account network constraints (including UTRAN, GERAN, and CN). + +If the BM-SC wants to use session repetition identification on the MBMS bearer service level, the BM-SC must stop the MBMS session before starting the next MBMS user service session for that TMGI. + +#### 4.4.2.7 Session Update + +Session Update is used to update specific parameters of an ongoing MBMS Multicast session. The SGSN can use the procedure to update the list of RAs where MBMS multicast users are located for an ongoing MBMS Multicast service session. + +### 4.4.3 BROADCAST MODE + +An example for the phases of MBMS broadcast service provision is described in the figure below: + +![Flowchart showing the phases of MBMS broadcast service provision: Service announcement, Session Start, MBMS notification, Data transfer, and Session Stop.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +graph TD + A[Service announcement] --> B[Session Start] + B --> C[MBMS notification] + C --> D[Data transfer] + D --> E[Session Stop] + + style A fill:#D3D3D3,stroke:#000,stroke-width:1px + style B fill:#D3D3D3,stroke:#000,stroke-width:1px + style C fill:#D3D3D3,stroke:#000,stroke-width:1px + style D fill:#D3D3D3,stroke:#000,stroke-width:1px + style E fill:#D3D3D3,stroke:#000,stroke-width:1px + +``` + +The diagram illustrates the sequence of phases for MBMS broadcast service provision. It consists of five gray rectangular boxes stacked vertically, each containing a phase name: 'Service announcement', 'Session Start', 'MBMS notification', 'Data transfer', and 'Session Stop'. These boxes are centered over a large, light-blue arrow pointing downwards, which spans the entire height of the stack and ends in a large arrowhead at the bottom. + +Flowchart showing the phases of MBMS broadcast service provision: Service announcement, Session Start, MBMS notification, Data transfer, and Session Stop. + +**Figure 4: Phases of MBMS broadcast service provision** + +The sequence of phases may repeat, e.g. depending on the need to transfer data. It is also possible that the service announcement and MBMS notification phase may run in parallel with other phases, in order to inform UEs which have not yet received the related service. + +![Figure 5: Broadcast service timeline. This sequence diagram illustrates the interaction between User Equipment (UE1, UE2) and a Broadcast Service over time. UE1 performs a 'UE local service activation' (green dot) and later a 'Local service de-activation' (red X). UE2 also activates (green dot) and deactivates (red X) the service. The timeline shows a 'Start Broadcast Service announcement' (blue dot), followed by an 'Idle period of seconds' (dashed green line). A 'Broadcast session start' (green dot) initiates 'Data transfer' (green double-headed arrows) for 'Service 1 session 1'. A 'Session stop' (red dot) ends this session. Later, another 'Data transfer' occurs for 'Service 1 Session 2', ending with a 'Stop announcement' (blue dot). At the bottom, a 'Broadcast service Announcement' (blue bar) is shown, with a callout stating 'Broadcast of Data, received by any UE which is present'.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +Figure 5: Broadcast service timeline. This sequence diagram illustrates the interaction between User Equipment (UE1, UE2) and a Broadcast Service over time. UE1 performs a 'UE local service activation' (green dot) and later a 'Local service de-activation' (red X). UE2 also activates (green dot) and deactivates (red X) the service. The timeline shows a 'Start Broadcast Service announcement' (blue dot), followed by an 'Idle period of seconds' (dashed green line). A 'Broadcast session start' (green dot) initiates 'Data transfer' (green double-headed arrows) for 'Service 1 session 1'. A 'Session stop' (red dot) ends this session. Later, another 'Data transfer' occurs for 'Service 1 Session 2', ending with a 'Stop announcement' (blue dot). At the bottom, a 'Broadcast service Announcement' (blue bar) is shown, with a callout stating 'Broadcast of Data, received by any UE which is present'. + +**Figure 5: Broadcast service timeline** + +#### 4.4.3.1 Service announcement + +Informs UEs about forthcoming MBMS user services. Also see clause 4.4.1.2 on Multicast mode. + +#### 4.4.3.1a UE local service activation + +The MBMS user service part in the UE initiates reception of the MBMS bearer service to receive an MBMS user service. In case one MBMS user service is carried by more than one MBMS bearer service, the UE may need to initiate the reception of multiple relevant MBMS bearer services to receive the MBMS user service (see clause 8.12). + +#### 4.4.3.2 Session Start + +Session Start is the point at which the BM-SC is ready to send data. This can be identified with the start of a "Broadcast session" as defined in TS 22.146 [2]. Session Start is the trigger for bearer resource establishment for MBMS data transfer. If an MBMS user service is carried by more than one MBMS bearer service, a Session Start message is sent for each MBMS bearer service. In that case the UE may need to initiate the reception of multiple relevant MBMS bearer services to receive the MBMS user service. + +#### 4.4.3.3 MBMS notification + +Informs the UEs about forthcoming (and potentially about ongoing) MBMS broadcast data transfer. + +#### 4.4.3.4 Data transfer + +It is the phase when MBMS data are transferred to the UEs. + +#### 4.4.3.5 Session Stop + +It is the point at which the MBMS user service determines that there will be no more data to send for some period of time – this period being long enough to justify removal of bearer resources associated with the service. At Session Stop, the bearer resources are released. + +#### 4.4.3.6 Session Update + +Session Update is used to update specific parameters of an ongoing MBMS Broadcast session. Parameters which can be updated are MBMS Service Area, and/or the List of SGSNs/MMEs (only from BM-SC to GGSN or MBMS GW). A Session Update received in one node, results in a Session Update being sent to downstream nodes, to inform of the changed MBMS Service Area. When a Session Update is received in the GGSN or MBMS GW including the List of SGSN/MME parameter, it results in a Session Start being sent to new downstream nodes, and in a Session Stop being sent to downstream nodes that have been removed from the list. + +In order to support the update of the priority of a broadcast data flow of a group communication service as specified in TS 23.468 [24], the QoS(ARP parameter only) of an MBMS Broadcast service session may be modified by the Session Update procedure. + +NOTE: The update of the QoS(ARP) only applies to the E-UTRAN. + +### 4.4.4 Broadcast Mode timeline + +#### 4.4.4.1 Period between Service Announcement and Session Start + +Same as for Multicast mode. + +#### 4.4.4.2 Period between Session Start and First Data Arrival + +Same as for Multicast mode. + +#### 4.4.4.3 Period between Session Start and Session Stop + +Same as for Multicast mode. + +# --- 5 Functional Entities To Support MBMS + +## 5.0 General + +To provide MBMS bearer services existing functional entities, GGSN, MME, SGSN, eNodeB/RNC/BSC, perform several MBMS related functions and procedures, some of which are specific to MBMS. An MBMS specific functional entity – Broadcast Multicast Service Centre (BM-SC) supports various MBMS user service specific services such as provisioning and delivery. In the EPS a functional entity MBMS GW exists at the edge between the CN and the BM-SC. + +## 5.1 Broadcast-Multicast Service Centre (BM-SC) + +### 5.1.0 General + +The BM-SC provides functions for MBMS user service provisioning and delivery. It may serve as an entry point for content provider MBMS transmissions, used to authorise and initiate MBMS Bearer Services within the PLMN and can be used to schedule and deliver MBMS transmissions. + +The BM-SC is a functional entity, which must exist for each MBMS User Service. + +The BM-SC consists of the following sub-functions: + +- Membership function; +- Session and Transmission function; +- Proxy and Transport function; + +- Service Announcement function; +- Security function. +- Content synchronization for MBMS in UTRAN. +- Content synchronization for MBMS in E-UTRAN for broadcast mode. +- Header compression for MBSFN MBMS data in UTRAN. +- Header compression for Mission Critical services using MBMS in E-UTRAN (see TS 23.468 [24]). + +NOTE: Header compression of MBMS data is not supported in E-UTRAN only for Mission Critical services in this Release. + +- For MBMS bearer service for NB or M UE categories, provide mapping from UE Capability for MBMS as defined in TS 23.682 [29] to QCIs as defined in clause 6.3.2. + +This clause describes BM-SC functions, which are defined for the standardised MBMS User Services. + +![Figure 5a: BM-SC functional structure diagram. The diagram shows the internal functional blocks of a BM-SC and its interfaces. Inside the BM-SC box, there are four main functions: 'Security Function' (top right), 'Membership Function' (top left), 'Proxy and Transport Function' (middle left), and 'Service Announcement function' (bottom right). The 'Security Function' is connected to the 'Membership Function' and the 'Session and Transmission Function'. The 'Membership Function' is connected to the 'Proxy and Transport Function' via a 'Gmb' interface. The 'Proxy and Transport Function' is connected to the 'Session and Transmission Function' via 'Gmb' and 'Gi' interfaces. The 'Service Announcement function' is connected to the 'Session and Transmission Function' and has an interface 'Gi/SGi' leading 'To UE' with data types 'WAP, http, MMS, ...'. The 'Session and Transmission Function' is connected to an external 'Content Provider / Multicast Broadcast Source' and has interfaces 'Gi/SGi' leading 'To UE' (data: 'http, MIKEY/UDP, ...') and 'Gmb/SGi' leading 'To GGSN' (data: 'MBMS GW SGmb/SGi-rb').](e636d7ccca0ad14c6b95201404324823_img.jpg) + +Figure 5a: BM-SC functional structure diagram. The diagram shows the internal functional blocks of a BM-SC and its interfaces. Inside the BM-SC box, there are four main functions: 'Security Function' (top right), 'Membership Function' (top left), 'Proxy and Transport Function' (middle left), and 'Service Announcement function' (bottom right). The 'Security Function' is connected to the 'Membership Function' and the 'Session and Transmission Function'. The 'Membership Function' is connected to the 'Proxy and Transport Function' via a 'Gmb' interface. The 'Proxy and Transport Function' is connected to the 'Session and Transmission Function' via 'Gmb' and 'Gi' interfaces. The 'Service Announcement function' is connected to the 'Session and Transmission Function' and has an interface 'Gi/SGi' leading 'To UE' with data types 'WAP, http, MMS, ...'. The 'Session and Transmission Function' is connected to an external 'Content Provider / Multicast Broadcast Source' and has interfaces 'Gi/SGi' leading 'To UE' (data: 'http, MIKEY/UDP, ...') and 'Gmb/SGi' leading 'To GGSN' (data: 'MBMS GW SGmb/SGi-rb'). + +**Figure 5a: BM-SC functional structure** + +### 5.1.1 Membership Function + +The BM-SC Membership function provides authorization for UEs requesting to activate an MBMS service. + +The Membership function may have subscription data of MBMS service users. + +The Membership Function may generate charging records for MBMS service users. + +The Membership Function is an MBMS bearer service level function, but it may also provide user service level functions e.g. membership management etc. In this case it does also have a Gi/SGi interface. + +### 5.1.2 Session and Transmission Function + +The BM-SC Session and Transmission Function shall be able to schedule MBMS session transmissions. + +The BM-SC Session and Transmission Function should be able to schedule MBMS session retransmissions, and label each MBMS session with an MBMS Session Identifier to allow the UE to distinguish the MBMS session retransmissions. The BM-SC Session and Transmission Function allocates TMGIs. + +Each transmission and subsequent retransmission(s) of a specific MBMS session are identifiable by a common MBMS Session Identifier (2-3 Octets) passed at the application layer in the content, and also passed in a shortened form (i.e. the least significant octet) in the MBMS Session Start Request message to the eNodeBs/RNCs/BSCs. The full MBMS Session Identifier should be used by the UE to identify an MBMS session when completing point-to-point repair, while the shortened MBMS Session Identifier is included by the RANs in the notification messages for MBMS + +The BM-SC Session and Transmission Function shall be able to provide the MBMS GW or GGSN with transport associated parameters such as quality-of-service and MBMS service area. + +The BM-SC Session and Transmission Function shall be able to initiate and terminate MBMS bearer resources prior to and following transmission of MBMS data. + +The BM-SC Session and Transmission Function should be able to send MBMS data. It could also apply favourable error resilient schemes e.g. specialized MBMS codecs or Forward Error Correction schemes. + +When IP multicast is used for distribution of payload from GGSN to RNC or from MBMS GW to eNodeB and RNC, the BM-SC Session and Transmission Function shall include synchronization information for the MBMS payload. If the header compression is used over the radio, the compression is done in the BM-SC. The details of synchronization and header compression for the MBMS payload are specified in TS 25.346 [10] and TS 25.446 [18]. + +The BM-SC Session and Transmission Function should be able to authenticate and authorize external sources and accept content from them. + +The Session and Transmission Function is user service level function and it triggers bearer level functions when MBMS sessions are scheduled. + +### 5.1.3 Proxy and Transport Function + +The BM-SC Proxy and Transport Function is a Proxy Agent for signalling over SGmb and Gmb reference points between MBMS GWs/GGSNs and other BM-SC sub-functions, e.g. the BM-SC Membership Function and the BM-SC Session and Transmission Function. Further, the BM-SC Proxy and Transport Function shall also be able to handle when BM-SC functions for different MBMS services are provided by multiple physical network elements. Routing of the different signalling interactions shall be transparent to the MBMS GW and the GGSN. + +The BM-SC Proxy and Transport function shall be able to generate charging records for content provider charging of transmitted data. Content provider name is provided to BM-SC Proxy and Transport function over SGmb/Gmb at session start. + +The BM-SC Proxy and Transport function may act as an intermediate device for the MBMS data sent from the BM-SC Session and Transmission function to the MBMS GW or GGSN. + +The Proxy and Transport Function may be divided further into a Proxy function managing the control plane (SGmb/Gmb) and a Transport function managing the multicast payload. + +The Proxy and Transport Function is an MBMS bearer service function. + +### 5.1.4 Service Announcement Function + +The BM-SC Service Announcement function shall be able to provide service announcements for multicast and broadcast MBMS user services. + +The BM-SC Service Announcement function shall be able to provide the UE with media descriptions specifying the media to be delivered as part of an MBMS user service (e.g. type of video and audio encodings). + +The BM-SC Service Announcement function shall be able to provide the UE with MBMS session descriptions specifying the MBMS sessions to be delivered as part of an MBMS user service (e.g. multicast service identification, addressing, time of transmission, etc.). + +The BM-SC Service Announcement function shall be able to deliver media and session descriptions by means of service announcements using IETF specified protocols over MBMS multicast and broadcast bearer services. + +The Service Announcement Function is a user service level function. + +The following mechanisms should be supported for service announcement. Service announcements may be triggered by the BM-SC but are not necessarily sent by the BM-SC: + +- MBMS bearer capabilities to advertise MBMS user Services; +- PUSH mechanism (WAP push); +- URL (WAP, HTTP); + +- SMS (point-to-point); +- SMS-CB cell broadcast. + +Other mechanisms could be considered in future releases. + +### 5.1.4a MBMS Security Function + +MBMS user services may use the Security functions for integrity and/or confidentiality protection of MBMS data. The MBMS Security function is used for distributing MBMS keys (Key Distribution Function) to authorized UEs. Detailed description of the security functions is provided in (TS 33.246 [5]). + +### 5.1.5 MBMS Content Transfer for the same MBMS User Service for GPRS and EPS + +#### 5.1.5.1 General + +For GPRS, although these procedures mention GERAN and UTRAN extensively, only the BM-SC (which renders the content differently) and the SGSN have to implement functionality to deliver this. The GGSN, RNC and BSC shall all be transparent to this functionality. + +For EPS, although these procedures mention UTRAN and E-UTRAN extensively, only the BM-SC and the MBMS-GW have to implement functionality to deliver this. The MME, S4-SGSN, RNC and eNodeB remain transparent to this functionality. + +#### 5.1.5.2 Separate MBMS Bearer Services for the same MBMS User Service + +The same MBMS user service may transfer its data on separate MBMS bearer services for different access technologies, typically with different QoS, e.g. for GPRS using separate MBMS bearer services for GERAN and UTRAN or for EPS using separate MBMS bearer services for UTRAN and E-UTRAN. For this purpose two IP multicast addresses (multicast mode only) and/or two TMGIs should be allocated for the same MBMS user service. One IP multicast address (multicast mode only) and/or one TMGI is for, e.g. GERAN, and another IP multicast address (multicast mode) and/or another TMGI is for, e.g. UTRAN. The detailed impacts on the network nodes are listed below: + +- a) The service announcement instructs the UE to join two multicast MBMS bearer services (e.g. for GPRS one is for GERAN and the other is for UTRAN), i.e. for multicast mode, two IP multicast addresses that are allocated in the BM-SC are sent to UE within one service announcement message. + +NOTE 1: One MBMS User Service may use several MBMS Bearer Services. + +- b) A UE that might move between areas covered by different access technologies activates both MBMS bearer services. +- c) The UE monitors the paging/notification channels for both TMGIs and receives MBMS data when transferred by the MBMS bearer services. +- d) When the BM-SC needs to deliver the content, the BM-SC produces two sets of MBMS data from the same content and sends independent Session Start messages for both of the MBMS bearer services. The "different" content streams for the same MBMS user service are sent on the separate MBMS bearer services. For GPRS, a 2G/3G indicator in the Session Start message (which the GGSN passes transparently to the SGSN) indicates whether the content should be delivered in GERAN-only or UTRAN-only (or both) coverage areas. +- e) For GPRS, the SGSN uses the 2G/3G indicator to decide whether a MBMS Session Start Request message should be sent to the BSCs and/or the RNCs. + +NOTE 2: See clause 7.3 for potential issues. + +#### 5.1.5.3 Same MBMS Bearer Service for the same MBMS User Service + +The same MBMS user service may also transfer its data on the same MBMS bearer service for multiple access technologies, i.e. for GPRS using a same MBMS bearer service for GERAN and UTRAN or for EPS using a same MBMS bearer service for UTRAN and E-UTRAN. For this purpose one IP multicast address (multicast mode only) and/or one TMGI should be allocated for the same MBMS user service. In such application, the "different" content for the same MBMS user service are sent in separate MBMS Sessions sequentially. For GPRS, the 2G/3G indicator in the + +Session Start message indicates whether the MBMS session should be delivered in GERAN-only or UTRAN-only (or both) coverage areas and the SGSN uses the 2G/3G indicator to decide whether a MBMS Session Start Request message should be sent to the BSCs and/or the RNCs. + +NOTE: The same MBMS bearer service for both UTRAN and E-UTRAN may be used if the BM-SC does not execute header compression for the MBMS service. + +### 5.1.6 Location Dependent Content Transfer for the same MBMS User Service (Broadcast Mode only) + +Some MBMS user services may broadcast different content in different areas of the network. In such case the UE is not aware of the relation between location and content, i.e. the UE just activates the reception of the service and receives the content that is relevant for its location. + +The BM-SC controls which content is broadcasted in which area by establishing a separate MBMS bearer service for each content data flow. All MBMS bearer services of the same MBMS user service share the same TMGI but bear different Flow Identifiers. The BM-SC allocates the Flow Identifier during the MBMS Session Start procedure and initiates a separate session for each content data flow. For IP Multicast support in EPS, the MBMS GW allocates an IP Multicast Address based on the TMGI and Flow Identifier (broadcast mode only). Since in any specific location only one version of the content shall be available at any point in time, the MBMS Service Areas of each session of a same user service shall not overlap; this shall be ensured by proper configuration of the service in the BM-SC. The RNC and the eNodeB ultimately enforces this constraint by rejecting any session start request with the same TMGI as an already active session if there is any overlap in the respective service areas. As indicated above, the UE is unaware of the Flow Identifier and of the existence of multiple sessions for the same MBMS user service. + +### 5.1.7 MBMS User Service Consumption Reporting (Broadcast mode only) + +MBMS User Service Consumption Reporting functionality better enables the MBMS service operator to decide in a dynamic manner, based on real time demand of an MBMS User Service, to either: + +- establish service delivery over an MBMS bearer; +- tear down service delivery over an already established MBMS bearer to only leave service delivery over unicast. + +By permitting these decisions to be made dynamically, this functionality enables the MBMS service operator to better utilize overall network resources in supporting unicast and/or MBMS services delivery. The MBMS service consumption reporting procedure is optional and initiated by the MBMS receiver (UE) to the BM-SC, in accordance with parameters in the Associated Delivery Procedure description as defined in TS 26.346 [7]. + +The BM-SC can specify the nominal periodicity by which the UE, when it is continuously consuming the service of concern, performs consumption reporting. The BM-SC can specify whether the UE includes its current location (serving cell-ID or MBMS SAI) when it performs consumption reporting. The location type is selected based on the Associated Delivery Procedure Description settings, or the MooD Management Object (MO) on the UE, or via UE pre-configuration rules. Typically, the BM-SC is pre-configured, via OAM procedures, with a threshold per location (number of UEs reporting consumption) to be used in making the decision to switch delivery method. + +The service offloaded to the MBMS bearer could be either one delivered by unicast not involving MBMS User Services, or an MBMS User Service delivered on a unicast bearer. Furthermore, the BM-SC can determine, based on Consumption Reporting from UEs consuming that MBMS User Service over an MBMS bearer, the interest for that MBMS User Service has decreased sufficiently to terminate the MBMS bearer. In such event, UEs may continue to receive the service but over unicast instead, either not involving the MBMS User Service, or as an MBMS User Service over unicast. Continued consumption monitoring by the BM-SC, and consumption reporting by UEs, may be employed to facilitate further switching, over time, between bearer modes. + +Along with MBMS Consumption Reporting, the use of MBMS operation on Demand (clause 7.4) permits certain content that is initially delivered over the unicast network to be turned into an MBMS User Service, in order to efficiently use network resources when the traffic exceeds a certain threshold. + +## 5.2 User Equipment + +The UE shall support functions for the activation/deactivation of the MBMS bearer service. + +Once a particular MBMS bearer service is activated, no further explicit user request is required to receive MBMS data although the user may be notified that data transfer is about to start. + +The UE shall support security functions as appropriate for MBMS. + +The UE should, depending on terminal capabilities, be able to receive MBMS user service announcements, paging information (non MBMS specific) and support simultaneous services (for example the user can originate or receive a call or send and receive messages whilst receiving MBMS video content). Reception of this paging or announcements may however, create losses in the MBMS data reception. The MBMS user service should be able to cope with such losses. + +A UE in Multicast Mode shall be able to synchronise with the SGSN, which of its MBMS UE contexts are still active. + +Depending upon terminal capability, UEs may be able to store MBMS data. This may involve DRM but this is out of scope of this specification. + +The MBMS Session Identifier contained in the notification to the UE shall enable the UE to decide whether it needs to ignore the forthcoming transmission of MBMS session (e.g. because the UE has already received this MBMS session). + +## 5.3 UTRAN/GERAN + +UTRAN/GERAN are responsible for efficiently delivering MBMS data to the designated MBMS service area. + +Efficient delivery of MBMS data in multicast mode may require mechanisms in the UTRAN/GERAN, e.g. the number of users within a cell prior to and during MBMS transmission could be used to choose an appropriate radio bearer. + +MBMS transmissions may be initiated and terminated intermittently. The UTRAN/GERAN shall support the initiation and termination of MBMS transmissions by the core-network. Further, the UTRAN/GERAN shall be able to receive MBMS data from the core-network over Iu bearers shared by many UEs. + +UTRAN (and GERAN in Iu mode) may also support reception of MBMS data from the core-network over IP multicast. When UTRAN (or GERAN Iu mode) supports IP multicast reception, the UTRAN (GERAN Iu mode) should support TEID coordination, i.e. avoid using the same value ranges for its own unicast TEIDs as are used by the GGSN and MBMS GW for the Common TEID-U (C-TEIDs). If clashes anyhow occur, the RNC (Iu mode BSC) shall reject IP multicast reception and fallback to normal shared Iu bearers for reception of MBMS data. + +The UTRAN/GERAN shall support both intra-RNC/BSC and inter-RNC/BSC mobility of MBMS receivers. Mobility is expected to cause limited data loss. Therefore, MBMS user services should be able to cope with potential data loss caused by UE mobility. + +The UTRAN/GERAN shall be able to transmit MBMS user service announcements, paging information (non MBMS specific) and support other services in parallel with MBMS (for example depending on terminal capabilities the user could originate or receive a call or send and receive messages whilst receiving MBMS video content). + +## 5.4 SGSN + +The SGSN's role within the MBMS architecture is to perform MBMS bearer service control functions for each individual UE and to provide MBMS transmissions to UTRAN/GERAN. When IP multicast is used for MBMS transmissions the SGSN is bypassed in the 3G case (and GERAN Iu mode case), i.e. MBMS data sent directly from GGSN to RNC (or Iu mode BSC) or from MBMS GW to RNC in EPS. + +The SGSN shall provide support for intra-SGSN and inter-SGSN mobility procedures. Specifically this requires the SGSN to store a user-specific MBMS UE context for each activated multicast MBMS bearer service and to pass these contexts to the new SGSN during inter-SGSN mobility procedures. + +The SGSN shall be able to indicate its MBMS support to the UE as well as it shall be able to synchronise with the UE, which of the UE's MBMS UE contexts are still active. + +The SGSN shall be able to generate charging data per multicast MBMS bearer service for each user. The SGSN does not perform on-line charging for either the MBMS bearer service or the MBMS user service (this is handled in the BM-SC). + +The SGSN shall be able to establish Iu and Gn bearers shared by many users upon receiving a session start from the GGSN. Likewise, the SGSN shall be able to tear down these bearers upon instruction from the GGSN. + +When MBMS in EPS for UTRAN access is supported, the SGSN shall support the necessary control plane functions provided via Sn interface to/from MBMS GW. + +## 5.5 GGSN + +The GGSN role within the MBMS architecture is to serve as an entry point for IP multicast traffic as MBMS data. Upon notification from the BM-SC the GGSN shall be able to request the establishment of a bearer plane for a broadcast or multicast MBMS transmission. Further, upon BM-SC notification the GGSN shall be able to tear down the established bearer plane. Bearer plane establishment for multicast services is carried out towards those SGSNs and /or RNCs that have requested to receive transmissions for the specific multicast MBMS bearer service. For an optimized bearer plane, IP multicast transport may be used within the core network. The bearer plane is then established between the GGSN and the RNCs. + +When IP multicast is used for distribution payload from GGSN to RNC, and one or more RNC rejects IP multicast distribution, the GGSN should in parallel with the IP multicast distribution provide legacy MBMS payload distribution (i.e. using point-to-point GTP-tunnels) via the SGSNs to these RNCs. In that case, the GGSN shall remove the synchronisation protocol elements included by the BM-SC (i.e. synchronization information and the compressed header) before forwarding the payload on the legacy path (see TS 25.446 [18]). + +The GGSN shall be able to receive MBMS specific IP multicast traffic and to route this data to the proper IP multicast distribution address and/or GTP tunnels set-up as part of the MBMS bearer service. + +The GGSN may also provide features that support the MBMS bearer service that are not exclusive to MBMS. Examples are: + +- Message Screening (not needed if the MBMS sources are internal in the PLMN); +- Charging Data Collection; +- Flow Based Charging (see clause 10). + +## 5.6 MBMS Data Sources and Content Provider + +For group communications related services, the standard interface to and from BM-SC is MB2 (TS 23.468 [24], TS 29.468 [27]). For services other than Group Communications, the standard reference point between the content provider and the BM-SC is defined in TS 26.348 [31]. + +## 5.7 Other Functional Element + +### 5.7.1 Void + +### 5.7.2 CBC + +The Cell Broadcast Centre (CBC) may be used to announce MBMS user services to the users. + +### 5.7.3 Void + +## 5.8 Void + +## 5.9 Functional Elements for the Evolved Packet System + +### 5.9.1 MBMS GW + +One or more MBMS GW function entities may be used in a PLMN. + +Note that MBMS GW may be stand alone or co-located with other network elements such as BM-SC or combined S-GW/PDN GW. + +MBMS GW functions include: + +- It provides an interface for entities using MBMS bearers through the SGi-mb (user plane) reference point; +- It provides an interface for entities using MBMS bearers through the SGmb (control plane) reference point; +- IP multicast distribution of MBMS user plane data to E-UTRAN (M1 reference point). If the MBMS-GW has allocated both an IPv4 and an IPv6 IP Multicast address, IP multicast distribution of MBMS user plane data is performed towards both IP Multicast addresses, using the same C-TEID; +- IP multicast distribution of MBMS user plane data to RNCs (M1 reference point); + +NOTE 1: In case of mobility in or out from an MBMS service area, the service continuity is handled by the Service Layer (in UE and network). + +- In the case of UTRAN access, it allocates either an IPv4 or an IPv6 IP Multicast address. An RNC should join to IP Multicast distribution to receive the MBMS data. The IP Multicast address together with the IP address of the multicast source (SSM) and a C-TEID is provided to the RNC via SGSN; +- In the case of E-UTRAN access, and if the MBMS-GW supports both IPv4 and IPv6, it may allocate both an IPv4 and an IPv6 IP Multicast address (e.g. in deployments with a mix of IPv4 and IPv6 eNodeBs and/or backhauls). Otherwise it allocates either an IPv4 or an IPv6 IP Multicast address. An eNodeB should join to IP Multicast distribution using one IP Multicast address (either IPv4 or IPv6) to receive the MBMS data. When a single IP Multicast address is allocated by the MBMS-GW, this IP Multicast address together with the IP address of the multicast source (SSM) and a C-TEID is provided to the eNodeB via MME. When two IP Multicast addresses are allocated by the MBMS-GW: + - each of them is associated with an IP address of the multicast source (SSM); + - the same C-TEID is associated to both IP Multicast addresses; + - both IP Multicast addresses together with the corresponding IP addresses of the multicast source (SSM) and the C-TEID is provided to the E-UTRAN via MME; + +NOTE 2: The C-TEID is allocated based on MBMS bearer service uniquely identified by the TMGI and Flow Identifier (Broadcast mode only). + +The IP Multicast Address or, optionally in case of E-UTRAN access and if the MBMS-GW supports both IPv4 and IPv6, both an IPv4 and an IPv6 IP Multicast address are either uniquely allocated for the MBMS bearer service (identified by the TMGI and Flow Identifier), or it may be reused from another active MBMS bearer service with an identical service area and of the same QoS. + +NOTE 3: Care should be taken to avoid clashes among C-TEIDs generated in MBMS-GWs. and UTRAN/E-UTRAN. + +- An MBMS GW may support fall back to point to point mode where applicable for UTRAN access; +- An MBMS GW can communicate with multiple control plane entities (i.e. MME, SGSN and BM-SCs). + +### 5.9.2 MBMS Control plane function + +The MBMS control plane function is supported by MME for E-UTRAN access and by SGSN for UTRAN access. For SGSN functions, see clause 5.4. + +One or more MBMS control plane functional entities are used in a PLMN. + +MME supports the following functions in order to enable MBMS support for E-UTRAN: + +- Session control of MBMS bearers to the E-UTRAN access (including reliable delivery of Session Start/Session Stop to E-UTRAN); +- Transmit Session control messages towards multiple E-UTRAN nodes; + +- When connected to multiple MCEs (see TS 36.300 [17]), the MME should filter the distribution of Session Control message to the MCEs based on the MBMS service area; +- Provision of the list of MBMS Service Areas served by the MCE to the MME using M3AP Setup signalling; +- Transmit Session Control messages towards the necessary E-UTRAN nodes to ensure the distribution of content from ongoing MBMS sessions: + - if an MCE sets up (or restarts) an M3AP connection with the MME, by applying the MCE Failure procedure specified in TS 23.007 [26]; or + - if the MCE modifies the list of MBMS Service Areas it serves, by triggering the MCE Configuration Update procedure. +- It provides an Sm interface to the MBMS GW function: it receives MBMS service control messages and the IP Multicast address or, optionally, (e.g. in deployments with a mix of IPv4 and IPv6 eNodeBs and/or backhauls) and if the MBMS-GW supports both IPv4 and IPv6, both an IPv4 and an IPv6 IP Multicast address for MBMS data reception from MBMS GW function over the Sm interface. + +NOTE: When a UE leaves or enters MBMS bearer coverage, the service continuity is handled by the Service Layer (in UE and network). + +### 5.9.3 E-UTRAN + +E-UTRAN is responsible for efficiently delivering MBMS data to the designated MBMS service area. + +The E-UTRAN for MBMS in EPS shall have capability of receiving IP multicast distribution. + +In order to provide the appropriate MBMS bearer service for NB or M UE categories, E-UTRAN/MCE may map received QCI into appropriate radio configurations for the appropriate UE categories, when such mapping is configured as described in clause 6.3.2. + +# --- 6 MBMS Attributes and Parameters + +## 6.1 MBMS UE Context + +The MBMS UE Context is used in Multicast Mode and contains UE-specific information related to a particular MBMS bearer service that the UE has joined. An MBMS UE Context is created in the UE, SGSN, GGSN and BM-SC Membership function when the UE joins an MBMS bearer service. In the SGSN, an MBMS UE Context is also created as a result of an inter-SGSN routing area update after the transfer of the MBMS UE Context from the old SGSN. + +In Iu mode, all MBMS UE Contexts of a UE are provided via MBMS UE Linking mechanism to the BSC/SRNC at least when the first PS RAB is established for the UE, or when the UE performs MBMS Multicast Service Activation. MBMS UE Contexts are provided to the Iu mode BSC/SRNC regardless whether MBMS Sessions are ongoing or not (i.e. before, between and after Sessions). In addition, all MBMS UE Contexts of a UE are provided via MBMS UE Linking mechanism when a UE, which has an MBMS UE Context active, moves to PMM-Connected state via the MBMS Service Request procedure for the purpose of MBMS. + +In the UE and SGSN, the MBMS UE Context is stored as part of the MM Context for the UE. The MBMS UE Context is stored in the GGSN. There is one MBMS UE Context per MBMS bearer service that the UE has joined. + +In the Iu mode BSC/RNC, the MBMS UE Contexts are stored as part of the UE Context of the BSC/RNC. + +The content of the MBMS UE Context is described in Table 1. + +**Table 1: MBMS UE Context** + +| Parameter | Description | UE | SGSN | GGSN | RNC | BSC | BM-SC | +|----------------------------|------------------------------------------------------------------------------------|-----|------|------|-----|----------------------|-------| +| IP multicast address | IP multicast address identifying an MBMS bearer that the UE has joined. | X | X | X | X | Iu - X
Gb - none | X | +| APN | Access Point Name on which this IP multicast address is defined. | X | X | X | X | Iu - X
Gb - none | X | +| GGSN Address in Use | The IP address of the GGSN currently used | | X | | | | | +| SGSN address | The IP address of SGSN | | | X | | | | +| TMGI | Temporary Mobile Group Identity allocated to the MBMS bearer. | X | X | | X | Iu - X
Gb - none | | +| RAI | The Routing Area Identity | | (5) | | | | | +| Linked NSAPI | NSAPI of the PDP context used by the UE to carry IGMP/MLD signalling. | X | X | | | | | +| IMSI | IMSI identifying the user. | (1) | (1) | X | (2) | Iu - (2)
Gb - (3) | X | +| TI | Transaction Identifier | X | X | | | | | +| TEID for Control Plane | The Tunnel Endpoint Identifier for the control plane between SGSN and GGSN. | | X | X | | | | +| MBMS_NSAPI | Network layer Service Access Point Identifier which identifies an MBMS UE Context. | X | X | X | X | | | +| Additional MBMS Trace Info | Identifies additional information required to perform trace. | | (4) | (4) | | | (4) | +| Trace Reference | Identifies a record or a collection of records for a particular trace. | | (4) | (4) | (4) | (4) | | +| Trace Type | Indicates the type of trace. | | (4) | (4) | (4) | (4) | | +| Trigger Id | Identifies the entity that initiated the trace. | | (4) | (4) | (4) | (4) | | +| OMC Identity | Identifies the OMC that shall receive the trace record(s). | | (4) | (4) | (4) | (4) | | + +(1) In the UE and SGSN, the IMSI is available within the MM Context which contains the MBMS UE Context. +(2) The IMSI is available within the UE Context which contains the MBMS UE Context. +(3) IMSI availability does not depend on MBMS. +(4) Trace parameters are only stored if trace is activated. +(5) RAI is available within the MM Context of the UE. + +## 6.2 MBMS Bearer Context + +The MBMS Bearer Context, which is referred to as MBMS Service Context in RAN, contains all information describing a particular MBMS bearer service and is created in each node involved in the delivery of the MBMS data. + +In MBMS multicast mode a MBMS Bearer Context is created in the SGSN and GGSN when the first MBMS UE Context is created in the node or when a downstream node requests it. The MBMS Bearer Context is statically configured in the BM-SC Proxy and Transport Function; how this is done is out of the scope of this specification. The MBMS Bearer Context is created in the Iu mode BSC and in SRNC when a first MBMS UE Context is created in BSC/SRNC. MBMS Session Start procedure may create MBMS Bearer Context in a BSC/RNC which has no MBMS Bearer Context yet. + +In MBMS broadcast mode, an MBMS Bearer Context is created in the MME/SGSN, MBMS GW/GGSN and RAN as a result of the MBMS Session Start procedure. + +An MBMS Bearer Context, once created, can be in one of two states reflecting the bearer plane resource status of the corresponding MBMS bearer service. + +![State transition diagram for MBMS Bearer Context State Model. It shows two states: 'Standby' at the top and 'Active' at the bottom. A transition arrow labeled 'Session Start' points from 'Standby' to 'Active'. A transition arrow labeled 'Session Stop' points from 'Active' to 'Standby'.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +No bearer plane resources required + +``` +graph TD; Standby((Standby)) -- "Session Start" --> Active((Active)); Active -- "Session Stop" --> Standby; +``` + +Bearer plane resources required + +State transition diagram for MBMS Bearer Context State Model. It shows two states: 'Standby' at the top and 'Active' at the bottom. A transition arrow labeled 'Session Start' points from 'Standby' to 'Active'. A transition arrow labeled 'Session Stop' points from 'Active' to 'Standby'. + +**Figure 6: MBMS Bearer Context State Model** + +'Active' reflects the state of an MBMS Bearer Context in which bearer plane resources are required in the network for the transfer of MBMS data. This state is maintained as long as there is a corresponding MBMS session ongoing. + +'Standby' reflects the state of an MBMS Bearer Context in which no bearer plane resources are required in the network for the transfer of MBMS data. This state is maintained as long as there is no corresponding MBMS session ongoing. + +In MBMS broadcast mode, the MBMS Bearer Context is always implicitly in state 'active' (since it is created as a result of an MBMS Session Start procedure) and does not use the MBMS Bearer Context State Model in Figure 6. + +The content of the MBMS Bearer Context is described in Table 2. + +**Table 2: MBMS Bearer Context for GPRS** + +| Parameter | Description | RAN | SGSN | GGSN | BM-SC | +|---------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-----------------|---------------------|---------------| +| Multicast/broadcast mode | MBMS bearer service in broadcast or multicast mode | X | X | X | X | +| IP multicast address (multicast mode only) | IP multicast address identifying the MBMS bearer described by this MBMS Bearer Context. | X | X | X | X | +| APN (multicast mode only) | Access Point Name on which this IP multicast address is defined. | X | X | X | X | +| TMGI | Temporary Mobile Group Identity allocated to the MBMS bearer service. | X | X | X | X | +| Flow Identifier (broadcast mode only) | Location dependent subflow of the MBMS bearer service. When present, the Flow Identifier together with the TMGI uniquely identify the MBMS Bearer Context. | | X
(note 1) | X
(note 1) | X
(note 1) | +| GGSN TEID-C | Tunnel Endpoint Identifier of GGSN for control plane. | | X | | | +| GGSN IP Address for Control Plane in use | The IP address of the GGSN used for the control plane. | | X
(note 4) | | | +| State | State of bearer plane resources ('standby' or 'active') | X | X | X | X | +| Required MBMS Bearer Capabilities (multicast mode only) | Minimum bearer capabilities the UE needs to support | | X | X | X | +| QoS | Quality of Service required for the MBMS bearer service. | X | X | X | X | +| MBMS Service Area | Area over which the MBMS bearer service has to be distributed. | X | X | X | X | +| List of downstream nodes | List of downstream nodes that have requested the MBMS bearer service and to which notifications and MBMS data have to be forwarded. | | X
(note 5) | X
(notes 3, 4,6) | X | +| Number of UEs (multicast mode only) | Number of UEs hosted by the node that have joined the multicast MBMS bearer service. | | X | X | | +| List of PMM-CONNECTED UEs | List of PMM-CONNECTED UEs which have activated an MBMS service. | X 2) | | | | +| List of RAs (multicast mode only) | List of RAs, each of which contains at least one UE that has joined the MBMS bearer service. | X 1) | X 1) | | | +| IP multicast and Source address for distribution | IP addresses identifying the SSM channel used for user plane distribution on the backbone network | X | X | X | | +| MBMS HC indicator | Flag set by BM-SC if it is using compressed header for the payload. | | X | X | X | + +NOTE 1: It is an optional parameter. + +NOTE 2: It is available only for UTRAN, not for GERAN. + +NOTE 3: For GGSN, the list at least includes the couples of the SGSN IP addresses and TEIDs for control plane, and the couples for user plane. + +NOTE 4: GSN that supports both IPv4 and IPv6 address types, stores only the IP address in use. + +NOTE 5: For SGSN, the list includes the registered DRNC. + +NOTE 6: The GGSN shall include SGSN Address for user data and TEID-U for downstream SGSNs that do not accept the IP multicast backbone distribution. + +**Table 3: MBMS Bearer Context for EPS (E-UTRAN/UTRAN) broadcast mode only** + +| Parameter | Description | RAN | MME/
SGSN | MBMS-
GW | BM-SC | +|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---------------|---------------|---------------| +| MBMS GW TEID-C | Tunnel Endpoint Identifier of MBMS GW for control plane. | | X | | | +| TMGI | Temporary Mobile Group Identity allocated to the MBMS bearer service. | X | X | X | X | +| Flow Identifier | Location dependent subflow of the MBMS bearer service. When present, the Flow Identifier together with the TMGI uniquely identify the MBMS Bearer Context. | | X
(note 1) | X
(note 1) | X
(note 1) | +| MBMS GW IP Address for Control Plane in use | The IP address(es) of the MBMS GW used for the control plane. | | X
(note 2) | | | +| MBMS GW IP Address for User Plane in use | The IP address of the MBMS GW used for the user plane. | | X
(note 2) | | | +| C-TEID | Common Tunnel Endpoint Identifier of MBMS GW for user plane | X | | X | | +| QoS parameters | Quality of Service required for the MBMS bearer service. | X | X | X | X | +| MBMS Service Area | Area over which the MBMS bearer service has to be distributed. | X | X | X | X | +| List of downstream nodes | List of downstream nodes that have requested the MBMS bearer service and to which notifications have to be forwarded. | | X
(note 3) | X
(note 4) | X | +| IP multicast address(es) and IP Source address(es) for distribution | IP addresses identifying the SSM channel used for user plane distribution on the backbone network. The IP multicast address and paired IP address of the multicast source shall be of the same IP type. | X | X
(note 6) | X
(note 6) | | +| MBMS HC indicator | Flag set by BM-SC if it is using compressed header for the payload. | | X
(note 5) | | X
(note 5) | +| SGSN IP Address and TEID for User Plane over Sn-U | The IP address and TEID of SGSN used for the user plane over Sn-U when some RNCs have not accepted IP multicast distribution. | | | X | | +| List of cell ID(s) | Cell(s) for which the MBMS bearer service may be distributed. | X
(note 7) | X
(note 7) | X
(note 7) | X
(note 7) | + +NOTE 1: It is an optional parameter. +NOTE 2: An MBMS GW that supports both IPv4 and IPv6 address types, stores both IP addresses. +NOTE 3: For SGSN, the list includes the registered DRNC. +NOTE 4: For MBMS GW, the list includes the couples of the SGSNs and MMEs IP addresses and TEIDs for control plane. +NOTE 5: Header Compression is only supported for UTRAN and for Mission Critical services over E-UTRAN for this Release. +NOTE 6: An MBMS-GW or an MME that supports IPv4 and IPv6 M1 multicast address types stores both IPv4 and IPv6 pairs of source and multicast addresses. The alternative IP multicast address and paired IP address of the multicast source are of the same IP type. +NOTE 7: It is applicable for LTE only. + +## 6.3 Quality-of-Service + +### 6.3.1 Quality-of-Service for GPRS + +It shall be possible for the network to control quality-of-service parameters for sessions of multicast and broadcast MBMS bearer services. All QoS attributes related to the UMTS bearer service described in TS 23.107 [3] are applicable to MBMS bearer services. Compared to point-to-point bearer services the following limitations exist: + +- For **traffic class**, only the background and streaming classes shall be supported. +- For **SDU error ratio**, only higher values are supported, i.e. the values describing higher numbers of lost or corrupted SDUs (actual values are for the background and streaming classes are $10^{-2}$ and $10^{-1}$ ). +- For **maximum bit-rate**, see the values described in TS 22.246 [6]. + +- For **Guaranteed bit rate** of the Streaming Traffic Class: depending on radio resource usage by other services, some cells of the MBMS Service Area may not have sufficient resources available for a MBMS Session. The RAN may decide not to establish RB in cells where requested resources are not available. The RAN does not reject a MBMS Session Start Request message even if one or more cells do not have enough resources to establish radio bearers. + +MBMS bearer services of background class are best suited for the transport of MBMS user services such as messaging or downloading. Buffering, shaping schemes and packet dropping may be applied to the traffic flow to adapt to the available resources and changing network conditions. The total transfer time is not critical for background class bearer services since the content must normally have been received in totality and stored in the UE before the user can access it. + +MBMS bearer services of streaming class are best suited for the transport of MBMS user services such as streaming. As for point-to-point bearer services, the network should minimise the packet transfer delay of streaming class bearer services as far as possible. Packet dropping should be the preferred traffic conditioning action applied to the traffic flow to adapt to the available resources. + +The principle difference between background and streaming classes for MBMS is the support of a guaranteed bit-rate in the streaming case. No indication is provided to the UE in cases where the RAN cannot provide the requested QoS. As a result, some UEs may not receive the MBMS session or parts of it. For background class, the RAN may continue to distribute data in congestion conditions but at potentially high packet loss rates, therefore the MBMS user service will have to provide sufficient redundancy within the data to be able to cope with the high packet loss. + +MBMS user services that would normally use MBMS bearer services of background class may however decide to use a streaming class MBMS bearer service if the MBMS user service cannot cope with high packet loss. + +The Allocation and Retention Priority of the MBMS bearer service allows for prioritisation between MBMS bearer services. + +As the MBMS bearer service transfers data to many UEs in parallel and because of the lack of feedback channel on radio level low SDU error ratios are difficult to achieve. When the resulting packet error ratio is not suitable for the MBMS user service or when prevention of data loss is required, an MBMS user service may perform retransmission of MBMS data over a point-to-point PDP context. + +### 6.3.2 Quality-of-Service for EPS + +It shall be possible for the network to control quality-of-service parameters for sessions of broadcast MBMS bearer services. All EPS QoS attributes related to the EPS bearer service are applicable to MBMS bearer services. + +For EPS, only GBR MBMS service is defined and the MBMS bearer service QoS includes the parameters QCI, ARP, GBR and MBR (TS 23.401 [16]). + +For E-UTRAN MBMS bearer service for NB or M UE categories, operator defined QCIs may be configured in the BMSC and in the EUTRAN. + +The BMSC may take into account the UE Capability for MBMS received via Activate MBMS Bearer Request in addition to the QoS requirements of the service and map that to a QCI value that is sent using MBMS Session Start Procedure towards EUTRAN (see TS 23.682 [29]). + +BMSC may be configured to take into account the UE Category for MBMS to derive operator defined QCIs. + +An example mapping is shown below for a service with otherwise the same QoS requirements: + +**Table 6.3.2-1: QCI association with UE Categories** + +| UE Categories supported | Operator defined QCI
(not standardised) | +|--------------------------------|--------------------------------------------| +| IoT UE type M2 | a | +| Both UE Category M1 and M2 UEs | b | +| IoT UE type NB2 | c | +| Both UE Category NB1 and NB2 | d | + +The BMSC may receive coverage level information for MBMS in addition to the UE Category for MBMS. When coverage information is received, and the BMSC is configured to take into account the coverage level, then BMSC + +generates the appropriate QCI based on the UE Category for MBMS and coverage level information for the MBMS service as defined in TS 23.682 [29]. + +An example mapping is shown below for a service with otherwise the same QoS requirements including coverage level: + +**Table 6.3.2-2: QCI association with UE Categories and coverage level** + +| UE Categories supported | Operator defined QCI
(not standardised) | +|----------------------------------------|--------------------------------------------| +| IoT UE type M2, Coverage level: Medium | a | +| IoT UE type M2, Coverage level: Normal | b | +| IoT UE type M2 Coverage level: High | c | +| Both UE Category M1 and M2 UEs | d | +| IoT UE type NB2 | e | +| Both UE Category NB1 and NB2 | f | + +NOTE 1: The QCI to and from UE Capability for MBMS needs to be the same in E-UTRAN and BMSC. + +Each GBR MBMS bearer service is associated with the following MBMS bearer level QoS parameters: + +- QoS Class Identifier (QCI); +- Allocation and Retention Priority (ARP); +- Maximum Bit Rate (MBR); +- Guaranteed Bit Rate (GBR). + +Unlike point-to-point EPS bearers, the MBR of a particular GBR bearer service shall be set equal to the GBR. + +NOTE 2: UE-AMBR and APN-AMBR do not apply to MBMS bearer services. + +Compared to point-to-point bearer services the following limitations exist: + +- For Guaranteed bit rate: depending on radio resource usage by other services, some cells of the MBMS Service Area may not have sufficient resources available for a MBMS Session. The RAN may decide not to establish RB in cells where requested resources are not available. The RAN does not reject a MBMS Session Start Request message even if one or more cells do not have enough resources to establish radio bearers. +- MBMS bearer admission control within E-UTRAN is constrained by the E-UTRAN resources that are configured for MBMS. + +In the case of E-UTRAN, established MBMS bearers may not always use all the resources configured for MBMS. When the resources configured for MBMS are not fully utilised, the E-UTRAN may schedule delivery of traffic from point-to-point bearers using some of the un-utilised MBMS resources (refer to TS 36.213 [25]). + +GBR MBMS bearer services are best suited for the transport of MBMS user services where a constant bit rate is needed. As for point-to-point bearer services, the network should comply with the transfer delay for GBR QCI's (TS 23.203 [23]). Packet dropping should be the preferred traffic conditioning action applied to the traffic flow to adapt to the available resources. The BM-SC ensures that the bit rate is not larger than the MBR. There is no radio aware flow shaping in the BM-SC. + +The Allocation and Retention Priority of the MBMS bearer service allows for prioritisation between MBMS bearer services at MBMS bearer service establishment. + +When the MBMS bearer service experience a packet error ratio which is not suitable for the MBMS user service or when prevention of data loss is required, an MBMS user service may perform retransmission of MBMS data over a point-to-point PDP context or PDN connection. + +### 6.3.3 MBMS QoS distribution tree + +MBMS data will be distributed to multiple users through a MBMS distribution tree that can go through many BSCs/RNCs, many SGSNs and one or more GGSNs. Furthermore some bearer resources may be shared between many users accessing the same MBMS bearer service in order to save resources. As a result, each branch of a MBMS distribution tree shall be established with the same QoS. + +MBMS distribution tree shall have the same QoS for all its branches. + +When a branch of the MBMS distribution tree has been created, it is not possible for another branch (e.g. due to arrival of a new UE or change of location of a UE with removal of a branch and addition of a new one) to impact the QoS of already established branches. + +There is no QoS (re-)negotiation between network elements (e.g. between RNC and SGSN). This implies that some branches may not be established if QoS requirement cannot be accepted by the concerned network node. + +## 6.4 Temporary Mobile Group Identity + +Temporary Mobile Group Identity (TMGI) is used for MBMS notification purpose. The BM-SC allocates a globally unique TMGI per MBMS bearer service. The structure of the TMGI is defined in TS 23.003 [13]. + +For Multicast MBMS bearer services the TMGI is transmitted to UE via the MBMS Multicast Service Activation procedure. For Broadcast Service the TMGI can be obtained via service announcement see " Service Announcement". + +The TMGI is a radio resource efficient MBMS bearer service identification, which is equivalent to the MBMS bearer service identification consisting of IP multicast address and APN. + +## 6.5 IP Multicast distribution + +### 6.5.1 General + +For GPRS in GGSN or for EPS in MBMS GW it shall by configuration be possible to enable distribution of MBMS payload by using IP Multicast in the backbone network. IP Multicast distribution is done from GGSN to RNC downstream nodes or from MBMS GW to eNodeB or RNC downstream nodes. The Source Specific Multicast (SSM) service model shall be used by nodes and routers as specified in RFC 4607 [21] and RFC 4604 [22]. + +### 6.5.2 IP Multicast distribution for GERAN Iu-mode and UTRAN for GPRS + +Fallback to legacy point-to-point distribution is done for RNC nodes which do not support IP Multicast distribution. + +NOTE: Support of fallback assumes the corresponding SGSNs have user plane functionality. + +The GGSN chooses an IP Multicast address for distribution and a Source address as well as a common TEID-U (C-TEID). The proposed IP Multicast and Source address for distribution and the C-TEID is indicated by the GGSN to the downstream SGSNs at Session Start. The SGSN forwards the request to the downstream RNC (and BSC in Iu mode) at Session Start. The RNC may accept or reject the proposed IP Multicast distribution in the MBMS Session Start Response to the SGSN. If accepted the RNC shall report the channel (IP Multicast and Source address) to the backbone in order to join the bearer service multicast distribution. At Session Stop the RNC shall correspondingly report to the backbone in order to leave the bearer service multicast distribution. + +If one or more downstream RNC nodes do not accept IP Multicast distribution, the SGSN will establish a normal MBMS point-to-point GTP-U tunnel to related RNCs and a point-to-point GTP-U tunnel to the GGSN. The SGSN does not respond to the GGSN until it has received responses from all RNCs. The SGSN shall indicate to the GGSN if IP Multicast distribution is accepted (by one or more RNCs) and it shall also indicate if normal MBMS point-to-point distribution is required (by one or more RNCs). The SGSN will also establish a normal MBMS point-to-point GTP-U tunnel to GGSN if there are BSCs in Gb mode in the MBMS distribution tree. + +The RNC node shall indicate to SGSN if IP Multicast distribution is accepted in the Session Start Response. If this indication is missing, the SGSN node shall treat the RNC node as not accepting IP Multicast distribution and use unicast distribution. + +IP Multicast distribution is only used within a PLMN. In the roaming case the GGSN establishes normal MBMS point-to-point GTP-U tunnels to SGSNs/RAN nodes in other networks. + +GGSN shall assign IP Multicast addresses used for MBMS distribution according to RFC 4607 [21]. When several GGSN are used for MBMS payload distribution, the used IP Multicast addresses and common TEIDs shall be coordinated by configuration. Clashes between common TEIDs allocated by GGSN and TEIDs allocated by RNC should be avoided by coordinated TEID ranges. + +The GTP-U Error Indication mechanism shall be disabled for MBMS bearers using IP Multicast distribution. The receiving node controls itself what is received using the IGMPv3/MLDv2 protocol, RFC 4604 [22]. + +The MBMS payload with the synchronization information received from the BM-SC included, shall be distributed by the GGSN with IP Multicast to the RNC. The synchronization information is used in the radio interface for the user data transmission synchronization across the RNCs as described in TS 25.346 [10]. It is up to RAN configurations whether the inter-RNC MBMS combining/MBSFN operation mode is used during the MBMS payload delivery. + +### 6.5.3 IP Multicast distribution for E-UTRAN and UTRAN for EPS + +The MBMS GW chooses an IP Multicast address for distribution or, optionally, in the case of E-UTRAN access (e.g. in deployments with a mix of IPv4 and IPv6 eNodeBs and/or backhauls) and if the MBMS-GW supports both IPv4 and IPv6, both an IPv4 and an IPv6 IP Multicast address for distribution. The IP Multicast Addresses may be unique for the MBMS bearer service, or it may be reused from another active MBMS bearer service with an identical service area and of the same QoS. The proposed IP Multicast and Source addresses for distribution is indicated by the MBMS GW to the downstream MMEs and/or SGSNs at Session Start. The MME/SGSN forwards the request to the downstream eNodeB/RNC at Session Start. + +In the UTRAN case, the RNC may accept or reject the proposed IP Multicast distribution in the MBMS Session Start Response to the SGSN. The RNC node shall indicate to SGSN if IP Multicast distribution is accepted in the Session Start Response. If accepted the RNC shall report the channel (IP Multicast and Source address) to the backbone in order to join the bearer service multicast distribution. For an IP Multicast address that is shared by several MBMS bearer services, RNC only reports to the backbone once. At Session Stop the RNC shall correspondingly report to the backbone in order to leave the bearer service multicast distribution. For a MBMS bearer service that shares the IP Multicast address with one or more other MBMS bearer service(s), the RNC does only report to the backbone at session stop of the last remaining bearer service that has used a shared IP Multicast address. If one or more downstream RNC nodes do not accept IP Multicast distribution, the SGSN will establish a normal MBMS point-to-point GTP-U tunnel to related RNCs and a point-to-point GTP-U tunnel to the MBMS GW. The SGSN does not respond to the MBMS GW until it has received responses from all RNCs or until a configurable time has elapsed (e.g. with a recommended default of 5 seconds). The SGSN shall indicate to the MBMS GW if IP Multicast distribution is accepted (by one or more RNCs) and it shall also indicate if normal MBMS point-to-point distribution is required (by one or more RNCs). The RNC node shall indicate to SGSN if IP Multicast distribution is accepted in the Session Start Response. If this indication is missing, the SGSN node shall treat the RNC node as not accepting IP Multicast distribution and use unicast distribution. + +IP Multicast distribution is only used within a PLMN. + +MBMS GW shall assign IP Multicast addresses used for MBMS distribution according to RFC 4607 [21]. When several MBMS GWs are used for MBMS payload distribution, the used IP Multicast addresses shall be coordinated by configuration. Clashes between common TEIDs allocated by MBMS GW and TEIDs allocated by eNodeB/RNC should be avoided by coordinated TEID ranges. + +The receiving node controls itself what is received using the IGMPv3/MLDv2 protocol RFC 4604 [22]. + +The MBMS payload with the synchronization information received from the BM-SC shall be distributed by the MBMS GW with IP Multicast to the eNodeB/RNC. The synchronization information is used in the radio interface for the user data transmission synchronization across the eNodeBs and RNCs as described in TS 25.346 [10]. It is up to RAN configurations whether the inter-RNC MBMS combining/MBSFN operation mode is used during the MBMS payload delivery. + +Mobility between cells may cause limited MBMS data loss towards the UE. Therefore, MBMS user services should be able to cope with potential data loss caused by UE mobility. + +# --- 7 Architectural Aspects of MBMS User Services + +MBMS bearers may be used in numerous ways to provide different types of applications. MBMS user services employ MBMS bearers and possibly point-to-point bearers in order to provide application data in an efficient manner. This clause is used to discuss different aspects of MBMS user services that directly relate to the usage of MBMS and point-to-point bearers. This clause is not intended to deal with the architecture and interfaces of MBMS user services. + +## 7.1 Alternative User Service Support + +For many MBMS services, it will be necessary to provide alternative means for the UE to access the service without using MBMS bearer capabilities. This is required, for example, after completion of the MBMS session for a file download to permit errors in the file to be corrected; to permit the network to charge for a successful download; to pass + +a decrypt key to the UE; etc. It may also be useful in cases where all or part of an MBMS transmission has been missed due to the UE being out of coverage, switched off, etc. + +Care is needed to ensure that such alternative access mechanisms do not create traffic that overloads the network (radio, RNC, BSC, SGSN, GGSN and BM-SC). In the case that such alternative access requires direct interaction between the UE and a network server, one way for this load to be distributed is for the BM-SC to distribute to each UE, at activation time, one or more server addresses (from a group of addresses), along with parameter(s) that are used to generate a random time dispersion of the requests. + +## 7.2 Avoid overload in SGSN, GGSN and BM-SC caused by Joining + +For Joining that is triggered by a service announcement (e.g. CBS or MBMS), then the service announcement needs to be able to contain parameters to help avoid overload in the SGSN, GGSN and BM-SC. The UE uses the defined parameters in the service announcement to randomly select the time at which to join the service. Hence the BM-SC needs to be able to generate the parameters and needs to be able to get them sent to the UE in the service announcement. + +## 7.3 Access aspects of MBMS user services + +In networks with multiple accesses, e.g. GERAN and UTRAN for GPRS, users may in some situations experience problems in receiving MBMS services. These situations include: + +- an operator that has chosen to provide a service on one access only (e.g. only on GERAN), and where a UE is camping on the wrong access (i.e. on UTRAN in the previous example) when an MBMS session is started. This UE may miss the MBMS content, as the MBMS architecture doesn't provide any mechanism for paging coordination, etc. +- an operator that has chosen to provide a service with different QoS levels e.g. on GERAN and UTRAN (see clause 5.1.5.2). A UE that is changing access type during an ongoing MBMS session may not be able sort the situation out and receive the MBMS content correctly. + +## 7.4 MBMS operation on Demand + +"MBMS operation on Demand" (MooD) allows certain content that is initially delivered over the unicast network to be turned into an MBMS User Service, in order to efficiently use network resources when the traffic exceeds a certain threshold. Two types of MBMS operation on Demand are described in TS 26.346 [7]: UE-Elected and Network-Elected offloading. In both types, there could be a network proxy/server to detect whether unicast traffic volume for the same service or content exceeds a certain threshold, and to indicate such occurrence to the BM-SC to enable MBMS offloading. The MooD feature is optional. + +UEs that support MooD functionality support handling of the MooD redirection message. To assist the MooD decision, the network proxy/server may obtain UE location by many possible means as per the operator's policy, including use of the current location field in the MooD Header. + +MooD is supported for E-UTRAN and UTRAN accesses. + +## 7.5 Enhanced TV services support over E-UTRAN + +Enhanced TV services over E-UTRAN enables operators and service providers to deliver TV services from broadcasters as well as 3rd party service providers. The separation of access to MBMS transport services from MBMS user services allow separate content delivery and transport services from the operators. This is achieved by: + +- A broadcast component where mechanisms to enable decoupling of content, MBMS service and MBMS transport, allowing the system to offer: MBMS transport only, a shared MBMS network between operators, broadcast only TV service to devices with no operator subscription. +- A unicast component via PDN connectivity is achieved through operator's EPC network, in which operator subscription for TV service may be achieved via dedicated APN. +- Enable mechanisms for broadcast/unicast fall-back support, consumption-based switching between unicast/broadcast are supported. + +- Support standardised interface between BM-SC and the content provider, as defined in TS 26.348 [31], in order to facilitate both transport and user services delivery for TV services via MBMS (for broadcast) and EPC (for unicast). + +There are 2 MBMS Service Types considered for TV service: + +- MBMS transport only mode: + - The 3GPP network provides only transport of data/TV content in a transparent manner. + - The 3rd party content provider's signalling and data transferred via MBMS bearer(s) are transparent to BM-SC and the MBMS bearer service. + - All other service aspects, e.g. decision of whether to send data over broadcast or unicast, is not within 3GPP network, and assumed to be performed by application server. +- MBMS full service mode: + - 3GPP MBMS system provides full service layer capability. + - BM-SC is aware of the content stream and is capable of transforming the content stream into 3GPP compliant stream. + - BM-SC can perform decision on whether to switch an MBMS user service between broadcast or unicast service. + +# --- 8 MBMS Procedures + +## 8.1 MBMS Notification + +### 8.1.1 Iu mode notification (UTRAN and GERAN) for GPRS + +When an MBMS Session starts, UEs interested in the MBMS bearer service (PMM-CONNECTED UEs and PMM-IDLE UEs) shall be notified. + +MBMS Session attributes such as Session Identifier and MBMS Service Area(s) are made available in all interested RNCs during the Session Start procedure. + +For radio efficiency reasons, the UTRAN may select on a per cell basis whether to establish point-to-point or point-to-multipoint links for the distribution of MBMS data to the UEs. + +In order to perform this selection, the UTRAN requests a proportion of UEs to move to PMM-CONNECTED mode by means of MBMS notification sent in the MBMS service Area. + +The exact number of UEs moved to PMM-CONNECTED mode is a decision of the RAN node. It is not necessary for all UEs to move to PMM-CONNECTED mode in order for the RAN to decide to use point-to-multipoint, other UEs may remain in PMM-IDLE state. This is a UTRAN choice (based on Radio Resource Management criteria). + +Following the decision to set up point-to-point or point-to-multipoint links, the number of UEs that need to be maintained in PMM-CONNECTED mode or moved to PMM-IDLE mode for MBMS data reception is also a decision of the RAN node. + +### 8.1.2 A/Gb mode notification (GERAN) + +When an MBMS Session starts, UEs interested in the MBMS bearer service and that are in READY or STANDBY states shall be notified. The MBMS notification triggers detection or counting of UEs per cell for selection of the most appropriate MBMS radio bearer. + +MBMS Session attributes such as Session Identifier, MBMS Service Area, QoS are made available in all interested BSCs that are connected to a registered SGSN by the Session Start procedure. + +## 8.2 MBMS Multicast Service Activation + +The MBMS multicast service activation procedure registers the user in the network to enable the reception of data from a specific multicast MBMS bearer service. The activation is a signalling procedure between the UE and the network. The procedure establishes MBMS UE contexts in UE, SGSN and GGSN and Iu mode BSC/RNC for each activated multicast MBMS bearer service comparable to regular PDP contexts. + +![Sequence diagram illustrating the activation of an MBMS multicast service. The diagram shows the interaction between UE, RAN, SGSN, GGSN, and BM-SC. The process starts with PDP Context Activation and IGMP Join from the UE. The GGSN sends an MBMS Authorization Request to the BM-SC, which responds. The GGSN then sends an MBMS Notification Request to the SGSN, which responds. The SGSN sends a Request MBMS Context Activation to the UE, which responds with Activate MBMS Context Request. The SGSN then sends an MBMS Notification Reject Request to the GGSN, which responds. The SGSN performs Security Functions and Invoke Trace. The GGSN sends a Create MBMS Context Request to the SGSN, which responds. The GGSN sends an MBMS Authorization Request to the BM-SC, which responds. The GGSN sends an MBMS Registration Request to the SGSN, which responds. The SGSN sends a Create MBMS Context Response to the GGSN, which responds. The SGSN sends an MBMS Registration Request to the UE, which responds. The SGSN performs Provision of MBMS UE Context to RAN and Invoke Trace. Finally, the SGSN sends an Activate MBMS Context Accept to the UE.](382a9c9e4816bd229191ab4591424dd8_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant SGSN + participant GGSN + participant BM-SC + + Note right of GGSN: GGSN + UE->>GGSN: 1. PDP Context Activation + UE->>GGSN: 2. IGMP Join + GGSN->>BM-SC: 3. MBMS Authorization Request + BM-SC-->>GGSN: 3. MBMS Authorization Response + GGSN->>SGSN: 4a. MBMS Notification Request + SGSN-->>GGSN: 4b. MBMS Notification Response + SGSN->>UE: 5. Request MBMS Context Activation + UE-->>SGSN: 6. Activate MBMS Context Request + SGSN->>GGSN: 7. MBMS Notification Reject Request + GGSN-->>SGSN: 7. MBMS Notification Reject Response + SGSN->>UE: 8. Security Functions + Note right of GGSN: GGSN + RAN-->>GGSN: 9. Invoke Trace + SGSN->>GGSN: 10. Create MBMS Context Request + GGSN->>BM-SC: 11. MBMS Authorization Request + BM-SC-->>GGSN: 11. MBMS Authorization Response + GGSN->>SGSN: 12. MBMS Registration Request + SGSN-->>GGSN: 12. MBMS Registration Response + SGSN->>GGSN: 13. Create MBMS Context Response + GGSN-->>SGSN: 14. MBMS Registration Request + SGSN-->>GGSN: 14. MBMS Registration Response + Note right of SGSN: 15. Provision of MBMS UE Context to RAN + RAN-->>GGSN: 16. Invoke Trace + SGSN->>UE: 17. Activate MBMS Context Accept + +``` + +Sequence diagram illustrating the activation of an MBMS multicast service. The diagram shows the interaction between UE, RAN, SGSN, GGSN, and BM-SC. The process starts with PDP Context Activation and IGMP Join from the UE. The GGSN sends an MBMS Authorization Request to the BM-SC, which responds. The GGSN then sends an MBMS Notification Request to the SGSN, which responds. The SGSN sends a Request MBMS Context Activation to the UE, which responds with Activate MBMS Context Request. The SGSN then sends an MBMS Notification Reject Request to the GGSN, which responds. The SGSN performs Security Functions and Invoke Trace. The GGSN sends a Create MBMS Context Request to the SGSN, which responds. The GGSN sends an MBMS Authorization Request to the BM-SC, which responds. The GGSN sends an MBMS Registration Request to the SGSN, which responds. The SGSN sends a Create MBMS Context Response to the GGSN, which responds. The SGSN sends an MBMS Registration Request to the UE, which responds. The SGSN performs Provision of MBMS UE Context to RAN and Invoke Trace. Finally, the SGSN sends an Activate MBMS Context Accept to the UE. + +**Figure 7: The activation of an MBMS multicast service** + +1. The UE activates a general purpose PDP context if one is not already established. +2. The UE sends an IGMP (IPv4) or MLD (IPv6) Join message over the default PDP context to signal its interest in receiving a particular multicast MBMS bearer service identified by an IP multicast address. +3. The GGSN sends an MBMS Authorization Request seeking authorization for the activating UE to receive data. The MBMS Authorization Request may include trace information (Additional MBMS Trace Info), if activated. The authorization decision, which may be based on subscription data in the BM-SC, Membership function is provided in the MBMS Authorization Response together with the APN to be used for creation of the MBMS UE context. If the MBMS Authorization Response indicates that the UE is not authorized to receive the MBMS data the process terminates with no additional message exchange. +- 4a. The GGSN sends an MBMS Notification Request (IP multicast address, APN, Linked NSAPI) to the SGSN. Linked NSAPI is set equal to the NSAPI of the PDP context over which the Join request was received. The IP + +multicast address is the one requested by the UE in the Join request. The APN may be different from the APN to which the default PDP context has been activated. In any case, the APN may resolve to a GGSN that is different from the GGSN receiving the IGMP/MLD Join request. + +- 4b. The SGSN sends a MBMS Notification Response (Cause) to the GGSN that sent the MBMS Notification Request, where Cause shall indicate whether or not the MBMS context activation will proceed. Upon reception of the response message with Cause indicating unsuccessful operation the GGSN should not send any further MBMS Notification Request messages. The procedure is then terminated. +5. The SGSN sends a Request MBMS Context Activation (IP multicast address, APN, Linked NSAPI, TI) to the UE to request it to activate an MBMS UE Context. Linked NSAPI allows the UE to associate the MBMS UE Context with the PDP context over which it sent the IGMP/MLD Join message in step 2. TI was chosen by the SGSN and contains a value not used by any other activated PDP context and MBMS UE context for this UE. +6. The UE creates an MBMS UE context and sends an Activate MBMS Context Request (IP multicast address, APN, MBMS\_NSAPI, MBMS bearer capabilities) to the SGSN. The IP multicast address identifies the MBMS multicast service, which the UE wants to join/activate. An APN may indicate a specific GGSN. The MBMS bearer capabilities indicate the maximum QoS the UE can handle. The MBMS\_NSAPI was chosen by the UE and contains a value not used by any other activated PDP context and MBMS UE context for this UE. If the SGSN has the MBMS Bearer Context information for this MBMS bearer service, the SGSN should verify the UE's MBMS bearer capabilities. If the SGSN determines that the UE's MBMS bearer capabilities are less than the Required MBMS Bearer Capabilities, it shall reject the request for activation of an MBMS context with an appropriate cause. +7. If the MBMS UE Context was not established, the SGSN sends a MBMS Notification Reject Request (Cause) to the GGSN that sent the MBMS Notification Request, where Cause shall indicate the reason why the MBMS UE Context could not be established. The GGSN then sends a MBMS Notification Reject Response back to the SGSN. This should prevent further sending of MBMS Notification Request messages. The procedure is then terminated. +8. Security Functions may be performed, e.g. to authenticate the UE. +9. In A/Gb mode and if BSS trace is activated, the SGSN shall send an Invoke Trace (Trace Reference, Trace Type, Trigger Id, and OMC Identity) message to the BSS. Trace Reference, and Trace Type are copied from the trace information received from the HLR or OMC. +10. The SGSN creates an MBMS UE context and sends a Create MBMS Context Requests (IP multicast address, APN, MBMS\_NSAPI, IMSI, MSISDN, RAI, IMEI-SV, RAT Type, MS Time Zone, CGI/SAI, Trace Reference, Trace Type, Trigger Id, OMC Identity , Additional MBMS Trace Info) to the GGSN. The SGSN shall include Trace Reference, Trace Type, Trigger Id, and OMC Identity if GGSN trace is activated. The SGSN shall include Additional MBMS Trace Info if BM-SC trace is activated. The SGSN shall copy Trace Reference, Trace Type, and OMC Identity from the trace information received from the HLR or OMC. The inclusion of CGI/SAI shall be according rules detailed in clause 15.1.1a in TS 23.060 [15]. +11. The GGSN sends an MBMS Authorization Request (IMSI, MSISDN, RAI, IMEI-SV, RAT Type, MS Time Zone, CGI/SAI, Additional MBMS Trace Info) seeking authorization for the activating UE. The GGSN shall include Additional MBMS Trace Info if BM-SC trace is activated. The CGI/SAI is included, if available. The authorization decision is provided in the MBMS Authorization Response. The BM-SC creates an MBMS UE Context. +12. If the GGSN does not have the MBMS Bearer Context information for this MBMS bearer service, the GGSN sends a MBMS Registration Request to the BM-SC. See clause "MBMS Registration Procedure". + +If no TMGI has been allocated for this MBMS bearer service, the BM-SC will allocate a new TMGI. This TMGI will be passed to GGSN and SGSN via the MBMS Registration Response message and further to UE via Activate MBMS Context Accept message. + +The BM-SC responds with a MBMS Registration Response containing the MBMS Bearer Context information for this MBMS bearer service and adds the identifier of the GGSN to the "list of downstream nodes" parameter in its MBMS Bearer Context. See clause "MBMS Registration Procedure". + +13. The GGSN creates an MBMS UE context and sends a Create MBMS Context Response to the SGSN. + +14. If the SGSN does not have the MBMS Bearer Context information for this MBMS bearer service, the SGSN sends a MBMS Registration Request to the GGSN. See clause "MBMS Registration Procedure". + +The GGSN responds with a MBMS Registration Response containing the MBMS Bearer Context information for this MBMS bearer service and adds the identifier of the SGSN to the "list of downstream nodes" parameter in its MBMS Bearer Context. See clause "MBMS Registration Procedure". + +15. The SGSN provides Iu mode RAN with the MBMS UE Context(s) if at least one PS RAB is established for the UE. + 16. In Iu mode and if trace is activated, the SGSN shall send an Invoke Trace (Trace Reference, Trace Type, Trigger Id, and OMC Identity) message to the RAN. Trace Reference, and Trace Type are copied from the trace information received from the HLR or OMC. +- NOTE: Step 16 is applied when the trace activation is triggered by means of signalling. Another alternative is the triggering of trace activation by the OMC. The details of both Trace Activation procedures are described in TS 32.422 [14]. +17. The SGSN sends an Activate MBMS Context Accept (TMGI) to the UE. If it was not possible to verify the UE's MBMS bearer capabilities in Step 6, the UE's MBMS bearer capabilities shall be verified now by the SGSN. If the SGSN determines that the UE's MBMS bearer capabilities are lower than the Required MBMS Bearer Capabilities the SGSN rejects the request for activation of an MBMS context indicating an appropriate cause and starts the deactivation of the already established MBMS UE contexts. + +### 8.2.1 Void + +## 8.3 MBMS Session Start Procedure + +### 8.3.0 General + +The BM-SC initiates the MBMS Session Start procedure when it is ready to send data. This is a request to activate all necessary bearer resources in the network for the transfer of MBMS data and to notify interested UEs of the imminent start of the transmission. + +Through this procedure, MBMS session attributes such as QoS, MBMS service Area, estimated session duration, are provided to the registered GGSN(s) and SGSN(s), to all BSCs/RNCs that are connected to a listed SGSN and to the registered MBMS GW(s) and MME(s). In addition the procedure allocates the bearer plane to all registered GGSNs, all registered SGSNs and all registered MBMS GWs, to BSCs/RNCs and E-UTRAN that respond to the session start request message. If IP multicast distribution of MBMS user plane data to E-UTRAN/UTRAN is supported, the MBMS-GW allocates an IP Multicast address together with the corresponding IP address of the multicast source (i.e. MBMS GW) and the C-TEID are provided to the eNodeB via MME and to the RNC via SGSN in this procedure. Optionally, in the case of E-UTRAN access (e.g. in deployments with a mix of IPv4 and IPv6 eNodeBs and/or backhauls) and if the MBMS-GW supports both IPv4 and IPv6, both an IPv4 and an IPv6 IP Multicast address together with the corresponding alternative IP addresses of the multicast source are also allocated by the MBMS-GW and provided to the E-UTRAN via the MME. An IP multicast address and the paired IP address of the multicast source shall be of the same IP type. + +After sending the Session Start Request message the BM-SC waits for a configurable delay (time to MBMS data transfer) before sending MBMS data. This delay should be long enough to avoid buffering of MBMS data in entities other than the BM-SC, i.e. the delay should allow the network to perform all procedures required to enable MBMS data transfer before the BM-SC sends MBMS data. For example notification of UEs and radio bearer establishment should be performed before MBMS data arrive in the RAN. The delay may be in the region of multiple seconds or tens of seconds. It may be useful for the BM-SC to be able to configure different delays for MBMS bearer services on 2G, 3G and E-UTRAN, respectively. + +For the distributed MCE architectures, i.e. when the MCE is part of the eNB as described in clause 15.1.1 in TS 36.300 [17], an absolute time stamp for when data can be expected, "MBMS data transfer start", should be used at MBSFN operation mode to ensure synchronized session control and to facilitate a graceful reallocation of resources for the MBSFN when needed. When the parameter "MBMS data transfer start" is present, a receiving supporting node shall ignore the parameter "time to MBMS data transfer". For session stop signalling, the parameter "MBMS data transfer stop" is if present used to schedule the release of the radio resources in order to ensure a synchronized session control. + +### 8.3.1 MBMS Session Start Procedure for GERAN and UTRAN for GPRS + +For multicast MBMS bearer services the registration of SGSNs and GGSNs is initiated by MBMS multicast Service Activation procedures, Inter SGSN Routeing Area Update procedures, Inter SGSN Serving RNS Relocation procedure and performed by MBMS Registration procedures. The GGSN keeps track of the registered SGSNs in the list of downstream nodes. + +For broadcast MBMS bearer services the list of downstream nodes of BM-SC and GGSN are achieved in the following ways: + +- The list of downstream nodes for GGSN will be sent from the BM-SC to the GGSN in the Session Start Request. + +Normally, the GGSN contained in the "list of downstream nodes" for BM-SC is the default GGSN (or two for resilience). + +The overall Session Start procedure is presented in the following figure: + +![Sequence diagram of the Session Start procedure for GERAN and UTRAN for GPRS. The diagram shows five lifelines: UE, BSC/RNC, SGSN, GGSN, and BM-SC. The sequence of messages is: 1. BM-SC sends a Session Start Request to GGSN; 2. GGSN sends a Session Start Response to BM-SC; 3. GGSN sends an MBMS Session Start Request to SGSN; 4. SGSN sends an MBMS Session Start Request to BSC/RNC; 5. BSC/RNC sends an MBMS Session Start Response to SGSN; 6. SGSN sends an MBMS Session Start Response to GGSN; 7. A dashed box labeled '4. RAN Resource Setup' is shown between UE and BSC/RNC; 8. BSC/RNC sends an IGMPv3 Membership Report to GGSN.](e94cbc0895c6914a2bb53f150ab7495e_img.jpg) + +``` + +sequenceDiagram + participant BM-SC + participant GGSN + participant SGSN + participant BSC/RNC + participant UE + + Note right of BM-SC: 1. Session Start Request + BM-SC->>GGSN: 1. Session Start Request + Note right of GGSN: 1. Session Start Response + GGSN-->>BM-SC: 1. Session Start Response + Note right of GGSN: 2. MBMS Session Start Request + GGSN->>SGSN: 2. MBMS Session Start Request + Note right of SGSN: 3. MBMS Session Start Request + SGSN->>BSC/RNC: 3. MBMS Session Start Request + Note right of BSC/RNC: 3. MBMS Session Start Response + BSC/RNC-->>SGSN: 3. MBMS Session Start Response + Note right of SGSN: 2. MBMS Session Start Response + SGSN-->>GGSN: 2. MBMS Session Start Response + Note left of BSC/RNC: 4. RAN Resource Setup + Note right of BSC/RNC: 3a. IGMPv3 Membership Report + BSC/RNC-->>GGSN: 3a. IGMPv3 Membership Report + +``` + +Sequence diagram of the Session Start procedure for GERAN and UTRAN for GPRS. The diagram shows five lifelines: UE, BSC/RNC, SGSN, GGSN, and BM-SC. The sequence of messages is: 1. BM-SC sends a Session Start Request to GGSN; 2. GGSN sends a Session Start Response to BM-SC; 3. GGSN sends an MBMS Session Start Request to SGSN; 4. SGSN sends an MBMS Session Start Request to BSC/RNC; 5. BSC/RNC sends an MBMS Session Start Response to SGSN; 6. SGSN sends an MBMS Session Start Response to GGSN; 7. A dashed box labeled '4. RAN Resource Setup' is shown between UE and BSC/RNC; 8. BSC/RNC sends an IGMPv3 Membership Report to GGSN. + +**Figure 8a: Session Start procedure for GERAN and UTRAN for GPRS** + +1. The BM-SC Session and Transmission function sends a Session Start Request message to indicate the impending start of the transmission and to provide the session attributes (TMGI, Flow Identifier (Broadcast only), QoS, MBMS service Area, Session identifier, estimated session duration, broadcast/multicast, list of downstream nodes for GGSN (Broadcast only), time to MBMS data transfer, MBMS HC indicator (if header compression is used for MBMS payload), ...) and the 2G/3G indicator. The message is sent to the BM-SC Proxy and Transport function, which then forwards it to the GGSNs listed in the "list of downstream nodes" parameter of the corresponding MBMS Bearer Context. The BM-SC Proxy and Transport function sets the state attribute of its MBMS Bearer Context to 'Active'. For a broadcast MBMS bearer service the GGSN creates an MBMS bearer context. In broadcast mode, the BM-SC may start multiple sessions for the same MBMS bearer service (identified by the TMGI) but with different content. If so, a Flow Identifier is included in the Session Start Request to identify the different sub-sessions and the associated MBMS Service Areas shall not overlap. The GGSN stores the session attributes and the list of downstream nodes in the MBMS Bearer Context, sets the state attribute of its MBMS Bearer Context to 'Active' and sends a Session Start Response message to the BM-SC. Proxy and Transport function which forwards it to the BM-SC Session and Transmission function. The BM-SC Proxy and Transport function copies Session Start Requests to the BM-SC Membership function for charging purposes. +2. The GGSN sends an MBMS Session Start Request message containing the session attributes (TMGI, Flow Identifier (Broadcast only), QoS, MBMS service Area, Session identifier, estimated session duration, broadcast/multicast, time to MBMS data transfer, IP Multicast and Source addresses for backbone distribution, common TEID-U, MBMS HC indicator, ...) and the 2G/3G indicator to the SGSNs listed in the "list of downstream nodes" parameter of the corresponding MBMS Bearer Context. For a broadcast MBMS bearer service the SGSN creates an MBMS bearer context. The SGSN stores the session attributes and the 2G/3G indicator in the MBMS Bearer Context, sets the state attribute of its MBMS Bearer Context to 'Active'. If one or + +more of the downstream nodes accepts the Session Start and the proposed IP Multicast and Source address for backbone distribution and the proposed C-TEID, the SGSN includes an indication that IP Multicast distribution is accepted in the MBMS Session Start Response message to GGSN. If one or more of the downstream nodes does not accept the proposed IP Multicast and Source address for backbone distribution or the proposed C-TEID or if there are downstream BSCs in Gb mode connected to the SGSN, the SGSN falls back to normal point-to-point MBMS bearer establishment for these nodes and responds with an MBMS Session Start Response message providing the TEID for bearer plane that the GGSN shall use for forwarding the MBMS data. Otherwise if all nodes accept multicast, the SGSN returns the C-TEID and the IP Multicast distribution address in the Session Start Response message. The GGSN shall initiate IP Multicast distribution if at least one of the SGSNs indicates it has accepted IP Multicast distribution. For MBMS bearer service a SGSN receiving multiple MBMS Session Start Request messages establishes only one bearer plane with one GGSN. + +3. The SGSN sends an MBMS Session Start Request message including the session attributes (TMGI, QoS, MBMS service Area, Session identifier, estimated session duration, broadcast/multicast, time to MBMS data transfer, list of RAs, MBMS HC indicator, ...) to each BSC and/or each RNC that is connected to this SGSN. When the message is sent to an RNC/BSC in Iu mode, the IP Multicast and Source address for backbone distribution and C-TEID shall also be included if received from the GGSN. The 2G/3G indicator shall be used by the SGSN to determine whether the MBMS Session Start Request message is sent only to BSCs, or only to RNCs, or to both RNCs and BSCs. For a broadcast MBMS bearer service the BSC/RNC creates an MBMS Service Context. The BSC in Iu mode/RNC stores the session attributes in the MBMS Service Context, sets the state attribute of its MBMS Service Context to 'Active'. If the RNC accepts the Session start and the proposed IP Multicast and Source address for backbone distribution and the proposed C-TEID the RNC sends an MBMS Session Start Response message to SGSN including an indication that IP Multicast distribution is accepted. If an RNC does not accept the proposed IP Multicast and Source address for backbone distribution (or the proposed C-TEID), the RNC falls back to normal point-to-point MBMS bearer establishment. A BSC in Gb mode which does not serve the MBMS Service Area need not store the session attributes. A BSC/RNC receiving multiple MBMS Session Start Request messages establishes only one bearer plane with one SGSN. +- 3a If the BSC/RNC accepts IP Multicast distribution the BSC/RNC joins the multicast group in the IP backbone according to RFC 3376 [19], RFC 3810 [20] and RFC 4604 [22]. +4. The BSC/RNC establishes the necessary radio resources for the transfer of MBMS data to the interested UEs. RAN resource set up can be scheduled according to the time to MBMS data transfer parameter. + +NOTE: The upstream node normally provides the MBMS Session Start Request message once per MBMS session to a downstream node. Due to "Intra Domain Connection of RAN Nodes to Multiple Core Network Nodes" however, a BSC/RNC may receive the MBMS Session Start Request message from several SGSNs. + +### 8.3.2 MBMS Session Start Procedure for E-UTRAN and UTRAN for EPS + +The list of downstream nodes of BM-SC and the list of MBMS control plane nodes (MMEs and SGSNs) of MBMS GW are achieved in the following ways: + +- The list of MBMS control plane nodes for MBMS GW will be sent from the BM-SC to the MBMS GW in the Session Start Request. + +Normally, the MBMS GW contained in the "list of downstream nodes" for BM-SC is the default MBMS GW (or two for resilience). + +The overall Session Start procedure is presented in the following figures: + +![Sequence diagram for Figure 8b.1: Session Start procedure for E-UTRAN and UTRAN for EPS. Lifelines: UE, E-UTRAN/UTRAN, MME/SGSN, MBMS GW, BM-SC. The sequence shows the BM-SC sending a Session Start Request to the MBMS GW, which then forwards it to the MME/SGSN, then to the E-UTRAN/UTRAN. Responses are sent back up the chain. The E-UTRAN/UTRAN performs RAN Resource Setup and IP Multicast Join. Finally, MBMS data is sent from the BM-SC through the MBMS GW and E-UTRAN/UTRAN to the UE.](8269648391c59363ea61243864a2adf7_img.jpg) + +``` + +sequenceDiagram + participant UE + participant E-UTRAN/UTRAN + participant MME/SGSN + participant MBMS GW + participant BM-SC + BM-SC->>MBMS GW: 1. Session Start Request + MBMS GW->>BM-SC: 2. Session Start Response + MBMS GW->>MME/SGSN: 3. Session Start Request + MME/SGSN->>E-UTRAN/UTRAN: 4. Session Start Request + E-UTRAN/UTRAN->>MME/SGSN: 5. Session Start Response + MME/SGSN->>MBMS GW: 6. Session Start Response + Note over UE, E-UTRAN/UTRAN: 7. RAN Resource Setup (Dashed Box) + Note over E-UTRAN/UTRAN, MME/SGSN: 8. IP Multicast Join (Dashed Box) + BM-SC->>MBMS GW: 9. MBMS data + MBMS GW->>E-UTRAN/UTRAN: 10. MBMS data + +``` + +Sequence diagram for Figure 8b.1: Session Start procedure for E-UTRAN and UTRAN for EPS. Lifelines: UE, E-UTRAN/UTRAN, MME/SGSN, MBMS GW, BM-SC. The sequence shows the BM-SC sending a Session Start Request to the MBMS GW, which then forwards it to the MME/SGSN, then to the E-UTRAN/UTRAN. Responses are sent back up the chain. The E-UTRAN/UTRAN performs RAN Resource Setup and IP Multicast Join. Finally, MBMS data is sent from the BM-SC through the MBMS GW and E-UTRAN/UTRAN to the UE. + +**Figure 8b.1: Session Start procedure for E-UTRAN and UTRAN for EPS** + +![Sequence diagram for Figure 8b.2: Session Start procedure for E-UTRAN for EPS with delayed response. Lifelines: UE, E-UTRAN, MME, MBMS GW, BM-SC. The sequence is similar to Figure 8b.1 but the MBMS GW sends its Session Start Response to the BM-SC (step 2) after receiving the Session Start Response from the MME (step 6).](9a14684f8ae1345c6efea6f5994c730c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant E-UTRAN + participant MME + participant MBMS GW + participant BM-SC + BM-SC->>MBMS GW: 1. Session Start Request + MBMS GW->>MME: 3. Session Start Request + MME->>E-UTRAN: 4. Session Start Request + Note over UE, E-UTRAN: 7. RAN Resource Setup (Dashed Box) + E-UTRAN->>MME: 5. Session Start Response + MME->>MBMS GW: 6. Session Start Response + MBMS GW->>BM-SC: 2. Session Start Response + Note over E-UTRAN, MME: 8. IP Multicast Join (Dashed Box) + BM-SC->>MBMS GW: 9. MBMS data + MBMS GW->>E-UTRAN: 10. MBMS data + +``` + +Sequence diagram for Figure 8b.2: Session Start procedure for E-UTRAN for EPS with delayed response. Lifelines: UE, E-UTRAN, MME, MBMS GW, BM-SC. The sequence is similar to Figure 8b.1 but the MBMS GW sends its Session Start Response to the BM-SC (step 2) after receiving the Session Start Response from the MME (step 6). + +**Figure 8b.2: Session Start procedure for E-UTRAN for EPS with delayed response** + +1. BM-SC sends a Session Start Request message to MBMS GW to indicate the impending start of the transmission and to provide the session attributes (TMGI, Flow Identifier, QoS, MBMS service Area, list of cell IDs if available, Session identifier, estimated session duration, list of MBMS control plane nodes (MMEs, SGSNs) for MBMS GW, time to MBMS data transfer, MBMS data transfer start, access indicator, ...). The message is sent to the MBMS GWs listed in the "downstream nodes" parameter of the corresponding MBMS Bearer Context in the BM-SC. The BM-SC may start multiple sessions for the same MBMS bearer service (identified by the TMGI) but with different content. If so, a Flow Identifier is included in the Session Start Request to identify the different sub-sessions and the associated MBMS Service Areas shall not overlap. The Access indicator indicates in which radio access types the MBMS service should be broadcasted, i.e. UTRAN, or E-UTRAN, or both. The Access indicator may be included in charging information generated by the MBMS GW. + +If MBMS-GW is configured to delay response to BMSC when access type is E-UTRAN, then MBMS-GW delays response to BMSC (i.e. step 2) until after step 6 is executed as shown in figure 8b.2. This configuration should be only performed when E-UTRAN executes step 7 below before responding to the MBMS Session Start message as specified in TS 36.300 [17]. + +NOTE: It is up to the operator to ensure that E-UTRAN, MBMS-GW and BMSC are configured only when E-UTRAN supports delaying the response from eNB. + +2. The MBMS GW responds with a Session Start Response message with information for BM-SC to send MBMS data to the MBMS GW , if figure 8b.1 is executed. The MBMS-GW responds only after first MME response in step 6 is received, if it is configured to do so as shown in figure 8b.2. +3. The MBMS GW creates an MBMS bearer context. The MBMS GW stores the session attributes and the list of MBMS control plane nodes in the MBMS bearer context and allocates a transport network IP multicast address or, optionally, for E-UTRAN access (e.g. in deployments with a mix of IPv4 and IPv6 eNodeBs and/or backhauls) and if the MBMS-GW supports both IPv4 and IPv6, both an IPv4 and an IPv6 IP Multicast address, according to clause 6.5.3 and a C-TEID for this session. The MBMS GW sends a Session Start Request message including the session attributes (TMGI, Flow Identifier, QoS, MBMS service Area, list of cell IDs if available, Session identifier, estimated session duration, transport network IP Multicast Address(es), IP address(es) of the multicast source, C-TEID, ...) to MMEs and/or SGSNs listed in the "list of MBMS control plane nodes" parameter after filtering the list using the Access indicator, thus ignoring entries not consistent with the Access indicator. +4. The MME or SGSN creates an MBMS bearer context. The MME/SGSN stores the session attributes and sends a Session Start Request message including the session attributes (TMGI, QoS, MBMS service area, list of cell IDs if available, Session identifier, estimated session duration, broadcast (for UTRAN only), transport network IP Multicast Address, IP address of the multicast source, C-TEID, ...) to E-UTRAN/UTRAN. Optionally in the case of E-UTRAN access and if the MBMS-GW supports both IPv4 and IPv6, the MME includes both an IPv4 and an IPv6 IP Multicast address together with the corresponding alternative IP address(es) of the multicast source. When connected to multiple MCEs, the MME should filter the distribution of Session Control message to the MCEs based on the MBMS service area. + +For UTRAN, if one or more of the downstream nodes accepts the Session Start with the proposed IP Multicast and Source addresses for backbone distribution and the proposed C-TEID, the SGSN includes an indication that IP Multicast distribution is accepted in the MBMS Session Start Response message to MBMS GW. If one or more of the downstream nodes does not accept the proposed IP Multicast and Source addresses for backbone distribution or the proposed C-TEID, the SGSN falls back to normal point-to-point MBMS bearer establishment for these nodes and responds with an MBMS Session Start Response message providing the TEID for bearer plane that the MBMS GW shall use for forwarding the MBMS data. Otherwise if all nodes accept multicast, the SGSN returns the C-TEID and the IP Multicast distribution address in the Session Start Response message. + +For E-UTRAN access, eNB may respond to Session Start Request after first successful MBMS resources have been reserved (i.e. step 7) which indicates to the BMSC that there are resources already available for MBMS data delivery, as shown in figure 8b.2. + +5. The E-UTRAN/UTRAN creates an MBMS bearer context. The E-UTRAN/UTRAN stores the session attributes, sets the state attribute of its MBMS Bearer Context to 'Active' (in UTRAN only) and responds the MME/SGSN to confirm the reception of the Session Start Request message. When a cell ID list is included in the Session Start Request, E-UTRAN uses it to determine a set of radio resources to be used for the broadcast. Based on the cell ID list, the set of radio resources selected may be reduced from the full set of resources defined by the MBMS service area. The E-UTRAN ensures that all of its corresponding nodes make the same decision on the reduced set. + +For UTRAN, if an RNC accepts the Session start and the proposed IP Multicast and Source addresses for backbone distribution and the proposed C-TEID the RNC sends an MBMS Session Start Response message to SGSN including an indication that IP Multicast distribution is accepted. If an RNC does not accept the proposed IP Multicast and Source address for backbone distribution (or the proposed C-TEID), the RNC falls back to normal point-to-point MBMS bearer establishment. + +6. The MME/SGSN stores the session attributes and the identifier of the eNBs/RNCs as the "list of downstream nodes" parameter in its MBMS Bearer Context and responds to the MBMS GW. The SGSN should wait for a response from all UTRAN nodes (until an acceptable duration) to be able to report to the MBMS-GW whether all, part or none of the RNCs have accepted IP multicast distribution and to provide an SGSN IP address and TEID for user plane over Sn if some RNCs did not accept IP multicast distribution. The MME may return an + +MBMS Session Start Response to the MBMS-GW as soon as the session request is accepted by one E-UTRAN node. The MBMS-GW initiates IP Multicast distribution and/or point-to-point MBMS bearers (for UTRAN only) depending on the responses from the MMEs/SGSNs. + +If the MBMS-GW is configured to delay response to the BMSC, MBMS-GW waits until step 6 occurs before responding to the BMSC as shown in figure 8b.2. + +7. The E-UTRAN/UTRAN establishes the necessary radio resources for the transfer of MBMS data to the interested UEs. For E-UTRAN the radio resource set up is scheduled using the MBMS data transfer start parameter if it is present, otherwise using the time to MBMS data transfer parameter. The MBMS data transfer start parameter is not used by UTRAN. +8. If the E-UTRAN/UTRAN node accepts IP Multicast distribution, it joins the appropriate transport network IP multicast address (including the IP address of the multicast source) allocated by the MBMS GW, to enable reception of MBMS data. If several MBMS bearer services uses the same IP multicast address, the join is only done once. +9. The BM-SC starts sending the MBMS data. +10. MBMS GW function receives MBMS data. MBMS GW sends the MBMS data using IP multicast distribution towards all joined eNodeBs/RNCs. + +## 8.4 MBMS Registration Procedure + +The MBMS Registration is the procedure by which a downstream node informs an upstream node that it would like to receive session attributes and data for a particular MBMS bearer service in order to distribute it further downstream. This procedure builds up a distribution tree for the delivery of MBMS session attributes and data from the BM-SC to the UEs interested in the service. This procedure results in the set-up of a corresponding MBMS Bearer Context in the nodes along the distribution tree, but it does not result in the establishment of bearer plane which will be established by the Session Start procedure. + +The MBMS Registration procedure is initiated: + +- When the first MBMS UE Context for a particular MBMS bearer service is created in the SGSN or GGSN (see clause "MBMS UE Context") and the corresponding MBMS Bearer Context is not already established in the node; +- When an MBMS Registration Request for a particular MBMS bearer service is received from a downstream node but the corresponding MBMS Bearer Context is not established in the node; or +- When a DRNC detects that it hosts UEs interested in the MBMS bearer service. + +NOTE: The terms 'downstream' and 'upstream' refer to the topological position of one node with respect to another and relative to the direction of the MBMS data flow, i.e. from BM-SC to UE. + +![Sequence diagram of the MBMS Registration procedure showing interactions between RNC, SGSN, GGSN, and BM-SC.](822e033872d5ab16e861571f47b81ba7_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant SGSN + participant GGSN + participant BM-SC + + Note right of RNC: 1. MBMS Registration Request + RNC->>SGSN: 1. MBMS Registration Request + Note right of SGSN: 2. MBMS Registration Request + SGSN->>GGSN: 2. MBMS Registration Request + Note right of GGSN: 3. MBMS Registration Request + GGSN->>BM-SC: 3. MBMS Registration Request + Note right of BM-SC: 4. MBMS Registration Response + BM-SC-->>GGSN: 4. MBMS Registration Response + Note right of GGSN: 4. MBMS Session Start Procedure + GGSN-->>SGSN: 5. MBMS Registration Response + Note right of SGSN: 5. MBMS Session Start Procedure + SGSN-->>RNC: 6. MBMS Registration Response + Note right of RNC: 6. MBMS Session Start Procedure + +``` + +The diagram illustrates the MBMS Registration procedure across four network elements: RNC, SGSN, GGSN, and BM-SC. The sequence of messages is as follows: + + +- The RNC sends an **1. MBMS Registration Request** to the SGSN. +- The SGSN forwards this as **2. MBMS Registration Request** to the GGSN. +- The GGSN forwards this as **3. MBMS Registration Request** to the BM-SC. +- The BM-SC responds with **4. MBMS Registration Response** back to the GGSN. Simultaneously, the **4. MBMS Session Start Procedure** is initiated within the GGSN. +- The GGSN then sends **5. MBMS Registration Response** back to the SGSN. Simultaneously, the **5. MBMS Session Start Procedure** is initiated within the SGSN. +- Finally, the SGSN sends **6. MBMS Registration Response** back to the RNC. Simultaneously, the **6. MBMS Session Start Procedure** is initiated within the RNC. + + The Session Start Procedures are shown as dashed boxes, indicating they occur concurrently with the registration responses at each node. + +Sequence diagram of the MBMS Registration procedure showing interactions between RNC, SGSN, GGSN, and BM-SC. + +Figure 9: MBMS Registration procedure + +1. When the DRNC detects that it hosts UEs interested in the MBMS bearer service, the DRNC sends a MBMS Registration Request message to its parent SGSN if not already done. How the RNC determines its parent SGSN is a matter of implementation. +2. If the SGSN has no MBMS Bearer Context for an MBMS bearer service and the SGSN receives an MBMS Registration Request from an RNC for this MBMS bearer service, or if the first MBMS UE Context is created in the SGSN for an MBMS bearer service for which the SGSN has no corresponding MBMS Bearer Context, the SGSN creates an MBMS Bearer Context (in "Standby" state) and sends an MBMS Registration request (IP multicast address, APN) message to the GGSN. How the SGSN selects a GGSN is a matter of implementation; it may for instance be based on prior signalling related to a particular UE or via APN resolution. +3. If the GGSN has no MBMS Bearer Context for an MBMS bearer service and the GGSN receives an MBMS Registration from an SGSN for this MBMS bearer service, or when the first MBMS UE Context is created in the GGSN for an MBMS bearer service for which the GGSN has no MBMS Bearer Context, the GGSN creates an MBMS Bearer Context (in "Standby" state) and sends a Registration Request (IP multicast address, APN) message to the BM-SC. Proxy and Transport function The exact nature of the signalling between GGSN and BM-SC via Gmb interface is specified in TS 29.061 [4]. +4. Upon reception of an MBMS Registration Request from a GGSN, the BM-SC Proxy and Transport function adds the identifier of the GGSN to the "list of downstream nodes" parameter in its MBMS Bearer Context and responds with a MBMS Registration Response (TMGI, Required Bearer Capabilities) message. The exact nature of the signalling between GGSN and BM-SC via Gmb interface is specified in TS 29.061 [4]. If the MBMS Bearer Context is in the 'Active' state, the BM-SC initiates the Session Start procedure with the GGSN, as described in clause "MBMS Session Start Procedure". +5. If the GGSN receives a Registration Request from the SGSN in step 2, the GGSN: + - adds the identifier of the SGSN to the "list of downstream nodes" parameter in its MBMS Bearer Context, + - responds with an MBMS Registration Response (TMGI, Required Bearer Capabilities) message, and + - if the MBMS Bearer Context is in the 'Active' state, initiates the Session Start procedure with the SGSN, as described in clause "MBMS Session Start Procedure". +6. If the SGSN received MBMS Registration Request from the DRNC in step 1, the SGSN: + - adds the identifier of the RNC to the "list of downstream nodes" parameter in its MBMS Bearer Context, + - responds with an MBMS Registration Response message, and + - if the MBMS Bearer Context is in the 'Active' state, initiates the Session Start procedure with the DRNC, as described clause "MBMS Session Start Procedure". + +## 8.5 MBMS Session Stop Procedure + +### 8.5.0 General + +The BM-SC Session and Transmission function initiates the MBMS Session Stop procedure when it considers the MBMS session to be terminated. The session is typically terminated when there is no more MBMS data expected to be transmitted for a sufficiently long period of time to justify a release of bearer plane resources in the network. For GERAN and UTRAN for GPRS, the procedure is propagated to all SGSNs and GGSNs that are registered for the corresponding MBMS bearer service and to BSCs/RNCs that have an established Iu bearer plane with an SGSN. For E-UTRAN and UTRAN for EPS, the procedure is propagated to all MBMS GWs, MMEs and SGSNs that are registered for corresponding MBMS bearer service and to E-UTRAN/UTRAN that have accept to receive IP multicast distribution. + +### 8.5.1 MBMS Session Stop Procedure for GERAN and UTRAN for GPRS + +The overall MBMS Session Stop procedure is presented in the following figure: + +![Sequence diagram of MBMS Session Stop procedure for GERAN and UTRAN for GPRS. Lifelines: UE, BSC/RNC, SGSN, GGSN, BM-SC. The sequence starts with BM-SC sending a Session Stop Request to GGSN, which responds. GGSN then sends an MBMS Session Stop Request to SGSN, which responds. SGSN sends an MBMS Session Stop Request to BSC/RNC, which responds. BSC/RNC sends an IGMPv3 Membership Report to UE. Finally, a dashed box labeled '4. RAN Resource Release' is shown between UE and BSC/RNC.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +``` + +sequenceDiagram + participant UE + participant BSC/RNC + participant SGSN + participant GGSN + participant BM-SC + + Note right of BM-SC: 1. Session Stop Request + BM-SC->>GGSN: 1. Session Stop Request + Note right of GGSN: 1. Session Stop Response + GGSN->>BM-SC: 1. Session Stop Response + Note right of GGSN: 2. MBMS Session Stop Request + GGSN->>SGSN: 2. MBMS Session Stop Request + Note right of SGSN: 2. MBMS Session Stop Response + SGSN->>GGSN: 2. MBMS Session Stop Response + Note right of SGSN: 3. MBMS Session Stop Request + SGSN->>BSC/RNC: 3. MBMS Session Stop Request + Note right of BSC/RNC: 3. MBMS Session Stop Response + BSC/RNC->>SGSN: 3. MBMS Session Stop Response + Note right of BSC/RNC: 3a. IGMPv3 Membership Report + BSC/RNC->>UE: 3a. IGMPv3 Membership Report + Note left of UE: 4. RAN Resource Release + UE-->>BSC/RNC: 4. RAN Resource Release + +``` + +Sequence diagram of MBMS Session Stop procedure for GERAN and UTRAN for GPRS. Lifelines: UE, BSC/RNC, SGSN, GGSN, BM-SC. The sequence starts with BM-SC sending a Session Stop Request to GGSN, which responds. GGSN then sends an MBMS Session Stop Request to SGSN, which responds. SGSN sends an MBMS Session Stop Request to BSC/RNC, which responds. BSC/RNC sends an IGMPv3 Membership Report to UE. Finally, a dashed box labeled '4. RAN Resource Release' is shown between UE and BSC/RNC. + +**Figure 10: MBMS Session Stop procedure for GERAN and UTRAN for GPRS** + +1. The BM-SC Session and Transmission function sends a Session Stop Request message to the BM-SC Proxy and Transport function, which forwards it to all GGSNs listed in the "list of downstream nodes" parameter of the affected MBMS Bearer Context to indicate that the MBMS session is terminated and the bearer plane resources can be released. The MBMS Bearer Context is uniquely identified by the TMGI or the combination of TMGI and Flow Identifier. The BM-SC Proxy and Transport function sets the state attribute of its MBMS Bearer Context to 'Standby'. The GGSN sends a Session Stop Response message to the BM-SC Proxy and Transport function, which forwards it to the BM-SC Session and Transmission function. The BM-SC Proxy and Transport function copies Session Stop Requests to the BM-SC Membership function for charging purposes. +2. The GGSN sends an MBMS Session Stop Request message to all SGSNs that have a bearer plane established with the GGSN, releases the corresponding bearer plane resources towards these SGSNs and sets the state attribute of its MBMS Bearer Context to 'Standby'. The GGSN releases the MBMS Bearer Context in case of a broadcast MBMS bearer service. +3. The SGSN releases the TEID and bearer plane resources on which it was receiving MBMS data from the GGSN for the affected MBMS bearer service and sends an MBMS Session Stop Request message to all BSCs/RNCs that have a bearer plane established with the SGSN and sets the state attribute of its MBMS Bearer Context to 'Standby'. The SGSN releases the MBMS Bearer Context in case of a broadcast MBMS bearer service. +- 3a If the RNC/BSC is using IP multicast distribution it shall disable reception from the IP backbone of the particular MBMS bearer service according to RFC 3376 [19], RFC 3810 [20] and RFC 4604 [22]. +4. The RNC releases the affected radio and Iu resources; the BSC releases the affected radio resources. The BSC/RNC sets the state attribute of its MBMS Bearer Context to 'Standby'. The BSC/RNC releases the MBMS Service Context in case of a broadcast MBMS bearer service. A BSC in Gb mode shall send an acknowledgement to the SGSN even if there is no active MBMS context in the BSC. + +### 8.5.2 MBMS Session Stop Procedure for E-UTRAN and UTRAN for EPS + +The overall MBMS Session Stop procedure is presented in the following figure: + +![Sequence diagram of MBMS Session Stop procedure for E-UTRAN and UTRAN for EPS. The diagram shows five lifelines: UE, E-UTRAN/UTRAN, MME/SGSN, MBMS GW, and BM-SC. The sequence of messages is: 1. BM-SC sends Session Stop Request to MBMS GW; 2. MBMS GW sends Session Stop Request to MME/SGSN; 3. MME/SGSN sends Session Stop Request to E-UTRAN/UTRAN; 3a. E-UTRAN/UTRAN sends IGMPv3 Membership Report to UE; 4. E-UTRAN/UTRAN performs RAN Resource Release (indicated by a dashed box). Responses are sent back up the chain: 1. MBMS GW sends Session Stop Response to BM-SC; 2. MME/SGSN sends Session Stop Response to MBMS GW; 3. E-UTRAN/UTRAN sends Session Stop Response to MME/SGSN.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) + +``` + +sequenceDiagram + participant BM-SC + participant MBMS_GW as MBMS GW + participant MME_SGSN as MME/SGSN + participant E_UTRAN_UTRAN as E-UTRAN/UTRAN + participant UE + + Note right of BM-SC: 1. Session Stop Request + BM-SC->>MBMS_GW: 1. Session Stop Request + Note right of MBMS_GW: 1. Session Stop Response + MBMS_GW-->>BM-SC: 1. Session Stop Response + Note right of MBMS_GW: 2. Session Stop Request + MBMS_GW->>MME_SGSN: 2. Session Stop Request + Note right of MME_SGSN: 2. Session Stop Response + MME_SGSN-->>MBMS_GW: 2. Session Stop Response + Note right of MME_SGSN: 3. Session Stop Request + MME_SGSN->>E_UTRAN_UTRAN: 3. Session Stop Request + Note right of E_UTRAN_UTRAN: 3. Session Stop Response + E_UTRAN_UTRAN-->>MME_SGSN: 3. Session Stop Response + Note right of E_UTRAN_UTRAN: 3a. IGMPv3 Membership Report + E_UTRAN_UTRAN-->>UE: 3a. IGMPv3 Membership Report + Note right of E_UTRAN_UTRAN: 4. RAN Resource Release + E_UTRAN_UTRAN-->>E_UTRAN_UTRAN: 4. RAN Resource Release + +``` + +Sequence diagram of MBMS Session Stop procedure for E-UTRAN and UTRAN for EPS. The diagram shows five lifelines: UE, E-UTRAN/UTRAN, MME/SGSN, MBMS GW, and BM-SC. The sequence of messages is: 1. BM-SC sends Session Stop Request to MBMS GW; 2. MBMS GW sends Session Stop Request to MME/SGSN; 3. MME/SGSN sends Session Stop Request to E-UTRAN/UTRAN; 3a. E-UTRAN/UTRAN sends IGMPv3 Membership Report to UE; 4. E-UTRAN/UTRAN performs RAN Resource Release (indicated by a dashed box). Responses are sent back up the chain: 1. MBMS GW sends Session Stop Response to BM-SC; 2. MME/SGSN sends Session Stop Response to MBMS GW; 3. E-UTRAN/UTRAN sends Session Stop Response to MME/SGSN. + +**Figure 10b: MBMS Session Stop procedure for E-UTRAN and UTRAN for EPS** + +1. The BM-SC sends a Session Stop Request message (MBMS data transfer stop, ...) to the MBMS GW listed in the "list of down stream nodes" parameter of affected MBMS Bearer Context to indicate the end of session and the bearer plane resources can be released. The MBMS Bearer Context is uniquely identified by the TMGI or the combination of TMGI and Flow Identifier. The BM-SC sets the state attribute of its MBMS Bearer Context to 'Standby'. The MBMS GW responds with Session Stop Response and release its information regarding the session. +2. The MBMS GW forwards Session Stop Request message to the MME/SGSN which previously received the Session Start Request message, release the corresponding bearer plane resources to E-UTRAN/UTRAN and sets the state attribute of its MBMS Bearer Context to 'Standby'. The MBMS GW releases the MBMS Bearer Context in case of a broadcast MBMS bearer service. +3. MME/SGSN forwards Session Stop Request message to the E-UTRAN/UTRAN which previously received the Session Start Request message and sets the state attribute of its MBMS bearer Context to 'Standby'. Each E-UTRAN/UTRAN responds with Session Stop Response message to the MME/SGSN. The MME/SGSN releases the MBMS Bearer Context in case of a broadcast MBMS bearer service. +- 3a If the E-UTRAN/UTRAN is using IP multicast distribution it shall disable reception from the IP backbone of the particular MBMS bearer service according to RFC 3376 [19], RFC 3810 [20] and RFC 4604 [22]. If several MBMS bearer services shares the same IP multicast address, the reception from the IP backbone shall only be disabled when the last MBMS bearer service that has used a shared IP multicast address is stopped. +4. The E-UTRAN/UTRAN releases the affected resources and removes the MBMS Bearer Context (in E-UTRAN) or sets the state attribute of its MBMS Bearer Context to 'Standby' (in UTRAN). For E-UTRAN the release of the radio resources are scheduled using the MBMS data transfer stop parameter if present. It may be provided by the BM-SC in the Session Stop signalling. The MBMS data transfer stop parameter is not used by UTRAN. + +## 8.6 MBMS De-Registration Procedure + +### 8.6.0 Common MBMS De-Registration procedure + +The MBMS De-Registration is the procedure by which a downstream node informs an upstream node that it does not need to receive signalling, session attributes and data for a particular MBMS bearer service anymore and therefore would like to be removed from the corresponding distribution tree. + +The MBMS De-registration procedure is initiated: + +- By the SGSN or GGSN when the last MBMS UE Context for a particular MBMS bearer service is deleted from the node and the "list of downstream nodes" parameter in the corresponding MBMS Bearer Context is empty; + +- By the SGSN or GGSN when the last node registered in the "list of downstream nodes" de-registers from an MBMS bearer service for which there is no corresponding MBMS UE Context; or +- By the DRNC that registered at an SGSN when it deletes the associated MBMS Service Context. + +![Sequence diagram of the MBMS De-Registration Procedure. The diagram shows three stages of de-registration: A. DRNC to SGSN, B. SGSN to GGSN, and C. GGSN to BM-SC. Each stage consists of a Request message followed by a Response message.](0f1767577a073167eb9628d72034e083_img.jpg) + +``` + +sequenceDiagram + participant DRNC + participant SGSN + participant GGSN + participant BM-SC + + Note over DRNC, SGSN: A. MBMS Deregistration + DRNC->>SGSN: A. MBMS Deregistration Request + SGSN-->>DRNC: A. MBMS Deregistration Response + + Note over SGSN, GGSN: B. MBMS Deregistration + SGSN->>GGSN: B. MBMS Deregistration Request + GGSN-->>SGSN: B. MBMS Deregistration Response + + Note over GGSN, BM-SC: C. Deregistration + GGSN->>BM-SC: C. Deregistration Request + BM-SC-->>GGSN: C. Deregistration Response + +``` + +Sequence diagram of the MBMS De-Registration Procedure. The diagram shows three stages of de-registration: A. DRNC to SGSN, B. SGSN to GGSN, and C. GGSN to BM-SC. Each stage consists of a Request message followed by a Response message. + +**Figure 11: MBMS De-Registration Procedure** + +- A. When the DRNC that is registered at an SGSN no longer hosts any UE interested in that MBMS bearer service, the DRNC requests the de-registration from the MBMS bearer service to its parent SGSN. As an implementation option, the DRNC may decide not to de-register from the MBMS bearer service immediately when these conditions are met, e.g. in order to avoid unnecessary signalling in the case where the RNC would again need the same MBMS bearer service shortly after. + +The SGSN removes the identifier of the RNC from the "list of downstream nodes" parameter of the affected MBMS Bearer Context and confirms the operation by sending an MBMS De-Registration Response message to the RNC. If an Iu bearer plane had been established between the DRNC and the SGSN for this MBMS bearer service, the Iu bearer plane is released. If the RNC is using IP multicast distribution it shall disable reception from the IP backbone of the particular MBMS bearer service according to RFC 3376 [19], RFC 3810 [20] and RFC 4604 [22]. + +- B. When the "list of downstream nodes" of a particular MBMS Bearer Context in the SGSN becomes empty and the SGSN has no MBMS UE Contexts linked to that MBMS Bearer Context, the SGSN sends an MBMS De-Registration Request (IP multicast address, APN) message to its upstream GGSN associated with the MBMS Bearer Context. + +The GGSN removes the identifier of the SGSN from the "list of downstream nodes" parameter of the affected MBMS Bearer Context and confirms the operation by sending an MBMS De-Registration Response message to the SGSN. If a bearer plane had been established between the SGSN and the GGSN for this MBMS bearer service, the bearer plane is released. + +- C. When the "list of downstream nodes" of a particular MBMS Bearer Context in the GGSN becomes empty and the GGSN has no MBMS UE Contexts linked to that MBMS Bearer Context, the GGSN sends a De-Registration Request (IP multicast address, APN) message to the BM-SC. Proxy and Transport function If a bearer plane had been established over Gi for this MBMS bearer service, the bearer plane is released. + +The BM-SC removes the identifier of the GGSN from the "list of downstream nodes" parameter of the affected MBMS Bearer Context and confirms the operation by sending a De-Registration Response message to the GGSN. + +### 8.6.1 BM-SC initiated MBMS De-Registration Procedure + +This MBMS De-Registration Procedure is initiated by BM-SC when the specific MBMS bearer service is terminated. This procedure tears down the distribution tree for the delivery of session attributes and MBMS data. This procedure results in releasing of all MBMS Bearer Contexts and associated MBMS UE Contexts in the nodes along the distribution tree. + +![Sequence diagram of BM-SC initiated MBMS De-Registration Procedure. Lifelines: UE, BSC/RNC, SGSN, GGSN, BM-SC. The sequence starts with BM-SC sending a Deregistration Request to GGSN, followed by a response. Then GGSN sends an MBMS Deregistration Request to SGSN, followed by a response. SGSN then sends an MBMS Deregistration Request to BSC/RNC, followed by a response. Finally, BSC/RNC sends a RAN Resource Release message to UE.](9cbc1ebd80813fc36e499f7d70ed6881_img.jpg) + +``` + +sequenceDiagram + participant UE + participant BSC/RNC + participant SGSN + participant GGSN + participant BM-SC + Note left of UE: 4. RAN Resource Release + BM-SC->>GGSN: 1.Deregistration Request + GGSN-->>BM-SC: 1.Deregistration Response + GGSN->>SGSN: 2. MBMS Deregistration Request + SGSN-->>GGSN: 2. MBMS Deregistration Response + SGSN->>BSC/RNC: 3. MBMS Deregistration Request + BSC/RNC-->>SGSN: 3. MBMS Deregistration Response + BSC/RNC->>UE: 4. RAN Resource Release + +``` + +Sequence diagram of BM-SC initiated MBMS De-Registration Procedure. Lifelines: UE, BSC/RNC, SGSN, GGSN, BM-SC. The sequence starts with BM-SC sending a Deregistration Request to GGSN, followed by a response. Then GGSN sends an MBMS Deregistration Request to SGSN, followed by a response. SGSN then sends an MBMS Deregistration Request to BSC/RNC, followed by a response. Finally, BSC/RNC sends a RAN Resource Release message to UE. + +**Figure 12: BM-SC initiated MBMS De-Registration Procedure** + +1. The BM-SC sends a De-Registration Request message to all GGSNs contained in the "list of downstream nodes" parameter of the corresponding MBMS Bearer Context to indicate the session is terminated and any related MBMS bearer resources shall be released. + +The GGSN returns a De-Registration Response message to the BM-SC. The BM-SC releases all MBMS UE Contexts and the corresponding MBMS Bearer context. + +2. The GGSN sends an MBMS De-Registration Request message to all SGSNs contained in the "list of downstream nodes" parameter of the corresponding MBMS Bearer Context. The SGSN returns an MBMS De-registration Response message to the GGSN and releases all bearer resources if the state attribute of the MBMS Bearer Context is 'Active'. The GGSN releases all MBMS UE Contexts and the affected MBMS Bearer Context. If a bearer plane had been established over Gi for this MBMS bearer service, the bearer plane is released. +3. The SGSN sends an MBMS De-Registration Request message to all BSCs/RNCs connected with this SGSN. The BSC/RNC returns an MBMS De-Registration Response message to the SGSN, and releases all bearer resources if the state attribute of the MBMS Service Context is 'Active'. If the BSC/RNC is using IP multicast distribution it shall disable reception from the IP backbone of the particular MBMS bearer service according to RFC 3376 [19], RFC 3810 [20] and RFC 4604 [22]. The SGSN releases all MBMS UE Contexts and the affected MBMS Bearer Context. If a bearer plane had been established between the SGSN and the GGSN for this MBMS bearer service, the bearer plane is released. +4. The BSC/RNC releases the affected radio resources, all MBMS UE Contexts and the MBMS Service Context. The detailed procedures are specified in TS 25.346 [10] and TS 43.246 [11]. RAN may notify the UEs that the MBMS Bearer service has being terminated, so that the UE can locally deactivate its MBMS UE context, detailed procedures are specified in TS 25.346 [10] and TS 43.246 [11]. + +## 8.7 MBMS Multicast Service Deactivation + +The multicast service deactivation is a signalling procedure between the UE and the network. The procedure removes the MBMS UE Context from the UE, RAN, SGSN and GGSN for a particular MBMS multicast service. The multicast service deactivation can be initiated by: + +- The UE; +- The GGSN; +- The BM-SC; or +- The SGSN + +All these cases are contained in the procedure illustrated in figure 13. The UE initiated Multicast Service Deactivation starts with step 1), the BM-SC initiated Multicast Service Deactivation starts with step 3), the GGSN initiated Multicast Service Deactivation starts with step 4), the SGSN initiated Multicast Service Deactivation starts with step 5) or 9), and the MBMS UE de-linking is performed at step 7). + +At GPRS detach, all MBMS UE contexts of the UE are implicitly deactivated in the UE, SGSN and GGSN, i.e. the SGSN performs the deactivation procedure starting with step 7). + +If the PDP context linked to the MBMS UE context by the linked NSAPI is deactivated by the UE or SGSN or GGSN, then the SGSN shall perform the MBMS deactivation procedure starting with step 7). The UE will remove all MBMS UE Contexts locally after the Linked PDP Context was deactivated. + +![Sequence diagram for MBMS Multicast Service Deactivation showing interactions between UE, RAN, SGSN, GGSN, and BM-SC.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant SGSN + participant GGSN + participant BM-SC + + Note right of GGSN: GGSN + + UE->>GGSN: 1. IGMP Leave + GGSN->>BM-SC: 2. Leave Indication + BM-SC->>GGSN: 3. UE Removal Request + GGSN->>SGSN: 4. MBMS UE Context Deactivation Request + SGSN->>GGSN: 4. MBMS UE Context Deactivation Response + SGSN->>UE: 5. Deactivate MBMS Context Request + UE->>SGSN: 6. Deactivate MBMS Context Response + SGSN->>RAN: 7. MBMS UE De-Linking Request + RAN->>SGSN: 7. MBMS UE De-Linking Response + Note left of RAN: 8. RAN Resource Release + SGSN->>GGSN: 9. Delete MBMS Context Request + GGSN->>BM-SC: 10. Deactivation Indication + BM-SC->>GGSN: 10. Deactivation Confirmation + GGSN-->>BM-SC: 11. MBMS Deregistration Request + BM-SC-->>GGSN: 11. MBMS Deregistration Response + GGSN->>SGSN: 12. Delete MBMS Context Response + GGSN-->>SGSN: 13. Deregistration Request + SGSN-->>GGSN: 13. Deregistration Response + +``` + +Sequence diagram for MBMS Multicast Service Deactivation showing interactions between UE, RAN, SGSN, GGSN, and BM-SC. + +**Figure 13: MBMS Multicast Service Deactivation** + +1. The UE sends an IGMP (IPv4) or MLD (IPv6) Leave message (here, the Leave message means Leave Group message in RFC 2236 for IGMP (IPv4) and Multicast Listener Done in RFC2710 for MLD (IPv6)) over the default PDP context to leave a particular multicast service identified by an IP multicast address. +2. The GGSN sends a Leave Indication (IP multicast address, APN, IMSI) to the BM-SC Proxy and Transport function, which forwards it to the BM-SC Membership function, indicating that the UE is requesting to leave the multicast service identified by the IP multicast address. The exact nature of the signalling between GGSN and BM-SC is specified in TS 29.061 [4]. +3. Upon reception of the Leave Indication, the BM-SC Membership function verifies that the IP multicast address corresponds to a valid MBMS bearer service and sends a UE Removal Request (IP multicast address, APN, IMSI) to the GGSN that originated the Leave Indication. The APN shall be the same that was provided during service activation (see "MBMS Multicast Service Activation"). The exact nature of the signalling between GGSN and BM-SC is specified in TS 29.061 [4]. The BM-SC Membership function may also initiate the deactivation of an MBMS UE Context for service-specific reasons (e.g. the service is terminated but the UE has not yet left the multicast group) by directly sending a UE Removal Request message to the GGSN. +4. Upon reception of the UE Removal Request or for other reasons (e.g. Error cases), the GGSN sends an MBMS UE Context Deactivation Request (IP multicast address, APN, IMSI) to the SGSN. The IP multicast address, APN and IMSI together identify the MBMS UE Context to be deleted by the SGSN. The APN is the one received in step 3. The SGSN acknowledges reception of the MBMS UE Context Deactivation Request by sending an MBMS UE Context Deactivation Response to the GGSN. + +5. Upon reception of the MBMS UE Context Deactivation Request or for other reasons (e.g. due to a change in the roaming restrictions for the user) the SGSN sends a Deactivate MBMS Context Request (TI) to the UE. The TI identifies the MBMS UE Context to be deleted by the UE. +6. The UE deletes the MBMS UE Context and sends a Deactivate MBMS Context Accept (TI) to the SGSN. +7. If the UE is PMM-CONNECTED and has been already linked towards the RAN, the SGSN sends a MBMS UE De-Linking Request to the RNC (IP multicast address, APN, TMGI). RAN deletes the MBMS UE Context and sends a MBMS UE De-Linking Response (TMGI) to the SGSN. +8. If dedicated radio resources are currently assigned to the UE for the reception of the MBMS data, the RAN releases these radio resources. If shared radio resources are currently assigned for the distribution of the MBMS data, the RAN may decide to move the remaining UEs to dedicated resources. The detailed procedures and conditions are specified in TS 25.346 [10] and TS 43.246 [11]. +9. Upon reception of the Deactivate MBMS Context Accept or for other reasons (e.g. due to expiry of the long timer that is started upon a periodic routing area update not being received) the SGSN sends a Delete MBMS Context Request (MBMS\_NSAPI) to the GGSN that holds the MBMS UE Context. This GGSN may be different from the GGSN that receives IGMP Leave request in step 1. +10. The GGSN deletes the MBMS UE Context and sends a Deactivation Indication to the BM-SC to confirm the successful deactivation of the MBMS UE Context. The BM-SC, after receiving the Deactivation Indication, deletes the MBMS UE Context and sends a confirmation to the GGSN. The exact nature of the signalling between GGSN and BM-SC is specified in TS 29.061 [4]. +11. If the GGSN does not have any more users interested in this MBMS bearer service and the "list of downstream nodes" in the corresponding MBMS Bearer Context is empty, the GGSN sends a MBMS De-Registration Request to the BM-SC Proxy and Transport function. The BM-SC Proxy and Transport function responds with a MBMS De-Registration Response and removes the identifier of the GGSN from the "list of downstream nodes" parameter in its MBMS Bearer Context. See clause "MBMS De-Registration Procedure". +12. The GGSN confirms the deactivation of the MBMS UE Context to the SGSN by sending a Delete MBMS Context Response to the SGSN, which then deletes the MBMS UE Context. +13. If the SGSN does not have any more users interested in this MBMS bearer service and the "list of downstream nodes" in the corresponding MBMS Bearer Context is empty, the SGSN sends an MBMS De-Registration Request to the GGSN. The GGSN responds with an MBMS De-Registration Response and removes the identifier of the SGSN from the "list of downstream nodes" parameter in its MBMS Bearer Context. See clause "MBMS De-Registration Procedure". + +## 8.8 MBMS Session Update procedure + +### 8.8.1 General + +The MBMS Session Update procedure may be invoked by BM-SC or by SGSN. The BM-SC uses the procedure to update the service area or the QoS(ARP) for an ongoing MBMS Broadcast service session. The SGSN can also use the procedure to update the list of RAs where MBMS multicast users are located for an ongoing MBMS Multicast service session. + +For the distributed MCE architectures, i.e. when the MCE is part of the eNB as described in clause 15.1.1 in TS 36.300 [17], an absolute time stamp for when data can be expected, "MBMS data transfer start", should be used at MBSFN operation mode to ensure synchronized session control and to facilitate a graceful reallocation of resources for the MBSFN when needed. When the parameter "MBMS data transfer start" is present, a receiving supporting node shall ignore the parameter "time to MBMS data transfer". For session stop signalling, the parameter "MBMS data transfer stop" is if present used to schedule the release of the radio resources in order to ensure a synchronized session control. The MME also sends an MBMS Session Start Request message to any added MCEs, and an MBMS Session Stop Request message to any removed MCEs. The MME shall set "MBMS Data Transfer Start" to " Time of MBMS Data Transfer " or " Time of MBMS Data Stop " respectively as specified in TS 36.444 [28]. + +### 8.8.2 SGSN initiated Session Update for GERAN and UTRAN for MBMS Multicast service + +If the SGSN has provided a list of RAs in the MBMS Session Start Request message (even if the list was empty) and RAs are added or removed from the list, the SGSN shall use the MBMS Session Update procedure to inform the RNCs that the list has changed. The SGSN sends the Session Update message only to the RNCs that are affected by the list change. The procedure is used only during the MBMS Multicast service session and when SGSN has already sent a MBMS Session Start Request message to the RNC. + +If the SGSN has provided a list of RAs in the MBMS Session Start Request message (even if the list was empty) the SGSN shall send the Session Update to a RNC when: + +- the first UE which have activated the service enters in a RA that is not in the list; +- the last UE which have activated the service leaves from a RA that was in the list. + +![Sequence diagram showing the Session Update procedure between an RNC and an SGSN. The RNC is on the left and the SGSN is on the right. Step 1: An arrow labeled '1 MBMS Session Update Request' points from the SGSN to the RNC. Step 2: An arrow labeled '2 MBMS Session Update Response' points from the RNC to the SGSN.](db5deafdae53dbc7d5972957f708c691_img.jpg) + +``` + +sequenceDiagram + participant RNC + participant SGSN + Note left of RNC: RNC + Note right of SGSN: SGSN + SGSN->>RNC: 1 MBMS Session Update Request + RNC-->>SGSN: 2 MBMS Session Update Response + +``` + +Sequence diagram showing the Session Update procedure between an RNC and an SGSN. The RNC is on the left and the SGSN is on the right. Step 1: An arrow labeled '1 MBMS Session Update Request' points from the SGSN to the RNC. Step 2: An arrow labeled '2 MBMS Session Update Response' points from the RNC to the SGSN. + +Figure 13a. Session Update procedure + +- 1) The SGSN sends MBMS Session Update Request message to a RNC. +- 2) The RNC acknowledges the MBMS Session Update Request with the MBMS Session Update Response message. + +### 8.8.3 BM-SC initiated Session Update for GERAN and UTRAN for MBMS Broadcast service + +The BM-SC initiates the MBMS Session Update procedure when the service area for an ongoing MBMS Broadcast service session shall be modified. + +The attributes that can be modified by the Session Update Request are the MBMS Service Area, and the list of downstream nodes for GGSN (Broadcast only). A node receiving the Session Update Request determines how the attributes have changed by comparing the attributes in the message with corresponding attributes in its stored MBMS Bearer Context. + +A Session Update received in one node, results in a Session Update being sent to downstream nodes, to inform of the changed MBMS Service Area. If a Session Update with the List of SGSN parameter included is received in the GGSN, it does also result in a Session Start being sent to new downstream nodes, and in a Session Stop being sent to downstream nodes that have been removed from the list. + +The overall Session Update procedure is presented in figure 13b. + +![Sequence diagram showing the Session Update procedure for GERAN and UTRAN. The diagram involves five entities: UE, BSC/RNC, SGSN, GGSN, and BM-SC. The sequence of messages is: 1. BM-SC sends a Session Update Request to GGSN, which responds with a Session Update Response. 2. GGSN sends an MBMS Session Update Request to SGSN, which responds with an MBMS Session Update Response. 3. SGSN sends an MBMS Session Update Request to BSC/RNC, which responds with an MBMS Session Update Response. 4. BSC/RNC performs RAN Resource Setup or Release, indicated by a dashed box.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +``` + +sequenceDiagram + participant BM-SC + participant GGSN + participant SGSN + participant BSC/RNC + participant UE + + Note right of BM-SC: 1. Session Update Request + BM-SC->>GGSN: 1. Session Update Request + Note right of GGSN: 1. Session Update Response + GGSN-->>BM-SC: 1. Session Update Response + Note right of GGSN: 2. MBMS Session Update Request + GGSN->>SGSN: 2. MBMS Session Update Request + Note right of SGSN: 2. MBMS Session Update Response + SGSN-->>GGSN: 2. MBMS Session Update Response + Note right of SGSN: 3. MBMS Session Update Request + SGSN->>BSC/RNC: 3. MBMS Session Update Request + Note right of BSC/RNC: 3. MBMS Session Update Response + BSC/RNC-->>SGSN: 3. MBMS Session Update Response + Note right of BSC/RNC: 4. RAN Resource Setup or Release + BSC/RNC-->>UE: 4. RAN Resource Setup or Release + +``` + +Sequence diagram showing the Session Update procedure for GERAN and UTRAN. The diagram involves five entities: UE, BSC/RNC, SGSN, GGSN, and BM-SC. The sequence of messages is: 1. BM-SC sends a Session Update Request to GGSN, which responds with a Session Update Response. 2. GGSN sends an MBMS Session Update Request to SGSN, which responds with an MBMS Session Update Response. 3. SGSN sends an MBMS Session Update Request to BSC/RNC, which responds with an MBMS Session Update Response. 4. BSC/RNC performs RAN Resource Setup or Release, indicated by a dashed box. + +**Figure 13b: Session Update procedure for GERAN and UTRAN** + +1. The BM-SC Session and Transmission function sends a Session Update Request (TMGI, Flow Identifier (Broadcast only), QoS, MBMS Service Area, Session identifier, estimated session duration, broadcast/multicast, list of downstream nodes for GGSN, time to MBMS data transfer) to the BM-SC Proxy and Transport function, which then forwards it to the GGSNs listed in the "list of downstream nodes" parameter of the corresponding MBMS Bearer Context. The TMGI and Session identifier identifies the ongoing session. The QoS, broadcast/multicast attributes and the 2G/3G indicator shall be identical as in the preceding Session Start message. The MBMS Service Area and the List of downstream nodes for GGSN define the new service area. The time to MBMS data transfer shall be set to 0 and the estimated session duration shall be set to a value corresponding to the remaining part of the session. + +The GGSN stores the new session attributes and the list of downstream nodes in the MBMS Bearer Context and sends a Session Update Response message to the BM-SC Proxy and Transport function which forwards it to the BM-SC Session and Transmission function. The BM-SC Proxy and Transport function copies the Session Update Request to the BM-SC Membership function for charging purposes. + +2. The GGSN compares the new list of downstream nodes with the list of downstream nodes it has stored in the MBMS Bearer Context. It sends an MBMS Session Start Request message to any added SGSN, an MBMS Session Stop Request to any removed SGSN, and an MBMS Session Update Request to the remaining SGSNs in the new list. +3. The SGSN receiving an MBMS Session Update Request message, sends an MBMS Session Update Request message including the session attributes (TMGI, QoS, MBMS service Area, Session identifier, estimated session duration, broadcast/multicast, time to MBMS data transfer, list of RAs, etc.) to each BSC and/or each RNC that is connected to this SGSN. +4. The BSCs/RNCs establish or release the necessary radio resources for the transfer of MBMS data to the interested UEs. + +### 8.8.4 BM-SC initiated Session Update for EPS with E-UTRAN and UTRAN + +The BM-SC initiates the MBMS Session Update procedure when the service attributes (e.g. Service Area, list of cell IDs or ARP) for an ongoing MBMS Broadcast service session shall be modified, e.g. the Session Update procedure for EPS is initiated by BM-SC to notify eNBs to join or leave the service area. Update of the QoS(ARP) is triggered when the priority of a broadcast data flow of a group communication service is changed as specified in TS 23.468 [24]. + +The attributes that can be modified by the Session Update Request are the MBMS service area, list of cell IDs, Access indicator, MBMS data transfer start, QoS(ARP) and the List of MBMS control plane nodes. A node receiving the Session Update Request determines how the attributes have changed by comparing the attributes in the message with corresponding attributes in its stored MBMS Bearer Context. + +A Session Update received in one node, results in a Session Update being sent to downstream nodes, to inform of the changed MBMS service attributes. If a Session Update with the List of MME and SGSN parameter included is received in the MBMS GW, it does also result in a Session Start being sent to new downstream nodes, and in a Session Stop being sent to downstream nodes that have been removed from the list. + +NOTE: For a MBMS session the change of service area does not result in a change of MBMS-GW. + +The overall Session Update procedure is presented in figure 13c-1 and 13c-2. + +![Figure 13c-1: Session Update procedure for EPS with E-UTRAN and UTRAN. This sequence diagram shows the interaction between UE, E-UTRAN/UTRAN, MME/SGSN, MBMS GW, and BM-SC. The process starts with the BM-SC sending a Session Update Request to the MBMS GW, which then forwards it to the MME/SGSN. The MME/SGSN sends a Session Update Request to the E-UTRAN/UTRAN, which responds with a Session Update Response. The MME/SGSN then sends a Session Update Response to the MBMS GW, which in turn sends a Session Update Response to the BM-SC. The E-UTRAN/UTRAN also performs RAN Resource Setup or Release and IP Multicast Join or leave actions, indicated by dashed boxes.](cc6f9dbfc36aa5821d9749ca84861f93_img.jpg) + +``` + +sequenceDiagram + participant BM-SC + participant MBMS_GW as MBMS GW + participant MME_SGSN as MME/SGSN + participant E_UTRAN_UTRAN as E-UTRAN/UTRAN + participant UE + + Note right of BM-SC: 1. Session Update Request + BM-SC->>MBMS_GW: 1. Session Update Request + Note right of MBMS_GW: 2. Session Update Response + MBMS_GW-->>BM-SC: 2. Session Update Response + Note right of MBMS_GW: 3. Session Update Request + MBMS_GW->>MME_SGSN: 3. Session Update Request + Note right of MME_SGSN: 4. Session Update Request + MME_SGSN->>E_UTRAN_UTRAN: 4. Session Update Request + Note right of E_UTRAN_UTRAN: 5. Session Update Response + E_UTRAN_UTRAN-->>MME_SGSN: 5. Session Update Response + Note right of MME_SGSN: 6. Session Update Response + MME_SGSN->>MBMS_GW: 6. Session Update Response + Note right of E_UTRAN_UTRAN: 7. RAN Resource Setup or Release + Note right of E_UTRAN_UTRAN: 8. IP Multicast Join or leave + +``` + +Figure 13c-1: Session Update procedure for EPS with E-UTRAN and UTRAN. This sequence diagram shows the interaction between UE, E-UTRAN/UTRAN, MME/SGSN, MBMS GW, and BM-SC. The process starts with the BM-SC sending a Session Update Request to the MBMS GW, which then forwards it to the MME/SGSN. The MME/SGSN sends a Session Update Request to the E-UTRAN/UTRAN, which responds with a Session Update Response. The MME/SGSN then sends a Session Update Response to the MBMS GW, which in turn sends a Session Update Response to the BM-SC. The E-UTRAN/UTRAN also performs RAN Resource Setup or Release and IP Multicast Join or leave actions, indicated by dashed boxes. + +Figure 13c-1: Session Update procedure for EPS with E-UTRAN and UTRAN + +![Figure 13c-2: Session Update procedure for EPS with E-UTRAN with delayed response. This sequence diagram shows the interaction between UE, E-UTRAN, MME/SGSN, MBMS GW, and BM-SC. The process starts with the BM-SC sending a Session Update Request to the MBMS GW, which then forwards it to the MME/SGSN. The MME/SGSN sends a Session Update Request to the E-UTRAN, which performs RAN Resource Setup or Release and IP Multicast Join or leave actions (indicated by dashed boxes). The E-UTRAN then sends a Session Update Response to the MME/SGSN. The MME/SGSN sends a Session Update Response to the MBMS GW, which in turn sends a Session Update Response to the BM-SC.](0997dbaa9dfecedd60029d70b53327b8_img.jpg) + +``` + +sequenceDiagram + participant BM-SC + participant MBMS_GW as MBMS GW + participant MME_SGSN as MME/SGSN + participant E_UTRAN as E-UTRAN + participant UE + + Note right of BM-SC: 1. Session Update Request + BM-SC->>MBMS_GW: 1. Session Update Request + Note right of MBMS_GW: 3. Session Update Request + MBMS_GW->>MME_SGSN: 3. Session Update Request + Note right of MME_SGSN: 4. Session Update Request + MME_SGSN->>E_UTRAN: 4. Session Update Request + Note right of E_UTRAN: 7. RAN Resource Setup or Release + Note right of E_UTRAN: 8. IP Multicast Join or leave + Note right of E_UTRAN: 5. Session Update Response + E_UTRAN-->>MME_SGSN: 5. Session Update Response + Note right of MME_SGSN: 6. Session Update Response + MME_SGSN->>MBMS_GW: 6. Session Update Response + Note right of MBMS_GW: 2. Session Update Response + MBMS_GW-->>BM-SC: 2. Session Update Response + +``` + +Figure 13c-2: Session Update procedure for EPS with E-UTRAN with delayed response. This sequence diagram shows the interaction between UE, E-UTRAN, MME/SGSN, MBMS GW, and BM-SC. The process starts with the BM-SC sending a Session Update Request to the MBMS GW, which then forwards it to the MME/SGSN. The MME/SGSN sends a Session Update Request to the E-UTRAN, which performs RAN Resource Setup or Release and IP Multicast Join or leave actions (indicated by dashed boxes). The E-UTRAN then sends a Session Update Response to the MME/SGSN. The MME/SGSN sends a Session Update Response to the MBMS GW, which in turn sends a Session Update Response to the BM-SC. + +Figure 13c-2: Session Update procedure for EPS with E-UTRAN with delayed response + +1. The BM-SC sends a Session Update Request (TMGI, Flow Identifier, QoS, MBMS Service Area, list of cell IDs if available, Session identifier, estimated session duration, the list of MBMS control plane nodes(MMEs, SGSNs) for MBMS GW, time to MBMS data transfer, MBMS data transfer start, Access Indicator, ...) to MBMS GW. The TMGI and Session identifier identifies the ongoing session. Apart from the ARP parameter, all other parameters in the QoS profile shall be identical as in the preceding Session Start message. The ARP parameter may be different if it is to be updated. The MBMS Service Area and the list of MBMS control plane nodes (MMEs, SGSNs) for MBMS GW define the new service area. The estimated session duration shall be set to a value corresponding to the remaining part of the session. If radio access of MBMS service is updated the Access indicator shall be included to indicate in which radio access types the MBMS service should be broadcasted, i.e. UTRAN, or E-UTRAN, or both. The ARP parameter may be updated only if the Access + +Indicator indicates E-UTRAN. The Access indicator may be included in charging information generated by the MBMS-GW. + +If MBMS-GW is configured to delay response to BMSC when access type is E-UTRAN, then MBMS-GW delays response to BMSC (i.e. Step 2) until after step 6 is executed as shown in figure 13c-2. This configuration should be only performed when E-UTRAN executes step 7 below before responding to the MBMS Session Update message as specified in TS 36.300 [17]. + +NOTE: It is up to the operator to ensure that E-UTRAN, MBMS-GW and BMSC are configured only when E-UTRAN supports delaying the response from eNB. + +2. The MBMS GW stores the new session attributes in the MBMS Bearer Context and sends a Session Update Response message to the BM-SC, if figure 13c-1 is executed. The MBMS-GW responds only after first MME response in step 6 is received, if it is configured to do so as shown in figure 13c-2. +3. The MBMS GW filters the new list of MBMS control plane nodes using the Access indicator to ignore entries not consistent with the Access indicator, and compares remaining entries in the new list of MBMS control plane nodes with the list of MBMS control plane nodes it has stored in the MBMS Bearer Context. It sends an MBMS Session Start Request message to any added MME/SGSN, an MBMS Session Stop Request to any removed MME/SGSN, and an MBMS Session Update Request (TMGI, Flow Identifier, QoS, MBMS Service Area, list of cell IDs if available, Session identifier, estimated session duration, ...) to the remaining MME/SGSNs in the new list. The handlings of the MBMS Session Start/Stop Request message are described in clauses 8.3.2 and 8.5.2. +4. The MME/SGSN receiving an MBMS Session Update Request message, sends an MBMS Session Update Request message including the session attributes (TMGI, QoS, MBMS service Area, list of cell IDs if available, Session identifier, estimated session duration, broadcast (for UTRAN only), transport network IP Multicast Address, IP address of the multicast source, C-TEID, etc.) to each eNodeB/MCE/RNC that is connected to the MME/SGSN. + +For E-UTRAN, when connected to multiple MCEs, the MME should filter the distribution of MBMS Session Update Request messages to the MCEs based on the MBMS service area. + +For UTRAN, if one or more of the downstream nodes newly added to the MBMS Service Area accepts the Session Update and the proposed IP Multicast and Source address for backbone distribution and the proposed C-TEID, the SGSN includes an indication that IP Multicast distribution is accepted in the MBMS Session Update Response message to MBMS GW. If one or more of the downstream nodes newly added to the MBMS Service Area does not accept the proposed IP Multicast and Source address for backbone distribution or the proposed C-TEID, the SGSN falls back to normal point-to-point MBMS bearer establishment for these nodes and responds with an MBMS Session Update Response message providing the TEID for bearer plane that the MBMS GW shall use for forwarding the MBMS data. Otherwise if all nodes accept multicast, the SGSN returns the C-TEID and the IP Multicast distribution address in the Session Update Response message. + +E-UTRAN may respond to Session Update Request after first successful MBMS resources have been set up or released (i.e. Step 7) which indicates to the BMSC that there are resources already available for MBMS data delivery, as shown in figure 13c-2. + +5. If the E-UTRAN/UTRAN has no MBMS bearer context with the TMGI indicated in the MBMS Session Update Request message, the E-UTRAN/UTRAN creates an MBMS bearer context and sets its state attribute to 'Active' (in UTRAN only). Otherwise the E-UTRAN/UTRAN compare the new service area with the one it has stored in the MBMS Bearer Context and make the corresponding update. Then the E-UTRAN/UTRAN responds the MME/SGSN to confirm the reception of the Session Update Request message. When a cell ID list is included in the Session Start Request, E-UTRAN uses it to determine a set of radio resources to be used for the broadcast. Based on the cell ID list, the set of radio resources selected may be reduced from the full set of resources defined by the MBMS service area. The E-UTRAN ensures that all of its corresponding nodes make the same decision on the reduced set. + +For UTRAN, if an RNC newly added to the MBMS Service Area accepts the Session Update and the proposed IP Multicast and Source address for backbone distribution and the proposed C-TEID the RNC sends an MBMS Session Update Response message to SGSN including an indication that IP Multicast distribution is accepted. If an RNC newly added to the MBMS Service Area does not accept the proposed IP Multicast and Source address for backbone distribution (or the proposed C-TEID), the RNC falls back to normal point-to-point MBMS bearer establishment. + +- The MME/SGSN updates the session attributes in its MBMS Bearer Context and responds to the MBMS GW. The SGSN should wait for a response from all UTRAN nodes (until an acceptable duration) if the Service Area has been changed to be able to report to the MBMS-GW whether all, part or none of any newly added RNCs have accepted IP multicast distribution and to provide an SGSN IP address and TEID for user plane over Sn if some RNCs did not accept IP multicast distribution. The MME may return a response to the MBMS-GW as soon as the session update request is accepted by one E-UTRAN node. + +If the MBMS-GW is configured to delay response to the BMSC, MBMS-GW waits until step 6 occurs before responding to the BMSC as shown in figure 13c-2. + +- The E-UTRAN/UTRAN establishes/releases the radio resources for the transfer of MBMS data to the interested UEs. If the ARP parameter is updated the MCE shall ensure that any necessary changes to radio resources are synchronized across all eNBs in the corresponding MBSFN area. For E-UTRAN the radio resource set up is scheduled using the MBMS data transfer start parameter if it is present, otherwise using the time to MBMS data transfer parameter if it is present. The MBMS data transfer start parameter is not used by UTRAN. +- The eNodeBs/RNCs send IP multicast Join or Leave message to the received user plane IP multicast address allocated by the MBMS GW. If multiple MBMS bearers services shares the same IP multicast address, this shall be considered before a Join or Leave message is sent. + +## 8.9 MBMS UE Context Synchronisation Procedure + +The Routing Area Update procedure transfers the MBMS UE Context status between UE and SGSN. This MBMS UE Context status identifies MBMS UE contexts, which are lost or deactivated only on one side. All MBMS UE Contexts, which are active on one side only shall be deactivated locally. If the UE wishes to re-activate the related MBMS bearer service, it shall join the MBMS bearer service again. See clause 8.2 "MBMS Multicast Service Activation". + +![Sequence diagram of MBMS UE Context Synchronisation procedure between UE and SGSN.](39536a630fa74c3bcfd1670ee2152809_img.jpg) + +``` + +sequenceDiagram + participant UE + participant SGSN + Note left of UE: + UE->>SGSN: 1. Routeing Area Update Request + Note right of SGSN: + SGSN-->>UE: 2. Routeing Area Update Accept + Note left of UE: + +``` + +The diagram shows a sequence of two messages between a User Equipment (UE) and a Serving GPRS Support Node (SGSN). + 1. The UE sends a 'Routeing Area Update Request' to the SGSN. + 2. The SGSN responds with a 'Routeing Area Update Accept' to the UE. + +Sequence diagram of MBMS UE Context Synchronisation procedure between UE and SGSN. + +**Figure 13d. MBMS UE Context Synchronisation procedure** + +- The UE sends Routeing Area Update Request to the SGSN. It includes the MBMS UE Context status, which indicates the UE's active MBMS UE Contexts. +- The SGSN sends Routeing Area Update Accept to the UE. It includes the MBMS UE Context status, which indicates the UE's MBMS UE Contexts that are stored in the SGSN. + +## 8.9a MBMS feature support indication + +An SGSN that supports MBMS shall indicate MBMS feature support to the UE during Routing Area Update procedure in the Routing Area Update Accept message and during GPRS attach procedure in the Attach Accept message. The UE then knows it can use already activated MBMS bearers, or activate new MBMS bearers according to clause 8.2 "MBMS Multicast Service Activation". + +An SGSN that does not support MBMS will not indicate MBMS feature support to the UE. This indicates to the UE that MBMS bearers are no longer supported, which may allow the UE to use point-to-point bearers for MBMS data transfer. In this case, the UE shall deactivate all active MBMS UE Contexts locally. + +## 8.10 Inter SGSN Routeing Area Update + +This procedure describes the handling of MBMS bearer services when an MBMS UE performs a Routeing Area Update and the serving SGSN changes. It is based on the Inter SGSN Routeing Area Update procedure specified in TS 23.060 [15]. The procedure is performed regardless whether MBMS sessions are ongoing or not. The handling of any PDP contexts established by the UE is not changed compared to the procedure without MBMS. The procedure described below does not show all details of the Routeing Area update procedure. Only for the MBMS specific additions the steps are described. + +![Sequence diagram for Inter SGSN Routing Area Update. Lifelines: UE, RAN, new SGSN, old SGSN, GGSN, HLR, BM-SC. The diagram shows the interaction between these entities during a routing area update, including context transfer, security functions, and MBMS-related updates.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant new_SGSN as new SGSN + participant old_SGSN as old SGSN + participant GGSN + participant HLR + participant BM-SC + + Note right of GGSN: GGSN + + UE->>new_SGSN: 1. Routeing Area Update Request + new_SGSN->>old_SGSN: 2. SGSN Context Request + old_SGSN-->>new_SGSN: 2. SGSN Context Response + new_SGSN-->>UE: 3. Security Functions + new_SGSN->>old_SGSN: 4. SGSN Context Acknowledge + old_SGSN-->>new_SGSN: 5. Forward Packets + new_SGSN->>GGSN: 6. Update PDP Context Request + GGSN-->>new_SGSN: 6. Update PDP Context Response + new_SGSN-->>GGSN: 7. Update MBMS UE Context Request + GGSN-->>new_SGSN: 7. Update MBMS UE Context Response + GGSN-->>BM-SC: 8. Update MBMS UE Context Request + BM-SC-->>GGSN: 8. Update MBMS UE Context Response + GGSN-->>BM-SC: 9. Activate Trace + new_SGSN->>HLR: 10. Update Location + old_SGSN-->>HLR: 11. Cancel Location + HLR-->>old_SGSN: 11. Cancel Location Ack + new_SGSN->>HLR: 12. Insert Subscriber Data + HLR-->>new_SGSN: 12. Insert Subscriber Data Ack + new_SGSN->>HLR: 13. Update Location Ack + Note right of new_SGSN: 14. MBMS Multicast Service Deactivation! + Note right of old_SGSN: 15. MBMS De-Registr. Proc! + Note right of new_SGSN: 16. MBMS Registration Procedure + new_SGSN-->>UE: 17. Routeing Area Update Accept + UE->>new_SGSN: 18. Routeing Area Update Complete + +``` + +Sequence diagram for Inter SGSN Routing Area Update. Lifelines: UE, RAN, new SGSN, old SGSN, GGSN, HLR, BM-SC. The diagram shows the interaction between these entities during a routing area update, including context transfer, security functions, and MBMS-related updates. + +**Figure 14: Inter SGSN Routeing Area Update** + +- 2) An SGSN supporting MBMS indicates its MBMS support in the SGSN Context Request message. If the SGSN indicates that it supports MBMS, the old SGSN includes the transfer of the MBMS UE Context(s) in the SGSN Context Response message. +- 7) For the MBMS UE context(s) received in step 2) the new SGSN sends Update MBMS UE Context Request (Serving network identity, MS Time Zone, CGI/SAI, RAT Type, Additional MBMS Trace Info) to the GGSNs concerned. The GGSNs update their MBMS UE Context fields and return Update MBMS UE Context Response. +- 8) The GGSN sends Update MBMS UE Context Request (RAI) to the BM-SC. The inclusion of CGI/SAI shall be according rules detailed in clause 15.1.1a in TS 23.060 [15]. The BM-SC updates its MBMS UE Context fields and return Update MBMS UE Context Response. +- 9) If the GGSN receives new or updated Additional MBMS Trace Info from the new SGSN, the GGSN sends an Activate Trace (Additional MBMS Trace Info) message to the BM-SC. + +- 14) In case the new SGSN indicated no MBMS support in step 2) the old SGSN deactivates all MBMS UE context(s) of the UE in SGSN, GGSN and BM-SC by initiating deactivation procedure(s) as described in clause "8.7 MBMS Multicast Service Deactivation". +- 15) If the old SGSN does not have any more MBMS UE Contexts for the MBMS bearer service(s) and the "list of downstream nodes" in the corresponding MBMS Bearer Context is empty, the SGSN initiates the MBMS De-Registration Procedure. See clause "8.6 MBMS De-Registration Procedure". +- 16) In case the new SGSN indicated MBMS support in step 2), the new SGSN verifies for each MBMS UE Context received whether it has a corresponding MBMS Bearer Context. For each MBMS Bearer Context that the SGSN does not already have, the SGSN creates an MBMS Bearer Context (in "Standby" state) and initiates the MBMS Registration Procedure towards the GGSN. See clause "8.4 MBMS Registration Procedure". +- 17) An SGSN without MBMS support does not indicate MBMS feature support in the Routing Area Update Accept message. On the other hand if the SGSN supports MBMS, the Routing Area Update Accept indicates to the UE that the network supports MBMS. + +## 8.10a Inter-system Intra-SGSN change + +For an MBMS UE transitioning between UTRAN and A/Gb mode GERAN, the procedures are the same as the Iu mode to A/Gb mode Intra SGSN Change and A/Gb mode to Iu mode Intra SGSN Change procedures specified in TS 23.060 [15]. + +Furthermore, the same considerations on Radio Access Technology changes apply as specified in the impacts of applying flow based charging specified in TS 23.060 [15], i.e. the SGSN shall send an Update MBMS UE Context Request to the GGSN. Subsequently the GGSN shall send an Update MBMS UE Context Request to the BM-SC as described in the Inter SGSN Routing Area Update procedure in clause 8.10. + +## 8.11 Inter SGSN Serving RNS Relocation Procedure + +This procedure is performed when the SGSN changes due to SRNS relocation. It bases on the SRNS Relocation procedure specified in TS 23.060 [15]. The procedure is performed regardless whether MBMS sessions are ongoing or not. The handling of any PDP contexts established by the UE is not changed compared to the procedure without MBMS. The procedure described below does not show all details of the SRNS relocation procedure. Only for the MBMS specific additions the steps are described. + +![Sequence diagram of SRNS Relocation Procedure. Lifelines: MS, Source RNC, Target RNC, Old SGSN, New SGSN, GGSN, BM-SC. The diagram shows the flow of messages for relocating a radio access network, including bearer establishment, data forwarding, and MBMS context updates.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +``` + +sequenceDiagram + participant MS + participant Source RNC + participant Target RNC + participant Old SGSN + participant New SGSN + participant GGSN + participant BM-SC + + Note left of Source RNC: 1. Decision to perform SRNS relocation + Source RNC->>Old SGSN: 2. Relocation Required + Old SGSN->>New SGSN: 3. Forward Relocation Request + New SGSN->>Target RNC: 4. Relocation Request + Note right of Target RNC: Establishment of Radio Access Bearers + Target RNC->>New SGSN: 4. Relocation Request Acknowledge + New SGSN->>Old SGSN: 5. Forward Relocation Response + Note left of Old SGSN: C1 + Old SGSN->>Source RNC: 6. Relocation Command + Source RNC->>Target RNC: 7. Forwarding of data + Source RNC->>Target RNC: 8. Relocation Commit + Target RNC->>New SGSN: 9. Relocation Detect + New SGSN->>MS: 10. RAN Mobility Information + MS->>Target RNC: 10. RAN Mobility Information Confirm + Target RNC->>New SGSN: 11. Relocation Complete + New SGSN->>Old SGSN: 12. Forward Relocation Complete + Old SGSN->>New SGSN: 12. Forward Relocation Complete Acknowledge + New SGSN->>GGSN: 13. Update PDP Context Request + GGSN->>New SGSN: 13. Update PDP Context Response + Note right of GGSN: GGSN + New SGSN->>Source RNC: 15. Iu Release Command + Source RNC->>Old SGSN: 15. Iu Release Complete + Note right of New SGSN: 14. MBMS Registration Procedure + Note right of Old SGSN: 16. MBMS Multicast Service Deactivation + Note right of Old SGSN: 17. MBMS De-Registration Procedure + New SGSN->>GGSN: 18. Update MBMS UE Context Request + GGSN->>New SGSN: 18. Update MBMS UE Context Response + New SGSN->>BM-SC: 19. Activate Trace + Note left of Source RNC: 20. Routing Area Update + Note right of New SGSN: C2 + Note right of New SGSN: C3 + +``` + +Sequence diagram of SRNS Relocation Procedure. Lifelines: MS, Source RNC, Target RNC, Old SGSN, New SGSN, GGSN, BM-SC. The diagram shows the flow of messages for relocating a radio access network, including bearer establishment, data forwarding, and MBMS context updates. + +Figure 15: SRNS Relocation Procedure + +3) The old SGSN transfers the MBMS UE Context(s), in the Forward Relocation Request message to the new SGSN + +5) An MBMS supporting SGSN indicates its MBMS support in the Forward Relocation Response message. + +14) In case the new SGSN supports MBMS it verifies for each MBMS UE Context received whether it has a corresponding MBMS Bearer Context. For each MBMS Bearer Context not yet existing in the SGSN the SGSN creates an MBMS Bearer Context (in "Standby" state) and initiates the MBMS Registration Procedure. See clause "MBMS Registration Procedure". + +- 16) In case the new SGSN indicated no MBMS support in step 3) the old SGSN deactivates all MBMS UE contexts of the UE in SGSN, GGSN and BMSC by initiating deactivation procedure(s) as described in clause "8.7 MBMS Multicast Service Deactivation". +- 17) If the old SGSN does not have any more MBMS UE Contexts for this MBMS bearer service and the "list of downstream nodes" in the corresponding MBMS Bearer Context is empty, the SGSN initiates the MBMS De-Registration Procedure. See clause "MBMS De-Registration Procedure". +- 18) If the new SGSN supports the MBMS and for the MBMS UE context(s) received in step 5) the new SGSN sends Update MBMS UE Context Request (Serving network identity, MS Time Zone, CGI/SAI, RAT Type, Additional MBMS Trace Info) to the GGSNs concerned. The GGSNs update their MBMS UE Context fields and return Update MBMS UE Context Response. The GGSN sends updated Serving network identity to the BM-SC. The inclusion of CGI/SAI shall be according rules detailed in clause 15.1.1a in TS 23.060 [15]. +- 19) If the GGSN receives new or updated Additional MBMS Trace Info from the new SGSN, the GGSN sends an Activate Trace (Additional MBMS Trace Info) message to the BM-SC. +- 20) An SGSN without MBMS support does not indicate MBMS feature support in the Routing Area Update Accept message. On the other hand if the SGSN supports MBMS, the Routing Area Update Accept indicates to the UE that the network supports MBMS. + +## 8.12 MBMS Broadcast Service Activation + +MBMS Broadcast service activation is the procedure by which a UE locally activates a broadcast MBMS bearer service: + +- The MBMS broadcast service activation procedure does not register the user in the network. There is no MBMS bearer service specific signalling exchanged between the UE and the Network. +- The broadcast service activation procedure does not establish MBMS UE contexts in UE, SGSN and GGSN. + +## 8.13 MBMS Broadcast service de-activation + +The MBMS Broadcast service de-activation by the UE is local to the UE, i.e. without interaction with the Network. + +## 8.14 Void + +## 8.15 MBMS UE Linking/De-linking mechanism + +MBMS UE Linking is the process by which UE MBMS context(s) is (are) provided to an Iu-mode RAN. + +MBMS UE linking procedure is performed when the UE is PMM-CONNECTED at least in the following cases. + +- When a UE which has a MBMS UE context is moved to the PMM CONNECTED state and a PS RAB is established. This may happen at any point in time e.g. before, during and between Sessions. +- When a UE joins the MBMS bearer service and is in the PMM CONNECTED state due to an existing PS RAB. This may happen at any point in time e.g. before, during and between Sessions. +- When a UE is moved to the PMM CONNECTED state via the MBMS Service Request procedure. This may happen at any point in time during a MBMS session. + +The UE linking is performed to link a specific UE to an MBMS service. It provides the SRNC/Iu-mode BSC with a list of MBMS service identifiers (including TMGI) for MBMS bearer services activated by the UE. If no MBMS service context exists for this particular MBMS bearer service then the SRNC/Iu-mode BSC creates an MBMS service context after this procedure. + +NOTE: the MBMS Bearer Context is referred to as the MBMS Service Context in 3GPP RAN specifications + +MBMS UE De-Linking denotes the process where a MBMS UE context is removed from the RAN. + +MBMS UE De-Linking procedure is performed if the UE is PMM-CONNECTED and has been already linked towards the RAN at least when it initiates MBMS Multicast Service Deactivation procedure. This may happen at any point in time during the whole MBMS service availability i.e. before, during and between MBMS sessions. + +The UE De-Linking is performed to unlink a specific UE from a MBMS service. The entry for this UE is removed from the concerned MBMS service context(s) in the SRNC. + +## 8.16 MBMS Service Request Procedure + +For MBMS, when UTRAN wants to count the number of users that are interested in a specific MBMS service which are present in a cell, it will request a percentage of the interested UEs to transit to PMM-CONNECTED state. The MBMS Service Request procedure is used by a UE in the PMM-IDLE state to move to the PMM-CONNECTED state. The MBMS Service Request procedure is also used by a UE in PMM IDLE or PMM-CONNECTED state to request to be maintained in PMM-CONNECTED state for the purpose of receiving data over an MBMS point-to-point radio bearer. + +![Sequence diagram of the MBMS Service Request procedure showing interactions between UE, RNC, SGSN, and HLR.](a4bfa2343d75076b79f7e33d93915e00_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RNC + participant SGSN + participant HLR + + UE->>RNC: 1. RRC Connection Request + RNC-->>UE: 1. RRC Connection Setup + UE->>SGSN: 2. Service Request + Note over UE, HLR: 3. Security Functions + SGSN->>RNC: 4. Common ID + RNC->>SGSN: 5. MBMS UE Linking Request + SGSN-->>RNC: 5. MBMS UE Linking Response + Note over UE, RNC: 6. MBMS RAN Resource Setup + Note over RNC, SGSN: UE activity supervision + RNC->>SGSN: 7. Iu Release Request + SGSN-->>RNC: 7. Iu Release Command + RNC-->>SGSN: 7. Iu Release Complete + +``` + +The diagram illustrates the MBMS Service Request procedure. It begins with an RRC Connection establishment (Step 1) between UE and RNC. Then, the UE sends a Service Request to the SGSN (Step 2). Security Functions (Step 3) are performed involving all entities. The SGSN sends a Common ID to the RNC (Step 4). An MBMS UE Linking exchange occurs between RNC and SGSN (Step 5). MBMS RAN Resource Setup (Step 6) is indicated at the RNC/UE level. Following UE activity supervision, an Iu Release procedure (Step 7) occurs between the RNC and SGSN. + +Sequence diagram of the MBMS Service Request procedure showing interactions between UE, RNC, SGSN, and HLR. + +**Figure 17: MBMS Service Request procedure** + +- 1) An RRC connection is established if it doesn't already exist. + - 2) The UE sends a Service Request message to the SGSN if MBMS PTP reception shall be used or if otherwise required to do so by the RAN when MBMS reception shall be started. The Service Type shall indicate MBMS multicast service reception or MBMS broadcast service reception. The SGSN shall not release the Iu signalling connection until requested by the RAN. + - 3) The SGSN may perform the security functions. + - 4) The SGSN provides the RAN with the IMSI of the UE. + - 5) The SGSN provides the RAN with the MBMS UE context(s) (IP multicast address/APN, TMGI, MBMS\_NSAPI) via MBMS UE Linking procedure, if the SGSN has active MBMS UE context(s) for the UE. +- NOTE: Step 6 is independent of steps 4 to 5 and can occur before or simultaneously with any of these steps. +- 6) The RNC establishes the necessary radio resources for the transfer of MBMS data to the interested UEs. + +- 7) When PTP transmission of a MBMS multicast or MBMS broadcast service is active for a UE then the RNC shall supervise the Iu signalling connection. When the RAN determines that it does not need to keep the UE in RRC-CONNECTED state anymore, it shall trigger a normal Iu release towards SGSN. + +## 8.17 Notification in case of parallel services + +### 8.17.1 Notification of incoming CS domain call during an ongoing MBMS session + +For the RRC connected mobiles in UTRAN, the RNS will have received the IMSI from the core network and hence is able to perform paging coordination. The UEs in RRC idle state in UTRAN need to perform paging coordination while receiving the MBMS session's user data. + +In GERAN, this is achieved by the UE monitoring its paging channels while receiving the MBMS session's user data. If the mobile responds to the CS paging in GERAN, then the ongoing MBMS service is likely to be interrupted in the UE. + +### 8.17.2 Notification of additional MBMS session during an ongoing MBMS session + +For the RRC connected mobiles in UTRAN, the SGSN has sent the list of MBMS bearer services that the user has activated to the UTRAN. The RNS needs to notify an RRC connected UE. + +For the UEs in RRC idle state, the UTRAN performs MBMS notification for the UE. + +In GERAN, this is achieved by the UE monitoring its paging channel(s) where notification is sent while receiving the MBMS session's user data. + +If the mobile accepts the new MBMS session in GERAN, then the ongoing MBMS service is likely to be interrupted in the UE. + +### 8.17.3 Notification of Mobile Terminating PS data during an ongoing MBMS session + +For the RRC connected mobiles in UTRAN, the SGSN request the establishment of a RAB which will be used to deliver the MT user data. + +For the UEs in RRC idle state, the UTRAN performs paging notification for the UE. + +In GERAN, this is achieved by the UE monitoring its paging channels while receiving the MBMS session's user data. + +If the mobile responds to the PS paging in GERAN, then the ongoing MBMS service is likely to be interrupted in the UE. + +### 8.17.4 Notification of MBMS session during an ongoing CS or PS domain "connection" + +When the UE establishes the UTRAN RRC connection for a CS service, the UE shall send a flag indicating that it has activated at least one MBMS bearer service. The RNC requests the SGSN to send the list of MBMS bearer services that the user has activated to enable the RNC to notify the UE when MBMS session starts. + +When a UE moves to PMM-connected state, the SGSN sends the list of MBMS bearer services that the user has activated to the RNC. The RNC notifies the UE when an MBMS session of the user's activated MBMS bearer services starts. + +These procedures are not supported by GERAN in this version of the specification. + +# --- 9 Security + +Security of MBMS is found in TS 33.246 [5]. + +# 10 Charging requirement + +## 10.1 General + +The MBMS architecture shall support on-line and off-line charging. + +It shall be possible to collect charging information for the multicast mode. It shall also be possible to collect charging information for MBMS services in visited networks. + +MBMS shall collect charging information about the transmission of MBMS broadcast or multicast data that are provided by content or service providers (e.g. 3rd parties). This shall enable billing of broadcast and multicast content or service providers. + +To enable billing of broadcast and multicast content providers, data shall be collected at the BM-SC. + +NOTE: SGSN, GGSN and BM-SC generate charging data for the transmitted data, always under the assumption that the UEs are within the MBMS service area. If the MBMS service area is less than the PLMN, then there is the possibility that a UE will have moved outside the MBMS service area. Charging data will still be generated for that UE causing an inaccuracy in the data. This inaccuracy increases as the size of the MBMS service area is decreased. + +## 10.2 Bearer level charging for MBMS + +To provide bearer level charging for MBMS, mechanisms and functional elements described in TS 23.125 [12] are used for MBMS Bearer Contexts. + +For EPS, MBMS GW shall collect charging information about the transmission of MBMS broadcast for UTRAN and E-UTRAN. MBMS Bearer context in MBMS GW should include charging related information elements. + +Flow Based Charging (FBC) may be used to collect charging data records for MBMS Bearer Contexts e.g. for the purpose to charge the service provider, cf. TS 23.125 [12]. + +NOTE: Since multiple users share an MBMS bearer context FBC cannot be used for creating reports on a per user basis. + +## 10.3 Application level charging for MBMS + +For GPRS, in order to meet the MBMS charging requirements in TS 22.146 [2] and TS 22.246 [6], the following elements and functionalities are provided by the GPRS MBMS architecture: + +- a) The MSISDN and IMSI are passed to the BM-SC. This provides the operator with the ability to associate GPRS location information (i.e. serving network identity) with a user. +- b) In order to permit differential roaming tariffs, the serving network identity is provided to the BM-SC. +- c) Charging for MBMS services is based on application layer mechanisms, since it is only at the application layer that security is provided which can restrict content to authorised users or confirm delivery of content to users: + +The following general requirements apply to charging information generated by the BM-SC: + +- Charging information generated for application layer charging events should include the above information provided by the GPRS network to facilitate differential roaming tariffs. +- Charging information should include an indication of the point at which the user had access to the content (e.g. if and when decryption keys for encrypted content are sent to the UE.). + +For EPS, in order to meet the MBMS charging requirements in TS 22.146 [2], charging requirements for MBMS in EPS should be supported in broadcast mode and be same as that in broadcast mode for MBMS in GPRS network on application level. + +## 10.4 Generation of charging records in the VPLMN + +In this Release, charging for roaming scenario of MBMS in EPS will not be considered. + +For GPRS, in order to permit the settlement of inter-operator roaming charges , the SGSN needs to raise CDRs. The information that needs to be included on these CDRs is FFS. + +# --- 11 Roaming Support for MBMS user services + +## 11.1 Scenarios description + +There are three specific scenarios to provide MBMS user services to roaming users. + +One uses a GGSN in the HPLMN, the other two are enabled by use of the Mz interface and are further described below: + +- A visited PLMN may offer to roaming users MBMS user services from their home PLMN. For this case, the PDP connection, which will be used for the JOIN step, may always be from the UE to the V-GGSN due to operator policy or routing optimization, then the authorization is done in the BM-SC in visited PLMN with the authorization information retrieved from the BM-SC in home PLMN. Then the MBMS user traffic is provided by the BM-SC in home PLMN and proxied. An APN indicating a GGSN will be included in the authorisation information sent from home BM-SC to visited BM-SC. Whether GGSN of home or visited PLMN would be used is based on the operator policy, or agreement between PLMNs, for example, the visited BM-SC may modify the APN from the home BM-SC according to configuration of operator policy. +- Or, a visited PLMN may offer its own MBMS user services to roaming users when visited and home PLMN support the same classes of MBMS user services. For this case, the authorization is done in the BM-SC in visited PLMN with the authorization information retrieved from the BM-SC in home PLMN. Then the MBMS user traffic is provided by the BM-SC in visited PLMN. + +**Editors' note: It is FFS how to deal with the services in the BM-SC in visited network which are not the same service class as supported by the BM-SC in home network.** + +The usage of any of the scenarios and the offered MBMS user services are subject to the roaming agreement between visited and home PLMN operators. + +## 11.2 Scenario signalling flow + +### 11.2.1 APN selection + +When a UE is authorized through the BM-SC in the visited PLMN (by proxying the authorization signalling), an APN may be selected and decided by the BM-SC in the home PLMN or the BM-SC in the visit PLMN depending on the operator policy or agreement between PLMNs. See step 4 of the figure 18. + +![Sequence diagram for MBMS route optimization for HPLMN provided MBMS services. The diagram shows interactions between V-SGSN, GGSN, BM-SC in Visit PLMN, and BM-SC in Home PLMN. The process involves PDP activation, IGMP, authorization requests and responses, notification to the UE, activation request, APN resolution, and MBMS context creation.](5801c19431e76330430e92a598cc7a16_img.jpg) + +``` + +sequenceDiagram + participant UE + participant V-SGSN + participant GGSN + participant BM-SC_Visit as BM-SC in Visit PLMN + participant BM-SC_Home as BM-SC in Home PLMN + + Note left of V-SGSN: 1. PDP activation + UE->>V-SGSN: + V-SGSN->>GGSN: 2. IGMP + GGSN->>BM-SC_Visit: 3. Authorization request + BM-SC_Visit->>BM-SC_Home: 4. Authorization request + BM-SC_Home-->>BM-SC_Visit: 4. Authorization response (APN) + BM-SC_Visit-->>GGSN: 5. Authorization response (APN) + GGSN->>V-SGSN: 6. Notification and other signalling to the UE + V-SGSN-->>UE: + Note left of V-SGSN: 7. Activation request (APN) + V-SGSN->>GGSN: + Note left of V-SGSN: 8. Resolve the APN + V-SGSN->>GGSN: 9. Create MBMS context + GGSN->>BM-SC_Home: 10. Authorization request + BM-SC_Home-->>GGSN: 10. Authorization response + GGSN->>V-SGSN: 11. Create MBMS context + V-SGSN-->>UE: + +``` + +Sequence diagram for MBMS route optimization for HPLMN provided MBMS services. The diagram shows interactions between V-SGSN, GGSN, BM-SC in Visit PLMN, and BM-SC in Home PLMN. The process involves PDP activation, IGMP, authorization requests and responses, notification to the UE, activation request, APN resolution, and MBMS context creation. + +**Figure 18: MBMS route optimization for HPLMN provided MBMS services** + +Figure 18 is an extension of MBMS multicast service activation procedure described in clause 8.2, the only revise is that an authorization step (step 4) is added according to clause 11.1. + +- The BM-SC in visited PLMN finds the BM-SC in home PLMN which will serve the UE based on the multicast IP address, and identity of the user, and sends the authorization request to it. The BM-SC in home PLMN can respond with an APN, which indicates a GGSN in home PLMN which will serve the UE for the specific MBMS service. The BM-SC in the visit network may modify the APN based on the operator policy or agreement between PLMNs. + +# --- Annex A (Informative): Void + +# --- Annex B (Informative): Void + +# --- Annex C (normative): TV services delivery using unicast mode & switching between broadcast & unicast modes for E-UTRAN + +To enable TV services delivery using unicast mode of transport, the applicable functions need to be enabled in the operator's network: + +UE: + +Able to support TV services as required including: + +- For Unicast support, there needs to be additional PDN connection via dedicated APN for TV services delivery. + +NOTE: It can require explicit connection towards TV Content Provider for Unicast reachability information (e.g. IP addresses, ports, etc.). UE should be configured with appropriate APN to facilitate easy access to TV services via unicast. + +- Ability to support Consumption Reporting and MooD feature for enabling switching between broadcast and unicast operation on demand, if required. + +Content Provider/Packet Streaming Server needs to provide the required functions for MBMS Broadcast services as defined in this specification. The operator needs to enable access to the transport and MBMS user services towards TV content providers, if required, as described in clause 7.5. + +MME: If APN is configured in the HSS for enabling unicast delivery for TV services for the user, then MME checks when UE provides an APN and verifies that the user has subscription for that APN against the HSS provided APN, using existing procedures. + +HSS: Shall be configured well known dedicated APN in the user's subscription for Unicast TV services support when dedicated PDN connectivity for TV services is required. + +The main deployment options for TV services are, but not limited to : + +## Deployment Option 1: + +Joint broadcast + unicast TV service through BM-SC and PDN GW via SGi. + +### Scenario A: + +The Content Provider has a Service Level Agreement with an operator. The dedicated TV service includes a TV Service subscription associated with the operator subscription, which allows tuning to TV unicast and MBMS broadcast for transport. + +In case popularity based switching according to MBMS operations on Demand (MooD, TS 26.346 [7]) is supported, then: + +- The operator monitors the TV service consumption per channel in areas and decide to use unicast or MBMS broadcast usage. + +According to the agreement between the Content Provider and the operator, the operator may provide usage information to the Content Provider. + +### Scenario B : + +This Scenario enables the realization for multi-purpose devices, where the managing operator provides all functionality. + +In case popularity based switching according to MBMS operations on Demand (MOOD, TS 26.346 [7]) is supported, then: + +- The operator monitors the TV service consumption per channel in areas and decide to use unicast or MBMS broadcast transport. + +According to the agreement between the Content Provider & the operator, the operator may provide usage information to the Content Provider. + +## **Deployment option 2:** + +Separate direct broadcast service through BM-SC and direct unicast service via SGi through PDN GW. + +For Unicast TV transport, the Content Provider uses regular unicast data connectivity. For MBMS broadcast, the Content Provider provides the content of the TV channel via user plane. + +In case popularity based switching according to MBMS operations on Demand (MooD, TS 26.346 [7]) is supported, then: + +- The Content Provider monitors the popularity of the TV service over Unicast, for each operator individually. +- When unicast TV service usage of a channel is high in a certain area, the Content Provider interacts with operator in order to activate MBMS Broadcast in the identified area. + +In order to monitor popularity in the MBMS Broadcast Areas, the operator can expose popularity information (derived from HTTP Consumption Reporting, TS 26.346 [7]) to the Content Provider via dedicated provisioning interface (see TS 26.348 [31]). + +# Annex D (normative): Shared MBMS Network over E-UTRAN + +## D.1 General + +A Shared MBMS network (SMN) consists of network elements shared by multiple PLMNs to offer MBMS service over E-UTRAN. The shared network elements are at least a shared BM-SC and shared MBMS-GW. Shared MBMS Network has MBMS synchronization area (MBSFN area) defined within each PLMN. + +The SMN has the following properties: + +- The BM-SC and MBMS-GW are shared among participating PLMNs. +- The SMN provides the entry point of the data stream. +- The BM-SC can provide full service layer functionality or act only in transparent mode for the case of MBMS as transport only. +- An MBMS service area may span across RAN nodes from different participating PLMNs. +- RAN nodes (eNBs/MCEs) dedicated to MBMS bearer service may be deployed, in which case these nodes are part of the SMN. This deployment requires a shared MME function. + +## D.2 Architecture + +### D.2.1 Architecture for per PLMN MBSFN synchronization area + +Figure D.2.1-1 shows an example network architecture for Shared MBMS Network with MBMS synchronization area defined within each PLMN. The example shows two PLMNs (PLMN 1 and PLMN2) providing shared MBMS service. In the example, F3 is shared spectrum used by all involved PLMN for MBMS service. + +![Figure D.2.1-1: Shared MBMS Network architecture with per-PLMN MBMS synchronization area. The diagram illustrates the network architecture for Shared MBMS Network (SMN) with per-PLMN MBMS synchronization areas. It shows two PLMNs (PLMN 1 and PLMN 2) sharing a common SMN infrastructure. The SMN includes a shared MBMS-GW (SMN) and a shared BM-SC (SMN). PLMN 1 and PLMN 2 each have their own RAN (RAN(1) and RAN(2)), MME (MME(1) and MME(2)), S-GW (S-GW(1) and S-GW(2)), and P-GW (P-GW(1) and P-GW(2)). The RANs are connected to the SMN via F3 interfaces. The SMN is connected to the BM-SC via SGmb and SGi-mb interfaces. The legend indicates that solid lines represent shared broadcast and dashed lines represent unicast.](cc468dcda006ef315536400517a09ad3_img.jpg) + +Legend: + +- (SMN) Shared MBMS network element +- (1) PLMN 1 network element +- (2) PLMN 2 network element +- Shared broadcast +- - - Unicast + +Figure D.2.1-1: Shared MBMS Network architecture with per-PLMN MBMS synchronization area. The diagram illustrates the network architecture for Shared MBMS Network (SMN) with per-PLMN MBMS synchronization areas. It shows two PLMNs (PLMN 1 and PLMN 2) sharing a common SMN infrastructure. The SMN includes a shared MBMS-GW (SMN) and a shared BM-SC (SMN). PLMN 1 and PLMN 2 each have their own RAN (RAN(1) and RAN(2)), MME (MME(1) and MME(2)), S-GW (S-GW(1) and S-GW(2)), and P-GW (P-GW(1) and P-GW(2)). The RANs are connected to the SMN via F3 interfaces. The SMN is connected to the BM-SC via SGmb and SGi-mb interfaces. The legend indicates that solid lines represent shared broadcast and dashed lines represent unicast. + +Figure D.2.1-1: Shared MBMS Network architecture with per-PLMN MBMS synchronization area + +The SMN contains the following network elements: + +- Shared BM-SC (denoted BM-SC(SMN) in Figure D.2.1-1): + - Provides all the functionality defined in clause 5.1 for EPC. +- Shared MBMS-GW (denoted MBMS-GW(SMN) in Figure D.2.1-1) + - Provides all the functionality defined in clause 5.9.1. + - In addition: + - It connects to MMEs from one or multiple PLMNs via the inter-PLMN Sm-s reference point for control plane signalling. + - It connects to E-UTRAN nodes from one or multiple PLMNs via the inter-PLMN M1-s reference point for IP multicast distribution. + +The SMN may also contain shared E-UTRAN functionality for the purpose of MBMS service only. In that case the SMN also contains the following network entities: + +- Shared E-UTRAN - eNB, MCE (denoted RAN(SMN) in Figure D.2.1-1) + - Provides functionality as defined in clause 5.9.1. +- Shared MME MBMS function (denoted MME(SMN)): + - The shared MME MBMS control function provides the functionality defined in clause 5.9.2. + +NOTE: The shared MME MBMS control function provides only a subset of the functionality of a regular MME as defined in TS 23.401 [16], dedicated only to providing control plane functionality related to MBMS service. + +### D.2.2 Reference Points + +The following reference points are defined for Shared MBMS Network: + +- All internal reference points within the SMN leverage existing reference points M1, M2, M3, Sm, SGmb, SGi-mb. +- All internal reference points within each PLMN existing reference points M2, M3 +- M1-s: + - Inter-PLMN reference point between the Shared MBMS-GW and the E-UTRAN node from a participating PLMN. + - Provides equivalent functionality to M1. +- Sm-s: + - Inter-PLMN reference point between the Shared MBMS-GW and MME from a participating PLMN. + - Provides equivalent functionality to Sm. + +### D.2.3 UE Aspects + +Different scenarios can be supported from the perspective of the UE. The following is a non-exhaustive list of possible scenarios: + +- UE Scenario 1: The UE receives both unicast and broadcast service from same PLMN. The UE follows the same functionality as defined in clause 5.2. +- UE Scenario 2: The UE receives broadcast MBMS service without PLMN subscription over E-UTRAN without the need to access and register with the PLMN offering the MBMS service. The UE acts in Receive Only mode as defined in Annex E. + +UE Scenario 3: The UE receives unicast service from one serving PLMN's (e.g. the PLMN for which it has unicast subscription), and receive MBMS service through a different PLMN. The UE acts in Receive Only mode with independent unicast as defined in Annex E. + +### D.2.4 TMGI for shared MBMS networks + +As described in TS 23.003 [13], the TMGI is composed by an MBMS Service ID and a PLMN ID (MCC/MNC). + +The construction of the PLMN ID field in the TMGI is deployment dependent. The following are example deployment options: + +- Example Deployment Option 1: Shared PLMN ID + - A Shared PLMN ID is used for the shared MBMS service. The shared PLMN ID is broadcasted in the cells broadcasting the shared MBMS service content. +- Example Deployment Option 2: Internal PLMN ID in the Shared MBMS network + - The Shared MBMS network (i.e. BMSC) uses the "Internal" PLMN ID to generate the TMGI. MBMS-GW uses the PLMN ID from the incoming SGmb interface towards the rest of the network entities in the MBMS path. eNB announces a MBMS session TMGI whose PLMN ID is not in the SIB1 PLMN ID list. The "Internal" PLMN ID is not used for any other PLMN services. + +# --- Annex E (normative): UE behaviour in Receive Only Mode + +A UE configured as Receive Only Mode can receive only MBMS broadcast service over E-UTRAN without the need to access and register with the PLMN offering the MBMS service. A UE configured to operate in Receive Only Mode shall camp on a network cell in an eMBMS Broadcast carrier, shall attempt to receive MBMS service based only on a standardised TMGI value range for Receive Only Mode. The UE shall not attempt to receive MBMS service for TMGIs outside the standardized TMGI range. The UE shall refrain from any Mobility Management or other signalling with the network offering MBMS. The UE uses the acquired system information to receive MBMS broadcast. Use of Receive Only Mode does not require USIM for the UE. + +A UE may be configured as Receive Only Mode with independent unicast using EPS bearer contexts. This configuration option allows a UE to operate as Receive Only Mode (as defined above) for MBMS broadcast service, and independently follows regular NAS/RRC procedures for unicast service with a PLMN. This mode of operation requires USIM and PLMN subscription to receive unicast service. No additional subscription or credentials are required to receive MBMS broadcast service. + +Any device that is equipped with MBMS broadcast receiver and is configured to operate in Receive Only Mode is able to receive the broadcast content, with the following characteristics: + +- No PLMN credentials/subscription are required, as long as use of EPS unicast bearers is not required by the device. +- Without PLMN credentials/subscription, the UE can only access broadcast services without subscription. The content can be Free To Air (FTA) content as defined in TS 22.101 [30] in which case it can be viewed without content subscription. +- There is no need for the UE to support uplink. + +NOTE: It is possible though that there is content protection handled at application layer. In that case security is provided at application layer, and keys, etc. are provisioned out of band. This provisioning is out of scope of 3GPP. + +The UE is preconfigured with all the necessary information for the UE to acquire the system information and receive MBMS service. This information includes: + +- PLMN ID(s) that provide the MBMS service. +- TMGI(s): + - In the case of the network providing MBMS service in MBMS transport only mode, the TMGI(s) for each MBMS service need to be configured in the UE. + - The UE may be configured to receive TMGI(s) via Service Announcement (see clauses 4.4.3.1, 5.1.4 and 6.4). +- RAN specific information, +- USD(s). + +Figure E-1 shows the components of a UE in Receive Only Mode and in Receive Only Mode with independent unicast. + +![Diagram showing UE components in Receive Only Mode and Receive Only Mode with independent unicast.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +The diagram illustrates two User Equipment (UE) configurations and their connections to network components. + +**UE in Receive Only Mode:** This configuration is shown in a box at the top left. It contains a dashed horizontal line separating the top section from the bottom. The bottom section contains two components: "Broadcast Component" and "Receive Only Mode". An arrow points from the "Receive Only Mode" component to an oval labeled "eMBMS Broadcast". + +**UE in Receive Only Mode with independent unicast:** This configuration is shown in a box below the first one. It is divided into three horizontal sections by dashed lines. The top section contains "Broadcast Component" and "Receive Only Mode". The middle section contains "Unicast Component" and "NAS/RRC/etc". The bottom section is empty. Arrows point from the "Receive Only Mode" component and the "NAS/RRC/etc" component to an oval labeled "PLMN A". + +Diagram showing UE components in Receive Only Mode and Receive Only Mode with independent unicast. + +**Figure E-1: UE components in Receive Only Mode and Receive Only Mode with independent unicast** + +The unicast component is active only in Receive Only Mode with independent unicast. The unicast component follows regular NAS/RRC procedures for E-UTRAN/EPC in order to receive unicast service. + +For the broadcast component, the UE is configured with MBMS radio resources for TV service with no PLMN subscription. The broadcast component of the UE shall camp on a network cell in an eMBMS Broadcast carrier and shall attempt to receive MBMS service based only on a standardised TMGI value range. The UE shall not attempt to receive MBMS service for TMGIs outside the standardized TMGI range. The broadcast component shall refrain from any Mobility Management or other signalling with the network offering MBMS. The broadcast component uses the acquired system information to receive MBMS broadcast. + +# Annex C (Informative): Change history + +| Change history | | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------|---------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2011-12 | SA#54 | SP-110748 | 0269 | 4 | C | MBMS data transfer time | 11.0.0 | | +| 2012-03 | SA#55 | SP-120088 | 0273 | - | F | Correction to Absolute Start Time for MBMS Data Delivery | 11.1.0 | | +| 2013-12 | SA#62 | SP-130534 | 0276 | 3 | C | M1 Group reuse | 12.0.0 | | +| 2014-03 | SA#63 | SP-140102 | 0277 | 1 | B | MBMS bearer priority update | 12.1.0 | | +| 2014-06 | SA#64 | SP-140377 | 0279 | 2 | F | Resource allocation for the MBMS bearer | 12.2.0 | | +| 2014-06 | SA#64 | SP-140260 | 0281 | 1 | F | Lift restriction GBR=MBR for MBMS when GCSE is used | 12.2.0 | | +| 2014-09 | SA#65 | SP-140425 | 0384 | 1 | F | Clarify the MBMS session update procedure | 12.3.0 | | +| 2014-12 | SA#66 | SP-140678 | 0387 | 4 | F | Long Group Calls and New Cells | 12.4.0 | | +| 2015-03 | SA#67 | SP-150015 | 0390 | - | A | Correction to BM-SC initiated Session Update procedure | 12.5.0 | | +| 2015-03 | SA#67 | SP-150027 | 0391 | 2 | B | eMBMS alternative IP multicast distribution address | 13.0.0 | | +| 2015-03 | SA#67 | SP-150239 | 0392 | 1 | F | MBMS Session Start procedure correction and editorial corrections | 13.1.0 | | +| 2015-09 | SA#69 | SP-150239 | 0394 | 2 | A | Support for UE Consumption Reporting towards BM-SC | 13.2.0 | | +| 2015-09 | SA#69 | SP-150506 | 0396 | 2 | B | MBMS bearer establishment and update with cell ID list | 13.2.0 | | +| 2015-12 | SA#70 | SP-150616 | 0397 | 2 | F | Cell ID in MBMS bearer context table for EPS | 13.3.0 | | +| 2015-12 | SA#70 | SP-150614 | 0398 | 2 | F | Differentiate MBMS User and Bearer Services | 13.3.0 | | +| 2016-09 | SA#73 | SP-160656 | 0402 | 1 | B | Enhanced TV services using Broadcast and Unicast mode of operation | 14.0.0 | | +| 2016-09 | SA#73 | SP-160656 | 0404 | 2 | B | Introducing Shared eMBMS Network and Receive Only Mode for TV services | 14.0.0 | | +| 2016-12 | SA#74 | SP-160820 | 0405 | 1 | F | Corrections of MBMS Shared Network | 14.1.0 | | +| 2016-12 | SA#74 | SP-160820 | 0406 | 1 | F | 3GPP network and Content provider reference point | 14.1.0 | | +| 2016-12 | SA#74 | SP-160820 | 0407 | 1 | F | Shared MBMS Network scope clarification | 14.1.0 | | +| 2016-12 | SA#74 | SP-160820 | 0408 | 2 | F | Use of TMGI & PLMN ID for Shared MBMS Network | 14.1.0 | | +| 2016-12 | SA#74 | SP-160825 | 0412 | 1 | F | MBMS Update with session time | 14.1.0 | | +| 2017-09 | SA#77 | SP-170723 | 0414 | 4 | C | UE Capabilities for MBMS | 14.2.0 | | +| 2017-12 | SA#78 | SP-170928 | 0415 | 1 | C | MBMS session setup/event notification procedure alignment with RAN WG3 | 15.0.0 | | +| 2017-12 | SA#78 | SP-170928 | 0416 | 2 | F | MB2 improvements for GCS AS to be able to request application of FEC and/or RoHC to a MBMS bearer | 15.0.0 | | +| 2019-03 | SA#83 | SP-190175 | 0417 | 1 | F | Change xMB reference | 16.0.0 | | +| 2019-09 | SA#85 | SP-190602 | 0419 | 2 | A | Fix missed update to Session Update procedure - add delayed response | 16.1.0 | | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23271/0931f3e098bd4539041de11c50cec2d2_img.jpg b/marked/Rel-16/23_series/23271/0931f3e098bd4539041de11c50cec2d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..334cfa1af7d4c71d24b5f708f6baa4aa0170193c --- /dev/null +++ b/marked/Rel-16/23_series/23271/0931f3e098bd4539041de11c50cec2d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf5b89f35faf28fcb428064812b9e4d41c7eb4425451d59077a77e9bda001f28 +size 45711 diff --git a/marked/Rel-16/23_series/23271/0a12cc47f3c5ca76c39d5943ba8661bd_img.jpg b/marked/Rel-16/23_series/23271/0a12cc47f3c5ca76c39d5943ba8661bd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9ddf262c71397a0beb48bb1afdaa52b8a8ca0917 --- /dev/null +++ b/marked/Rel-16/23_series/23271/0a12cc47f3c5ca76c39d5943ba8661bd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:edade56420fa6c7c9a9624034da706230da85b5c0f8a6545241ccdf5999090f1 +size 15460 diff --git a/marked/Rel-16/23_series/23271/10bf8762a8e8d9385609cc6fb11061fe_img.jpg b/marked/Rel-16/23_series/23271/10bf8762a8e8d9385609cc6fb11061fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4548f945073a95c52a7047f5a8ebba078ad076a --- /dev/null +++ b/marked/Rel-16/23_series/23271/10bf8762a8e8d9385609cc6fb11061fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:718c5260cc11ce4ff9bcc43cf18f89ca80598386ac01e4fcc31893c2f27dabd6 +size 41659 diff --git a/marked/Rel-16/23_series/23271/10ceb47973510a1b47421741263146cc_img.jpg b/marked/Rel-16/23_series/23271/10ceb47973510a1b47421741263146cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c288133f3f76ca50a3f878e09b2100ff24ff74d5 --- /dev/null +++ b/marked/Rel-16/23_series/23271/10ceb47973510a1b47421741263146cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0171ef7ba58760885902a2891d8137a2623fab4dbd25fbbee4c18179ceb0fdb6 +size 68924 diff --git a/marked/Rel-16/23_series/23271/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/Rel-16/23_series/23271/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f56052e83770c8acd72624e8e4fcb0226e552ce2 --- /dev/null +++ b/marked/Rel-16/23_series/23271/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e3a6953b64eba3164ac3b0d60ebc1df8b8985932a715db4d70136434a534fc59 +size 107160 diff --git a/marked/Rel-16/23_series/23271/1381593e48739f603c81fa60e6b98a6c_img.jpg b/marked/Rel-16/23_series/23271/1381593e48739f603c81fa60e6b98a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..868d25e90f66ef8482054410c23578e360239ceb --- /dev/null +++ b/marked/Rel-16/23_series/23271/1381593e48739f603c81fa60e6b98a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb0e69402d3af506f092547f469fba25fdb5e704450c46255180cea1b61c00e2 +size 29235 diff --git a/marked/Rel-16/23_series/23271/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/23_series/23271/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5558c9a9658104da0019d3d9d09f7ba744418934 --- /dev/null +++ b/marked/Rel-16/23_series/23271/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67bb4dbea93db6fbf0f62e0abb924262bca377e7a693e8d734ae5490dfa42f4e +size 91007 diff --git a/marked/Rel-16/23_series/23271/1e8c50ad4fca7f315a407347dd5091cc_img.jpg b/marked/Rel-16/23_series/23271/1e8c50ad4fca7f315a407347dd5091cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af46d27fc0118872cd3bda69ba2c07612cea64fd --- /dev/null +++ b/marked/Rel-16/23_series/23271/1e8c50ad4fca7f315a407347dd5091cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1713ba80d7d2a87af1cbd8b0ec568f4937ab7f61093c0d30da40b180ea297a33 +size 113745 diff --git a/marked/Rel-16/23_series/23271/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/marked/Rel-16/23_series/23271/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cc8a3be1cf6ad0fe8fba53062d4ad6e00fda9a5 --- /dev/null +++ b/marked/Rel-16/23_series/23271/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c9e3d593e0689103d475233afbda4e824b9ff061c502f4af8051c6cf09b29407 +size 122877 diff --git a/marked/Rel-16/23_series/23271/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/23_series/23271/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ced66aacc5186497aee71f4eb2a70441a01a634 --- /dev/null +++ b/marked/Rel-16/23_series/23271/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ee5eb6c0e4fe9c2843c33c8985f0a311defc2b1e9615da8331426a89745edee3 +size 172182 diff --git a/marked/Rel-16/23_series/23271/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/23_series/23271/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f3eb664420ac9c82746c9bc63cd761c26713aab --- /dev/null +++ b/marked/Rel-16/23_series/23271/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c37f4f40ed00e4f3f473bdab15bbc465971d3699fc5e2c4e282c9fb6cb449ed +size 47315 diff --git a/marked/Rel-16/23_series/23271/32ff77da4286b58c4778033acaa10836_img.jpg b/marked/Rel-16/23_series/23271/32ff77da4286b58c4778033acaa10836_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5e0ad28d922645bad209641b57ec5baf40e0f5d --- /dev/null +++ b/marked/Rel-16/23_series/23271/32ff77da4286b58c4778033acaa10836_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8c7d7c9eca34aaf3418c018060d373b91c0be2f1e288287b7840dde11abd6e34 +size 49328 diff --git a/marked/Rel-16/23_series/23271/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-16/23_series/23271/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8a2d228afbb0ca464f48d7717baa91a3eeff347a --- /dev/null +++ b/marked/Rel-16/23_series/23271/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3b5d358838ba70ba3207c624e88eadb9930533bfdffd8ea3a604f6475d573216 +size 83613 diff --git a/marked/Rel-16/23_series/23271/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-16/23_series/23271/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8224bf8448e54631747392fb83b3be0810ec0892 --- /dev/null +++ b/marked/Rel-16/23_series/23271/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f0322db4970196a2ee334fa2def9f1a828b75815ad6472ec3c10b5c3305c266 +size 53906 diff --git a/marked/Rel-16/23_series/23271/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/marked/Rel-16/23_series/23271/367926125450c2bc3f4bdca9d59a62ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7065bd6229bd3aee5ddf922eeaaf25c1a5fbe3b6 --- /dev/null +++ b/marked/Rel-16/23_series/23271/367926125450c2bc3f4bdca9d59a62ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a7d72d07a1c8c609b0bf8c532b63d88b9ecc6088b81652558d6d2d07d65dd49 +size 86123 diff --git a/marked/Rel-16/23_series/23271/36fd537a1e39baa2471ecfaaf869751a_img.jpg b/marked/Rel-16/23_series/23271/36fd537a1e39baa2471ecfaaf869751a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..88abb46c82593fa6e21fa745675193deda021c66 --- /dev/null +++ b/marked/Rel-16/23_series/23271/36fd537a1e39baa2471ecfaaf869751a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f67f36f5809811778301067bcf2a747f41ce3bf40e2b15fc020abf82c0703f8d +size 52199 diff --git a/marked/Rel-16/23_series/23271/408c4798ea60469e0728a7cbbd598668_img.jpg b/marked/Rel-16/23_series/23271/408c4798ea60469e0728a7cbbd598668_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82a5a50c5e0ecdc9ea818533358bff481cc8bf34 --- /dev/null +++ b/marked/Rel-16/23_series/23271/408c4798ea60469e0728a7cbbd598668_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bcc7f7d3d42cf8da7fa3f8f0480763676fde53f37e6b377b889a271b071559e1 +size 79840 diff --git a/marked/Rel-16/23_series/23271/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23271/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af1365ac3945aac7258985313ebc844d5aa0484f --- /dev/null +++ b/marked/Rel-16/23_series/23271/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:93a00b329c7756271b8b88c464155bd55e02814d2b6031905107c2e8c089bbdb +size 50934 diff --git a/marked/Rel-16/23_series/23271/4792a2ccd62226861fadc22117edb7b1_img.jpg b/marked/Rel-16/23_series/23271/4792a2ccd62226861fadc22117edb7b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a141f2fccc1541b7e6a79dae89f74819351deed9 --- /dev/null +++ b/marked/Rel-16/23_series/23271/4792a2ccd62226861fadc22117edb7b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02b429359932ef28b41f1461ea4254f3095743a8cc9707e5718f8e17a6d8b792 +size 18222 diff --git a/marked/Rel-16/23_series/23271/4842f073775fb1e84d101c02fd74e59e_img.jpg b/marked/Rel-16/23_series/23271/4842f073775fb1e84d101c02fd74e59e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee8b29b9d4ad8473bb7add2496da14be586f30ec --- /dev/null +++ b/marked/Rel-16/23_series/23271/4842f073775fb1e84d101c02fd74e59e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8584649eb39561f32961dcadff533b55928aa9a6ba2f5c0e54d1732284766569 +size 112166 diff --git a/marked/Rel-16/23_series/23271/4b87467ad9642943235f48f7d4b59449_img.jpg b/marked/Rel-16/23_series/23271/4b87467ad9642943235f48f7d4b59449_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e28a628e000977bd3e01aa0d97414e65ca60e86c --- /dev/null +++ b/marked/Rel-16/23_series/23271/4b87467ad9642943235f48f7d4b59449_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:75476c65e786507ab255a70ae4e515ac0c1cc4d5a113730cd18d87d3c8ccba40 +size 60010 diff --git a/marked/Rel-16/23_series/23271/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg b/marked/Rel-16/23_series/23271/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..02bd9da81e951348c6e4bb9681e4baa68c807a14 --- /dev/null +++ b/marked/Rel-16/23_series/23271/5132b3a97ac70fe4765c1e07e66b72b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:73534b7508b3e80e4dd01b7cea2b3ed939165abcc711b4e6bb612965c105bfbb +size 25703 diff --git a/marked/Rel-16/23_series/23271/52f68e21acc86c9aaab2f5abc51a9748_img.jpg b/marked/Rel-16/23_series/23271/52f68e21acc86c9aaab2f5abc51a9748_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50d5de1373978552de3aab20030114fe324763d6 --- /dev/null +++ b/marked/Rel-16/23_series/23271/52f68e21acc86c9aaab2f5abc51a9748_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8745608ceb4221a0938f16d3db80206921fb798fa738e250160285d9789c6ac +size 31154 diff --git a/marked/Rel-16/23_series/23271/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/23_series/23271/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..743d0923434b0820437d451f7e490041695b899f --- /dev/null +++ b/marked/Rel-16/23_series/23271/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:490d9b9e64b3d6d85883f46facc62e0d52658d61af4008af454bd7deb807564e +size 103186 diff --git a/marked/Rel-16/23_series/23271/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-16/23_series/23271/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..432369e216a8750af0eb22181b0e4a5e5b6f5a29 --- /dev/null +++ b/marked/Rel-16/23_series/23271/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97fd58cfac348d827bbfdcb53fd9297b6f703af55deaf25759be0e518ba735bc +size 109322 diff --git a/marked/Rel-16/23_series/23271/69edc2887e907309499ac95b47ab6905_img.jpg b/marked/Rel-16/23_series/23271/69edc2887e907309499ac95b47ab6905_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f91cc6055c4b14615d2874fc7b4f8f73fe01ba2 --- /dev/null +++ b/marked/Rel-16/23_series/23271/69edc2887e907309499ac95b47ab6905_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2cd8d68662e62000251f80bc3f2fc5f1e21a8c7a272f3aa7d69a6534554b500b +size 95426 diff --git a/marked/Rel-16/23_series/23271/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/23_series/23271/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..07d5f592c03220f0eca66d24f282ef968ea4aa0a --- /dev/null +++ b/marked/Rel-16/23_series/23271/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df94e7c42ecafc6cdaf734190dfbb8a9b7d869c91762f1ebc4336d2062ce914c +size 77936 diff --git a/marked/Rel-16/23_series/23271/7136ef99edf9289cc069898bd584d3aa_img.jpg b/marked/Rel-16/23_series/23271/7136ef99edf9289cc069898bd584d3aa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9516c7e929adbbc95a7e4bc2f3f20f2fb61ea4cd --- /dev/null +++ b/marked/Rel-16/23_series/23271/7136ef99edf9289cc069898bd584d3aa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5800f2a0e065b6e45fa6b74c714245619a22a1f38b79650d12fd1bea98afb854 +size 68159 diff --git a/marked/Rel-16/23_series/23271/76d19e4271bf243b20d55a98efd51483_img.jpg b/marked/Rel-16/23_series/23271/76d19e4271bf243b20d55a98efd51483_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f00c46b48fe3e821dea752204eb91325d51c5d5 --- /dev/null +++ b/marked/Rel-16/23_series/23271/76d19e4271bf243b20d55a98efd51483_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd65f68a30507b3bd36418ee323d515f98a246a1ca38b12663aa7bbad375772a +size 106104 diff --git a/marked/Rel-16/23_series/23271/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23271/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..10a9069c4e56cc16581dbb99a36b3fde1ffef8af --- /dev/null +++ b/marked/Rel-16/23_series/23271/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1471c54d73129f3631ebd984a60fe1564bd02d0963a80e971c2cadb5e277ff8c +size 89525 diff --git a/marked/Rel-16/23_series/23271/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg b/marked/Rel-16/23_series/23271/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c10476b6d3de219984b96da28cd50de65318c344 --- /dev/null +++ b/marked/Rel-16/23_series/23271/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c3449db877da45deab3118a861804b2fa2a8bd0ec6beec6da5e5cbc6c016a9c +size 76496 diff --git a/marked/Rel-16/23_series/23271/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/23_series/23271/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6cb8bb0a82eb694f804314279ea7d9da8e44116 --- /dev/null +++ b/marked/Rel-16/23_series/23271/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e06281a4ba3b769b17c8b78e3fa517b444f1491c5c3d0955ac808713470e384 +size 122440 diff --git a/marked/Rel-16/23_series/23271/820515db47ded68f5e0b625f4ec7d2c1_img.jpg b/marked/Rel-16/23_series/23271/820515db47ded68f5e0b625f4ec7d2c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..303cec9277bd040a0f8dd70cb36c8fbc230cd2cb --- /dev/null +++ b/marked/Rel-16/23_series/23271/820515db47ded68f5e0b625f4ec7d2c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:032c49ecca40f7aaa09caac5953adda6376e60843138ce75566b8bcc34c8ed9f +size 20700 diff --git a/marked/Rel-16/23_series/23271/8307f6b04df072c9332f9987e034272c_img.jpg b/marked/Rel-16/23_series/23271/8307f6b04df072c9332f9987e034272c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d8cdec25e381bb4c8512bf1ea1649f90e52f469 --- /dev/null +++ b/marked/Rel-16/23_series/23271/8307f6b04df072c9332f9987e034272c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:25274640cf088dacf95c7f5415fb50caa27e2652b3400dbb0b17efee4cf290f2 +size 50105 diff --git a/marked/Rel-16/23_series/23271/88b0f3f4393228e9ea4d6542aef7c399_img.jpg b/marked/Rel-16/23_series/23271/88b0f3f4393228e9ea4d6542aef7c399_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a32ca3dddf2ecf6b7125fee66906127bbf222f6e --- /dev/null +++ b/marked/Rel-16/23_series/23271/88b0f3f4393228e9ea4d6542aef7c399_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4d87aa8057fb92d7f1c0546a17b0b118b6a95887a7a33452bd6eaf8dffb0c81 +size 57773 diff --git a/marked/Rel-16/23_series/23271/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/Rel-16/23_series/23271/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c984f3712946604a7747432a2094776ee4de4961 --- /dev/null +++ b/marked/Rel-16/23_series/23271/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba7942e9bb82fd73ee019456c181d89672a22423852b67a39efea59c87c3c155 +size 76239 diff --git a/marked/Rel-16/23_series/23271/97b3ed12d7f6c65cf3f7187326728409_img.jpg b/marked/Rel-16/23_series/23271/97b3ed12d7f6c65cf3f7187326728409_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83c0cf29bb20503975c1a4113de01904ecc62035 --- /dev/null +++ b/marked/Rel-16/23_series/23271/97b3ed12d7f6c65cf3f7187326728409_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1d716c790af63c36a8ada6a063858de7ee350a9b678a8c420829ee22d448f5b5 +size 104539 diff --git a/marked/Rel-16/23_series/23271/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/marked/Rel-16/23_series/23271/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fa8af291a138f9da18c0756f566723e67c25ccc2 --- /dev/null +++ b/marked/Rel-16/23_series/23271/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df37a97c9b9554f51c8dab8a9e67a04919ef95df69457fdb82dd6b9cf3acd729 +size 55281 diff --git a/marked/Rel-16/23_series/23271/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/marked/Rel-16/23_series/23271/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a88781ced558888e5e9b989cf4f1828bc0ec310f --- /dev/null +++ b/marked/Rel-16/23_series/23271/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1ac238f371a6c064229f27e6e57ff20f2d163c03a53c2d8cb19b5de14de71e57 +size 75366 diff --git a/marked/Rel-16/23_series/23271/9e9104f9ba7eec1259a7893c6380ca1b_img.jpg b/marked/Rel-16/23_series/23271/9e9104f9ba7eec1259a7893c6380ca1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..60d247ad480b9260579c28894ed4609b4c7f60c5 --- /dev/null +++ b/marked/Rel-16/23_series/23271/9e9104f9ba7eec1259a7893c6380ca1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4221f40760b9b1c75048d0063c96947d4a92d261d9bcd74bfae6edf68c9ba9d2 +size 52670 diff --git a/marked/Rel-16/23_series/23271/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23271/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0f5608f73d932ea2951922024f7b064b56d2b714 --- /dev/null +++ b/marked/Rel-16/23_series/23271/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b214d9532d20b189d6c82bc8050204aa27c79ee968641cd5960b64e56f19cf95 +size 76280 diff --git a/marked/Rel-16/23_series/23271/a0739aaf13fa5a632d4faa830f6b2708_img.jpg b/marked/Rel-16/23_series/23271/a0739aaf13fa5a632d4faa830f6b2708_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e5226f7d15dbef45c58d6440fd7cbc2d4ef368e5 --- /dev/null +++ b/marked/Rel-16/23_series/23271/a0739aaf13fa5a632d4faa830f6b2708_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aef7d8152fae44e5bf399cab23701b669541334988b9c99ab88d475a98b088e2 +size 80120 diff --git a/marked/Rel-16/23_series/23271/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/marked/Rel-16/23_series/23271/a0e8fe7862a6d7341faf5dac275277cc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..40b8bec251a2cb2e5b8b24fa8c4a9854ca21c0c8 --- /dev/null +++ b/marked/Rel-16/23_series/23271/a0e8fe7862a6d7341faf5dac275277cc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a47b29f824d5cd593105dd8fa610ee3a862759c3d9041ba5c486fc9b7764cb8e +size 156697 diff --git a/marked/Rel-16/23_series/23271/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23271/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67ffb8c587fe7d940ffb1fabf7d7dda1ea0c0c8e --- /dev/null +++ b/marked/Rel-16/23_series/23271/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61875355d3193d8b8d09a83af4e27c3b4c398c2ec6983b1a1e7b7ccff93532a5 +size 108824 diff --git a/marked/Rel-16/23_series/23271/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg b/marked/Rel-16/23_series/23271/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3ada031830c4bff1928a9bf74e6062e759c0fd28 --- /dev/null +++ b/marked/Rel-16/23_series/23271/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6e3930c390c51b3b43430f1f782347039d25546e072850c6a3939acd39098a4f +size 68414 diff --git a/marked/Rel-16/23_series/23271/a3f61f2e4a173b16257cd80e83d41d38_img.jpg b/marked/Rel-16/23_series/23271/a3f61f2e4a173b16257cd80e83d41d38_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8444d298c941350f74e4aba969f7eedd65ab7f9 --- /dev/null +++ b/marked/Rel-16/23_series/23271/a3f61f2e4a173b16257cd80e83d41d38_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2739f4b8b4df96cb7f308ff4057a16ebfc368ec4231eddd9bd90708b0f23a86 +size 49348 diff --git a/marked/Rel-16/23_series/23271/a634891d16b60b21df90a35c2af72c67_img.jpg b/marked/Rel-16/23_series/23271/a634891d16b60b21df90a35c2af72c67_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09e13f12230c6e85413d40788d22b63bcc080bf5 --- /dev/null +++ b/marked/Rel-16/23_series/23271/a634891d16b60b21df90a35c2af72c67_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c7dd3cdb2d7322922471e07d26cb91d73ac69cc64a786266d9b5efaa5b4a77c5 +size 44021 diff --git a/marked/Rel-16/23_series/23271/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Rel-16/23_series/23271/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..69815fdd14566f2cb0bc7f5fafa64b582ec0b8c3 --- /dev/null +++ b/marked/Rel-16/23_series/23271/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7b172100b124a1d31276d588d27dbf3979589e15b23afc245aa474a195763e4 +size 89005 diff --git a/marked/Rel-16/23_series/23271/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg b/marked/Rel-16/23_series/23271/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9be4eefff7650f2843fadf56d600d036b3118de6 --- /dev/null +++ b/marked/Rel-16/23_series/23271/b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fd5cb34c615b1649b1fec6fddc54ac3629e7c93ca205edd3cd7c6b4345c79a20 +size 66952 diff --git a/marked/Rel-16/23_series/23271/b904ac2472cab80892d1e783e6230d6e_img.jpg b/marked/Rel-16/23_series/23271/b904ac2472cab80892d1e783e6230d6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53db3b2c8834c8bc3f1014b62657d8314e0caf06 --- /dev/null +++ b/marked/Rel-16/23_series/23271/b904ac2472cab80892d1e783e6230d6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9a09a9794a5215e42c8c509d04b9d8694dff5a8862116a5a117116810b271a4c +size 76563 diff --git a/marked/Rel-16/23_series/23271/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-16/23_series/23271/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90d67a45818cbdc89e56fb665a9fc1b553f7f84c --- /dev/null +++ b/marked/Rel-16/23_series/23271/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72672b34438e8d6c08dcf9269072542e88765bb7ecb8ad6994f5dbf58d53271b +size 129792 diff --git a/marked/Rel-16/23_series/23271/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg b/marked/Rel-16/23_series/23271/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7182f5fb856bc336697041cc0cafeaca7f28d130 --- /dev/null +++ b/marked/Rel-16/23_series/23271/c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82caa85aa15b3110b75bc8ba5f81789ef9b1743745c1f89d298e886146efdcfb +size 98608 diff --git a/marked/Rel-16/23_series/23271/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg b/marked/Rel-16/23_series/23271/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..005960a561277caf9088a7c26059cd3fd891eeb1 --- /dev/null +++ b/marked/Rel-16/23_series/23271/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3a25baae2eaed016224ea8bfc1ba4a91c04433c65ad4a0c391c6f43926812a8a +size 29399 diff --git a/marked/Rel-16/23_series/23271/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/marked/Rel-16/23_series/23271/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83981c1def3f287b32467721be77ace1aeac57c1 --- /dev/null +++ b/marked/Rel-16/23_series/23271/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd5ba08f9849cdb5b0142484b6d9d4357698f3878b9ae1058a85a5e9cfe8c5fd +size 104382 diff --git a/marked/Rel-16/23_series/23271/d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg b/marked/Rel-16/23_series/23271/d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0dc77fc084f1f78c9b3cc764cb44cfac2da6819 --- /dev/null +++ b/marked/Rel-16/23_series/23271/d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6eb2253c74bc05dccb4fbc35ca05973228ccb3e26cf9301503f63d0e40269c4b +size 99322 diff --git a/marked/Rel-16/23_series/23271/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23271/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0ebd25cc8f832af71e6a9b4e1a19796e5fca259 --- /dev/null +++ b/marked/Rel-16/23_series/23271/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:296980a92e0a3c1e19f9ffbf246bda4ad27299c741c4ffa1ae0d1375c9721040 +size 75972 diff --git a/marked/Rel-16/23_series/23271/e05122559f56af5699789b7118d8fe87_img.jpg b/marked/Rel-16/23_series/23271/e05122559f56af5699789b7118d8fe87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6665d8ef00e96cd071293a45629559e30e367f9e --- /dev/null +++ b/marked/Rel-16/23_series/23271/e05122559f56af5699789b7118d8fe87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c6ae80bab8365753c5561bb664cc0dfce0d733243b608edf7a65bb3174cc4f85 +size 67256 diff --git a/marked/Rel-16/23_series/23271/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/marked/Rel-16/23_series/23271/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c143905f3bd55a4e65bea1885297fee80d249b2c --- /dev/null +++ b/marked/Rel-16/23_series/23271/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:efdb9454463bd38c4a34ffdf7715eb3668ae7b72ae33f401ba0c642cf1fe48e2 +size 119346 diff --git a/marked/Rel-16/23_series/23271/e417ae35ab07134888be901c201d54cd_img.jpg b/marked/Rel-16/23_series/23271/e417ae35ab07134888be901c201d54cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5dd08535b1042e3c8454dd7c899aa780c69c77e --- /dev/null +++ b/marked/Rel-16/23_series/23271/e417ae35ab07134888be901c201d54cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d7905a8f43f284123888c3b4e763cb892287354e10168c4d5ec21d708806c2b +size 93409 diff --git a/marked/Rel-16/23_series/23271/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/23_series/23271/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78c1cd451329b9ca829face3488b2bfec38e7a1b --- /dev/null +++ b/marked/Rel-16/23_series/23271/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3845982acd79f90856ff7457d218c88e14ae4d3bab4d59a2932999d0a82f41c +size 65408 diff --git a/marked/Rel-16/23_series/23271/raw.md b/marked/Rel-16/23_series/23271/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..d7c014fc52294c07c183f0542de5e967725f508a --- /dev/null +++ b/marked/Rel-16/23_series/23271/raw.md @@ -0,0 +1,6048 @@ +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Functional stage 2 description of Location Services (LCS) (Release 16)** --- + +## --- **Keywords** + +--- + +LTE, UMTS, location, stage 2 + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + +--- + + + +## --- **Copyright Notification** + +--- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------|----| +| Foreword ..... | 9 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions, symbols and abbreviations ..... | 12 | +| 3.1 Definitions..... | 12 | +| 3.2 Symbols..... | 16 | +| 3.3 Abbreviations ..... | 16 | +| 4 Main concepts ..... | 20 | +| 4.1 Assumptions..... | 20 | +| 4.2 Location Services Categories..... | 21 | +| 4.3 Positioning methods ..... | 21 | +| 4.3.1 Standard LCS Methods in UTRAN..... | 21 | +| 4.3.2 Standard LCS Methods in GERAN..... | 22 | +| 4.3.3 Standard LCS Methods in E-UTRAN..... | 22 | +| 4.4 Types of Location Request..... | 22 | +| 4.4.1 Immediate Location Request..... | 22 | +| 4.4.2 Deferred Location Request..... | 22 | +| 4.4.2.1 Types of event..... | 22 | +| 4.5 Concurrent Location Requests ..... | 23 | +| 5 General LCS architecture..... | 24 | +| 5.1 LCS access interfaces..... | 24 | +| 5.2 LCS Functional diagram, high level functions..... | 25 | +| 5.3 LCS Client functional group ..... | 26 | +| 5.3.1 External Location Client Function (LCF) ..... | 26 | +| 5.4 LCS Server functional group..... | 26 | +| 5.4.1 Client handling component..... | 26 | +| 5.4.1.1 Location Client Control Function (LCCF) ..... | 26 | +| 5.4.1.2 Location Client Authorization Function (LCAF) ..... | 26 | +| 5.4.1.2.1 Access Subfunction ..... | 26 | +| 5.4.1.2.2 Subscription Subfunction ..... | 27 | +| 5.4.1.3 Location Client Co-ordinate Transformation Function (LCCTF) ..... | 27 | +| 5.4.1.4 Location Client Zone Transformation Function (LCZTF) ..... | 27 | +| 5.4.2 System handling component..... | 27 | +| 5.4.2.1 Location System Control Function(LSCF)..... | 27 | +| 5.4.2.2 Location System Billing Function (LSBF)..... | 28 | +| 5.4.2.3 Location System Operations Function (LSOF) ..... | 28 | +| 5.4.2.4 Location System Broadcast Function (LSBcF) ..... | 28 | +| 5.4.2.5 Location System Co-ordinate Transformation Function (LSCTF)..... | 28 | +| 5.4.2.6 Location IMS – Interworking Function (LIMS-IWF) ..... | 28 | +| 5.4.3 Subscriber handling Component ..... | 28 | +| 5.4.3.1 Location Subscriber Authorization Function (LSAF) ..... | 28 | +| 5.4.3.2 Location Subscriber Translation Function (LSTF)..... | 28 | +| 5.4.3.3 Location Subscriber Privacy Function (LSPF) ..... | 28 | +| 5.4.4 Positioning components..... | 28 | +| 5.5 Information Flows between Client and Server..... | 29 | +| 5.5.1 Location Service Request..... | 29 | +| 5.5.2 Location Service Response..... | 30 | +| 5.6 Information Flows between LCS Servers ..... | 31 | +| 5.6.1 Location Service Request..... | 31 | +| 5.6.2 Location Service Response..... | 33 | +| 5.7 Optimized Lgd Procedure ..... | 34 | +| 6 LCS Architecture ..... | 34 | +| 6.0 Introduction ..... | 34 | + +| | | | +|---------|-------------------------------------------------------------------------------------------|----| +| 6.1 | Schematic functional description of LCS operations ..... | 37 | +| 6.2 | Allocation of LCS functions to network elements ..... | 38 | +| 6.3 | Functional description of LCS per network element ..... | 41 | +| 6.3.1 | Access Network..... | 41 | +| 6.3.2 | LCS Clients, LCS applications and Requestors ..... | 42 | +| 6.3.3 | Gateway Mobile Location Centre, GMLC ..... | 42 | +| 6.3.3A | Location Retrieval Function, LRF ..... | 43 | +| 6.3.4 | LCS support in the UE ..... | 43 | +| 6.3.5 | MSC/VLR..... | 43 | +| 6.3.6 | MSC Server ..... | 43 | +| 6.3.7 | SGSN ..... | 44 | +| 6.3.8 | Home Location Register, HLR..... | 44 | +| 6.3.9 | HSS..... | 44 | +| 6.3.10 | gsmSCF ..... | 44 | +| 6.3.11 | Privacy Profile Register, PPR..... | 44 | +| 6.3.12 | Pseudonym Mediation Device, PMD ..... | 44 | +| 6.3.13 | Mobility Management Entity, MME..... | 44 | +| 6.3.14 | Evolved Serving Mobile Location Centre, E-SMLC ..... | 45 | +| 6.4 | Addressing the target UE for LCS purposes ..... | 45 | +| 6.4.1 | Verinym for the target UE ..... | 45 | +| 6.4.2 | Pseudonyms for the target UE ..... | 45 | +| 6.4.3 | Non-dialable callback numbers ..... | 45 | +| 6.5 | Quality of Service Information ..... | 45 | +| 6.5.1 | LCS QoS Class ..... | 46 | +| 6.5.1.1 | Best Effort Class ..... | 46 | +| 6.5.1.2 | Assured Class..... | 46 | +| 7 | Signalling and Interfaces..... | 46 | +| 7.1 | LCS signalling between Access and Core Networks for GERAN and UTRAN access networks ..... | 46 | +| 7.1.1 | Core network Location Request ..... | 46 | +| 7.1.2 | Location Report ..... | 46 | +| 7.1a | LCS signalling between Access and Core Networks for E-UTRAN access networks ..... | 47 | +| 7.1a.1 | Core network Measurement Request..... | 47 | +| 7.1a.2 | Location Measurement Report ..... | 47 | +| 7.2 | Um, Uu and Uu-LTE Interfaces ..... | 47 | +| 7.3 | MAP Interfaces ..... | 48 | +| 7.4 | Lpp interface ..... | 48 | +| 7.4.1 | LCS Authorisation Request..... | 48 | +| 7.4.2 | LCS Authorisation Response ..... | 49 | +| 7.4.3 | LCS Privacy Profile Update notification..... | 50 | +| 7.4.4 | LCS Privacy Profile Update notification ack ..... | 50 | +| 7.5 | Lid interface ..... | 50 | +| 7.5.1 | LCS Identity Request ..... | 50 | +| 7.5.2 | LCS Identity Response ..... | 50 | +| 7.6 | IMS related Interfaces ..... | 50 | +| 7.6.1 | Dh Interface ..... | 50 | +| 7.6.2 | Sh Interface ..... | 51 | +| 7.6.3 | MI Interface ..... | 51 | +| 7.7 | SLg Interface ..... | 51 | +| 7.8 | SLs Interface ..... | 51 | +| 7.9 | SLh Interface ..... | 51 | +| 7.10 | SLm Interface ..... | 51 | +| 7.11 | Lgd Interface ..... | 51 | +| 8 | General network location procedures ..... | 51 | +| 8.1 | State description for GMLC ..... | 51 | +| 8.1.1 | GMLC states..... | 51 | +| 8.1.1.1 | NULL State ..... | 51 | +| 8.1.1.2 | INTERROGATION State ..... | 52 | +| 8.1.1.3 | LOCATION State ..... | 52 | +| 8.1.2 | State functionality..... | 52 | +| 8.1.2.1 | State Transitions ..... | 52 | + +| | | | +|-----------|---------------------------------------------------------------------------------------------|----| +| 8.1.2.2 | INTERROGATION Timer Function..... | 53 | +| 8.1.2.3 | LOCATION Timer Function..... | 53 | +| 8.2 | State description for VMSC and MSC Server ..... | 53 | +| 8.2.1 | VMSC and MSC Server States..... | 53 | +| 8.2.1.1 | LCS IDLE State ..... | 53 | +| 8.2.1.2 | LOCATION State ..... | 53 | +| 8.2.2 | State Functionality ..... | 53 | +| 8.2.2.1 | State Transitions ..... | 53 | +| 8.2.2.2 | LOCATION Timer Function..... | 54 | +| 8.3 | LCS State description for SGSN ..... | 54 | +| 8.3.1 | SGSN States ..... | 54 | +| 8.3.1.1 | LCS IDLE State ..... | 54 | +| 8.3.1.2 | LOCATION State ..... | 54 | +| 8.3.2 | State Functionality ..... | 54 | +| 8.3.2.1 | State Transitions ..... | 54 | +| 8.3.2.2 | LOCATION Timer Function..... | 55 | +| 8.4 | Signalling connection for the Iu interface ..... | 55 | +| 8.5 | Signalling connection for the A-interface ..... | 55 | +| 8.6 | Gb interface mapping of target UE ..... | 55 | +| 8.7 | LCS State description for MME..... | 55 | +| 8.7.1 | MME States ..... | 55 | +| 8.7.1.1 | LCS IDLE State ..... | 55 | +| 8.7.1.2 | LOCATION State ..... | 55 | +| 8.7.2 | State Functionality ..... | 56 | +| 8.7.2.1 | State Transitions ..... | 56 | +| 8.7.2.2 | LOCATION Timer Function..... | 56 | +| 8.8 | Signalling connection for the S1 interface ..... | 56 | +| 9 | General Network Positioning Procedures ..... | 56 | +| 9.1 | Mobile Terminating Location Request ..... | 57 | +| 9.1.1 | Common MT-LR procedure in PS and CS domain..... | 58 | +| 9.1.1A | Common MT-LR procedure in PS and CS domain for Emergency MT-LR ..... | 62 | +| 9.1.1.1 | LCS Authorisation request..... | 64 | +| 9.1.1.2 | LCS Privacy Profile Update ..... | 65 | +| 9.1.1.3 | LCS identity request ..... | 65 | +| 9.1.2 | Circuit Switched Mobile Terminating Location Request (CS-MT-LR) ..... | 66 | +| 9.1.2.1 | Location Preparation Procedure..... | 67 | +| 9.1.2.2 | Positioning Measurement Establishment Procedure..... | 68 | +| 9.1.2.3 | Location Calculation and Release Procedure ..... | 68 | +| 9.1.3 | CS-MT-LR without HLR Query ..... | 68 | +| 9.1.4 | CS-MT-LR and PS-MT-LR for a previously obtained location estimate ..... | 69 | +| 9.1.4.1 | Initial Location..... | 70 | +| 9.1.4.2 | Current Location ..... | 70 | +| 9.1.4.3 | Last known Location ..... | 70 | +| 9.1.4.4 | Security and Privacy ..... | 70 | +| 9.1.4.5 | Failing to locate the target UE ..... | 70 | +| 9.1.4.5.1 | Target UE is "Not Reachable" ..... | 70 | +| 9.1.4.5.2 | Target UE is "Detached" ..... | 71 | +| 9.1.4.5.3 | Target UE is Reachable but Positioning Fails..... | 71 | +| 9.1.4.5.4 | MSC Server or SGSN Target UE is "Purged" ..... | 71 | +| 9.1.5 | Network Induced Location Request (NI-LR)..... | 72 | +| 9.1.5.1 | Location Preparation Procedure..... | 72 | +| 9.1.5.2 | Positioning Measurement Establishment Procedure..... | 73 | +| 9.1.5.3 | Location Calculation and Release Procedure ..... | 73 | +| 9.1.5A | NI-LR using Location Based Routing – applicable to North American Emergency Calls only..... | 74 | +| 9.1.5A.1 | Location Preparation Procedure..... | 75 | +| 9.1.5A.2 | Positioning Measurement Establishment Procedure..... | 75 | +| 9.1.5A.3 | Location Calculation and Release Procedure ..... | 75 | +| 9.1.5A.4 | Location Preparation Procedure..... | 75 | +| 9.1.5A.5 | Positioning Measurement Establishment Procedure..... | 76 | +| 9.1.5A.6 | Location Calculation and Release Procedure ..... | 76 | +| 9.1.6 | Packet Switched Mobile Terminating Location Request (PS-MT-LR) ..... | 76 | + +| | | | +|----------|-------------------------------------------------------------------------------------------------|-----| +| 9.1.6.1 | Location Preparation Procedure..... | 77 | +| 9.1.6.2 | Positioning Measurement Establishment Procedure..... | 78 | +| 9.1.6.3 | Location Calculation and Release Procedure ..... | 79 | +| 9.1.6A | PS-MT-LR without HLR Query..... | 79 | +| 9.1.7 | Packet Switched Network Induced Location Request (PS-NI-LR)..... | 80 | +| 9.1.7.1 | Positioning Measurement Establishment Procedure..... | 81 | +| 9.1.7.2 | Location Calculation and Release Procedure ..... | 81 | +| 9.1.8 | Mobile Terminating Deferred Location Request – UE available event..... | 82 | +| 9.1.8.1 | Deferred Location Request Procedure..... | 82 | +| 9.1.8.2 | Location Report Procedure ..... | 83 | +| 9.1.8.3 | Combined Periodical/Deferred Mobile Terminating Location Request with UE available event ..... | 84 | +| 9.1.8.4 | Cancellation of a Deferred Location Request – UE available event ..... | 87 | +| 9.1.9 | Deferred Location Request Procedure for the change of area event ..... | 88 | +| 9.1.9.1 | Cancellation of a Deferred Location Request – Change of Area event..... | 91 | +| 9.1.10 | Circuit Switched Post Positioning Notification and Verification Procedure ..... | 92 | +| 9.1.11 | Packet Switched Post Positioning Notification and Verification Procedure ..... | 95 | +| 9.1.12 | Deferred Location Request Procedure for the Periodic Location Event ..... | 96 | +| 9.1.12.1 | Instigation of an MT-LR Request for Periodic Location..... | 96 | +| 9.1.12.2 | Reporting of Periodic Location..... | 98 | +| 9.1.12.3 | LCS Client cancellation of a Deferred Location Request – Periodic Location Event..... | 101 | +| 9.1.12.4 | UE cancellation of a Deferred Location Request – Periodic Location Event..... | 103 | +| 9.1.13 | IW-MT-LR Procedure ..... | 105 | +| 9.1.14 | IW-MT-LR Procedure without HLR/HSS or AAA Query ..... | 106 | +| 9.1.15 | EPC Mobile Terminating Location Request (EPC-MT-LR)..... | 108 | +| 9.1.15.1 | Location Preparation Procedure..... | 108 | +| 9.1.15.2 | Positioning Measurement Establishment Procedure..... | 110 | +| 9.1.15.3 | Location Calculation and Release Procedure ..... | 110 | +| 9.1.16 | EPC-MT-LR without HLR Query..... | 111 | +| 9.1.17 | EPC Network Induced Location Request (EPC-NI-LR)..... | 112 | +| 9.1.17.1 | Positioning Measurement Establishment Procedure..... | 112 | +| 9.1.17.2 | Location Calculation and Release Procedure ..... | 113 | +| 9.1.18 | EPC Post Positioning Notification and Verification Procedure ..... | 113 | +| 9.1.19 | Deferred EPC-MT-LR for Periodic and Triggered Location ..... | 115 | +| 9.1.19.1 | Instigation and Reporting of Periodic and Triggered Location ..... | 115 | +| 9.1.19.2 | LCS Client cancellation of a Deferred Location Request for Periodic and Triggered Location..... | 119 | +| 9.1.19.3 | UE cancellation of a Deferred Location Request for Periodic and Triggered Location..... | 120 | +| 9.2 | Mobile Originating Location Request..... | 122 | +| 9.2.1 | Mobile Originating Location Request, Circuit Switched (CS-MO-LR) ..... | 122 | +| 9.2.1.1 | Location Preparation Procedure..... | 122 | +| 9.2.1.2 | Positioning Measurement Establishment Procedure..... | 123 | +| 9.2.1.3 | Location Calculation and Release Procedure ..... | 123 | +| 9.2.2 | Mobile Originating Location Request, Packet Switched (PS-MO-LR) ..... | 125 | +| 9.2.2.1 | Location Preparation Procedure..... | 125 | +| 9.2.2.2 | Positioning Measurement Establishment Procedure..... | 126 | +| 9.2.2.3 | Location Calculation and Release Procedure ..... | 126 | +| 9.2.3 | MO-LR Request for Periodic Location Transfer to a Third Party ..... | 127 | +| 9.2.4 | MO-LR Request for Periodic Self Location..... | 129 | +| 9.2.5 | WLAN UE Originated Procedure in I-WLAN..... | 131 | +| 9.2.6 | Mobile Originating Location Request, EPC (EPC-MO-LR) ..... | 132 | +| 9.2.6.1 | Location Preparation Procedure..... | 132 | +| 9.2.6.2 | Positioning Measurement Establishment Procedure..... | 133 | +| 9.2.6.3 | Location Calculation and Release Procedure ..... | 133 | +| 9.3 | LCS signalling procedures specified in UTRAN and GERAN Stage 2 ..... | 134 | +| 9.3a | LCS signalling procedures applicable to E-UTRAN..... | 134 | +| 9.3a.1 | UE Assisted and UE Based Positioning and Assistance Delivery ..... | 134 | +| 9.3a.2 | Network Assisted and Network Based Positioning Procedure..... | 135 | +| 9.3a.3 | Obtaining Non-UE Associated Network Assistance Data ..... | 137 | +| 9.3a.4 | Broadcasting Network Assistance Data ..... | 137 | +| 9.3a.5 | Delivery of Ciphering Keys to UEs for Broadcast Assistance Data ..... | 138 | +| 9.4 | Exception Procedures..... | 140 | +| 9.4.1 | Procedures in the VMSC /MSC server..... | 140 | +| 9.4.2 | Void ..... | 141 | + +| | | | +|-----------|-------------------------------------------------------------------------------|-----| +| 9.4.3 | Procedures in the SGSN ..... | 141 | +| 9.4.3a | Procedures in the MME..... | 141 | +| 9.4.4 | Void..... | 142 | +| 9.4.5 | Handover handling ..... | 142 | +| 9.4.5.1 | VMSC /MSC server procedure for Inter-VMSC /MSC server Handover..... | 142 | +| 9.4.5.2 | Handling of an ongoing handover while a request for positioning arrives..... | 142 | +| 9.4.5.3 | Handover handling in Iu mode ..... | 142 | +| 9.4.5.4 | Handover of an IMS Emergency Call with EPS/GPRS/WLAN Access ..... | 142 | +| 9.4.5.4.1 | Common Requirements..... | 142 | +| 9.4.5.4.2 | Location Continuity for Handover between 3GPP and 3GPP2 Access Types ..... | 147 | +| 9.4.5.4.3 | Location Continuity for E-UTRAN Handover to WLAN ..... | 150 | +| 9.4.5.4.4 | Location Continuity for WLAN Handover to E-UTRAN, UTRAN or GERAN..... | 151 | +| 9.5 | Privacy..... | 152 | +| 9.5.1 | Privacy Override Indicator (POI) ..... | 152 | +| 9.5.2 | Privacy Procedures ..... | 152 | +| 9.5.3 | UE Privacy Options ..... | 153 | +| 9.5.3.1 | Universal class ..... | 153 | +| 9.5.3.2 | Call/Session related class..... | 154 | +| 9.5.3.2.1 | Call/session-related class in the CS-domain ..... | 154 | +| 9.5.3.2.2 | Call/session-related class in the PS-domain..... | 155 | +| 9.5.3.2.3 | Call/session-related class when LCS client not in SLPP ..... | 155 | +| 9.5.3.3 | Call/Session-unrelated class ..... | 155 | +| 9.5.3.3.1 | Call/session-unrelated class when LCS client identities match ..... | 156 | +| 9.5.3.3.2 | Call/session-unrelated class when LCS client identities do not match ..... | 156 | +| 9.5.3.4 | PLMN operator class ..... | 156 | +| 9.5.3.5 | Service type checking ..... | 157 | +| 9.5.3.6 | Matching of LCS client identities..... | 157 | +| 9.5.4 | Indicator of privacy check related action ..... | 157 | +| 9.6 | Mobile Originating Location..... | 158 | +| 9.7 | CM Procedures..... | 158 | +| 9.7.1 | Location request for a mobile in idle-mode..... | 158 | +| 9.7.2 | Location request for a mobile in dedicated-mode ..... | 158 | +| 9.8 | Interworking with the IMS ..... | 158 | +| 9.8.1 | Standard Location Request using a SIP-URI ..... | 158 | +| 9.8.2 | Standard Location Request using a TEL-URL..... | 160 | +| 9.8.3 | Mobile Originated Location Requests in the IMS..... | 160 | +| 9.8.4 | IMS Emergency Location Procedure ..... | 160 | +| 10 | Information storage..... | 161 | +| 10.1 | HLR and HSS..... | 161 | +| 10.1.1 | LCS Data in the HLR/HSS for an UE Subscriber ..... | 161 | +| 10.2 | VLR/SGSN..... | 164 | +| 10.2a | MME ..... | 164 | +| 10.3 | GMLC ..... | 164 | +| 10.3.1 | LCS Data in the GMLC for a LCS Client ..... | 164 | +| 10.3.2 | LCS Data in the GMLC/PPR for a UE Subscriber..... | 167 | +| 10.4 | Recovery and Restoration Procedures..... | 170 | +| 10.5 | Interworking between network nodes in different releases..... | 170 | +| 10.5.1 | LCS capability set..... | 170 | +| 10.5.2 | Interworking between pre Rel-4 serving node and Rel-4 or later HLR/HSS..... | 171 | +| 10.5.3 | Interworking between pre Rel-5 serving node and Rel-5 or later HLR/HSS..... | 171 | +| 10.5.4 | Interworking between pre Rel-6 network nodes and Rel-6 or later HLR/HSS ..... | 171 | +| 10.5.4.1 | Rel-6 or later HLR/HSS with pre Rel-6 serving node ..... | 171 | +| 10.6 | LIMS-IWF..... | 171 | +| 11 | Operational Aspects ..... | 171 | +| 11.1 | Charging..... | 171 | +| 11.2 | Charging Information Collected by the Visited PLMN ..... | 172 | + +| | | +|---------------------------------------------------------------------------------------------|------------| +| Annex A (normative): Privacy Class selection rule in serving node..... | 173 | +| A.1 Interrelation among privacy settings..... | 173 | +| A.2 Privacy class selection rule for pre Rel-6 mechanism ..... | 173 | +| A.3 Privacy related action selection rule for Rel-6 and later..... | 174 | +| Annex B (normative): Presence of LCS client ID Components in MT-LR ..... | 176 | +| Annex C (Informative): Pseudo external ID..... | 177 | +| Annex D (normative): including Requestor identity to LCS client name..... | 181 | +| Annex E (Informative): Handling of pseudonyms in location services ..... | 182 | +| Annex F (Informative): Mechanism for performing Change of Area Event Detection ..... | 185 | +| F.1 (U)SIM Application Toolkit (USAT) Based Solution..... | 185 | +| Annex G (normative): Defined Service Types and numbering..... | 187 | +| Annex H (informative): Change history..... | 188 | + +--- + +## Foreword + +This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +--- + +# 1 Scope + +The present document specifies the stage 2 of the LoCation Services (LCS) feature in UMTS, GSM and EPS (for E-UTRAN), which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers. + +Location Services in 5GC are restricted to regulatory services and are specified in TS 23.501 [54] and TS 23.502 [55] in this release of the specification. The architecture and signalling procedures in NG-RAN are defined in TS 38.305 [56]. + +The present document replaces the specifications TS 23.171 (Release 1999) and the system and core network parts of GSM 03.71 (Release 1999). TS 43.059 [16] replaces the radio access network parts of GSM 03.71 (Release 1999). + +Location Services may be considered as a network provided enabling technology consisting of standardised service capabilities, which enable the provision of location applications. The application(s) may be service provider specific. The description of the numerous and varied possible location applications which are enabled by this technology are outside the scope of the present document. However, clarifying examples of how the functionality being described may be used to provide specific location services may be included. + +This stage 2 service description covers the LCS system functional model for the whole system, the LCS system architecture, state descriptions, message flows, etc. + +--- + +# 2 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 25.305: "Stage 2 functional specification of UE positioning in UTRAN". +- [2] (void). +- [3] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". +- [4] 3GPP TS 22.071: "Technical Specification Group Systems Aspects; Location Services (LCS); Stage 1". +- [5] (void). +- [6] (void). +- [7] (void). +- [8] 3GPP TS 22.101: "Service principles". +- [9] (void). +- [10] (void). +- [11] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)". +- [12] (void). +- [13] (void). + +- [14] 3GPP TS 25.413: "UTRAN Iu Interface RANAP signalling". +- [15] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [16] 3GPP TS 43.059: "Functional Stage 2 description of Location Services in GERAN". +- [17] 3GPP TS 23.003: "Numbering, addressing and identification". +- [18] 3GPP TS 29.002: "Mobile Application Part (MAP) Specification". +- [19] (void). +- [20] 3GPP TS 23.002: "Network architecture". +- [21] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) - stage 2". +- [22] 3GPP TS 23.011: "Technical realization of Supplementary Services". +- [23] 3GPP TS 23.007: "Restoration procedures". +- [24] 3GPP TS 24.008: "Mobile Radio Interface - Layer 3 MM/CC Specification". +- [25] 3GPP TS 25.331: "RRC protocol specification". +- [26] 3GPP TS 23.127: "Virtual Home Environment/Open Service Access". +- [27] 3GPP TS 29.198-1: "Open Service Access (OSA); Application Programming Interface (API); Part 1; Overview". +- [28] 3GPP TS 29.198-2: "Open Service Access (OSA); Application Programming Interface (API); Part 2; Common Data". +- [29] 3GPP TS 29.198-3: "Open Service Access (OSA); Application Programming Interface (API); Part 3; Framework". +- [30] 3GPP TS 29.198-6: "Open Service Access (OSA); Application Programming Interface (API); Part 6: Mobility". +- [31] OMA MLP TS: "Mobile Location Protocol", []. +- [32] ANSI J-STD-036B: "Enhanced Wireless 9-1-1 Phase 2". +- [33] RFC 2396: "Uniform Resource Identifiers". +- [34] RFC 3261: "SIP: Session Initiation Protocol". +- [35] 3GPP TS 23.228: "IP multimedia subsystem (IMS)". +- [35a] ITU Recommendation E.164: "The international public telecommunication numbering plan". +- [35b] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service Description, Stage 1". +- [36] OMA RLP TS: "Roaming Location Protocol", []. +- [36a] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions". +- [37] 3GPP TS 31.111: "Universal Subscriber Identity Module (USIM) Application Toolkit (USAT)". +- [38] Open Mobile Alliance, OMA AD SUPL: "Secure User Plane Location Architecture", (). +- [39] Open Mobile Alliance, OMA TS ULP: "User Plane Location Protocol", (). +- [40] IETF RFC 4119: "A Presence-based GEOPRIV Location Object Format". + +- [41] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [42] 3GPP TS 36.305: "Stage 2 functional specification of UE positioning in E-UTRAN". +- [43] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2". +- [44] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses". +- [45] 3GPP TS 29.173: "Location Services (LCS); Diameter-based SLh interface for Control Plane LCS". +- [46] 3GPP TS 29.171: "LCS Application Protocol (LCS-AP) between MME and E-SMLC; SLs Interface". +- [47] 3GPP TS 36.355: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol (LPP)". +- [48] 3GPP TS 36.455: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE Positioning Protocol Annex (LPPa)". +- [49] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (SIAP)". +- [50] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall Description; Stage 2". +- [51] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol". +- [52] 3GPP TS 23.234: "3GPP system to Wireless Local Area Network (WLAN) interworking". +- [53] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2". +- [54] 3GPP TS 23.501: " System Architecture for the 5G System; Stage 2". +- [55] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2". +- [56] 3GPP TS 38.305: "Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the following terms and definitions apply: + +**CAMEL:** CAMEL is a network functionality, which provides the mechanisms of Intelligent Network to a mobile user. + +**Call Related:** any LCS related operation which is associated with an established call in CS domain and a session via an active PDP context in PS domain. + +**Codeword:** access code, which is used by a Requestor or LCS Client in order to gain acceptance of a location request for a Target UE. The codeword is part of the privacy information that may be registered by a Target UE user. + +**Current Location:** after a location attempt has successfully delivered a location estimate and its associated time stamp, the location estimate and time stamp is referred to as the "current location" at that point in time. + +**Deferred location request:** location request where the location response (responses) is (are) required after a specific event has occurred. The event may or may not occur immediately. + +**Global Navigation Satellite System:** Global Navigation Satellite System (GNSS) consists of three functional elements: Space Segment (satellites), User Segment (receivers), and Control Segment (maintenance etc.). The GNSS receiver + +calculates its own position based on the received time differences for several satellites. GNSS include Global Positioning System (GPS) and GALILEO. + +**Immediate location request:** location request where a single location response only is required immediately + +**Initial Location:** in the context of an originating emergency call the location estimate and the associated time stamp at the commencement of the call set-up is referred to as "initial location". + +**Last Known Location:** current location estimate and its associated time stamp for Target UE stored in the LCS Server is referred to as the "last known location" and until replaced by a later location estimate and a new time stamp is referred to as the "last known location". + +**LCS (LoCation Services):** LCS is a service concept in system (e.g. GSM or UMTS) standardization. LCS specifies all the necessary network elements and entities, their functionalities, interfaces, as well as communication messages, due to implement the positioning functionality in a cellular network. Note that LCS does not specify any location based (value added) services except locating of emergency calls. + +**LCS Client:** software and/or hardware entity that interacts with a LCS Server for the purpose of obtaining location information for one or more Mobile Stations. LCS Clients subscribe to LCS in order to obtain location information. LCS Clients may or may not interact with human users. The LCS Client is responsible for formatting and presenting data and managing the user interface (dialogue). The LCS Client may reside in the Mobile Station (UE). + +**LCS Client Access barring list:** optional list of MSISDNs per LCS Client where the LCS Client is not allowed to locate any MSISDN therein. + +**LCS Client Subscription Profile:** collection of subscription attributes of LCS related parameters that have been agreed for a contractual period of time between the LCS client and the service provider. + +**LCS Feature:** capability of a PLMN to support LCS Client/server interactions for locating Target UEs. + +**LCS QoS Class:** The QoS class determines the degree of adherence to the quality of service information as required by the source of a location request. + +**LCS Server:** software and/or hardware entity offering LCS capabilities. The LCS Server accepts requests, services requests, and sends back responses to the received requests. The LCS server consists of LCS components, which are distributed to one or more PLMN and/or service provider. + +**LDR reference number:** the identity which is assigned and maintained by the H-GMLC and circulated between the LCS Client, R-GMLC, H-GMLC, V-GMLC, MSC/SGSN and UE. With the identity of the UE, the LDR reference number can unique identify a Location Deferred Request. Notes: UE is involved only when the event type of the deferred request is "change of area" or "periodic location". In addition, in a Periodical Immediate/deferred LCS Service Request, the LDR reference number is exclusive. + +**Linear Distance Threshold:** a straight line distance used for a deferred location request for the motion event. The linear distance threshold is defined by the LCS client and triggers a motion event when a UE moves by more than this distance from a previous location. The linear distance threshold is equivalent to a change of area event for leaving an area where the area is a circle with the linear distance threshold as a radius and centred on the previous location. + +**Local Information:** information related to a given location, or general information, which is made available in a given location. + +**Local Service:** service, which can be exclusively provided in the current serving network by a Value added Service Provider. + +**Location (Based) Application:** location application is an application software processing location information or utilizing it in some way. The location information can be input by a user or detected by network or UE. Navigation is one location application example. + +**Location Based Service (LBS):** service provided either by teleoperator or a 3rd party service provider that utilizes the available location information of the terminal. Location Application offers the User Interface for the service. LBS is either a pull or a push type of service (see Location Dependent Services and Location Independent Services). In ETSI/GSM documentation of SoLSA, LBS is called "Location Related Service". ETSI and/or 3GPP -wide terminology harmonization is expected here. + +**Location Dependent Service:** service provided either by teleoperator or a 3rd party service provider that is available (pull type) or is activated (push type) when the user arrives to a certain area. It doesn't require any subscription in advance, but the push type activation shall be confirmed by the user. The offered service itself can be any kind of service (e.g. a public Xerox machine or the discount list in a store). + +**Location Estimate:** geographic location of an UE and/or a valid Mobile Equipment (ME), expressed in latitude and longitude data. The Location Estimate shall be represented in a well-defined universal format. Translation from this universal format to another geographic location system may be supported, although the details are considered outside the scope of the primitive services. The location estimate may include the velocity of the UE. + +**Location Identifier:** information about the current location of the UE in the network. Location is indicated in network terms, for example using the global cell id in cellular networks, line-id in fixed broadband networks, the (MAC) address of the WLAN AP or Location Object as defined by IETF RFC 4119 [40], (OMA-Location also uses this term, but OMA so far defines the Location Identifier only for cellular access). + +**Location Independent Service:** service provided either by teleoperator or a 3rd party service provider that is available and therefore can be activated anywhere in the network coverage. It is activated by the user's request or by other user's activated service, and therefore it requires a subscription in advance (pull type). The offered service itself can be any kind of service (e.g. MMS, SWDL, or LBS!). + +**Location Retrieval Function (LRF):** this functional entity handles the retrieval of location information for the UE including, where required, interim location information, initial location information and updated location information. The LRF may interact with a separate RDF or contain an integrated RDF in order to obtain routing information. The LRF may interact with a separate GMLC or contain an integrated GMLC in order to obtain location information. The LRF may interact with or contain other types of location server functions in order to obtain location information. + +**Maximum reporting time:** maximum allowed time between successive area/motion event reports. Expiration of the maximum reporting time triggers a report, the UE indicates expiration of the maximum reporting time as the trigger event. + +**Minimum reporting time:** minimum allowed time between successive area/motion event reports. The UE defers any event report if needed until minimum reporting time expires. + +**Mobile Assisted positioning:** any mobile centric positioning method (e.g. IPDL-OTDOA, E-OTD, GPS) in which the UE provides position measurements to the network for computation of a location estimate by the network. The network may provide assistance data to the UE to enable position measurements and/or improve measurement performance. + +**Mobile Based positioning:** any mobile centric positioning method (e.g. IPDL-OTDOA, E-OTD, GPS) in which the UE performs both position measurements and computation of a location estimate and where assistance data useful or essential to one or both of these functions is provided to the UE by the network. Position methods where an UE performs measurements and location computation without network assistance data are not considered within this category. + +**Mobile Station:** mobile station (MS) consists of Mobile or User Equipment (ME or UE) with a valid SIM or USIM attached. The abbreviation "UE" in this specification refers both to MS and User Equipment, see below. + +**MO-LR Short Circuit:** use of an MO-LR based procedure to provide a location estimate directly from the UE to the serving SGSN or MSC using a Mobile Based positioning method (e.g. GPS) according to the requested LCS QoS and that is not obtained or verified by the RAN. + +**Network-based positioning:** a positioning method (i.e. UTDOA) in which multiple network nodes (e.g. LMUs) perform position radio measurements based on UL transmissions from a mobile terminal to provide them to an E-SMLC for computation of a location estimate for the mobile terminal. + +**Non-dialable call back number:** In case of a SIM-less emergency call, or a non-registered (U)SIM emergency call, a non-dialable callback number shall be used to identify the target UE. The format and structure of the non-dialable callback number is according to national or regional regulations. + +**Non-registered (U)SIM emergency call:** The emergency call where the U(SIM) has not been authenticated and have not been registered in the VLR. Examples of such cases could be emergency call from a blocked (U)SIM due to mistyped PIN, or when the UE is in "enter PIN" mode, or the emergency call is performed in another network with no roaming agreement with the home PLMN. Any IMSI retrieved from such a (U)SIM cannot be trusted and so cannot be used to identify the calling party. + +**PLMN Access barring list:** optional list of MSISDN per PLMN where any LCS Client is not allowed to locate any MSISDN therein except for certain exceptional cases. + +**Positioning (/location detecting):** positioning is a functionality, which detects a geographical location and optionally, velocity (of e.g. a mobile terminal). + +**Positioning method (/locating method):** method or technical solution, which is used to get an estimate of the target mobile's geographical location. For example positioning methods based on radio cell coverage, GPS or Assisted GPS methods, which are based on the Time-Of-Arrival (TOA) algorithm, and UTDOA, OTDOA or E-OTD methods, which are based on the Time-Difference-Of-Arrival (TDOA) algorithm. The positioning methods are further described in E-UTRAN Stage 2, TS 36.305 [42], UTRAN Stage 2, TS 25.305 [1] and GERAN Stage 2, TS 43.059 [16]. + +**Predefined area:** geographical area, which is not related to cell or radio coverage. The mobile may take special action when it recognises it has entered or left a predefined area. + +**Privacy Class:** list of LCS Clients defined within a privacy exception class to which permission may be granted to locate the target UE. The permission shall be granted either on activation by the target UE or permanently for a contractual period of time agreed between the target UE and the service provider. + +**Privacy Exception List:** list consisting of various types of privacy classes (i.e. operator related, personal etc.). Certain types of classes may require agreement between the service provider and the target UE. + +**Privacy Profile Register, PPR:** The PPR stores privacy information of the target mobile. The PPR also executes privacy checks and sends the privacy check results to other network elements using the Lpp interface. PPR may be a standalone network entity or the PPR functionality may be integrated in H-GMLC. + +**Prohibited area:** area where the mobile must not activate its transmitter. The Prohibited area may be a Predefined area described above or related to radio cell(s). + +**Pseudo-external identity:** The pseudo-external identity is not the identity of real external LCS client but the identity, which is used for notifying the result of the enhanced privacy check. The pseudo-external identity shall keep the compatibility with pre Rel-6 privacy mechanisms, which does not understand privacy check result made by H-GMLC/PPR. Each operator defines its own the pseudo-external identities. + +**Pseudonym:** A fictitious identity, which may be used to conceal the true identity (i.e. MSISDN and IMSI) of a target UE from the requestor and the LCS client. + +**Pseudonym mediation device:** Functionality that verifies pseudonyms to verinymns. + +**Request id:** identity which is used to identify the correspondence of a location request to multiple responses when the Response method is ASYNC. Each receiving GMLC (R-GMLC or V-GMLC or H-GMLC) allocates and maintains the Request id to identify each ASYNC location request, and includes it in the responses to the source entity of the location request (i.e. LCS client or GMLC). + +**Requestor:** the originating entity which has requested the location of the target UE from the LCS client. + +**Requestor Identity:** This identifier is identifying the Requestor and can be e.g. MSISDN or logical name. + +**Response method:** method how a GMLC, which receives a location request message from another entity (i.e. LCS client or GMLC), responds to the location request. There are two methods, synchronous (SYNC) and asynchronous (ASYNC). When the requesting entity wishes multiple responses (either about one or several target UE's location) to a single location request the procedure is ASYNC and when the requesting entity wishes a single response the procedure is SYNC. The source entity of the location request (i.e. LCS client or GMLC) can choose a preferred method and informs the method to the receiving GMLC. However, the selection of the method used is made by the receiving GMLC and when the ASYNC method is selected the Request id is notified to the source entity. The receiving GMLC can turn a SYNC request into an ASYNC procedure, e.g. in an overload situation, and the source entity (i.e. LCS client or GMLC) should be able to receive multiple responses even though the request was SYNC. + +**Routing Determination Function (RDF):** The functional entity, which may be integrated in a Location Server (e.g. GMLC) or in an LRF, provides the proper PSAP destination address to the E-CSCF for routing the emergency request. It can interact with a location functional entity (e.g. GMLC) to manage ESQK allocation and management, and deliver location information to the PSAP. + +**Service Area Identifier (SAI):** information, which is used to identify an area consisting of one or more cells belonging to the same Location Area, see TS 25.413 [14]. Such an area is called a Service Area and can be used for indicating the + +location of a UE to the CN. For this specification, only a Service Area that is defined to be applicable to the PS and CS domains shall be used. + +**Service coverage:** a list of country codes where an LCS client offers its location services. Country code in this context means E.164 country code for a geographic area [35a]. + +**Service Type:** attribute of specific location based service provided by the LCS client, as defined in TS 22.071 [4]. + +**Serving cell identity:** the Cell Global Identification (CGI), see TS 23.003 [17], of the cell currently used by the target UE, e.g. for an emergency call in A-mode. + +**SIM-less emergency call:** The emergency call that is originated from a UE, which does not have a SIM or USIM. + +**Subscription Profile:** profile detailing the subscription to various types of privacy classes. + +**Target area:** geographical area which is used for change of area type deferred location request. The target area is defined by the LCS client and is expressed as geographical area using a shape defined in TS 23.032 [11], as a geographical area using local coordinate system, as an E.164 country code for a geographic area [35a], as a PLMN identity or as a geopolitical name of the area (e.g. London). + +**Target UE:** UE being positioned. + +**User Equipment:** term 'User Equipment', or 'UE', as defined in TR 21.905 [3]. UE in this specification may also refer to a Mobile Equipment or User Equipment used for emergency calls, that do not have valid SIM or USIM. + +**Velocity:** The speed of a UE and the direction in which it is travelling, encoded as defined in TS 23.032 [11]. Velocity may be defined as either 2-D (horizontal) velocity or 3-D (horizontal and vertical) velocity. Both 2-D and 3-D velocity may be reported either with or without uncertainty. + +**Verinym:** True identity, i.e. MSISDN or IMSI, of the target UE. + +Further UMTS related definitions are given in TS 22.101 [8]. + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|-----|----------------------------------------------------------------------------------------------| +| Dh | Interface between LIMS-IWF and SLF | +| Gb | Interface between 2G-SGSN and BSS | +| Gs | Interface between MSC and SGSN | +| La | Interface between GMLC and AAA | +| Lc | Interface between gateway MLC and gsmSCF (CAMEL interface) | +| Le | Interface between External User and MLC (external interface) | +| Lg | Interface between Gateway MLC - VMSC, GMLC - MSC Server, GMLC - SGSN (gateway MLC interface) | +| Lgd | Interface between GMLC and SGSN (Diameter based) | +| Lh | Interface between Gateway MLC and HLR (MAP based) | +| Lid | Interface between GMLC and PMD. | +| Lpp | Interface between GMLC(H-GMLC) and PPR entity. | +| Lr | Interface between Gateway MLCs | +| Ml | Interface between the E-CSCF and LRF | +| Sh | Interface between LIMS-IWF and HSS | +| SLg | Interface between GMLC and MME | +| SLh | Interface between GMLC and HSS (Diameter based) | +| SLs | Interface between MME and E-SMLC | +| Um | GERAN Air Interface | +| Uu | UTRAN Air Interface | + +## 3.3 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------------|----------------------------------------------------------| +| 2G- | Second Generation | +| 3G- | Third Generation | +| A-GNSS | Assisted Global Navigation Satellite System | +| AAA | Authentication, Authorization, Accounting | +| AC | Admission Control | +| AI | Application Interface (prefix to interface class method) | +| ANM | Answer Message (ISUP) | +| APN | Access Point Name | +| APN-NI | APN Network Identifier | +| ARIB | Association of Radio Industries and Business | +| ATD | Absolute Time Difference | +| BCCH | Broadcast Control Channel | +| BER | Bit Error Rate | +| BSSID | Basic Service Set Identifier | +| BSS | Base Station Subsystem | +| BTS | Base Transceiver Station | +| CAMEL | Customised Application For Mobile Network Enhanced Logic | +| CAP | CAMEL Application Part | +| CM | Connection Management | +| CN | Core Network | +| CSCF | Call Service Control Function | +| CSE | Camel Service Environment | +| DL | Downlink | +| DNS | Domain Name System | +| DRNC | Drift RNC | +| E-CSCF | Emergency CSCF | +| E-OTD | Enhanced Observed Time Difference | +| E-SLP | Emergency SUPL Location Platform | +| E-SMLC | Evolved Serving Mobile Location Centre | +| E-STN-DR | Emergency Session Transfer Number for DRVCC | +| FER | Frame Error Rate | +| GERAN | GSM EDGE Radio Access Network | +| GGSN | Gateway GPRS Support Node | +| GMLC | Gateway MLC | +| GNSS | Global Navigation Satellite System | +| GPRS | General Packet Radio Service | +| GPS | Global Positioning System | +| HE | Home Environment | +| H-GMLC | Home-GMLC | +| H-LIMS-IWF | Home-LIMS-IWF | +| HSS | Home Subscriber Server | +| HLR | Home Location Register | +| HPLMN | Home Public Land Mobile Network | +| IMEI | International Mobile Equipment Identity | +| IMS | IP Multimedia Subsystem | +| IMSI | International Mobile Subscriber Identity | +| IP | Internet Protocol | +| IPDL | Idle Period Downlink | +| IW-MT-LR | Mobile Terminated Location Request for an I-WLAN | +| I-WLAN | Interworking WLAN | +| LA | Location Application | +| LAF | Location Application Function | +| LBS | Location Based Services | +| LCAF | Location Client Authorization Function | +| LCCF | Location Client Control Function | +| LCCTF | Location Client Co-ordinate Transformation Function | +| LCF | Location Client Function | +| LCZTF | Location Client Zone Transformation Function | +| LCS | LoCation Services | +| LDR | Location Deferred Request | +| LIMS-IWF | Location IMS – Interworking Function | +| LIR | Location Immediate Request | + +| | | +|------------|------------------------------------------------------| +| LMU | Location Measurement Unit | +| LRF | Location Retrieval Function | +| LSAF | Location Subscriber Authorization Function | +| LSBcF | Location System Broadcast Function | +| LSBF | Location System Billing Function | +| LSCF | Location System Control Function | +| LSCTF | Location System Co-ordinate Transformation Function | +| LSOF | Location System Operation Function | +| LSPF | Location Subscriber Privacy Function | +| LSTF | Location Subscriber Translation Function | +| MAP | Mobile Application Part | +| ME | Mobile Equipment | +| MExE | Mobile Execution Environment | +| MGCF | Media Gateway Control Function | +| MLC | Mobile Location Centre | +| MLP | Mobile Location Protocol | +| MM | Mobility Management | +| MO-LR | Mobile Originated Location Request | +| MS | Mobile Station | +| MSC | Mobile services Switching Centre | +| MSISDN | Mobile Station Integrated Services Data Network | +| MT-LR | Mobile Terminated Location Request | +| NA-ESRD | North American Emergency Service Routing Digits | +| NA-ESRK | North American Emergency Service Routing Key | +| NI-LR | Network Induced Location Request | +| NPLI | Network Provided Location Information | +| OMA | Open Mobile Alliance | +| OSA | Open Service Architecture | +| OTDOA | Observed Time Difference Of Arrival | +| PC | Power Control | +| PCF | Power Calculation Function | +| PLMN | Public Land Mobile Network | +| PMD | Pseudonym mediation device functionality | +| POI | Privacy Override Indicator | +| PPR | Privacy Profile Register | +| PRCF | Positioning Radio Co-ordination Function | +| PRRM | Positioning Radio Resource Management | +| PSAP | Public Safety Answering Point | +| PSE | Personal Service Environment | +| PSM | Power Saving Mode | +| PSMF | Positioning Signal Measurement Function | +| PSTN | Public Switched Telephone Network | +| QoS | Quality of Service | +| RA | Routing Area | +| RACH | Random Access Channel | +| RAN | Radio Access Network | +| RANAP | Radio Access Network Application Part | +| R-GMLC | Requesting-GMLC | +| RDF | Routing Determination Function | +| RIS | Radio Interface Synchronization | +| R-LIMS-IWF | Requesting-LIMS-IWF | +| RLP | Roaming Location Protocol | +| RNC | Radio Network Controller | +| RRM | Radio Resource Management | +| RTD | Real Time Difference | +| RTT | Round Trip Time | +| SAI | Service Area Identifier | +| SAT | SIM Application Tool-Kit | +| SCCP | Signalling Connection Control Part | +| SCS | Service Capability Server | +| SGSN | Serving GPRS Support Node | +| SI | Service Interface (prefix to interface class method) | + +| | | +|---------|--------------------------------------------| +| SIM | Subscriber Identity Module | +| SIP | Session Initiation Protocol | +| SIP-URI | SIP Uniform Resource Identifier | +| SIR | Signal Interference Ratio | +| SLF | Subscription Locator Function | +| SLP | SUPL Location Platform | +| SLPP | Subscriber LCS Privacy Profile | +| SMLC | Serving Mobile Location Centre | +| SMS | Short Message Service | +| SP | Service Point | +| SRNC | Serving RNC | +| SS7 | Signalling System No 7 | +| SUPL | Secure User Plane Location | +| TA | Timing Advance | +| TAU | Tracking Area Update | +| TEL-URL | Telephone Uniform Resource Locator | +| TMSI | Temporary Mobile Subscriber Identity | +| TOA | Time Of Arrival | +| TTTP | Transfer To Third Party | +| UDT | SCCP Unitdata message | +| UE | User Equipment | +| UL | Uplink | +| UMTS | Universal Mobile Telecommunication System | +| UPLI | UE Provided Location Information | +| USIM | Universal Subscriber Identity Module | +| UTDOA | Uplink Time Difference of Arrival | +| UTRAN | Universal Terrestrial Radio Access Network | +| VASP | Value Added Service Provider | +| V-GMLC | Visited -GMLC | +| VHE | Virtual Home Environment | +| WCDMA | Wideband Code Division Multiple Access | + +Further related abbreviations are given in TR 21.905 [3]. + +## 4 Main concepts + +A general description of location services and service requirements are given in the specification TS 22.071 [4]. The positioning of the UE is a service provided by the Access Network. In particular, all Access Networks (e.g. UTRAN, GERAN, E-UTRAN), that facilitate determination of the locations of User Equipments, shall be able to exchange location information with the core network as defined in the present document (when connected to a Core Network). Optionally, location information may also be communicated between GMLCs, located in the same or a different PLMN, via the specified GMLC to GMLC interface. + +By making use of the radio signals the capability to determine the (geographic) location of the user equipment (UE) or mobile station (UE) shall be provided. The location information may be requested by and reported to a client (application) associated with the UE, or by a client within or attached to the Core Network. The location information may also be utilised internally in the system; for example, for location assisted handover or to support other features such as home location billing. The location information request may ask for the velocity of the UE as part of the positioning information. The position information shall be reported in standard, i.e. geographical co-ordinates, together with the time-of-day and the estimated errors (uncertainty) of the location of the UE according to specification TS 23.032 [11]. The velocity of the UE may be optionally returned in a format specified in TS 23.032 [11]. + +It shall be possible for the majority of the UE (active or idle) within a network to use the feature without compromising the radio transmission or signalling capabilities of the GSM/UMTS/EPS networks. + +The UE and the network may support a number of different positioning methods and the UE may support or not support privacy invocation request and response. The UE informs the core network and radio access network about its LCS capabilities in this respect as defined in TS 24.008 [24] and TS 25.331 [25]. + +The uncertainty of the location measurement shall be network design (implementation) dependent at the choice of the network operator, this is further described in TS 25.305 [1], TS 36.305 [42], and TS 43.059 [16]. + +There are many different possible uses for the location information. The positioning feature may be used internally by the GSM/UMTS/EPS network (or attached networks), by value-added network services, by the UE itself or through the network, and by "third party" services. The positioning feature may also be used by an emergency service (which may be mandated or "value-added"), but the position service is not exclusively for emergencies. + +There are regulatory requirements to support anonymity in location services in some countries. + +### 4.1 Assumptions + +As a basis for the further development work on LCS in GSM, UMTS and EPS the following assumptions apply: + +- positioning methods are Access Network specific, although commonalties should be encouraged between Access Networks; +- commercial location services are only applicable for an UE with a valid SIM or USIM; +- the provision of the location services in the Access Network is optional through support of the specified method(s); +- the provision of location services is optional in MSC, SGSN and MME; +- LCS is applicable to any target UE whether or not the UE supports LCS, but with restrictions on choice of positioning method or notification of a location request to the UE user when LCS or individual positioning methods, respectively, are not supported by the UE; +- LCS shall be applicable for both circuit switched and packet switched services; +- the location information may be used for internal system operations to improve system performance; +- it shall be possible to accommodate future techniques of measurement and processing to take advantage of advancing technology so as to meet new service requirements; +- it may be necessary to support LCS signalling between separate access networks via the core network. For UMTS, the Iur interface should be used if available; + +- Provide positioning procedures through the circuit-switched domain are also applicable to GPRS UEs which are GPRS and IMSI attached; +- it shall be possible for more than one LCS Client to request and obtain the location of the same target UE at the same time. + +## 4.2 Location Services Categories + +Generally there are four categories of usage of the location service. These are the Commercial LCS, the Internal LCS, the Emergency LCS and the Lawful Intercept LCS. The definition of these services and their categories is outside the scope of the present document. + +- The Commercial LCS (or Value Added Services) will typically be associated with an application that provides a value-added service to the subscriber of the service, through knowledge of the UE location (and optionally, velocity) and if available, and at the operator's discretion, the positioning method used to obtain the location estimate. This may be, for example, a directory of restaurants in the local area of the UE, together with directions for reaching them from the current UE location. +- The Internal LCS will typically be developed to make use of the location information of the UE for Access Network internal operations. This may include; for example, location assisted handover and traffic and coverage measurement. This may also include support certain O&M related tasks, supplementary services, IN related services and GSM bearer services and teleservices. +- The Emergency LCS will typically be part of a service provided to assist subscribers who place emergency calls. In this service, the location of the UE caller and, if available, the positioning method used to obtain the location estimate is provided to the emergency service provider to assist them in their response. This service may be mandatory in some jurisdictions. In the United States, for example, this service is mandated for all mobile voice subscribers. +- The Lawful Intercept LCS will use the location information to support various legally required or sanctioned services. + +## 4.3 Positioning methods + +The LCS feature utilises one or more positioning methods in order to determine the location of user equipment (UE). Determining the position of a UE involves two main steps: + +- Radio signal measurements; and +- Position estimate computation based on the measurements. + +The positioning methods for UTRAN are further described in TS 25.305 [1]. + +### 4.3.1 Standard LCS Methods in UTRAN + +The specification TS 25.305 [1] UTRAN Stage 2 specifies the locating methods to be supported: + +- cell coverage based positioning method; +- OTDOA positioning method; +- A-GNSS based positioning methods; +- UTDOA positioning method; +- Barometric pressure sensor method; +- WLAN method; +- Bluetooth method; +- Terrestrial Beacon System method. + +For more details on these positioning methods, refer to TS 25.305 [1]. + +### 4.3.2 Standard LCS Methods in GERAN + +The specification TS 43.059 [16] GERAN LCS Stage 2 specifies the locating methods to be supported in GERAN: + +- cell coverage based positioning method; +- Enhanced Observed Time Difference (E-OTD) positioning method; +- A-GNSS based positioning methods; +- Uplink Time Difference of Arrival (UTDOA) positioning method. + +### 4.3.3 Standard LCS Methods in E-UTRAN + +Locating methods specified in TS 36.305 [42] applicable to E-UTRAN comprise: + +- uplink and downlink cell coverage based positioning methods; +- OTDOA positioning method; +- A-GNSS based positioning methods; +- UTDOA positioning method; +- Barometric pressure sensor method; +- WLAN method; +- Bluetooth method; +- Terrestrial Beacon System methods. + +Hybrid positioning using multiple methods from the list of positioning methods above is also supported. + +In case of the Home eNodeB, applicable locating methods may be restricted, e.g. when a Home eNodeB is connected via Home eNodeB GW. + +## 4.4 Types of Location Request + +### 4.4.1 Immediate Location Request + +Request for location where the LCS Server replies immediately to the LCS Client with the current location estimate if this could be obtained. + +### 4.4.2 Deferred Location Request + +Request for location contingent on some current or future events where the response from the LCS Server to the LCS Client may occur some time after the request was sent. + +#### 4.4.2.1 Types of event + +- a) UE available: Any event in which the MSC/SGSN/MME has established a contact with the UE. Note, this event is considered to be applicable when the UE is temporarily unavailable due to inaction by the user, temporarily loss of radio connectivity or IMSI detach and so on. Note that IMSI detach is only applicable in the case the UE has previously been registered and information is still kept in the node. The UE Available event only requires one response and after this response, the UE Available event is concluded. +- b) Change of Area: An event where the UE enters or leaves a pre-defined geographical area or if the UE is currently within the pre-defined geographical area. Only one type of area event may be defined (i.e. entering, + +leaving or remaining within the area). The LCS client defines the target area as a geographical area, as an E.164 country code for a geographic area [35a], as a PLMN identity or as a geopolitical name of the area. The LCS server may translate and define the target area as the identities of one or more radio cells, location areas, routing areas, tracking areas, country code or PLMN identity. The target UE must not give the target UE user access to the area definitions and network identities. The change of area event may be reported one time only, or several times. The area event report must not be repeated more often than allowed by the LCS client. The change of area event report shall contain an indication of the event occurrence. The location estimate may be included in the report. If an area event is detected by the UE but an event report cannot be sent (e.g. because the UE cannot access the network or due to a minimum reporting interval), a report shall be sent later when possible irrespective of whether the area event still applies for the current UE location. For E-UTRAN access, area event reporting is controlled by a minimum and a maximum reporting time. The minimum reporting time defines the minimum allowed time between successive area events. The maximum reporting time defines the maximum time between successive reports. When a UE sends a report due to expiration of the maximum reporting time, the UE indicates expiration of the maximum reporting time as the trigger event. The maximum reporting time enables the LCS client, R-GMLC and H-GMLC to remain aware of continuing support by the UE for the area event (e.g. to detect if area event reporting may have been aborted due to UE power off). + +- c) Periodic Location: An event where a defined periodic timer expires in the UE and activates a location report or a location request. If a periodic event is detected by the UE but an event report cannot be sent (e.g. because the UE cannot access the network temporarily), a report shall be sent later when possible and the periodic timer for the next event shall then be started. The reporting duration for periodic location shall equal the requested number of reports multiplied by the periodic interval even when reports are delayed. +- d) Motion: An event where the UE moves by more than some predefined linear distance from a previous location. The motion event may be reported one time only, or several times. The motion event report shall contain an indication of the event occurrence. A location estimate may be included in the report if requested by the LCS client. For successive motion event reports, motion is determined relative to the UE location corresponding to the immediately preceding event report (including an event report triggered by expiration of the maximum reporting time). If a motion event is detected by the UE but an event report is deferred (e.g. because the UE cannot access the network temporarily), a report shall be sent later when possible irrespective of whether the motion event still applies to the current UE location. Motion reporting is controlled by a minimum and a maximum reporting time. The minimum reporting time defines the minimum allowed time between successive event reports. The maximum reporting time defines the maximum time between successive reports. When a UE sends a report due to expiration of the maximum reporting time, the UE indicates expiration of the maximum reporting time as the trigger event. The maximum reporting time enables the LCS client, R-GMLC and H-GMLC to remain aware of continuing support by the UE for the motion event (e.g. to detect if motion event reporting may have been aborted due to UE power off). +- e) Other events are FFS. + +## 4.5 Concurrent Location Requests + +The LCS Server is enabled to support concurrent location requests for the same target UE. The following principles apply. + +1. Under certain conditions, an entity may combine concurrent location requests by fully executing one request and using the ensuing location estimate result(s) to satisfy the other request(s) without fully executing the latter and as allowed by QoS requirements. The allowed conditions for each type of entity are defined below: + - a) An R-GMLC may combine concurrent MT-LR requests for the same target UE-LCS Client pair. + - b) An H-GMLC may combine concurrent MT-LR requests for the same target UE if privacy requirements can be fully resolved by the H-GMLC (e.g. no notification or verification needed for the UE for any MT-LR that will not be fully executed). + - c) A V-GMLC may combine concurrent MT-LR and NI-LR related location requests for the same target UE provided it is clear and unambiguous for any MT-LR that will not be fully executed (e.g. from the contents of any MAP Provide Subscriber Location request received from the H-GMLC) that no outstanding privacy related actions are required for the UE (e.g. no privacy notification and/or privacy verification interaction with the UE and no privacy subscription verification in the VLR, SGSN or MME). + +- d) An MSC, MSC server, SGSN or MME may combine concurrent MT-LR, MO-LR and NI-LR location requests once any needed privacy related actions (e.g. UE notification and verification) have been performed for each MT-LR. + - e) A UE may combine concurrent MO-LR requests for LCS Clients internal to or associated with the UE. +2. Except under the conditions permitted in (1), different concurrent location requests shall be treated separately and shall not be visibly combined or made dependent on one another by any entity within the LCS Server. This means that the procedures defined here in clause 9 continue to apply to each separate location request and do not visibly impact one another. + 3. Implementation limitations are allowed whereby an entity that, either itself or in association with another entity, cannot support concurrent location requests or more than a certain number of concurrent location requests is allowed to reject or defer a new concurrent request or cancel one or more existing requests. When concurrent location requests are supported, each entity needs to ensure it correlates each location/position response with the associated request. + 4. In support of principles 1, 2 and 3, an entity (e.g. GMLC, MSC, MSC server, SGSN, MME, UE) that receives a new location request (e.g. MT-LR, MO-LR, NI-LR) while already supporting previous location requests for the same target UE may reject the new location request, defer (i.e. queue) the new request, cancel one or more previous requests (where a procedure for cancellation has been defined), allow the new location request to proceed concurrently with and separately from the previous requests if allowed on applicable interfaces or, for the specific cases defined in principle 1, combine the new request with one or more previous requests if this will not impair or affect service support for the new request (e.g. privacy and QoS). + 5. In support of principle 4, LCS Client priority and any other relevant priority information (e.g. UE subscription preferences) should be considered. In particular, location requests associated with emergency services or lawful interception clients should be given priority over other location requests. + +## 5 General LCS architecture + +### 5.1 LCS access interfaces + +One or more LCS Clients may access a Location Server via its Le interface. Location Servers, resident in the same or different PLMNs, may communicate with each other, indirectly, via the Lg interface to their associated MSC/SGSNs. Optionally, the Lr interface, as specified for direct GMLC to GMLC messaging, may be used for this purpose. For EPS, Location Servers, resident in the same PLMN, may communicate via the SLg interface to their associated MME. A fuller description of the LCS architecture, together with a diagram showing other LCS related interfaces, can be found in clause 6. + +![Diagram of LCS Access Interfaces and Reference Points](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) + +The diagram illustrates the LCS architecture. It features three main components: 'LCS network 1', 'LCS network 2', and a group of 'LCS Clients or other networks'. 'LCS network 1' is connected to 'LCS network 2' via a vertical line labeled 'Lg or Lr'. 'LCS network 1' is also connected to the 'LCS Clients or other networks' via a horizontal line labeled 'Le'. The 'LCS Clients or other networks' are represented by three overlapping ovals. + +Diagram of LCS Access Interfaces and Reference Points + +**Figure 5.1: LCS Access Interfaces and Reference Points** + +## 5.2 LCS Functional diagram, high level functions + +TS 22.071 [4] describes LCS services from the LCS client point of view. In the present document, a more detailed description of LCS is given. The LCS functional diagram shown in figure 5.2 depicts the interaction of the LCS client and the LCS server within the PLMN. The PLMN uses the various LCS components within the LCS server to provide the target UE Location Information to the LCS client. + +![Figure 5.2: LCS capability server Functional Diagram. The diagram shows the interaction between an LCS Client and an LCS Server. The LCS Client contains a 'Client handling component' with multiple 'LCF' units (LCF1, LCF2, LCF3, ..., LCFn). The LCS Server contains four main components: 'Subscriber handling component' (LSAF -- LSPF), 'System handling component' (LMMF, LSCTF, LSCF, LIMS-IWF, LSOF-LSBF), 'Client handling component' (LCCF, LCCTF, LCAF), and 'Positioning component' (PRCF, PCF, PSMF, PRRM). Arrows show the flow of 'Location Service Request' from the client to the server and 'Location Service Response' from the server back to the client. Internal arrows show interactions between the server components. A legend indicates that arrows represent 'Resources: Signalling protocols'.](a0739aaf13fa5a632d4faa830f6b2708_img.jpg) + +Figure 5.2: LCS capability server Functional Diagram. The diagram shows the interaction between an LCS Client and an LCS Server. The LCS Client contains a 'Client handling component' with multiple 'LCF' units (LCF1, LCF2, LCF3, ..., LCFn). The LCS Server contains four main components: 'Subscriber handling component' (LSAF -- LSPF), 'System handling component' (LMMF, LSCTF, LSCF, LIMS-IWF, LSOF-LSBF), 'Client handling component' (LCCF, LCCTF, LCAF), and 'Positioning component' (PRCF, PCF, PSMF, PRRM). Arrows show the flow of 'Location Service Request' from the client to the server and 'Location Service Response' from the server back to the client. Internal arrows show interactions between the server components. A legend indicates that arrows represent 'Resources: Signalling protocols'. + +**Figure 5.2: LCS capability server Functional Diagram** + +The following list gives the logical functional entities for the LCS. Two main functional groupings are defined which encompass a number of smaller functions. + +The LCS Functional entities are grouped as follows: + +- the LCS Client functional group; +- the LCS Server functional group consists of functions in the GSM, UMTS or EPS PLMN supporting LCS: + - client handling component; + - system handling component; + - subscriber handling component; + - positioning component. + +The functions of the LCS Client and the LCS Server in the PLMN are described in more detail in this clause. + +The allocation of LCS functions to network elements is specified in clause 6. + +## 5.3 LCS Client functional group + +An LCS client contains an LCS component with one or more client(s), which by using location information can provide location, based services. + +An LCS client is a logical functional entity that requests from the LCS server in the PLMN location information for one or more than one target UE within a specified set of parameters such as Quality of Service (QoS). The LCS Client may reside in an entity (including the UE) within the PLMN or in an entity external to the PLMN. + +The specification of the LCS Client's internal logic and its relation to the external use is outside the scope of the present document. + +### 5.3.1 External Location Client Function (LCF) + +The Location Client Function (LCF) provides a logical interface between the LCS client and the LCS server. + +This function is responsible for requesting location information for one or more UEs, with a specified "QoS" and receiving a response, which contains either location information or a failure indicator. + +## 5.4 LCS Server functional group + +The LCS server functional group consists of the functions that are needed for GSM, UMTS and EPS to support Location Services. + +### 5.4.1 Client handling component + +#### 5.4.1.1 Location Client Control Function (LCCF) + +The Location Client Control Function (LCCF) manages the external interface towards LCF. The LCCF identifies the LCS client by requesting client verification and authorization (i.e. verifies that the LCS client is allowed to position the subscriber) through interaction with the Location Client Authorization Function (LCAF). The LCCF handles mobility management for location services (LCS) e.g., forwarding of positioning requests to VMSC, SGSN or MME. The LCCF determines if the final positioning estimate satisfies the QoS for the purpose of retry/reject. The LCCF provides flow control of positioning requests between simultaneous positioning requests. It may order the Location Client Co-ordinate Transformation Function (LCCTF) to perform a transformation to local co-ordinates. It may also order a transformation of local co-ordinates to network identities via the Location System Co-ordinate Transformation Function (LSCTF). It also generates charging and billing related data for LCS via the Location System Billing Function (LSBF). + +#### 5.4.1.2 Location Client Authorization Function (LCAF) + +The Location Client Authorization Function (LCAF) is responsible for providing access and subscription authorization to a client. Specifically, it provides authorization to a LCS client requesting access to the network and authorizes the subscription of a client. LCAF provides authorization to a LCS client requesting Location Information of a specific UE. + +##### 5.4.1.2.1 Access Subfunction + +An *Access Subfunction* enables LCS clients to access LCS services. This subfunction provides verification and authorization of the requesting client. + +When a LCS is requested, the Access Subfunction uses the information stored in the LCS client *subscription profile* to verify that: + +- the LCS client is registered; and +- the LCS client is authorized to use the specified LCS request type; +- the LCS client is allowed to request location information for the subscriber(s) specified in the LCS request. + +#### 5.4.1.2.2 Subscription Subfunction + +The LCS client Subscription profile shall contain a minimum set of parameters assigned on per LCS client basis for an agreed contractual period. The LCS client profile shall contain the following set of access parameters: + +- LCS client identity; +- allowed LCS request types (i.e. LIR, LDR or both) (see note); +- maximum number of subscribers allowed in a single LCS request; +- priority; +- position override indicator; +- state(s); +- event(s) (applicable to LDR requests only); +- local coordinate system; +- LCS client access barring list (optional); +- PLMN access barring list applicability. + +NOTE: LIR = Location Immediate Request; and +LDR = Location Deferred Request. + +For certain authorized LCS client internal to the PLMN, a subscription profile is unnecessary. These clients are empowered to access any defined service that is not barred for an UE subscriber. This permits positioning of emergency calls without the need for pre-subscription. + +#### 5.4.1.3 Location Client Co-ordinate Transformation Function (LCCTF) + +The Location Client Co-ordinate Transformation Function (LCCTF) provides conversion of a location estimate expressed according to a universal latitude and longitude system into an estimate expressed according to a local geographic system understood by the LCF and known as location information. The local system required for a particular LCF will be either known from subscription information or explicitly indicated by the LCF. The LCCTF also provides the conversion of a target area to either a shape as defined in TS 23.032 [11], a PLMN, or country code. This is performed only if target area information is received from the LCS Client. + +#### 5.4.1.4 Location Client Zone Transformation Function (LCZTF) + +The Location Client Zone Transformation Function (LCZTF) performs transformations of a location (latitude and longitude) into a zone identity, which in North America identifies a particular emergency services zone. + +### 5.4.2 System handling component + +#### 5.4.2.1 Location System Control Function(LSCF) + +The Location System Control Function (LSCF) is responsible for co-ordinating location requests. This function manages call-related and non-call-related positioning requests of LCS and allocates network resources for handling them. The LSCF retrieves UE classmark information for the purpose of determining the LCS capabilities of UE. + +The LSCF performs call setup if required as part of a LCS e.g., putting the UE on dedicated radio resources. It also caters for co-ordinating resources and activities with regard to requests related to providing assistance data needed for positioning. This function interfaces with the LCCF, LSPF, LSBF and PRCF. Using these interfaces, it conveys positioning requests to the PRCF, relays positioning data to the LCCF and passes charging related data to the LSBF. + +The U-LSCF for UTRAN is further described in TS 25.305 [1], LSCF for GERAN is described in TS 43.059 [16]. + +#### 5.4.2.2 Location System Billing Function (LSBF) + +The Location System Billing Function (LSBF) is responsible for charging and billing activity within the network related to location services (LCS). This includes charging and billing of both clients and subscribers. Specifically, it collects charging related data and data for accounting between PLMNs. + +#### 5.4.2.3 Location System Operations Function (LSOF) + +The Location System Operations Function (LSOF) is responsible for provisioning of data, positioning capabilities, data related to clients and subscription (LCS client data and UE data), validation, fault management and performance management of LCS. + +An LSOF may be associated with each entity. + +#### 5.4.2.4 Location System Broadcast Function (LSBcF) + +The Location System Broadcast Function (LSBcF) provides broadcast capability. The LSBcF capability is only used when broadcast data is required for E-OTD, OTDOA or A-GNSS positioning methods. + +#### 5.4.2.5 Location System Co-ordinate Transformation Function (LSCTF) + +The Location System Co-ordinate Transformation Function (LSCTF) provides the conversion of an area definition, expressed in a geographic shape as defined in TS 23.032 [11], to network identities recognised only within a PLMN (such as Cell Identity, Location Area Identity). The area definition may convert to more than one network identity such as a collection of Cell Global Identities. + +#### 5.4.2.6 Location IMS – Interworking Function (LIMS-IWF) + +The Location IMS – Interworking Function (LIMS-IWF) in the requesting network provides the capability to route LCS service requests based on an IMS Public User Identity (SIP-URI) to the home network of the target user. The LIMS-IWF in the home network of the target user is responsible to determine the appropriate HSS and to obtain the MSISDN associated with a IMS Public User Identity from the HSS. + +### 5.4.3 Subscriber handling Component + +#### 5.4.3.1 Location Subscriber Authorization Function (LSAF) + +The Location Subscriber Authorization Function (LSAF) is responsible for authorizing the provision of a location service (LCS) for a particular mobile station (UE with SIM/USIM). Specifically, this function validates that a LCS can be applied to a given subscriber. In case LCF is in the UE then LSAF verifies that the UE subscriber has subscribed to the requested LCS service. LSAF also detects if the identity used to address the target UE is a pseudonym. If the identity used is detected as a pseudonym, the LSAF can then call the Location Subscriber Translation Function to perform the translation to verinym. + +#### 5.4.3.2 Location Subscriber Translation Function (LSTF) + +The Location Subscriber Translation Function (LSTF) is responsible for the mapping between pseudonyms and verinym of the target UE. + +#### 5.4.3.3 Location Subscriber Privacy Function (LSPF) + +The Location Subscriber Privacy function is responsible performs all privacy related authorizations. For a target UE it shall authorize the positioning request versus the privacy options of the target UE, if any. + +### 5.4.4 Positioning components + +The positioning components Positioning Radio Co-ordination Function (PRCF), Positioning Calculation Function (PCF), Positioning Signal Measurement Function (PSMF) and Positioning Radio Resource Management (PRRM) are described in documents specific to each Access Network type. + +For location services for GSM and UMTS, the Access Network shall send the result of the positioning to the core network in geographical co-ordinates as defined in TS 23.032 [11]. For location services for EPS (for E-UTRAN access), the E-SMLC shall determine the result of the positioning in geographical co-ordinates as defined in TS 23.032 [11]. If requested and if available, the positioning result may also include the velocity of the UE as defined in TS 23.032 [11]. The Access Network or E-SMLC shall map the cell(s) the Target UE is associated with into geographical co-ordinates, but this mapping is not standardized. + +These entities are defined in TS 36.305 [42] for E-UTRAN, TS 25.305 [1] for UTRAN and in TS 43.059 [16] for GERAN. + +## 5.5 Information Flows between Client and Server + +Other types of national specific information flows may be supported in addition to the information flow specified here. + +Any of the information flows here indicated may not be externally realized if the information does not flow over an open interface. + +### 5.5.1 Location Service Request + +Via the Location Service Request, the LCS client communicates with the LCS server to request for the location information of one or more than one UE within a specified quality of service. There exist two types of location service requests: + +- Location Immediate Request (LIR); and +- Location Deferred Request (LDR). + +The attributes for the information exchange between the LCS Client and the LCS Server have been standardized by OMA in MLP [31]. + +The following attributes are identified for Location Service Request information flow: + +- Target UE identity (either verinum or pseudonym); +- LCS Client identity; +- Service identity, if needed; +- Response method (SYNC or ASYNC), if needed; +- Codeword, if needed; +- Requestor identity, if needed (and type of Requestor identity if available); +- Number dialled by the target mobile user or APN-NI, if the request is call or session related; +- Type of Event definition, i.e. UE available, change of area, motion or periodic location, applicable to deferred location requests only; +- Definitions for change of area type deferred location requests. Following parameters may be defined, if needed: + - a) Indication for event trigger, i.e. UE enters, leaves or is within requested target area; + - b) Indication of either a single event report or multiple event reports; + - c) Minimum time interval between area event reports, if multiple event reports are requested; + - d) Indication of the requested location estimate; i.e. whether the location estimate of the target UE should be contained in the change of area event report; + - e) Duration of event reporting; + - f) For EPC access, the maximum time interval between reports; + - g) For EPC access, the maximum sampling time for event detection; + +- Definitions for motion type deferred location requests. Following parameters may be defined, if needed; + - a) Linear distance threshold; + - b) Indication of either a single event report or multiple event reports; + - c) Minimum time interval between motion event reports, if multiple event reports are requested; + - d) Indication of the requested location estimate; i.e. whether the location estimate of the target UE should be contained in the motion event report; + - e) Duration of event reporting; + - e) Maximum time interval between reports; + - f) Maximum sampling time for event detection; +- Definitions for periodic location type deferred location requests. Following parameters may be defined, if needed: + - a) Time interval between successive location reports; + - b) Total number of reports; +- Start time, stop time (i.e. specifying the validity time of LCS request), if needed; +- Interval, applicable to periodical requests only; +- Requested Quality of Service information, if needed, i.e. accuracy, response time and LCS QoS Class; +- Requested type of location, i.e. "current location", "current or last known location" or "initial location" applicable to LIR only (current location is only available for LDR); +- Velocity of the UE, if needed; +- Priority, if needed; +- Service coverage (i.e. E.164 country codes for geographic areas [35a]), if needed; +- Requested maximum age of location, if needed; +- Local coordinate reference system, if needed; +- Target area, i.e. geographical area expressed as one of the following format, if needed. + - a) a shape defined in TS 23.032 [11] + - b) local coordinate system + - c) E.164 country code for a geographic area [35a] + - d) PLMN identity + - e) geopolitical name of the area (e.g. London) + +Some of the information may be stored in GMLC and the LCS client does not need to include such information in the location service request. + +## 5.5.2 Location Service Response + +The LCS server (GMLC) sends the Location Service Response to the LCS client either as an: + +- Immediate Response; or a +- Deferred Response, these deferred responses can be either single or periodic. + +The following attributes are identified for the Location Service Response information flow: + +- Location indication of UE in geographical coordinates expressed as a shape as defined in TS 23.032 [11] or local coordinate system; +- Velocity of the UE as defined in TS 23.032 [11], if requested and if available; +- The information about the positioning method used to obtain the location estimate of the UE, if it is available at the LCS server and if needed; +- Time stamp of location estimate; +- Indication when UE enters, is within or leaves the Geographical area, if needed; +- Acknowledgement for a deferred location request, if needed. +- Request id, if needed. +- LDR reference number, if needed. +- Indication that the requested QoS was not met, if needed, only applicable if the request was for best effort class +- Indication of a periodic event. +- Indication of a motion event. +- Indication that a deferred location request has been activated in a UE. +- Indication of expiration of the maximum reporting interval for the area event or motion event. + +In addition the information attributes of the location service request may be used also in the location service response. + +## 5.6 Information Flows between LCS Servers + +Other types of national specific information flows may be supported in addition to the information flow specified here. + +Any of the information flows here indicated may not be externally realized if the information does not flow over an open interface. + +When the LCS server's associated GMLC uses the Lr interface then this interface shall conform to the procedures defined in clause 9 of the current specification. + +### 5.6.1 Location Service Request + +Via the Location Service Request, the source LCS server communicates with the destination LCS server to request for the location information of one UE within a specified quality of service. There exist two types of location service requests: + +- Location Immediate Request (LIR); and +- Location Deferred Request (LDR). + +The attributes for the information exchange between the LCS Servers have been standardized by OMA in RLP [36]. + +The following attributes are identified for Location Service Request information flow: + +- Target UE identity, (either one or both of MSISDN and IMSI, or SIP-URI, or pseudonym); +- LCS Client identity, i.e. LCS client external identity or internal identity; +- LCS Client type, (i.e. Value added, Emergency, PLMN operator or Lawful interception); +- LCS Client name, if needed (and type of LCS client name if available); +- Service type, if needed; +- Response method (SYNC or ASYNC), if needed; + +- Codeword, if needed; +- Requestor identity, if needed (and type of Requestor identity if available); +- Number dialled by the target mobile user or APN-NL, if the request is call or session related; +- Type of Event definition, i.e. UE available, change of area, motion or periodic location, applicable to deferred location requests only; +- Definitions for change of area type deferred location requests. Following parameters may be defined, if needed: + - a) Indication for event trigger, i.e. UE enters, leaves or is within requested target area; + - b) Indication of either a single event report or multiple event reports; + - c) Minimum time interval between area event reports; + - d) Start time, stop time, i.e. specifying the validity time of LCS area event request; + - e) Indication of the requested location estimate; i.e. whether the location estimate of the target UE should be contained in the change of area event report; + - f) Duration of event reporting; + - g) For EPC access, the maximum time interval between reports; + - h) For EPC access, the maximum sampling time for event detection; +- Definitions for periodic location type deferred location requests. Following parameters may be defined, if needed: + - a) Time interval between successive location reports; + - b) Total number of reports; + - c) Indication of whether MO-LR Short Circuit is permitted (not applicable to EPC access); + - d) Reporting PLMN list; +- Definitions for motion type deferred location requests. Following parameters may be defined, if needed: + - a) Linear distance threshold; + - b) Indication of either a single event report or multiple event reports; + - c) Minimum time interval between motion event reports, if multiple event reports are requested; + - d) Indication of the requested location estimate; i.e. whether the location estimate of the target UE should be contained in the motion event report; + - e) Duration of event reporting; + - e) Maximum time interval between reports; + - f) Maximum sampling time for event detection; +- Requested Quality of Service information, if needed, i.e. accuracy, response time and LCS QoS Class; +- Requested type of location, i.e. "current location", "current or last known location" or "initial location" applicable to LIR only (current location is only available for LDR); +- Velocity of the UE, if needed; +- Priority, if needed; +- Requested maximum age of location, if needed; +- Privacy override indicator, if needed; + +- Service coverage (i.e. E.164 country codes for geographic areas [35a]), if needed; +- Indicator of privacy check related actions, if needed; +- Supported GAD shapes, if needed; +- HPLMN LCS server address, i.e. H-GMLC address, if needed; +- VPLMN LCS server address, i.e. V-GMLC address, if needed; +- Network address of Privacy Profile Register, if needed; +- Network numbers of serving nodes; +- LCS capability sets of serving nodes, if needed. +- Target area, i.e. geographical area expressed as one of the following format, if needed. + - a) a shape defined in TS 23.032 [11] + - b) E.164 country code for a geographic area [35a] + - c) PLMN identity +- LDR reference number, if needed. + +## 5.6.2 Location Service Response + +The Location Service Response is sent to the source LCS server as the result of the Location Service Request by the destination LCS Server: + +- Immediate Response; or a +- Deferred Response, these deferred responses can be either single or periodic. + +The following attributes are identified for the Location Service Response information flow: + +- Location indication of UE in geographical coordinates expressed as a shape as defined in TS 23.032 [11]; +- Velocity of the UE as defined in TS 23.032 [11], if requested and if available; +- Indication when UE enters, is within or leaves the geographical area, if needed; +- The information about the positioning method used to obtain the location estimate of the UE, if it is available at the LCS server and needed; +- Age of location estimate; +- Acknowledgement for a deferred location request, if needed. +- Request id, if needed +- Indication that the requested QoS was not met, if needed, only applicable if the request was for best effort QoS class +- Indication of a periodic event. +- Indication of a motion event. +- Indication that a deferred location request has been activated in a UE. +- Indication of expiration of the maximum reporting interval for the area event or motion event. + +In addition the information attributes of the location service request may be used also in the location service response. + +## 5.7 Optimized Lgd Procedure + +Optimized Lgd is an optional feature, applicable when Lgd is used, which allows signalling savings for when the GMLC needs the location information from the UE served by a combined MME/SGSN. It requires support from the following network elements: + +- Combined MME / SGSN when both MME and SGSN parts of the combined MME / SGSN are serving the UE. +- HSS. +- GMLC. + +A combined MME/SGSN supporting this feature shall indicate its support to the HSS via 'Optimized Lgd' indicator during Update Location Request procedures when network supports ISR, as specified in TS 29.272 [51]. + +An HSS supporting this feature shall indicate its support to the GMLC via 'Optimized Lgd' indicator in response to Send Routing Info for LCS request if the combined MME/SGSN registered for the given UE has indicated support for this procedure as specified in TS 29.173 [45]. Upon receipt of 'Optimized Lgd' indicator from the HSS, and if the GMLC supports this feature, then the GMLC shall consider this feature as activated for a given LCS Service Request procedure. + +Once the GMLC receives "Optimized Lgd" indicator from the HSS indicating support for this feature, and the GMLC has received both MME and SGSN addresses from the HSS, and the GMLC has determined to execute either PS-MT-LR or EPS-MT-LR procedures, and the GMLC has determined to not execute deferred location procedures, then the GMLC shall send only a single Provide Subscriber Location request to the combined MME/SGSN. When the combined MME/SGSN receives a single Provide Subscriber Location request, it shall perform either EPC-MT-LR or PS-MT-LR procedure depending upon the knowledge of the current RAT type of the UE. e.g. if the UE is in connected mode in E-UTRAN, the combined MME/SGSN performs only EPC-MT-LR procedure; if the ISR activated UE is in idle mode, the combined MME/SGSN performs the paging procedure followed by either EPC-MT-LR or PS-MT-LR procedure (depending upon the RAT where the UE is active). + +--- + +## 6 LCS Architecture + +### 6.0 Introduction + +Figure 6.1 shows the general arrangement of the Location Service feature in GSM, UMTS and EPS. This illustrates, generally, the relation of LCS Clients and servers in the core network with the GERAN, UTRAN and E-UTRAN Access Networks. The LCS entities within the Access Network communicate with the Core Network (CN) across the A, Gb, Iu and S1 interfaces. Communication among the Access Network LCS entities makes use of the messaging and signalling capabilities of the Access Network. + +As part of their service or operation, the LCS Clients may request the location information of UE. There may be more than one LCS client. These may be associated with the GSM/UMTS/EPS networks or the Access Networks operated as part of a UE application or accessed by the UE through its access to an application (e.g. through the Internet). + +The clients make their requests to a LCS Server. There may be more than one LCS Server. The client must be authenticated and the resources of the network must be co-ordinated including the UE and the calculation functions, to estimate the location and optionally, velocity of the UE and result returned to the client. As part of this process, information from other systems (other Access Networks) can be used. As part of the location information returned to the client, an estimate of the accuracy of the estimate and the time-of-day the measurement was made may be provided. + +![Figure 6.1-1: General arrangement of LCS. This diagram illustrates the network architecture for Location Services (LCS) across various radio access networks (RANs). At the center is the GMLC (*Note 6), which acts as a hub for location-related signaling. It connects to GERAN via 2G-MSC and 2G-SGSN (interfaces A, Gb, Lu); to UTRAN via 3G-SGSN and MSC server (interfaces Lu, Lg/Lgd *Note 9); and to E-UTRAN via MME (interface S1). The MME connects to E-SMLC and SLP (*Note 7) via SLs, and to LMU (*Note 8) via SLm. The GMLC also connects to PPR (*Note 3), E-CSCF, gsmSCF (*Note 2), LRF, HSS (*Note 1), and PMD (*Note 4). External LCS Clients connect to the GMLC via Le and Lid interfaces, with gsmSCF providing Proprietary and OSA API connections. UE connections are shown via Um, Uu, and LTE-Uu interfaces to their respective RANs.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +Figure 6.1-1: General arrangement of LCS. This diagram illustrates the network architecture for Location Services (LCS) across various radio access networks (RANs). At the center is the GMLC (\*Note 6), which acts as a hub for location-related signaling. It connects to GERAN via 2G-MSC and 2G-SGSN (interfaces A, Gb, Lu); to UTRAN via 3G-SGSN and MSC server (interfaces Lu, Lg/Lgd \*Note 9); and to E-UTRAN via MME (interface S1). The MME connects to E-SMLC and SLP (\*Note 7) via SLs, and to LMU (\*Note 8) via SLm. The GMLC also connects to PPR (\*Note 3), E-CSCF, gsmSCF (\*Note 2), LRF, HSS (\*Note 1), and PMD (\*Note 4). External LCS Clients connect to the GMLC via Le and Lid interfaces, with gsmSCF providing Proprietary and OSA API connections. UE connections are shown via Um, Uu, and LTE-Uu interfaces to their respective RANs. + +- NOTE 1: HSS includes both 2G-HLR and 3G-HLR functionality. LCS is included in the overall network architecture in TS 23.002 [20]. +- NOTE 2: As one alternative the LCS client may get location information directly from GMLC, which may contain OSA Mobility SCS with support for the OSA user location interfaces. See TS 23.127 [26], TS 29.198-1 [27], TS 29.198-2 [28], TS 29.198-3 [29] and TS 29.198-6 [30]. +- NOTE 3: The PPR functionality may be integrated in GMLC +- NOTE 4: The PMD functionality may be integrated in GMLC or PPR. +- NOTE 5: The LIMS-IWF may optionally be located within the GMLC. +- NOTE 6: LRF may interact with a separate GMLC or contain an integrated GMLC. +- NOTE 7: the SLP, which may be an H-SLP, V-SLP or E-SLP, may optionally be associated with an E-SMLC in order to share assistance data for support of both control plane LCS and OMA SUPL for an operator who deploys both solutions. Interaction between the E-SMLC and SLP is outside the scope of this TS. +- NOTE 8: The E-UTRAN may also comprise an LMU as noted in TS 36.300 [50] which interacts with an E-SMLC via the SLm interface. This LMU may be standalone or integrated into an eNodeB, as noted in TS 36.305 [42]. +- NOTE 9: Interface between SGSN and GMLC when MAP-based is referred to as Lg and when Diameter-based is referred to as Lgd. + +**Figure 6.1-1: General arrangement of LCS** + +Figure 6.1-1a shows the general arrangement of the Location Service feature in I-WLAN. This illustrates, generally, the relation of LCS Clients and servers in the core network with the WLAN Access Networks defined in TS 23.234 [52]. + +NOTE 1: The support of location services for the I-WLAN architecture is no longer maintained. + +![Diagram showing the general arrangement of LCS for I-WLAN. It includes a WLAN UE connected to a WLAN Access Network, which is connected to a 3GPP Home Network. The 3GPP Home Network contains various components like SLF, HSS, HLR, E-CSCF, 3GPP AAA Server, GMLC, LRF, Offline Charging System, OCS, WAG, and PDG. The PDG is part of the WLAN 3GPP IP Access functionality, which is shaded in the diagram. Interfaces are labeled with codes like Wa, Ww, Wn, Wu, Dw, Wx, D'/Gr', Lh/SLh, Lh, MI, La, Wo, Le, Lr, Wf, Wm, Wz, Wy, Wp, and Wi.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +Diagram showing the general arrangement of LCS for I-WLAN. It includes a WLAN UE connected to a WLAN Access Network, which is connected to a 3GPP Home Network. The 3GPP Home Network contains various components like SLF, HSS, HLR, E-CSCF, 3GPP AAA Server, GMLC, LRF, Offline Charging System, OCS, WAG, and PDG. The PDG is part of the WLAN 3GPP IP Access functionality, which is shaded in the diagram. Interfaces are labeled with codes like Wa, Ww, Wn, Wu, Dw, Wx, D'/Gr', Lh/SLh, Lh, MI, La, Wo, Le, Lr, Wf, Wm, Wz, Wy, Wp, and Wi. + +NOTE 1: The shaded area refers to WLAN 3GPP IP Access functionality. + +NOTE 2: The LCS La interface is added to support LCS for I-WLAN + +NOTE 3: The GMLC can have the SLP functionality or GMLC can be connected to the SLP. + +NOTE 4: For I-WLAN emergency location determination, the MI interface between E-CSCF and LRF will be used. For roaming scenario, the Lr will be used. + +Figure 6.1-1a: General arrangement of LCS for I-WLAN defined in TS 23.234 [52] + +![Figure 6.1-2: General arrangement of LCS with inter-GMLC and LIMS-IWF [Lr] interface. The diagram shows the network architecture for Location Services (LCS) across different radio access networks (GERAN, UTRAN, E-UTRAN) and core network elements (MSC, SGSN, MME, GMLC, LRF, PMD, HSS/HLR, LIMS-IWF).](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +The diagram illustrates the general arrangement of LCS with inter-GMLC and LIMS-IWF [Lr] interface. It shows the following components and interfaces: + +- VPMLN (Voice Packet Mobile Network):** A central domain containing various network elements. +- GERAN (GSM EDGE Radio Access Network):** Connected to the VPMLN via interfaces A (to 2G-MSC) and Gb (to 2G-SGSN). It also has an interface Um to the UE. +- UTRAN (UMTS Radio Access Network):** Connected to the VPMLN via interfaces Iu (to 3G-SGSN and MSC server). It has interfaces Uu to the UE and Lu to the 3G-SGSN. +- E-UTRAN (Evolved UMTS Radio Access Network):** Connected to the VPMLN via interface S1 (to MME). It has an interface LTE-Uu to the UE and SLm to the LMU \*Note3. +- Core Network Elements:** + - 2G-MSC:** Connected to GERAN (A) and 2G-SGSN (Gb). + - 2G-SGSN:** Connected to 2G-MSC (Gb) and UTRAN (Iu). + - 3G-SGSN:** Connected to UTRAN (Iu) and MSC server (Lu). + - MSC server:** Connected to UTRAN (Iu) and 3G-SGSN (Lu). + - MME:** Connected to E-UTRAN (S1) and LMU \*Note3 (SLm). + - LMU \*Note3:** Connected to E-UTRAN (SLm) and E-SMLC (SLm). + - E-SMLC:** Connected to MME (SLs) and SLP \*Note2 (SLs). + - SLP \*Note2:** Connected to E-SMLC (SLs). + - E-CSCF:** Connected to the VPMLN (MI). + - PMD:** Connected to the VPMLN (Lid). + - gsmSCF:** Connected to the External LCS Client (OSA-LCS). + - External LCS Client:** Connected to gsmSCF (OSA-LCS). + - LRF:** Connected to E-CSCF (MI) and VGMLC \*Note1 (Lg/Lgd \*Note 4). + - VGMLC \*Note1:** Connected to LRF (Lg/Lgd \*Note 4) and HGMLC \*Note1 (Lr). + - HGMLC \*Note1:** Connected to VGMLC \*Note1 (Lr) and RGMLC (Lr). + - RGMLC:** Connected to HGMLC \*Note1 (Lr) and PMD (Lid). + - HSS/HLR:** Connected to the VPMLN (Lh/SLh). + - HLIMS-IWF:** Connected to the VPMLN (Lh/SLh) and RLIMS-IWF (Lr). + - RLIMS-IWF:** Connected to HLIMS-IWF (Lr). +- Interfaces:** + - Um:** Between GERAN and UE. + - Uu:** Between UTRAN and UE. + - LTE-Uu:** Between E-UTRAN and UE. + - A:** Between GERAN and 2G-MSC. + - Gb:** Between GERAN and 2G-SGSN. + - Iu:** Between UTRAN and 3G-SGSN, and UTRAN and MSC server. + - Lu:** Between 3G-SGSN and MSC server. + - S1:** Between E-UTRAN and MME. + - SLm:** Between E-UTRAN (via LMU \*Note3) and E-SMLC. + - SLs:** Between MME and E-SMLC, and E-SMLC and SLP \*Note2. + - Lg / Lgd \*Note 4:** Between 2G-SGSN and LRF, and 3G-SGSN and VGMLC \*Note1. + - Lg:** Between MSC server and VGMLC \*Note1. + - Lr:** Between VGMLC \*Note1 and HGMLC \*Note1, HGMLC \*Note1 and RGMLC, and HLIMS-IWF and RLIMS-IWF. + - Lh/SLh:** Between HGMLC \*Note1 and HSS/HLR. + - Lid:** Between PMD and E-CSCF, and PMD and RGMLC. + - MI:** Between E-CSCF and LRF. + - OSA-LCS:** Between gsmSCF and External LCS Client. + - Le:** Between gsmSCF and External LCS Client. + - Lpp:** Between PPR and HGMLC \*Note1. + +Figure 6.1-2: General arrangement of LCS with inter-GMLC and LIMS-IWF [Lr] interface. The diagram shows the network architecture for Location Services (LCS) across different radio access networks (GERAN, UTRAN, E-UTRAN) and core network elements (MSC, SGSN, MME, GMLC, LRF, PMD, HSS/HLR, LIMS-IWF). + +NOTE 1: LRF may interact with a separate GMLC or contain an integrated GMLC. + +NOTE 2: the SLP, which may be an H-SLP, V-SLP or E-SLP, may optionally be associated with an E-SMLC in order to share assistance data for support of both control plane LCS and OMA SUPL for an operator who deploys both solutions. Interaction between the E-SMLC and SLP is outside the scope of this TS. + +NOTE 3: The E-UTRAN may also comprise an LMU as noted in TS 36.300 [50] which interacts with an E-SMLC via the SLm interface. This LMU may be standalone or integrated into an eNodeB, as noted in TS 36.305 [42]. + +NOTE 4: Interface between SGSN and GMLC when MAP-based is referred to as Lg and when Diameter-based is referred to as Lgd. + +**Figure 6.1-2: General arrangement of LCS with inter-GMLC and LIMS-IWF [Lr] interface** + +NOTE 2: For the scope of supporting location retrieval for IMS Emergency Service for WLAN access to EPC see TS 23.167 [36a]. + +## 6.1 Schematic functional description of LCS operations + +The allocation of LCS functional blocks to the Client, LCS server, Core Network, Access Network and UE is based on the schematic functional description below. The detailed functions and interactions are specified later in the present document and in TS 36.305 [42] for E-UTRAN, TS 25.305 [1] for UTRAN, in TS 43.059 [16] for GERAN and in corresponding Stage 3 specifications. + +The operation begins with a LCS Client requesting location information for a UE from the LCS server. The LCS server will pass the request to the LCS functional entities in the core network. The LCS functional entities in the core network shall then: + +- verify that the LCS Client is authorized to request the location of the UE or subscriber; +- verify that LCS is supported by the UE; +- establish whether it is allowed to locate the UE or subscriber, for privacy or other reasons; +- establish which network element in the Access Network for GERAN or UTRAN, or EPC for E-UTRAN, should receive the Location request; +- request the Access Network (via the A, Gb or Iu interface) for GERAN or UTRAN, or the E-SMLC (via the SLs interface) for E-UTRAN, to provide location information for an identified UE, with indicated QoS; + +- receive information about the location of the UE from the Access Network or E-SMLC and forward it to the Client; +- send appropriate accounting information to an accounting function. + +The Access Network LCS functional entities shall determine the position of the target UE according to TS 36.305 [42] for E-UTRAN, TS 25.305 [1] for UTRAN and TS 43.059 [16] for GERAN. + +## 6.2 Allocation of LCS functions to network elements + +Table 6.1 shows a summary of the Functional Groups and Functional Blocks for Location services. Table 6.2 and figure 6.2 show the generic configuration for LCS and the distribution of LCS functional blocks to network elements. Different positioning methods, including network-based, mobile-based, mobile-assisted and network-assisted positioning methods may be used. With this configuration both the network and the mobiles are able to measure the timing of signals and compute the mobile's location estimate. Depending on the applied positioning method it is possible to utilise the corresponding configuration containing all needed entities. For instance, if network-based positioning is applied, the entities that are involved in measuring the mobile's signal and calculating its location estimate are allocated to the network elements of the access stratum. On the other hand, in case mobile-based or network-assisted methods are used these entities should be allocated to the UE. + +LCS is logically implemented on the network structure through the addition of one network node, the Mobile Location Centre (MLC). It is necessary to name a number of new interfaces. The LCS generic architecture can be combined to produce LCS architecture variants. + +**Table 6.1: Summary of Functional Groups and Functional Blocks for Location services** + +| Funct. Group | Functional component | Full name of Functional Block | Abbrev. | +|---------------------------|-------------------------------|-----------------------------------------------------|------------------| +| Loc. | Location Client | (External) Location Client Function | LCF | +| Client | Component | Internal Location Client Function | LCF
-internal | +| LCS Server in PLMN | Client handling component | Location Client Control Function | LCCF | +| | | Location Client Authorization Function | LCAF | +| | | Location Client Co-ordinate Transformation Function | LCCTF | +| | | Location Client Zone Transformation Function | LCZTF | +| | System handling component | Location System Control Function | LSCF | +| | | Location System Billing Function | LSBF | +| | | Location System Operations Function | LSOF | +| | | Location System Broadcast Function | LSBcF | +| | | Location System Co-ordinate Transformation Function | LSCTF | +| | Subscriber Handling component | Location IMS – Interworking Function | LIMS-IWF | +| | | Location Subscriber Authorization Function | LSAF | +| | | Location Subscriber Translation Function | LSTF | +| | | Location Subscriber Privacy function | LSPF | +| | Positioning component | Positioning Radio Control Function | PRCF | +| | | Positioning Calculation Function | PCF | +| | | Positioning Signal Measurement Function | PSMF | +| | | Positioning Radio Resource Management | PRRM | + +Tables 6.2 and 6.2a and figure 6.2 illustrate the allocation of functional entities in the reference configuration of LCS. It is assumed that the CS and PS have either their own independent mobility management or use the joint mobility management through the optional Gs interface. + +It is also seen that LCS may take benefit of the Iur interface between RNCs, when uplink radio information and measurement results are collected. + +The functional model presented in the figure includes functional entities for both CS and PS related LCS. In addition, it consists of all the entities needed for different positioning methods, i.e. network based, mobile based, mobile assisted, and network assisted positioning, exploiting either uplink or downlink measurements. Similarly, the velocity of a UE may be calculated in either the network or the UE. It is noted that the UE may use e.g. the GPS positioning mechanism, but still demand e.g. auxiliary measurements from the serving network. RAN specific functional entities are specified in TS 36.305 [42] for E-UTRAN, TS 25.305 [1] for UTRAN and in TS 43.059 [16] for GERAN. + +Table 6.2: Allocation of LCS functional entities to network elements + +| | UE | RAN | GMLC | SGSN | MSC/MSC Server | HLR/HSS | PPR | PMD | Client | +|--------------------------------------|----|-----|------------|------|----------------|---------|-----|-----|--------| +| Location client functions | | | | | | | | | | +| LCF | X | | | X | X | | | | X | +| LCF Internal | | X | | | | | | | | +| Client handling functions | | | | | | | | | | +| LCCTF | | | X | | | | | | | +| LCCF | | | X | | | | | | | +| LCAF | | | X | | | | | | | +| LCZTF | | | X | | | | | | | +| System handling functions | | | | | | | | | | +| LSCF | | X | | X | X | | | | | +| LSBF | | | X | X | X | | | | | +| LSOF | X | X | X | X | X | | | | | +| LSBcF | | X | | | | | | | | +| LSCTF | | | X | | | | | | | +| LIMS-IWF | | | X (Note 1) | | | | | | | +| Subscriber handling functions | | | | | | | | | | +| LSAF | | | X | X | X | | X | | | +| LSPF | | | X | X | X | X | X | | | +| LSTF | | | | | | | | X | | +| Positioning functions | | | | | | | | | | +| PRCF | | X | | | | | | | | +| PCF | X | X | | | | | | | | +| PSMF | X | X | | | | | | | | +| PRRM | | X | | | | | | | | +| | UE | RAN | GMLC | SGSN | MSC/MSC Server | HLR/HSS | PPR | PMD | Client | + +NOTE 1: The LIMS-IWF may optionally be located within the GMLC. If it is not located within the GMLC, it shall use the Le or Lr reference point to interface to the GMLC. + +NOTE 2: The functional entities shown for the RAN are valid for GSM and UMTS but not EPS. + +Table 6.2a: Allocation of LCS functional entities to EPS elements + +| | UE | RAN | GMLC | MME | E-SMLC | HLR/HSS | PPR | PMD | Client | +|--------------------------------------|----|-----|------------|-----|--------|---------|-----|-----|--------| +| Location client functions | | | | | | | | | | +| LCF | X | | | X | | | | | X | +| LCF Internal | | | | | | | | | | +| Client handling functions | | | | | | | | | | +| LCCTF | | | X | | | | | | | +| LCCF | | | X | | | | | | | +| LCAF | | | X | | | | | | | +| LCZTF | | | X | | | | | | | +| System handling functions | | | | | | | | | | +| LSCF | | | | X | | | | | | +| LSBF | | | X | X | | | | | | +| LSOF | X | X | X | X | X | | | | | +| LSBcF | | X | | | X | | | | | +| LSCTF | | | X | | | | | | | +| LIMS-IWF | | | X (Note 1) | | | | | | | +| Subscriber handling functions | | | | | | | | | | +| LSAF | | | X | X | | | X | | | +| LSPF | | | X | X | | X | X | | | +| LSTF | | | | | | | | X | | +| Positioning functions | | | | | | | | | | +| PRCF | | | | | X | | | | | +| PCF | X | | | | X | | | | | +| PSMF | X | X | | | | | | | | +| PRRM | | X | | | | | | | | +| | UE | RAN | GMLC | MME | E-SMLC | HLR/HSS | PPR | PMD | Client | + +NOTE 1: The LIMS-IWF may optionally be located within the GMLC. If it is not located within the GMLC, it shall use the Le or Lr reference point to interface to the GMLC. + +![Figure 6.2: Generic LCS Logical Architecture diagram showing the internal components and interfaces of a Core Network (E-SMLC, MME, MSC/MSC Server, SGSN, PPR, PMD) and their connections to external elements like E-UTRAN, GERAN/UTRAN, UE, HLR/HSS, and an External LCS Client.](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +The diagram illustrates the Generic LCS Logical Architecture. It features a central 'Core Network' block containing several functional elements: + + +- E-SMLC**: Contains PRCF, PCF, LSOF, and LSBcF. +- MME**: Contains LSAF, LCF, LSOF, LSPF, LSBF, and LSCF. It connects to E-UTRAN via the S1 interface and to the MSC/MSC Server via the SLs interface. +- MSC/MSC Server**: Contains LSAF, LCF, LSOF, LSPF, LSBF, and LSCF. It connects to the MME via SLs, to the SGSN via the Gs interface, and to the HLR/HSS via the Lh interface. +- SGSN**: Contains LSAF, LCF, LSOF, LSPF, LSBF, and LSCF. It connects to the MSC/MSC Server via Gs, to the PPR via the Lg/Lgd interface, and to the PMD via the Lpp interface. +- PPR**: Contains LSAF and LSPF. It connects to the SGSN via Lg/Lgd and to the PMD via the Lid interface. +- PMD**: Contains LSTF. It connects to the PPR via Lid and to the GMLC via the Le interface. + + External elements and their connections: + + +- E-UTRAN**: Contains PSMF, LSOF, LSBcF, and PRRM. It connects to the MME via the S1 interface. +- GERAN/UTRAN**: Contains PSMF, LCF, LSCF, LSOF, LSBcF, PRCF, PCF, and PRRM. It connects to the UE via the Um/Uu interface and to the MSC/MSC Server via the A/Iu interface. +- UE**: Contains LCF, PCF, PSMF, and LSOF. It connects to GERAN/UTRAN via Um/Uu. +- HLR/HSS**: Contains LSPF. It connects to the MSC/MSC Server via the Lh interface. +- GMLC**: Contains LCCF, LCAF, LSOF, LSBF, LCCTF, LSAF, LSPF, LSCTF, and LCZTF. It connects to the HLR/HSS via Lh, to the PMD via Le, and to an **External LCS Client** via the Lr interface. +- LIMS-IWF**: Shown as an optional component within the GMLC, marked with '\* See ]'. + + Reference points are labeled as follows: + + +- SLs**: Between MME and MSC/MSC Server. +- SLg**: Between MME and HLR/HSS. +- Lh**: Between MSC/MSC Server and HLR/HSS. +- Gs**: Between MSC/MSC Server and SGSN. +- Lg/Lgd**: Between MSC/MSC Server and SGSN. +- Lpp**: Between SGSN and PPR. +- Lid**: Between PPR and PMD. +- Le**: Between PMD and GMLC. +- Lr**: Between GMLC and External LCS Client. + +Figure 6.2: Generic LCS Logical Architecture diagram showing the internal components and interfaces of a Core Network (E-SMLC, MME, MSC/MSC Server, SGSN, PPR, PMD) and their connections to external elements like E-UTRAN, GERAN/UTRAN, UE, HLR/HSS, and an External LCS Client. + +NOTE 1: The LIMS-IWF may optionally be located within the GMLC. If it is not located within the GMLC, it shall use the Le or Lr reference point to interface to the GMLC. + +Figure 6.2: Generic LCS Logical Architecture + +### 6.3 Functional description of LCS per network element + +#### 6.3.1 Access Network + +The Access Network is involved in the handling of various positioning procedures. + +The LCS specific functionalities of the radio access network elements are specified in TS 36.305 [42] for E-UTRAN, TS 25.305 [1] for UTRAN and TS 43.059 [16] for GERAN. + +### 6.3.2 LCS Clients, LCS applications and Requestors + +There are two classes of LCS Application - Internal applications and External applications. Internal applications represent entities internal to the GSM/UMTS/EPC that make use of location information for the (improved) operation of the network. Internal LCS client can be identified by LCS client internal ID. LCS client Internal ID distinguishes the following classes: (LCS client broadcasting location related information, O&M LCS client in the HPLMN, O&M LCS client in the VPLMN, LCS client recording anonymous location information, LCS Client supporting a bearer service, teleservice or supplementary service to the target UE). External applications represent entities (such as Commercial or Emergency services) that make use of location information for operations external to the mobile communications network. External LCS client can be identified by LCS client external ID. The LCS Applications interface to the LCS entities through their Location Client functions (LCF). Location requests from the external LCS clients may be originated by external entities (i.e. Requestor). LCS client should authenticate the Requestor Identity but this is outside the scope of this specification. + +LCS client may indicate the type of the Requestor identity in the LCS service request. The type of the Requestor identity can be one of the following: + +- Logical name +- MSISDN (TS 23.003 [17]) +- E-mail address (RFC 2396 [33]) +- URL (RFC 2396 [33]) +- SIP URL (RFC 3261 [34]) +- IMS public identity (TS 23.228 [35]) + +The LCS Client, LCS applications and Requestors are outside the scope of the present document. + +### 6.3.3 Gateway Mobile Location Centre, GMLC + +The Gateway Mobile Location Centre (GMLC) contains functionality required to support LCS. In one PLMN, there may be more than one GMLC. + +A GMLC is the first node an external LCS client accesses in a PLMN (i.e. the Le reference point is supported by the GMLC). The GMLC may request routing information from the HLR via the Lh interface or HSS via the SLh/Lh interface. After performing registration authorization, it sends positioning requests to either VMSC, SGSN, MSC Server or MME and receives final location estimates from the corresponding entity via the Lg, Lgd or SLg interface. + +NOTE: Support of both Lg and Lgd on GMLC is an implementation option. Whether a GMLC supporting both interfaces (Lg and Lgd) uses Lg or Lgd towards an SGSN is based on operator configuration. + +Information needed for authorisation, location service requests and location information may be communicated between GMLCs, located in the same or different PLMNs, via the Lr interface. The target UE's privacy profile settings shall always be checked in the UE's home PLMN prior to delivering a location estimate. In order to allow location request from a GMLC outside the HPLMN while having privacy check in the HPLMN, the Lr interface is needed. + +The "Requesting GMLC" is the GMLC, which receives the request from LCS client. + +The "Visited GMLC" is the GMLC, which is associated with the serving node of the target mobile. + +The "Home GMLC" is the GMLC residing in the target mobile's home PLMN, which is responsible for the control of privacy checking of the target mobile. + +The Requesting GMLC can be the Visited GMLC, and either one or both of which can be the Home GMLC at the same time. + +### 6.3.3A Location Retrieval Function, LRF + +Location Retrieval Function (LRF) may be collocated with the GMLC or separate and is responsible for retrieving or validating location information, providing routing and/or correlation info of an UE that has initiated an IMS emergency session. The information is provided to the E-CSCF via the MI interface. For detail, refer to TS 23.167 [36a]. + +### 6.3.4 LCS support in the UE + +The UE may be involved in the various positioning procedures. Specific UE involvement is specified in each of the positioning procedures specified in TS 36.305 [42] in E-UTRAN, TS 25.305 [1] for UTRAN and TS 43.059 [16] for GERAN. + +The UE interacts with the measurement co-ordination functions to transmit the needed signals for uplink based LCS measurements and to make measurements of downlink signals. The measurements to be made will be determined by the chosen location method. + +The UE may also contain LCS applications, or access a LCS application through communication with a network accessed by the UE or an application residing in the UE. This application may include the needed measurement and calculation functions to determine the UE's location with or without assistance of the GSM/UMTS/EPS LCS entities. + +In GSM the positioning methods supported by the UE are signalled by the UE to the core network and radio access network using Classmark3 in CS mode, as specified in TS 24.008 [24]. + +In UMTS the UE capability to support different positioning methods is only communicated within UTRAN, as specified in TS 25.331 [25]. + +In EPS the positioning methods supported by the UE may be signalled by the UE to the core network using LPP by the initial location service invocation as specified in TS 36.305 [42]. Also, in EPS the UE capabilities to support LCS Notification for an MT-LR and LPP for positioning are exchanged at the initial EPS attach procedure. The indication of the UE LPP capability will be forwarded by MME to E-SMLC as specified in TS 29.171 [46]. + +The UE informs the core network about its capability to support privacy invocation request and response using Classmark2 in CS mode and MS Network Capability in PS mode, as specified in TS 24.008 [24]. + +The UE may also, for example, contain an independent location function (e.g. Global Satellite Positioning Service GPS) and thus be able to report its location, independent of the RAN transmissions. The UE with an independent location function may also make use of information broadcast by the RAN that assists the function. + +The UE may support multiple simultaneous location sessions. + +### 6.3.5 MSC/VLR + +The MSC/VLR contains functionality responsible for UE subscription authorization and managing call-related and non-call related positioning requests of LCS. The MSC is accessible to the GMLC via the Lg interface. The LCS functions of MSC are related to charging and billing, LCS co-ordination, location request, authorization and operation of the LCS services. If connected to SGSN through the Gs interface, it checks whether the UE is GPRS attached to decide whether to page the UE on the A/Iu or Gs interface. + +The MSC/VLR may inform HLR/HSS about the UE's LCS Capabilities and may include the IP address of the V-GMLC associated with the MSC/VLR in the MAP UPDATE LOCATION message, during Registration and Inter MSC Update Location procedures. + +### 6.3.6 MSC Server + +The MSC Server handles the same functionality as the MSC/VLR including charging and billing, LCS co-ordination, location request, authorization and operation of the LCS services. The MSC Server is accessible to the GMLC via the Lg interface. + +### 6.3.7 SGSN + +The SGSN contains functionality responsible for UE subscription authorization and managing positioning requests of LCS. The SGSN is accessible to the GMLC via the Lg (MAP-based) or Lgd (Diameter-based) interface. The LCS functions of SGSN are related to charging and billing, LCS co-ordination, location request, authorization and operation of the LCS services. + +NOTE: Support of both Lg and Lgd on SGSN is an implementation option. Whether an SGSN supporting both (Lg or Lgd) interfaces uses Lg or Lgd towards a GMLC is based on operator configuration. + +The SGSN may inform HLR/HSS about the UE's LCS Capabilities for GPRS and may include the IP address of the V-GMLC associated with the SGSN in the MAP UPDATE GPRS LOCATION message, during Attach and Inter SGSN Routing Area Update procedures. + +The SGSN forwards the circuit-switched paging request received from the Gs interface to the BSS/RNC. + +### 6.3.8 Home Location Register, HLR + +The HLR contains LCS subscription data and routing information. The HLR is accessible from the GMLC via the Lh interface. For a roaming UE, HLR may be in a different PLMN. + +### 6.3.9 HSS + +The HSS contains LCS subscription data and routing information. The HSS is accessible from the GMLC via the Lh/SLh interface. For roaming UEs, HSS may be in a different PLMN. + +### 6.3.10 gsmSCF + +The Lc interface supports CAMEL access to LCS and is applicable in CAMEL Phase 3 and later. The procedures and signalling associated with it are defined in TS 23.078 [21] and TS 29.002 [18], respectively. + +### 6.3.11 Privacy Profile Register, PPR + +Privacy check may be done in the privacy profile register. The HLR or HSS contains the address to the PPR. The PPR is accessible from the H-GMLC via the Lpp interface. PPR may be a standalone network entity or the PPR functionality may be integrated in H-GMLC. + +### 6.3.12 Pseudonym Mediation Device, PMD + +The pseudonym mediation device (PMD) functionality maps or decrypts the pseudonym into the corresponding verinym (i.e. IMSI or MSISDN). PMD functionality may be a standalone network entity or the PMD functionality may be integrated in PPR, GMLC or other network entity. If PMD functionality is not part of GMLC it may be accessed using the Lid interface. The detail of PMD functionality is out of scope, and only the interface between GMLC and PMD functionality is specified in this specification. + +### 6.3.13 Mobility Management Entity, MME + +The Mobility Management Entity (MME) contains functionality responsible for UE subscription authorization and managing positioning requests of LCS. The MME is accessible to the GMLC via the SLg interface. The LCS functions of MME are related to charging and billing, LCS co-ordination, E-SMLC selection, location request, authorization and operation of the LCS services. + +The MME may inform HLR/HSS about the UE's LCS Capabilities for EPS and may include the IP address of the V-GMLC associated with the MME in the Update Location Request message, during Attach and Inter MME Tracking Area Update procedures. + +The MME selects an available E-SMLC to serve the location request for a UE. The selection is based on network topology and should provide load balancing between E-SMLCs. Other criteria for E-SMLC selection may include LCS Client type and requested QoS. + +When assistance data is broadcast by the EPS in ciphered form, the MME receives ciphering keys from the E-SMLC and forwards to suitably subscribed UEs using mobility management procedures. + +## 6.3.14 Evolved Serving Mobile Location Centre, E-SMLC + +The E-SMLC manages the overall co-ordination and scheduling of resources required for the location of a UE that is attached to E-UTRAN. It also calculates the final location and velocity estimate and estimates the achieved accuracy. The E-SMLC interacts with the UE in order to exchange location information applicable to UE assisted and UE based position methods and interacts with the E-UTRAN in order to exchange location information applicable to network assisted and network based position methods. The E-SMLC may provide broadcast assistance data via E-UTRAN in ciphered or unciphered form and forward any ciphering keys to subscribed UEs via the MME. + +## 6.4 Addressing the target UE for LCS purposes + +### 6.4.1 Verinymns for the target UE + +It shall be possible to address and indicate the target UE using MSISDN and SIP-URI. It may be possible in certain cases to address the target UE using IP address when a static or dynamic IP address (IPv4 or IPv6) has been allocated for the UE. + +In the mobile terminated location request procedures in the PS domain (as well as in the CS domain), the target UE is identified using either MSISDN or IMSI. + +**NOTE:** It is recognized that IP-addressing of the target UE is only possible when there is an active PDP context established between the target UE and the external LCS client. Using the established PDP context, the LCS client can request the target UE, as identified with the IP address it currently uses, to initiate a Mobile originated location request. The actual signalling exchange between the LCS Client/server and the target UE or the user of the target UE is outside the scope of this specification. The resulting MO-LR is performed as specified in this document. + +### 6.4.2 Pseudonyms for the target UE + +National regulations require support for the anonymity of the target mobile user in some countries. It shall therefore be possible to address and indicate the target UE using a pseudonym. The pseudonym may be the IMSI or MSISDN of the target UE encrypted e.g. using the public key of the home operator. The address of the network element that issued the pseudonym, i.e. the PMD address, shall either be attached to the pseudonym, if required or this address can be deduced from the pseudonym. The H-GMLC address may also either be attached to the pseudonym or be deduced from the pseudonym. It is outside the scope of this specification how the requestor and the LCS client will receive and handle the pseudonym, but some examples are described in the informative Annex E. + +### 6.4.3 Non-dialable callback numbers + +In case of a SIM-less emergency call, or in case of a non-registered (U)SIM emergency call, a non-dialable callback number shall be used to identify the target UE. The format and structure of the non-dialable callback number is according to national or regional regulations. The non-dialable callback number in North America shall, according to J-STD-036 [32], be the digits 911 + the last 7 digits of IMEI expressed in decimal numbers. + +**NOTE:** The use of non-dialable callback numbers in other parts of the world is for further study. The non-dialable callback number should adopt random numbering, if not otherwise unique. + +## 6.5 Quality of Service Information + +LCS Quality of Service information is characterised by 3 key attributes: + +- LCS QoS Class +- Accuracy +- Response Time + +The use of quality of service to characterise location requests is optional and if not requested the default shall be either network operator determined or client negotiated. + +## 6.5.1 LCS QoS Class + +The LCS QoS Class defines the degree of adherence by the Location Service to another quality of service parameter (Accuracy), if requested. The LCS Server shall attempt to satisfy the other quality of service parameter regardless of the use of QoS Class. + +### 6.5.1.1 Best Effort Class + +This class defines the least stringent requirement on the QoS achieved for a location request. If a location estimate obtained does not fulfil the other QoS requirements, it should still be returned but with an appropriate indication that the requested QoS was not met. If no location estimate is obtained, an appropriate error cause is sent. + +### 6.5.1.2 Assured Class + +This class defines the most stringent requirement on the accuracy achieved for a location request. If a location estimate obtained does not fulfil the other QoS requirements, then it shall be discarded and an appropriate error cause sent. + +--- + +## 7 Signalling and Interfaces + +### 7.1 LCS signalling between Access and Core Networks for GERAN and UTRAN access networks + +For GERAN and UTRAN access networks, the core network sends location requests to the access network, which then sends the corresponding responses back to the core network. + +Communication between access and core networks is accomplished through Iu interface in UMTS whereas the A, Gb and Iu interfaces are used for the purpose in GSM (see TS 25.305 [1] and TS 43.059 [16]). + +#### 7.1.1 Core network Location Request + +The core network request for a location estimate of a target UE shall contain sufficient information to enable location of the Target UE according to the required QoS using any positioning method supported by the PLMN and, where necessary, UE. For location services the core network may request the geographical co-ordinates and velocity of the Target UE. + +In Iu mode the core network may also request in which Service Area the Target UE is located. The Service Area information may be used for routing of corresponding Emergency calls, or for CAMEL services. + +In A/Gb mode this corresponds to the usage of Cell ID in the core network. It should be noted that the Service Area concept is different from the Localized Service Area concept used for SoLSA services. + +When the location of a Target UE in Idle Mode is requested, the core network shall determine which RAN entity is associated with the Target UE. + +#### 7.1.2 Location Report + +The access network reports the location of the Target UE to the core network entities. The location report may contain the following information as defined in the corresponding location request: + +- the geographical co-ordinates of the Target UE; +- the positioning method used to obtain the location estimate if the access network is either GERAN in the A/Gb mode, GERAN in the Iu mode or UTRAN in the Iu mode. +- the service area in which the Target UE is located; + +- achieved quality level of the location estimate; +- velocity estimate of the Target UE, if available; +- achieved quality level of the velocity estimate of the Target UE, if available. + +## 7.1a LCS signalling between Access and Core Networks for E-UTRAN access networks + +For E-UTRAN access networks, the MME sends location requests to the E-SMLC via the SLs interface (see clause 7.8). The E-SMLC then sends core network measurement requests, as described in clause 7.1a.1, to the access network via the MME. The access network sends corresponding network measurement reports, as described in clause 7.1a.2, back to the E-SMLC, again via the MME. + +Communication between access and core networks is accomplished through S1 interface in E-UTRAN (see TS 36.305 [42]). + +### 7.1a.1 Core network Measurement Request + +The core network request for network measurements shall contain sufficient information to enable the desired measurements to be provided by the access network. + +The core network shall determine which RAN entities are associated with the Target UE. + +### 7.1a.2 Location Measurement Report + +The access network reports measurements pertaining to the Target UE back to the E-SMLC as defined in the corresponding core network measurement request. + +## 7.2 Um, Uu and Uu-LTE Interfaces + +The Um, Uu and Uu-LTE interfaces are used to communicate among the LCS entities associated with the BSC, RNC, the UE and the stand-alone (Type A) Location Measurement Units (LMU). The Um, Uu and Uu-LTE interfaces are also used to communicate between the LCS entities in the core network and the UE. + +NOTE: The Type A and Type B LMUs are defined only for GERAN. For LTE, the LMU may be standalone or integrated into an eNodeB, as noted in TS 36.305 [42]. + +The Um/Uu/Uu-LTE interfaces may pass measurement requests and results to and from UE or the stand-alone LMU. + +The Um/Uu/Uu-LTE interfaces may also pass location requests from internal or external LCS Clients (Applications) at the UE. Note that these requests may require the services of the LCS entities associated with the core network to authenticate clients and subscriber subscriptions to aspects of the LCS. + +The Um/Uu/Uu-LTE interfaces may also be used for broadcast of information that may be used by the UE or stand-alone LMU for their LCS operations. This may, for example, include timing information about nearby Node-B/BTS transmissions that may assist the UE or LMU in making their measurements. In UTRAN code information may be included. + +The Um, Uu and Uu-LTE interfaces may also pass messages relating to changes or reporting of the data associated with the Location System Operations Function (LSOF) in the UE or the remote LMU. + +UTRAN Stage 2 specification TS 25.305 [1] specifies LCS signalling over the Uu interface and GERAN Stage 2 specification TS 43.059 [16] specifies LCS signalling over the Um interface correspondingly. E-UTRAN Stage 2 specification TS 36.305 [42] specifies LCS signalling over the Uu-LTE interface. + +Message segmentation is specified in GERAN LCS Stage 2, TS 43.059 [16]. + +## 7.3 MAP Interfaces + +The following interfaces are based on MAP in LCS. + +- Lh interface: interface between GMLC and HSS. This interface is used by the GMLC to request the address of the H-GMLC, and/or the address of the visited MSC or SGSN for a particular target UE whose location has been requested +- Lg interface: interface between GMLC MSC and GMLC - SGSN. This interface is used by the GMLC to convey a location request to the MSC or SGSN currently serving a particular target UE whose location was requested. The interface is used by the MSC or SGSN to return location results to the GMLC. +- Lc interface: interface between GMLC and gsmSCF, CAMEL. This interface is used to get location information for CAMEL based services. + +The following MAP services are defined for LCS. + +- MAP-SEND-ROUTING-INFO-FOR-LCS Service. + +This service is used between the GMLC and the HLR/HSS to retrieve the routing information needed for routing a location service request to the serving VMSC, SGSN. The service may be used in GMLC - HSS interface to retrieve routing information in order to route the location service request to the correct VMSC, SGSN and MSC Server. + +In case the service is used between the R-GMLC and the HSS, the H-GMLC address of the target UE to be located is retrieved. The address of the V-GMLC associated with the serving node and PPR may also be retrieved. + +- MAP-PROVIDE-SUBSCRIBER-LOCATION Service. + +This service is used by a GMLC to request the location and optionally, velocity, of a target UE from the visited MSC, SGSN or MSC Server at any time. + +- MAP-SUBSCRIBER-LOCATION-REPORT Service. + +This service is used by a VMSC, SGSN or MSC Server to provide the location of a target UE to a GMLC when a request for location is either implicitly administered or made at some earlier time. + +The MAP Subscriber Location Report could also be used to send information about location and, if requested and available, velocity of the Target UE (for MO-LR) to an external client. + +## 7.4 Lpp interface + +Lpp is the interface between H-GMLC and PPR. If the UE subscribers LCS privacy information is kept in the PPR this interface is used by the H-GMLC to request the PPR to perform a privacy check. The Lpp interface shall conform to the protocol as specified in (reference to be added) and the procedures defined in clause 9 of this specification. + +### 7.4.1 LCS Authorisation Request + +Via the LCS Authorisation Request, the H-GMLC can request the PPR to perform the privacy check. There exist two types of LCS Authorisation Request: + +- LCS Authorisation Request without location estimate (send by H-GMLC before location request); +- LCS Authorisation Request with location estimate (to check location related privacy settings). + +The following attributes are identified for LCS Authorisation Request information flow: + +- Target UE identity, (one or both of MSISDN and IMSI), if needed; +- If PPR contains PMD functionality the LCS Authorisation Request may contain the same information as the LCS Identity request, i.e. the pseudonym of the target UE, if needed. +- Indication on call/session related MT-LR; +- LCS Client identity, i.e. LCS client external identity or internal identity; + +- LCS Client type, (i.e. Value added, Emergency, PLMN operator or Lawful interception); +- LCS Client name, if needed (and type of LCS client name if available); +- Service type, if needed; +- Codeword, if needed; +- Requestor identity, if needed (and type of Requestor identity if available); +- Type of location, i.e. "current location", "current or last known location" or "initial location"; +- Velocity of the UE, if needed; +- LCS capability sets of serving nodes, if needed; +- Location estimate, if needed and available (This is only relevant for LCS Authorisation Request with location estimate); +- Type of Deferred Location Request, if needed (i.e. UE available, Change of Area, Motion or Periodic Location); +- Geographic area for change of area event, if needed; +- Parameters for Periodic Location event, if needed (i.e. reporting interval, total number of reports, request for MO-LR short circuit). +- Parameters for change of area event, if needed (i.e. type of area event, indication of single or multiple reports, minimum interval between reports, whether location estimates are requested, duration, maximum interval between reports, maximum sampling interval); +- Parameters for motion event, if needed (i.e. linear distance threshold, indication of single or multiple reports, minimum interval between reports, whether location estimates are requested, duration, maximum interval between reports, maximum sampling interval). + +## 7.4.2 LCS Authorisation Response + +The LCS Authorisation Response is sent by the PPR to the H-GMLC as the result for the LCS Authorisation Request. + +The following attributes are identified for the LCS Authorisation Response information flow: + +- Indicator for location request is to be barred, if needed. If this is set, no other indicators shall be included in the response; +- Indicator for call/session related class of privacy check related actions, if needed; + - positioning not allowed; + - positioning allowed without notifying the UE user; + - positioning allowed with notification to the UE user; + - positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification; + - positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user. +- Indicator for call/session unrelated class of privacy check related actions, if needed; + - positioning not allowed; + - positioning allowed without notifying the UE user; + - positioning allowed with notification to the UE user; + - positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification; + +- positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user. +- Pseudo external ID, if needed (see Annex C); +- Indicator on additional privacy check with location estimate, if needed; +- Indicator on additional notification/verification by the UE user without positioning (existing location estimate to be returned to the LCS Client if this is successful), if needed; +- Same information as in the LCS Identity Response, in case the PMD is integrated in PPR, if needed; +- Indicator for MO-LR short circuit allowed/not allowed, if needed. + +### 7.4.3 LCS Privacy Profile Update notification + +The LCS Privacy Profile Update notification is sent to the H-GMLC from the PPR in order to notify the H-GMLC about the change of UEs privacy profile. + +- Target UE identity, (one or both of MSISDN and IMSI); +- Indication on the changed UEs privacy profile + +### 7.4.4 LCS Privacy Profile Update notification ack + +The LCS Privacy Profile Update notification ack. is sent to the PPR as the result of the LCS Privacy Profile Update Request by H-GMLC. + +- Acknowledgement + +## 7.5 Lid interface + +Lid is the interface between H-GMLC and PMD. If the UE subscribers pseudonym can be mapped or decrypted to the corresponding verinym in the standalone PMD. The Lid interface shall conform to the protocol as specified in (reference to be added) and the procedures defined in clause 9 of this specification. + +### 7.5.1 LCS Identity Request + +Via the LCS Identity Request, the H-GMLC can request the PMD to retrieve the verinym of the subscriber. + +The following attribute is identified for the LCS Identity Request: + +- Pseudonym; + +### 7.5.2 LCS Identity Response + +The PMD sends the LCS Identity Response to the H-GMLC as a result of the LCS Identity Request by the H-GMLC. + +The following attribute is identified for the LCS Identity Response information flow: + +- Target UE identity, (one or both of MSISDN and IMSI); + +## 7.6 IMS related Interfaces + +### 7.6.1 Dh Interface + +Dh is the interface between LIMS-IWF and SLF. The purpose of this interface is to retrieve the address of the correct HSS serving the user. Dh is an optional interface. + +## 7.6.2 Sh Interface + +Sh is the interface between LIMS-IWF and HSS. The purpose of this interface is to retrieve the user's MSISDN. + +## 7.6.3 MI Interface + +MI is the interface between the E-CSCF and LRF. For details, refer to TS 23.167 [36a]. + +## 7.7 SLg Interface + +SLg is the interface that is used by the GMLC to convey a location request to the MME currently serving a particular target UE whose location was requested. The interface is also used by the MME to return location results to the GMLC. + +## 7.8 SLs Interface + +SLs is the interface between the MME and the E-SMLC. This interface is used to convey location requests from the MME to the E-SMLC and to convey corresponding location reports back from the E-SMLC to the MME. + +It is also used for tunnelling core network measurement requests from the E-SMLC to the RAN, using RAN specified protocols transparent to the MME as described in TS 36.305 [42]. + +## 7.9 SLh Interface + +SLh is the Diameter based interface between the HSS and the GMLC as described in TS 29.173 [45]. + +## 7.10 SLm Interface + +SLm is the interface between the E-SMLC and the LMU. This interface allows the E-SMLC to exchange measurement information with the LMU for the purpose of UTDOA positioning as described in TS 36.305 [42]. + +## 7.11 Lgd Interface + +Lgd is the interface that is used by the GMLC to convey a location request to the SGSN currently serving a particular target UE whose location was requested. The interface is also used by the SGSN to return location results to the GMLC. This interface is applicable only for an SGSN supporting EPS based interfaces and protocols. + +--- + +# 8 General network location procedures + +## 8.1 State description for GMLC + +### 8.1.1 GMLC states + +#### 8.1.1.1 NULL State + +In the NULL state, a particular location request from some LCS client either has not been received yet or has already been completed. After a location request is received from a LCS client, the GMLC remains in the NULL state while the identity of the client and nature of its location request are verified. While the NULL state exists conceptually, it need not be represented explicitly in the GMLC. + +### 8.1.1.2 INTERROGATION State + +In this state, the GMLC has sent an interrogation to the home HLR/HSS of the UE to be located and is awaiting a response giving one or several of the following addresses: the VMSC, MSC Server, SGSN address, MME address and IMSI for this UE. + +### 8.1.1.3 LOCATION State + +In this state, the GMLC has sent a location request to the VMSC, MSC Server, SGSN or MME serving the UE to be located and is awaiting a response containing a location estimate. Optionally, location information may also be communicated between GMLCs, located in the same or a different PLMN, via the GMLC to GMLC Lr interface + +## 8.1.2 State functionality + +### 8.1.2.1 State Transitions + +![Figure 8.1: State Transitions in the GMLC. A state transition diagram showing three states: NULL, INTERROGATION, and LOCATION. Transitions are as follows: NULL to INTERROGATION (Location Request - Interrogate HLR/HSS for GMLC/VMSC/SGSN/MME/MSC Server address); NULL to LOCATION (Location Request - GMLC knows VGMLC/VMSC/SGSN/MME/MSC Server address); INTERROGATION to NULL (Timeout or Error); INTERROGATION to LOCATION (Receive VGMLC/VMSC/SGSN/MME/MSC Server address from HLR/HSS); LOCATION to NULL (Receive Location or Timeout or Error).](9e9104f9ba7eec1259a7893c6380ca1b_img.jpg) + +``` + +stateDiagram-v2 + [*] --> NULL + NULL --> INTERROGATION : Location Request - Interrogate HLR/HSS for GMLC/VMSC/SGSN/MME/MSC Server address + NULL --> LOCATION : Location Request - GMLC knows VGMLC/VMSC/SGSN/MME/MSC Server address + INTERROGATION --> NULL : Timeout or Error + INTERROGATION --> LOCATION : Receive VGMLC/VMSC/SGSN/MME/MSC Server address from HLR/HSS + LOCATION --> NULL : Receive Location or Timeout or Error + +``` + +Figure 8.1: State Transitions in the GMLC. A state transition diagram showing three states: NULL, INTERROGATION, and LOCATION. Transitions are as follows: NULL to INTERROGATION (Location Request - Interrogate HLR/HSS for GMLC/VMSC/SGSN/MME/MSC Server address); NULL to LOCATION (Location Request - GMLC knows VGMLC/VMSC/SGSN/MME/MSC Server address); INTERROGATION to NULL (Timeout or Error); INTERROGATION to LOCATION (Receive VGMLC/VMSC/SGSN/MME/MSC Server address from HLR/HSS); LOCATION to NULL (Receive Location or Timeout or Error). + +Figure 8.1: State Transitions in the GMLC + +Moving from NULL to INTERROGATION state: + +If the GMLC does not know any of the following addresses: VMSC, MSC Server, SGSN, MME, V-GMLC address or IMSI when it receives a location service request from some LCS client, it moves from the NULL state to the INTERROGATION state and sends a request to the UE's home HLR/HSS for the VMSC/ MSC Server/ SGSN /MME/ V-GMLC address and IMSI. + +Moving from NULL to LOCATION state: + +If the GMLC already knows one of the following addresses: VMSC, MSC Server, SGSN, MME or UE IMSI, when it receives a location service request from some LCS client (e.g. from information retained for an earlier location request for the same UE), it moves from the NULL state to the LOCATION state and sends a location request to either the VMSC, MSC Server, SGSN, or MME. Optionally, it may send the location request to another GMLC via the Lr interface. + +NOTE: It is for further study how GMLC selects if it shall send the location request to VMSC, MSC server, SGSN, and/or MME in different cases. This should be specified in the signalling procedures. + +Moving from INTERROGATION to LOCATION state: + +After the GMLC, in the INTERROGATION state, receives one or several of the addresses VMSC, MSC Server, SGSN, MME, V-GMLC and IMSI from the home HLR/HSS, it enters the LOCATION state and sends a location request to either the VMSC, MSC Server, SGSN, MME or V-GMLC of the UE being located. + +Moving from LOCATION to NULL state: + +After the GMLC receives a location estimate response from the VMSC, MSC Server, SGSN, MME or V\_GMLC, it forwards the location estimate to the requesting LCS client and re-enters the NULL state. + +#### 8.1.2.2 INTERROGATION Timer Function + +The GMLC runs a timer while in the INTERROGATION state to limit the amount of time waiting for an interrogation response from the HLR/HSS. If the timer expires before an interrogation response is received, the GMLC indicates a location failure to the LCS client and re-enters the NULL state. + +#### 8.1.2.3 LOCATION Timer Function + +The GMLC runs a timer while in the LOCATION state to limit the amount of time waiting for a location estimate response from the VMSC/ MSC Server /SGSN/MME. If the timer expires before a response is received, the GMLC indicates a location failure to the LCS client and re-enters the NULL state. + +### 8.2 State description for VMSC and MSC Server + +#### 8.2.1 VMSC and MSC Server States + +##### 8.2.1.1 LCS IDLE State + +In this state, the VMSC/MSC Server location service is inactive for a particular UE. The UE may be known in the VMSC/MSC Server (except for a USIM less or SIM less Emergency call or where the UE information has been cancelled or lost in the VMSC/MSC Server), but there may not be an active Mobility Management to the UE. + +##### 8.2.1.2 LOCATION State + +In this state, the VMSC/MSC Server is awaiting a response from RAN after requesting the location for a particular UE. + +#### 8.2.2 State Functionality + +##### 8.2.2.1 State Transitions + +![State transition diagram for VMSC/MSC Server showing transitions between LCS-IDLE and LOCATION states.](52f68e21acc86c9aaab2f5abc51a9748_img.jpg) + +``` +stateDiagram-v2 + [*] --> LCS-IDLE + LCS-IDLE --> LOCATION : Request Location from the RAN + LOCATION --> LCS-IDLE : Receive Location results from the RAN or Timeout + LOCATION --> LOCATION : Transfer Positioning Messages +``` + +The diagram illustrates the state transitions for the VMSC/MSC Server. It features two main states: LCS-IDLE and LOCATION. The LCS-IDLE state is the initial state, indicated by an arrow from the left. A transition arrow points from LCS-IDLE to LOCATION, labeled 'Request Location from the RAN'. A return transition arrow points from LOCATION back to LCS-IDLE, labeled 'Receive Location results from the RAN or Timeout'. Additionally, there is a self-loop transition on the LOCATION state, labeled 'Transfer Positioning Messages'. + +State transition diagram for VMSC/MSC Server showing transitions between LCS-IDLE and LOCATION states. + +Figure 8.2: State Transitions in the VMSC/MSC Server + +Moving from LCS IDLE to LOCATION state: + +After a request has been received to locate a particular UE and the UE subscription options have been verified, a location request is sent to the RAN of the UE to be located: the VMSC/MSC Server then enters the LOCATION state. Before entering this state, the VMSC/MSC Server must have setup a Mobility Management connection to the UE if none was previously active. The mobile is paged and authenticated before positioning. + +Moving from LOCATION to LCS IDLE state: + +After the return of a location estimate result from RAN, the VMSC/MSC Server shall re-enter IDLE state. + +### 8.2.2.2 LOCATION Timer Function + +The VMSC/MSC Server runs a timer while in the LOCATION state to limit the amount of time waiting for a location response from the RAN. If the timer expires before such information is received, the VMSC/MSC Server indicates a location failure to the original requesting entity and re-enters IDLE state. + +## 8.3 LCS State description for SGSN + +### 8.3.1 SGSN States + +#### 8.3.1.1 LCS IDLE State + +In this state, the SGSN location service is inactive for a particular UE. The UE is known in the SGSN except in case where the UE data has been cancelled or lost in the SGSN. There is not an active Mobility Management to the UE. + +#### 8.3.1.2 LOCATION State + +In this state, the SGSN is awaiting a response from the RAN after requesting the location for a particular UE. In this state, a Mobility Management connection to the target UE will be active. + +### 8.3.2 State Functionality + +#### 8.3.2.1 State Transitions + +![State transition diagram for the SGSN showing two states: LCS-IDLE and LOCATION. Transitions are triggered by 'Request Location from the RAN', 'Receive Location results from the RAN or Timeout', and 'Transfer Positioning Messages'.](1381593e48739f603c81fa60e6b98a6c_img.jpg) + +``` +stateDiagram-v2 + [*] --> LCS-IDLE + LCS-IDLE --> LOCATION : Request Location from the RAN + LOCATION --> LCS-IDLE : Receive Location results from the RAN or Timeout + LOCATION --> LOCATION : Transfer Positioning Messages +``` + +State transition diagram for the SGSN showing two states: LCS-IDLE and LOCATION. Transitions are triggered by 'Request Location from the RAN', 'Receive Location results from the RAN or Timeout', and 'Transfer Positioning Messages'. + +Figure 8.3: State Transitions in the SGSN + +Moving from LCS-IDLE to LOCATION state: + +After a request has been received to locate a particular UE and the UE subscription options have been verified to allow this, the SGSN sends a location request to the RAN. The SGSN then enters the LOCATION state. Before entering this state, the SGSN must have setup a Mobility Management connection to the UE if none was previously active. The mobile is paged and authenticated before positioning. + +#### **Moving from LOCATION to LCS IDLE state:** + +After the return of a location estimate result from RAN, or if the Location Timer described below expires, the SGSN shall re-enter IDLE state. + +### **8.3.2.2 LOCATION Timer Function** + +The SGSN runs a timer while in the LOCATION state to limit the amount of time waiting for a location response from the RAN. If the timer expires before such information is received, the SGSN indicates a location failure to the original requesting entity and re-enters IDLE state. + +## **8.4 Signalling connection for the Iu interface** + +When using the Iu interface, before SGSN/MSC server can request location information of a target UE from RAN, an Iu signalling connection must have been established between SGSN/MSC server and RAN. The SGSN/MSC server sends a location request message to RAN, which determines the location of the target UE related to this Iu signalling connection and sends a location report to SGSN/MSC server over the same Iu signalling connection. On the Iu interface, only one location request for a geographic location estimate can be ongoing at any time. + +## **8.5 Signalling connection for the A-interface** + +When using the A interface, before MSC can request location information of a target UE from RAN, an A interface signalling connection must have been established between MSC and RAN. The MSC sends a location request message to RAN, which determines the location of the target UE related to this A interface signalling connection and sends a location report to MSC over the same A interface signalling connection. On the A interface, only one location request can be ongoing at any time. + +## **8.6 Gb interface mapping of target UE** + +The pre-requisite for LCS procedures on the Gb interface is that UE is in "ready state". On the Gb interface, only one location request can be ongoing at any time. + +## **8.7 LCS State description for MME** + +### **8.7.1 MME States** + +An MME supports at least one location session for any UE at any one time. A location session is invoked by the MME in order to obtain the location of the UE or perform some other location related service such as transferring assistance data to the UE. + +#### **8.7.1.1 LCS IDLE State** + +In this state, the MME location service is inactive for a particular UE. The UE is known in the MME and a mobility management connection for the UE may or may not be active. + +#### **8.7.1.2 LOCATION State** + +In this state, the MME is awaiting a response from an E-SMLC after requesting a location service for a particular UE. In this state, the UE is known in the MME and a Mobility Management connection to the UE is active. + +## 8.7.2 State Functionality + +### 8.7.2.1 State Transitions + +![State transition diagram for the MME showing two states: LCS-IDLE and LOCATION. Transitions are triggered by 'Request Location from the E-SMLC' (LCS-IDLE to LOCATION), 'Receive Location results from the E-SMLC or Timeout' (LOCATION to LCS-IDLE), and 'Transfer Positioning Messages' (self-loop on LOCATION).](cc6f9dbfc36aa5821d9749ca84861f93_img.jpg) + +``` + +stateDiagram-v2 + [*] --> LCS-IDLE + LCS-IDLE --> LOCATION : Request Location from the E-SMLC + LOCATION --> LCS-IDLE : Receive Location results from the E-SMLC or Timeout + LOCATION --> LOCATION : Transfer Positioning Messages + +``` + +State transition diagram for the MME showing two states: LCS-IDLE and LOCATION. Transitions are triggered by 'Request Location from the E-SMLC' (LCS-IDLE to LOCATION), 'Receive Location results from the E-SMLC or Timeout' (LOCATION to LCS-IDLE), and 'Transfer Positioning Messages' (self-loop on LOCATION). + +**Figure 8.4: State Transitions in the MME** + +#### Moving from LCS-IDLE to LOCATION state: + +After a request has been received for a particular location service for a particular UE and the UE subscription options have been verified where applicable to allow this, the MME sends a location request to an E-SMLC. The MME then enters the LOCATION state. Before entering this state, the MME must have setup a Mobility Management connection to the UE if none was previously active. + +#### Moving from LOCATION to LCS IDLE state: + +After the return of a location result from the E-SMLC, or if the Location Timer described below expires, the MME shall re-enter IDLE state. + +### 8.7.2.2 LOCATION Timer Function + +The MME runs a timer while in the LOCATION state, whose value may depend on the location service, to limit the amount of time waiting for a location response from the E-SMLC. If the timer expires before such information is received, the MME indicates a location failure to the original requesting entity and re-enters IDLE state. + +## 8.8 Signalling connection for the S1 interface + +Before the MME can request location information of a target UE from the E-SMLC, an S1 signalling connection must have been established between the MME and E-UTRAN. The MME sends a location request message to E-SMLC, which determines the location of the target UE related to this S1 signalling connection and sends a location measurement report to the MME. + +# 9 General Network Positioning Procedures + +The generic network positioning procedure of providing the location information of an UE subscriber can be partitioned into the following procedures. + +### Location Preparation Procedure + +This generic procedure is concerned with verifying the privacy restrictions of the UE subscriber, reserving network resources, communicating with the UE to be located and determining the positioning method to be used for locating the UE subscriber based on the requested QoS and the UE and network capabilities. + +#### **Positioning Measurement Establishment Procedure** + +This procedure is concerned with performing measurements by involving the necessary network and/or UE resources. Depending on the positioning method to be used for locating the UE the internals of this procedure can be positioning method dependent. The procedure is completed with the end of the positioning measurements. + +#### **Location Calculation and Release Procedure** + +This generic procedure is initiated after the measurements are completed and is concerned with calculating the location and optionally, velocity of the UE and releasing all network and/or UE resources involved in the positioning. + +Each of the following procedures defines the support of a single location request (MT-LR, MO-LR or NI-LR) that may be immediate or deferred. Treatment alternatives for a new location request when other concurrent location requests are already ongoing for the same target UE is not generally defined in these procedures except in certain specific cases. For such general treatment alternatives, refer to clause 4.5. + +## **9.1 Mobile Terminating Location Request** + +The MT-LR procedures for the location request from the LCS client which does not have the privacy override capability are described in the clause 9.1.1. + +The MT-LR procedures for the location request from the LCS client which has the privacy override capability (e.g. the request is come from the emergency service provider) are described in the clause 9.1.1A. In this case the H-GMLC is not involved to the location procedures and the privacy check procedures in H-GMLC/PPR are skipped. + +It is noted that R-GMLC or the UE may handle the periodicity of location requests as requested by the LCS client both in CS and PS domain. + +### 9.1.1 Common MT-LR procedure in PS and CS domain + +![Sequence diagram illustrating the General Network Positioning for a MT-LR procedure. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN/MME, RAN, and UE. The process involves sending a location service request, routing information, privacy checks, and final service responses.](e417ae35ab07134888be901c201d54cd_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC_R as GMLC (Requesting) + participant GMLC_H as GMLC (Home) + participant HLR_HSS as HLR/HSS + participant GMLC_V as GMLC (Visited) + participant MSC_SGSN_MME as MSC/SGSN/MME + participant RAN + participant UE + + Note right of GMLC_H: 5. Privacy check . + Note right of GMLC_H: 11. Privacy check . + Note right of GMLC_V: 9. MT-LR procedures for CS and PS domain . + Note right of GMLC_V: 13. Post positioning notification procedure for CS and PS domain + + Client->>GMLC_R: 1. LCS Service Request + GMLC_R->>HLR_HSS: 2. Send Routing Info for LCS + HLR_HSS-->>GMLC_R: 3. Send Routing Info for LCS ack + GMLC_R->>GMLC_H: 4. LCS Service Request + GMLC_H->>HLR_HSS: 6. Send Routing Info for LCS + HLR_HSS-->>GMLC_H: 7. Send Routing Info for LCS ack + GMLC_H->>GMLC_V: 8. LCS Service Request + GMLC_V->>GMLC_H: 10. LCS Service Response + GMLC_H->>GMLC_V: 12. LCS Service Request + GMLC_V->>GMLC_H: 14. LCS Service Response + GMLC_H->>GMLC_R: 15. LCS Service Response + GMLC_R->>Client: 16. LCS Service Response + +``` + +Sequence diagram illustrating the General Network Positioning for a MT-LR procedure. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN/MME, RAN, and UE. The process involves sending a location service request, routing information, privacy checks, and final service responses. + +**Figure 9.1: General Network Positioning for a MT-LR** + +- 1) An external LCS client requests the current location and optionally, velocity of a target UE from a GMLC. The LCS Client may also request a deferred location request, i.e. based on event. The R-GMLC verifies the identity of the LCS client and its subscription to the LCS service requested and derives the MSISDN or IMSI or pseudonym of the target UE to be located and the LCS QoS from either subscription data or data supplied by the LCS client. For a call related location request, the LCS client includes the LCS client's called party number, as dialled by the target mobile user, in the LCS service request. For a session related location request, the LCS client includes the APN-NI of the LCS client, as used by the target UE, in the LCS service request. For a call/session related request the R-GMLC may verify that the called party number or APN-NI is correct for the LCS client in question. The LCS client's dialled number or APN-NI are checked in step 9 for the call/session related class. + The LCS request may carry also the Service Identity and the Codeword and the service coverage information. The R-GMLC may verify that the Service Identity received in the LCS request matches one of the service identities allowed for the LCS client. If the service identity does not match one of the service identities for the LCS client, the R-GMLC shall reject the LCS request. Otherwise, the R-GMLC can map the received service identity in a corresponding service type. + If the location request is originated by a Requestor, the Requestor Identity may be added to the LCS service request. The LCS client should authenticate the Requestor Identity but this is outside the scope of this specification. The LCS service request may also contain the type of the Requestor identity if the requestor identity was included. + +If the H-GMLC address is not contained in the pseudonym or cannot be deduced from the pseudonym, the R-GMLC shall determine the verinym for the pseudonym. In this case the R-GMLC may access to its associated PMD as described in clause 9.1.1.3. + +The R-GMLC verifies whether it stores the privacy profile of the target UE. If the R-GMLC stores the UE's privacy profile, (this means the R-GMLC is the H-GMLC of the target UE), then step 2, 3, 4 and 12 are skipped. If location is required for more than one UE, the steps following below may be repeated and in that case the R-GMLC should verify whether the number of Target UEs in the LCS request is equal or less than the Maximum Target UE Number of the LCS client. If the Maximum Target UE Number is exceeded, the R-GMLC should respond to the client with proper error cause. If periodic location is requested, the steps following below may be repeated or the R-GMLC may forward the periodic location request to the UE, see clause 9.1.12. + +- 2) If the R-GMLC already knows, (e.g. from a previous location request or an internal lookup table), or is able to determine, (e.g. it is possible to use a DNS lookup mechanism similar to IETF RFC 2916), the network address of H-GMLC of the target UE, or in case the location service request contains the target UE's pseudonym, which includes the target UE's Home-GMLC address, or a pseudonym from which the target UE's Home-GMLC address can be deduced, then this step and step 3 may be skipped. + +Otherwise, the R-GMLC sends a SEND\_ROUTING\_INFO\_FOR\_LCS message to the home HLR/HSS of the target UE to be located with the IMSI or MSISDN of the UE. + +The details of the alternative methods of retrieving H-GMLC address other than the sending SEND\_ROUTING\_INFO\_FOR\_LCS message to the HLR/HSS, (e.g. internal lookup table, DNS lookup mechanism), are not in the scope of this specification. + +**Editor's note: The support for number portability with these alternative solutions of retrieving H-GMLC address still needs further study and should be in line with the general solution to support number portability in Rel-6.** + +- 3) The HLR/HSS verifies whether the R-GMLC is authorized to request UE location information. If not, an error response is returned. +Otherwise the HLR/HSS returns one or several of the network addresses of the current SGSN and/or VMSC/MSC server and/or current MME, the LCS capabilities of the serving nodes if available, the V-GMLC address associated with the serving nodes, if available and whichever of the IMSI and MSISDN that was not provided in step 2. The HLR/HSS returns the address of the H-GMLC. The HLR/HSS also returns the address of the PPR, if available. + +NOTE 1: HLR/HSS may prioritise between the MSC/VLR or SGSN or MME address sent to the GMLC. The prioritisation might be based on information received from SGSN and/or MSC/VLR and/or MME concerning the UE's capabilities for LCS. Other priority criteria are for further study. + +- 4) If R-GMLC finds out that it is the H-GMLC, the signalling steps 4 and 15 are skipped. +If the R-GMLC did not receive the H-GMLC address in step 3 and can not retrieve the H-GMLC address in some other way (e.g. DNS lookup), then steps 4, 5, 6, 7, 8, 10, 11, 12, 14 and 15 are skipped and the R-GMLC directly sends the PSL message to the serving node. +Otherwise, the R-GMLC sends the location request to the H-GMLC. If one or several of the network addresses of the current SGSN and/or VMSC/MSC server and/or current MME, the LCS core network signalling capabilities of the serving nodes, IMSI and MSISDN for the target UE and the address of the V-GMLC and the PPR have been retrieved in Step 3, the R-GMLC shall pass the information with the location request to the H-GMLC. The R-GMLC shall also send the service coverage information to the H-GMLC, if the information is available. +- 5) The H-GMLC verifies whether the R-GMLC is authorized to request UE location information. If the R-GMLC is not authorized, an error response is returned. +If the LCS service request contains the pseudonym of the target UE and the H-GMLC cannot resolve the PMD address from the pseudonym, the H-GMLC itself determines the verinym (MSISDN or IMSI) of the target UE. If the H-GMLC can resolve the address of PMD from the pseudonym, the H-GMLC requests the verinym from its associated PMD, see clause 9.1.1.3. In case H-GMLC knows that the PMD functionality is integrated in PPR, it can include the information from the LCS Identity Request in the LCS authorisation request to the PPR, see clause 9.1.1.1. In this case, if H-GMLC is not able to obtain the verinym of the target UE, the H-GMLC shall cancel the location request. +The H-GMLC performs privacy check on the basis of the UE user's privacy profile stored in the H-GMLC and the capabilities of the serving nodes (MSC/VLR and/or SGSN and/or MME), if available. If the privacy profile of the target UE is stored in a PPR and the H-GMLC received the network address of the PPR from R-GMLC or is able to determine the PPR address (e.g. from a previous location request or an internal lookup table), the H-GMLC shall ask the PPR to perform the privacy check as described in the 9.1.1.1. If the privacy profile is stored in a PPR but the network address of the PPR is not available, the H-GMLC shall send SRI for LCS message to + +HLR/HSS in step 6 in order to get the PPR address and the privacy check in this step shall be performed after step 7. Also if the key of the UE user's privacy profile (i.e. MSISDN or IMSI) is not available, the privacy check in this step shall be performed after step 7. The H-GMLC/PPR verifies LCS barring restrictions in the UE user's privacy profile in the H-GMLC/PPR. In verifying the barring restrictions, barring of the whole location request is assumed if any part of it is barred or any requisite condition is not satisfied. If the location service request is to be barred, GMLC shall terminate the request towards the R-GMLC or the LCS client with the appropriate error code. As a result of the privacy check, the H-GMLC/PPR selects one or two indicators of the privacy check related action and/or a pseudo-external identity in the case of interaction with a pre Rel-6 serving node. (The details of the indicator of the privacy check related action and the pseudo-external identity are described in clause 9.5.4 and Annex C). If the requested type of location is "current or last known location" and the requested maximum age of location information is available, the H-GMLC verifies whether it stores the previously obtained location estimate of the target UE. If the H-GMLC stores the location estimate and the location estimate satisfies the requested accuracy and the requested maximum age of location, the H-GMLC checks the result of the privacy check. In case the result of the privacy check for call/session unrelated class is "Location allowed without notification" then steps 6, 7, 8, 9 and 10 may be skipped. + +- 6) If the H-GMLC does not know IMSI for the particular MSISDN (e.g. from a previous location request), and the VMSC/MSC server address, SGSN address or MME address, the H-GMLC shall send a SEND\_ROUTING\_INFO\_FOR\_LCS message to the home HLR/HSS of the target UE to be located with the IMSI or MSISDN of this UE. Also if the privacy profile is stored in a PPR but the network address of the PPR was not available in the step 5, the H-GMLC shall send the SRI for LCS message to HLR/HSS. Otherwise, this step and step 7 may be skipped. +- 7) The HLR/HSS then returns one or several of the network addresses of the current SGSN and/or VMSC/MSC server and/or current MME, the LCS core network signalling capabilities of the serving nodes, the V-GMLC address associated with the serving nodes, if available, "Optimized Lgd" indicator if enabled according to the criteria in clause 5.7 and whichever of the IMSI and MSISDN that was not provided in step (6) for the particular UE. The HLR/HSS may also return the address of the PPR, if available. + +NOTE 2: HLR/HSS may prioritise between the MSC/VLR or SGSN or MME address sent to the GMLC. The prioritisation might be based on information received from SGSN and/or MSC/VLR and/or MME concerning the UE's capabilities for LCS. Other priority criteria are for further study. + +NOTE 3: If ISR is active for LTE access, the HSS may return the address of both the current MME and current SGSN. + +- 8) If step 6 and step 7 were performed, the H-GMLC/PPR may do a new privacy check, or if the privacy profile is stored in a PPR but the network address of the PPR was not available in step 5 and the PPR address is obtained in step 7, the H-GMLC shall ask the PPR to perform the privacy check as described in the 9.1.1.1. If the location request is an immediate location request and the service coverage information was sent from R-GMLC, the H-GMLC checks the country codes of the serving node addresses. If the H-GMLC finds out the current SGSN and/or VMSC/MSC server and/or current MME locates out of the service coverage, the H-GMLC returns an appropriate error message to the R-GMLC or the LCS client. In the cases when the H-GMLC did not receive the address of the V-GMLC, or when the V-GMLC address is the same as the H-GMLC address, or when both PLMN operators agree not to use the Lr interface, the H-GMLC does not send the location request to the V-GMLC and step 10 is skipped. In this case, the H-GMLC sends the location service request message to the serving node. If the H-GMLC received the address of the V-GMLC from the HLR/HSS and the V-GMLC address is different from the H-GMLC address, the H-GMLC may send the location request to the V-GMLC. The location request shall contain one or several of the network addresses of the current SGSN and/or MSC/VLR and/or current MME, and the IMSI and MSISDN of the target UE. The location request may also carry the requested action of the VPLMN as the result of the privacy check in the H-GMLC (i.e. by using the indicator of the privacy check related action as described in clause 9.5.4 or by using the pseudo-external identity as described in Annex C in the case of query to a pre Rel-6 serving node). If the result of privacy check indicates that the notification (and verification) based on current location is needed, the H-GMLC shall send a location request to the V-GMLC indicating "positioning allowed without notification" or, for backwards compatibility with a pre Rel-6 serving node, a pseudo external identity representing the same privacy notification and verification action required as for the "positioning allowed without notification" procedure as described in Annex C and V-GMLC shall send a Provide Subscriber Location message to the MSC/SGSN/MME indicating "positioning allowed without notification" or, for backwards compatibility with a pre Rel-6 serving node, a pseudo external identity representing the same privacy notification and verification action required as for the "positioning allowed without notification" procedure as described in Annex C. The V-GMLC first authenticates that the location request is allowed from this GMLC, PLMN or from this country. If not, an error response is returned. + +- 9) If the GMLC (H-GMLC, R-GMLC or V-GMLC) receives only the MSC/VLR address, the MT LR proceeds as the CS-MT-LR procedure described in clause 9.1.2. If the GMLC receives only the SGSN address, the MT LR proceeds as the PS-MT-LR procedure described in clause 9.1.6. If the GMLC receives only the MME address, the MT LR proceeds as the EPC-MT-LR procedure described in clause 9.1.15. If the GMLC receives several of the following addresses, SGSN, VMSC, MSC Server and/or MME, it has to decide where to send the location request. If the requested MT-LR is known to be associated with a CS call, the CS-MT-LR procedure shall be invoked. If the requested MT-LR is associated with a PS session in UTRAN, the PS-MT-LR procedure shall be invoked. If the requested MT-LR is associated with a PS session in E-UTRAN, the EPC-MT-LR procedure shall be invoked. Otherwise, two or more of CS-MT-LR, PS-MT-LR and EPC-MT-LR are applicable. If the GMLC has determined that PS-MT-LR and/or EPC-MT-LR procedures are to be executed then according to the criteria in clause 5.7 the GMLC shall set the "Optimized Lgd" indicator in the Provide Subscriber Location request procedure for either EPC-MT-LR or PS-MT-LR. In this case, GMLC shall only execute either EPC-MT-LR or PS-MT-LR procedure. If LCS Client indicated deferred location request, GMLC shall indicate this together with applicable event type (e.g. UE available) in the requested EPC/PS/CS-MT-LR, see clauses 9.1.8 and 9.1.15. + +NOTE 4: The order in which these procedures are invoked and whether one or both procedures are used may depend on information in the LCS service request, subscription information for the LCS client, possible priority information returned by the HSS or information already stored in the GMLC (e.g. obtained from previous location requests). The order may also depend on operator preference for invoking or not invoking location estimation on a particular access type when CSFB or ISR may be supported. + +NOTE 5: If ISR is active for LTE access, the V-GMLC receives both an SGSN and MME address. The VGMLC which hasn't received activation of Optimized Lgd procedures (see clause 5.7) from HSS and which doesn't support Optimized Lgd procedures (see clause 5.7), may then instigate both PS-MT-LR and EPC-MT-LR procedures. This will lead to separate paging of the UE in its registered TA(s) in association with the MME procedure and in its registered RA(s) in association with the SGSN procedure. The UE would then respond to only one paging request leading to continuation of only one of the MT-LR procedures and a termination of the other. The V-GMLC will discover which is which from the responses it later receives from the MME and SGSN for each MT-LR procedure. + +- 10) The V-GMLC sends the location service response to the H-GMLC in accordance with the requested LCS QoS Class. If the requested LCS QoS class was Assured, V-GMLC sends the result only if the result has been indicated to fulfil the requested accuracy, otherwise V-GMLC sends a LCS service response with a suitable error cause. If the UE requested LCS QoS class was Best Effort, V-GMLC sends whatever result it received with an appropriate indication if the requested accuracy was not met. The location service response may contain the information about the positioning method used. The V-GMLC may record charging information. + +- 11) If the privacy check in step 5 indicates that further privacy checks are needed, or on the basis of the privacy profile, the H-GMLC shall perform an additional privacy check or the H-GMLC may ask the PPR to perform the privacy check as described in the 9.1.1.1 in order to decide whether the H-GMLC can forward the location information to the LCS client or send a notification if the result of the privacy check requires the notification and verification based on current location. If the location request from the R-GMLC or the LCS client contained the pseudonym, the H-GMLC shall use the pseudonym of the target UE in the location response to the R-GMLC or the LCS client. One example when this additional privacy check is needed is when the target UE user has defined different privacy settings for different geographical locations. + +- 12) If the result of privacy checks in step 11 indicates that the notification (and verification) based on current location is needed, the H-GMLC shall send a location request to the V-GMLC indicating "notification only" or, for backwards compatibility with a pre Rel-6 serving node, a pseudo external identity representing the same privacy notification and verification action required as for the "notification only" procedure as described in Annex C. Otherwise this step and steps 13, 14 may be skipped. If the H-GMLC received the address of the V-GMLC from the HLR/HSS and the V-GMLC address is different from the H-GMLC address in step 8, the H-GMLC may send the location request to the V-GMLC. The location request shall contain one or several of the network addresses of the current SGSN and/or MSC/VLR and/or current MME, and the IMSI and MSISDN of the target UE. + +NOTE: The use of pseudo external identities in this step implies that a second positioning attempt is performed. + +- 13) If the GMLC (H-GMLC, R-GMLC or V-GMLC) received only the MSC/VLR address in step 9, the MT LR proceeds as the CS post positioning notification and verification procedure described in clause 9.1.10 or clause 9.1.2 if pseudo external identity is used. If the GMLC receives only the SGSN address in step 9, the MT LR proceeds as the PS post positioning notification and verification procedure described in clause 9.1.11 or clause 9.1.6 if pseudo external identity is used. If the GMLC receives only the MME address in step 9, the MT + +LR proceeds as the EPC post positioning notification and verification procedure described in clause 9.1.18. If the GMLC receives several of the following addresses, SGSN, VMSC, MSC Server and/or MME, it has to decide where to send the location request. If the requested MT-LR is known to be associated with a CS call, the CS post positioning notification and verification procedure shall be invoked. If the requested MT-LR is associated with a PS session in UTRAN, the PS post positioning notification and verification procedure shall be invoked. If the requested MT-LR is associated with a PS session in E-UTRAN, the EPC post positioning notification and verification procedure shall be invoked. Otherwise, CS and/or PS and/or EPC post positioning notification and verification procedure are applicable. + +- 14) The V-GMLC sends the location service response with an indication of the result of notification and verification procedure performed in step 13 to the H-GMLC. +- 15) The H-GMLC sends the location service response to the R-GMLC. The H-GMLC may store the location information and its age. The location service response may contain the information about the positioning method used and the indication whether the obtained location estimate satisfies the requested accuracy or not. The H-GMLC may record charging information. +- 16) R-GMLC sends the location service response to the LCS client. If the location request from the LCS client contained the pseudonym and the R-GMLC resolved the veronym from the pseudonym in the step 1, the R-GMLC shall use the pseudonym of the target UE in the location response to the LCS client. If the LCS client requires it, the R-GMLC may first transform the universal location co-ordinates provided by the SGSN or MSC/MSC server or MME into some local geographic system. The R-GMLC may record charging information both for the LCS client and inter-network revenue charges from the SGSN or MSC/MSC server or MME's network. The location service response from the R-GMLC to the LCS client may contain the information about the positioning method used and the indication whether the obtained location estimate satisfies the requested accuracy or not. + +The detailed CS-MT-LR, PS-MT-LR and EPC-MT-LR procedures in step 9 of figure 9.1 are described in clauses 9.1.2, 9.1.6 and 9.1.15. The detailed procedure for deferred PS/CS-MT-LR is described in clause 9.1.8. + +### 9.1.1A Common MT-LR procedure in PS and CS domain for Emergency MT-LR + +This clause describes how an emergency location request may be handled similarly to a normal location request. This method should be restricted to those countries where there is not a national requirement to provide location for callers who are either roaming or making a SIM-less emergency call, or making a non-registered (U)SIM emergency call. It is also appropriate to use this method to provide location for lawful intercept services where allowed by national regulation. + +![Sequence diagram for Network Positioning for an Emergency MT-LR. Lifelines: Client, GMLC (Requesting), HLR/HSS, GMLC (Visited), MSC/SGSN/MME, RAN, UE. The sequence starts with a 1. LCS Service Request from Client to GMLC (Requesting). GMLC (Requesting) sends 2. Send Routeing Info for LCS to HLR/HSS, which responds with 3. Send Routeing Info for LCS ack. GMLC (Requesting) then sends 4. LCS Service Request to GMLC (Visited). A block labeled 5. Common MT-LR procedures in CS and PS domain. follows, involving GMLC (Visited), MSC/SGSN/MME, RAN, and UE. GMLC (Visited) sends 6. LCS Service Response to GMLC (Requesting), which finally sends 7. LCS Service Response to the Client.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC_R as GMLC (Requesting) + participant HLR_HSS as HLR/HSS + participant GMLC_V as GMLC (Visited) + participant MSC_SGSN_MME as MSC/SGSN/MME + participant RAN + participant UE + + Client->>GMLC_R: 1. LCS Service Request + GMLC_R->>HLR_HSS: 2. Send Routeing Info for LCS + HLR_HSS-->>GMLC_R: 3. Send Routeing Info for LCS ack + GMLC_R->>GMLC_V: 4. LCS Service Request + rect rgb(255, 255, 255) + Note over GMLC_V, UE: 5. Common MT-LR procedures in CS and PS domain. + end + GMLC_V-->>GMLC_R: 6. LCS Service Response + GMLC_R-->>Client: 7. LCS Service Response + +``` + +Sequence diagram for Network Positioning for an Emergency MT-LR. Lifelines: Client, GMLC (Requesting), HLR/HSS, GMLC (Visited), MSC/SGSN/MME, RAN, UE. The sequence starts with a 1. LCS Service Request from Client to GMLC (Requesting). GMLC (Requesting) sends 2. Send Routeing Info for LCS to HLR/HSS, which responds with 3. Send Routeing Info for LCS ack. GMLC (Requesting) then sends 4. LCS Service Request to GMLC (Visited). A block labeled 5. Common MT-LR procedures in CS and PS domain. follows, involving GMLC (Visited), MSC/SGSN/MME, RAN, and UE. GMLC (Visited) sends 6. LCS Service Response to GMLC (Requesting), which finally sends 7. LCS Service Response to the Client. + +**Figure 9.1A: Network Positioning for an Emergency MT-LR** + +- 1) An external LCS client which has the privacy override capability, (e.g. Emergency service provider), requests the location of a target UE from a GMLC. The R-GMLC verifies the identity of the LCS client and its subscription to the LCS service requested and derives the MSISDN or IMSI of the target UE to be located and the LCS QoS from either subscription data or data supplied by the LCS client. +- 2) If the R-GMLC already knows IMSI for the particular MSISDN, (e.g. from a previous location request) and the VMSC/MSC server address, SGSN address or MME address, this step and step 3 may be skipped. Otherwise, the R-GMLC sends a SEND\_ROUTING\_INFO\_FOR\_LCS message to the home HLR/HSS of the target UE to be located with the IMSI or MSISDN of this UE. +- 3) The HLR/HSS verifies whether the R-GMLC is authorized to request UE location information. If not, an error response is returned. +Otherwise the HLR/HSS returns one or several of the network addresses of the current SGSN and/or VMSC/MSC server and/or current MME and whichever of the IMSI and MSISDN that was not provided in step 2. The HLR/HSS also returns the address of the V-GMLC associated with the serving nodes, if available. + +NOTE 1: HLR/HSS may prioritise between the MSC/VLR, SGSN or MME address sent to the GMLC. The prioritisation might be based on information received from SGSN and/or MSC/VLR and/or MME concerning the UE's capabilities for LCS. Other priority criteria are for further study. + +NOTE 2: If ISR is active for LTE access, the HSS may return the address of both the current MME and current SGSN. + +- 4) In the cases when the R-GMLC did not receive the address of the V-GMLC, or when the V-GMLC address is the same as the R-GMLC address, or when both PLMN operators agree not to use the Lr interface, the R-GMLC does not send the location request to the V-GMLC and the step 6 is skipped. In this case, the R-GMLC sends the location service request message directly to the serving node. +If the R-GMLC received the address of the V-GMLC from the HLR/HSS and the V-GMLC address is different from the R-GMLC address, the R-GMLC sends the location request to the V-GMLC. The location request shall contain one or several of the network addresses of the current SGSN and/or MSC/VLR, the IMSI and MSISDN of the target UE and the privacy override indicator. The V-GMLC first authenticates that the location request is allowed from this GMLC, PLMN or from this country. If not, the positioning request is rejected and an error response is returned. Otherwise, it sets the privacy indicator to "not allowed" and includes it with the POI in the Provide Subscriber Location message. +- 5) If the GMLC receives only the MSC/VLR address, the MT LR proceeds as the CS-MT-LR procedure described in clause 9.1.2. If the GMLC receives only the SGSN address, the MT LR proceeds as the PS-MT-LR procedure described in clause 9.1.6. + +described in clause 9.1.6. If the GMLC receives only the MME address, the MT LR proceeds as the EPC-MT-LR procedure described in clause 9.1.15. If the GMLC receives several of the following addresses, SGSN, VMSC, MSC Server and/or MME, it has to decide where to send the location request. In any case the serving node checks for POI applicability. + +NOTE: The order in which these procedures are invoked and whether one or both procedures are used may depend on information in the LCS service request, subscription information for the LCS client, possible priority information returned by the HLR/HSS or information already stored in the GMLC (e.g. obtained from previous location requests). + +- 6) The V-GMLC sends the location service response to the R-GMLC. The location service response may contain the information about the positioning method used. The V-GMLC may record charging information. +- 7) R-GMLC sends the location service response to the LCS client. If the LCS client requires it, the R-GMLC may first transform the universal location co-ordinates provided by the SGSN or MSC/ MSC server into some local geographic system. The location service response from the GMLC to the LCS client may contain the information about the positioning method used. After receiving (stage 3) acknowledgement from the LCS client, the R-GMLC may record charging information both for the LCS client and inter-network revenue charges from the SGSN or MSC/ MSC server's network. + +The detailed CS-MT-LR, PS-MT-LR and EPC-MT-LR procedures in step 5 of figure 9.1A are described in clauses 9.1.2, 9.1.6 and 9.1.15. + +#### 9.1.1.1 LCS Authorisation request + +If the UE subscribers LCS privacy information is kept in the PPR the GMLC (H-GMLC) shall send a LCS Authorisation request to PPR, see figure 9.1B. + +![Sequence diagram showing LCS authorisation in PPR. The GMLC sends a '1. LCS Authorisation Request' to the PPR, and the PPR responds with a '2. LCS Authorisation Response'.](820515db47ded68f5e0b625f4ec7d2c1_img.jpg) + +``` + +sequenceDiagram + participant GMLC + participant PPR + Note left of GMLC: GMLC + Note right of PPR: PPR + GMLC->>PPR: 1. LCS Authorisation Request + PPR-->>GMLC: 2. LCS Authorisation Response + +``` + +Sequence diagram showing LCS authorisation in PPR. The GMLC sends a '1. LCS Authorisation Request' to the PPR, and the PPR responds with a '2. LCS Authorisation Response'. + +**Figure 9.1B: LCS authorisation in PPR** + +- 1) The GMLC sends the LCS authorisation request to the PPR. The LCS authorisation request carries the type of location information requested (e.g. current location), the LCS client type, the UE subscriber's identity and indication whether the request is call/session related or call/session unrelated. The UE subscriber's identity can be one or both of MSISDN and IMSI. If PMD functionality is integrated in PPR, the LCS authorization request may carry the pseudonym of the target UE, instead of the verinum. In case GMLC received the LCS client's called party number or the APN-NI of the target mobile's session, GMLC shall request both call/session related and call/session unrelated privacy checks in PPR. In case GMLC did not receive the LCS client's called party number or the APN-NI of the target mobile's session, GMLC requests only a call/session unrelated privacy check in PPR. For a value added LCS client, the message shall carry the client's name, the external identity of the LCS client and the requestor identity (if that is both supported and available). Moreover the message may also carry the Service Type and the Codeword. This message shall also carry the LCS capabilities of the SGSN or VMSC/MSC server. + +In case the additional privacy check was requested to be performed after the positioning procedure the LCS Authorisation Request shall also include the location estimate. + +- 2) If the LCS authorization request contains the pseudonym of the target UE, the PPR with PMD functionality seeks to determine the verinum of the target UE. PPR performs the privacy check based on the target UE's privacy profile. The result of that privacy check is sent to GMLC in the LCS Authorisation response. If the location request is to be barred, the PPR shall send an indication of this within the LCS Authorisation response and no other indicators. If requested by the GMLC the PPR shall include two privacy check results for the LCS Authorisation response, both call/session related and call/session unrelated privacy check results. The response may also contain information if an additional privacy check is needed when the GMLC has received the location information of the target UE (e.g. if the target UE allows its location information to be given to the LCS client only when it is located in certain areas). + +If the LCS authorisation request contains the pseudonym of the target UE and the PPR has integrated PMD functionality, the PPR shall return the target UE's IMSI and/or MSISDN corresponding to the pseudonym in the LCS authorisation response. + +If PPR received information that the visited MSC/SGSN is pre Rel-6 it shall select a pseudo external ID which shall carry the response of the privacy check. For more information on pseudo external IDs, see Annex C. + +#### 9.1.1.2 LCS Privacy Profile Update + +If the UE subscribers privacy information has been changed in the PPR the LCS Privacy Profile Update shall be sent to the GMLC (H-GMLC), see figure 9.1C. + +![Sequence diagram showing PPR notification to GMLC about LCS privacy profile change.](4792a2ccd62226861fadc22117edb7b1_img.jpg) + +``` +sequenceDiagram + participant PPR + participant GMLC + Note right of PPR: 1. LCS privacy profile update notification + PPR->>GMLC: 1. LCS privacy profile update notification + Note left of GMLC: 2. LCS profile update notification ack. + GMLC->>PPR: 2. LCS profile update notification ack. +``` + +A sequence diagram illustrating the interaction between a PPR (Privacy Profile Repository) and a GMLC (Gateway Mobile Location Center). The PPR sends a message labeled '1. LCS privacy profile update notification' to the GMLC. The GMLC responds with a message labeled '2. LCS profile update notification ack.'. + +Sequence diagram showing PPR notification to GMLC about LCS privacy profile change. + +**Figure 9.1C: PPR notification to GMLC about LCS privacy profile change** + +- 1) In case subscriber changed his privacy profile information in the PPR the LCS Privacy Profile Update shall be sent to the GMLC (H-GMLC). The message shall carry the identity of the UE subscriber. +- 2) GMLC acknowledges that it received the notification + +#### 9.1.1.3 LCS identity request + +The GMLC may request the verinym of the UE from the PMD, see figure 9.1D. + +![Sequence diagram showing LCS identity request from GMLC to PMD.](0a12cc47f3c5ca76c39d5943ba8661bd_img.jpg) + +``` +sequenceDiagram + participant GMLC + participant PMD + Note right of GMLC: 1. Identity Request + GMLC->>PMD: 1. Identity Request + Note left of PMD: 2. Identity Response + PMD->>GMLC: 2. Identity Response +``` + +A sequence diagram illustrating the interaction between a GMLC (Gateway Mobile Location Center) and a PMD (Pseudonym Decryption). The GMLC sends a message labeled '1. Identity Request' to the PMD. The PMD responds with a message labeled '2. Identity Response'. + +Sequence diagram showing LCS identity request from GMLC to PMD. + +**Figure 9.1D: LCS identity request** + +- 1) The GMLC sends the pseudonym to its associated PMD and requests the corresponding verinym of the target UE from PMD. +- 2) The PMD shall map or decrypt (e.g. using the private key of the operator) the target UE's pseudonym to the corresponding verinym, i.e. IMSI and /or MSISDN, to be included in the Identity Response. + +### 9.1.2 Circuit Switched Mobile Terminating Location Request (CS-MT-LR) + +Figure 9.2 illustrates general network positioning for LCS clients external to the PLMN. In this scenario, it is assumed that the target UE is identified using either an MSISDN or IMSI. + +![Sequence diagram for Network Positioning for a CS-MT-LR. Lifelines: Client, GMLC, HLR/HSS, VMSC/MSC SERVER, RAN, UE. The diagram shows a 10-step process involving common MT-LR procedures, subscriber location provision, UE paging, LCS location notification, location requests, individual positioning messages, and location reports.](69edc2887e907309499ac95b47ab6905_img.jpg) + +``` +sequenceDiagram + participant Client + participant GMLC + participant HLR/HSS + participant VMSC/MSC SERVER + participant RAN + participant UE + + Note over Client, HLR/HSS: 1. Common MT-LR procedure in CS and PS domain + GMLC->>VMSC/MSC SERVER: 2. Provide Subscriber Location + VMSC/MSC SERVER->>UE: 3. UE Paging, Authentication, Ciphering + VMSC/MSC SERVER->>UE: 4. LCS Location Notification Invoke + UE->>VMSC/MSC SERVER: 5. LCS Location Notification Return Result + VMSC/MSC SERVER->>RAN: 6. Location Request + Note over RAN, UE: 7. Messages for individual positioning methods + RAN->>VMSC/MSC SERVER: 8. Location Report + VMSC/MSC SERVER->>GMLC: 9. Provide Su bscrber Location ack. + Note over Client, HLR/HSS: 10. Common MT-LR procedure in CS and PS domain +``` + +Sequence diagram for Network Positioning for a CS-MT-LR. Lifelines: Client, GMLC, HLR/HSS, VMSC/MSC SERVER, RAN, UE. The diagram shows a 10-step process involving common MT-LR procedures, subscriber location provision, UE paging, LCS location notification, location requests, individual positioning messages, and location reports. + +Figure 9.2: Network Positioning for a CS-MT-LR + +#### 9.1.2.1 Location Preparation Procedure + +- 1) Common PS and CS MT-LR procedure as described in clause 9.1.1. +- 2) The GMLC sends a PROVIDE\_SUBSCRIBER\_LOCATION message to the MSC/MSC server indicated by the HLR/HSS. This message carries the type of location information requested (e.g. current location and optionally, velocity), the UE subscriber's IMSI, LCS QoS information (e.g. accuracy, response time) and an indication of whether the LCS client has the override capability. For a call related location request, the message also carries the LCS client's called party number. For a value added LCS client, the message shall carry the client name, the external identity of the LCS client (or the pseudo external identity) and the Requestor Identity (if that is both supported and available). Also the message may carry the type of the LCS client name and also the type of the Requestor identity if the requestor identity was included. For a PLMN operator LCS client, the message shall carry the internal identity of the LCS client. Moreover the message may also carry the Service Type. If the result of the privacy check at H-GMLC/PPR indicated that the codeword shall be sent to the UE user, the message may carry also the codeword received from the LCS client. For a PLMN operator LCS client, the message shall carry the internal identity of the LCS client. If the Requestor Identity is provided, the GMLC shall send it as separate information. In addition, in order to display the requestor identity in case of pre rel-5 network elements (i.e. MSC and/or UE), the requestor identity may be also added to the LCS client name by the GMLC. When the Requestor identity is added to the LCS client name the practise described in the Annex D should be followed. The message also shall carry the indicators of privacy related action which is described in clause 9.5.4 , if it is provided by H-GMLC. +- 3) If the GMLC is located in another PLMN or another country, the VMSC/MSC server first authenticates that a location request is allowed from this PLMN or from this country. If not, an error response is returned. If the PSL message from the GMLC contains the indicators of privacy related action, the VMSC/MSC server determines a required privacy related action as described in Annex A.3. If the PSL message from the GMLC does not include the indicators of privacy related action, the VMSC/MSC server then verifies LCS barring restrictions in the UE user's subscription profile in the MSC server. In verifying the barring restrictions, barring of the whole location request is assumed if any part of it is barred or any requisite condition is not satisfied. If LCS is to be barred without notifying the target UE and a LCS client accessing a GMLC in the same country does not have the override capability, an error response is returned to the GMLC. +Otherwise, if the UE is in idle mode, the Core Network performs paging, authentication and ciphering. The MSC will page a GPRS attached UE either through A/Iu or Gs interface, depending on the presence of the Gs interface (see Note 2). The UE will inform the network about its LCS capabilities, as described in clause 6.3.4. If the UE is instead in dedicated mode, the VMSC/MSC server will already have UE classmark information. In GSM this is supported by controlled early classmark sending. + +NOTE 1: In GSM, if the target UE has an established circuit call other than speech, the location request may be denied and an error response is then returned to the GMLC. If the location request is allowed for a non-speech circuit call, it shall be up to RAN to decide, on the basis of the applicable position methods and requested QoS, whether positioning is possible. + +NOTE 2: In some network mode of operation, a GPRS capable UE may not receive the CS paging. In addition, upon receipt of a CS paging, a GPRS capable UE may immediately answer to the Paging Request or delay the answer, as defined in TS 22.060 [35b] and TS 23.060 [15]. A GPRS UE in class B mode may also suspend its GPRS traffic, sending a GPRS Suspension Request to the network. + +- 4) If the location request comes from a value added LCS client and the indication of requested privacy related action or the UE subscription profile indicates that the UE must either be notified or notified with privacy verification and the UE supports notification of LCS (according to the UE Capability information), an LCS Location Notification Invoke message is sent to the target UE indicating the type of location request from the LCS Client (e.g. current location or "current or last known location") and the identity of the LCS client, the Requestor Identity (if that is both supported and available) and whether privacy verification is required. Also the message may indicate the type of the LCS client name and also the type of the Requestor identity if the requestor identity was included. Moreover, the message may carry also the service type and the codeword. Optionally, the VMSC/MSC server may, after sending the LCS Location Notification Invoke message continue in parallel the location process, i.e. continue to step 6 without waiting for a LCS Location Notification Return Result message in step 5. + +NOTE 3: It is for further study, if all available client identities are to be included in the Privacy Notification message to be shown to the end-user. + +- 5) The target UE notifies the UE user of the location request. If privacy verification was requested, the target UE indicates to the UE user whether the location request will be allowed or not allowed in the absence of a response and waits for the user to grant or withhold permission. The UE then returns an LCS Location Notification Return Result to the VMSC/MSC server indicating, if privacy verification was requested, whether permission is granted or denied. Optionally, the LCS Location Notification Return Result message can be returned some time after step 4, but before step 9. If the UE user does not respond after a predetermined time period, the VMSC/MSC server shall infer a "no response" condition. The VMSC/MSC server shall return an error response to the GMLC if privacy verification was requested and either the UE user denies permission or there is no response with the UE subscription profile indicating barring of the location request in the absence of a response. +- 6) The MSC/MSC server sends a Location Request message to RAN. This message includes the type of location information requested and requested QoS and, in GSM, the UE's location capabilities. + +#### 9.1.2.2 Positioning Measurement Establishment Procedure + +- 7) RAN determines the positioning method and instigates the particular message sequence for this method, as specified in UTRAN Stage 2, TS 25.305 [1] and GERAN Stage 2, TS 43.059 [16]. + +#### 9.1.2.3 Location Calculation and Release Procedure + +- 8) When a location estimate best satisfying the requested QoS has been obtained, RAN returns it to the MSC/MSC server in a Location Report message. RAN shall in its response include an indication whether the obtained location estimate satisfies the requested accuracy or not. The information about the positioning method used may be returned with the location estimate. If a location estimate could not be obtained, RAN returns a Location Report message containing a failure cause and no location estimate. +- 9) The MSC/MSC server returns the location information, its age and obtained accuracy indication to the GMLC, if the VMSC/MSC server has not initiated the Privacy Verification process in step 4. If step 4 has been performed for privacy verification, the VMSC/MSC server returns the location information only, if it has received a LCS Location Notification Return Result indicating that permission is granted. In these cases, the information about the positioning method used may be sent with the location information. If a LCS Location Notification Return Result message indicating that permission is not granted is received, or there is no response, with the requested privacy action or the UE subscription profile indicating barring of location in the absence of a response, the VMSC/MSC server shall return an error response to the GMLC. If RAN did not return a successful location estimate, but the privacy checks in steps 4 - 5 were successfully executed, the VMSC/MSC server may return the last known location of the target UE if this is known and the LCS client is requesting the current or last known location. The MSC/MSC server may then release the Mobility Management connection to the UE, if the UE was previously idle, and the MSC/MSC server may record charging information. + +10) Common MT-LR procedure in PS and CS domain as described in clause 9.1.1. + +### 9.1.3 CS-MT-LR without HLR Query + +Figure 9.3 illustrates current or last known location requests for an emergency services call, where an emergency services client (i.e., a Public Safety Answering Point) identifies the target UE and the serving GMLC using correlation information that were previously provided to it by the VMSC. In North America, this correlation information is provided by either an NA-ESRK, or an MSISDN and NA-ESRD. In E.U. it is provided through the ISUP/BICC IAM message with location number parameter set to MSC number and the calling party number parameter set to MSISDN. The signalling used to provide the correlation information to the PSAP is out of scope of this TS, but is presumed to occur on the signalling for the call. This allows the requesting V-GMLC to request location from the VMSC without first querying the home HLR of the target UE. This scenario therefore supports location of emergency callers from roamers or SIM-less emergency calls, or non-registered (U)SIM emergency calls, and requires that the initial location, as well as UE and VMSC identifying information had been pushed to the GMLC as per 9.1.5 (or 9.1.5.A for North America). In North America, additional requirements are found in [32]. + +![Sequence diagram for Positioning for an Emergency Services MT-LR without HLR Query. The diagram shows interactions between Client, GMLC, HLR/HSS, VMSC/MSC SERVER, RAN, and UE.](88b0f3f4393228e9ea4d6542aef7c399_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC + participant HLR/HSS + participant VMSC/MSC SERVER + participant RAN + participant UE + + Client->>GMLC: 1. LCS Service Request + GMLC->>VMSC/MSC SERVER: 2. Provide Subscriber Location + VMSC/MSC SERVER->>RAN: 3. Location Request + Note over RAN,UE: 4. Messages for individual positioning methods + RAN->>UE: + UE->>RAN: + RAN->>VMSC/MSC SERVER: 5. Location Report + VMSC/MSC SERVER->>GMLC: 6. Provide Subscriber Location ack. + GMLC->>Client: 7. LCS Service Response + +``` + +Sequence diagram for Positioning for an Emergency Services MT-LR without HLR Query. The diagram shows interactions between Client, GMLC, HLR/HSS, VMSC/MSC SERVER, RAN, and UE. + +**Figure 9.3: Positioning for an Emergency Services MT-LR without HLR Query** + +- 1) Same as step 1 in figure 9.1 but with the LCS client (PSAP) identifying first the target UE and the serving V-GMLC by previously supplied correlation information for the emergency call. +- 2) The GMLC may determine the VMSC from correlation information received from the PSAP, or from stored information for the target UE (e.g. from a prior location estimate delivery from the VMSC/MSC server). In North America, the GMLC determines the VMSC using the NA-ESRK or NA-ESRD - with use of the NA-ESRK taking priority over that of the NA-ESRD. The MAP\_PROVIDE\_SUBSCRIBER\_LOCATION message sent to the VMSC carries the MSISDN and, if provided, the IMSI and IMEI for the target UE, as well as the required QoS and an indication of a location request from an emergency services client. The VMSC identifies the target UE using the IMSI or MSISDN and, if provided, the IMEI. In case of a SIM-less emergency call, or non-registered (U)SIM emergency call, the IMEI shall be always sent and the MSISDN may be populated with a non-dialable callback number as specified in clause 6.4.3. +- 3) The MSC verifies that UE privacy is overridden by the emergency services provider and that positioning is not prevented for other reasons (e.g. unreachable UE, inapplicable call type to the UE). The VMSC then sends a Location Request to the RAN, as for a normal MT-LR. +- 4) RAN performs positioning as for a normal CS-MT-LR. +- 5) RAN returns a location estimate to the VMSC as for a normal CS-MT-LR. +- 6) Same as step 9 for a normal CS-MT-LR. +- 7) Same as step 10 for a normal CS-MT-LR. + +### 9.1.4 CS-MT-LR and PS-MT-LR for a previously obtained location estimate + +Every time the location estimate of a target UE subscriber is returned by the RAN to the VMSC, MSC Server or SGSN, the corresponding entity may store the location estimate together with a time stamp. The MSC/MSC server may store this information in the subscriber's MSC server record. Also when the location estimate of a target UE subscriber is returned to the H-GMLC, the H-GMLC may store the location estimate together with the age in the subscriber's record. + +The time stamp is the time at which the location estimate is stored at the corresponding entity i.e. after the RAN returns the location estimate to the VMSC, MSC Server or SGSN. The time stamp indicates the "age" of the location estimate. + +#### 9.1.4.1 Initial Location + +In the context of an originating emergency call the location estimate and the associated time stamp at the commencement of the call set-up is referred to as "*initial location*". + +#### 9.1.4.2 Current Location + +After a location attempt has successfully delivered a location estimate and its associated time stamp, the location estimate and time stamp is referred to as the "*current location*" at that point in time. + +#### 9.1.4.3 Last known Location + +Depending on national regulations, the current location estimate and its associated time stamp may be stored in MSC/VLR, MSC Server, SGSN, or in H-GMLC and until replaced by a later location estimate and a new time stamp is referred to as the "*last known location*". The last known location may be distinct from the initial location - i.e. more recent. + +#### 9.1.4.4 Security and Privacy + +The collection and/or the release of the last known and initial location estimate of the target UE may not be allowed by national option. The handling of security and privacy of the target UE with regard to returning the last known or initial location estimate of the target UE shall be the same as when the target UE is reachable for positioning. (i.e. the requesting LCS client is authorized and the privacy of the target UE is secured before the VMSC/MSC server check the MSC server status of the target UE (i.e. whether the UE is marked as attached or detached in the MSC server). A similar status check apply for SGSN and MSC Server. + +#### 9.1.4.5 Failing to locate the target UE + +In case of a "Detached" or "Not Reachable" target UE, the last known location and a time stamp stored at the VLR, MSC Server or SGSN, may be returned to a LCS client requesting location information if the LCS client specifically requested the current or last known location. This does not apply to a value added LCS client where the target UE subscribes to notification of the location request: if the notification cannot be performed, the VMSC, MSC Server or SGSN shall reject the location request. + +NOTE: Due to CAMEL, the MSC/MSC server/VLR may already be storing other location information parameters like location number, service area identity and MSC server number in the subscriber's MSC server record. + +When a request for location information is received at the VMSC, MSC Server or SGSN, the request shall indicate whether the "last known location of the target UE" should be returned in case of a "detached" or "not reachable" target UE. + +If the VLR, MSC Server or SGSN has a valid copy of the subscriber's permanent data and the target UE's privacy settings are such that positioning is allowed, then the following two cases can occur. + +##### 9.1.4.5.1 Target UE is "Not Reachable" + +If the target UE is marked as "attached" in the VLR, MSC Server or SGSN, the corresponding entity orders paging of the target UE. If paging fails, due to target UE being "not reachable" then the corresponding VMSC, MSC Server or SGSN shall check whether the LCS client has requested "last known location" in case of "not reachable" target UE. + +If such a request exists and notification to the target UE does not apply for a value added LCS client, the VMSC, MSC Server or SGSN shall include the last known location together with the time stamp available in its response to the request for location information. + +An indicator of "last known location" returned shall be marked at the CDR at VMSC, MSC Server or SGSN correspondingly. + +##### 9.1.4.5.2 Target UE is "Detached" + +If the target UE is marked as "detached" in the VLR, MSC Server or SGSN, the corresponding entity shall check whether the LCS client has requested "last known location" in case of "detached" target UE. + +If such a request exists and notification to the target UE does not apply for a value added LCS client, the VMSC, MSC Server or SGSN includes the "last known location" together with the time stamp available in its response to the request for location information. + +An indicator of "last known location" returned shall be marked at the CDR at VMSC, MSC Server or SGSN. + +##### 9.1.4.5.3 Target UE is Reachable but Positioning Fails + +If the target UE is reachable (e.g. paging succeeds), but the VMSC, MSC Server or SGSN is unable to obtain a current location estimate, then the corresponding entity shall check whether the LCS client has requested "last known location". + +If such a request exists and notification to the target UE either does not apply or was successfully executed for a value added LCS client, the VMSC, MSC Server or SGSN includes the "last known location" together with the time stamp available in its response to the request for location information. An indicator of "last known location" returned shall be marked at the CDR at VMSC. + +##### 9.1.4.5.4 MSC Server or SGSN Target UE is "Purged" + +If the target UE is marked as "Purged" in HLR/HSS, then an indication "Absent Subscriber" is returned to the GMLC. + +### 9.1.5 Network Induced Location Request (NI-LR) + +Figure 9.4 illustrates how the initial position for an emergency service call is determined when the subscriber initiates the emergency call. + +![Sequence diagram for Figure 9.4: Positioning for a NI-LR Emergency Service Call. The diagram shows the interaction between LCS Client, GMLC, HLR/HSS, VMSC/MSC Server, RAN, and UE. The sequence starts with the UE sending a CM Service Request to the RAN, which is then forwarded to the VMSC/MSC Server. The VMSC/MSC Server sends an Emergency Call Origination message to the UE. The VMSC/MSC Server also sends a Location Request to the RAN. The RAN then sends messages for individual positioning methods to the UE. The UE sends a Location Report back to the RAN, which is then forwarded to the VMSC/MSC Server. The VMSC/MSC Server sends a MAP Subscriber Location Report to the GMLC, which in turn sends a MAP Subscriber Location Report ack back to the VMSC/MSC Server. The VMSC/MSC Server then sends a Location Information message to the LCS Client. The VMSC/MSC Server also sends an Emergency Call Release message to the UE. Finally, the VMSC/MSC Server sends a MAP Subscriber Location Report to the GMLC, which in turn sends a MAP Subscriber Location Report ack back to the VMSC/MSC Server.](367926125450c2bc3f4bdca9d59a62ba_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant VMSC/MSC Server + participant HLR/HSS + participant GMLC + participant LCS Client + + Note right of RAN: 5. Messages for individual positioning methods + + UE->>RAN: 1. CM Service Request + RAN->>VMSC/MSC Server: 2. (CM Service Request) + VMSC/MSC Server->>UE: 3. Emergency Call Origination + VMSC/MSC Server->>RAN: 4. Location Request + Note right of RAN: 5. Messages for individual positioning methods + RAN->>VMSC/MSC Server: 6. Location Report + VMSC/MSC Server->>GMLC: 7. MAP Subscriber Location Report + GMLC->>VMSC/MSC Server: 8. MAP Subscriber Location Report ack + VMSC/MSC Server->>LCS Client: 9. Location Information + VMSC/MSC Server->>UE: 10. Emergency Call Release + VMSC/MSC Server->>GMLC: 11. MAP Subscriber Location Report + GMLC->>VMSC/MSC Server: 12. MAP Subscriber Location Report ack + +``` + +Sequence diagram for Figure 9.4: Positioning for a NI-LR Emergency Service Call. The diagram shows the interaction between LCS Client, GMLC, HLR/HSS, VMSC/MSC Server, RAN, and UE. The sequence starts with the UE sending a CM Service Request to the RAN, which is then forwarded to the VMSC/MSC Server. The VMSC/MSC Server sends an Emergency Call Origination message to the UE. The VMSC/MSC Server also sends a Location Request to the RAN. The RAN then sends messages for individual positioning methods to the UE. The UE sends a Location Report back to the RAN, which is then forwarded to the VMSC/MSC Server. The VMSC/MSC Server sends a MAP Subscriber Location Report to the GMLC, which in turn sends a MAP Subscriber Location Report ack back to the VMSC/MSC Server. The VMSC/MSC Server then sends a Location Information message to the LCS Client. The VMSC/MSC Server also sends an Emergency Call Release message to the UE. Finally, the VMSC/MSC Server sends a MAP Subscriber Location Report to the GMLC, which in turn sends a MAP Subscriber Location Report ack back to the VMSC/MSC Server. + +**Figure 9.4: Positioning for a NI-LR Emergency Service Call** + +#### 9.1.5.1 Location Preparation Procedure + +- 1) An initially idle UE requests radio connection setup indicating a request for an Emergency Service call to the VMSC/MSC server via RAN. +- 2) RAN shall convey the CM service request to the core network. (Before having a CM connection there must be a radio connection.) The UE may identify itself using a TMSI, IMSI or IMEI. +- 3) The emergency call procedure is applied. The VMSC/MSC server determines based on the serving cell the appropriate emergency services client. The VMSC/MSC server, RAN and UE continue the normal procedure for emergency call origination towards that emergency services client. Depending on local regulatory requirements, the sending of call setup information into the PSTN may be delayed until either the UE's location has been obtained or the location attempt has failed or a PLMN defined timer has expired before location was obtained. If the serving cell serves an area that contains the service domain of multiple emergency services clients, the VMSC/MSC server may delay call setup and invoke location based routing procedures described in clause 9.1.5A. Call setup information sent into the PSTN may include the UE location (if already obtained) plus information that will enable the emergency service provider to request UE location at a later time (e.g. NA-ESRD or NA-ESRK in North America, or the ISUP/BICC IAM message with location number parameter set to MSC number and the calling party parameter set to MSISDN, in E.U.). + +- 4) At any time after step 2, the VMSC/MSC server may initiate procedures to obtain the UE's location and optionally, velocity. These procedures may run in parallel with the emergency call origination. The VMSC/MSC server sends a Location Request message to RAN associated with the UE's current location area (see step 6 for a MT-LR). This message includes the QoS required for an emergency call. + +#### 9.1.5.2 Positioning Measurement Establishment Procedure + +- 5) RAN determines the positioning method and instigates the particular message sequence for this method, as specified in UTRAN Stage 2, TS 25.305 [1] and GERAN Stage 2, TS 43.059 [16]. + +#### 9.1.5.3 Location Calculation and Release Procedure + +- 6) When a location estimate best satisfying the requested QoS has been obtained, RAN returns it to the VMSC/MSC server in a Location Report. As a national option, Cell ID positioning accuracy is allowed. RAN shall in its response include an indication whether the obtained location estimate satisfies the requested accuracy or not. The information of the positioning method used may be returned with the location estimate. If a location estimate could not be obtained, the RAN returns a location response containing a failure cause and no location estimate. +- 7) Depending on local regulatory requirements, the VMSC/MSC server may send a MAP Subscriber Location report to a GMLC associated with the emergency services provider to which the emergency call has been or will be sent. This message shall carry any location estimate returned in step 6 including the indication received from RAN whether the obtained location estimate satisfies the requested accuracy or not, the age of this estimate and may carry the MSISDN, IMSI and IMEI of the calling UE, the information about the positioning method used and the serving cell identity or SAI of the UE. In case of a SIM-less emergency call, or a non-registered (U)SIM emergency call, the IMEI shall be always sent and the MSISDN may be populated with a non-dialable callback number as specified in clause 6.4.3. In North America, any NA-ESRD and any NA-ESRK that may have been assigned by the VMSC/MSC server shall be included. In the E.U. the VMSC/MSC Server shall provide the identity of the PSAP to which the emergency call was connected. The message shall also indicate the event that triggered the location report. If location failed (i.e. an error result was returned by RAN in step 6), an indication of failure rather than a location estimate may be sent to the GMLC: the indication of failure is conveyed by not including a location estimate in the MAP Subscriber Location Report. The MSC/MSC server may record charging information. +- 8) The GMLC acknowledges receipt of the location information. The GMLC shall store the location information for later retrieval by the emergency services LCS client. +- 9) The GMLC may optionally forward the information received in step 8 to the emergency services LCS client. The GMLC may also record charging information. The client is expected to obtain the location information by requesting it from the GMLC. The information about the positioning method used may be sent with the location information from the GMLC to the LCS client. +- 10) At some later time, the emergency services call is released. +- 11) The MSC/MSC server sends another MAP Subscriber Location Report to the GMLC. This message may include the same parameters as before except that there is no position estimate and an indication of emergency call termination is included. +- 12) The GMLC acknowledges the MSC/MSC server notification and may then delete all information previously stored for the emergency call per national regulation. + +### 9.1.5A NI-LR using Location Based Routing – applicable to North American Emergency Calls only + +Figure 9.4A illustrates positioning for an emergency service call using location based routing. + +![Sequence diagram for NI-LR Emergency Service Call using Location Based Routing](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +``` +sequenceDiagram + participant Client + participant GMLC + participant VMSC/MSC SERVER + participant RAN + participant UE + + Note right of UE: 1. CM Service Request + UE->>RAN: 1. CM Service Request + RAN->>VMSC/MSC SERVER: 2. (CM Service Request) + VMSC/MSC SERVER->>RAN: 3. Location Request + Note right of RAN: 4. Messages for individual positioning methods + RAN->>VMSC/MSC SERVER: 5. Location Report + VMSC/MSC SERVER->>GMLC: 6. MAP Subscriber Location Report + GMLC->>VMSC/MSC SERVER: 7. MAP Subscriber Location Report ack + Note right of Client: 8. Emergency Call Origination + Client->>UE: 8. Emergency Call Origination + Client->>GMLC: 9. Request for Location Information + GMLC->>VMSC/MSC SERVER: 10. Provide Subscriber Location + VMSC/MSC SERVER->>RAN: 11. Location Request + Note right of RAN: 12. Messages for individual positioning methods + RAN->>VMSC/MSC SERVER: 13. Location Report + VMSC/MSC SERVER->>GMLC: 14. Provide Subscriber Location ack + GMLC->>Client: 15. Location Information + Note right of Client: 16. Emergency Call Release + Client->>UE: 16. Emergency Call Release + VMSC/MSC SERVER->>GMLC: 17. MAP Subscriber Location Report + GMLC->>VMSC/MSC SERVER: 18. MAP Subscriber Location Report ack +``` + +The sequence diagram illustrates the interaction between five entities: Client, GMLC, VMSC/MSC SERVER, RAN, and UE. The process begins with the UE sending a 'CM Service Request' to the RAN. The RAN then forwards this to the VMSC/MSC SERVER as '(CM Service Request)'. The VMSC/MSC SERVER sends a 'Location Request' to the RAN. The RAN performs 'Messages for individual positioning methods' and returns a 'Location Report' to the VMSC/MSC SERVER. The VMSC/MSC SERVER then sends a 'MAP Subscriber Location Report' to the GMLC, which responds with 'MAP Subscriber Location Report ack'. The Client sends an 'Emergency Call Origination' to the UE and a 'Request for Location Information' to the GMLC. The GMLC sends 'Provide Subscriber Location' to the VMSC/MSC SERVER. The VMSC/MSC SERVER sends another 'Location Request' to the RAN. The RAN again performs 'Messages for individual positioning methods' and returns a 'Location Report' to the VMSC/MSC SERVER. The VMSC/MSC SERVER sends 'Provide Subscriber Location ack' to the GMLC, which in turn sends 'Location Information' to the Client. Finally, the Client sends an 'Emergency Call Release' to the UE. The VMSC/MSC SERVER sends a 'MAP Subscriber Location Report' to the GMLC, which responds with 'MAP Subscriber Location Report ack'. + +Sequence diagram for NI-LR Emergency Service Call using Location Based Routing + +Figure 9.4A: Positioning for a NI-LR Emergency Service Call using Location Based Routing + +#### 9.1.5A.1 Location Preparation Procedure + +- 1) An initially idle UE requests radio connection setup indicating a request for an Emergency Service call to the VMSC/MSC server via RAN. +- 2) RAN shall convey the CM service request to the core network. (Before having a CM connection there must be a radio connection.) The UE may identify itself using a TMSI, IMSI or IMEI. +- 3) The VMSC/MSC server determines that the serving cell serves an area that contains portions of multiple emergency services zones. Therefore, the VMSC/MSC server delays call setup and initiates procedures to obtain the UE's location for routing the emergency call to the emergency services LCS client. The VMSC/MSC server sends a Location Request message to RAN associated with the UE's current location area. This message includes the type of location information requested, the UE's location capabilities and a QoS with low delay and low horizontal accuracy. + +#### 9.1.5A.2 Positioning Measurement Establishment Procedure + +- 4) RAN determines the positioning method and instigates the particular message sequence for this method, as specified in UTRAN Stage 2, TS 25.305 [1] and GERAN Stage 2, TS 43.059 [16]. + +#### 9.1.5A.3 Location Calculation and Release Procedure + +- 5) When a location estimate best satisfying the requested QoS has been obtained, RAN returns it to the VMSC/MSC server. If a location estimate could not be obtained, the RAN returns a location response containing a failure cause and no location estimate. If a failure is received, the VMSC/MSC server initiates emergency call setup using the normal NI-LR procedures. +- 6) The VMSC/MSC server sends a MAP Subscriber Location Report to a GMLC associated with the emergency services provider to which the emergency call will be sent. This message shall carry any location estimate returned in step 5, the age of this estimate and may carry the MSISDN, IMSI, IMEI of the calling UE, the information about the positioning method used and the serving cell identity or SAI of the UE. In case of a SIM-less emergency call, or a non-registered (U)SIM emergency call, the IMEI shall be always sent and the MSISDN shall be populated with a non-dialable callback number as specified in clause 6.4.3. The message shall also indicate the event that triggered the location report. Any NA-ESRD and NA-ESRK that was assigned by the VMSC/MSC server shall be included. The message shall also include an indication that the VMSC/MSC server supports the capability to replace an NA-ESRK or NA-ESRD value with the one assigned by the GMLC. The VMSC/MSC server and GMLC may record charging information. +- 7) The GMLC translates the location estimate into a zone identity and assigns either a NA-ESRK or a NA-ESRD, which was requested by the VMSC/MSC server. The GMLC shall include either the NA-ESRK value or the NA-ESRD value in the MAP Subscriber Location Report ack and send it to the VMSC/MSC server. The GMLC stores either the assigned NA-ESRD or the assigned NA-ESRK and any NA-ESRD that was sent by the VMSC/MSC server in step 6. + +#### 9.1.5A.4 Location Preparation Procedure + +- 8) The emergency call procedure is applied. The VMSC/MSC server, RAN and UE continue the normal procedure for emergency call origination towards the appropriate emergency services client. Call setup information sent into the PSTN may include the UE location plus information that will enable the emergency service provider to request UE location at a later time (NA-ESRD or NA-ESRK in North America). The NA-ESRK or NA-ESRD used shall be the one received from the GMLC. If a NA-ESRK or NA-ESRD is not received from the GMLC then the VMSC/MSC server shall employ default routing for the call using a default NA-ESRK, default NA-ESRD or other default number as in clause 9.1.5.1 step 3. +- 9) At any time after step 8, the emergency services LCS client may request location information. +- 10) At any time after step 6, the GMLC may send a MAP Provide Subscriber Location message to the VMSC/MSC server. This message includes a QoS with higher delay and higher horizontal accuracy required for an emergency call. In case of a SIM-less emergency call, or a non-registered (U)SIM emergency call, the IMEI shall be included in the message. + +If the GMLC is capable of determining whether the initial location satisfies the higher accuracy requirements for an emergency call, then the GMLC may not need to request for a higher accuracy location. + +- 11) The VMSC/MSC server sends a Location Request message to RAN. This message includes the type of location information requested, the UE's location capabilities and requested higher accuracy QoS. + +#### 9.1.5A.5 Positioning Measurement Establishment Procedure + +- 12) same as step 4. + +#### 9.1.5A.6 Location Calculation and Release Procedure + +- 13) same as step 5. +- 14) The VMSC/MSC server returns the location information and its age, the information about the positioning method used and the serving cell identity or SAI of the UE to the GMLC. The GMLC shall replace the previously stored low accuracy location information with the higher accuracy information for later retrieval by the emergency services LCS client. The VMSC/MSC server and GMLC may record charging information. +- 15) The GMLC may forward the information received in the previous step to the emergency services LCS client. The client is expected to have requested this information from GMLC before. The information about the positioning method used may be sent with this location information from the GMLC to the LCS client. +- 16) same as step 10 for normal NI-LR. +- 17) same as step 11 for normal NI-LR. +- 18) same as step 12 for normal NI-LR. + +### 9.1.6 Packet Switched Mobile Terminating Location Request (PS-MT-LR) + +Figure 9.5 illustrates the general network positioning for LCS clients external to the PLMN for packet switched services. In this scenario, it is assumed that the target UE is identified using an MSISDN or IMSI. + +![Sequence diagram illustrating General Network Positioning for Packet Switched MT-LR. The diagram shows interactions between Client, GMLC, HLR/HSS, SGSN, RAN, and UE. The process starts with a common MT-LR procedure in PS and CS domain, followed by a Provide Subscriber Location request from GMLC to SGSN. The SGSN then performs UE Paging, Security procedures, and LCS Location Notification. The RAN handles individual positioning methods and returns a Location Report to the SGSN. Finally, the SGSN provides a Subscriber Location Report to the GMLC, which then completes the common MT-LR procedure.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC + participant HLR/HSS + participant SGSN + participant RAN + participant UE + + Note over Client, GMLC, HLR/HSS: 1. Common MT-LR procedure in PS and CS domain + GMLC->>SGSN: 2. Provide Subscriber Location + SGSN-->>GMLC: 2a. Provide Subscriber Location ack. + SGSN->>UE: 3. UE Paging + UE-->>SGSN: 4. Security procedures + SGSN-->>UE: 5. LCS Location Notification Invoke + UE-->>SGSN: 6. LCS Location Notification Return Result + SGSN->>RAN: 7. Location Request + Note over RAN, UE: 8. Messages for individual positioning methods + RAN->>SGSN: 9. Location Report + SGSN-->>GMLC: 10. Provide Subscriber Location ack. + SGSN-->>GMLC: 10a. Subscriber Location Report + GMLC-->>SGSN: 10b. Subscriber Location Report ack. + Note over Client, GMLC, HLR/HSS: 11. Common MT-LR procedure in PS and CS domain + +``` + +Sequence diagram illustrating General Network Positioning for Packet Switched MT-LR. The diagram shows interactions between Client, GMLC, HLR/HSS, SGSN, RAN, and UE. The process starts with a common MT-LR procedure in PS and CS domain, followed by a Provide Subscriber Location request from GMLC to SGSN. The SGSN then performs UE Paging, Security procedures, and LCS Location Notification. The RAN handles individual positioning methods and returns a Location Report to the SGSN. Finally, the SGSN provides a Subscriber Location Report to the GMLC, which then completes the common MT-LR procedure. + +**Figure 9.5: General Network Positioning for Packet Switched MT-LR** + +#### 9.1.6.1 Location Preparation Procedure + +- 1) Common PS and CS MT-LR procedure as described in clause 9.1.1. +- 2) GMLC sends a Provide Subscriber Location message to the SGSN indicated by the HLR/HSS. This message carries the type of location information requested (e.g. current location and optionally, velocity), the UE subscriber's IMSI, LCS QoS information (e.g. accuracy, response time) and an indication of whether the LCS client has the override capability. For a session related location request, the message also carries the APN-NI to which the user has established the session. For a value added LCS client, the message shall carry the client name, the external identity of the LCS client (or the pseudo external identity) and the Requestor Identity (if that is both supported and available), optionally the message may also carry the Service Type. Also the message may carry the type of the LCS client name and also the type of the Requestor identity if the requestor identity was included. If the result of the privacy check at H-GMLC/PPR indicated that the codeword shall be sent to the UE user, the message may carry also the codeword received from the LCS client. For a PLMN operator LCS client, the message shall carry the internal identity of the LCS client. If the Requestor Identity is provided, the GMLC shall send it as separate information. In addition, in order to display the requestor identity in case of pre rel-5 network elements (i.e. SGSN and/or UE), the requestor identity may be also added to the LCS client name by the GMLC. When the Requestor identity is added to the LCS client name the practise described in the Annex D should be followed. The message also shall carry the indicators of privacy related action which is described in clause 9.5.4 , if it is provided by H-GMLC. If the GMLC supports delayed location reporting for UEs transiently not reachable (i.e because they are in extended idle mode DRX or PSM), this shall be indicated in this message. + +- 2a) If the UE for which the request in step 2 is related is transiently not reachable and the GMLC supports delayed location reporting for UEs transiently not reachable as indicated in step 2, the SGSN sends a Provide Subscriber Location ack and a "UE transiently not reachable" indication. In this case step 10a and 10b are executed instead of step 10. +- 3) If the GMLC is located in another PLMN or another country, the SGSN first authenticates that a location request is allowed from this PLMN or from this country. If not, an error response is returned. If the PSL message from the GMLC includes the indicators of privacy related action, the SGSN determines a required privacy related action as described in Annex A.3. If the PSL message from the GMLC does not include the indicators of privacy related action, the SGSN then verifies LCS barring restrictions in the UE user's subscription profile in the SGSN. In verifying the barring restrictions, barring of the whole location request is assumed if any part of it is barred or any requisite condition is not satisfied. If LCS is to be barred without notifying the target UE and a LCS client accessing a GMLC in the same country does not have the override capability, an error response is returned to the GMLC. Otherwise, if the UE is in idle mode, the SGSN performs paging. The paging procedure is defined in TS 23.060 [15]. +- 4) Security functions may be executed. These procedures are defined in TS 23.060 [15]. +- 5) If the location request comes from a value added LCS client and the indicators of privacy related action or the UE subscription profile indicates that the UE must either be notified or notified with privacy verification and the UE supports notification of LCS, a notification invoke message is sent to the target UE indicating the type of location request from the LCS Client (e.g. current location or "current or last known location") and the identity of the LCS client and the Requestor Identity (if that is both supported and available), whether privacy verification is required. Also the message may indicate the type of the LCS client name and also the type of the Requestor identity if the requestor identity was included. Moreover, the message may carry also the service type and the codeword. Optionally, the SGSN may after sending the LCS Location Notification Invoke message continue in parallel the location process, i.e. continue to step 7 without waiting for a LCS Location Notification Return Result message in step 6. +- 6) The target UE notifies the UE user of the location request and, if privacy verification was requested, waits for the user to grant or withhold permission. The UE then returns a notification result to the SGSN indicating, if privacy verification was requested, whether permission is granted or denied. Optionally, this message can be returned some time after step 5, but before step 10. If the UE user does not respond after a predetermined time period, the SGSN shall infer a "no response" condition. The SGSN shall return an error response to the GMLC if privacy verification was requested and either the UE user denies permission or there is no response with the UE subscription profile indicating barring of the location request. +- 7) The SGSN sends a Location Request message to the RAN. This message includes the type of location information requested, the requested QoS and any other location information received in paging response. + +#### 9.1.6.2 Positioning Measurement Establishment Procedure + +- 8) If the requested location information and the location accuracy within the QoS can be satisfied based on parameters received from the SGSN and the parameters obtained by the RAN e.g. cell coverage and timing information (i.e. RTT or TA), the RAN may send a Location Report immediately. Otherwise, the RAN determines the positioning method and instigates the particular message sequence for this method in UTRAN Stage 2 TS 25.305 [1] and in GERAN Stage 2 TS 43.059 [16]. If the position method returns position measurements, the RAN uses them to compute a location estimate. If there has been a failure to obtain position measurements, the RAN may use the current cell information and, if available, RTT or TA value to derive an approximate location estimate. If an already computed location estimate is returned for an UE based position method, the RAN may verify consistency with the current cell and, if available, RTT or TA. If the location estimate so obtained does not satisfy the requested accuracy and sufficient response time still remains, the RAN may instigate a further location attempt using the same or a different position method. If a vertical location co-ordinate is requested but the RAN can only obtain horizontal co-ordinates, these may be returned. + +#### 9.1.6.3 Location Calculation and Release Procedure + +- 9) When location information best satisfying the requested location type and QoS has been obtained, the RAN returns it to the SGSN in a Location Report message. RAN shall in its response include an indication whether the obtained location estimate satisfies the requested accuracy or not. The information of the positioning method used may be returned with the location information. If a location estimate could not be obtained, the RAN returns a Location Report message containing a failure cause and no location estimate. +- 10) This step is executed only if Step 2a was not executed. The SGSN returns the location information, its age and obtained accuracy indication to the GMLC, if the SGSN has not initiated the Privacy Verification process in step 5. If step 5 has been performed for privacy verification, the SGSN returns the location information only, if it has received a LCS Location Notification Return Result indicating that permission is granted. In these cases, the information about the positioning method used may be sent with the location information. If a LCS Location Notification Return Result message indicating that permission is not granted is received, or there is no response, with the requested privacy action or the UE subscription profile indicating barring of location, the SGSN shall return an error response to the GMLC. If the SGSN did not return a successful location estimate, but the privacy checks were successfully executed, the SGSN may return the last known location of the target UE if this is known and the LCS client is requesting the current or last known location. The SGSN may record charging information. +- 10a) This step is executed only if Step 2a was executed. The SGSN shall send a Subscriber Location Report to the GMLC, and, if these were obtained in steps 7 to 9, the location information, its age and obtained accuracy indication to the GMLC, if the SGSN has not initiated the Privacy Verification process in step 5. If step 5 has been performed for privacy verification, the SGSN returns the location information only, if it has received a LCS Location Notification Return Result indicating that permission is granted. In these cases, the information about the positioning method used may be sent with the location information. If a LCS Location Notification Return Result message indicating that permission is not granted is received, or there is no response, with the requested privacy action or the UE subscription profile indicating barring of location, the SGSN shall send an error indication to the GMLC. If the SGSN did not return a successful location estimate, but the privacy checks were successfully executed, the SGSN may return the last known location of the target UE if this is known and the LCS client is requesting the current or last known location. The SGSN may record charging information. If SGSN relocation happens before location information can be reported, the old SGSN includes an error cause code indicating that it cannot proceed with the request as a result of UE mobility. The GMLC may reiterate then its request towards the new SGSN. +- 10b) If step 10a was executed, the GMLC shall acknowledge receipt of the Subscriber Location Report. +- 11) Common MT-LR procedure in PS and CS domain as described in clause 9.1.1. + +### 9.1.6A PS-MT-LR without HLR Query + +Figure 9.5A illustrates current or last known location requests for an emergency services call, where an emergency services client (i.e., a Public Safety Answering Point) identifies the target UE and the serving GMLC using correlation information that was previously provided to it by the IMS Core. The signalling used to provide the correlation information to the PSAP is out of scope of this TS, but is presumed to occur on the signalling for the call. The correlation information may be used by the GMLC to retrieve other information previously provided to it by the IMS Core as per TS 23.167 [36a] and/or SGSN as described in clause 9.1.7. This allows the requesting V-GMLC to request location from the SGSN without first querying the home HLR of the target UE. This scenario therefore supports location of emergency calls from roamers or SIM-less emergency calls, or non-registered (U)SIM emergency calls, and requires that the initial location, as well as UE and SGSN identifying information had been pushed to the GMLC as per clause 9.1.7 or as per TS 23.167 [36a]. + +![Sequence diagram for Positioning for an Emergency Services PS-MT-LR without HLR Query. The diagram shows interactions between LCS Client, GMLC, HLR/HSS, SGSN, RAN, and UE. The steps are: 1. LCS Service Request from LCS Client to GMLC; 2. Provide Subscriber Location from GMLC to SGSN; 3. Location Request from SGSN to RAN; 4. Messages for individual positioning methods between RAN and UE; 5. Location Report from RAN to SGSN; 6. Provide Subscriber Location ack. from SGSN to GMLC; 7. LCS Service Response from GMLC to LCS Client.](8307f6b04df072c9332f9987e034272c_img.jpg) + +``` + +sequenceDiagram + participant LCS Client + participant GMLC + participant HLR/HSS + participant SGSN + participant RAN + participant UE + + Note left of LCS Client: 1. LCS Service Request + LCS Client->>GMLC: 1. LCS Service Request + Note left of GMLC: 2. Provide Subscriber Location + GMLC->>SGSN: 2. Provide Subscriber Location + Note left of SGSN: 3. Location Request + SGSN->>RAN: 3. Location Request + Note right of RAN: 4. Messages for individual positioning methods + RAN->>UE: 4. Messages for individual positioning methods + UE-->>RAN: 4. Messages for individual positioning methods + Note left of RAN: 5. Location Report + RAN->>SGSN: 5. Location Report + Note left of SGSN: 6. Provide Subscriber Location ack. + SGSN->>GMLC: 6. Provide Subscriber Location ack. + Note left of GMLC: 7. LCS Service Response + GMLC->>LCS Client: 7. LCS Service Response + +``` + +Sequence diagram for Positioning for an Emergency Services PS-MT-LR without HLR Query. The diagram shows interactions between LCS Client, GMLC, HLR/HSS, SGSN, RAN, and UE. The steps are: 1. LCS Service Request from LCS Client to GMLC; 2. Provide Subscriber Location from GMLC to SGSN; 3. Location Request from SGSN to RAN; 4. Messages for individual positioning methods between RAN and UE; 5. Location Report from RAN to SGSN; 6. Provide Subscriber Location ack. from SGSN to GMLC; 7. LCS Service Response from GMLC to LCS Client. + +**Figure 9.5A: Positioning for an Emergency Services PS-MT-LR without HLR Query** + +- 1) Same as step 1 in figure 9.1 but with the LCS client (PSAP) identifying first the target UE and the serving V-GMLC by previously supplied correlation information for the emergency call. +- 2) The GMLC may determine the SGSN by associating the correlation information received from the PSAP with other information received previously from the SGSN using a PS-NI-LR and/or from the IMS core. The Provide Subscriber Location request sent to the SGSN carries, if available, the MSISDN or the IMSI and, if available, the IMEI for the target UE, as well as the required QoS and an indication of a location request from an emergency services client. The SGSN identifies the target UE using the IMSI, MSISDN and/or the IMEI. In case of a SIM-less emergency call, or non-registered (U)SIM emergency call, the IMEI shall be always sent. +- 3) The SGSN verifies that UE privacy is overridden by the emergency services provider and that positioning is not prevented for other reasons (e.g. unreachable UE). The SGSN then sends a Location Request to the RAN, as for a normal PS-MT-LR. +- 4) RAN performs positioning as for a normal PS-MT-LR. +- 5) RAN returns a location estimate to the SGSN as for a normal PS-MT-LR. +- 6) The SGSN returns the location information, its age and obtained accuracy indication to the GMLC. The information about the positioning method used may be sent with the location information. If the RAN did not return a successful location estimate, the SGSN may return the last known location of the target UE if this is known and the LCS client is requesting the current or last known location. +- 7) The GMLC sends the location service response to the LCS client (PSAP). + +NOTE: The SGSN determined by the GMLC in step 2 must be the current SGSN for the UE. In the event of handover to a new SGSN, this may require updating of the GMLC using the PS-NI-LR procedure in clause 9.1.7. Before any handover has occurred, this may require using the cell ID or SAI for the UE provided by the IMS Core. + +### 9.1.7 Packet Switched Network Induced Location Request (PS-NI-LR) + +At any time after detecting an emergency situation (i.e. after emergency Attach or Service Request for emergency, PDP context activation towards emergency APN), the SGSN may initiate the Packet Switched Network Induced Location Request (PS-NI-LR) procedure. At any time after the handover or relocation of an emergency PDP context from an old to a new SGSN, where the old SGSN indicates that a PS-NI-LR is still needed, the new SGSN may initiate a PS-NI-LR to the GMLC indicated by the old SGSN. At any time after the handover or relocation of an emergency PDP context from an old to a new SGSN, where the old SGSN indicates that a PS-NI-LR is not needed but provides a GMLC address, the new SGSN may initiate a PS-NI-LR procedure to transfer its address to the GMLC indicated by the old SGSN in order to support a later PS-MT-LR. The procedure is illustrated in figure 9.6. + +![Sequence diagram for Network Induced Location Request for the PS Domain. Lifelines: LCS Client, GMLC, HLR/HSS, SGSN, RAN, UE. The sequence starts with the SGSN sending a Location Request to the RAN. The RAN then sends messages for individual positioning methods to the UE. The UE returns a Location Report to the RAN, which then forwards it to the SGSN. The SGSN sends a Subscriber LCS Report to the GMLC, which acknowledges it. Finally, the GMLC sends Location Information to the LCS Client.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant LCS Client + participant GMLC + participant HLR/HSS + participant SGSN + participant RAN + participant UE + + Note right of SGSN: 1. Location Request + SGSN->>RAN: 1. Location Request + Note right of RAN: 2. Messages for individual positioning methods + RAN->>UE: 2. Messages for individual positioning methods + Note right of UE: 3. Location Report + UE->>RAN: 3. Location Report + RAN->>SGSN: 3. Location Report + Note right of SGSN: 4. Subscriber LCS Report + SGSN->>GMLC: 4. Subscriber LCS Report + Note right of GMLC: 5. Subscriber LCS Report ACK + GMLC->>SGSN: 5. Subscriber LCS Report ACK + Note right of GMLC: 6. Location Information + GMLC-->>LCS Client: 6. Location Information + +``` + +Sequence diagram for Network Induced Location Request for the PS Domain. Lifelines: LCS Client, GMLC, HLR/HSS, SGSN, RAN, UE. The sequence starts with the SGSN sending a Location Request to the RAN. The RAN then sends messages for individual positioning methods to the UE. The UE returns a Location Report to the RAN, which then forwards it to the SGSN. The SGSN sends a Subscriber LCS Report to the GMLC, which acknowledges it. Finally, the GMLC sends Location Information to the LCS Client. + +**Figure 9.6: Network Induced Location Request for the PS Domain** + +- 1) The SGSN sends a Location Request message to the RAN. This message indicates the type of location information requested and requested QoS. If the location of the UE is not required (e.g. the SGSN is only sending its address to the GMLC), the SGSN skips both this step and steps 2 and 3. + +#### 9.1.7.1 Positioning Measurement Establishment Procedure + +- 2) If the requested location information and the location accuracy within the QoS can be satisfied based on parameters received from the SGSN and the parameters obtained by the RAN e.g. cell coverage and timing information (i.e. RTT or TA), the RAN may send a Location Report immediately. Otherwise, the RAN determines the positioning method and instigates the particular message sequence for this method. If the position method returns position measurements, the RAN uses them to compute a location estimate. If there has been a failure to obtain position measurements, the RAN may use the current cell information and, if available, RTT or TA value to derive an approximate location estimate. If an already computed location estimate is returned for an UE based position method, the RAN may verify consistency with the current cell and, if available, RTT or TA value. If the location estimate so obtained does not satisfy the requested accuracy and sufficient response time still remains, the RAN may instigate a further location attempt using the same or a different position method. If a vertical location co-ordinate is requested but the RAN can only obtain horizontal co-ordinates, these may be returned. + +#### 9.1.7.2 Location Calculation and Release Procedure + +- 3) When a location estimate best satisfying the requested QoS has been obtained, the RAN returns a Location Report to the SGSN with an indication whether the obtained location estimate satisfies the requested accuracy or not. This message carries the location estimate that was obtained. If a location estimate was not successfully obtained, a failure cause is included in the Location Report. +- 4) The SGSN may determine the GMLC and emergency services client using the SAI or cell identity, the location estimate if obtained or information received from a previous SGSN in the case of SRNS relocation, RAU or handover. The SGSN shall send a Subscriber Location Report to the GMLC carrying the MSISDN of the UE, the identity of the LCS client, the event causing the message (PS-NI-LR), and, if these were obtained in steps 1 to 3, the location estimate and its age and the indication received from RAN whether the obtained location estimate satisfies the requested accuracy or not. The serving cell identity or SAI of the UE may also be sent. The SGSN may include its own address. If the UE was not authenticated, the IMEI shall be included. The SGSN may record charging information. +- 5) The GMLC shall acknowledge receipt of the location estimate provided that it serves the identified LCS client and the client is accessible. + +- 6) The GMLC may transfer the location information to the LCS client either immediately or upon request from the client. The GMLC may store the information received in step 4: e.g. may store the UE identity and the address of the SGSN. The GMLC may record charging information. + +NOTE: Determination of the GMLC in step 4 must ensure a match with any GMLC used by the IMS Core to assist with location retrieval for, and/or routing of, the IMS Emergency call. + +### 9.1.8 Mobile Terminating Deferred Location Request – UE available event + +Figure 9.6a illustrates the procedures for a Deferred Location Request, where the Location Report is returned based on a UE available event. + +![Sequence diagram illustrating the General Network Positioning for a Deferred MT-LR with UE available event. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The process involves an initial LCS Service Request, GMLC handling, a deferred location request to the MSC/SGSN, detection of the UE available event, and subsequent location reporting and response generation.](12de9b926df0384ec07702671827c9cd_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC_R as GMLC (Requesting) + participant GMLC_H as GMLC (Home) + participant HLR_HSS as HLR/HSS + participant GMLC_V as GMLC (Visited) + participant MSC_SGSN as MSC/SGSN + participant RAN + participant UE + + Note right of GMLC_R: 2. LCS service request handling between GMLCs + Note right of MSC_SGSN: 9. Location procedures as for PS and CS MT-LR + Note right of GMLC_H: 12. H-GMLC repeats the deferred MT-LR UE available request with new SGSN/MSC + Note right of GMLC_H: 13. Privacy check + + Client->>GMLC_R: 1. LCS Service Request + GMLC_R->>GMLC_H: 2. LCS service request handling between GMLCs + GMLC_H->>GMLC_V: 3. Provide Subscriber Location + GMLC_V->>MSC_SGSN: 4. Provide Subscriber Location ack. + MSC_SGSN->>GMLC_V: 5. LCS Service Response + GMLC_V->>GMLC_H: 6. LCS Service Response + GMLC_H->>GMLC_R: 7. LCS Service Response + UE->>MSC_SGSN: 8. "Requested event is detected" + MSC_SGSN->>GMLC_V: 10a. Subscriber Location Report + GMLC_V->>MSC_SGSN: 10b. Subscriber Location Report Ack. + GMLC_V->>GMLC_H: 11. LCS Service Response + GMLC_H->>GMLC_R: 14. LCS Service Response + GMLC_R->>Client: 15. LCS Service Response + +``` + +Sequence diagram illustrating the General Network Positioning for a Deferred MT-LR with UE available event. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The process involves an initial LCS Service Request, GMLC handling, a deferred location request to the MSC/SGSN, detection of the UE available event, and subsequent location reporting and response generation. + +Figure 9.6a: General Network Positioning for a Deferred MT-LR with UE available event + +#### 9.1.8.1 Deferred Location Request Procedure + +- 1) The LCS Service Request shall contain an indication of the requested event i.e. UE available. +- 2) LCS service request handling between GMLCs as described in clause 9.1.1. The information received by the R-GMLC is transferred to the H-GMLC. The H-GMLC assigns a LDR reference number to this LCS Service request and transfers the information to the V-GMLC, including the LDR reference number and the H-GMLC address. +- 3) The V-GMLC sends the UE available event to MSC/SGSN in the Provide Subscriber Location request (deferred) and includes the LDR reference number and the H-GMLC address in the request. + +NOTE: It shall be possible to issue the deferred location requests for the UE available event, even in case there is an ongoing previous MT-LR for the same UE. + +- 4) If the SGSN/MSC cannot support the deferred location request for the specified event (for temporary or permanent reasons), or if either the security or privacy check related actions fail, then a Provide Subscriber Location return error shall be returned with a suitable cause. If the SGSN/MSC can support the deferred location request for the specified event, a Provide Subscriber Location ack. shall be returned to the V-GMLC without a location estimate. The SGSN/MSC may record charging information for an accepted deferred location request. +- 5) V-GMLC returns the LCS Service Response to H-GMLC to notify whether the request was successfully accepted or not. The V-GMLC may record charging information for an accepted deferred location request. +- 6) H-GMLC returns the LCS Service Response to R-GMLC to notify whether the request was successfully accepted or not. When the H-GMLC returns the LCS Service Response to the R-GMLC, the LDR reference number assigned by the H-GMLC shall be included. The H-GMLC may record charging information for an accepted deferred location request. +- 7) The R-GMLC then returns the LCS Service Response with LDR reference number to the LCS Client to notify whether the request was successfully accepted or not. The R-GMLC may record charging information for an accepted deferred location request. + +#### 9.1.8.2 Location Report Procedure + +- 8) Immediately following step 3, the SGSN/MSC shall verify if the requested event is already satisfied (e.g. UE available inferred from a current transaction) or can be invoked immediately (e.g. by paging the UE and receiving a page response). If the requested event is not already satisfied, the SGSN/MSC waits until it has occurred or until some maximum time has expired. + +In case the SGSN/MSC receives an indication that the UE has moved to another SGSN/MSC, while it is waiting for the requested event to happen, SGSN/MSC shall immediately send a Subscriber Location Report to the V-GMLC. The report shall include the reference number and H-GMLC address that were included in the Provide Subscriber Location request and the information that the MT-LR must be reinitiated against the new SGSN/MSC. It shall also include the address of the new SGSN/MSC, if available. If the V-GMLC is associated with the new MSC/SGSN, it re-issues the location request to the new MSC/SGSN. Otherwise the V-GMLC forwards the responses to the H-GMLC. If the H-GMLC already knows (e.g. from a previous location request or an internal lookup table), or is able to determine, (e.g. it is possible to use a DNS lookup mechanism similar to IETF RFC 2916), the network address of the V-GMLC, it reinitiates the MT-LR to the new SGSN/MSC through the new V-GMLC. Otherwise, the H-GMLC shall then issue a SEND\_ROUTING\_INFO\_FOR\_LCS message to get the address of the V-GMLC associated with the new SGSN/MSC and reinitiate the MT-LR with the new SGSN/MSC through the new V-GMLC, see step 12. + +- 9) When the requested event is detected, the SGSN/MSC shall proceed with the location request as described in clauses 9.1.2/9.1.6. If an LCS Location Notification Invoke message is sent to the target UE as defined in step 4 of clause 9.1.2.1 and step 5 of clause 9.1.6.1, the type of location request shall indicate current location and the deferred location event type shall be omitted. + +If either security or privacy check related actions fail, the SGSN/MSC shall send a Subscriber Location Report with the reference number and H-GMLC address that was included in the Provide Subscriber Location with appropriate error cause indicating termination of the deferred location request. + +- 10) When location information has been obtained from the RAN, the SGSN/MSC returns the Subscriber Location Report. The report shall include the reference number that was included in the Provide Subscriber Location, the H-GMLC address, an indication that this is a response to a previously sent deferred location request and may also include the indication whether the obtained location estimate satisfies the requested accuracy or not (provided that this indication is obtained from RAN with the location estimate). The SGSN/MSC may record charging information. + +If the location information could not be obtained, or the SGSN/MSC for some other reason decides to not wait any longer for the requested event to occur (ex. timer expires), the Subscriber Location Report with the reference number and H-GMLC address that was included in the Provide Subscriber Location will be returned with an appropriate error cause indicating termination of the deferred location request. + +- 11) V-GMLC sends the LCS Service Response to the H-GMLC with an indication of the event occurrence and the LDR reference number. The LCS Service Response is sent in accordance with the requested QoS Class, as described in clause 9.1.1 for common MT-LR. +- 12) In case the LCS Service Response indicates to H-GMLC that the mobile has moved to another SGSN/MSC, the H-GMLC shall send the deferred MT-LR with UE available event to the V-GMLC (previous or new), which forwards the request to the new SGSN/MSC, as described in step 2 onwards. +- 13) The H-GMLC performs the privacy check as described in clause 9.1.1. +- 14) The H-GMLC sends the LCS Service Response to R-GMLC. When the H-GMLC returns the LCS Service Response to the R-GMLC, the LDR reference number that was sent to the R-GMLC in step 6 shall be included. +- 15) The R-GMLC sends the LCS Service Response with the LDR reference number to the LCS Client. + +#### 9.1.8.3 Combined Periodical/Deferred Mobile Terminating Location Request with UE available event + +Figure 9.6b illustrates the procedures for a Combined Periodical/Deferred Mobile Terminating Location Request with UE available event, where the response to the LCS client is returned periodically and based on the event. This clause is applicable only to the case, when the R-GMLC handles the periodicity of the location requests. The case when the UE handles the periodicity of location reporting, as specified in clause 9.1.12, is independent of this clause. + +NOTE: In the description below, it is assumed that the LCS client issues the Periodical/Deferred MT-LR with only the location estimate type of "current location". + +![Sequence diagram for General Network Positioning for a Combined Periodical/Deferred MT-LR. Lifelines: Client, R-GMLC, H-GMLC/V-GMLC, SGSN/MSC, RAN, UE. The diagram shows two main flows: a periodical request and a deferred request. The periodical flow involves a service request, timer start, location request to SGSN/MSC, response, timer timeout, and a subsequent response. The deferred flow involves a service request, location request to SGSN/MSC, response, an event detection from UE via RAN, location procedures, a subsequent location request to SGSN/MSC, response, and a final service response.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) + +``` + +sequenceDiagram + participant Client + participant R-GMLC + participant HVGMLC as H-GMLC +V-GMLC + participant SGSN_MSC as SGSN / MSC + participant RAN + participant UE + + Client->>R-GMLC: 1. LCS Service Request + R-GMLC-->>HVGMLC: + Note right of HVGMLC: 2. Start Periodical timer + HVGMLC->>SGSN_MSC: 3. Provide Subscriber Location + SGSN_MSC-->>HVGMLC: 4. Provide Subscriber Location ack. + HVGMLC-->>R-GMLC: + R-GMLC-->>Client: 5. LCS Service Response + + Note right of HVGMLC: 6a. Periodical timer timeout + HVGMLC-->>R-GMLC: + R-GMLC-->>Client: 6b. LCS Service Response + + UE->>RAN: 7a. "Requested event is detected". + Note right of SGSN_MSC: 7b. Location procedures as for PS and CS MT-LR + SGSN_MSC-->>HVGMLC: 8a. Subscriber Location Report + HVGMLC-->>SGSN_MSC: 8b. Subscriber Location Report ack. + HVGMLC-->>R-GMLC: + R-GMLC-->>Client: 9. LCS Service Response + + Note right of HVGMLC: 10. Periodical timer timeout + HVGMLC->>SGSN_MSC: 11. Provide Subscriber Location + SGSN_MSC-->>HVGMLC: 12. Provide Subscriber Location ack. + HVGMLC-->>R-GMLC: + R-GMLC-->>Client: 13. LCS Service Response + + Note right of RAN: 14a. Event is already satisfied.. + Note right of SGSN_MSC: 14b. Location procedures as for PS and CS MT-LR + SGSN_MSC-->>HVGMLC: 15a. Subscriber Location Report + HVGMLC-->>SGSN_MSC: 15b. Subscriber Location Report ack. + HVGMLC-->>R-GMLC: + R-GMLC-->>Client: 16. LCS Service Response + +``` + +Sequence diagram for General Network Positioning for a Combined Periodical/Deferred MT-LR. Lifelines: Client, R-GMLC, H-GMLC/V-GMLC, SGSN/MSC, RAN, UE. The diagram shows two main flows: a periodical request and a deferred request. The periodical flow involves a service request, timer start, location request to SGSN/MSC, response, timer timeout, and a subsequent response. The deferred flow involves a service request, location request to SGSN/MSC, response, an event detection from UE via RAN, location procedures, a subsequent location request to SGSN/MSC, response, and a final service response. + +**Figure 9.6b: General Network Positioning for a Combined Periodical/Deferred MT-LR** + +- 1) When a R-GMLC receives a LCS Service Request from a LCS client, the R-GMLC verifies the identity of the LCS client as described in clause 9.1.1, then the R-GMLC transfers the periodical request to the H-GMLC. +- 2) The H-GMLC starts the periodical timer and assigns a LDR reference number for this periodical request, and initiates the common LCS procedures as described in clause 9.1.1. +- 3) The V-GMLC sends a Deferred Location Request to the SGSN/MSC by means of Provide Subscriber Location as described in clauses 9.1.2/9.1.6. In addition, the Deferred Location Request includes the reference number assigned by the H-GMLC and the event that shall trigger the sending of Subscriber Location Report. +- 4) If the SGSN/MSC cannot support the deferred location request for the specified event or the LCS client is not allowed to position the requested UE according to subscription information, a Provide Subscriber Location error is returned to the V-GMLC. If the SGSN/MSC can support the deferred location request for the specified event and the privacy checks are satisfied, a Provide Subscriber Location ack shall be returned to the V-GMLC without a location estimate. The SGSN/MSC may record charging information for an accepted deferred location request. +- 5) The V-GMLC then returns the LCS Service Response to the LCS Client via H-GMLC and R-GMLC to notify whether the request was successfully accepted or not. The V-GMLC, H-GMLC and R-GMLC may record + +charging information for an accepted deferred location request. When the H-GMLC returns the LCS Service Response to the LCS Client via R-GMLC, the LDR reference number assigned by the H-GMLC shall be included. + +- 6) When the periodical timer expires, if the H-GMLC is still waiting for the event, the H-GMLC shall send a LCS Service Response to the LCS client via R-GMLC, indicating that the location is not available at that moment. The LDR reference number that was sent to the LCS Client in step 5 shall be included in the response. +- 7) When the requested event is detected, the SGSN/MSC will proceed with the location request as described in clauses 9.1.2/9.1.6. If an LCS Location Notification Invoke message is sent to the target UE as defined in step 4 of clause 9.1.2.1 and step 5 of clause 9.1.6.1, the type of location request shall indicate current location and the deferred location event type shall be omitted. +- 8) When location information has been obtained from the RAN, the SGSN/MSC returns the Subscriber Location Report. The report shall include the reference number included in the previously sent Provide Subscriber Location and an indication that this is a response to a previously sent deferred location request. The SGSN/MSC may record charging information. + +If the location information could not be obtained, or the SGSN/MSC for some other reason decides to not wait any longer for the requested event to occur (ex. timer expires), the Subscriber Location Report with the reference number included in the previously sent Provide Subscriber Location will be returned with an appropriate error cause indicating termination of the deferred location request. + +- 9) The V-GMLC then returns the LCS Service Response to the LCS Client via H-GMLC and R-GMLC as in clauses 9.1.2/9.1.6. When the H-GMLC returns the LCS Service Response to the LCS Client via R-GMLC, the LDR reference number that was sent to the LCS Client in step 5 shall be included. +- 10) When the timer expires, if the H-GMLC is not waiting for the event, the H-GMLC initiates the common LCS procedures as described in clause 9.1.1. The H-GMLC should use the same LDR reference number assigned in the step 2, should NOT assign a new LDR reference number. +- 11) Same as step 3. +- 12) Same as step 4. +- 13) Same as step 5. +- 14) If the requested event is already satisfied, the SGSN/MSC will proceed with the location request as described in clauses 9.1.2/9.1.6. If an LCS Location Notification Invoke message is sent to the target UE as defined in step 4 of clause 9.1.2.1 and step 5 of clause 9.1.6.1, the type of location request shall indicate current location and the deferred location event type shall be omitted. +- 15) Same as step 8. +- 16) Same as step 9. + +#### 9.1.8.4 Cancellation of a Deferred Location Request – UE available event + +![Sequence diagram illustrating the Cancellation of a Deferred MT-LR – UE available event procedure. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The steps are: 1. Client sends LCS Cancel Service Request to GMLC (Requesting); 2. GMLC (Requesting) sends LCS Cancel Service Request to GMLC (Home); 3. GMLC (Home) sends LCS Cancel Service Request to GMLC (Visited); 4. GMLC (Visited) sends Provide Subscriber Location to MSC/SGSN; 5. MSC/SGSN sends Provide Subscriber Location ack. to GMLC (Visited); 6. GMLC (Visited) sends LCS Cancel Service Response to GMLC (Home); 7. GMLC (Home) sends LCS Cancel Service Response to GMLC (Requesting); 8. GMLC (Requesting) sends LCS Cancel Service Response to Client.](4b87467ad9642943235f48f7d4b59449_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC_R as GMLC (Requesting) + participant GMLC_H as GMLC (Home) + participant HLR_HSS as HLR/HSS + participant GMLC_V as GMLC (Visited) + participant MSC_SGSN as MSC/SGSN + participant RAN + participant UE + + Note left of Client: UE available event + Client->>GMLC_R: 1. LCS Cancel Service Request + GMLC_R->>GMLC_H: 2. LCS Cancel Service Request + GMLC_H->>GMLC_V: 3. LCS Cancel Service Request + GMLC_V->>MSC_SGSN: 4. Provide Subscriber Location + MSC_SGSN-->>GMLC_V: 5. Provide Subscriber Location ack. + GMLC_V-->>GMLC_H: 6. LCS Cancel Service Response + GMLC_H-->>GMLC_R: 7. LCS Cancel Service Response + GMLC_R-->>Client: 8. LCS Cancel Service Response + +``` + +Sequence diagram illustrating the Cancellation of a Deferred MT-LR – UE available event procedure. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The steps are: 1. Client sends LCS Cancel Service Request to GMLC (Requesting); 2. GMLC (Requesting) sends LCS Cancel Service Request to GMLC (Home); 3. GMLC (Home) sends LCS Cancel Service Request to GMLC (Visited); 4. GMLC (Visited) sends Provide Subscriber Location to MSC/SGSN; 5. MSC/SGSN sends Provide Subscriber Location ack. to GMLC (Visited); 6. GMLC (Visited) sends LCS Cancel Service Response to GMLC (Home); 7. GMLC (Home) sends LCS Cancel Service Response to GMLC (Requesting); 8. GMLC (Requesting) sends LCS Cancel Service Response to Client. + +**Figure 9.6c: Cancellation of a Deferred MT-LR – UE available event procedure** + +- 1) The LCS Client requests the cancellation of a previously requested Deferred Location Request. The LDR reference number that was included in the previous LCS Service Response sent by the GMLC shall be included in the request to indicate which outstanding LDR should be cancelled. +- 2) The R-GMLC sends the cancellation request to H-GMLC, including the LDR reference number. The cancellation could be initiated by the R-GMLC itself for some reasons (e.g. the expiry of the validity timer specified by the start time and stop time; or the expiry of an implementation dependent timer specified by the Operator as a default value in the R-GMLC when the stop time is undefined or exceeds the maximum allowed value). +- 3) The H-GMLC forwards the LCS Cancel Service Request to V-GMLC with the LDR reference number which is received from the R-GMLC, and the H-GMLC address. The H-GMLC may itself initiate the cancellation procedure, e.g. if an implementation dependent timer in the H-GMLC expired, or when the UE's privacy profile stored in the H-GMLC or in the PPR was changed. For every outstanding Deferred Location Request against that UE, the H-GMLC shall perform or ask the PPR to perform a new privacy check based on the updated privacy profile. If the privacy check passes, i.e. the LCS Client is still allowed to position the target UE, the handling of the outstanding Deferred Location Request should be continued. Otherwise, if the privacy check does not pass, i.e. the Location estimate of the target UE is not allowed to be provided to the LCS Client, the H-GMLC shall initiate a cancellation procedure. + +NOTE: The H-GMLC shall know that the UE subscriber's privacy profile has been changed in the PPR when the LCS Privacy Profile Update has been sent from PPR to H-GMLC as described in clause 9.1.1.2. + +- 4) The V-GMLC will indicate this cancellation request in the Provide Subscriber Location toward the SGSN/MSC. The Provide Subscriber Location shall include the H-GMLC address, and the reference number specified by LCS Client in the LCS Cancel Service Request. +- 5) When the SGSN/MSC completes the cancellation procedure, it notifies it to the V-GMLC in the Provide Subscriber Location Ack (with no location estimate included). +- 6) The V-GMLC sends the LCS Cancel Service Response to H-GMLC. +- 7) H-GMLC sends the LCS Cancel Service Response to R-GMLC. H-GMLC may send the LCS Cancel Service Response to R-GMLC, even if the R-GMLC/LCS client has not requested the cancellation, see step 3. +- 8) The R-GMLC sends the LCS Cancel Service Response to the LCS Client. + +### 9.1.9 Deferred Location Request Procedure for the change of area event + +Figure 9-6d illustrates the procedures for a Deferred Location Request where the Location Report is returned to the network by the UE following a change of area event. An area event occurs when the UE leaves, enters or is within a target area as defined by geographical area, PLMN identity, country code or geopolitical name of the area. Details of the target area are contained in the LCS Service Request message, see clause 5.5.1. + +The PLMN operator may choose to use another mechanism (such as SIM Application Toolkit) for the transfer and detection mechanism of the Area Definition and change of area event information to the UE. In this case, the GMLCs handle steps 2 to 7 and 11 to 14 differently from that shown below. An alternative mechanism is detailed in Annex F + +![Sequence diagram of the Deferred MT-LR procedure for the Area event. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The process involves an initial LCS Service Request, handling between GMLCs, providing subscriber location, paging, area event invoke, and subsequent reports and responses. Step 15 is a repeat of the area event request to the new PLMN, applicable only to roaming. Step 16 is a privacy check.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC_R as GMLC (Requesting) + participant GMLC_H as GMLC (Home) + participant HLR as HLR/HSS + participant GMLC_V as GMLC (Visited) + participant MSC as MSC/SGSN + participant RAN + participant UE + + Note right of GMLC_R: 2. LCS service request handling between GMLCs + Note right of UE: 11. Area event occurs + Note right of GMLC_H: 15. Repeat sending the Area Event Request to the new PLMN (Only applicable to the roaming case) + Note right of GMLC_H: 16. Privacy check + + Client->>GMLC_R: 1. LCS Service Request + GMLC_R->>GMLC_H: + GMLC_H->>GMLC_V: + GMLC_V->>MSC: 3. Provide Subscriber Location + MSC->>RAN: 4. Paging, Authentication, Notification + RAN->>UE: 5. LCS Area Event Invoke + UE->>RAN: 6. LCS Area Event Invoke ack. + RAN->>MSC: + MSC->>GMLC_V: 7. Provide Subscriber Location ack. + GMLC_V->>GMLC_H: 8. LCS Service Response + GMLC_H->>GMLC_R: 9. LCS Service Response + GMLC_R->>Client: 10. LCS Service Response + UE->>RAN: 11. Area event occurs + RAN->>MSC: 12. LCS Area Event Report + MSC->>GMLC_V: 13a. Subscriber Location Report + GMLC_V->>MSC: 13b. Subscriber Location Report Ack. + GMLC_V->>GMLC_H: 14. LCS Service Response + GMLC_H->>GMLC_R: + GMLC_R->>Client: 17. LCS Service Response + Client->>GMLC_R: + GMLC_R->>Client: 18. LCS Service Response + +``` + +Sequence diagram of the Deferred MT-LR procedure for the Area event. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The process involves an initial LCS Service Request, handling between GMLCs, providing subscriber location, paging, area event invoke, and subsequent reports and responses. Step 15 is a repeat of the area event request to the new PLMN, applicable only to roaming. Step 16 is a privacy check. + +**Figure 9.6d: Deferred MT-LR procedure for the Area event** + +- 1) The LCS Service Request contains the change of area type deferred location request information, i.e. details of the target area and the nature of the event, whether the event to be reported is the UE being inside, entering into or leaving the target area. The LCS service request may specify the validity time, i.e. start time and stop time, for the deferred location request and R-GMLC may cancel the deferred location request as described in clause 9.1.9.1. In addition, when validity time of a pending area event request in the target UE expires, the UE shall delete the pending deferred location request. The LCS Service Request shall contain an indication of the minimum interval time between area event reports, if applicable. The LCS service request shall contain the information whether the deferred area event may be reported one time only, or several times. If the change of area event is reported one time only, the Location Service request shall be completed after the first area event has occurred. If the target area is expressed by local coordinate system or geopolitical name, the R-GMLC shall convert the target area to geographical area expressed by a shape defined in TS 23.032 [11]. In addition to the target area definition, the LCS Client may include the country code of the target area in the area event request. + +- 2) LCS service request handling between GMLCs as described in clause 9.1.1. The information received by the R-GMLC is transferred to the H-GMLC. If indication of the requested location estimate is included in the area event request, the H-GMLC should record this indication and any relevant parameters such as QoS. The H-GMLC assigns a LDR reference number to this LCS Service request then transfers the information to the V-GMLC, including the LDR reference number and the H-GMLC address. + +If the H-GMLC notices that the current visited PLMN does not serve the target area, it may generate a modified deferred LCS service request in order to get notified when the target UE enters a PLMN that serves the target area. The modified target area event is that the target UE enters one of the PLMNs that serve the original target area. Note that the new area event may include multiple PLMNs (identified by PLMN IDs) if there are more than one PLMN that serves the original target area, based on the stored PLMN list and the corresponding estimated coverage. The H-GMLC then generates a new location request with the new defined area event and the same rest of the information in the original request. + +The new location request is sent to the target UE via the current V-GMLC. The H-GMLC keeps the original area event location service request pending for as long as determined by the validity time of the request. When the UE enters one of the pre-defined PLMNs, it sends an area event location report to H-GMLC. The H-GMLC then sends the original area event location service request to the UE via the new V-GMLC. If the H-GMLC cannot derive a list of PLMNs that may cover the target area, and the current visited network does not cover the target area, the H-GMLC may reject the request. + +- 3) If the received target area is expressed by a shape defined in TS 23.032 [11], V-GMLC converts the target area into an Area Definition consisting of the corresponding list of cell identities, location areas or routing area. If the V-GMLC is not able to translate the target area into network identities, it shall reject the request and send an LCS service response to H-GMLC with the appropriate error cause. + +If the received target area is expressed by country code or PLMN identity, the V-GMLC shall use the country code or PLMN identity as the Area Definition. + +The V-GMLC sends the Area Definition to MSC/SGSN in the Provide Subscriber Location request (deferred) and includes the LDR reference number and the H-GMLC address in the request. + +The message shall define whether the event to be reported is the UE being inside, entering into or leaving the area. The message shall also include the validity period of the location request, the minimum interval time between area event reports, the information whether the deferred area event may be reported one time only or several times, if applicable. + +- 4) The MSC/SGSN verifies the UE capabilities with regard to the change of area event. If either the MSC/SGSN or the UE does not support the deferred location request for the change of area event (for temporary or permanent reasons), a Provide Subscriber Location return error shall be returned with a suitable cause in step 7. If the UE is in idle mode, the core network performs paging, authentication and ciphering. If privacy notification/verification is requested, the MSC/SGSN sends an LCS Location Notification Invoke message to the target UE with a location type indicating activation of a deferred location request, a deferred location event type containing the change of area types requested and an indication as to whether privacy verification is required. LCS Location Notification is further specified in clauses 9.1.2 and 9.1.6. If privacy verification was requested, the UE returns an LCS Location Notification Return Result to the MSC/SGSN indicating whether permission is granted or denied. If a previous deferred location request is ongoing in the UE and the MSC/SGSN proceeds with the current deferred request, the UE may return an LCS Location Notification Return Error response to the MSC/SGSN indicating that the new request cannot be supported. +- 5) The MSC/SGSN sends the LCS Area Event Invoke to the UE carrying the Area Definition, other area event information, the LDR reference number and the H-GMLC address. The message shall also define whether the event to be reported is the UE being inside, entering into, leaving the area. The message shall also include the validity period of the location request, the minimum interval time between area event reports and the information whether the deferred area event may be reported one time only, or several times, if applicable. + +- 6) If the LCS Area Event Invoke is successfully received by the UE and the UE supports the change of area type deferred location request, the UE sends acknowledgement to MSC/SGSN and begins monitoring for the change of area event. The UE shall determine whether it is inside, entering into or leaving the target area by comparing the current serving cell identity, location area, routing area, PLMN identity or country code to the Area Definition received from the MSC/SGSN. In case of soft handover, it is sufficient if one of the cells belongs to the target area. In case the Area Definition consists of a location or routing area, PLMN or country identity the UE shall check for the area event during the normal location or routing area update procedure. The change of area event detection mechanism must not influence on the normal UE cell selection and reselection procedures. If the UE does not support the deferred location request (for temporary or permanent reasons), it shall send the LCS Area Event Invoke ack. with the appropriate error cause. If a previous deferred location request is still ongoing in the UE, the UE may return an LCS Area Event Return Error response to the MSC/SGSN indicating that the new request cannot be supported. +- 7) If either the MSC/SGSN or the UE does not support the deferred location request for the change of area event (for temporary or permanent reasons), a Provide Subscriber Location return error shall be returned to the V-GMLC with a suitable cause. If both of the SGSN/MSC and UE supports the deferred location request for the change of area event, a Provide Subscriber Location ack. shall be returned to the V-GMLC without a location estimate. MSC/SGSN shall include the result of the notification/verification in the response to the V-GMLC, if the notification/verification is needed. The response message shall include the LDR reference number and the H-GMLC address. The change of area event invoke result shall be also included, if necessary. After sending the Provide Subscriber Location ack to the V-GMLC, the deferred location request shall be completed in the MSC/SGSN. The SGSN/MSC may record charging information for an accepted area event request. +- 8) to 10) V-GMLC returns the LCS Service Response via H-GMLC and R-GMLC to the LCS Client to notify whether the request was successfully accepted or not. When the H-GMLC returns the LCS Service Response to the R-GMLC, the LDR reference number assigned by the H-GMLC shall be included, then the R-GMLC shall transfer the LDR reference number to the LCS Client in the LCS Service Response. After sending the LCS Service Response to the H-GMLC, the deferred location request shall be completed in the V-GMLC. The V-GMLC or R-GMLC may record charging information for an accepted area event request. + +11) UE detects that the requested area event has occurred. + +- 12) Before sending the LCS Area Event Report the UE shall establish either a CS radio connection or PS signalling connection as specified in clauses 9.2.1 and 9.2.2. The UE sends the LCS Area Event Report to the VMSC/SGSN including the original LDR reference number and the H-GMLC address. The report shall also include the result of the notification/verification procedure, if the notification/verification is needed. + +When the MSC/SGSN receives the report and it can handle this report, an acknowledgement as a response should be sent to the UE. If the UE does not receive any response from the MSC/SGSN after sending the report, i.e. the current MSC/SGSN does not support the deferred location request for the area event (for temporary or permanent reasons), the UE may re-send the report more times. If the UE always does not receive the response, the UE shall stop sending the report, then record a corresponding flag to indicate that a report has been sent unsuccessfully. When the UE performs location update and detects the LAI or RA is changed, if the flag has been set, the UE shall send the report to the corresponding MSC/SGSN, and the flag will be cleared upon a success of the sending. + +If the UE was requested to report the change of area event one time only, the deferred location request shall be completed. In case multiple reports were requested, the UE must not send a repeated LCS Area Event Report more often than the requested minimum interval indicated in the LCS Area Event Invoke. + +**Editor's Note: It could be useful to have MSC/SGSN repeat the notification procedure with the target UE after the UE has reported the change of area event, but this is for further study.** + +- 13) The MSC/SGSN sends the subscriber location report to its associated V-GMLC with an indication of the event occurrence, the LDR reference number, the H-GMLC address and may also include the indication whether the obtained location estimate satisfies the requested accuracy or not (provided that this indication is obtained from RAN with the location estimate). V-GMLC sends an acknowledgement to MSC/SGSN in step 13b and the MSC/SGSN may record charging information. +- 14) The V-GMLC sends the LCS Service Response to the H-GMLC with an indication of the event occurrence, the LDR reference number and the H-GMLC address. The LCS Service Response is sent in accordance with the requested QoS Class, as described in clause 9.1.1 for common MT-LR. The LDR reference number and the H-GMLC address will be used to identify the source of the original deferred location request in the case that the UE has relocated before the area event occurred. The V-GMLC may record charging information. + +15) In case the UE moves to another PLMN of the PLMN identities list, according to the PLMN identity the UE shall determine whether the Area Definition of the target area is available. If it is not available, the UE shall report that it has roamed into a new PLMN, including the new PLMN identity and the LDR reference number. The H-GMLC shall transfer the original area event request to the V-GMLC of the new PLMN. The procedure should be continued as described in step 2 and onwards where the Area Definition of the new PLMN shall be downloaded to the UE. Otherwise, the UE monitors the area event in the new PLMN, does not inform the H-GMLC that it has entered into a new PLMN. + +16) The H-GMLC performs the privacy check as described in clause 9.1.1. + +17) If the H-GMLC finds the indication of the requested location estimate is stored, the H-GMLC should generate a new immediate LCS Service Request with the QoS specified in the original request. Then the H-GMLC sends the new request as described in clause 9.1.1 to the V-GMLC and waits the result the location request, the subsequent procedures in clause 9.1.1 are continued. + +The H-GMLC sends the LCS Service Response to R-GMLC with the LDR reference number. If the location estimate of the target UE is requested in the request and the location estimate was successfully obtained, the H-GMLC shall put the obtained location estimate into the LCS Service Response. If the location estimate of the target UE is requested in the request but the location estimate could not be obtained, the H-GMLC sends the LCS Service Response without the location estimate. Unless multiple reports were requested, the deferred location request shall be completed in the H-GMLC after sending the LCS Service Response to the R-GMLC. The H-GMLC may record charging information. + +18) The R-GMLC sends the LCS Service Response to the LCS client. Unless multiple reports were requested, the deferred location request shall be completed in the R-GMLC after sending the LCS Service Response to the LCS client. The R-GMLC may record charging information. + +#### 9.1.9.1 Cancellation of a Deferred Location Request – Change of Area event + +Figure 9-7b illustrates the procedure for cancelling the Deferred Location Request for the change of area event. + +![Sequence diagram illustrating the cancellation of a Deferred MT-LR with change of area event procedure. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE.](7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC_R as GMLC (Requesting) + participant GMLC_H as GMLC (Home) + participant HLR as HLR/HSS + participant GMLC_V as GMLC (Visited) + participant MSC as MSC/SGSN + participant RAN + participant UE + + Note left of Client: 1. LCS Cancel Service Request + Client->>GMLC_R: 1. LCS Cancel Service Request + GMLC_R->>GMLC_H: 2. LCS Cancel Service Request + GMLC_H->>GMLC_V: 3. LCS Cancel Service Request + GMLC_V->>MSC: 4. Provide Subscriber Location + MSC->>UE: 5. LCS Area Event Cancel + UE-->>MSC: 6a. LCS Area Event Cancel ack. +6b. LCS area event report, cancel + MSC->>GMLC_V: 7. Provide Subscriber Location ack. + GMLC_V->>GMLC_H: 8. LCS Cancel Service Response + GMLC_H->>GMLC_R: 9. LCS Cancel Service Response + GMLC_R->>Client: 10. LCS Cancel Service Response + +``` + +Sequence diagram illustrating the cancellation of a Deferred MT-LR with change of area event procedure. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. + +**Figure 9.7b: Cancellation of a Deferred MT-LR with change of area event procedure** + +1) The LCS Client requests the cancellation of a previously requested Deferred Location Request. The LDR reference number that was included in the previous LCS Service Response sent by the GMLC shall be included in the request to indicate which outstanding LDR should be cancelled. + +- 2) The R-GMLC sends the cancellation request to H-GMLC, including the LDR reference number. R-GMLC may itself initiate the cancellation for some other reason, e.g. the expiry of the validity timer specified by the start time and stop time; or the expiry of an implementation dependent timer specified by the Operator as a default value in the R-GMLC when the stop time is undefined or exceeds the maximum allowed value. +- 3) The H-GMLC forwards the LCS Cancel Service Request to V-GMLC with the LDR reference number which is received from the R-GMLC, and the H-GMLC address. The H-GMLC may itself initiate the cancellation procedure, when the UE's privacy profile stored in the H-GMLC or in the PPR was changed. For every outstanding Deferred Location Request against that UE, the H-GMLC shall perform or ask the PPR to perform a new privacy check based on the updated privacy profile. If the privacy check passes, i.e. the LCS Client is still allowed to position the target UE, the handling of the outstanding Deferred Location Request should be continued. Otherwise, if the privacy check does not pass, i.e. the Location estimate of the target UE is not allowed to be provided to the LCS Client, the H-GMLC shall initiate a cancellation procedure. + +NOTE: The H-GMLC shall know that the UE subscriber's privacy profile has been changed in the PPR when the LCS Privacy Profile Update has been sent from PPR to H-GMLC as described in clause 9.1.1.2. + +- 4) The V-GMLC sends the Provide Subscriber Location request to SGSN/MSC, indicating a cancellation of a deferred location request and including the LDR reference number specified by the LCS Client in the LCS Cancel Service Request and the H-GMLC address received from the H-GMLC. +- 5) The SGSN/MSC sends the LCS Area Event Cancellation, including the LDR reference number and the H-GMLC address, request to UE. +- 6a) The UE cancels the Area event deferred location request and sends the LCS Area Event cancellation ack., with no area event information included to VMSC/SGSN. +- 6b) While the UE is monitoring for the area event to occur, the UE may cancel or terminate the deferred location request for the change of area on its own behalf by sending the LCS Area Event report with the LDR reference number, an indication of the cancellation and an appropriate error cause. +- 7) The SGSN/MSC sends the cancellation acknowledgement to the V-GMLC in the Provide Subscriber Location Ack, with the LDR reference number and the H-GMLC address. +- 8) The V-GMLC sends the LCS Cancel Service Response to H-GMLC with the LDR reference number and the H-GMLC address. +- 9) H-GMLC sends the LCS Cancel Service Response to R-GMLC with the LDR reference number. H-GMLC may send the LCS Cancel Service Response to R-GMLC, even if the R-GMLC/LCS client has not requested the cancellation, see step 3. +- 10) R-GMLC sends the LCS Cancel Service Response to the LCS Client. + +### 9.1.10 Circuit Switched Post Positioning Notification and Verification Procedure + +Figure 9.10 illustrates the post positioning notification and verification procedure. + +![Sequence diagram illustrating the CS Post Positioning Notification and Verification Procedure. Lifelines: Client, GMLC, HLR/HSS, VMSC/MSC SERVER, RAN, UE. The procedure involves a common MT-LR procedure, followed by a 'Provide Subscriber Location' request from GMLC to VMSC/MSC SERVER, then UE paging, LCS location notification to the UE, a return from the UE, a 'Provide Subscriber Location ack' from VMSC/MSC SERVER to GMLC, and finally a common ML-LR procedure.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC + participant HLR/HSS + participant VMSC/MSC SERVER + participant RAN + participant UE + + Note over Client, HLR/HSS: 1. Common MT-LR procedure in CS and PS domain + GMLC->>VMSC/MSC SERVER: 2. Provide Subscriber Location + VMSC/MSC SERVER->>UE: 3. UE Paging, Authentication, Ciphering + VMSC/MSC SERVER->>UE: 4. LCS Location Notification + UE->>VMSC/MSC SERVER: 5. LCS Location Notification Return + VMSC/MSC SERVER->>GMLC: 6. Provide Subscriber Location ack + Note over Client, HLR/HSS: 7. Common ML-LR procedure in CS and PS domain + +``` + +Sequence diagram illustrating the CS Post Positioning Notification and Verification Procedure. Lifelines: Client, GMLC, HLR/HSS, VMSC/MSC SERVER, RAN, UE. The procedure involves a common MT-LR procedure, followed by a 'Provide Subscriber Location' request from GMLC to VMSC/MSC SERVER, then UE paging, LCS location notification to the UE, a return from the UE, a 'Provide Subscriber Location ack' from VMSC/MSC SERVER to GMLC, and finally a common ML-LR procedure. + +**Figure 9.10: CS Post Positioning Notification and Verification Procedure** + +- 1) Common PS and CS MT-LR procedure as described in clause 9.1.1. +- 2) The GMLC sends a PROVIDE\_SUBSCRIBER\_LOCATION message to the MSC/MSC server with an indication of "notification only". This message carries the UE subscriber's IMSI. For a call related location request, the message also carries the LCS client's called party number. For a value added LCS client, the message shall carry the client name, the external identity of the LCS client and the Requestor Identity (if that is both supported and available). Also the message may carry the type of the LCS client name and also the type of the Requestor identity if the requestor identity was included. For a PLMN operator LCS client, the message shall carry the internal identity of the LCS client. Moreover the message may also carry the Service Type. If the result of the privacy check at H-GMLC/PPR indicated that the codeword shall be sent to the UE user, the message may carry also the codeword received from the LCS client. For a PLMN operator LCS client, the message shall carry the internal identity of the LCS client. If the Requestor Identity is provided, the GMLC shall send it as separate information. In addition, in order to display the requestor identity in case of pre Rel-5 network elements (i.e. MSC and/or UE), the requestor identity may be also added to the LCS client name by the GMLC. When the Requestor identity is added to the LCS client name the practice described in the Annex D should be followed. +- 3) If the UE is in idle mode, the Core Network performs paging, authentication and ciphering. The MSC will page a GPRS attached UE either through A/Iu or Gs interface, depending on the presence of the Gs interface. +- 4) An LCS Location Notification Invoke message is sent to the target UE indicating a location type of notification and verification only, the identity of the LCS client, the Requestor Identity (if that is both supported and available) and whether privacy verification is required. Also the message may indicate the type of the LCS client + +name and also the type of the Requestor identity if the requestor identity was included. Moreover, the message may carry also the service type and the codeword.4). + +- 5) The target UE notifies the UE user of the location request. If privacy verification was requested, the target UE indicates to the UE user whether the location report will be allowed or not allowed in the absence of a response and waits for the user to grant or withhold permission. The UE then returns an LCS Location Notification Return Result to the VMSC/MSC server indicating, if privacy verification was requested, whether permission is granted or denied. If the UE user does not respond after a predetermined time period, the VMSC/MSC server shall infer a "no response" condition. The VMSC/MSC server shall return an error response to the GMLC if privacy verification was requested and either the UE user denies permission or there is no response with the UE subscription profile indicating barring of the location request in the absence of a response. +- 6) The VMSC/MSC server returns the indication of successful notification and verification result, if it has received a LCS Location Notification Return Result indicating that permission is granted. If a LCS Location Notification Return Result message indicating that permission is not granted is received, or there is no response, with the requested privacy action or the UE subscription profile indicating barring of location in the absence of a response, the VMSC/MSC server shall return an error response to the GMLC. The MSC/MSC server may then release the Mobility Management connection to the UE, if the UE was previously idle, and the MSC/MSC server may record charging information. +- 7) Common MT-LR procedure in PS and CS domain as described in clause 9.1.1. + +### 9.1.11 Packet Switched Post Positioning Notification and Verification Procedure + +Figure 9.11 illustrates the post positioning notification and verification procedure. + +![Sequence diagram of the PS Post Positioning Notification and Verification Procedure. Lifelines: Client, GMLC, HLR/HSS, SGSN, RAN, UE. The procedure starts with a common MT-LR procedure in PS and CS domain. The GMLC sends a 'Provide Subscriber Location' message to the SGSN. The SGSN sends a 'Paging' message to the UE. The UE and SGSN perform 'Security procedures'. The SGSN sends an 'LCS Location Notification Invoke' message to the RAN. The RAN sends an 'LCS Location Notification Return Result' message to the SGSN. The SGSN sends a 'Provide Subscriber Location ack' message to the GMLC. The procedure ends with another common MT-LR procedure in PS and CS domain.](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC + participant HLR/HSS + participant SGSN + participant RAN + participant UE + + Note over Client, GMLC, HLR/HSS: 1. Common MT-LR procedure in PS and CS domain + GMLC->>SGSN: 2. Provide Subscriber Location + SGSN->>UE: 3. Paging + Note over UE, SGSN: 4. Security procedures + Note over RAN, UE: 5. LCS Location Notification Invoke + Note over SGSN, RAN: 6. LCS Location Notification Return Result + SGSN->>GMLC: 7. Provide Subscriber Location ack + Note over Client, GMLC, HLR/HSS: 8. Common MT-LR procedure in PS and CS domain + +``` + +Sequence diagram of the PS Post Positioning Notification and Verification Procedure. Lifelines: Client, GMLC, HLR/HSS, SGSN, RAN, UE. The procedure starts with a common MT-LR procedure in PS and CS domain. The GMLC sends a 'Provide Subscriber Location' message to the SGSN. The SGSN sends a 'Paging' message to the UE. The UE and SGSN perform 'Security procedures'. The SGSN sends an 'LCS Location Notification Invoke' message to the RAN. The RAN sends an 'LCS Location Notification Return Result' message to the SGSN. The SGSN sends a 'Provide Subscriber Location ack' message to the GMLC. The procedure ends with another common MT-LR procedure in PS and CS domain. + +**Figure 9.11: PS Post Positioning Notification and Verification Procedure** + +- 1) Common PS and CS MT-LR procedure as described in clause 9.1.1. +- 2) The GMLC sends a Provide Subscriber Location message to the SGSN with an indication of "notification only". This message carries the UE subscriber's IMSI. For a session related location request, the message also carries the APN-NI to which the user has established the session. For a value added LCS client, the message shall carry the client name, the external identity of the LCS client and the Requestor Identity (if that is both supported and available), optionally the message may also carry the Service Type. Also the message may carry the type of the LCS client name and also the type of the Requestor identity if the requestor identity was included. If the result of the privacy check at H-GMLC/PPR indicated that the codeword shall be sent to the UE user, the message may carry also the codeword received from the LCS client. For a PLMN operator LCS client, the message shall carry the internal identity of the LCS client. If the Requestor Identity is provided, the GMLC shall send it as separate information. In addition, in order to display the requestor identity in case of pre Rel-5 network elements (i.e. SGSN and/or UE), the requestor identity may be also added to the LCS client name by the GMLC. When the Requestor identity is added to the LCS client name the practice described in the Annex D should be followed. + +- 3) The SGSN determines a required privacy related action as described in Annex A.3 based on the indicators of privacy related action in the PSL message from the GMLC. If the UE is in idle mode, the SGSN performs paging. The paging procedure is defined in TS 23.060 [15]. +- 4) Security functions may be executed. These procedures are defined in TS 23.060 [15]. +- 5) A notification invoke message is sent to the target UE indicating a location type of notification and verification only, the identity of the LCS client and the Requestor Identity (if that is both supported and available), whether privacy verification is required. Also the message may indicate the type of the LCS client name and also the type of the Requestor identity if the requestor identity was included. Moreover, the message may carry also the service type and the codeword. +- 6) The target UE notifies the UE user of the location request and, if privacy verification was requested, waits for the user to grant or withhold permission. The UE then returns a notification result to the SGSN indicating, if privacy verification was requested, whether permission is granted or denied. If the UE user does not respond after a predetermined time period, the SGSN shall infer a "no response" condition. The SGSN shall return an error response to the GMLC if privacy verification was requested and either the UE user denies permission or there is no response with the UE subscription profile indicating barring of the location request. +- 7) The SGSN returns the indication of successful notification and verification result, if it has received a LCS Location Notification Return Result indicating that permission is granted. If a LCS Location Notification Return Result message indicating that permission is not granted is received, or there is no response, with the requested privacy action or the UE subscription profile indicating barring of location, the SGSN shall return an error response to the GMLC. +- 8) Common MT-LR procedure in PS and CS domain as described in clause 9.1.1. + +### 9.1.12 Deferred Location Request Procedure for the Periodic Location Event + +This clause describes the procedures for a Deferred Location Request where a Location Report is returned to the network each time the periodic reporting event occurs within the UE. + +#### 9.1.12.1 Instigation of an MT-LR Request for Periodic Location + +![Sequence diagram illustrating the Deferred MT-LR Initiation Procedure for Periodic Location. The diagram shows the interaction between a Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The process involves 10 steps: 1. LCS Service Request from Client to GMLC (Requesting); 2. LCS service request handling between GMLCs; 3. Provide Subscriber Location from GMLC (Visited) to MSC/SGSN; 4. Paging, Authentication, Notification from MSC/SGSN to UE; 5. LCS Periodic Location Invoke from MSC/SGSN to UE; 6. LCS Periodic Location Invoke ack. from UE to MSC/SGSN; 7. Provide Subscriber Location ack. from MSC/SGSN to GMLC (Visited); 8. LCS Service Response from GMLC (Visited) to GMLC (Home); 9. LCS Service Response from GMLC (Home) to GMLC (Requesting); 10. LCS Service Response from GMLC (Requesting) to Client.](b904ac2472cab80892d1e783e6230d6e_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC_Req as GMLC (Requesting) + participant GMLC_Home as GMLC (Home) + participant HLR_HSS as HLR/HSS + participant GMLC_Visited as GMLC (Visited) + participant MSC_SGSN as MSC/SGSN + participant RAN + participant UE + + Note right of GMLC_Req: 2. LCS service request handling between GMLCs + Note right of MSC_SGSN: 4. Paging, Authentication, Notification + + Client->>GMLC_Req: 1. LCS Service Request + GMLC_Req->>GMLC_Home: + GMLC_Home->>GMLC_Visited: + GMLC_Visited->>MSC_SGSN: 3. Provide Subscriber Location + MSC_SGSN->>UE: 4. Paging, Authentication, Notification + MSC_SGSN->>UE: 5. LCS Periodic Location Invoke + UE->>MSC_SGSN: 6. LCS Periodic Location Invoke ack. + MSC_SGSN->>GMLC_Visited: 7. Provide Subscriber Location ack. + GMLC_Visited->>GMLC_Home: 8. LCS Service Response + GMLC_Home->>GMLC_Req: 9. LCS Service Response + GMLC_Req->>Client: 10. LCS Service Response + +``` + +Sequence diagram illustrating the Deferred MT-LR Initiation Procedure for Periodic Location. The diagram shows the interaction between a Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The process involves 10 steps: 1. LCS Service Request from Client to GMLC (Requesting); 2. LCS service request handling between GMLCs; 3. Provide Subscriber Location from GMLC (Visited) to MSC/SGSN; 4. Paging, Authentication, Notification from MSC/SGSN to UE; 5. LCS Periodic Location Invoke from MSC/SGSN to UE; 6. LCS Periodic Location Invoke ack. from UE to MSC/SGSN; 7. Provide Subscriber Location ack. from MSC/SGSN to GMLC (Visited); 8. LCS Service Response from GMLC (Visited) to GMLC (Home); 9. LCS Service Response from GMLC (Home) to GMLC (Requesting); 10. LCS Service Response from GMLC (Requesting) to Client. + +Figure 9.12: Deferred MT-LR Initiation Procedure for Periodic Location + +- 1) The LCS Service Request contains the periodic location request information, such as time interval between successive location reports and total number of reports. +- 2) LCS service request handling between GMLCs as described in clause 9.1.1. The information received by the R-GMLC is transferred to the H-GMLC. The R-GMLC also indicates whether MO-LR Short Circuit is allowed. The H-GMLC assigns a LDR reference number to this LCS Service Request and may include a list of PLMNs and possibly associated radio access technologies (e.g. GSM, UMTS), either prioritized or non-prioritized, in which subsequent MO-LR TTTP requests must be made by the UE (according to the procedure in clause 9.1.12.2) and an indication for each PLMN (and possibly associated radio access technology) as to whether the PLMN supports periodic location in the RAN. If no list is included by the H-GMLC, subsequent MO-LR TTTP requests are restricted to the current serving PLMN only. The H-GMLC then transfers the information to the V-GMLC, including the LDR reference number, any reporting PLMN list and the H-GMLC address. + +NOTE 1: Any preference for using MO-LR Short Circuit needs to consider the list of PLMNs in which subsequent MO-LR TTTP requests will be made (if this was included by the H-GMLC) since this agreement applies to all of these PLMNs. + +- 3) The V-GMLC conveys the periodic location request to MSC/SGSN in the Provide Subscriber Location request including the LDR reference number, any reporting PLMN list and the H-GMLC address in the request, as well as an indication of whether MO-LR Short Circuit is permitted. +- 4) The MSC/SGSN verifies the UE capabilities with regard to the support of location service related call independent supplementary services (e.g. notification for LCS). If either the UE does not support any location service related call independent supplementary service or the MSC/SGSN does not support the deferred location request for the periodic location event (for temporary or permanent reasons), a Provide Subscriber Location return error shall be returned with a suitable cause in step 7. +If the UE is in idle mode, the core network performs paging, authentication and ciphering. If privacy notification/verification is requested, the MSC/SGSN sends an LCS Location Notification Invoke message to the target UE with a location type indicating activation of a deferred location request, a deferred location event type indicating periodic location and an indication as to whether privacy verification is required. LCS Location Notification is further specified in clauses 9.1.2 and 9.1.6. If privacy verification was requested, the UE returns an LCS Location Notification Return Result to the MSC/SGSN indicating whether permission is granted or denied. If a previous deferred location request is ongoing in the UE and the MSC/SGSN proceeds with the current deferred request, the UE may return an LCS Location Notification Return Error response to the MSC/SGSN indicating that the new request cannot be supported. + +NOTE 2: There is no UE capability information directly indicating support of a periodic deferred location request. However, if the UE supports at least one location service related call independent supplementary service (such as notification for LCS), the MSC/SGSN can assume support for a periodic deferred location request and attempt to request it in step 5. If the UE does not recognize this request, it may return a Facility Rejected indication in step 6 (as defined in TS 24.008 [24]) to the MSC/SGSN. The return of at least this minimal indication of non-support (as opposed to the UE ignoring the request and sending back nothing) is ensured by support of at least one location service related call independent supplementary service. + +- 5) The MSC/SGSN sends an LCS Periodic Location Invoke to the UE containing the periodic location related parameters (reporting interval and total number of reports) and other relevant information (QoS, LCS Client External ID, H-GMLC address, LDR reference number, any reporting PLMN list and use of MO-LR Short Circuit). +- 6) If the LCS Periodic Location Invoke is successfully received by the UE and the UE supports the periodic location according to the request received in step 5, the UE sends an acknowledgement to MSC/SGSN including the MO-LR Short Circuit indication if received in step 5. If the MO-LR Short Circuit indication is received in step 5 and the UE does not support MO-LR Short Circuit (for temporary or permanent reasons), the UE sends the LCS Periodic Location Invoke Ack without the MO-LR Short Circuit indication indicating to the MSC/SGSN that MO-LR Short Circuit will not be used. If a previous deferred location request is still ongoing in the UE, the UE may return an LCS Periodic Location Return Error response to the MSC/SGSN indicating that the new request cannot be supported. +- 7) If either the MSC/SGSN or the UE does not support the periodic location request (for temporary or permanent reasons), a Provide Subscriber Location return error shall be returned to the V-GMLC with a suitable error cause. + +If both of the MSC/SGSN and UE supports the periodic location request, a Provide Subscriber Location Ack. shall be returned to the V-GMLC. The MSC/SGSN shall include an MO-LR Short Circuit indication in the response to the V-GMLC, if the use of MO-LR Short Circuit was requested and accepted by the UE in step 6. + +- 8) to 10) The V-GMLC returns the LCS Service Response via H-GMLC and R-GMLC to the LCS Client to notify whether the periodic location request was successfully accepted or not. When the H-GMLC returns the LCS Service Response to the R-GMLC, the LDR reference number assigned by the H-GMLC shall be included, and the R GMLC may transfer the LDR reference number to the LCS Client in the LCS Service Response. + +NOTE 3: If the R-GMLC receives an error response in step 9 indicating that the MT-LR request for periodic location cannot be supported (for temporary or permanent reasons), the R-GMLC may invoke periodic location using the common MT-LR procedure defined in clause 9.1.1. + +#### 9.1.12.2 Reporting of Periodic Location + +Once the periodic location reporting has been successfully instigated using the procedure in figure 9.12 (or 9.8a in case the UE subscriber or an application in the UE is the instigator), the UE is responsible for sending location estimates periodically to the LCS Client using MO-LR TTTP procedure illustrated in figure 9.13 below. This procedure begins immediately or, in the case of MO-LR short circuit, almost immediately after the procedure in figure 9.12 (or 9.8a) and continues until the specified number of reports for this request is attained or the procedure is cancelled by the UE, R-GMLC or H-GMLC using the procedure specified in clause 9.1.12.3. + +![Sequence diagram for Reporting of Periodic Location. Lifelines: LCS Client, R-GMLC, H-GMLC, V-GMLC, MSC/SGSN, RAN, UE. The diagram shows two periodic location reporting cycles. In the first cycle, the UE sends a CS/PS Service Request to the MSC/SGSN, which authenticates and invokes an LCS MO-LR. The MSC/SGSN sends a Location Request to the RAN, which returns a Location Report. The MSC/SGSN then sends a Subscriber Location Report to the V-GMLC, which acknowledges it. The V-GMLC sends an LCS Service Response to the H-GMLC, which performs a Privacy Check and returns an LCS Service Response to the R-GMLC, which finally sends an LCS Service Response to the LCS Client. The MSC/SGSN also sends an LCS Location Update to the UE, which acknowledges it. A second cycle follows, with the RAN sending Messages for individual positioning to the UE, then a Location Report to the MSC/SGSN. The MSC/SGSN sends a Subscriber Location Report to the V-GMLC, which acknowledges it. The V-GMLC sends an LCS Service Response to the H-GMLC, which performs a Privacy Check and returns an LCS Service Response to the R-GMLC, which finally sends an LCS Service Response to the LCS Client. The MSC/SGSN also sends an LCS Location Update to the UE, which acknowledges it. After some ellipsis, the MSC/SGSN sends an LCS MO-LR Return Result to the UE, and finally releases CM, MM/GMM, RR/RRC connections.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +sequenceDiagram + participant LCS Client + participant R-GMLC + participant H-GMLC + participant V-GMLC + participant MSC/SGSN + participant RAN + participant UE + + Note left of MSC/SGSN: 1. CS: CM Service Request +PS: Service Request + UE->>MSC/SGSN: 1. CS: CM Service Request +PS: Service Request + Note right of MSC/SGSN: 2. CS: Authentication, Ciphering or CM Service +Accept +(PS: Part of 1: Possible Security Procedures) + MSC/SGSN->>UE: 2. CS: Authentication, Ciphering or CM Service +Accept +(PS: Part of 1: Possible Security Procedures) + Note left of MSC/SGSN: 3. LCS MO-LR Invoke (+ location estimate) + MSC/SGSN->>RAN: 3. LCS MO-LR Invoke (+ location estimate) + Note right of RAN: 4. Location Request + RAN->>MSC/SGSN: 4. Location Request + Note right of RAN: 5. Messages for individual +positioning + RAN->>UE: 5. Messages for individual +positioning + Note left of RAN: 6. Location Report + RAN->>MSC/SGSN: 6. Location Report + Note right of MSC/SGSN: 7. Subscriber Location Report + MSC/SGSN->>V-GMLC: 7. Subscriber Location Report + Note left of V-GMLC: 8. Subscriber Location Report ack. + V-GMLC->>MSC/SGSN: 8. Subscriber Location Report ack. + Note right of V-GMLC: 9. LCS Service Response + V-GMLC->>H-GMLC: 9. LCS Service Response + Note right of H-GMLC: 10. Privacy Check + H-GMLC->>R-GMLC: 11. LCS Service Response + R-GMLC->>LCS Client: 12. LCS Service Response + + Note left of MSC/SGSN: 13. LCS Location Update + MSC/SGSN->>UE: 13. LCS Location Update + Note right of UE: 14. LCS Location Update Ack. + UE->>MSC/SGSN: 14. LCS Location Update Ack. + + Note right of RAN: 15. Messages for +individual positioning + RAN->>UE: 15. Messages for +individual positioning + Note left of RAN: 16. Location Report + RAN->>MSC/SGSN: 16. Location Report + Note right of MSC/SGSN: 17. Subscriber Location Report + MSC/SGSN->>V-GMLC: 17. Subscriber Location Report + Note left of V-GMLC: 18. Subscriber Location Report ack. + V-GMLC->>MSC/SGSN: 18. Subscriber Location Report ack. + Note right of V-GMLC: 19. LCS Service Response + V-GMLC->>H-GMLC: 19. LCS Service Response + Note right of H-GMLC: 20. Privacy Check + H-GMLC->>R-GMLC: 21. LCS Service Response + R-GMLC->>LCS Client: 22. LCS Service Response + + Note left of MSC/SGSN: 23. LCS Location Update + MSC/SGSN->>UE: 23. LCS Location Update + Note right of UE: 24. LCS Location Update Ack. + UE->>MSC/SGSN: 24. LCS Location Update Ack. + + Note right of MSC/SGSN: 25. LCS MO-LR Return Result + MSC/SGSN->>UE: 25. LCS MO-LR Return Result + Note left of MSC/SGSN: 26. Release CM, MM/GMM, RR/RRC connections + MSC/SGSN->>UE: 26. Release CM, MM/GMM, RR/RRC connections + +``` + +Sequence diagram for Reporting of Periodic Location. Lifelines: LCS Client, R-GMLC, H-GMLC, V-GMLC, MSC/SGSN, RAN, UE. The diagram shows two periodic location reporting cycles. In the first cycle, the UE sends a CS/PS Service Request to the MSC/SGSN, which authenticates and invokes an LCS MO-LR. The MSC/SGSN sends a Location Request to the RAN, which returns a Location Report. The MSC/SGSN then sends a Subscriber Location Report to the V-GMLC, which acknowledges it. The V-GMLC sends an LCS Service Response to the H-GMLC, which performs a Privacy Check and returns an LCS Service Response to the R-GMLC, which finally sends an LCS Service Response to the LCS Client. The MSC/SGSN also sends an LCS Location Update to the UE, which acknowledges it. A second cycle follows, with the RAN sending Messages for individual positioning to the UE, then a Location Report to the MSC/SGSN. The MSC/SGSN sends a Subscriber Location Report to the V-GMLC, which acknowledges it. The V-GMLC sends an LCS Service Response to the H-GMLC, which performs a Privacy Check and returns an LCS Service Response to the R-GMLC, which finally sends an LCS Service Response to the LCS Client. The MSC/SGSN also sends an LCS Location Update to the UE, which acknowledges it. After some ellipsis, the MSC/SGSN sends an LCS MO-LR Return Result to the UE, and finally releases CM, MM/GMM, RR/RRC connections. + +**Figure 9.13: Reporting of Periodic Location** + +1) to 2) If the UE is in idle mode, the UE requests a radio connection setup and sends a CM Service Request indicating a request for call independent supplementary service to the VMSC/MSC server via RAN (CS domain). If the UE is in dedicated mode, the UE sends a CM Service Request on the already established radio connection. The VMSC/MSC server investigates authentication and ciphering if the UE was in idle mode or returns a CM Service Accept if the UE was in dedicated mode. + +For PS domain, in UMTS, if the UE is in idle mode, the UE requests a PS signalling connection and sends a Service Request indicating signalling to the SGSN via RAN. If the UE already has PS signalling connection, the UE does not need to send the Service Request. Security functions may be executed. These procedures are described in TS 23.060 [15]. In GSM this signalling step is not needed. + +- 3) The UE sends an LCS MO-LR Invoke to the VMSC/MSC Server (CS domain) or to the SGSN (PS domain) for a transfer of the location estimate to a third party LCS client. This message includes the identity of the LCS client and the H-GMLC address received by the UE during execution of the procedure described in clause 9.1.12.1 (or clause 9.2.3). +The LCS MO-LR Invoke also includes the LDR Reference Number. The presence of the LDR Reference Number indicates that the transfer and its attributes (e.g. use of MO-LR Short Circuit) have been previously authorized by the R-GMLC, H-GMLC and V-GMLC, using the procedure described in clause 9.1.12.1 (or clause 9.2.3). +This message also includes a location estimate if MO-LR Short Circuit was requested and has been acknowledged by the UE. If MO-LR Short Circuit has been acknowledged and the UE was not able to obtain a location estimate, the LCS MO-LR Invoke shall still be sent when the reporting event occurs indicating that no location estimate is available. +If MO-LR Short circuit has not been agreed or was not requested, the LCS MO-LR Invoke message does not include any location estimate or error indication, but includes QoS information and optional periodic location information (reporting interval and number of reports), as well as an optional request for location update notification (see steps 13 and 14). +- 4) to 6) If MO-LR Short Circuit is not used (i.e. no location estimate or no error indicating unavailability of a location estimate is included in step 3), the MSC/SGSN obtains a location estimate by sending a Location Request to RAN associated with the target UE in step 4. The Location Request includes the LCS QoS. If supported by the serving RAN and included by the UE in step 3, the Location Request can include periodic location information (e.g. reporting interval and number of reports). In step 5, RAN determines the positioning method and instigates the particular message sequence for this method, as specified in UTRAN Stage 2, TS 25.305 [1] and GERAN Stage 2, TS 43.059 [16]. When a location estimate best satisfying the requested QoS has been obtained, RAN returns it to the MSC/SGSN in a Location Report message in step 6. +- 7) If a location estimate has been received from the UE in step 3 (i.e. use of MO-LR Short Circuit) or was successfully obtained in step (6), the MSC/SGSN sends a Subscriber Location Report to its associated V-GMLC with an indication of the periodic event occurrence, the LDR reference number, the H-GMLC address and may also include the indication whether the obtained location estimate satisfies the requested accuracy or not (provided that this indication is obtained from RAN or the UE with the location estimate). If no location estimate was obtained in step 3 or 6 (e.g. positioning failure or time out), a report indicating this shall be returned. +- 8) The V-GMLC sends an acknowledgement to the MSC/SGSN and the MSC/SGSN may record charging information. +- 9) The V-GMLC sends an LCS Service Response to the H-GMLC with an indication of the periodic event occurrence, the LDR reference number and the location estimate if this was successfully obtained. If the location estimate could not be obtained, the V-GMLC sends the LCS Service Response without the location estimate. The LDR reference number will be used by the H-GMLC to identify the source of the original periodic location request. The V-GMLC may record charging information. +- 10) The H-GMLC may perform a privacy check as described in clause 9.1.1. +- 11) The H-GMLC sends an LCS Service Response to the R-GMLC with an indication of the periodic event occurrence, the LDR reference number and the location estimate if this was successfully obtained. If the location estimate could not be obtained, the H-GMLC sends the LCS Service Response without the location estimate. If this is the final location report, the periodic location request shall be completed in the H-GMLC. The H-GMLC may record charging information. +- 12) The location information is passed to the LCS Client. If this is the final location report, the periodic location request shall be completed in the R-GMLC. The R-GMLC may record charging information. +- 13) to 14) If periodic reporting in the RAN was instigated in step 4 and location update notification was requested in step 3, an LCS Location Update is sent to the UE to indicate successful transfer of the first location estimate (or possibly transfer of a location failure report) towards the LCS Client. The UE acknowledges this. The UE may employ the LCS Location Update ack. to cancel the procedure (see Note 2). +- 15) to 24) If periodic reporting in the RAN was instigated in step 4, RAN obtains a new location estimate in step 15 and transfers this to the MSC/SGSN in step 16 after the reporting interval has transpired. The MSC/SGSN transfers the location estimate to the LCS client in steps 17 to 22. Steps 17 to 22 are as in steps 7 to 12. An LCS Location Update is then sent to the UE in step 23 and acknowledged in step 24 if requested in step 3. Steps 23 and 24 are as in steps 13 and 14. Steps 15-24 are repeated at the periodic location interval (as the RAN provides each new location estimate to the MSC/SGSN) until the number of reports is attained, or until there is a request + +from the RAN to hand the UE over to a different MSC/SGSN. Following transfer of the final location estimate to the LCS Client, the transfer and acknowledgment of an LCS Location Update in steps 23 and 24, if requested in step 3, could be omitted as an implementation option. + +- 25) The MSC/SGSN returns an LCS MO-LR Return Result to the UE indicating that the location estimate (or location estimates in case of periodic reporting in RAN was instigated at step 4 has been successfully transferred to the LCS client or not. +- 26) The MSC/SGSN may release the CM, MM or GMM and radio connection to the UE, if the UE was previously idle. +The UE is responsible for restarting the procedure at step 1 or 3 if the total number of location reports has not yet been reached. In the case of restarting at step 3, the CM, MM/GMM and radio connections would not be released. + +NOTE 1: In case of periodic reporting in the RAN is used, the LCS MO-LR TTTP invoke request sent by the UE in step 3 could include, besides the periodic reporting interval, a number of reports less than or equal to the remaining number of reports for the whole procedure. When a smaller number of reports was requested, the target UE would be responsible for reissuing further MO-LR requests, after periodic reporting from the RAN was completed, until the overall number of reports was attained. + +NOTE 2: After each location estimate (or possibly location failure report) has been transferred to the LCS client (e.g. after step 12, 22), the MSC/SGSN sends an LCS Location Update Invoke message to the UE indicating that the location estimate (or possibly location failure report) has been successfully transferred if this was requested by the UE in step 3. The UE acknowledges the receipt of the LCS Location Update Invoke message and a cancellation of location could be included if the UE subscriber wishes to cancel the periodic location procedure at that point. In the event that the UE cancels the procedure, the MSC/SGSN shall notify the V-GMLC, H-GMLC, R-GMLC and LCS Client using the procedure in clause 9.1.12.4. + +If the UE moves out of coverage of the PLMN(s) in which the location reports are allowed or if a conflict with the PLMNs preferred by the UE for other services prevents access to the PLMN(s) for periodic location, the UE terminates the procedure and stops sending LCS MO-LR Invoke. The UE may determine the need for termination if it is unable to instigate an MO-LR TTTP request for some period of time (e.g. some multiple of the required periodic location interval). + +If any LCS MO-LR Invoke TTTP request is rejected by the current serving PLMN with a cause indicating that the procedure cannot be supported (for temporary or permanent reasons) – e.g. MO-LR Short Circuit was initially agreed, but can no longer be supported or cannot be supported in the new PLMN – and the UE is unable to instigate the procedure in any other PLMN allowed when the procedure was originally started, the UE terminates the procedure and stops sending LCS MO-LR Invoke TTTP requests. + +#### 9.1.12.3 LCS Client cancellation of a Deferred Location Request – Periodic Location Event + +Figure 9.14 illustrates the procedure for cancelling the Deferred Location Request for the periodic location event when cancellation is requested by the LCS Client. + +![Sequence diagram for LCS Client cancellation of a Deferred MT-LR for Periodic Location. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The Client sends an LCS Cancel Service Request to the Requesting GMLC, which then forwards it to the Home GMLC. The Home GMLC sends a Send Routing Info for LCS to the HLR/HSS, which returns the routing info. The Home GMLC then forwards the request to the Visited GMLC, which provides the subscriber location to the MSC/SGSN. The MSC/SGSN sends an LCS Periodic Location Cancel to the UE, which responds with an ack. The MSC/SGSN then provides the subscriber location ack to the Visited GMLC, which sends an LCS Cancel Service Response to the Home GMLC, which finally sends the response to the Requesting GMLC, which then sends it to the Client.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC_R as GMLC (Requesting) + participant GMLC_H as GMLC (Home) + participant HLR_HSS as HLR/HSS + participant GMLC_V as GMLC (Visited) + participant MSC_SGSN as MSC/SGSN + participant RAN + participant UE + + Client->>GMLC_R: 1. LCS Cancel Service Request + GMLC_R->>GMLC_H: 2. LCS Cancel Service Request + GMLC_H->>HLR_HSS: 3. Send Routing Info for LCS + HLR_HSS-->>GMLC_H: 4. Send Routing Info for LCS ack. + GMLC_H->>GMLC_V: 5. LCS Cancel Service Request + GMLC_V->>MSC_SGSN: 6. Provide Subscriber Location + MSC_SGSN->>UE: 7. LCS Periodic Location Cancel + UE-->>MSC_SGSN: 8. LCS Periodic Location Cancel ack. + MSC_SGSN->>GMLC_V: 9. Provide Subscriber Location ack + GMLC_V->>GMLC_H: 10. LCS Cancel Service Response + GMLC_H->>GMLC_R: 11. LCS Cancel Service Response + GMLC_R->>Client: 12. LCS Cancel Service Response + +``` + +Sequence diagram for LCS Client cancellation of a Deferred MT-LR for Periodic Location. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MSC/SGSN, RAN, and UE. The Client sends an LCS Cancel Service Request to the Requesting GMLC, which then forwards it to the Home GMLC. The Home GMLC sends a Send Routing Info for LCS to the HLR/HSS, which returns the routing info. The Home GMLC then forwards the request to the Visited GMLC, which provides the subscriber location to the MSC/SGSN. The MSC/SGSN sends an LCS Periodic Location Cancel to the UE, which responds with an ack. The MSC/SGSN then provides the subscriber location ack to the Visited GMLC, which sends an LCS Cancel Service Response to the Home GMLC, which finally sends the response to the Requesting GMLC, which then sends it to the Client. + +**Figure 9.14: LCS Client cancellation of a Deferred MT-LR for Periodic Location** + +- 1) The LCS Client requests the cancellation of a previously requested Deferred Location Request. The LDR reference number that was included in the previous LCS Service Response sent by the R-GMLC shall be included in the request to indicate which outstanding LDR should be cancelled. +- 2) The R-GMLC sends the cancellation request to H-GMLC, including the LDR reference number. The R-GMLC may itself initiate the cancellation for some other reason, e.g. whenever the R-GMLC infers from the absence of periodic location reports that the service may have been terminated. +- 3) The H-GMLC may send a SEND\_ROUTING\_INFO\_FOR\_LCS message to the home HLR/HSS of the UE with the IMSI or MSISDN of this UE. This may be needed if the UE may no longer be served by the original V-PLMN or by the original SGSN or VMSC/MSC server. +- 4) The HLR/HSS returns the current SGSN and/or VMSC/MSC server for the UE and the V-GMLC address. +- 5) The H-GMLC forwards the LCS Cancel Service Request to V-GMLC with the LDR reference number which is received from the R-GMLC, the H-GMLC address and the SGSN or VMSC/MSC server address (e.g. received from the HLR/HSS). The H-GMLC may itself initiate the cancellation procedure, when the UE's privacy profile stored in the H-GMLC or in the PPR was changed. For every outstanding Deferred Location Request against that UE, the H-GMLC shall perform or ask the PPR to perform a new privacy check based on the updated privacy profile. If the new privacy check passes, i.e. the LCS Client is still allowed to position the target UE, the handling of the outstanding Deferred Location Request should be continued. Otherwise, if the new privacy check does not pass, i.e. the location estimate of the target UE is not allowed to be provided to the LCS Client, the H-GMLC shall initiate a cancellation procedure. If the H-GMLC cannot complete the new privacy check (e.g., because it requires information, such as UE location, not currently available to the H-GMLC), then the H-GMLC may initiate a cancellation procedure according to H-PLMN privacy policy. + +NOTE: The H-GMLC shall know that the UE subscriber's privacy profile has been changed in the PPR when the LCS Privacy Profile Update has been sent from PPR to H-GMLC as described in clause 9.1.1.2. + +- 6) The V-GMLC sends the Provide Subscriber Location request to MSC/SGSN, indicating a cancellation of a deferred location request and including the LDR reference number specified by the LCS Client in the LCS Cancel Service Request and the H-GMLC address received from the H-GMLC. The V-GMLC shall transfer the location cancellation even when the V-GMLC was not involved in establishing the periodic location request – e.g. if the target UE is now served by another V-PLMN. +- 7) The MSC/SGSN sends the LCS Periodic Location Cancellation request, including the LDR reference number and H-GMLC address, to the UE. If the periodic reporting is via the serving RAN as described in step 4 of figure 9.13, the periodic location cancellation request is also sent to RAN. +- 8) The UE stops the periodic location reporting and returns the LCS Periodic Location cancellation ack. to the MSC/SGSN. Return of an LCS Periodic Location cancellation ack. shall apply even when the UE has no knowledge of the periodic location procedure being cancelled (e.g. UE was powered off during the procedure). +- 9) The MSC/SGSN sends the cancellation acknowledgement to the V-GMLC in the Provide Subscriber Location Ack, with the LDR reference number and the H-GMLC address. +- 10) The V-GMLC sends the LCS Cancel Service Response to H-GMLC with the LDR reference number and the H-GMLC address. +- 11) H-GMLC sends the LCS Cancel Service Response to R-GMLC with the LDR reference number. +- 12) R-GMLC sends the LCS Cancel Service Response to the LCS Client. + +#### 9.1.12.4 UE cancellation of a Deferred Location Request – Periodic Location Event + +Figure 9.15 illustrates the procedure for cancelling the Deferred Location Request for the periodic location event when cancellation is requested by the UE. If a network entity (e.g. H-GMLC, V-GMLC, SGSN/MSC) cancels the Deferred Location Request, the procedure in clause 9.1.12.3 for LCS Client cancellation shall be used to cancel towards the UE and the procedure in this clause shall be used to cancel towards the LCS Client. + +![Sequence diagram showing UE cancellation of a Deferred MT-LR for Periodic Location. Lifelines: LCS Client, R-GMLC, H-GMLC, V-GMLC, MSC/SGSN, RAN, UE. The process involves 13 steps: 1. CS: CM Service Request / PS: Service Request (UE to MSC/SGSN); 2. CS: Authentication, Ciphering or CM Service Accept / PS: Part 1: Possible Security Procedures (MSC/SGSN to UE); 3. MO-LR Invoke (+ termination cause + LCS Client Address) (UE to MSC/SGSN); 4. Subscriber Location Report (MSC/SGSN to V-GMLC); 5. MO-LR Location Cancellation (V-GMLC to H-GMLC); 6. MO-LR Location Cancellation (H-GMLC to R-GMLC); 7. Location Cancellation (R-GMLC to LCS Client); 8. Location Cancellation ack (LCS Client to R-GMLC); 9. MO-LR Location Cancellation Ack (R-GMLC to H-GMLC); 10. MO-LR Location Cancellation Ack (H-GMLC to V-GMLC); 11. Subscriber Location Report ack. (V-GMLC to MSC/SGSN); 12. LCS MO-LR Return Result (MSC/SGSN to UE); 13. Release CM, MM/GMM, RR/RRC connections or (UE to MSC/SGSN).](c99bf3a0530a3e58f5f2d2790ba7441b_img.jpg) + +Sequence diagram showing UE cancellation of a Deferred MT-LR for Periodic Location. Lifelines: LCS Client, R-GMLC, H-GMLC, V-GMLC, MSC/SGSN, RAN, UE. The process involves 13 steps: 1. CS: CM Service Request / PS: Service Request (UE to MSC/SGSN); 2. CS: Authentication, Ciphering or CM Service Accept / PS: Part 1: Possible Security Procedures (MSC/SGSN to UE); 3. MO-LR Invoke (+ termination cause + LCS Client Address) (UE to MSC/SGSN); 4. Subscriber Location Report (MSC/SGSN to V-GMLC); 5. MO-LR Location Cancellation (V-GMLC to H-GMLC); 6. MO-LR Location Cancellation (H-GMLC to R-GMLC); 7. Location Cancellation (R-GMLC to LCS Client); 8. Location Cancellation ack (LCS Client to R-GMLC); 9. MO-LR Location Cancellation Ack (R-GMLC to H-GMLC); 10. MO-LR Location Cancellation Ack (H-GMLC to V-GMLC); 11. Subscriber Location Report ack. (V-GMLC to MSC/SGSN); 12. LCS MO-LR Return Result (MSC/SGSN to UE); 13. Release CM, MM/GMM, RR/RRC connections or (UE to MSC/SGSN). + +**Figure 9.15: UE cancellation of a Deferred MT-LR for Periodic Location** + +- 1) to 2) If the UE is in idle mode, the UE requests a radio connection setup and sends a CM Service Request indicating a request for call independent supplementary service to the VMSC/MSC server via RAN (CS domain). If the UE is in dedicated mode, the UE sends a CM Service Request on the already established radio connection. The VMSC/MSC server instigates authentication and ciphering if the UE was in idle mode or returns a CM Service Accept if the UE was in dedicated mode. + +For PS domain, in UMTS, if the UE is in idle mode, the UE requests a PS signalling connection and sends a Service Request indicating signalling to the SGSN via RAN. If the UE already has PS signalling connection, the UE does not need to send the Service Request. Security functions may be executed. These procedures are described in TS 23.060 [15]. In GSM this signalling step is not needed. + +- 3) The UE sends an LCS MO-LR Invoke to the VMSC/MSC Server (CS domain) or to the SGSN (PS domain) for cancellation of a transfer of location to a third party LCS client. This message includes the identity of the LCS client, the H-GMLC address, a termination cause (e.g. subscriber terminates the procedure) and the LDR Reference Number. The presence of the LDR Reference Number indicates that the cancellation is for a previously authorized periodic location request. +- 4) to 7) The cancellation request shall be transferred in succession from the MSC/SGSN to the V-GMLC, H-GMLC, R-GMLC serving the LCS client and finally may be transferred to the LCS client (e.g. if the LCS Client originated the periodic location request or was informed of a periodic location request originated by the UE as in clause 9.2.3). +- 8) to 11) The response transferred back to the MSC/SGSN acknowledges the cancellation. +- 12) The MSC/SGSN returns the acknowledgment to the UE in a LCS MO-LR Return Result message. +- 13) The UE may instigate release of the CM, MM/GMM and radio connections. + +### 9.1.13 IW-MT-LR Procedure + +Figure 9.16 describes the IW-MT-LR procedure. This procedure is applicable to the I-WLAN defined in TS 23.234 [52] and it is no longer maintained. + +![Sequence diagram of the IW-MT-LR procedure in I-WLAN. The diagram shows interactions between WLAN UE, WLAN AN, AAA, HSS/HLR, WAG, PDG, GMLC, and External LCS Client. The process starts with a connection setup, followed by an LCS request from the client to the GMLC, routing information exchange, UE routing info inquiry, positioning procedures, and finally an LCS response.](e05122559f56af5699789b7118d8fe87_img.jpg) + +``` + +sequenceDiagram + participant WLAN_UE as WLAN UE + participant WLAN_AN as WLAN AN + participant AAA as AAA + participant HSS_HLR as HSS/HLR + participant WAG as WAG + participant PDG as PDG + participant GMLC as GMLC + participant External_LCS_Client as External LCS Client + + Note over WLAN_UE, PDG: 1. Connection Setup, Authentication, Tunnel Establishment + External_LCS_Client->>GMLC: 2. LCS Request + GMLC->>HSS_HLR: 3. Routing info + HSS_HLR->>GMLC: 4. Routing info Ack + GMLC->>AAA: 5. UE Routing Info Inquiry + AAA->>GMLC: 6. UE Routing Info Inquiry Ack. + Note over WLAN_UE, GMLC: 7. Positioning Procedures + GMLC->>External_LCS_Client: 8. LCS Response + +``` + +Sequence diagram of the IW-MT-LR procedure in I-WLAN. The diagram shows interactions between WLAN UE, WLAN AN, AAA, HSS/HLR, WAG, PDG, GMLC, and External LCS Client. The process starts with a connection setup, followed by an LCS request from the client to the GMLC, routing information exchange, UE routing info inquiry, positioning procedures, and finally an LCS response. + +**Figure 9.16: IW-MT-LR in I-WLAN** + +NOTE 1: Even though figure 9.16 does not specify the specific services with IW-MT-LR, this flow can be applicable for both immediate and triggered services (e.g. periodic or change of area event case). + +1. A WLAN UE selects a WLAN AN and establishes the WLAN connection and is authenticated in I-WLAN. The WLAN AN may send the current location of WLAN AN to the WLAN UE. The WLAN AN may send its location to the AAA. The tunnel may be established with between WLAN UE and one of PDGs in PLMN. +2. An external LCS client sends the LCS request to the GMLC. An external LCS client requests the current location, e.g. immediate location request, from a GMLC. The LCS Client may also request a triggered location request, e.g. periodic or change of area event. The GMLC verifies the identity of the LCS client and its subscription to the LCS service requested and derives the MSISDN or IMSI or pseudonym of the target UE to be located and the LCS QoS from either subscription data or data supplied by the LCS client. + +The LCS request may carry also the Service Identity and the Codeword. The GMLC may verify that the Service Identity received in the LCS request matches one of the service identities allowed for the LCS client. If the service identity does not match one of the service identities for the LCS client, the GMLC shall reject the LCS request. Otherwise, the GMLC can map the received service identity in a corresponding service type. + +If the location request is originated by a Requestor, the Requestor Identity may be added to the LCS service request. The LCS client should authenticate the Requestor Identity but this is outside the scope of this specification. The LCS service request may also contain the type of the Requestor identity if the requestor identity was included. + +The GMLC performs privacy check on the basis of the UE user's privacy profile stored in the GMLC or PPR. + +3. Steps 3 and 4 may be skipped if the GMLC already has the address of the AAA server. Steps 3 to 6 may be skipped if the GMLC has alternative access to the UE's IP address (e.g. using dynamic DNS or from a previous interaction with the UE) or is able to instigate step 7 without knowing this address (e.g. using MT-SMS or WAP Push in the case of SUPL). GMLC requests the address of AAA server and WLAN UE capability to the HSS. In this case, the capability information of the WLAN UE refers to capability information of the terminal relevant to positioning such as whether the terminal supports the OMA SUPL (OMA AD SUPL [38], OMA TS ULP [39]) or whether it supports another location procedures. +4. HSS returns the address of AAA server of the target WLAN UE and the capability of the WLAN UE to GMLC. +5. If the target WLAN UE supports the OMA SUPL, GMLC queries AAA to obtain the address of WLAN UE. GMLC may request the location of WLAN UE. +6. If its location is available and the quality of position meets the LCS QoS requested by GMLC, then AAA responds with available location information of the WLAN UE to the GMLC. Otherwise, GMLC retrieves the address of WLAN UE from AAA. If there is no tunnel is available between the PDG and the WLAN UE, the AAA will return an indication that UE is not reachable. +7. GMLC initiates positioning procedure. This shall use SUPL procedures based on OMA SUPL (OMA AD SUPL [38], OMA TS ULP [39]). If the tunnel between the WLAN UE and the PDG is available and the GMLC has obtained the UE IP address, GMLC generates an SUPL initiation message, and transmits it to the WLAN UE by using the address of WLAN UE over available IP connection between the WLAN UE and the PDG. If the tunnel between the WLAN UE and the PDG is not available or if the GMLC did not obtain the UE IP address, GMLC sends an SUPL initiation message using the UE IP address if available or by other means (e.g. MT-SMS or WAP Push). +8. The location information obtained will be transferred to external LCS client. + +NOTE 2: The GMLC may, as an implementation option, cache the results received in step 4 and/or step 6 in order to avoid further queries when a location request is received for the same target UE at a later time and the AAA server address and/or WLAN UE address, respectively, has not changed. + +### 9.1.14 IW-MT-LR Procedure without HLR/HSS or AAA Query + +This procedure is applicable to the I-WLAN defined in TS 23.234 [52] and it is no longer maintained. + +Figure 9.17 illustrates current or last known location requests for an emergency services call, where an emergency services client (i.e. a Public Safety Answering Point) requests updated location information for the target UE. In order to support location of emergency calls from UICC-less terminals, TS 23.167 [36a] specifies that the IMS core shall push information identifying the terminal to the PSAP and GMLC during establishment of the emergency call. + +NOTE 1: In some regions, based on regional specifications, the GMLC may use correlation information that was previously provided to it by the IMS Core to identify the target UE. + +The IMS core also sends the correlation information to the PSAP during the call establishment as described in TS 23.167 [36a]. Using the correlation key the PSAP may request the initial or updated location information from the GMLC. The management of this regional correlation information (e.g. ESQK in North America) and support of the Le interface to the external LCS Client may be handled by a separate functional entity from the GMLC, e.g. a RDF as defined in TS 23.167 [36a]. + +![Sequence diagram for IW-MT-LR without an HLR/HSS or AAA Query. The diagram shows interactions between WLAN UE, WLAN AN, AAA, HSS/HLR, WAG, PDG, GMLC/SLP, and External LCS Client. The sequence includes: 1. Connection Setup, Authentication, Tunnel Establishment; 2. Emergency Call Establishment; 3. LCS Request (from External LCS Client to GMLC/SLP); 4. Positioning Procedures; 5. LCS Response (from GMLC/SLP to External LCS Client).](32ff77da4286b58c4778033acaa10836_img.jpg) + +``` + +sequenceDiagram + participant WLAN_UE as WLAN UE + participant WLAN_AN as WLAN AN + participant AAA + participant HSS_HLR as HSS/HLR + participant WAG + participant PDG + participant GMLC_SLP as GMLC/SLP + participant External_LCS_Client as External LCS Client + + Note over WLAN_UE, PDG: 1. Connection Setup, Authentication, Tunnel Establishment + Note over WLAN_UE, External_LCS_Client: 2. Emergency Call Establishment + External_LCS_Client->>GMLC_SLP: 3. LCS Request + Note over WLAN_UE, GMLC_SLP: 4. Positioning Procedures + GMLC_SLP->>External_LCS_Client: 5. LCS Response + +``` + +Sequence diagram for IW-MT-LR without an HLR/HSS or AAA Query. The diagram shows interactions between WLAN UE, WLAN AN, AAA, HSS/HLR, WAG, PDG, GMLC/SLP, and External LCS Client. The sequence includes: 1. Connection Setup, Authentication, Tunnel Establishment; 2. Emergency Call Establishment; 3. LCS Request (from External LCS Client to GMLC/SLP); 4. Positioning Procedures; 5. LCS Response (from GMLC/SLP to External LCS Client). + +**Figure 9.17: IW-MT-LR without an HLR/HSS or AAA Query** + +1. The WLAN UE selects a WLAN AN and establishes the WLAN connection and may be authenticated in I-WLAN. The tunnel is established between the WLAN UE and a PDG in PLMN. +2. The WLAN UE establishes an emergency services call as described in TS 23.167 [36a]. The UE determines its own location if possible. The UE may include the identifier of access node (e.g., MAC address of the AP), if available, as location identifier in the session request and possibly other readily available location information, e.g. GPS based coordinates or the street address of the UE or the AP as provided by the user of the UE. If the UE is not able to determine its own location, the UE may, if capable, request the location information from the IP-CAN or SLP. The case when the UE requests its own location information or enhanced location information from the SLP using OMA-SUPL is described in clause 9.2.5. The IP-CAN may return a representation of the location information to the UE. During this step, the IMS core may push the WLAN UE's identification and the location information provided by the UE to the LRF (GMLC) along with correlation information, if applicable. The GMLC may record this information but in some regions only for the duration of the call as the case may be. The correlation information may be regionally specific (e.g. as is the case for support of location for an emergency call in the CS domain in clause 9.1.3). The IMS core shall also send the correlation information to the PSAP/ emergency centre during the call establishment as specified in TS 23.167 [36a]. + +NOTE 2: The mechanism used by the UE to obtain location information from the I-WLAN IP-CAN is out of scope. One method that could be used is the mechanism defined by IEEE 802.11k Task Group for carrying location information (per RFC 3825) from one IEEE 802.11 station/AP to another IEEE 802.11 station/AP. + +3. An external LCS client associated with the emergency centre PSAP sends a location request to the GMLC for the initial location or an updated location for the WLAN UE. The request may include the address and the identification of the WLAN UE and in some regions may include correlation information that enables the GMLC to associate the request with the information stored in step 2. +4. If initial location was requested the procedure continues from step 5. If updated location was requested the GMLC initiates a positioning procedure where either the UE or GMLC determines the position of the UE. GMLC/SLP shall request the UE to establish a so called user plane connection with the GMLC/SLP and use the OMA SUPL mechanism specified by OMA (OMA AD SUPL [38], OMA TS ULP [39]) to transport location related assistance data and location information between the UE and GMLC/SLP. The UE may send the identifier of the access node (e.g. MAC address of the AP) to the GMLC and GMLC, possibly using an external database, maps this location identifier to the corresponding geographical information, e.g. coordinates or street address. GMLC may return this geographical information to the UE. + +NOTE 3: The location information obtained based on the mapping of an identifier of access node (e.g. MAC address of the AP) to location information stored in a database may not be correct, e.g. the location of the AP might be changed without any updates to the database. + +5. GMLC sends the initial location information, if so requested, or the updated location information obtained in step 4 to the external LCS client. + +### 9.1.15 EPC Mobile Terminating Location Request (EPC-MT-LR) + +Figure 9.18 illustrates the general network positioning for LCS clients external to the PLMN for EPC services. In this scenario, it is assumed that the target UE is identified using an MSISDN or IMSI. This procedure is applicable to a request from an LCS client for a current location, current or last known location or a deferred location for the UE availability event. + +![Sequence diagram for EPC Mobile Terminating Location Request (EPC-MT-LR) showing interactions between Client, GMLC, HLR/HSS, E-SMLC, MME, RAN, and UE.](1e8c50ad4fca7f315a407347dd5091cc_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC + participant HLR/HSS + participant E-SMLC + participant MME + participant RAN + participant UE + + Note over Client, HLR/HSS: 1. Common MT-LR procedure in PS and CS domain + GMLC->>MME: 2. Provide Subscriber Location + MME-->>GMLC: 2a. Provide Subscriber Location ack. + GMLC-->>Client: 2b. LCS Service Response + Note over MME, UE: 3. Network Triggered Service Request + MME->>UE: 4. NAS Location Notification Invoke + UE-->>MME: 5. NAS Location Notification Return Result + MME->>E-SMLC: 6. Location Request + Note over E-SMLC, RAN: 7. Positioning Procedure + E-SMLC-->>MME: 8. Location Response + MME-->>GMLC: 9. Provide Subscriber Location ack. + GMLC-->>E-SMLC: 9a. Subscriber Location Report + E-SMLC-->>MME: 9b. Subscriber Location Report ack + Note over Client, HLR/HSS: 10. Common MT-LR procedure in PS and CS domain + +``` + +Sequence diagram for EPC Mobile Terminating Location Request (EPC-MT-LR) showing interactions between Client, GMLC, HLR/HSS, E-SMLC, MME, RAN, and UE. + +Figure 9.18: General Network Positioning for EPC-MT-LR + +#### 9.1.15.1 Location Preparation Procedure + +- 1) For a request for a current location or a current or last known location the common PS and CS MT-LR procedure is performed as described in clause 9.1.1. For a request for a deferred location for the UE availability event, steps 1 and 2 of the deferred location request procedure are performed as described in clause 9.1.8.1. +- 2) GMLC sends a Provide Subscriber Location message to the MME indicated in step 1. This message carries the type of location information requested (e.g. current location and optionally, velocity), the UE subscriber's IMSI, LCS QoS information (e.g. accuracy, response time) and an indication of whether the LCS client has the override capability. For a session related location request, the message also carries the APN-NI to which the UE user has established the session. For a value added LCS client, the message shall carry the client name, the + +external identity of the LCS client and the Requestor Identity (if that is both supported and available), optionally the message may also carry the Service Type. Also the message may carry the type of the LCS client name and also the type of the Requestor identity if the requestor identity was included. If the result of the privacy check at H-GMLC/PPR indicated that the codeword shall be sent to the UE user, the message may carry also the codeword received from the LCS client. For a PLMN operator LCS client, the message shall carry the internal identity of the LCS client. If the Requestor Identity is provided, the GMLC shall send it as separate information. The message also shall carry the indicators of privacy related action which is described in clause 9.5.4, if it is provided by H-GMLC. If a deferred location was requested in step 1 for the UE availability event and if the GMLC supports delayed location reporting for UEs transiently not reachable ( i.e. because they are in extended idle mode DRX or PSM), the GMLC shall indicate support of delayed location reporting in this message. + +NOTE 1: For a deferred location request for the UE availability event, the GMLC interworks the procedure in clause 9.1.8 as applicable to the LCS client, R-GMLC, H-GMLC, HSS and V-GMLC with the procedure in this clause as applicable to the GMLC, MME, E-SMLC, RAN and UE. This means, for example, that the LDR reference number assigned by the H-GMLC in step 2 in clause 9.1.8.1 is not transferred by the GMLC to the MME in step 2 but is returned by the GMLC to the H-GMLC in steps 2b and 10. + +2a) If the GMLC indicates support of delayed location reporting in step 2 and the MME supports delayed location reporting for UEs transiently not reachable, the MME sends a Provide Subscriber Location ack message with a "UE transiently not reachable" indication. In this case, steps 9a and 9b are executed instead of step 9. If the GMLC indicates support of delayed location reporting in step 2, and the MME does not support delayed location reporting and the UE is transiently not reachable, a Provide Subscriber Location return error shall be returned with a suitable cause. + +NOTE 2: For compatibility with support of deferred location between an LCS client, R-GMLC and H-GMLC as defined in clause 9.1.8, if the GMLC and MME both support delayed location reporting, the MME returns a Provide Subscriber Location ack message in step 2a even if the UE is currently reachable. This will minimize delay in notifying the LCS client that the deferred location request was accepted. + +2b) If step 2a occurs, the GMLC returns an LCS Service Response to the LCS Client by instigating steps 5, 6 and 7 of the procedure in clause 9.1.8.1. + +3) If the GMLC is located in another PLMN or another country, the MME first authenticates that a location request is allowed from this PLMN or from this country. If not, an error response is returned. Secondly the MME checks if the UE is detached or suspended and in either such case an error response is returned. If the PSL message from the GMLC includes the indicators of privacy related action, the MME determines a required privacy related action as described in clause A.3. + +If the UE is not using Control Plane CIoT EPS Optimisation and if the UE is in ECM-IDLE state and is not in power saving mode and is currently reachable, the MME performs a network triggered service request as defined in TS 23.401 [41] in order to establish a signalling connection with the UE and assign a specific eNodeB. If step 2a was performed and the UE is transiently not reachable, the MME waits until the UE next becomes reachable and then performs a network triggered service request if needed to establish a signalling connection with the UE. + +If the UE is using Control Plane CIoT EPS Optimisation, procedures for Mobile Terminated Data Transport in Control Plane CIoT EPS optimisation as defined in TS 23.401 [41] are performed by the MME to establish a signalling connection with the UE. + +4) If the location request comes from a value added LCS client and the indicators of privacy related action indicates that the UE must either be notified or notified with privacy verification and the UE supports notification of LCS, a notification invoke message is sent to the target UE indicating the type of location request from the LCS Client (e.g. current location or "current or last known location") and the identity of the LCS client and the Requestor Identity (if that is both supported and available), whether privacy verification is required. Also the message may indicate the type of the LCS client name and also the type of the Requestor identity if the requestor identity was included. Moreover, the message may carry also the service type and the codeword. Optionally, the MME may after sending the NAS Location Notification Invoke message continue in parallel the location process, i.e. continue to step 6 without waiting for a LCS Location Notification Return Result message in step 5. + +5) The target UE notifies the UE user of the location request and, if privacy verification was requested, waits for the user to grant or withhold permission. The UE then returns a notification result to the MME indicating, if privacy verification was requested, whether permission is granted or denied. Optionally, this message can be returned some time after step 4, but before step 9. If the UE user does not respond after a predetermined time period, the MME shall infer a "no response" condition. The MME shall return an error response to the GMLC if privacy + +verification was requested and either the UE user denies permission or there is no response with the UE privacy profile received from the GMLC indicating barring of the location request. + +- 6) The MME selects a E-SMLC as described in clause 6.3.13 and sends a Location Request message to the selected E-SMLC. Once an MME has selected an E-SMLC it must continue to use that E-SMLC for the duration of the session. The Location Request includes the type of location information requested, the requested QoS, identity of serving cell, UE location capabilities and, if available, the Service Type. If the UE is in power saving mode, steps 4 and 5 do not apply, the location request specifies current or last known location and the MME has stored the last serving cell for the UE, this step may be performed to obtain the last known location. The location request also indicates RAT type and/or coverage level if applicable. If this step is performed after the MME receives the NAS Location Notification Return Result in step 5, the Location Request message contains the identity of the serving cell obtained from the S1-AP message that carries the NAS Location Notification Return Result. + +NOTE 3: If the UE is in connected mode and step 6 is performed without receiving NAS Location Notification Return Result in step 5, the MME may not have the most current serving cell identity if there was an intra-eNodeB handover. + +#### 9.1.15.2 Positioning Measurement Establishment Procedure + +- 7) If the requested location information and the location accuracy within the QoS can be satisfied based on parameters received from the MME, e.g. cell identity, the E-SMLC may send a Location Response immediately. If the requested location information indicates a last known location, the E-SMLC shall determine a last known location based on the cell identity and send a Location Response immediately. Otherwise, the E-SMLC determines the positioning method and instigates the particular message sequence for this method as described in clause 9.3a. If the position method returns position measurements, the E-SMLC uses them to compute a location estimate. If there has been a failure to obtain position measurements, the E-SMLC may use the current cell identity to derive an approximate location estimate. If an already computed location estimate is returned for an UE based position method, the E-SMLC may verify consistency with the current cell. If the location estimate so obtained does not satisfy the requested accuracy and sufficient response time still remains, the E-SMLC may instigate a further location attempt using the same or a different position method. If a vertical location coordinate is requested but the E-SMLC can only obtain horizontal co-ordinates, these may be returned. + +NB-IoT UEs may perform measurements for some positioning methods only when in ECM-IDLE state. An E-SMLC that is aware of this (e.g. from an indication sent by the UE) may allow additional response time to the UE (e.g. in the QoS) to obtain the measurements. An MME that is aware of this (e.g. from the UE access type) may also allow additional time for a location session to complete. + +#### 9.1.15.3 Location Calculation and Release Procedure + +- 8) When location information best satisfying the requested location type and QoS has been obtained, the E-SMLC returns it to the MME in a Location Response message. E-SMLC shall in its response include an indication whether the obtained location estimate satisfies the requested accuracy or not. The information of the positioning method used may be returned with the location information. If a location estimate could not be obtained, the E-SMLC returns a Location Response message containing a failure cause and no location estimate. +- 9) This step is executed only if step 2a was not executed. The MME returns the location information, its age and obtained accuracy indication to the GMLC, if the MME has not initiated the Privacy Verification process in step 4. If step 4 has been performed for privacy verification, the MME returns the location information only, if it has received a NAS Location Notification Return Result indicating that permission is granted. In these cases, the information about the positioning method used may be sent with the location information. If a NAS Location Notification Return Result message indicating that permission is not granted is received, or there is no response, with the requested privacy action or the UE subscription profile indicating barring of location, the MME shall return an error response to the GMLC. If the MME did not return a successful location estimate, but the privacy checks were successfully executed, the MME may return the last known location of the target UE if this is known and the LCS client is requesting the current or last known location. The MME may record charging information. +- 9a) This step is executed only if step 2a was executed. The MME shall send a Subscriber Location Report to the GMLC, and, if these were obtained in steps 6 to 8, the location information, its age and obtained accuracy indication to the GMLC, if the MME has not initiated the Privacy Verification process in step 4. If step 4 has been performed for privacy verification, the MME sends the location information only, if it has received a NAS + +Location Notification Return Result indicating that permission is granted. In these cases, the information about the positioning method used may be sent with the location information. If a NAS Location Notification Return Result message indicating that permission is not granted is received, or there is no response, with the requested privacy action or the UE subscription profile indicating barring of location, the MME shall send an error indication to the GMLC. The MME shall include in the Subscriber Location Report any identities for the UE received in step 2. The MME may record charging information. If MME relocation or change of MME happens before location information can be obtained or reported, the old MME includes an error cause code indicating that it cannot proceed with the request and includes the address of the new MME if available. The GMLC may reiterate then its request towards the new MME. + +9b) If step 9a was executed, the GMLC shall acknowledge receipt of the Subscriber Location Report. + +10) For a request for a current location or a current or last known location in step 1, the common MT-LR procedure in PS and CS domain as described in clause 9.1.1 is performed. For a request for a deferred location for the UE availability event in step 1, steps 11, 13, 14 and 15 of the procedure in clause 9.1.8.2 are performed. + +### 9.1.16 EPC-MT-LR without HLR Query + +Figure 9.19 illustrates current or last known location requests for an emergency services call, where an emergency services client (i.e., a Public Safety Answering Point) identifies the target UE and the serving LRF using correlation information that was previously provided to it by the IMS Core. The signalling used to provide the correlation information to the PSAP is defined in TS 23.167 [36a]. The correlation information may be used by the LRF to retrieve other information previously provided to it by the IMS Core as per TS 23.167 [36a] and/or MME as described in clause 9.1.17. This allows the V GMLC associated with the LRF to request location from the MME without first querying the home HLR of the target UE. This scenario therefore supports location of emergency calls from roamers or SIM-less emergency calls, or non-registered (U)SIM emergency calls, and requires that the initial location, as well as UE and MME identifying information had been pushed to the GMLC/LRF as per clause 9.1.17 or as per TS 23.167 [36a]. + +![Sequence diagram for Figure 9.19: Positioning for an Emergency Services EPC-MT-LR without HLR Query. The diagram shows the interaction between LCS Client, LRF/GMLC, HLR/HSS, E-SMLC, MME, RAN, and UE. The steps are: 1. LCS Service Request from LCS Client to LRF/GMLC; 2. Provide Subscriber Location from LRF/GMLC to MME; 3. Location Request from MME to E-SMLC; 4. Messages for individual positioning methods (between E-SMLC, MME, RAN, and UE); 5. Location Report from E-SMLC to MME; 6. Provide Subscriber Location ack. from MME to LRF/GMLC; 7. LCS Service Response from LRF/GMLC to LCS Client.](36fd537a1e39baa2471ecfaaf869751a_img.jpg) + +``` + +sequenceDiagram + participant LCS Client + participant LRF/GMLC + participant HLR/HSS + participant E-SMLC + participant MME + participant RAN + participant UE + + Note left of LCS Client: LCS Service Request + LCS Client->>LRF/GMLC: 1. LCS Service Request + LRF/GMLC->>MME: 2. Provide Subscriber Location + MME->>E-SMLC: 3. Location Request + Note right of E-SMLC: 4. Messages for individual positioning methods + E-SMLC->>MME: 5. Location Report + MME->>LRF/GMLC: 6. Provide Subscriber Location ack. + LRF/GMLC->>LCS Client: 7. LCS Service Response + +``` + +Sequence diagram for Figure 9.19: Positioning for an Emergency Services EPC-MT-LR without HLR Query. The diagram shows the interaction between LCS Client, LRF/GMLC, HLR/HSS, E-SMLC, MME, RAN, and UE. The steps are: 1. LCS Service Request from LCS Client to LRF/GMLC; 2. Provide Subscriber Location from LRF/GMLC to MME; 3. Location Request from MME to E-SMLC; 4. Messages for individual positioning methods (between E-SMLC, MME, RAN, and UE); 5. Location Report from E-SMLC to MME; 6. Provide Subscriber Location ack. from MME to LRF/GMLC; 7. LCS Service Response from LRF/GMLC to LCS Client. + +**Figure 9.19: Positioning for an Emergency Services EPC-MT-LR without HLR Query** + +- 1) Same as step 1 in figure 9.1 but with the LCS client (PSAP) identifying first the target UE and the serving LRF by previously supplied correlation information for the emergency call. +- 2) The LRF/GMLC may determine the MME by associating the correlation information received from the PSAP with other information received previously from the MME using an EPC NI LR as in clause 9.1.17 and/or from the IMS core as in TS 23.167 [36a]. The Provide Subscriber Location message sent to the MME carries, if available, the MSISDN or the IMSI and, if available, the IMEI for the target UE, as well as the required QoS and an indication of a location request from an emergency services client. The MME identifies the target UE using the IMSI, MSISDN and/or the IMEI. In case of a SIM-less emergency call, or non-registered (U)SIM emergency call, the IMEI shall be always sent. +- 3) The MME sends a Location Request to the E-SMLC, as for a normal EPC MT LR. + +- 4) E-SMLC performs positioning as for a normal EPC MT LR. +- 5) E-SMLC returns a location estimate to the MME as for a normal EPC MT LR. +- 6) The MME returns the location information, its age and obtained accuracy indication to the LRF/GMLC. The information about the positioning method used may be sent with the location information. If the E-SMLC did not return a successful location estimate, the MME may return the last known location of the target UE if this is known and the LCS client is requesting the current or last known location. +- 7) The LRF sends the location service response to the LCS client (PSAP). + +NOTE: The MME determined by the LRF/GMLC in step 2 must be the current MME for the UE. In the event of handover to a new MME, this may require updating of the GMLC using the EPC NI LR procedure in clause 9.1.17. + +### 9.1.17 EPC Network Induced Location Request (EPC-NI-LR) + +At any time after detecting an emergency situation (i.e. after emergency Attach, UE requested emergency PDN Connectivity), the MME may initiate the EPC Network Induced Location Request (EPC NI LR) procedure. The procedure is illustrated in figure 9.20. + +![Sequence diagram for EPC Network Induced Location Request (EPC-NI-LR) showing interactions between LCS Client, LRF/GMLC, HLR/HSS, E-SMLC, MME, RAN, and UE.](a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant MME + participant E-SMLC + participant HLR/HSS + participant LRF/GMLC + participant LCS_Client as LCS Client + + Note right of MME: 1. Emergency Attach or Setup Emergency Bearer + MME->>E-SMLC: 2. Location Request + Note right of E-SMLC: 3. Messages for individual positioning methods + E-SMLC->>MME: 4. Location Response + MME->>LRF/GMLC: 5. Subscriber LCS Report + LRF/GMLC->>MME: 6. Subscriber LCS Report ACK + MME->>LRF/GMLC: 7. Location Information + Note right of MME: 8. Deactivate Emergency Bearer + MME->>LRF/GMLC: 9. Subscriber LCS Report + LRF/GMLC->>MME: 10. Subscriber LCS Report ACK + +``` + +Sequence diagram for EPC Network Induced Location Request (EPC-NI-LR) showing interactions between LCS Client, LRF/GMLC, HLR/HSS, E-SMLC, MME, RAN, and UE. + +Figure 9.20: Network Induced Location Request for EPC + +- 1) For the emergency call invocation from the user, the UE performs emergency attach if not attached or requests emergency PDN connection if already normal attached. As part of the Attach procedure, the UE support of LPP indication is provided by the UE to the MME. When an emergency attach or emergency PDN connection establishment is detected, the MME initiates the EPC-NI-LR procedure. +- 2) The MME selects a E-SMLC as described in clause 6.3.13 and sends a Location Request message to the selected E-SMLC. Once an MME has selected an E-SMLC it must continue to use that E-SMLC for the duration of the session. The Location Request includes the type of location information requested, the requested QoS, identity of serving cell and UE capability to support LPP. + +NOTE: If the UE is in connected mode and step 2 was not performed immediately after step 1, the MME may not have the most current serving cell identity if there was an intra-eNodeB handover. + +#### 9.1.17.1 Positioning Measurement Establishment Procedure + +- 3) If the requested location information and the location accuracy within the QoS can be satisfied based on parameters received from the MME, e.g. cell identity, the E-SMLC may send a Location Response immediately. Otherwise, the E-SMLC determines the positioning method and instigates the particular message sequence for + +this method as described in clause 9.3a. If the position method returns position measurements, the E-SMLC uses them to compute a location estimate. If there has been a failure to obtain position measurements, the E-SMLC may use the current cell identity to derive an approximate location estimate. If an already computed location estimate is returned for an UE based position method, the E-SMLC may verify consistency with the current cell identity. If the location estimate so obtained does not satisfy the requested accuracy and sufficient response time still remains, the E-SMLC may instigate a further location attempt using the same or a different position method. If a vertical location co-ordinate is requested but the E-SMLC can only obtain horizontal co-ordinates, these may be returned. + +#### 9.1.17.2 Location Calculation and Release Procedure + +- 4) When a location estimate best satisfying the requested QoS has been obtained, the E-SMLC returns a Location Response to the MME with an indication whether the obtained location estimate satisfies the requested accuracy or not. This message carries the location estimate that was obtained. If a location estimate was not successfully obtained, a failure cause is included in the Location Response. +- 5) The MME may determine the GMLC and emergency services client using the cell identity or the location estimate or according to some fixed association for the MME. The MME shall send a Subscriber Location Report to the GMLC carrying the IMEI and if available the IMSI and MSISDN of the UE, the event causing the message (EMERGENCY\_CALL\_ORIGINATION), and, if these were obtained in steps 2 to 4, the location estimate and its age and the indication received from E-SMLC whether the obtained location estimate satisfies the requested accuracy or not. The serving cell identity of the UE may also be sent if available. The MME shall include its own address. The MME may record charging information. +- 6) The GMLC shall acknowledge receipt of the location estimate provided that the associated LRF serves the emergency services LCS client and the client is accessible. These conditions would normally be fulfilled if the LRF either already has created, or expects to later create, a record for the UE for the emergency services session as described in clause 9.8.4. +- 7) The LRF associated with the GMLC treats the received location estimate as described in clause 9.8.4: e.g. may use the location information to assist routing of the emergency session to the PSAP/emergency centre and/or may transfer the location information to the emergency services LCS client immediately or upon request from the client. The LRF/GMLC may store the information received in step 5: e.g. may store the UE identity and the address of the MME. The LRF/GMLC may record charging information. +- 8) At some point, MME determines that emergency service is no longer active (e.g. EPS bearer for emergency service is deactivated). +- 9) The MME may send a Subscriber Location Report to the GMLC carrying the same UE's information as in step 5 and the event causing the message (EMERGENCY\_CALL\_RELEASE). +- 10) The GMLC shall acknowledge receipt of the location report from MME. + +NOTE: Determination of the GMLC in step 5 must ensure a match with any LRF/GMLC used by the IMS Core to assist with location retrieval for, and/or routing of, the IMS Emergency call as described in clause 9.8.4. + +### 9.1.18 EPC Post Positioning Notification and Verification Procedure + +Figure 9.21 illustrates the post positioning notification and verification procedure. + +![Sequence diagram of EPC Post Positioning Notification and Verification Procedure. Lifelines: Client, GMLC, HLR/HSS, E-SMLC, MME, RAN, UE. The process involves a common MT-LR procedure, a 'Provide Subscriber Location' message from GMLC to MME, a network triggered service request from MME to UE, NAS location notification invoke/return, and a 'Provide Subscriber Location ack' from MME to GMLC.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC + participant HLR/HSS + participant E-SMLC + participant MME + participant RAN + participant UE + + Note left of Client: 1. Common MT-LR procedure in PS and CS domain + GMLC->>MME: 2. Provide Subscriber Location + Note right of MME: 3. Network Triggered Service Request + MME->>UE: 4. NAS Location Notification Invoke + UE-->>MME: 5. NAS Location Notification Return Result + MME-->>GMLC: 6. Provide Subscriber Location ack + Note left of Client: 7. Common MT-LR procedure in PS and CS domain + +``` + +Sequence diagram of EPC Post Positioning Notification and Verification Procedure. Lifelines: Client, GMLC, HLR/HSS, E-SMLC, MME, RAN, UE. The process involves a common MT-LR procedure, a 'Provide Subscriber Location' message from GMLC to MME, a network triggered service request from MME to UE, NAS location notification invoke/return, and a 'Provide Subscriber Location ack' from MME to GMLC. + +**Figure 9.21: EPC Post Positioning Notification and Verification Procedure** + +- 1) Common PS and CS MT-LR procedure as described in clause 9.1.1. +- 2) The GMLC sends a Provide Subscriber Location message to the MME with an indication of "notification only". This message carries the UE subscriber's IMSI. For a session related location request, the message also carries the APN-NI to which the user has established the session. For a value added LCS client, the message shall carry the client name, the external identity of the LCS client and the Requestor Identity (if that is both supported and available), optionally the message may also carry the Service Type. Also the message may carry the type of the LCS client name and also the type of the Requestor identity if the requestor identity was included. If the result of the privacy check at H-GMLC/PPR indicated that the codeword shall be sent to the UE user, the message may carry also the codeword received from the LCS client. For a PLMN operator LCS client, the message shall carry the internal identity of the LCS client. If the Requestor Identity is provided, the GMLC shall send it as separate information. +- 3) The MME first checks if the UE is detached or suspended. If this is the case, an error response is returned. The MME determines a required privacy related action as described in Annex A.3 based on the indicators of privacy related action in the PSL message from the GMLC. + +If the UE is not using Control Plane CIoT EPS Optimisation and if the UE is in ECM-IDLE state, the MME performs a network triggered service request as defined in TS 23.401 [41] in order to establish a signalling connection with the UE and assign a specific eNodeB. + +If the UE is using Control Plane CIoT EPS Optimisation, procedures for Mobile Terminated Data Transport in Control Plane CIoT EPS optimisation as defined in TS 23.401 [41] are performed by the MME to establish a signalling connection with the UE. + +- 4) A notification invoke message is sent to the target UE indicating a location type of notification and verification only, the identity of the LCS client and the Requestor Identity (if that is both supported and available), whether privacy verification is required. Also the message may indicate the type of the LCS client name and also the type of the Requestor identity if the requestor identity was included. Moreover, the message may carry also the service type and the codeword. +- 5) The target UE notifies the UE user of the location request and, if privacy verification was requested, waits for the user to grant or withhold permission. The UE then returns a notification result to the MME indicating, if privacy verification was requested, whether permission is granted or denied. If the UE user does not respond after a predetermined time period, the MME shall infer a "no response" condition. The MME shall return an error response to the GMLC if privacy verification was requested and either the UE user denies permission or there is no response with the UE subscription profile indicating barring of the location request. +- 6) The MME returns the indication of successful notification and verification result, if it has received a NAS Location Notification Return Result indicating that permission is granted. If a LCS Location Notification Return Result message indicating that permission is not granted is received, or there is no response, with the requested privacy action or the UE subscription profile indicating barring of location, the MME shall return an error response to the GMLC. +- 7) Common MT-LR procedure in PS and CS domain as described in clause 9.1.1. + +### 9.1.19 Deferred EPC-MT-LR for Periodic and Triggered Location + +The procedures for periodic and triggered location for EPC services support instigation and cancellation of location reporting at periodic intervals or whenever some other trigger event is detected by the UE. The supported trigger events comprise an area event (where a UE enters, leaves or remains within a predefined area) and a motion event. In this version of the specification, only one type of reporting may be included in any request from among periodic, area event and motion event. In the case of the area event, a target area can be defined by a geographical area, PLMN identity, country code or geopolitical name. Details of the target area are contained in the LCS Service Request message, see clause 5.5.1. In the case of the motion event, motion corresponds to movement by the UE exceeding a linear distance threshold from a previous location. The procedure supports UE mobility between different serving MMEs and different serving PLMNs without interruption of event reporting. + +#### 9.1.19.1 Instigation and Reporting of Periodic and Triggered Location + +Figure 9.1.19.1-1 illustrates the procedure used to instigate and perform event reporting for a periodic and triggered EPC-MT-LR request from an LCS client. + +![Sequence diagram illustrating the Deferred EPC-MT-LR procedure for Periodic and Triggered Location. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), E-SMLC, MME, RAN, and UE. The process involves an initial LCS Service Request, handling between GMLCs, location reporting, and subsequent periodic or triggered location updates.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC_R as GMLC (Requesting) + participant GMLC_H as GMLC (Home) + participant HLR_HSS as HLR/HSS + participant GMLC_V as GMLC (Visited) + participant E_SMLC as E-SMLC + participant MME + participant RAN + participant UE + + Note left of Client: 1. LCS Service Request + Client->>GMLC_R: 1. LCS Service Request + Note over GMLC_R, GMLC_H: 2. LCS service request handling between GMLCs + GMLC_R->>GMLC_H: 2. LCS service request handling between GMLCs + Note over GMLC_H, GMLC_V: 3. Provide Subscriber Location + GMLC_H->>GMLC_V: 3. Provide Subscriber Location + GMLC_V-->>GMLC_H: 4. Provide Subscriber Location ack. + Note over GMLC_H, GMLC_R: 5. LCS Service Response + GMLC_H->>GMLC_R: 5. LCS Service Response + Note over GMLC_R, Client: 6. LCS Service Response + GMLC_R->>Client: 6. LCS Service Response + Note over Client, GMLC_R: 7. LCS Service Response + Client->>GMLC_R: 7. LCS Service Response + Note over MME, UE: 8. Paging, Authentication, Notification + MME->>UE: 8. Paging, Authentication, Notification + Note over MME, UE: 9. LCS Periodic-Triggered Event Invoke + MME->>UE: 9. LCS Periodic-Triggered Event Invoke + UE-->>MME: 10. LCS Periodic-Triggered Event Invoke ack. + Note over Client, MME: 11. LCS Service Response + Client->>MME: 11. LCS Service Response + Note over RAN, UE: 12. Event Detected + RAN->>UE: 12. Event Detected + Note over RAN, UE: 13. UE Triggered Service Request or Connection Resume + RAN->>UE: 13. UE Triggered Service Request or Connection Resume + Note over RAN, MME: 14. LCS MO-LR Invoke (location estimate) + RAN->>MME: 14. LCS MO-LR Invoke (location estimate) + Note over E_SMLC, MME: 15. Location Request + E_SMLC->>MME: 15. Location Request + Note over E_SMLC, GMLC_V: 16. Positioning Procedure + E_SMLC->>GMLC_V: 16. Positioning Procedure + Note over E_SMLC, MME: 17. Location Response + E_SMLC->>MME: 17. Location Response + Note over E_SMLC, GMLC_V: 18. LCS MO-LR Return Result + E_SMLC->>GMLC_V: 18. LCS MO-LR Return Result + Note over GMLC_V, GMLC_H: 19. Subscriber Location Report + GMLC_V->>GMLC_H: 19. Subscriber Location Report + GMLC_H-->>GMLC_V: 20. Subscriber Location Report Ack. + Note over GMLC_H, GMLC_R: 21. LCS Service Response + GMLC_H->>GMLC_R: 21. LCS Service Response + Note over GMLC_R, Client: 22. Privacy check + GMLC_R->>Client: 22. Privacy check + Note over Client, GMLC_R: 23. LCS Service Response + Client->>GMLC_R: 23. LCS Service Response + Note over Client, GMLC_R: 24. LCS Service Response + Client->>GMLC_R: 24. LCS Service Response + Note over RAN, UE: 25. Event Detected + RAN->>UE: 25. Event Detected + +``` + +Sequence diagram illustrating the Deferred EPC-MT-LR procedure for Periodic and Triggered Location. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), E-SMLC, MME, RAN, and UE. The process involves an initial LCS Service Request, handling between GMLCs, location reporting, and subsequent periodic or triggered location updates. + +**Figure 9.1.19.1-1: Deferred EPC-MT-LR procedure for Periodic and Triggered Location** + +- 1) The LCS Service Request provides the type of periodic or triggered location reporting being requested and associated parameters. For periodic location, the LCS Service Request includes the time interval between successive location reports, the total number of reports and may include location QoS. For area event reporting, the LCS Service Request includes details of the target area, whether the event to be reported is the UE being inside, entering into or leaving the target area, the duration of event reporting, the minimum and maximum time intervals between successive event reports, the maximum event sampling interval, whether location estimates shall be included in event reports (and associated location QoS), and whether only one location report is required or more than one. If the target area is expressed by a local coordinate system or a geopolitical name, the R-GMLC shall convert the target area to a geographical area expressed by a shape as defined in TS 23.032 [11]. For motion event reporting, the LCS Service Request includes the threshold linear distance, the duration of event reporting, the minimum and maximum time intervals between successive event reports, the maximum event sampling interval, whether location estimates shall be included in event reports (and associated location QoS), and whether only one location report is required or more than one. +- 2) LCS service request handling is performed between GMLCs as described in clause 9.1.1. The information received by the R-GMLC is transferred to the H-GMLC. The H-GMLC should record the received information + +and relevant parameters. The H-GMLC assigns an LDR reference number to the LCS Service request and an optional list of reporting PLMNs (which should include the serving PLMN), then transfers the information to the V-GMLC, including the LDR reference number, the H-GMLC address and any list of reporting PLMNs. + +- 3) In case area event reporting is requested, if the target area is defined by a shape in TS 23.032 [11], the V-GMLC converts the target area into a corresponding list of cell identities and/or tracking areas. If the V-GMLC cannot convert the entire target area into network identities, it shall reject the request and send an LCS service response to the H-GMLC with the appropriate error cause. The V-GMLC then conveys the location request to the MME in a Provide Subscriber Location request including details of the events to be reported, the LDR reference number, the H-GMLC address and any list of reporting PLMNs. +- 4) The MME verifies the UE capabilities with regard to the support of location service related call independent supplementary services (e.g. notification for LCS). If either the UE does not support location service related call independent supplementary services or the MME does not support the deferred location request for periodic and triggered location (for temporary or permanent reasons), a Provide Subscriber Location error response shall be returned with a suitable error cause. Otherwise, the MME returns a Provide Subscriber Location Ack. to confirm that the request has been accepted by the MME. + +NOTE 1: There is no UE capability information directly indicating support of a deferred periodic and triggered location request. However, if the UE supports at least one location service related call independent supplementary service (such as notification for LCS), the MME can assume support for deferred periodic and triggered location. If the UE does not recognize the request in step 9, it may return a Facility Rejected indication in step 10 (as defined in TS 24.008 [24]) to the MME in which case, the MME would terminate the request by instigating steps 19-24 with an appropriate error cause in the Subscriber Location Report sent at step 19. + +- 5) to 7) The V-GMLC returns the LCS Service Response via the H-GMLC and R-GMLC to the LCS Client to notify whether the periodic and triggered location request was accepted or not. When the H-GMLC returns the LCS Service Response to the R-GMLC, the LDR reference number assigned by the H-GMLC shall be included, and the R-GMLC may transfer the LDR reference number, or another reference number assigned by the R-GMLC, to the LCS Client in the LCS Service Response. + +NOTE 2: The LCS Service Response does not confirm that location reporting was activated in the UE or that the UE will necessarily be able to support the request. However, the response does confirm the capability and intent to support the request on the network side and may be useful to the LCS client when a response from the UE is delayed due to the UE being temporarily unreachable (e.g. if in PSM). + +- 8) If the UE is currently not reachable (e.g. when in PSM), the MME waits until the UE again becomes reachable. When the UE is reachable, if the UE is in ECM-IDLE state, the MME performs paging, authentication and ciphering. If privacy notification/verification was requested and the UE supports location service related call independent supplementary services, the MME sends an LCS Location Notification Invoke message to the target UE with a location type indicating activation of a deferred location request, a deferred location event type indicating the type of event (i.e. entering into area, leaving from area, being inside area, periodic or motion) and an indication as to whether privacy verification is required. LCS Location Notification is further specified in clause 9.1.15. If privacy verification was requested, the UE returns an LCS Location Notification Return Result to the MME indicating whether permission is granted or denied. If the UE denies permission or does not return a response when a response is required, the MME terminates the request as described for step 11. If the UE changes serving MME before becoming reachable from the MME, the MME returns a Subscriber Location Report to the V-GMLC indicating a change of MME and including the new MME address if available. The V-GMLC may then forward the error to the LCS client via the H-GMLC and R-GMLC or repeat step 3 to transfer the periodic and triggered location request to the new MME if provided. In this case, when step 4 recurs, the V-GMLC does not repeat steps 5-7 as the LCS client was already informed of network acceptance of the request. +- 9) The MME sends an LCS Periodic-Triggered Event Invoke to the UE carrying all of the event related information received from the V-GMLC, the LDR reference number, the H-GMLC address, the list of reporting PLMNs if provided and any requested QoS in the case that location estimates are required. +- 10) If the UE supports periodic and triggered location according to the request received in step 9 and currently has resources to service the request, the UE sends an acknowledgement to the MME. Otherwise, the UE sends a return error response to the MME with a suitable error cause. +- 11) If the UE cannot support the periodic and triggered location request, a Subscriber Location Report shall be returned to the V-GMLC with a suitable error cause and including the LDR reference number and H-GMLC address. Otherwise, if the UE confirms support of the periodic and triggered location request, a Subscriber + +Location Report shall be returned to the V-GMLC indicating that event reporting was activated in the UE and including the LDR reference number and H-GMLC address. If location estimates are required for subsequent event reports, the MME should obtain the current UE location as in steps 15-17 and include the location estimate in the Subscriber Location Report. The V-GMLC returns an LCS Service Response via the H-GMLC and R-GMLC to the LCS Client to notify whether the periodic and triggered location request was activated in the UE. When the H-GMLC returns the LCS Service Response to the R-GMLC, the LDR reference number assigned by the H-GMLC and H-GMLC address shall be included, and the R GMLC may transfer the LDR reference number to the LCS Client in the LCS Service Response. The V-GMLC, H-GMLC and/or R-GMLC may record charging information for the request. Following step 11, the MME and V-GMLC may release all resources for the request including any state information. + +NOTE 3: The LCS Service Response with an activation indication confirms to the LCS client that event reporting has started in the UE. + +12) For the area event or motion event, the UE monitors the requested event at intervals equal to or less than the maximum event sampling interval. An event trigger is detected by the UE when any of the following occur: (i) a requested area event or motion event has been detected and the minimum reporting time interval has elapsed since the last report (if this is not the first event report); (ii) a requested periodic location event has occurred; or (iii) the maximum reporting time for an area event or motion event has expired. When an event trigger is detected, the UE proceeds to step 13 once the UE can register via E-UTRAN access with a PLMN in the list of reporting PLMNs received at step 9 or with the original serving PLMN if no list of reporting PLMNs was provided or if the UE does not support the list of reporting PLMNs. If the UE cannot register with a permitted PLMN, the UE waits until a permitted PLMN can be accessed in order to report the event, or for the periodic and triggered location request to terminate due to cancellation by the LCS client, cancellation by the UE or expiration of the allowed duration. + +NOTE 4: If the UE uses a different serving PLMN to report occurrence of the area event, the UE still continues to use the target area provided by the original serving PLMN which contains cell IDs and/or TAs for the original serving PLMN. + +NOTE 5: The restriction to use only permitted PLMNs does not affect PLMN selection. + +13) If the UE is not using Control Plane CIOT EPS Optimisation and if the UE is in ECM-IDLE state, the UE performs a UE triggered service request or connection resume as defined in TS 23.401 [41] in order to obtain a signalling connection to a serving MME. + +If the UE is using Control Plane CIoT EPS Optimisation, procedures for Mobile Originated Data Transport in Control Plane CIoT EPS optimisation as defined in TS 23.401 [41] are performed by the UE to establish a signalling connection with the MME. + +NOTE 6: The MME and V-GMLC for steps 13 to 24 may be different to the MME and V-GMLC for steps 1 to 11. + +14) The UE sends an LCS MO-LR Invoke to the MME indicating an event report for a deferred periodic and triggered location request. The message includes the type of event trigger being reported (e.g. whether a normal event or expiration of the maximum reporting interval), the LDR reference number, H-GMLC address and whether a location estimate is required. When a location estimate is required (e.g. for a periodic location event or for an area event or motion event if requested by the LCS client), the UE shall include any QoS received in step 9 and a location estimate if a location estimate is currently available. The UE shall also indicate whether the periodic and triggered location request is now terminated in the UE (e.g. due to expiration of the reporting duration or because only one event report was requested). + +NOTE 7: Provision of a location estimate when requested also applies to the trigger event corresponding to expiration of the maximum reporting interval for an area event or motion event. + +15-17) If the UE indicates that a location estimate is required in step 14, the MME shall instigate location of the UE as described in steps 6-8 of clause 9.1.15 if a location estimate is not provided by the UE in step 14 and may optionally instigate location of the UE if a location estimate is provided by the UE in step 14. In the latter case, the location estimate provided by the UE shall be included in the location request sent to the E-SMLC in step 15. + +18) The MME sends an MO-LR Return Result to the UE confirming that the event report will be sent. If the MME is unable to send the event report (e.g. because this capability is not supported by the MME), an MO-LR return error is returned to the UE. The UE may terminate event reporting after an implementation defined number of MO-LR return errors are received. + +- 19) The MME selects a V-GMLC in the same network and sends a Subscriber Location Report to the V-GMLC with an indication of the type of event being reported, the LDR reference number, the H-GMLC address, whether the location request is now terminated in the UE, any location estimate provided in step 13 or obtained in steps 14-16 and information on positioning methods used for the location estimate. The MME shall also include the UE IMSI. +- 20) The V-GMLC sends an acknowledgement to the MME and the MME may record charging information. +- 21) The V-GMLC forwards the information received in step 19 to the H-GMLC. The V-GMLC may record charging information. +- 22) The H-GMLC identifies the location request to which the message received in step 21 applies using the LDR reference number and IMSI. The H-GMLC may perform a privacy check as described in clause 9.1.1. +- 23) The H-GMLC forwards the information received from the V-GMLC in an LCS Service Response to the R-GMLC. If the UE indicates termination of the location request, the periodic location request shall be completed in the H-GMLC. The H-GMLC may record charging information. +- 24) The R-GMLC transfers the event report and any included location estimate to the LCS Client. If the UE indicates termination of the location request, the location request shall be completed in the R-GMLC. The R-GMLC may record charging information. +- 25) If the UE did not terminate the location request following step 18, the UE continues to monitor for the requested event as in step 12 and reports each occurrence of the requested event as in steps 13-24 until expiration of the requested duration or until the UE terminates reporting for other reasons. + +#### 9.1.19.2 LCS Client cancellation of a Deferred Location Request for Periodic and Triggered Location + +Figure 9.1.19.2-1 illustrates the procedure for cancelling a Deferred Location Request for periodic and triggered location when cancellation is requested by the LCS Client. + +![Sequence diagram illustrating the procedure for cancelling a Deferred Location Request for periodic and triggered location. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MME, RAN, and UE.](408c4798ea60469e0728a7cbbd598668_img.jpg) + +``` + +sequenceDiagram + participant Client + participant GMLC_Req as GMLC (Requesting) + participant GMLC_Home as GMLC (Home) + participant HLR_HSS as HLR/HSS + participant GMLC_Visited as GMLC (Visited) + participant MME + participant RAN + participant UE + + Note right of Client: 1. LCS Cancel Service Request + Client->>GMLC_Req: 1. LCS Cancel Service Request + Note right of GMLC_Req: 2. LCS Cancel Service Request + GMLC_Req->>GMLC_Home: 2. LCS Cancel Service Request + Note right of GMLC_Home: 3. Send Routing Info for LCS + GMLC_Home->>HLR_HSS: 3. Send Routing Info for LCS + Note right of HLR_HSS: 4. Send Routing Info for LCS ack. + HLR_HSS->>GMLC_Home: 4. Send Routing Info for LCS ack. + Note right of GMLC_Home: 5. LCS Cancel Service Request + GMLC_Home->>GMLC_Visited: 5. LCS Cancel Service Request + Note right of GMLC_Visited: 6. Provide Subscriber Location + GMLC_Visited->>MME: 6. Provide Subscriber Location + Note right of MME: 7. Paging, Authentication, Notification + MME->>RAN: 7. Paging, Authentication, Notification + RAN->>UE: 7. Paging, Authentication, Notification + Note right of UE: 8. LCS Periodic Location Cancel + UE->>MME: 8. LCS Periodic Location Cancel + Note right of MME: 9. LCS Periodic Location Cancel ack. + MME->>UE: 9. LCS Periodic Location Cancel ack. + Note right of MME: 10. Provide Subscriber Location ack. + MME->>GMLC_Visited: 10. Provide Subscriber Location ack. + Note right of GMLC_Visited: 11. LCS Cancel Service Response + GMLC_Visited->>GMLC_Home: 11. LCS Cancel Service Response + Note right of GMLC_Home: 12. LCS Cancel Service Response + GMLC_Home->>GMLC_Req: 12. LCS Cancel Service Response + Note right of GMLC_Req: 13. LCS Cancel Service Response + GMLC_Req->>Client: 13. LCS Cancel Service Response + +``` + +Sequence diagram illustrating the procedure for cancelling a Deferred Location Request for periodic and triggered location. The diagram shows interactions between Client, GMLC (Requesting), GMLC (Home), HLR/HSS, GMLC (Visited), MME, RAN, and UE. + +Figure 9.1.19.2-1: LCS Client cancellation of a Deferred MT-LR for Periodic and Triggered Location + +- 1) The LCS Client requests the cancellation of a previously requested Deferred Location Request for periodic and triggered location. The LDR (or other) reference number that was included in the previous LCS Service Response sent by the R-GMLC shall be included in the request to indicate which outstanding LDR should be cancelled. +- 2) The R-GMLC sends the cancellation request to the H-GMLC, including the LDR reference number. The R GMLC may itself initiate the cancellation, e.g. whenever the R-GMLC infers from the absence of location reports for a long period that the service may have been terminated by the UE. +- 3) The H-GMLC may send a SEND\_ROUTING\_INFO\_FOR\_LCS message to the home HLR/HSS of the UE with the IMSI or MSISDN of this UE. This may be needed if the UE is no longer served by the original V PLMN or by the original MME. +- 4) The HLR/HSS returns the current serving MME for the UE and the V-GMLC address. +- 5) The H-GMLC forwards the LCS Cancel Service Request to the V-GMLC with the LDR reference number received from the R-GMLC, the H-GMLC address and the serving MME address (e.g. received from the HLR/HSS). The H-GMLC may itself initiate the cancellation procedure, when the UE's privacy profile stored in the H-GMLC or in the PPR was changed in a manner that no longer allows the LCS Client to receive event and location reports for the UE. + +NOTE: The H-GMLC shall know that the UE subscriber's privacy profile has been changed in the PPR when the LCS Privacy Profile Update has been sent from PPR to H-GMLC as described in clause 9.1.1.2. + +- 6) The V-GMLC sends the Provide Subscriber Location request to the serving MME, indicating a cancellation of a deferred location request for periodic and triggered location and including the LDR reference number specified by the LCS Client in the LCS Cancel Service Request and the H-GMLC address received from the H-GMLC. The V-GMLC shall transfer the location cancellation even when the V-GMLC was not involved in establishing the location request. +- 7) If the UE is currently not reachable (e.g. during an eDRX cycle or when in PSM), the MME waits until the UE becomes reachable. When the UE is reachable, if the UE is in ECM-IDLE state, the MME performs paging, authentication and ciphering. +- 8) The MME sends an LCS Periodic Location Cancellation request, including the LDR reference number and H-GMLC address, to the UE. +- 9) The UE stops the periodic and triggered event reporting and returns an LCS Periodic Location cancellation ack. to the MME. Return of an LCS Periodic Location cancellation ack. shall apply even when the UE has no knowledge of the location procedure being cancelled (e.g. if the UE was powered off during the procedure). +- 10) The MME sends the cancellation acknowledgement to the V-GMLC in a Provide Subscriber Location Ack, with the LDR reference number and the H-GMLC address. If the MME was unable to perform steps 7-8 (e.g. due to a change of MME or PLMN by the UE), the MME returns a Provide Subscriber Location error response with a suitable error cause. The V-GMLC then returns the error to the H-GMLC which may retry the cancellation with a different MME or different PLMN if applicable. +- 11) The V-GMLC sends an LCS Cancel Service Response to the H-GMLC with the LDR reference number and the H GMLC address. +- 12) The H-GMLC sends an LCS Cancel Service Response to the R-GMLC with the LDR reference number. +- 13) The R-GMLC sends an LCS Cancel Service Response to the LCS Client. + +#### 9.1.19.3 UE cancellation of a Deferred Location Request for Periodic and Triggered Location + +Figure 9.1.19.3-1 illustrates the procedure for cancelling the Deferred Location Request for the periodic and triggered location event when cancellation is requested by the UE. If a network entity (e.g. H-GMLC, V-GMLC, MME) cancels the Deferred Location Request, the procedure in clause 9.1.19.2 for LCS Client cancellation shall be used to cancel towards the UE and the procedure in this clause shall be used to cancel towards the LCS Client. + +![Sequence diagram showing UE cancellation of a Deferred MT-LR for Periodic and Triggered Location. The diagram involves seven lifelines: LCS Client, R-GMLC, H-GMLC, V-GMLC, MME, RAN, and UE. The sequence starts with a '1. UE Triggered Service Request or Connection Resume' from UE to MME. The UE then sends a '2. MO-LR Invoke (termination cause)' to the MME. The MME sends a '3. Subscriber Location Report' to the V-GMLC. The V-GMLC sends a '4. LCS Cancel Service Request' to the H-GMLC. The H-GMLC sends a '5. LCS Cancel Service Request' to the R-GMLC. The R-GMLC sends a '6. Location Cancellation' to the LCS Client. The LCS Client sends a '7. Location Cancellation ack' to the R-GMLC. The R-GMLC sends a '8. LCS Cancel Service Response' to the H-GMLC. The H-GMLC sends a '9. LCS Cancel Service Response' to the V-GMLC. The V-GMLC sends a '10. Subscriber Location Report ack.' to the MME. Finally, the MME sends a '11. LCS MO-LR Return Result' to the UE.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MME + participant V-GMLC + participant H-GMLC + participant R-GMLC + participant LCS Client + + Note right of UE: 1. UE Triggered Service Request or Connection Resume + UE->>MME: 2. MO-LR Invoke (termination cause) + MME->>V-GMLC: 3. Subscriber Location Report + V-GMLC->>H-GMLC: 4. LCS Cancel Service Request + H-GMLC->>R-GMLC: 5. LCS Cancel Service Request + R-GMLC->>LCS Client: 6. Location Cancellation + LCS Client->>R-GMLC: 7. Location Cancellation ack + R-GMLC->>H-GMLC: 8. LCS Cancel Service Response + H-GMLC->>V-GMLC: 9. LCS Cancel Service Response + V-GMLC->>MME: 10. Subscriber Location Report ack. + MME->>UE: 11. LCS MO-LR Return Result + +``` + +Sequence diagram showing UE cancellation of a Deferred MT-LR for Periodic and Triggered Location. The diagram involves seven lifelines: LCS Client, R-GMLC, H-GMLC, V-GMLC, MME, RAN, and UE. The sequence starts with a '1. UE Triggered Service Request or Connection Resume' from UE to MME. The UE then sends a '2. MO-LR Invoke (termination cause)' to the MME. The MME sends a '3. Subscriber Location Report' to the V-GMLC. The V-GMLC sends a '4. LCS Cancel Service Request' to the H-GMLC. The H-GMLC sends a '5. LCS Cancel Service Request' to the R-GMLC. The R-GMLC sends a '6. Location Cancellation' to the LCS Client. The LCS Client sends a '7. Location Cancellation ack' to the R-GMLC. The R-GMLC sends a '8. LCS Cancel Service Response' to the H-GMLC. The H-GMLC sends a '9. LCS Cancel Service Response' to the V-GMLC. The V-GMLC sends a '10. Subscriber Location Report ack.' to the MME. Finally, the MME sends a '11. LCS MO-LR Return Result' to the UE. + +**Figure 9.1.19.3-1: UE cancellation of a Deferred MT-LR for Periodic and Triggered Location** + +- 1) The UE waits until the UE is registered or can register via E-UTRAN access with a PLMN in the list of reporting PLMNs received at step 9 of the procedure in clause 9.1.19.1 or with the original serving PLMN for the procedure in clause 9.1.19.1 if no list of reporting PLMNs was provided or if the UE does not support the list of reporting PLMNs. + +If the UE is not using Control Plane CIoT EPS Optimisation and if the UE is in ECM-IDLE state, the UE performs a UE triggered service request or connection resume as defined in TS 23.401 [41] in order to obtain a signalling connection to a serving MME. + +If the UE is using Control Plane CIoT EPS Optimisation, procedures for Mobile Originated Data Transport in Control Plane CIoT EPS optimisation as defined in TS 23.401 [41] are performed by the UE to establish a signalling connection with the MME. + +- 2) The UE sends an LCS MO-LR Invoke to the serving MME for cancellation of a deferred MR-LR for periodic and triggered location. This message includes the H-GMLC address, a termination cause (e.g. subscriber terminates the procedure) and the LDR Reference Number. +- 3) The cancellation request shall be transferred from the MME to a V-GMLC and shall include the H-GMLC address, LDR reference number and IMSI of the UE. +- 4) to 6) The cancellation request shall be transferred to the H GMLC, R GMLC serving the LCS client and finally to the LCS client. +- 7) to 10) The response transferred back to the MME acknowledges the cancellation. +- 11) The MME returns the acknowledgment to the UE in a LCS MO-LR Return Result message. + +## 9.2 Mobile Originating Location Request + +### 9.2.1 Mobile Originating Location Request, Circuit Switched (CS-MO-LR) + +The following procedure shown in figure 9.7 allows an UE to request either its own location and optionally, velocity, location assistance data or broadcast assistance data message ciphering keys from the network. Location assistance data may be used subsequently by the UE to compute its own location throughout an extended interval using a mobile based position method. The ciphering key enables the UE to decipher other location assistance data broadcast periodically by the network. The MO-LR after location update request may be used to request ciphering keys or GNSS assistance data using the follow-on procedure described in TS 24.008 [24]. The procedure may also be used to enable an UE to request that its own location be sent to an external LCS client. + +![Sequence diagram for General Network Positioning for CS-MO-LR. The diagram shows interactions between LCS Client, GMLC, H-GMLC, V-GMLC, MSC SERVER, RAN, and UE. The process starts with a CM Service Request from UE to RAN, followed by a series of location requests and reports through the GMLC hierarchy, ending with connection release.](4842f073775fb1e84d101c02fd74e59e_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant MSC_SERVER as MSC SERVER + participant V-GMLC + participant H-GMLC + participant GMLC + participant LCS_Client as LCS Client + + Note right of UE: 1. CM Service Request + UE->>RAN: 1. CM Service Request + RAN->>MSC_SERVER: 2. CM Service Request + MSC_SERVER->>UE: 3. Authentication, Ciphering or CM Service Accept + MSC_SERVER->>RAN: 4. Location Services Invoke + RAN->>UE: 5. Location Request + Note right of RAN: 6. Messages for individual positioning methods or transfer of location assistance data + RAN->>MSC_SERVER: 7. Location Report. + MSC_SERVER->>V-GMLC: 8. MAP Subscriber Location Report + V-GMLC->>H-GMLC: 9. MO-LR Location Information + H-GMLC->>GMLC: 10. MO-LR Location Information + GMLC->>LCS_Client: 11. Location Information + LCS_Client->>GMLC: 12. Location Information ack + GMLC->>H-GMLC: 13. MO-LR Location Information Ack + H-GMLC->>V-GMLC: 14. MO-LR Location Information Ack + V-GMLC->>MSC_SERVER: 15. MAP Subscriber Location Report ack. + MSC_SERVER->>UE: 16. LCS MO-LR Return Result + MSC_SERVER->>RAN: 17. Release CM, MM, RRC connections + +``` + +Sequence diagram for General Network Positioning for CS-MO-LR. The diagram shows interactions between LCS Client, GMLC, H-GMLC, V-GMLC, MSC SERVER, RAN, and UE. The process starts with a CM Service Request from UE to RAN, followed by a series of location requests and reports through the GMLC hierarchy, ending with connection release. + +Figure 9.7: General Network Positioning for CS-MO-LR + +#### 9.2.1.1 Location Preparation Procedure + +- 1) If the UE is in idle mode, the UE requests a radio connection setup and sends a CM service request indicating a request for a call independent supplementary services to the VMSC/MSC server via RAN. +- 2) RAN shall convey the CM service request to the core network. If the UE is in dedicated mode, the UE sends a CM Service Request on the already established radio connection. + +- 3) The VMSC/MSC server instigates authentication and ciphering if the UE was in idle mode or returns a Direct Transfer CM Service Accept if the UE was in dedicated mode. The UE will inform the network about its LCS capabilities, as described in clause 6.3.4. +- 4) The UE sends a LCS CS-MO-LR Location Services invoke to the VMSC/MSC server. Different types of location services can be requested: location estimate of the UE, location estimate of the UE to be sent to an external LCS client, location assistance data or broadcast assistance data message ciphering keys. If the UE is requesting its own location estimate or that its own location be sent to an external LCS client, this message carries LCS requested QoS information (e.g. accuracy, response time, LCS QoS Class), the requested maximum age of location and the requested type of location (e.g. "current location", "current or last known location"). If the UE is requesting that its location be sent to an external LCS client, the message shall include the identity of the LCS client and may include the address of the GMLC through which the LCS client should be accessed. In addition, a Service Identity indicates which MO-LR service of the LCS Client is requested by the UE may be included. The message also may include a pseudonym indicator to indicate a pseudonym should be assigned by the network and transferred to the LCS Client as the UE's identity. If the UE is instead requesting location assistance data or ciphering keys, the message specifies the type of assistance data or deciphering keys and the positioning method for which the assistance data or ciphering applies. For an LCS CS-MO-LR Location Services invoke, the VMSC/MSC server shall assign a GMLC address, i.e. V-GMLC address, which is stored in the VMSC/MSC server. If a V-GMLC address is not available, the VMSC/MSC server may reject the location request. The VMSC/MSC server verifies in the UE's subscription profile that the UE has permission to request its own location, request that its location be sent to an external LCS client or request location assistance data or deciphering keys (whichever applies). If the UE is requesting positioning and has an established call, the VMSC/MSC server may reject the request for certain non-speech call types. +- 5) In case the requested type of location is "current or last known location" and the requested maximum age of location information is sent from UE, the VMSC/MSC server verifies whether it stores the previously obtained location estimate of the target UE. If the VMSC/MSC server stores the location estimate and the location estimate satisfies the requested maximum age of location, this step and steps 6 and 7 may be skipped. Otherwise the VMSC/MSC server sends a Location Request message to RAN associated with the Target UE. The message indicates whether a location estimate or location assistance data is requested and, in GSM, includes the UE's location capabilities. If the UE's location is requested, the message also includes the requested QoS. If location assistance data is requested, the message carries the requested types of location assistance data. + +#### 9.2.1.2 Positioning Measurement Establishment Procedure + +- 6) If the UE is requesting its own location, RAN determines the positioning method and instigates the particular message sequence for this method, as specified in UTRAN Stage 2, TS 25.305 [1] and GERAN Stage 2, TS 43.059 [16]. If the UE is instead requesting location assistance data, RAN transfers this data to the UE as described in subsequent clauses in TS 25.305 [1] and TS 43.059 [16] UE. + +#### 9.2.1.3 Location Calculation and Release Procedure + +- 7) When a location estimate best satisfying the requested QoS has been obtained or when the requested location assistance data has been transferred to the UE, RAN returns a Location Report to the VMSC/MSC server with an indication whether the obtained location estimate satisfies the requested accuracy or not. This message carries the location estimate or ciphering keys if this was obtained. If a location estimate or deciphering keys were not successfully obtained or if the requested location assistance data could not be transferred successfully to the UE, a failure cause is included in the Location Report. +- 8) If the location estimate was successfully obtained, the VMSC/MSC server shall send a MAP Subscriber Location Report to the V-GMLC assigned in the step 4, carrying the MSISDN/IMSI of the UE, the event causing the location estimate (CS-MO-LR) and the location estimate, its age, obtained accuracy indication and the LCS QoS Class requested by the target UE. In addition, the MAP Subscriber Location Report may include the pseudonym indicator, the identity of the LCS Client, the GMLC address and the Service Identity specified by the UE, if available. + +- 9) Upon receipt of the MAP Subscriber Location Report, the V-GMLC shall determine whether the UE requests transfer of its location estimate to an external LCS Client. If the identity of the LCS Client is not available, this step and steps 10 to 14 are skipped. Otherwise, the V-GMLC shall send the MO-LR Location Information to the H-GMLC (the V-GMLC may query the HLR/HSS of the UE to obtain the address of the H-GMLC), carrying the MSISDN/IMSI of the UE, the event causing the location estimate (CS-MO-LR), the location estimate and its age and the identity of the LCS Client. The pseudonym indicator and/or the GMLC address specified by the UE may also be included if available. +- 10) If the pseudonym indicator is included in the MO-LR Location Information, the H-GMLC assigns or asks the PMD to assign a pseudonym to the UE. If the identity of the LCS Client and the GMLC address access to the LCS Client are available, the H-GMLC shall send the MO-LR Location Information to the specified GMLC. If the identity of the LCS Client is available but the GMLC address access to the LCS Client is not available, the H-GMLC determines whether the specified LCS Client is accessible. If yes, the H-GMLC shall send the Location Information to the LCS Client, then the H-GMLC itself act as the specified GMLC, this step and step 13 are skipped. If not, according to the LCS Client identity, the H-GMLC shall determine a GMLC that can access the LCS Client, and send the MO-LR Location Information to the GMLC, carrying the MSISDN or the pseudonym of the UE, the identity of the LCS client, the event causing the location estimate (CS-MO-LR), location estimate and its age. +- 11) If the identified LCS Client is not accessible, this step and step 12 are skipped. Otherwise the GMLC transfers the location information to the LCS client, carrying the MSISDN/IMSI or the pseudonym of the UE, the event causing the location estimate (CS-MO-LR), the Service Identity, if available, and the location estimate and its age, in accordance with the LCS QoS Class requested by the target UE. If the UE requested LCS QoS class was Assured, GMLC sends the result to the LCS client only if the result has been indicated to fulfil the requested accuracy. If the UE requested LCS QoS class was Best Effort, GMLC sends whatever result it received to the LCS client with an appropriate indication if the requested accuracy was not met. +- 12) If the LCS Client does not support MO-LR (for temporary or permanent reasons) or can not handle the location estimate of the UE, e.g. the LCS Client does not know the Service Identity, or the UE does not register to the LCS Client, the LCS Client have no corresponding data of the UE, the LCS Client shall return the Location Information ack message to the GMLC or the H-GMLC (in case the LCS Client received Location Information is sent from H-GMLC) with a suitable error cause. Otherwise, the LCS Client handles the location estimate according to the Service Identity, sends the GMLC or the H-GMLC the Location Information ack message signalling that the location estimate of the UE has been handled successfully. +- 13) If the identified LCS Client is not accessible, the GMLC sends MO-LR Location Information Acknowledgement to the H-GMLC with an appropriate error cause. Otherwise, the GMLC shall send MO-LR Location Information Acknowledgement to the H-GMLC. The message shall specify whether the location estimate of the UE has been handled successfully by the identified LCS Client, and if not, the corresponding error cause obtained in step 12. The GMLC may record charging information both for the LCS Client and inter-operator revenue charges. +- 14) In case the H-GMLC receives the MO-LR Location Information Acknowledgement from the GMLC, it shall forward the MO-LR Location Information Acknowledgement from the GMLC to the V-GMLC, and record charging information both for the UE and inter-working revenue charges. + +In case the H-GMLC receives the Location Information Acknowledgement from the LCS Client, it shall send MO-LR Location Information Acknowledgement to the V-GMLC. The message shall specify whether the location estimate of the UE has been handled successfully by the identified LCS Client, and if not, the corresponding error cause obtained in step 12. The H-GMLC shall record charging information both for the UE and inter-working revenue charges. + +- 15) In case the V-GMLC receives the MO-LR Location Information Acknowledgement from the H-GMLC, the V-GMLC shall record charging information both for the UE and inter-working revenue charges and send the MAP Subscriber Location Report Acknowledgement to the VMSC/MSC server, carrying the information specifies whether the location estimate of the UE has been handled successfully by the identified LCS Client, and if not success, the corresponding error cause obtained in step 14. + +In case the V-GMLC receives the MAP Subscriber Location Report from the VMSC/MSC server and it is not required to send to any LCS Client, the V-GMLC shall record charging information for the UE and response the MAP Subscriber Location Report Acknowledgement to the VMSC/MSC server. + +- 16) The VMSC/MSC server returns a CS-MO-LR Return Result to the UE carrying any location estimate requested by the UE including the indication received from RAN whether the obtained location estimate satisfies the requested accuracy or not, ciphering keys or an indicator whether a location estimate was successfully transferred to the identified LCS client. If the location estimate was successfully transferred to the identified LCS Client, the CS-MO-LR Return Result message shall specify whether the location estimate of the UE has been handled successfully by the identified LCS Client, and if not, the corresponding error cause obtained in step 15. +- 17) The VMSC/MSC server may release the CM, MM and radio connections to the UE, if the UE was previously idle, and the VMSC/MSC server may record charging information. + +### 9.2.2 Mobile Originating Location Request, Packet Switched (PS-MO-LR) + +The following procedure shown in figure 9.8 allows an UE to request either its own location and optionally, velocity; location assistance data or broadcast assistance data message ciphering keys from the network. Location assistance data may be used subsequently by the UE to compute its own location throughout an extended interval using a mobile based position method. A ciphering key enables the UE to decipher other location assistance data broadcast periodically by the network. The PS-MO-LR may be used to request ciphering keys or GNSS assistance data. The procedure may also be used to enable an UE to request that its own location be sent to an external LCS client. + +![Sequence diagram for General Network Positioning for packet switched MO-LR. Lifelines: LCS Client, GMLC, H-GMLC, V-GMLC, HLR/HSS, SGSN, RAN, UE. The sequence shows 14 steps: 1. Service Request (UE to SGSN), (Part of 1: Possible security procedures) (SGSN to UE), 2. Services Invoke (SGSN to HLR/HSS), 3. Location Request (SGSN to RAN), 4. Messages for individual positioning methods or transfer of location assistance data (RAN to UE), 5. Location Report (RAN to SGSN), 6. Subscriber Location Report (SGSN to V-GMLC), 7. MO-LR Location Information (V-GMLC to H-GMLC), 8. MO-LR Location Information (H-GMLC to GMLC), 9. Location Information (GMLC to LCS Client), 10. Location Information ack (LCS Client to GMLC), 11. MO-LR Location Information Ack (GMLC to H-GMLC), 12. MO-LR Location Information Ack (H-GMLC to V-GMLC), 13. Subscriber Location Report ack (V-GMLC to SGSN), 14. Service Response (SGSN to UE).](cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant SGSN + participant HLR/HSS + participant V-GMLC + participant H-GMLC + participant GMLC + participant LCS_Client as LCS Client + + Note right of UE: (Part of 1: Possible security procedures) + UE->>SGSN: 1. Service Request + SGSN-->>UE: + SGSN->>HLR/HSS: 2. Services Invoke + SGSN->>RAN: 3. Location Request + Note right of RAN: 4. Messages for individual positioning methods or transfer of location assistance data + RAN-->>UE: + RAN->>SGSN: 5. Location Report + SGSN->>V-GMLC: 6. Subscriber Location Report + V-GMLC->>H-GMLC: 7. MO-LR Location Information + H-GMLC->>GMLC: 8. MO-LR Location Information + GMLC->>LCS_Client: 9. Location Information + LCS_Client->>GMLC: 10. Location Information ack + GMLC->>H-GMLC: 11. MO-LR Location Information Ack + H-GMLC->>V-GMLC: 12. MO-LR Location Information Ack + V-GMLC->>SGSN: 13. Subscriber Location Report ack + SGSN->>UE: 14. Service Response + +``` + +Sequence diagram for General Network Positioning for packet switched MO-LR. Lifelines: LCS Client, GMLC, H-GMLC, V-GMLC, HLR/HSS, SGSN, RAN, UE. The sequence shows 14 steps: 1. Service Request (UE to SGSN), (Part of 1: Possible security procedures) (SGSN to UE), 2. Services Invoke (SGSN to HLR/HSS), 3. Location Request (SGSN to RAN), 4. Messages for individual positioning methods or transfer of location assistance data (RAN to UE), 5. Location Report (RAN to SGSN), 6. Subscriber Location Report (SGSN to V-GMLC), 7. MO-LR Location Information (V-GMLC to H-GMLC), 8. MO-LR Location Information (H-GMLC to GMLC), 9. Location Information (GMLC to LCS Client), 10. Location Information ack (LCS Client to GMLC), 11. MO-LR Location Information Ack (GMLC to H-GMLC), 12. MO-LR Location Information Ack (H-GMLC to V-GMLC), 13. Subscriber Location Report ack (V-GMLC to SGSN), 14. Service Response (SGSN to UE). + +Figure 9.8: General Network Positioning for packet switched MO-LR + +#### 9.2.2.1 Location Preparation Procedure + +- 1) In UMTS, if the UE is in idle mode, the UE requests a PS signalling connection and sends a Service request indicating signalling to the SGSN via the RAN. If the UE already has PS signalling connection, the UE does not + +need to send Service request. Security functions may be executed. These procedures are described in TS 23.060 [15]. In GSM this signalling step is not needed. + +- 2) The UE sends a LCS PS-MO-LR Location Services invoke message to the SGSN. Different types of location services can be requested: location estimate of the UE, location estimate of the UE to be sent to an external LCS client, location assistance data or broadcast assistance data message ciphering keys. If the UE is requesting its own location or that its own location be sent to an external LCS client, this message carries LCS requested QoS information (e.g. accuracy, response time, LCS QoS Class), the requested maximum age of location and the requested type of location (e.g. "current location", "current or last known location"). If the UE is requesting that its location be sent to an external LCS client, the message shall include the identity of the LCS client and may include the address of the GMLC through which the LCS client should be accessed. In addition, a Service Identity indicates which MO-LR service of the LCS Client is requested by the UE may be included. The message also may include a pseudonym indicator to indicate a pseudonym should be assigned by the network and transferred to the LCS Client as the UE's identity. If the UE is instead requesting location assistance data or ciphering keys, the message specifies the type of assistance data or deciphering keys and the positioning method for which the assistance data or ciphering applies. For an LCS PS-MO-LR Location Services invoke, the SGSN shall assign a GMLC address, i.e. V-GMLC address, which is stored in the SGSN. If a V-GMLC address is not available, the SGSN may reject the location request. The SGSN verifies the subscription profile of the UE and decides if the requested service is allowed or not. +- 3) In case the requested type of location is "current or last known location" and the requested maximum age of location information is sent from UE, the SGSN verifies whether it stores the previously obtained location estimate of the target UE. If the SGSN stores the location estimate and the location estimate satisfies the requested maximum age of location, this step and steps 4 and 5 may be skipped. Otherwise the SGSN sends a Location Request message to the RAN associated with the Target UE's location. The message indicates whether a location estimate or location assistance data is requested. If the UE's location is requested, the message also includes the requested QoS. If location assistance data is requested, the message carries the requested types of location assistance data. The message carries also location parameters received in the Service Invoke message. + +#### 9.2.2.2 Positioning Measurement Establishment Procedure + +- 4) If the UE is requesting its own location, the actions described in UTRAN Stage 2, TS 25.305 [1] or GERAN stage 2 TS 43.059 [16] are performed. If the UE is instead requesting location assistance data, the RAN transfers this data to the UE as described in subsequent clauses. The RAN determines the exact location assistance data to transfer according to the type of data specified by the UE, the UE location capabilities and the current cell. + +#### 9.2.2.3 Location Calculation and Release Procedure + +- 5) When a location estimate best satisfying the requested QoS has been obtained or when the requested location assistance data has been transferred to the UE, the RAN returns a Location Report to the SGSN with an indication whether the obtained location estimate satisfies the requested accuracy or not. This message carries the location estimate or ciphering keys if this was obtained. If a location estimate or deciphering keys were not successfully obtained or if the requested location assistance data could not be transferred successfully to the UE, a failure cause is included in the Location Report. +- 6) If the location estimate was successfully obtained, the SGSN shall send a Subscriber Location Report to the V-GMLC assigned in the step 2, carrying the MSISDN/IMSI of the UE, the event causing the location estimate (PS-MO-LR) and the location estimate, its age, obtained accuracy indication and the LCS QoS Class requested by the target UE. In addition, the Subscriber Location Report may include the pseudonym indicator, the identity of the LCS Client, the GMLC address and the Service Identity specified by the UE, if available. +- 7) Upon receipt of the Subscriber Location Report, the V-GMLC shall determine whether the UE requests transfer of its location estimate to an external LCS Client. If the identity of the LCS Client is not available, this step and steps 8 to 12 are skipped. Otherwise, the V-GMLC shall send the MO-LR Location Information to the H-GMLC (the V-GMLC may query the HLR/HSS of the UE to obtain the address of the H-GMLC), carrying the MSISDN/IMSI of the UE, the event causing the location estimate (PS-MO-LR), the location estimate and its age, and the identity of the LCS Client. The pseudonym indicator and/or the GMLC address specified by the UE may also be included if available. +- 8) If the pseudonym indicator is included in the MO-LR Location Information, the H-GMLC assigns or asks the PMD to assign a pseudonym to the UE. If the identity of the LCS Client and the GMLC address access to the LCS Client are available, the H-GMLC shall send the MO-LR Location Information to the specified GMLC. If + +the identity of the LCS Client is available but the GMLC address access to the LCS Client is not available, the H-GMLC determines whether the specified LCS Client is accessible. If yes, the H-GMLC shall send the Location Information to the LCS Client, then the H-GMLC itself act as the specified GMLC, this step and step 11 are skipped. If not, according to the LCS Client identity, the H-GMLC shall determine a GMLC that can access the LCS Client, and send the MO-LR Location Information to the GMLC, carrying the MSISDN or the pseudonym of the UE, the identity of the LCS client, the event causing the location estimate (PS-MO-LR), location estimate and its age. + +- 9) If the identified LCS Client is not accessible, this step and step 10 are skipped. Otherwise the GMLC transfers the location information to the LCS client, carrying the MSISDN/IMSI or the pseudonym of the UE, the event causing the location estimate (PS-MO-LR), the Service Identity, if available, and the location estimate and its age, in accordance with the LCS QoS Class requested by the target UE. If the UE requested LCS QoS class was Assured, GMLC sends the result to the LCS client only if the result has been indicated to fulfil the requested accuracy. If the UE requested LCS QoS class was Best Effort, GMLC sends whatever result it received to the LCS client with an appropriate indication if the requested accuracy was not met. +- 10) If the LCS Client does not support MO-LR (for temporary or permanent reasons) or can not handle the location estimate of the UE, e.g. the LCS Client does not know the Service Identity, or the UE does not register to the LCS Client, the LCS Client have no corresponding data of the UE, the LCS Client shall return the Location Information ack message to the GMLC or the H-GMLC (in case the LCS Client received Location Information is sent from H-GMLC) with a suitable error cause. Otherwise, the LCS Client handles the location estimate according to the Service Identity, sends the GMLC or the H-GMLC the Location Information ack message signalling that the location estimate of the UE has been handled successfully. +- 11) If the identified LCS Client is not accessible, the GMLC sends MO-LR Location Information Acknowledgement to the H-GMLC with an appropriate error cause. Otherwise, the GMLC shall send MO-LR Location Information Acknowledgement to the H-GMLC. The message shall specify whether the location estimate of the UE has been handled successfully by the identified LCS Client, and if not, the corresponding error cause obtained in step 10. The GMLC may record charging information both for the LCS Client and inter-operator revenue charges. +- 12) In case the H-GMLC receives the MO-LR Location Information Acknowledgement from the GMLC, it shall forward the MO-LR Location Information Acknowledgement from the GMLC to the V-GMLC, and record charging information both for the UE and inter-working revenue charges. + +In case the H-GMLC receives the Location Information Acknowledgement from the LCS Client, it shall send MO-LR Location Information Acknowledgement to the V-GMLC. The message shall specify whether the location estimate of the UE has been handled successfully by the identified LCS Client, and if not, the corresponding error cause obtained in step 10. The H-GMLC shall record charging information both for the UE and inter-working revenue charges. + +- 13) In case the V-GMLC receives the MO-LR Location Information Acknowledgement from the H-GMLC, the V-GMLC shall record charging information both for the UE and inter-working revenue charges and send the Subscriber Location Report Acknowledgement to the SGSN, carrying the information specifies whether the location estimate of the UE has been handled successfully by the identified LCS Client, and if not success, the corresponding error cause obtained in step 12. + +In case the V-GMLC receives the Subscriber Location Report from the SGSN and it is not required to send to any LCS Client, the V-GMLC shall record charging information for the UE and response the Subscriber Location Report Acknowledgement to the SGSN. + +- 14) The SGSN returns a Service Response message to the UE carrying any location estimate requested by the UE including the indication received from RAN whether the obtained location estimate satisfies the requested accuracy or not, ciphering keys or an indicator whether a location estimate was successfully transferred to the identified LCS client. If the location estimate was successfully transferred to the identified LCS Client, the Service Response message shall specify whether the location estimate of the UE has been handled successfully by the identified LCS Client, and if not, the corresponding error cause obtained in step 13. The SGSN may record charging information. + +### 9.2.3 MO-LR Request for Periodic Location Transfer to a Third Party + +The following procedure shown in figure 9.8a allows a UE to instigate a periodic transfer of location to an external LCS client. The procedure would be executed once after which it would be followed by the procedure described in clause 9.1.12.2. + +![Sequence diagram for Deferred MO-LR Initiation for Periodic Location in CS and PS domain. The diagram shows interactions between LCS Client, R-GMLC, H-GMLC, V-GMLC, MSC/SGSN, RAN, and UE. The process involves service requests, authentication, MO-LR invokes, and location information reports.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` + +sequenceDiagram + participant UE + participant RAN + participant MSC_SGSN as MSC/SGSN + participant V_GMLC as V-GMLC + participant H_GMLC as H-GMLC + participant R_GMLC as R-GMLC + participant LCS_Client as LCS Client + + Note right of UE: 1. CS: CM Service Request +PS: Service Request + UE->>RAN: 1. CS: CM Service Request +PS: Service Request + RAN->>MSC_SGSN: 1. CS: CM Service Request +PS: Service Request + Note right of MSC_SGSN: 2. CS: Authentication, Ciphering or +CM Service Accept +PS: Part of 1: Possible Security Procedures + MSC_SGSN->>RAN: 2. CS: Authentication, Ciphering or +CM Service Accept +PS: Part of 1: Possible Security Procedures + RAN->>UE: 2. CS: Authentication, Ciphering or +CM Service Accept +PS: Part of 1: Possible Security Procedures + Note right of UE: 3. MO-LR Invoke (+ periodic location information + +LCS Client Address) + UE->>MSC_SGSN: 3. MO-LR Invoke (+ periodic location information + +LCS Client Address) + MSC_SGSN->>V_GMLC: 4. MAP Subscriber Location Report + V_GMLC->>H_GMLC: 5. MO-LR Location Information + H_GMLC->>R_GMLC: 6. MO-LR Location Information + R_GMLC->>LCS_Client: 7. Location Information + LCS_Client->>R_GMLC: 8. Location Information ack + R_GMLC->>H_GMLC: 9. MO-LR Location Information Ack + H_GMLC->>V_GMLC: 10. MO-LR Location Information Ack + V_GMLC->>MSC_SGSN: 11. MAP Subscriber Location Report ack. + MSC_SGSN->>UE: 12. LCS MO-LR Return Result + Note right of MSC_SGSN: 13a. Release CM, MM/GMM, RR/RRC connections +or + MSC_SGSN->>RAN: 13a. Release CM, MM/GMM, RR/RRC connections +or + RAN->>UE: 13a. Release CM, MM/GMM, RR/RRC connections +or + Note right of MSC_SGSN: 13b. MO-LR Invoke (+ location estimate or request) + MSC_SGSN->>RAN: 13b. MO-LR Invoke (+ location estimate or request) + RAN->>UE: 13b. MO-LR Invoke (+ location estimate or request) + +``` + +Sequence diagram for Deferred MO-LR Initiation for Periodic Location in CS and PS domain. The diagram shows interactions between LCS Client, R-GMLC, H-GMLC, V-GMLC, MSC/SGSN, RAN, and UE. The process involves service requests, authentication, MO-LR invokes, and location information reports. + +**Figure 9.8a: Deferred MO-LR Initiation for Periodic Location in CS and PS domain** + +- 1) to 2) If the UE is in idle mode, the UE requests a radio connection setup and sends a CM Service Request indicating a request for call independent supplementary service to the VMSC/MSC server via RAN (CS domain). If the UE is in dedicated mode, the UE sends a CM Service Request on the already established radio connection. The VMSC/MSC server instigates authentication and ciphering if the UE was in idle mode or returns a CM Service Accept if the UE was in dedicated mode. + +For PS domain, in UMTS, if the UE is in idle mode, the UE requests a PS signalling connection and sends a Service Request indicating signalling to the SGSN via RAN. If the UE already has PS signalling connection, the UE does not need to send the Service Request. Security functions may be executed. These procedures are described in TS 23.060 [15]. In GSM this signalling step is not needed. + +- 3) The UE sends an LCS MO-LR Invoke for periodic transfer of location to a third party LCS client. The UE shall include the periodic location related parameters (reporting interval and total number of reports). The UE shall also include the identity of the LCS client and may include the address of the GMLC through which the LCS client can be accessed. The UE may include a request for use of MO-LR Short Circuit (e.g. if the UE supports UE based positioning). The absence of an H-GMLC assigned LDR reference number in this case indicates that the request has not yet been authorized. +- 4) to 7) The request to initiate periodic location shall be transferred in succession from the MSC/SGSN to the V-GMLC, H-GMLC, R-GMLC serving the LCS client and finally may be transferred to the LCS client. The periodic location parameters (reporting interval and number of reports) are included as well as any request for use of MO-LR Short Circuit. Any entity (MSC/SGSN, V-GMLC, H-GMLC, R-GMLC and, if notified, LCS Client) is enabled to accept or refuse the request. In addition, if the request was accepted, any entity is free to reject use of MO-LR Short Circuit. If the request is accepted, a LDR reference number is assigned by the H-GMLC. + +- 8) to 11) The response transferred back to the MSC/SGSN shall indicate acceptance or rejection and whether MO-LR short circuit (if requested) has been accepted. The response also includes the LDR reference number assigned by the H-GMLC and the H-GMLC address. The H-GMLC may include in the response a list of PLMNs and possibly associated radio access technologies, either prioritized or non-prioritized, in which subsequent location estimates must be obtained and an indication for each PLMN (and possibly each associated radio access technology) of whether periodic location in the RAN is supported. If no list is included, subsequent locations are restricted to the current serving PLMN only +- 12) The MSC/SGSN returns the result of the request to the UE in a LCS MO-LR Return Result message including the LDR reference number, the H-GMLC address any reporting PLMN list and an indication whether MO-LR Short Circuit is allowed (if requested by the UE in step 3. +- 13a) The UE may instigate release of the CM, MM/GMM and radio connections – e.g. if the request was rejected or if the MSC/SGSN provided a list of PLMNs that did not include the serving PLMN (or if the serving PLMN was included in a prioritized list with a lower priority). Assuming the request was accepted, the UE may then initiate reporting of the first location estimate using the procedure described in clause 9.1.12.2 and beginning at step 1. +- 13b) If the request was accepted and the serving PLMN can be used for subsequent location, the UE may initiate reporting of the first location estimate by sending an MO-LR request indicating transfer of location to the LCS Client using the procedure described in clause 9.1.12.2 and beginning at step 3. + +NOTE: If the UE receives a response in step 12 indicating that the MO-LR request for periodic location transfer to a third party cannot be supported (for temporary or permanent reasons), the UE may periodically invoke the MO-LR procedure for location transfer to a third party defined in clause 9.2.1 for the CS domain (CS-MO-LR) and in clause 9.2.2 for the PS domain (PS-MO-LR). + +### 9.2.4 MO-LR Request for Periodic Self Location + +The following procedure shown in figure 9.8b allows an UE to request its own location periodically if the RAN serving the target UE supports periodic location. This procedure is useful if a UE only supports UE-assisted positioning or has no positioning capability. + +![Sequence diagram for MO-LR for Periodic Self Location with Periodic Positioning in the RAN. The diagram shows interactions between LCS Client, R-GMLC, H-GMLC, V-GMLC, MSC/SGSN, RAN, and UE. The sequence starts with the UE sending a CS: CM Service Request or PS: Service Request to the MSC/SGSN. The MSC/SGSN responds with CS: Authentication, Ciphering or CM Service Accept or PS: Part of 1: Possible Security Procedures. The UE then sends an LCS MO-LR Invoke to the MSC/SGSN. The MSC/SGSN sends a Location Request to the RAN. The RAN performs individual positioning and returns a Location Report to the MSC/SGSN. The MSC/SGSN sends an LCS Location Update to the UE. The UE responds with an LCS Location Update Ack. The RAN performs another individual positioning and returns a Location Report to the MSC/SGSN. The MSC/SGSN sends another LCS Location Update to the UE. The UE responds with an LCS Location Update Ack. The MSC/SGSN then sends an LCS MO-LR Return Result to the UE. Finally, the MSC/SGSN releases CM, MM/GMM, RR/RRC connections.](5801c19431e76330430e92a598cc7a16_img.jpg) + +``` + +sequenceDiagram + participant LCS Client + participant R-GMLC + participant H-GMLC + participant V-GMLC + participant MSC/SGSN + participant RAN + participant UE + + Note right of MSC/SGSN: 1. CS: CM Service Request +PS: Service Request + UE->>MSC/SGSN: 1. CS: CM Service Request +PS: Service Request + Note right of MSC/SGSN: 2. CS: Authentication, Ciphering or CM Service Accept +PS: Part of 1: Possible Security Procedures + MSC/SGSN->>UE: 2. CS: Authentication, Ciphering or CM Service Accept +PS: Part of 1: Possible Security Procedures + Note right of UE: 3. LCS MO-LR Invoke + UE->>MSC/SGSN: 3. LCS MO-LR Invoke + Note right of MSC/SGSN: 4. Location Request + MSC/SGSN->>RAN: 4. Location Request + Note right of RAN: 5. Messages for individual positioning + RAN->>MSC/SGSN: 6. Location Report + Note right of MSC/SGSN: 7. LCS Location Update + MSC/SGSN->>UE: 7. LCS Location Update + Note right of UE: 8. LCS Location Update Ack + UE->>MSC/SGSN: 8. LCS Location Update Ack + Note right of RAN: 9. Messages for individual positioning + RAN->>MSC/SGSN: 10. Location Report + Note right of MSC/SGSN: 11. LCS Location Update + MSC/SGSN->>UE: 11. LCS Location Update + Note right of UE: 12. LCS Location Update Ack + UE->>MSC/SGSN: 12. LCS Location Update Ack + Note right of MSC/SGSN: 13. LCS MO-LR Return Result + MSC/SGSN->>UE: 13. LCS MO-LR Return Result + Note right of MSC/SGSN: 14. Release CM, MM/GMM, RR/RRC connections + MSC/SGSN->>UE: 14. Release CM, MM/GMM, RR/RRC connections + +``` + +Sequence diagram for MO-LR for Periodic Self Location with Periodic Positioning in the RAN. The diagram shows interactions between LCS Client, R-GMLC, H-GMLC, V-GMLC, MSC/SGSN, RAN, and UE. The sequence starts with the UE sending a CS: CM Service Request or PS: Service Request to the MSC/SGSN. The MSC/SGSN responds with CS: Authentication, Ciphering or CM Service Accept or PS: Part of 1: Possible Security Procedures. The UE then sends an LCS MO-LR Invoke to the MSC/SGSN. The MSC/SGSN sends a Location Request to the RAN. The RAN performs individual positioning and returns a Location Report to the MSC/SGSN. The MSC/SGSN sends an LCS Location Update to the UE. The UE responds with an LCS Location Update Ack. The RAN performs another individual positioning and returns a Location Report to the MSC/SGSN. The MSC/SGSN sends another LCS Location Update to the UE. The UE responds with an LCS Location Update Ack. The MSC/SGSN then sends an LCS MO-LR Return Result to the UE. Finally, the MSC/SGSN releases CM, MM/GMM, RR/RRC connections. + +**Figure 9.8b: MO-LR for Periodic Self Location with Periodic Positioning in the RAN** + +- 1) to 2) If the UE is in idle mode, the UE requests a radio connection setup and sends a CM Service Request indicating a request for call independent supplementary service to the VMSC/MSC server via RAN (CS domain). If the UE is in dedicated mode, the UE sends a CM Service Request on the already established radio connection. The VMSC/MSC server instigates authentication and ciphering if the UE was in idle mode or returns a CM Service Accept if the UE was in dedicated mode. + +For PS domain, in UMTS, if the UE is in idle mode, the UE requests a PS signalling connection and sends a Service Request indicating signalling to the SGSN via RAN. If the UE already has PS signalling connection, the UE does not need to send the Service Request. Security functions may be executed. These procedures are described in TS 23.060 [15]. In GSM this signalling step is not needed. + +- 3) The UE sends an MO-LR invoke requesting periodic self location. The request includes the required QoS, the periodic location interval and the total number of reports. +- 4) The MSC/SGSN sends a location request to the RAN containing the QoS and periodic location information received in step 3. +- 5) RAN determines the positioning method and instigates the particular message sequence for this method, as specified in UTRAN Stage 2, TS 25.305 [1] and GERAN Stage 2, TS 43.059 [16]. +- 6) When a location estimate best satisfying the requested QoS has been obtained, RAN returns it to the MSC/SGSN. + +- 7) The MSC/SGSN sends an LCS Location Update invoke to the UE containing the first location estimate. +- 8) The UE acknowledges receipt of the first location estimate. If the UE wished to cancel the periodic location procedure at that point, an additional parameter (e.g. flag or cause value) is included in this message. +- 9-12) As steps 5-8 for the second location estimate and thereafter repeated at the periodic location interval until the total number of reports is attained. +- 13) After the final location estimate has been transferred in step 12, the MSC/SGSN returns an MO-LR return result to the UE to indicate completion of the periodic location request in step 3. As an implementation option, the final location estimate may be returned in the MO-LR return result in step 13 rather than in an LCS Location Update in step 11. +- 14) The MSC/SGSN instigates clearing of the CM, MM/GMM and radio connections. + +NOTE: If the UE receives a response in step 13 indicating that the MO-LR request for periodic self location cannot be supported (for temporary or permanent reasons), the UE may periodically invoke the MO-LR procedure for self location defined in clause 9.2.1 for the CS domain (CS-MO-LR) and in clause 9.2.2 for the PS domain (PS-MO-LR). + +### 9.2.5 WLAN UE Originated Procedure in I-WLAN + +This procedure is applicable to a UE connected to I-WLAN defined in TS 23.234 [52] and it is no longer maintained. + +Figure 9.8c describes the MO-LR procedure for LCS for I-WLAN. + +![Sequence diagram for WLAN UE Originated Procedure in I-WLAN. The diagram shows interactions between WLAN UE, WLAN AN, AAA, HSS/HLR, WAG, PDG, GMLC/SLP, and External LCS Client. The process is divided into three main phases: 1. Connection Setup, Authentication, Tunnel Establishment; 2. Mobile Originated Positioning Procedures; 3. LCS Response.](10bf8762a8e8d9385609cc6fb11061fe_img.jpg) + +``` + +sequenceDiagram + participant WLAN UE + participant WLAN AN + participant AAA + participant HSS/HLR + participant WAG + participant PDG + participant GMLC/SLP + participant External LCS Client + + Note over WLAN UE, PDG: 1. Connection Setup, Authentication, Tunnel Establishment + Note over WLAN UE, GMLC/SLP: 2. Mobile Originated Positioning Procedures + GMLC/SLP->>External LCS Client: 3. LCS Response + +``` + +Sequence diagram for WLAN UE Originated Procedure in I-WLAN. The diagram shows interactions between WLAN UE, WLAN AN, AAA, HSS/HLR, WAG, PDG, GMLC/SLP, and External LCS Client. The process is divided into three main phases: 1. Connection Setup, Authentication, Tunnel Establishment; 2. Mobile Originated Positioning Procedures; 3. LCS Response. + +**Figure 9.8c: WLAN UE Originated Procedure in I-WLAN** + +1. The WLAN UE selects a WLAN AN and establishes the WLAN connection and is authenticated in I-WLAN. The tunnel is established with between WLAN UE and one of PDGs in PLMN. +2. WLAN UE initiates positioning procedure by establishing a so called user plane connection with the GMLC/SLP and shall use the OMA SUPL mechanism specified by OMA (OMA AD SUPL [38], OMA TS ULP [39]) to transport location related assistance data and location information between the UE and GMLC/SLP. The UE may receive assistance data and determine its own location and send its location information to the GMLC/SLP or the UE sends measurement results to the GMLC/SLP. In case GMLC/SLP determines the location of the UE, the GMLC/SLP shall send the location information to the WLAN UE. The UE may also send the identifier of the access node (e.g., MAC address of the AP) to the GMLC and GMLC, possibly using an external database, maps this location identifier to the corresponding geographical information, e.g. coordinates or street address and returns the result to the UE. +3. The location information obtained is transferred to external LCS client if requested by WLAN UE. The estimated position of a WLAN UE can be stored in the GMLC after WLAN UE originated positioning procedure for future uses subject to the privacy settings of the WLAN UE. If there is an LCS request from an external LCS Client, the stored location information can be delivered to the external LCS client if the stored location information satisfies LCS QoS requested. + +### 9.2.6 Mobile Originating Location Request, EPC (EPC-MO-LR) + +The following procedure shown in figure 9.8d allows an UE to request either, its own location and optionally, velocity or location assistance data. Location assistance data may be used subsequently by the UE to compute its own location throughout an extended interval using a mobile based position method. The EPC-MO-LR may be used to request GNSS assistance data. The procedure may also be used to enable an UE to request that its own location be sent to an external LCS client. + +![Sequence diagram for General Network Positioning for packet switched MO-LR. The diagram shows interactions between LCS Client, GMLC, H-GMLC, V-GMLC, HLR/HSS, E-SMLC, MME, RAN, and UE.](76d19e4271bf243b20d55a98efd51483_img.jpg) + +``` + +sequenceDiagram + participant LCS Client + participant GMLC + participant H-GMLC + participant V-GMLC + participant HLR/HSS + participant E-SMLC + participant MME + participant RAN + participant UE + + Note over MME, UE: 1. UE Triggered Service Request + UE->>MME: 2. NAS MO-LR Request + MME->>E-SMLC: 3. Location Request + Note over E-SMLC, UE: 4. Messages for individual positioning methods or +transfer of location assistance data + E-SMLC->>MME: 5. Location Response + MME->>V-GMLC: 6. Subscriber Location Report + V-GMLC->>H-GMLC: 7. MO-LR Location Information + H-GMLC->>GMLC: 8. MO-LR Location Information + GMLC->>LCS Client: 9. Location Information + LCS Client->>GMLC: 10. Location Information Ack + GMLC->>H-GMLC: 11. MO-LR Location Information Ack + H-GMLC->>V-GMLC: 12. MO-LR Location Information Ack + V-GMLC->>MME: 13. Subscriber Location Report ack. + MME->>UE: 14. NAS MO-LR Response + +``` + +Sequence diagram for General Network Positioning for packet switched MO-LR. The diagram shows interactions between LCS Client, GMLC, H-GMLC, V-GMLC, HLR/HSS, E-SMLC, MME, RAN, and UE. + +**Figure 9.8d: General Network Positioning for packet switched MO-LR** + +#### 9.2.6.1 Location Preparation Procedure + +- 1) If the UE is not using Control Plane CIoT EPS Optimisation and if the UE is in ECM-IDLE state, the UE performs a UE triggered service request as defined in TS 23.401 [41] in order to establish a signalling connection with the MME and assign a specific eNodeB. + + +If the UE is using Control Plane CIoT EPS Optimisation, procedures for Mobile Originated Data Transport in Control Plane CIoT EPS optimisation as defined in TS 23.401 [41] are performed by the UE to establish a signalling connection with the MME. +- 2) The UE sends a NAS PDU containing an MO-LR Request inside an RRC UL Information Transfer message to the eNodeB. The MO-LR Request may optionally include an LPP positioning message. The eNodeB forwards the MO-LR Request (including any embedded LPP message) to the MME inside an S1AP Uplink NAS Transport message. Different types of location services can be requested: location estimate of the UE, location estimate of the UE to be sent to an external LCS client or location assistance data. If the UE is requesting its own location or that its own location be sent to an external LCS client, this message carries LCS requested QoS information (e.g. accuracy, response time, LCS QoS Class), the requested maximum age of location and the + +requested type of location (e.g. "current location", "current or last known location"). If the UE is requesting that its location be sent to an external LCS client, the message shall include the identity of the LCS client and may include the address of the GMLC through which the LCS client should be accessed. In addition, a Service Identity indicates which MO-LR service of the LCS Client is requested by the UE may be included. The message also may include a pseudonym indicator to indicate a pseudonym should be assigned by the network and transferred to the LCS Client as the UE's identity. If the UE is instead requesting location assistance data, the embedded LPP message specifies the type of assistance data and the positioning method for which the assistance data applies. For an LCS EPC-MO-LR requesting location transfer to an external LCS Client, the MME shall assign a GMLC address, i.e. V-GMLC address, which is stored in the MME. If a V-GMLC address is not available, the MME may reject the location request. The MME verifies the subscription profile of the UE and decides if the requested service is allowed or not. + +- 3) The MME selects a E-SMLC as described in clause 6.3.13 and sends a Location Request message to the selected E-SMLC. The Location Request message conveys any embedded LPP message in the MO-LR Request. Once an MME has selected an E-SMLC it must continue to use that E-SMLC for the duration of the session. The Location Request message indicates whether a location estimate or location assistance data is requested. If the UE's location is requested, the message also includes the requested QoS. If location assistance data is requested, the embedded LPP message will convey the requested types of location assistance data. The message carries also other location parameters received in the MO-LR Request message, the current cell identity obtained from S1-AP message that carries the NAS MO-LR Request, and the UE capability to support LPP. The message also indicates RAT type and/or coverage level if applicable. + +#### 9.2.6.2 Positioning Measurement Establishment Procedure + +- 4) If the UE is requesting its own location, the actions described in clause 9.3a are performed. If the UE is instead requesting location assistance data, the E-SMLC transfers this data to the UE as described in clause 9.3a.1. The E-SMLC determines the exact location assistance data to transfer according to the type of data specified by the UE, the UE location capabilities and the current cell. + +NB-IoT UEs may perform measurements for some positioning methods only when in ECM-IDLE state. An E-SMLC that is aware of this (e.g. from an indication sent by the UE) may allow additional response time to the UE (e.g. in the QoS) to obtain the measurements. An MME that is aware of this (e.g. from the UE access type) may also allow additional time for a location session to complete. + +#### 9.2.6.3 Location Calculation and Release Procedure + +- 5) When a location estimate best satisfying the requested QoS has been obtained or when the requested location assistance data has been transferred to the UE, the E-SMLC returns a Location Response to the MME with an indication whether the obtained location estimate satisfies the requested accuracy or not. This message carries the location estimate if this was obtained. If a location estimate was not successfully obtained, or if the requested location assistance data could not be transferred successfully to the UE, a failure cause is included in the Location Response. +- 6) If the UE did not request transfer of its location to an external LCS Client in step 2, steps 6 to 13 are skipped. Otherwise, if the location estimate was successfully obtained, the MME shall send a Subscriber Location Report to the V-GMLC assigned in the step 2, carrying the MSISDN/IMSI of the UE, the event causing the location estimate (EPC-MO LR) and the location estimate, its age, obtained accuracy indication and the LCS QoS Class requested by the target UE. In addition, the Subscriber Location Report may include the pseudonym indicator, the identity of the LCS Client, the GMLC address and the Service Identity specified by the UE, if available. +- 7) This step is the same as step 7 for a PS-MO-LR in clause 9.2.2.3. +- 8) This step is the same as step 8 for a PS-MO-LR in clause 9.2.2.3. +- 9) This step is the same as step 9 for a PS-MO-LR in clause 9.2.2.3. +- 10) This step is the same as step 10 for a PS-MO-LR in clause 9.2.2.3. +- 11) This step is the same as step 11 for a PS-MO-LR in clause 9.2.2.3. +- 12) This step is the same as step 12 for a PS-MO-LR in clause 9.2.2.3. + +- If the V-GMLC receives the MO-LR Location Information Acknowledgement from the H-GMLC, the V-GMLC shall record charging information both for the UE and inter-working revenue charges and send the Subscriber Location Report Acknowledgement to the MME, carrying the information specifies whether the location estimate of the UE has been handled successfully by the identified LCS Client, and if not success, the corresponding error cause obtained in step 12. + +If the V-GMLC receives the Subscriber Location Report from the MME and it is not required to send to any LCS Client, the V-GMLC shall record charging information for the UE and response the Subscriber Location Report Acknowledgement to the MME. + +- The MME returns a NAS MO-LR Response message to the UE carrying any location estimate requested by the UE including the indication received from E-SMLC whether the obtained location estimate satisfies the requested accuracy or not, or an indicator whether a location estimate was successfully transferred to the identified LCS client. If the location estimate was successfully transferred to the identified LCS Client, the MO-LR Response message shall specify whether the location estimate of the UE has been handled successfully by the identified LCS Client, and if not, the corresponding error cause obtained in step 13. The MME may record charging information. + +## 9.3 LCS signalling procedures specified in UTRAN and GERAN Stage 2 + +The signalling procedures in UTRAN and GERAN are defined in TS 25.305 [1] and TS 43.059 [16] respectively. + +## 9.3a LCS signalling procedures applicable to E-UTRAN + +### 9.3a.1 UE Assisted and UE Based Positioning and Assistance Delivery + +The following procedure depicts a positioning service transaction that is used by the E-SMLC to support UE based positioning, UE assisted positioning and delivery of assistance data. A single location request from the MME may invoke one or more transactions, in which each transaction may perform a single positioning service (e.g. UE assisted positioning, UE capability retrieval). RAN positioning procedures related to E-SMLC and UE communication are specified in TS 36.355 [47]. + +![Sequence diagram illustrating the UE Assisted and UE Based Positioning and Assistance Delivery Procedure. The diagram shows interactions between E-SMLC, MME, eNodeB, and UE. The steps are: 1. Positioning Request (DL Positioning Message) from E-SMLC to MME; 2. Network Triggered Service Request from MME to UE; 3. NAS Transport (DL Positioning Message) from MME to eNodeB; 4. DL Positioning Message from eNodeB to UE; 5. Positioning Measurements and Computation by UE; 6. UE Triggered Service Request or Connection Resume from UE to MME; 7. UL Positioning Message from UE to eNodeB; 8. NAS Transport (UL Positioning Message) from eNodeB to MME; 9. Positioning Response (UL Positioning Message) from MME to E-SMLC.](7136ef99edf9289cc069898bd584d3aa_img.jpg) + +``` + +sequenceDiagram + participant E-SMLC + participant MME + participant eNodeB + participant UE + + E-SMLC->>MME: 1. Positioning Request (DL Positioning Message) + Note over MME,UE: 2. Network Triggered Service Request + MME->>eNodeB: 3. NAS Transport (DL Positioning Message) + eNodeB->>UE: 4. DL Positioning Message + Note right of UE: 5. Positioning Measurements and Computation + Note over MME,UE: 6. UE Triggered Service Request or Connection Resume + UE->>eNodeB: 7. UL Positioning Message + eNodeB->>MME: 8. NAS Transport (UL Positioning Message) + MME->>E-SMLC: 9. Positioning Response (UL Positioning Message) + +``` + +Sequence diagram illustrating the UE Assisted and UE Based Positioning and Assistance Delivery Procedure. The diagram shows interactions between E-SMLC, MME, eNodeB, and UE. The steps are: 1. Positioning Request (DL Positioning Message) from E-SMLC to MME; 2. Network Triggered Service Request from MME to UE; 3. NAS Transport (DL Positioning Message) from MME to eNodeB; 4. DL Positioning Message from eNodeB to UE; 5. Positioning Measurements and Computation by UE; 6. UE Triggered Service Request or Connection Resume from UE to MME; 7. UL Positioning Message from UE to eNodeB; 8. NAS Transport (UL Positioning Message) from eNodeB to MME; 9. Positioning Response (UL Positioning Message) from MME to E-SMLC. + +**Figure 9.8e: UE Assisted and UE Based Positioning and Assistance Delivery Procedure** + +**Precondition:** A Correlation identifier allocated by MME had been passed to the E-SMLC when the location session (i.e. EPC-MT-LR, EPC-MO-LR, or ECP-NI-LR) was initiated. The Correlation identifier must be assigned such that it can be used to identify the E-SMLC serving the location session. + +1. The E-SMLC sends a Location Information message to the MME carrying a Downlink Positioning Information and the Correlation identifier which may request location information from the UE, provide assistance data to the UE or query for the UE capabilities. +2. If the UE is not using Control Plane CIoT EPS Optimisation and if the UE is in ECM-IDLE state (e.g. if the S1 connection was previously released due to data and signalling inactivity), the MME performs a network triggered service request as defined in TS 23.401 [41] in order to establish a signalling connection with the UE. + +If the UE is using Control Plane CIoT EPS Optimisation, procedures for Mobile Terminated Data Transport in Control Plane CIoT EPS optimisation as defined in TS 23.401 [41] are performed by the MME to establish a signalling connection with the UE. + +3. The MME forwards the Downlink Positioning Information to the serving eNodeB in a NAS Transport message conveyed by the S1-AP Transport Message. The MME includes a Routing identifier, in the NAS transport message, representing the Correlation identifier associated with the location session between the MME and E-SMLC. +4. The eNodeB forwards the Downlink Positioning Information and Routing identifier to the UE by NAS Transport Message. +5. The UE stores any assistance data provided in the Downlink Positioning Information and performs any positioning measurements and location computation requested by the Downlink Positioning Information. + +NB-IoT UEs may perform measurements for some positioning methods only when in ECM-IDLE state. In this case, the UE delays performing positioning measurements in step 5 until after the UE enters ECM-IDLE state. + +6. If the UE is not using Control Plane CIoT EPS Optimisation and if the UE is in ECM-IDLE state, the UE initiates a UE triggered service request or, when User Plane CIoT EPS optimization applies, the Connection Resume procedure as defined in TS 23.401 [41] in order to establish a signalling connection with the MME. + +If the UE is using Control Plane CIoT EPS Optimisation, procedures for Mobile Originated Data Transport in Control Plane CIoT EPS optimisation as defined in TS 23.401 [41] are performed by the UE to establish a signalling connection with the MME. + +7. The UE returns any location information obtained in step 5 or returns any capabilities requested in step 4 to the eNodeB in an Uplink Positioning Information included in the NAS Transport message. The Uplink Positioning Information may alternatively carry a request for further assistance data. The UE shall also include the Routing identifier in the NAS Transport Message received in step 4. +8. The eNodeB forwards the Uplink Positioning Information and Routing identifier to the MME in a NAS Transport message. +9. The MME forwards the Uplink Positioning Information and the Correlation identifier to the E-SMLC, based on the received Routing identifier, in a Positioning Response. Steps 6 to 9 may be repeated if the UE needs to send multiple messages to respond to the request received in Step 4. Steps 1 to 9 may be repeated to send new assistance data, and to request further location information and further UE capabilities. + +**NOTE:** The DL Positioning Information messages can be asynchronous. Once the E-SMLC sends at least one DL Positioning Information message towards the UE (steps 1-4), the UE can then send zero or more UL Positioning Information messages towards the E-SMLC (steps 6-9). The UE includes the same Routing identifier in each subsequent message. + +### 9.3a.2 Network Assisted and Network Based Positioning Procedure + +The following procedure is used by the E-SMLC to support network assisted and network based positioning. RAN positioning procedures related to E-SMLC and eNodeB communication are specified in TS 36.455 [48]. + +![Sequence diagram of Network Assisted and Network Based Positioning Procedure. Lifelines: E-SMLC, MME, eNode B, UE. Steps: 1. E-SMLC to MME: Location Information (Network Positioning Information); 2. MME to UE: Network Triggered Service Request; 3. MME to eNode B: S1-AP Transport Message (Network Positioning Information); 4. eNode B: Obtain Measurements; 5. eNode B to MME: S1-AP Transport Message (Network Positioning Information); 6. MME to E-SMLC: Location Information (Network Positioning Information).](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +``` + +sequenceDiagram + participant E-SMLC + participant MME + participant eNode B + participant UE + Note left of E-SMLC: 1. Location Information (Network Positioning Information) + E-SMLC->>MME: 1. Location Information (Network Positioning Information) + Note right of MME: 2. Network Triggered Service Request + MME->>UE: 2. Network Triggered Service Request + Note right of MME: 3. S1-AP Transport Message (Network Positioning Information) + MME->>eNode B: 3. S1-AP Transport Message (Network Positioning Information) + Note right of eNode B: 4. Obtain Measurements + eNode B->>eNode B: 4. Obtain Measurements + Note right of eNode B: 5. S1-AP Transport Message (Network Positioning Information) + eNode B->>MME: 5. S1-AP Transport Message (Network Positioning Information) + Note right of MME: 6. Location Information (Network Positioning Information) + MME->>E-SMLC: 6. Location Information (Network Positioning Information) + +``` + +Sequence diagram of Network Assisted and Network Based Positioning Procedure. Lifelines: E-SMLC, MME, eNode B, UE. Steps: 1. E-SMLC to MME: Location Information (Network Positioning Information); 2. MME to UE: Network Triggered Service Request; 3. MME to eNode B: S1-AP Transport Message (Network Positioning Information); 4. eNode B: Obtain Measurements; 5. eNode B to MME: S1-AP Transport Message (Network Positioning Information); 6. MME to E-SMLC: Location Information (Network Positioning Information). + +**Figure 9.8f: Network Assisted and Network Based Positioning Procedure** + +**Precondition:** A Correlation identifier allocated by the MME had been passed to the E-SMLC when the location session (i.e. EPC-MT-LR, EPC-MO-LR, or EPC-NI-LR) was initiated. + +1. The E-SMLC sends a Location Information message to the MME carrying Network Positioning Information and Correlation identifier which may request location information for the UE from the E-UTRAN. +2. If the UE is not using Control Plane CIoT EPS Optimisation Data Transport in Control Plane CIoT EPS Optimisation and if the UE is in ECM-IDLE state (e.g. if the S1 connection was previously released due to data and signalling inactivity), the MME performs a network triggered service request as defined in TS 23.401 [41] in order to establish a signalling connection with the UE. + +If the UE is using Control Plane CIoT EPS Optimisation, procedures for Mobile Terminated Data Transport in Control Plane CIoT EPS optimisation as defined in TS 23.401 [41] are performed by the MME to establish a signalling connection with the UE. + +3. The MME sends a Network Positioning Information message conveyed in a S1-AP Transport Message to the serving eNodeB for the UE. The MME includes a Routing identifier in the S1-AP Transport Message, representing the E-SMLC associated with the location session. +4. The eNodeB obtains any location information for the UE requested in step 3. +5. The eNodeB returns a Network Positioning Information message to the MME, conveyed in a S1-AP Transport Message, containing the location information obtained in step 4. The eNodeB shall also include the Routing identifier in the S1-AP Transport Message received in step 3. +6. The MME returns the Network Positioning Information received in step 5 to the E-SMLC based on the received Routing identifier. Steps 1 to 6 may be repeated to request further location information and further E-UTRAN capabilities. + +**NOTE:** The Network Positioning Information messages can be asynchronous. Once the E-SMLC sends at least one Network Positioning Information message towards the eNodeB (steps 1-3), the eNodeB can then send zero or more Network Positioning Information messages towards the E-SMLC (steps 5-6). The eNodeB includes the same Routing identifier in each subsequent message. + +### 9.3a.3 Obtaining Non-UE Associated Network Assistance Data + +The following procedure is used by the E-SMLC to support network assisted and network based positioning. This procedure is not associated with a UE location session. It is used in a MME LCS stateless manner to obtain network assistance data from an eNodeB. RAN positioning procedures related to E-SMLC and eNodeB communication are specified in TS 36.455 [48]. + +![Sequence diagram illustrating the procedure for Obtaining Network Assisted Data. The diagram shows four lifelines: E-SMLC, MME, eNode B, and UE. The sequence of messages is: 1. E-SMLC sends 'Location Information (Network Positioning Information)' to MME. 2. MME sends 'S1-AP Transport Message (Network Positioning Information)' to eNode B. 3. eNode B performs 'Obtain Measurements'. 4. eNode B sends 'S1-AP Transport Message (Network Positioning Information)' back to MME. 5. MME sends 'Location Information (Network Positioning Information)' back to E-SMLC.](a634891d16b60b21df90a35c2af72c67_img.jpg) + +``` + +sequenceDiagram + participant E-SMLC + participant MME + participant eNode B + participant UE + Note right of eNode B: 3. Obtain Measurements + E-SMLC->>MME: 1. Location Information (Network Positioning Information) + MME->>eNode B: 2. S1-AP Transport Message (Network Positioning Information) + eNode B-->>MME: 4. S1-AP Transport Message (Network Positioning Information) + MME-->>E-SMLC: 5. Location Information (Network Positioning Information) + +``` + +Sequence diagram illustrating the procedure for Obtaining Network Assisted Data. The diagram shows four lifelines: E-SMLC, MME, eNode B, and UE. The sequence of messages is: 1. E-SMLC sends 'Location Information (Network Positioning Information)' to MME. 2. MME sends 'S1-AP Transport Message (Network Positioning Information)' to eNode B. 3. eNode B performs 'Obtain Measurements'. 4. eNode B sends 'S1-AP Transport Message (Network Positioning Information)' back to MME. 5. MME sends 'Location Information (Network Positioning Information)' back to E-SMLC. + +**Figure 9.8g: Obtaining Network Assisted Data** + +1. The E-SMLC sends a Location Information message to the MME carrying a Network Positioning Information which may request eNodeB position related information from the E-UTRAN. The target eNodeB identity and E-SMLC identity are included for MME routing purposes. +2. The MME sends a Network Positioning Information message to the eNodeB, conveyed in a S1-AP Transport Message. The MME includes a Routing identifier that represents the E-SMLC identity in a S1-AP Transport Message. This Routing identifier is not dynamically retained at the MME (i.e., the MME remains LCS stateless). +3. The eNodeB obtains position information related to the eNodeB. +4. The eNodeB returns a Network Positioning Information message to the MME, conveyed in a S1-AP Transport Message containing the location information obtained in step 3. The eNodeB also includes the Routing identifier in a S1-AP Transport Message received in step 2. +5. The MME returns the Network Positioning Information received in step 4 to the E-SMLC. The MME determines the E-SMLC from the Routing identifier received in step 4. Steps 4 and 5 may be repeated, using the same Routing identifier if the eNB has multiple messages to respond to the request in Step 2. Steps 1 to 5 may be repeated to request further location information and further E-UTRAN capabilities. + +**NOTE:** The Network Positioning Information messages can be asynchronous. Once the E-SMLC sends at least one Network Positioning Information message towards the eNodeB (steps 1-2), the eNodeB can then send zero or more Network Positioning Information messages towards the E-SMLC (steps 4-5). + +### 9.3a.4 Broadcasting Network Assistance Data + +The following procedure is used by the E-SMLC to support broadcasting of network assistance data to target UEs. This procedure is not associated with a UE location session. It is used in a MME LCS stateless manner to send network assistance data to an eNodeB for broadcasting by the eNodeB to target UEs. RAN positioning procedures related to E-SMLC and eNodeB communication are specified in TS 36.455 [48]. + +![Sequence diagram illustrating the Broadcasting Network Assistance Data procedure. The diagram shows five steps: 1. E-SMLC sends Location Information (Network Assistance Data) to MME; 2. MME sends S1-AP Transport Message (Network Assistance Data) to eNode B; 3. eNode B broadcasts Broadcast Message (Network Assistance Data) to UE; 4. eNode B sends S1-AP Transport Message (Network Assistance Data Feedback) to MME; 5. MME sends Location Information (Network Assistance Data Feedback) to E-SMLC.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +``` +sequenceDiagram + participant E-SMLC + participant MME + participant eNode B + participant UE + Note left of E-SMLC: + E-SMLC->>MME: 1. Location Information (Network Assistance Data) + Note right of MME: + MME->>eNode B: 2. S1-AP Transport Message (Network Assistance Data) + Note right of eNode B: + eNode B->>UE: 3. Broadcast Message (Network Assistance Data) + Note right of UE: + eNode B->>MME: 4. S1-AP Transport Message (Network Assistance Data Feedback) + Note right of MME: + MME->>E-SMLC: 5. Location Information (Network Assistance Data Feedback) + Note left of E-SMLC: +``` + +Sequence diagram illustrating the Broadcasting Network Assistance Data procedure. The diagram shows five steps: 1. E-SMLC sends Location Information (Network Assistance Data) to MME; 2. MME sends S1-AP Transport Message (Network Assistance Data) to eNode B; 3. eNode B broadcasts Broadcast Message (Network Assistance Data) to UE; 4. eNode B sends S1-AP Transport Message (Network Assistance Data Feedback) to MME; 5. MME sends Location Information (Network Assistance Data Feedback) to E-SMLC. + +**Figure 9.8h: Broadcasting Network Assistance Data** + +1. The E-SMLC sends a Location Information message to the MME carrying a Network Assistance Data message. The Network Assistance Data message includes assistance data which may be optionally ciphered. The target eNodeB identity and E-SMLC identity are included for MME routing purposes. +2. The MME sends the Network Assistance Data message to the eNodeB, conveyed in a S1-AP Transport Message. The MME includes a Routing identifier that represents the E-SMLC identity in a S1-AP Transport Message. This Routing identifier is not dynamically retained at the MME (i.e., the MME remains LCS stateless). +3. The eNodeB broadcasts the assistance data contained in the Network Assistance Data message. +4. The eNodeB may return a Network Assistance Data Feedback message to the MME, conveyed in a S1-AP Transport Message. The eNodeB also includes the Routing identifier in a S1-AP Transport Message received in step 2. +5. The MME returns the Network Assistance Data Feedback message received in step 4 to the E-SMLC. The MME determines the E SMLC from the Routing identifier received in step 4. + +### 9.3a.5 Delivery of Ciphering Keys to UEs for Broadcast Assistance Data + +The following procedure depicts a procedure that is used by the E-SMLC and the MME to distribute ciphering keys to UEs to enable UEs to decipher broadcast assistance data that was ciphered by the E-SMLC. This procedure is not associated with a UE location session. The procedure makes use of the Attach and Tracking Area Update (TAU) procedures defined in TS 23.401 [41]. + +![Sequence diagram showing the delivery of ciphering keys to UEs for broadcast assistance data. The diagram involves four lifelines: E-SMLC, MME, eNodeB, and UE. The sequence of messages is: 1. E-SMLC sends '1. Ciphering Key Data (ciphering keys)' to MME; 2. MME performs '2. Store ciphering keys'; 3. UE sends '3. Attach Request or TAU Request' to eNodeB; 4. eNodeB forwards '4. Attach Request or TAU Request' to MME; 5. MME sends '5. Attach Accept or TAU Accept' to eNodeB; 6. eNodeB forwards '6. Attach Accept or TAU Accept' to UE; 7. MME performs '7. Delete ciphering keys'.](0931f3e098bd4539041de11c50cec2d2_img.jpg) + +``` + +sequenceDiagram + participant E-SMLC + participant MME + participant eNodeB + participant UE + Note right of MME: 2. Store ciphering keys + E-SMLC->>MME: 1. Ciphering Key Data (ciphering keys) + Note right of MME: 2. Store ciphering keys + UE->>eNodeB: 3. Attach Request or TAU Request + eNodeB->>MME: 4. Attach Request or TAU Request + MME->>eNodeB: 5. Attach Accept or TAU Accept + eNodeB->>UE: 6. Attach Accept or TAU Accept + Note right of MME: 7. Delete ciphering keys + +``` + +Sequence diagram showing the delivery of ciphering keys to UEs for broadcast assistance data. The diagram involves four lifelines: E-SMLC, MME, eNodeB, and UE. The sequence of messages is: 1. E-SMLC sends '1. Ciphering Key Data (ciphering keys)' to MME; 2. MME performs '2. Store ciphering keys'; 3. UE sends '3. Attach Request or TAU Request' to eNodeB; 4. eNodeB forwards '4. Attach Request or TAU Request' to MME; 5. MME sends '5. Attach Accept or TAU Accept' to eNodeB; 6. eNodeB forwards '6. Attach Accept or TAU Accept' to UE; 7. MME performs '7. Delete ciphering keys'. + +**Figure 9.8i: Delivery of Ciphering Keys to UEs for Broadcast Assistance Data** + +1. The E-SMLC sends a Ciphering Key Data message to the MME carrying one or more ciphering keys used to cipher network assistance data that is broadcast to UEs according to the procedure in clause 9.3a.4. For each ciphering key, the E-SMLC includes a ciphering key value, a ciphering key identifier, a validity period, a set of applicable tracking areas and a set of applicable types of broadcast assistance data. +2. The MME stores the ciphering keys including the validity periods, applicable tracking areas and the types of applicable broadcast assistance data. +3. A UE sends an Attach Request or a TAU Request to the eNodeB. The Attach Request or TAU Request may be sent as part of normal mobility management, A TAU request may also be sent specifically to request and obtain ciphering keys. The UE includes in the Attach Request or TAU Request an indication that ciphering keys are requested. Other details of the Attach Request and TAU Request are as defined in TS 23.401 [41]. + +NOTE 1: A UE should request new ciphering keys using a TAU Request caused by expiration of the periodic TAU timer if the remaining validity period for one or more ciphering keys received earlier by the UE is less than the TAU timer value. This can help avoid all UEs initiating a TAU procedure at the same time to obtain new ciphering keys when a validity period for a ciphering key is about to expire. A UE should also request new ciphering keys for a TAU Request caused by entering a new tracking area if previous ciphering keys are not applicable to the new tracking area. + +4. The eNodeB forwards the Attach Request or TAU Request to the serving MME. + +5. The serving MME returns an Attach Accept or TAU Accept to the eNodeB as defined in TS 23.401 [41]. The MME includes in the Attach Accept or TAU Accept one or more ciphering keys applicable to the current tracking area for the UE. The MME also includes for each ciphering key the ciphering key value, the ciphering key identifier, the validity period, the set of applicable tracking areas and the set of applicable types of broadcast assistance data. + +NOTE 2: The MME does not need to keep a record of ciphering keys delivered to a UE and may instead send all ciphering keys stored at step 2 that are applicable to the current tracking area, for which the UE has a subscription and whose validity period had not yet expired. + +6. The eNodeB forwards the Attach Accept or TAU Accept to the UE. The UE may start to use each ciphering key to decipher network assistance data that is broadcast according to the procedure in clause 9.3a.4 once the validity period for the ciphering key has started and if the UE is currently in an applicable tracking area. The UE shall cease using a ciphering key when entering a tracking area not applicable to the ciphering key. The UE shall cease using and shall delete a ciphering key when the validity period for the ciphering key has expired. + +NOTE 3: A UE that receives no ciphering keys in response to a request for ciphering keys may assume that the UE does not have a subscription to receive ciphering keys in the serving PLMN. + +- The MME deletes all information for a ciphering key when the validity period has expired. + +## 9.4 Exception Procedures + +The procedures in this clause apply to all variants of an MT-LR, NI-LR and MO-LR where a Location Request message has been sent either to RAN, for a UE with GERAN or UTRAN access, or to an E-SMLC, for a UE with E-UTRAN access, in order to request some location service (e.g. provision of a location estimate for a target UE or transfer of assistance data to a target UE). + +### 9.4.1 Procedures in the VMSC /MSC server + +After the VMSC /MSC server has requested a location service for a particular UE from RAN, certain events may occur that may temporarily or permanently interfere with the location service attempt. For each such event notified to the VMSC /MSC server, the VMSC /MSC server shall employ one of the following error recovery actions. + +#### Restart the Location Service + +This action shall be employed for any event that temporarily impedes a location service attempt and cannot be delayed until the location service attempt is complete. When such an event is notified to the VMSC /MSC server, it shall immediately cancel the location service attempt and the associated signalling dialogue with RAN, if this still exists by sending a "stop reporting" message to RAN. The "stop reporting" message shall contain the reason for the location procedure cancellation in A/Gb mode or the indication about the type of location request to cancel (e.g. direct) in Iu mode. + +After aborting the location request dialogue with RAN, the VMSC /MSC server may queue the location service request until the event causing the restart has terminated (if not already terminated). The VMSC /MSC server may optionally wait for an additional time period (e.g. if the queuing delay is minimal) to ensure that any resources allocated in and by RAN have time to be released. The VMSC /MSC server may then send another location service request to RAN associated with the target UE. + +#### Abort the Location Service + +This action shall be employed for any event that permanently impedes a location service attempt, such as loss of the dedicated signalling channel to the target UE. When such an event is notified to the VMSC /MSC server, it shall cancel the current location service attempt and the associated signalling dialogue with RAN, if still existing, by sending a "stop reporting" message to RAN. The "stop reporting" message shall contain the reason for the location procedure cancellation in A/Gb mode or the indication about the type of location request to cancel (e.g. direct) in Iu mode. The VMSC /MSC server shall then return an error response to the client or network entity from which the location request was originally received. The VMSC /MSC server shall also release all resources specifically allocated for the location attempt. + +The following table indicates the appropriate error recovery procedure for certain events. For events not listed in the table, the VMSC /MSC server need take no action. + +**Table 9.1: LCS Error Recovery Procedures in the VMSC /MSC server for certain Events** + +| Event | VMSC /MSC server Error Recovery | +|------------------------------------------------------------------------------------------|---------------------------------------------------------| +| Release of radio channel to the UE | Abort | +| Any error response from RAN except for SRNC relocation or inter-MSC handover | Abort | +| In Iu mode inter RNC hard handover, SRNC relocation and inter-MSC or MSC server handover | Abort on Iu level
Restart after process is completed | +| In A/Gb mode inter-MSC Handover and inter-BSC handover | Restart after handover is completed | +| InterSystem handover | Restart after handover is completed | + +If RAN is in an overload condition, it may reject a location request by indicating congestion. The VMSC /MSC server may reduce the frequency of future location service requests until rejection due to overload has ceased. + +### 9.4.2 Void + +### 9.4.3 Procedures in the SGSN + +After the SGSN has requested a location service for a particular UE from RAN, certain events may occur that may temporarily or permanently interfere with the location service attempt. For each such event notified to the SGSN, the SGSN shall employ one of the following error recovery actions. + +#### Restart the Location Service + +This action shall be employed for any event that temporarily impedes a location service attempt and cannot be delayed until the location service attempt is complete. When such an event is notified to the SGSN, it shall immediately cancel the location service attempt and the associated signalling dialogue with RAN, if this still exists by sending a "stop reporting" (Iu mode) or "location abort" (A/Gb mode) message to RAN. The "stop reporting"/"location abort" message shall contain the reason for the location procedure cancellation. + +After aborting the location request dialogue with RAN, the SGSN may queue the location service request until the event causing the restart has terminated (if not already terminated). The SGSN may optionally wait for an additional time period (e.g. if the queuing delay is minimal) to ensure that any resources allocated in and by RAN have time to be released. The SGSN may then send another location service request to RAN associated with the target UE. + +#### Abort the Location Service + +This action shall be employed for any event that permanently impedes a location service attempt, such as loss of the radio channel to the target UE. When such an event is notified to the SGSN, it shall cancel the current location service attempt and the associated signalling dialogue with RAN, if still existing, by sending a "stop reporting"/"location abort" message to RAN. The "stop reporting"/"location abort" message shall contain the reason for the location procedure cancellation. The SGSN shall then return an error response to the client or network entity from which the location request was originally received. The SGSN shall also release all resources specifically allocated for the location attempt. + +The following table indicates the appropriate error recovery procedure for certain events. For events not listed in the table, the SGSN need take no action. + +**Table 9.2: LCS Error Recovery Procedures in the SGSN for certain Events** + +| Event | SGSN Error Recovery | +|--------------------------------------------------------------------------------|---------------------------------------------------------| +| Release of radio channel to the UE | Abort | +| Any error response from RAN causing unavailable signalling connections | Abort | +| Inter RNC hard handover, Inter SRNC relocation (Iu mode only) | Abort on Iu level
Restart after process is completed | +| Suspend of GPRS services (A/Gb mode only)(During CS connection for class B UE) | Abort | +| Intra SGSN Routing Area Update (A/Gb mode only) | Restart | +| Inter SGSN Routing Area Update, inter SGSN relocation | Abort (Note: GMLC may restart) | +| Standalone P-TMSI Reallocation (A/Gb mode only) | Restart | + +### 9.4.3a Procedures in the MME + +After the MME has requested a location service for a particular UE from an E-SMLC, certain events may occur that may temporarily or permanently interfere with the location service attempt. For each such event notified to the MME, the MME shall employ one of the following error recovery actions. + +#### Abort the Location Service: + +This action shall be employed for any event that permanently impedes a location service attempt, such as loss of the radio channel to the target UE or handover to a different MME. When such an event is notified to the MME, it shall cancel the current location service attempt and the associated signalling dialogue with the E-SMLC by sending a "location abort" message to the E-SMLC. The "location abort" message shall contain the reason for the location procedure cancellation. The MME shall then return an error response to the client or network entity (e.g. GMLC) from + +which the location request was originally received. The MME shall also release all resources specifically allocated for the location attempt. + +The following table indicates the appropriate error recovery procedure for certain events. For events not listed in the table, the MME need take no action. + +**Table 9.4.3a: LCS Error Recovery Procedures in the MME for certain Events** + +| Event | MME Error Recovery | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| +| UE Detach | Abort | +| Inter MME Tracking Area Update | Abort | +| E-UTRAN to UTRAN Routing Area Update | Abort | +| Inter MME and inter RAT handover | Abort | +| RRC or S1 connection release not due to User Inactivity (NOTE) | Abort | +| NOTE: The MME can determine the reason for an S1 connection release requested by the eNodeB from the Cause IE included in the UE Context Release Request message - see TS 36.413 [49]. | | + +#### Release S1 Connection and Preserve the Location Service + +This action shall be employed when the MME receives a UE Context Release Request from the serving eNodeB where the cause IE indicates user inactivity. The MME shall release the S1 connection but shall preserve and retain associated context information for the location service. + +### 9.4.4 Void + +### 9.4.5 Handover handling + +#### 9.4.5.1 VMSC /MSC server procedure for Inter-VMSC /MSC server Handover + +When a location estimate is required for a target UE with an established call in a state of inter-VMSC /MSC server handover, the serving location area ID shall be used by the visited MSC /MSC server to identify the correct RAN to serve the location request. All location request related messages shall be sent via MAP/E interface piggy-backed in MAP\_FORWARD\_ACCESS\_SIGNALLING and MAP\_PROCESS\_ACCESS\_SIGNALLING between the visited and serving MSCs /MSC servers. + +#### 9.4.5.2 Handling of an ongoing handover while a request for positioning arrives + +If during an ongoing handover procedure a request for location information arrives, the request shall be suspended until the handover is completed. On completion of the handover, the location preparation procedure shall continue. + +#### 9.4.5.3 Handover handling in Iu mode + +In case of hard handovers in Iu mode, e.g. inter RNC hard handover, or Serving RNC relocation, and inter- MSC, MSC Server or SGSN handovers, the ongoing positioning process is aborted on Iu level. In soft handovers where the Serving RNS and Iu are relocated, any ongoing positioning process is also aborted on Iu level. The MSC, MSC Server or SGSN shall restart the Iu aborted location requests with the new Serving RNC. The new SGSN, however, shall not restart the location request after inter SGSN Routing Area Update or inter SGSN relocation. During intra and inter RNC soft and softer handovers the existing RRC connection can normally be used without any need to abort the on-going positioning process on Iu level. + +#### 9.4.5.4 Handover of an IMS Emergency Call with EPS/GPRS/WLAN Access + +##### 9.4.5.4.1 Common Requirements + +Handover of the PS bearer for an established or not yet established IMS emergency call may occur within the PS domain (i.e. intra E-UTRAN, intra UTRAN, E-UTRAN to UTRAN, UTRAN to E-UTRAN, E-UTRAN to HRPD, WLAN to E-UTRAN, or E-UTRAN to WLAN) as defined in TS 23.401 [41], TS 23.402 [44] and TS 23.060 [15]. Handover of an already established IMS emergency call may also occur from the PS domain to the CS domain using SRVCC as defined in TS 23.216 [43] or DRVCC as defined in TS 23.237 [53]. When such an event occurs in a context + +where location support for the emergency call is required on the source side, continuity of location support may be required on the target side. In this case, the location solution employed on the source and target access sides may stay the same or may change. In addition, some reconfiguration of the associated location server or servers (e.g. GMLC, LRF, E-SLP) may be needed whether or not the solution changes. Table 9.2a summarizes the support of all possible handover scenarios. Note that in all cases, the LRF that was originally assigned to the IMS emergency call as described in clause 9.8.4 must be retained after handover in order to avoid any impact to the emergency centre/PSAP. However, other location server changes (e.g. addition or removal of a GMLC) may occur following handover as summarized in Table 9.2a. + +**Table 9.2a: Location Reconfiguration Requirements for handover of an Emergency PS Bearer or IMS Emergency Call to support Location Continuity (Note 1)** + +NOTE: The source side can choose to send an update even with no active location. + +| Source Access Side(s) | Target Access Side(s) | Source Location Solution | Target Location Solution | Reconfiguration Requirements | +|-------------------------|-------------------------|-----------------------------------|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRAN, UTRAN PS | E-UTRAN, UTRAN PS | TS 23.271 | TS 23.271 |

Either (a) Source side SGSN or MME transfers the target side SGSN or MME identity to the source side GMLC Or (b) Target side SGSN or MME transfers its own identity to the target side GMLC (Note 2)

Source or target side GMLC updates the LRF

LRF replaces the source side GMLC with the target side GMLC if the GMLCs are different

| +| E-UTRAN, UTRAN PS | E-UTRAN, UTRAN PS | TS 23.271 | OMA AD SUPL [38], OMA TS ULP [39] (Note 3) |

Source side SGSN or MME transfers the target side SGSN or MME identity to the source side GMLC (Note 2)

Source side GMLC updates the LRF

LRF replaces the source side GMLC with a target side E-SLP

LRF transfers the UE identity or address (e.g. IP address) to the target side E-SLP when the UE location is next needed.

| +| E-UTRAN, UTRAN PS | E-UTRAN, UTRAN PS | OMA AD SUPL [38], OMA TS ULP [39] | TS 23.271 (Note 3) |

Target side SGSN or MME transfers its own identity to the target side GMLC (Note 2)

Target side GMLC updates the LRF

LRF replaces the source side SUPL E-SLP with the target side GMLC

| +| E-UTRAN, UTRAN PS, WLAN | E-UTRAN, UTRAN PS, WLAN | OMA AD SUPL [38], OMA TS ULP [39] | OMA AD SUPL [38], OMA TS ULP [39] | None identified | +| E-UTRAN | HRPD | TS 23.271 | OMA AD SUPL [38], OMA TS ULP [39] |

Source side MME transfers an HRPD indication and an HRPD identity if known (e.g. cell ID) to the source side GMLC (Note 2)

Source side GMLC updates the LRF

LRF replaces the source side GMLC with a target side E-SLP

LRF transfers the UE identity or address (e.g. IP address) to the target side E-SLP when the UE location is next needed.

| + +| | | | | | +|----------------------|----------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| E-UTRAN,
UTRAN PS | UTRAN CS
GERAN CS | TS 23.271 | TS 23.271 |

Either (a) Source side SGSN or MME transfers the target side SRVCC MSC identity to the source side GMLC
Or (b) Target side SRVCC MSC transfers its own identity to the target side GMLC (Note 2)

Source or target side GMLC updates the LRF

LRF replaces the source side GMLC with the target side GMLC if the GMLCs are different

| +| E-UTRAN,
UTRAN PS | UTRAN CS
GERAN CS | OMA AD
SUPL [38], OMA
TS ULP [39] | TS 23.271 |

Target side SRVCC MSC transfers its own identity to the target side GMLC (Note 2)

Target side GMLC updates the LRF

LRF replaces the source side SUPL E-SLP with the target side GMLC

| +| E-UTRAN | 1xRTT | TS 23.271 | J-STD-036B [32]
(Note 4) |

Either (a) Source side MME transfers the 1xRTT Reference Cell ID to the source side GMLC
Or (b) A target side update occurs (Note 2, Note 4)

Source side GMLC or Target side updates the LRF (Note 4)

LRF replaces the source side GMLC with location support on the target side (Note 4)

| +| E-UTRAN | 1xRTT | OMA AD
SUPL [38], OMA
TS ULP [39] | J-STD-036B [32]
(Note 4) |

The target side updates the LRF (Note 4)

The LRF replaces the source side E-SLP with location support on the target side (Note 4)

| +| E-UTRAN | WLAN | TS 23.271 | OMA AD
SUPL [38], OMA TS
ULP [39]
or
UPLI/NPLI
TS 23.167 [36a] |

Source side MME transfers an indication of handover to a non-3GPP access to the source side GMLC (Note 2)

Source side GMLC updates the LRF

LRF removes use of the GMLC

If SUPL is used on the target side, the LRF assigns a target side E-SLP and transfers the UE identity or address (e.g. IP address) to the E-SLP when the UE location is next needed.

| +| WLAN | E-UTRAN | OMA AD
SUPL [38], OMA
TS ULP [39]
or
UPLI/NPLI
TS 23.167 [36a] | TS 23.271 |

Target side MME transfers its own identity to the target side GMLC (Note 2)

Target side GMLC updates the LRF

LRF uses the target side GMLC and removes the source side SUPL E-SLP if previously used.

| + +| | | | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------|-------------------------------------------------------------------------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| WLAN | UTRAN CS
GERAN CS | OMA AD
SUPL [38], OMA
TS ULP [39]
or
UPLI/NPLI
TS 23.167 [36a] | TS 23.271 | Target side MSC server transfers its own identity to the target side GMLC (Note 5)

Target side GMLC updates the LRF

LRF uses the target side GMLC and removes the source side SUPL E-SLP if previously used. | +| NOTE 1: It is assumed that all handovers are intra-operator and that a single LRF is used by an operator for all IMS emergency calls. Use of more than one LRF is FFS. | | | | | +| NOTE 2: A source side update should be configured if the control plane location is used on the source side but will not be used on the target side. A target side update should be configured if the control plane location will be used on the target side but was not used on the source side. An update on either the source or target side but not both should be configured when the control plane location solution is or may be used on both sides. No update is needed when a user plane location solution is used on both sides. The knowledge of the location solution can also be configured - e.g. and may depend on the access type, the location capabilities of the UE and whether a UE is roaming or not.. | | | | | +| NOTE 3: it is allowed to change location solution for an intra E-UTRAN or intra UTRAN PS handover as well as for inter-RAT PS handover although this is expected to be an unlikely scenario for handover within the same operator's networks. | | | | | +| NOTE 4: actions on the target 1xRTT side are outside the scope of this TS. | | | | | +| NOTE 5: The target side MSC server needs to be aware of E-STN-DR association with an emergency call. | | | | | + +##### 9.4.5.4.2 Location Continuity for Handover between 3GPP and 3GPP2 Access Types + +Details concerning the interactions between the LRF, GMLCs, E-SLPs and any 1xRTT location servers to support the reconfiguration requirements in Table 9.2a are outside the scope of this TS. Support of location continuity by other entities is defined below in association with Figure 9.8h. + +![Sequence diagram illustrating the support of location continuity for handover of an IMS emergency call. The diagram shows interactions between LRF, Target Location Server, Source Location Server, Target Serving Node, Source MME/SG SN, and UE. The process involves emergency IP bearer setup, location requests, location sessions, handover requests, and final reconfiguration of location servers.](c07e21a8d65991db04263322f859c94f_img.jpg) + +``` + +sequenceDiagram + participant LRF + participant TLS as Target Location Server + participant SLS as Source Location Server + participant TSNode as Target Serving Node + participant SMSN as Source MME/SG SN + participant UE + + Note over LRF, UE: 1. Emergency IP Bearer Setup and IMS Emergency Call Origination + SLS->>SMSN: 2. Provide Subscriber Location request (IMSI, MSISDN, IMEI) + SMSN->>UE: 3. Start Location Session + Note over SMSN, UE: 4. Handover Required + SMSN->>TSNode: 5. Handover Request + Note over TSNode, UE: 6. Handover + Note over TSNode, UE: 7. Terminate Location Session + TSNode->>SLS: 8a. Provide Subscriber Location response (location estimate, Target Serving Node Identity or Reference Cell ID) + TSNode->>SLS: 8b. Subscriber Location Report (Handover event, IMSI, MSISDN, IMEI, Location Estimate, Target Serving Node Identity or Reference Cell ID) + SLS->>TSNode: 9. Subscriber Location Report Ack. + SLS->>TLS: 10. Subscriber Location Report (Handover event, IMSI, MSISDN, IMEI, Target Serving Node Identity) + TLS->>SLS: 11. Subscriber Location Report Ack. + Note over LRF, SLS: 12. Reconfigure source and target location servers + Note over LRF, UE: 13. MT -LR + +``` + +Sequence diagram illustrating the support of location continuity for handover of an IMS emergency call. The diagram shows interactions between LRF, Target Location Server, Source Location Server, Target Serving Node, Source MME/SG SN, and UE. The process involves emergency IP bearer setup, location requests, location sessions, handover requests, and final reconfiguration of location servers. + +**Figure 9.8h: Support of Location Continuity for Handover of an IMS Emergency Call** + +1. Following the request for an emergency call, the UE establishes an emergency PDN connection for E-UTRAN access as defined in TS 23.401 [41] or an emergency PDP context for UTRAN PS access as defined in TS 23.060 [15]. The UE may then establish an IMS emergency call as defined in TS 23.167 [36a] during which an LRF is assigned and a source location server (e.g. GMLC) may be chosen as described in clause 9.8.4 +2. At some later time, the serving MME or SGSN (hereafter referred to as the source SGSN or MME) may receive a request from an associated GMLC (hereafter referred to as the source GMLC) for the location of the UE if the location solution defined in this TS is used on the source access side. +3. If step 2 occurs or if support for an NI-LR is required, the source SGSN or MME starts a location session with the serving RNC or an E-SMLC, in each case respectively, to obtain the location of the UE. + +4. A request is later sent to the source SGSN or MME from the serving eNodeB (for E-UTRAN access) or serving RNC (for UTRAN access) for a handover to a particular target eNodeB (for handover to E-UTRAN) or target RNC (for handover to UTRAN PS) or target MSC server (for handover to UTRAN CS or GERAN CS) or target cell associated with a particular 1xRTT MSC (for handover to 1xRTT) or HRPD target cell (for handover to HRPD). +5. For handover to E-UTRAN, UTRAN PS, UTRAN CS or GERAN CS, the source MME or SGSN sends a Handover Request message to the target MME, SGSN, MSC server or MSC server (hereafter referred to as the target serving node) in each case respectively as defined in TS 23.401 [41], TS 23.060 [15] or TS 23.216 [43]. For handover from E-UTRAN to 1xRTT, the source MME initiates a handover to a target 1xRTT IWS using single radio voice call continuity procedures as described in TS 23.216 [43]. For handover from E-UTRAN to HRPD, this step does not occur. +6. The rest of the handover preparation and execution procedure is completed as defined in TS 23.401 [41], TS 23.402 [44], TS 23.060 [15] or TS 23.216 [43]. +7. The location session started in step 3 may terminate normally before step 6 is complete. If not, the source SGSN or MME shall abort the session once step 6 is complete. This may lead to provision of a location estimate for the UE to the source SGSN or MME. +- 8a. If the location solution defined in this TS is used on the source side and step 2 occurred, the source SGSN or MME returns a Provide Subscriber Location response to the source GMLC carrying any location estimate obtained previously for the UE. Depending on configuration information in the source SGSN or MME (e.g. which may be related to the source and target serving node identities, the location capabilities of the UE and whether the UE is roaming or not), the Provide Subscriber Location response may, except for handover to HRPD, convey the identity of the target serving node. In the case of handover to 1xRTT, the Provide Subscriber Location response may convey the Reference Cell ID. +- 8b. If the location solution defined in this TS is used on the source side but steps 2 and 8a do not occur, the source SGSN or MME may depending on configuration information in the source SGSN or MME (e.g. as in step 8a) send a Subscriber Location Report to the source GMLC carrying the UE identity (IMSI, MSISDN and/or IMEI), an event type indicating handover and, except for handover to HRPD, the identity of the target serving node. In the case of handover to 1xRTT, the Subscriber Location Report may convey the Reference Cell ID. +9. The source GMLC acknowledges the message in step 8b if this occurs. +10. Steps 10 and 11 only apply when the target side supports a 3GPP access type (e.g. do not apply to 1xRTT or HRPD). Depending on configuration information in the target serving node (e.g. which may be related to the source and target serving node identities, the location capabilities of the UE and whether the UE is roaming or not), the target serving node may after handover in step 6 is complete send a Subscriber Location Report to a GMLC on the target side if the location solution defined in this TS will be used on the target side. The Subscriber Location Report carries the UE identity (IMSI, MSISDN and/or IMEI), an event type indicating handover and the identity of the target serving node. If the target serving node is an MSC, it will send the UE identity as received from source MME/SGSN in Handover Request message in step 5. If the MSC does not receive MSISDN from source MME/SGSN, MSISDN may be populated with a non-dialable callback number as specified in clause 6.4.3. However, no location estimate is included. The target serving node may determine the address of the target GMLC from configuration information. +11. The target GMLC acknowledges the message in step 10. +12. Reconfiguration of the LRF and the source and target location servers may occur as summarized in Table 9.2a which may involve removal of a source GMLC or E-SLP, assignment of a new target GMLC or E-SLP and/or updating of information in the LRF and in the source/target location server(s). The details of this step are outside the scope of this TS. +13. If the LRF needs a location estimate for the UE after handover has occurred, it may instigate an MT-LR request via either the target GMLC if the location solution defined in this TS will be used on the target side or a target E-SLP if the location solution defined in OMA SUPL [38], [39] will be used. This will involve a repetition of step 2 on the target side if the location solution defined in this TS is used. Steps 2 to 12 may also be repeated on the target side to support a further handover if the previous handover was to either E-UTRAN or UTRAN PS. + +If target serving node is MME and it determines that emergency service is no longer active, the MME may send a Subscriber Location Report to the GMLC with the event (EMERGENCY\_CALL\_RELEASE) causing the message, see step 8-10 of figure 9-20. + +##### 9.4.5.4.3 Location Continuity for E-UTRAN Handover to WLAN + +Support of location continuity for E-UTRAN handover to WLAN is defined below in association with Figure 9.8i. + +![Sequence diagram illustrating Location Continuity for Handover of an IMS Emergency Call from E-UTRAN to WLAN. The diagram shows interactions between LRF, Target Location Server, Source Location Server, Source MME, and UE. The sequence includes: 1. Emergency IP Bearer Setup and IMS Emergency Call Origination; 2. Provide Subscriber Location request (IMSI, MSISDN, IMEI); 3. Start Location Session; 4. Handover; 5. Terminate Location Session; 6a. Provide Subscriber Location response (location estimate, Handover to non-3GPP Access); 6b. Subscriber Location Report (Handover event, IMSI, MSISDN, IMEI, Location Estimate, Handover to non-3GPP Access); 7. Subscriber Location Report Ack.; 8. Reconfigure source and target location servers; 9. MT-LR.](d0654bc33a544f31c1cb3e0cd77e0aab_img.jpg) + +``` + +sequenceDiagram + participant LRF + participant TLS as Target Location Server + participant SLS as Source Location Server + participant SMME as Source MME + participant UE + + Note over LRF, SMME: 1. Emergency IP Bearer Setup and IMS Emergency Call Origination + SLS->>SMME: 2. Provide Subscriber Location request (IMSI, MSISDN, IMEI) + SMME->>UE: 3. Start Location Session + SMME->>UE: 4. Handover + SMME->>UE: 5. Terminate Location Session + SMME->>SLS: 6a. Provide Subscriber Location response (location estimate, Handover to non-3GPP Access) + SMME->>SLS: 6b. Subscriber Location Report (Handover event, IMSI, MSISDN, IMEI, Location Estimate, Handover to non-3GPP Access) + SLS->>SMME: 7. Subscriber Location Report Ack. + Note over LRF, SLS: 8. Reconfigure source and target location servers + Note over LRF, SMME: 9. MT-LR + +``` + +Sequence diagram illustrating Location Continuity for Handover of an IMS Emergency Call from E-UTRAN to WLAN. The diagram shows interactions between LRF, Target Location Server, Source Location Server, Source MME, and UE. The sequence includes: 1. Emergency IP Bearer Setup and IMS Emergency Call Origination; 2. Provide Subscriber Location request (IMSI, MSISDN, IMEI); 3. Start Location Session; 4. Handover; 5. Terminate Location Session; 6a. Provide Subscriber Location response (location estimate, Handover to non-3GPP Access); 6b. Subscriber Location Report (Handover event, IMSI, MSISDN, IMEI, Location Estimate, Handover to non-3GPP Access); 7. Subscriber Location Report Ack.; 8. Reconfigure source and target location servers; 9. MT-LR. + +**Figure 9.8i: Location Continuity for Handover of an IMS Emergency Call from E-UTRAN to WLAN** + +1. Following the request for an emergency call, the UE establishes an emergency PDN connection for E-UTRAN access as defined in TS 23.401 [41]. The UE may then establish an IMS emergency call as defined in TS 23.167 [36a] during which an LRF is assigned and a source location server (e.g. a GMLC) may be chosen as described in clause 9.8.4. +2. At some later time, the serving MME (hereafter referred to as the source MME) may receive a request from an associated GMLC (hereafter referred to as the source GMLC) for the location of the UE if the location solution defined in this TS is used on the source access side. +3. If step 2 occurs or if support for an NI-LR is required, the source MME starts a location session with the serving E-SMLC to obtain the location of the UE. +4. A handover of the UE to WLAN access occurs as defined in TS 23.402 [44]. The source MME is informed of the handover to a non-3GPP access through the PDN GW Initiated PDN Disconnection at the end of the handover procedure (see TS 23.401 [41] and TS 23.402 [44]). + +5. The location session started in step 3 may terminate normally before step 4 is complete. If not, the source MME shall abort the session once step 4 is complete. This may lead to provision of a location estimate for the UE to the source MME. +- 6a. If the location solution defined in this TS is used on the source side and step 2 occurred, the source MME returns a Provide Subscriber Location response to the source GMLC carrying any location estimate obtained previously for the UE and including an indication of handover to a non-3GPP access. +- 6b. If the location solution defined in this TS is used on the source side but steps 2 and 6a do not occur, the source MME shall send a Subscriber Location Report to the source GMLC carrying the UE identity (IMSI, MSISDN and/or IMEI), an event type indicating handover and an indication of handover to a non-3GPP access. +7. The source GMLC acknowledges the message in step 6b if this occurs. +8. Reconfiguration of the LRF and the source and target location servers may occur as summarized in Table 9.2a which may involve removal of a source GMLC, assignment of a new target E-SLP and/or updating of information in the LRF and in the source/target location server(s). The details of this step are outside the scope of this TS. +9. If the LRF needs a location estimate for the UE after handover has occurred, it may either instigate an MT-LR request via a target E SLP if the location solution defined in OMA SUPL [38], [39] will be used on the target side or instigate a location request for a UPLI or NPLI as defined in TS 23.167 [36a]. + +##### 9.4.5.4.4 Location Continuity for WLAN Handover to E-UTRAN, UTRAN or GERAN + +Support of location continuity for WLAN handover to E-UTRAN, UTRAN or GERAN is defined below in association with Figure 9.8j. + +![Sequence diagram for Figure 9.8j: Location Continuity for Handover of an IMS Emergency Call from WLAN to E-UTRAN, UTRAN or GERAN. The diagram shows interactions between LRF, Target Location Server, Source Location Server, Target MME or MSC, and UE. The steps are: 1. Emergency IP Bearer Setup and IMS Emergency Call Origination; 2. Handover; 3. Subscriber Location Report (Handover event, IMSI, MSISDN, IMEI, Location Estimate, Target Node Identity); 4. Subscriber Location Report Ack.; 5. Reconfigure source and target location servers; 6. MT-LR.](b3cd59f24a21fab4cd8ac6fe743ab3a9_img.jpg) + +``` + +sequenceDiagram + participant LRF + participant TLS as Target Location Server + participant SLS as Source Location Server + participant TMM as Target MME or MSC + participant UE + + Note over LRF, UE: 1. Emergency IP Bearer Setup and IMS Emergency Call Origination + Note over TMM, UE: 2. Handover + TMM->>SLS: 3. Subscriber Location Report (Handover event, IMSI, MSISDN, IMEI, Location Estimate, Target Node Identity) + SLS->>TMM: 4. Subscriber Location Report Ack. + Note over LRF, SLS: 5. Reconfigure source and target location servers + Note over LRF, UE: 6. MT-LR + +``` + +Sequence diagram for Figure 9.8j: Location Continuity for Handover of an IMS Emergency Call from WLAN to E-UTRAN, UTRAN or GERAN. The diagram shows interactions between LRF, Target Location Server, Source Location Server, Target MME or MSC, and UE. The steps are: 1. Emergency IP Bearer Setup and IMS Emergency Call Origination; 2. Handover; 3. Subscriber Location Report (Handover event, IMSI, MSISDN, IMEI, Location Estimate, Target Node Identity); 4. Subscriber Location Report Ack.; 5. Reconfigure source and target location servers; 6. MT-LR. + +**Figure 9.8j: Location Continuity for Handover of an IMS Emergency Call from WLAN to E-UTRAN, UTRAN or GERAN** + +1. Following the request for an emergency call, the UE establishes an emergency PDN connection for WLAN access as defined in TS 23.402 [44]. The UE may then establish an IMS emergency call as defined in + +TS 23.167 [36a] during which an LRF is assigned and a source location server (e.g. an E-SLP) may be chosen as described in clause 9.8.4. + +2. A handover of the UE to either E-UTRAN access or UTRAN/GERAN CS access occurs as defined in TS 23.402 [44] or TS 23.237 [53], respectively. For handover to E-UTRAN, the target MME is informed of the handover through the UE Attach Request indicating "handover for emergency services" at the start of the handover procedure as defined in TS 23.402 [44]. For handover to GERAN or UTRAN CS access, the target MSC server is informed of the handover through receipt of a normal CS call setup request from the UE using an E-STN-DR assigned by the serving network as defined in TS 23.237 [53]. +3. After the handover in step 2 is complete, the target MME or MSC server shall send a Subscriber Location Report to a GMLC on the target side if the location solution defined in this TS will be used on the target side. The Subscriber Location Report carries the UE identity (IMSI, MSISDN and/or IMEI), an event type indicating handover and the identity of the target serving node. The target serving node may determine the address of the target GMLC from configuration information. +4. The target GMLC acknowledges the message in step 3. +5. Reconfiguration of the LRF and the source and target location servers may occur as summarized in Table 9.2a which may involve removal of a source E-SLP, assignment of a new target GMLC and/or updating of information in the LRF and in the source/target location server(s). The details of this step are outside the scope of this TS. +6. If the LRF needs a location estimate for the UE after handover has occurred, it may instigate an MT-LR request via the target GMLC if the location solution defined in this TS will be used on the target side. + +If the location solution defined in this TS will be used on the target side and the target MME or MSC server determines that emergency service is no longer active, the MME or MSC server may send a Subscriber Location Report to the GMLC with the event (EMERGENCY\_CALL\_RELEASE) causing the message, see steps 8-10 of Figure 9.20 in the case of a target MME or steps 11-12 of Figure 9.4 in the case of a target MSC server. + +## 9.5 Privacy + +### 9.5.1 Privacy Override Indicator (POI) + +The POI is used to determine whether the privacy settings of the subscriber to be positioned shall be overridden by the request for location services. The POI is applicable only to Emergency service and Lawful intercept service. The assignment of a POI value with an "override" or "not override" value in the LCS client profile is done during the LCS client provisioning. The type of LCS client requesting location information (i.e. emergency, law-enforcement etc.) shall determine the value of the POI assigned to the LCS client profile. + +POI is not sent to the MME. + +There are two distinct cases regarding the handling of the privacy override indicator. + +**Procedure A:** If the subscriber to be positioned is in the same country as the GMLC or if the subscriber to be positioned is in a different country than the GMLC and an appropriate bilateral agreement exists between operators, then the POI shall override the subscriber's privacy options, as allowed by regulatory requirements. + +**Procedure B:** Otherwise the POI shall not override the subscriber's privacy options. + +### 9.5.2 Privacy Procedures + +The privacy profile of the UE subscriber (SLPP) may for GSM and UMTS be stored in HLR/HSS and/or in H-GMLC/PPR. The privacy profile of the UE subscriber (SLPP) shall for EPS be stored in H-GMLC/PPR. If the privacy profile data are stored in SLPP of H-GMLC/PPR, then the pseudo external identities, if required, shall be contained in the SLPP of the HLR/HSS. Also if the privacy profile data are stored in H-GMLC/PPR, H-GMLC/PPR sends the indicators of privacy related action or the pseudo external identities to the serving nodes in order to inform the results of the privacy check procedures in H-GMLC/PPR. + +The SLPP stored in the HLR/HSS shall be downloaded to the VMSC, MSC Server and SGSN together with the rest of his subscription information in the existing operation INSERT\_SUBSCRIBER\_DATA. It will be deleted with the existing operation DELETE\_SUBSCRIBER\_DATA. + +In case of an Emergency Services location request, based on the location of the VMSC/MSC Server/SGSN and the R-GMLC, the V-GMLC evaluates whether to accept or ignore the received POI, according to the definition in clause 9.1.5. If privacy override is not allowed, then the V-GMLC rejects the request. + +In case the privacy override is allowed, the POI is transferred from the GMLC to the VMSC/MSC Server/SGSN in the location request. Based on the location of the GMLC the VMSC/MSC Server/SGSN evaluates whether to accept or ignore the received POI according to the definition in clause 9.5.1. + +If the POI is accepted the location requested is unconditionally performed. Otherwise the VMSC/MSC Server/SGSN evaluates the privacy options in the UE subscriber's subscription profile (assuming this is held in the VLR/MSC Server/SGSN) or evaluates the received privacy related action indicators. If the corresponding register does not contain the UE subscription profile, LCS will rely on the existing GSM recovery mechanisms to obtain the profile. + +If local regulatory requirements mandate it, any MT-LR for an emergency services LCS client and any NI-LR for an emergency services call origination shall be allowed by the VMSC/MSC Server/SGSN/MME. + +If the location request is allowed by the privacy options the location request is performed. Otherwise, if the location request is barred by the privacy options, the location request is refused an error response is returned to the LCS client with a cause code indicating that the request was rejected by the subscriber. + +### 9.5.3 UE Privacy Options + +The UE privacy options in the SLPP apply to an CS-MT-LR/PS-MT-LR or NI-LR/PS-NI-LR and either indicate that no CS-MT-LR/PS-MT-LR or NI-LR/PS-NI-LR is allowed for the UE (except as may be overridden by the POI or local regulatory requirements) or define the particular classes of LCS client for which an CS-MT-LR/PS-MT-LR or NI-LR/PS-NI-LR for location are allowed, with the following classes being possible: + +[Editor's note: An e-mail comment pointed out that there are different cases still to be covered in the description of the classes: 1. the LCS Client identity is included in SLPP or 2. the LCS Client identity is NOT included in SLPP. Also some GMLC restriction conditions need to be mentioned.] + +- a) Universal Class - allow positioning by all LCS clients; +- b) Call/Session related Class +- c) Call/Session-unrelated Class +- d) PLMN operator Class + +Moreover the SLPP may contain the service types allowed by the subscriber. + +All UE privacy options of above four classes are commonly used for both CS and PS domain. + +The privacy classes are selected according to the rules described in the ANNEX A. If more than one privacy class are subscribed in the UE's SLPP, the looser privacy setting shall be selected. ANNEX A applies also in case service types privacy checking are subscribed together with one or more other privacy classes. + +NOTE 1: If a privacy option setting in a domain is updated, the same modification will be applied to the other domain. + +NOTE 2: The options for each privacy class and the service type are described in the subsequent clauses independently from the options of the other privacy classes. The combination of the privacy class and service type options are described in the rules of Annex A + +#### 9.5.3.1 Universal class + +When the user of the UE subscribes to the "Universal Class" the CS-MT-LR/PS-MT-LR or NI-LR/PS-NI-LR positioning is allowed by all LCS clients. + +If the UE subscribes to the universal class, any CS-MT-LR or NI-LR shall be allowed by the VMSC/MSC Server and any PS-MT-LR or PS-NI-LR shall be allowed by the SGSN. + +If the UE subscribes to the universal class and H-GMLC/PPR knows that the serving node supports the indicator of privacy check related action, H-GMLC/PPR sends the indicators for call/session unrelated class, which indicates "Location allowed without notification". If the UE subscribes to the universal class and H-GMLC/PPR knows that the serving node does not support the indicator of privacy check related action, H-GMLC/PPR may send the appropriate pseudo external identity as described in Annex C. + +#### 9.5.3.2 Call/Session related class + +When the user of the UE subscribes to the "Call/Session related Class" the CS-MT-LR/PS-MT-LR/EPC-MT-LR or NI-LR/PS-NI-LR positioning is allowed in the following cases: + +Allow positioning by specific identified value added LCS client or groups of value added LCS Client to which the UE originated a call in CS domain or a value added LCS client with which the UE has a session via an active PDP context in PS domain indicated by a specific APN-NI. For each identified LCS client or group of LCS Clients, one of the following subscription options shall apply: + +- \* location request allowed only from GMLCs identified in the SLPP; +- \* location request allowed only from a GMLC in the home country; +- \* location request allowed from any GMLC (default case). + +For each identified value added LCS client or group of LCS Clients in the privacy exception list, one of the following subscription options shall apply: + +- \* positioning allowed without notifying the UE user (default case); +- \* positioning allowed with notification to the UE user; +- \* positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification; +- \* positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user. + +For all value added LCS clients sending a call related CS-MT-LR/PS-MT-LR/EPC-MT-LR that are not identified in the privacy exception list, one of the following subscription option shall apply: + +- \* positioning not allowed; +- \* positioning allowed without notifying the UE user (default case); +- \* positioning allowed with notification to the UE user; +- \* positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification; +- \* positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user. + +NOTE 2: The usage of Call/Session related Class in the IM subsystem is FFS. + +##### 9.5.3.2.1 Call/session-related class in the CS-domain + +If the UE subscribes to the call/session-related class, an CS-MT-LR may be allowed if both of following conditions are met: + +- The UE previously originated a call in CS domain that is still established and the called party number dialled by the UE matches the called party number received from the GMLC. +- The identity of the LCS client or LCS client group supplied by the GMLC matches the identity of any LCS Client or LCS Client group contained in the UE's SLPP and any other GMLC restrictions associated with this LCS Client identity in the SLPP are also met + +If these conditions are satisfied, the CS-MT-LR shall be allowed if the UE user subscribes to either location without notification or location with notification. If the UE user subscribes to location with notification and privacy verification, the CS-MT-LR shall be allowed following notification to the UE if the UE user either returns a response indicating that location is allowed or returns no response but subscribes to allowing location in the absence of a response. In all other cases, the CS-MT-LR shall be restricted. + +##### 9.5.3.2.2 Call/session-related class in the PS-domain + +If the UE subscribes to the call/session-related class, a PS-MT-LR/EPC-MT-LR may be allowed if all of the following conditions are met: + +- The UE previously originated a PDP/EPS Bearer-context towards the network where the external client is located and that this context is still established. +- The APN-NI negotiated between the UE and SGSN/MME matches the APN-NI received from the GMLC. +- The identity of the LCS client or LCS client group supplied by the GMLC matches the identity of any LCS Client or LCS Client group contained in the UE's SLPP and any other GMLC restrictions associated with this LCS Client identity in the SLPP are also met. + +If these conditions are satisfied, the PS-MT-LR/EPC-MT-LR shall be allowed if the UE user subscribes to either location without notification or location with notification. If the UE user subscribes to location with notification and privacy verification, the PS-MT-LR/EPC-MT-LR shall be allowed following notification to the UE if the UE user either returns a response indicating that location is allowed or returns no response but subscribes to allowing location in the absence of a response. In all other cases, the PS-MT-LR/EPC-MT-LR shall be restricted. + +##### 9.5.3.2.3 Call/session-related class when LCS client not in SLPP + +If the UE subscribes to the call/session related class, a CS-MT-LR, PS-MT-LR or EPC-MT-LR from an LCS client that is NOT contained in the SLPP of the target UE shall be allowed or restricted according to the following conditions: + +- For any non-matched LCS client, the CS-MT-LR, PS-MT-LR or EPC-MT-LR shall be allowed, if the UE user subscribes to either location without notification or location with notification. + +If the UE user subscribes to location with notification and privacy verification, the CS-MT-LR, PS-MT-LR or EPC-MT-LR shall be allowed following notification to the UE if the UE user either returns a response indicating that location is allowed or returns no response but subscribes to location in the absence of a response. In all other cases, the CS-MT-LR, PS-MT-LR or EPC-MT-LR shall be restricted. + +#### 9.5.3.3 Call/Session-unrelated class + +When the user of the UE subscribes to the "Call/Session unrelated Class" the CS-MT-LR/PS-MT-LR/EPC-MT-LR or NI-LR/PS-NI-LR positioning is allowed in the following cases: + +Allow positioning by specific identified value added LCS Clients or groups of value added LCS Client with the following restrictions allowed for each identified value added LCS Client or group of value added LCS Clients: + +- \* location request allowed only from GMLCs identified in the SLPP; +- \* location request allowed only from a GMLC in the home country; +- \* location request allowed from any GMLC (default case). + +For each identified value added LCS client in the privacy exception list, one of the following subscription options shall apply: + +- \* positioning allowed without notifying the UE user (default case); +- \* positioning allowed with notification to the UE user; +- \* positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification; + +- \* positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user. + +For all value added LCS clients sending a non-call/session related CS-MT-LR/PS-MT-LR/EPC-MT-LR that are not identified in the privacy exception list, one of the following subscription option shall apply: + +- \* positioning not allowed (default case); +- \* positioning allowed with notification to the UE user; +- \* positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification; +- \* positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user. + +##### 9.5.3.3.1 Call/session-unrelated class when LCS client identities match + +If the UE subscribes to the call/session-unrelated class, an CS-MT-LR/PS-MT-LR/EPC-MT-LR may be allowed by the MSC/MSC server, SGSN or MME if the identity of the LCS client or LCS client group supplied by the GMLC matches the identity of any LCS Client or LCS Client group contained in the UE's SLPP and any other GMLC restrictions associated with this LCS Client identity in the SLPP are also met. + +If the LCS client is correctly matched in this way and any GMLC restrictions are satisfied, the CS-MT-LR/PS-MT-LR/EPC-MT-LR shall be allowed if the UE user subscribes to either location without notification or location with notification. If the UE user subscribes to location with notification and privacy verification, the CS-MT-LR/PS-MT-LR/EPC-MT-LR shall be allowed following notification to the UE if the UE user either returns a response indicating that location is allowed or returns no response but subscribes to location in the absence of a response. In all other cases, the CS-MT-LR/PS-MT-LR/EPC-MT-LR shall be restricted. + +##### 9.5.3.3.2 Call/session-unrelated class when LCS client identities do not match + +If the UE subscribes to the call/session-unrelated class, an CS-MT-LR/PS-MT-LR/EPC-MT-LR from an LCS client that is not contained in the UE's SLPP shall be allowed or restricted according to the following conditions. For any non-matched LCS client, the CS-MT-LR/PS-MT-LR/EPC-MT-LR shall be allowed if the UE user subscribes to location with notification. If the UE user subscribes to location with notification and privacy verification, the CS-MT-LR/PS-MT-LR/EPC-MT-LR shall be allowed following notification to the UE if the UE user either returns a response indicating that location is allowed or returns no response but subscribes to location in the absence of a response. In all other cases, the CS-MT-LR/PS-MT-LR/EPC-MT-LR shall be restricted. + +#### 9.5.3.4 PLMN operator class + +When the user of the UE subscribes to the " PLMN operator Class" the CS-MT-LR/PS-MT-LR or NI-LR/PS-NI-LR positioning is allowed in the following cases: + +Allow positioning by specific types of client within or associated with the VPLMN, with the following types of client identified: + +- \* clients providing a location related broadcast service; +- \* O&M client in the HPLMN (when the UE is currently being served by the HPLMN); +- \* O&M client in the VPLMN; +- \* clients recording anonymous location information without any UE identifier; +- \* clients enhancing or supporting any supplementary service, IN service, bearer service or teleservice subscribed to by the target UE subscriber. + +If the UE subscribes to the PLMN class, an NI-LR/PS-NI-LR or CS-MT-LR/PS-MT-LR shall be allowed if the client within the VPLMN, for an NI-LR/PS-NI-LR, or the client identified by the GMLC, for an CS-MT-LR/PS-MT-LR, either matches a generic type of client contained in the UE's SLPP or is otherwise authorized by local regulatory requirements to locate the UE. If H-GMLC/PPR knows that the serving node supports LCS capability set 4 or later, then H-GMLC/PPR will send the indicators for call/session unrelated class, which indicates 'location allowed without + +notification'. If H-GMLC/PPR is notified that the serving node does not support the LCS capability set 4 or later, then it will not send any indicator. + +#### 9.5.3.5 Service type checking + +If the SLPP contains service types, a CS-MT-LR/PS-MT-LR may be allowed if the service type supplied by the LCS client matches the identity of any service type contained in the UE's SLPP and any other GMLC restrictions associated with this service type in the SLPP are also met. + +If the service type is correctly matched in this way and any GMLC restrictions are satisfied, the CS-MT-LR/PS-MT-LR shall be allowed if the UE user subscribes to either location without notification or location with notification. If the UE user subscribes to location with notification and privacy verification, the CS-MT-LR/PS-MT-LR shall be allowed following notification to the UE if the UE user either returns a response indicating that location is allowed or returns no response but subscribes to location in the absence of a response. In all other cases, the CS-MT-LR/PS-MT-LR shall be restricted. + +#### 9.5.3.6 Matching of LCS client identities + +In evaluating privacy where any address "A" associated with the LCS client (e.g. LCS client ID or GMLC address) needs to be compared with a corresponding address "B" in the target UE's SLPP, a match shall be determined if a match is found for each of the following components of each address: + +- a) numbering plan; +- b) nature of address indicator; +- c) corresponding address digits for all digits in "B" (the digits or initial digits in "A" must match all the digits in "B", but "A" may contain additional digits beyond those in "B"). + +All addresses shall be transferred to the MSC/VLR, MSC server or SGSN in international format, except for the called party number received from the GMLC during a Call-Related CS MT-LR when the LCS client was reached via IN or abbreviated number routing (e.g. toll-free number or emergency call routing). In these cases it is up to the GMLC to use the valid national specific number of the visited country. + +In evaluating privacy where an APN-NI associated with the LCS client notified by the GMLC needs to be compared with a corresponding APN-NI that is used to set up the associated PDP context, a match shall be determined if a match is found for each component of APN-NI. + +### 9.5.4 Indicator of privacy check related action + +When the client type indicates value added service and the serving node supports LCS capability set 4 or later, H-GMLC/PPR shall select indicators for privacy check related action and the indicators shall be included in the Provide\_Subscriber\_Location request towards the serving node. The indication is sent to the serving node directly from the H-GMLC or via V-GMLC. There shall be an indicator for the call/session unrelated. For GSM and UMTS there shall be an optional indicator for the call/session related and it shall be sent only if call/session related identity, i.e. the number dialled by UE or APN-NI, is sent to the serving node. For EPS, there shall be an optional indicator for the session related and it shall be sent only if session related identity, i.e. APN-NI, is sent to the serving node. + +The possible values of the indicator of privacy check related action for call/session unrelated case shall be: + +- Location allowed without notification +- Location allowed with notification +- Location with notification and privacy verification; location allowed if no response +- Location with notification and privacy verification; location restricted if no response +- Location not allowed (only applicable when the indicator for call/session related case is sent, or the POI is included in the provide subscriber location request) + +The possible values of the indicator of privacy check related action for call/session related case shall be: + +- Location allowed without notification + +- Location allowed with notification +- Location with notification and privacy verification; location allowed if no response +- Location with notification and privacy verification; location restricted if no response + +If both indicators are sent but indicating different actions and the call/session related criteria met in the serving node then an action according to the indicator with the looser action according to the definition in Annex A shall be chosen as shown in Annex A.3. + +If the UE subscribes service types, then the result of the service type checking may be included in any of the privacy check indicators, as it is described in annex A.3. + +If the UE subscribes either to PLMN class or to the universal class, H-GMLC/PPR sends the indicator for call/session unrelated class with the value of "Location allowed without notification". + +## 9.6 Mobile Originating Location + +An UE may subscribe to any of the following classes of mobile originating location: + +- a) Basic Self Location; +- b) Autonomous Self Location; +- c) Transfer to Third Party. + +An MO-LR shall be allowed by the serving node (VMSC/MSC Server/SGSN/MME) if the type of request is supported by the appropriate subscription according to the following table. + +**Table 9.3: Required UE Subscription Options for MO-LR Requests** + +| Type of MO-LR Request | Required UE Subscription | +|------------------------------------------------------------|--------------------------| +| UE requests own location | Basic Self Location | +| UE requests location assistance data | Autonomous Self Location | +| UE requests transfer of own location to another LCS Client | Transfer to Third Party | + +## 9.7 CM Procedures + +### 9.7.1 Location request for a mobile in idle-mode + +When a request for location information is received at the serving node the LCS-layer shall order paging of the UE subscriber. In case of first unsuccessful paging, normal paging procedures should apply. After successful paging the LCS-layer shall invoke the location preparation procedure. + +### 9.7.2 Location request for a mobile in dedicated-mode + +When a request for location information is received at the serving node, if the UE is already busy on CM level, the LCS-layer shall attempt to establish a parallel transaction to the existing one. If successful, the LCS-layer shall invoke the location preparation procedure. + +## 9.8 Interworking with the IMS + +### 9.8.1 Standard Location Request using a SIP-URI + +An external LCS Client shall use the same interface to the LCS Server regardless of the target UE's identity. + +If a location request from an external LCS client uses a SIP-URI as the target UE's identity, the requesting GMLC shall invoke a LIMS-IWF (Location IMS Interworking Function) to route the request to the user's home network. This routing mechanism may use standard technologies like pre-configuration of destination addresses or DNS lookups to + +determine the address of a LIMS-IWF in the home network of the user. The interface between two LIMS-IWF in different networks shall be Lr. + +If the LIMS-IWF in the home network is not co-located with the home GMLC, it shall use the same interface towards the home GMLC as the requesting GMLC, i.e. the Lr interface. The LIMS-IWF in the home network has to determine the HSS serving the user. This may be done e.g. by a Dh SLF query or the HSS address is known to the LIMS-IWF through configuration. The LIMS-IWF retrieves the MSISDN from the HSS through Sh Pull and use MAP Send Routing Info for LCS to get the home GMLC IP address from the HLR/HSS. Afterwards the LIMS-IWF in the home network can forward the LCS service request (including the target UE's MSISDN) on the Lr interface to the home GMLC. + +The following figure shows the principle call flow when a GMLC receives a location request where the target UE's identity is an IMS Public User Identity (SIP-URI). + +![Sequence diagram illustrating the MT-LR procedure for IMS Public User Identities. The diagram shows the interaction between an LCS Client, a Requesting GMLC, a Requesting LIMS-IWF, a Home LIMS-IWF, an HLR/HSS, a Home GMLC, and a Visited GMLC. The process involves routing the location request through various network elements, including SLF and Sh Pull operations to resolve the user's identity and location.](97b3ed12d7f6c65cf3f7187326728409_img.jpg) + +``` + +sequenceDiagram + participant LCS Client + participant GMLC as GMLC (Requesting) + participant LIMS-IWF-R as LIMS-IWF (Requesting) + participant LIMS-IWF-H as LIMS-IWF (Home) + participant HLR/HSS + participant SLF + participant GMLC-H as GMLC (Home) + participant GMLC-V as GMLC (Visited) + + Note right of HLR/HSS: SLF + LCS Client->>GMLC: 1. LCS Service Request + GMLC->>LIMS-IWF-R: 2. LCS Service Request + LIMS-IWF-R->>LIMS-IWF-H: 3. LCS Service Request + LIMS-IWF-H->>SLF: 4. Dh SLF Query + SLF-->>LIMS-IWF-H: 5. Dh SLF Resp + LIMS-IWF-H->>HLR/HSS: 6. Sh PULL (SIP-URI) + HLR/HSS-->>LIMS-IWF-H: 7. Sh PULL Resp (MSISDN) + LIMS-IWF-H->>HLR/HSS: 8. Send Routing Info for LCS (MSISDN) + HLR/HSS-->>LIMS-IWF-H: 9. Send Routing Info for LCS Ack + LIMS-IWF-H->>GMLC-H: 10. LCS Service Request + GMLC-H->>GMLC-H: 11. Privacy check + GMLC-H->>HLR/HSS: 12. Send Routing Info for LCS (MSISDN) + HLR/HSS-->>GMLC-H: 13. Send Routing Info for LCS Ack + GMLC-H->>GMLC-V: 14. LCS Service Request + GMLC-V->>GMLC-V: 15. MT-LR procedures for PS Domain + GMLC-V-->>GMLC-H: 16. LCS Service Response + GMLC-H->>GMLC-H: 17. Privacy check + GMLC-H-->>LIMS-IWF-H: 18. LCS Service Response + LIMS-IWF-H-->>LIMS-IWF-R: 19. LCS Service Response + LIMS-IWF-R-->>GMLC: 20. LCS Service Response + GMLC-->>LCS Client: 21. LCS Service Response + +``` + +Sequence diagram illustrating the MT-LR procedure for IMS Public User Identities. The diagram shows the interaction between an LCS Client, a Requesting GMLC, a Requesting LIMS-IWF, a Home LIMS-IWF, an HLR/HSS, a Home GMLC, and a Visited GMLC. The process involves routing the location request through various network elements, including SLF and Sh Pull operations to resolve the user's identity and location. + +**Figure 9.9: MT-LR procedure for IMS Public User Identities** + +1. An external LCS Client requests the current location of a target UE from a R-GMLC using the Public User Identity (SIP-URI) associated with the target UE. + +2. The R-GMLC selects a LIMS-IWF in the requesting network. The LIMS-IWF address may be pre-configured or DNS is used for this purpose. The R-GMLC forwards the LCS service request to the requested LIMS-IWF via Lr interface. +3. The LIMS-IWF in the requesting network determines the LIMS-IWF address in the home network. This may be done by using a pre-configured address or by DNS. The requesting LIMS-IWF forwards the LCS service request to the home LIMS-IWF via Lr interface. +4. The home LIMS-IWF queries the SLF via Dh interface to get the HSS address (using the Dh interface to retrieve the HSS address is an option). +5. The home LIMS-IWF retrieves the HSS address from the SLF via Dh SLF Response. +6. The home LIMS-IWF queries the HSS via Sh PULL (including the SIP-URI) to get the user's MSISDN. +7. The home LIMS-IWF retrieves the user's MSISDN from the HSS via Sh PULL Response. +8. The LIMS-IWF uses MAP Send Routing Info for LCS to get the H-GMLC address from the HLR/HSS. +9. The LIMS-IWF retrieves the H-GMLC address from the HLR/HSS. +10. The LCS service request is forwarded to the H-GMLC through Lr interface. +11. The H-GMLC performs the privacy check. +12. The H-GMLC queries the HLR/HSS using MAP Send Routing Info for LCS to get the V-GMLC address. +13. The H-GMLC retrieves the V-GMLC address from the HLR/HSS. +14. The H-GMLC forwards the LCS service request to the V-GMLC. +15. The standard MT-LR procedure is performed. +16. The LCS service response is sent from the V-GMLC to the H-GMLC. +17. The H-GMLC performs the privacy check. +18. The LCS service response is sent from the H-GMLC to home LIMS-IWF. +19. The LCS service response is sent from the home LIMS-IWF to the requesting LIMS-IWF. +20. The LCS service response is sent from the requesting LIMS-IWF to the R-GMLC. +21. The LCS service response is sent from the R-GMLC to the external LCS Client. + +### 9.8.2 Standard Location Request using a TEL-URL + +If a location request from an external LCS client uses a TEL-URL as the target UE's identity, the requesting GMLC shall convert the TEL-URL into a MSISDN, use this MSISDN in the location request as the target UE's address and continue with the MT-LR procedure for the PS domain. + +### 9.8.3 Mobile Originated Location Requests in the IMS + +Mobile Originated Location Requests will not specifically require IMS interworking and therefore are not covered within this specification. + +### 9.8.4 IMS Emergency Location Procedure + +A common procedure to support location and PSAP/Emergency Centre selection for any type of access network is shown in TS 23.167 [36a] "Retrieving Location information for Emergency Session". The procedure may be used dependent on the access type and the requirements of the applicable regulatory authority. + +# 10 Information storage + +This clause describes information storage structures that are mandatory (M), conditional (C) or optional (O) for LCS, and the recovery and restoration procedures needed to maintain service if inconsistencies in databases occur and for lost or invalid database information. Information storage in RAN network elements is specified in UTRAN Stage 2 (TS 25.305 [1]) and GERAN Stage 2 (TS 43.059 [16]) specifications. + +## 10.1 HLR and HSS + +The HLR/HSS holds LCS data for both UE subscribers and LMUs. If the privacy profile data for UE subscribers are stored in H-GMLC/PPR, HLR/HSS needs to store the corresponding pseudo-external identities and MO-LR related subscription data shown in Table 10.4 and 10.5. The pseudo-external identities are stored in the privacy exception list shown in Table 10.2. The details of the pseudo-external identity are described in Annex C. + +### 10.1.1 LCS Data in the HLR/HSS for an UE Subscriber + +The IMSI is the primary key for LCS UE subscription data in the HLR/HSS. This subscription data may be stored in a Multiple Subscriber Profile (MSP), with the HLR/HSS able to hold a number of MSPs per IMSI. + +For GSM and UMTS, the LCS UE subscription data includes a privacy exception list containing the privacy classes for which location of the target UE is permitted. Each privacy class is treated as a distinct supplementary service with its own supplementary service code. The following logical states are applicable to each privacy class (refer to TS 23.011 [22] for an explanation of the notation). + +**Table 10.1: Logical States for each LCS Privacy Class** + +| 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) | + +For each LCS privacy class, the HLR/HSS shall store the logical state of the class on a per-subscriber (or per subscriber MSP) basis. In addition, the permanent data indicated below shall be stored on a per subscriber (or per subscriber MSP) basis when the logical provisioning state of the associated LCS privacy class is "provisioned". For the meaning of each LCS privacy class, refer to clause 9 and to TS 22.071 [4]. + +Moreover a list of allowed service types may be stored. The meaning of service types is defined in TS 22.071 [4]. + +**Table 10.2: LCS data stored in the HLR privacy exception list for an UE Subscriber +(or UE Subscriber MSP)** + +| LCS Privacy Class | Status | Additional HLR Data when Class is provisioned | +|------------------------------|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Universal Class | - | No additional data | +| Call/session Related Class | M | Indication of one of the following mutually exclusive options for any LCS client not in the external LCS client list:
  • - Location not allowed
  • - Location allowed without notification (default case)
  • - Location allowed with notification
  • - Location with notification and privacy verification; location allowed if no response
  • - Location with notification and privacy verification; location restricted if no response
| +| | O | External LCS client list: a list of zero or more LCS clients, with the following data stored for each LCS client in the list:
  • - International E.164 address identifying a single LCS client or a single group of LCS clients that are permitted to locate this target UE
  • - Restriction on the GMLC. If no value is stored for this data, there is no restriction on GMLC and any GMLC is allowed to request location information for the UE. Possible values are:
    • - Identified GMLCs only
    • - Any GMLC in the home country
| +| | C |
  • - Indication of one of the following mutually exclusive options:
    • - Location allowed without notification (default case)
    • - Location allowed with notification
    • - Location with notification and privacy verification; location allowed if no response
    • - Location with notification and privacy verification; location restricted if no response
| +| | O |
  • - Restriction on the GMLC. If no value is stored for this data there is no restriction on GMLC and any GMLC is allowed to request location information for the UE. Possible values are:
    • - Identified GMLCs only
    • - Any GMLC in the home country
| +| | C |
  • - Indication of one of the following mutually exclusive options:
    • - Location allowed without notification (default case)
    • - Location allowed with notification
    • - Location with notification and privacy verification; location allowed if no response
    • - Location with notification and privacy verification; location restricted if no response
| +| Call/session Unrelated Class | M | Indication of one of the following mutually exclusive options for any LCS client not in the external LCS client list:
  • - Location not allowed (default case)
  • - Location allowed with notification
  • - Location with notification and privacy verification; location allowed if no response
  • - Location with notification and privacy verification; location restricted if no response
| +| | O | External LCS client list: a list of zero or more LCS clients, with the following data stored for each LCS client in the list:
  • - International E.164 address identifying a single LCS client or a single group of LCS clients that are permitted to locate this target UE
  • - Restriction on the GMLC. If no value is stored for this data there is no restriction on GMLC and any GMLC is allowed to request location information for the UE. Possible values are:
    • - Identified GMLCs only
    • - Any GMLC in the home country
| +| | C |
  • - Restriction on the GMLC. If no value is stored for this data there is no restriction on GMLC and any GMLC is allowed to request location information for the UE. Possible values are:
    • - Identified GMLCs only
    • - Any GMLC in the home country
| +| | O |
  • - Restriction on the GMLC. If no value is stored for this data there is no restriction on GMLC and any GMLC is allowed to request location information for the UE. Possible values are:
    • - Identified GMLCs only
    • - Any GMLC in the home country
| +| | C |
  • - Indication of one of the following mutually exclusive options:
    • - Location allowed without notification (default case)
    • - Location allowed with notification
    • - Location with notification and privacy verification; location allowed if no response
    • - Location with notification and privacy verification; location restricted if no response
| +| PLMN Operator Class | O | LCS client list: a list of one or more generic classes of LCS client that are allowed to locate the particular UE. The following classes are distinguished:
  • - LCS client broadcasting location related information
  • - O&M LCS client in the HPLMN
  • - O&M LCS client in the VPLMN
  • - LCS client recording anonymous location information
  • - LCS Client supporting a bearer service, teleservice or supplementary service to the target UE
| + +**Table 10.3: LCS Service types stored in the HLR/HSS per UE subscriber** + +| Service type indication | Status | Additional HLR data when the indication is stored | +|--------------------------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service Types | O

O

C | Service types list: a list of one or more service types for which the LCS client is allowed to locate the particular UE. The possible service types are defined in TS 22.071 [4]. The following data may be present for each service type in the list:
  • - Restriction on the GMLC. If no value is stored for this data, there is no restriction on GMLC and any GMLC is allowed to request location information for the UE. Possible values are:
  • - Identified GMLCs only
  • - Any GMLC in the home country
  • - Indication of one of the following mutually exclusive options:
    • - Location allowed without notification (default case)
    • - Location allowed with notification
    • - Location with notification and privacy verification; location allowed if no response
    • - Location with notification and privacy verification; location restricted if no response
| + +In case that UE's privacy profile is stored and is checked in the GMLC (H-GMLC) or in the PPR, pseudo-external identities may be set in the external LCS client list of the HLR privacy exception list shown in Table 10.2. The pseudo-external identity is not the identity of real external LCS client but the identity which is used for notifying SGSN/MSC of the location request class (call/session related or non-call/session related) and the required type of indication for each class. Operator allocates E.164 addresses for the pseudo-external identities. + +Fourteen pseudo-external identities are needed to be defined. The pseudo-external identities are summarized in the Table C.1. The pseudo-external identities are registered in SLPP of each UE in advance. + +LCS UE subscription data may include a mobile originating list containing the LCS mobile originating classes that an UE is permitted to request. Each LCS mobile originating class is treated as a distinct supplementary service with its own supplementary service code. The following logical states are applicable to each mobile originating class (refer to TS 23.011 [22] for an explanation of the notation). + +**Table 10.4: Logical States for each Mobile Originating LCS Class** + +| 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) | + +For each LCS Mobile Originating class, the HLR/HSS shall store the logical state of the class on a per-subscriber (or per subscriber MSP) basis. In this version of LCS, there is no additional permanent data in the HLR. The table below shows the defined mobile originating classes. For the meaning of each LCS mobile originating class, refer to clause 8 and to TS 22.071 [4]. + +**Table 10.5: Data stored in the HLR for the LCS Mobile Originating List for an UE (or UE Subscriber MSP)** + +| LCS Mobile Originating Class | Status | Additional HLR Data when Class is provisioned | +|-------------------------------------|---------------|------------------------------------------------------| +| Basic Self Location | - | No additional data | +| Autonomous Self Location | - | No additional data | +| Transfer to Third Party | - | No additional data | + +In addition to the privacy exception list, the following other data items may be stored in the UE subscription profile in the HLR to support LCS. + +**Table 10.6a: Temporary LCS data in the HLR** + +| Other Data in the HLR | Status | Description | +|-----------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| GMLC List | O | List of one or more E.164 addresses of the GMLCs from which a location request for an MT-LR is allowed, The addresses are only relevant to an LCS client that is restricted (in the UE privacy exception list) to making call/session related or call/session unrelated location requests. | + +To support broadcast of assistance data for E-UTRAN access where assistance data is ciphered, the following data items may be stored in the HSS for a UE subscriber. + +**Table 10.6b: Data stored in the HSS to support broadcast of ciphered assistance data for E-UTRAN access** + +| Data in the HSS | Status | Description | +|-------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| List of Assistance Data Types | O | A list of one or more types of location assistance data for which ciphering keys should be provided to the UE if requested by the UE when the assistance data is broadcast using ciphering. | + +## 10.2 VLR/SGSN + +The VLR/SGSN contains the same LCS permanent data for each registered UE subscriber, as does the HLR/HSS. This data is downloaded to the VLR/SGSN as part of the location update procedure between the VLR/SGSN and HLR/HSS for an UE subscriber. + +## 10.2a MME + +The MME contains the same LCS permanent data for each registered UE subscriber, as does the HSS. This data is downloaded to the MME as part of the Attach and Tracking Area Update procedures between the MME and HSS for a UE subscriber. + +## 10.3 GMLC + +### 10.3.1 LCS Data in the GMLC for a LCS Client + +The GMLC holds data for a set of external LCS clients that may make call related or non-call related MT-LR requests to this GMLC. The permanent data administered for each LCS client is as follows. + +**Table10.7: GMLC Permanent Data for a LCS Client** + +| LCS Client data in GMLC | Status | Description | +|--------------------------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| LCS Client Type | M | Identifies the type LCS client from among the following:
  • - Emergency Services
  • - Value Added Services
  • - PLMN Operator Services
  • - Lawful Intercept Services
| +| External identity | O | A list of one or more identifiers used to identify an external LCS client. The identity may be used when making an MT-LR and/or MO-LR. The format of the identity is an international E.164 address [35a]. Each external identity shall be associated with a logical client name. | +| Authentication data | M | Data employed to authenticate the identity of an LCS client – details are outside the scope of the present document | +| Call/session related identity | O | A list of one or more international E.164 addresses [35a], which are used to make calls by mobile subscribers, or APN-NIs (see NOTE) to identify the client for a call related MT-LR
In case the LCS client was reached via IN or abbreviated number routing (e.g. toll free number or emergency call routing), the E.164 number(s) stored in the GMLC shall be the number(s) that the UE has to dial to reach the LCS Client. In these cases the E.164 number is not to be in international format. The country in which the national specific number(s) is (are) applicable is (are) also stored (or implied) in this case.
Each call related identity may be associated with a specific external identity. Each call/session-related identity shall be associated with a logical client name. | +| Internal identity | O | Identifies the type PLMN operator services and the following classes are distinguished:
  • - LCS client broadcasting location related information
  • - O&M LCS client in the HPLMN
  • - O&M LCS client in the VPLMN
  • - LCS client recording anonymous location information
  • - LCS Client supporting a bearer service, teleservice or supplementary service to the target UE
This identity is applicable only to PLMN Operator Services. | +| Client name | O | An address string which is associated with LCS client's external identity (i.e., E.164 address). See note 2. | +| Client name type | O | Indication what is the type of the LCS client name. The type of the LCS client name can be one of the following:
  • - Logical name
  • - MSISDN
  • - E-mail address (RFC 2396 [33])
  • - URL (RFC 2396 [33])
  • - SIP URL (RFC 3261 [34])
  • - IMS public identity (TS 23.228 [35])
| +| Override capability | O | Indication of whether the LCS client possesses the override capability (not applicable to a value added and PLMN operator service) | +| Authorized UE List | O | A list of MSISDNs or groups of MSISDN for which the LCS client may issue a non-call related MT-LR. Separate lists of MSISDNs and groups of MSISDN may be associated with each distinct external or non-call related client identity. | + +| | | | +|---------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Priority | M | The priority of the LCS client – to be treated as either the default priority when priority is not negotiated between the LCS server and client or the highest allowed priority when priority is negotiated | +| QoS parameters | M | The default QoS requirements for the LCS client, comprising:
  • - Accuracy
  • - Response time
  • - LCS QoS Class
Separate default QoS parameters may be maintained for each distinct LCS client identity (external, non-call related, call related) | +| Service Coverage | O | A list of E.164 country codes for geographic areas [35a] where the LCS client offers its location services. | +| Allowed LCS Request Types | M | Indicates which of the following are allowed:
  • - Non-call related CS-MT-LR/PS-MT-LR/EPC-MT-LR
  • - Call/session related CS-MT-LR/PS-MT-LR/EPC-MT-LR
  • - Specification or negotiation of priority
  • - Specification or negotiation of QoS parameters
  • - Specification or negotiation of Service Coverage parameter
  • - Request of current location
  • - Request of current or last known location
| +| Local Co-ordinate System | O | Definition of the co-ordinate system(s) in which a location estimate shall be provided – details are outside the scope of the present document | +| Access Barring List(s) | O | List(s) of MSISDNs or groups of MSISDN for which a location request is barred | +| Service Identities | O | List of service identities allowed for the LCS client. | +| Maximum Target UE Number | O | The maximum number of the Target UEs in one LCS request. For a specific LCS Client, this parameter may have different values for different service identities. | + +NOTE 1: The LCS Client is identified with E.164 number or APN-NI. APN-NI is specified in TS 23.003 [17]. + +NOTE 2: The LCS Client name should not contain two equal signs, because those characters are used to separate LCS client name from Requestor ID when GMLC includes them into the same field. + +### 10.3.2 LCS Data in the GMLC/PPR for a UE Subscriber + +The GMLC (H-GMLC) or PPR may store LCS UE subscription data. This clause describes Rel-5 based privacy profile data stored in GMLC/PPR. If the home network operator uses Rel-5 compatible privacy profile data, the profiles shown in this clause may be stored in GMLC/PPR. If the home network operator supports Rel-6 or later compatible privacy profile data, the profiles stored in the GMLC/PPR may be related to different geographic areas, i.e. subscribers may have different privacy profiles depending on subscribers' locations. + +The IMSI or MSISDN is the primary key for LCS UE subscription data in the GMLC/PPR. This subscription data may be stored in a Multiple Subscriber Profile (MSP), with the GMLC/PPR able to hold a number of MSPs per IMSI. + +LCS UE subscription data includes a privacy exception list containing the privacy classes for which location of the target UE is permitted. Each privacy class is treated as a distinct supplementary service with its own supplementary service code. The following logical states are applicable to each privacy class (refer to TS 23.011 [22] for an explanation of the notation). + +**Table 10.9: Logical States for each LCS Privacy Class** + +| 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) | + +For each LCS privacy class, the GMLC/PPR shall store the logical state of the class on a per-subscriber (or per subscriber MSP) basis. In addition, the permanent data indicated in Table 10.10 may be stored on a per subscriber (or per subscriber MSP) basis when the logical provisioning state of the associated LCS privacy class is "provisioned". For the meaning of each LCS privacy class, refer to clause 9 and to TS 22.071 [4]. + +Moreover a list of allowed service types may be stored. The meaning of service types is defined in TS 22.071 [4]. The numbers assigned to service types are defined in Annex G. + +**Table 10.10: LCS data stored in the GMLC/PPR privacy exception list for an UE Subscriber (or UE Subscriber MSP)** + +| | | | +|---------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service Types | O | Service types list: a list of one or more service types for which the LCS client is allowed to locate the particular UE. The possible service types are defined in TS 22.071 [4] and the assigned numbers are shown in Annex G. The following data may be present for each service type in the list: | +| | O |
  • - Restriction on the GMLC. If no value is stored for this data, there is no restriction on GMLC and any GMLC is allowed to request location information for the UE. Possible values are:
  • - Identified GMLCs only
  • - Any GMLC in the home country
| +| | C |
  • - Indication of one of the following mutually exclusive options:
  • - Location allowed without notification (default case)
  • - Location allowed with notification
  • - Location with notification and privacy verification; location allowed if no response
  • - Location with notification and privacy verification; location restricted if no response
| + +**Table 10.11: LCS Service types stored in the GMLC per UE subscriber** + +| Service type indication | Status | Additional HLR data when the indication is stored | +|--------------------------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Service Types | O |

Indication of one of the following mutually exclusive options for any service type not in the service type list:

  • - Location not allowed (default case)
  • - Location allowed with notification
  • - Location with notification and privacy verification; location allowed if no response
  • - Location with notification and privacy verification; location restricted if no response

Service types list: a list of one or more service types for which the LCS client is allowed to locate the particular UE. The possible service types are defined in TS 22.071 [4] and the assigned numbers are shown in Annex G.

  • - Restriction on the GMLC. If no value is stored for this data, there is no restriction on GMLC and any GMLC is allowed to request location information for the UE. Possible values are:
    • - Identified GMLCs only
    • - Any GMLC in the home country
  • - Indication of one of the following mutually exclusive options:
    • - Location allowed without notification (default case)
    • - Location allowed with notification
    • - Location with notification and privacy verification; location allowed if no response

Location with notification and privacy verification; location restricted if no response

| + +In case that UE's privacy profile is stored and is checked in the GMLC (H-GMLC) or in the PPR, the GMLC/PPR shall store the same pseudo-external identity table with HLR, which is shown in Annex C. + +GMLC (H-GMLC) or PPR may store codeword handling information and a list of codewords given by the UE subscriber in order not to get the location request rejected. + +**Table 10.12a: Codeword handling information stored in the GMLC** + +| Other Data in the GMLC | Status | Description | +|-------------------------------|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Codeword handling information | O |

Indication of one of the following mutually exclusive options for codeword:

  • - codeword shall be checked in network.
  • - codeword shall be sent to UE
| + +**Table 10.12b: LCS data stored in the GMLC for a UE Subscriber** + +| LCS Privacy profile | Status | Additional GMLC data when profile is provisioned | +|----------------------------|---------------|---------------------------------------------------------| +| Codeword | O | A list of codeword. | + +The GMLC (H-GMLC) or the PPR may store additional privacy information in order protect UE users privacy. The details of the additional privacy check are defined by each network operator and are outside the scope of this specification. + +## 10.4 Recovery and Restoration Procedures + +The LCS recovery and restoration procedures allow temporary data to be recovered or reinitialized following loss or corruption of data, such that normal LCS service is rapidly restored and inconsistency between the data held by different LCS network elements is removed. For a full description, refer to TS 23.007 [23]. + +## 10.5 Interworking between network nodes in different releases + +This clause describes possible scenarios for interworking between network nodes in different releases. It is noted that LCS is only supported in A-mode and Iu-mode in the CS domain in Rel-99. LCS is supported in A-mode and Iu-mode in UTRAN CS and PS domains, but not in Gb-mode, in Rel-4. LCS is supported in A/Gb mode and Iu mode in CS and PS domains for UTRAN and GERAN in Rel-5, Rel-6, Rel-7 and Rel-8. LCS is supported in A/Gb mode and Iu mode in CS and PS domains for UTRAN and GERAN and in the PS domain for E-UTRAN in Rel-9 onwards. + +The concept of LCS capability set is introduced in Rel-4, so it does not appear in the specifications for R98 and R99 LCS. + +### 10.5.1 LCS capability set + +The following LCS capabilities are identified in the current version of this specification. The HLR/HSS is notified the LCS capability of the serving node by an indication, which indicates all the LCS the serving node supports, from the serving node during location update procedure. + +- LCS capability set 1: R98 and R99 LCS (pre-Rel'4 LCS) +- LCS capability set 2: Rel'4 LCS +- LCS capability set 3: Rel'5 LCS +- LCS capability set 4: Rel'6 LCS +- LCS capability set 5: Rel'7 or later LCS + +NOTE 1: the concept of LCS capability set is introduced in Rel4 so that R98 and R99 serving nodes do not notify HLR/HSS this parameter. Therefore, even if this parameter is absent the serving node may support at most LCS capability set 1. + +NOTE 2: For E-UTRAN access, LCS capability sets 1 through 4 are not applicable. An MME that does not signal an LCS capability to the HSS shall be assumed to provide no LCS support. + +The serving node, which notified the HLR/HSS that it supports LCS capability set 2, shall be able to handle the extended LCS Client list and LCS Client List for call-related class from the HLR/HSS. + +The serving node, which notified the HLR/HSS that it supports LCS capability set 3, shall support the following capabilities: + +- capability to perform the service type privacy check. +- capability to send the codeword to target UE for notification/verification. +- capability to send the requestor ID to target UE for notification/verification. + +The serving node, which notified the HLR/HSS that it supports LCS capability set 4, shall support the following capability: + +- capability to perform the privacy related action (i.e. checking the on-going call/session and/or notification/verification procedures) which is requested by H-GMLC. + +The serving node, which notified the HLR/HSS that it supports LCS capability set 5, shall support the following capability: + +- capability to perform the privacy related action (i.e. checking the on-going call/session and/or notification/verification procedures) for notification based on current location which is requested by H-GMLC. + +### 10.5.2 Interworking between pre Rel-4 serving node and Rel-4 or later HLR/HSS + +The serving node that supports only pre-Rel'4 LCS cannot handle the extended privacy control for call-related/call-unrelated class of the Rel'4 and later LCS. That is, the serving node cannot provide the extended call-related/call-unrelated class service to the user who subscribes to the Rel'4 LCS. Therefore HLR does not send the LCS subscriber data on call-related/call-unrelated class for users who subscribe to the call-related class of Rel'4 LCS to the serving node that supports only pre-Rel'4 LCS. + +### 10.5.3 Interworking between pre Rel-5 serving node and Rel-5 or later HLR/HSS + +If the HLR/HSS is notified that the LCS capability set 3 is not supported by the serving node, it may decide not to send the LCS subscriber data to the serving node, in order to protect user privacy. + +In addition, if the HLR/HSS is notified that the serving node does not support the LCS capability set 2, the procedures described in 10.5.2 also shall be applied. + +### 10.5.4 Interworking between pre Rel-6 network nodes and Rel-6 or later HLR/HSS + +In addition to the procedures in this clause, if the HLR/HSS is notified that the serving node does not support the LCS capability set 2 and/or set 3, the procedures described in 10.5.3 shall be also taken into consideration. + +#### 10.5.4.1 Rel-6 or later HLR/HSS with pre Rel-6 serving node + +The Rel-6 or later HLR/HSS notifies the H-GMLC about the all LCS capability set supported by the serving node. + +In accordance with the notified LCS capability of the serving node and the privacy profile of the target UE, the H-GMLC decides whether the location estimation process can be continued or not. + +In order to request the privacy related action (i.e. checking the on-going call/session and/or notification/verification procedures) to the pre Rel-6 serving node, H-GMLC may send the Provide Subscriber Location request message to the serving node with the pseudo-external identity. The detail of the pseudo-external identity is described in Annex C. + +## 10.6 LIMS-IWF + +As the LIMS-IWF is a simple interworking function that provides routing of LCS service requests and responses based on the target UE's SIP-URI and mapping of SIP-URI to MSISDN it must not store user or LCS Client specific data during or after a location request procedure. + +# --- 11 Operational Aspects + +## 11.1 Charging + +Charging Information collected by the PLMN serving the LCS Client. + +The following charging information shall be collected by the PLMN serving the LCS Client: + +- type and identity of the LCS Client; + +- identity of the target UE; +- results (e.g. success/failure, method used if known, response time, accuracy) - to be repeated for each instance of positioning for a deferred location request; +- identity of the visited PLMN; +- LCS request type (i.e. LDR or LIR); +- requested Quality of Service information; +- state; +- type of event (applicable to LDR requests only); +- time stamp; +- type of co-ordinate system used. + +## 11.2 Charging Information Collected by the Visited PLMN + +The following charging information shall be collected by the visited PLMN: + +- date and time; +- type and identity of the LCS Client (if known); +- identity of the target UE; +- location of the target UE (e.g., MSC, MSC Server, SGSN, MME, tracking area ID, location area ID, cell ID, location co-ordinates); +- which location services were requested; +- requested Quality of Service information; +- results (e.g. success/failure, positioning method used, response time, accuracy) - to be repeated for each instance of positioning for a batch location request; +- identity of the GMLC or PLMN serving the LCS Client; +- state; +- type of event (applicable to LDR requests only). + +## --- Annex A (normative): Privacy Class selection rule in serving node + +## A.1 Interrelation among privacy settings + +There are five privacy settings and the interrelation among each privacy setting in terms of privacy strictness is shown as follows: + +**Table A.1: Privacy settings** + +| | | +|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| loose | Positioning allowed without notifying the UE user | +| ↑ | Positioning allowed with notification to the UE user | +| | Positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user or if there is no response to the notification | +| ↓ | Positioning requires notification and verification by the UE user; positioning is allowed only if granted by the UE user | +| strict | Positioning not allowed | + +## --- A.2 Privacy class selection rule for pre Rel-6 mechanism + +In pre Rel-6 network, the users privacy profile (SLPP) is stored HLR/HSS and is downloaded to the serving MSC/SGSN. If more than one privacy class are subscribed or in case Service Types and at least one privacy class are subscribed, privacy class for an MT-LR is selected by the serving MSC/SGSN according to the flow diagram shown in Fig. A-1. + +An MT-LR may be applied to more than one privacy class or to Service Types and one or more privacy classes. In this case, looser privacy setting shall be selected. The privacy settings to be compared are the results of the privacy checks for each applicable class and Service Type. + +![Figure A.1: Privacy Class selection flow diagram. The flowchart starts with 'Start' and proceeds through a series of decision diamonds to select a privacy class. The first decision is 'Universal class subscribed?'. If 'Yes', it leads to 'Universal class'. If 'No', it proceeds to 'PLMN Operator class criteria met? [Note 1]'. If 'Yes', it leads to 'PLMN Operator class subscribed?'. If 'Yes', it leads to 'PLMN Operator class'. If 'No', it leads to 'The location request is not allowed unconditionally'. If 'No' to 'PLMN Operator class criteria met?', it proceeds to 'Call Related class criteria met? [Note 2]'. If 'Yes', it leads to 'Call Related class subscribed?'. If 'Yes', it leads to 'Call Related/Call Unrelated class [Note 4]'. If 'No', it leads to 'Call Related class'. If 'No' to 'Call Related class criteria met?', it proceeds to 'Call Unrelated class criteria met? [Note 3]'. If 'Yes', it leads to 'Call Unrelated class subscribed?'. If 'Yes', it leads to 'Call Unrelated class'. If 'No', it leads to 'The location request is not allowed unconditionally'.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +``` + +graph TD + Start([Start]) --> D1{Universal class subscribed?} + D1 -- Yes --> U[Universal class] + D1 -- No --> D2{PLMN Operator class criteria met? [Note 1]} + D2 -- Yes --> D3{PLMN Operator class subscribed?} + D3 -- Yes --> P[PLMN Operator class] + D3 -- No --> L1[The location request is not allowed unconditionally] + D2 -- No --> D4{Call Related class criteria met? [Note 2]} + D4 -- Yes --> D5{Call Related class subscribed?} + D5 -- Yes --> CRU[Call Related/Call Unrelated class [Note 4]] + D5 -- No --> CR[Call Related class] + D4 -- No --> D6{Call Unrelated class criteria met? [Note 3]} + D6 -- Yes --> D7{Call Unrelated class subscribed?} + D7 -- Yes --> CU[Call Unrelated class] + D7 -- No --> L2[The location request is not allowed unconditionally] + D6 -- No --> L3[The location request is not allowed unconditionally] + +``` + +Figure A.1: Privacy Class selection flow diagram. The flowchart starts with 'Start' and proceeds through a series of decision diamonds to select a privacy class. The first decision is 'Universal class subscribed?'. If 'Yes', it leads to 'Universal class'. If 'No', it proceeds to 'PLMN Operator class criteria met? [Note 1]'. If 'Yes', it leads to 'PLMN Operator class subscribed?'. If 'Yes', it leads to 'PLMN Operator class'. If 'No', it leads to 'The location request is not allowed unconditionally'. If 'No' to 'PLMN Operator class criteria met?', it proceeds to 'Call Related class criteria met? [Note 2]'. If 'Yes', it leads to 'Call Related class subscribed?'. If 'Yes', it leads to 'Call Related/Call Unrelated class [Note 4]'. If 'No', it leads to 'Call Related class'. If 'No' to 'Call Related class criteria met?', it proceeds to 'Call Unrelated class criteria met? [Note 3]'. If 'Yes', it leads to 'Call Unrelated class subscribed?'. If 'Yes', it leads to 'Call Unrelated class'. If 'No', it leads to 'The location request is not allowed unconditionally'. + +Note 1: The client type indicates PLMN Operator service, and the client is within or associated with the VPLMN. + +Note 2: The client type indicates value added service; the UE originated call/session to the requesting LCS client is established and the address associated to the LCS client used by the UE in call/session set up matches with that contained in the location request. + +Note 3: The client type indicates value added service. + +Note 4: The looser privacy setting shall be selected. + +**Figure A.1: Privacy Class selection flow diagram** + +If the user subscribes Service Types, once that the privacy class has been selected according to figure A.1, the resulting privacy setting shall be compared with the result of Service Type privacy checking, and the looser condition shall be applied to the MT-LR, provided that the LCS client was authorized by the UE user to get location information. + +## A.3 Privacy related action selection rule for Rel-6 and later + +In Rel-6 and later, the privacy checking function is moved from MSC/SGSN to H-GMLC/PPR of the target UE. This is also applied to EPS location request, i.e. privacy checking is done at H-GMLC/PPR of the target UE. H-GMLC/PPR selects one or two indicators of privacy check related action and sends the indicators to serving MSC/SGSN/MME as shown in the clause 9.5.4. If the user subscribes Service Types, the resulting privacy setting shall be compared with the result of Service Type privacy checking, and the looser condition shall be selected. The Service Type check result may be included in any of the two privacy indicators, provided that the MT-LR is allowed for the relative privacy class. + +If the serving MSC/SGSN/MME receives the indicators from H-GMLC, the serving node selects the privacy related action according to the flow diagram shown in Fig. A-2. + +![Flowchart of privacy related action selection for the serving node.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) + +``` +graph TD; Start([Start]) --> D1{Indicator for call/session related class received?}; D1 -- YES --> D2{call/session related class criteria met? [Note 1]}; D1 -- NO --> D3{Indicator for call/session unrelated class received? [Note 2]}; D2 -- YES --> D4{Indicator for call/session unrelated class received? [Note 2]}; D2 -- NO --> D3; D4 -- YES --> D5{call/session related class is looser?}; D4 -- NO --> D3; D5 -- YES --> D4; D5 -- NO --> D3; D4 -- YES --> D6[Call/session unrelated class]; D4 -- NO --> D7[The location request is not allowed unconditionally]; D5 -- YES --> D8[Call/session related class]; D5 -- NO --> D6; +``` + +The flowchart illustrates the privacy related action selection process at the serving node. It begins with a 'Start' terminal, leading to a decision diamond: 'Indicator for call/session related class received?'. If 'YES', it proceeds to 'call/session related class criteria met? [Note 1]'. If 'NO', it proceeds to 'Indicator for call/session unrelated class received? [Note 2]'. From 'call/session related class criteria met? [Note 1]', a 'YES' leads to 'Indicator for call/session unrelated class received? [Note 2]' and a 'NO' leads to 'Indicator for call/session unrelated class received? [Note 2]'. From 'Indicator for call/session unrelated class received? [Note 2]', a 'YES' leads to 'call/session related class is looser?' and a 'NO' leads to 'The location request is not allowed unconditionally'. From 'call/session related class is looser?', a 'YES' leads back to 'Indicator for call/session unrelated class received? [Note 2]' and a 'NO' leads to 'Call/session unrelated class'. Finally, 'Indicator for call/session unrelated class received? [Note 2]' leads to 'Call/session unrelated class' if 'YES', and 'The location request is not allowed unconditionally' if 'NO'. 'call/session related class is looser?' leads to 'Call/session related class' if 'YES' and 'Call/session unrelated class' if 'NO'. + +Flowchart of privacy related action selection for the serving node. + +**Figure A.2: Privacy related action selection flow diagram of the serving node** + +NOTE 1: The UE originated call/session to the requesting LCS client is established and the address associated to the LCS client used by the UE in call/session set up matches with that contained in the location request. + +NOTE 2: A prior change makes this check unnecessary; since the call unrelated indicator is mandatory therefore the result is always "YES". + +# --- Annex B (normative): Presence of LCS client ID Components in MT-LR + +The LCS client identity is composed of one or more than one of the following components: LCS client type, external identity, internal identity, call/session related identity, APN-NI, client name and Requestor Identity. For Value added LCS client type it may contain also Client name and Requestor ID type indicator. The LCS client type shall always be present and for each LCS client type the presence of the other components are defined as follows: + +| Component
LCS Client type | External
identity | Internal
identity | Call/session
related identity | Client name | Requestor
Identity | +|------------------------------|----------------------|----------------------|----------------------------------|-------------|-----------------------| +| Emergency | O | N.A. | N.A. | N.A. | N.A. | +| Value added | M | N.A. | O [Note] | M | O | +| PLMN operator | N.A. | M | N.A. | N.A. | N.A. | +| Lawful Intercept | N.A. | N.A. | N.A. | N.A. | N.A. | + +NOTE: This component shall be present if the MT-LR is associated to either CS call or PS session. If the MT-LR is associated with the CS call, the number dialled by UE is used. Otherwise if the MT-LR is associated with the PS session, the APN-NI is used. + +## Annex C (Informative): Pseudo external ID + +In case that UE's privacy profile is stored and is checked in the GMLC (H-GMLC) or in the PPR, a pseudo-external identity may be selected as a result of the privacy check in GMLC/PPR. + +The pseudo-external identities may be set in the external LCS client list of the HLR privacy exception list shown in Table 10.2. The pseudo-external identity is not the identity of real external LCS client but the identity which is used for notifying SGSN/MSC of the location request class (call/session related or non-related) and the required type of indication for each class. Operator allocates E.164 addresses for the pseudo-external identities. The pseudo-external identities are used for interworking with pre Rel-6 serving nodes. + +Fourteen pseudo-external identities shall be defined. The pseudo-external identities are summarized in the Table C.1. + +**Table C.1: Pseudo-external identities** + +| Pseudo-external identity | Privacy setting for Call/Session related class | Privacy setting for Call/Session unrelated class | +|-------------------------------------------|-----------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------| +| Pseudo-external identity 1 | N.A. | Location allowed without notification | +| Pseudo-external identity 2 | N.A. | Location allowed with notification | +| Pseudo-external identity 3 | N.A. | Location with notification and privacy verification; location allowed if no response | +| Pseudo-external identity 4 | N.A. | Location with notification and privacy verification; location restricted if no response | +| Pseudo-external identity 5 | Location with notification and privacy verification; location restricted if no response | Location not allowed | +| Pseudo-external identity 6
Indicator 6 | Location with notification and privacy verification; location allowed if no response | Location not allowed | +| Pseudo-external identity 7 | | Location with notification and privacy verification; location restricted if no response | +| Pseudo-external identity 8 | Location allowed with notification | Location not allowed | +| Pseudo-external identity 9 | | Location with notification and privacy verification; location restricted if no response | +| Pseudo-external identity 10 | | Location with notification and privacy verification; location allowed if no response | +| Pseudo-external identity 11 | Location allowed without notification | Location not allowed | +| Pseudo-external identity 12 | | Location with notification and privacy verification; location restricted if no response | +| Pseudo-external identity 13 | | Location with notification and privacy verification; location allowed if no response | +| Pseudo-external identity 14 | | Location allowed with notification | + +NOTE: There are five privacy settings shown in Annex A.1 for each class (call/session unrelated class and call/session related class), so there are twenty-five possible combinations of the privacy settings. However, as shown in Annex A.2, even if the call/session related class criteria is met, the privacy setting for call/session unrelated class is selected when the privacy setting for the call/session unrelated class is looser than the privacy setting for the call/session related class. Therefore the twenty-five combinations can be reduced to the above fourteen combinations. + +If the UE subscribes to the universal or PLMN class, H-GMLC/PPR sends the pseudo external identity 1 to the serving nodes. + +Usage of the pseudo-external identities are as follows: + +- The pseudo-external identities are registered in SLPP of the HLR/HSS. +- The SLPP is sent to the serving nodes, during the Insert Subscriber Data procedures. +- After the privacy check in the H-GMLC/PPR, the H-GMLC/PPR selects an appropriate pseudo-external identity according to the required privacy related actions (i.e. checking the on-going call/session and/or notification/verification procedures) in the serving node. +- H-GMLC sends Provide Subscriber Location message to the serving node, which includes the pseudo-external identity instead of the real external client identity. The real external client identity may be included in the additional information element and is sent to serving node. The pseudo-external identity is sent to the serving node directly from H-GMLC or via V-GMLC. + +Table C.2 and C.3 shows how the pseudo-external identities are set in the SLPP in HLR/HSS. + +**Table C.2: Example of SLPP in HLR/HSS for Call/Session unrelated Class** + +| Pseudo-external identity | Privacy Setting | +|---------------------------------|-----------------------------------------------------------------------------------------| +| Pseudo-external identity 1 | Location allowed without notification | +| Pseudo-external identity 2 | Location allowed with notification | +| Pseudo-external identity 3 | Location with notification and privacy verification; location allowed if no response | +| Pseudo-external identity 4 | Location with notification and privacy verification; location restricted if no response | +| Pseudo-external identity 5 | Location not allowed | +| Pseudo-external identity 6 | Location not allowed | +| Pseudo-external identity 7 | Location with notification and privacy verification; location restricted if no response | +| Pseudo-external identity 8 | Location not allowed | +| Pseudo-external identity 9 | Location with notification and privacy verification; location restricted if no response | +| Pseudo-external identity 10 | Location with notification and privacy verification; location allowed if no response | +| Pseudo-external identity 11 | Location not allowed | +| Pseudo-external identity 12 | Location with notification and privacy verification; location restricted if no response | +| Pseudo-external identity 13 | Location with notification and privacy verification; location allowed if no response | +| Pseudo-external identity 14 | Location allowed with notification | + +**Table C.3: Example of SLPP in HLR/HSS for Call/Session related Class** + +| Pseudo-external identity | Privacy Setting | +|---------------------------------|-----------------------------------------------------------------------------------------| +| Pseudo-external identity 5 | Location with notification and privacy verification; location restricted if no response | +| Pseudo-external identity 6 | Location with notification and privacy verification; location allowed if no response | +| Pseudo-external identity 7 | Location with notification and privacy verification; location allowed if no response | +| Pseudo-external identity 8 | Location allowed with notification | +| Pseudo-external identity 9 | Location allowed with notification | +| Pseudo-external identity 10 | Location allowed with notification | +| Pseudo-external identity 11 | Location allowed without notification | +| Pseudo-external identity 12 | Location allowed without notification | +| Pseudo-external identity 13 | Location allowed without notification | +| Pseudo-external identity 14 | Location allowed without notification | + +The selection of pseudo-external identity is based on the result of the privacy check in the H-GMLC/PPR. Table C.4 shows the relation between privacy check result and the pseudo-external identities. + +**Table C.4: Pseudo-external identity selection at H-GMLC/PPR** + +| Privacy related actions as a result of privacy check | Pseudo-external identity | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| +| Location request is allowed without notification, regardless of on-going call/session. | Pseudo-external identity 1 | +| Location request is allowed with notification, regardless of on-going call/session, | Pseudo-external identity 2 | +| Location request is allowed with notification and privacy verification, regardless of on-going call/session. Location request is allowed even if there is no response from UE. | Pseudo-external identity 3 | +| Location request is allowed with notification and privacy verification, regardless of on-going call/session. Location request is restricted if there is no response from UE. | Pseudo-external identity 4 | +| If there is call/session with the client, location request is allowed with notification and privacy verification. Location request is restricted if there is no response from UE.
If there is no call/session with the client, location request is restricted. | Pseudo-external identity 5 | +| If there is call/session with the client, location request is allowed with notification and privacy verification. Location request is allowed even if there is no response from UE.
If there is no call/session with the client, location request is restricted. | Pseudo-external identity 6 | +| If there is call/session with the client, location request is allowed with notification and privacy verification. Location request is allowed even if there is no response from UE.
If there is no call/session with the client, location request is allowed with notification and privacy verification. Location request is restricted if no response. | Pseudo-external identity 7 | +| If there is call/session with the client, location request is allowed with notification.
If there is no call/session with the client, location request is restricted. | Pseudo-external identity 8 | +| If there is call/session with the client, location request is allowed with notification.
If there is no call/session with the client, location request is with notification and privacy verification. Location request is restricted if no response. | Pseudo-external identity 9 | +| If there is call/session with the client, location request is allowed with notification.
If there is no call/session with the client, location request is allowed even if there is no response from UE. | Pseudo-external identity 10 | +| If there is call/session with the client, location request is allowed without notification.
If there is no call/session with the client, location request is restricted. | Pseudo-external identity 11 | +| If there is call/session with the client, location request is allowed without notification.
If there is no call/session with the client, location request is with notification and privacy verification. Location request is restricted if no response. | Pseudo-external identity 12 | +| If there is call/session with the client, location request is allowed without notification.
If there is no call/session with the client, location request is allowed even if there is no response from UE. | Pseudo-external identity 13 | +| If there is call/session with the client, location request is allowed without notification.
If there is no call/session with the client, location request is allowed with notification. | Pseudo-external identity 14 | + +## --- Annex D (normative): including Requestor identity to LCS client name + +In case the MSC/SGSN or the UE is pre Rel-5 then there is no possibility to send the Requestor identity to the UE in a new separate parameter. To obtain this backward compatibility the GMLC can add the Requestor identity to LCS client name. + +In order to offer best possible service for the end user the UE should be able to differentiate LCS client name and Requestor ID when they are included in to a same parameter. Also it is important that the LCS client name and the Requestor ID are separated with a consistent manner. Therefore there is a need to define a rule how the GMLC should separate LCS client name and Requestor identity. In the box below is described the practice how the LCS client name and Requestor identity should be separated. + +| | +|------------------------------------------| +| LCS clientName==RequestorIdentity | +|------------------------------------------| + +LCS client name and Requestor identity are separated with two equal signs. + +NOTE: It is possible that the Requestor identity does not fit into the LCS client name field. In that case as many characters as possible from the beginning is added to the LCS client name field. + +## Annex E (Informative): Handling of pseudonyms in location services + +There is a requirement in place on anonymity for both the requestor and the target in the LCS Stage 1, TS 22.071, and there are or will be regulatory requirements to support anonymity in location services in some countries. It is seen as a basic service requirement that the user should be able to request anonymity at will. + +There are various methods available for providing anonymity-support for LCS. One model has been described by the GSM Association in the LS in TD S2-021104 to 3GPP. In short, GSMA's model introduces the following logical architecture. + +![Figure E.1: GSMA logical model to support anonymity. This sequence diagram shows the interaction between five entities: Terminal, Gateway, LCS client, PMD, and GMLC/PPR. The sequence of messages is as follows: 1. Terminal sends a 'Service request' to Gateway. 2. Gateway sends 'Obtain pseudonym' to PMD. 3. Gateway sends 'Service request with pseudonym' to LCS client. 4. LCS client sends 'Location request with pseudonym' to GMLC/PPR. 5. GMLC/PPR sends 'Obtain verinym' to PMD. 6. GMLC/PPR sends 'Location response' to LCS client. 7. LCS client sends 'Service response' to Gateway. 8. Gateway sends 'Obtain MSISDN' to PMD. 9. Gateway sends 'Service response' to Terminal.](a3f61f2e4a173b16257cd80e83d41d38_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant Gateway + participant LCS client + participant PMD + participant GMLC/PPR + + Terminal->>Gateway: 1. Service request + Gateway->>PMD: 2. Obtain pseudonym + Gateway->>LCS client: 3. Service request with pseudonym + LCS client->>GMLC/PPR: 4. Location request with pseudonym + GMLC/PPR->>PMD: 5. Obtain verinym + GMLC/PPR->>LCS client: 6. Location response + LCS client->>Gateway: 7. Service response + Gateway->>PMD: 8. Obtain MSISDN + Gateway->>Terminal: 9. Service response + +``` + +Figure E.1: GSMA logical model to support anonymity. This sequence diagram shows the interaction between five entities: Terminal, Gateway, LCS client, PMD, and GMLC/PPR. The sequence of messages is as follows: 1. Terminal sends a 'Service request' to Gateway. 2. Gateway sends 'Obtain pseudonym' to PMD. 3. Gateway sends 'Service request with pseudonym' to LCS client. 4. LCS client sends 'Location request with pseudonym' to GMLC/PPR. 5. GMLC/PPR sends 'Obtain verinym' to PMD. 6. GMLC/PPR sends 'Location response' to LCS client. 7. LCS client sends 'Service response' to Gateway. 8. Gateway sends 'Obtain MSISDN' to PMD. 9. Gateway sends 'Service response' to Terminal. + +**Figure E.1: GSMA logical model to support anonymity** + +In this PUSH model the pseudonym of the target UE is always generated for certain LCS clients on behalf of the terminal's subscriber without a specific request. + +The PUSH model describes the case when the target UE requests its own location using e.g. SMS or WAP. SMS and WAP functions currently have problems in supporting anonymity, because the SMS/WAP gateways forward the originating MSISDN to the receiver. This weakness may be resolved in practise e.g. such that the SMS or WAP Gateway requests pseudonyms from a common device (PMD), as shown in Figure E.1. In this process the gateway requests a pseudonym from PMD in signalling step 2 and in signalling step 3 the gateway uses the pseudonym in the service request that it sends to the LCS client. The gateway includes the requesting terminal's verinym, i.e. the MSISDN, in the service response it sends to the terminal in step 9. In this way the LCS client only knows the pseudonym of the terminal and not the verinym. This solution is not LCS specific, since the SMS/WAP gateway inserts pseudonyms in all SMS/WAP messages, which the gateway forwards to the receivers (LCS clients) defined by the operator in advance. + +The Liberty Alliance Project has standardized methods that can be used to ensure the anonymity of the target UE in location services using pseudonyms as shown by the example in Figure E.2 below. The specifications of the Liberty Alliance project are publicly available at . + +![Figure E.2: Logical model to support anonymity. A sequence diagram showing interactions between Terminal, Liberty enabled Proxy/Gateway, LCS client, PPR/PMD (IPD), and GMLC. The sequence starts with a Service request from Terminal to Proxy/Gateway. The Proxy/Gateway sends an Anonym Ser. Req to LCS client. The LCS client sends a Pseudonym Req to Proxy/Gateway. The Proxy/Gateway sends an Obtain pseudonym request to PPR/PMD (IPD). The PPR/PMD (IPD) sends an Obtain Verinym request to GMLC. The GMLC sends a Location request with pseudonym to LCS client. The LCS client sends a Location Response to GMLC. The GMLC sends a Pseudonym Resp to PPR/PMD (IPD). The PPR/PMD (IPD) sends a Final Ser. Resp to Proxy/Gateway. The Proxy/Gateway sends a Final Ser. Resp to Terminal.](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +``` + +sequenceDiagram + participant Terminal + participant Proxy as Liberty enabled Proxy/Gateway + participant LCS as LCS client + participant PMD as PPR/PMD (IPD) + participant GMLC + + Terminal->>Proxy: 1. Service request + Proxy->>LCS: 2. Anonym Ser. Req + LCS->>Proxy: 3. Pseudonym Req + Proxy->>PMD: 4. Obtain pseudonym + PMD->>GMLC: 7. Obtain Verinym + GMLC->>LCS: 6. Location request with pseudonym + LCS->>GMLC: 8. Location Response + GMLC->>PMD: 5. Pseudonym Resp + PMD->>Proxy: 9. Anonym Ser. Resp + Proxy->>Terminal: 10. Final Ser. Resp + +``` + +Figure E.2: Logical model to support anonymity. A sequence diagram showing interactions between Terminal, Liberty enabled Proxy/Gateway, LCS client, PPR/PMD (IPD), and GMLC. The sequence starts with a Service request from Terminal to Proxy/Gateway. The Proxy/Gateway sends an Anonym Ser. Req to LCS client. The LCS client sends a Pseudonym Req to Proxy/Gateway. The Proxy/Gateway sends an Obtain pseudonym request to PPR/PMD (IPD). The PPR/PMD (IPD) sends an Obtain Verinym request to GMLC. The GMLC sends a Location request with pseudonym to LCS client. The LCS client sends a Location Response to GMLC. The GMLC sends a Pseudonym Resp to PPR/PMD (IPD). The PPR/PMD (IPD) sends a Final Ser. Resp to Proxy/Gateway. The Proxy/Gateway sends a Final Ser. Resp to Terminal. + +**Figure E.2: Logical model to support anonymity** + +In this PULL model the LCS client requests the pseudonym from the Gateway before accepting the service request from the terminal. The proxy/gateway is a so-called Liberty Enabled Client/Proxy, which also may support standard WAP proxy/gateway functions as described in the appropriate WAP Forum specifications. + +1. The terminal (UE) sends a standard Wireless Transport Protocol (WTP) –request to the Proxy/Gateway. +2. The proxy/gateway converts the service request into an HTTP-request with a dynamic IP address. This HTTP-request does not contain the MSISDN of the terminal, so it is totally anonymous to the LCS-client. +3. The LCS-client needs to get an assertion, i.e. a pseudonym, before it can accept to provide location services to the terminal, so it sends a HTTP-response to the Proxy/Gateway, which includes a request for a pseudonym. +4. The proxy/gateway maps the LCS client's HTTP-response to the HTTP-request it sent in step 2 and thus the proxy/gateway also knows to which terminal the LCS client's HTTP-response is related. The proxy/gateway intercepts and interprets the HTTP-response and finds the pseudonym request. It forwards the pseudonym request to PMD and attaches the terminal's MSISDN to allow the PMD to provide a pseudonym related to this MSISDN. In case PMD needs to contact the target UE user for some reason, e.g. to ask for consent to deliver the pseudonym to this specific LCS-client, this interaction is fully supported in the Liberty Enabled Client/Proxy specification. +5. The proxy/gateway sends an HTTP-request containing the pseudonym to the LCS-client. +6. The LCS-client sends a location service request to GMLC using the pseudonym of the target terminal. +7. The PMD may include the MSISDN in the pseudonym by encrypting it in such a way that GMLC is able to determine the MSISDN itself and in such a case step 7 is not needed. In case GMLC cannot find out the verinym of the terminal itself, it requests from PMD the MSISDN that corresponds to the pseudonym it received from the LCS-client. +8. GMLC provides location information to the LCS-client using the pseudonym of the target terminal. +9. The LCS-client sends an HTTP-response to the proxy/gateway containing the requested location specific service content. +10. The proxy/gateway maps the response to the outstanding request sent in step 1 and delivers the result to the correct terminal using MSISDN. + +Note that the mechanism described above is a generalized solution to the problem of transporting something from party 1 (PMD) to party 3 (GMLC) so that intermediate party 2 (LCS-client) cannot find out the real content transferred between party 1 and party 3 (verinym in this case). Also note that since the proxy/gateway does not push any pseudonym in step 2, it is not required to understand the destination application and what information it may need. Step 3 allows any application to request a pseudonym or any information it may need, thus making this a generalized solution, which may be used for many types of applications, not only LCS. + +It is to be noted that the Liberty release 1.1 specification has been carefully studied by the EU article 29 committee and found to be in accordance with the current EU privacy requirements. It is stressed, however, that it is the responsibility + +of someone implementing or deploying a system in accordance with the Liberty Alliance specifications to comply with EU directives and requirements on privacy. + +For roaming cases clause 9.1.1 in this specification describes the cases where the pseudonym contains the address(es) of the target UE's Home-GMLC so that the Requesting-GMLC can forward the location request to H-GMLC, which may determine the corresponding verinym itself or request the verinym from its associated PMD. + +# Annex F (Informative): Mechanism for performing Change of Area Event Detection + +Note: the classification (i.e. normative or informative) of this Annex is FFS. + +As described in clause 9.1.9 that there may be alternative mechanisms to transfer the deferred MT-LR with Area Event request to the UE. This annex illustrates one mechanism. In this mechanism a Short Message Service (SMS) is used to transfer, to the UE/(U)SIM, the Area event detection request via an (U)SIM Application Toolkit application. + +## F.1 (U)SIM Application Toolkit (USAT) Based Solution + +In this (U)SAT based solution, the area event detection mechanism relies on the proactive control of the UE by the (U)SIM using the (U)SAT commands controlled by a specific Change of Area Deferred Location application. Figure F.1 illustrates one possible method for downloading a change of area event application to the UE, but does not detail the operation of the application. The details of the application is outside the scope of this specification. Further information about the possible (U)SAT commands, can be found from TS 31.111 [37]. + +The following procedure (shown in Figure F.1) replaces Figure 9.6d in clause 9.1.9. + +![Sequence diagram illustrating the (U)SAT Application Download and Change of Area Event Detection Procedure. The diagram shows interactions between LCS Client, R-GMLC, H-GMLC, MSC / SGSN, and UE/(U)SIM. The steps are: 1. LCS Service Request from LCS Client to R-GMLC; 2. Common Procedures for LCS between R-GMLC and H-GMLC; 3. USAT Application Delivery – Change of Area Event Invoke + Notification from H-GMLC to UE/(U)SIM; 4. USAT Application Delivery Acknowledge from UE/(U)SIM to H-GMLC; 5. LCS Service Response from R-GMLC to LCS Client; 6. Event Occurs at UE/(U)SIM; 7. Change of Area Event Report from UE/(U)SIM to H-GMLC; 8. Privacy Check between H-GMLC and R-GMLC; 9. LCS Service Response from H-GMLC to LCS Client.](10ceb47973510a1b47421741263146cc_img.jpg) + +``` + +sequenceDiagram + participant LCS Client + participant R-GMLC + participant H-GMLC + participant MSC / SGSN + participant UE/(U)SIM + + Note right of R-GMLC: 2. Common Procedures for LCS + Note right of UE/(U)SIM: 6. Event Occurs + Note right of H-GMLC: 8. Privacy Check + + LCS Client->>R-GMLC: 1. LCS Service Request + R-GMLC->>H-GMLC: 2. Common Procedures for LCS + H-GMLC->>UE/(U)SIM: 3. USAT Application Delivery – Change of Area Event Invoke + Notification + UE/(U)SIM->>H-GMLC: 4. USAT Application Delivery Acknowledge + R-GMLC->>LCS Client: 5. LCS Service Response + UE/(U)SIM->>H-GMLC: 7. Change of Area Event Report + H-GMLC->>R-GMLC: 8. Privacy Check + H-GMLC->>LCS Client: 9. LCS Service Response + +``` + +Sequence diagram illustrating the (U)SAT Application Download and Change of Area Event Detection Procedure. The diagram shows interactions between LCS Client, R-GMLC, H-GMLC, MSC / SGSN, and UE/(U)SIM. The steps are: 1. LCS Service Request from LCS Client to R-GMLC; 2. Common Procedures for LCS between R-GMLC and H-GMLC; 3. USAT Application Delivery – Change of Area Event Invoke + Notification from H-GMLC to UE/(U)SIM; 4. USAT Application Delivery Acknowledge from UE/(U)SIM to H-GMLC; 5. LCS Service Response from R-GMLC to LCS Client; 6. Event Occurs at UE/(U)SIM; 7. Change of Area Event Report from UE/(U)SIM to H-GMLC; 8. Privacy Check between H-GMLC and R-GMLC; 9. LCS Service Response from H-GMLC to LCS Client. + +Figure F.1: (U)SAT Application Download and Change of Area Event Detection Procedure + +- 1) This step is the same as step 1 in clause 9.1.9. +- 2) This step is similar to step 2 in clause 9.1.9, except the LCS Service Request does not reach the V-GMLC. Also the H-GMLC may request a translation of geographic shape to network identities from a GMLC in the network serving the target UE. +- 3) Information about the event, the (U)SAT application, that shall trigger the sending of the Location Report shall be sent to the UE/(U)SIM. If privacy action (notification and/or verification) was requested as a result of the privacy check, the H-GMLC shall also include the required action to the UE/(U)SIM. If notification/verification is required, the request shall indicate the identity of the LCS client, the Requestor Identity (if available), and the reference number. The mechanism by which the trigger detection is performed via (U)SAT application may be operator dependent. However, the (U)SAT Application shall contain the following information: reference number, H-GMLC address, validity period of request, and the area definition (of the target area). +- 4) If privacy verification was requested, the UE/(U)SIM indicates to its user whether the location request will be allowed or not allowed in the absence of a response and waits for the user to grant or deny permission. If privacy verification was requested and the user grants permission, the USAT Application shall be installed and the + +UE/(U)SIM then returns an acknowledgement to the H-GMLC indicating permission is granted and (U)SAT application is successfully installed. If the UE user does not respond after a predetermined time period (and the request is not allowed in the absence of a response) or denies permission, the UE/(U)SIM shall infer a "no response" condition, the USAT Application is not installed, an appropriate error response is returned to the GMLC/LCS Client and the remaining steps are skipped. Otherwise the UE/(U)SIM notifies the UE user of the location request (if required by the privacy action) and shall install the (U)SAT application and acknowledge successful installation to the H-GMLC, including an indication of "no response" but request is allowed if necessary. If at any point the (U)SAT application fails to install, due to lack of support or otherwise, the UE/(U)SIM shall inform the H-GMLC using an appropriate error cause. + +- 5) The H-GMLC returns a LCS Service Response via R-GMLC to the LCS Client to notify whether the request was successfully accepted/installed or not, without a location estimate. When the R-GMLC returns the LCS Service Response to the LCS Client, the LDR reference number assigned by the R-GMLC shall be included. +- 6) The UE/(U)SIM detects the desired change of area event. +- 7) The UE/(U)SIM reports the change of area event. +- 8) The H-GMLC may perform another privacy check as described in clause 9.1.1. +- 9) The H-GMLC then returns a LCS Service Response to the LCS Client via the R-GMLC, if applicable, as in clause 9.1.1. When the R-GMLC returns the LCS Service Response to the LCS Client, the LDR reference number that was sent to the LCS Client in step 5 shall be included. If the GMLC for some other reason decides to not wait any longer for the requested event to occur (e.g. timer expires), an LCS Service Response shall be returned with an appropriate error cause indicating termination of the deferred location request. + +H-GMLC may be the origination point of the SMS-DELIVER and the USAT Application messages. + +## --- Annex G (normative): Defined Service Types and numbering + +The defined Service Types and assigned numbers shall be as defined in TS 29.002 [18], clause 17.7.8. + +## Annex H (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2012-09 | - | - | - | - | - | Update to Rel-11 version (MCC) | 11.0.0 | +| 2012-12 | SP-58 | SP-120711 | 0395 | 2 | A | Continuation of LCS Session in EPS after S1 Connection Release | 11.1.0 | +| 2012-12 | SP-58 | SP-120726 | 0396 | 3 | B | Addition of UTDOA technology and SLm interface in LTE | 11.1.0 | +| 2013-03 | SP-59 | SP-130079 | 0399 | - | A | Use of non-dialable callback number at SR-VCC handover of emergency call. | 11.2.0 | +| 2013-12 | SP-62 | SP-130535 | 0400 | 4 | B | Introduction of Diameter interface between SGSN and GMLC (Lgd) | 12.0.0 | +| 2014-06 | SP-64 | SP-140255 | 0403 | 2 | A | Correction on location reporting in emergency 1xSRVCC | 12.1.0 | +| 2015-09 | SP-69 | SP-150503 | 0409 | 1 | B | Support of retrieval of Location Information for support of IMS ES for WLAN interworking based on TR 23.771 phase 1 conclusion | 13.0.0 | +| 2015-09 | SP-69 | SP-150501 | 0410 | 1 | B | MT Location procedures when a UE is in Idle eDRX mode | 13.0.0 | +| 2016-12 | SP-74 | SP-160825 | 0417 | 1 | F | EPC-NI-LI procedure with release indication | 14.0.0 | +| 2016-12 | SP-74 | SP-160822 | 0418 | 2 | B | Deferred location for the UE availability event with EPC Access | 14.0.0 | +| 2016-12 | SP-74 | SP-160822 | 0419 | 2 | B | Indication of UE Access Type for NB-IoT | 14.0.0 | +| 2016-12 | SP-74 | SP-160822 | 0421 | - | B | Support of Last Known Location for a UE in power saving mode | 14.0.0 | +| 2016-12 | SP-74 | SP-160822 | 0422 | 2 | B | Addition of Periodic and Triggered Location for EPC Access | 14.0.0 | +| 2016-12 | SP-74 | SP-160822 | 0423 | 2 | B | Support of UE positioning measurements in Idle State | 14.0.0 | +| 2017-03 | SP-75 | SP-170050 | 0424 | 2 | F | Location reporting using Control Plane CIOT EPS Optimisation | 14.1.0 | +| 2017-03 | SP-75 | SP-170053 | 0425 | 1 | F | Location Continuity for Emergency Call Handover between E-UTRAN and WLAN | 14.1.0 | +| 2017-06 | SP-76 | SP-170369 | 0427 | - | F | Support of UE positioning measurements in Idle State | 14.2.0 | +| 2017-12 | SP-78 | SP-170911 | 0429 | 1 | A | Positioning methods alignment | 14.3.0 | +| 2018-03 | SP-79 | SP-180085 | 0430 | 1 | F | Removal of hanging Editor's Note on support for deferred location | 14.4.0 | +| 2018-06 | SP-80 | SP-180496 | 0432 | 3 | B | Addition of Broadcast of Assistance Data for E-UTRAN | 15.0.0 | +| 2018-06 | SP-80 | SP-180475 | 0433 | - | F | LCS in 5GC | 15.0.0 | +| 2018-09 | SP-81 | SP-180729 | 0434 | - | F | Cleanup of Broadcast of Assistance Data for E-UTRAN | 15.1.0 | +| 2019-12 | SP-86 | SP-191067 | 0435 | - | F | Corrections to LCS Assistance Data Broadcast procedure | 15.2.0 | +| 2020-07 | SP-88E | - | - | - | - | Update to Rel-16 version (MCC) | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23278/18003425d0e8638dde4acc9c5c468c5c_img.jpg b/marked/Rel-16/23_series/23278/18003425d0e8638dde4acc9c5c468c5c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..19a72704d47eaec5a478218e5734c4a18ca1dd28 --- /dev/null +++ b/marked/Rel-16/23_series/23278/18003425d0e8638dde4acc9c5c468c5c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:958a8287fa4049c606fb3668b07ba5c567583352c14953313b10f96da50184f1 +size 150049 diff --git a/marked/Rel-16/23_series/23278/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/23_series/23278/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d7442e73638cb53f03bbb6f716d5cec62494b0b --- /dev/null +++ b/marked/Rel-16/23_series/23278/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e50dc468fbe6ce76a9e57b278886be56709ac4d23ef866302fb430d0d09ecba8 +size 138278 diff --git a/marked/Rel-16/23_series/23278/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-16/23_series/23278/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fcf98d3b1f8219d5eee4666defc39d38ea8fa67e --- /dev/null +++ b/marked/Rel-16/23_series/23278/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f1b73cc06a5804f2ce5a7030fc46a3e4f7d5da2a20d29cd222b2605378c85a3 +size 134389 diff --git a/marked/Rel-16/23_series/23278/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23278/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dc9e9953eef978130351321c551bc68270fa5d77 --- /dev/null +++ b/marked/Rel-16/23_series/23278/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:568e3fecd5bf753495828fe6f2df9ec40b47d884c07e270601df4247ee2f618c +size 80025 diff --git a/marked/Rel-16/23_series/23278/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/marked/Rel-16/23_series/23278/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e87ac6b609fe34e137ef0d532bc5171c935646f7 --- /dev/null +++ b/marked/Rel-16/23_series/23278/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2e2850ab33821657945b24199ce8e582ac022466ede1a134c2fc4ac4fa714dd8 +size 136742 diff --git a/marked/Rel-16/23_series/23278/a5404b7275b06497eecf9b5883604753_img.jpg b/marked/Rel-16/23_series/23278/a5404b7275b06497eecf9b5883604753_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cd117c7f40a5006a45d8f460d715b0a792e1885 --- /dev/null +++ b/marked/Rel-16/23_series/23278/a5404b7275b06497eecf9b5883604753_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c52f377e0ffccd51866df8fecf07da52575f6449ee31c4426d19fbf388ca5549 +size 145685 diff --git a/marked/Rel-16/23_series/23278/b8efedb73292a798b3f2050f9335cae6_img.jpg b/marked/Rel-16/23_series/23278/b8efedb73292a798b3f2050f9335cae6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a25596b349da331834fdc2ffc623fac8c22858cf --- /dev/null +++ b/marked/Rel-16/23_series/23278/b8efedb73292a798b3f2050f9335cae6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97e09c63337401d9ae5d77bfc5a3e94f06673ff243455c4ce1d70a913062c1cc +size 21285 diff --git a/marked/Rel-16/23_series/23278/fc3e2b49a9f850951570e502393b697f_img.jpg b/marked/Rel-16/23_series/23278/fc3e2b49a9f850951570e502393b697f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab47553f5506fe20df615e25fc65ccf0ab5b28f1 --- /dev/null +++ b/marked/Rel-16/23_series/23278/fc3e2b49a9f850951570e502393b697f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23546982bae1133fed29d3f5cbd8e0162176a840e8f5930c89dc2373fa208da4 +size 80555 diff --git a/marked/Rel-16/23_series/23278/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/marked/Rel-16/23_series/23278/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51367e931183dd37982ad195f021a2665e3be197 --- /dev/null +++ b/marked/Rel-16/23_series/23278/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:361450b8aa31af0ec8f9d38fd56ee6ffaf835c4c09c0dc475d4c737efb36d69b +size 54056 diff --git a/marked/Rel-16/23_series/23279/053f1077d592e6622cd21dc4bb4cb366_img.jpg b/marked/Rel-16/23_series/23279/053f1077d592e6622cd21dc4bb4cb366_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa11c8b93e7ea1d405cd0bfadde5c0f990b4d444 --- /dev/null +++ b/marked/Rel-16/23_series/23279/053f1077d592e6622cd21dc4bb4cb366_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a44707e5e86d242d3f73ff239b21c6ecdc7d1d554467d115b157014cddb0e41 +size 74249 diff --git a/marked/Rel-16/23_series/23279/12de9b926df0384ec07702671827c9cd_img.jpg b/marked/Rel-16/23_series/23279/12de9b926df0384ec07702671827c9cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03f8068c9c21329b29bf0975b1ad24637b9be317 --- /dev/null +++ b/marked/Rel-16/23_series/23279/12de9b926df0384ec07702671827c9cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ca502fbfc41213cc950824441980926baf07e7127321f8f13e4e5e237a2d2b5 +size 85675 diff --git a/marked/Rel-16/23_series/23279/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23279/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3056e04bb4aa8253627d22f83a23fa7fa8554c3 --- /dev/null +++ b/marked/Rel-16/23_series/23279/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b3a4d4730a7455d6645b818f44453177f0ffcc82063de601759fc10d6a190214 +size 57652 diff --git a/marked/Rel-16/23_series/23279/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23279/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1ce2428b5a284c333b04fb1d8fe058bb24561770 --- /dev/null +++ b/marked/Rel-16/23_series/23279/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:907b8410382e95ac4da735c8d88cb2fdde124b7e505f8ee38b302fdc63e90182 +size 94828 diff --git a/marked/Rel-16/23_series/23279/4356776ca004ecba5d599667a155d7d4_img.jpg b/marked/Rel-16/23_series/23279/4356776ca004ecba5d599667a155d7d4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..00279fa974f85ef2e3f93750ba390b11f895a7ae --- /dev/null +++ b/marked/Rel-16/23_series/23279/4356776ca004ecba5d599667a155d7d4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c0e5b65c2b80332992f22e3005c30d001d7f730688ec2ba863187f6df4944305 +size 76324 diff --git a/marked/Rel-16/23_series/23279/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg b/marked/Rel-16/23_series/23279/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c11ea268d882d56c07dffaa09cc2291fbf7672f2 --- /dev/null +++ b/marked/Rel-16/23_series/23279/5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31066e35cbd69e9a8cd6c45135b5ac1f63bafd0530539c4670293b85497e6d04 +size 52170 diff --git a/marked/Rel-16/23_series/23279/6470d350326789d5306eabcb76533951_img.jpg b/marked/Rel-16/23_series/23279/6470d350326789d5306eabcb76533951_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22e21d8e11a69988af4926ab237b95412e00b8e5 --- /dev/null +++ b/marked/Rel-16/23_series/23279/6470d350326789d5306eabcb76533951_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:312e6d65a7630abeb0df5222b7d38729b14bc8eb026a74f4a4571afc31dba78a +size 68470 diff --git a/marked/Rel-16/23_series/23279/803776dff64331076ffc951fc95358ee_img.jpg b/marked/Rel-16/23_series/23279/803776dff64331076ffc951fc95358ee_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7265da9090ff64da609c3bb7fdb530583bcec7de --- /dev/null +++ b/marked/Rel-16/23_series/23279/803776dff64331076ffc951fc95358ee_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d10798cf8c0ff9b864d67babdbff5136df34b383754f16e85548cf337356c8ce +size 60871 diff --git a/marked/Rel-16/23_series/23279/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23279/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3243969b7ba6aa345de9180a963f42f221c8e75b --- /dev/null +++ b/marked/Rel-16/23_series/23279/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a27af33c6ab0623e7277f79d53fe0e89ab33fdb76cb86556b22849edde187318 +size 61609 diff --git a/marked/Rel-16/23_series/23279/a3472689858b068ef469213682965325_img.jpg b/marked/Rel-16/23_series/23279/a3472689858b068ef469213682965325_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..859123861a976fd25017593d547de434931d3058 --- /dev/null +++ b/marked/Rel-16/23_series/23279/a3472689858b068ef469213682965325_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4468c680a5dea0ccbfd0439cfe00307d06c4212ae7163b9a288a304b411c20d5 +size 110135 diff --git a/marked/Rel-16/23_series/23279/c036e2540a94b31357ceb0002f0cacab_img.jpg b/marked/Rel-16/23_series/23279/c036e2540a94b31357ceb0002f0cacab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8eebb53ddccfe277bd08be3b607c0ca3c7026965 --- /dev/null +++ b/marked/Rel-16/23_series/23279/c036e2540a94b31357ceb0002f0cacab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd32233530f45356ac43bfeccbe71dfbcbb771c01e7fa5efb6bdae903793c604 +size 71776 diff --git a/marked/Rel-16/23_series/23279/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/marked/Rel-16/23_series/23279/dbbc0baac7341cda76cc4f8355dce23f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e1e9e68257384922d835d842ddc56507a03c16c --- /dev/null +++ b/marked/Rel-16/23_series/23279/dbbc0baac7341cda76cc4f8355dce23f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d933cad5e351a00f4c9ad51b6d1da3c8381c8461070ad03a58923f0d72340f7a +size 102204 diff --git a/marked/Rel-16/23_series/23279/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23279/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fc6f0896aed83db2821e49cfa43663e452c5c42e --- /dev/null +++ b/marked/Rel-16/23_series/23279/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea6a3db241856ddc9ab18d8ae2a70f77c112f80f174d2c861d5963a404821937 +size 123296 diff --git a/marked/Rel-16/23_series/23279/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg b/marked/Rel-16/23_series/23279/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c5bf5b16f30c494f26eaf0943fca14618ff99575 --- /dev/null +++ b/marked/Rel-16/23_series/23279/f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cd28a65a04b44c65beb3669ef6fbb7e28b6f5f5b35a593fac247faaa8f68595b +size 70021 diff --git a/marked/Rel-16/23_series/23279/raw.md b/marked/Rel-16/23_series/23279/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..e9250cdbc28f2f26f22327bcc2c04f5871b832b7 --- /dev/null +++ b/marked/Rel-16/23_series/23279/raw.md @@ -0,0 +1,1197 @@ + + + + + + +# Contents + +| | | +|-----------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| Introduction ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 7 | +| 4 Overall requirements..... | 8 | +| 4.1 General description ..... | 8 | +| 4.2 Service requirements..... | 8 | +| 5 Architectural requirements..... | 8 | +| 5.1 Architectural requirements ..... | 8 | +| 5.2 Session scenarios..... | 9 | +| 5.3 UE logic..... | 9 | +| 6 Architecture..... | 10 | +| 6.1 General Architecture ..... | 10 | +| 6.2 CSI Application Server (CSI AS) ..... | 11 | +| 6.2.1 CSI AS functionality ..... | 11 | +| 6.2.2 Initial Filter Criteria..... | 11 | +| 7 Capability exchange..... | 11 | +| 7.1 General ..... | 11 | +| 7.2 Capability information ..... | 12 | +| 7.2.1 Information about the current radio environment..... | 12 | +| 7.2.2 UE capability information ..... | 12 | +| 7.2.3 IM Status ..... | 13 | +| 7.3 Registering UE capability information ..... | 13 | +| 7.4 Multiple MEs per user..... | 13 | +| 8 Information flows..... | 14 | +| 8.1 Exchange of capability information at CS call setup ..... | 14 | +| 8.2 Exchange of UE capability information..... | 15 | +| 8.3 User adds an IMS service to an ongoing CS call ..... | 17 | +| 8.3.1 IMS session set up without media requiring resource reservation ..... | 17 | +| 8.3.2 IMS session set- up with media requiring resource reservation..... | 19 | +| 8.4 User adds a CS call to an ongoing IMS session..... | 21 | +| 8.5 Release of CSI..... | 22 | +| 8.6 Terminating a Multimedia IMS session to a CSI UE..... | 22 | +| 9 Interaction with supplementary services..... | 24 | +| 9.1 General ..... | 24 | +| 9.2 Line Identification ..... | 24 | +| 9.2.1 Calling Line Identity Presentation (CLIP) ..... | 24 | +| 9.2.2 Calling Line Identification Restriction (CLIR) ..... | 24 | +| 9.2.3 Connected Line Identification Presentation (COLP)..... | 25 | +| 9.2.4 Connected Line Identification Restriction (COLR) ..... | 25 | +| 9.3 Call Forwarding..... | 25 | +| 9.4 Call Offering ..... | 25 | +| 9.4.1 Explicit Call Transfer (ECT)..... | 25 | +| 9.5 Call Completion ..... | 26 | +| 9.5.1 Call Waiting (CW) and Call Hold (CH)..... | 26 | +| 9.6 Call Barring..... | 26 | +| 10 Other considerations ..... | 26 | +| 10.1 Handover ..... | 26 | + +10.2 Relation to SMS ..... 26 + +**Annex A (Informative): Support of CSI origination towards IMS termination with CSI interworking ..... 27** + +A.1 Introduction ..... 27 + +A.2 Overview ..... 27 + +A.3 Procedures ..... 27 + +A.3.1 General Architecture ..... 27 + +A.3.3 Call flows for setting up the voice session for CSI origination and IMS termination with CSI interworking ..... 28 + +A.3.4 Call flows for adding IMS sessions to existing voice calls for CSI origination with CSI interworking ..... 31 + +Annex B (informative): Change history ..... 35 + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- Introduction + +The combination of CS and IMS services (CSI) is the parallel operation of a CS service and an IMS session between the same two users. It does not require a specific subscription and a specific charging correlation. + +# --- 1 Scope + +The present document provides architectural details to combine CS services and IMS services for using them in parallel between the same two users in a peer-to-peer context. The document provides a detailed description of how capabilities and identities are exchanged to enable the combination of CS and IMS services between the same two UEs. + +The present document includes the following capabilities that enable the combination of CS and IMS services: + +- Radio capability exchange. +- SIP based UE terminal capability exchange. +- MSISDN number exchange in SIP. +- Establishing an IMS session in parallel to an ongoing CS call between the same two UEs. +- Establishing a CS call in parallel to an ongoing IMS session between the same two users UEs. +- Network support for establishing multimedia sessions between a UE that uses IMS origination and a UE that uses CS termination. + +The individual CS call or IMS service that are combined are described in their respective specifications. + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [3] 3GPP TS 23.081: "Line Identification supplementary services; Stage 2". +- [4] 3GPP TS 23.221: "Architectural Requirements". +- [5] 3GPP TS 23.002: "Network Architecture". +- [6] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3". +- [7] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". +- [8] 3GPP TS 23.082: "Call Forwarding (CF) supplementary services; Stage 2". +- [9] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2". +- [10] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [11] 3GPP TS 23.088: "Call Barring (CB) Supplementary Service; Stage 2". +- [12] 3GPP TS 23.091: "Explicit Call Transfer (ECT) Supplementary Service; Stage 2". +- [13] 3GPP TS 22.279: "Combined CS Calls and IMS Sessions; Stage 1". +- [14] 3GPP TS 22.115: "Service Aspects; Charging and Billing". + +- [15] 3GPP TS 23.087: "User-to-User Signalling (UUS) Supplementary Service; Stage 2". +- [16] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2". +- [17] 3GPP TS 23.206: "Voice Call Continuity (VCC) between Circuit Switched (CS) and IP Multimedia Subsystem (IMS); Stage 2". +- [18] IETF RFC 3840: "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)". +- [19] IETF RFC 3841: "Caller Preferences for the Session Initiation Protocol (SIP)". +- [20] 3GPP TS 22.087: "User-to-User Signalling (UUS); Service description; Stage 1". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**CSI session:** a multimedia session that uses the CS domain to transport all or some media components (typically, voice) and the IMS/PS domain to transport the other media components. A CSI session can be created either by establishing first a CS call and subsequently a concurrent IMS session(s), or by establishing first an IMS session(s) and subsequently a concurrent CS call. From the user point of view, a CSI session is conceived as a single multimedia session. + +**Multimedia IMS session:** a multimedia session that uses only the IMS/PS domain to transport both real-time and non-real-time media components. + +**CSI origination:** the case when a UE initiates a CS call and subsequently adds an IMS session(s), or vice versa, addressed towards the same user. + +**CSI termination:** the case when a call to a UE is terminated in the CS domain (e.g. for real-time component), while an IMS session(s) from the same originating user and towards the same UE is terminated in the IMS/PS domain. + +**IMS origination:** the case when a UE initiates an IMS session(s) and the CS domain is not involved in the originating part of the session(s). + +**IMS termination:** the case when an IMS session(s) is terminated in the IMS/PS domain and the CS domain is not involved in the terminating part of the session(s). + +## 3.2 Abbreviations + +For the purposes of the present document, the following abbreviations apply: + +| | | +|------|----------------------------------------| +| AS | Application Server | +| CSI | Combination of CS and IMS services | +| DTM | Dual Transfer Mode | +| IAM | Initial Address Message | +| CON | Connect Message | +| MRFC | Media Resource Function; Control part | +| MRFP | Media Resource Function; Physical Part | +| MSRP | Message Session Relay Protocol | +| RAT | Radio Access Technology | +| RTP | Real-time Transfer Protocol | + +# --- 4 Overall requirements + +## 4.1 General description + +The "combination of CS and IMS services" (CSI) is essentially a combination of existing CS and IMS services, i.e. mechanisms and procedures for the IMS part of the CSI session apply according to TS 23.228 [2]. + +The UE presents the CS call and IMS session within one context to the user. To facilitate this, the following capabilities shall be provided: + +1. Exchange of information related to the current radio environment; +2. Exchange of terminal capability information; +3. Addition of an IMS session to an ongoing CS call; +4. Addition of a CS call to an ongoing IMS session. +5. Network support for establishing multimedia sessions between a UE that uses IMS origination and a UE that uses CSI termination. + +CSI services can be provided: + +1. Between two CSI capable UEs that both use CSI origination and CSI termination; +2. Between a UE that uses IMS origination and a UE that uses CSI termination. + +## 4.2 Service requirements + +The service requirements of combining IMS and CS services are described in TS 22.279 [13]. + +# --- 5 Architectural requirements + +## 5.1 Architectural requirements + +The following general requirements are applicable to CSI: + +- The solution is applicable to GERAN and UTRAN; +- A CSI capable UE requires DTM capability (in case of GERAN access) and MultiRAB capability (in case of UTRAN access); +- IMS networks and IMS UEs without CSI support should not be impacted; +- CS core, PS core, xRAN are not to be impacted. Conclusively, changes should be restricted to the IMS elements and the UEs that support CSI for IMS; +- Procedures connecting the IMS to the CS domain, to the PSTN and to other SIP networks, including other IMS networks should remain unchanged; +- CS only UEs and PS only UEs are not to be impacted; +- CSI capable UE provides capabilities to associate the corresponding peer-to-peer CS and IMS communication to present it within one context for the user. The IMS communication may be peer-to-peer session or session unrelated communication, e.g. IMS immediate messaging; +- The quality of the CS call (e.g. voice quality, setup delay, handover, etc.) shall not be impacted from a user perception point of view regardless of whether the CS call is combined with an IMS session or not; +- The use of CSI requires that the UE is CS attached, PS attached and IMS registered; +- The solution shall be transparent for the end-user; + +- Existing security mechanisms for CS and IMS shall be re-used; +- For network efficiency, the UE capability exchange functionality requires the terminal to store information about the other terminals' capabilities; +- Functionality is required to handle remote parties who use more than one device (e.g. with the same MSISDN or the same public user ID). +- The same MSISDN should be used for the users IMS subscription and their CS subscription. The system behaviour is not specified for the case where the MSISDN for the IMS subscription and the CS subscription are different. +- If the UE is not IMS registered and gets engaged in a CS call, then the UE should make an IMS registration using a Public User Identity causing the MSISDN used in the CS call to be implicitly registered. + +The following general requirements are applicable to multimedia sessions between UEs that use IMS origination and UEs that use CS termination: + +- It shall be possible to interwork between IMS origination and CS termination for sessions that include a real-time (e.g. voice) components. + +NOTE: This implies the capability to perform the termination of the voice component of the session in the CS domain as a CS call, e.g. even if the UE for the CS termination is not IMS registered. + +- There shall be no requirement to maintain time synchronization between media transferred over different domains. +- The terminating CS domain and the originating IMS domain shall not be impacted. +- The impact on UE behaviour relating to the origination and termination of IMS sessions shall be minimized. +- The impact on UE behaviour relating to the origination and termination of CS calls shall be minimized. + +## 5.2 Session scenarios + +The generic architectural requirements, as described in TS 23.221 [4], are applicable, and specifically + +- The architectural solution shall support handover scenarios, including inter-system handover; +- The architectural solution shall support roaming scenarios with home GGSN ("IMS with GPRS roaming"); +- The architectural solution shall support roaming scenarios with visited GGSN ("IMS roaming"); +- The architectural solution shall be compatible with the IMS home control paradigm; +- The architectural solution shall consider future evolution to support interworking with conversational IMS services, which use PS bearers; +- The architectural solution shall consider future evolution to support migration towards conversational IMS services, which use PS bearers. + +## 5.3 UE logic + +A CS-capable UE shall have logic to trigger the capability and identity exchange required for simultaneous communication on the CS and IMS domains. Further, the logic shall be able to co-ordinate current activities in the UE, the user preferences, whether support for simultaneous CS and PS access is available and available IMS enablers in such a way, that only those services/enablers are offered to a user, which can be used simultaneously. This logic shall function in such a way that it makes the simultaneous usage of the CS and IMS domains for the media flows as transparent as possible for the user. + +For the scenario of a CS call and an IMS session being established at the same time from an end user perspective, an IMS session can be setup first followed by adding a CS call to the IMS session using the call-flow of clause 8.4, or a CS call can be setup first followed by adding the IMS session to the CS call using the call-flow of clause 8.3. + +# 6 Architecture + +## 6.1 General Architecture + +The figure below shows a high level E2E architecture of a simultaneous IMS session and CS call between two end-users belonging to the same operator. + +![Figure 6-1: High level architecture diagram showing the flow of signaling and data between two User Equipment (UE) units through various network components. The diagram is split into 'Originating session side' and 'Terminating session side'. On the originating side, a UE contains a CS (dashed box) and an IMS Client. The CS connects to an xRAN, which connects to a CS Core. The IMS Client connects to a PS Core, which connects to an IMS Core. The CS Core and IMS Core are connected via an AS (Application Server) and ISC. The IMS Core connects to another PS Core, which connects to another xRAN, which connects to the terminating UE. The terminating UE also contains a CS (dashed box) and an IMS Client. Signaling paths are shown with dashed lines (Uu/Um) between CS and CS Core, and solid lines (Nc, Nb) between CS Core and IMS Core. Data paths are shown with solid lines (Gm, Mw, Mb) between PS Core, IMS Core, and CS Core.](053f1077d592e6622cd21dc4bb4cb366_img.jpg) + +Figure 6-1: High level architecture diagram showing the flow of signaling and data between two User Equipment (UE) units through various network components. The diagram is split into 'Originating session side' and 'Terminating session side'. On the originating side, a UE contains a CS (dashed box) and an IMS Client. The CS connects to an xRAN, which connects to a CS Core. The IMS Client connects to a PS Core, which connects to an IMS Core. The CS Core and IMS Core are connected via an AS (Application Server) and ISC. The IMS Core connects to another PS Core, which connects to another xRAN, which connects to the terminating UE. The terminating UE also contains a CS (dashed box) and an IMS Client. Signaling paths are shown with dashed lines (Uu/Um) between CS and CS Core, and solid lines (Nc, Nb) between CS Core and IMS Core. Data paths are shown with solid lines (Gm, Mw, Mb) between PS Core, IMS Core, and CS Core. + +**Figure 6-1: High level architecture** + +NOTE 1: No specific IMS user plane handling capabilities that are required to support CSI have been identified, i.e. regular IMS user plane handling applies. + +### - **UE** + +The UE needs to support simultaneous CS and PS domain access i.e. GERAN DTM and/or UTRAN multiRAB capabilities. Additionally, the UE should support the capability exchange mechanism outlined in clause 7, and the capability to present the CS call and IMS session within the same context to the user. + +### - **xRAN** + +The Radio Access Network is not impacted by Combinational Services. However, for CSI to function, for GERAN access DTM is required, for UTRAN multiRAB is required + +### - **PS Core** + +The Packet Switched Core network remains unchanged. + +NOTE 2: For CSI to function, the PS core needs to support IMS. + +### - **CS Core** + +The CS Core Network remains unchanged. The CS core network contains MSC/VLR, HLR, and possibly other logical elements according to the 3GPP specifications TS 23.002 [5], TS 24.008 [6] and TS 29.002 [7]. However for the Current Radio Environment information exchange to work, support for User-User Signalling Service 1 is required (TS 22.087 [20]). + +### - **IMS Core** + +The IMS routes the SIP signalling between the UE (A) and UE (B). In addition, the IMS provides the session control and supports UE capability exchange mechanism for the support of CSI. The IMS core includes the HSS, the CSCFs, and other logical elements like MRFC, MRFP, MGCF, or Messaging AS, according to 3GPP specifications TS 23.228 [2]. + +### - **AS** + +The means of using an AS is identical to its usage in IMS. The AS may be utilised to handle the control of the IMS specific aspects of a CSI session, for example service-based charging, as described in TS 22.115 [14]. If service-based charging mechanisms like charging based on the content of a multimedia message, the message type or the number of sent and/or received messages are required, then the AS should be involved. The AS may + +also provide support for time- and/or volume based charging, see TS 23.228 [2] for a more detailed description. For meeting the requirements of interworking between UEs that use IMS origination and UEs that use CSI termination, the AS will implement the role of a CSI AS as specified in clause 6.2. + +## 6.2 CSI Application Server (CSI AS) + +### 6.2.1 CSI AS functionality + +The CSI AS is an optional application server functionality in the IMS terminating network that serves as a control entity for enabling multimedia sessions between UEs that use IMS origination and UEs that use CSI termination. This functionality can be co-hosted within a standalone or any existing application servers. The main functionality of the CSI AS is: + +- to retrieve the CSI related capabilities of UEs which have CSI capability, via third-party registration when the UE registers to IMS; +- to control the CSI termination by implementing a third-party call control logic (as per TS 23.228 [2], clause 4.2.4); +- to perform termination logic, i.e. examine the media components of a multimedia IMS session targeted toward a CSI capable UE and make a decision how to terminate them; +- to map a SIP URI to an associated Tel URI, in case the CSI AS decides to terminate an IMS session or part of the IMS session to the CS domain, and the CSI AS received a SIP URI of the called CSI capable user; +- to decide whether to keep itself in the session path or not; +- to handle session separation/forwarding for session initiation request, session modification request and session termination request. +- for CSI termination, to generate CSI capability information on behalf of the originating IMS UE and send it to the terminating CSI UE. + +Some of the factors that could influence the handling of session termination are: + +- SIP Caller preferences, Communication Service Identifiers or lack thereof; +- SDP Media components; +- UE capabilities. + +### 6.2.2 Initial Filter Criteria + +Initial filter criteria may be installed on a user's service profile regardless of their subscription so that applicable SIP requests are forwarded to the CSI AS in the terminating IMS network, and IMS registrations from a CSI capable UE are forwarded as third-party registrations to the CSI AS. + +Trigger Points in the initial filter criteria may use the following criteria: + +- IMS Communication Service ID, or lack of IMS Communication Service ID; +- The UE capability of CS voice and/or video capability during IMS registrations. + +NOTE: CSI AS can dynamically activate/deactivate the service indication data in HSS according to information collected, e.g. UE's CSI capability information. + +# --- 7 Capability exchange + +## 7.1 General + +It is highly advantageous if the set of services that can be supported between two endpoints is known to the endpoints when (or shortly after) communication is established. This information can be used to provide an indication to the user of the services that are available for a particular user-to-user communication session. This can encourage use of + +available services and avoid invocation of unavailable services, thereby avoiding customer dissatisfaction and unnecessary resource and bearer establishment attempts. + +Two types of capability information are described: information about the current radio environment, and UE capability information. + +During the radio capability exchange procedure, if the UE find that the remote UE and its current radio environment supports simultaneous CS and PS services and the IM Status indicates that an IMS communication is likely to be successful, then the UE should attempt an IMS registration (in case IMS registration had not previously been performed) based on preconfigured user's preference. + +## 7.2 Capability information + +### 7.2.1 Information about the current radio environment + +The purpose of the information about the current radio environment is to use it as input to the UE's and/or the user's decision whether to initiate further procedures (e.g. whether to start UE capability exchange, or an IMS session, or "in call MMS", etc.). + +This radio environment information exchange occurs over the CS domain during CS call set-up. + +This radio environment information is only valid during the lifetime of the CS call. At the end of the CS call, the UE should not store the radio environment information. This information can be used while the CS call is on going to help decide how to present service options to the user and/or whether to initiate a UE capability information exchange. + +The following information is exchanged: + +- a) The terminal is capable of simultaneous CS and PS services and initiated/received the CS call in a radio environment that currently supports simultaneous CS and PS services. +- b) The IM Status. +- c) UE capability version, which is used for identifying current capabilities of a terminal (to notify capability update). +- d) Personal ME Identifier (as defined in clause 7.4). + +The information flows for exchanging this information are shown in clause 8.1. + +For the CSI termination, the MGCF may interwork the UUS1 element between the IMS and the CS domain. + +### 7.2.2 UE capability information + +The UE capability information provides input to determine the set of services that can be successfully invoked between two users. + +NOTE 1: This UE capability information is exchanged only over the IMS domain. The exchange of such capabilities may occur during peer-to-peer session or session unrelated communication. + +It shall be possible to exchange the UE capabilities described below in this clause. Note that the exchange of these capabilities is subject to the availability of the information and privacy control. + +- IMS Media types which can be supported as IMS media streams (i.e. media component definitions of IMS sessions). +- Media format parameters for supported IMS media types (Codecs, media file formats etc.). +- MSISDN and preferred SIP URI for the UE sending the UE capability information. +- Personal ME Identifier to identify which of the user's MEs the UE capability information is related to. +- UE capability version. + +Additionally, it shall be possible for the UE to use IMS to exchange capability information about: + +- CS video telephony capability; +- CS voice capability; +- Support for other IMS based capabilities or services e.g. PoC. + +The UE capability information is exchanged between the calling party and the called party. + +NOTE 2: due to varying radio environments (e.g. DTM/non-DTM, etc.) a UE capability exchange has the best success rate when performed outside of any other service, i.e. when no other CS/PS/IMS service is currently invoked. + +The information flows for exchanging UE capabilities are shown in clause 8.2. + +### 7.2.3 IM Status + +The IM Status provided by the sending UE as part of the current radio environment information can be used by the receiving UE as an input for IMS registration, session initiation and any subsequent attempt to perform UE capability exchange via OPTIONS. + +NOTE: The IM Status includes the aspect that a UE may always register if the remote UE is in a state where IMS communication is possible. + +The IM Status provided by a UE during CS call setup is valid for the duration of that CS call. + +## 7.3 Registering UE capability information + +During IMS registration, a UE may register its capability information using SIP User Agent capability registration mechanism specified in RFC 3840 [18] and endorsed by TS 23.228 [2]. To facilitate the operation of CSI, it shall be possible for the UE to register at least the following UE capabilities: + +- CS video telephony capability; +- CS voice capability. + +Registration of these UE capabilities could help the core IMS network in routing SIP messages to appropriate UE when the caller indicates preference for these capabilities in the a SIP message using mechanism specified in RFC 3841 [19] and endorsed by TS 23.228 [2]. + +The UE may update registered capabilities as specified in TS 23.228 [2]. + +## 7.4 Multiple MEs per user + +For network efficiency, the capability detection functionality requires the terminal to store information about the other terminals' capabilities. + +In order to cater for remote parties who use more than one ME (e.g. with the same MSISDN or the same public user ID), CSI needs a mechanism that allows for identifying a particular user's ME. This mechanism shall be capable of identifying a ME upon UE capability exchange, CS call setup and IMS session initiation. This enables the remote party to retrieve the correct stored ME capabilities. + +In order to limit network signalling (e.g. use of SIP OPTIONS to trigger other party's request) and avoid an inconsistency between the actual and stored capabilities, it is necessary to exchange the UE capability version. + +Procedures are needed to avoid MEs of one user having the same Personal ME Identifier. + +The Personal ME Identifier and UE capability version shall fulfil the following requirements: + +- Minimal impact on SIP signalling and no impact on the IM CN subsystem; +- The identifier and the capability version should fit into UUS-1 signalling, also allowing for other services to be run over UUS-1; +- The Personal ME Identifier uniquely identifies an ME of the user. + +- The capability version is updated when UE changes its capability (e.g. UE performing online upgrade or configuration change). The capability version is unique for a given set of capabilities of a UE. + +# 8 Information flows + +## 8.1 Exchange of capability information at CS call setup + +It shall be possible for the UE to perform end-to-end information exchange about the current radio environment during CS call setup. The current radio environment information exchange procedure shall include the information as outlined in clause 7.2.1. + +NOTE: There will exist UEs, which do not support the radio environment exchange procedure, but do support parallel CS calls and IMS sessions, e.g. Rel-5 IMS-capable UMTS UEs. Thus lack of an answer in the radio capability exchange procedure does not mean that the remote UE cannot handle a parallel IMS session or the SIP based capability exchange. + +The sequence diagram in figure 8-1 outlines the exchange of information about the current radio environment, at CS call setup. The diagram the messages that should be used to transport the information of the current radio environment: the full message sequences for UUS-1 are specified in TS 23.087 [15]. For this procedure to be successful, the network must handle the radio capability information transparently. + +![Sequence diagram showing the exchange of current radio environment information at CS call setup between UE-A and UE-B through various network domains.](c036e2540a94b31357ceb0002f0cacab_img.jpg) + +``` + +sequenceDiagram + participant UE-A + participant CS_Domain_A as CS Domain (A) + participant IMS_Core_A as IMS Core (A) + participant IMS_Core_B as IMS Core (B) + participant CS_Domain_B as CS Domain (B) + participant UE-B + + Note right of UE-B: 4a. UE-B may trigger to do the IMS registration based on preconfigured user's preference + + UE-A->>CS_Domain_A: 1. SETUP + CS_Domain_A->>IMS_Core_A: 2. IAM + IMS_Core_A->>CS_Domain_B: 3. SETUP + CS_Domain_B->>UE-B: 4. CONNECT + CS_Domain_B->>IMS_Core_B: 5. CON/ANM + IMS_Core_B->>CS_Domain_A: 6. CONNECT + Note left of UE-A: 7. UE-A takes the current radio environment information of UE-B into account when deciding whether to initiate further CSI procedures + Note left of UE-A: 7a. UE-A may trigger to do the IMS registration based on preconfigured user's preference + +``` + +Sequence diagram showing the exchange of current radio environment information at CS call setup between UE-A and UE-B through various network domains. + +Figure 8-1: Exchange of current radio environment information "at" CS call setup + +- 1) The UE-A initiates a CS call by sending a SETUP message towards UE-B, including the current radio environment information encoded in the User-User Signalling IE. +- 2) The CS domain of the originating network sends an IAM message including the current radio environment information of UE-A to the CS domain of the terminating network. Whether the MSC performs the procedures for UUS-1 (refer to TS 23.087 [15]), or, whether the MSC merely copies the User-User Signalling IE from the SETUP message into the IAM is implementation dependent. Additional MSC based policing of the UUS information content is also implementation dependent. + +- 3) The CS domain of the terminating network sends a SETUP message IAM including the current radio environment information of UE-A to the UE-B. Whether the GMSC and/or the VMSC performs the procedures for UUS-1, or, whether they merely copy the information into the User-User Signalling IE of the SETUP message from the IAM is implementation dependent. +- 4) The UE-B stores the current radio environment information of UE-A and sends the current radio environment information of UE-B in the final response to the SETUP message, i.e. the CONNECT message. UE-B takes the current radio environment information of UE-A into account when deciding what service options to present to the user and/or whether to initiate a UE capability information exchange, see clause 8.2. + +If UE-B find that UE-A and UE-A's current radio environment supports simultaneous CS and PS services and the IM Status indicates that an IMS communication is likely to be successful, then UE B should attempt an IMS registration (in case IMS registration had not previously been performed) based on preconfigured user's preference. + +NOTE: The radio environment information is only sent in the CONNECT message to avoid sending non-relevant information to the originating side, e.g. in case Call Forwarding on No Reply is active. + +- 5) The CS domain of the terminating network sends an ANM or CON message including the current radio environment information of UE-B to the CS domain of the originating network. +- 6) The CS domain of the originating network sends a CONNECT message including the current radio environment information of UE-B to the UE-A. +- 7) The UE-A takes the current radio environment information of UE-B received into account when deciding what service options to present to the user and/or whether to initiate a UE capability information exchange, see clause 8.2. + +If UE-A find that UE-B and UE-B's current radio environment supports simultaneous CS and PS services and the IM Status indicates that an IMS communication is likely to be successful, then UE-A should attempt an IMS registration (in case IMS registration had not previously been performed) based on preconfigured user's preference. + +## 8.2 Exchange of UE capability information + +This clause outlines the exchange of UE related capability information using the SIP OPTIONS procedure to minimize the amount of network signalling and resource usage as well as the number of failed SIP INVITE requests. It also allows an up-to-date indication to the user which capabilities he could add to the ongoing call. Note that UE capability information exchange at IMS session initiation is specified in clause 8.4. + +It shall be possible for a UE to request the SIP OPTIONS request to be sent to any other registered UE. In case of existing IMS session between UE-A and UE-B, to guarantee that SIP OPTIONS request is routed to UE-B, the SIP OPTIONS request should be sent as part of the existing IMS session. In case there is an ongoing CS call between UE-A and UE-B, it should be possible to provide a higher probability that the UE capability exchange is routed to the UE-B. + +As the SIP OPTIONS request include both the IMS Public User Identity in the form of an SIP URI and the MSISDN the procedure enables both UE-A and UE-B to correlate the IMS session with the CS call and within one context inform the user what capabilities the user is able to use. + +NOTE: If the UICC is not provisioned with the MSISDN the UE may get it during the IMS registration as an associated identity. + +The execution of this SIP OPTIONS request procedure is recommended when UE-A has not stored capability information for UE-B, or when UE-A has become aware that UE-B has changed its capabilities by comparing the stored and received UE capability version. + +A SIP OPTIONS may also be sent by UE-A to UE-B in case UE-A's capabilities have been updated. This request triggers UE-B to initiate SIP OPTIONS request towards UE-A to retrieve the updated capabilities. + +![Sequence diagram illustrating the Exchange of UE capability information between UE-A and UE-B via IMS Core (A) and IMS Core (B).](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant UE-A + participant CS Domain (A) + participant IMS Core (A) + participant IMS Core (B) + participant CS Domain (B) + participant UE-B + + Note right of IMS Core (B): 3. Routing decision based on caller preferences and callee capabilities + Note right of UE-B: 5. UE-B stores the address information of UE-A + Note left of UE-A: 9. UE-A updates or stores the received capability information of UE-B + + UE-A->>IMS Core (A): 1. OPTIONS + IMS Core (A)->>IMS Core (B): 2. OPTIONS + IMS Core (B)->>UE-B: 4. OPTIONS + UE-B-->>IMS Core (B): 6. 200 OK + IMS Core (B)->>IMS Core (A): 7. 200 OK + IMS Core (A)->>UE-A: 8. 200 OK + +``` + +Sequence diagram illustrating the Exchange of UE capability information between UE-A and UE-B via IMS Core (A) and IMS Core (B). + +**Figure 8-2: Exchange of UE capability information** + +- 1) UE-A sends an SIP OPTIONS request towards UE-B preferably using a SIP URI of UE-B, or a TEL URI, if no valid SIP URI is available. In case of an existing IMS session, the OPTIONS request should be sent as part of the existing session. Subject to privacy controls, in UE-A the SIP OPTIONS request shall contain MSISDN of UE-A, if available. +- 2) The IMS Core (A) performs the normal security procedures and forwards the SIP OPTIONS request towards IMS Core (B). If the destination address is in the format of a TEL URI, IMS Core (A) performs MSISDN to SIP URI translation as per clause 4.3.5 in TS 23.228 [2], before forwarding the SIP OPTIONS request to IMS Core (B). + +The IMS Core (A) should add the MSISDN of UE-A to the SIP OPTIONS request, if not included by UE-A. + +- 3) If the SIP OPTIONS request is not sent as part of an existing dialog, the IMS Core (B) makes a routing decision based on information in the caller preferences, as defined in RFC 3841 [19], in the SIP OPTIONS request and any registered caller capabilities, as defined in RFC 3840 [18], (e.g. CS-Voice or CS-Video). +- 4) The IMS Core (B) then forwards the SIP OPTIONS request to UE-B. If privacy is requested, IMS Core (B) shall remove the MSISDN of UE-A. +- 5) The UE-B stores the address information of UE-A. +- 6) The UE-B sends a 200 OK that, subject to UE-B's privacy settings contain the information outlined in clause 7.2.2. +- 7) The IMS Core (B) forwards the 200 OK to IMS Core (A). + +The IMS Core (B) should add the MSISDN of UE-B to the 200 OK, if not included by UE-B. + +- 8) The IMS Core (A) forwards the 200 OK to UE-A. If privacy is requested, IMS Core (A) shall remove the MSISDN of UE-B. +- 9) The UE-A stores or updates the UE capability information received and if not already available stores the address information of UE-B. + +For the capability exchange procedure to work properly UE-B should send an SIP OPTIONS request towards UE-A, in the following situations, provided that the associated conditions are met: + +1. An SIP INVITE request is received from UE-A, and + +- The SIP INVITE request received from UE-A did not include any UE's capabilities capability information, and + - UE-B has not stored capability information for UE-A's capabilities, or UE-B's capabilities have been updated e.g. UE-B has been upgraded with video capability or supports a new service, or; + - The UE capability version included in the SIP INVITE request received from UE-A is different from the previously stored UE-A's capability version. +2. UE-B is in a CS call with UE-A, and +- UE-B has not stored capability information for UE-A or has received a UE capability version different from previously stored UE-A's capability version from UE-A during CS call setup, and + - If received, the current radio environment information indicates that UE-A is capable of supporting CS and PS simultaneously. +3. A SIP OPTIONS request is received from UE-A, and +- There is no ongoing (or recently finished) UE-B initiated capability exchange with UE-A. + +NOTE: The received SIP OPTIONS is not a result of a recent UE-B capability version sent from UE-B. + +In the situations 1 and 2 above, a SIP OPTIONS request may also be sent by UE-B to UE-A in case UE-B's capabilities have been updated. This request triggers UE-A to initiate SIP OPTIONS request towards UE-B to retrieve the updated capabilities. + +## 8.3 User adds an IMS service to an ongoing CS call + +### 8.3.1 IMS session set up without media requiring resource reservation + +The following sequence diagram shows an IMS service being added to an ongoing CS call when the CSI capabilities of UE-B have not previously been stored by UE-A and are therefore exchanged after CS call setup. + +NOTE 1: The SIP session may setup any service based on IMS and normal requirements as per TS 23.228 [2] apply. + +![Sequence diagram showing the interaction between UE-A, CS Domain (A), IMS Core (A), IMS Core (B), CS Domain (B), and UE-B to add an IMS session to an ongoing CS call. The diagram includes 13 numbered steps: 1. CS Call Setup, 2. IMS Capability exchange (see Note), 3. INVITE, 4. INVITE, 5. INVITE, 6. User B accepts the service, 7. 200 OK, 8. 200 OK, 9. 200 OK, 10. ACK, 11. ACK, 12. ACK, and 13. Media session established. A note indicates that User A triggers an IMS service from a set of illuminated choices.](4356776ca004ecba5d599667a155d7d4_img.jpg) + +``` + +sequenceDiagram + participant UE-A + participant CS Domain (A) + participant IMS Core (A) + participant IMS Core (B) + participant CS Domain (B) + participant UE-B + + Note left of UE-A: User A triggers an IMS service from a set of illuminated choices + + UE-A->>IMS Core (A): 3. INVITE + IMS Core (A)->>IMS Core (B): 4. INVITE + IMS Core (B)->>UE-B: 5. INVITE + Note right of UE-B: 6. User B accepts the service + UE-B->>IMS Core (B): 7. 200 OK + IMS Core (B)->>IMS Core (A): 8. 200 OK + IMS Core (A)->>UE-A: 9. 200 OK + UE-A->>IMS Core (A): 10. ACK + IMS Core (A)->>IMS Core (B): 11. ACK + IMS Core (B)->>UE-B: 12. ACK + Note over all participants: 13. Media session established + +``` + +Sequence diagram showing the interaction between UE-A, CS Domain (A), IMS Core (A), IMS Core (B), CS Domain (B), and UE-B to add an IMS session to an ongoing CS call. The diagram includes 13 numbered steps: 1. CS Call Setup, 2. IMS Capability exchange (see Note), 3. INVITE, 4. INVITE, 5. INVITE, 6. User B accepts the service, 7. 200 OK, 8. 200 OK, 9. 200 OK, 10. ACK, 11. ACK, 12. ACK, and 13. Media session established. A note indicates that User A triggers an IMS service from a set of illuminated choices. + +**Figure 8.3-1: User adds an IMS session to an ongoing CS call** + +- 1) A CS call is setup as per clause 8.1. + - 2) The UE-A should initiate an IMS capability exchange as described in clause 8.2. +- NOTE 2: This step is only needed when UE-A does not have the UE-B IMS capabilities stored and vice versa. +- NOTE 3: The IMS Capability exchange will also include the correlation between the MSISDN and the SIP URI. +- 3) The UE-A shall send the SIP INVITE request to the IMS Core along the signalling path established during registration. + - 4) The IMS Core (A) forwards the INVITE request to IMS Core (B). + - 5) The IMS Core (B) forwards the INVITE request to UE-B. + - 6) The UE-B shall associate the INVITE request with the ongoing CS call by using the MSISDN and SIP URI, obtained through the IMS Capability exchange procedure and/or included in the INVITE request + - 7) The UE-B invokes the correct application, which associates the SIP session with the ongoing call by matching the identities used in the CS call and the SIP session. The UE-B then sends a 200 OK. + - 8) The IMS Core (B) forwards the 200 OK to IMS Core (A). + - 9) The IMS Core (A) forwards the 200 OK to UE-A. + - 10) The UE-A acknowledges the 200 OK. + - 11) The IMS Core (A) forwards the acknowledgement to IMS Core (B). + - 12) The IMS Core (B) forwards the acknowledgement to UE-B. + +13) Media as per the session setup is sent between the two UEs. + +### 8.3.2 IMS session set- up with media requiring resource reservation + +For an IMS session setup in the context of CSI it shall be possible to require media resource reservation as per procedures in TS 23.228 [2], illustrated in the use case below. + +The following sequence diagram shows an IMS service being added to an ongoing CS call when the CSI capabilities of UE-B have not previously been stored by UE-A and are therefore exchanged after CS call setup. Only media resource reservation based on the "inactive" mechanism is shown. + +![Sequence diagram showing the interaction between UE-A, CS Domain (A), IMS Core (A), IMS Core (B), CS Domain (B), and UE-B to add an IMS session to an ongoing CS call. The process involves CS call setup, IMS capability exchange, and a two-stage INVITE/200 OK/ACK exchange (inactive then active) to establish the media session.](12de9b926df0384ec07702671827c9cd_img.jpg) + +``` + +sequenceDiagram + participant UE-A + participant CS_Domain_A as CS Domain (A) + participant IMS_Core_A as IMS Core (A) + participant IMS_Core_B as IMS Core (B) + participant CS_Domain_B as CS Domain (B) + participant UE-B + + Note left of UE-A: User A triggers an IMS service from a set of illuminated choices + + UE-A->>CS_Domain_A: 1. CS Call Setup + CS_Domain_A->>IMS_Core_A: + IMS_Core_A->>IMS_Core_B: + IMS_Core_B->>CS_Domain_B: + CS_Domain_B->>UE-B: + Note right of UE-B: 6. UE-B associate the INVITE with the CS call + + UE-A->>IMS_Core_A: 2. IMS Capability exchange (see Note) + IMS_Core_A->>IMS_Core_B: + IMS_Core_B->>CS_Domain_B: + CS_Domain_B->>UE-B: + + Note left of UE-A: bearer set up + UE-A->>IMS_Core_A: 3. INVITE(inactive) + IMS_Core_A->>IMS_Core_B: 4. INVITE(inactive) + IMS_Core_B->>CS_Domain_B: 5. INVITE(inactive) + CS_Domain_B->>UE-B: + UE-B->>CS_Domain_B: 7. 200 OK (inactive) + CS_Domain_B->>IMS_Core_B: + IMS_Core_B->>IMS_Core_A: 8. 200 OK (inactive) + IMS_Core_A->>UE-A: 9. 200 OK (inactive) + UE-A->>IMS_Core_A: 10. ACK + IMS_Core_A->>IMS_Core_B: 11. ACK + IMS_Core_B->>CS_Domain_B: 12. ACK + CS_Domain_B->>UE-B: + Note right of UE-B: bearer set up + UE-A->>IMS_Core_A: 13. INVITE(active) + IMS_Core_A->>IMS_Core_B: 14. INVITE(active) + IMS_Core_B->>CS_Domain_B: 15. INVITE(active) + CS_Domain_B->>UE-B: + Note right of UE-B: 16. User B accepts the service + UE-B->>CS_Domain_B: 17. 200 OK (active) + CS_Domain_B->>IMS_Core_B: + IMS_Core_B->>IMS_Core_A: 18. 200 OK (active) + IMS_Core_A->>UE-A: 19. 200 OK (active) + UE-A->>IMS_Core_A: 20. ACK + IMS_Core_A->>IMS_Core_B: 21. ACK + IMS_Core_B->>CS_Domain_B: 22. ACK + CS_Domain_B->>UE-B: + Note right of UE-B: 23. Media session established + +``` + +Sequence diagram showing the interaction between UE-A, CS Domain (A), IMS Core (A), IMS Core (B), CS Domain (B), and UE-B to add an IMS session to an ongoing CS call. The process involves CS call setup, IMS capability exchange, and a two-stage INVITE/200 OK/ACK exchange (inactive then active) to establish the media session. + +**Figure 8.3-2: User adds an IMS session to an ongoing CS call** + +- 1) A CS call is setup as per clause 8.1. +- 2) The UE-A should initiate an IMS capability exchange as described in clause 8.2. If UE-B does not receive any IMS capability exchange from UE-A within a certain time limit the UE-B should initiate the IMS capability exchange, if required. + +NOTE 1: This step is only needed when UE-A does not have the UE-B IMS capabilities stored and vice versa. + +NOTE 2: The IMS Capability exchange will also include the correlation between the MSISDN and the SIP URI. + +- 3) The UE-A shall send the SIP INVITE request with the media components marked "inactive" to the IMS Core along the signalling path established during registration. +- 4) The IMS Core (A) forwards the INVITE request to IMS Core (B). +- 5) The IMS Core (B) forwards the INVITE request to UE-B. +- 6) The UE-B shall associate the INVITE request with the ongoing CS call by using the MSISDN and SIP URI, obtained through the IMS Capability exchange procedure and/or included in the INVITE request. If required, UE-B immediately initiates IP-CAN bearer setup. No alerting of user B needs to be carried out. +- 7) The UE-B directly sends a 200 OK with the media components marked 'inactive'. +- 8) The IMS Core (B) forwards the 200 OK to IMS Core (A). +- 9) The IMS Core (A) forwards the 200 OK to UE-A. +- 10) The UE-A initiates IP-CAN bearer setup for the media and acknowledges the 200 OK. +- 11) The IMS Core (A) forwards the acknowledgement to IMS Core (B). +- 12) The IMS Core (B) forwards the acknowledgement to UE-B. +- 13) The UE-A shall send the SIP INVITE request with the media components marked "active" to the IMS core when the IP-CAN bearer is established on UE-A access. +- 14) The IMS Core (A) forwards the INVITE request to IMS Core (B). +- 15) The IMS Core (B) forwards the INVITE request to UE-B. +- 16) The UE-B shall perform necessary service action to receive/send user plane media. +- 17) The UE-B shall send 200 OK with the media components marked 'active' when the IP-CAN bearer is setup and the UE is ready to receive media. +- 18) The IMS Core (B) forwards the 200 OK to IMS Core (A). +- 19) The IMS Core (A) forwards the 200 OK to UE-A. +- 20) The UE-A acknowledges the 200 OK. +- 21) The IMS Core (A) forwards the acknowledgement to IMS Core (B). +- 22) The IMS Core (B) forwards the acknowledgement to UE-B. +- 23) User plane connection is established. + +## 8.4 User adds a CS call to an ongoing IMS session + +![Sequence diagram showing the interaction between UE-A, CS Domain (A), IMS Core (A), IMS Core (B), CS Domain (B), and UE-B for adding a CS call to an ongoing IMS session. The diagram is divided into two main parts: the initial IMS session setup (steps 1-6) and the subsequent CS call setup (steps 8-16), with a continuation of the IMS flow in between (step 7).](a3472689858b068ef469213682965325_img.jpg) + +``` + +sequenceDiagram + participant UE-A + participant CS-A as CS Domain (A) + participant IMS-A as IMS Core (A) + participant IMS-B as IMS Core (B) + participant CS-B as CS Domain (B) + participant UE-B + + Note right of UE-B: UE recognises calling party number as negotiated in SIP session setup + + UE-A->>IMS-A: 1. INVITE (Requested Services, Current CSI Capabilities, MSISDN) + IMS-A->>IMS-B: 2. INVITE (Requested Services, Current CSI Capabilities, MSISDN) + IMS-B->>UE-B: 3. INVITE (Requested Services, Current CSI Capabilities, MSISDN) + UE-B-->>IMS-B: 4. 200 OK (Requested Services (subset), Current CSI Capabilities (subset), MSISDN) + IMS-B-->>IMS-A: 5. 200 OK (Requested Services (subset), Current CSI Capabilities (subset), MSISDN) + IMS-A-->>UE-A: 6. 200 OK (Requested Services (subset), Current CSI Capabilities (subset), MSISDN) + + Note over all: 7. Call flow continues as per standard IMS flow + + UE-A->>CS-A: 8. SETUP + CS-A->>CS-B: 9. IAM + CS-B->>UE-B: 10. SETUP + UE-B-->>CS-B: 11. ALERTING + CS-B-->>IMS-B: 12. ACM + IMS-B-->>CS-A: 15. ANM + CS-A-->>UE-A: 13. ALERTING + UE-B-->>CS-B: 14. CONNECT. + CS-A-->>UE-A: 16. CONNECT + +``` + +Sequence diagram showing the interaction between UE-A, CS Domain (A), IMS Core (A), IMS Core (B), CS Domain (B), and UE-B for adding a CS call to an ongoing IMS session. The diagram is divided into two main parts: the initial IMS session setup (steps 1-6) and the subsequent CS call setup (steps 8-16), with a continuation of the IMS flow in between (step 7). + +**Figure 8.4-1: User adds a CS call to an ongoing IMS Session** + +- 1) The UE-A sends the SIP INVITE request to the IMS Core (A) using the address obtained during registration. + +The SIP INVITE may contain CSI specific information including MSISDN and current CSI capabilities in addition to the standard information for the desired IMS service. + +- 2) The IMS-Core (A) forwards the SIP INVITE request to the IMS Core (B) +- 3) The IMS-Core (B) forwards the SIP INVITE request to UE-B. +- 4) The UE-B should send a provisional response i.e. 18x (or a final response) and include the MSISDN of UE-B. If the session includes media requiring resource reservation then same principles apply as described in clause 8.3.2, except that the UE-B should reply with a provisional response to allow the user to answer from other UEs. +- 5) The IMS Core (B) forwards the provisional or final response to IMS Core (A). +- 6) The IMS Core (A) forwards the provisional or final response to UE-A +- 7) The IMS flow continues as standard. +- 8) The UE-A initiates a CS call by sending a SETUP message towards UE-B. +- 9) The CS domain of the originating network sends an IAM message to the CS domain of the terminating network. + +10) The CS domain of the terminating network sends a SETUP message IAM of UE-A to the UE-B. + +UE-B recognises the calling party number as negotiated in SIP session setup. + +NOTE: Without exchanging radio capabilities in IMS, the PS connection could be suspended. From the user experience perspective this is considered as acceptable. + +11) The UE-B sends ALERTING message to UE-A. + +12) The CS domain of the terminating network sends an ACM message to the CS domain of the originating network. + +13) The CS domain of the originating network sends an ALERTING message to the UE-A. + +14) The UE-B sends CONNECT message to UE-A. + +15) The CS domain of the terminating network sends an ANM message to the CS domain of the originating network. + +16) The CS domain of the originating network sends a CONNECT message to the UE-A. + +## 8.5 Release of CSI + +The UE shall release the CS call and the IMS session independently of each other. + +## 8.6 Terminating a Multimedia IMS session to a CSI UE + +Figure 8.6-1 describes the call flow for a multimedia session (e.g. with both voice and messaging components of IMS origination and CSI termination. The assumption is that UE 1 is both CS attached and IMS domain registered. Also, the MSRP protocol is used for transporting the messaging component. Note that the procedure below is simplified for clarity, e.g. some entities are omitted, but the normal IMS procedure for IMS/CS interworking procedure shall be applied. + +![Sequence diagram showing the call flow for terminating a multimedia IMS session to a CSI UE. The diagram is divided into two main sections: 'CSI termination' and 'IMS origination'. The participants are UE 1, CS Domain 1, S-CSCF 1, CSI AS, MGCF/MGW, S-CSCF 2, and UE 2. The sequence of messages is as follows: 1. INVITE (Voice + MSRP) from UE 2 to S-CSCF 2; 2. INVITE (Voice + MSRP) from S-CSCF 2 to S-CSCF 1; 3. INVITE (Voice + MSRP) from S-CSCF 1 to CSI AS; 4. Termination logic (internal to CSI AS); 5. INVITE (Voice) from CSI AS to S-CSCF 1; 6. INVITE (Voice) from S-CSCF 1 to MGCF/MGW; 7. IAM from MGCF/MGW to CS Domain 1; 8. SETUP from CS Domain 1 to UE 1; 9. INVITE (MSRP) from S-CSCF 1 to CSI AS; 10. INVITE (MSRP) from CSI AS to S-CSCF 1; 11. CONNECT from UE 1 to CS Domain 1; 12. CON from S-CSCF 1 to MGCF/MGW; 13. 200 OK (for Voice) from MGCF/MGW to S-CSCF 1; 14. 200 OK (for Voice) from S-CSCF 1 to CSI AS; 15. 200 OK (for MSRP) from S-CSCF 1 to CS Domain 1; 16. 200 OK (for MSRP) from CS Domain 1 to S-CSCF 1; 17. 200 OK (for Voice + MSRP) from S-CSCF 1 to CSI AS; 18. 200 OK (for Voice + MSRP) from CSI AS to S-CSCF 2; 19. 200 OK (for Voice + MSRP) from S-CSCF 2 to UE 2. Below the messages, three horizontal double-headed arrows indicate the bearers: 20. CS voice bearer between UE 1 and MGCF/MGW; 20. VoIP voice bearer between MGCF/MGW and UE 2; 20. User plane for MSRP between UE 1 and UE 2.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Sequence diagram showing the call flow for terminating a multimedia IMS session to a CSI UE. The diagram is divided into two main sections: 'CSI termination' and 'IMS origination'. The participants are UE 1, CS Domain 1, S-CSCF 1, CSI AS, MGCF/MGW, S-CSCF 2, and UE 2. The sequence of messages is as follows: 1. INVITE (Voice + MSRP) from UE 2 to S-CSCF 2; 2. INVITE (Voice + MSRP) from S-CSCF 2 to S-CSCF 1; 3. INVITE (Voice + MSRP) from S-CSCF 1 to CSI AS; 4. Termination logic (internal to CSI AS); 5. INVITE (Voice) from CSI AS to S-CSCF 1; 6. INVITE (Voice) from S-CSCF 1 to MGCF/MGW; 7. IAM from MGCF/MGW to CS Domain 1; 8. SETUP from CS Domain 1 to UE 1; 9. INVITE (MSRP) from S-CSCF 1 to CSI AS; 10. INVITE (MSRP) from CSI AS to S-CSCF 1; 11. CONNECT from UE 1 to CS Domain 1; 12. CON from S-CSCF 1 to MGCF/MGW; 13. 200 OK (for Voice) from MGCF/MGW to S-CSCF 1; 14. 200 OK (for Voice) from S-CSCF 1 to CSI AS; 15. 200 OK (for MSRP) from S-CSCF 1 to CS Domain 1; 16. 200 OK (for MSRP) from CS Domain 1 to S-CSCF 1; 17. 200 OK (for Voice + MSRP) from S-CSCF 1 to CSI AS; 18. 200 OK (for Voice + MSRP) from CSI AS to S-CSCF 2; 19. 200 OK (for Voice + MSRP) from S-CSCF 2 to UE 2. Below the messages, three horizontal double-headed arrows indicate the bearers: 20. CS voice bearer between UE 1 and MGCF/MGW; 20. VoIP voice bearer between MGCF/MGW and UE 2; 20. User plane for MSRP between UE 1 and UE 2. + +**Figure 8.6-1: Call flow for terminating a multimedia IMS session to a CSI UE** + +The procedure is as follows: + +1. UE 2 initiates the multimedia session for voice and MSRP by sending an INVITE message towards UE 1. +2. The S-CSCF 2 of the originating network sends the INVITE message for the voice and MSRP to the S-CSCF 1 of the terminating network. +3. Triggered by the applicable iFC, the S-CSCF 1 of terminating network sends the INVITE message for the voice and MSRP to the CSI AS. + +4. The CSI AS invokes the Termination Logic (see clause 6.2) that decides to split the original IMS session into two sessions: One with the voice media component that will be terminated via the CS domain 1 of the terminating network and another with the messaging component that will be terminated via the PS domain. The CSI AS acts as a 3rd party call control entity for initiating and controlling these two sessions. +5. The CSI AS initiates the first session with the voice component by sending an INVITE message to S-CSCF 1 containing a Tel URI corresponding to UE 1 and any additional information to terminate the session in the CS domain. +- 6-8. and 11-14. Normal IMS/CS interworking functionality is invoked and a CS voice call is established toward UE 1 via CS domain 1 of the terminating network. +9. The CSI AS initiates the second session with the messaging component by sending an INVITE message to S-CSCF 1 containing a SIP URI corresponding to UE 1. CSI AS uses any information available to ensure to send the second session to the same terminating UE as the destination of the voice call. +10. and 15-16. UE 1 accepts the messaging session by sending a 200 OK message to CSI AS. +- 17-19. The CSI AS accepts the original INVITE message from UE 2 by sending to UE 2 a 200 OK response. +20. Finally, the CS voice bearer, the PS VoIP bearer, and the PS MSRP bearer are created. + +NOTE: The MSRP media could go through the CSI AS. + +# --- 9 Interaction with supplementary services + +## 9.1 General + +CS supplementary services apply to the CS component of the CSI call only. The present clause describes how best to configure and utilize CS Supplementary Services in the context of CSI. + +NOTE: The CS supplementary services are defined in TS 23.081 [3] (Line Identification), TS 23.082 [8] (Call Forwarding), TS 23.083 [9] (Call Waiting and Hold), TS 23.088 [11] (Barring) and TS 23.091 [12] (Explicit Call Transfer). + +This TS covers only the Supplementary Services that are identified as having an impact on CSI within the current release as stated in TS 22.279 [13]. + +## 9.2 Line Identification + +### 9.2.1 Calling Line Identity Presentation (CLIP) + +It is beneficial to utilize CLIP in the context of CSI. + +- 1) The called party uses the CLI of the calling party to correlate an incoming SIP INVITE with the CS call. +- 2) When the called party wishes to establish an IMS session with the calling party in the context of the CS call, the called party uses the CLI of the calling party to derive the destination URI of the IMS session. The UE may use the CLI as TEL URL or may use the CLI to derive a SIP URI. + +### 9.2.2 Calling Line Identification Restriction (CLIR) + +If the calling party is subscribed to the automatic suppression of the presentation of her CLI, then it must be anticipated that the network must also automatically suppress her "IMS CLI", and, that her UE shall not reveal her CLI to other parties without her explicit permission. This can be achieved by either: + +- a) The network operator refuses to give an IMS subscription to her. +- b) Appropriate mechanism for the HSS to control the removal of "CLI" based on subscription information. + +NOTE: Point B is related to an IETF privacy mechanism and is identified as a generic IMS issue, not one specifically related to CSI. As this causes subscriber information to be sent around more than usual, it will be worked on as a generic IMS issue within 3GPP. + +The calling party may also wish to use CLIR on a "per call" basis. In this case, the UE shall not include any CLI information in any OPTIONS data exchange linked to the CS call. + +There are several mechanisms that can be imagined for the UEs to swap static terminal information as a background task, e.g., outside of CS calls and 'user initiated' IMS sessions. Because the E.164/identity information may need to be restricted from transmission to certain destinations, the UE shall ensure that the user's permission is obtained before such sensitive information is transmitted. + +Given that CLIP is highly desirable and useful for CSI, it is accepted that the use of CLIR causes significant degradation to the overall user experience in case of CSI. + +### 9.2.3 Connected Line Identification Presentation (COLP) + +It is beneficial to utilize COLP in the context of CSI: + +- 1) The calling party uses the COL of the connected party to correlate an incoming SIP INVITE with the CS call. +- 2) When the calling party wishes to establish an IMS session with the connected party, the calling party uses the COL of the called party as the destination URI of the IMS session. The UE may use the COL as TEL URI or may use the COL to derive a SIP URI. + +NOTE: The availability of the COL may be affected by Call Forwarding GSM supplementary service, regulations and network services such as IN. + +### 9.2.4 Connected Line Identification Restriction (COLR) + +If the presentation of her COL is suppressed by means of a subscription or on a per call basis, then automatic combination of the IMS session and the CS call is unavailable. Note that user can still manually combine the CS call and the IMS session. + +## 9.3 Call Forwarding + +When a call is subject to CS call forwarding, the calling party is notified that the call has been forwarded. In CS first scenario, when the user would like to establish an IMS session that is to be automatically combined with this call then the user initiates the IMS session to the forwarded-to user. In IMS first scenario, if the UE can not associate the Public User Identity of the remote UE (of the IMS session) with the COL of the CS connected party, the UE realizes that the CS call can't be established in context of the existing IMS session and appropriately notifies the user. + +Call forwarding may result in the restriction of the presentation of the COL, depending on subscriber option settings. Refer to the clause on Line Identification for the usage of the CLI and COL for establishing an IMS session associated with the CS call and for correlating an incoming IMS session with the CS call. + +For CSI termination scenario, if CSI AS gets the information that the CS call is forwarded, (e.g. MGCF gets this information from the COL number in CS Connect message and sends it to CSI AS), or CSI AS gets the information that the IMS session is forwarded/will be forwarded, it may decide what the further action will be based on local policy, i.e. keep the successfully established CS call or/and IMS session with the calling party. + +## 9.4 Call Offering + +### 9.4.1 Explicit Call Transfer (ECT) + +If a UE has an ongoing IMS session with one of two parties and invokes ECT, the end user may keep or terminate this IMS session when ECT is invoked. + +The two parties that have established a CS session after ECT will not have each others line identification and are therefore incapable of establishing a CSI call / session. + +If the IMS session is established prior to the establishment of the CS call/session, then the two parties will not have each others line identification and are therefore incapable of establishing a CSI call/session. + +## 9.5 Call Completion + +### 9.5.1 Call Waiting (CW) and Call Hold (CH) + +When a subscriber (calling or called) is engaged in a CS call and a second call is offered to her (Call Waiting), an IMS session may be ongoing between that subscriber and her speech partner of the ongoing call. The offering of the second call (i.e. the alerting) does not affect the ongoing IMS session. + +When a subscriber (calling or called) receives a CS call when already engaged in another CS call, then she may act as follows. + +- a) Reject the incoming call. This action does not affect the IMS session of the active call. +- b) Release the first CS call and answer the second CS call. The user may decide whether to keep the IMS session that was established in the context of the first CS call. The user may also decide to establish a new IMS session to be combined with the second CS call. +- c) Invoke Call Hold. The first call is placed on hold and the second call is answered. The following options apply to the IMS session for the first call: + +Option I: The IMS session is retained, but the sending and receiving of streaming data is suspended. + +Option II: The IMS session is retained and the sending and receiving of non real-time data continues. + +Similar principles apply to the case where A-party places an ongoing call on hold and establishes a second CS call. + +For CSI termination scenario, if the CSI AS gets the information that CS call is being held/retrieved (e.g. MGCF maps CS Call Hold/Call Retrieve signalling into SIP message and sends it to CSI AS), or the CSI AS gets the information that the non voice media is suspended/resumed, it may initiate session modification request to perform corresponding media modification towards the peer IMS UE. + +## 9.6 Call Barring + +If a CS call is barred, then IMS sessions in the context of the CS call are not applicable. + +If an IMS session is active and the user intends to establish a CS call, then Call Barring categories apply. + +For CSI termination scenario, if the CSI AS cannot establish a voice call/IMS session with the CSI capable UE, e.g. due to Call Barring service, it may remove the voice/non voice component by negotiating /renegotiating media with the calling party. + +# --- 10 Other considerations + +## 10.1 Handover + +- Handover from DTM GERAN or UTRAN to non-DTM GERAN +If, during a simultaneous IMS session and CS call between two end-users, one of the end-users makes an intersystem handover into a non-DTM GERAN access, in this case the data traffic on the PDP contexts are handled as per procedures described in TS 23.060 [10]. +- Handover from non-DTM GERAN to DTM GERAN or UTRAN +When a UE is participating in a CS call and not able to operate in Class A mode of operation, the UE cannot perform IMS capability exchange procedures. When the UE is again able to operate in Class A mode of operation, the UE can perform the IMS capability exchange procedures during the CS call, if required according to procedures outlined in clauses 7 and 8. + +## 10.2 Relation to SMS + +A user should be able to send or receive SMS during an ongoing CSI session. SMS is in general treated independently from CSI. + +# Annex A (Informative): Support of CSI origination towards IMS termination with CSI interworking + +## A.1 Introduction + +This annex describes the flows and architecture for CSI originations towards IMS termination with CSI interworking. + +CSI interworking is the ability to perform the interworking between e.g. a pure IMS voice/video session and a combination of a CS call and an IMS session. + +## A.2 Overview + +CSI interworking from CSI origination to IMS termination is required to enable communication from UE's support CSI towards UEs supporting IMS termination. CSI interworking can be implemented in two different ways: + +- 1) CSI interworking can also be achieved in the terminating terminal if the operator has control of the terminal. This is beyond the scope of this document. +- 2) CSI Interworking is detected and performed in the originating network. +- 3) CSI Interworking is detected and performed in the terminating network. + +## A.3 Procedures + +### A.3.1 General Architecture + +Figures A.1 and A.2 show an architecture for the general architecture for CSI interworking when CSI origination and IMS termination is used for the CSI interworking with the support of interworking in the network. Figure A.1 shows the case where the CSI interworking is performed in the originating network, and figure A.2 shows the case where the CSI interworking is performed in the terminating network. + +![Figure A.1: General architecture and signalling flow in case of CSI origination and IMS termination with CSI interworking in originating network. The diagram shows two main sections: 'CSI Origination' on the left and 'IMS termination' on the right, separated by a dashed vertical line. In the CSI Origination section, UE 1 contains a CS (Circuit Switched) and IMS (IP Multimedia Subsystem) unit. The CS unit connects to an xRAN, which connects to a CS domain 1. The IMS unit connects to an xRAN, which connects to a PS domain 1. Both the CS domain 1 and PS domain 1 connect to a CSI AS (CSI Application Server) in the IMS domain 1. A blue arrow (Multimedia IMS session) originates from the CS domain 1 and points to the CSI AS. A green arrow (IMS session) originates from the PS domain 1 and points to the CSI AS. A red arrow (CS call) originates from the CS domain 1 and points to the CSI AS. The CSI AS connects to the IMS domain 2 via an Mw interface. The IMS domain 2 connects to a PS domain 2, which connects to an xRAN, which connects to UE 2. UE 2 contains an IMS unit. A blue arrow (Multimedia IMS session) originates from the IMS domain 2 and points to the IMS unit in UE 2. A legend at the bottom right identifies the arrows: blue for Multimedia IMS session (for voice and other), red for CS call (for voice), and green for IMS session (for other).](803776dff64331076ffc951fc95358ee_img.jpg) + +Figure A.1: General architecture and signalling flow in case of CSI origination and IMS termination with CSI interworking in originating network. The diagram shows two main sections: 'CSI Origination' on the left and 'IMS termination' on the right, separated by a dashed vertical line. In the CSI Origination section, UE 1 contains a CS (Circuit Switched) and IMS (IP Multimedia Subsystem) unit. The CS unit connects to an xRAN, which connects to a CS domain 1. The IMS unit connects to an xRAN, which connects to a PS domain 1. Both the CS domain 1 and PS domain 1 connect to a CSI AS (CSI Application Server) in the IMS domain 1. A blue arrow (Multimedia IMS session) originates from the CS domain 1 and points to the CSI AS. A green arrow (IMS session) originates from the PS domain 1 and points to the CSI AS. A red arrow (CS call) originates from the CS domain 1 and points to the CSI AS. The CSI AS connects to the IMS domain 2 via an Mw interface. The IMS domain 2 connects to a PS domain 2, which connects to an xRAN, which connects to UE 2. UE 2 contains an IMS unit. A blue arrow (Multimedia IMS session) originates from the IMS domain 2 and points to the IMS unit in UE 2. A legend at the bottom right identifies the arrows: blue for Multimedia IMS session (for voice and other), red for CS call (for voice), and green for IMS session (for other). + +NOTE: When to support interworking in the originating network is a matter of policy in the home operator originating network. Such policy could take into account the destination network. + +**Figure A.1: General architecture and signalling flow in case of CSI origination and IMS termination with CSI interworking in originating network** + +![Figure A.2: General architecture and signalling flow in case of CSI origination and IMS termination with CSI level interworking in terminating network. The diagram shows two network domains separated by a dashed line. On the left, 'CSI Origination' includes UE 1 with CS and IMS components, connected to an xRAN, which is further connected to a 'CS domain 1' and a 'PS domain 1'. UE 1's IMS component connects to 'IMS domain 1'. On the right, 'IMS termination' includes UE 2 with IMS components, connected to an xRAN, which connects to a 'PS domain 2' and then to 'IMS domain 2'. A 'CSI AS' (CSI Application Server) is located within 'IMS domain 2'. Signalling flows are shown as follows: a yellow line (CS call) from UE 1's CS component through the xRAN and CS domain 1 to the CSI AS; a green line (IMS session for other services) from UE 1's IMS component through the xRAN, PS domain 1, and IMS domain 1 to the CSI AS; and a blue line (Multimedia IMS session) from the CSI AS through IMS domain 2, PS domain 2, and the xRAN to UE 2's IMS component. Interface labels include Uu/Um between UE 1 and xRAN, Gm between IMS and PS domains, and Mw between IMS domain 1 and IMS domain 2.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +Legend: + +- Blue line: Multimedia IMS session (for voice and other) +- Yellow line: CS call (for voice) +- Green line: IMS session (for other) + +Figure A.2: General architecture and signalling flow in case of CSI origination and IMS termination with CSI level interworking in terminating network. The diagram shows two network domains separated by a dashed line. On the left, 'CSI Origination' includes UE 1 with CS and IMS components, connected to an xRAN, which is further connected to a 'CS domain 1' and a 'PS domain 1'. UE 1's IMS component connects to 'IMS domain 1'. On the right, 'IMS termination' includes UE 2 with IMS components, connected to an xRAN, which connects to a 'PS domain 2' and then to 'IMS domain 2'. A 'CSI AS' (CSI Application Server) is located within 'IMS domain 2'. Signalling flows are shown as follows: a yellow line (CS call) from UE 1's CS component through the xRAN and CS domain 1 to the CSI AS; a green line (IMS session for other services) from UE 1's IMS component through the xRAN, PS domain 1, and IMS domain 1 to the CSI AS; and a blue line (Multimedia IMS session) from the CSI AS through IMS domain 2, PS domain 2, and the xRAN to UE 2's IMS component. Interface labels include Uu/Um between UE 1 and xRAN, Gm between IMS and PS domains, and Mw between IMS domain 1 and IMS domain 2. + +**Figure A.2: General architecture and signalling flow in case of CSI origination and IMS termination with CSI level interworking in terminating network** + +The solid lines present the signalling flow between UE 1 and UE 2. The voice call (yellow line) which is initiated by UE 1 is routed to the CSI-AS, while the IMS session for other services is also routed to the CSI-AS. The CSI-AS continues the communication towards UE 2 with a single session using normal IMS routing procedure. The above examples illustrate the interworking in both originating and the terminating networks and further consideration is required in order to determine whether the CSI-AS is in the originating network, terminating network or both. + +NOTE: This is for the case when the UE in CSI origination is not subscribing the VCC service. + +### A.3.3 Call flows for setting up the voice session for CSI origination and IMS termination with CSI interworking + +Figure A.3 shows the flows for establishing the voice session for CSI origination and IMS termination with the interworking performed in the originating network. The flow is simplified and omits elements such as I-CSCF and HSS from IMS Core B. + +![Sequence diagram illustrating CSI interworking on the originating side for CSI origination. The diagram shows the interaction between UE, VMSC, MGCF, I-CSCF, S-CSCF, CSI-AS, gsmSCF, CAMEL Svc, CSAF, and IMS Core B. The process involves setup, IDP, routing to IMS, connect, IAM, and multiple INVITE messages.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant UE + participant VMSC + participant MGCF + participant I-CSCF + participant S_CSCF as S-CSCF + participant CSI_AS as CSI-AS + participant gsmSCF + participant CAMEL_Svc as CAMEL Svc + participant CSAF + participant IMS_Core_B as IMS Core B + + UE->>VMSC: 1. Setup (B-party DN) + VMSC->>gsmSCF: 2. IDP () + rect rgb(255, 255, 255) + Note over gsmSCF, CAMEL_Svc: 3. Rerouting to IMS + end + gsmSCF->>VMSC: 4. Connect (IMRN) + VMSC->>MGCF: 5. IAM (IMRN) + MGCF->>I-CSCF: 6. INVITE (IMRN) + + rect rgb(255, 255, 255) + Note over I-CSCF, CSAF: 7a1. INVITE (IMRN) + I-CSCF->>S_CSCF: + S_CSCF->>CSI_AS: + CSI_AS->>S_CSCF: + Note over I-CSCF, CSAF: 7a2. INVITE (IMRN) + S_CSCF->>CSAF: + Note over I-CSCF, CSAF: 7b. INVITE (IMRN) + I-CSCF->>CSAF: + end + + rect rgb(255, 255, 255) + Note over CSAF, IMS_Core_B: 8. CS origination processing + end + + CSAF->>S_CSCF: 9. INVITE (B-party DN) + S_CSCF->>CSI_AS: 10. INVITE (B-party DN) + CSI_AS->>S_CSCF: + S_CSCF->>I-CSCF: 11. INVITE (B-party DN) + I-CSCF->>IMS_Core_B: 12. INVITE (B-party DN) + +``` + +Sequence diagram illustrating CSI interworking on the originating side for CSI origination. The diagram shows the interaction between UE, VMSC, MGCF, I-CSCF, S-CSCF, CSI-AS, gsmSCF, CAMEL Svc, CSAF, and IMS Core B. The process involves setup, IDP, routing to IMS, connect, IAM, and multiple INVITE messages. + +**Figure A.3: CSI interworking on originating side for CSI origination** + +NOTE: The functionality of the CAMEL Svc and CSAF are the same as described in TS 23.206 [17]. + +1. The CSI user originates a voice call in the CS domain using a CSI UE to party-B. + 2. Origination triggers at the VMSC are detected; VMSC sends an Initial DP message towards the gsmSCF. + 3. The gsmSCF invokes the CSI interworking Application's CAMEL Service that determines that the call needs to be interworked to IMS for CSI; thus, the CAMEL Service interworks the call to the IMS by allocating an IMRN and returning it to the gsmSCF; otherwise it responds with a CAP Continue. +- NOTE: How the information available to the CAMEL Service is used to decide whether the call should be routed through the IMS is implementation specific. +4. The gsmSCF responds with a CAP Connect message containing the Original Called party ID and Destination Routing Address. Destination Routing Address contains the IMRN to route the call to the CSAF. Handling of Destination Routing Address and Original Called party ID is as defined in TS 23.078 [16]. + 5. The VMSC routes the call towards the user's home IMS network using the IMRN via an MGCF in the home network. + 6. The MGCF initiates an INVITE towards the I-CSCF in the home IMS of the originating CSI user. The calling party number and/or original called number are included in the INVITE if they are received from the PSTN call setup signalling (e.g. ISUP). + 7. The I-CSCF routes the INVITE based on one of the following standard procedures specified in "PSI based Application Server termination - direct" and "PSI based Application Server termination – indirect" procedures in TS 23.228 [2]. + - 7a. The I-CSCF forwards the INVITE to the CSAF via the S-CSCF that is assigned to the IMRN. + - 7b. The I-CSCF forwards the INVITE directly to the CSAF. + +8. If, when the INVITE arrives at the CSI Interworking Application, it is processed by the CSAF of the CSI Interworking Application that may use the IMRN to retrieve the original called party number and the calling party number from the CAMEL Service. The CSAF uses the original called number and the calling party number to setup the outgoing call leg to party-B in accordance with the AS origination procedure defined in clause 5.6.5 of TS 23.228 [2]. +9. The CSAF sends the INVITE back to the S-CSCF for completion of the call toward the remote end. +10. The S-CSCF forwards the INVITE to the CSI-AS +11. The CSI-AS forwards the INVITE to the S-CSCF. +12. The CSI-AS forwards the INVITE to the IMS Core B. + +The rest of the call is established as per normal SIP signalling with interworking towards the CS domain. The voice call is considered to be established. + +Figure A.4 shows the flows for establishing the voice session for CSI origination and IMS termination with the interworking performed in the terminating network. The flow is simplified and omits elements such as I-CSCF and HSS. + +![Sequence diagram illustrating CSI interworking on the terminating side for CSI origination. The diagram is divided into two main sections: 'Originating side for CSI origination' and 'Terminating side for IMS session'. The originating side includes UE1, CS domain 1, and S-CSCF1. The terminating side includes CSI-AS2, MGCF/MGW, S-CSCF2, and UE2. The sequence of messages is: 1. SETUP from UE1 to CS domain 1; 2. IAM from CS domain 1 to MGCF/MGW; 3. INVITE from MGCF/MGW to S-CSCF2; 4. INVITE from S-CSCF2 to CSI-AS2; 5. Service Logic interaction between CSI-AS2 and MGCF/MGW; 6. INVITE from CSI-AS2 to S-CSCF2; 7. INVITE from S-CSCF2 to UE2; 8. 200OK from UE2 to S-CSCF2; 9. 200OK from S-CSCF2 to CSI-AS2; 10. 200OK from CSI-AS2 to MGCF/MGW; 11. 200OK from MGCF/MGW to S-CSCF2; 12. CON from S-CSCF2 to CS domain 1; 13. CONNECT from CS domain 1 to UE1. Below the sequence, a 'CS voice bearer' is shown between UE1 and MGCF/MGW, and a 'VoIP voice bearer' is shown between MGCF/MGW and UE2.](6470d350326789d5306eabcb76533951_img.jpg) + +Sequence diagram illustrating CSI interworking on the terminating side for CSI origination. The diagram is divided into two main sections: 'Originating side for CSI origination' and 'Terminating side for IMS session'. The originating side includes UE1, CS domain 1, and S-CSCF1. The terminating side includes CSI-AS2, MGCF/MGW, S-CSCF2, and UE2. The sequence of messages is: 1. SETUP from UE1 to CS domain 1; 2. IAM from CS domain 1 to MGCF/MGW; 3. INVITE from MGCF/MGW to S-CSCF2; 4. INVITE from S-CSCF2 to CSI-AS2; 5. Service Logic interaction between CSI-AS2 and MGCF/MGW; 6. INVITE from CSI-AS2 to S-CSCF2; 7. INVITE from S-CSCF2 to UE2; 8. 200OK from UE2 to S-CSCF2; 9. 200OK from S-CSCF2 to CSI-AS2; 10. 200OK from CSI-AS2 to MGCF/MGW; 11. 200OK from MGCF/MGW to S-CSCF2; 12. CON from S-CSCF2 to CS domain 1; 13. CONNECT from CS domain 1 to UE1. Below the sequence, a 'CS voice bearer' is shown between UE1 and MGCF/MGW, and a 'VoIP voice bearer' is shown between MGCF/MGW and UE2. + +**Figure A.4: CSI interworking on terminating side for CSI origination** + +1. UE1 initiates a voice call on the CS side by sending a SETUP message to the CS domain (MSC). +2. The originating network generates an IAM which is forwarded to the visiting network. The IAM is routed to a MGCF. +3. The MGCF generates an INVITE and forwards the INVITE the call to S-CSCF2. +4. S-CSCF2, based upon iFC, forwards the INVITE to CSI-AS2. +5. CSI-AS2 terminates the INVITE from the MGCF and generates a new INVITE towards UE2. It also performs the service logic required for originating CSI interworking (e.g. 3rd party call control). +6. CSI-AS2 sends the INVITE back towards S-CSCF2. +7. S-CSCF2 forwards the INVITE to UE2. +8. UE2 accepts the session by responding to S-CSCF2 with a 200OK. +9. S-CSCF2 forwards the 200 OK to CSI-AS2. + +10. CSI-AS2 forwards the 200OK back to S-CSCF2. +11. S-CSCF2 forwards the 200OK to the MGCF. +12. The MGCF generates a CON messages which is sent to the originating CS domain. +13. The MSC in the CS domain accepts the call by sending a CONNECT to UE1. + +The voice bearer is considered to be established. + +### A.3.4 Call flows for adding IMS sessions to existing voice calls for CSI origination with CSI interworking + +In addition to the call flows described above, the following call flows describe some of the cases where CSI interworking can occur within the network on the terminating side. + +Figure A.5 below shows a call flow for adding an IMS session (e.g. MSRP session) to an existing voice call. In this case the voice call was established with IMS origination, and the interworking is performed in the network. The addition of the IMS session is from the terminal that performed the IMS origination. + +NOTE: The procedure below is simplified for clarity, e.g. some entities are omitted, but the normal IMS procedure for IMS/CS interworking procedure shall be applied. + +![Figure A.5: Call flow for adding IMS session to existing voice call using the existing dialog. The diagram shows two sides: Terminating side for IMS session (UE1, CS domain 1, S-CSCF1, CSI-AS1, MGCF/MGW) and Originating side for IMS session (S-CSCF2, UE2). A CS voice bearer exists between UE1 and MGCF/MGW, and a VoIP voice bearer exists between MGCF/MGW and UE2. The sequence of messages is: 1. RE-INVITE from UE2 to S-CSCF2; 2. RE-INVITE from S-CSCF2 to S-CSCF1; 3. RE-INVITE from S-CSCF1 to CSI-AS1; 4. INVITE from CSI-AS1 to S-CSCF1; 5. INVITE from S-CSCF1 to UE1; 6. 200 OK from UE1 to S-CSCF1; 7. 200 OK from S-CSCF1 to CSI-AS1; 8. 200 OK from CSI-AS1 to S-CSCF1; 9. 200 OK from S-CSCF1 to S-CSCF2; 10. 200 OK from S-CSCF2 to UE2. A Userplane for MSRP is established between UE1 and UE2.](5456ef9dc49ffc9cbb93cf1dd8052884_img.jpg) + +Figure A.5: Call flow for adding IMS session to existing voice call using the existing dialog. The diagram shows two sides: Terminating side for IMS session (UE1, CS domain 1, S-CSCF1, CSI-AS1, MGCF/MGW) and Originating side for IMS session (S-CSCF2, UE2). A CS voice bearer exists between UE1 and MGCF/MGW, and a VoIP voice bearer exists between MGCF/MGW and UE2. The sequence of messages is: 1. RE-INVITE from UE2 to S-CSCF2; 2. RE-INVITE from S-CSCF2 to S-CSCF1; 3. RE-INVITE from S-CSCF1 to CSI-AS1; 4. INVITE from CSI-AS1 to S-CSCF1; 5. INVITE from S-CSCF1 to UE1; 6. 200 OK from UE1 to S-CSCF1; 7. 200 OK from S-CSCF1 to CSI-AS1; 8. 200 OK from CSI-AS1 to S-CSCF1; 9. 200 OK from S-CSCF1 to S-CSCF2; 10. 200 OK from S-CSCF2 to UE2. A Userplane for MSRP is established between UE1 and UE2. + +**Figure A.5: Call flow for adding IMS session to existing voice call using the existing dialog** + +1. The UE 2 initiates a request for adding the MSRP by sending the RE-INVITE message within the existing dialogue. +2. The S-CSCF 2 of the originating network sends the RE-INVITE message for the MSRP to the S-CSCF 1 of the terminating network, in accordance with the already established sessions. +3. The S-CSCF 1 sends the INVITE message for the MSRP to the CSI-AS +4. The CSI-AS generates an INVITE that is targeted towards the user of UE1 and sends this to S-CSCF1 +5. The S-CSCF1 sends the INVITE towards UE1 +6. The UE 1 responds to the INVITE message with the 200OK message. +7. The S-CSCF1 sends the 200OK message to the CSI-AS1. +8. The CSI-AS1 generates a 200OK and sends it to S-CSCF1. +9. S-CSCF1 sends the 200OK message to S-CSCF 2 of the originating network. +10. The S-CSCF 2 of the originating network sends the 200OK message to the UE 2. + +11. Finally, the user plane for the MSRP is created. + +NOTE: The MSRP media could go through the CSI AS. + +Figure A.6 shows a call flow for adding an IMS session (e.g. MSRP session) to an existing voice call. In this case the voice call was established with CSI origination, and the interworking is performed in the network. The addition of the IMS session is from the terminal that performed the CSI origination. + +NOTE: The procedure below is simplified for clarity, e.g. some entities are omitted, but the normal IMS procedure for IMS/CS interworking procedure shall be applied. + +The flow below assumes that the CSI interworking was performed in the originating network. + +![Sequence diagram showing the call flow for adding an IMS session to an existing voice call. The diagram is divided into two main sections: 'Originating side for IMS session' and 'Terminating side for IMS session'. The entities involved are UE1, CS domain 1, S-CSCF1, CSI-AS1, MGCF/MGW, S-CSCF2, and UE2. The flow starts with UE1 sending an INVITE to S-CSCF1. S-CSCF1 sends an INVITE to CSI-AS1. CSI-AS1 generates a RE-INVITE and returns it to S-CSCF1. S-CSCF1 forwards the RE-INVITE to S-CSCF2. S-CSCF2 forwards the RE-INVITE to UE2. UE2 responds with a 200 OK to S-CSCF2. S-CSCF2 sends the 200 OK to S-CSCF1. S-CSCF1 forwards the 200 OK to CSI-AS1. CSI-AS1 generates a 200 OK and forwards it to S-CSCF1. S-CSCF1 sends the 200 OK to UE1. Finally, a userplane for MSRP is established between UE1 and UE2 via the CSI-AS1.](f0b7abcb093621bb310bf61fbe0f0d2d_img.jpg) + +``` + +sequenceDiagram + participant UE1 + participant CS_domain_1 as CS domain 1 + participant S-CSCF1 + participant CSI-AS1 + participant MGCF_MGW as MGCF/MGW + participant S-CSCF2 + participant UE2 + + Note left of UE1: Originating side for IMS session + Note right of MGCF_MGW: Terminating side for IMS session + + UE1->>S-CSCF1: 1. INVITE + S-CSCF1->>CSI-AS1: 2. INVITE + CSI-AS1-->>S-CSCF1: 3. RE-INVITE + S-CSCF1->>S-CSCF2: 4. RE-INVITE + S-CSCF2->>UE2: 5. RE-INVITE + UE2-->>S-CSCF2: 6. 200 OK + S-CSCF2->>S-CSCF1: 7. 200 OK + S-CSCF1->>CSI-AS1: 8. 200 OK + CSI-AS1-->>S-CSCF1: 9. 200 OK + S-CSCF1->>UE1: 10. 200 OK + + Note right of CSI-AS1: Userplane for MSRP + UE1-->>UE2: + +``` + +Sequence diagram showing the call flow for adding an IMS session to an existing voice call. The diagram is divided into two main sections: 'Originating side for IMS session' and 'Terminating side for IMS session'. The entities involved are UE1, CS domain 1, S-CSCF1, CSI-AS1, MGCF/MGW, S-CSCF2, and UE2. The flow starts with UE1 sending an INVITE to S-CSCF1. S-CSCF1 sends an INVITE to CSI-AS1. CSI-AS1 generates a RE-INVITE and returns it to S-CSCF1. S-CSCF1 forwards the RE-INVITE to S-CSCF2. S-CSCF2 forwards the RE-INVITE to UE2. UE2 responds with a 200 OK to S-CSCF2. S-CSCF2 sends the 200 OK to S-CSCF1. S-CSCF1 forwards the 200 OK to CSI-AS1. CSI-AS1 generates a 200 OK and forwards it to S-CSCF1. S-CSCF1 sends the 200 OK to UE1. Finally, a userplane for MSRP is established between UE1 and UE2 via the CSI-AS1. + +**Figure A.6: Call flow for adding IMS session to existing voice call using a the existing dialog** + +1. The UE1 initiates a request for adding the MSRP by sending an INVITE message within the destination towards UE2. +2. The S-CSCF 1 of the originating network sends the INVITE message for the MSRP to CSI-AS1 based upon the filter criteria. +3. The CSI-AS1 generates a RE-INVITE message within the existing dialogue towards UE2. This is returned to the S-CSCF1. The RE-INVITE contains the SDP for the original media (e.g. the audio) and the added media (e.g. MSRP). +4. S-CSCF1 forwards the RE-INVITE message towards S-CSCF2 within the existing dialogue. +5. S-CSCF2 forwards the RE-INVITE towards UE2. +6. The UE 2 responds to the INVITE message with the 200OK message. +7. The S-CSCF1 sends the 200OK message to S-CSCF2. +8. S-CSCF1 forwards the 200OK message CSI-AS1. +9. CS-AS1 generates a 200OK messages and forwards the message to S-CSCF1. +10. S-CSCF1 of the originating network sends the 200OK message to the UE1. +11. Finally, the user plane for the MSRP is created. Note that the MSRP media could go through the CSI AS. + +Figure A.7 shows a call flow for adding a voice call to an existing IMS session (e.g. MSRP session). In this case the original IMS session was established with CSI origination, and the interworking is performed in the network. The addition of the IMS session is from the terminal that performed the CSI origination. + +NOTE: The procedure below is simplified for clarity, e.g. some entities are omitted, but the normal IMS procedure for IMS/CS interworking procedure shall be applied. + +The flow below assumes that the CSI interworking is performed in the originating network. + +![Sequence diagram showing the call flow for adding a voice call to an existing IMS session. The diagram involves the following entities: UE, VMSC, MGCF, I-CSCF, S-CSCF, CSI-AS, gsmSCF, CAMEL Svc, CSAF, and IMS Core B. The sequence starts with the UE sending a Setup (B-party DN) to the VMSC. The VMSC responds with an IDP ( ) to the gsmSCF. The gsmSCF then sends a Rerouting to IMS message to the CAMEL Svc. The CAMEL Svc responds with a Connect ( IMRN ) to the VMSC. The VMSC sends an IAM ( IMRN ) to the MGCF. The MGCF sends an INVITE ( IMRN ) to the I-CSCF. The I-CSCF sends a 7a1. INVITE ( IMRN ) to the S-CSCF. The S-CSCF sends a 7a2. INVITE ( IMRN ) to the CSI-AS. The CSI-AS sends a 7b. INVITE ( IMRN ) to the CSAF. The CSAF sends a CS origination processing message to the IMS Core B. The IMS Core B sends a 9. INVITE ( B-party DN ) to the S-CSCF. The S-CSCF sends a 10. INVITE ( B-party DN ) to the I-CSCF. The I-CSCF sends a 11. RE-INVITE ( B-party DN ) to the MGCF. The MGCF sends a 12. RE-INVITE ( B-party DN ) to the VMSC. The VMSC then establishes a CS voice bearer with the UE and a VoIP voice bearer with the IMS Core B.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) + +Sequence diagram showing the call flow for adding a voice call to an existing IMS session. The diagram involves the following entities: UE, VMSC, MGCF, I-CSCF, S-CSCF, CSI-AS, gsmSCF, CAMEL Svc, CSAF, and IMS Core B. The sequence starts with the UE sending a Setup (B-party DN) to the VMSC. The VMSC responds with an IDP ( ) to the gsmSCF. The gsmSCF then sends a Rerouting to IMS message to the CAMEL Svc. The CAMEL Svc responds with a Connect ( IMRN ) to the VMSC. The VMSC sends an IAM ( IMRN ) to the MGCF. The MGCF sends an INVITE ( IMRN ) to the I-CSCF. The I-CSCF sends a 7a1. INVITE ( IMRN ) to the S-CSCF. The S-CSCF sends a 7a2. INVITE ( IMRN ) to the CSI-AS. The CSI-AS sends a 7b. INVITE ( IMRN ) to the CSAF. The CSAF sends a CS origination processing message to the IMS Core B. The IMS Core B sends a 9. INVITE ( B-party DN ) to the S-CSCF. The S-CSCF sends a 10. INVITE ( B-party DN ) to the I-CSCF. The I-CSCF sends a 11. RE-INVITE ( B-party DN ) to the MGCF. The MGCF sends a 12. RE-INVITE ( B-party DN ) to the VMSC. The VMSC then establishes a CS voice bearer with the UE and a VoIP voice bearer with the IMS Core B. + +NOTE: The functionality of the CAMEL Svc and CSAF are the same as described in TS 23.206 [17]. + +**Figure A.7: Call flow for adding a voice call to an existing IMS session** + +1. The CSI user originates a voice call in the CS domain using a CSI UE to party-B. +2. Origination triggers at the VMSC are detected; VMSC sends an Initial DP message towards the gsmSCF. +3. The gsmSCF invokes the CSI interworking Application's CAMEL Service that determines that the call needs to be interworked to IMS for CSI; thus, the CAMEL Service interworks the call to the IMS by allocating an IMRN and returning it to the gsmSCF; otherwise it responds with a CAP Continue. + +NOTE: How the information available to the CAMEL Service is used to decide whether the call should be routed through the IMS is implementation specific. + +4. The gsmSCF responds with a CAP Connect message containing the Original Called party ID and Destination Routing Address. Destination Routing Address contains the IMRN to route the call to the CSAF. Handling of Destination Routing Address and Original Called party ID is as defined in TS 23.078 [16]. +5. The VMSC routes the call towards the user's home IMS network using the IMRN via an MGCF in the home network. + +6. The MGCF initiates an INVITE towards the I-CSCF in the home IMS of the originating CSI user. The calling party number and/or original called number are included in the INVITE if they are received from the PSTN call setup signalling (e.g. ISUP). +7. The I-CSCF routes the INVITE based on one of the following standard procedures specified in "PSI based Application Server termination - direct" and "PSI based Application Server termination – indirect" procedures in TS 23.228 [2]. + - 7a. The I-CSCF forwards the INVITE to the CSAF via the S-CSCF that is assigned to the IMRN. + - 7b. The I-CSCF forwards the INVITE directly to the CSAF. +8. If, when the INVITE arrives at the CSI Interworking Application, it is processed by the CSAF of the CSI Interworking Application that may use the IMRN to retrieve the original called party number and the calling party number from the CAMEL Service. The CSAF uses the original called number and the calling party number to setup the outgoing call leg to party-B in accordance with the AS origination procedure defined in clause 5.6.5 of TS 23.228 [2]. +9. The CSAF sends the INVITE back to the S-CSCF for completion of the call toward the remote end. +10. The S-CSCF forwards the INVITE to the CSI-AS. +11. The CSI-AS forwards the RE-INVITE to the S-CSCF. The RE-INVITE contains the SDP for the original media (e.g. MSRP) and the added media (e.g. audio). +13. The CSI-AS forwards the RE-INVITE to the IMS Core B. The CS part of the CSI session is now interworked to IMS Core B. + +The rest of the call is established as per normal SIP signalling with interworking towards the CS domain. The voice call is considered to be established. + +# Annex B (informative): Change history + +| Change history | | | | | | | | | +|----------------|--------|-----------|------|-----|-----|---------------------------------------------------------|--------|---------------| +| Date | TSG # | TSG Doc. | CR | Rev | Cat | Subject/Comment | Old | New | +| 2007-06 | SA#36 | SP-070398 | 0036 | - | B | Supporting CSI capability exchange for CSI Interworking | 7.6.0 | 8.0.0 | +| 2007-09 | SA#37 | SP-070534 | 0038 | 2 | A | CSI phase 1 alignment with stage 3 | 8.0.0 | 8.1.0 | +| 2009-12 | SA#46 | - | - | - | - | Update to Rel-9 version (MCC) | 8.1.0 | 9.0.0 | +| 2011-03 | SA#51 | - | - | - | - | Update to Rel-10 version (MCC) | 9.0.0 | 10.0.0 | +| 2012-09 | - | - | - | - | - | Update to Rel-11 version (MCC) | 10.0.0 | 11.0.0 | +| 2014-09 | SA#65 | - | - | - | - | Update to Rel-12 version (MCC) | 11.0.0 | 12.0.0 | +| 2015-12 | - | - | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | - | - | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | +| 2018-06 | SP-80 | - | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | SP-88E | - | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23282/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/23_series/23282/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac928b5f23776d78e3c68fccfc7f41d19cfb2ae7 --- /dev/null +++ b/marked/Rel-16/23_series/23282/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8e75f95888ec680570a7ed2f773ad1e813261c1749203a56daad63fc56656dd0 +size 29267 diff --git a/marked/Rel-16/23_series/23282/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/marked/Rel-16/23_series/23282/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ab984f200049a63848d131126134455b41254ed1 --- /dev/null +++ b/marked/Rel-16/23_series/23282/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a9173384c0d4d2cac8099e304dc0477657e530a30f77b06bd945ad271a73bf4 +size 39473 diff --git a/marked/Rel-16/23_series/23282/10d81b2cc455e3563e3e562a7f451124_img.jpg b/marked/Rel-16/23_series/23282/10d81b2cc455e3563e3e562a7f451124_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6c99953cfd59893cf6c9fbcb60336e815e3e774 --- /dev/null +++ b/marked/Rel-16/23_series/23282/10d81b2cc455e3563e3e562a7f451124_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c91b116c5205dc598da8125255141dd3caaacb4ce56d7e79c0d739c6de823c51 +size 34967 diff --git a/marked/Rel-16/23_series/23282/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23282/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b4c77ca9f90372fda63c61288e37ee466f9014c --- /dev/null +++ b/marked/Rel-16/23_series/23282/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c4ccf6ff39ad76ff6897463673fab87d45bd395523f616fc38daf10623f161c +size 88207 diff --git a/marked/Rel-16/23_series/23282/2119293733c74fc64de88aefd597f4bb_img.jpg b/marked/Rel-16/23_series/23282/2119293733c74fc64de88aefd597f4bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fda967b58eea895930e0f390b887dda46dadc971 --- /dev/null +++ b/marked/Rel-16/23_series/23282/2119293733c74fc64de88aefd597f4bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:375258eb044f1ad8bfacb637d3109a1aa2bf6a37b25ffa5f2a40e0cc7e4b41c2 +size 34323 diff --git a/marked/Rel-16/23_series/23282/21d8ca19de468e733e521605b1890767_img.jpg b/marked/Rel-16/23_series/23282/21d8ca19de468e733e521605b1890767_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04d8ec1c78a02e135e4149bf7baa42e93abf767b --- /dev/null +++ b/marked/Rel-16/23_series/23282/21d8ca19de468e733e521605b1890767_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d2ff1959b339d124452d38178eaf8203deb6fe5fb6e83b2ad8cbda315fd0a40f +size 41807 diff --git a/marked/Rel-16/23_series/23282/24c9e038a791677ed33100667b64f7e6_img.jpg b/marked/Rel-16/23_series/23282/24c9e038a791677ed33100667b64f7e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f529ddeae0c60ae0f8908d24145a6114df0ae5e6 --- /dev/null +++ b/marked/Rel-16/23_series/23282/24c9e038a791677ed33100667b64f7e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f4c9e84edac4ec8ac61a4c40986afc29f7ff958c77bf8038402d270cc87256a +size 90119 diff --git a/marked/Rel-16/23_series/23282/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/23_series/23282/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..273e88782d8ec507d6ebcb20be311fef39589baa --- /dev/null +++ b/marked/Rel-16/23_series/23282/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5bd9f2a4f9af3af9d41279775507979d2b4bff23d0ef7985f7929c51de66253 +size 28520 diff --git a/marked/Rel-16/23_series/23282/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/23_series/23282/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc9b3110217dfef469c7b7d8e831dfb1a76cd6dd --- /dev/null +++ b/marked/Rel-16/23_series/23282/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:328aab3a0ea339d45363db2e21c6cbaa331cf6cd1dd54d0b97d3d21539f2ebdd +size 30031 diff --git a/marked/Rel-16/23_series/23282/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23282/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1cbb3b4f4b53e98678f73a82ad2713ebe388e719 --- /dev/null +++ b/marked/Rel-16/23_series/23282/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe24f152c91b51fe250e926ec6bc0cdf96da05e62dd4c91f3425aacbb6b89950 +size 81527 diff --git a/marked/Rel-16/23_series/23282/3337af75dfee8af7687b4f49914d6c93_img.jpg b/marked/Rel-16/23_series/23282/3337af75dfee8af7687b4f49914d6c93_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d62e6c59ad974ce3d344b95d82ab8fbf743f16ac --- /dev/null +++ b/marked/Rel-16/23_series/23282/3337af75dfee8af7687b4f49914d6c93_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:020ba5bc4bca1af46b3c657e9467d26544618860f63c90c64273cf23c313097e +size 28648 diff --git a/marked/Rel-16/23_series/23282/356eb99ab9489bbd647223390a913903_img.jpg b/marked/Rel-16/23_series/23282/356eb99ab9489bbd647223390a913903_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe251a4277b0b1d27951ec7e232ea39171c1f03f --- /dev/null +++ b/marked/Rel-16/23_series/23282/356eb99ab9489bbd647223390a913903_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:52a2af39453fda819da1b11ac1ffbff5ad61d6d47badb059336541ebe4d62b92 +size 69952 diff --git a/marked/Rel-16/23_series/23282/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-16/23_series/23282/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b24ab1978e5c1469de27b68fd5cb1b2e9948ba3 --- /dev/null +++ b/marked/Rel-16/23_series/23282/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2dde00accec4ebe07d2905886d92e7e0aae34dd380f918528919fef01abb867e +size 100882 diff --git a/marked/Rel-16/23_series/23282/3c04b14104f95eb8f7100f6d497d956e_img.jpg b/marked/Rel-16/23_series/23282/3c04b14104f95eb8f7100f6d497d956e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bf47351161d82bbf829652cb5ad89edc8f1e1e6 --- /dev/null +++ b/marked/Rel-16/23_series/23282/3c04b14104f95eb8f7100f6d497d956e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b8a859fddd38691c7c392d4a3c0b3adee9d48776320b87a0d05cf26a340e8b8 +size 86457 diff --git a/marked/Rel-16/23_series/23282/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/Rel-16/23_series/23282/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62b06bb7374476d8605bab065c98e45e0d2a43f2 --- /dev/null +++ b/marked/Rel-16/23_series/23282/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:528d30b409a1daf58980593dd41793e8ba20e3c002fefcbe057c1199dc5a8525 +size 72031 diff --git a/marked/Rel-16/23_series/23282/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg b/marked/Rel-16/23_series/23282/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e6d5fb57ff93e4a640ac51245120af308a4d2806 --- /dev/null +++ b/marked/Rel-16/23_series/23282/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4d7a4fc26673a7cd0ec4ccf47035641c320021c4e8f79d8fed53287f0581b2c7 +size 43110 diff --git a/marked/Rel-16/23_series/23282/3e20f0289a1945c7c3894f51383d8e37_img.jpg b/marked/Rel-16/23_series/23282/3e20f0289a1945c7c3894f51383d8e37_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b74ee2bd96625485d2bfb68fada1aa7285b0d09e --- /dev/null +++ b/marked/Rel-16/23_series/23282/3e20f0289a1945c7c3894f51383d8e37_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c568657779f4482505b12d6e3efc1265a7676d824297174b445e157874a9633b +size 69696 diff --git a/marked/Rel-16/23_series/23282/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg b/marked/Rel-16/23_series/23282/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7e22dff027183bb15c6cc0f0a27ab4d3f15afdf --- /dev/null +++ b/marked/Rel-16/23_series/23282/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70e6cc5455c8c28ad2c619b702c325e86f42b0499ab93929cf406b1cd549545a +size 47510 diff --git a/marked/Rel-16/23_series/23282/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg b/marked/Rel-16/23_series/23282/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..999ddc9c092e155cab13db5c903593608fe4faa4 --- /dev/null +++ b/marked/Rel-16/23_series/23282/4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37e9b39b965d49a8c082da45d16d247f2913b5cd72bb2014550996f7206039f0 +size 74854 diff --git a/marked/Rel-16/23_series/23282/47e8c2042061e08a14e012472e9fdbaa_img.jpg b/marked/Rel-16/23_series/23282/47e8c2042061e08a14e012472e9fdbaa_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0035fe1852abed574ee96323f76a5c947814b278 --- /dev/null +++ b/marked/Rel-16/23_series/23282/47e8c2042061e08a14e012472e9fdbaa_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a4d5c83c4a48af7cda59d8765318f24d27504f12d492b3601adb5cf29add6418 +size 85629 diff --git a/marked/Rel-16/23_series/23282/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/Rel-16/23_series/23282/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51f399b1eb9cad92187fa4df4a8d7a220f17885e --- /dev/null +++ b/marked/Rel-16/23_series/23282/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e804eea211b2834e03c4d7df4c6c46864cb376f8fa7221da5779853b058775b +size 35321 diff --git a/marked/Rel-16/23_series/23282/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg b/marked/Rel-16/23_series/23282/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f7a7b1a59130feaadd5b89aaaf41fdddb9ace94 --- /dev/null +++ b/marked/Rel-16/23_series/23282/4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c956dcafc271dd39bb1e04e5cba69c632c4c6a6f7011350837d2fecc368ff48 +size 19868 diff --git a/marked/Rel-16/23_series/23282/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-16/23_series/23282/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e77e82a0910ed40d5d9f68e6a73f9637cc78b8b --- /dev/null +++ b/marked/Rel-16/23_series/23282/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bfaeb2219d3376f20b5f4f567d4de3d82753282fb9e8b6afcf937dc8b00e3646 +size 32735 diff --git a/marked/Rel-16/23_series/23282/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/23_series/23282/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dba7256c69894af66e4d045515e4ee8191b403c7 --- /dev/null +++ b/marked/Rel-16/23_series/23282/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e95865ee5f8ec305c83b8bc2d46a2fe23d3981487f0f635dc5e533162d6ff472 +size 40243 diff --git a/marked/Rel-16/23_series/23282/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-16/23_series/23282/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..876b68977c79d532ce52324ec2de49f08d6a8c2b --- /dev/null +++ b/marked/Rel-16/23_series/23282/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1c110f9c980685b7e76789e8651f072c85829cbd1bf2f343f22b6b2d1799cb0 +size 34406 diff --git a/marked/Rel-16/23_series/23282/57939c16065211317c5442cf2a4009e0_img.jpg b/marked/Rel-16/23_series/23282/57939c16065211317c5442cf2a4009e0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45d518d71a8e8b6d8d9efef0d30df584fe3ee9da --- /dev/null +++ b/marked/Rel-16/23_series/23282/57939c16065211317c5442cf2a4009e0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e1d9e18137045db45672109e1d4252694099f91b7824516f7bbcae8d689d6e7f +size 48868 diff --git a/marked/Rel-16/23_series/23282/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/23_series/23282/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a2e4202f17ee8d31f07e93eb4f7578a9d2fd5d5 --- /dev/null +++ b/marked/Rel-16/23_series/23282/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c87c76651fc7c1a1375d1d5a5bcd52ff59573b087d1e1520b1e91e263b86db4d +size 30648 diff --git a/marked/Rel-16/23_series/23282/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23282/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc28936844e018e9ad403807d3047f7dcbc6bf03 --- /dev/null +++ b/marked/Rel-16/23_series/23282/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:328944da8d66dbff02b468d5b648a33d4c2ef4c2f1f016085a64973b6f2f935a +size 76416 diff --git a/marked/Rel-16/23_series/23282/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-16/23_series/23282/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d99c5b2a4127b4f882c0287609a948204ed09745 --- /dev/null +++ b/marked/Rel-16/23_series/23282/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fe08f0d385bb825755332f1c8a53743cc4dab3365c061e0470c5de50ab70042 +size 41406 diff --git a/marked/Rel-16/23_series/23282/5f0781dd750d507531d474aed1ff9df9_img.jpg b/marked/Rel-16/23_series/23282/5f0781dd750d507531d474aed1ff9df9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2713383d0e9725a2b6fefcf369ca984b2c46c2cd --- /dev/null +++ b/marked/Rel-16/23_series/23282/5f0781dd750d507531d474aed1ff9df9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a6541390e59f3f99aab29b2c27f8c0eb406a8d7cb038194ddc6fd754449e1b0 +size 64980 diff --git a/marked/Rel-16/23_series/23282/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/marked/Rel-16/23_series/23282/61a7f401eb46fe99a71f27bc37493f04_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cf1c93bb8fa1c7aceac30b428842344f1c5d6ab6 --- /dev/null +++ b/marked/Rel-16/23_series/23282/61a7f401eb46fe99a71f27bc37493f04_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e5edd69b506abc03fb2764bb8d886fab21bb778e199b8ead65a1101359b8f559 +size 36411 diff --git a/marked/Rel-16/23_series/23282/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/23_series/23282/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..540379329f2c734971d0bb7c3f06cb3d5dc2ce7c --- /dev/null +++ b/marked/Rel-16/23_series/23282/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60da315538b95e6f3945517086ce1f2acf5613aa43ddc27d2316a378c1697a9c +size 38057 diff --git a/marked/Rel-16/23_series/23282/6929132b4964d52244da61d4614bc4d6_img.jpg b/marked/Rel-16/23_series/23282/6929132b4964d52244da61d4614bc4d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8dc35de141512ef7586b0f4307a122c4fac5a09 --- /dev/null +++ b/marked/Rel-16/23_series/23282/6929132b4964d52244da61d4614bc4d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5f354dc4099de7944367e91c8bbe040ab9613584208e02cbb18d08cb0c9fd14 +size 22206 diff --git a/marked/Rel-16/23_series/23282/6a555cff11e140861ce08db72b01a6a2_img.jpg b/marked/Rel-16/23_series/23282/6a555cff11e140861ce08db72b01a6a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..919be574233286291b5885de126dbff1408bed43 --- /dev/null +++ b/marked/Rel-16/23_series/23282/6a555cff11e140861ce08db72b01a6a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d7666f859894a00acd9f61affb3f0c07de2605d3c4dd4d51855e6906f12cb1bb +size 37602 diff --git a/marked/Rel-16/23_series/23282/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/23_series/23282/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..20bbc380e17616e4fec9eb74bb80db77346f6cc9 --- /dev/null +++ b/marked/Rel-16/23_series/23282/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ac498e8cacfa72b31cbb20676cb7dbd0561855ac136c069741a3f6e8f0442245 +size 83962 diff --git a/marked/Rel-16/23_series/23282/71a22f206329906db6e3860c7ff8c796_img.jpg b/marked/Rel-16/23_series/23282/71a22f206329906db6e3860c7ff8c796_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f0dc6c61bbea8827959fb871f937973f1ffa2b0 --- /dev/null +++ b/marked/Rel-16/23_series/23282/71a22f206329906db6e3860c7ff8c796_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3b4f316b70b04fe55e9c131bdf7fb4869e2ee0ff9248637f72075bc719d57e1 +size 42005 diff --git a/marked/Rel-16/23_series/23282/72bc1a2b64dd6bac8285f560440c1218_img.jpg b/marked/Rel-16/23_series/23282/72bc1a2b64dd6bac8285f560440c1218_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bd0ad1f951f2854ca563978794403ba93b0bb002 --- /dev/null +++ b/marked/Rel-16/23_series/23282/72bc1a2b64dd6bac8285f560440c1218_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:587501d6be633d15c71da5875966a320e5e334770febc3e67991f2db9fdaf0d3 +size 62715 diff --git a/marked/Rel-16/23_series/23282/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-16/23_series/23282/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa223937fb729f1a7470389d66e9bca66128c516 --- /dev/null +++ b/marked/Rel-16/23_series/23282/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9aac3b6b8b0dd223ff3ea8a0ab7bbc1ecd97e873e072ad7f142d3b5f930974c2 +size 53453 diff --git a/marked/Rel-16/23_series/23282/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23282/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..622761a828e386c7234081db0afb73ceb153af66 --- /dev/null +++ b/marked/Rel-16/23_series/23282/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6141b0d638cbd53e4c661003b9046f98ca4bd7e153e9d6352b570e2bf11ff52 +size 60954 diff --git a/marked/Rel-16/23_series/23282/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/23_series/23282/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8668d24a4718179d24f93dc9c007af6c75da9213 --- /dev/null +++ b/marked/Rel-16/23_series/23282/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c384d15e63345920dda263a61d3ca6a21b85ffde0afe72664eafd9d1c4fee6b +size 31697 diff --git a/marked/Rel-16/23_series/23282/8d8c758885b4f754ff071bf3b572ab3c_img.jpg b/marked/Rel-16/23_series/23282/8d8c758885b4f754ff071bf3b572ab3c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5c1ece4c6b32194087b7e9391a3ef9c5b2df7b9 --- /dev/null +++ b/marked/Rel-16/23_series/23282/8d8c758885b4f754ff071bf3b572ab3c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8eaefcb6d9ce0adce1b7be3a4a995b0e791964b7bad63dea498bbd0b96fd9fb7 +size 37263 diff --git a/marked/Rel-16/23_series/23282/8f8caebe58364416a2eda21039d8c7bf_img.jpg b/marked/Rel-16/23_series/23282/8f8caebe58364416a2eda21039d8c7bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67da07ef30d2c957327d44ef903132434b60da8b --- /dev/null +++ b/marked/Rel-16/23_series/23282/8f8caebe58364416a2eda21039d8c7bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:81359d98e0d881dedd030175ec04a378eeee2670e72d7f797dff0b1d92a073f3 +size 19427 diff --git a/marked/Rel-16/23_series/23282/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23282/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f7fdb13b6abac99462ce54d5ca71f04d3c25fa4b --- /dev/null +++ b/marked/Rel-16/23_series/23282/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8ec47e097f66873758ea30061ac7fa5e6c8de0128e2237b623f2c543416dd411 +size 45707 diff --git a/marked/Rel-16/23_series/23282/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/23_series/23282/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..faf8eeedc660bc29e6cef9f66daac03a9d3cab47 --- /dev/null +++ b/marked/Rel-16/23_series/23282/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b658a05949bf575077c61071bc88ce963c80dd64e8ae37e06c7deef5cc9199e3 +size 20191 diff --git a/marked/Rel-16/23_series/23282/98a45dd7d474e067b7533cc966c11e95_img.jpg b/marked/Rel-16/23_series/23282/98a45dd7d474e067b7533cc966c11e95_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ebc7167587ff8e55a5314560deba6d906fdbc135 --- /dev/null +++ b/marked/Rel-16/23_series/23282/98a45dd7d474e067b7533cc966c11e95_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:db17b7fd95c70ce966af7ad56448c83ac0ac3eca94d2e79578db656f18a753f8 +size 23986 diff --git a/marked/Rel-16/23_series/23282/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/23_series/23282/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..29c2aadb1968fcf415cb342186cdcb71bf9a9a69 --- /dev/null +++ b/marked/Rel-16/23_series/23282/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:55d267446d865dc340841c434c0fd6e4e563da15d0d5eb3c593762141b164a41 +size 29046 diff --git a/marked/Rel-16/23_series/23282/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/23_series/23282/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..631dcb2e183199b8dae793b1fd945b41786c6da5 --- /dev/null +++ b/marked/Rel-16/23_series/23282/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d629064be9331403581fd0deee7cd63000248ae026ba0c1ce916eabee0a52e87 +size 30503 diff --git a/marked/Rel-16/23_series/23282/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23282/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d5d23b0e023bf3d22dbcbb065aa35b3b6e4f3d7 --- /dev/null +++ b/marked/Rel-16/23_series/23282/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:70acbee96426a12fbefc2dc77f46a19191701f20a6148d671a44e6052e1b91ef +size 81834 diff --git a/marked/Rel-16/23_series/23282/a0b72ad654428ce2b44766f24928643e_img.jpg b/marked/Rel-16/23_series/23282/a0b72ad654428ce2b44766f24928643e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46f3a43b6a10debff68dc346db87f459f986b467 --- /dev/null +++ b/marked/Rel-16/23_series/23282/a0b72ad654428ce2b44766f24928643e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2fc1b1bdda22467a4f82edc605d2f171c99f0c4fdce07893a29eca400c4cdeb1 +size 18644 diff --git a/marked/Rel-16/23_series/23282/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/Rel-16/23_series/23282/b28af4985cdef1e519e3aaf26561dcb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90aab2c2af190faef66c2cae02fd30af8c24c49c --- /dev/null +++ b/marked/Rel-16/23_series/23282/b28af4985cdef1e519e3aaf26561dcb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34526498424921e70afb31891f832f47cb478e6364ef42b9f0a8d62950e06ec5 +size 61137 diff --git a/marked/Rel-16/23_series/23282/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/23_series/23282/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb3e19ee088305c2b8b54ee0c987cf78aef85f04 --- /dev/null +++ b/marked/Rel-16/23_series/23282/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da10a55ee9fee565cfbaf59d4d33aef3d9aa4af82c9f16ff35301eff7d0d817f +size 30578 diff --git a/marked/Rel-16/23_series/23282/c0f64806753a053854921deb8f4fc798_img.jpg b/marked/Rel-16/23_series/23282/c0f64806753a053854921deb8f4fc798_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..57b4980e4d0ae41b90dac19190a98036df02c5d5 --- /dev/null +++ b/marked/Rel-16/23_series/23282/c0f64806753a053854921deb8f4fc798_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e010cda30a5422f2825d8fe206bb6c5da5e006ae40292928a7c389a7b8f4f7cf +size 57460 diff --git a/marked/Rel-16/23_series/23282/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg b/marked/Rel-16/23_series/23282/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a391cdd02f4906189880bfec77e3f089f919a56 --- /dev/null +++ b/marked/Rel-16/23_series/23282/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1b92ae5fd01f8eb6ee621f5fcf171531f3c58aebc1e8eb1e789b3cc14d09497 +size 58170 diff --git a/marked/Rel-16/23_series/23282/d62e2e2281009c16f4ee61660e716cd9_img.jpg b/marked/Rel-16/23_series/23282/d62e2e2281009c16f4ee61660e716cd9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4fe893c0a218498ca31c1a5d08b681749f844a6f --- /dev/null +++ b/marked/Rel-16/23_series/23282/d62e2e2281009c16f4ee61660e716cd9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b107cf454d3ffe061ee1616bdbd686bd22d14641d525339040d8b02880ddd9a9 +size 71906 diff --git a/marked/Rel-16/23_series/23282/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/23_series/23282/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2da171ac4a764347c2c0cf6b5d71983a95597484 --- /dev/null +++ b/marked/Rel-16/23_series/23282/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:da53c20eab3828fecd0ac8c828e1f98559a41a9bac37c1b43bb77dbfef5c8a6e +size 35529 diff --git a/marked/Rel-16/23_series/23282/dcf83796ccf494110638fbd4677b931d_img.jpg b/marked/Rel-16/23_series/23282/dcf83796ccf494110638fbd4677b931d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f0e09e478fe8c8d3e8a84153de0a46c0b6792d8c --- /dev/null +++ b/marked/Rel-16/23_series/23282/dcf83796ccf494110638fbd4677b931d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e91446f298e2503f5f8f89e4955d9b7e43e0525ab1d069a322461e6ce460ee45 +size 54861 diff --git a/marked/Rel-16/23_series/23282/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-16/23_series/23282/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d694029a13dc4c54d6043eba308c4ee312b6144 --- /dev/null +++ b/marked/Rel-16/23_series/23282/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1cb9567717f123d9626e2ba2e5c2746eb006b29a3c0a436690f4453f5b5f4ca6 +size 33860 diff --git a/marked/Rel-16/23_series/23282/e38206fcefa2045af01d494b2956775a_img.jpg b/marked/Rel-16/23_series/23282/e38206fcefa2045af01d494b2956775a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6c08d77ec910ab7ad61eba42127b042365b1daa --- /dev/null +++ b/marked/Rel-16/23_series/23282/e38206fcefa2045af01d494b2956775a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58beb6c7955149fdaadf603182895e7ebec871824247959a80aac87a8652e254 +size 37530 diff --git a/marked/Rel-16/23_series/23282/e4a14961bdc9882e296b25f7ae5f9760_img.jpg b/marked/Rel-16/23_series/23282/e4a14961bdc9882e296b25f7ae5f9760_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e371634798cf053a60ef53c09c1ea00d14ee1ce4 --- /dev/null +++ b/marked/Rel-16/23_series/23282/e4a14961bdc9882e296b25f7ae5f9760_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:513db67f767936de2cad2e1ad020793a074e58ef04e23dfc4862005dd37225d9 +size 42211 diff --git a/marked/Rel-16/23_series/23282/e4bbddb050930c71ba62996a2e194549_img.jpg b/marked/Rel-16/23_series/23282/e4bbddb050930c71ba62996a2e194549_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..35f7a31ffd610c587ffe11f4b6bab57b14439c23 --- /dev/null +++ b/marked/Rel-16/23_series/23282/e4bbddb050930c71ba62996a2e194549_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0da1899f80ac40877b3bcc4bdb79b5f37849260ddb476d050d2accf49468139c +size 81982 diff --git a/marked/Rel-16/23_series/23282/e94cbc0895c6914a2bb53f150ab7495e_img.jpg b/marked/Rel-16/23_series/23282/e94cbc0895c6914a2bb53f150ab7495e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..76d250acec70206e502e3fbcf9958735fc85920a --- /dev/null +++ b/marked/Rel-16/23_series/23282/e94cbc0895c6914a2bb53f150ab7495e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ba907874385d3dca40a0d26c8a209e520df00e55778bdae45757d3e09390bab +size 24492 diff --git a/marked/Rel-16/23_series/23282/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23282/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..66802bb540f99b3c37e12a8b5c9be206814bdb0c --- /dev/null +++ b/marked/Rel-16/23_series/23282/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1b17e16acf4bea9c966a633922318a0ba3fdcaca2286c203e6de2d42dbffa27c +size 73708 diff --git a/marked/Rel-16/23_series/23282/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/marked/Rel-16/23_series/23282/f0a97d0d3818a253c1d2a009966081b1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c339e6e7179fc56c55bb03d811cb2294601c949 --- /dev/null +++ b/marked/Rel-16/23_series/23282/f0a97d0d3818a253c1d2a009966081b1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b66832df68c6ed9c82bff306309454b04b19c1536f9fbd89d3a3d0d96d9a9ae1 +size 57757 diff --git a/marked/Rel-16/23_series/23282/f324fbc5d5af1e4da9cd932389f0064c_img.jpg b/marked/Rel-16/23_series/23282/f324fbc5d5af1e4da9cd932389f0064c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0ba9680763094740e18ecfdd7078e269b6440ab8 --- /dev/null +++ b/marked/Rel-16/23_series/23282/f324fbc5d5af1e4da9cd932389f0064c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f05fe25ee15df0e07137818b09138c09e0adb5e39bb44385adb5e4f33327af2 +size 51591 diff --git a/marked/Rel-16/23_series/23282/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg b/marked/Rel-16/23_series/23282/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0c6952506d20d46a2e0ed17edc6d02905a1e0942 --- /dev/null +++ b/marked/Rel-16/23_series/23282/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc5f299cf7cc7133c21e8f82a85e9f020ed7161d4b4a419e9d3a92c9105df872 +size 34909 diff --git a/marked/Rel-16/23_series/23282/f6e8acf9f931452d01688d311b5c0364_img.jpg b/marked/Rel-16/23_series/23282/f6e8acf9f931452d01688d311b5c0364_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea81389fa21ac7df4a9c355cf1cd7beae96d510b --- /dev/null +++ b/marked/Rel-16/23_series/23282/f6e8acf9f931452d01688d311b5c0364_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f7f43a938d70addb31860fae849c9193b296e87cd623b73dd638feaabf6f38fb +size 80352 diff --git a/marked/Rel-16/23_series/23282/fb5442ad7130829bed9e3682ccb84c87_img.jpg b/marked/Rel-16/23_series/23282/fb5442ad7130829bed9e3682ccb84c87_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85a20e695081b6c13100c6fe1cc2c644828b303d --- /dev/null +++ b/marked/Rel-16/23_series/23282/fb5442ad7130829bed9e3682ccb84c87_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b55488042d30a8c221a7c94f33bcc40bccbb00d73b3d05c0306223abecab901 +size 22213 diff --git a/marked/Rel-16/23_series/23282/fcc757566216206ceddbd6c775e8db02_img.jpg b/marked/Rel-16/23_series/23282/fcc757566216206ceddbd6c775e8db02_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..82772ddd6bb8ebb20d5c528709484ab2e1d04f2d --- /dev/null +++ b/marked/Rel-16/23_series/23282/fcc757566216206ceddbd6c775e8db02_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38fe380554a3e5bef5bd8bf6f5ec9b0b7d04128c2bf541d8cd0be33e19cbe239 +size 33781 diff --git a/marked/Rel-16/23_series/23282/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/23_series/23282/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cb87825ced88f66cef70948f3798d937c76a764 --- /dev/null +++ b/marked/Rel-16/23_series/23282/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0c985b480296eefcaacf9acbe1d0669242ad471c825de48df5333661f40f8d5e +size 32003 diff --git a/marked/Rel-16/23_series/23282/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23282/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d6afd873adc3d87638d1b47e170ccc6b67341a0 --- /dev/null +++ b/marked/Rel-16/23_series/23282/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7763674a878cdd49dc05e0caf22416856bc56067d2d8d7c1e2119933986292bb +size 65040 diff --git a/marked/Rel-16/23_series/23282/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg b/marked/Rel-16/23_series/23282/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a03d93b99bafe8296b80009f1ba2213deacf1c13 --- /dev/null +++ b/marked/Rel-16/23_series/23282/ff5f89b660edddb67971d7d3d4ce87ef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:48f5309406f19fb9ec604ee7d55d5b800e8baaa9fdc8a16c3c83ca040e9ad42f +size 58273 diff --git a/marked/Rel-16/23_series/23282/raw.md b/marked/Rel-16/23_series/23282/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..ed09fbc89678031ab0a64b64ab2c351c8f6d6014 --- /dev/null +++ b/marked/Rel-16/23_series/23282/raw.md @@ -0,0 +1,7214 @@ +Error! No +text of + +Error! No text of specified style in +document. + +# Contents + +| | | +|--------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 12 | +| 1 Scope..... | 13 | +| 2 References..... | 13 | +| 3 Definitions, symbols and abbreviations..... | 14 | +| 3.1 Definitions..... | 14 | +| 3.2 Abbreviations ..... | 16 | +| 4 Introduction..... | 16 | +| 5 Architectural requirements..... | 16 | +| 5.1 Transmission control..... | 16 | +| 5.2 Reception control ..... | 17 | +| 5.3 Short Data Service capability..... | 17 | +| 5.4 File distribution capability ..... | 18 | +| 5.5 Data streaming capability..... | 19 | +| 5.6 MCData group affiliation and MCData group de-affiliation ..... | 19 | +| 5.7 Conversation management..... | 19 | +| 5.8 Bearer management..... | 19 | +| 5.8.1 General ..... | 19 | +| 5.8.2 EPS bearer considerations ..... | 20 | +| 5.8.3 EPS unicast bearer considerations for MCData ..... | 20 | +| 5.8.4 MBMS bearer management..... | 20 | +| 5.9 Disposition ..... | 20 | +| 5.10 MCData message store..... | 20 | +| 5.11 IP connectivity (IPcon) capability..... | 21 | +| 5.12 MBMS user service architecture requirements ..... | 22 | +| 6 Functional model..... | 22 | +| 6.1 General ..... | 22 | +| 6.2 Description of the planes..... | 22 | +| 6.3 Transmission and reception control aspects..... | 23 | +| 6.3.1 General ..... | 23 | +| 6.4 Generic functional model ..... | 23 | +| 6.4.1 On-network functional model..... | 23 | +| 6.4.2 Off-network functional model..... | 24 | +| 6.4.3 Functional entities description..... | 24 | +| 6.4.3.1 Application plane..... | 24 | +| 6.4.3.1.1 MCData client..... | 24 | +| 6.4.3.1.2 MCData server ..... | 24 | +| 6.4.3.1.3 MCData user database..... | 25 | +| 6.4.3.1.4 Interworking function to LMR system..... | 25 | +| 6.4.3.1.5 MC gateway server..... | 25 | +| 6.4.3.2 Signalling control plane ..... | 25 | +| 6.4.3.3 MCData message store ..... | 25 | +| 6.4.3.4 Message store client..... | 25 | +| 6.4.4 Reference points ..... | 26 | +| 6.4.4.1 Application plane..... | 26 | +| 6.4.4.1.1 General ..... | 26 | +| 6.4.4.1.2 Reference point MCData-2 (between the MCData server and the MCData user database)..... | 26 | +| 6.4.4.1.3 Reference point MCData-3 (between the MCData server and the MCData server)..... | 26 | +| 6.4.4.1.3A Reference point MCData-5 (between the MCData capability function and the EPS)..... | 26 | +| 6.4.4.1.4 Reference point MCData-6 (between the MCData server and the EPS) ..... | 26 | +| 6.4.4.1.5 Reference point IWF-2 (between the interworking function to LMR system and the MCData server)..... | 26 | +| 6.4.4.1.6 Reference point MCData-7 (between the Message store client and MCData message store)..... | 26 | +| 6.4.4.1.7 Reference point MCData-8 (between the MCData message store and MCData server)..... | 27 | +| 6.4.4.1.8 Reference point MCData-9 (between the MC gateway server and the MC gateway server in a different MCData system)..... | 27 | + +| | | | +|-----------|------------------------------------------------------------------------------------------------------------------------|----| +| 6.5 | Functional model for short data service ..... | 27 | +| 6.5.1 | On-network functional model..... | 27 | +| 6.5.2 | Off-network functional model..... | 28 | +| 6.5.3 | Functional entities description..... | 28 | +| 6.5.3.1 | Application plane..... | 28 | +| 6.5.3.1.1 | SDS function ..... | 28 | +| 6.5.3.1.2 | SDS distribution function..... | 28 | +| 6.5.3.1.3 | Transmission/Reception control..... | 29 | +| 6.5.3.2 | Signalling control plane ..... | 29 | +| 6.5.4 | Reference points ..... | 29 | +| 6.5.4.1 | Application plane..... | 29 | +| 6.5.4.1.1 | Reference point MCData-SDS-1 (between the SDS distribution function and the SDS function) ..... | 29 | +| 6.5.4.1.2 | Reference point MCData-SDS-2 (unicast between the SDS distribution function and the SDS function) ..... | 29 | +| 6.5.4.1.3 | Reference point MCData-SDS-3 (multicast between the SDS distribution function and the SDS function)..... | 29 | +| 6.5.4.2 | Signalling control plane ..... | 29 | +| 6.6 | Functional model for file distribution ..... | 29 | +| 6.6.1 | On-network functional model..... | 29 | +| 6.6.1a | On-network functional model for interconnection ..... | 31 | +| 6.6.2 | Off-network functional model..... | 31 | +| 6.6.3 | Functional entities description..... | 32 | +| 6.6.3.1 | Application plane..... | 32 | +| 6.6.3.1.1 | FD function ..... | 32 | +| 6.6.3.1.2 | Media storage client ..... | 32 | +| 6.6.3.1.3 | Transmission/Reception control..... | 32 | +| 6.6.3.1.4 | Media storage function..... | 33 | +| 6.6.3.2 | Signalling control plane ..... | 33 | +| 6.6.4 | Reference points ..... | 33 | +| 6.6.4.1 | Application plane..... | 33 | +| 6.6.4.1.1 | Reference point MCData-FD-1 (between the FD functions of the MCData client and the MCData server) ..... | 33 | +| 6.6.4.1.2 | Reference point MCData-FD-2 (unicast between the FD functions of the MCData client and the MCData server) ..... | 33 | +| 6.6.4.1.3 | Reference point MCData-FD-3 (multicast between the FD functions of the MCData client and the MCData server) ..... | 34 | +| 6.6.4.1.4 | Reference point MCData-FD-4 (media storage function and media storage client)..... | 34 | +| 6.6.4.1.5 | Reference point MCData-FD-5 (FD function and media storage function) ..... | 34 | +| 6.6.4.2 | Signalling control plane ..... | 34 | +| 6.7 | Functional model for data streaming..... | 34 | +| 6.7.1 | On-network functional model..... | 34 | +| 6.7.2 | Off-network functional model..... | 35 | +| 6.7.3 | Functional entities description..... | 35 | +| 6.7.3.1 | Application plane..... | 35 | +| 6.7.3.1.1 | DS function ..... | 35 | +| 6.7.3.1.2 | Data streaming and distribution function ..... | 35 | +| 6.7.3.1.3 | Transmission/Reception control..... | 35 | +| 6.7.3.2 | Signalling control plane ..... | 35 | +| 6.7.4 | Reference points ..... | 35 | +| 6.7.4.1 | Application plane..... | 35 | +| 6.7.4.1.1 | Reference point MCData-DS-1 (between the data streaming and distribution function and the DS function) ..... | 35 | +| 6.7.4.1.2 | Reference point MCData-DS-2 (unicast between the data streaming and distribution function and the DS function) ..... | 36 | +| 6.7.4.1.3 | Reference point MCData-DS-3 (multicast between the data streaming and distribution function and the DS function) ..... | 36 | +| 6.7.4.2 | Signalling control plane ..... | 36 | +| 6.8 | Functional model for IP connectivity..... | 36 | +| 6.8.1 | On-network functional model..... | 36 | +| 6.8.2 | Off-network functional model..... | 37 | +| 6.8.3 | Functional entities description..... | 37 | + +| | | | +|-------------|------------------------------------------------------------------------------------------------------------------|----| +| 6.8.3.1 | Application plane..... | 37 | +| 6.8.3.1.1 | IP connectivity function ..... | 37 | +| 6.8.3.1.2 | IPcon distribution function..... | 37 | +| 6.8.3.1.3 | Transmission/Reception control..... | 38 | +| 6.8.3.2 | Signalling control plane ..... | 38 | +| 6.8.4 | Reference points ..... | 38 | +| 6.8.4.1 | Application plane ..... | 38 | +| 6.8.4.1.1 | Reference point MCData-IPcon-1 (between the IPcon distribution function and the U-IPcon function) ..... | 38 | +| 6.8.4.1.2 | Reference point MCData-IPcon-2 (unicast between the U-IPcon distribution function and the U-IPcon function)..... | 38 | +| 6.8.4.1.3 | Reference point MCData-IPcon-3 (multicast between the IPcon distribution function and the IPcon function)..... | 38 | +| 6.8.4.2 | Signalling control plane ..... | 38 | +| 7 | Procedures and information flows ..... | 39 | +| 7.1 | MCData service configuration ..... | 39 | +| 7.2 | Affiliation and de-affiliation to/from MCData group(s) ..... | 39 | +| 7.3 | Use of MBMS transmission (on-network)..... | 39 | +| 7.3.1 | Information flows for MBMS Transmission..... | 39 | +| 7.3.2 | Use of pre-established MBMS bearers..... | 39 | +| 7.3.3 | Use of dynamic MBMS bearer establishment..... | 40 | +| 7.3.4 | Switching from MBMS bearer to unicast bearer..... | 40 | +| 7.3.5 | Use of MBMS user services for file distribution..... | 40 | +| 7.3.5.1 | General..... | 40 | +| 7.3.5.2 | Information flows for MBMS user service usage..... | 40 | +| 7.3.5.2.1 | MBMS user service announcement..... | 40 | +| 7.3.5.3 | Procedures for MBMS user service usage..... | 41 | +| 7.3.5.3.1 | Use of pre-established MBMS user services..... | 41 | +| 7.3.5.3.1.1 | General ..... | 41 | +| 7.3.5.3.1.2 | Procedure ..... | 41 | +| 7.3.5.3.2 | Use of dynamic MBMS user service establishment..... | 43 | +| 7.4 | Short data service ..... | 44 | +| 7.4.1 | General ..... | 44 | +| 7.4.2 | Short data service for on-network ..... | 44 | +| 7.4.2.1 | Information flows for short data service..... | 44 | +| 7.4.2.1.1 | MCData standalone data request..... | 44 | +| 7.4.2.1.2 | MCData data disposition notification ..... | 45 | +| 7.4.2.1.3 | MCData standalone session data request ..... | 45 | +| 7.4.2.1.4 | MCData standalone session data response..... | 46 | +| 7.4.2.1.5 | MCData session data request ..... | 46 | +| 7.4.2.1.6 | MCData session data response..... | 47 | +| 7.4.2.1.7 | MCData group standalone data request (MCData client – MCData server)..... | 47 | +| 7.4.2.1.8 | MCData group standalone data request (MCData server – MCData client)..... | 48 | +| 7.4.2.1.9 | MCData data disposition notification(s) (MCData server – MCData client) ..... | 49 | +| 7.4.2.1.10 | MCData group session standalone data request (MCData client – MCData server) ..... | 49 | +| 7.4.2.1.11 | MCData group session standalone data request (MCData server – MCData client)..... | 50 | +| 7.4.2.1.12 | MCData group session standalone data response ..... | 51 | +| 7.4.2.1.13 | MCData group data request (MCData client – MCData server)..... | 51 | +| 7.4.2.1.14 | MCData group data request (MCData server – MCData client)..... | 52 | +| 7.4.2.1.15 | MCData group data response ..... | 53 | +| 7.4.2.1.16 | MCData one-to-one SDS communication upgrade request ..... | 53 | +| 7.4.2.1.17 | MCData one-to-one SDS communication upgrade response..... | 54 | +| 7.4.2.1.18 | MCData group SDS communication upgrade request..... | 54 | +| 7.4.2.1.19 | MCData group SDS communication upgrade response..... | 54 | +| 7.4.2.1.20 | MCData group SDS communication in-progress priority state cancel request ..... | 55 | +| 7.4.2.1.21 | MCData group SDS communication in-progress priority state cancel response ..... | 55 | +| 7.4.2.2 | One-to-one standalone short data service using signalling control plane..... | 55 | +| 7.4.2.2.1 | General ..... | 55 | +| 7.4.2.2.2 | Procedure..... | 55 | +| 7.4.2.3 | One-to-one standalone short data service using media plane..... | 57 | +| 7.4.2.3.1 | General ..... | 57 | + +| | | | +|------------|-----------------------------------------------------------------------------------------|----| +| 7.4.2.3.2 | Procedure..... | 57 | +| 7.4.2.4 | One-to-one short data service session..... | 59 | +| 7.4.2.4.1 | General ..... | 59 | +| 7.4.2.4.2 | Procedure..... | 59 | +| 7.4.2.5 | Group standalone short data service using signalling control plane..... | 61 | +| 7.4.2.5.1 | General ..... | 61 | +| 7.4.2.5.2 | Procedure..... | 61 | +| 7.4.2.6 | Group standalone short data service using media plane ..... | 63 | +| 7.4.2.6.1 | General ..... | 63 | +| 7.4.2.6.2 | Procedure..... | 64 | +| 7.4.2.7 | Group short data service session..... | 66 | +| 7.4.2.7.1 | General ..... | 66 | +| 7.4.2.7.2 | Procedure..... | 66 | +| 7.4.2.8 | One-to-one SDS communication upgrade to an emergency one-to-one SDS communication ..... | 69 | +| 7.4.2.8.1 | General ..... | 69 | +| 7.4.2.8.2 | Procedrue..... | 69 | +| 7.4.2.9 | Group SDS communication upgrade to an group emergency SDS communication ..... | 70 | +| 7.4.2.9.1 | General ..... | 70 | +| 7.4.2.9.2 | Procedure..... | 70 | +| 7.4.2.10 | Group SDS communication in-progress emergency group state cancel..... | 72 | +| 7.4.2.10.1 | General ..... | 72 | +| 7.4.2.10.2 | Procedure..... | 72 | +| 7.4.2.11 | Group SDS communication upgrade to an imminent peril group SDS communication ..... | 74 | +| 7.4.2.11.1 | General ..... | 74 | +| 7.4.2.11.2 | Procedure..... | 74 | +| 7.4.2.12 | Group SDS communication in-progress imminent peril group state cancel ..... | 74 | +| 7.4.2.12.1 | General ..... | 74 | +| 7.4.2.12.2 | Procedure..... | 74 | +| 7.4.3 | Short data service for off-network..... | 74 | +| 7.4.3.1 | General..... | 74 | +| 7.4.3.2 | Information flows for short data service ..... | 74 | +| 7.4.3.2.1 | MCData standalone data request..... | 74 | +| 7.4.3.2.2 | MCData data disposition notification ..... | 75 | +| 7.4.3.2.3 | MCData group standalone data request ..... | 75 | +| 7.4.3.3 | One-to-one standalone short data service using signalling control plane..... | 76 | +| 7.4.3.3.1 | General ..... | 76 | +| 7.4.3.3.2 | Procedure..... | 76 | +| 7.4.3.4 | Group standalone short data service using signalling control plane..... | 77 | +| 7.4.3.4.1 | General ..... | 77 | +| 7.4.3.4.2 | Procedure..... | 78 | +| 7.4.3.5 | Providing data for a user entering an ongoing MCData group conversation ..... | 79 | +| 7.4.3.5.1 | General ..... | 79 | +| 7.4.3.5.2 | Procedure..... | 79 | +| 7.4.3.6 | Group standalone short data service with MCData message store..... | 80 | +| 7.4.3.6.1 | General ..... | 80 | +| 7.4.3.6.2 | Procedure..... | 80 | +| 7.5 | File distribution ..... | 81 | +| 7.5.1 | General ..... | 81 | +| 7.5.2 | File distribution for on-network ..... | 81 | +| 7.5.2.1 | Information flows for file distribution ..... | 81 | +| 7.5.2.1.1 | MCData upload data request..... | 81 | +| 7.5.2.1.2 | MCData upload data response..... | 82 | +| 7.5.2.1.3 | MCData download data request..... | 82 | +| 7.5.2.1.4 | MCData download data response..... | 82 | +| 7.5.2.1.5 | MCData FD request (using HTTP)..... | 83 | +| 7.5.2.1.6 | MCData FD response (using HTTP)..... | 83 | +| 7.5.2.1.7 | MCData download completed report ..... | 83 | +| 7.5.2.1.8 | MCData FD request (using media plane)..... | 83 | +| 7.5.2.1.9 | MCData FD response (using media plane) ..... | 84 | +| 7.5.2.1.10 | MCData group standalone FD request (using HTTP)..... | 84 | +| 7.5.2.1.11 | MCData group standalone FD response (using HTTP or MBMS download delivery method)..... | 85 | +| 7.5.2.1.12 | MCData group standalone FD request (using media plane) ..... | 85 | + +| | | | +|------------|----------------------------------------------------------------------------------|-----| +| 7.5.2.1.13 | MCData group standalone FD response (using media plane)..... | 85 | +| 7.5.2.1.14 | MCData remove file request by user..... | 86 | +| 7.5.2.1.15 | MCData remove file response by user ..... | 86 | +| 7.5.2.1.16 | Void..... | 86 | +| 7.5.2.1.17 | Void..... | 86 | +| 7.5.2.1.18 | MCData remove file notify ..... | 86 | +| 7.5.2.1.19 | MCData file retrieve request..... | 86 | +| 7.5.2.1.20 | MCData file retrieve response..... | 87 | +| 7.5.2.1.21 | MCData group standalone FD over MBMS request..... | 87 | +| 7.5.2.1.22 | MCData one-to-one FD upgrade request ..... | 87 | +| 7.5.2.1.23 | MCData one-to-one FD upgrade response..... | 88 | +| 7.5.2.1.24 | MCData group FD upgrade request ..... | 88 | +| 7.5.2.1.25 | MCData group FD upgrade response..... | 88 | +| 7.5.2.1.26 | MCData group FD in-progress priority state cancel request..... | 88 | +| 7.5.2.1.27 | MCData group FD in-progress priority state cancel response ..... | 89 | +| 7.5.2.2 | File upload using HTTP..... | 89 | +| 7.5.2.2.1 | General ..... | 89 | +| 7.5.2.2.2 | Procedure..... | 89 | +| 7.5.2.3 | File download using HTTP..... | 90 | +| 7.5.2.3.1 | General ..... | 90 | +| 7.5.2.3.2 | Procedure..... | 90 | +| 7.5.2.4 | One-to-one file distribution using HTTP..... | 91 | +| 7.5.2.4.1 | General ..... | 91 | +| 7.5.2.4.2 | Procedure for single MCData system..... | 91 | +| 7.5.2.4.3 | Procedure with interconnection between MCData systems..... | 92 | +| 7.5.2.5 | One-to-one file distribution using media plane ..... | 94 | +| 7.5.2.5.1 | General ..... | 94 | +| 7.5.2.5.2 | Procedure..... | 94 | +| 7.5.2.6 | Group standalone file distribution using HTTP..... | 96 | +| 7.5.2.6.1 | General ..... | 96 | +| 7.5.2.6.2 | Procedure..... | 96 | +| 7.5.2.7 | Group standalone file distribution using media plane ..... | 99 | +| 7.5.2.7.1 | General ..... | 99 | +| 7.5.2.7.2 | Procedure..... | 99 | +| 7.5.2.8 | File removal using HTTP by authorized user..... | 101 | +| 7.5.2.8.1 | General ..... | 101 | +| 7.5.2.8.2 | Procedure for single MCData system..... | 101 | +| 7.5.2.8.3 | Procedure for interconnection between MCData systems ..... | 102 | +| 7.5.2.9 | Void ..... | 103 | +| 7.5.2.10 | Group standalone file distribution using the MBMS download delivery method ..... | 103 | +| 7.5.2.10.1 | General ..... | 103 | +| 7.5.2.10.2 | Procedure..... | 103 | +| 7.5.2.11 | One-to-one FD communication upgrade to an emergency FD communication..... | 105 | +| 7.5.2.11.1 | General ..... | 105 | +| 7.5.2.11.2 | Procedure..... | 105 | +| 7.5.2.12 | Group FD communication upgrade to an emergency group FD communication..... | 106 | +| 7.5.2.12.1 | General ..... | 106 | +| 7.5.2.12.2 | Procedure..... | 107 | +| 7.5.2.13 | Group FD communication in-progress emergency group state cancel..... | 108 | +| 7.5.2.13.1 | General ..... | 108 | +| 7.5.2.13.2 | Procedure..... | 108 | +| 7.5.2.14 | Group FD communication upgrade to an imminent peril group FD communication ..... | 110 | +| 7.5.2.14.1 | General ..... | 110 | +| 7.5.2.14.2 | Procedure..... | 110 | +| 7.5.2.15 | Group FD communication in-progress imminent peril group state cancel..... | 110 | +| 7.5.2.15.1 | General ..... | 110 | +| 7.5.2.15.2 | Procedure..... | 110 | +| 7.5.3 | File distribution for off-network..... | 110 | +| 7.5.3.2 | Information flows for file distribution ..... | 110 | +| 7.5.3.2.1 | MCData FD request (using media plane)..... | 110 | +| 7.5.3.2.2 | MCData FD response (using media plane) ..... | 111 | +| 7.5.3.2.3 | MCData download completed report ..... | 111 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------|-----| +| 7.5.3.2.4 | MCData group standalone FD request (using media plane) ..... | 111 | +| 7.5.3.2.5 | MCData group standalone FD response (using media plane)..... | 112 | +| 7.5.3.3 | One-to-one standalone file distribution using media plane ..... | 112 | +| 7.5.3.3.1 | General ..... | 112 | +| 7.5.3.3.2 | Procedure..... | 112 | +| 7.5.3.4 | Group standalone file distribution using media plane ..... | 113 | +| 7.5.3.4.1 | General ..... | 113 | +| 7.5.3.4.2 | Procedure..... | 113 | +| 7.6 | Transmission and reception control ..... | 115 | +| 7.6.1 | General ..... | 115 | +| 7.6.2 | Transmission and reception control for on-network..... | 115 | +| 7.6.2.1 | Information flows for transmission and reception control..... | 115 | +| 7.6.2.1.1 | MCData control indication..... | 115 | +| 7.6.2.1.2 | MCData indication ..... | 115 | +| 7.6.2.1.3 | MCData get deferred list request ..... | 115 | +| 7.6.2.1.4 | MCData get deferred list response ..... | 116 | +| 7.6.2.2 | Automatic transmission for SDS ..... | 116 | +| 7.6.2.2.1 | General ..... | 116 | +| 7.6.2.2.2 | Procedure..... | 116 | +| 7.6.2.3 | Send data with mandatory download..... | 117 | +| 7.6.2.3.1 | General ..... | 117 | +| 7.6.2.3.2 | Procedure..... | 117 | +| 7.6.2.4 | Send data without mandatory download..... | 119 | +| 7.6.2.4.1 | General ..... | 119 | +| 7.6.2.4.2 | Procedure..... | 119 | +| 7.6.2.5 | Accessing list of deferred data group communications ..... | 120 | +| 7.6.2.5.1 | General ..... | 120 | +| 7.6.2.5.2 | Procedure..... | 120 | +| 7.7 | Communication release..... | 121 | +| 7.7.1 | General ..... | 121 | +| 7.7.2 | Communication release for on-network ..... | 121 | +| 7.7.2.1 | Information flows for communication release..... | 121 | +| 7.7.2.1.1 | MCData communication release request (one-to-one communication using media plane)..... | 121 | +| 7.7.2.1.2 | MCData communication release response (one-to-one communication using media plane)..... | 121 | +| 7.7.2.1.3 | MCData communication release request (group communication using media plane)..... | 122 | +| 7.7.2.1.4 | MCData communication release response (group communication using media plane) ..... | 122 | +| 7.7.2.1.5 | 122 | | +| 7.7.2.1.6 | 122 | | +| 7.7.2.1.7 | 122 | | +| 7.7.2.1.8 | MCData server communication release request (one-to-one communication using media plane)..... | 122 | +| 7.7.2.1.9 | MCData server communication release response (one-to-one communication using media plane)..... | 123 | +| 7.7.2.1.10 | MCData server communication release request (group communication using media plane)..... | 123 | +| 7.7.2.1.11 | MCData server communication release response (group communication using media plane) .... | 123 | +| 7.7.2.1.12 | 123 | | +| 7.7.2.1.13 | MCData release intent request (one-to-one communication using media plane) ..... | 124 | +| 7.7.2.1.14 | MCData more information response (one-to-one communication using media plane)..... | 124 | +| 7.7.2.1.15 | MCData release intent request (group communication using media plane) ..... | 124 | +| 7.7.2.1.16 | MCData more information response (group communication using media plane)..... | 124 | +| 7.7.2.1.17 | MCData auth user communication release request (one-to-one communication using media plane)..... | 125 | +| 7.7.2.1.18 | MCData auth user communication release response (one-to-one communication using media plane)..... | 125 | +| 7.7.2.1.19 | MCData auth user communication release request (group communication using media plane)... | 125 | +| 7.7.2.1.20 | MCData auth user communication release response (group communication using media plane)..... | 126 | +| 7.7.2.1.21 | MCData request for extension..... | 126 | +| 7.7.2.1.22 | MCData response for extension..... | 126 | +| 7.7.2.2 | MCData user initiated communication release ..... | 126 | +| 7.7.2.2.1 | General ..... | 126 | +| 7.7.2.2.2 | Release of MCData communication using media plane ..... | 126 | + +| | | | +|-------------|---------------------------------------------------------------------------------------|-----| +| 7.7.2.2.2.1 | General ..... | 126 | +| 7.7.2.2.2.2 | Procedure..... | 127 | +| 7.7.2.2.3 | Release of MCData communication using HTTP..... | 127 | +| 7.7.2.3 | MCData server initiated communication release without prior indication..... | 128 | +| 7.7.2.3.1 | General ..... | 128 | +| 7.7.2.3.2 | Release of MCData communication using media plane ..... | 128 | +| 7.7.2.3.2.1 | General ..... | 128 | +| 7.7.2.3.2.2 | Procedure..... | 128 | +| 7.7.2.3.3 | Release of MCData communication using HTTP..... | 129 | +| 7.7.2.4 | MCData server initiated communication release with prior indication..... | 130 | +| 7.7.2.4.1 | General ..... | 130 | +| 7.7.2.4.2 | Procedure..... | 130 | +| 7.7.2.5 | Authorized MCData user initiated communication release without prior indication ..... | 131 | +| 7.7.2.5.1 | General ..... | 131 | +| 7.7.2.5.2 | Procedure..... | 131 | +| 7.7.2.6 | Authorized MCData user initiated communication release with prior indication ..... | 132 | +| 7.7.2.6.1 | General ..... | 132 | +| 7.7.2.6.2 | Procedure..... | 132 | +| 7.8 | Conversation management..... | 134 | +| 7.8.1 | General ..... | 134 | +| 7.8.2 | Conversation management for on-network ..... | 134 | +| 7.8.2.1 | Information flows for conversation management..... | 134 | +| 7.8.2.2 | One-to-one conversation management ..... | 134 | +| 7.8.2.2.1 | Procedure..... | 134 | +| 7.8.2.3 | Group conversation management ..... | 135 | +| 7.8.2.3.1 | Procedure..... | 135 | +| 7.8.3 | Conversation management for off-network..... | 135 | +| 7.8.3.1 | One-to-one conversation management ..... | 135 | +| 7.8.3.1.1 | Procedure..... | 135 | +| 7.8.3.2 | Group conversation management ..... | 136 | +| 7.8.3.2.1 | Procedure..... | 136 | +| 7.9 | Enhanced status..... | 137 | +| 7.9.1 | General ..... | 137 | +| 7.9.2 | Preset values for enhanced status ..... | 137 | +| 7.9.3 | Enhanced status for on-network..... | 137 | +| 7.9.3.1 | Sharing enhanced status information..... | 137 | +| 7.9.3.1.1 | Procedure..... | 137 | +| 7.9.4 | Enhanced status for off-network..... | 138 | +| 7.9.4.1 | Sharing enhanced status information..... | 138 | +| 7.9.4.1.1 | Procedure..... | 138 | +| 7.10 | MCData emergency alert (on-network and off-network) ..... | 139 | +| 7.11 | User authentication and authorization for MCData service ..... | 139 | +| 7.12 | MCData resource management (on-network)..... | 139 | +| 7.12.1 | General ..... | 139 | +| 7.12.2 | MCData services not handled by SIP core ..... | 139 | +| 7.13 | Operations on MCData message store ..... | 140 | +| 7.13.1 | MCData message store structure..... | 140 | +| 7.13.2 | Authentication and authorization ..... | 141 | +| 7.13.3 | Manage MCData message store ..... | 141 | +| 7.13.3.1 | Information flows for managing MCData message store..... | 141 | +| 7.13.3.1.1 | MCData retrieve a stored object request..... | 141 | +| 7.13.3.1.2 | MCData retrieve a stored object response..... | 141 | +| 7.13.3.1.3 | MCData search stored objects request ..... | 141 | +| 7.13.3.1.4 | MCData search stored objects response..... | 142 | +| 7.13.3.1.5 | MCData update a stored object request..... | 142 | +| 7.13.3.1.6 | MCData update a stored object response ..... | 142 | +| 7.13.3.1.7 | MCData delete a stored object request..... | 142 | +| 7.13.3.1.8 | MCData delete a stored object response ..... | 143 | +| 7.13.3.1.9 | MCData synchronization request..... | 143 | +| 7.13.3.1.10 | MCData synchronization response..... | 143 | +| 7.13.3.1.11 | MCData create a user account request..... | 143 | +| 7.13.3.1.12 | MCData create a user account response..... | 144 | + +| | | | +|-------------|--------------------------------------------|-----| +| 7.13.3.1.13 | MCData deposit an object request ..... | 144 | +| 7.13.3.1.14 | MCData deposit an object response ..... | 144 | +| 7.13.3.1.15 | MCData copy a stored object request ..... | 144 | +| 7.13.3.1.16 | MCData copy a stored object response ..... | 144 | +| 7.13.3.1.17 | MCData move a stored object request ..... | 145 | +| 7.13.3.1.18 | MCData move a stored object response ..... | 145 | +| 7.13.3.1.19 | MCData create folder request ..... | 145 | +| 7.13.3.1.20 | MCData create folder response ..... | 145 | +| 7.13.3.1.21 | MCData delete folder request ..... | 145 | +| 7.13.3.1.22 | MCData delete folder response ..... | 146 | +| 7.13.3.1.23 | MCData copy folder request ..... | 146 | +| 7.13.3.1.24 | MCData copy folder response ..... | 146 | +| 7.13.3.1.25 | MCData move folder request ..... | 146 | +| 7.13.3.1.26 | MCData move folder response ..... | 147 | +| 7.13.3.1.27 | MCData list folder request ..... | 147 | +| 7.13.3.1.28 | MCData list folder response ..... | 147 | +| 7.13.3.1.29 | MCData upload objects request ..... | 147 | +| 7.13.3.1.30 | MCData upload objects response ..... | 147 | +| 7.13.3.1.31 | MCData synchronization notification ..... | 148 | +| 7.13.3.2 | Retrieve a stored object ..... | 148 | +| 7.13.3.2.1 | General ..... | 148 | +| 7.13.3.2.2 | Procedure ..... | 148 | +| 7.13.3.3 | Search stored objects ..... | 149 | +| 7.13.3.3.1 | General ..... | 149 | +| 7.13.3.3.2 | Procedure ..... | 149 | +| 7.13.3.4 | Update a stored object ..... | 149 | +| 7.13.3.4.1 | General ..... | 149 | +| 7.13.3.4.2 | Procedure ..... | 149 | +| 7.13.3.5 | Delete a stored object ..... | 150 | +| 7.13.3.5.1 | General ..... | 150 | +| 7.13.3.5.2 | Procedure ..... | 150 | +| 7.13.3.6 | Synchronization ..... | 151 | +| 7.13.3.6.1 | General ..... | 151 | +| 7.13.3.6.2 | Procedure ..... | 151 | +| 7.13.3.7 | Create a user account ..... | 152 | +| 7.13.3.7.1 | General ..... | 152 | +| 7.13.3.7.2 | Procedure ..... | 152 | +| 7.13.3.8 | Deposit an object ..... | 153 | +| 7.13.3.8.1 | General ..... | 153 | +| 7.13.3.8.2 | Procedure ..... | 153 | +| 7.13.3.9 | Copy a stored object ..... | 154 | +| 7.13.3.9.1 | General ..... | 154 | +| 7.13.3.9.2 | Procedure ..... | 154 | +| 7.13.3.10 | Move a stored object ..... | 155 | +| 7.13.3.10.1 | General ..... | 155 | +| 7.13.3.10.2 | Procedure ..... | 155 | +| 7.13.3.11 | Folder create operation ..... | 156 | +| 7.13.3.11.1 | General ..... | 156 | +| 7.13.3.11.2 | Procedure ..... | 156 | +| 7.13.3.12 | Folder delete operation ..... | 157 | +| 7.13.3.12.1 | General ..... | 157 | +| 7.13.3.12.2 | Procedure ..... | 157 | +| 7.13.3.13 | Folder copy operation ..... | 158 | +| 7.13.3.13.1 | General ..... | 158 | +| 7.13.3.13.2 | Procedure ..... | 158 | +| 7.13.3.14 | Folder move operation ..... | 159 | +| 7.13.3.14.1 | General ..... | 159 | +| 7.13.3.14.2 | Procedure ..... | 159 | +| 7.13.3.15 | Folder list operation ..... | 160 | +| 7.13.3.15.1 | General ..... | 160 | +| 7.13.3.15.2 | Procedure ..... | 160 | +| 7.13.3.16 | Upload objects ..... | 161 | + +| | | | +|----------------------------------------------------------------------------|---------------------------------------------------------------|------------| +| 7.13.3.16.1 | General ..... | 161 | +| 7.13.3.16.2 | Procedure..... | 161 | +| 7.13.3.17 | Notify client to synchronize..... | 162 | +| 7.13.3.17.1 | General ..... | 162 | +| 7.13.3.17.2 | Procedure..... | 162 | +| 7.13.4 | Generic outgoing SDS procedure with MCData message store..... | 163 | +| 7.13.4.1 | General..... | 163 | +| 7.13.4.2 | Procedure ..... | 163 | +| 7.13.5 | Generic incoming SDS procedure with MCData message store..... | 164 | +| 7.13.5.1 | General..... | 164 | +| 7.13.5.2 | Procedure ..... | 164 | +| 7.13.6 | Interconnection and migration with MCData message store..... | 165 | +| 7.13.6.1 | Interconnection ..... | 165 | +| 7.13.6.2 | Migration ..... | 165 | +| 7.14 | IP connectivity..... | 165 | +| 7.14.1 | General ..... | 165 | +| 7.14.2 | IP connectivity for on-network..... | 166 | +| 7.14.2.1 | Information flows for IP connectivity ..... | 166 | +| 7.14.2.1.1 | MCData IPcon point-to-point request..... | 166 | +| 7.14.2.1.2 | MCData IPcon point-to-point response..... | 166 | +| 7.14.2.2 | IP connectivity point-to-point MCData transport service..... | 166 | +| 7.14.2.2.1 | General ..... | 166 | +| 7.14.2.2.2 | Procedure..... | 166 | +| 7.15 | Location information (on-network)..... | 168 | +| Annex A (normative): MCData related configuration data..... | | 169 | +| A.1 | General..... | 169 | +| A.2 | MCData UE configuration data ..... | 170 | +| A.3 | MCData user profile configuration data ..... | 170 | +| A.4 | MCData related Group configuration data..... | 177 | +| A.5 | MCData service configuration data ..... | 179 | +| Annex B (informative): Transmission control for MCData..... | | 180 | +| B.1 | Overview of transmission control process..... | 180 | +| B.2 | Transmission control arbitration ..... | 181 | +| Annex C VOID | | 182 | +| Annex D (informative): Example of a User Message Storage Area ..... | | 183 | +| Annex E (informative): Change history ..... | | 184 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +--- + +# 1 Scope + +This document specifies the functional architecture, procedures and information flows needed to support the Mission Critical Data (MCData) services. MCData is a suite of services which utilizes the common functional architecture defined in 3GPP TS 23.280 [5] to support MC services over LTE including the common services core. + +MCData services suite consists of the following sub-services: + +- short data service (SDS); +- file distribution (FD). + +MCData features include: + +- conversation management; +- transmission and reception control; +- communication release; and +- enhanced status. + +The corresponding service requirements are defined in 3GPP TS 22.282 [3] and 3GPP TS 22.280 [2]. + +The present document is applicable primarily to MCData service using E-UTRAN access based on the EPC architecture defined in 3GPP TS 23.401 [4]. Certain application functions of the MCData service could also be supported via non-3GPP access networks but no additional functionality is specified to support non-3GPP access. + +The MCData service can be used for public safety applications and also for general commercial applications e.g. utility companies and railways. + +--- + +# 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.280: "Mission Critical Common Requirements (MCCoRe); Stage 1". +- [3] 3GPP TS 22.282: "Mission Critical Data services". +- [4] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [5] 3GPP TS 23.280: "Common functional architecture and information flows to support mission critical communication services; Stage 2". +- [6] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2". +- [7] 3GPP TS 23.303: "Proximity-based services (ProSe); Stage 2". +- [8] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE); Stage 2". +- [9] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2". + +- [10] 3GPP TS 23.002: "Network Architecture". +- [11] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); stage 2". +- [12] 3GPP TS 29.283: "Diameter data management applications". +- [13] 3GPP TS 33.180: "Security of the Mission Critical Service". +- [14] 3GPP TS 23.203: "Policy and charging control architecture". +- [15] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [16] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE\_LTE); MB2 reference point; Stage 3". +- [17] 3GPP TS 29.214: "Policy and charging control over Rx reference point". +- [18] 3GPP TS 23.283: "Mission Critical Communication Interworking with Land Mobile Radio Systems; Stage 2". +- [19] 3GPP TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point". +- [20] 3GPP TS 29.116: "Representational state transfer over xMB reference point between content provider and BM-SC ". +- [21] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs". + +--- + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**Auto-receive:** A mechanism where data smaller than a configured size threshold are delivered to the receiving MCData client(s) from the MCData server i.e. without waiting for the receiving user to indicate a present need for the data. + +**Conversation identifier:** A universally unique identifier that identifies a series of related MCData transactions. + +**Data stream:** A sequence of data that is agnostic to any underlying media (e.g. audio, video, telemetry data), on which processing of data (e.g. semantic, syntactic, save or filter operation) can begin before all the content is received. + +**FD disposition:** is one of "not downloaded" and "download completed". + +**Folder Identifier:** A unique identifier that identifies a folder in the MCData message store + +**IP Data:** Structured or unstructured payload that is transparent to the MCData transport service. + +**MCData client:** An instance of an MC service client that provides the client application function for the MCData service. + +**MCData emergency communication:** An MC service emergency group communication or MC service emergency private communication within the MCData service. + +**MCData group:** An MC service group configured for MCData service. + +**MCData group affiliation:** An MC service group affiliation for MCData. + +**MCData group communication:** A one-to-many communication using an MCData service. + +**MCData group de-affiliation:** An MC service group de-affiliation for MCData. + +**MCData ID:** An instance of an MC service ID within the MCData service. + +**MCData imminent peril communication:** An MC service imminent peril group communication within the MCData service. + +**MCData server:** An instance of an MC service server that provides the server application function for the MCData service. + +**MCData service:** A data communication service comprising at least one underlying generic capability (e.g. SDS, file distribution, data streaming) with strong security, high availability, reliability and priority handling to support applications for mission critical organizations and mission critical applications for other businesses and organizations (e.g. utilities, railways). + +**MCData UE:** An MC service UE that can be used to participate in MCData services. + +**MCData user:** An MC service user who is authorized for MCData services suite via an MCData UE. + +**Metadata:** data associated with a stored message, consisting of information retrieved from the incoming message (e.g. MCData IDs, conversation ID) and other information. + +**Object:** An MCData communication information (such as a message or a file) that is stored in the MCData message store with its associated metadata. + +**Object identifier:** A unique identifier that identifies an object stored in the MCData message store. + +**Reception control:** A mechanism that allows the MCData service to regulate data reception to the receiving MCData clients. + +**Reply identifier:** A reference to the original MCData transaction to which the current transaction is a reply. + +**SDS data:** A payload with limited size and variable content type used in SDS transactions. + +**SDS disposition:** is one of "undelivered", "delivered" and "read". + +**Standalone communication:** A unidirectional one-to-one or group data communication completed after one transaction. + +**Transaction identifier:** A unique identifier that identifies a MCData transaction within a conversation. + +**Transmission control:** A mechanism that allows the MCData service to regulate data transmission requests from the sending MCData users, either prior to or after active sending from the MCData UE. + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.280 [2] apply: + +**Mission Critical** + +**Mission Critical Applications** + +**Mission Critical Service** + +**Mission Critical Organization** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.282 [3] apply: + +**MCData system** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.280 [5] apply: + +**MC service client** + +**MC service group** + +**MC service group affiliation** + +**MC service group de-affiliation** + +**MC service ID** + +**MC service server** + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.203 [14] apply: + +### Dynamic PCC rule + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-----------|--------------------------------------| +| DS | Data Streaming | +| E2EE | End to End Encryption | +| FD | File Distribution | +| ITSI | Individual TETRA Subscriber Identity | +| LMR | Land Mobile Radio | +| MC | Mission Critical | +| MCData ID | MCData user identity | +| PCC | Policy and Charging Control | +| PCRF | Policy and Charging Rules Function | +| QCI | QoS Class Identifier | +| RSI | Radio Set Identity | +| SDS | Short Data Service | +| UM | Unacknowledged Mode | + +--- + +## 4 Introduction + +The MCData service suite provides a set of generic capabilities and specific services to enable one-to-one and group data communications between MCData users. + +The MCData architecture utilises the common functional architecture to support mission critical services over LTE defined in 3GPP TS 23.280 [5] and aspects of the IMS architecture defined in 3GPP TS 23.228 [6], the Proximity-based Services (ProSe) architecture defined in 3GPP TS 23.303 [7], the Group Communication System Enablers for LTE (GCSE\_LTE) architecture defined in 3GPP TS 23.468 [8], the MBMS User Service architecture defined in 3GPP TS 26.348 [19], the Security of the Mission Critical Service in 3GPP TS 33.180 [13] and the PS-PS access transfer procedures defined in 3GPP TS 23.237 [9] to enable support of the MCData service. + +The MCData UE primarily obtains access to the MCData service via E-UTRAN, using the EPS architecture defined in 3GPP TS 23.401 [4]. Certain application functions of MCData service can be accessed using MCData UEs via non-3GPP access networks. + +The MCData system provides the function to support interworking with LMR systems defined in 3GPP TS 23.283 [18]. + +--- + +## 5 Architectural requirements + +### 5.1 Transmission control + +The MCData service supports the ability to transmit SDS messages automatically towards the selected recipient user (private communication) or members of the selected MCData group. The MCData server may still reject the sent message (e.g. if there is no authority to send). + +**NOTE:** If a MCData group is configured for lossless communication, all members of the selected MCData group will receive the transmitted SDS messages, at a time dependent on affiliation status. **An affiliated group member of this MCData group will receive the SDS messages when they are sent. A group member that is not affiliated at the time an SDS message is sent, the SDS message will be stored in the group member's personal account in the MCData message store. The stored message will be available to the group member when he synchronizes with the MCData message store.** If a MCData group is not configured for lossless communication, only the affiliated members of the selected MCData group will receive the transmitted SDS messages. + +For MCData types other than SDS using signalling control plane, the MCData service invokes a transmission request grant approach before data is permitted to be transmitted. The MCData service provides configurable limits for the + +maximum amount of data for and/or maximum amount of time that an MCData user can transmit in a single request, which may be configured by the MCData administrator. + +**Editor's note: Additional criteria such as frequency of transmission, category/type of data, etc., for transmission control arbitration is FFS.** + +For congestion control, related to transmission requests, the MCData service may perform the following: + +- reject the data transmission requests and then shall notify the MCData user of the rejection; +- queue the data transmission requests; or +- at any time, withhold the permission to transmit data automatically. + +The MCData service shall notify the transmitting MCData group member if there are no other MCData group members affiliated to the MCData group. + +## 5.2 Reception control + +The MCData service shall support the ability to receive small amounts of data automatically. The MCData service may store data waiting for delivery in a temporary store, and notify availability to the receiving MCData users. The data which is temporarily stored may be configured with "time to live" value, and subsequently, the data may be purged from the temporary store upon expiry of "time to live". + +The recipient individual user (private communication) or affiliated members of the MCData group(s) shall be notified of the list of available data either on request or periodically. + +The MCData service shall provide a mechanism for the MCData user to select data to be downloaded from the list corresponding to the temporary store, subject to limitations such as expiry time and size. + +The MCData service shall support the ability to automatically deliver files with a size less than a configured threshold value (i.e. auto-receive). The data size for auto-receive shall be configured by the MCData administrator. + +## 5.3 Short Data Service capability + +The MCData service shall support SDS capability for one-to-one and group communications. + +The SDS capability shall support messages with a maximum payload of at least 1000 bytes. The supported message types shall include text, binary, or hyperlinks. Multiple message types may be interleaved within in a single message payload. The payload shall support inclusion of location information of the sending MCData user, with or without user or application provided data. + +The MCData service shall support messages to be sent over the signalling plane or the media plane. + +The SDS capability shall allow for multiple related messages to be correlated and sequenced within the MCData service. + +The MCData user shall be able to selectively request read and delivery receipt indication for the sent messages. The message delivery history information should be made available to an authorized MCData user. + +## 5.4 File distribution capability + +The MCData service shall support distribution of files for one-to-one and group communications. + +The MCData service shall allow the MCData user to send a file or a URL of a file to another MCData user. The source of the file can originate either from an MCData client or from a network functional entity. The generated URL shall be a reference to a stored file to allow for subsequent retrieval. The file storage policy may determine the availability of the file to be retrieved, and is subject to expiry time and size limitations. + +When the file delivery request is set by the sending user to mandatory download, the MCData service shall proceed to deliver the file to the recipient when possible. The file distribution mechanisms shall support both unicast and broadcast delivery methods. + +**Editor's note: Requirements for automatic re-try mechanisms and maximum retry count is FFS.** + +The MCData service shall support aggregation of download completion and disposition notification reports when files are distributed to multiple recipients. + +The MCData service shall support mechanisms for detection and recovery of lost data. A receiving MCData client should be able to: + +- detect and report when a transfer did not complete properly and request retransmission; +- identify and re-request the missing parts of an incompletely received file; and +- accept partial retransmissions and use them to reconstitute the original file. + +**Editor's note:** File repair when end-to-end encryption is used is FFS. + +When employing MBMS delivery: + +- MCData may use the MB2 interface specified in 3GPP TS 23.468 [8]. See also Group Communication Delivery Method in 3GPP TS 26.346 [21]; or +- if MBMS user services and Download Delivery Method (see 3GPP TS 26.346 [21]) are utilized, MCData shall use the xMB interface specified in 3GPP TS 26.348 [19]. For the MBMS path, figure 5.4-1 shows both the MB2 and the xMB interfaces. + +![Figure 5.4-1: MCData on-network architecture diagram showing the flow of data from an MCData client (UE) through an E-UTRAN to an MCData server. The diagram illustrates two delivery paths: a Unicast path (yellow) and an MBMS path (green). The Unicast path connects the E-UTRAN to the MCData server via the Rx, SGi, and MB2-C interfaces. The MBMS path connects the E-UTRAN to the MCData server via the MB2-U, xMB-C, and xMB-U interfaces. The MCData server is shown acting as a GCS AS and/or a content provider. The UE contains an MCData client. The E-UTRAN is connected to the UE via the Uu interface. The GC1 interface is shown between the MCData client and the MCData server.](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) + +Figure 5.4-1: MCData on-network architecture diagram showing the flow of data from an MCData client (UE) through an E-UTRAN to an MCData server. The diagram illustrates two delivery paths: a Unicast path (yellow) and an MBMS path (green). The Unicast path connects the E-UTRAN to the MCData server via the Rx, SGi, and MB2-C interfaces. The MBMS path connects the E-UTRAN to the MCData server via the MB2-U, xMB-C, and xMB-U interfaces. The MCData server is shown acting as a GCS AS and/or a content provider. The UE contains an MCData client. The E-UTRAN is connected to the UE via the Uu interface. The GC1 interface is shown between the MCData client and the MCData server. + +**Figure 5.4-1** MCData on-network architecture showing the unicast and MBMS delivery paths + +## 5.5 Data streaming capability + +The MCData service shall support data streaming capability for one-to-one and group communications. + +The MCData service shall allow the MCData user to send a data stream or a URL of a data stream to another MCData user. The source of the data stream can originate either from an MCData client or from a network functional entity. For a data stream originating at a network functional entity, the data stream may be provided by an MCData user. The data streaming mechanisms shall support both unicast and broadcast delivery methods. + +**Editor's note:** The minimum bitrate support for data streaming is FFS. + +When the data streaming request is set to automatic reception, the MCData service shall not require consent from the receiving MCData user. + +The MCData user shall be able to apply controls (i.e. start, stop, cancel) to the streams, and on a per recipient basis. + +**Editor's note:** The applicability of pause and resume controls to one-to-one communication is FFS + +The stream shall be terminated through an explicit user control (i.e. stop, cancel operation) or by reaching the end of the streamed content. + +## 5.6 MCData group affiliation and MCData group de-affiliation + +MCData groups may be configured with one or more MCData sub-services (e.g. SDS, FD, DS) as specified within the MCData service. When an MCData user affiliates to an MCData group, the MCData user is affiliated to each of those MCData sub-services configured in the MCData group. The list of MCData sub-services configured for an MCData group shall be included in the MCData group configuration data. + +MCData group affiliation shall be as specified in clause 5.2.5 of 3GPP TS 23.280 [5]. In addition, the following requirements shall be fulfilled by the MCData service for MCData users affiliated to MCData groups: + +- MCData users receive notifications for participating in MCData sub-services and invitations for their affiliated MCData group(s). +- MCData users select an affiliated MCData group to initiate a new message, file distribution, data stream, etc. +- MCData users receive messages, files, data streams, enhanced status updates, etc, from their affiliated MCData group(s). + +## 5.7 Conversation management + +The conversation management: + +1. shall include a service indication for conversation management in each SDS and FD transaction. +2. may be comprised of SDS transactions or FD transactions or a combination of both. +3. shall include a conversation identifier in each SDS and FD transaction. +4. shall treat conversation between different set of users (either in one-to-one or group) as a separate conversation. +5. shall treat conversation between the same set of users (either in one-to-one or group), but with a different conversation identifier as a separate conversation. + +## 5.8 Bearer management + +### 5.8.1 General + +The MCData UE shall use the APNs as defined in subclause 5.2.7.0 and table A.6-1 of 3GPP TS 23.280 [5]. The MCData UE shall use the MC services APN as defined in subclause 5.2.7.0 and table A.6-1 of 3GPP TS 23.280 [5] for the SIP-1 reference point. + +### 5.8.2 EPS bearer considerations + +The EPS bearer considerations specified in subclause 5.2.7.2 of 3GPP TS 23.280 [5] shall apply. + +### 5.8.3 EPS unicast bearer considerations for MCData + +For an MCData session request, resources shall be requested utilising interaction with dynamic PCC. The MCData system shall request resources over Rx to a PCRF. The dedicated bearer for MCData media shall utilise the QCI value of 70 (as specified in 3GPP TS 23.203 [14]). The request of resources over Rx shall include an application identifier for MCData in order for the PCRF to evaluate the correct QCI. + +The UE is required to support at minimum one bearer, which is used for MCData (see annex A in 3GPP TS 36.331 [15]). + +Depending on operator policy, for media plane: + +- the MCData system may be able to request modification of the priority (ARP) of an existing bearer without the need to initiate a new dedicated GBR bearer; or +- the EPS bearers for MCData communication may enable pre-emption of lower priority EPS bearers if the maximum number of bearers has been reached in favour of the newly initiated MCData EPS bearer, if the EPS bearer used for MCData communication has higher priority level (ARP) than the bearer(s) used for other application(s) and if the bearers for non MCData application are pre-emptable. In this case, the EPS bearer for + +MCDData communication pre-empts one of the existing EPS bearers when the maximum number of bearers is established for other applications. + +NOTE: Operator policy takes into account regional/national requirements. + +The EPS bearer for MCData emergency communication shall have highest priority level among MCData communication types. The EPS bearer for MCData imminent peril communication shall have higher priority level than one for MCData communication but lower than the priority level for MCData emergency communication. + +## 5.8.4 MBMS bearer management + +The MBMS bearer management for MC services is specified in subclause 5.2.7.1 of 3GPP TS 23.280 [5]. + +## 5.9 Disposition + +Disposition requests and notifications can be sent "in-band" using the same mechanism used for transport of the data, or can be sent "out-of-band" when the mechanism used for transport of the data is no longer available. + +For standalone SDS and FD, the MCData UE shall use the signalling plane for disposition request and disposition notifications. For session SDS, the MCData UE shall use: + +- the media plane for disposition request and disposition notifications; and +- the signalling plane for disposition notifications when the media plane is no longer available. + +## 5.10 MCData message store + +MCData message store is used by MCData users to store their MCData communications permanently; it shall provide secured storage area for each authorized MCData user having a user account. The storage area is identified by the MCData user's MCData ID. The MCData message store shall allow an MCData user to access only the storage area that he is authorized to access. A user (i.e. a dispatcher) other than the user account holder shall be able to access the account holder's storage area if authorized. + +During an active MCData communication, the participating function on the MCData server of a MCData user participant shall, if requested by the MCData user, deposit messages and files exchanged in the conversation to the MCData user's storage area in the MCData message store. When depositing the MCData communication into the MCData message store, if no such MCData user account is available on the MCData message store the MCData server shall create the user's account first and then deposit the MCData communications. The MCData message store shall support user account creation and deposit MCData communications operations from the MCData server after successful authentication and authorization. The MCData message store shall support the message store client to retrieve, update, delete, search and synchronize MCData communications stored in the MCData message store, after successful authentication and authorization. + +The MCData user shall have an option if he wants to store the MCData communications in the MCData message store or not. + +All messages and files exchanged in an active MCData communication shall be stored as objects in the MCData message store. A stored object shall contain the following information: + +1. The message or file itself; and +2. Associated metadata, consisting of: + - a. information retrieved from the information elements of the message or file, such as MCData IDs, Conversation identifier etc.; and + - b. other information, such as content type (message or file), status ("seen", "received by", "read by ", "downloaded by " etc). + +NOTE: It is the decision of SA3 on the mechanism to store an encrypted message or file in the MCData message store. + +When a MCData user logs onto a UE with successful authentication and authorization and obtains the user service profile, the message store client on the UE shall synchronize with the user's account on the MCData message store, + +either automatically or manually (i.e. interacts with the user on which option to synchronize or no synchronization at all), before any MCData service starts. + +## 5.11 IP connectivity (IPcon) capability + +IP connectivity service enables the exchange of IP Data using MCData transport service and provides the transport of IP Data for e.g. data hosts, servers, etc. that do not have mission critical communication capabilities. The exchange of IP Data is not limited in a transaction. + +![Figure 5.11-1: IP connectivity model diagram. The diagram shows a 'Data host' on the left and a 'Server' on the right, both connected to a central '3GPP system'. The 'Data host' connects to an 'IP connectivity MCData client' which is part of an 'MC service UE'. The 'Server' connects to another 'IP connectivity MCData client' which is also part of an 'MC service UE'. Both 'MC service UE' blocks are connected to the '3GPP system', which contains the 'MCData transport service'. A dashed line labeled 'IP Data' runs from the 'Data host' through the 'IP connectivity MCData client' to the 'Server', passing through the '3GPP system'.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +Figure 5.11-1: IP connectivity model diagram. The diagram shows a 'Data host' on the left and a 'Server' on the right, both connected to a central '3GPP system'. The 'Data host' connects to an 'IP connectivity MCData client' which is part of an 'MC service UE'. The 'Server' connects to another 'IP connectivity MCData client' which is also part of an 'MC service UE'. Both 'MC service UE' blocks are connected to the '3GPP system', which contains the 'MCData transport service'. A dashed line labeled 'IP Data' runs from the 'Data host' through the 'IP connectivity MCData client' to the 'Server', passing through the '3GPP system'. + +**Figure 5.11-1: IP connectivity model** + +The corresponding MCData client enables bidirectional IP Data communication with the support of the IP connectivity service and thus forms the gateway to data hosts or servers. Therefore, the IP connectivity MCData client requests the MCData transport service with the associated QoS requirement and communication priority. + +An authorised MCData client supporting IP connectivity capabilities is able to bar incoming IP connectivity requests either on demand or by providing a list of excluded origins identified by the MCData ID and, if available, by the functional alias. + +For IP connectivity, the MCData server may support following limitation to exchange IP Data: + +- limit the total data volume between the authorized MCData clients, divided by transmission and reception; +- max time limit, e.g. total minutes or allow exchange between predefined start and end time. + +IP connectivity MCData service supports MCData transport services for one-to-one and group communication. + +The IP address allocation necessary for user-IP connectivity MCData transport service is independent to the IP address allocation of the individual data hosts attached with the MCData client supporting IP connectivity capabilities. The required IP address pools for the user-IP connectivity MCData service are managed by the IP connectivity MCData transport service. + +**Editor's note:** The withdrawal of an IP connectivity connection by an authorized user is FFS. + +**Editor's note:** The remote initiation of IP connectivity service is FFS. + +**Editor's note:** The control of QoS based on per packet priority is FFS. + +**Editor's note:** The impact of IP connectivity services on interworking is FFS. + +## 5.12 MBMS user service architecture requirements + +The MBMS user service architecture offers a set of delivery methods to applications, specified in 3GPP TS 26.346 [21]. The MBMS download delivery method is used for the delivery of files over MBMS and provides reliability control by means of forward-error-correction. + +The MCData File Distribution capability can use the MBMS download delivery method by including, in the MC service-on network architecture (subclause 5.2.6 from 3GPP TS 23.280 [5]), the MBMS user service architecture (3GPP TS 26.346 [21]), with the MCData server assuming the role of the content provider. + +The MCData server may determine the MBMS broadcast area based on the cell identities of the affiliated group members received over GC1. + +When the xMB interface is used, the MCData server uses the xMB mission critical extension, specified in 3GPP TS 26.348 [19] to control the QoS and the MBMS broadcast area of the MBMS user services. The MCData server also + +provides a file delivery manifest over xMB-C (see subclause 5.6.2 from 3GPP TS 26.348 [19]) describing the list of files to be broadcasted, and, for each file, the target completion date and the number of repetitions. + +The MBMS user service metadata, which provides the delivery and schedule parameters, are returned to the MCData server after the MBMS session creation or update, under the form of a SA file (annex L.3A from 3GPP TS 26.346 [21]). The MCData server signals this SA file, together with the service id and the uri of the file to be received to the targeted MCData clients. + +**Editor's note:** it is FFS how the service announcement channel (3GPP TS 26.346) to deliver the MBMS user service metadata can be used. + +--- + +## 5A Involved business relationships + +The description of the involved business relationships for the MCData service is contained in clause 6 of 3GPP TS 23.280 [5]. + +--- + +## 6 Functional model + +### 6.1 General + +This clause defines the functional model for MCData service. + +The security solution for the MCData service, including end-to-end encryption, is specified in 3GPP TS 33.180 [13]. + +### 6.2 Description of the planes + +The functional model for the support of MCData is defined as a series of planes to allow for the breakdown of the architectural description. + +The description of the planes and the relationship between the planes are contained in the common functional architecture to support MC services in 3GPP TS 23.280 [5]. + +### 6.3 Transmission and reception control aspects + +#### 6.3.1 General + +The transmission and reception control are functions of the MCData server. + +For small data transmissions there is no need for prior grant of request to transmit. The procedures in the present document describe when data is automatically sent. + +For large data transmissions, i.e. large files, the data is transmitted only after request to transmit is granted. The data to be transmitted and/or received may be stored in a data repository associated with the transmission and reception control functions. + +**NOTE:** An overview of transmission control process and possible arbitration mechanisms is provided in the Annex B. + +### 6.4 Generic functional model + +#### 6.4.1 On-network functional model + +Figure 6.4.1-1 shows the generic application plane functional model. + +![Figure 6.4.1-1: Generic application plane functional model. This diagram illustrates the functional architecture of the MCData application plane. On the left, four external entities are shown: 'Other MCData server', 'MCData user database', 'Interworking function to LMR system', and 'MC gateway server'. These are connected to a central 'MCData server' block via reference points MCDat-3, MCDat-2, IWF-2, and MCDat-3 respectively. The 'MC gateway server' is also connected to an 'Other MCData system' (represented by a dashed box) via MCDat-9. The 'MCData server' contains a 'Capability functions (SDS, FD, DS, IPcon)' block. This block is connected to an 'MCData UE' (User Equipment) block on the right via reference points MCDat-cap-1, MCDat-cap-n, MCDat-5 (labeled Rx), and MCDat-6 (labeled MB2C). The 'MCData UE' contains 'MCData client' and 'Message store client' blocks, both of which include 'Capability functions (SDS, FD, DS, IPcon)'. A 'MCData message store' block is connected to the 'MCData server' via MCDat-8 and to the 'Message store client' via MCDat-7. The 'MCData server' and 'MCData UE' are separated by a vertical line labeled 'EPS' (Evolved Packet System).](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Figure 6.4.1-1: Generic application plane functional model. This diagram illustrates the functional architecture of the MCData application plane. On the left, four external entities are shown: 'Other MCData server', 'MCData user database', 'Interworking function to LMR system', and 'MC gateway server'. These are connected to a central 'MCData server' block via reference points MCDat-3, MCDat-2, IWF-2, and MCDat-3 respectively. The 'MC gateway server' is also connected to an 'Other MCData system' (represented by a dashed box) via MCDat-9. The 'MCData server' contains a 'Capability functions (SDS, FD, DS, IPcon)' block. This block is connected to an 'MCData UE' (User Equipment) block on the right via reference points MCDat-cap-1, MCDat-cap-n, MCDat-5 (labeled Rx), and MCDat-6 (labeled MB2C). The 'MCData UE' contains 'MCData client' and 'Message store client' blocks, both of which include 'Capability functions (SDS, FD, DS, IPcon)'. A 'MCData message store' block is connected to the 'MCData server' via MCDat-8 and to the 'Message store client' via MCDat-7. The 'MCData server' and 'MCData UE' are separated by a vertical line labeled 'EPS' (Evolved Packet System). + +**Figure 6.4.1-1: Generic application plane functional model** + +In the model shown in figure 6.4.1-1, capability functions (SDS, FD, DS, IPcon) of the MCData client and the MCData server along with their reference points (MCDat-cap-1 to MCDat-cap-n) are described in the respective functional models for each capability. + +**NOTE:** The security aspects of new network components (MCData message store and Message store client) and its two new reference points are the responsibility of SA3 and thus outside the scope of the present document. + +## 6.4.2 Off-network functional model + +## 6.4.3 Functional entities description + +**Editor's note:** Combining functional models describing each capability into one functional model is FFS. + +### 6.4.3.1 Application plane + +#### 6.4.3.1.1 MCData client + +The MCData client functional entity acts as the user agent for all MCData application transactions. The client supports SDS, file distribution, data streaming and IP connectivity MCData capabilities utilized by MCData services like conversation management, robots control, enhanced status, database enquiries and secured internet. + +#### 6.4.3.1.2 MCData server + +The MCData server functional entity provides centralised support for MCData services suite. Conversation management, robots, enhanced status, database enquiries and secured internet MCData services requiring one-to-one or group data communication are realized using SDS, file distribution, data streaming and IP connectivity MCData communication capabilities. + +All the MCData clients supporting users belonging to a single group are required to use the same MCData server for that group. An MCData client supporting a user involved in multiple groups can have relationships with multiple MCData servers. + +For MBMS delivery, the MCData server functional entity represents a specific instantiation of the GCS AS described in 3GPP TS 23.468 [8] to control multicast and unicast operations for group communications. + +If the MBMS user service architecture is utilized, the MCData server functional entity represents a specific instantiation of the content provider as described in 3GPP TS 26.346 [21] to control multicast operations for file distribution. + +The MCData server functional entity is supported by the SIP AS functional entity of the signalling control plane. + +The MCData server shall support the controlling role and the participating role. The MCData server may perform the controlling role for one-to-one and group data communication. The MCData server performing the controlling role for a one-to-one or group data communication may also perform a participating role for the same one-to-one or group data communication. For each one-to-one and group data communication, there shall be only one MCData server assuming the controlling role, while one or more MCData servers in participating role may be involved. + +The MCData server performing the controlling role is responsible for: + +- handling transmission and reception control (e.g. policy enforcement for participation in the MCData group communication) towards all the MCData users of the one-to-one and group data communication; +- interfacing with the group management server for group policy and affiliation status information of this MCData server's served affiliated users; +- managing SDS and FD data distribution during MCData group communication; and +- managing the MCData transport service for IP connectivity. + +The MCData server performing the participating role is responsible for: + +- handling transmission control (e.g. authorization for participation in the MCData group communication) to MCData users of the one-to-one and group data communication; +- group affiliation support for MCData user, including enforcement of maximum Nc2 number of simultaneous group affiliations by a user; +- interfacing with the group management server for group policy and affiliation status information of this MCData server's served affiliated users; +- relaying the MCData communication messages between the MCData client and the MCData server performing the controlling role; and +- handling reception control (e.g. temporarily storing the data to present to the MCData user as required) to its MCData users of the one-to-one and group data communication. + +NOTE: The MCData server in the controlling role and the MCData server in the participating role can belong to the same MCData system. + +#### 6.4.3.1.3 MCData user database + +This functional entity contains information of the MCData user profile associated with an MCData ID that is held by the MCData service provider at the application plane. The MCData user profile is determined by the mission critical organization, the MCData service provider, and potentially the MCData user. + +#### 6.4.3.1.4 Interworking function to LMR system + +The functional entity is specified in 3GPP TS 23.283 [18]. + +#### 6.4.3.1.5 MC gateway server + +The MC gateway server provides support for MCData interconnection services with a partner MCData system in a different trust domain whilst providing topology hiding. It acts as a proxy for one or more MCData servers in the partner MCData system without needing to expose the MCData servers in the primary MCData system outside the trusted domain of the primary MCData system. It may be a role of the MCData server described in subclause 6.4.3.1.2 of the present document. + +The MC gateway server is responsible for relaying call control and transmission control signalling messages, and media between MCData servers within the MCData system and the interconnected MCData system. + +#### 6.4.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +### 6.4.3.3 MCData message store + +The MCData message store is a network base persistent store that allows Mission Critical Organization to configure their MCData users to permanently store their MCData communications. Once configured a MCData user will be allocated a secured storage area (i.e. size) in the MCData message store that is only accessible by that configured MCData user and any authorized users. The MCData user can manage how and what will be stored in his personal message store with the support of management operations such as creating, deleting and merging folders, moving stored messages and files around and synchronization all used devices to provide the same context view etc. + +NOTE: The security aspects of access and management (such as read/write/update/sync etc.) of personal message store are the responsibility of SA3 and thus outside the scope of the present document. + +### 6.4.3.4 Message store client + +The Message store client is used to support MCData client to manage the MCData communication history stored in MCData message store for a particular MCData user. It supports the secure access to a MCData user's configured MCData message store area and operations relevant to the stored communication history such as folders management and synchronization to the device local message store. + +## 6.4.4 Reference points + +### 6.4.4.1 Application plane + +#### 6.4.4.1.1 General + +The reference points for the application plane of MCData service are described in the following subclauses. + +#### 6.4.4.1.2 Reference point MCData-2 (between the MCData server and the MCData user database) + +The MCData-2 reference point, which exists between the MCData server and the MCData user database, is used by the MCData server to obtain information about a specific user. The MCData-2 reference point utilises a diameter management application protocol as defined in 3GPP TS 29.283 [12] and shall be intra-network. + +#### 6.4.4.1.3 Reference point MCData-3 (between the MCData server and the MCData server) + +The MCData-3 reference point, which exists between the MCData server and the MCData server for MCData application signalling for establishing MCData sessions, shall use the SIP-2 reference point for transport and routing of signalling. If each MCData server is served by a different SIP core then the MCData-3 reference point shall also use the SIP-3 reference point for transport and routing of signalling. Media is also transferred using the MCData-3 reference point. + +#### 6.4.4.1.3A Reference point MCData-5 (between the MCData capability function and the EPS) + +The MCData-5 reference point, which exists between the MCData capability function and the EPS, is used, subject to the conditions below, by the MCData capability function of the MCData server to obtain unicast bearers with appropriate QoS from the EPS. It utilises the Rx interface of the EPS according to 3GPP TS 23.203 [14]. + +MCData-5 is not used when the MCData service provider and the PLMN operator do not have an operational agreement for QoS control to be provided directly from the MCData service provider domain. + +MCData-5 may be used when the MCData service provider and the PLMN operator have an operational agreement where QoS control is provided directly from the MCData service provider domain. + +NOTE: Any coordination between the P-CSCF use of Rx and the MCData server use of Rx (via MCData-5) from the MCData service provider domain is not specified in this release of this specification. + +#### 6.4.4.1.4 Reference point MCData-6 (between the MCData server and the EPS) + +The MCData-6 reference point, which exists between the MCData server and the EPS, is used to request the allocation and activation of multicast transport resources for MCData application usage. The MCData-6 reference point uses the MB2-C interface as defined in 3GPP TS 29.468 [16]. The MCData-6 reference point also uses the xMB-C interface as defined in 3GPP TS 29.116 [20] for file distribution. + +#### 6.4.4.1.5 Reference point IWF-2 (between the interworking function to LMR system and the MCData server) + +The IWF-2 reference point is specified in 3GPP TS 23.283 [18]. + +#### 6.4.4.1.6 Reference point MCData-7 (between the Message store client and MCData message store) + +The MCData-7 reference point, which exists between the Message store client and the MCData message store, is used by the Message store client to manage the information stored in the MCData message store and synchronization between the MCData client and the MCData message store. + +#### 6.4.4.1.7 Reference point MCData-8 (between the MCData message store and MCData server) + +The MCData-8 reference point, which exists between the MCData server and the MCData message store, is used by the MCData server to access and manage the MCData message store such as creating MCData user folders and depositing the communications history. + +#### 6.4.4.1.8 Reference point MCData-9 (between the MC gateway server and the MC gateway server in a different MCData system) + +The MCData-9 reference point, which exists between the MC gateway server and the MC gateway server in an interconnected MCData system for MCData application signalling for establishing MCData sessions, shall use the SIP-3 reference point for transport and routing of signalling. The MCData-9 reference point also carries application data where the data size is too great to be transferred on the signalling plane. + +## 6.5 Functional model for short data service + +### 6.5.1 On-network functional model + +Figure 6.5.1-1 shows the application plane functional model for SDS. + +![Figure 6.5.1-1: Application plane functional model for SDS. The diagram shows the functional components and reference points for the Short Data Service (SDS) within an MCData system. On the left, the MCData server contains an SDS distribution function and a Transmission/Reception control. On the right, the MCData UE contains an MCData client with an SDS function and a Message store client. In the center, the MCData Message Store is shown. Reference points are indicated by lines: MCData-SDS-1 (dashed line) between the SDS distribution function and the SDS function; MCData-SDS-2 (solid line) between the SDS distribution function and the SDS function; MCData-SDS-3 (solid line) between the SDS distribution function and the SDS function; MCData-8 (solid line) between the MCData server and the MCData Message Store; and MCData-7 (solid line) between the MCData Message Store and the Message store client. The entire system is connected to an EPS (Evolved Packet System) via a vertical line labeled EPS.](21d8ca19de468e733e521605b1890767_img.jpg) + +Figure 6.5.1-1: Application plane functional model for SDS. The diagram shows the functional components and reference points for the Short Data Service (SDS) within an MCData system. On the left, the MCData server contains an SDS distribution function and a Transmission/Reception control. On the right, the MCData UE contains an MCData client with an SDS function and a Message store client. In the center, the MCData Message Store is shown. Reference points are indicated by lines: MCData-SDS-1 (dashed line) between the SDS distribution function and the SDS function; MCData-SDS-2 (solid line) between the SDS distribution function and the SDS function; MCData-SDS-3 (solid line) between the SDS distribution function and the SDS function; MCData-8 (solid line) between the MCData server and the MCData Message Store; and MCData-7 (solid line) between the MCData Message Store and the Message store client. The entire system is connected to an EPS (Evolved Packet System) via a vertical line labeled EPS. + +**Figure 6.5.1-1: Application plane functional model for SDS** + +In the model shown in figure 6.5.1-1, the following apply: + +- MCData-SDS-1 reference point is primarily used for MCData application signalling during session establishment in support of SDS data transfer. Secondarily, MCData-SDS-1 reference point is used for uplink and downlink unicast SDS data transaction over signalling control plane by the SDS distribution function of the MCData server and SDS function of the MCData client. +- MCData-SDS-2 reference point carries uplink and downlink unicast SDS data over media plane between the SDS distribution function of the MCData server and the SDS function of the MCData client. + +- MCData-SDS-3 reference point carries downlink multicast SDS data over media plane from the SDS distribution function of the MCData server to the SDS function of the MCData client. + +Examples of SDS data (in the form of text, binary, application data, URL or combinations of these) are: + +- information pertaining to applications e.g. health parameters of MCData user for situational awareness application; +- information pertaining to enhanced status service; +- text or URL data between MCData users; +- application data (e.g. health parameters) to the MCData user; +- location information (independent or along with user or application provided data); +- command instructions to invoke certain operations on the MCData UE e.g. invoking UE specific applications; and +- application plane identities for the MCData user and MCData application. + +## 6.5.2 Off-network functional model + +Figure 6.5.2-1 shows the off-network application plane functional model for SDS. + +![Figure 6.5.2-1: Application plane functional model for SDS. The diagram shows two User Equipment (UE) blocks, UE 1 and UE 2, connected by two horizontal lines: a green line labeled 'Media' and a red line labeled 'Signalling'. Each UE block contains a top section with 'SDS function' and 'MCData client', a middle section with 'Configuration management client', 'Group management client', and 'Common services core' (all within a dashed box labeled 'Application plane'), and a bottom section with 'Signalling user agent' and 'Signalling control plane'.](356eb99ab9489bbd647223390a913903_img.jpg) + +Figure 6.5.2-1: Application plane functional model for SDS. The diagram shows two User Equipment (UE) blocks, UE 1 and UE 2, connected by two horizontal lines: a green line labeled 'Media' and a red line labeled 'Signalling'. Each UE block contains a top section with 'SDS function' and 'MCData client', a middle section with 'Configuration management client', 'Group management client', and 'Common services core' (all within a dashed box labeled 'Application plane'), and a bottom section with 'Signalling user agent' and 'Signalling control plane'. + +**Figure 6.5.2-1: Application plane functional model for SDS** + +## 6.5.3 Functional entities description + +### 6.5.3.1 Application plane + +#### 6.5.3.1.1 SDS function + +SDS function of the MCData client is responsible to handle SDS capability related requests and responses. + +#### 6.5.3.1.2 SDS distribution function + +The SDS distribution function of the MCData server is responsible for the SDS data transaction to MCData communication participants. The SDS distribution function of the MCData server provides the following functionality: + +- reception of uplink SDS data transaction by means of the MCData-SDS-1 and MCData-SDS-2 reference points; +- replicate the SDS data as needed for distribution to those MCData communication participants using unicast transport; + +- distribute downlink data by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of the MCData-SDS-1 and MCData-SDS-2 reference points; and +- distribute downlink SDS data using multicast downlink transport by means of the MCData-SDS-3 reference point. + +#### 6.5.3.1.3 Transmission/Reception control + +This functional entity is responsible for transmission and reception control of MCData SDS data transaction between the sending MCData UE, the MCData server, and the receiving MCData UE. For SDS capability, due to small data size, the SDS messages can be automatically sent. + +#### 6.5.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +### 6.5.4 Reference points + +#### 6.5.4.1 Application plane + +##### 6.5.4.1.1 Reference point MCData-SDS-1 (between the SDS distribution function and the SDS function) + +MCData-SDS-1 reference point is used for uplink and downlink unicast SDS data transaction over signalling control plane by the SDS distribution function of the MCData server and SDS function of the MCData client. This reference point is also used for MCData application signalling during session establishment in support of SDS data transfer. + +The MCData-SDS-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. MCData-SDS-1 reference point can be used when the SDS payload data size does not exceed the configured maximum payload data size for SDS over signalling control plane, otherwise MCData-SDS-2 and MCData-SDS-3 may be used appropriately. + +Reference point MCData-SDS-1 also provides support to delivered and read requests and notifications as appropriate. + +##### 6.5.4.1.2 Reference point MCData-SDS-2 (unicast between the SDS distribution function and the SDS function) + +The MCData-SDS-2 reference point, which exists between the SDS distribution function and the SDS function of the MCData client, is used unicast SDS data transaction (when the SDS payload data size exceeds the configured maximum payload data size for SDS over signalling control plane) between the MCData server and the MCData client. The MCData-SDS-2 reference point uses the SGi reference point defined in 3GPP TS 23.002 [10]. + +Reference point MCData-SDS-2 also provides support to message thread indication using conversation identifier, delivered and read notifications as appropriate. + +##### 6.5.4.1.3 Reference point MCData-SDS-3 (multicast between the SDS distribution function and the SDS function) + +The MCData-SDS-3 reference point, which exists between the SDS distribution function of the MCData server and the SDS function of the MCData client, is used by the SDS distribution function of the MCData server to send downlink multicast SDS data to the SDS function of the MCData client. The MCData-SDS-3 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [8]. + +#### 6.5.4.2 Signalling control plane + +The description of the signalling control plane reference points is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +## 6.6 Functional model for file distribution + +### 6.6.1 On-network functional model + +Figure 6.6.1-1 shows the application plane functional model for file distribution. + +![Figure 6.6.1-1: Application plane functional model for file distribution. The diagram shows the functional components and reference points for file distribution between an MCDData server and an MCDData UE. The MCDData server contains an FD function, a Transmission/Reception control, and an MCDData content server (with a Media Storage function). The MCDData UE contains an MCDData client with an FD function, a Media Storage client, and a Message store client. Reference points are: MCDData-FD-1 (signalling), MCDData-FD-2 (uplink/downlink unicast file data), MCDData-FD-3 (downlink multicast file data), MCDData-FD-4 (uplink/downlink unicast file data), MCDData-FD-5 (server access to content server), MCData-8 (server to message store), MCData-7 (message store to UE), and EPS (network).](f0a97d0d3818a253c1d2a009966081b1_img.jpg) + +Figure 6.6.1-1: Application plane functional model for file distribution. The diagram shows the functional components and reference points for file distribution between an MCDData server and an MCDData UE. The MCDData server contains an FD function, a Transmission/Reception control, and an MCDData content server (with a Media Storage function). The MCDData UE contains an MCDData client with an FD function, a Media Storage client, and a Message store client. Reference points are: MCDData-FD-1 (signalling), MCDData-FD-2 (uplink/downlink unicast file data), MCDData-FD-3 (downlink multicast file data), MCDData-FD-4 (uplink/downlink unicast file data), MCDData-FD-5 (server access to content server), MCData-8 (server to message store), MCData-7 (message store to UE), and EPS (network). + +**Figure 6.6.1-1: Application plane functional model for file distribution** + +In the model shown in figure 6.6.1-1, the following apply: + +- MCDData-FD-1 reference point is primarily used for MCDData application signalling for establishing a session in support of MCDData file distribution. Secondly, MCDData-FD-1 reference point is also used for both uplink and downlink unicast data (e.g., URL associated to file, file download completed report). +- MCDData-FD-2 reference point carries uplink and downlink unicast file data between the FD functions of the MCDData server and the MCDData UE. +- MCDData-FD-3 reference point carries downlink multicast file data from the FD function of the MCDData server to the FD function of the MCDData UE. +- MCDData-FD-4 reference point carries uplink and downlink unicast file data between the media storage function of the MCDData Content server and the media storage client of the MCDData UE. +- MCDData-FD-5 reference point supports the MCDData server to access the stored files in the MCDData content server for certain file distribution functions, such as retrieval a file to be distributed through multicast etc. This reference points also supports any necessary operational requirements. + +NOTE 1: The security aspects of MCDData-FD-5 reference point are the responsibility of SA3 and thus outside the scope of the present document. + +**Editor's note: It is FFS on what the operational requirements (such as QoS control of file upload and download) are needed to be supported by this reference point.** + +- MCDData content server is a repository area in the MCDData trust domain that allows authorized MCDData user to temporarily store files that are intended to share to other MCDData users. It provides common pool of storage area (i.e. size) to all authorized MCDData users to use, no personal space is allocated. An authorized MCDData user can + +use the supported operations on the defined reference point to upload shared files and download the files that are shared to him. The MCData server will use the defined reference point to access the files stored in the MCData content server and support the necessary operational supports. As part of the file life cycle management the temporarily stored files will be removed periodically based on the Mission Critical service provider policy. An MCData content server may share files with another MCData content server in another MCData system to support interconnection. + +NOTE 2: The security aspects of MCData content server and its operational supports are the responsibility of SA3 and thus outside the scope of the present document. + +### 6.6.1a On-network functional model for interconnection + +Figure 6.6.1a-1 shows the application plane functional model for file distribution with interconnection. + +![Figure 6.6.1a-1: Application plane functional model for file distribution. The diagram illustrates the functional components and interfaces for file distribution across three main systems: Partner MCData system, Primary MCData system, and MCData UE. The Partner MCData system contains an MCData content server (with Media Storage function) and an MCData server (with FD function and Transmission/reception control). The Primary MCData system contains an MCData server (with FD function, Transmission/reception control, and MCData Message store), an MC gateway server, and an HTTP proxy. The MCData UE contains an MCData client (with FD function, Media Storage client, and Message store client). Interfaces are labeled as follows: MCData-FD-1, MCData-FD-2, MCData-FD-3 (between Primary MCData server and MCData UE); MCData-FD-4 (between MCData content server and MCData UE); MCData-FD-5 (between MCData content server and MCData server); MCData-FD-6 (between Partner MCData content server and MCData UE via HTTP proxies); MCData-3 (between MCData server and MC gateway server); MCData-9 (between MC gateway server and MCData server); MCData-7 (between MCData Message store and MCData UE); MCData-8 (between MCData server and MCData Message store).](24c9e038a791677ed33100667b64f7e6_img.jpg) + +Figure 6.6.1a-1: Application plane functional model for file distribution. The diagram illustrates the functional components and interfaces for file distribution across three main systems: Partner MCData system, Primary MCData system, and MCData UE. The Partner MCData system contains an MCData content server (with Media Storage function) and an MCData server (with FD function and Transmission/reception control). The Primary MCData system contains an MCData server (with FD function, Transmission/reception control, and MCData Message store), an MC gateway server, and an HTTP proxy. The MCData UE contains an MCData client (with FD function, Media Storage client, and Message store client). Interfaces are labeled as follows: MCData-FD-1, MCData-FD-2, MCData-FD-3 (between Primary MCData server and MCData UE); MCData-FD-4 (between MCData content server and MCData UE); MCData-FD-5 (between MCData content server and MCData server); MCData-FD-6 (between Partner MCData content server and MCData UE via HTTP proxies); MCData-3 (between MCData server and MC gateway server); MCData-9 (between MC gateway server and MCData server); MCData-7 (between MCData Message store and MCData UE); MCData-8 (between MCData server and MCData Message store). + +**Figure 6.6.1a-1: Application plane functional model for file distribution** + +In the model shown in figure 6.6.1a-1, the following apply: + +- MCData-FD-1, MCData-FD-2, MCData-FD-3, MCData-FD-4, MCData-FD-5 reference points are described in subclause 6.6.1. +- MCData-7 and MCData-8 reference points are described in subclause 6.4.4.1. +- The MC gateway server is described in subclause 6.4.3.1.5. +- MCData-3 and MCData-9 allow the MCData server in the primary MCData system to share URLs related to files for upload and download with the MCData server in the partner MCData system. +- MCData-FD-6 allows file contents and metadata to be shared between the MCData content server in the primary MCData system and the MCData content server in the partner MCData system. MCData-FD-6 is based on HTTP. +- The HTTP proxies are contained in the signalling plane. They provide topology and IP address hiding between MCData systems. + +## 6.6.2 Off-network functional model + +Figure 6.6.2-1 shows the off-network application plane functional model for FD. + +![Figure 6.6.2-1: Application plane functional model for FD. The diagram shows two User Equipment (UE) blocks, UE 1 and UE 2, connected by two horizontal lines labeled 'Media' (green) and 'Signalling' (red). Each UE block contains a stack of functional layers. From top to bottom: 1. FD function and MCData client; 2. Configuration management client, Group management client, and Common services core (grouped by a dashed box); 3. Application plane; 4. Signalling user agent and Signalling control plane.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +Figure 6.6.2-1: Application plane functional model for FD. The diagram shows two User Equipment (UE) blocks, UE 1 and UE 2, connected by two horizontal lines labeled 'Media' (green) and 'Signalling' (red). Each UE block contains a stack of functional layers. From top to bottom: 1. FD function and MCData client; 2. Configuration management client, Group management client, and Common services core (grouped by a dashed box); 3. Application plane; 4. Signalling user agent and Signalling control plane. + +**Figure 6.6.2-1: Application plane functional model for FD** + +## 6.6.3 Functional entities description + +### 6.6.3.1 Application plane + +#### 6.6.3.1.1 FD function + +FD function of the MCData client and the MCData server is responsible to handle file distribution capability related requests and responses. + +The FD function of the MCData server is responsible for the distribution of file to the MCData communication participants. The FD function of the MCData server provides the following functionality: + +- reception of uplink file data by means of the MCData-FD-2 reference point; +- replicate the file data as needed for distribution to those MCData communication participants using unicast transport; +- distribute downlink file data by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of the MCData-FD-2 reference point; and +- distribute downlink file data using multicast downlink transport by means of the MCData-FD-3 reference point. + +#### 6.6.3.1.2 Media storage client + +The media storage client is used to support FD function of the MCData client for file distribution capability. FD function of the MCData client interacts with media storage client for uploading and downloading file to or from the media storage function of the MCData content server. + +#### 6.6.3.1.3 Transmission/Reception control + +This functional entity is responsible for transmission and reception control of MCData file data between the sending MCData UE, the MCData server, and the receiving MCData UE. Transmission and reception control function is used to provide arbitration between multiple data requests and apply the necessary policy to ensure that appropriate data is transmitted between the MCData UE. However, when the file distribution requests are exceeding a certain size, it may be necessary to control the data that is transmitted or received by the MCData UEs. The control is subject to criteria like application level priorities (e.g. user priority, group priority), service type, emergency nature of the communication, etc. + +#### 6.6.3.1.4 Media storage function + +The media storage function is responsible for the storing of media uploaded by the media storage client of the MCData UE in case of MCData file distribution. It also supports download of stored media by the MCData UE in case of file distribution via media storage client. + +The media storage function supports partial download requests of stored media by the MCData UE via media storage client. + +#### 6.6.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +### 6.6.4 Reference points + +#### 6.6.4.1 Application plane + +##### 6.6.4.1.1 Reference point MCData-FD-1 (between the FD functions of the MCData client and the MCData server) + +MCData-FD-1 reference point is used for MCData application signalling for establishing a session in support of MCData file distribution. The bearer is also used for both uplink and downlink unicast data (e.g., URL associated to file, file download completed report). The MCData-FD-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. MCData-FD-1 reference point can be used as long as the file size does not exceed the capabilities (e.g. payload or transmission limits) provided by MCData-FD-1. + +Messages supported on this interface include the uplink and the downlink unicast file transaction between the MCData clients in MCData communication via the MCData server for: + +- metadata (file size, type etc.) of the file being distributed; +- URL of the file being distributed; +- sending download completed report; +- small size file; +- conversation identifier for message thread indication; and +- application plane identities for the MCData user and MCData application. + +Messages supported on this interface may also include the MCData client providing the MCData server with + +- MCData application signalling for establishing a file distribution session in support of MCData communication. + +##### 6.6.4.1.2 Reference point MCData-FD-2 (unicast between the FD functions of the MCData client and the MCData server) + +The MCData-FD-2 reference point, which exists between the FD functions of the MCData client and the MCData server, is used for unicast file transaction between MCData server and MCData client. The MCData-FD-2 reference point uses the SGi reference point defined in 3GPP TS 23.002 [10]. + +Reference point MCData-FD-2 supports the following functions: + +- file being distributed from and to the MCData client; +- conversation identifier for message thread indication; and +- application plane identities for the MCData user and MCData application. + +##### 6.6.4.1.3 Reference point MCData-FD-3 (multicast between the FD functions of the MCData client and the MCData server) + +The MCData-FD-3 reference point, which exists between the FD functions of the MCData client and the MCData server, is used by the FD function of the MCData server to send downlink multicast file data to the FD function of the + +MCData client. The MCData-FD-3 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [8] or the xMB-U interface as defined in 3GPP TS 26.348 [20]. + +#### 6.6.4.1.4 Reference point MCData-FD-4 (media storage function and media storage client) + +The MCData-FD-4 reference point, which exists between the media storage function and the media storage client, is used by the media storage client of MCData UE to upload and download file to the media storage function of the MCData content server. The MCData-FD-4 reference point uses the HTTP reference point. + +#### 6.6.4.1.5 Reference point MCData-FD-5 (FD function and media storage function) + +The MCData-FD-5 reference point, which exists between FD function and the media storage function, is used by the FD function of MCData server to fetch the file in the MCData content server that was uploaded by the media storage client of a MCData UE for multicast delivery using MBMS. It also supports necessary operational functions such as size check for transmission control etc. The MCData-FD-5 reference point uses the HTTP reference point. + +#### 6.6.4.2 Signalling control plane + +The description of the signalling control plane reference points is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +### 6.7 Functional model for data streaming + +#### 6.7.1 On-network functional model + +Figure 6.7.1-1 shows the application plane functional model for data streaming. + +![Figure 6.7.1-1: Application plane functional model for data streaming. The diagram shows the functional architecture for data streaming between an MCData server and an MCData UE, separated by an EPS. The MCData server contains a 'Data streaming and distribution function' and a 'Transmission / Reception control' function. The MCData UE contains an 'MCData client' with a 'DS function' and a 'Message store client'. The 'MCData Message store' is located within the MCData server. Reference points are labeled: MCData-DS-1 (between MCData server and MCData client), MCData-DS-2 (between Data streaming and distribution function and DS function), MCData-DS-3 (between Data streaming and distribution function and DS function), MCData-8 (between Transmission / Reception control and MCData client), and MCData-7 (between MCData Message store and Message store client).](e4a14961bdc9882e296b25f7ae5f9760_img.jpg) + +Figure 6.7.1-1: Application plane functional model for data streaming. The diagram shows the functional architecture for data streaming between an MCData server and an MCData UE, separated by an EPS. The MCData server contains a 'Data streaming and distribution function' and a 'Transmission / Reception control' function. The MCData UE contains an 'MCData client' with a 'DS function' and a 'Message store client'. The 'MCData Message store' is located within the MCData server. Reference points are labeled: MCData-DS-1 (between MCData server and MCData client), MCData-DS-2 (between Data streaming and distribution function and DS function), MCData-DS-3 (between Data streaming and distribution function and DS function), MCData-8 (between Transmission / Reception control and MCData client), and MCData-7 (between MCData Message store and Message store client). + +**Figure 6.7.1-1: Application plane functional model for data streaming** + +In the model shown in figure 6.7.1-1, the following apply: + +- MCData-DS-1 reference point is used for MCData application signalling for establishing a session in support of MCData data streaming. The bearer is also used for both uplink and downlink unicast stream download reports (e.g. stream start and stop records). +- MCData-DS-2 reference point carries unicast data stream between the data streaming and distribution function of the MCData server and the DS function of the MCData UE. The bearer is used for both uplink and downlink unicast data streaming. +- MCData-DS-3 reference point carries multicast data stream from the data streaming and distribution function of the MCData server to the DS function of the MCData UE. The bearer is used for downlink multicast data streaming. + +## 6.7.2 Off-network functional model + +## 6.7.3 Functional entities description + +### 6.7.3.1 Application plane + +#### 6.7.3.1.1 DS function + +DS function of the MCData client is responsible to handle DS capability related requests and responses for data streaming. FD function may interact with storage entity for retrieving the locally stored data for data streaming. + +#### 6.7.3.1.2 Data streaming and distribution function + +The data streaming and distribution function is responsible for the distribution of data stream to MCData communication participants. The data streaming and distribution function provides the following functionality: + +- reception of uplink data stream transmission by means of the MCData-DS-2 reference point; +- replicate the data stream as needed for distribution to those MCData communication participants using unicast transport; +- distribute downlink data stream by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of MCData-DS-2 reference point; and +- distribute downlink data stream using multicast downlink transport by means of the MCData-DS-3 reference point. + +#### 6.7.3.1.3 Transmission/Reception control + +This functional entity is responsible for transmission and reception control of data stream between the sending MCData UE, the MCData server, and the receiving MCData UE. Transmission and reception control function is used to provide arbitration between multiple data requests and apply the necessary policy to ensure that appropriate data is transmitted between the MCData UEs. + +### 6.7.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +## 6.7.4 Reference points + +### 6.7.4.1 Application plane + +#### 6.7.4.1.1 Reference point MCData-DS-1 (between the data streaming and distribution function and the DS function) + +MCData-DS-1 reference point is used for MCData application signalling for establishing a session in support of MCData data streaming. The bearer is also used for both uplink and downlink unicast stream download reports (e.g., stream start and stop records). The MCData-DS-1 reference point shall use the SIP-1 and SIP-2 reference points for transport and routing of SIP signalling. + +Messages supported on this interface includes the uplink and the downlink unicast data stream between the MCData clients MCData communication via the MCData server for + +- metadata of the data being streamed; +- URL of the data being streamed; +- sending stream download report; +- conversation identifier for message thread indication; and +- application plane identities for the MCData user and MCData application. + +Messages supported on this interface may also include the MCData client providing the MCData server with + +- MCData application signalling for establishing a UE data streaming session in support of MCData communication. + +### 6.7.4.1.2 Reference point MCData-DS-2 (unicast between the data streaming and distribution function and the DS function) + +The MCData-DS-2 reference point, which exists between the data streaming and distribution function and the DS function, is used to unicast data stream between the data streaming and distribution function of the MCData server and the DS function of the MCData client. The MCData-DS-2 reference point uses the SGi reference point defined in 3GPP TS 23.002 [10]. + +MCData-DS-2 supports the following functions: + +- stream data from MCData UE; +- stream data from network; +- data stream controls from the authorized MCData UE; +- stream data stream controls from the MCData UE over uplink; +- start and stop data stream from MCData UE over downlink; +- conversation identifier for message thread indication; and +- application plane identities for the MCData user and MCData application. + +### 6.7.4.1.3 Reference point MCData-DS-3 (multicast between the data streaming and distribution function and the DS function) + +The MCData-DS-3 reference point, which exists between the data streaming and distribution function and the DS function, is used by the data streaming and distribution function of the MCData server to send multicast data stream to the DS function of the MCData client. The MCData-DS-3 reference point uses the MB2-U interface defined in 3GPP TS 23.468 [8]. + +### 6.7.4.2 Signalling control plane + +The description of the signalling control plane reference points is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +## 6.8 Functional model for IP connectivity + +### 6.8.1 On-network functional model + +Figure 6.5.1-1 shows the application plane functional model for User-IP connectivity. + +![Figure 6.8.1-1: Application plane functional model for IP connectivity. The diagram shows an MCData server on the left and an MCData UE on the right, separated by an EPS boundary. The MCData server contains an 'IPcon distribution function' and a 'Transmission / Reception control' block. The MCData UE contains an 'MCData client' which includes an 'IPcon function'. Three reference points, MCData-IPcon-1, MCData-IPcon-2, and MCData-IPcon-3, connect the IPcon distribution function to the IPcon function. An 'IPcon-host' connection extends from the IPcon function to the right.](10d81b2cc455e3563e3e562a7f451124_img.jpg) + +Figure 6.8.1-1: Application plane functional model for IP connectivity. The diagram shows an MCData server on the left and an MCData UE on the right, separated by an EPS boundary. The MCData server contains an 'IPcon distribution function' and a 'Transmission / Reception control' block. The MCData UE contains an 'MCData client' which includes an 'IPcon function'. Three reference points, MCData-IPcon-1, MCData-IPcon-2, and MCData-IPcon-3, connect the IPcon distribution function to the IPcon function. An 'IPcon-host' connection extends from the IPcon function to the right. + +**Figure 6.8.1-1: Application plane functional model for IP connectivity** + +In the model shown in figure 6.8.1-1, the following apply: + +- MCData-IPcon-1 reference point is used for MCData application signalling for establishing a session in support of MCData IP connectivity. +- MCData-IPcon-2 reference point carries bidirectional IP Data for point-to-point MCData IP connectivity over the media plane between the U-IPcon distribution function of the MCData server and the IPcon function of the MCData client(s). +- MCData-IPcon-3 reference point is used by the IP-con distribution function of the MCData server to send unidirectional downlink IP Data to the IP-con function of the MCData clients. +- IPcon-host reference point is used for a data host, e.g. server, to use IP connectivity service capabilities. This reference point is outside the scope of the present document. + +## 6.8.2 Off-network functional model + +## 6.8.3 Functional entities description + +### 6.8.3.1 Application plane + +#### 6.8.3.1.1 IP connectivity function + +IP connectivity function of the MCData client is responsible to handle IPcon capability related requests and responses. + +#### 6.8.3.1.2 IPcon distribution function + +The IPcon distribution function of the MCData server is responsible for the distribution of IP Data to MCData communication participants. The IPcon distribution function of the MCData server provides the following functionality: + +- reception of uplink IP Data transmission by means of the MCData-IPcon-2 reference points; +- replicate the IP Data as needed for distribution to those MCData communication participants using unicast transport; +- distribute downlink data by IP unicast transmission to those MCData communication participants utilizing unicast transport by means of the MCData-IPcon-2 reference points; and +- distribute downlink IP Data using multicast downlink transport by means of the MCData-IPcon-3 reference point. + +#### 6.8.3.1.3 Transmission/Reception control + +This functional entity is responsible for transmission and reception control of IP Data transaction between the sending MCData client, the MCData server, and the receiving MCData client. Transmission and reception control function is used to provide arbitration between multiple data requests and apply the necessary policy to ensure that appropriate IP Data are transmitted between the MCData clients. + +### 6.8.3.2 Signalling control plane + +The description of the signalling control plane is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +## 6.8.4 Reference points + +### 6.8.4.1 Application plane + +#### 6.8.4.1.1 Reference point MCData-IPcon-1 (between the IPcon distribution function and the U-IPcon function) + +MCData-IPcon-1 reference point is used for MCData application signalling for establishing a session in support of MCData IP connectivity. + +#### 6.8.4.1.2 Reference point MCData-IPcon-2 (unicast between the U-IPcon distribution function and the U-IPcon function) + +MCData-IPcon-2 reference point carries bidirectional IP Data for point-to-point MCData IP connectivity over the media plane between the IPcon distribution function of the MCData server and the IPcon function of the MCData client(s). + +#### 6.8.4.1.3 Reference point MCData-IPcon-3 (multicast between the IPcon distribution function and the IPcon function) + +MCData-IPcon-3 reference point carries downlink unidirectional IP Data over the media plane between the IPcon distribution function of the MCData server and the IPcon function of the MCData client(s). + +#### 6.8.4.2 Signalling control plane + +The description of the signalling control plane reference points is contained in the common functional architecture to support MC services as specified in 3GPP TS 23.280 [5]. + +--- + +## 6A Identities + +The MCData service specific identities (e.g. MCData ID, MCData group ID) are described in clause 8 of 3GPP TS 23.280 [5]. + +--- + +## 6B Application of functional model to deployments + +The application of the functional model to deployments, and description of various deployment scenarios for the MCData service, can be found in clause 9 of 3GPP TS 23.280 [5]. + +--- + +## 7 Procedures and information flows + +### 7.1 MCData service configuration + +The MCData service shall support the procedures and related information flows as specified in subclause 10.1 and Annex A of 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; +- The MC service ID is the MCData ID; and +- The MC service user profile index is the MCData user profile index. + +### 7.2 Affiliation and de-affiliation to/from MCData group(s) + +The MCData service shall support the procedures and related information flows as specified in subclause 10.8 of 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; +- The MC service group is the MCData group; +- The MC service ID is the MCData ID; and +- The MC service group ID is the MCData group ID. + +When an MCData user has affiliated to an MCData group then the MCData user can send and receive MCData related media for that MCData group. When an MCData user has de affiliated from an MCData group then the MCData user cannot send and receive MCData related media to and from that MCData group. + +## 7.3 Use of MBMS transmission (on-network) + +### 7.3.1 Information flows for MBMS Transmission + +Information flows for generic MBMS procedures are defined in 3GPP TS 23.280 [5]. + +### 7.3.2 Use of pre-established MBMS bearers + +The MCData service shall support the procedure for using pre-established MBMS bearers as specified in 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; and +- The MC service ID is the MCData ID. + +The MCData service shall use the MCData-6, MCData-SDS-1, MCData-SDS-2, MCData-SDS-3, MCData-FD-1, MCData-FD-3, MCData-DS-1 and MCData-DS-3 reference points for this procedure. + +MCData may use pre-established MBMS bearer for the MCData features short data service, file distribution and data streaming. The MBMS bearer can be used by any group. Depending on the capacity of the MBMS bearer, the bearer can be used to broadcast one or more services in parallel. + +Both the media packets as well as the transmission control messages to the receiving users may be sent on the MBMS bearer. Optionally a separate MBMS bearer could be used for the transmission control messages, due to different bearer characteristic requirements. + +### 7.3.3 Use of dynamic MBMS bearer establishment + +The MCData service shall support the procedure for using pre-established MBMS bearers as specified 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; and +- The MC service ID is the MCData ID. + +The MCData service shall use the MCData-6, MCData-DS-1 and MCData-DS-3 reference points for this procedure. + +MCData may use dynamic MBMS bearer for the MCData feature data streaming. The MBMS bearer can be used by any group. Depending on the capacity of the MBMS bearer, the bearer can be used to broadcast one or more services in parallel. + +For file distribution using the media plane (7.5.2.7), the use of dynamic MBMS bearer is not supported. Both the media packets as well as the transmission control messages to the receiving users may be sent on the MBMS bearer. Optionally a separate MBMS bearer could be used for the transmission control messages, due to different bearer characteristic requirements. + +### 7.3.4 Switching from MBMS bearer to unicast bearer + +The MCData service shall support the procedure for switching from MBMS bearer to unicast bearer as specified 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; and +- The MC service ID is the MCData ID. + +The MCData service shall use the MCData-SDS-1, MCData-SDS-2, MCData-FD-1, MCData-FD-3, MCData-DS-1 and MCData-DS-3 reference points for this procedure. + +## 7.3.5 Use of MBMS user services for file distribution + +### 7.3.5.1 General + +This subclause defines information flows and procedures for usage of MBMS user services that applies to MCData file distribution. MBMS user services can be used for any MC service group. + +### 7.3.5.2 Information flows for MBMS user service usage + +#### 7.3.5.2.1 MBMS user service announcement + +Table 7.3.5.2.1-1 describes the information flow MBMS bearer announcement from the MCData server to the MCData client. + +**Table 7.3.5.2.1-1: MBMS user service announcement** + +| Information element | Status | Description | +|----------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------| +| MBMS user service id | M | Id of the MBMS user service | +| SA file | M | The service announcement file as returned in the create/update session response (subclause 5.4 in 3GPP TS 26.348 [19]) (see NOTE) | +| Monitoring state | O | The monitoring state is used to control if the client is actively monitoring the reception quality or the MBMS bearer used by the MBMS user service. | +| Unicast status | O | An indication that the listening status of the unicast bearer is requested. | +| NOTE: | | The SA file provides the TMGI, the list of MBMS service area identifiers, the frequency and the delivery parameters. | + +### 7.3.5.3 Procedures for MBMS user service usage + +#### 7.3.5.3.1 Use of pre-established MBMS user services + +##### 7.3.5.3.1.1 General + +In this scenario, the MCData server pre-establishes MBMS user service(s) in certain pre-configured areas before the initiation of a group file distribution. When a user originates a request for a file distribution in one of these areas, the MCData server can use the pre-established MBMS user service(s) for the DL media transmission. + +The MBMS user service can be announced prior to the file distribution or within the signalling message for the file distribution. + +The MBMS user service does not transmit application level control signalling. An MBMS bearer could be used for the application level control messages according to the generic MBMS procedures defined in 3GPP TS 23.280 [5]. + +##### 7.3.5.3.1.2 Procedure + +**Editor's note: The procedure in this clause needs to be revised considering that MBMS user services, as specified in 3GPP TS 26.346 [21], cannot be supported over the MB2 interface.** + +The procedure figure 7.3.5.3.1.2-1 shows only one of the receiving MCData clients using an MBMS user service. + +Pre-conditions: + +- The participating users are already affiliated. + +![Sequence diagram illustrating the use of pre-established MBMS user service between an MCData client and an MCData server.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant MCData client + participant MCData server + Note right of MCData server: 1. create MBMS user service + Note right of MCData server: 2. create MBMS session + Note right of MCData server: 3a. activate MBMS bearer + Note right of MCData server: 3b. generate SA File + MCData server->>MCData client: 4. MBMS user service announcement + Note left of MCData client: 5. MCData client stores MBMS user service id, TMGI(s), service area and other info about the MBMS User service, the MCData UE starts to monitor the TMGI(s). + MCData client->>MCData server: 6. MBMS listening status report + Note right of MCData server: 7. update MBMS session with new file to be distributed + Note over MCData client, MCData server: 8. Signalling file distribution. + Note over MCData client, MCData server: 9. File distribution over MBMS + +``` + +The diagram shows a sequence of interactions between an MCData client and an MCData server. The server initiates the process by creating an MBMS user service, session, and bearer, and generating an SA File. It then sends an MBMS user service announcement to the client. The client stores this information and starts monitoring the TMGI(s). The client sends a listening status report to the server, which updates the session with a new file. Finally, the server performs signalling file distribution, followed by file distribution over MBMS. + +Sequence diagram illustrating the use of pre-established MBMS user service between an MCData client and an MCData server. + +**Figure 7.3.5.3.1.2-1: Use of pre-established MBMS user service** + +1. The MCData server determines to create an MBMS user service with a given MBMS user service id. If the MCData server makes use of the xMB interface, the MCData server creates an MBMS user service over xMB-C (subclause 5.3 from 3GPP TS 26.348 [19]). + +NOTE 1: The procedure to determine the creation of MBMS user services is implementation specific. + +2. If the MCData server makes use of the xMB interface, the MCData server creates an MBMS session over xMB-C for the MBMS user service (subclause 5.4 from 3GPP TS 26.348 [19]), with the type set to "Files" to use the MBMS download delivery method. This MBMS session will be used for file distribution. In response, the MCData server gets the TMGI of the MBMS bearer used for the MBMS session, and the SA file containing the metadata of the MBMS user service. + +- 3a. Else, the MCData server activates an MBMS bearer over MB2-C for the MBMS user service. + +- 3b. The MCData server, if not already in the possession of the SA file, generates the SA file containing the metadata of the MBMS user service. + +4. The MCData server passes using control plane signalling the MBMS user service info for the service description associated with the pre-established MBMS user service to the MCData client. The MCData client obtains the TMGI, identifying the MBMS bearer, from the SA file included in the MBMS user service description. + +5. The MCData client stores the information associated with the MBMS user service. The MCData client uses the TMGI and other MBMS user service related information to activate the monitoring of the MBMS bearer. + +6. The MCData client that enters or is in the service area of at least one announced TMGI indicates to the MCData server that the MCData client is able to receive file distributed over MBMS, whereby the MCData server may decide to use this MBMS user service instead of unicast bearer for MC communication sessions. + +NOTE 2: Step 4 is optional for the MCData UE on subsequent MBMS user service announcements. + +NOTE 3: The information flow is specified in subclause 10.7.2.2 from 3GPP TS 23.280 [5]. + +7. If the MCData server makes use of the xMB interface and wants to deliver a file to a group, the MCData server updates the MBMS session to provide the file location and its uri. +8. The MCData server signals the file transmission over the MBMS user service to the targeted MCData clients. +9. The file, transmitted with the MBMS download delivery method, is received by the MCData clients. If the MCData server does not make use of the xMB interface, the MCData server fragments the file to be sent, applies error correction according to the MBMS download delivery method (3GPP TS 26.346 [21]) and sent the FLUTE packets over MB2-U. + +### 7.3.5.3.2 Use of dynamic MBMS user service establishment + +**Editor's note:** The procedure in this clause needs to be revised considering that MBMS user services, as specified in 3GPP TS 26.346 [21], cannot be supported over the MB2 interface. + +In this scenario depicted in figure 7.3.5.3.2-1, the MCData server decides to establish an MBMS user service for the distribution of a given file. The MBMS user service is announced to the MCData client, together with the file information to be received. + +NOTE 1: The MCData server logic for determining when to establish the new MBMS user service is implementation specific. For example, the MCData server could decide to establish the MBMS delivery based on the location of the UE's that are a part of the targeted group. + +![Sequence diagram illustrating the use of dynamic MBMS user service establishment between an MCData client and an MCData server.](4669a2ca9d019b9c2de9a9d9a0c4e644_img.jpg) + +``` + +sequenceDiagram + participant MCData client + participant MCData server + Note right of MCData server: 1.Create MBMS user service + Note right of MCData server: 2.Create MBMS session with info of the file to be distributed + Note right of MCData server: 3a. activate MBMS bearer + Note right of MCData server: 3b. generate SA File + MCData server->>MCData client: 4. MBMS user service announcement + Note left of MCData client: 5. MC service client stores MBMS user service ID, TMGI(s), service area and other info about the MBMS user service(s), the MC service UE starts to monitor the TMGI(s). + MCData client->>MCData server: 6. MBMS listening status report + Note over MCData client, MCData server: 7. Signalling file distribution + Note over MCData client, MCData server: 8. File distribution over MBMS + +``` + +The diagram is a sequence diagram showing the interaction between an MCData client and an MCData server. The sequence of messages is as follows: + + +- The MCData server performs internal steps: 1. Create MBMS user service, 2. Create MBMS session with info of the file to be distributed, 3a. activate MBMS bearer, and 3b. generate SA File. +- The MCData server sends a message labeled "4. MBMS user service announcement" to the MCData client. +- The MCData client performs an internal step: 5. MC service client stores MBMS user service ID, TMGI(s), service area and other info about the MBMS user service(s), the MC service UE starts to monitor the TMGI(s). +- The MCData client sends a message labeled "6. MBMS listening status report" to the MCData server. +- Both the MCData client and MCData server perform a step labeled "7. Signalling file distribution". +- Both the MCData client and MCData server perform a step labeled "8. File distribution over MBMS", represented by a large blue arrow pointing from the server to the client. + +Sequence diagram illustrating the use of dynamic MBMS user service establishment between an MCData client and an MCData server. + +**Figure 7.3.5.3.2-1: Use of dynamic MBMS user service establishment** + +1. The MCData server determines to create an MBMS user service with a given MBMS user service id for the group communication session. If the MCData server makes use of the xMB interface, the MCData server creates an MBMS user service over xMB-C (subclause 5.3 from 3GPP TS 26.348 [19]). +2. If the MCData server makes use of the xMB interface, the MCData server creates a MBMS session for the MBMS user service (subclause 5.4 from 3GPP TS 26.348 [19]), with the type set to "Files" to use the MBMS download delivery method, and provide the file location and its uri. In response, the MCData server gets the TMGI of the MBMS bearer used for the MBMS session, the SA file containing the metadata of the MBMS user service and the scheduling parameter for the file delivery. + +- 3a. Else, the MCData server activates an MBMS bearer over MB2-C for the MBMS user service. +- 3b. The MCData server, if not already in the possession of the SA file, generates the SA file containing the metadata of the MBMS user service. +4. The MCData server passes using control plane signalling the SA file to the MCData client. The MCData client obtains the TMGI, identifying the MBMS bearer, from the SA file included in the MBMS user service description. +5. The MCData client stores the information associated with the MBMS user service. The MCData client uses the TMGI and other MBMS user service related information to activate the monitoring of the MBMS bearer. +6. The MCData client that enters or is in the service area of at least one announced TMGI indicates to the MCData server that the MCData client is able to receive file distributed over MBMS, whereby the MCData server may decide to use this MBMS user service instead of unicast bearer for MC communication sessions. +7. The MCData server signals the file transmission over the MBMS user service to the targeted MCData clients. +8. The file, transmitted with the MBMS download delivery method, is received by the MCData clients. If the MCData server does not make use of the xMB interface, the MCData server fragments the file to be sent, applies error correction according to the MBMS download delivery method (3GPP TS 26.346 [21]) and sent the FLUTE packets over MB2-U. + +## 7.4 Short data service + +### 7.4.1 General + +There are several procedures how an SDS message can be transported from the sender to the recipient. All of the following factors are used by MCData client for selecting appropriate SDS procedures: + +- Whether the data to transfer is within or outside the SDS data size limit to transport over signalling control plane; +- Whether the MCData user has only one SDS transaction or multiple SDS transactions; +- Whether MCData user, optionally using its associated and activated functional alias, is targeting SDS transaction to another MCData user or MCData group; +- Whether MCData UE is on-network or off-network; and +- Security reasons. + +### 7.4.2 Short data service for on-network + +The procedures described in the following subclauses are limited to single MCData system only. + +#### 7.4.2.1 Information flows for short data service + +##### 7.4.2.1.1 MCData standalone data request + +Table 7.4.2.1.1-1 describes the information flow for the MCData standalone data request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.1-1: MCData standalone data request** + +| Information element | Status | Description | +|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Location | O | Location of the Originating MCData user sending the SDS | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE: | The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | + +#### 7.4.2.1.2 MCData data disposition notification + +Table 7.4.2.1.2-1 describes the information flow for the MCData data disposition notification sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.2-1: MCData data disposition notification** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| MCData ID | M | The identity of the MCData user sending notification | +| Conversation Identifier | M | Identifies the conversation | +| Disposition association | M | Identity of the original MCData transaction | +| Disposition | M | Disposition which is delivered or read or both | + +#### 7.4.2.1.3 MCData standalone session data request + +Table 7.4.2.1.3-1 describes the information flow for the MCData standalone session data request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.3-1: MCData standalone session data request** + +| Information element | Status | Description | +|-----------------------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Standalone transaction | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| NOTE: | | The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | + +#### 7.4.2.1.4 MCData standalone session data response + +Table 7.4.2.1.4-1 describes the information flow for the MCData standalone session data response sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.4-1: MCData standalone session data response** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +#### 7.4.2.1.5 MCData session data request + +Table 7.4.2.1.5-1 describes the information flow for the MCData session data request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.5-1: MCData session data request** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Session based transactions | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | +| NOTE: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +#### 7.4.2.1.6 MCData session data response + +Table 7.4.2.1.6-1 describes the information flow for the MCData session data response sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.6-1: MCData session data response** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +#### 7.4.2.1.7 MCData group standalone data request (MCData client – MCData server) + +Table 7.4.2.1.7-1 describes the information flow for the MCData group standalone data request (in subclause 7.4.2.5.2) sent from the MCData client to the MCData server. + +**Table 7.4.2.1.7-1: MCData group standalone data request (MCData client – MCData server)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Location | O | Location of the Originating MCData user sending the SDS | +| Application identifier (see NOTE 3) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | +| NOTE 3: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +#### 7.4.2.1.8 MCData group standalone data request (MCData server – MCData client) + +Table 7.4.2.1.8-1 describes the information flow for the MCData group standalone data request (in subclause 7.4.2.5.2) sent from the MCData server to the MCData client. + +**Table 7.4.2.1.8-1: MCData group standalone data request (MCData server – MCData client)** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Location | O | Location of the Originating MCData user sending the SDS | +| Application identifier (see NOTE 3) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | +| NOTE 3: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | | + +#### 7.4.2.1.9 MCData data disposition notification(s) (MCData server – MCData client) + +Table 7.4.2.1.9-1 describes the information flow for the MCData data disposition notification(s) sent from the MCData server to the MCData client. + +**Table 7.4.2.1.9-1: MCData data disposition notification(s) (MCData server – MCData client)** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| MCData ID | M | The identity of the MCData user sending notification | +| Conversation Identifier | M | Identifies the conversation | +| Disposition association | M | Identity of the original MCData transaction | +| Disposition | M | Disposition which is delivered or read or both | + +#### 7.4.2.1.10 MCData group session standalone data request (MCData client – MCData server) + +Table 7.4.2.1.10-1 describes the information flow for the MCData group session standalone data request (in subclause 7.4.2.6.2) sent from the MCData client to the MCData server. + +**Table 7.4.2.1.10-1: MCData group session standalone data request (MCData client – MCData server)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Standalone transaction | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE 3) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | +| NOTE 3: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +#### 7.4.2.1.11 MCData group session standalone data request (MCData server – MCData client) + +Table 7.4.2.1.11-1 describes the information flow for the MCData group session standalone data request (in subclause 7.4.2.6.2) sent from the MCData server to the MCData client. + +**Table 7.4.2.1.11-1: MCData group session standalone data request (MCData server – MCData client)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Standalone transaction | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE 3) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | +| NOTE 3: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +#### 7.4.2.1.12 MCData group session standalone data response + +Table 7.4.2.1.12-1 describes the information flow for the MCData group standalone data response (in subclause 7.4.2.6.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.12-1: MCData group session standalone data response** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +#### 7.4.2.1.13 MCData group data request (MCData client – MCData server) + +Table 7.4.2.1.13-1 describes the information flow for the MCData group data request sent from the MCData client to the MCData server. + +**Table 7.4.2.1.13-1: MCData group data request (MCData client – MCData server)** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Session based transactions | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE 3) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | +| NOTE 1: If used, only one of these information elements shall be present.
NOTE 2: This information element may be present only when Emergency indicator is present.
NOTE 3: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +#### 7.4.2.1.14 MCData group data request (MCData server – MCData client) + +Table 7.4.2.1.14-1 describes the information flow for the MCData group data request sent from the MCData server to the MCData client. + +**Table 7.4.2.1.14-1: MCData group data request (MCData server – MCData client)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| Functional alias | O | The associated functional alias of the MCData user sending data. | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the recipient MCData user | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Session based transactions | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Location | O | Location of the Originating MCData user sending the SDS message | +| Application identifier (see NOTE 3) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | +| NOTE 3: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +#### 7.4.2.1.15 MCData group data response + +Table 7.4.2.1.15-1 describes the information flow for the MCData group data response sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.15-1: MCData group data response** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +#### 7.4.2.1.16 MCData one-to-one SDS communication upgrade request + +Table 7.4.2.1.16-1 describes the information flow for the MCData one-to-one SDS communication upgrade request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.4.2.1.16-1: MCData one-to-one SDS communication upgrade request** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data (when initiated by MCData client);
The identity of the MCData user receiving data (when initiated by MCData server). | +| Functional alias | O | The associated functional alias of the MCData user sending data or receiving data. | +| Conversation Identifier | M | Identifies the conversation | +| Emergency indicator | M | Indicates that the data request is for MCData emergency communication | + +#### 7.4.2.1.17 MCDATA one-to-one SDS communication upgrade response + +Table 7.4.2.1.17-1 describes the information flow for the MCDATA one-to-one SDS communication upgrade response sent from the MCDATA client to the MCDATA server and from the MCDATA server to another MCDATA client. + +**Table 7.4.2.1.17-1: MCDATA one-to-one SDS communication upgrade response** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user sending data (when initiated by MCDATA client);
The identity of the MCDATA user receiving data (when initiated by MCDATA server). | +| Conversation Identifier | M | Identifies the conversation | + +#### 7.4.2.1.18 MCDATA group SDS communication upgrade request + +Table 7.4.2.1.18-1 describes the information flow for the MCDATA group SDS communication upgrade request sent from the MCDATA client to the MCDATA server and from the MCDATA server to another MCDATA client. + +**Table 7.4.2.1.18-1: MCDATA group SDS communication upgrade request** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user sending data (when initiated by MCDATA client);
The identity of the MCDATA user receiving data (when initiated by MCDATA server). | +| Functional alias | O | The associated functional alias of the MCDATA user sending data or receiving data. | +| MCDATA group ID | M | The MCDATA group ID on which the emergency upgrade request is made | +| Conversation Identifier | M | Identifies the conversation | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCDATA emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCDATA imminent peril communication | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +#### 7.4.2.1.19 MCDATA group SDS communication upgrade response + +Table 7.4.2.1.19-1 describes the information flow for the MCDATA group SDS communication upgrade response sent from the MCDATA client to the MCDATA server and from the MCDATA server to another MCDATA client. + +**Table 7.4.2.1.19-1: MCDATA group SDS communication upgrade response** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user sending data (when initiated by MCDATA client);
The identity of the MCDATA user receiving data (when initiated by MCDATA server). | +| MCDATA group ID | M | The MCDATA group ID on which the emergency upgrade request is made | +| Conversation Identifier | M | Identifies the conversation | + +#### 7.4.2.1.20 MCDATA group SDS communication in-progress priority state cancel request + +Table 7.4.2.1.20-1 describes the information for the MCDATA group SDS communication in-progress priority state cancel request sent from the MCDATA client to the MCDATA server and from the MCDATA server to another MCDATA client. + +**Table 7.4.2.1.20-1: MCData group SDS communication in-progress priority state cancel request** + +| Information Element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the cancelling party | +| MCData group ID | M | The MCData group ID on which the MCData in-progress emergency state is to be cancelled. | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Conversation Identifier | M | Identifies the conversation | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +#### 7.4.2.1.21 MCData group SDS communication in-progress priority state cancel response + +Table 7.4.2.1.21-1 describes the information flow for the MCData group SDS communication in-progress priority state cancel response sent from the MCData server to the MCData client. + +**Table 7.4.2.1.21-1: MCData group SDS communication in-progress priority state cancel response** + +| Information Element | Status | Description | +|-------------------------|--------|-----------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the cancelling party | +| MCData group ID | M | The MCData group ID on which the MCData in-progress emergency in-progress is to be cancelled. | +| Conversation Identifier | M | Identifies the conversation | + +#### 7.4.2.2 One-to-one standalone short data service using signalling control plane + +##### 7.4.2.2.1 General + +A MCData user initiates a standalone SDS data transfer with another MCData user. For the SDS data transfer signalling plane is used. + +##### 7.4.2.2.2 Procedure + +The procedure in figure 7.4.2.2.2-1 describes the case where an MCData user is initiating one-to-one MCData data communication for sending standalone SDS data to other MCData user, with or without disposition request. Standalone refers to sending unidirectional data in one transaction. + +Pre-conditions: + +1. The SDS payload data size is below the configured maximum payload data size for SDS over signalling control plane. +2. MCData users on MCData client 1 and MCData client 2 are already registered for receiving MCData service. +3. MCData client 1 and MCData client 2 belong to the same MCData system. +4. Optionally, the MCData client may have activated functional alias to be used. +5. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating the One-to-one standalone short data service using signalling control plane. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData standalone data request + Note right of MCData server: 3. Authorize request and policy assertion + MCData server->>MCData client 2: 4. MCData standalone data request + Note right of MCData client 2: 5. Process payload + MCData client 2-->>MCData server: 6. MCData data disposition notification + MCData server-->>MCData client 1: 7. MCData data disposition notification + MCData client 2-->>MCData server: 8. MCData data disposition notification + MCData server-->>MCData client 1: 9. MCData data disposition notification + +``` + +Sequence diagram illustrating the One-to-one standalone short data service using signalling control plane. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. + +**Figure 7.4.2.2.2-1: One-to-one standalone short data service using signalling control plane** + +1. The user at MCData client 1 initiates an SDS data transfer for the chosen MCData user. + 2. MCData client 1 sends a MCData standalone data request towards the MCData server. The MCData standalone data request contains conversation identifier for message thread indication. The MCData standalone data request may contain disposition request if indicated by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the SDS data transfer. + - a) If the MCData user at the MCData client 1 initiates an MCData emergency short data service communication or MCData emergency state is already set for the MCData client 1 (due to previously triggered MCData emergency alert): + - i) The MCData standalone data request shall contain emergency indicator; and + - ii) If MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled. + 3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData standalone data request. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the user. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege or affiliation. +- NOTE: The MCData server prioritizes the MCData emergency communication over the other MCData communication. How the MCData server prioritizes MCData emergency communication is not in the scope of the present document. +4. MCData server initiates the MCData standalone data request towards the MCData user. The MCData standalone data request towards the MCData user contains the emergency indicator if it is present in the received MCData standalone data request from MCData client 1. + 5. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData client 2 shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. + +6. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client initiates a MCData data disposition notification for delivery report. The MCData data disposition notification from MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. +7. MCData data disposition notification is sent to the disposition requesting user at MCData client 1. +8. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. The MCData data disposition notification from MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. The MCData data disposition notification from MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. +9. MCData data disposition notification is sent to the disposition requesting user at MCData client 1. + +### 7.4.2.3 One-to-one standalone short data service using media plane + +#### 7.4.2.3.1 General + +A MCData user initiates a standalone SDS data transfer with another MCData user. For the SDS data transfer media plane is used. + +#### 7.4.2.3.2 Procedure + +The procedure in figure 7.4.2.3.2-1 describes the case where an MCData user is initiating one-to-one MCData data communication for sending standalone SDS data to other MCData user, with or without disposition request. Standalone refers to sending unidirectional data in one transaction. The SDS payload data size is assumed to be above the configured maximum payload data size for SDS over signalling control plane. + +Pre-conditions: + +1. MCData users on MCData client 1 and MCData client 2 are already registered for receiving MCData service. +2. MCData client 1 and MCData client 2 belong to the same MCData system. +3. Optionally, the MCData client may have an activated functional alias to be used. +4. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for One-to-one standalone short data service using media plane. Lifelines: MCData client 1, MCData server, MCData client 2. The sequence starts with MCData client 1 initiating a data request. MCData client 1 sends an MCData standalone session data request to the MCData server. The MCData server sends an authorize request and policy assertion to MCData client 1. The MCData server then sends an MCData standalone session data request to MCData client 2. MCData client 2 responds with an MCData standalone session data response to the MCData server. The MCData server then sends an MCData standalone session data response to MCData client 1. A data transmission block occurs between MCData client 1 and MCData client 2. MCData client 2 processes the payload and sends MCData data disposition notifications to the MCData server. The MCData server then sends MCData data disposition notifications to MCData client 1.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData standalone session data request + MCData server-->>MCData client 1: 3. Authorize request and policy assertion + MCData server->>MCData client 2: 4. MCData standalone session data request + MCData client 2-->>MCData server: 5. MCData standalone session data response + MCData server-->>MCData client 1: 6. MCData standalone session data response + Note over MCData client 1, MCData client 2: 7. Data transmission + Note right of MCData client 2: 8. Process payload + MCData client 2-->>MCData server: 9. MCData data disposition notification + MCData server-->>MCData client 1: 10. MCData data disposition notification + MCData client 2-->>MCData server: 11. MCData data disposition notification + MCData server-->>MCData client 1: 12. MCData data disposition notification + +``` + +Sequence diagram for One-to-one standalone short data service using media plane. Lifelines: MCData client 1, MCData server, MCData client 2. The sequence starts with MCData client 1 initiating a data request. MCData client 1 sends an MCData standalone session data request to the MCData server. The MCData server sends an authorize request and policy assertion to MCData client 1. The MCData server then sends an MCData standalone session data request to MCData client 2. MCData client 2 responds with an MCData standalone session data response to the MCData server. The MCData server then sends an MCData standalone session data response to MCData client 1. A data transmission block occurs between MCData client 1 and MCData client 2. MCData client 2 processes the payload and sends MCData data disposition notifications to the MCData server. The MCData server then sends MCData data disposition notifications to MCData client 1. + +**Figure 7.4.2.3.2-1: One-to-one standalone short data service using media plane** + +1. User at MCData client 1 would like to initiate a SDS data transfer request for the chosen MCData user. + 2. MCData client 1 sends a MCData standalone session data request towards the MCData server. The MCData standalone session data request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData standalone session data request contains conversation identifier for message thread indication. The MCData data request may contain disposition request if indicated by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the SDS data transfer. + - a) If the MCData user at the MCData client 1 initiates an MCData emergency short data service communication or MCData emergency state is already set for the MCData client 1 (due to previously triggered MCData emergency alert): + - i) The MCData standalone session data request shall contain emergency indicator; and + - ii) If MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled. + 3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData standalone session data request. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the user. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. MCData server determines the eligible MCData user(s) after policy assertion for sending the MCData standalone session data request. +- NOTE: The MCData server prioritizes the MCData emergency communication over the other MCData communication. How the MCData server prioritizes MCData emergency communication is not in the scope of the present document. +4. MCData server initiates the MCData standalone session data request towards the MCData user. The MCData standalone session data request towards the MCData user contains an emergency indicator if it is present in the received MCData standalone session data request from MCData client 1. + 5. The receiving MCData client 2 automatically accepts the MCData standalone session data request and responds with MCData standalone session data response towards MCData server. + +6. MCData server forwards the MCData client 2 accepted response to the MCData user initiating the MCData standalone session data request. +7. MCData client 1 and MCData client 2 have successfully established media plane for data communication and the MCData client 1 transmits the SDS data. +8. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData client 2 shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. +9. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client initiates a MCData data disposition notification for delivery report. The MCData data disposition notification from the receiving MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. +10. MCData data disposition notification is sent to the disposition requesting user at MCData client 1. +11. If the MCData disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData disposition notification for read report. The MCData data disposition notification from the receiving MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. +12. MCData data disposition notification is sent to the disposition requesting user at MCData client 1. + +#### 7.4.2.4 One-to-one short data service session + +##### 7.4.2.4.1 General + +A MCData user triggers an establishment of a MCData session with another MCData user for the exchange of SDS data. + +##### 7.4.2.4.2 Procedure + +The procedure in figure 7.4.2.4.2-1 describes the case where an MCData user is initiating data communication session with another MCData user for exchanging at least one SDS data transaction between them, with or without disposition request using MCData-SDS-1 and MCData-SDS-2 or MCData-SDS-3 reference points. + +Pre-conditions: + +1. MCData users on MCData client 1 and MCData client 2 are already registered for receiving MCData service. +2. Optionally, the MCData client may have activated functional alias to be used. +3. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for One-to-one short data service session. Lifelines: MCData client 1, MCData server, MCData client 2. The sequence starts with MCData client 1 initiating a session data request. The server authorizes and asserts a policy. The server then sends a request to MCData client 2, which notifies the user. Data transmission and disposition occur between client 1 and the server, and then between client 2 and the server. Finally, the session is terminated.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate session data request + MCData client 1->>MCData server: 2. MCData session data request + MCData server->>MCData server: 3. Authorize request and policy assertion + MCData server->>MCData client 2: 4. MCData session data request + Note right of MCData client 2: 5. Notify request + MCData client 2->>MCData server: 6. MCData session data response + MCData server->>MCData client 1: 7. MCData session data response + Note over MCData client 1, MCData server: 8. Data transmission and disposition + Note right of MCData client 2: 9. Notify data + Note over MCData client 2, MCData server: 10. Data transmission and disposition + Note left of MCData client 1: 11. Notify data + Note over MCData client 1, MCData server: 12. Session data termination + +``` + +Sequence diagram for One-to-one short data service session. Lifelines: MCData client 1, MCData server, MCData client 2. The sequence starts with MCData client 1 initiating a session data request. The server authorizes and asserts a policy. The server then sends a request to MCData client 2, which notifies the user. Data transmission and disposition occur between client 1 and the server, and then between client 2 and the server. Finally, the session is terminated. + +**Figure 7.4.2.4.2-1: One-to-one short data service session** + +1. User at MCData client 1 would like to initiate a SDS data communication session request for the chosen MCData user. + 2. MCData client 1 sends a MCData session data request towards the MCData server. The MCData session data request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData session data request contains conversation identifier for message thread indication. MCData user at MCData client 1 may include a functional alias within the SDS data transfer. + - a) If the MCData user at the MCData client 1 initiates an MCData emergency short data service communication or MCData emergency state is already set for the MCData client 1 (due to previously triggered MCData emergency alert): + - i) The MCData session data request shall contain emergency indicator; and + - ii) If MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled. + 3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData session data request. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. MCData server determines the eligible MCData user(s) after policy assertion for sending the MCData session data request. MCData server also verifies whether the provided functional alias, if present, can be used and has been activated for the user. +- NOTE:** The MCData server prioritizes the MCData emergency communication over the other MCData communication. How the MCData server prioritizes MCData emergency communication is not in the scope of the present document. +4. MCData server initiates the MCData session data request towards the MCData user determined. The MCData session data request towards the MCData user contains the emergency indicator if it is present in the received MCData session data request from MCData client 1. + 5. If the emergency indicator is present, the receiving MCData client 2 notifies the user about the incoming MCData session data request. + +6. The receiving MCData client 2 accepts the MCData session data request and responds with MCData session data response towards MCData server. +7. MCData server forwards the MCData client 2 accepted response to the MCData user initiating the MCData session data request. +8. and 10. MCData client 1 and MCData client 2 have successfully established media plane for data communication and either MCData client can transmit SDS data. The MCData data request may contain disposition request if indicated by the client sending data. If MCData data disposition was requested by the user, then the receiving MCData client initiates a MCData data disposition notification for delivery, read reports to the disposition requesting user. The MCData data disposition notification from MCData user may be stored by the MCData server for disposition history interrogation from authorized users. +9. and 11. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 may be notified, otherwise the MCData user of MCData client 2 shall not be notified. +12. After SDS data transaction is complete, the established media plane is released. + +#### 7.4.2.5 Group standalone short data service using signalling control plane + +##### 7.4.2.5.1 General + +The initiation of a group standalone SDS to a selected group results in affiliated group members receiving the SDS data. The SDS payload data size is assumed to be below the configured maximum payload data size for SDS over signalling control plane. + +##### 7.4.2.5.2 Procedure + +The procedure in figure 7.4.2.5.2-1 describes the case where an MCData user is initiating group standalone MCData data communication with or without disposition request, to a group. + +Pre-conditions: + +1. MCData users on MCData clients 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. +2. Optionally, the MCData client may have activated functional alias to be used. +3. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating Group standalone SDS using signalling control plane. The diagram shows interactions between MCData client 1, MCData server, Group management server, and MCData client 2 to n. The sequence of messages is: 1. initiate group standalone data request (client 1 to server), 2. MCData group standalone data request (client 1 to server), 2a. Affiliate user to group (server to group management server), 3. Resolve group id (group management server to server), 4. MCData group standalone data request (server to clients 2 to n), 5. Process payload (clients 2 to n), 6. MCData data disposition notification (clients 2 to n to server), 7. MCData data disposition notification (clients 2 to n to server), 8. Aggregate notifications (server to group management server), 9. MCData data disposition notification(s) (server to client 1).](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate group standalone data request + MCData client 1->>MCData server: 2. MCData group standalone data request + Note right of MCData server: 2a. Affiliate user to group + MCData server->>Group management server: 3. Resolve group id + MCData server->>MCData client 2 to n: 4. MCData group standalone data request + Note right of MCData client 2 to n: 5. Process payload + MCData client 2 to n->>MCData server: 6. MCData data disposition notification + MCData client 2 to n->>MCData server: 7. MCData data disposition notification + Note right of MCData server: 8. Aggregate notifications + MCData server->>MCData client 1: 9. MCData data disposition notification(s) + +``` + +Sequence diagram illustrating Group standalone SDS using signalling control plane. The diagram shows interactions between MCData client 1, MCData server, Group management server, and MCData client 2 to n. The sequence of messages is: 1. initiate group standalone data request (client 1 to server), 2. MCData group standalone data request (client 1 to server), 2a. Affiliate user to group (server to group management server), 3. Resolve group id (group management server to server), 4. MCData group standalone data request (server to clients 2 to n), 5. Process payload (clients 2 to n), 6. MCData data disposition notification (clients 2 to n to server), 7. MCData data disposition notification (clients 2 to n to server), 8. Aggregate notifications (server to group management server), 9. MCData data disposition notification(s) (server to client 1). + +**Figure 7.4.2.5.2-1: Group standalone SDS using signalling control plane** + +1. The user at MCData client 1 initiates an SDS data transfer to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +2. MCData client 1 sends a MCData group standalone data request towards the MCData server. The MCData group data request contains MCData group ID as selected by the user at MCData client 1. The MCData group standalone data request contains conversation identifier for message thread indication. The MCData group standalone data request may contain disposition request if indicated by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the SDS data transfer. + +If the MCData user at MCData client 1 initiates an MCData emergency short data service communication or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert): + +- i) the MCData group standalone data request shall contain an emergency indicator; +- ii) the MCData group standalone data request shall set an alert indicator if configured to send an MCData emergency alert while initiating an MCData standalone data request for the emergency short data service communication; +- iii) if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCPTT emergency state is retained until explicitly cancelled; and +- iv) once an MCData emergency communication has been initiated, the MCData group is considered to be in an in-progress emergency state until cancelled; + +If the MCData user at MCData client 1 initiates an MCData imminent peril short data service communication: + +- i) the MCData group standalone data request shall contain imminent peril indicator; and +- ii) once an MCData imminent peril communication has been initiated, the MCData group is considered to be in an in-progress imminent peril state until cancelled. + +- 2a. If either emergency indicator or imminent peril indicator is present in the received MCData group standalone data request, the MCData server implicitly affiliates MCData client 1 to the MCData group if the client is not already affiliated. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData group standalone data request. The MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege or affiliation. MCData server also verifies whether the provided functional alias, if present, can be used and has been activated for the user. + - i) If an emergency indicator is present in the received MCData group standalone data request and if the MCData group is not in the in-progress emergency state, the MCData group is considered to be in the in-progress emergency state until cancelled; + - ii) If an imminent peril indicator is present in the received MCData group standalone data request and if the MCData group is not in the in-progress imminent peril state, the MCData group is considered to be in the in-progress imminent peril state until cancelled; +4. MCData server initiates the MCData group standalone data request towards each MCData client determined in Step 3. The MCData group standalone data request towards each MCData client contains: + - i) an emergency indicator if it is present in the received MCData group standalone data request from the MCData client 1; + - ii) an imminent peril indicator if it is present in the received MCData group standalone data request from the MCData client 1; and + - iii) an alert indicator if requested to initiate an emergency alert in the received MCData group standalone data request from the MCData client 1. +5. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData clients 2 to n may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData clients 2 to n shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. +6. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client(s) initiates a MCData data disposition notification for delivery report. +7. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. +8. The MCData data disposition notification(s) from MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. The MCData data disposition notification(s) from each MCData user may be aggregated. +9. Aggregated or individual MCData data disposition notification(s) is sent to the disposition requesting user at MCData client 1. + +#### 7.4.2.6 Group standalone short data service using media plane + +##### 7.4.2.6.1 General + +The initiation of a group standalone SDS to a selected group results in affiliated group members receiving the SDS data. The SDS payload data size is assumed to be above the configured maximum payload data size for SDS over signalling control plane. + +##### 7.4.2.6.2 Procedure + +The procedure in figure 7.4.2.6.2-1 describes the case where an MCData user is initiating group standalone MCData data communication with or without disposition request to a group. + +Pre-conditions: + +1. MCData users on MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. +2. Optionally, the MCData client may have activated functional alias to be used. +3. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for Group standalone SDS using media plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. The sequence shows steps from initiating a data request to processing the payload and sending notifications.](3c04b14104f95eb8f7100f6d497d956e_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData group session standalone data request + Note right of MCData server: 2a. Affiliate user to group + Note right of MCData server: 3. Resolve group id + Note right of MCData server: 3a. Bearer priority configuration + MCData server->>MCData client 2 to n: 4. MCData group session standalone data request + MCData client 2 to n-->>MCData server: 5. MCData group session standalone data response + MCData server-->>MCData client 1: 6. MCData group session standalone data response + Note left of MCData server: 7. Data transmission + Note right of MCData server: 8. Data transmission + Note right of MCData client 2 to n: 9. Process payload + MCData client 2 to n-->>MCData server: 10. MCData data disposition notification + MCData client 2 to n-->>MCData server: 11. MCData data disposition notification + Note right of MCData server: 12. Aggregate notifications + MCData server-->>MCData client 1: 13. MCData data disposition notification(s) + +``` + +Sequence diagram for Group standalone SDS using media plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. The sequence shows steps from initiating a data request to processing the payload and sending notifications. + +Figure 7.4.2.6.2-1: Group standalone SDS using media plane + +1. User at MCData client 1 would like to initiate a SDS data transfer request to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +2. MCData client 1 sends a MCData group session standalone data request towards the MCData server. The MCData group session standalone data request contains target recipient(s) as selected by the user at MCData client 1. The MCData session group standalone data request contains conversation identifier for message thread indication. The MCData session group standalone data request may contain disposition request if indicated by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the SDS data transfer. + +If the MCData user at MCData client 1 initiates an MCData emergency short data service communication or the MCData emergency state is already set for MCData client 1 (due to a previously triggered MCData emergency alert): + +- i) the MCData group session standalone data request shall contain an emergency indicator; + +- ii) the MCData group session standalone data request shall set the alert indicator if configured to send an MCData emergency alert while initiating an MCData standalone data request for the emergency short data service communication; +- iii) if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCPTT emergency state is retained until explicitly cancelled; and +- iv) once an MCData emergency communication has been initiated, the MCData group is considered to be in an in-progress emergency state until cancelled. + +If the MCData user at MCData client 1 initiates an MCData imminent peril short data service communication: + +- i) the MCData group session standalone data request shall contain an imminent peril indicator; and + - ii) once an MCData imminent peril communication has been initiated, the MCData group is considered to be in an in-progress imminent peril state until cancelled; +- 2a. If either an emergency indicator or an imminent peril indicator is present in received MCData group session standalone data request, the MCData server implicitly affiliates MCData client 1 to the MCData group if the client is not already affiliated. + 3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData session group standalone data request. The MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. MCData server also verifies whether the provided functional alias, if present, can be used and has been activated for the user. + - i) if an emergency indicator is present in the received MCData group session standalone data request and if the MCData group is not in the in-progress emergency state, the MCData group is considered to be in the in-progress emergency state until cancelled; + - ii) if an imminent peril indicator is present in the received MCData group session standalone data request and if the MCData group is not in the in-progress imminent peril state, the MCData group is considered to be in the in-progress imminent peril state until cancelled; + - 3a. The MCData server configures the priority of the underlying bearers for all participants in the MCData group. + 4. MCData server initiates the MCData group session standalone data request towards each MCData user determined in Step 3. The MCData group session standalone data request towards each MCData client contains: + - i) an emergency indicator if it is present in the received MCData group session standalone data request from the MCData client 1; + - ii) an imminent peril indicator if it is present in the received MCData group session standalone data request from the MCData client 1; and + - iii) an alert indicator if requested to initiate an emergency alert in the received MCData group session standalone data request from MCData client 1; + 5. The receiving MCData clients 2 to n automatically accepts the MCData group session standalone data request and responds with MCData group standalone data response towards MCData server. + 6. MCData server forwards the MCData clients 2 to n accepted response to the MCData user initiating the MCData group session standalone data request. + +NOTE 1: Step 6 can occur at any time following step 4, and prior to step 7 depending on the conditions to proceed with the data transmission. + +7. MCData client 1 and MCData server have successfully established media plane for data communication and the MCData client 1 transmits the SDS data. +8. MCData server distributes the data received from MCData client 1 to MCData clients 2 to n over the established media plane. After completion of the MCData transfer from MCData client 1, media plane resources associated to the data communication are released. + +NOTE 2: MCData server is not required to wait for the complete reception of SDS data from MCData client 1 prior to initiating transmission to MCData client 2 to n. + +9. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 to n may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData client 2 to n shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. +10. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client(s) initiates a MCData data disposition notification for delivery report. +11. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. +12. The MCData data disposition notification(s) from MCData client may be stored by the MCData server for disposition history interrogation from authorized MCData users. The MCData data disposition notification(s) from each MCData user may be aggregated. +13. Aggregated or individual MCData data disposition notification(s) is sent to the disposition requesting user at MCData client 1. + +#### 7.4.2.7 Group short data service session + +##### 7.4.2.7.1 General + +The initiation of a group SDS to a selected group results in affiliated group members exchanging SDS data. + +##### 7.4.2.7.2 Procedure + +The procedure in figure 7.4.2.7.2-1 describes the case where an MCData user is initiating SDS data communication session with an MCData group for exchanging SDS data transactions between the group participants, with or without disposition request, using MCData-SDS-1 and MCData-SDS-2 reference points. + +Pre-conditions: + +1. MCData users on MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. +2. Optionally, the MCData client may have activated functional alias to be used. +3. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for Group SDS session showing interactions between MCData client 1, MCData server, Group management server, and MCData client 2 to n.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData group data request + Note right of MCData server: 2a. Affiliate user to group + Note right of MCData server: 3. Resolve group id + Note right of MCData server: 3a. Bearer priority configuration + MCData server->>MCData client 2 to n: 4. MCData group data request + Note right of MCData client 2 to n: 5. Notify request + MCData client 2 to n->>MCData server: 6. MCData group data response + MCData server->>MCData client 1: 7. MCData group data response + Note right of MCData server: 8. Data transmission + Note right of MCData server: 9. Disposition notifications + Note right of MCData server: 10. Session data termination + +``` + +Sequence diagram for Group SDS session showing interactions between MCData client 1, MCData server, Group management server, and MCData client 2 to n. + +**Figure 7.4.2.7.2-1: Group SDS session** + +1. User at MCData client 1 would like to initiate a SDS group data transfer request to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +2. MCData client 1 sends a MCData group data request towards the MCData server. The MCData group data request contains MCData group ID as selected by the user at MCData client 1. The MCData session data request contains conversation identifier for message thread indication. MCData user at MCData client 1 may include a functional alias within the SDS data transfer. + +If the MCData user at MCData client 1 initiates an MCData emergency short data service communication or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert): + +- i) the MCData group data request shall contain an emergency indicator; +- ii) the MCData group data request shall set an alert indicator if configured to send an MCData emergency alert while initiating an MCData standalone data request for the emergency short data service communication; +- iii) if MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCPTT emergency state is retained until explicitly cancelled; and +- iv) once an MCData emergency communication has been initiated, the MCData group is considered to be in an in-progress emergency state until cancelled. + +If the MCData user at MCData client 1 initiates an MCData imminent peril short data service communication: + +- i) the MCData group data request shall contain an imminent peril indicator; and +- ii) once an MCData imminent peril communication has been initiated, the MCData group is considered to be in an in-progress imminent peril state until cancelled; + +- 2a. If either emergency indicator or imminent peril indicator is present in received MCData group data request, the MCData server implicitly affiliates MCData client 1 to the MCData group if the client is not already affiliated. + 3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData group data request. The MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. The MCData server also checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. MCData server also verifies whether the provided functional alias, if present, can be used and has been activated for the user. + - i) if an emergency indicator is present in the received MCData group data request and if MCData group is not in in-progress emergency state, the MCData group is considered to be in the in-progress emergency state until cancelled; + - ii) if an imminent peril indicator is present in the received MCData group data request and if the MCData group is not in the in-progress imminent peril, the MCData group is considered to be in the in-progress imminent peril state until cancelled; + - 3a. The MCData server configures the priority of the underlying bearers for all participants in the MCData group. + 4. MCData server initiates the MCData group data request towards each MCData user determined in Step 3. The MCData group data request towards each MCData client contains: + - i) an emergency indicator if it is present in the received MCData group data request from the MCData client 1; + - ii) an imminent peril indicator if it is present in the received MCData group data request from the MCData client 1; and + - iii) an alert indicator if requested to initiate an emergency alert in the received MCData group data request from MCData client 1; + 5. The receiving MCData clients 2 to n optionally notify the user about the incoming MCData session data request. + 6. The receiving MCData client 2 to n accept or reject the MCData group data request and the corresponding result is in the MCData group data response towards MCData server. + 7. MCData server forwards the MCData client 2 accepted response to the MCData user initiating the MCData session data request. +- NOTE: Step 7 can occur at any time following step 4, and prior to step 8 depending on the conditions to proceed with the data transmission. +8. MCData client 1 and the MCData group data request accepted clients have successfully established media plane for data communication and either MCData client can transmit SDS data. The MCData data request may contain disposition request if indicated by the client sending data. If the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the SDS data receiving MCData users may be notified, otherwise those MCData users shall not be notified. + 9. If MCData data disposition was requested by the user, then the SDS data receiving MCData client initiates a MCData data disposition notification for delivery, read reports to the disposition requesting user. The MCData data disposition notification from MCData user may be stored by the MCData server for disposition history interrogation from authorized users. + 10. Based on the MCData user action or conditions to release, the established media plane for SDS data exchange is released. + +#### 7.4.2.8 One-to-one SDS communication upgrade to an emergency one-to-one SDS communication + +##### 7.4.2.8.1 General + +This clause is for adding procedures related to upgrading an existing MCData one-to-one SDS communication to an MCData emergency one-to-one SDS communication. + +### 7.4.2.8.2 Procedure + +The procedure in figure 7.4.2.8.2-1 describes the case where an authorized MCData user is upgrading an ongoing MCData one-to-one SDS communication to an MCData emergency one-to-one SDS communication. This procedure is applicable only when MCData one-to-one SDS communication is established as described in subclause 7.4.2.3 "One-to-one standalone short data service using media plane" or as described in subclause 7.4.2.4 "One-to-one short data service session". + +Pre-conditions: + +1. Both members of the MCData one-to-one SDS communication belong to the same MCData system. +2. MCData one-to-one SDS communication is already in progress. + +![Sequence diagram showing the procedure to upgrade an MCData one-to-one SDS communication to an MCData emergency one-to-one SDS communication. The diagram involves three main entities: MCData client 1, MCData server, and MCData client 2, all under the Home MCData service provider. The process starts with a box 'MCData one-to-one SDS session is in progress'. Step 1: MCData client 1 initiates emergency communication. Step 2: MCData client 1 sends an upgrade request to the server. Step 3: The server sends an upgrade request to MCData client 2. Step 4: MCData client 2 notifies the user of the emergency. Step 5: MCData client 2 sends an upgrade response to the server. Step 6: The server performs bearer priority adjustment. Step 7: The server sends an upgrade response to MCData client 1. Step 8: A final box indicates 'Media plane and floor control over upgraded bearer'.](3e20f0289a1945c7c3894f51383d8e37_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note right of MCData client 1: MCData one-to-one SDS session is in progress + Note left of MCData client 1: 1. initiate emergency communication + MCData client 1->>MCData server: 2. MCData one-to-one SDS communication upgrade request + MCData server->>MCData client 2: 3. MCData one-to-one SDS communication upgrade request + Note right of MCData client 2: 4. Notify emergency communication + MCData client 2->>MCData server: 5. MCData one-to-one SDS communication upgrade response + Note left of MCData server: 6. Bearer priority adjustment + MCData server->>MCData client 1: 7. MCData one-to-one SDS communication upgrade response + Note right of MCData client 1: 8. Media plane and floor control over upgraded bearer + +``` + +Sequence diagram showing the procedure to upgrade an MCData one-to-one SDS communication to an MCData emergency one-to-one SDS communication. The diagram involves three main entities: MCData client 1, MCData server, and MCData client 2, all under the Home MCData service provider. The process starts with a box 'MCData one-to-one SDS session is in progress'. Step 1: MCData client 1 initiates emergency communication. Step 2: MCData client 1 sends an upgrade request to the server. Step 3: The server sends an upgrade request to MCData client 2. Step 4: MCData client 2 notifies the user of the emergency. Step 5: MCData client 2 sends an upgrade response to the server. Step 6: The server performs bearer priority adjustment. Step 7: The server sends an upgrade response to MCData client 1. Step 8: A final box indicates 'Media plane and floor control over upgraded bearer'. + +**Figure 7.4.2.8.2-1 MCData one-to-one SDS communication upgraded to MCData emergency one-to-one SDS communication** + +1. The MCData user at MCData client 1 initiates an emergency. MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled. +2. MCData client 1 requests the MCData server to upgrade the one-to-one MCData SDS communication to in-progress emergency by sending a MCData one-to-one SDS communication upgrade request. +3. The MCData server sends the MCData one-to-one SDS communication upgrade request towards the MCData client of the other participant. +4. The MCData user is notified of the in-progress emergency of the MCData emergency one-to-one SDS communication. +5. The receiving MCData client acknowledges the MCData one-to-one SDS communication upgrade request and sends MCData one-to-one SDS communication upgrade response to the MCData server. + +6. The MCData server adjusts the priority of the underlying bearer for both participants of the MCData one-to-one SDS communication. The priority is retained until the communication session ends. +7. The MCData server sends MCData one-to-one SDS communication upgrade response to MCData client 1. +8. MCData client 1 and MCData client 2 continue with the MCData one-to-one SDS communication, which has been transformed into an MCData emergency one-to-one SDS communication. + +#### 7.4.2.9 Group SDS communication upgrade to an group emergency SDS communication + +##### 7.4.2.9.1 General + +This clause is for adding procedures related to upgrading an existing MCData group SDS communication to an MCData emergency group SDS communication. + +##### 7.4.2.9.2 Procedure + +The procedure in figure 7.4.2.9.2-1 describes the case where an authorized MCData user is upgrading an ongoing MCData group SDS communication to an MCData emergency group SDS communication. This procedure is applicable only when group MCData communication is established as described in subclause 7.4.2.6 "Group standalone short data service using media plane" or as described in subclause 7.4.2.7 "Group short data service session". + +NOTE 1: For simplicity, a single MCData server is shown in place of a user home MCData server and a group hosting MCData server. + +Pre-conditions: + +1. The MCData group is previously defined on the group management server with MCData client 1, MCData client 2 and MCData client 3 are affiliated to that MCData group. +2. All members of the MCData group belong to the same MCData system. +3. MCData group SDS communication is already in progress. +4. The initiating MCData client 1 has been configured to send an MCData emergency alert when upgrading an MCData emergency group communication. + +![Sequence diagram showing the upgrade of MCData group SDS communication to an emergency state. Lifelines: MCData client 1, MCData server, MCData client 2, and MCData client 3. The process involves initiating an emergency, sending upgrade requests, adjusting bearer priority, notifying clients, and receiving responses.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` + +sequenceDiagram + participant MC1 as MCData client 1 + participant MS as MCData server + participant MC2 as MCData client 2 + participant MC3 as MCData client 3 + + Note over MC1, MC3: MCData group SDS communication is in progress + + MC1->>MS: 1. Initiate group emergency + Note right of MC1: 1. Initiate group emergency + MC1->>MS: 2. MCData group SDS communication upgrade request + Note right of MS: 3. Bearer priority adjustment + MS->>MC2: 4. MCData group SDS communication upgrade request + MS->>MC3: 4. MCData group SDS communication upgrade request + Note right of MC2: 5. Notify group emergency status + Note right of MC3: 5. Notify group emergency status + MC2->>MS: 6. MCData group SDS communication upgrade response + MC3->>MS: 6. MCData group SDS communication upgrade response + MS->>MC1: 7. MCData group SDS communication upgrade response + Note over MC1, MC3: MCData group SDS communication over upgraded bearer + +``` + +Sequence diagram showing the upgrade of MCData group SDS communication to an emergency state. Lifelines: MCData client 1, MCData server, MCData client 2, and MCData client 3. The process involves initiating an emergency, sending upgrade requests, adjusting bearer priority, notifying clients, and receiving responses. + +**Figure 7.4.2.9.2-1: MCData group SDS communication upgraded to MCData emergency group SDS communication** + +1. The MCData user at MCData client 1 initiates a group emergency. MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled. +2. MCData client 1 requests the MCData server to upgrade the MCData group to an in-progress emergency state by sending a MCData group SDS communication upgrade request. The MCData client 1 sets emergency indicator in the request. If configured to send an MCData alert when initiating an MCData emergency group SDS upgrade, the request also contains an indication that an MCData alert is to be initiated. +3. The MCData server adjusts the priority of the underlying bearer for all or selected participants in the MCData group SDS communication that receive the communication over unicast. + +NOTE 2: The determination of the selected participants whose bearers have to be upgraded is left to implementation. + +4. MCData server sends the MCData group SDS communication upgrade request towards the MCData clients of each of those affiliated MCData group members. The request contains an indication of an MCData emergency alert if the request from the originator indicated MCData emergency alert. +5. MCData users are notified of the in-progress emergency state of the MCData group. +6. The receiving MCData clients send the MCData group SDS communication upgrade response to the MCData server to acknowledge the MCData group emergency request. For a multicast call, these acknowledgements are not sent. +7. The MCData server sends the MCData group SDS communication upgrade response to the MCData user 1 to confirm the upgrade request. + +NOTE 3: Step 7 can occur at any time following step 3, and prior to step 8 depending on the conditions to proceed with the call. + +MCDData client 1, MCDData client 2 and MCDData client 3 continue with the MCDData group SDS communication, which has been transformed into an MCDData emergency group SDS communication. + +#### 7.4.2.10 Group SDS communication in-progress emergency group state cancel + +##### 7.4.2.10.1 General + +This clause is for adding procedures related to MCDData in-progress emergency group state cancel. + +##### 7.4.2.10.2 Procedure + +The procedure in figure 7.4.2.10.2-1 describes the case where an authorized MCDData user cancels MCDData group's in-progress emergency. + +Pre-conditions: + +1. The MCDData group is previously defined on the group management server with MCDData client 1, MCDData client 2 and MCDData client 3 affiliated to that MCDData group. +2. All members of the MCDData group belong to the same MCDData system. +3. MCDData group members have been notified about the in-progress emergency. +4. The MCDData group is in the in-progress emergency state and has prioritized bearer support. +5. MCDData client 1 previously initiated the in-progress emergency for the group. + +![Sequence diagram titled 'Home MCData service provider' showing the interaction for 'MCData group SDS in-progress emergency group state cancel'. Lifelines: MCData client 1, MCData server, MCData client 2, and MCData client 3. The process involves an initiate request from client 1, a priority state cancel request to the server, a bearer priority adjustment, a request from the server to clients 2 and 3, a notify emergency cancel to clients 2 and 3, and finally responses from clients 2 and 3 back to the server, which then sends a response back to client 1.](5e9af8986a5845504f251d3079da8078_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client 3 + + Note over MCData client 1: 1. Initiate in-progress emergency group state cancel + MCData client 1->>MCData server: 2. MCData group SDS in-progress priority state cancel request + Note over MCData server: 3. Bearer priority adjustment + MCData server->>MCData client 2: 4. MCData group SDS in-progress priority state cancel request + MCData server->>MCData client 3: 4. MCData group SDS in-progress priority state cancel request + Note over MCData client 2: 5. Notify emergency cancel + Note over MCData client 3: 5. Notify emergency cancel + MCData client 2->>MCData server: 6. MCData group SDS in-progress priority state cancel response + MCData client 3->>MCData server: 6. MCData group SDS in-progress priority state cancel response + MCData server->>MCData client 1: 7. MCData group SDS in-progress priority state cancel response + +``` + +Sequence diagram titled 'Home MCData service provider' showing the interaction for 'MCData group SDS in-progress emergency group state cancel'. Lifelines: MCData client 1, MCData server, MCData client 2, and MCData client 3. The process involves an initiate request from client 1, a priority state cancel request to the server, a bearer priority adjustment, a request from the server to clients 2 and 3, a notify emergency cancel to clients 2 and 3, and finally responses from clients 2 and 3 back to the server, which then sends a response back to client 1. + +**Figure 7.4.2.10.2-1: MCData group SDS in-progress emergency group state cancel** + +1. The user at the MCData client 1 initiates an MCData group SDS in-progress emergency group state cancel. + +NOTE 1: An MCData user authorized to cancel in-progress emergencies on the MCData group can also be authorised to cancel the MCData emergency alert in addition to the initiator. However, only the initiator can cancel the initiator's local MCData emergency state. + +2. The MCData client 1 sends an MCData group SDS communication in-progress priority state cancel request to the MCData server. The MCData client 1 also resets emergency indicator in the request to inform MCData server about cancellation of in-progress emergency group state. + +NOTE 2: When MCData emergency alerts are in effect together with an MCData in-progress emergency group state on the same MCData group, the MCData emergency alert can, under some circumstances be cancelled at the same time. In that case, the MCData group SDS in-progress priority group state cancel request carries an indication that the alert is also being cancelled. + +3. The MCData server adjusts the priority of the underlying bearer; priority treatment is no longer required. The MCData server cancels/resets the emergency in-progress state of the MCData group. +4. The MCData server sends an MCData group SDS in-progress priority state cancel request to the MCData group members. +5. MCData group members are notified of the MCData group SDS in-progress emergency state cancel. +6. The receiving MCData clients send the MCData group SDS in-progress priority state cancel response to the MCData server to acknowledge the MCData in-progress emergency group state cancel. For a multicast call scenario, these acknowledgements are not sent. + +7. The MCData server sends the MCData group SDS in-progress priority state cancel response to the MCData user 1 to confirm the MCData in-progress emergency group state cancel. If the MCData in-progress emergency group state cancel request (in step 2) contained the "Alert indicator" IE, the MCData client 1 resets its local emergency status. + +NOTE 3: Step 7 can occur at any time following step 3, depending on the conditions to proceed with the call. + +#### 7.4.2.11 Group SDS communication upgrade to an imminent peril group SDS communication + +##### 7.4.2.11.1 General + +This clause is for adding procedures related to upgrade to an imminent peril group SDS communication. + +##### 7.4.2.11.2 Procedure + +This procedure is applicable only when group MCData SDS communication is established as described in subclause 7.4.2.6 "Group standalone short data service using media plane" or as described in subclause 7.4.2.7 "Group short data service session". The MCData service shall support the procedures and related information flows as specified in subclause 7.4.2.9 "Group SDS communication upgrade to an group SDS emergency communication" with the following clarifications: + +- In step 2), The MCData client 1 set imminent peril indicator; and +- In step 5), MCData users are notified of the in-progress imminent peril state of the MCData group. + +#### 7.4.2.12 Group SDS communication in-progress imminent peril group state cancel + +##### 7.4.2.12.1 General + +This clause is for adding procedures related to group SDS communication in-progress imminent peril group state cancel. + +##### 7.4.2.12.2 Procedure + +The MCData service shall support the procedures and related information flows as specified in subclause 7.4.2.10 "Group SDS communication in-progress emergency group state cancel" with the following clarifications: + +- In step 2), The MCData client 1 set imminent peril indicator; and +- In step 6), MCData users are notified of the group SDS communication in-progress imminent peril state cancel. + +### 7.4.3 Short data service for off-network + +#### 7.4.3.1 General + +#### 7.4.3.2 Information flows for short data service + +##### 7.4.3.2.1 MCData standalone data request + +Table 7.4.3.2.1-1 describes the information flow for the MCData standalone data request sent from the MCData client to another MCData client. + +**Table 7.4.3.2.1-1: MCData standalone data request** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Date and Time | M | Date and time of transmission | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Emergency indicator (see NOTE 1) | O | Indicates that the MCData communication is an MCData emergency communication | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier (see NOTE 2) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE 1: This information element shall be included for the MCData emergency communication. | | | +| NOTE 2: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | | + +#### 7.4.3.2.2 MCData data disposition notification + +Table 7.4.3.2.2-1 describes the information flow for the MCData data disposition notification sent from the MCData client to another MCData client. + +**Table 7.4.3.2.2-1: MCData data disposition notification** + +| Information element | Status | Description | +|--------------------------|--------|---------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| MCData ID | M | The identity of the MCData user sending notification | +| Conversation Identifier | M | Identifies the conversation | +| Reply Identifier | M | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition | M | Disposition which is delivered or read or both | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | + +#### 7.4.3.2.3 MCData group standalone data request + +Table 7.4.3.2.3-1 describes the information flow for the MCData group standalone data request sent from the MCData client to another MCData client. + +**Table 7.4.3.2.3-1: MCData group standalone data request** + +| Information element | Status | Description | +|---------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Date and Time | M | Date and time of transmission | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Emergency indicator (see NOTE 1) | O | Indicates that the MCData communication is an MCData emergency communication | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the MCData communication is an MCData imminent peril communication | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier (see NOTE 2) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | + +NOTE 1: If used, only one of these information elements shall be present. +NOTE 2: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. + +### 7.4.3.3 One-to-one standalone short data service using signalling control plane + +#### 7.4.3.3.1 General + +This subclause describes the detailed procedures for the scenario where SDS data is to be sent to MCData user in off-network. + +#### 7.4.3.3.2 Procedure + +Figure 7.4.3.3.2-1 describes procedures for an off-network MCData client 1 initiating one-to-one MCData data communication for sending standalone SDS data to other MCData client, with or without disposition request. Standalone refers to sending unidirectional data in one transaction. The SDS data size is assumed to be pre-configured. + +Pre-conditions: + +1. MCData user 1 has initiated communication for sending standalone SDS data to other MCData user 2. +2. MCData client 1 and MCData client 2 are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable. +3. MCData client 1 has discovered MCData client 2 in proximity, associated with MCData user B, using ProSe Discovery procedures. + +![Sequence diagram illustrating the one-to-one standalone short data service using signalling control plane. The diagram shows two lifelines: MCData client 1 and MCData client 2. The sequence of messages is: 1. Check authorization (internal to MCData client 1), 2. MCData standalone data request (from MCData client 1 to MCData client 2), 3. Assert policy (internal to MCData client 2), 4. Process payload (internal to MCData client 2), 5. MCData data disposition notification (dashed arrow from MCData client 2 to MCData client 1), and 6. MCData data disposition notification (dashed arrow from MCData client 2 to MCData client 1).](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + Note left of MCData client 1: 1. Check authorization + MCData client 1->>MCData client 2: 2. MCData standalone data request + Note right of MCData client 2: 3. Assert policy + Note right of MCData client 2: 4. Process payload + MCData client 2-->>MCData client 1: 5. MCData data disposition notification + MCData client 2-->>MCData client 1: 6. MCData data disposition notification + +``` + +Sequence diagram illustrating the one-to-one standalone short data service using signalling control plane. The diagram shows two lifelines: MCData client 1 and MCData client 2. The sequence of messages is: 1. Check authorization (internal to MCData client 1), 2. MCData standalone data request (from MCData client 1 to MCData client 2), 3. Assert policy (internal to MCData client 2), 4. Process payload (internal to MCData client 2), 5. MCData data disposition notification (dashed arrow from MCData client 2 to MCData client 1), and 6. MCData data disposition notification (dashed arrow from MCData client 2 to MCData client 1). + +**Figure 7.4.3.3.2-1: One-to-one standalone short data service using signalling control plane** + +1. MCData client 1 checks whether the MCData user 1 is authorized to send MCData standalone data request. +2. If MCData user 1 is authorised MCData client 1 sends a MCData standalone data request towards the MCData client 2. The MCData standalone data request contains conversation identifier for message thread indication. The MCData standalone data request may contain disposition request if indicated by the user at MCData client 1. If MCData user at the MCData client 1 initiates an MCData emergency communication, then emergency indicator is included in the MCData standalone data request. If an MCData emergency state is not set already when MCData emergency communication is initiated, the MCData client 1 sets its MCData emergency state and is retained until explicitly cancelled. The value of ProSe Per Packet Priority is upgraded according to the state of the MCData communication. +3. On receiving a MCData standalone data request, the MCData client 2 checks whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. +4. If the policy assertion is positive and the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user of MCData client 2 may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user of MCData client 2 shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. + +NOTE: If the policy assertion was negative, the MCData client 2 sends an appropriate notification to MCData client 1. + +5. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData client 2 initiates a MCData data disposition notification for delivery report. +6. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. + +#### 7.4.3.4 Group standalone short data service using signalling control plane + +##### 7.4.3.4.1 General + +The initiation of a group standalone SDS to a selected group results in off-network MCData group members receiving the SDS data. + +##### 7.4.3.4.2 Procedure + +Figure 7.4.3.4.2-1 describes procedures for an off-network MCData client 1 initiating group MCData data communication for sending SDS data to a MCData group, with or without disposition request. The SDS data size limit is pre-configured. + +Pre-conditions: + +1. MCData user 1 has initiated group communication for sending SDS data to the MCData group. +2. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCData client 1. +3. MCData client 1 to MCData client N are members of the same MCData group. + +![Sequence diagram illustrating the Group standalone short data service using signalling control plane. The diagram shows interactions between MCData client 1, MCData client 2, and MCData client N. Step 1: MCData client 1 checks authorization. Step 2: MCData client 1 sends a MCData group standalone data request to MCData client 2. Step 3: MCData client 2 asserts policy. Step 4: MCData client 2 processes payload. Step 5: MCData client 2 sends a MCData data disposition notification to MCData client 1. Step 6: MCData client 2 sends another MCData data disposition notification to MCData client 1. The same steps 3-6 are shown for MCData client N.](57939c16065211317c5442cf2a4009e0_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + participant MCData client N + Note left of MCData client 1: 1. Check authorization + MCData client 1->>MCData client 2: 2. MCData group standalone data request + Note right of MCData client 2: 3. Assert policy + Note right of MCData client 2: 4. Process payload + MCData client 2-->>MCData client 1: 5. MCData data disposition notification + MCData client 2-->>MCData client 1: 6. MCData data disposition notification + Note right of MCData client N: 3. Assert policy + Note right of MCData client N: 4. Process payload + MCData client N-->>MCData client 1: 5. MCData data disposition notification + MCData client N-->>MCData client 1: 6. MCData data disposition notification + +``` + +Sequence diagram illustrating the Group standalone short data service using signalling control plane. The diagram shows interactions between MCData client 1, MCData client 2, and MCData client N. Step 1: MCData client 1 checks authorization. Step 2: MCData client 1 sends a MCData group standalone data request to MCData client 2. Step 3: MCData client 2 asserts policy. Step 4: MCData client 2 processes payload. Step 5: MCData client 2 sends a MCData data disposition notification to MCData client 1. Step 6: MCData client 2 sends another MCData data disposition notification to MCData client 1. The same steps 3-6 are shown for MCData client N. + +**Figure 7.4.3.4.2-1: Group standalone short data service using signalling control plane** + +1. MCData client 1 checks whether the MCData user 1 is authorized to send MCData group standalone data request. +2. If MCData user 1 is authorised MCData client 1 sends a MCData group standalone data request towards the MCData group. The MCData group standalone data request contains conversation identifier for message thread indication. The MCData group standalone data request may contain disposition request if indicated by the user at MCData client 1. If MCData group standalone data request contains disposition request, MCData group standalone data request shall also contain the IP address of the MCData client 1. If MCData user at the MCData client 1 initiates an MCData emergency communication, then the emergency indicator or the imminent peril indicator is included in the MCData standalone data request. If an MCData emergency state is not set already when MCData emergency communication is initiated, the MCData client 1 sets its MCData emergency state and is retained until explicitly cancelled. The value of ProSe Per Packet Priority is upgraded according to the state of the MCData communication. +3. On receiving a MCData group standalone data request, the MCData clients check whether any policy is to be asserted to limit certain types of message or content to certain members due, for example, to location or user privilege. +4. If the policy assertion is positive and the payload is for MCData user consumption (e.g. is not application data, is not command instructions, etc.) then the MCData user may be notified. Otherwise if the payload is not for MCData user consumption, then the MCData user shall not be notified. The action taken when the payload contains application data or command instructions are specific based on the contents of the payload. Payload content received by MCData client 2 which is addressed to a known local non-MCData application that is not yet running shall cause the MCData client 2 to start the local non-MCData application (i.e., remote start application) and shall pass the payload content to the just started application. + +NOTE: If the policy assertion was negative, the MCData client sends an appropriate notification to MCData client 1. + +5. If the MCData data disposition for delivery was requested by the user at MCData client 1, then the receiving MCData clients initiate a MCData data disposition notification for delivery report. +6. If the MCData data disposition for read was requested by the user at MCData client 1, then once the receiving user reads the data, the receiving MCData client 2 initiates a MCData data disposition notification for read report. + +### 7.4.3.5 Providing data for a user entering an ongoing MCData group conversation + +#### 7.4.3.5.1 General + +The MCData service shall support mechanisms that allow a MCData user be presented with the whole content of a group conversation in a group that he is a member of. This includes the content (messages) exchanged before the MCData user joins the group conversation. + +#### 7.4.3.5.2 Procedure + +Figure 7.4.3.5.2-1 describes procedures for a MCData user joins late to a group conversation. + +Pre-conditions: + +1. The MCData group is provisioned for lossless communication. +2. All members of the MCData group have an account created in the MCData message store. +3. MCData client 1, MCData client 2 and MCData client 3 are members of the same MCData group, +4. MCData client 1 and 2 are served by MCData server 1 and have registered and affiliated to the MCData group. +5. MCData client 3 is served by MCData server 2 and has not affiliated to the MCData group yet. + +NOTE 1: The interactions of MCData client 1 and MCData client 2 to MCData message store are not shown in the figure. + +![Sequence diagram illustrating the procedure for a MCData user (Client 3) joining an ongoing MCData group conversation. The diagram shows interactions between MCData Client 1, MCData Server 1, MCData Client 2, MCData server 2, MCData message store, and MCData Client 3. The steps are: 1. Initiate a data group conversation (between Client 1 and Server 2); 2. The media plane is established (between Client 1 and Server 2); 3. Deposit objects (between Server 2 and Message store); 4. Affiliate to the group (between Server 2 and Client 3); 5. Synchronization (between Message store and Client 3); 6. Invite to the group conversation (between Server 2 and Client 3); 7. Group conversations (ongoing state for all participants).](5f0781dd750d507531d474aed1ff9df9_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCData Client 1 + participant S1 as MCData Server 1 + participant C2 as MCData Client 2 + participant S2 as MCData server 2 + participant MS as MCData message store + participant C3 as MCData Client 3 + + Note over C1, S2: 1. Initiate a data group conversation + Note over C1, S2: 2. The media plane is established + Note over S2, MS: 3. Deposit objects + Note over S2, C3: 4. Affiliate to the group + Note over MS, C3: 5. Synchronization + Note over S2, C3: 6. Invite to the group conversation + Note over all: 7. Group conversations + +``` + +Sequence diagram illustrating the procedure for a MCData user (Client 3) joining an ongoing MCData group conversation. The diagram shows interactions between MCData Client 1, MCData Server 1, MCData Client 2, MCData server 2, MCData message store, and MCData Client 3. The steps are: 1. Initiate a data group conversation (between Client 1 and Server 2); 2. The media plane is established (between Client 1 and Server 2); 3. Deposit objects (between Server 2 and Message store); 4. Affiliate to the group (between Server 2 and Client 3); 5. Synchronization (between Message store and Client 3); 6. Invite to the group conversation (between Server 2 and Client 3); 7. Group conversations (ongoing state for all participants). + +**Figure 7.4.3.5.2-1: Providing data for a user entering an ongoing MCData group conversation** + +1. A group conversation is initiated according to procedures in subclause 7.4.2.6, and all members of the group are invited into the communication whether affiliated or not. As MCData user 3 is not affiliated at this time, MCData server 2 accepts the invitation to the group conversation on behalf of MCData user 3. +2. The media plane is established for the group conversation. MCData server 2 is in the media plane to receive the conversation on behalf of MCData user 3. +3. MCData server 2 stores the received conversation to MCData user 3 account in the MCData message store. + +NOTE 2: If the received conversation requests delivery notification the MCData server 2 will send message delivered to the message sender. If the received conversation requests read notification the MCData client 3 will send message read to the message sender once it has presented the message to the user. + +4. MCData user 3 is online and using MCData client 3 to affiliate to the MCData group. +5. MCData client 3, through the message store client, synchronizes with the MCData user 3 account in the MCData message store. +6. MCData server 2 invites MCData client 3 to the MCData group conversation. +7. MCData user 3 joins the MCData group conversation. + +#### 7.4.3.6 Group standalone short data service with MCData message store + +##### 7.4.3.6.1 General + +A MCData user's off-network communication needs to be part of his communication history when the MCData user has an account in the MCData message store. + +##### 7.4.3.6.2 Procedure + +Figure 7.4.3.5.2-1 describes procedures of a MCData user, MCData user 2, that has an account in MCData message store and how his off-network SDS group communication is stored in his account in the MCData message store. All other MCData clients in the figure follow the procedures described in subclause 7.4.3.4. + +Pre-conditions: + +1. MCData user 1 to N are in an off-network group communication. +2. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured to MCData client 1 to N. +3. MCData client 1 to N are members of the same MCData group. +4. MCData user 2 has an account in the MCData message store. + +![Sequence diagram illustrating the Group standalone short data service with MCData message store. The diagram shows five steps: 1. Off-network SDS group communication among MCData clients 1, 2, and N. 2. Store object from MCData client 2 to Message store client 2. 3. Off-network SDS group communication ends. 4. MCData user 2 connects to network. 5. Upload objects to MCData message store from MCData user 2.](cdc21bbfcba380e98ece42e5b8da50bb_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + participant Message store client 2 + participant MCData client N + participant MCData message store + + Note over MCData client 1, MCData client N: 1. Off-network SDS group communication + Note over MCData client 2, Message store client 2: 2. Store object + Note over MCData client 1, MCData client N: 3. Off-network SDS group communication ends + Note over MCData user 2: 4. MCData user 2 connects to network + Note over MCData user 2, MCData message store: 5. Upload objects to MCData message store + +``` + +Sequence diagram illustrating the Group standalone short data service with MCData message store. The diagram shows five steps: 1. Off-network SDS group communication among MCData clients 1, 2, and N. 2. Store object from MCData client 2 to Message store client 2. 3. Off-network SDS group communication ends. 4. MCData user 2 connects to network. 5. Upload objects to MCData message store from MCData user 2. + +**Figure 7.4.3.6.2-1: Group standalone short data service with MCData message store** + +1. MCData client 1 to MCData client N are in an off-network group communication according to the procedures in subclause 7.4.3.4, SDS are exchanged among all MCData clients. +2. If the SDS is for MCData user consumption, the SDS is stored in the local message store on the MCData UE of MCData user 2. + +NOTE: A pre-configured folder for off-network communication objects can be provisioned both on the UE and the user account on the MCData message store to be used for synchronization. + +3. The off-network group communication comes to an end. +4. The MCData user 2 connects back to the network. +5. The MCData user 2 decides to keep the off-network communication in his account on the MCData message store. The message store client 2 uploads the off-network communication objects from the local message store to the MCData message store. + +## 7.5 File distribution + +### 7.5.1 General + +File distribution (mandatory and non-mandatory download) is enabled for both one-to-one and group. + +### 7.5.2 File distribution for on-network + +#### 7.5.2.1 Information flows for file distribution + +##### 7.5.2.1.1 MCData upload data request + +Table 7.5.2.1.1-1 describes the information flow for the MCData upload data request sent from the media storage client to the MCData content server. + +**Table 7.5.2.1.1-1: MCData upload data request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user uploading data | +| Content | M | Content to upload | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | + +##### 7.5.2.1.2 MCData upload data response + +Table 7.5.2.1.2-1 describes the information flow for the MCData upload data response sent from the MCData content server to the media storage client. + +**Table 7.5.2.1.2-1: MCData upload data response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to upload data | +| Upload confirmation | M | An indication whether the upload to the content storage is successful or not | +| Content reference | O | URL reference of the content stored (see NOTE). | +| NOTE: Content reference shall be present when the upload confirmation is successful. | | | + +##### 7.5.2.1.3 MCData download data request + +Table 7.5.2.1.3-1 describes the information flow for the MCData download data request sent from the MCData media storage client to the MCData content server. + +**Table 7.5.2.1.3-1: MCData download data request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user downloading data | +| Content reference | M | URL reference to the content to download | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | + +Editor's note: it is FFS how the media storage client requests a file repair and indicates the missing data. + +#### 7.5.2.1.4 MCData download data response + +Table 7.5.2.1.4-1 describes the information flow for the MCData download data response sent from the MCData content server to the media storage client. + +**Table 7.5.2.1.4-1: MCData download data response** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to download data | +| Content (see NOTE) | O | Requested content to download | +| Result | M | Indicates success or failure of MCData download data request | +| NOTE: Content shall be present when the result of the MCData download data request indicates success. | | | + +Editor's note: it is FFS how the content server indicates a full file download versus a patch file to be used in a repair. + +#### 7.5.2.1.5 MCData FD request (using HTTP) + +Table 7.5.2.1.5-1 describes the information flow for the MCData FD request (in subclause 7.5.2.4.2) sent from the MCData client to the MCData server, from the MCData server to another MCData client and from an MCData server to a partner MCData server. + +**Table 7.5.2.1.5-1: MCData FD request (using HTTP)** + +| Information element | Status | Description | +|-------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending file | +| Functional alias | O | The functional alias associated with MCData user sending the file. | +| MCData ID | M | The identity of the MCData user receiving file | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed reported is expected or not | +| Download indication | O | Indicates mandatory download | +| Content reference | M | URL reference to the content and file metadata information | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | + +#### 7.5.2.1.6 MCData FD response (using HTTP) + +Table 7.5.2.1.6-1 describes the information flow for the MCData FD response (in subclause 7.5.2.4.2) sent from the MCData client to the MCData server, from the MCData server to another MCData client and from an MCData server to a partner MCData server. + +**Table 7.5.2.1.6-1: MCData FD response (using HTTP)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | + +#### 7.5.2.1.7 MCData download completed report + +Table 7.5.2.1.7-1 describes the information flow for the MCData download completed report sent from the MCData client to the MCData server, from the MCData server to another MCData client and from an MCData server to a partner MCData server. + +**Table 7.5.2.1.7-1: MCData download completed report** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | M | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition confirmation | M | An indication that the client has completed downloading file | + +#### 7.5.2.1.8 MCData FD request (using media plane) + +Table 7.5.2.1.8-1 describes the information flow for the MCData FD request (in subclause 7.5.2.5.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.8-1: MCData FD request (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending file | +| Functional alias | O | The functional alias associated with MCData user sending the file. | +| MCData ID | M | The identity of the MCData user receiving file | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed reported is expected or not | +| Download indication | O | Indicates mandatory download. (i.e. auto accept this media plane setup request) | +| SDP offer | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | +| Emergency indicator | O | Indicates that the data request is for MCData emergency communication | + +#### 7.5.2.1.9 MCData FD response (using media plane) + +Table 7.5.2.1.9-1 describes the information flow for the MCData FD response (in subclause 7.5.2.5.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.9-1: MCData FD response (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +#### 7.5.2.1.10 MCData group standalone FD request (using HTTP) + +Table 7.5.2.1.10-1 describes the information flow for the MCData group standalone FD request (in subclause 7.5.2.6.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.10-1: MCData group standalone FD request (using HTTP)** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending file | +| Functional alias | O | The functional alias associated with MCData user sending the file. | +| MCData group ID | M | The MCData group ID to which the file is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed reported is expected or not | +| Download indication | O | Indicates mandatory download | +| Content reference | M | URL reference to the content and file metadata information | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +#### 7.5.2.1.11 MCData group standalone FD response (using HTTP or MBMS download delivery method) + +Table 7.5.2.1.11-1 describes the information flow for the MCData group standalone FD response (in subclause 7.5.2.6.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.11-1: MCData group standalone FD response (using HTTP)** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData group ID | M | The MCData group ID to which the file is to be sent | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | + +#### 7.5.2.1.12 MCData group standalone FD request (using media plane) + +Table 7.5.2.1.12-1 describes the information flow for the MCData group standalone FD request (in subclause 7.5.2.7.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.12-1: MCData group standalone FD request (using media plane)** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending file | +| Functional alias | O | The functional alias associated with MCData user sending the file. | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed reported is expected or not | +| Download indication | O | Indicates mandatory download. (i.e. auto accept this media plane setup request) | +| SDP offer | M | Media parameters offered | +| Requested priority | O | Application priority level requested for this communication session | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +#### 7.5.2.1.13 MCData group standalone FD response (using media plane) + +Table 7.5.2.1.13-1 describes the information flow for the MCData group standalone FD response (in subclause 7.5.2.7.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.13-1: MCData group standalone FD response (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData group ID | M | The MCData group ID to which the file is to be sent | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | + +#### 7.5.2.1.14 MCData remove file request by user + +Table 7.5.2.1.14-1 describes the information flow for the MCData remove file request by user sent from the media storage client to the media storage function of the MCData content server, and from the MCData content server to another MCData content server in a partner MCData system. + +**Table 7.5.2.1.14-1: MCData remove file request by user** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------| +| MCData ID (see NOTE 1) | O | The identity of the MCData user removing file | +| Partner MCData system identity (see NOTE 2) | O | The identity of the partner MCData system where the file has also been downloaded | +| Content reference | M | URL of the content to be removed | +| NOTE 1: The identity of the MCData user removing the file is present when sent from MCData client to MCData content server | | | +| NOTE 2: The identity of the partner MCData system is present when sent from MCData content server to MCData content server. | | | + +#### 7.5.2.1.15 MCDData remove file response by user + +Table 7.5.2.1.15-1 describes the information flow for the MCDData remove file response by user sent from the media storage function of the MCDData content server to the media storage client, and from the MCDData content server to another MCDData content server in a partner MCDData system. + +**Table 7.5.2.1.15-1: MCDData remove file response by user** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------------------------| +| MCDData ID (see NOTE 1) | O | The identity of the MCDData user removing file | +| Partner MCDData system identity (see NOTE 2) | O | The identity of the partner MCDData system where the file has also been downloaded | +| Result | M | Indicates the success or failure of the file removal | +| NOTE 1: The identity of the MCDData user removing the file is present when sent from MCDData content server to MCDData client | | | +| NOTE 2: The identity of the partner MCDData system is present when sent from MCDData content server to MCDData content server. | | | + +#### 7.5.2.1.16 Void + +#### 7.5.2.1.17 Void + +#### 7.5.2.1.18 MCDData remove file notify + +Table 7.5.2.1.18-1 describes the information flow for the MCDData remove file notify sent from the MCDData server to the MCDData client that the shared file has been removed. + +**Table 7.5.2.1.18-1: MCDData remove file notify** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------| +| MCDData ID | M | The identity of the MCDData user uploaded the file | +| Content reference | M | URL of the content that has been removed | +| Reason | O | The reason the file is removed | + +#### 7.5.2.1.19 MCDData file retrieve request + +Table 7.5.2.1.19-1 describes the information flow for the MCDData file retrieve request sent from an MCDData content server in a partner MCDData system to an MCDData content server in the primary MCDData system of the source of the content. + +**Table 7.5.2.1.19-1: MCDData file retrieve request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------| +| Content reference | M | URL reference to the content to download | + +#### 7.5.2.1.20 MCDData file retrieve response + +Table 7.5.2.1.20-1 describes the information flow for the MCDData file retrieve response sent from the MCDData content server in the primary MCDData system of the source of the content to an MCDData content server in a partner MCDData system. + +**Table 7.5.2.1.20-1: MCDData file retrieve response** + +| Information element | Status | Description | +|--------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------| +| Content (see NOTE) | O | Requested content to download | +| Result | M | Indicates success or failure of MCDData download data request | +| NOTE: Content shall be present when the result of the MCDData file retrieve request indicates success. | | | + +### 7.5.2.1.21 MCDATA group standalone FD over MBMS request + +Table 7.5.2.1.21-1 describes the information flow for the MCDATA group standalone FD request (in subclause 7.5.2.6.2) sent from the MCDATA server to another MCDATA client. + +**Table 7.5.2.1.21-1: MCDATA group standalone FD over MBMS request** + +| Information element | Status | Description | +|-------------------------|--------|-------------------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user sending file | +| MCDATA group ID | M | The MCDATA group ID to which the file is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCDATA transaction | +| Reply Identifier | O | Identifies the original MCDATA transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed reported is expected or not | +| Download indication | M | Indicates mandatory download | +| Content reference | M | URL reference to the content and file metadata information | +| MBMS user service id | M | Id of the MBMS user service delivering the file | +| MBMS content URI | M | URI upon which the content is delivered in the MBMS user service | + +### 7.5.2.1.22 MCDATA one-to-one FD upgrade request + +Table 7.5.2.1.22-1 describes the information flow for the MCDATA one-to-one FD upgrade request sent from the MCDATA client to the MCDATA server and from the MCDATA server to another MCDATA client. + +**Table 7.5.2.1.22-1: MCDATA one-to-one FD upgrade request** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user sending data (when initiated by MCDATA client);
The identity of the MCDATA user receiving data (when initiated by MCDATA server). | +| Functional alias | O | The associated functional alias of the MCDATA user sending data or receiving data. | +| Conversation Identifier | M | Identifies the conversation | +| Emergency indicator | M | Indicates that the data request is for MCDATA emergency communication | + +### 7.5.2.1.23 MCDATA one-to-one FD upgrade response + +Table 7.5.2.1.23-1 describes the information flow for the MCDATA one-to-one FD upgrade response sent from the MCDATA client to the MCDATA server and from the MCDATA server to another MCDATA client. + +**Table 7.5.2.1.23-1: MCDATA one-to-one FD upgrade response** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user sending data (when initiated by MCDATA client);
The identity of the MCDATA user receiving data (when initiated by MCDATA server). | +| Conversation Identifier | M | Identifies the conversation | + +### 7.5.2.1.24 MCDATA group FD upgrade request + +Table 7.5.2.1.24-1 describes the information flow for the MCDATA group FD upgrade request sent from the MCDATA client to the MCDATA server and from the MCDATA server to another MCDATA client. + +**Table 7.5.2.1.24-1: MCData group FD upgrade request** + +| Information element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data (when initiated by MCData client);
The identity of the MCData user receiving data (when initiated by MCData server). | +| Functional alias | O | The associated functional alias of the MCData user sending data or receiving data. | +| MCData group ID | M | The MCData group ID on which the emergency upgrade request is made | +| Conversation Identifier | M | Identifies the conversation | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +#### 7.5.2.1.25 MCData group FD upgrade response + +Table 7.5.2.1.25-1 describes the information flow for the MCData group FD upgrade response sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.25-1: MCData group FD upgrade response** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data (when initiated by MCData client);
The identity of the MCData user receiving data (when initiated by MCData server). | +| MCData group ID | M | The MCData group ID on which the emergency upgrade request is made | +| Conversation Identifier | M | Identifies the conversation | + +#### 7.5.2.1.26 MCData group FD in-progress priority state cancel request + +Table 7.5.2.1.26-1 describes the information for the MCData group FD in-progress priority state cancel request sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.5.2.1.26-1: MCData group FD in-progress priority state cancel request information elements** + +| Information Element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the cancelling party | +| MCData group ID | M | The MCData group ID on which the MCData in-progress emergency state is to be cancelled. | +| Emergency indicator (see NOTE 1) | O | Indicates that the data request is for MCData emergency communication | +| Alert indicator (see NOTE 2) | O | Indicates whether an emergency alert is to be sent | +| Imminent peril indicator (see NOTE 1) | O | Indicates that the data request is for MCData imminent peril communication | +| Conversation Identifier | M | Identifies the conversation | +| NOTE 1: If used, only one of these information elements shall be present. | | | +| NOTE 2: This information element may be present only when Emergency indicator is present. | | | + +#### 7.5.2.1.27 MCData group FD in-progress priority state cancel response + +Table 7.5.2.1.27-1 describes the information flow for the MCData group FD in-progress priority state cancel response sent from the MCData server to the MCData client. + +**Table 7.5.2.1.27-1: MCData group FD in-progress priority state cancel response information elements** + +| Information Element | Status | Description | +|-------------------------|--------|-----------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the cancelling party | +| MCData group ID | M | The MCData group ID on which the MCData in-progress emergency in-progress is to be cancelled. | +| Conversation Identifier | M | Identifies the conversation | + +## 7.5.2.2 File upload using HTTP + +### 7.5.2.2.1 General + +The media storage client uses HTTP for a standalone data file upload towards the MCData content server. + +### 7.5.2.2.2 Procedure + +The procedure in figure 7.5.2.2.2-1 describes the case where an MCData user is uploading a file to media storage function on the MCData content server. + +Pre-conditions: + +1. The MCData user on the media storage client is registered for receiving MCData service. +2. The MCData content server has the ability to verify if the requesting MCData user is authorised to upload. + +![Sequence diagram for file upload using HTTP. The Media storage client sends a '1. initiate upload request' to the MCData content server. The MCData content server responds with '2. MCData upload data request' and '3. MCData upload data response'.](a0b72ad654428ce2b44766f24928643e_img.jpg) + +``` + +sequenceDiagram + participant Client as Media storage client + participant Server as MCData content server + Note left of Client: 1. initiate upload request + Client->>Server: 2. MCData upload data request + Server-->>Client: 3. MCData upload data response + +``` + +Sequence diagram for file upload using HTTP. The Media storage client sends a '1. initiate upload request' to the MCData content server. The MCData content server responds with '2. MCData upload data request' and '3. MCData upload data response'. + +**Figure 7.5.2.2.2-1: File upload using HTTP** + +1. The user at the media storage client initiates a file upload request of the chosen file. If MCData emergency state is already set for the media storage client (due to previously triggered MCData emergency alert), the media storage client sets emergency indicator in the request. The media storage client verifies that the size of the file is within the maximum data size for FD for the intended MCData FD request (by checking the group configuration for a group FD request and by checking the service configuration for a one-to-one FD request). +2. The file to be uploaded is received by the media storage client and sent to the media storage function on the MCData content server for storing using the MCData upload data request. +3. The MCData content server may apply transmission control policy before storage and provides a MCData upload data response indicating success (along with file URL to the media storage client) or failure. + +## 7.5.2.3 File download using HTTP + +### 7.5.2.3.1 General + +The media storage client uses HTTP for a standalone data file download from the MCData content server. + +### 7.5.2.3.2 Procedure + +The procedure in figure 7.5.2.3.2-1 describes the case where an MCData user is downloading a file from the media storage function of the MCData content server. + +Pre-conditions: + +1. The MCData user on the media storage client is registered for receiving MCData service. + +![Sequence diagram for Figure 7.5.2.3.2-1: File download using HTTP. The diagram shows two lifelines: 'Media storage client' and 'MCData content server'. The sequence of messages is: 1. initiate download request (from client to server), 2. MCData download data request (from client to server), and 3. MCData download data response (from server to client).](8f8caebe58364416a2eda21039d8c7bf_img.jpg) + +``` + +sequenceDiagram + participant Media storage client + participant MCData content server + Note left of Media storage client: 1. initiate download request + Media storage client->>MCData content server: 2. MCData download data request + MCData content server-->>Media storage client: 3. MCData download data response + +``` + +Sequence diagram for Figure 7.5.2.3.2-1: File download using HTTP. The diagram shows two lifelines: 'Media storage client' and 'MCData content server'. The sequence of messages is: 1. initiate download request (from client to server), 2. MCData download data request (from client to server), and 3. MCData download data response (from server to client). + +**Figure 7.5.2.3.2-1: File download using HTTP** + +1. The user at the media storage client initiates a file download request available at the indicated URL. + 2. The file available at the URL (received in MCData FD request or MCData group standalone FD request) is requested to be downloaded by the media storage client from the media storage function on the MCData content server using a MCData download data request. If emergency indicator is set in received in MCData FD request or MCData group standalone FD request, the media storage client sets emergency indicator in MCData download data request. +- NOTE: the Media storage client can perform partial download requests to complete the missing parts after an incomplete transmission. +3. The media storage function on the MCData content server may apply reception control policy and provides a MCData download data response including the file to the media storage client. + +## 7.5.2.4 One-to-one file distribution using HTTP + +### 7.5.2.4.1 General + +The MCData client uses HTTP file distribution to download a file that is uploaded by another MCData client. The procedure is appropriate for both mandatory and non-mandatory download cases. + +### 7.5.2.4.2 Procedure for single MCData system + +The procedure in figure 7.5.2.4.2-1 describes the case where a MCData user is initiating one-to-one data communication for sending file to the other MCData user, with or without download completed report request. + +Pre-conditions: + +1. The MCData users on the MCData client 1 and the MCData client 2 are already registered for receiving MCData service. +2. File to be distributed is uploaded to media storage function on MCData content server using the procedures defined in subclause 7.5.2.2. +3. Optionally, the MCData client may have activated functional alias to be used. +4. The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating one-to-one file distribution using HTTP between MCData client 1, MCData server, and MCData client 2.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData FD request + Note right of MCData server: 3. Authorize request + Note right of MCData server: 4. Transmission/ Reception control + MCData server->>MCData client 2: 5. MCData FD request + Note right of MCData client 2: 6. Notify request + MCData client 2->>MCData server: 7. MCData FD response + MCData server->>MCData client 1: 8. MCData FD response + Note right of MCData client 2: 9. Download file + MCData client 2->>MCData server: 10. MCData download completed report + MCData server->>MCData client 1: 11. MCData download completed report + +``` + +Sequence diagram illustrating one-to-one file distribution using HTTP between MCData client 1, MCData server, and MCData client 2. + +**Figure 7.5.2.4.2-1: One-to-one file distribution using HTTP** + +1. The user at the MCData client 1 initiates a file distribution request to the chosen MCData user. +2. The MCData client 1 sends a MCData FD request towards the MCData server. The MCData FD request contains content payload in the form of file URL and may contain the file metadata information. The MCData FD request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData FD request contains conversation identifier for message thread indication. If MCData user at MCData client 1 has requested to mandatory download at the recipient side, then MCData FD request contains mandatory download indication. The MCData FD request may contain download completed report indication if selected by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the FD data transfer. + - a) If the MCData user at the MCData client 1 initiates an MCData emergency file distribution using HTTP or MCData emergency state is already set for the MCData client 1 (due to previously triggered MCData emergency alert): + - i) The MCData FD request shall contain emergency indicator; and + - ii) If MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData FD request and that the size of the file is below maximum data size for FD from the service configuration. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the user. +4. The MCData server also applies transmission and reception control and the necessary policy control to ensure that appropriate data is transmitted between the MCData users. +5. MCData server initiates the MCData FD request towards the MCData user. The MCData FD request towards the MCData user contains an emergency indicator if it is present in the received MCData FD request from MCData client 1. +6. The receiving MCData client 2 notifies the user about the incoming MCData FD request (including file metadata, if present) which may be either accepted or rejected or ignored. +7. MCData user 2 may provide a response (accept or reject) or not (ignore) to the notification, then MCData client 2 sends the MCData FD response to the MCData server. MCData client 2 automatically sends accepted MCData FD response when the incoming request includes mandatory download indication. +8. The MCData server forwards the MCData FD response to the MCData client 1. + +9. Media storage client of MCData client 2 downloads the file using the procedures defined in subclause 7.5.2.3, either automatically (for mandatory download) or based upon the MCData user 2 subsequent action. The MCData client 2 records file download completed and notifies MCData user 2. +10. MCData client 2 initiates a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. +11. The MCData file download completed report from MCData user may be stored by the MCData server for download history interrogation from the authorized MCData users. MCData download completed report is sent by the MCData server to the MCData user at MCData client 1. + +#### 7.5.2.4.3 Procedure with interconnection between MCData systems + +The procedure in figure 7.5.2.4.3-1 describes the case where a MCData user initiates a one-to-one data communication for sending a file to another MCData user where that other MCData user is receiving MCData service on a partner MCData system, and where interconnection is in use between the two MCData systems. In this procedure, the file has not previously been downloaded in the partner MC system. + +Pre-conditions: + +1. The MCData users on the MCData client 1 and the MCData client 2 are already service authorized and receiving MCData service. MCData client 1 is receiving service on its primary MCData system, and MCData client 2 is receiving MCData service in the partner MCData system of MCData client 1. +2. The file to be distributed has been uploaded to the media storage function on the MCData content server in the primary MCData system of MCData client 1 using the procedures defined in subclause 7.5.2.2. +3. There is a service agreement between the primary and partner MCData systems to allow files to be shared between MCData content servers in the two systems. + +![Sequence diagram showing one-to-one file distribution using HTTP with interconnection between Primary and Partner MCData systems.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +The diagram illustrates a sequence of interactions between two systems: the Primary MCData system and the Partner MCData system. The Primary system contains three lifelines: MCData client 1, MCData content server, and MCData server FD function. The Partner system contains three lifelines: MCData server FD function, MCData content server, and MCData client 2. The sequence of messages is as follows: + +- MCData client 1 sends a message labeled "1. initiate data request" to MCData client 2. +- MCData client 1 sends a message labeled "2. MCData FD request" to MCData server FD function. +- MCData server FD function sends a message labeled "3. Authorize request" to MCData server FD function in the Partner system. +- MCData server FD function in the Partner system sends a message labeled "4. MCData FD request" to MCData content server. +- MCData content server sends a message labeled "5. MCData FD request" to MCData client 2. +- MCData client 2 sends a message labeled "6. Notify request" to MCData content server. +- MCData content server sends a message labeled "7. MCData FD response" to MCData server FD function in the Partner system. +- MCData server FD function in the Partner system sends a message labeled "8. MCData FD response" to MCData server FD function in the Primary system. +- MCData server FD function in the Primary system sends a message labeled "9. MCData FD response" to MCData client 1. +- MCData client 2 sends a message labeled "10. MCData download data request" to MCData content server. +- MCData content server sends a message labeled "11. MCData file retrieve request" to MCData content server in the Primary system. +- MCData content server in the Primary system sends a message labeled "12. MCData file retrieve response" to MCData content server. +- MCData content server sends a message labeled "13. MCData download data response" to MCData client 2. +- MCData content server sends a message labeled "14. MCData download completed report" to MCData server FD function in the Partner system. +- MCData server FD function in the Partner system sends a message labeled "15. MCData download completed report" to MCData server FD function in the Primary system. +- MCData server FD function in the Primary system sends a message labeled "16. MCData download completed report" to MCData client 1. + +Sequence diagram showing one-to-one file distribution using HTTP with interconnection between Primary and Partner MCData systems. + +**Figure 7.5.2.4.3-1: One-to-one file distribution using HTTP with interconnection** + +1. The user at the MCData client 1 initiates a file distribution request to the MCData user at MCData client 2. + +2. MCData client 1 sends an MCData FD request towards the primary MCData server. The MCData FD request contains content payload in the form of a file URL with the necessary access authorization information and may contain the file metadata information. The MCData FD request indicates the target MCData user for the one-to-one data communication. The MCData FD request contains a conversation identifier for message thread indication. If the MCData user at MCData client 1 has requested to mandatory download at the recipient side, then the MCData FD request contains the mandatory download indication. The MCData FD request may contain a request for a download completed report indication if selected by the user at MCData client 1. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send the MCData FD request and that the size of the file is below maximum data size for FD from the service configuration. +4. The MCData server in the primary MCData system initiates the MCData FD request towards the MCData server in the partner MCData system, which contains the URL of the file which is stored in the primary MCData content server. The request includes the necessary access authorization information as MCData client 2 will retrieve the file while receiving service in the partner MCData system. + +NOTE 1: The contents of and mechanisms to use the authorization information are outside the scope of the present document. + +5. The partner MCData server sends the MCData FD request to MCData client 2. The file URL being provided in MCData FD request to MCData client 2 is prepended with server URI of the partner MCData content server, such that the URL identifies a file location in the partner MCData content server. +6. The receiving MCData client 2 may notify the user about the incoming MCData FD request (including file metadata, if present) which may be either accepted, rejected or ignored. +7. MCData user 2 may provide a response (accept or reject) or not (ignore) to the notification, then MCData client 2 sends the MCData FD response to the partner MCData server. MCData client 2 automatically sends an accepted MCData FD response when the incoming request includes mandatory download indication. +8. The partner MCData server forwards the MCData FD response to the MCData server in the primary MCData system. +9. The primary MCData server forwards the MCData FD response to MCData client 1. +10. MCData client 2 requests the file from the partner MCData content server. + +NOTE 2: Step 10 may occur any time after step 7, before or after steps 8 and 9. + +11. The partner MCData content server checks whether the file is stored locally, and if this is not the case, sends an MCData file retrieve request to the primary MCData content server. The MCData file retrieve request contains the URL of the file location in the primary MCData system, generated by removing the prepended local path from the requested URL. + +NOTE 3: The means of proving authorization for the request is outside the scope of the present document. + +12. The primary MCData content server responds to the partner MCData content server with an MCData file retrieve response which contains the content of the file to be retrieved. File metadata may include the lifetime of the file. The primary MCData content server records that the file has been sent to the indicated partner MCData system. + +NOTE 4: The partner MCData content server may store the local copy of the file in case future requests arise until the expiry time sent from the primary MCData system for the file is reached or until a request is received to delete the file. + +13. The partner MCData content server sends the file to MCData client 2 in the MCData download data response. MCData client 2 records file download completed and notifies MCData user 2. +14. MCData client 2 initiates an MCData download complete report for reporting file download completed, if this was requested by the user at MCData client 1 in the initial MCData FD request. +15. The MCData download complete report is sent to the primary MCData server. The partner MCData server may store the download complete report for download history interrogation from authorized MCData users in the partner MCData system. + +16. The MCData download completed report is sent by the primary MCData server to the MCData user at MCData client 1. The MCData file download completed report from MCData user may be stored by the primary MCData server for download history interrogation from authorized MCData users in the primary MCData system. + +#### 7.5.2.5 One-to-one file distribution using media plane + +##### 7.5.2.5.1 General + +The MCData client uses the media plane for a standalone data file download from another MCData client. The procedure is appropriate for mandatory download case. + +##### 7.5.2.5.2 Procedure + +The procedure in figure 7.5.2.5.2-1 describes the case where an MCData user is initiating one-to-one data communication for sending file to the other MCData user, with or without download completed report request. + +Pre-conditions: + +1. The MCData users on the MCData client 1 and the MCData client 2 are already registered for receiving MCData service. +2. Optionally, the MCData client may have an activated functional alias to be used. +3. The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for One-to-one file distribution using media plane. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. The process starts with MCData client 1 sending an 'initiate data request' to the user. The user then sends an 'MCData FD request' to the MCData server. The server sends an 'Authorize request' and 'Transmission/Reception control' messages. The server then sends an 'MCData FD request' to MCData client 2. MCData client 2 sends a 'Notify request' (dashed box) to the user. The user sends an 'MCData FD response' to the server. The server sends an 'MCData FD response' to MCData client 1. Both clients then perform 'file distribution over media plane'. Finally, the server sends 'MCData download completed report' messages to both clients.](72bc1a2b64dd6bac8285f560440c1218_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData FD request + MCData server->>MCData server: 3. Authorize request + MCData server->>MCData server: 4. Transmission/Reception control + MCData server->>MCData client 2: 5. MCData FD request + Note right of MCData client 2: 6. Notify request + MCData client 2->>MCData server: 7. MCData FD response + MCData server->>MCData client 1: 8. MCData FD response + Note left of MCData client 1: 9. file distribution over media plane + Note right of MCData client 2: 10. file distribution over media plane + MCData server->>MCData client 1: 12. MCData download completed report + MCData server->>MCData client 2: 11. MCData download completed report + +``` + +Sequence diagram for One-to-one file distribution using media plane. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. The process starts with MCData client 1 sending an 'initiate data request' to the user. The user then sends an 'MCData FD request' to the MCData server. The server sends an 'Authorize request' and 'Transmission/Reception control' messages. The server then sends an 'MCData FD request' to MCData client 2. MCData client 2 sends a 'Notify request' (dashed box) to the user. The user sends an 'MCData FD response' to the server. The server sends an 'MCData FD response' to MCData client 1. Both clients then perform 'file distribution over media plane'. Finally, the server sends 'MCData download completed report' messages to both clients. + +**Figure 7.5.2.5.2-1: One-to-one file distribution using media plane** + +1. The user at the MCData client 1 initiates a file distribution request to the chosen MCData user. +2. MCData client 1 sends a MCData FD request towards the MCData server. The MCData FD request may contain the file metadata information. The MCData FD request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData FD request contains conversation identifier for message thread indication. MCData FD request may contain mandatory download indication. The MCData FD request may contain download completed report indication if selected by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the FD data transfer. + - a) If the MCData user at the MCData client 1 initiates an MCData emergency file distribution communication or MCData emergency state is already set for the MCData client 1 (due to previously triggered MCData emergency alert): + +- i) The MCData FD request shall contain emergency indicator; and + - ii) If MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled. + 3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData FD request. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the user. + 4. The MCData server also applies transmission and reception control and the necessary policy to ensure that appropriate data is transmitted between the MCData UEs. + 5. MCData server initiates the MCData FD request towards the MCData user. The MCData FD request towards the MCData user contains the emergency indicator if it is present in the received MCData FD request from MCData client 1. + 6. The receiving MCData client 2 notifies the user about the incoming MCData FD request (including file metadata, if present) which may be either accepted or rejected or ignored. If the request includes mandatory download indication in the MCData FD request an accepted response is assumed. + 7. If the target MCData user 2 provides a response (accept or reject) to the notification, then the MCData client 2 sends the MCData FD response to the MCData server. MCData client 2 automatically sends accepted MCData FD response when the incoming request included mandatory download indication. + 8. MCData server forwards the MCData FD response from MCData client 2 back to MCData client 1. + 9. MCData client 1 distributes the file over the established media plane to MCData server. + 10. MCData server distributes the file received from MCData client 1 to MCData client 2 over the established media plane. File download report is shared by the MCData client 2, if requested by the user at MCData client 1. After file transaction is completed, the media plane is released. The MCData client 2 records file download completed and notifies MCData user 2. +- NOTE: MCData server is not required to wait for the complete download of file from MCData client 1 prior to initiating file distribution to MCData client 2. +11. MCData client 2 initiates a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. + 12. The MCData file download completed report from MCData client may be stored by the MCData server for download history interrogation from the authorized MCData users. MCData download completed report is sent by the MCData server to the user at MCData client 1. + +#### 7.5.2.6 Group standalone file distribution using HTTP + +##### 7.5.2.6.1 General + +The initiation of a group standalone FD using HTTP to a selected group, results in affiliated group members receiving the file data. + +##### 7.5.2.6.2 Procedure + +The procedure in figure 7.5.2.6.2-1 describes the case where a MCData user is initiating group standalone data communication for sending file to multiple MCData users, with or without download completed report request. + +Pre-conditions: + +1. The MCData users on the MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. +2. File to be distributed is uploaded to media storage function on MCData content server using the procedures defined in subclause 7.5.2.2. +3. Optionally, the MCData client may have an activated functional alias to be used. + +4. The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram titled 'Figure 7.5.2.6.2-1: Group standalone FD using HTTP'. The diagram shows interactions between four lifelines: MCData client 1, MCData server, Group management server, and MCData client 2 to n. The sequence of messages is: 1. initiate data request (client 1 to server), 2. MCData group standalone FD request (client 1 to server), 2a. Affiliate user to group (server to server), 3. Resolve group id (server to server), 4. Transmission/Reception control (server to server), 5. MCData group standalone FD request (server to clients 2 to n), 6. Notify request (clients 2 to n to server), 7. MCData group standalone FD response (server to clients 2 to n), 8. MCData group standalone FD response (clients 2 to n to client 1), 9. Download file (clients 2 to n to server), 10. MCData download completed report (server to clients 2 to n), 11. Aggregate download completed report (clients 2 to n to server), 12. MCData download completed report (server to client 1).](d62e2e2281009c16f4ee61660e716cd9_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData group standalone FD request + Note right of MCData server: 2a. Affiliate user to group + Note right of MCData server: 3. Resolve group id + Note right of MCData server: 4. Transmission/Reception control + MCData server->>MCData client 2 to n: 5. MCData group standalone FD request + Note right of MCData client 2 to n: 6. Notify request + MCData client 2 to n->>MCData server: 7. MCData group standalone FD response + MCData server->>MCData client 1: 8. MCData group standalone FD response + Note right of MCData client 2 to n: 9. Download file + MCData client 2 to n->>MCData server: 10. MCData download completed report + Note right of MCData client 2 to n: 11. Aggregate download completed report + MCData server->>MCData client 1: 12. MCData download completed report + +``` + +Sequence diagram titled 'Figure 7.5.2.6.2-1: Group standalone FD using HTTP'. The diagram shows interactions between four lifelines: MCData client 1, MCData server, Group management server, and MCData client 2 to n. The sequence of messages is: 1. initiate data request (client 1 to server), 2. MCData group standalone FD request (client 1 to server), 2a. Affiliate user to group (server to server), 3. Resolve group id (server to server), 4. Transmission/Reception control (server to server), 5. MCData group standalone FD request (server to clients 2 to n), 6. Notify request (clients 2 to n to server), 7. MCData group standalone FD response (server to clients 2 to n), 8. MCData group standalone FD response (clients 2 to n to client 1), 9. Download file (clients 2 to n to server), 10. MCData download completed report (server to clients 2 to n), 11. Aggregate download completed report (clients 2 to n to server), 12. MCData download completed report (server to client 1). + +**Figure 7.5.2.6.2-1: Group standalone FD using HTTP** + +1. The user at the MCData client 1 initiates a file distribution request to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +2. The MCData client 1 sends a MCData group standalone FD request towards the MCData server. The MCData FD request contains content payload in the form of file URL and may contain the file metadata information. The MCData group standalone data request contains either the selected MCData group ID or the target recipients as selected by the user at MCData client 1. The MCData group standalone FD request contains conversation identifier for message thread indication. If MCData user at MCData client 1 has requested to mandatory download at the recipient side, then MCData group standalone FD request contains mandatory download indication. The MCData group standalone FD request may contain download completed report indication if selected by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the FD data transfer. + +If the MCData user at MCData client 1 initiates an MCData emergency FD communication or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert): + +- i) the MCData group standalone FD request shall contain an emergency indicator; +- ii) the MCData group standalone FD request shall set an alert indicator if configured to send an MCData emergency alert while initiating an MCData group standalone FD request for the emergency FD communication; +- iii) if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled; and +- iv) once an MCData emergency communication has been initiated, the MCData group is considered to be in an in-progress emergency state until cancelled; + +If the MCData user at MCData client 1 initiates an MCData imminent peril FD communication: + +- i) the MCData group standalone FD request shall contain imminent peril indicator; and + +- ii) once an MCData imminent peril communication has been initiated, the MCData group is considered to be in an in-progress imminent peril state until cancelled. +- 2a. If either emergency indicator or imminent peril indicator is present in the received MCData group standalone FD request, the MCData server implicitly affiliates MCData client 1 to the MCData group if the client is not already affiliated. + 3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData group standalone FD request and that the size of the file is below maximum data size for FD from the group configuration. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the user. If the MCData group ID is used, the MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. + - i) If an emergency indicator is present in the received MCData group standalone FD request and if the MCData group is not in the in-progress emergency state, the MCData group is consider to be in the in-progress emergency state until cancelled; + - ii) If an imminent peril indicator is present in the received MCData group standalone FD request and if the MCData group is not in the in-progress imminent peril state, the MCData group is considered to be in the in-progress imminent peril state until cancelled; + 4. The MCData server also applies transmission and reception control and the necessary policy control to ensure that appropriate data is transmitted between the MCData users. + 5. MCData server initiates the MCData group standalone FD request towards each MCData user determined in step 3. The MCData group standalone FD request towards each MCData client contains: + - i) an emergency indicator if it is present in the received MCData group standalone FD request from the MCData client 1; + - ii) an imminent peril indicator if it is present in the received MCData group standalone FD request from the MCData client 1; and + - iii) an alert indicator if requested to initiate an emergency alert in the received MCData group standalone FD request from the MCData client 1. + 6. The receiving MCData clients 2 to n notify the user about the incoming MCData group standalone FD request (including file metadata, if present) which may be either accepted or rejected or ignored. + 7. MCData user on MCData clients 2 to n provides a response (accept or reject or ignore) to the notification, then respective MCData client sends the MCData group standalone FD response to the MCData server. MCData client 2 to n automatically sends accepted MCData group standalone FD response when the incoming request included mandatory download indication. + 8. The MCData server forwards the MCData group standalone FD responses to the MCData client 1. +- NOTE: Step 8 can occur at any time following step 5, and prior to step 9 depending on the conditions to proceed with the file transmission. +9. Media storage client of the MCData client(s) downloads the file using the procedures defined in subclause 7.5.2.3, either automatically (for mandatory download) or based upon the MCData user subsequent action. The MCData clients successfully receiving the file through the media storage clients, record file download completed and notify MCData users. + 10. The MCData clients, successfully receiving the file through the media storage client, initiate a MCData download completed reports for reporting file download completed, if requested by the user at MCData client 1. + 11. The MCData file download completed reports from MCData clients may be stored by the MCData server for download history interrogation from the authorized MCData users. The MCData file download completed report from each MCData user may be aggregated. + 12. Aggregated or individual MCData download completed report is sent by the MCData server to the MCData user at MCData client 1. + +#### 7.5.2.7 Group standalone file distribution using media plane + +##### 7.5.2.7.1 General + +The initiation of a group standalone FD using media plane to a selected group, results in affiliated group members receiving the file data. + +##### 7.5.2.7.2 Procedure + +The procedure in figure 7.5.2.7.2-1 describes the case where an MCData user is initiating group standalone data communication for sending file to multiple MCData users, with or without download completed report request. + +Pre-conditions: + +1. The MCData users on the MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. +2. Optionally, the MCData client may have an activated functional alias to be used. +3. The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for Group standalone FD using media plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. The sequence shows steps from initiating a data request to receiving a download completed report.](47e8c2042061e08a14e012472e9fdbaa_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Group management server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData group standalone FD request + Note right of MCData server: 2a. Affiliate user to group + Note right of MCData server: 3. Resolve group id + Note right of MCData server: 4. Transmission/ Reception control + MCData server->>MCData client 2 to n: 5. MCData group standalone FD request + Note right of MCData client 2 to n: 6. Notify request + MCData client 2 to n->>MCData server: 7. MCData group standalone FD response + MCData server->>MCData client 1: 8. MCData group standalone FD response + Note left of MCData server: 9. file distribution over media plane + Note right of MCData server: 10. file distribution over media plane + Note right of MCData client 2 to n: 11. Notify data + MCData client 2 to n->>MCData server: 12. MCData download completed report + Note right of MCData server: 13. Aggregate download completed reports + MCData server->>MCData client 1: 14. MCData download completed report + +``` + +Sequence diagram for Group standalone FD using media plane. Lifelines: MCData client 1, MCData server, Group management server, MCData client 2 to n. The sequence shows steps from initiating a data request to receiving a download completed report. + +Figure 7.5.2.7.2-1: Group standalone FD using media plane + +1. The user at the MCData client 1 initiates a file distribution request to multiple MCData users selecting a pre-configured group (identified by MCData group ID) and optionally particular members from that group. +2. MCData client 1 sends a MCData group standalone FD request towards the MCData server. The MCData group standalone FD request may contain the file metadata information. The MCData group standalone data request contains target recipient(s) as selected by the user at MCData client 1. The MCData group standalone FD request contains conversation identifier for message thread indication. MCData group standalone FD request may contain mandatory download indication. The MCData group standalone FD request may contain download completed report indication if selected by the user at MCData client 1. MCData user at MCData client 1 may include a functional alias within the FD data transfer. + +If the MCData user at MCData client 1 initiates an MCData emergency file distribution communication or the MCData emergency state is already set for the MCData client 1 (due to a previously triggered MCData emergency alert): + +- i) the MCData group standalone FD request shall contain an emergency indicator; +- ii) the MCData group standalone FD request shall set an alert indicator if configured to send an MCData emergency alert while initiating an MCData group standalone FD request for the emergency file distribution service communication; +- iii) if the MCData emergency state is not set already, MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled; and +- iv) once an MCData emergency communication has been initiated, the MCData group is considered to be in an in-progress emergency state until cancelled; + +If the MCData user at MCData client 1 initiates an MCData imminent peril short data service communication: + +- i) the MCData group standalone FD request shall contain imminent peril indicator; and +- ii) once an MCData imminent peril communication has been initiated, the MCData group is considered to be in an in-progress imminent peril state until cancelled. + +- 2a. If either emergency indicator or imminent peril indicator is present in the received MCData group standalone data request, the MCData server implicitly affiliates MCData client 1 to the MCData group if the client is not already affiliated. +3. MCData server checks whether the MCData user at MCData client 1 is authorized to send MCData group standalone FD request. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the user. The MCData server resolves the MCData group ID to determine the members of that group and their affiliation status, based on the information from the group management server. + - i) If an emergency indicator is present in the received MCData group standalone FD request and if the MCData group is not in the in-progress emergency state, the MCData group is considered to be in the in-progress emergency state until cancelled; + - ii) If an imminent peril indicator is present in the received MCData group standalone FD request and if the MCData group is not in the in-progress imminent peril state, the MCData group is considered to be in the in-progress imminent peril state until cancelled; +4. The MCData server also applies transmission and reception control and the necessary policy to ensure that appropriate data is transmitted between the MCData UEs. +5. MCData server initiates the MCData group standalone FD request towards each MCData user determined in step 3. The MCData group standalone data request towards each MCData client contains: + - i) an emergency indicator if it is present in the received MCData group standalone FD request from the MCData client 1; + - ii) an imminent peril indicator if it is present in the received MCData group standalone FD request from the MCData client 1; and + - iii) an alert indicator if requested to initiate an emergency alert in the received MCData group standalone FD request from the MCData client 1. +6. The receiving MCData clients 2 to n notifies the user about the incoming MCData group standalone FD request (including file metadata if present) which may be either accepted or rejected or ignored. If the request includes mandatory download indication in the MCData group standalone FD request an accepted response is assumed. +7. If the target MCData user on MCData clients 2 to n provides a response (accept or reject) to the notification, then the respective MCData client sends the MCData group standalone FD response to the MCData server. MCData client 2 to n automatically sends accepted MCData group standalone FD response when the incoming request included mandatory download indication. +8. MCData server forwards the MCData group standalone FD response to the MCData client 1. + +**NOTE 1:** Step 8 can occur at any time following step 5, and prior to step 9 depending on the conditions to proceed with the file transmission. + +9. MCData client 1 and MCData server have successfully established media plane for file transmission and the MCData client 1 transmits the file data. + +10. MCData server distributes the file received from MCData client 1 to MCData clients 2 to n over the established media plane. Distribution of file can be via unicast or via MBMS bearer(s). For distribution via MBMS bearer(s), the procedure described in subclause 7.3 Use of MBMS transmission (on-network) is executed. File download report is shared by the receiving MCData clients, if requested by the user at MCData client 1. After file transaction is completed, the media plane is released. + +**NOTE 2:** MCData server is not required to wait for the complete download of file from MCData client 1 prior to initiating file distribution to MCData client 2. + +11. The MCData clients successfully receiving the file, records file download completed and notifies MCData user. + +12. MCData client 2 initiates a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. + +13. The MCData file download completed report from MCData client(s) may be stored by the MCData server for download history interrogation from the authorized MCData users. The MCData file download completed report from each MCData user may be aggregated. + +14. Aggregated or individual MCData file download completed report is sent to the disposition requesting user at MCData client 1. + +#### 7.5.2.8 File removal using HTTP by authorized user + +##### 7.5.2.8.1 General + +The media storage client uses HTTP to remove a file that was previously uploaded to the MCData content server. + +##### 7.5.2.8.2 Procedure for single MCData system + +The procedure in figure 7.5.2.8.2-1 describes the case where a MCData user is removing the file that was previously uploaded to the MCData content server. + +Pre-conditions: + +1. The MCData user on the media storage client is registered for receiving MCData service. +2. The file has been successfully uploaded by the MCData user using the procedures defined in subclause 7.5.2.2. +3. The MCData content server has the ability to verify if the requesting MCData user is authorised to remove. + +![Sequence diagram showing file removal procedure between Media storage client and MCData content server. Step 1: initiate file removal request (internal to client). Step 2: MCData remove file request by user (client to server). Step 3: Using URL to remove the file (internal to server). Step 4: MCData remove file response by user (server to client).](98a45dd7d474e067b7533cc966c11e95_img.jpg) + +``` + +sequenceDiagram + participant MSC as Media storage client + participant MCS as MCData content server + Note over MSC: 1. initiate file removal request + MSC->>MCS: 2. MCData remove file request by user + Note over MCS: 3. Using URL to remove the file + MCS->>MSC: 4. MCData remove file response by user + +``` + +Sequence diagram showing file removal procedure between Media storage client and MCData content server. Step 1: initiate file removal request (internal to client). Step 2: MCData remove file request by user (client to server). Step 3: Using URL to remove the file (internal to server). Step 4: MCData remove file response by user (server to client). + +**Figure 7.5.2.8.2-1: File removal using HTTP by authorised user** + +1. The user on the media storage client decides to remove a file that was previously uploaded. +2. The URL of the file to be removed is included in the request sent to the media storage function on the MCData content server. + +3. The MCData content server remove the file indicated by the URL. +4. The MCData content server informs the media storage client if the file is successfully removed. + +Editor's note: It is FFS if and how the recipients of the file URL need to be notified if the file is no longer available to be downloaded + +##### 7.5.2.8.3 Procedure for interconnection between MCData systems + +The procedure in figure 7.5.2.8.3-1 describes the case where an MCData user removes the file that was previously uploaded to the primary MCData system MCData content server, and where the file has been made available in the partner MCData system MCData content server. + +Pre-conditions: + +1. The MCData user on the media storage client is registered for receiving MCData service. +2. The file has previously been uploaded to the MCData content server in the primary MCData system of MCData client 1. +3. The file has been successfully transferred to the MCData content server in the partner MCData system. + +![Sequence diagram for Figure 7.5.2.8.3-1: File removal using HTTP by authorized user. The diagram shows interactions between a Media storage client, MCData content server, and MCData server FD function in both a Primary MCData system and a Partner MCData system. The process involves initiating a removal request, using a URL to remove the file, and sending responses between the systems.](b28af4985cdef1e519e3aaf26561dcb3_img.jpg) + +``` + +sequenceDiagram + participant MSC as Media storage client + participant MCS as MCData content server + participant MSFD as MCData server FD function + subgraph Primary MCData system + MSC + MCS + MSFD + end + subgraph Partner MCData system + MSFD + MCS + end + Note left of MSC: 1. initiate file removal request + MSC->>MCS: 2. MCData remove file request by user + Note right of MCS: 3. Use URL to remove file + MCS->>MCS: 4. MCData remove file request by user + Note right of MCS: 5. Use URL to remove file + MCS->>MSFD: 6. MCData remove file response by user + MSFD->>MCS: 7. MCData remove file response by user + +``` + +Sequence diagram for Figure 7.5.2.8.3-1: File removal using HTTP by authorized user. The diagram shows interactions between a Media storage client, MCData content server, and MCData server FD function in both a Primary MCData system and a Partner MCData system. The process involves initiating a removal request, using a URL to remove the file, and sending responses between the systems. + +**Figure 7.5.2.8.3-1: File removal using HTTP by authorized user** + +1. The user on the media storage client decides to remove a file that was previously uploaded. + 2. The URL of the file to be removed is included in the request sent to the media storage function on the primary MCData content server. + 3. The primary MCData content server removes the file indicated by the URL. +- NOTE: Step 3 may occur at any time following step 2 and before step 6. +4. As the primary MCData content server has recorded that the file has previously been sent to the partner MCData system, the primary MCData content server sends the MCData remove file request by user to the partner MCData content server, containing the URL of the file which was stored on the primary MCData content server. + 5. The partner MCData content server removes the file indicated by the URL. + 6. The partner MCData content server informs the primary MCData content server that the file has been successfully removed. + +7. The primary MCData content server informs the media storage client if the file is successfully removed. + +**Editor's note: It is FFS if and how the recipients of the file URL need to be notified if the file is no longer available to be downloaded** + +#### 7.5.2.9 Void + +#### 7.5.2.10 Group standalone file distribution using the MBMS download delivery method + +##### 7.5.2.10.1 General + +The initiation of a group standalone FD to a selected group results in affiliated group members receiving the file data over MBMS. + +The first steps of the procedure are identical to the procedure Group standalone file distribution using HTTP (7.5.2.6). Based on the density and distribution of target group members, the MCData server may decide to deliver the file over MBMS. + +##### 7.5.2.10.2 Procedure + +The procedure in figure 7.5.2.10.2-1 describes the case where a MCData user is initiating group standalone data communication for sending file to multiple MCData users, with or without download completed report request. + +Pre-conditions: + +1. The MCData users on the MCData client 1 to n belong to the same group and are already registered for receiving MCData service and affiliated. +2. File to be distributed is uploaded to media storage function on MCData content server using the procedures defined in subclause 7.5.2.2. + +![Sequence diagram for Group standalone FD using the MBMS download delivery method. Lifelines: MCData client 1, MCData server, MCData Content Server, MCData client 2 to n. The sequence shows steps 1 through 14, including data request initiation, group ID resolution, MBMS bearer establishment, and file download completion reporting.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData Content Server + participant MCData client 2 to n + + Note left of MCData client 1: 1. initiate data request + MCData client 1->>MCData server: 2. MCData group standalone FD request + Note right of MCData server: 3. Resolve group id + Note right of MCData server: 4. Transmission/Reception control + Note right of MCData server: 5. establish MBMS Bearer + MCData server->>MCData client 2 to n: 6. MCData group standalone FD over MBMS request + Note right of MCData client 2 to n: 7. Notify request + MCData client 2 to n->>MCData server: 8. MCData group standalone FD response + MCData server->>MCData client 1: 9. MCData group standalone FD response + Note right of MCData client 2 to n: 10. Receive file + Note right of MCData client 2 to n: 11. Download missing parts + MCData client 2 to n->>MCData server: 12. MCData download completed report + Note right of MCData server: 13. Aggregate download completed report + MCData server->>MCData client 1: 14. MCData download completed report + +``` + +Sequence diagram for Group standalone FD using the MBMS download delivery method. Lifelines: MCData client 1, MCData server, MCData Content Server, MCData client 2 to n. The sequence shows steps 1 through 14, including data request initiation, group ID resolution, MBMS bearer establishment, and file download completion reporting. + +**Figure 7.5.2.10.2-1: Group standalone FD using the MBMS download delivery method** + +1-4. Steps 1-4 are the same as in the procedure for Group standalone FD using HTTP (7.5.2.6). + +5. The MCData server executes the procedure described in subclause 7.3.5 Use of MBMS user services for file distribution. The MCData server provides, in the MBMS session properties (subclause 5.4 of 3GPP TS 26.348 [19]), the file location on the media storage function and sets the earlier fetch time with a long enough delay so that steps 6 to 8 are executed before the delivery over MBMS. + +6. MCData server initiates the MCData group standalone FD over MBMS request towards each MCData user determined in step 3. The request is sent over unicast or within an MBMS bearer for application level control signalling. + +7. The receiving MCData clients 2 to n notify the user about the incoming MCData group standalone FD request (including file metadata, if present). + +8. MCData client 2 to n automatically sends accepted MCData group standalone FD response when the incoming request included mandatory download indication. + +NOTE 1: When the UE is in idle mode, MCData clients may skip step 8. + +9. The MCData server forwards the MCData group standalone FD responses to the MCData client 1. + +NOTE 2: Step 8 can occur at any time following step 6, and prior to step 10 depending on the conditions to proceed with the file transmission. + +10. The MCData client receives the file delivered over MBMS. + +11. If losses occurred after the end of the file delivery over MBMS, the MCData client downloads the missing parts using the procedures defined in subclause 7.5.2. + +Editor's note: whether any enhancements are required on MCData-FD5 are FFS. + +- NOTE 3: If the MBMS reception quality is too bad, the Media storage client of the MCData client(s) downloads the file using the procedures defined in subclause 7.5.2.3. +12. The MCData clients, after a successfully reception, initiate a MCData download completed reports for reporting file download completed, if requested by the user at MCData client 1. + 13. The MCData file download completed reports from MCData clients may be stored by the MCData server for download history interrogation from the authorized MCData users. The MCData file download completed report from each MCData user may be aggregated. + 14. Aggregated or individual MCData download completed report is sent by the MCData server to the MCData user at MCData client 1. + +#### 7.5.2.11 One-to-one FD communication upgrade to an emergency FD communication + +##### 7.5.2.11.1 General + +This clause is for adding procedures related to upgrading an existing one-to-one FD communication to an emergency one-to-one FD communication. + +##### 7.5.2.11.2 Procedure + +The procedure in figure 7.5.2.11.2-1 describes the case where an authorized MCData user is upgrading a MCData one-to-one FD communication to a MCData emergency one-to-one FD communication. This procedure is applicable only when MCData one-to-one file distribution communication is established as described in subclause 7.5.2.5 "One-to-one file distribution using media plane". + +Pre-conditions: + +1. Both members of the one-to-one FD communication belong to the same MCData system. +2. One-to-one FD communication is already in progress. + +![Sequence diagram illustrating the one-to-one FD communication upgrade to an emergency one-to-one FD communication. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2 within a Home MCData service provider. The process starts with an emergency communication initiation at client 1, followed by upgrade requests to the server and then to client 2. The server notifies client 2, receives responses, adjusts bearer priority, and finally establishes the media plane over an upgraded bearer.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note over MCData client 1, MCData server, MCData client 2: MCData one-to-one FD communication is in progress + Note left of MCData client 1: 1. initiate emergency communication + MCData client 1->>MCData server: 2. MCData one-to-one FD upgrade request + MCData server->>MCData client 2: 3. MCData one-to-one FD upgrade request + Note right of MCData client 2: 4. Notify emergency communication + MCData client 2->>MCData server: 5. MCData one-to-one FD upgrade response + Note left of MCData server: 6. Bearer priority adjustment + MCData server->>MCData client 1: 7. MCData one-to-one FD upgrade response + Note over MCData client 1, MCData server, MCData client 2: 8. Media plane and floor control establishment over upgraded bearer + +``` + +Sequence diagram illustrating the one-to-one FD communication upgrade to an emergency one-to-one FD communication. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2 within a Home MCData service provider. The process starts with an emergency communication initiation at client 1, followed by upgrade requests to the server and then to client 2. The server notifies client 2, receives responses, adjusts bearer priority, and finally establishes the media plane over an upgraded bearer. + +**Figure 7.5.2.11.2-1 One-to-one FD communication upgrade to an emergency one-to-one FD communication** + +1. The MCData user at MCData client 1 initiates an emergency. MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled. +2. MCData client 1 requests the MCData server to upgrade the MCData one-to-one FD communication to in-progress emergency by sending a MCData one-to-one FD upgrade request. +3. The MCData server sends the MCData one-to-one FD upgrade request towards the MCData client of the other participant. +4. The MCData user is notified of the in-progress emergency of the MCData emergency one-to-one FD communication. +5. The receiving MCData client acknowledges the MCData one-to-one FD upgrade request and sends MCData one-to-one FD upgrade response to the MCData server. +6. The MCData server adjusts the priority of the underlying bearer for both participants of the MCData one-to-one FD communication. The priority is retained until the communication ends. +7. The MCData server sends MCData one-to-one FD upgrade response to MCData client 1. +8. MCData client 1 and MCData client 2 continue with the MCData one-to-one FD communication, which has been transformed into an MCData emergency one-to-one FD communication. + +#### 7.5.2.12 Group FD communication upgrade to an emergency group FD communication + +##### 7.5.2.12.1 General + +This clause is for adding procedures related to upgrading an existing MCData group FD communication to an MCData emergency group FD communication. + +##### 7.5.2.12.2 Procedure + +The procedure in figure 7.5.2.12-1 describes the case where an authorized MCData user is upgrading an ongoing MCData group FD communication to an MCData emergency group FD communication. This procedure is applicable only when group MCData FD communication is established as described in subclause 7.5.2.7 "Group standalone file distribution using media plane". + +NOTE 1: For simplicity, a single MCData server is shown in place of a user home MCData server and a group hosting MCData server. + +Pre-conditions: + +1. The MCData group is previously defined on the group management server with MCData client 1, MCData client 2 and MCData client 3 are affiliated to that MCData group. +2. All members of the MCData group belong to the same MCData system. +3. An MCData group FD communication is already in progress. +4. The initiating MCData client 1 has been configured to send an MCData emergency alert when upgrading an MCData emergency group communication. + +![Sequence diagram showing the procedure to upgrade an MCData group FD communication to an MCData emergency group FD communication. The diagram involves four lifelines: MCData client 1, MCData server, MCData client 2, and MCData client 3, all under the 'Home MCData service provider'. The process starts with a bar 'MCData group FD communication is in progress'. Step 1: MCData client 1 initiates a group emergency. Step 2: MCData client 1 sends an MCData group FD upgrade request to the MCData server. Step 3: The MCData server performs a bearer priority adjustment. Step 4: The MCData server sends an MCData group FD upgrade request to MCData client 2 and MCData client 3. Step 5: MCData client 2 and MCData client 3 notify the group emergency status. Step 6: MCData client 2 and MCData client 3 send an MCData group FD upgrade response to the MCData server. Step 7: The MCData server sends an MCData group FD upgrade response to MCData client 1. The process ends with a bar 'MCData group FD communication over upgraded bearer'.](f6e8acf9f931452d01688d311b5c0364_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client 3 + Note over MCData client 1, MCData client 3: MCData group FD communication is in progress + MCData client 1->>MCData server: 1. Initiate group emergency + MCData client 1->>MCData server: 2. MCData group FD upgrade request + Note over MCData server: 3. Bearer priority adjustment + MCData server->>MCData client 2: 4. MCData group FD upgrade request + MCData server->>MCData client 3: 4. MCData group FD upgrade request + Note over MCData client 2, MCData client 3: 5. Notify group emergency status + MCData client 2->>MCData server: 6. MCData group FD upgrade response + MCData client 3->>MCData server: 6. MCData group FD upgrade response + MCData server->>MCData client 1: 7. MCData group FD upgrade response + Note over MCData client 1, MCData client 3: MCData group FD communication over upgraded bearer +``` + +Sequence diagram showing the procedure to upgrade an MCData group FD communication to an MCData emergency group FD communication. The diagram involves four lifelines: MCData client 1, MCData server, MCData client 2, and MCData client 3, all under the 'Home MCData service provider'. The process starts with a bar 'MCData group FD communication is in progress'. Step 1: MCData client 1 initiates a group emergency. Step 2: MCData client 1 sends an MCData group FD upgrade request to the MCData server. Step 3: The MCData server performs a bearer priority adjustment. Step 4: The MCData server sends an MCData group FD upgrade request to MCData client 2 and MCData client 3. Step 5: MCData client 2 and MCData client 3 notify the group emergency status. Step 6: MCData client 2 and MCData client 3 send an MCData group FD upgrade response to the MCData server. Step 7: The MCData server sends an MCData group FD upgrade response to MCData client 1. The process ends with a bar 'MCData group FD communication over upgraded bearer'. + +**Figure 7.5.2.12-1: MCData group FD communication upgraded to an MCData emergency group FD communication** + +1. The MCData user at MCData client 1 initiates a group emergency. MCData client 1 sets its MCData emergency state. The MCData emergency state is retained until explicitly cancelled. +2. MCData client 1 requests the MCData server to upgrade the MCData group to an in-progress emergency state by sending a MCData group FD upgrade request. The MCData client 1 sets emergency indicator in the request. If configured to send an MCData alert when initiating an MCData emergency upgrade, the request also contains an indication that an MCData alert is to be initiated. + +3. The MCData server adjusts the priority of the underlying bearer for all or selected participants in the MCData group FD communication that receive the communication over unicast. + +NOTE 2: The determination of the selected participants whose bearers have to be upgraded is left to implementation. + +4. MCData server sends the MCData group FD upgrade request towards the MCData clients of each of those affiliated MCData group members. The request contains an indication of an MCData emergency alert if the request from the originator indicated MCData emergency alert. +5. MCData users are notified of the in-progress emergency state of the MCData group. +6. The receiving MCData clients send the MCData group FD upgrade response to the MCData server to acknowledge the MCData group emergency request. For a multicast call, these acknowledgements are not sent. +7. The MCData server sends the MCData group FD upgrade response to the MCData user 1 to confirm the upgrade request. + +NOTE 3: Step 7 can occur at any time following step 3, and prior to step 8 depending on the conditions to proceed with the call. + +MCData client 1, MCData client 2 and MCData client 3 continue with the MCData group FD communication, which has been transformed into an MCData emergency group FD communication. + +#### 7.5.2.13 Group FD communication in-progress emergency group state cancel + +##### 7.5.2.13.1 General + +This clause is for adding procedures related to an MCData in-progress emergency group state cancel. + +##### 7.5.2.13.2 Procedure + +The procedure in figure 7.5.2.13-1 describes the case where an authorized MCData user cancels MCData group's in-progress emergency. + +Pre-conditions: + +1. The MCData group is previously defined on the group management server with MCData client 1, MCData client 2 and MCData client 3 affiliated to that MCData group. +2. All members of the MCData group belong to the same MCData system. +3. MCData group members have been notified about the in-progress emergency. +4. The MCData group is in the in-progress emergency state and has prioritized bearer support. +5. MCData client 1 previously initiated the in-progress emergency for the group. + +![Sequence diagram showing MCData group FD in-progress emergency group state cancel procedure between MCData client 1, MCData server, and MCData clients 2 and 3.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCData client 1 + participant S as MCData server + participant C2 as MCData client 2 + participant C3 as MCData client 3 + + Note over C1, C3: MCData group FD emergency communication is in progress + + Note left of C1: 1. Initiate in-progress +emergency group state +cancel + C1->>S: 2. MCData group FD in-progress priority state cancel request + Note over S: 3. Bearer priority +adjustment + S->>C2: 4. MCData group FD in-progress priority state cancel request + S->>C3: 4. MCData group FD in-progress priority state cancel request + Note right of C2: 5. Notify +emergency cancel + Note right of C3: 5. Notify +emergency cancel + C2-->>S: 6. MCData group FD in-progress priority state cancel response + C3-->>S: 6. MCData group FD in-progress priority state cancel response + S->>C1: 7. MCData group FD in-progress priority state cancel response + + Note over C1, C3: MCData group FD communication continues + +``` + +Sequence diagram showing MCData group FD in-progress emergency group state cancel procedure between MCData client 1, MCData server, and MCData clients 2 and 3. + +**Figure 7.5.2.13-1: MCData group FD in-progress emergency group state cancel** + +1. The user at the MCData client 1 initiates an MCData group FD in-progress emergency group state cancel. + +NOTE 1: An MCData user authorized to cancel in-progress emergencies on the MCData group can also be authorised to cancel the MCData emergency alert in addition to the initiator. However, only the initiator can cancel the initiator's local MCData emergency state. + +2. The MCData client 1 sends an MCData group FD in-progress priority state cancel request to the MCData server. The MCData client 1 also resets emergency indicator in the request to inform MCData server about cancelation of in-progress emergency group state. + +NOTE 2: When MCData emergency alerts are in effect together with an MCData in-progress emergency group state on the same MCData group, the MCData emergency alert can, under some circumstances be cancelled at the same time. In that case, the MCData group FD in-progress priority group state cancel request carries an indication that the alert is also being cancelled. + +3. The MCData server adjusts the priority of the underlying bearer; priority treatment is no longer required. The MCData server cancels/resets the emergency in-progress state of the MCData group. +4. The MCData server sends an MCData group FD in-progress priority state cancel request to the MCData group members. +5. MCData group members are notified of the MCData group FD in-progress emergency state cancel. +6. The receiving MCData clients send the MCData group FD in-progress priority state cancel response to the MCData server to acknowledge the MCData in-progress emergency group state cancel. For a multicast call scenario, these acknowledgements are not sent. +7. The MCData server sends the MCData group FD in-progress priority state cancel response to the MCData user 1 to confirm the MCData in-progress emergency group state cancel. If the MCData in-progress emergency group + +state cancel request (in step 2) contained the "Alert indicator" IE, the MCData client 1 resets its local emergency status. + +NOTE 3: Step 7 can occur at any time following step 3, depending on the conditions to proceed with the call. + +#### 7.5.2.14 Group FD communication upgrade to an imminent peril group FD communication + +##### 7.5.2.14.1 General + +This clause is for adding procedures related to an imminent peril group FD communication. + +##### 7.5.2.14.2 Procedure + +This procedure is applicable only when group MCData communication is established as described in subclause 7.5.2.7 "Group standalone file distribution using media plane". The MCData service shall support the procedures and related information flows as specified in subclause 7.5.2.12 "Group FD communication upgrade to an emergency group FD communication" with the following clarifications: + +- In step 2), The MCData client 1 set imminent peril indicator; and +- In step 5), MCData users are notified of the in-progress imminent peril state of the MCData group. + +#### 7.5.2.15 Group FD communication in-progress imminent peril group state cancel + +##### 7.5.2.15.1 General + +This clause is for adding procedures related to an imminent peril group state cancel. + +##### 7.5.2.15.2 Procedure + +The MCData service shall support the procedures and related information flows as specified in subclause 7.5.2.13 "Group FD communication in-progress emergency group state cancel" with the following clarifications: + +- In step 2), The MCData client 1 set imminent peril indicator; and +- In step 5), MCData users are notified of the in-progress imminent peril state cancel. + +### 7.5.3 File distribution for off-network + +#### 7.5.3.2 Information flows for file distribution + +##### 7.5.3.2.1 MCData FD request (using media plane) + +Table 7.5.3.2.1-1 describes the information flow for the MCData FD request sent from the MCData client to another MCData client. + +**Table 7.5.3.2.1-1: MCData FD request (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|-------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending file | +| MCData ID | M | The identity of the MCData user receiving file | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed reported is expected or not | +| Download indication | O | Indicates mandatory download. (i.e. auto accept this media plane setup request) | +| SDP offer | M | Media parameters offered | +| Content reference | M | URL reference to the content and file metadata information | + +##### 7.5.3.2.2 MCDATA FD response (using media plane) + +Table 7.5.3.2.2-1 describes the information flow for the MCDATA FD response sent from the MCDATA client to another MCDATA client. + +**Table 7.5.3.2.2-1: MCDATA FD response (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user sending FD request | +| MCDATA ID | M | The identity of the MCDATA user sending response | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | +| Acceptance confirmation | M | An indication whether the client has positively accepted the request | + +##### 7.5.3.2.3 MCDATA download completed report + +Table 7.5.3.2.3-1 describes the information flow for the MCDATA download completed report sent from the MCDATA client to another MCDATA client. + +**Table 7.5.3.2.3-1: MCDATA download completed report** + +| Information element | Status | Description | +|--------------------------|--------|--------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user sending FD request | +| MCDATA ID | M | The identity of the MCDATA user sending response | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCDATA transaction | +| Disposition association | M | Identifies the original MCDATA transaction | +| Disposition confirmation | M | An indication that the client has completed downloading file | + +##### 7.5.3.2.4 MCDATA group standalone FD request (using media plane) + +Table 7.5.3.2.4-1 describes the information flow for the MCDATA group standalone FD request sent from the MCDATA client to another MCDATA client. + +**Table 7.5.3.2.4-1: MCDATA group standalone FD request (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|-------------------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user sending file | +| MCDATA group ID | M | The MCDATA group ID to which the data is to be sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCDATA transaction | +| Reply Identifier | O | Identifies the original MCDATA transaction to which the current transaction is a reply to | +| Disposition indication | O | Indicates whether file download completed reported is expected or not | +| Download indication | O | Indicates mandatory download. (i.e. auto accept this media plane setup request) | +| SDP offer | M | Media parameters offered | +| Content reference | M | URL reference to the content and file metadata information | + +##### 7.5.3.2.5 MCDATA group standalone FD response (using media plane) + +Table 7.5.3.2.5-1 describes the information flow for the MCDATA group standalone FD response sent from the MCDATA client to another MCDATA client. + +**Table 7.5.3.2.5-1: MCData group standalone FD response (using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending FD request | +| MCData group ID | M | The MCData group ID to which the file is to be sent | +| MCData ID | M | The identity of the MCData user sending response | +| Conversation Identifier | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | +| Acceptance confirmation | M | An indication whether the client has positively accepted the request | + +#### 7.5.3.3 One-to-one standalone file distribution using media plane + +##### 7.5.3.3.1 General + +The MCData client uses media plane for a standalone FD download from another MCData client in off-network. + +##### 7.5.3.3.2 Procedure + +Figure 7.5.3.3.2-1 describes procedures for an off-network MCData client 1 initiating one-to-one MCData data communication for sending standalone FD data to other MCData client, with or without download completed report request. + +Pre-conditions: + +1. MCData user 1 has initiated communication for sending standalone FD data to other MCData user 2. +2. MCData client 1 and MCData client 2 are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable. +3. MCData client 1 has discovered MCData client 2 in proximity, associated with MCData user 2, using ProSe Discovery procedures. + +![Sequence diagram showing the procedure for one-to-one standalone file distribution between MCData client 1 and MCData client 2.](f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCData client 1 + participant C2 as MCData client 2 + C1->>C2: 1. MCData FD request + Note over C2: 2. Assert policy + Note over C2: 3. Notify request + C2-->>C1: 4. MCData FD response + Note over C1,C2: 5. file distribution over media plane + C2-->>C1: 6. MCData download completed report + +``` + +The diagram illustrates the message flow between MCData client 1 and MCData client 2. It starts with an FD request from client 1 to client 2. Client 2 then performs internal actions (Assert policy and Notify request). Client 2 responds with an FD response. This is followed by the actual file distribution over the media plane (represented by a large green arrow from client 1 towards client 2). Finally, client 2 sends a download completed report back to client 1. + +Sequence diagram showing the procedure for one-to-one standalone file distribution between MCData client 1 and MCData client 2. + +**Figure 7.5.3.3.2-1: One-to-one standalone file distribution using media plane** + +1. MCData client 1 sends a MCData FD request towards the MCData client 2. The MCData FD request may contain the file metadata information. The MCData FD request contains one MCData user for one-to-one data communication as selected by the user at MCData client 1. The MCData FD request contains conversation identifier for message thread indication. MCData FD request may contain mandatory download indication. The + +MCDData FD request may contain download completed report indication if selected by the user at MCDData client 1. + +2. On receiving a MCDData FD request, the MCDData client 2 checks whether any policy is to be asserted to limit certain types of message or content to certain members, for example, due to location or user privilege. +3. The receiving MCDData client 2 notifies the user about the incoming MCDData FD request (including file metadata if present) which may be either accepted or rejected or ignored. MCDData user may not be sought consent if the request includes mandatory download indication in the MCDData FD request and instead only notify the MCDData user about file downloading. +4. If the target MCDData user 2 provides a response (accept or reject) to the notification, then the MCDData client 2 sends the MCDData FD response to the MCDData client 1. MCDData client 2 automatically sends accepted MCDData FD response when the incoming request included mandatory download indication. +5. MCDData client 1 distributes the file over the established media plane to MCDData client 2. +6. The MCDData client 2 records file download completed and notifies MCDData user 2. MCDData client 2 initiates a MCDData download completed report for reporting file download completed, if requested by the user at MCDData client 1. + +#### 7.5.3.4 Group standalone file distribution using media plane + +##### 7.5.3.4.1 General + +The initiation of a group standalone FD to a selected group results in off-network MCDData group members receiving the file data. + +##### 7.5.3.4.2 Procedure + +Figure 7.5.3.4.2-1 describes procedures for an off-network MCDData client 1 initiating group MCDData data communication for sending FD data to a MCDData group, with or without download completed report request. + +Pre-conditions: + +1. MCDData user 1 has initiated group communication for sending FD data to the MCDData group. +2. Information for ProSe direct communications corresponding to the MCDData group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCDData client 1. +3. MCDData client 1 to MCDData client N are members of the same MCDData group. + +![Sequence diagram illustrating Group standalone file distribution using media plane. Lifelines: MCData client 1, MCData client 2, MCData client N. The sequence starts with MCData client 1 sending a '1. MCData group standalone FD request' to MCData client N. MCData client N responds with '2. Assert policy' and '3. Notify request'. MCData client 2 also responds with '2. Assert policy' and '3. Notify request'. MCData client 1 receives '4. MCData group standalone FD response' from both MCData client 2 and MCData client N. MCData client 1 then initiates '5. File distribution over media plane' to MCData client 2. MCData client 2 receives the file and sends '6. Notify data' to MCData client N. Finally, MCData client 2 sends '7. MCData download completed report' to MCData client 1.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + participant MCData client N + Note right of MCData client 1: 1. MCData group standalone FD request + MCData client 1->>MCData client N: 1. MCData group standalone FD request + Note right of MCData client N: 2. Assert policy + MCData client N-->>MCData client N: 2. Assert policy + Note right of MCData client N: 3. Notify request + MCData client N-->>MCData client N: 3. Notify request + Note right of MCData client 2: 2. Assert policy + MCData client 2-->>MCData client 2: 2. Assert policy + Note right of MCData client 2: 3. Notify request + MCData client 2-->>MCData client 2: 3. Notify request + MCData client 2->>MCData client 1: 4. MCData group standalone FD response + MCData client N->>MCData client 1: 4. MCData group standalone FD response + Note right of MCData client 1: 5. File distribution over media plane + MCData client 1->>MCData client 2: 5. File distribution over media plane + Note right of MCData client 2: 6. Notify data + MCData client 2->>MCData client N: 6. Notify data + Note right of MCData client 2: 7. MCData download completed report + MCData client 2-->>MCData client 1: 7. MCData download completed report + +``` + +Sequence diagram illustrating Group standalone file distribution using media plane. Lifelines: MCData client 1, MCData client 2, MCData client N. The sequence starts with MCData client 1 sending a '1. MCData group standalone FD request' to MCData client N. MCData client N responds with '2. Assert policy' and '3. Notify request'. MCData client 2 also responds with '2. Assert policy' and '3. Notify request'. MCData client 1 receives '4. MCData group standalone FD response' from both MCData client 2 and MCData client N. MCData client 1 then initiates '5. File distribution over media plane' to MCData client 2. MCData client 2 receives the file and sends '6. Notify data' to MCData client N. Finally, MCData client 2 sends '7. MCData download completed report' to MCData client 1. + +**Figure 7.5.3.4.2-1: Group standalone file distribution using media plane** + +1. MCData client 1 sends a MCData FD request towards the MCData group. The MCData group standalone FD request may contain the file metadata information. The MCData group standalone data request contains MCData group ID as selected by the user at MCData client 1. The MCData group standalone FD request contains conversation identifier for message thread indication. MCData group standalone FD request may contain mandatory download indication. The MCData group standalone FD request may contain download completed report indication if selected by the user at MCData client 1. +2. On receiving a MCData FD request, the MCData clients check whether any policy is to be asserted to limit certain types of message or content to certain members, for example, due to location or user privilege. +3. If the policy assertion is positive, the receiving MCData clients 2 to n notifies the user about the incoming MCData group standalone FD request (including file metadata if present) which may be either accepted or rejected or ignored. MCData user may not be sought consent if the request includes mandatory download indication in the MCData group standalone FD request and instead only notify the MCData user about file downloading. +4. If the target MCData user on MCData clients 2 to n provides a response (accept or reject) to the notification, then the respective MCData client sends the MCData group standalone FD response to the MCData client 1. MCData client 2 to n automatically sends accepted MCData group standalone FD response when the incoming request included mandatory download indication. +5. MCData client 1 and MCData client 2 to n have successfully established media plane for file transmission and the MCData client 1 transmits the file data. +6. The MCData client 2 to n successfully receiving the file, records file download completed and notifies MCData users. +7. MCData client 2 to n initiate a MCData download completed report for reporting file download completed, if requested by the user at MCData client 1. + +## 7.6 Transmission and reception control + +### 7.6.1 General + +Based on the configurations (available in MCData user profile, group configuration and service configuration), the MCData transmission and reception control provides a necessary capability for an authorized user of the MCData + +service to transmit, receive notification messages due to various trigger conditions, advocates reception mode and terminate transmission when there is no longer a need to transmit. The subclauses below describe the transmission and reception control procedures using signalling control plane. + +### 7.6.2 Transmission and reception control for on-network + +#### 7.6.2.1 Information flows for transmission and reception control + +##### 7.6.2.1.1 MCData control indication + +Table 7.6.2.1.1-1 describes the information flow for the MCData control indication sent from the MCData server to the MCData client. + +**Table 7.6.2.1.1-1: MCData control indication** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the control indication is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Control indication type | M | One of the following:
- No permission to transmit data
- No affiliated members found to the selected MCData group
- Rejected due to exceeding data transmit size
- Rejected due to exceeding data transmit time
- Request to transmit is queued | + +##### 7.6.2.1.2 MCData indication + +Table 7.6.2.1.2-1 describes the information flow for the MCData indication sent from the MCData server to the MCData client. + +**Table 7.6.2.1.2-1: MCData indication** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the MCData indication is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Deferred data list | M | List of references to deferred data awaiting download | + +##### 7.6.2.1.3 MCData get deferred list request + +Table 7.6.2.1.3-1 describes the information flow for the MCData get deferred list request sent from the MCData client to the MCData server. + +**Table 7.6.2.1.3-1: MCData get deferred list request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting deferred list | + +##### 7.6.2.1.4 MCData get deferred list response + +Table 7.6.2.1.4-1 describes the information flow for the MCData get deferred list response sent from the MCData server to the MCData client. + +**Table 7.6.2.1.4-1: MCData get deferred list response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting deferred list | +| Deferred data list | M | List of references to deferred data awaiting download | + +#### 7.6.2.2 Automatic transmission for SDS + +##### 7.6.2.2.1 General + +When SDS message is sent, the data is transferred from the sending MCData client to the receiving MCData client without any request/grant procedure or any explicit actions on the part of the receiving MCData client. + +##### 7.6.2.2.2 Procedure + +The procedure in figure 7.6.2.2.2-1 describes the case where MCData SDS is automatically transmitted to the selected recipient user or affiliated members of the selected MCData group. + +Pre-conditions: + +1. MCData user is configured with permission to transmit data. +2. Optionally, MCData client may have an activated functional alias to be used. +3. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for Automatic transmission for SDS. The diagram shows three participants: MCData client 1, MCData server, and MCData client 2. The sequence of messages is: 1. initiate data transmit (from client 1 to server), 2. MCData transmission to MCData server (from client 1 to server), 3. Authorize request and size check for auto-send (internal server message), 4. MCData control indication (dashed line from server to client 1), and 5. MCData delivery to recipient(s) (from server to client 2).](2119293733c74fc64de88aefd597f4bb_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data transmit + MCData client 1->>MCData server: 2. MCData transmission to MCData server + Note right of MCData server: 3. Authorize request and size check for auto-send + MCData server-->>MCData client 1: 4. MCData control indication + Note right of MCData server: 5. MCData delivery to recipient(s) + MCData server->>MCData client 2: + +``` + +Sequence diagram for Automatic transmission for SDS. The diagram shows three participants: MCData client 1, MCData server, and MCData client 2. The sequence of messages is: 1. initiate data transmit (from client 1 to server), 2. MCData transmission to MCData server (from client 1 to server), 3. Authorize request and size check for auto-send (internal server message), 4. MCData control indication (dashed line from server to client 1), and 5. MCData delivery to recipient(s) (from server to client 2). + +**Figure 7.6.2.2.2-1: Automatic transmission for SDS** + +1. MCData user selects the data to transmit and the recipient MCData user or MCData group. The MCData user at MCData client 1 may include a functional alias used within the SDS data transmission. +2. MCData client checks for MCData user's permission to transmit data and checks if the data size is less than the maximum data size for SDS. MCData client calculates the total transmission request size and determines to select one of the appropriate procedures described in subclause 7.4.2.2, 7.4.2.3, 7.4.2.5 or 7.4.2.6. +3. Transmission control on the MCData server verifies if the MCData user is authorized to transmit and the data size in the received transmission request does not exceed the maximum data size for SDS. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the MCData user. +4. MCData server may send one of the following MCData control indications: + - a) If the MCData user does not have permission to transmit data to another MCData user or MCData group then the "No permission to transmit data" control indication is sent. + +- b) If the selected transmission is for a MCData group and there are no affiliated group members, then the transmission control on MCData server sends the "No affiliated members found to the selected MCData group" control indication. +- c) MCData server may queue the data transmit request for later transmission with control indication "Request to transmit is queued". + +Otherwise continue with step 5. + +5. MCData server automatically transmits the data and, if available, the functional alias of the originating MCData client 1 to the selected MCData user or the affiliated members or all group members (in the case of lossless communication) of the selected MCData group according to the procedures selected in step 2. + +#### 7.6.2.3 Send data with mandatory download + +##### 7.6.2.3.1 General + +The mandatory download procedure allows a sending MCData client to send data to a receiving MCData client, where the receiving MCData client is compelled to download the data. + +##### 7.6.2.3.2 Procedure + +The procedure in figure 7.6.2.3.2-1 describes the case where MCData user is using FD. The FD is subjected to transmission control prior to transmitting data to the selected recipient user or affiliated members of the selected MCData group for mandatory download. + +Pre-conditions: + +1. MCData user is configured with permission to transmit data. +2. MCData administrator has configured maximum data size for FD. +3. Maximum amount of data that a MCData user can transmit in a single request is configured. +4. Maximum amount of time that a MCData user can transmit in a single request is configured. +5. Optionally, MCData client may have an activated functional alias to be used. +6. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram for 'Send data with mandatory download' showing interactions between MCData client 1, MCData server, and MCData client 2.](6a555cff11e140861ce08db72b01a6a2_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data transmit + MCData client 1->>MCData server: 2. MCData transmission to MCData server + Note right of MCData server: 3. Authorize request and size check for non automatic transmission + MCData server-->>MCData client 1: 4. MCData control indication + Note right of MCData server: 5. Mandatory download transmission to recipient(s) + MCData server->>MCData client 2: + +``` + +Sequence diagram for 'Send data with mandatory download' showing interactions between MCData client 1, MCData server, and MCData client 2. + +**Figure 7.6.2.3.2-1: Send data with mandatory download** + +1. MCData user selects the data to transmit, the recipient MCData user or MCData group and the indication for mandatory download. The MCData user at MCData client 1 may include a functional alias used within the FD data transfer. +2. MCData client has checked for MCData user's permission to transmit data. MCData client calculates the total transmission request size and determines to select one of the appropriate procedures described in subclause 7.5.2.4, 7.5.2.5, 7.5.2.6 or 7.4.2.7 and including the mandatory download indication. + +3. Transmission control on the MCData server verifies if the MCData user is authorized to transmit, the data size in the received transmission request is within the maximum size allowed for FD transmission and is within the maximum amount of time that a MCData user can transmit in a single request. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the MCData user. + 4. MCData server may send one of the following MCData control indications: + - a) If the MCData user does not have permission to transmit data to another MCData user or MCData group then the "No permission to transmit data" control indication is sent. + - b) If the data size requested to be transmitted is more than the maximum amount of data that an MCData user can transmit in a single request, the transmission control on MCData server rejects the data transmission request and sends the rejection control indication "Rejected due to exceeding data transmit size". + - c) If the data transmission time exceeds the maximum amount of time that an MCData user can transmit in a single request, the transmission control on MCData server rejects the data transmission request and sends the rejection control indication "Rejected due to exceeding data transmit time". + - d) If the selected transmission is for a MCData group and there are no affiliated group members, then the transmission control on MCData server sends the "No affiliated members found to the selected MCData group" control indication. + - e) MCData server may queue the data transmit request for later transmission with control indication "Request to transmit is queued". +- Otherwise continue with step 5. +5. MCData server transmits the data and, if available, the functional alias of the originating MCData client 1 to the selected MCData user or the affiliated members or all group members (in the case of lossless communication) of the selected MCData group according to the procedures selected in step 2 (where the recipient MCData client receives the data automatically). + +#### 7.6.2.4 Send data without mandatory download + +##### 7.6.2.4.1 General + +The send data without mandatory download procedure allows the receiving MCData client to accept download, defer download (i.e. no response) or refuse (e.g. by the user deleting the notification item) the data sent from the sending MCData client. + +##### 7.6.2.4.2 Procedure + +The procedure in figure 7.6.2.4.2-1 describes the case where MCData user selected data is subjected to transmission control prior to transmitting data to the selected recipient user or affiliated members of the selected MCData group for downloading with recipient MCData user consent. + +Pre-conditions: + +1. MCData user is configured with permission to transmit data. +2. Maximum amount of data or time that an MCData user can transmit in a single request is configured. +3. Time limit for the temporarily stored data waiting to be delivered to a receiving user is configured. +4. Optionally, MCData client may have an activated functional alias to be used. +5. The MCData server may have subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. + +![Sequence diagram illustrating the 'Send data without mandatory download' process. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. The steps are: 1. initiate data transmit (client 1 to server), 2. MCData transmission to MCData server (client 1 to server), 3. Authorize request and size check for non automatic transmission (server internal), 4. MCData control indication (server to client 1), 5. Transmission to recipient(s) for downloading after user consent (server to client 2), 6. MCData indication (server to client 2).](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. initiate data transmit + MCData client 1->>MCData server: 2. MCData transmission to MCData server + Note right of MCData server: 3. Authorize request and size check for non automatic transmission + MCData server-->>MCData client 1: 4. MCData control indication + Note right of MCData server: 5. Transmission to recipient(s) for downloading after user consent + MCData server-->>MCData client 2: 6. MCData indication + +``` + +Sequence diagram illustrating the 'Send data without mandatory download' process. The diagram shows interactions between MCData client 1, MCData server, and MCData client 2. The steps are: 1. initiate data transmit (client 1 to server), 2. MCData transmission to MCData server (client 1 to server), 3. Authorize request and size check for non automatic transmission (server internal), 4. MCData control indication (server to client 1), 5. Transmission to recipient(s) for downloading after user consent (server to client 2), 6. MCData indication (server to client 2). + +**Figure 7.6.2.4.2-1: Send data without mandatory download** + +1. MCData user selects the data to transmit and the recipient MCData user or MCData group and does not select the mandatory download indication. The MCData user at MCData client 1 may include a functional alias used within the data transmission. + 2. MCData client has checked for MCData user's permission to transmit data and the data size is within the maximum data size allowed. The MCData client calculates the total transmission request size and determines to select procedure described in subclause 7.5.2.4 or 7.5.2.6 and without including the mandatory download indication. + 3. Transmission control on the MCData server verifies if the MCData user is authorized to transmit, the data size in the received transmission request is within the maximum data size allowed and is within the maximum amount of time that a MCData user can transmit in a single request. MCData server verifies whether the provided functional alias, if present, can be used and has been activated for the MCData user. + 4. MCData server may send one of the following control indications: + - a) If the MCData user does not have permission to transmit data to another MCData user or MCData group then the "No permission to transmit data" control indication is sent. + - b) If the selected transmission is for a MCData group and there are no affiliated group members, then the transmission control on MCData server sends the "No affiliated members found to the selected MCData group" control indication. + - c) If the data size requested to be transmitted is more than the maximum amount of data that an MCData user can transmit in a single request, the transmission control on MCData server rejects the data transmission requests and sends the rejection control indication "Rejected due to exceeding data transmit size". + - d) If the data transmission time exceeds the maximum amount of time that an MCData user can transmit in a single request (applies to DS only), the transmission control on MCData server rejects the data transmission request and sends the rejection control indication "Rejected due to exceeding data transmit time". + - e) MCData server may queue the data transmit request for later transmission with a control indication "Request to transmit is queued". +- Otherwise, continue with step 5. +5. MCData server transmits the data and, if available, the functional alias of the originating MCData client 1 to the selected MCData user or the affiliated members or all group members (in the case of lossless communication) of the selected MCData group according to the procedures selected in step 2 (where the recipient MCData client may receive the data automatically). + 6. The MCData server may store the data in temporary storage (e.g. if the recipient is not available at the time of data delivery or network congestion or data deferred by the user) and may send MCData indication to notify the recipient of available data for retrieval: + +- a) If the timer expired for periodic announcement with the list of available recently invited data communications, the recipient MCData client waiting to receive the temporarily stored data receives MCData indication with the list of available temporarily stored data waiting to download in the Deferred data list . +- b) If the temporarily stored data is expired, the data may be purged from the temporary store and the recipient MCData user may be informed in MCData indication with "Data expired and not available to download anymore" in the Deferred data list. + +#### 7.6.2.5 Accessing list of deferred data group communications + +##### 7.6.2.5.1 General + +This procedure allows an MCData client to obtain a list of deferred data communications. + +**Editor's note:** Due to the introduction of new MCData content server for HTTP FD in R16, this procedure is FFS. + +##### 7.6.2.5.2 Procedure + +The procedure in figure 7.6.2.5.2-1 describes the case where the recipient MCData client receives the list of available temporarily stored data waiting to download for the deferred data group communications. + +Pre-conditions: + +1. MCData server has temporarily stored data for the deferred data group communications e.g. due to recipient MCData client deferred to download. + +![Sequence diagram showing the interaction between an MCData client and an MCData server to access the list of deferred data group communications.](6929132b4964d52244da61d4614bc4d6_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + Note left of MCData client 1: 1. Get the list of deferred data group communications + MCData client 1->>MCData server: 2. MCData get deferred list request + MCData server-->>MCData client 1: 3. MCData get deferred list response + Note left of MCData client 1: 4. Notify + +``` + +Sequence diagram showing the interaction between an MCData client and an MCData server to access the list of deferred data group communications. + +**Figure 7.6.2.5.2-1: Accessing list of deferred data group communications** + +1. MCData user initiates the request to get the list of temporarily stored data for the deferred data group communications on the MCData server e.g. due to recipient MCData client deferred to download. +2. MCData client sends a MCData get deferred list request to the MCData server. +3. MCData server generates the list of temporarily stored data for the affiliated group(s), available to download for the requesting MCData client and sends the list in the MCData get deferred list response. +4. MCData client notifies the list of temporarily stored data for the deferred data group communications, upon which the MCData user may decide to retrieve the corresponding data. + +## 7.7 Communication release + +### 7.7.1 General + +The subclauses below describe the MCData communication release procedures, which may be initiated either by the sender or the MCData server or the authorized MCData user. + +### 7.7.2 Communication release for on-network + +#### 7.7.2.1 Information flows for communication release + +##### 7.7.2.1.1 MCData communication release request (one-to-one communication using media plane) + +Table 7.7.2.1.1-1 describes the information flow for the MCData communication release request (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.7.2.1.1-1: MCData communication release request (one-to-one communication using media plane)** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------| +| MCData ID | M | The identity of the MCData user uploading data | +| MCData ID | M | MCData ID on which the communication is to be released | + +##### 7.7.2.1.2 MCData communication release response (one-to-one communication using media plane) + +Table 7.7.2.1.2-1 describes the information flow for the MCData communication release response (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.7.2.1.2-1: MCData communication release response (one-to-one communication using media plane)** + +| Information element | Status | Description | +|----------------------|--------|-----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to upload data | +| MCData ID | M | MCData ID on which the communication is released | +| Release confirmation | M | Communication released or not indication | + +##### 7.7.2.1.3 MCData communication release request (group communication using media plane) + +Table 7.7.2.1.3-1 describes the information flow for the MCData communication release request (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.7.2.1.3-1: MCData communication release request (group communication using media plane)** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user uploading data | +| MCData group ID | M | MCData group ID on which the communication is to be released | + +##### 7.7.2.1.4 MCData communication release response (group communication using media plane) + +Table 7.7.2.1.4-1 describes the information flow for the MCData communication release response (in subclause 7.7.2.2.2.2) sent from the MCData client to the MCData server and from the MCData server to another MCData client. + +**Table 7.7.2.1.4-1: MCData communication release response (group communication using media plane)** + +| Information element | Status | Description | +|----------------------|--------|-----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user requesting to upload data | +| MCData group ID | M | MCData group ID on which the communication is released | +| Release confirmation | M | Communication released or not indication | + +##### 7.7.2.1.5 + +Void + +##### 7.7.2.1.6 + +Void + +##### 7.7.2.1.7 + +Void + +##### 7.7.2.1.8 MCData server communication release request (one-to-one communication using media plane) + +Table 7.7.2.1.8-1 describes the information flow for MCData server communication release request (in subclause 7.7.2.3.2.2) sent from the MCData server to the MCData clients involved in one-to-one communication. + +**Table 7.7.2.1.8-1: MCData server communication release request (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user to which communication is released | +| Conversation Identifier | M | Identifies the conversation | +| Release Reason | M | Indicates reason for the release | + +##### 7.7.2.1.9 MCData server communication release response (one-to-one communication using media plane) + +Table 7.7.2.1.9-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.3.2.2) sent from the MCData client to the MCData server. + +**Table 7.7.2.1.9-1: MCData server communication release response (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------| +| MCData ID | M | MCData ID to which the communication is released | +| Conversation Identifier | M | Identifies the conversation | +| Release confirmation | M | Communication released or not indication | + +##### 7.7.2.1.10 MCData server communication release request (group communication using media plane) + +Table 7.7.2.1.10-1 describes the information flow for MCData server communication release request (in subclause 7.7.2.3.2.2) sent from the MCData server to the MCData clients involved in group communication. + +**Table 7.7.2.1.10-1: MCData server communication release request (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user to which communication is released | +| MCData group ID | M | MCData group ID on which the communication is released | +| Conversation Identifier | M | Identifies the conversation | +| Release Reason | M | Indicates reason for the release | + +##### 7.7.2.1.11 MCData server communication release response (group communication using media plane) + +Table 7.7.2.1.11-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.3.2.2) sent from the MCData client to the MCData server. + +**Table 7.7.2.1.11-1: MCData server communication release response (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------------| +| MCData ID | M | MCData ID to which the communication is released | +| MCData group ID | M | MCData group ID on which the communication is released | +| Conversation Identifier | M | Identifies the conversation | +| Release confirmation | M | Communication released or not indication | + +##### 7.7.2.1.12 + +Void + +##### 7.7.2.1.13 MCData release intent request (one-to-one communication using media plane) + +Table 7.7.2.1.13-1 describes the information flow for MCData release intent request (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData server to the MCData client. + +**Table 7.7.2.1.13-1: MCData release intent request (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user who is originator of the one-to-one communication | +| Conversation Identifier | M | Identifies the conversation | +| Request for more info | O | Indicates what MCData server needs more information (e.g. to know the remaining data volume to transmit) about the communication which has been identified to be released | + +##### 7.7.2.1.14 MCData more information response (one-to-one communication using media plane) + +Table 7.7.2.1.14-1 describes the information flow for MCData more information response (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData client to the MCData server and from MCData server to authorized MCData user. + +**Table 7.7.2.1.14-1: MCData more information response (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user who is originator of the one-to-one communication | +| Conversation Identifier | M | Identifies the conversation | +| More info | M | Information as requested by MCData server | + +##### 7.7.2.1.15 MCDATA release intent request (group communication using media plane) + +Table 7.7.2.1.15-1 describes the information flow for MCDATA release intent request (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCDATA server to the MCDATA client. + +**Table 7.7.2.1.15-1: MCDATA release intent request (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user who is the originator of the group communication | +| Conversation Identifier | M | Identifies the conversation | +| MCDATA group ID | M | MCDATA group ID on which the communication is released | +| Request for more info | O | Indicates what MCDATA server needs more information about the communication which has been identified to be released | + +##### 7.7.2.1.16 MCDATA more information response (group communication using media plane) + +Table 7.7.2.1.16-1 describes the information flow for MCDATA more information response (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCDATA client to the MCDATA server and from MCDATA server to authorized MCDATA user. + +**Table 7.7.2.1.16-1: MCDATA more information response (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------------------| +| MCDATA ID | M | The identity of the MCDATA user who is originator of the group communication | +| Conversation Identifier | M | Identifies the conversation | +| MCDATA group ID | M | MCDATA group ID on which the communication is released | +| More info | M | Information as requested by MCDATA server | + +##### 7.7.2.1.17 MCDATA auth user communication release request (one-to-one communication using media plane) + +Table 7.7.2.1.17-1 describes the information flow for MCDATA auth user communication release request (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the authorized MCDATA user to the MCDATA server. + +**Table 7.7.2.1.17-1: MCDATA auth user communication release request (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| Request for more info | O | Indicates what MCDATA server needs more information about the communication which has been identified to be released | +| Release Reason | M | Indicates reason for the release | + +##### 7.7.2.1.18 MCDATA auth user communication release response (one-to-one communication using media plane) + +Table 7.7.2.1.18-1 describes the information flow for the MCDATA server communication release response (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the MCDATA server to the authorized MCDATA user. + +**Table 7.7.2.1.18-1: MCDATA auth user communication release response (one-to-one communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| Release confirmation | M | Communication released or not indication | + +##### 7.7.2.1.19 MCData auth user communication release request (group communication using media plane) + +Table 7.7.2.1.19-1 describes the information flow for MCData auth user communication release request (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the authorized MCData user to the MCData server. + +**Table 7.7.2.1.19-1: MCData auth user communication release request (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| MCData group ID | M | MCData group ID on which the communication is to be released | +| Request for more info | O | Indicates what MCData server needs more information about the communication which has been identified to be released | +| Release Reason | M | Indicates reason for the release | + +##### 7.7.2.1.20 MCData auth user communication release response (group communication using media plane) + +Table 7.7.2.1.20-1 describes the information flow for the MCData server communication release response (in subclause 7.7.2.5.2, 7.7.2.6.2) sent from the MCData server to the authorized MCData user. + +**Table 7.7.2.1.20-1: MCData auth user communication release response (group communication using media plane)** + +| Information element | Status | Description | +|-------------------------|--------|--------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| MCData group ID | M | MCData group ID on which the communication is to be released | +| Release confirmation | M | Communication released or not indication | + +##### 7.7.2.1.21 MCData request for extension + +Table 7.7.2.1.21-1 describes the information flow for the MCData request for extension (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the MCData client to the MCData server and from MCData server to authorized MCData user. + +**Table 7.7.2.1.21-1: MCData request for extension** + +| Information element | Status | Description | +|-------------------------|--------|-----------------------------| +| Conversation Identifier | M | Identifies the conversation | + +##### 7.7.2.1.22 MCData response for extension + +Table 7.7.2.1.22-1 describes the information flow for the MCData response for extension (in subclause 7.7.2.4.2, 7.7.2.6.2) sent from the authorized MCData user to the MCData server and MCData client to the MCData server and from MCData server to MCData client. + +**Table 7.7.2.1.22-1: MCData response for extension** + +| Information element | Status | Description | +|-------------------------|--------|------------------------------------------------------------------| +| Conversation Identifier | M | Identifies the conversation | +| Extension response | M | Indicates whether request for extension has been accepted or not | + +#### 7.7.2.2 MCData user initiated communication release + +##### 7.7.2.2.1 General + +During MCData communication, a transmitting participant can at any time indicate to stop transmission to the MCData server. + +##### 7.7.2.2.2 Release of MCData communication using media plane + +###### 7.7.2.2.2.1 General + +The subclause describes the procedure for MCData user initiated MCData communication release where MCData communication is established as SDS using media plane or SDS session or file distribution using media plane. + +**Editor's note: Release of MCData communication over MBMS is FFS.** + +###### 7.7.2.2.2.2 Procedure + +The procedure in figure 7.7.2.2.2.2-1 describes signalling control plane procedure for the case where MCData communication is ongoing and transmitting participant initiates MCData communication release. The procedure is applicable for one-to-one and group MCData communications. + +Pre-conditions: + +- 1. MCData users on MCData client 1 and client 2 are already registered for receiving MCData service. +- 2. MCData communication is established between MCData client 1 and MCData client 2 and MCData client1 is the initiator of the MCData communication. + +![Sequence diagram showing the release of MCData communication using media plane between MCData client 1, MCData server, and MCData client 2.](f324fbc5d5af1e4da9cd932389f0064c_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. Initiate communication termination + MCData client 1->>MCData server: 2. MCData communication release request + MCData server->>MCData client 2: 3. MCData communication release request + Note right of MCData client 2: 4. Notify user + MCData client 2->>MCData server: 5. MCData communication release response + MCData server->>MCData client 1: 6. MCData communication release response + Note over MCData client 1, MCData server, MCData client 2: 7. Release media plane resources associated with MCData communication + Note left of MCData client 1: 8. Notify user + +``` + +Sequence diagram showing the release of MCData communication using media plane between MCData client 1, MCData server, and MCData client 2. + +**Figure 7.7.2.2.2.2-1: Release of MCData communication using media plane** + +- 1. MCData user at MCData client 1 requests to release ongoing MCData communication. +- 2. MCData client 1 sends MCData communication release request towards MCData server, for tearing down the communication with the other MCData client(s). +- 3. MCData server sends MCData communication release request to all the participants of the MCData communication. +- 4. Recipient MCData clients notifies respective MCData user about the release of MCData communication. +- 5. MCData clients receiving the MCData communication release request provide communication release response back towards MCData server. +- 6. MCData server sends MCData communication release response back to MCData client 1. +- 7. All participants of the MCData communication have successfully released the media plane resources associated with the MCData communication that is released. + +8. MCData client 1 notifies the MCData user about the communication release. + +##### 7.7.2.2.3 Release of MCData communication using HTTP + +NOTE: The backward compatibility handling of this procedure is outside the scope of the present document. + +#### 7.7.2.3 MCData server initiated communication release without prior indication + +##### 7.7.2.3.1 General + +MCData server initiates the release of an ongoing MCData communication, since at least one of the communication release conditions are met e.g. lack of bearer capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on the configuration, MCData server either pre-empts the MCData communication without giving prior indication to MCData client or notifies the intent of release to the MCData client initiating communication. Latter scenario allows the MCData user to request for extension of MCData communication and defer the communication release. + +##### 7.7.2.3.2 Release of MCData communication using media plane + +###### 7.7.2.3.2.1 General + +The subclause describes the procedure for MCData server initiated MCData communication release without prior indication, where MCData communication is established as SDS using media plane or file distribution using media plane. + +**Editor's note: Release of MCData communication over MBMS is FFS.** + +###### 7.7.2.3.2.2 Procedure + +The procedure in figure 7.7.2.3.2.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, based on communication release conditions, MCData server initiates the communication release. The procedure is applicable for one-to-one and group communication. + +Pre-conditions: + +1. MCData users on MCData client 1, client 2 and client 3 are already registered for receiving MCData service. +2. A MCData administrator has configured the limits for the maximum amount of data and time that a participant transmits from a single request to transmit. +3. A MCData communication is ongoing between MCData client 1, client 2 and client 3. + +![Sequence diagram illustrating the MCDData server initiated release of MCDData communication using media plane. The diagram shows interactions between MCData client 1, MCData server, MCData client 2, and MCData client 3. The process involves the server sending release requests to all clients, clients notifying users, clients sending responses to the server, and finally the server releasing media plane resources.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client 3 + + Note right of MCData server: 1. Release MCData communication + Note right of MCData server: 2. Determine MCData communication participants and generate communication release request + MCData server->>MCData client 1: 3a. MCData server communication release request + MCData server->>MCData client 2: 3b. MCData server communication release request + MCData server->>MCData client 3: 3c. MCData server communication release request + MCData client 1->>MCData client 1: 4a. Notify user + MCData client 2->>MCData client 2: 4b. Notify user + MCData client 3->>MCData client 3: 4c. Notify user + MCData client 1->>MCData server: 5a. MCData server communication release response + MCData client 2->>MCData server: 5b. MCData server communication release response + MCData client 3->>MCData server: 5c. MCData server communication release response + Note over all participants: 6. Release media plane resources associated with the MCData communication + +``` + +Sequence diagram illustrating the MCDData server initiated release of MCDData communication using media plane. The diagram shows interactions between MCData client 1, MCData server, MCData client 2, and MCData client 3. The process involves the server sending release requests to all clients, clients notifying users, clients sending responses to the server, and finally the server releasing media plane resources. + +**Figure 7.7.2.3.2.2-1: MCData server initiated release of MCData communication using media plane** + +1. MCData server would like to release the ongoing MCData communication, identified by conversation identifier, since at least one of the release conditions are met e.g. lack of capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on configuration, MCData server decides to pre-empt the MCData communication without giving prior indication to MCData client 1. +2. MCData server identifies the participants of the ongoing MCData communication and generates communication release request to release ongoing MCData communication. +3. MCData server sends server MCData communication release request towards each participant of the MCData communication. +4. MCData users are notified about the release of the MCData communication. +5. MCData client at each MCData communication participant sends server MCData communication release response towards the MCData server. +6. All participants of the MCData communication have successfully released the media plane resources associated with the MCData communication that is released. + +##### 7.7.2.3.3 Release of MCData communication using HTTP + +**NOTE:** The backward compatibility handling of this procedure is outside the scope of the present document. + +#### 7.7.2.4 MCDATA server initiated communication release with prior indication + +##### 7.7.2.4.1 General + +The subclause describes the procedure for MCDATA server initiated MCDATA communication release with prior indication, where MCDATA communication is established as SDS using media plane or file distribution using media plane or file distribution using HTTP. + +##### 7.7.2.4.2 Procedure + +The procedure in figure 7.7.2.4.2-1 describes signalling control plane procedure for the case where during an ongoing MCDATA communication, based on communication release conditions, MCDATA server initiates communication release. As a result of configuration check, MCDATA server notifies the intent to release MCDATA communication, optionally requesting for more information (e.g. to know the remaining data volume to transmit) from the MCDATA client initiating MCDATA communication. + +Pre-conditions: + +1. MCDATA user on MCDATA client 1 is already registered for receiving MCDATA service. +2. MCDATA administrator has configured the limits for the maximum amount of data and time that a participant transmits from a single request to transmit. +3. MCDATA communication may be ongoing between MCDATA participants and MCDATA client 1 is the initiator of the communication. +4. MCDATA administrator has configured the time for which MCDATA server needs to wait for extension request from the MCDATA user. + +![Sequence diagram showing the procedure for MCDATA server initiated communication release with prior indication. The diagram involves two main participants: MCDATA client 1 and MCDATA server. The sequence of messages is: 1. Release MCDATA communication (from server to client), 2. MCDATA release intent request (from server to client), 3. Notify user (internal action on client), 4. MCDATA more information response (dashed arrow from client to server), 5. Request for extension (internal action on client), 6. MCDATA request for extension (from client to server), 7. Policy assertion (internal action on server), 8. MCDATA response for extension (from server to client).](3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg) + +``` + +sequenceDiagram + participant Client as MCDATA client 1 + participant Server as MCDATA server + Note right of Server: 1. Release MCDATA communication + Server->>Client: 2. MCDATA release intent request + Note left of Client: 3. Notify user + Client-->>Server: 4. MCDATA more information response + Note left of Client: 5. Request for extension + Client->>Server: 6. MCDATA request for extension + Note right of Server: 7. Policy assertion + Server->>Client: 8. MCDATA response for extension + +``` + +Sequence diagram showing the procedure for MCDATA server initiated communication release with prior indication. The diagram involves two main participants: MCDATA client 1 and MCDATA server. The sequence of messages is: 1. Release MCDATA communication (from server to client), 2. MCDATA release intent request (from server to client), 3. Notify user (internal action on client), 4. MCDATA more information response (dashed arrow from client to server), 5. Request for extension (internal action on client), 6. MCDATA request for extension (from client to server), 7. Policy assertion (internal action on server), 8. MCDATA response for extension (from server to client). + +Figure 7.7.2.4.2-1: MCDATA server initiates communication release with prior indication + +1. MCDATA server releases the ongoing MCDATA communication, identified by the conversation identifier, since at least one of the release conditions are met e.g. lack of capacity, limit for the maximum amount of data or time that a participant transmits from a single request to transmit exceeded. Based on the configuration, MCDATA server notifies the intent to release MCDATA communication. +2. MCDATA server sends the MCDATA release intent request towards the communication initiating MCDATA client 1. MCDATA server may include request for more information (e.g. to know the remaining data volume to transmit). +3. MCDATA client 1 informs MCDATA user about the intent to release communication. + +4. If request for more information is included in the received MCData release intent request, MCData client 1 sends MCData more information response including the remaining amount of data to transmit. Upon receiving more information response from MCData client 1, MCData server may wait for the request for extension until the time configured by the MCData administrator. If MCData server does not receive MCData request for extension within the configured timeout, the MCData server releases MCData communication as described in subclause 7.7.2.3. Otherwise, continue with remaining steps. +5. MCData user at MCData client 1 requests for extension of the ongoing MCData communication. +6. MCData client 1 sends MCData request for extension of the MCData communication. +7. Upon receiving the MCData request for extension of MCData communication from the MCData client 1, MCData server asserts policies to accept or reject the request for extension. +8. MCData server sends MCData response for extension with success or failure result to MCData client 1. MCData communication will continue if MCData server accepted the request for extension from MCData client 1. Otherwise, MCData communication is released according to procedures described in subclause 7.7.2.3. + +#### 7.7.2.5 Authorized MCData user initiated communication release without prior indication + +##### 7.7.2.5.1 General + +An authorized MCData user at any time during an ongoing MCData communication decides to release communication. The authorized user may decide to release MCData communication without prior indication to the initiator MCData client. + +##### 7.7.2.5.2 Procedure + +The procedure in figure 7.7.2.5.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, authorized MCData user initiates MCData communication release without prior indication to the initiator MCData client. An authorized MCData user is part of the ongoing MCData communication. + +Pre-conditions: + +1. An authorized MCData user on MCData client is already registered for receiving MCData service. +2. A MCData communication is ongoing between MCData participants and authorized MCData user is keeping track of which participants are receiving communication e.g. through "message delivered" and/or "message read" indications for the MCData communication. + +![Sequence diagram illustrating the procedure for an authorized MCData user to initiate communication release without prior indication. The diagram shows three lifelines: Authorized MCData client, MCData Server, and MCData client. The sequence of messages is: 1. Release MCData communication (internal to Authorized MCData client), 2. MCData auth user communication release request (from Authorized MCData client to MCData Server), 3. Validate request (internal to MCData Server), 4. Release communication (internal to MCData Server), 5. MCData auth user communication release response (from MCData Server to Authorized MCData client).](e38206fcefa2045af01d494b2956775a_img.jpg) + +``` + +sequenceDiagram + participant AMC as Authorized MCData client + participant MS as MCData Server + participant MC as MCData client + Note left of AMC: 1. Release MCData communication + AMC->>MS: 2. MCData auth user communication release request + Note right of MS: 3. Validate request + Note right of MS: 4. Release communication + MS->>AMC: 5. MCData auth user communication release response + +``` + +Sequence diagram illustrating the procedure for an authorized MCData user to initiate communication release without prior indication. The diagram shows three lifelines: Authorized MCData client, MCData Server, and MCData client. The sequence of messages is: 1. Release MCData communication (internal to Authorized MCData client), 2. MCData auth user communication release request (from Authorized MCData client to MCData Server), 3. Validate request (internal to MCData Server), 4. Release communication (internal to MCData Server), 5. MCData auth user communication release response (from MCData Server to Authorized MCData client). + +**Figure 7.7.2.5.2-1: An authorized MCData user initiates communication release without prior indication** + +1. An authorized MCData user requests to release the ongoing MCData communication, without providing prior indication to the initiator of the MCData communication, MCData client 1. + +2. An authorized MCData client sends MCData auth user communication release request towards MCData server identifying the MCData communication to release. The request also includes indication to the MCData server to release MCData communication without prior indication to the initiator of the MCData communication, MCData client 1. +3. MCData server validates the user from whom the MCData communication release request is received and checks whether the requesting MCData user is authorized to release communication or not. +4. If the user is authorized to release communication, then MCData server releases the ongoing MCData communication according to procedures described in subclause 7.7.2.3. +5. MCData server sends MCData auth user communication release response containing the result of MCData communication release back to authorized MCData client 1. + +#### 7.7.2.6 Authorized MCData user initiated communication release with prior indication + +##### 7.7.2.6.1 General + +An authorized MCData user at any time during an ongoing MCData communication decides to release communication. The authorized user may decide to release MCData communication with prior indication to the initiator MCData client. A prior indication allows initiator MCData client to request for extension for the MCData communication. + +##### 7.7.2.6.2 Procedure + +The procedure in figure 7.7.2.6.2-1 describes signalling control plane procedure for the case where during an ongoing MCData communication, authorized MCData user initiates MCData communication release with prior indication to the initiator MCData client. An authorized MCData user is part of the ongoing MCData communication. An initiator MCData user optionally decides to request for the extension of the ongoing communication. + +Pre-conditions: + +1. An authorized MCData user on MCData client is already registered for receiving MCData service. +2. A MCData communication is ongoing between MCData participants and authorized MCData user is keeping track of which participants are receiving communication e.g. through "message delivered" and/or "message read" indications for the MCData communication +3. MCData client 1 is the initiator of the MCData communication. + +![Sequence diagram showing the interaction between MCData client 1, MCData server, and Authorized MCData Client for a communication release process.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant Authorized MCData Client + + Note right of Authorized MCData Client: 1. Release MCData communication + Authorized MCData Client->>MCData server: 2. MCData auth user communication release request + Note right of MCData server: 3. Validate request + MCData server->>MCData client 1: 4. McData release intent request + Note right of MCData client 1: 5. Notify user + MCData client 1-->>MCData server: 6. MCData more information response + MCData server-->>Authorized MCData Client: 7. MCData more information response + Note right of MCData client 1: 8. Request for extension + MCData client 1->>MCData server: 9. MCData request for extension + MCData server->>Authorized MCData Client: 10. MCData request for extension + Note right of Authorized MCData Client: 11. Notify user + MCData server-->>MCData client 1: 13. MCData response for extension request + MCData server-->>Authorized MCData Client: 12. MCData response for extension request + Note right of MCData client 1: 14. Release communication + MCData server->>Authorized MCData Client: 15. MCData auth user communication release response + +``` + +Sequence diagram showing the interaction between MCData client 1, MCData server, and Authorized MCData Client for a communication release process. + +**Figure 7.7.2.6.2-1: An authorized MCData user initiates communication release with prior indication** + +1. An authorized MCData user requests to release the ongoing MCData communication by providing prior indication to the initiator of MCData communication, MCData client 1. + 2. An authorized MCData client sends MCData auth user communication release request towards MCData server including the communication identifier identifying the MCData communication to release. Authorized MCData client may include request for more information (e.g. to know the remaining data volume to transmit). The request also includes indication to MCData server to release MCData communication with prior indication to the initiator MCData client. + 3. MCData server validates the user from whom the communication release request is received and checks whether the requesting user is authorized to release communication or not. + 4. If the user is authorized to release communication, then the MCData server sends MCData release intent request, may be including the reason for the release. MCData server may include request for more information as received in the request from the authorized MCData client. + 5. MCData client informs MCData user about the intent to release communication by the authorized MCData user. + 6. If request for more information is included in the received MCData release intent request, MCData client 1 sends MCData more information response including the remaining amount of data to transmit. + 7. MCData server forwards the MCData more information response to the authorized MCData client. +- NOTE: Upon receiving more information response from MCData client 1, MCData server may wait for the request for extension until the time configured by the MCData administrator. If MCData server does not receive request for extension within the configured timeout, the MCData server releases MCData communication as described in subclause 7.7.2.3. Otherwise, continue with remaining steps. +8. MCData user at MCData client 1 decides to request for extension of the ongoing MCData communication. + +- 9 and 10. MCData client sends MCData request for extension towards MCData server. And MCData server forwards the MCData request for extension towards the authorized MCData client. +11. Authorized MCData client notifies the authorized user about the incoming request for extension. An authorized MCData user decides to accept or reject the request for extension. +- 12 and 13. Authorized MCData user decision is sent in MCData response for extension request towards the MCData server. MCData server forwards the MCData response for extension request to MCData client 1. +14. MCData communication will continue if the authorized user accepted the request for extension from MCData client 1. Otherwise, MCData communication will be released according to procedures described in subclause 7.7.2.3. +15. After MCData communication is released, MCData server sends the MCData auth user communication release response back to the authorized MCData client. + +## 7.8 Conversation management + +### 7.8.1 General + +Conversation management is a collection of related MCData transmissions for a given activity. Conversation management associates SDS and FD communication transmission and present them as a single thread to the user. + +### 7.8.2 Conversation management for on-network + +#### 7.8.2.1 Information flows for conversation management + +The information flow parameters related to conversation management are as described in the subclauses 7.4.2.1 and subclauses 7.5.2.1.5, 7.5.2.1.6, 7.5.2.1.7, 7.5.2.1.8, 7.5.2.1.9, 7.5.2.1.10, 7.5.2.1.11, 7.5.2.1.12, and 7.5.2.1.13. + +#### 7.8.2.2 One-to-one conversation management + +##### 7.8.2.2.1 Procedure + +The procedure for an MCData user to associate multiple MCData transmissions between a pair of users for a given activity is illustrated in figure 7.8.2.2.1-1. + +Pre-conditions: + +1. MCData user(s) on MCData client 1 and 2 are registered for receiving MCData service. + +![Sequence diagram illustrating the one-to-one conversation management procedure. The diagram shows three participants: MCData client 1, MCData server, and MCData client 2. The sequence of steps is: 1. Initiate conversation (from MCData client 1 to MCData server), and 2. Procedure(s) of one-to-one SDS or one-to-one FD or combination of both (between MCData client 1 and MCData client 2).](fb5442ad7130829bed9e3682ccb84c87_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + Note left of MCData client 1: 1. Initiate conversation + MCData client 1->>MCData server: + Note right of MCData client 2: 2. Procedure(s) of one-to-one SDS or one-to-one FD or combination of both + MCData client 1->>MCData client 2: + +``` + +Sequence diagram illustrating the one-to-one conversation management procedure. The diagram shows three participants: MCData client 1, MCData server, and MCData client 2. The sequence of steps is: 1. Initiate conversation (from MCData client 1 to MCData server), and 2. Procedure(s) of one-to-one SDS or one-to-one FD or combination of both (between MCData client 1 and MCData client 2). + +**Figure 7.8.2.2.1-1: One-to-one conversation management** + +1. The user at MCData client 1 initiates conversation. A universally unique conversation identifier is generated to identify new conversation. Conversation identifier is used in procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier is used in procedures mentioned in step 2. To allow multiple parallel conversations for the same pair of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation. + +2. The procedure of one-to-one SDS or one-to-one FD or combination of both these procedures can be executed. + +#### 7.8.2.3 Group conversation management + +##### 7.8.2.3.1 Procedure + +The procedure for an MCData user to associate multiple MCData transmissions between users of a group for a given activity is illustrated in figure 7.8.2.3.1-1. + +Pre-conditions: + +1. MCData user(s) on MCData client 1, 2, and n are registered for receiving MCData service. +2. The MCData users 1, 2 and n are members of the same MCData group and affiliated to the MCData service. + +![Sequence diagram for Group conversation management. Lifelines: MCData client 1, MCData server, MCData client 2, MCData client n. Step 1: MCData client 1 initiates conversation. Step 2: Procedure(s) of Group SDS or Group FD or combination of both.](e94cbc0895c6914a2bb53f150ab7495e_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client n + Note left of MCData client 1: 1. Initiate conversation + Note over MCData client 1, MCData server, MCData client 2, MCData client n: 2. Procedure(s) of Group SDS or Group FD or combination of both + +``` + +Sequence diagram for Group conversation management. Lifelines: MCData client 1, MCData server, MCData client 2, MCData client n. Step 1: MCData client 1 initiates conversation. Step 2: Procedure(s) of Group SDS or Group FD or combination of both. + +**Figure 7.8.2.3.1-1: Group conversation management** + +1. The user at MCData client 1 initiates conversation. A unique conversation identifier is generated to identify new conversation. Conversation identifier is used in procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier is used in procedures mentioned in step 2. To allow multiple parallel conversations for the same group of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation. +2. The procedure of group SDS or group FD or combination of both these procedures can be executed. + +### 7.8.3 Conversation management for off-network + +#### 7.8.3.1 One-to-one conversation management + +##### 7.8.3.1.1 Procedure + +The procedure for an MCData user to associate multiple off-network MCData transmissions between a pair of users is illustrated in figure 7.8.3.1.1-1. + +Pre-conditions: + +1. MCData client 1 and MCData client 2 are members of the same ProSe Discovery group and are ProSe 1:1 direct communication capable. +2. MCData client 1 has discovered MCData client 2 in proximity, associated with MCData user B, using ProSe Discovery procedures. + +![Sequence diagram for one-to-one conversation management between MCData client 1 and MCData client 2.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + Note left of MCData client 1: 1. Initiate conversation + Note right of MCData client 2: 2. Procedure(s) of one-to-one SDS or one-to-one FD or both +``` + +The diagram illustrates a sequence of interactions between two MCData clients. MCData client 1 initiates the conversation, and both clients then execute procedure(s) related to one-to-one SDS or one-to-one FD or both. + +Sequence diagram for one-to-one conversation management between MCData client 1 and MCData client 2. + +**Figure 7.8.3.1.1-1: One-to-one conversation management** + +1. The user at MCData client 1 initiates conversation. A universally unique conversation identifier is generated to identify the new conversation. Conversation identifier is used in the procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier from the existing conversation is used in the procedures mentioned in step 2. To allow multiple parallel conversations for the same pair of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation. +2. The procedure of one-to-one SDS or one-to-one FD or a combination of these can be executed. + +#### 7.8.3.2 Group conversation management + +##### 7.8.3.2.1 Procedure + +The procedure for an MCData user to associate multiple off-network MCData transmissions between users of a group is illustrated in figure 7.8.3.2.1-1. + +Pre-conditions: + +1. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCData client 1. +2. MCData client 1 to MCData client N are members of the same MCData group. + +![Sequence diagram for group conversation management between MCData client 1, MCData client 2, and MCData client n.](4c9ba399ca7df11cbe9b6322cd9aee0a_img.jpg) + +``` +sequenceDiagram + participant MCData client 1 + participant MCData client 2 + participant MCData client n + Note left of MCData client 1: 1. Initiate conversation + Note right of MCData client n: 2. Procedure(s) of Group SDS or Group FD or both +``` + +The diagram illustrates a sequence of interactions between multiple MCData clients (1, 2, and n). MCData client 1 initiates the conversation, and all clients then execute procedure(s) related to group SDS or group FD or both. + +Sequence diagram for group conversation management between MCData client 1, MCData client 2, and MCData client n. + +**Figure 7.8.3.2.1-1: Group conversation management** + +1. The user at MCData client 1 initiates conversation. A universally unique conversation identifier is generated to identify the new conversation. Conversation identifier is used in the procedures mentioned in step 2. If the intent of the user at MCData client 1 is to transmit within an existing conversation, then corresponding conversation identifier from the existing conversation is used in the procedures mentioned in step 2. To allow multiple parallel conversations for the same group of users, different conversation identifier is used for each conversation. The MCData users can view the MCData conversation at any time after the first MCData transaction is initiated within the conversation. +2. The procedure of group SDS or group FD or combination of both can be executed. + +## 7.9 Enhanced status + +### 7.9.1 General + +Enhanced status corresponds to information specific to the activities performed by the mission critical service users during their operation(s) e.g. available, in operation on site, going to the operation site, or just arrived. + +### 7.9.2 Preset values for enhanced status + +The enhanced status information i.e. the set of possible values corresponding to the activities of the MCData user, shall be configured by the MCData administrator. The configuration of status values is applicable on a per-group basis, and therefore shall be part of the MCData group configuration data as described in Annex A.4. + +The configuration mechanism shall allow the MCData administrator to configure a minimum of 32 possible values and allow up to 65536 separate values. The set of values may be divided into a fixed set of values defined by 3GPP standards which are common across all MCData systems, and a set which may be freely configured for any purpose. + +### 7.9.3 Enhanced status for on-network + +#### 7.9.3.1 Sharing enhanced status information + +##### 7.9.3.1.1 Procedure + +The procedure for an MCData user to share the enhanced status information to the members of the selected group is illustrated in figure 7.9.3.1.1-1. + +Pre-conditions: + +- 1. MCData user(s) on MCData client 1, 2, and n are registered for receiving MCData service. +- 2. The MCData users 1, 2 and n are members of the same MCData group and affiliated to the MCData service. +- 3. The MCData group is pre-configured with the possible values for enhanced status information. + +![Sequence diagram showing the procedure for sharing enhanced status information between MCData clients and a server.](71a22f206329906db6e3860c7ff8c796_img.jpg) + +``` + +sequenceDiagram + participant MCData client 1 + participant MCData server + participant MCData client 2 + participant MCData client n + + Note left of MCData client 1: 1. Select enhanced status information + MCData client 1->>MCData server: + Note over MCData server: 2. Procedure of group standalone SDS using signalling control plane + MCData server->>MCData client 2: + Note right of MCData client 2: 3. Notify enhanced status information + MCData server->>MCData client n: + Note right of MCData client n: 3. Notify enhanced status information + +``` + +The diagram illustrates a sequence of interactions for sharing enhanced status information. At the top, four boxes represent the participants: MCData client 1, MCData server, MCData client 2, and MCData client n. A vertical line descends from each participant. + +1. From MCData client 1, a horizontal box labeled '1. Select enhanced status information' is shown. A vertical line continues down from this box. + +2. A long horizontal box labeled '2. Procedure of group standalone SDS using signalling control plane' spans across the vertical lines of all participants. The vertical line from MCData client 1 enters this box. + +3. From the bottom of the '2.' box, vertical lines lead to two separate horizontal boxes, both labeled '3. Notify enhanced status information'. One is positioned under MCData client 2 and the other under MCData client n. Vertical lines continue down from these boxes. + +Sequence diagram showing the procedure for sharing enhanced status information between MCData clients and a server. + +Figure 7.9.3.1.1-1: Sharing enhanced status information + +- 1. The user at MCData client 1 selects the MCData group to share the enhanced status information. The user also selects the value of the status information to be shared from the list of pre-configured status values available for the MCData group. + +2. The procedure of group standalone SDS using signalling control plane as described in subclause 7.4.2.5, is used to deliver the enhanced status information. +3. The MCData users at MCData client 2 and n are notified of the enhanced status information. + +### 7.9.4 Enhanced status for off-network + +#### 7.9.4.1 Sharing enhanced status information + +##### 7.9.4.1.1 Procedure + +The procedure for an MCData user to share the enhanced status information to the members of the selected group is illustrated in figure 7.9.4.1.1-1. + +Pre-conditions: + +1. Information for ProSe direct communications corresponding to the MCData group and its mapping to ProSe Layer-2 Group ID are pre-configured in MCData client 1. +2. MCData client 1, 2 and n are members of the same MCData group. +3. The MCData group is pre-configured with the possible values for enhanced status information. + +![Sequence diagram showing the procedure for sharing enhanced status information between MCData clients 1, 2, and n. Step 1: MCData client 1 selects enhanced status information. Step 2: Procedure of off-network group standalone SDS using signalling control plane. Step 3: MCData client 2 and n are notified of the enhanced status information.](8d8c758885b4f754ff071bf3b572ab3c_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCData client 1 + participant C2 as MCData client 2 + participant Cn as MCData client n + Note over C1: 1. Select enhanced status information + rect rgb(255, 255, 255) + Note over C1, Cn: 2. Procedure of off-network group standalone SDS using signalling control plane + end + Note over C2: 3. Notify enhanced status information + Note over Cn: 3. Notify enhanced status information + +``` + +Sequence diagram showing the procedure for sharing enhanced status information between MCData clients 1, 2, and n. Step 1: MCData client 1 selects enhanced status information. Step 2: Procedure of off-network group standalone SDS using signalling control plane. Step 3: MCData client 2 and n are notified of the enhanced status information. + +**Figure 7.9.4.1.1-1: Sharing enhanced status information** + +1. The user at MCData client 1 selects the MCData group to share the enhanced status information. The user also selects the value of the status information to be shared from the list of pre-configured status values available for the MCData group. +2. The procedure of off-network group standalone SDS using signalling control plane as described in subclause 7.4.3.4, is used to deliver the enhanced status information. +3. The MCData users at MCData client 2 and n are notified of the enhanced status information. + +## 7.10 MCData emergency alert (on-network and off-network) + +The MCData service shall support the procedures and related information flows as specified in subclause 10.10 of 3GPP TS 23.280 [5] with the following clarifications: + +- The MC service client is the MCData client; +- The MC service server is the MCData server; + +- The MC service group ID is the MCData Group ID; and +- The MC service user profile index is the MCData user profile index. + +## 7.11 User authentication and authorization for MCData service + +NOTE: Flow 7.11-1 is a high level user authentication and authorization flow. 3GPP TS 33.180 [13] defines the specific user authentication and authorization architecture required by the MCData service in order to realize the MCData user authentication and authorization requirements as defined in 3GPP TS 22.280 [2]. + +A procedure for user authentication is illustrated in figure 7.11-1. The user authentication is performed based on the procedure specified in subclause 10.6 of 3GPP TS 23.280 [5]. + +![Sequence diagram for MCData user authentication and registration, single domain. The diagram shows six lifelines: MCData client, Identity management client, Signalling user agent, SIP core, Identity management server, and MCData server. Step 1, 'User Authentication is based on the procedure – “General user authentication and authorization for MC services” specified in 3GPP TS 23.280[5]', involves interactions between the Identity management client, Signalling user agent, SIP core, and Identity management server. Step 2, 'The MCData client performs the service authorization with the MCData server', involves an interaction between the MCData client and the MCData server.](ff5f89b660edddb67971d7d3d4ce87ef_img.jpg) + +Sequence diagram for MCData user authentication and registration, single domain. The diagram shows six lifelines: MCData client, Identity management client, Signalling user agent, SIP core, Identity management server, and MCData server. Step 1, 'User Authentication is based on the procedure – “General user authentication and authorization for MC services” specified in 3GPP TS 23.280[5]', involves interactions between the Identity management client, Signalling user agent, SIP core, and Identity management server. Step 2, 'The MCData client performs the service authorization with the MCData server', involves an interaction between the MCData client and the MCData server. + +**Figure 7.11-1: MCData user authentication and registration, single domain** + +1. The user authentication is performed as per the general user authentication procedure specified in subclause 10.6 of 3GPP TS 23.280 [5]. +2. MCData client performs the MCData service authorization for the user. Step 2 utilizes the results of step 1. + +## 7.12 MCData resource management (on-network) + +### 7.12.1 General + +Procedures for resource management are defined in subclause 10.x of 3GPP TS 23.280 [5]. + +### 7.12.2 MCData services not handled by SIP core + +MCData services that do not utilize the SIP core e.g. IP connectivity, cannot utilize the resource control functionality of the local outbound / inbound proxy. For these types of service, resource management is handled directly by the Rx interface from the MCData server to the PCRF, which is the MCData-5 reference point. The Rx interface is defined in 3GPP TS 29.214 [17]. + +The same types of resource management procedures as defined for SIP based services in 3GPP TS 23.280 [5] may also be applied for non SIP based services. That is: + +- Request for unicast resources at session establishment (in this case service initiation); +- Request for modification of unicast resources; and +- Request for resources with shared priority. + +## 7.13 Operations on MCData message store + +The MCData message store allows an MCData user to deposit his MCData communication information (i.e. messages or files) securely and permanently for later retrieval. During an active MCData communication, a message or a file with its associated metadata is deposited as an object in the MCData message store with an object identifier; this object identifier enabling a direct access to that object. The objects in the MCData message store are managed from both the MCData server and the message store client. + +Each MCData user is allocated a dedicated and secured storage area (i.e. with a user account) in the MCData message store. All MCData communications of a MCData user can be stored in his dedicated storage area. The access to this secured storage area is possible only after successful authentication and authorization procedures. A message store client can create a local copy of the stored objects into the device by synchronizing with the MCData message store for the MCData user using the device. + +### 7.13.1 MCData message store structure + +MCData message store supports a tree like architecture to securely store MCData communications for the MCData users. Figure 7.13.1 below illustrates the high-level structure of a MCData message store: + +![Diagram illustrating the Message store structure. At the top is a rectangular box labeled 'MCData message store (Common Root)'. Below it, a horizontal line branches out to three ovals labeled 'MCData User 1', 'MCData User 2', and 'MCData User n', with an ellipsis between User 2 and User n. From each user oval, a vertical line descends to a stack of three document icons, each labeled 'objects'.](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +``` + +graph TD + Root["MCData message store (Common Root)"] --> User1(["MCData User 1"]) + Root --> User2(["MCData User 2"]) + Root --> Dots1[...] + Root --> Usern(["MCData User n"]) + User1 --> Obj1["objects"] + User2 --> Obj2["objects"] + Usern --> Objn["objects"] + +``` + +Diagram illustrating the Message store structure. At the top is a rectangular box labeled 'MCData message store (Common Root)'. Below it, a horizontal line branches out to three ovals labeled 'MCData User 1', 'MCData User 2', and 'MCData User n', with an ellipsis between User 2 and User n. From each user oval, a vertical line descends to a stack of three document icons, each labeled 'objects'. + +**Figure 7.13.1 Message store structure** + +As illustrated in Figure 7.13.1 all MCData user storage areas are accessed only through the common root. The authorized MCData user shall only have the access to the MCData user's storage area after the successful authentication and authorization procedures. A MCData user shall not be able to access objects stored for other MCData users. + +The MCData user shall manage his stored objects using message store client through the MCData-7 reference point. The MCData server shall use the MCData-8 reference point to deposit MCData communication information, during an active MCData communication, into the designated MCData user's storage area in the MCData message store. + +One way to manage user stored objects is using folder hierarchy structure like the popular email system today. Annex X provides a simple example of how it will look like in deployment. When the user account is created in the MCData message store, a default folder (such as Inbox) is also created to capture all the objects during an active communication. To group relevant stored objects together and provide easier navigation interactively, a MCData user can create folders in his user account. Each folder is identified by its unique folder identifier that is composed with the location of the folder and the name of the folder. A folder may have child folders to further group the stored objects in more meaningful ways. For example, the folder identifier of the default Inbox folder is /MCData message store /MCData user1/Inbox. The folder identifier /MCData message store /MCData user1/Squad1/20190225 points to a folder named 20190225 which is a child folder of Squad1 folder in the MCData user1 user account. + +**NOTE:** The details of how the objects are stored in the MCData message store is out of scope of the present document. + +### 7.13.2 Authentication and authorization + +The MCData message store shall authenticate the credential of MCData server or the authorized MCData user before authorizing access to the MCData user's storage area. The success of authentication and authorization shall allow access to that MCData user's storage area only. + +NOTE: The authentication and authorization aspects of MCData message store access and its operational supports are the responsibility of SA3 and thus outside the scope of the present document. + +### 7.13.3 Manage MCData message store + +#### 7.13.3.1 Information flows for managing MCData message store + +##### 7.13.3.1.1 MCData retrieve a stored object request + +Table 7.13.3.1.1-1 describes the information flow for the MCData retrieve a stored object request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.1-1: MCData retrieve a stored object request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object identifier | M | The object identifier of the object stored in the MCData message store | + +##### 7.13.3.1.2 MCData retrieve a stored object response + +Table 7.13.3.1.2-1 describes the information flow for the MCData retrieve a stored object response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.2-1: MCData retrieve a stored object response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Stored object | M | The stored object identified by the object identifier in the request. This information element shall be returned as empty when there is no stored object can be identified by the object identifier in the request | + +##### 7.13.3.1.3 MCData search stored objects request + +Table 7.13.3.1.3-1 describes the information flow for the MCData search stored objects request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.3-1: MCData search stored objects request** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Search criteria | M | Any part of the stored object can be the search criteria. Linking multiple parts of a stored object as the search criteria is possible | + +##### 7.13.3.1.4 MCData search stored objects response + +Table 7.13.3.1.4-1 describes the information flow for the MCData search stored objects response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.4-1: MCData search stored objects response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Stored object(s) | M | The stored object(s) that meets the search criteria. This information element shall be returned as empty when there is no stored object can be identified by the search criteria in the request | + +##### 7.13.3.1.5 MCData update a stored object request + +Table 7.13.3.1.5-1 describes the information flow for the MCData update a stored object request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.5-1: MCData update a stored object request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object identifier | M | The object identifier of the object stored in the MCData message store | +| Metadata | M | The metadata that will be updated | + +##### 7.13.3.1.6 MCData update a stored object response + +Table 7.13.3.1.6-1 describes the information flow for the MCData update a stored object response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.6-1: MCData update a stored object response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user storage area in the MCData message store | +| Result | M | The result if the update is success or failure | + +##### 7.13.3.1.7 MCData delete a stored object request + +Table 7.13.3.1.7-1 describes the information flow for the MCData delete a stored object request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.7-1: MCData delete a stored object request** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object identifier | M | The object identifier of the object stored in the MCData message store | + +##### 7.13.3.1.8 MCData delete a stored object response + +Table 7.13.3.1.8-1 describes the information flow for the MCData delete a stored object response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.8-1: MCData delete a stored object response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user storage area in the MCData message store | +| Result | M | The result if the delete is success or failure | + +##### 7.13.3.1.9 MCData synchronization request + +Table 7.13.3.1.9-1 describes the information flow for the MCData synchronization request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.9-1: MCData synchronization request** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Synchronization type | M | Indicates the type of synchronization is requested. It can be a full or partial synchronization | +| Filter criteria (see NOTE) | O | The filter criteria indicate what knid of stored objects needs to be synchronized to the device local message store | +| NOTE: Filter criteria information element shall be presented if the Synchronization type is partial. | | | + +##### 7.13.3.1.10 MCData synchronization response + +Table 7.13.3.1.10-1 describes the information flow for the MCData synchronization response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.10-1: MCData synchronization response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Stored objects | M | The stored objects that need to be synchronized with the device local message store. Empty information element means no stored objects need to be synchronized | + +##### 7.13.3.1.11 MCData create a user account request + +Table 7.13.3.1.11-1 describes the information flow for the MCData create a user account request sent from the MCData server to the MCData message store. + +**Table 7.13.3.1.11-1: MCData create a user account request** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------| +| MCData ID | M | The identity of the MCData user | + +##### 7.13.3.1.12 MCData create a user account response + +Table 7.13.3.1.12-1 describes the information flow for the MCData create a user account response sent from the MCData message store to the MCData server. + +**Table 7.13.3.1.12-1: MCData create a user account response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the account creation is success or failure | + +##### 7.13.3.1.13 MCData deposit an object request + +Table 7.13.3.1.13-1 describes the information flow for the MCData deposit an object request sent from the MCData server to the MCData message store. + +**Table 7.13.3.1.13-1: MCData deposit an object request** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object | M | The object needs to be stored | + +##### 7.13.3.1.14 MCData deposit an object response + +Table 7.13.3.1.14-1 describes the information flow for the MCData deposit an object response sent from the MCData message store to the MCData server. + +**Table 7.13.3.1.14-1: MCData deposit an object response** + +| Information element | Status | Description | +|---------------------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object Identifier | M | The object identifier that will be used to retrieve this object in the MCData message store directly. If this information element is empty it means the object is not stored | + +##### 7.13.3.1.15 MCData copy a stored object request + +Table 7.13.3.1.15-1 describes the information flow for the MCData copy a stored object request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.15-1: MCData copy a stored object request** + +| Information element | Status | Description | +|-------------------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object identifier | M | The object identifier of the object stored in the MCData message store | +| Destination folder identifier | M | Indicates where the object will be copied to | + +##### 7.13.3.1.16 MCData copy a stored object response + +Table 7.13.3.1.16-1 describes the information flow for the MCData copy a stored object response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.16-1: MCData copy a stored object response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the operation is success or failure | + +##### 7.13.3.1.17 MCData move a stored object request + +Table 7.13.3.1.17-1 describes the information flow for the MCData move a stored object request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.17-1: MCData move a stored object request** + +| Information element | Status | Description | +|-------------------------------|--------|------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object identifier | M | The object identifier of the object stored in the MCData message store | +| Destination folder identifier | M | Indicates where the object will be moved to. | + +##### 7.13.3.1.18 MCData move a stored object response + +Table 7.13.3.1.18-1 describes the information flow for the MCData move a stored object response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.18-1: MCData move a stored object response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the operation is success or failure | + +##### 7.13.3.1.19 MCData create folder request + +Table 7.13.3.1.19-1 describes the information flow for the MCData create folder request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.19-1: MCData create folder request** + +| Information element | Status | Description | +|--------------------------|--------|----------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Parent folder identifier | O | The parent folder identifier of the created folder | +| Folder name | O | Indicates the name of the new folder | + +##### 7.13.3.1.20 MCData create folder response + +Table 7.13.3.1.20-1 describes the information flow for the MCData create folder response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.20-1: MCData create folder response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the operation is success or failure | +| Folder identifier | O | The identifier of the folder that is created | + +##### 7.13.3.1.21 MCData delete folder request + +Table 7.13.3.1.21-1 describes the information flow for the MCData delete folder request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.21-1: MCData delete folder request** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Folder identifier | M | The identifier of the folder to be deleted | + +##### 7.13.3.1.22 MCData delete folder response + +Table 7.13.3.1.22-1 describes the information flow for the MCData delete folder response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.22-1: MCData delete folder response** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the operation is success or failure | + +##### 7.13.3.1.23 MCData copy folder request + +Table 7.13.3.1.23-1 describes the information flow for the MCData copy folder request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.23-1: MCData copy folder request** + +| Information element | Status | Description | +|-------------------------------|--------|------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Source folder identifier | M | The identifier of the folder to copy from | +| Destination folder identifier | M | The identifier of the folder to copy to | +| New folder name (see NOTE) | O | Indicates the name of the new folder | +| NOTE: | | If no new folder name information element is provided, the new folder name will be the same as the source folder name. | + +##### 7.13.3.1.24 MCData copy folder response + +Table 7.13.3.1.24-1 describes the information flow for the MCData copy folder response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.24-1: MCData copy folder response** + +| Information element | Status | Description | +|-----------------------|--------|---------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the operation is success or failure | +| New folder identifier | M | Indicates the identifier of the new folder | + +##### 7.13.3.1.25 MCData move folder request + +Table 7.13.3.1.25-1 describes the information flow for the MCData move folder request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.25-1: MCData move folder request** + +| Information element | Status | Description | +|-------------------------------|--------|------------------------------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Source folder identifier | M | The identifier of the folder to be moved | +| Destination folder identifier | M | The identifier of the folder to move to | +| New folder name (see NOTE) | O | Indicates the name of the new folder | +| NOTE: | | If no new folder name information element is provided, the new folder name will be the same as the source folder name. | + +##### 7.13.3.1.26 MCData move folder response + +Table 7.13.3.1.26-1 describes the information flow for the MCData move folder response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.26-1: MCData move folder response** + +| Information element | Status | Description | +|-----------------------|--------|---------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result | M | The result if the operation is success or failure | +| New folder identifier | M | Indicates the identifier of the new folder | + +##### 7.13.3.1.27 MCData list folder request + +Table 7.13.3.1.27-1 describes the information flow for the MCData list folder request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.27-1: MCData list folder request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Folder identifier | O | The identifier of the folder to be listed | + +##### 7.13.3.1.28 MCData list folder response + +Table 7.13.3.1.28-1 describes the information flow for the MCData list folder response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.28-1: MCData list folder response** + +| Information element | Status | Description | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------| +| MCData ID | M | The identity of the MCData user | +| Result (see NOTE) | M | The result of the list operation | +| NOTE: | If no folder identifier information element is provided in the request, the MCData message store returns folders from the root of the user account. If folder identifier information element is provided in the request, the MCData message store returns the child folders from that folder identifier provided. | | + +##### 7.13.3.1.29 MCData upload objects request + +Table 7.13.3.1.29-1 describes the information flow for the MCData upload objects request sent from the message store client to the MCData message store. + +**Table 7.13.3.1.29-1: MCData upload objects request** + +| Information element | Status | Description | +|----------------------------|--------|--------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Targeted folder identifier | M | The folder where the uploaded objects will be stored | +| Uploaded objects | M | The objects in the client that need to be uploaded to the MCData message store | + +##### 7.13.3.1.30 MCData upload objects response + +Table 7.13.3.1.30-1 describes the information flow for the MCData upload objects response sent from the MCData message store to the message store client. + +**Table 7.13.3.1.30-1: MCData upload objects response** + +| Information element | Status | Description | +|----------------------|--------|------------------------------------------------------| +| MCData ID | M | The identity of the MCData user | +| Object upload result | M | Indicates if the objects upload is successful or not | + +##### 7.13.3.1.31 MCData synchronization notification + +Table 7.13.3.1.31-1 describes the information flow for the MCData synchronization notification sent from the MCData message store to the message store client. + +**Table 7.13.3.1.31-1: MCData synchronization notification** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user that the notification is for | + +#### 7.13.3.2 Retrieve a stored object + +##### 7.13.3.2.1 General + +A stored object can be retrieved from the MCData message store with the known object identifier that is generated by the MCData message store when the object was deposited. + +##### 7.13.3.2.2 Procedure + +The procedure in figure 7.13.3.2.2-1 describes the case when a message store client retrieves a stored object from the MCData message store using the known object identifier. + +Pre-conditions: + +1. A successful authentication and authorization have been performed between the message store client and the MCData message store. +2. The message store client knows the object identifier of the stored object. + +![Sequence diagram showing the interaction between a Message store client and an MCData message store for retrieving a stored object.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +``` + +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Client->>Store: 1. MCData retrieve a stored object request + Store-->>Client: 2. MCData retrieve a stored object response + +``` + +Sequence diagram showing the interaction between a Message store client and an MCData message store for retrieving a stored object. + +**Figure 7.13.3.2.2-1: Retrieve a stored object** + +1. The message store client would like to retrieve a stored object from the MCData message store and initiates a MCData retrieve a stored object request toward the MCData message store. The uniqe object identifier of the stored object is included in the request. +2. The MCData message store returns the stored object that is identified by the object identifier in the MCData retrieve a stored object response. + +#### 7.13.3.3 Search stored objects + +##### 7.13.3.3.1 General + +The message store client can search stored objects in the MCData message store with certain criteria. This procedure allows the message store client to look for stored object(s) without knowing the object identifier(s) of the object. This procedure also allows the message store client to retrieve stored objects that are related to each other; such as all messages and files exchanged in a conversation. + +##### 7.13.3.3.2 Procedure + +The procedure in figure 7.13.3.3.2-1 describes the case when a message store client searches and retrieves relevant stored objects from the MCData message store. + +Pre-conditions: + +1. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram showing the interaction between a Message store client and an MCData message store for searching stored objects.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note left of Client: Error! No + Note right of Store: Error! No text of specified style in + Client->>Store: 1. MCData search stored objects request + Store-->>Client: 2. MCData search stored objects response +``` + +The diagram is a sequence diagram with two lifelines: 'Message store client' on the left and 'MCData message store' on the right. The interaction consists of two steps: 1. A solid arrow labeled '1. MCData search stored objects request' points from the client to the store. 2. A dashed arrow labeled '2. MCData search stored objects response' points from the store back to the client. Above the lifelines, there are error messages: 'Error! No' on the left and 'Error! No text of specified style in' on the right. + +Sequence diagram showing the interaction between a Message store client and an MCData message store for searching stored objects. + +**Figure 7.13.3.3.2-1: Search stored objects** + +1. The message store client would like to retrieve stored objects that meet certain criteria (such as with the same Conversation identifier) and initiates a MCData search objects request toward the MCData message store. The search criteria are included in the request. +2. The MCData message store looks up all stored objects that meet the search criteria and returns them in the MCData search objects response. + +#### 7.13.3.4 Update a stored object + +##### 7.13.3.4.1 General + +The message store client can update the metadata of a stored object (such as mark a stored object as "flagged"). + +##### 7.13.3.4.2 Procedure + +The procedure in figure 7.13.3.4.2-1 describes the case when a message store client updates metadata of a stored object in the MCData message store. + +Pre-conditions: + +1. A successful authentication and authorization have been performed between the message store client and the MCData message store. +2. The message store client knows the object identifier of the stored object. + +![Sequence diagram for 'Update a stored object'](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note left of Client: Error! No text of specified style in + Note right of Store: Error! No text of specified style in + Client->>Store: 1. MCData update a stored object request + Store-->>Client: 2. MCData update a stored object response +``` + +The diagram is a sequence diagram illustrating the interaction between a 'Message store client' and an 'MCData message store' for updating a stored object. It consists of two lifelines. The 'Message store client' sends a synchronous message labeled '1. MCData update a stored object request' to the 'MCData message store'. The 'MCData message store' responds with a synchronous message labeled '2. MCData update a stored object response' back to the client. There are placeholder error messages at the top of each lifeline: 'Error! No text of specified style in'. + +Sequence diagram for 'Update a stored object' + +**Figure 7.13.3.4.2-1: Update a stored object** + +1. The message store client would like to update the metadata of a stored object (such as "flagged") and initiates a MCData update a stored object request toward the MCData message store. The stored object's object identifier and the updated meta data are included in the request. +2. The MCData message store locates the stored object with the object identifier and updates its metadata as carried in the MCData update a stored object request and communicates the result in the MCData update a stored object response. + +#### 7.13.3.5 Delete a stored object + +##### 7.13.3.5.1 General + +The message store client of an authorized user can delete a stored object in the MCData message store. + +##### 7.13.3.5.2 Procedure + +The procedure in figure 7.13.3.5.2-1 describes the case when a stored object in the MCData message store is deleted by the message store client of an authorized MCData user. + +Pre-conditions: + +1. A successful authentication and authorization have been performed between the message store client and the MCData message store. +2. The message store client knows the object identifier of the stored object. +3. The MCData user is authorized to delete the stored object. + +![Sequence diagram for deleting a stored object](7ed5d5770331f31ade15439a21c31425_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note left of Client: Error! No + Note right of Store: Error! No text of specified style in + Client->>Store: 1. MCData delete a stored object request + Store-->>Client: 2. MCData delete a stored object response +``` + +The diagram is a sequence diagram showing the interaction between a 'Message store client' and an 'MCData message store'. The client sends a '1. MCData delete a stored object request' to the store, and the store responds with a '2. MCData delete a stored object response'. There are placeholder error messages at the top of the lifelines. + +Sequence diagram for deleting a stored object + +**Figure 7.13.3.5.2-1: Delete a stored object** + +1. The message store client would like to delete a stored object in the MCData message store and initiates a MCData delete a stored object request toward the MCData message store. The stored object's object identifier is included in the request. +2. The MCData message store locates the stored object with the object identifier and permanently removes it from the MCData message store. It then communicates the result in the MCData delete a stored object response. + +#### 7.13.3.6 Synchronization + +##### 7.13.3.6.1 General + +The message store client can synchronize its local message store with the MCData message store. Different level of synchronization shall be supported with a filter in the request. + +##### 7.13.3.6.2 Procedure + +The procedure in figure 7.13.3.6.2-1 describes the case when a message store client synchronizes its local message store with the MCData message store for a MCData user. + +Pre-conditions: + +1. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram showing synchronization between a Message store client and an MCData message store.](3337af75dfee8af7687b4f49914d6c93_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Server as MCData message store + Note left of Client: Error! No + Note right of Server: Error! No text of specified style in + Client->>Server: 1. MCData synchronization request + Server-->>Client: 2. MCData synchronization response +``` + +The diagram is a sequence diagram with two lifelines: 'Message store client' on the left and 'MCData message store' on the right. The 'Message store client' sends a message labeled '1. MCData synchronization request' to the 'MCData message store'. The 'MCData message store' responds with a message labeled '2. MCData synchronization response' back to the 'Message store client'. There are placeholder error messages at the top of each lifeline: 'Error! No' for the client and 'Error! No text of specified style in' for the server. + +Sequence diagram showing synchronization between a Message store client and an MCData message store. + +**Figure 7.13.3.6.2-1: Synchronization** + +1. The message store client would like to synchronize its local message store with the MCData message store. It initiates the MCData synchronization request toward the MCData message store. The synchronization type and optional filter criteria are included in the request to indicate the type of synchronization (such as full synchronization, partial synchronization etc.) is requested. +2. The MCData message store returns all the stored objects, based on the synchronization filter criteria, to the message store client in the MCData synchronization response. + +#### 7.13.3.7 Create a user account + +##### 7.13.3.7.1 General + +When the MCData server is ready to deposit an object into the MCData user's storage area in the MCData message store the MCData user's storage area (i.e. user account) needs to be created already. If the user account is not created, the MCData server shall create the user account (i.e. allocate the MCData user's storage area in the MCData message store) first and then deposit the subsequent MCData communications. + +NOTE: Another possible way to create a user account on the MCData message store is through service provisioning which is out of the scope of the present document. + +##### 7.13.3.7.2 Procedure + +The procedure in figure 7.13.3.7.2-1 describes how the MCData server creates a user account (allocate MCData user storage area) in the MCData message store. + +Pre-conditions: + +1. A successful authentication and authorization hves been performed between the MCData server and the MCData message store. +2. No storage area in the MCData message store has been allocated for the MCData user; i.e. no user account has been created. +3. The MCData server is authorized to create user accounts on the MCData message store. + +![Sequence diagram for 'Create a user account' showing interaction between MCData server and MCData message store.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` +sequenceDiagram + participant MCData server + participant MCData message store + Note left of MCData server: Error! No + Note right of MCData message store: Error! No text of specified style in + MCData server->>MCData message store: 1. MCData create a user account request + MCData message store-->>MCData server: 2. MCData create a user account response +``` + +The diagram is a sequence diagram with two lifelines: 'MCData server' on the left and 'MCData message store' on the right. The interaction consists of two steps: 1. A solid arrow points from the MCData server to the MCData message store, labeled '1. MCData create a user account request'. 2. A return arrow points from the MCData message store back to the MCData server, labeled '2. MCData create a user account response'. There are also error messages at the top of each lifeline: 'Error! No' for the server and 'Error! No text of specified style in' for the message store. + +Sequence diagram for 'Create a user account' showing interaction between MCData server and MCData message store. + +**Figure 7.13.3.7.2-1: Create a user account** + +1. The MCData server would like to create a MCData user account in the MCData message store to store the MCData communication for that MCData user and initiates a MCData create a user account request toward the MCData message store. The MCData ID of the MCData user is included in the request. +2. The MCData message store creates a user account (i.e. allocate dedicated and secured storage area) for the MCData user as specified in the request and communicates the result back to the MCData server in the MCData create a user account response. + +#### 7.13.3.8 Deposit an object + +##### 7.13.3.8.1 General + +MCData server needs to store the communication information (i.e. an object) for a MCData user during an active MCData communication. + +##### 7.13.3.8.2 Procedure + +The procedure in figure 7.13.3.8.2-1 describes how the MCData server deposit an object into the MCData message store during an active MCData communication. + +Pre-conditions: + +1. A successful authentication and authorization has been performed between the MCData server and the MCData message store. +2. The MCData user has been allocated a secured storage area in the MCData message store. + +![Sequence diagram for depositing an object](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +``` +sequenceDiagram + participant MCData server + participant MCData message store + Note left of MCData server: Error! No + Note right of MCData message store: Error! No text of specified style in + MCData server->>MCData message store: 1. MCData deposit an object request + MCData message store-->>MCData server: 2. MCData deposit an object response +``` + +The diagram is a sequence diagram showing the interaction between an MCData server and an MCData message store. The MCData server sends a message labeled '1. MCData deposit an object request' to the MCData message store. The MCData message store responds with a message labeled '2. MCData deposit an object response' back to the MCData server. There are placeholder error messages at the top of the lifelines. + +Sequence diagram for depositing an object + +**Figure 7.13.3.8.2-1: Deposit an object** + +1. The MCData server would like to deposit a MCData communication information (i.e. object) to the MCData user's storage area in the MCData message store and initiates a MCData deposit an object request toward the MCData message store. The object is constructed by the MCData server and is included in the request. +2. The MCData message store deposits the object into the MCData user's storage area and communicates the result back to the MCData server in the MCData deposit an object response. The object identifier for the stored is returned in the MCData deposit an object response. + +#### 7.13.3.9 Copy a stored object + +##### 7.13.3.9.1 General + +A stored object in the MCData message store can be copied to another location (i.e. folder) in the same MCData user account where there is no such object stored. After the successful object copy operation, the object will exist in both the original and destination locations. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.9.2 Procedure + +The procedure in figure 7.13.3.9.2-1 describes the case when a stored object is copied to a different location in the same MCData user account. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. +3. The message store client knows the object identifier of the stored object and the destination folder identifier. + +![Sequence diagram for copying a stored object](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note right of Store: 2. copy the object to target location + Client->>Store: 1. MCData copy a stored object request + Store-->>Client: 3. MCData copy a stored object response +``` + +The diagram is a sequence diagram showing the interaction between a 'Message store client' and an 'MCData message store'. The client sends a '1. MCData copy a stored object request' to the store. The store then performs an internal action labeled '2. copy the object to target location'. Finally, the store sends a '3. MCData copy a stored object response' back to the client. + +Sequence diagram for copying a stored object + +**Figure 7.13.3.9.2-1: Copy a stored object** + +1. The message store client would like to copy a stored object in the MCData message store to a destination folder and initiates a MCData copy a stored object request toward the MCData message store. The unique identifier of the stored object and the destination folder are included in the request. +2. The MCData message store copies the object to the target location. +3. The MCData message store returns the result of the request in the MCData copy a stored object response. + +#### 7.13.3.10 Move a stored object + +##### 7.13.3.10.1 General + +A stored object in the MCData message store can be moved to a different location (i.e. folder) in the same MCData user account. After the successful object move operation the object will only exist in the new location. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.10.2 Procedure + +The procedure in figure 7.13.3.10.2-1 describes the case when a stored object is moved to a different location in the same MCData user account. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. +3. The message store client knows the object identifier of the stored object and the destination folder identifier. + +![Sequence diagram for 'Move a stored object' operation between a Message store client and an MCData message store.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note right of Store: 2. move the object to target location + Client->>Store: 1. MCData move a stored object request + Store-->>Client: 3. MCData move a stored object response +``` + +The diagram is a sequence diagram illustrating the interaction for moving a stored object. It features two lifelines: 'Message store client' on the left and 'MCData message store' on the right. The sequence of messages is as follows: 1. A request labeled 'MCData move a stored object request' is sent from the client to the store. 2. A self-message on the store lifeline is labeled 'move the object to target location'. 3. A response labeled 'MCData move a stored object response' is sent from the store back to the client. + +Sequence diagram for 'Move a stored object' operation between a Message store client and an MCData message store. + +**Figure 7.13.3.10.2-1: Move a stored object** + +1. The message store client would like to move a stored object in the MCData message store to a destination folder and initiates a MCData move a stored object request toward the MCData message store. The unique object identifier of the stored object and the destination folder are included in the request. +2. The MCData message store moves the object to the target location. +3. The MCData message store returns the result of the request in the MCData move a stored object response. + +#### 7.13.3.11 Folder create operation + +##### 7.13.3.11.1 General + +A user can create a new folder in his user account in the MCData message store. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.11.2 Procedure + +The procedure in figure 7.13.3.11.2-1 describes the case when a MCData user creates a new folder in the MCData message store. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram for 'Create a new user folder' showing interactions between Message store client and MCData message store.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note right of Store: Error! No text of specified style in + Client->>Store: 1. MCData create folder request + Store->>Store: 2. Create new folder + Store-->>Client: 3. MCData create folder response +``` + +The diagram is a sequence diagram illustrating the interaction for creating a new user folder. It features two lifelines: 'Message store client' on the left and 'MCData message store' on the right. The sequence of messages is: 1. A solid arrow labeled '1. MCData create folder request' points from the client to the store. 2. A self-call arrow labeled '2. Create new folder' is shown on the store's lifeline, enclosed in a rectangular box. 3. A return arrow labeled '3. MCData create folder response' points from the store back to the client. There is a placeholder note on the right side of the diagram. + +Sequence diagram for 'Create a new user folder' showing interactions between Message store client and MCData message store. + +**Figure 7.13.3.11.2-1: Create a new user folder** + +1. The MCData user would like to create a new folder in his user account in the MCData message store, the message store client initiates a MCData create folder request toward the MCData message store. The parent folder identifier and the folder name are included in the request to indicate where the new folder will be created. +2. The MCData message store creates the user folder in the location specified in the request. If the folder name is provided in the request, the MCData message store creates the folder with the provided folder name. If the provided folder name has a conflict or no folder name is provided in the request, the MCData message store assigns a name for the new user folder. +3. The MCData message store returns the result in the MCData create folder response. The identifier of the new folder is returned in the response. + +#### 7.13.3.12 Folder delete operation + +##### 7.13.3.12.1 General + +A user can delete an existing folder in his user account in the MCData message store. All the child folders and objects stored in that folder will be deleted. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.12.2 Procedure + +The procedure in figure 7.13.3.12.2-1 describes the case when a MCData user deletes an existing folder in the MCData message store. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram for deleting a user folder. Lifelines: Message store client and MCData message store. The client sends a '1. MCData delete folder request' to the store. The store performs '2. Delete the identified folder and all its objects'. The store returns '3. MCData delete folder response' to the client.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note right of Store: Error! No text of specified style in + Note left of Client: Error! No + Client->>Store: 1. MCData delete folder request + Note right of Store: 2. Delete the identified folder and all its objects + Store-->>Client: 3. MCData delete folder response +``` + +Sequence diagram for deleting a user folder. Lifelines: Message store client and MCData message store. The client sends a '1. MCData delete folder request' to the store. The store performs '2. Delete the identified folder and all its objects'. The store returns '3. MCData delete folder response' to the client. + +**Figure 7.13.3.12.2-1: Delete a user folder** + +1. The MCData user would like to delete an existing folder in his user account in the MCData message store, the message store client initiates a MCData delete folder request toward the MCData message store. The folder identifier of the folder to be deleted is included in the request. +2. The MCData message store identifies the target folder and deletes it from the user account. All the child folders and objects stored in this folder are also deleted. +3. The MCData message store returns the result in the MCData delete folder response. + +#### 7.13.3.13 Folder copy operation + +##### 7.13.3.13.1 General + +A user can copy an existing folder in his user account to a different location. All the child folders and objects stored in that folder will be copied to the new folder. The name of the new folder will be the same as the folder it copies from or the name provided in the request. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.13.2 Procedure + +The procedure in figure 7.13.3.13.2-1 describes the case when a MCData user copies an existing folder in the MCData message store. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram for copying a user folder. Lifelines: Message store client and MCData message store. The process involves: 1. MCData copy folder request from client to store; 2. Copy the source folder to the destination (internal to store); 3. MCData copy folder response from store to client.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note right of Store: 2. Copy the source folder to the destination + Client->>Store: 1. MCData copy folder request + Store-->>Client: 3. MCData copy folder response +``` + +Sequence diagram for copying a user folder. Lifelines: Message store client and MCData message store. The process involves: 1. MCData copy folder request from client to store; 2. Copy the source folder to the destination (internal to store); 3. MCData copy folder response from store to client. + +**Figure 7.13.3.13.2-1: Copy a user folder** + +1. The MCData user would like to copy an existing folder in his user account in the MCData message store, the message store client initiates a MCData copy folder request toward the MCData message store. The folder identifiers of the source and destination folders and the new folder name are included in the request. +2. The MCData message store copy the source folder to the destination with the new folder name. If no new folder name is provided in the request, the source folder name will be used. All the child folders and objects stored in this folder are also copied to the new folder. +3. The MCData message store returns the result in the MCData copy folder response. The identifier of the new folder is returned in the response. + +#### 7.13.3.14 Folder move operation + +##### 7.13.3.14.1 General + +A user can move an existing folder in his user account to a different location. All the child folders and objects stored in that folder will be moved to the new folder. The name of the new folder will be the same as the folder it moves from or the name provided in the request. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.14.2 Procedure + +The procedure in figure 7.13.3.14.2-1 describes the case when a MCData user moves an existing folder in the MCData message store. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram for 'Move a user folder' operation. Lifelines: Message store client and MCData message store. The process involves: 1. MCData move folder request from client to store; 2. Move the identified folder to the destination (internal to store); 3. MCData move folder response from store to client.](fcc757566216206ceddbd6c775e8db02_img.jpg) + +``` +sequenceDiagram + participant Client as Message store client + participant Store as MCData message store + Note right of Store: 2.Move the identified folder to the destination + Client->>Store: 1. MCData move folder request + Store-->>Client: 3. MCData move folder response +``` + +Sequence diagram for 'Move a user folder' operation. Lifelines: Message store client and MCData message store. The process involves: 1. MCData move folder request from client to store; 2. Move the identified folder to the destination (internal to store); 3. MCData move folder response from store to client. + +**Figure 7.13.3.14.2-1: Move a user folder** + +1. The MCData user would like to move an existing folder in his user account in the MCData message store to a new location, the message store client initiates a MCData move folder request toward the MCData message store. The folder identifiers of the source and destination folders and the new folder name are included in the request. +2. The MCData message store move the source folder to the destination with the new folder name. If no new folder name is provided in the request, the source folder name will be used. All the child folders and objects stored in this folder are also moved to the new folder. +3. The MCData message store returns the result in the MCData move folder response. The identifier of the new folder is returned in the response. + +#### 7.13.3.15 Folder list operation + +##### 7.13.3.15.1 General + +A user can view the folder structure in his user account in the MCData message store. The target folder hierarchy structure will be presented to the user; i.e. the folder and all its child folders. This operation is only meaningful when the user account in the MCData message store is structured in the folder hierarchy. + +##### 7.13.3.15.2 Procedure + +The procedure in figure 7.13.3.15.2-1 describes the case when a MCData user lists an existing folder's hierarchy structure in the MCData message store. + +Pre-conditions: + +1. The MCData user has an account in the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram for Folder list operation](5801c19431e76330430e92a598cc7a16_img.jpg) + +``` +sequenceDiagram + participant MSC as Message store client + participant MMS as MCData message store + Note right of MMS: 2. Generate folder view + MSC->>MMS: 1. MCData list folder request + MMS-->>MSC: 3. MCData list folder response +``` + +The diagram illustrates the interaction between a Message store client and an MCData message store for a folder list operation. The client sends a '1. MCData list folder request' to the store. The store then performs an internal action '2. Generate folder view' and returns the result with '3. MCData list folder response'. + +Sequence diagram for Folder list operation + +**Figure 7.13.3.15.2-1: Folder list operation** + +1. The MCData user would like to view the folder structure of a targeted folder in his user account in the MCData message store, the message store client initiates a MCData list folder request toward the MCData message store. The folder identifier of the target folder is included in the request. +2. The MCData message store retrieves the target folder and all its child folders. If no target folder name is provided in the request, the MCData message store will use the root folder as the target folder. +3. The MCData message store returns the result in the MCData list folder response. + +#### 7.13.3.16 Upload objects + +##### 7.13.3.16.1 General + +A MCData user, with an account in the MCData message store, involved in an off-network communication will store the communication as objects in a specific folder in the local message store on his UE. These objects can be uploaded to his user account in the MCData message store once he is connected to the network with MC data service again. + +##### 7.13.3.16.2 Procedure + +The procedure in figure 7.13.3.16.2-1 describes the case when a message store client uploads new objects in its local message store to the MCData message store for a MCData user. + +Pre-conditions: + +1. The MCData user has an account with the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram for Upload objects](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` +sequenceDiagram + participant MSC as Message store client + participant MMS as MCData message store + Note right of MMS: 2. Process the uploaded objects + MSC->>MMS: 1. MCData upload objects request + MMS-->>MSC: 3. MCData upload objects response +``` + +The diagram is a sequence diagram illustrating the 'Upload objects' interaction. It features two lifelines: 'Message store client' on the left and 'MCData message store' on the right. The interaction consists of three steps: 1. The client sends a 'MCData upload objects request' to the store. 2. The store performs an internal action labeled 'Process the uploaded objects'. 3. The store returns a 'MCData upload objects response' to the client. + +Sequence diagram for Upload objects + +**Figure 7.13.3.16.2-1: Upload objects** + +1. The message store client would like to upload new objects in its local message store to the MCData message store. It initiates the MCData upload objects request toward the MCData message store. The uploaded objects and the target folder identifier where the objects will be stored are included in the request. +2. The MCData message store stores the uploaded objects to the target folder. If the target folder doesn't exist, the MCData message store will create it. +3. The MCData message store returns the result in the MCData upload objects response. + +#### 7.13.3.17 Notify client to synchronize + +##### 7.13.3.17.1 General + +MCData message store will send a notification to the MCData user when there are new objects in the MCData message store that need to be synchronized with his local message store. + +##### 7.13.3.17.2 Procedure + +The procedure in figure 7.13.3.17.2-1 describes how the MCData message store notifies the message store client that there are new objects in the MCData message store need to be synchronized. + +Pre-conditions: + +1. The MCData user has an account with the MCData message store. +2. A successful authentication and authorization have been performed between the message store client and the MCData message store. + +![Sequence diagram showing the notification process between MCData message store and Message store client.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` +sequenceDiagram + participant MCData message store + participant Message store client + Note left of MCData message store: 1. New objects received since last synchronization + MCData message store->>Message store client: 2. MCData synchronization notification +``` + +The diagram is a sequence diagram with two lifelines: "MCData message store" on the left and "Message store client" on the right. The process starts with a self-call on the "MCData message store" lifeline, labeled "1. New objects received since last synchronization". Following this, a message arrow labeled "2. MCData synchronization notification" is sent from the "MCData message store" lifeline to the "Message store client" lifeline. + +Sequence diagram showing the notification process between MCData message store and Message store client. + +**Figure 7.13.3.17.2-1: Notify client to synchronize** + +1. The MCData message store receives new objects for the MCData user and decides to send a notification to inform the MCData user. + +NOTE: How MCData message store determines if a notification needs to be sent to the message store client is out of scope of the present specification. + +2. The MCData message store sends the MCData synchronization notification to the message store client. + +### 7.13.4 Generic outgoing SDS procedure with MCData message store + +#### 7.13.4.1 General + +When a MCData user is supported with MCData message store all his outgoing communications shall be stored in his account in the MCData message store when he has requested. This generic SDS procedure applies to all procedures in subclause 7.4.2 when the MCData user requests to store the MCData communication. + +#### 7.13.4.2 Procedure + +The procedure in figure 7.13.4.2-1 describes the generic SDS service where MCData message store is supported. + +Pre-conditions: + +1. MCData user has an account created with MCData message store. +2. MCData user has requested to store his MCData communication. + +![Sequence diagram showing the generic outgoing SDS procedure with MCData message store. Lifelines: MCData client, MCData server, and MCData message store. Step 1: MCData client initiates a MCData SDS service request to MCData server. Step 2: MCData server deposits the object to MCData message store. Step 3: MCData server continues with the MCData SDS service request.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) + +``` +sequenceDiagram + participant MCData client + participant MCData server + participant MCData message store + Note left of MCData client: 1. Initiates a MCData SDS service request + MCData client->>MCData server: + Note right of MCData server: 2. Deposit the object + MCData server->>MCData message store: + Note right of MCData message store: 3. Continue with the MCData SDS service request + MCData message store->>MCData server: +``` + +Sequence diagram showing the generic outgoing SDS procedure with MCData message store. Lifelines: MCData client, MCData server, and MCData message store. Step 1: MCData client initiates a MCData SDS service request to MCData server. Step 2: MCData server deposits the object to MCData message store. Step 3: MCData server continues with the MCData SDS service request. + +**Figure 7.13.4.2-1 Generic outgoing SDS procedure with MCData message store** + +1. MCData client initiates an MCData SDS service request; this service request can be a private or group communication. +2. MCData server stores the communication as an object to the MCData user account in the MCData message store. +3. MCData server checks and authorizes the service request and continue the service request toward the targeted recipient(s) as described in subclause 7.4.2. + +### 7.13.5 Generic incoming SDS procedure with MCData message store + +#### 7.13.5.1 General + +When a MCData user is supported with MCData message store all his incoming communications shall be stored in his account in the MCData message store when he has requested. This generic SDS procedure applies to all procedures in subclause 7.4.2 when the MCData user requests to store the MCData communication. + +#### 7.13.5.2 Procedure + +The procedure in figure 7.13.5.2-1 describes the generic SDS service where MCData message store is supported. + +Pre-conditions: + +1. MCData user has an account created with MCData message store. +2. MCData user has requested to store his MCData communication. + +![Sequence diagram showing the generic incoming SDS procedure with MCData message store. Lifelines: MCData client, MCData server, and MCData message store. Step 1: MCData server receives an incoming MCData SDS service request. Step 2: MCData server deposits the object into the MCData message store. Step 3: MCData server delivers the MCData SDS service request to the MCData client.](5e9af8986a5845504f251d3079da8078_img.jpg) + +``` + +sequenceDiagram + participant MCData client + participant MCData server + participant MCData message store + Note right of MCData server: 1. Receives an incoming MCData SDS service request + Note right of MCData server: 2. Deposit the object + Note right of MCData client: 3. Deliver the MCData SDS service request + +``` + +Sequence diagram showing the generic incoming SDS procedure with MCData message store. Lifelines: MCData client, MCData server, and MCData message store. Step 1: MCData server receives an incoming MCData SDS service request. Step 2: MCData server deposits the object into the MCData message store. Step 3: MCData server delivers the MCData SDS service request to the MCData client. + +**Figure 7.13.5.2-1 Generic incoming SDS procedure with MCData message store** + +1. The MCData server receives an incoming MCData SDS service request for the MCData user. This service request can be a response to an earlier service request sent by the MCData user or a new service request coming from any sender. +2. MCData server stores the communication as an object to the MCData user account in the MCData message store. +3. MCData server delivers the service request to MCData user as described in subclause 7.4.2. + +### 7.13.6 Interconnection and migration with MCData message store + +#### 7.13.6.1 Interconnection + +There is no interconnection of MCData message stores, as there are no defined reference points providing connection between message stores in different MCData systems. + +#### 7.13.6.2 Migration + +A migrated MCData user may be provided with access to a local message store by the partner MCData system of the migrated MCData user. The MCData user is identified by the MCData ID used in the partner MCData system by that migrated MCData user in order to access the message store. There is no connection between this message store in the partner MCData system of the migrated MCData user and any message store that the MCData user has access to in the primary MCData system of that MCData user, and therefore access to a message store in the partner MCData system does not provide a means of accessing stored content in the primary MCData system of the migrated MCData user. + +A migrated MCData user may be provided with a means of access to the message store in the primary MCData system of that MCData user, e.g. by providing the MCData user with a suitable APN and appropriate IP routing, or by use of the MCData IP connectivity service. Such access is outside the scope of the present document. + +## 7.14 IP connectivity + +### 7.14.1 General + +IP data shall be exchanged between two or more data hosts. The MCData client as the link between data host and MC service system enables the exchange of IP Data. For addressing the corresponding MCData users either MCData ID or the functional alias can be used independently of each other. The MCData server provides the mechanisms to establish the association between MCData ID and corresponding functional alias. + +### 7.14.2 IP connectivity for on-network + +#### 7.14.2.1 Information flows for IP connectivity + +##### 7.14.2.1.1 MCDATA IPcon point-to-point request + +Table 7.14.2.1.1-1 describes the information flow of the MCDATA IPcon point-to-point request sent from the MCDATA client to the MCDATA server and from the MCDATA server to the addressed MCDATA client. + +**Table 7.14.2.1.1-1: MCDATA IPcon point-to-point request** + +| Information element | Status | Description | +|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCDATA ID | M | The MCDATA identity of the originator MCDATA user; | +| Functional alias | O | The associated functional alias of the originator MCDATA user; | +| MCDATA ID | M | The MCDATA identity of the target MCDATA client IP connectivity is requested. | +| Application Priority | O | Contains the required application priority for the IP data communication. If not present, the MCDATA applies the predefined default application priority after reception of MCDATA IPcon response. | +| Location Information | O
(see NOTE) | Actual location information of the originating MCDATA user; | +| Time Limit | O | Proposed time limit of the requested IP connectivity (1min- infinite); | +| Establishment reason | O | IP connectivity establishment reason | +| NOTE: | This information contains the latest available location information of the requesting MCDATA user that may be different to the latest available location information in the MC system. | | + +##### 7.14.2.1.2 MCDATA IPcon point-to-point response + +Table 7.14.2.1.2-1 describes the information content of the MCDATA IPcon point-to-point response as answer to MCDATA IPcon point-to-point data request. + +**Table 7.14.2.1.2-1: MCDATA IPcon point-to-point response** + +| Information element | Status | Description | +|------------------------|--------|----------------------------------------------------| +| MCDATA ID | M | The MCDATA identity of the targeted MCDATA user. | +| MCDATA ID | M | The MCDATA identity of the requesting MCDATA user. | +| Time Limit | O | Negotiated time (1 min – infinite) | +| IP connectivity status | M | IP connectivity establishment result | + +#### 7.14.2.2 IP connectivity point-to-point MCDATA transport service + +##### 7.14.2.2.1 General + +IP connectivity service capabilities enables MCDATA unaware data host to use usual MCDATA service capabilities, e.g. data communication between them. This subsection describes the establishment of a point-to-point connection between two IP connectivity clients using the media plane for IP Data transmission. + +##### 7.14.2.2.2 Procedure + +The procedure in figure 7.14.2.2.2-1 describes the case where an IP connectivity capable MCDATA client is initiating a point-to-point IP connectivity with another IP connectivity capable MCDATA client. + +Pre-conditions: + +- The total data volume limit, e.g. daily time limit or total data volume per day does not restrict the establishment of an IP connectivity IP data exchange. +- MCDATA clients are linked with individual data hosts. +- MCDATA clients belong to the same MCDATA system. + +- The data hosts linked with the MCData clients already have an IP address allocated. +- MCData clients have IP connectivity capabilities. +- The linked data hosts are authorized to use the MCData clients to establish an IP connectivity. + +NOTE: How the data host is authorized to use the MCData client is out of the scope of the present document. + +- The MCData server has subscribed to the MCData functional alias controlling server within the MC system for functional alias activation/de-activation updates. +- MCData client 1 understands the correspondence between the IP addresses of target data hosts and MCData client 2. How this relationship is determined is out of scope of the present document. + +![Sequence diagram for Establishment of a point-to-point IP connectivity](c0f64806753a053854921deb8f4fc798_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCData client 1 + participant S as MCData server + participant C2 as MCData client 2 + Note over C1: 1. Initiate data request + C1->>S: 2. MCData IPcon point-to-point request + Note over S: 3. Authorize request + S->>C2: 4. MCData IPcon point-to-point request + C2->>S: 5. MCData IPcon point-to-point response + S->>C1: 6. MCData IPcon point-to-point response + Note over S: 7. Transmission/ Reception control + rect rgb(255, 255, 255) + Note over C1,C2: 8. IP Data Transmission + end + +``` + +The diagram illustrates the establishment of point-to-point IP connectivity. It shows three vertical lifelines for MCData client 1, MCData server, and MCData client 2. + 1. MCData client 1 initiates a data request internally. + 2. A request is sent from client 1 to the server. + 3. The server performs an authorization check. + 4. The server forwards the request to client 2. + 5. Client 2 sends a response back to the server. + 6. The server forwards the response to client 1. + 7. The server performs transmission/reception control. + 8. A horizontal bar across all lifelines indicates the final state of IP Data Transmission between the two clients. + +Sequence diagram for Establishment of a point-to-point IP connectivity + +**Figure 7.14.2.2.2-1: Establishment of a point-to-point IP connectivity** + +1. MCData client 1 has IP Data to send to MCData client 2 and initiates an IP connectivity point-to-point request. +2. MCData client 1 sends a MCData IPcon point-to-point request towards the MCData server. The MCData IPcon point-to-point request contains the MCData ID of MCData client 2. MCData user at MCData client 1 may include its associated functional alias. +3. MCData server checks whether MCData user at MCData client 1 is authorized to send an MCData IPcon point-to-point request and checks if MCData client 2 is authorised to receive the IP connectivity service. +4. MCData server initiates the MCData IPcon point-to-point request towards the MCData client 2. +5. MCData client 2 sends a MCData IPcon point-to-point response to the MCData server that contains the information if the request is accepted or the reason of rejection. If accepted, the MCData client 2 may include the data transmission time limit. +6. MCData server forwards the MCData IPcon point-to-point response of MCData client 2 to MCData client 1. +7. The MCData server applies transmission and reception control and the necessary policy to ensure that appropriate data is transmitted between the MCData clients. +8. MCData client 1 and MCData Client 2 have successfully established media plane for data communication and MCData client 1 and MCData client 2 exchange IP Data. + +## 7.15 Location information (on-network) + +The MCData system makes use of all of the procedures for location management as specified in 3GPP TS 23.280 [5], utilising the CSC-14 reference point between the location management client and location management server and the CSC-15 reference point between the MCData server and location management server. + +- The MC service client is the MCData client; +- The MC service server is the MCData server; +- The MC service group is the MCData group; +- The MC service ID is the MCData ID; and +- The MC service group ID is the MCData group ID. + +# Annex A (normative): MCData related configuration data + +## A.1 General + +This Annex provides information about the static data needed for configuration for the MCData service, which belongs to one of the following categories: + +- MCData UE configuration data (see subclause A.2); +- MCData user profile configuration data (see subclause A.3); +- MCData related group configuration data (see subclause A.4); and +- MCData service configuration data (see subclause A.5). + +For each configuration category, data is split between configuration data that is applicable to both on network and off network, configuration data that is applicable to on-network only, and configuration data that is applicable to off-network only. The configuration data in each configuration category corresponds to a single instance of the category type i.e. the MCData UE, MCData group, MCData user and MCData service configuration data refers to the information that will be stored against each MCData UE, MCData group, MCData user and MCData service. This means that the three separate tables (on-network and off-network, on-network only, off-network only) for each configuration category represent the complete set of data for each configuration data category element. + +The columns in the tables have the following meanings: + +- Reference: the reference of the corresponding requirement in 3GPP TS 22.282 [3] or 3GPP TS 22.280 [2] or the corresponding subclause from either the present document or the referenced document. +- Parameter description: A short definition of the semantics of the corresponding item of data, including denotation of the level of the parameter in the configuration hierarchy. + - When it is not clear to which functional entities the parameter is configured, then one or more columns indicating this are provided where the following nomenclature is used: + - "Y" to denote "Yes" i.e. the parameter denoted for the row needs to be configured to the functional entity denoted for the column. + - "N" to denote "No" i.e. the parameter denoted for the row does not need to be configured to the functional entity denoted for the column. + +Parameters within a set of configuration data have a level within a hierarchy that pertains only to that configuration data. The hierarchy of the configuration data is common across all three tables of on-network and off-network, on network only and off network only. The level of a parameter within the hierarchy of the configuration data is denoted by use of the character ">" in the parameter description field within each table, one per level. Parameters that are at the top most level within the hierarchy have no ">" character. Parameters that have one or more ">" characters are child parameters of the first parameter above them that has one less ">" character. Parent parameters are parameters that have one or more child parameters. Parent parameters act solely as a "grouping" of their child parameters and therefore do not contain an actual value themselves i.e. they are just containers for their child parameters. + +Each parameter that can be configured online shall only be configured through one online reference point. Each parameter that can be configured offline shall only be configured through one offline reference point. The most recent configuration data made available to the MCData UE shall always overwrite previous configuration data, irrespective of whether the configuration data was provided via the online or offline mechanism. + +## A.2 MCData UE configuration data + +The general aspects of UE configuration are specified in 3GPP TS 23.280 [5]. Data in tables A.2-1 and A.2-2 have to be known by the MCData UE after MCData authorization. + +Data in table A.2-1 can be configured offline using the CSC-11 reference point. Table A.2-1 contains the UE configuration required to support the use of off-network MCData service. + +**Table A.2-1: UE configuration data (on and off network)** + +| Reference | Parameter description | +|-------------------------------------|---------------------------------------------------------------------------------------------------------------------| +| | Short data service | +| [R-5.4.2-002] of 3GPP TS 22.280 [2] | > Maximum number of simultaneous SDS transactions (Nc4) | +| [R-5.4.2-004] of 3GPP TS 22.280 [2] | > Requested presentation priority of SDS messages received (see NOTE) | +| | File distribution | +| [R-5.4.2-002] of 3GPP TS 22.280 [2] | > Maximum number of simultaneous file distribution transactions (Nc4) | +| | Transmission control | +| [R-5.4.2-002] of 3GPP TS 22.280 [2] | > Maximum number of simultaneous data transmissions (Nc4) | +| [R-5.4.2-003] of 3GPP TS 22.280 [2] | > Maximum number of data transmissions (Nc5) in a group | +| | Reception control | +| [R-5.4.2-002] of 3GPP TS 22.280 [2] | > Maximum number of simultaneous data receptions (Nc4) | +| [R-5.4.2-003] of 3GPP TS 22.280 [2] | > Maximum number of data receptions (Nc5) in a group | +| NOTE: | Priority of SDS messages includes enhanced status updates, since enhanced status updates utilise the SDS mechanism. | + +**Table A.2-2: UE configuration data (on network)** + +| Reference | Parameter description | +|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| +| Subclause 5.2.3 of 3GPP TS 23.280 [6] | Relay service (Y/N) | +| Subclause 5.2.3 of 3GPP TS 23.280 [6] | List of allowed relayed MCData groups and their relay service code (as specified in 3GPP TS 23.303 [7]) (optional) (see NOTE) | +| | > MCData group ID | +| | > Relay service code (as specified in 3GPP TS 23.303 [7]) | +| NOTE: | When the value of the parameter Relay service is N, this parameter and its child parameters are not needed. | + +## A.3 MCData user profile configuration data + +The general aspects of MC service user profile configuration data are specified in 3GPP TS 23.280 [5]. The MCData user profile configuration data is stored in the MCData user database. The MCData server obtains the MCData user profile configuration data from the MCData user database (MCData-2). + +Tables A.3-1 and A.3-2 contain the MCData user profile configuration required to support the use of on-network MCData service. Tables A.3-1 and A.3-3 contain the MCData user profile configuration required to support the use of off-network MCData service. Data in table A.3-1 and A.3-3 can be configured offline using the CSC-11 reference point. + +**Table A.3-1: MCData user profile configuration data (on and off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | MCData user database | +|-----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|-----------|---------------|---------------------------------|----------------------| +| Subclause 8.1.2 of 3GPP TS 23.280 [5] | MCData identity (MCData ID) | Y | Y | Y | Y | +| 3GPP TS 33.180 [13] | KMSUri for security domain of MCData ID (see NOTE 1) | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [5] | Pre-selected MCData user profile indication (see NOTE 2) | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [5] | MCData user profile index | Y | Y | Y | Y | +| Subclause 5.2.4 of 3GPP TS 23.280 [5] | MCData user profile name | Y | Y | Y | Y | +| [R-5.17-007], [R-6.13.4-002] of 3GPP TS 22.280 [2] | User profile status (enabled/disabled) | | Y | Y | Y | +| [R-5.7-001], [R-6.9-003] of 3GPP TS 22.280 [2] | Authorised to create and delete aliases of an MCData user and its associated user profiles. | | | Y | Y | +| [R-5.7-002], [R-6.9-003] of 3GPP TS 22.280 [2] | Alphanumeric aliases of user | Y | Y | Y | Y | +| [R-5.1.1-005], [R-5.9-001] of 3GPP TS 22.280 [2] | Participant type of the user | Y | Y | Y | Y | +| [R-5.1.8-006], [R-5.3-002], [R-5.9-001], [R-5.16.2-001], [R-5.16.2-002] of 3GPP TS 22.280 [2] | User's Mission Critical Organization (i.e. which organization a user belongs to) | Y | Y | Y | Y | +| [R-5.2.2-003] of 3GPP TS 22.280 [2] | Authorisation to create a group-broadcast group | | | Y | Y | +| [R-5.2.2-003] of 3GPP TS 22.280 [2] | Authorisation to create a user-broadcast group | | | Y | Y | +| [R-5.6.2.4.1-002] of 3GPP TS 22.280 [2] | Authorised to activate MCData emergency alert | Y | Y | Y | Y | +| [R-5.6.2.4.1-013] of 3GPP TS 22.280 [17] | Automatically trigger a MCData emergency communication after initiating the MCData emergency alert | Y | Y | Y | Y | +| [R-5.6.2.4.1-004], [R-5.6.2.4.1-008], [R-5.6.2.4.1-012] of 3GPP TS 22.280 [2] | Group used on initiation of an MCData emergency group communication (see NOTE 3) | | | | | +| [R-5.6.2.4.1-004], [R-5.6.2.4.1-008], [R-5.6.2.4.1-012] of 3GPP TS 22.280 [17] | Recipient for an MCData emergency private communication (see NOTE 3) | | | | | +| | > MCData ID | Y | Y | Y | Y | +| 3GPP TS 33.180 [19] | > KMSUri for security domain of MCData ID (see NOTE 1) | Y | Y | Y | Y | +| [R-5.6.2.4.2-002] of 3GPP TS 22.280 [2] | Authorisation to cancel an MCData emergency alert | Y | Y | Y | Y | +| [R-6.1.1.2-005], [R-6.1.1.2-006], [R-6.1.1.2-007] of 3GPP TS 22.282 [3] | Individual conversation hang time | Y | Y | Y | Y | + +| | | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| | One-to-one communication | | | | | +| [R-6.3.1.2-007] of 3GPP TS 22.282 [3] and 3GPP TS 33.180 [13] | > List of MCData users this MCData user is authorized to initiate a one-to-one communication | | | | | +| | >> MCData ID | Y | N | Y | Y | +| | >> Discovery Group ID | Y | N | Y | Y | +| | >> User info ID (as specified in 3GPP TS 23.303 [7]) | Y | N | Y | Y | +| | >> KMSUri for security domain of MCData ID (see NOTE 1) | Y | Y | Y | Y | +| [R-6.7.3-007] of 3GPP TS 22.280 [2] | Authorised to make one-to-one communications towards users not included in "list of MCData user(s) this MCData user is authorized to initiate a one-to-one communication" | Y | Y | Y | Y | +| | File distribution | | | | | +| [R-5.3.2-010] of 3GPP TS 22.282 [3] and 3GPP TS 33.180 [13] | > List of MCData users this MCData user is allowed to cancel distribution of files being sent or waiting to be sent | | | | | +| | >> MCData ID | Y | Y | Y | Y | +| | >> KMSUri for security domain of MCData ID (see NOTE 1) | Y | Y | Y | Y | +| | Transmission and reception control | | | | | +| [R-6.2.2.1-001] of 3GPP TS 22.282 [3] | > Whether the MCData user is permitted to transmit data | Y | Y | Y | Y | +| [R-6.2.3-005] of 3GPP TS 22.282 [3] | > Maximum amount of data that the MCData user can transmit in a single request during one-to-one communication | Y | Y | Y | Y | +| [R-6.2.3-005] and [R-6.3.1.2-008] of 3GPP TS 22.282 [3] | > Maximum amount of time that the MCData user can transmit in a single request during one-to-one communication | Y | Y | Y | Y | +| [R-6.2.3-001] of 3GPP TS 22.282 [3] | > List of MCData users this MCData user is allowed to request the release of an ongoing transmission that this MCData user is participating in | | | | | +| | >> MCData ID | Y | Y | Y | Y | +| NOTE 1: If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5]. | | | | | | +| NOTE 2: As specified in 3GPP TS 23.280 [5], for each MCData user's set of MCData user profiles, only one MCData user profile shall be indicated as being the pre-selected MCData user profile. | | | | | | +| NOTE 3: This parameter is used for the emergency communication and also used as a target of the emergency alert request. At most one of them is configured; i.e. emergency communication will go to either a group or a user. If both are not configured the MCData user's currently selected group will be used. | | | | | | + +**Table A.3-2: MCData user profile configuration data (on network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | MCData user database | +|---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------|---------------|---------------------------------|----------------------| +| [R-5.1.5-001],
[R-5.1.5-002],
[R-5.10-001],
[R-6.4.7-002],
[R-6.8.1-008],
[R-6.7.4-002] of
3GPP TS 22.280 [2] | List of on-network MCData groups for use by an MCData user | | | | | +| | > MCData Group ID | Y | Y | Y | Y | +| | > Application plane server identity information of group management server where group is defined | | | | | +| | >> Server URI | Y | Y | Y | Y | +| | > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) | | | | | +| | >> Server URI | Y | Y | Y | Y | +| 3GPP TS 33.180 [13] | > KMSUri for security domain of group (see NOTE 2) | Y | Y | Y | Y | +| | > Presentation priority of the group relative to other groups and users (see NOTE 3) | Y | N | Y | Y | +| | > Transmission and reception control | | | | | +| | >> Whether MCData user is permitted to transmit data in the group | Y | Y | Y | Y | +| | >> Maximum amount of data that the MCData user can transmit in a single request during group communication | Y | Y | Y | Y | +| | >> Maximum amount of time that the MCData user can transmit in a single request during group communication | Y | Y | Y | Y | +| Subclause 5.2.5 of
3GPP TS 23.280 [5] | List of groups user implicitly affiliates to after MCData service authorization for the user | | | | | +| | > MCData Group ID | Y | Y | Y | Y | +| [R-6.4.2-006] of
3GPP TS 22.280 [2] | Authorisation of an MCData user to request a list of which MCData groups a user has affiliated to | | Y | Y | Y | +| [R-6.4.6.1-002],
[R-6.4.6.1-003] of
3GPP TS 22.280 [2] | Authorisation to change affiliated groups of other specified user(s) | | Y | Y | Y | +| [R-6.4.6.2-001],
[R-6.4.6.2-002] of
3GPP TS 22.280 [2] | Authorisation to recommend to specified user(s) to affiliate to specific group(s) | | Y | Y | Y | +| [R-6.6.1-004] of
3GPP TS 22.280 [2] | Authorisation to perform regrouping | Y | Y | Y | Y | +| [R-6.7.2-001] of
3GPP TS 22.280 [2] | Presence status is available/not available to other users | Y | Y | Y | Y | +| [R-6.7.1-002],
[R-6.7.2-002] of
3GPP TS 22.280 [2] | List of MCData users that MCData user is authorised to obtain presence of | | | | | +| | > MCData IDs | Y | Y | Y | Y | +| [R-6.8.7.4.2-001],
[R-6.8.7.4.2-002] of
3GPP TS 22.280 [2] | Authorisation of a user to cancel an emergency alert on any MCData UE of any user | | Y | Y | Y | +| [R-6.13.4-001] of
3GPP TS 22.280 [2] | Authorisation for an MCData user to enable/disable an MCData user | | Y | Y | Y | + +| | | | | | | +|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| [R-6.13.4-003],
[R-6.13.4-005],
[R-6.13.4-006],
[R-6.13.4-007] of
3GPP TS 22.280 [2] | Authorisation for an MCData user to
(permanently /temporarily)
enable/disable a UE | | Y | Y | Y | +| [R-7.14-002],
[R-7.14-003] of
3GPP TS 22.280 [2] | Authorization for manual switch to
off-network while in on-network | Y | Y | Y | Y | +| [R-5.1.5-004] of
3GPP TS 22.280 [2] | Limitation of number of affiliations
per user (N2) | N | Y | Y | Y | +| [R-6.4.6.1-001],
[R-6.4.6.1-004] of
3GPP TS 22.280 [2] | List of MCData users whose
selected groups are authorized to
be remotely changed | | | | | +| | > MCData ID | Y | Y | Y | Y | +| [R-6.7.3-007a] of
3GPP TS 22.280 [2]
and
3GPP TS 33.180 [13] | List of MCData users this MCData
user is authorized to receive a
one-to-one communication | | | | | +| | > MCData ID | Y | Y | Y | Y | +| | > KMSUri for security domain of
MCData ID | Y | Y | Y | Y | +| | Conversation management | | | | | +| [R-6.1.1.2-009] of
3GPP TS 22.282 [3]. | > List of MCData users to be sent
message delivered disposition
notifications in addition to the
message sender | N | Y | Y | Y | +| | >> MCData ID | N | Y | Y | Y | +| [R-6.1.1.2-009] of
3GPP TS 22.282 [3]. | > List of MCData users to be sent
message read disposition
notifications in addition to the
message sender | N | Y | Y | Y | +| | >> MCData ID | N | Y | Y | Y | +| 3GPP TS 23.283 [18] | Authorised to use LMR E2EE for
interworking | Y | Y | Y | Y | +| 3GPP TS 23.283 [18] | > List of supported LMR technology
types | | | | | +| 3GPP TS 23.283 [18] | >> LMR technology type (P25,
TETRA etc.) | Y | N | Y | Y | +| 3GPP TS 23.283 [18] | >> URI of LMR key management
functional entity (see NOTE 4 ) | Y | N | Y | Y | +| 3GPP TS 23.283 [18] | >> LMR specific identity (RSI for
P25 or ITSI for TETRA) (see
NOTE 5) | Y | N | Y | Y | +| 3GPP TS 23.283 [18] | >> LMR specific security information
(see NOTE 5) | Y | N | Y | Y | +| | List of servers used in the private
and group communications | | | | | +| | > MCData content server where the
HTTP FD file is uploaded | | | | | +| | >> Server URI | Y | Y | Y | Y | +| | > MCData message store where the
communication history stores | | | | | +| | >> Server URI | Y | Y | Y | Y | +| Subclause 5.2.9 of
3GPP TS 23.280 [16] | List of partner MCData systems in
which this profile is valid for use
during migration | | | | | +| Subclause 5.2.9 of
3GPP TS 23.280 [16] | > Identity of partner MCData system | Y | Y | Y | Y | +| Subclause 10.1.1 of
3GPP TS 23.280 [16] | > Access information for partner
MCData system (see NOTE 6) | Y | | Y | Y | + +| | | | | | | +|--------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|---|---|---|---| +| [R-5.9a-012] of 3GPP TS 22.280 [2]
[R-5.9a-013] of 3GPP TS 22.280 [2] | Authorised to request information query of the association between active functional alias(es) and the MCData ID(s) | | Y | Y | Y | +| [R-6.6.4.2-002a] and [R-6.6.4.2-002b] of 3GPP TS 22.280 [2] | List of groups the client affiliates/de-affiliates when criteria is met | | | | | +| | > MCData Group ID | Y | Y | Y | Y | +| | >> Criteria for affiliation (see NOTE 7) | Y | Y | Y | Y | +| | >> Criteria for de-affiliation (see NOTE 7) | Y | Y | Y | Y | +| | >> Manual de-affiliation is not allowed if criteria for affiliation are met | Y | Y | Y | Y | +| [R-6.6.4.2-002] of 3GPP TS 22.280 [2] | List of groups the client affiliates after receiving an emergency alert | | | | | +| | > MCData Group ID | Y | Y | Y | Y | +| | >> Manual de-affiliation is not allowed if criteria for affiliation are met | Y | Y | Y | Y | +| | List of functional alias(es) of the MCData user | | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [2] | > Functional alias | Y | Y | Y | Y | +| [R-5.9a-018] of 3GPP TS 22.280 [2] | >> Trigger criteria for activation by the MCData server (see NOTE 8) | N | Y | Y | Y | +| [R-5.9a-017], [R-5.9a-018] of 3GPP TS 22.280 [2] | >> Trigger criteria for de-activation by the MCData server (see NOTE 8) | N | Y | Y | Y | +| [R-5.9a-019] of 3GPP TS 22.280 [2] | >> Trigger criteria for activation by the MCData client (see NOTE 8) | Y | Y | Y | Y | +| [R-5.9a-019] of 3GPP TS 22.280 [2] | >> Trigger criteria for de-activation by the MCData client (see NOTE 8) | Y | Y | Y | Y | +| | >> Manual de-activation is not allowed if the criteria are met (see NOTE 8) | Y | Y | Y | Y | +| [R-5.9a-012] of 3GPP TS 22.280 [2] | Authorised to take over a functional alias from another MCData user | | Y | Y | Y | +| | Authorised to participate in an IP connectivity session | Y | Y | Y | Y | +| [R-5.5.2-003], [R-5.5.2-004] 3GPP TS 22.282 [3] | >List of MCData users which can be included in IP connectivity sessions. | | | | | +| | >> MCData ID | Y | Y | Y | Y | +| 3GPP TS 33.180 [13] | >> KMSUri for security domain of the MCData ID | Y | Y | Y | Y | +| | >>List of associated data host IP information | | | | | +| | >>>IP information (see NOTE 9) | Y | Y | Y | Y | + +| | | +|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| NOTE 1: | If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5]. | +| NOTE 2: | If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5]. | +| NOTE 3: | The use of this parameter by the MCData UE is outside the scope of the present document. | +| NOTE 4: | The LMR key management functional entity is part of the LMR system and is outside the scope of the present document. | +| NOTE 5: | This is an LMR specific parameter with no meaning within MC services. | +| NOTE 6: | Access information for each partner MCData system comprises the list of information required for initial UE configuration to access an MCData system, as defined in table A.6-1 of 3GPP TS 23.280 [16] | +| NOTE 7: | The criteria may consist conditions such as the location of the MCData user or the active functional alias of the MCData user. | +| NOTE 8: | The criteria may consist of conditions such as MCData user location or time. | +| NOTE 9: | IP information may contain IP addresses, corresponding subnet masks, gateway and DNS settings. | + +**Table A.3-3: MCData user profile configuration data (off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | MCData user database | +|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---------------|---------------------------------|----------------------| +| [R-7.2-003], [R-7.6-004] of 3GPP TS 22.280 [2] | List of off-network MCData groups for use by this MCData user | | | | | +| | > MCData Group ID | Y | N | Y | Y | +| | > Application plane server identity information of group management server where group is defined | | | | | +| | >> Server URI | Y | N | Y | Y | +| | > Application plane server identity information of identity management server which provides authorization for group (see NOTE 1) | | | | | +| | >> Server URI | Y | N | Y | Y | +| 3GPP TS 33.180 [13] | > KMSUri for security domain of group (see NOTE 2) | Y | N | Y | Y | +| | > Presentation priority of the group relative to other groups and users (see NOTE 3) | Y | N | Y | Y | +| [R-7.12-002], [R-7.12-003] of 3GPP TS 22.280 [2] | Authorization for off-network services | Y | N | Y | Y | +| Subclause 10.7.2 | User info ID (as specified in 3GPP TS 23.303 [7]) | Y | N | Y | Y | +| NOTE 1: | If this parameter is not configured, authorization to use the group shall be obtained from the identity management server identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of TS 23.280 [5]. | | | | | +| NOTE 2: | If this parameter is absent, the KMSUri shall be that identified in the initial MC service UE configuration data (on-network) configured in table A.6-1 of 3GPP TS 23.280 [5]. | | | | | +| NOTE 3: | The use of this parameter by the MCData UE is outside the scope of the present document. | | | | | + +## A.4 MCData related Group configuration data + +The general aspects of group configuration are specified in 3GPP TS 23.280 [5]. + +Parameters specified in table A.4-1 are child parameters of the "MCData configuration" parameter specified in table A.4-1 in 3GPP TS 23.280 [5]. Parameters specified in table A.4-2 are child parameters of the "MCData configuration" parameter specified in table A.4-2 in 3GPP TS 23.280 [5]. Parameters specified in table A.4-3 are child parameters of the "MCData configuration" parameter specified in table A.4-3 in 3GPP TS 23.280 [5]. + +**Table A.4-1: Group configuration data (on and off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Group management server | +|-----------------------------------------------------------------|-----------------------------------------------------------------------------|-----------|---------------|-------------------------| +| [R-5.12-001] of 3GPP TS 22.280 [2] | >> Media confidentiality and integrity protection (see NOTE) | Y | Y | Y | +| [R-5.12-001] of 3GPP TS 22.280 [2] | >> Transmission control confidentiality and integrity protection (see NOTE) | Y | Y | Y | +| [R-5.12-001] of 3GPP TS 22.280 [2] | >> Group media protection security material (see NOTE) | Y | N | Y | +| Subclause 5 | >> MCData sub-services and features enabled for the group | | | | +| | >>> Short data service enabled | Y | Y | Y | +| | >>> File distribution enabled | Y | Y | Y | +| | >>> IP connectivity enabled | Y | Y | Y | +| | >>> Conversation management enabled | Y | Y | Y | +| | >>> Transmission control enabled | Y | Y | Y | +| | >>> Reception control enabled | Y | Y | Y | +| | >>> Enhanced status enabled | Y | Y | Y | +| | >> Enhanced status | | | | +| [R-6.1.3.2-002] of 3GPP TS 22.282 [3] | >>> List of operational status values | Y | N | Y | +| [R-6.1.1.2-011] of 3GPP TS 22.282 [2] | >> Lossless communication | Y | Y | Y | +| [R-6.1.1.2-007] of 3GPP TS 22.282 [5] | >> Conversation hang time | Y | Y | Y | +| NOTE: Security mechanisms are specified in 3GPP TS 33.180 [13]. | | | | | + +**Table A.4-2: Group configuration data (on network)** + +| Reference | Parameter description | MCData UE | MCData Server | Group management server | +|--------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-----------|---------------|-------------------------| +| [R-6.4.5-001], [R-6.4.5-003] of 3GPP TS 22.280 [2] | >> Authorisation of a user to request a list of affiliated members of a group | Y | Y | Y | +| [R-5.1.7-002], [R-6.2.2-001], [R-6.6.2.2-006], [R-6.8.7.2-003] of 3GPP TS 22.280 [2] | >> Priority of the group | N | Y | Y | +| Subclause 6.2.2 of 3GPP TS 22.282 [3] | >> Transmission and reception control | | | | +| | >>> Maximum data size for SDS | Y | Y | Y | +| | >>> Maximum data size for FD | Y | Y | Y | +| | >>> Maximum data size for auto-receive | N | Y | Y | +| 3GPP TS 23.283 [18] | >> Indication whether use of LMR E2EE is permitted on the MCData group | Y | N | Y | +| 3GPP TS 23.283 [18] | >> LMR specific identity for MCData group (see NOTE) | Y | N | Y | +| 3GPP TS 23.283 [18] | >> Group to key binding (see NOTE) | Y | N | Y | +| NOTE: This is an LMR specific parameter with no meaning within MC services. | | | | | + +**Table A.4-3: Group configuration data (off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Group management server | +|---------------------------------------|----------------------------------------------------------------------------------|------------------|----------------------|--------------------------------| +| Subclause 10.10 of 3GPP TS 23.280 [5] | >> Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values | | | | +| | >>> MCData group call signalling | Y | N | Y | +| | >>> MCData group call media | Y | N | Y | + +## A.5 MCData service configuration data + +The general aspects of MC service configuration are specified in 3GPP TS 23.280 [5]. The MCData service configuration data is stored in the MCData server. + +Tables A.5-1 and A.5-2 describe the configuration data required to support the use of on-network MCData service. Tables A.5-1 and A.5-3 describe the configuration data required to support the use of off-network MCData service. Data in tables A.5-1 and A.5-3 can be configured offline using the CSC-11 reference point. + +**Table A.5-1: MCData service configuration data (on and off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | +|------------------|------------------------------|------------------|----------------------|----------------------------------------| +|------------------|------------------------------|------------------|----------------------|----------------------------------------| + +**Table A.5-2: MCData service configuration data (on network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | +|-----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|-----------|---------------|---------------------------------| +| Subclause 6.2.2 of 3GPP TS 22.282 [3] | Transmission and reception control | | | | +| | > Maximum data size for SDS | Y | Y | Y | +| | > Maximum payload data size for SDS over signalling control plane (NOTE) | Y | Y | Y | +| | > Maximum data size for FD | Y | Y | Y | +| [R-6.2.2.1-002d], [R-6.2.2.4-003] of 3GPP TS 22.282 [3] | > Time limit for the temporarily stored data waiting to be delivered to a receiving user | N | Y | Y | +| [R-6.2.2.3-001] of 3GPP TS 22.282 [3] | > Timer for periodic announcement with the list of available recently invited data group communications | N | Y | Y | +| | > Maximum data size for auto-receive | N | Y | Y | +| | List of functional alias identities | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | > Functional alias | N | Y | Y | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | >> Limit number of simultaneous activations | N | Y | Y | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | >> This functional alias can be taken over | N | Y | Y | +| | >> List of users | | | | +| [R-5.9a-005] of 3GPP TS 22.280 [17] | >>> MCData ID | N | Y | Y | +| [R-5.10-001a] of 3GPP TS 22.280 [2] | Maximum number of successful simultaneous service authorizations of clients from a user | N | Y | Y | +| NOTE: The maximum payload data size for SDS over signalling control plane shall be less than or equal to the maximum data size for SDS. | | | | | + +**Table A.5-3: MCData service configuration data (off network)** + +| Reference | Parameter description | MCData UE | MCData Server | Configuration management server | +|---------------------------------------|-------------------------------------------------------------------------------|-----------|---------------|---------------------------------| +| Subclause 10.10 of 3GPP TS 23.280 [5] | Default ProSe Per-Packet priority (as specified in 3GPP TS 23.303 [7]) values | | | | +| | > MCData one-to-one call signalling | Y | N | Y | +| | > MCData one-to-one call media | Y | N | Y | + +# Annex B (informative): Transmission control for MCData + +## B.1 Overview of transmission control process + +The MCData server may receive several simultaneous requests for data transmission, which may be associated with different types of communication e.g. group, private, 1-to-many. For each communication, how the requests are processed may be different. The requests that are not authorized shall be rejected by the transmission control function. For message requests over the signalling control plane, the processing should be immediate and is delivered to the recipients either via unicast or broadcast. However, for message requests over the media plane, transmission control arbitration (see Annex B.2) will be necessary. Subsequent to transmission control arbitration, and subject to the policy e.g. store and forward, the data is either delivered directly to the recipient MCData user or stored in the network + +repository and a corresponding URL is delivered. The end-to-end transmission control process is illustrated in figure B.1-1. + +**Editor's note: The aspects related to data streaming and accuracy of the process is FFS.** + +![Flowchart of the Transmission control process. The process starts with 'MCData user Wants to send data', followed by 'Select data to send' and 'Select recipient(s)/group'. A decision 'Use signaling control plane?' follows. If 'Yes', it checks 'Max payload Size over Signaling control Plane?'. If 'No' to that, it uses the media plane. If 'Yes', it uses the signaling control plane. If 'No' to 'Use signaling control plane?', it uses the media plane. Both paths lead to 'Authorized To send?'. If 'No', it's 'Rejected'. If 'Yes', it goes to 'Transmission control arbitration'. From there, it checks 'Store and Forward?'. If 'Yes', it sends a URL. If 'No', it checks 'Broadcast?'. If 'Yes', it sends via broadcast. If 'No', it sends via Unicast.](e4bbddb050930c71ba62996a2e194549_img.jpg) + +``` + +graph TD + A[MCData user Wants to send data] --> B[Select data to send] + B --> C[Select recipient(s)/group] + C --> D{Use signaling control plane?} + D -- No --> E[Use media plane to send] + D -- Yes --> F{Max payload Size over Signaling control Plane?} + F -- No --> E + F -- Yes --> G[Use signaling control plane to send] + E --> H{Authorized To send?} + G --> I{Authorized To send?} + H -- No --> J[Rejected] + H -- Yes --> K[Transmission control arbitration] + I -- No --> L[Rejected] + I -- Yes --> K + K --> M{Store and Forward?} + M -- Yes --> N[Send URL to recipient(s)] + M -- No --> O{Broadcast?} + O -- Yes --> P[Send data to recipient(s) via broadcast] + O -- No --> Q[Send data to recipient(s) via Unicast] + +``` + +Flowchart of the Transmission control process. The process starts with 'MCData user Wants to send data', followed by 'Select data to send' and 'Select recipient(s)/group'. A decision 'Use signaling control plane?' follows. If 'Yes', it checks 'Max payload Size over Signaling control Plane?'. If 'No' to that, it uses the media plane. If 'Yes', it uses the signaling control plane. If 'No' to 'Use signaling control plane?', it uses the media plane. Both paths lead to 'Authorized To send?'. If 'No', it's 'Rejected'. If 'Yes', it goes to 'Transmission control arbitration'. From there, it checks 'Store and Forward?'. If 'Yes', it sends a URL. If 'No', it checks 'Broadcast?'. If 'Yes', it sends via broadcast. If 'No', it sends via Unicast. + +**Figure B.1-1: Transmission control process** + +## B.2 Transmission control arbitration + +The transmission control arbitration is a central function of the transmission control process and is implementation specific. In a typical deployment, multiple or simultaneous requests can be received at the transmission control arbitration function. Each of these requests may be categorized into different request types with different queuing priorities, and therefore each request type will be maintained with separate queues. Each request shall not be present in more than one queue at any given time. The queue types and the order of queues may be configured by the MCData administrator, as described below. + +- Transmission control queue: It is the primary queue from which the request is processed for transmission e.g. emergency communication requests may result in this queue and processed at the highest priority. +- Communication type queue: This queue may be sorted in the order of the communication type associated with the request. For example, the group communication requests may always take precedence over one-to-many or private communication requests. +- Static attribute queue: This queue may be formed based on the static attributes associated with the request e.g. group priority, user priority, which may be pre-configured by the MCData administrator. +- Dynamic attribute queue: This queue may be formed based on the dynamic attributes associated with the request e.g. location of the sending user, content size, etc. + +# Annex C VOID + +# Annex D (informative): Example of a User Message Storage Area + +The figure in subclause 7.13.1 illustrates the high-level structure of the MCData message store where objects are stored in a flat structure in the user storage area. This flat data structure provides maximum flexibility for UI implementation to present stored objects to the user. However, a folder hierarchy structure provides a better visual presentation of the stored objects to the MCData user. + +![Diagram of a hierarchical folder structure for a user message storage area.](dcf83796ccf494110638fbd4677b931d_img.jpg) + +The diagram illustrates a hierarchical folder structure for a user message storage area. At the top level, an oval labeled "MCData user 1" is connected to a horizontal line. From this line, four vertical lines descend to four folder icons labeled "Inbox", "Group 1", "Group 2", and "Group N". Below the "Inbox" folder, three overlapping document icons, each labeled "object", are shown. Below the "Group 1" folder, a vertical line descends to a horizontal line, from which two vertical lines descend to two folder icons labeled "Subject 1" and "Subject 2". Below each of these folders, three overlapping document icons, each labeled "object", are shown. Below the "Group 2" folder, a vertical line descends to a single document icon labeled "object". Below the "Group N" folder, a vertical line descends to a horizontal line, from which two vertical lines descend to two folder icons labeled "Date 1" and "Date 2". Below each of these folders, three overlapping document icons, each labeled "object", are shown. + +Diagram of a hierarchical folder structure for a user message storage area. + +**Figure D-1: User message storage area example** + +In figure D-1 the MCData user 1 message storage area in the MCData message store is constructed in folder hierarchical way. A system default folder, Inbox, is configured to receive all new objects coming from active communications. The MCData user 1 creates Group 1, Group 2 and Group N folders to store communication history for different group communications that he is a member of. Once the Group 1 folder is created the MCData user 1 can then move all the objects related to Group 1 communication from the Inbox to the Group 1 folder. The MCData user 1 can also create child folders in Group 1 folder to further divide the stored objects into different groupings such as with different subjects, Subject 1 and Subject 2. Similarly, the MCData user 1 creates child folders, Date 1 and Date 2, in Group N folder to store communication history in group N occurred in different dates. With this hierarchical folder structure, the MCData user 1 can browse his user account in the MCData message store interactively and navigate to the information he would like to see. For example, the MCData user 1 can start with the top-level root folder and traverse down the folder hierarchy to reach to Date 2 folder and see the communication history of group N in that particular date. + +# --- Annex E (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-07 | | | | | | Initial version. | 0.0.0 | +| 2016-08 | | | | | | Update following SA6#12 incorporating the following pCRs:
S6-160810; S6-160875; S6-160876 | 0.1.0 | +| 2016-10 | | | | | | Update following SA6#13 incorporating the following pCRs:
S6-161169; S6-161170; S6-161243; S6-161265; S6-161085; S6-161173; S6-161174; S6-161245; S6-161176; S6-161248; S6-161177; S6-161178; S6-161266; S6-161267; S6-161184 | 0.2.0 | +| 2016-11 | | | | | | Update following SA6#14 incorporating the following pCRs:
S6-161316; S6-161586; S6-161609; S6-161587; S6-161589; S6-161506; S6-161576; S6-161507; S6-161326; S6-161508; S6-161577; S6-161511; S6-161512; S6-161616; S6-161514; S6-161515; S6-161516; S6-161580; S6-161581; S6-161519; S6-161498; S6-161642 | 0.3.0 | +| 2016-11 | SA#74 | SP-160878 | | | | Submitted for Approval at SA#74 | 1.0.0 | +| 2016-12 | SA#74 | SP-160878 | | | | MCC Editorial update for publication after TSG SA approval (SA#74) | 14.0.0 | +| 2017-03 | SA#75 | SP-170071 | 0002 | 2 | F | Alignment of definitions | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0003 | 2 | F | Alignment of group affiliation and de-affiliation requirements | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0004 | 1 | F | Alignment of bearer management | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0005 | 2 | D | Adding descriptive text for the FD procedure section | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0006 | 2 | D | Resolving editor's notes for the short data service feature | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0007 | 1 | D | Adding references for the signalling control plane | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0008 | 2 | D | Adding descriptive text for the transmission and reception control section | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0009 | | F | MCData correction of reference | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0010 | | F | Alignment of business relationships, identities, and application of functional model to deployments | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0011 | 3 | F | file download editorials | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0013 | 1 | F | Off-network conversation management | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0014 | 1 | D | Editorial corrections | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0015 | 1 | F | Resolving EN in Scope | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0016 | 5 | F | Resolving EN in Functional model | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0017 | 1 | F | Resolving EN in SDS procedures | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0018 | | F | Referring generic procedures from CFA | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0020 | 2 | F | Conversation management definitions | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0021 | 2 | F | Disposition alignments and corrections in SDS and FD | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0022 | 1 | F | Tx and Rx control procedure corrections | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0025 | 1 | F | MCData functional model alignment | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0027 | 1 | F | Moving configuration data to on-network only | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0028 | 3 | F | Resolve SDS on-network information flows EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0030 | 1 | F | Resolve FD information flows EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0031 | 2 | F | Adding end-to-end encryption requirements | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0032 | 1 | F | Resolve transmission control information flows EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0033 | 2 | F | Resolve conversation management EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0034 | 1 | F | Addition of definition for MCData ID | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0035 | | F | Addition of definition for MCData ID | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0036 | 3 | F | Off-network information flows for SDS | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0037 | 1 | F | Resolve communication release information flows EN | 14.1.0 | +| 2017-03 | SA#75 | SP-170071 | 0038 | 1 | F | Conditions for using SDS media plane | 14.1.0 | +| 2017-06 | SA#76 | SP-170392 | 0039 | 2 | F | Correction on MCData reference points when using MBMS | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0048 | | D | Additions to Definition and Abbreviations | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0049 | 2 | F | Clarifications to section 5 Architecture requirements | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0051 | 1 | F | Clarifications to section 6.5.1 that SDS Distribution function in MCData server talks to SDS function in MCData client not UE | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0052 | | F | Clarifications to section 6.5.3.1.2 | 14.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2017-06 | SA#76 | SP-170392 | 0054 | 1 | D | Correct wrong reference in section 7.2 | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0056 | 3 | F | Correct the MCData data disposition notification IEs | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0058 | 1 | D | Consistent use of pre-condition in section 7.4.2.2.2 | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0059 | 1 | F | Inconsistent use of MCData group ID or list of recipients in request | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0061 | 3 | F | Content reference URL should be a mandatory IE when uploading a file | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0062 | 5 | F | Addition of new configuration and miscellaneous corrections | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0063 | 5 | F | Addition of identity management server address per group | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0064 | | F | Correction on sending data with mandatory download | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0070 | 2 | F | Inclusion of KMSUri to allow multiple security domains | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0071 | 4 | F | Clarification to Auto-send | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0076 | | F | Corrections to Group configuration data for all MC services | 14.2.0 | +| 2017-06 | SA#76 | SP-170392 | 0078 | 2 | F | CR to 23.282 on Auto-receive | 14.2.0 | +| 2017-06 | SA#76 | SP-170394 | 0040 | 4 | B | Information flow of File Distribution for off-network | 15.0.0 | +| 2017-06 | SA#76 | SP-170394 | 0041 | 1 | B | Functional model of File Distribution for off-network | 15.0.0 | +| 2017-06 | SA#76 | SP-170394 | 0075 | 1 | C | Functional model of File Distribution for off-network | 15.0.0 | +| 2017-09 | SA#76 | SP-170682 | 0079 | 2 | B | Introduction of SDS application type identifiers | 15.1.0 | +| 2017-09 | SA#76 | SP-170685 | 0080 | 1 | B | Addition of IWF and IWF-2 | 15.1.0 | +| 2017-09 | SA#76 | SP-170681 | 0083 | 1 | A | File size check for FD | 15.1.0 | +| 2017-09 | SA#76 | SP-170681 | 0085 | 1 | A | Correction to configuration for Auto-receive parameter | 15.1.0 | +| 2018-01 | SA#78 | SP-170891 | 0087 | 1 | F | SDS location field: Alignment of Stage 2 with Stage 1 & Stage 3 | 15.2.0 | +| 2018-01 | SA#78 | SP-170891 | 0088 | 1 | D | Editorial changes to MCData stage 2 | 15.2.0 | +| 2018-01 | SA#78 | SP-170895 | 0089 | 1 | F | Adding application identifier in media plane SDSs | 15.2.0 | +| 2018-01 | SA#78 | SP-170891 | 0090 | 1 | F | Off-network Conversation Management clarifications | 15.2.0 | +| 2018-01 | SA#78 | SP-170889 | 0094 | 2 | A | PSI configuration for MCData service | 15.2.0 | +| 2018-01 | SA#78 | SP-170891 | 0095 | 1 | F | Completion of Communication Release | 15.2.0 | +| 2018-01 | SA#78 | SP-170894 | 0096 | 1 | F | MBMS packet recovery | 15.2.0 | +| 2018-04 | SA#79 | SP-180148 | 0099 | 1 | A | Correction of security specification references | 15.3.0 | +| 2018-04 | SA#79 | SP-180155 | 0100 | 3 | B | LMR E2EE user profile and group parameters | 15.3.0 | +| 2018-04 | SA#79 | SP-180148 | 0102 | 2 | A | Payload size limit for standalone SDS over signalling control plane | 15.3.0 | +| 2018-04 | SA#79 | SP-180151 | 0103 | 1 | F | Update of references to stage 1 specifications | 15.3.0 | +| 2018-04 | SA#79 | SP-180148 | 0107 | 1 | A | Duplicated procedure name for MCData Group SDS | 15.3.0 | +| 2018-06 | SA#80 | SP-180367 | 0109 | | A | Clarification for presentation priority in MCData UE configuration | 15.4.0 | +| 2018-06 | SA#80 | SP-180370 | 0110 | 3 | A | Modify MCData download data response | 15.4.0 | +| 2018-09 | SA#81 | SP-180677 | 0111 | 2 | C | Media storage function in the MCData server | 16.0.0 | +| 2018-09 | SA#81 | SP-180677 | 0113 | 3 | C | Adding the Network base Message Store | 16.0.0 | +| 2018-12 | SA#82 | SP-181178 | 0116 | 1 | F | Corrections on CR implementation errors | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0117 | 1 | F | Configuration parameters to support requirement [R-6.1.1.2-009] are incorrect | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0118 | 2 | F | Corrections to Table A.2-1, Table A.4-2 and Table A.5-2 | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0119 | 4 | F | Corrections to "Release of MCData communication using HTTP" procedures | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0120 | 1 | F | Alignment with the MCData content server | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0121 | 1 | F | There is no file download when using media plane for FD | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0122 | 2 | B | Procedures for MCData message store operations | 16.1.0 | +| 2018-12 | SA#82 | SP-181178 | 0123 | 1 | F | Correct misalignment on MCData user usage | 16.1.0 | +| 2019-03 | SA#83 | SP-190074 | 0124 | - | F | Correct the location of MCData content server and MCData message store configuration parameters in table A.3-2 configuration table | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0125 | - | D | Editorial correction on the term of MCData | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0126 | 2 | B | Additional architecture requirement for MCData message store | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0127 | 2 | B | Generic SDS procedure with MCData message store | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0128 | 3 | B | Providing data for a user entering an ongoing MCData group conversation | 16.2.0 | +| 2019-03 | SA#83 | SP-190075 | 0130 | 1 | B | MCData user profile migration information | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0131 | 2 | F | Message store object and metadata | 16.2.0 | +| 2019-03 | SA#83 | SP-190075 | 0132 | 1 | B | Introduction of gateway MC server for interconnection | 16.2.0 | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|--------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2019-03 | SA#83 | SP-190074 | 0133 | 2 | B | Example of user storage area with folder hierarchy structure | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0134 | 2 | C | Making data sync between MCData message store and message store client bi-directional | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0135 | 1 | B | Add more operations to the MCData message store | 16.2.0 | +| 2019-03 | SA#83 | SP-190074 | 0136 | 1 | B | Off-network SDS with MCData message store | 16.2.0 | +| 2019-06 | SA#84 | SP-190488 | 0137 | 1 | B | Restricting incoming private communications | 16.3.0 | +| 2019-06 | SA#84 | SP-190486 | 0138 | 2 | B | Interconnection for file distribution | 16.3.0 | +| 2019-06 | SA#84 | SP-190486 | 0139 | 1 | B | Interconnection and migration with message store | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0140 | 2 | B | User configuration for functional alias information query for MCData | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0141 | 1 | B | User requested priority in 23.281 | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0142 | 3 | B | Criteria based automatic group affiliation and deaffiliation | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0143 | 2 | B | MCData configuration for functional alias | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0144 | 4 | B | Functional alias support configuration items | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0145 | 3 | B | Functional alias supplements for the MCData transmission and reception control procedures | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0147 | 2 | B | Functional alias support for Short Data Service (SDS) | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0148 | 3 | B | MC Data User IP connectivity service capability– part 1 Functional Architecture | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0149 | 1 | C | MCData transport capabilities for IP connectivity service | 16.3.0 | +| 2019-06 | SA#84 | SP-190485 | 0150 | 6 | B | MCData File Distribution using the MBMS download delivery method | 16.3.0 | +| 2019-06 | SA#84 | SP-190485 | 0151 | - | C | Remove the procedure in 7.5.2.9 File removal using HTTP by MCData server | 16.3.0 | +| 2019-06 | SA#84 | SP-190485 | 0152 | 2 | F | Remove the duplicated MCData server URI in UE configuration table | 16.3.0 | +| 2019-06 | SA#84 | SP-190485 | 0153 | 3 | F | Add lossless communication to network group configuration and fix missing configuration parameter | 16.3.0 | +| 2019-06 | SA#84 | SP-190485 | 0154 | 2 | F | Resolution proposals for some Editor's Notes | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0155 | | B | MCData client performs automatic activation and deactivation of functional aliases based on location | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0156 | | B | MCData server limits the number of simultaneous successful service authorisations | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0157 | 3 | B | Functional alias support for MCData File Distribution | 16.3.0 | +| 2019-06 | SA#84 | SP-190488 | 0159 | 3 | B | MC Data User IP connectivity service capability– part 2 IP connectivity for Point-to-Point and Group communication | 16.3.0 | +| 2019-09 | SA#85 | SP-190729 | 0161 | 3 | F | Correct the configuration parameters for the MCData emergency alert procedures | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0169 | 1 | F | Fix omission of location services in MCData | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0170 | 2 | B | EPS bearer for emergency | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0171 | 2 | B | Emergency support for one-to-one SDS | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0172 | 2 | B | Emergency and imminent peril support for group SDS | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0173 | 2 | B | Emergency support for off-network SDS | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0174 | 2 | C | Addition of Location information to SDS and Enhance Status | 16.4.0 | +| 2019-09 | SA#85 | SP-190732 | 0177 | 1 | F | Fixing the user profile configuration data for criteria triggered functional alias activation and de-activation | 16.4.0 | +| 2019-09 | SA#85 | SP-190732 | 0178 | | F | Stage 1 requirement reference correction in the user profile data | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0179 | 2 | F | Clarification and corrections to support transmission control | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0180 | 2 | F | Corrections to the transmission and reception control procedures | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0183 | 1 | B | One-to-one SDS Session upgrade to emergency session | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0184 | 1 | B | Group SDS Session upgrade to emergency/imminent-peril session and cancel in-progress emergency/imminent-peril group state | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0185 | 2 | B | One-to-One Emergency MCData FD | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0186 | 1 | B | Group emergency MCData FD | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0187 | 1 | B | One-to-one FD Session upgrade to emergency session | 16.4.0 | +| 2019-09 | SA#85 | SP-190729 | 0188 | 1 | B | Group FD communication upgrade to emergency/imminent-peril communication and cancel in-progress emergency/imminent-peril group state | 16.4.0 | + +| | | | | | | | | +|---------|---------|-----------|------|---|---|------------------------------------------------------------------------------|--------| +| 2019-12 | SA#86 | SP-191108 | 0195 | 2 | F | File repair with the content storage function | 16.5.0 | +| 2020-03 | SA#87-E | SP-200113 | 0203 | 2 | F | Clarification on prepending the MCData content server URI | 16.6.0 | +| 2020-03 | SA#87-E | SP-200113 | 0204 | 1 | F | Local policies at Partner MCData system is not applied | 16.6.0 | +| 2020-03 | SA#87-E | SP-200113 | 0205 | 1 | F | Enhancements and clarifications for file repair and file delivery using MBMS | 16.6.0 | +| 2020-03 | SA#87-E | SP-200113 | 0206 | | F | Correction of internal clause references for Enhanced Status transmission | 16.6.0 | +| 2020-03 | SA#87-E | SP-200113 | 0209 | 1 | F | Corrections to IP Connectivity | 16.6.0 | +| 2020-04 | - | - | - | - | - | Editorial correction adding missing line break in clause 6.6.2 | 16.6.1 | +| 2020-09 | SA#89 | SP-200839 | 0235 | - | F | Removal of content reference IE from FD requests using media plane | 16.7.0 | +| 2020-12 | SA#90-E | SP-200989 | 0244 | 1 | F | Align Annex B with changes to “auto-send” | 16.8.0 | +| 2020-12 | SA#90-E | SP-200989 | 0245 | 2 | F | Correction to the transmission control configuration parameters” | 16.8.0 | +| 2020-12 | SA#90-E | SP-200989 | 0247 | 1 | F | IP connectivity, SDS and FD functional model correction | 16.8.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23283/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23283/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3aff8d7e56b6a5fd99aa51124ed626e8a1b0dd2d --- /dev/null +++ b/marked/Rel-16/23_series/23283/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50f5348855923ea32cbfdaae208f36455869f3dca976b383dc0c76586556ded1 +size 10585 diff --git a/marked/Rel-16/23_series/23283/02d5078b2b1c8b2c1e8374d5dc17aa86_img.jpg b/marked/Rel-16/23_series/23283/02d5078b2b1c8b2c1e8374d5dc17aa86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e6d5c8bee4de4bd85a10f8daf8abb66835b340b --- /dev/null +++ b/marked/Rel-16/23_series/23283/02d5078b2b1c8b2c1e8374d5dc17aa86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e34d4b68a6d0edca20110a8141025536b9f8f8655fc21214ef859df44285455a +size 14637 diff --git a/marked/Rel-16/23_series/23283/04c7ffb4a475a374f52b88704ecd295f_img.jpg b/marked/Rel-16/23_series/23283/04c7ffb4a475a374f52b88704ecd295f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f01a35ad49d69752c8afa316529273e3ddce8a80 --- /dev/null +++ b/marked/Rel-16/23_series/23283/04c7ffb4a475a374f52b88704ecd295f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f10da24e500dd3c929c3a1d10576cef7683b921ba63202f01fba4d05de33cfb +size 23452 diff --git a/marked/Rel-16/23_series/23283/0908107b858fa3783d10d93b3a3444b2_img.jpg b/marked/Rel-16/23_series/23283/0908107b858fa3783d10d93b3a3444b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ee4ddb4c985b2bef6523f9f0209a92f815efd83 --- /dev/null +++ b/marked/Rel-16/23_series/23283/0908107b858fa3783d10d93b3a3444b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f5c21685fc9d0c76815e3cf4e632cc6188cd9e7e1912b45f111a5e5690b5cb9 +size 25868 diff --git a/marked/Rel-16/23_series/23283/09797d4289ec96309d21a9a993153dab_img.jpg b/marked/Rel-16/23_series/23283/09797d4289ec96309d21a9a993153dab_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3b7afc1c6463c34386e0ea2e8e4a544f8a924481 --- /dev/null +++ b/marked/Rel-16/23_series/23283/09797d4289ec96309d21a9a993153dab_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:749c0e816435b6abb0f5df5263b01d01900e2719edd67895da72ac2903a47165 +size 83075 diff --git a/marked/Rel-16/23_series/23283/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg b/marked/Rel-16/23_series/23283/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a02e5006eed9b4aac10841af32532b447213122e --- /dev/null +++ b/marked/Rel-16/23_series/23283/09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:daf7d1367e7854640caa2b87a09565617eb94793b42d060fc2bff9d8f07cc8e7 +size 36690 diff --git a/marked/Rel-16/23_series/23283/0a73b03fba21af142d619a9a662e6490_img.jpg b/marked/Rel-16/23_series/23283/0a73b03fba21af142d619a9a662e6490_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc934e5a3c6abfc9b67ee744bc6d67564d91a94e --- /dev/null +++ b/marked/Rel-16/23_series/23283/0a73b03fba21af142d619a9a662e6490_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:72973bac0ef592a77e802a4894ce08e40cb1937bc93f4cbf260c5e4908753f19 +size 60415 diff --git a/marked/Rel-16/23_series/23283/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-16/23_series/23283/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0a4dc80389f86397d2875796db94908f6341f1e --- /dev/null +++ b/marked/Rel-16/23_series/23283/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b80f492309f01cb1a20dd680cc4cda88b482358bfa832692ed0ce68e2713ec74 +size 58085 diff --git a/marked/Rel-16/23_series/23283/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-16/23_series/23283/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83cda3b552401819b6a7435cb8db72d9aaf8cac5 --- /dev/null +++ b/marked/Rel-16/23_series/23283/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7a6a5e8b7777399d00b32a0d2858cbde7910f8b09349fa8ee2ec505134b921e +size 22511 diff --git a/marked/Rel-16/23_series/23283/1c29dadab94c3fa552d270434db09c81_img.jpg b/marked/Rel-16/23_series/23283/1c29dadab94c3fa552d270434db09c81_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb9fc1354d837f94bdf9e4350faa3a98f7be7903 --- /dev/null +++ b/marked/Rel-16/23_series/23283/1c29dadab94c3fa552d270434db09c81_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11594bdfea6ae47d4063d5dddccef25df551beb5836a1ec460f2a67c19da54d3 +size 13239 diff --git a/marked/Rel-16/23_series/23283/20180217c11e0af84b844796a9c68c6a_img.jpg b/marked/Rel-16/23_series/23283/20180217c11e0af84b844796a9c68c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..086283b697f21644761c6f96fad070d974c61d13 --- /dev/null +++ b/marked/Rel-16/23_series/23283/20180217c11e0af84b844796a9c68c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:468e05ba1caa3fe1e6f8509e8d21a68999f1ab19128b955a9644d7918ed15344 +size 11074 diff --git a/marked/Rel-16/23_series/23283/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23283/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5820575e9d311d3c4c044f6d87b8dd228086ab8f --- /dev/null +++ b/marked/Rel-16/23_series/23283/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6969768fc436b1b5a370c7bbed9225622a9919d436f6e3f6570c5b6edef3d517 +size 38192 diff --git a/marked/Rel-16/23_series/23283/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23283/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..759a221420718bff8287ffbd27d5609b2f2551ed --- /dev/null +++ b/marked/Rel-16/23_series/23283/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5cb7d0ddc6f62420abb4e58d2c42879d0748ba77ff865b275c2dab475f83f5ad +size 13693 diff --git a/marked/Rel-16/23_series/23283/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Rel-16/23_series/23283/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..748062246f720d3d2145f262c45e32feaef04840 --- /dev/null +++ b/marked/Rel-16/23_series/23283/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba5af5fda8ddf7b26180fb928f603d952a72fb1a84735fbc3b5bae887db735e5 +size 31175 diff --git a/marked/Rel-16/23_series/23283/2bcc7de24074ca97717d10c8c4bfe3ba_img.jpg b/marked/Rel-16/23_series/23283/2bcc7de24074ca97717d10c8c4bfe3ba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..656981e59d92647e22bd477f1a403dc96596f1fc --- /dev/null +++ b/marked/Rel-16/23_series/23283/2bcc7de24074ca97717d10c8c4bfe3ba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b706a47fe5f4dc95075fd7a95e4cdb7d1459a6aeb41792eacc6dfc9df33fd663 +size 22557 diff --git a/marked/Rel-16/23_series/23283/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/23_series/23283/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e966c677a58b5adff8f25ed6a435fd17760853ba --- /dev/null +++ b/marked/Rel-16/23_series/23283/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67bf14087ec2cbe8cabb6bbbfbb20df96037d06bb0f127ced9d9f39418c7c106 +size 42128 diff --git a/marked/Rel-16/23_series/23283/2e18ae7359d8c32e96919956f238ecc5_img.jpg b/marked/Rel-16/23_series/23283/2e18ae7359d8c32e96919956f238ecc5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..03ca52a6e3bc7eba3b32f428cde61c5eaccdfa14 --- /dev/null +++ b/marked/Rel-16/23_series/23283/2e18ae7359d8c32e96919956f238ecc5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64f13dc88b0e2a4c797772ae08091c4dcfa9954969a940cd456fb201816908e0 +size 38315 diff --git a/marked/Rel-16/23_series/23283/2e8dcf3d807269a64340a9c292ea7f5d_img.jpg b/marked/Rel-16/23_series/23283/2e8dcf3d807269a64340a9c292ea7f5d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1605a759bae9250cefd24450849203396bfe58f1 --- /dev/null +++ b/marked/Rel-16/23_series/23283/2e8dcf3d807269a64340a9c292ea7f5d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9f00428f559816ebfcf9f3b719d023e47565cb0bc6c5ca54911890b93017a554 +size 23465 diff --git a/marked/Rel-16/23_series/23283/2eb23c2210154279f8013a1594fbcc5a_img.jpg b/marked/Rel-16/23_series/23283/2eb23c2210154279f8013a1594fbcc5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..309206476fefa7f30fe7adab619867c626438068 --- /dev/null +++ b/marked/Rel-16/23_series/23283/2eb23c2210154279f8013a1594fbcc5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e96b6af46b911418cf05197d3774d81fa1602df12638c555ac5f27d7909150a3 +size 20829 diff --git a/marked/Rel-16/23_series/23283/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg b/marked/Rel-16/23_series/23283/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2ba2a729ba1f947636c9f91af6281bcefda5864a --- /dev/null +++ b/marked/Rel-16/23_series/23283/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:394100da62ab6cc57e3536092f996d4fd97d174e790a92f6c5fe95808613b758 +size 78920 diff --git a/marked/Rel-16/23_series/23283/317e0525ef1b2458976c246876f4a948_img.jpg b/marked/Rel-16/23_series/23283/317e0525ef1b2458976c246876f4a948_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..956b10ccf1c2f8cfd0689b8252f4d325663528b9 --- /dev/null +++ b/marked/Rel-16/23_series/23283/317e0525ef1b2458976c246876f4a948_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82760bc82943b69cadd19995a3a0b8be28a0ba7c034251fbe8fa0163a048cfd7 +size 3021 diff --git a/marked/Rel-16/23_series/23283/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23283/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2a4de5e1e02b8fb71d32f78200c4c4ed30bee024 --- /dev/null +++ b/marked/Rel-16/23_series/23283/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e589753195355e1247d5679673974a7900e8ed018dacb326b08f53e72bea6f0 +size 30037 diff --git a/marked/Rel-16/23_series/23283/367378559e35017a5e1a6f5c30798c5a_img.jpg b/marked/Rel-16/23_series/23283/367378559e35017a5e1a6f5c30798c5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5724f53e6277f72c271ce46e5e5895c477021a71 --- /dev/null +++ b/marked/Rel-16/23_series/23283/367378559e35017a5e1a6f5c30798c5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf150495888412950fe38205640443c7809a30d4de46429d52823d0942de84f9 +size 35622 diff --git a/marked/Rel-16/23_series/23283/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-16/23_series/23283/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..62af7045de812e4eb5ff031e41978e6f384487f5 --- /dev/null +++ b/marked/Rel-16/23_series/23283/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed1177b58ee1061e4fea677da14f16b9165129780a070f375ad0eaa555c9dc8b +size 22813 diff --git a/marked/Rel-16/23_series/23283/376f80eb8a41369e87da63a0210d173e_img.jpg b/marked/Rel-16/23_series/23283/376f80eb8a41369e87da63a0210d173e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a2ad4055893f613cabcaaac82227eff488606761 --- /dev/null +++ b/marked/Rel-16/23_series/23283/376f80eb8a41369e87da63a0210d173e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:033a3be3d544dfaa8c97566c4c2275247910591882e699b2eb382f241c56c0e0 +size 18984 diff --git a/marked/Rel-16/23_series/23283/3b8ac904c44dd47c5ccd03def99a19c4_img.jpg b/marked/Rel-16/23_series/23283/3b8ac904c44dd47c5ccd03def99a19c4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7878db6af7e21460f93b6bdcef8088d44d197c98 --- /dev/null +++ b/marked/Rel-16/23_series/23283/3b8ac904c44dd47c5ccd03def99a19c4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba2b468a51b407d432d77a5dc44f13633e3640911360fcea200c101fd1586e63 +size 46351 diff --git a/marked/Rel-16/23_series/23283/3c04b14104f95eb8f7100f6d497d956e_img.jpg b/marked/Rel-16/23_series/23283/3c04b14104f95eb8f7100f6d497d956e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6a92d3b9681925f3e3f7ffbde0092be8e10d5047 --- /dev/null +++ b/marked/Rel-16/23_series/23283/3c04b14104f95eb8f7100f6d497d956e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:12a08b064e63083f652a310b85e775d96893f69008c4cc7004b63aa3b4e04a8c +size 23527 diff --git a/marked/Rel-16/23_series/23283/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg b/marked/Rel-16/23_series/23283/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c1ad54b483f9c3b487f753cdfb5d28cc905764e7 --- /dev/null +++ b/marked/Rel-16/23_series/23283/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf0e263ee3e4c2ced77e5408a121f4a0650a298d6a3acd08a2b514f236956df4 +size 31733 diff --git a/marked/Rel-16/23_series/23283/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/23_series/23283/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22f3e812b09a5fd8e851ab4c02e43e3f3dc335f2 --- /dev/null +++ b/marked/Rel-16/23_series/23283/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d42a25dc026a8e7e1e39847d79c7316a32107d24fe73519cdbeb802e0ea5a0b +size 90647 diff --git a/marked/Rel-16/23_series/23283/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/Rel-16/23_series/23283/43837b056625d3d6ce615e4c02f163bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b2f37e86bc2a8436cb7750cf8f6c611bb2fb8710 --- /dev/null +++ b/marked/Rel-16/23_series/23283/43837b056625d3d6ce615e4c02f163bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:74b1c1851f722b0931a0896445d6d508eaf3b6e77450c505915054e5fed3d3b8 +size 43233 diff --git a/marked/Rel-16/23_series/23283/45578bd3ed11d45af63ce00e28bab2f8_img.jpg b/marked/Rel-16/23_series/23283/45578bd3ed11d45af63ce00e28bab2f8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b1c0a26e0267b7e5ddef2a93a6c201a48303184 --- /dev/null +++ b/marked/Rel-16/23_series/23283/45578bd3ed11d45af63ce00e28bab2f8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ff06d67a27214252cfc1f5614352a701ac4e155e4f1f5526e27d750b2f1ba9b +size 17892 diff --git a/marked/Rel-16/23_series/23283/4a390493f601ce1ac6b9201db4e28b5a_img.jpg b/marked/Rel-16/23_series/23283/4a390493f601ce1ac6b9201db4e28b5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2032254424cebd4fd8c9bfffd5e17915d08872c5 --- /dev/null +++ b/marked/Rel-16/23_series/23283/4a390493f601ce1ac6b9201db4e28b5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b0a4ab6cdc3496616b33d14f59506cd551b2eb466d1b6f05e2d2ae17d3c0655f +size 65402 diff --git a/marked/Rel-16/23_series/23283/4caed5b90277a5c5ee07547bfc8ff884_img.jpg b/marked/Rel-16/23_series/23283/4caed5b90277a5c5ee07547bfc8ff884_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f7d63c96ee9d408988aaa96da3e4b1f9ad71edd --- /dev/null +++ b/marked/Rel-16/23_series/23283/4caed5b90277a5c5ee07547bfc8ff884_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8b897c4288eaf1bba7c51c53a4672f4ab825586b6ec83c28ed9539f4731a967b +size 20359 diff --git a/marked/Rel-16/23_series/23283/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/23_series/23283/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..11a10371e9ee71fd2c79f40b942568d274f372a2 --- /dev/null +++ b/marked/Rel-16/23_series/23283/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb68231e1f227fab6af65306ad1f558344b1e917123fb4b61df5849487d44b78 +size 25728 diff --git a/marked/Rel-16/23_series/23283/4ee2de50739c96fd7bd5a38150ec9c78_img.jpg b/marked/Rel-16/23_series/23283/4ee2de50739c96fd7bd5a38150ec9c78_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d49a07340d0697f9e8dce3103de5d810978de9a0 --- /dev/null +++ b/marked/Rel-16/23_series/23283/4ee2de50739c96fd7bd5a38150ec9c78_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c5366d9517fc9afaf5e5821836c06fb17b6ffb2d0bfdec944886e710a153461 +size 24199 diff --git a/marked/Rel-16/23_series/23283/4f3c8d71b3b182deb469aed61870e3fe_img.jpg b/marked/Rel-16/23_series/23283/4f3c8d71b3b182deb469aed61870e3fe_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb0be9e4f0ac5ffa870b75bcd7c6c2524157d505 --- /dev/null +++ b/marked/Rel-16/23_series/23283/4f3c8d71b3b182deb469aed61870e3fe_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7a947c03705c8c0e26a8805b83f7e91112acc61e5f14a446b2d53dd3b4872d4 +size 38089 diff --git a/marked/Rel-16/23_series/23283/5199d255473623b85726fdb4f67dec8b_img.jpg b/marked/Rel-16/23_series/23283/5199d255473623b85726fdb4f67dec8b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7ed2d8a3f3938ae11405a58d21cffadc5aa57220 --- /dev/null +++ b/marked/Rel-16/23_series/23283/5199d255473623b85726fdb4f67dec8b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea8d3d051ea7613bcd28e96a249133ac25855f11a1ed58b3d8d7eccd88950a5e +size 12057 diff --git a/marked/Rel-16/23_series/23283/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/marked/Rel-16/23_series/23283/575d7d345b3ec04393bb2ec720ebabca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb98e9fbbd62dc14a6407af464628bb1e18b6c24 --- /dev/null +++ b/marked/Rel-16/23_series/23283/575d7d345b3ec04393bb2ec720ebabca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:251f7f98fcaf43a918631a6d873fccc8bc31134015fbd0abefc19ad5940f1704 +size 25952 diff --git a/marked/Rel-16/23_series/23283/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/23_series/23283/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..248285f2cd7bd031151595392922b9aabf99ba56 --- /dev/null +++ b/marked/Rel-16/23_series/23283/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f1e235492af7190c5478462992db7cb934e42284a3d26b68e3d1b8fba1316341 +size 19869 diff --git a/marked/Rel-16/23_series/23283/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg b/marked/Rel-16/23_series/23283/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aec90d73673e3998b9f07ceb74724cc2bc66c93f --- /dev/null +++ b/marked/Rel-16/23_series/23283/5b6e139e89c6ce90107ea7d7d77620a0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:35604684208f41ab7ddefa9854d26dc3924f4ecbb4992a4add55155514a3bdac +size 13505 diff --git a/marked/Rel-16/23_series/23283/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-16/23_series/23283/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ddf5588758dcd3ae86b14653cc067660e7aa035 --- /dev/null +++ b/marked/Rel-16/23_series/23283/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e12293fa9cf9a7d4bb2987c71b8628d606ff1c3d860ad2320069a29f4960628 +size 18104 diff --git a/marked/Rel-16/23_series/23283/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-16/23_series/23283/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2c25bdb358dab1e1b9246d6e6fc20d3463414f9 --- /dev/null +++ b/marked/Rel-16/23_series/23283/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20e737ef14d414e0dfcb8cef7520f5df0ada603cfe753e5e766feb89f80b0e5d +size 38624 diff --git a/marked/Rel-16/23_series/23283/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/23_series/23283/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..486ad4b9412394d199d907cefe2695b4d2930a48 --- /dev/null +++ b/marked/Rel-16/23_series/23283/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3fcd14b65fe14e9feb033b7c207164383d7aaf3385c757a62a8e245842b514b8 +size 18952 diff --git a/marked/Rel-16/23_series/23283/678ac9faaa56bb929499cebeea83a110_img.jpg b/marked/Rel-16/23_series/23283/678ac9faaa56bb929499cebeea83a110_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3eda1e9025d20139dfde91d337faa0376d7d02d4 --- /dev/null +++ b/marked/Rel-16/23_series/23283/678ac9faaa56bb929499cebeea83a110_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:16d6f16c220acfe478e5e9a7550e8548c4f73f0f563c27f50698badb75419e6c +size 37736 diff --git a/marked/Rel-16/23_series/23283/69e5f1993021af230d08c08aac97d9df_img.jpg b/marked/Rel-16/23_series/23283/69e5f1993021af230d08c08aac97d9df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9038542050cfc69347d03e24a34819962656c40 --- /dev/null +++ b/marked/Rel-16/23_series/23283/69e5f1993021af230d08c08aac97d9df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2618bb05c76b1b687e53192232229c634816b196f2e7fd853c7355216494f935 +size 29698 diff --git a/marked/Rel-16/23_series/23283/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-16/23_series/23283/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c6c62ba76178281b03a6086859b92d15b95cf24b --- /dev/null +++ b/marked/Rel-16/23_series/23283/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2179fdb20fc50e161098206312d0024a71d412ba66bf79b5116a191fe924da08 +size 25284 diff --git a/marked/Rel-16/23_series/23283/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg b/marked/Rel-16/23_series/23283/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4eba8e725f25f4f3a56c7908bb38b1d3695c03e3 --- /dev/null +++ b/marked/Rel-16/23_series/23283/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:442b667afad724f2a9f0412f689fdcf03565a64b262e244d63db70329494e208 +size 23463 diff --git a/marked/Rel-16/23_series/23283/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/marked/Rel-16/23_series/23283/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cadc2676b5ab7688598325abaae8d2317080a105 --- /dev/null +++ b/marked/Rel-16/23_series/23283/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:21e00840954135dde5add5416078a5cd3634f907bc33a7fb7820e491f8412ea7 +size 11849 diff --git a/marked/Rel-16/23_series/23283/71f0fd23b2f06b621ba89a65ee3c284c_img.jpg b/marked/Rel-16/23_series/23283/71f0fd23b2f06b621ba89a65ee3c284c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8445423e096f1e6fe0460595b8022ff1ec1ff030 --- /dev/null +++ b/marked/Rel-16/23_series/23283/71f0fd23b2f06b621ba89a65ee3c284c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:df863f3b9a57ba2c031ee930a72fa6d2f1e9ce8d3f684212bbeb848c3c942297 +size 14415 diff --git a/marked/Rel-16/23_series/23283/72d448a65347c51989171748789c7d4b_img.jpg b/marked/Rel-16/23_series/23283/72d448a65347c51989171748789c7d4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..afc85869f3be5521414e0b3ba6692096fba40abd --- /dev/null +++ b/marked/Rel-16/23_series/23283/72d448a65347c51989171748789c7d4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1dc014ec0128b76bb7e6a97610f584ca79987f38ceb5335664ad9fbd86659c2c +size 33105 diff --git a/marked/Rel-16/23_series/23283/742a5484e7dd016256ab99921bbd635d_img.jpg b/marked/Rel-16/23_series/23283/742a5484e7dd016256ab99921bbd635d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37499167cc8903d7400658051b3c6330d847a8c7 --- /dev/null +++ b/marked/Rel-16/23_series/23283/742a5484e7dd016256ab99921bbd635d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5290b69a2bcada396e678f679da16961b8c14538021e49f450f8d164e2dd2a79 +size 21467 diff --git a/marked/Rel-16/23_series/23283/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg b/marked/Rel-16/23_series/23283/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51624f0659206f1e7b338c43f60e7f18ac58e4ce --- /dev/null +++ b/marked/Rel-16/23_series/23283/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea92eb72751d1ebb9373bf6e2fd4681ca2e5ea4d426f58af0882b478b7f8be81 +size 21754 diff --git a/marked/Rel-16/23_series/23283/77b4b155b2bd3a525bbcdb4c10e149df_img.jpg b/marked/Rel-16/23_series/23283/77b4b155b2bd3a525bbcdb4c10e149df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..980944cc160503ffcbeff0bf34868e7b73990f4b --- /dev/null +++ b/marked/Rel-16/23_series/23283/77b4b155b2bd3a525bbcdb4c10e149df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:54a989a7c0f2c5dae7610df6c065e671bad81b4321276484a055189c0fe68e94 +size 21737 diff --git a/marked/Rel-16/23_series/23283/7f663b2f8632236c6e40ca16272d62df_img.jpg b/marked/Rel-16/23_series/23283/7f663b2f8632236c6e40ca16272d62df_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1a99b85146b7d93d777ee06005aee34bbfa4567f --- /dev/null +++ b/marked/Rel-16/23_series/23283/7f663b2f8632236c6e40ca16272d62df_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd586b56a58e37d19f53dc75bad9751c3fa8a6753776f9dd8167fd451476bf7d +size 42139 diff --git a/marked/Rel-16/23_series/23283/854cb86f664ff62fd23e7607cfeb5727_img.jpg b/marked/Rel-16/23_series/23283/854cb86f664ff62fd23e7607cfeb5727_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d089456e56ae4105b2595b2ad370fc9e51b38b8c --- /dev/null +++ b/marked/Rel-16/23_series/23283/854cb86f664ff62fd23e7607cfeb5727_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e789ddcc4b485bea6e7317ead2a4d140282b12ecaccd5943f9d36a4176ba9005 +size 43152 diff --git a/marked/Rel-16/23_series/23283/869856cc90b9ef75b821e64a3de8a39c_img.jpg b/marked/Rel-16/23_series/23283/869856cc90b9ef75b821e64a3de8a39c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c49722c4e2731ccc2cad4c47dff222621f13f1e2 --- /dev/null +++ b/marked/Rel-16/23_series/23283/869856cc90b9ef75b821e64a3de8a39c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:495d3b414b6c9347aa47f085d83d55dbb52c13f98be2fd240ca69a889e539dbc +size 21164 diff --git a/marked/Rel-16/23_series/23283/86e1f8551d4922ea8fa197f96fe4098b_img.jpg b/marked/Rel-16/23_series/23283/86e1f8551d4922ea8fa197f96fe4098b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..552d4a77f7abbee63d574d69cf637044c46e8ef2 --- /dev/null +++ b/marked/Rel-16/23_series/23283/86e1f8551d4922ea8fa197f96fe4098b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:065b245e6bc1ea9e1fb884a54ab77cadf17248ec43e9b20245cbac06fcf6854e +size 44511 diff --git a/marked/Rel-16/23_series/23283/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/marked/Rel-16/23_series/23283/898fb89a50d9ec1dfb4e425c816976a7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72ce891ff959a3d3550bd41004bde0110257a7fa --- /dev/null +++ b/marked/Rel-16/23_series/23283/898fb89a50d9ec1dfb4e425c816976a7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05572d266c4be9ebf826248c522f57f9bdc9fed0755ebc3231a0b1cfc377d39a +size 17283 diff --git a/marked/Rel-16/23_series/23283/8a94796989f4fcba2688c4faa7991538_img.jpg b/marked/Rel-16/23_series/23283/8a94796989f4fcba2688c4faa7991538_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6cc26b26239bfe42cc3b9c972ca61b608f1a577c --- /dev/null +++ b/marked/Rel-16/23_series/23283/8a94796989f4fcba2688c4faa7991538_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:530be648e79a04647fe95c3c0a703e8868c96c7595e6bb7ca4c47f8a7bc8c623 +size 28965 diff --git a/marked/Rel-16/23_series/23283/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/23_series/23283/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b10ed8cf1c98eeb452d0b9114fc6f22b22d7bdc7 --- /dev/null +++ b/marked/Rel-16/23_series/23283/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1885b610409367c1454cec6cd803c3c7695176e2d60b2cb31224685a319de223 +size 38410 diff --git a/marked/Rel-16/23_series/23283/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/23_series/23283/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c339d97afd27d09bd9ae081ebdb31b69a4335aa --- /dev/null +++ b/marked/Rel-16/23_series/23283/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60bfd1a277d20993619fa178331fd05e00dc0b7332a3608a64c687cf17fae309 +size 16536 diff --git a/marked/Rel-16/23_series/23283/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23283/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbe23159d4471bd2c2cf30417359412af80ee003 --- /dev/null +++ b/marked/Rel-16/23_series/23283/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a76e6710645a440527dd57a32699c357738a18c9d2e9aaf57f166291e9a01fc7 +size 49530 diff --git a/marked/Rel-16/23_series/23283/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/marked/Rel-16/23_series/23283/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49623e608a07f8ff9243b133cddf48a1574471d8 --- /dev/null +++ b/marked/Rel-16/23_series/23283/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:40713742e60fd2a399f259ed68a15a5b040ff527ec8cdd33b93da6be8fcb9e2a +size 27027 diff --git a/marked/Rel-16/23_series/23283/a48594f1a3fecef5e047a7c3a63b1220_img.jpg b/marked/Rel-16/23_series/23283/a48594f1a3fecef5e047a7c3a63b1220_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..24ecc284565077ddd08e4c5bd752c466e3c19a94 --- /dev/null +++ b/marked/Rel-16/23_series/23283/a48594f1a3fecef5e047a7c3a63b1220_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fb0dc5f503e1c669aa80306d1c92ab753cff886ea92a9c851564ccd662b6d3c6 +size 21701 diff --git a/marked/Rel-16/23_series/23283/ae0a6916b0794a1bd6cf99034401d857_img.jpg b/marked/Rel-16/23_series/23283/ae0a6916b0794a1bd6cf99034401d857_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a0e7d32045c0ae8adb1f08294898016f6f6b22b --- /dev/null +++ b/marked/Rel-16/23_series/23283/ae0a6916b0794a1bd6cf99034401d857_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:acb5d261dc34cb2751c11594e17cfea6d28b5fabdb6650336a862a02d221e482 +size 18545 diff --git a/marked/Rel-16/23_series/23283/b2a75beaa7e485cd651c2a83b30a4adc_img.jpg b/marked/Rel-16/23_series/23283/b2a75beaa7e485cd651c2a83b30a4adc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..158370872c0ed2ed5d0939e25b6437cb8ced41ef --- /dev/null +++ b/marked/Rel-16/23_series/23283/b2a75beaa7e485cd651c2a83b30a4adc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:31e4ad2754f6764325c495832b7c3e7121a69456d80f6def49a4d84d271f11b9 +size 34348 diff --git a/marked/Rel-16/23_series/23283/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/23_series/23283/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..79ebf6c6e2860185c58e889b6ddca7b43aa93e13 --- /dev/null +++ b/marked/Rel-16/23_series/23283/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:007a20d2acf6122dd235ae1806539de2db2becc9361b622354a5f90bc78c438d +size 13706 diff --git a/marked/Rel-16/23_series/23283/b44a429660cbf47740ee6777db90e34f_img.jpg b/marked/Rel-16/23_series/23283/b44a429660cbf47740ee6777db90e34f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a3b886ca4d2243474404bcc341860d330a7e03ca --- /dev/null +++ b/marked/Rel-16/23_series/23283/b44a429660cbf47740ee6777db90e34f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:59de881e4d093b68651532109da37f2ed9105690941de2f262007dfefb67e0d0 +size 24405 diff --git a/marked/Rel-16/23_series/23283/b49477e8f148b5ef044a2fd5a43528f6_img.jpg b/marked/Rel-16/23_series/23283/b49477e8f148b5ef044a2fd5a43528f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..75b8993b7bab1bceaeaeb75fb73443d954454fe6 --- /dev/null +++ b/marked/Rel-16/23_series/23283/b49477e8f148b5ef044a2fd5a43528f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:647b5bf25e29494482ca73a360d2162c37cdf92a7c2d7f241ae4a4a764c13791 +size 57732 diff --git a/marked/Rel-16/23_series/23283/b71ad9fc874230de9ba4480e12a216f7_img.jpg b/marked/Rel-16/23_series/23283/b71ad9fc874230de9ba4480e12a216f7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ca8a914ce3112823392cbbb03218608230ae0bad --- /dev/null +++ b/marked/Rel-16/23_series/23283/b71ad9fc874230de9ba4480e12a216f7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e16c10e8f997002d4bc533137715ea23d75f2eb67c54cc27c9073fb1cd40c804 +size 31436 diff --git a/marked/Rel-16/23_series/23283/b882c54d92390b4ca523f230e3e07617_img.jpg b/marked/Rel-16/23_series/23283/b882c54d92390b4ca523f230e3e07617_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c9bf070a91101954d1d1a864404d65ce038ccf7c --- /dev/null +++ b/marked/Rel-16/23_series/23283/b882c54d92390b4ca523f230e3e07617_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3abbc2f95ada21d1ef97737b28c7b7a296cff15d376be874771247d04288253e +size 19502 diff --git a/marked/Rel-16/23_series/23283/c2e2b17d61aecbead88a6278e4ba3605_img.jpg b/marked/Rel-16/23_series/23283/c2e2b17d61aecbead88a6278e4ba3605_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c492083b2f548b9c421f1e3b9b4623c19e883c9b --- /dev/null +++ b/marked/Rel-16/23_series/23283/c2e2b17d61aecbead88a6278e4ba3605_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a3084a7e73ddab750d091bf9a5f5a2cfc247625d68a46a025da380ff3bfcc71a +size 25585 diff --git a/marked/Rel-16/23_series/23283/c2f5e14ca0ed0f7944c7606451f67d85_img.jpg b/marked/Rel-16/23_series/23283/c2f5e14ca0ed0f7944c7606451f67d85_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aea21cdafc9ffbc255cdf6d6f9c8b601fdcec0fd --- /dev/null +++ b/marked/Rel-16/23_series/23283/c2f5e14ca0ed0f7944c7606451f67d85_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2488dc4f1703c07a34da11208cbbe3634244d448f5a8727a0519c0860e3b4355 +size 26548 diff --git a/marked/Rel-16/23_series/23283/c71fd22661fbd344a66043940bbd84fc_img.jpg b/marked/Rel-16/23_series/23283/c71fd22661fbd344a66043940bbd84fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67a0cb39e63560d3b4b0ba765674e38a9be9688a --- /dev/null +++ b/marked/Rel-16/23_series/23283/c71fd22661fbd344a66043940bbd84fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f5f7558d001902c04320b95245fa981bc06a383faf975807dfec877f34e04414 +size 28335 diff --git a/marked/Rel-16/23_series/23283/c9bcc9f954279dd8f99cdcb0f41fff4a_img.jpg b/marked/Rel-16/23_series/23283/c9bcc9f954279dd8f99cdcb0f41fff4a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b75671525d36e296ca303dc2658d5b799651e173 --- /dev/null +++ b/marked/Rel-16/23_series/23283/c9bcc9f954279dd8f99cdcb0f41fff4a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ca4c1e62e3cc4034f2d2be3f20ca36750342df5d923641ee1b407355208017d9 +size 28783 diff --git a/marked/Rel-16/23_series/23283/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg b/marked/Rel-16/23_series/23283/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..609227208e4a884cf2f40852dcf7059f587ffe82 --- /dev/null +++ b/marked/Rel-16/23_series/23283/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dde0402f9d515d7d428277d7f2c3436236da3b4ade8851576789c4cc57fc3d32 +size 43669 diff --git a/marked/Rel-16/23_series/23283/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg b/marked/Rel-16/23_series/23283/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb9066abac39d74a82cd53d48e5e658571681192 --- /dev/null +++ b/marked/Rel-16/23_series/23283/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e24d6291481b065a8c31045607c364a29ddd081bbd9649d39bc1979ce91209c0 +size 45130 diff --git a/marked/Rel-16/23_series/23283/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg b/marked/Rel-16/23_series/23283/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4af46e959c4476ce50d6536e79bd5240e2f0d780 --- /dev/null +++ b/marked/Rel-16/23_series/23283/ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8408d8be660bddde2d1efa04459f0f8d902e7af3710733ef59794d5ec295ed3c +size 26609 diff --git a/marked/Rel-16/23_series/23283/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/marked/Rel-16/23_series/23283/da85343976fdbb19f866d9ddbdad0eae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc508d4ec3f49cb5a47a4d8ecc1454a0d9360c0d --- /dev/null +++ b/marked/Rel-16/23_series/23283/da85343976fdbb19f866d9ddbdad0eae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ddf6357ebdd0613120002c9c6fce1c4cde7eb8c497ed36f757358b83ecffbe8b +size 27012 diff --git a/marked/Rel-16/23_series/23283/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/23_series/23283/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0d7ba03264018bc30a3b7e0a7f04495a97fa9aba --- /dev/null +++ b/marked/Rel-16/23_series/23283/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2eb8bed4ef7f184869f8c65300ad7171a9ce123c1daab236f89a9c385a23cde2 +size 61617 diff --git a/marked/Rel-16/23_series/23283/db7a693cf26f527ac6c0d4d41da20858_img.jpg b/marked/Rel-16/23_series/23283/db7a693cf26f527ac6c0d4d41da20858_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f62e9aa8f339aebd53d431e2c209514ba92c6a9 --- /dev/null +++ b/marked/Rel-16/23_series/23283/db7a693cf26f527ac6c0d4d41da20858_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e70c21e2b6a136a413b44c51aa86bce7018881be02776a8af13f7aefb503baae +size 25715 diff --git a/marked/Rel-16/23_series/23283/df94f7807f02e218ee3c66b9cbd829e5_img.jpg b/marked/Rel-16/23_series/23283/df94f7807f02e218ee3c66b9cbd829e5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..49872b4488527ff2b9b9471cae8b53f3e34c0084 --- /dev/null +++ b/marked/Rel-16/23_series/23283/df94f7807f02e218ee3c66b9cbd829e5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0ab1793d5cc1ef0f67d5cce626f97d3524913ca0456e28a5e04108007e13c844 +size 38123 diff --git a/marked/Rel-16/23_series/23283/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-16/23_series/23283/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ea67e337d789e47a43b35d397f2d49aad771f7b4 --- /dev/null +++ b/marked/Rel-16/23_series/23283/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1245770bbb59e7f8cf1dcf5d472f209c25d7fc2fed8b8a5699858af01547eeb4 +size 55589 diff --git a/marked/Rel-16/23_series/23283/e7010c66da16316c2935dfbbef5056b3_img.jpg b/marked/Rel-16/23_series/23283/e7010c66da16316c2935dfbbef5056b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81c8327b3ce6e0c4753b04ccf01535104dc69544 --- /dev/null +++ b/marked/Rel-16/23_series/23283/e7010c66da16316c2935dfbbef5056b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a7f4c095eb8c2a0a10a74c6568ffb99927509f4b93fe4af779d0efeab2f5249 +size 58341 diff --git a/marked/Rel-16/23_series/23283/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Rel-16/23_series/23283/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..723e3be5ae1406506716d3aa0b011ecc05258804 --- /dev/null +++ b/marked/Rel-16/23_series/23283/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d708832ea48e338e24b0cd85f09933fb05b908a608570b2f3cb823bf289aaf3 +size 33573 diff --git a/marked/Rel-16/23_series/23283/f4b570ddd089f54943d46e9f8776f9f9_img.jpg b/marked/Rel-16/23_series/23283/f4b570ddd089f54943d46e9f8776f9f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1089c62986ffa783279bf95fe8a238ba8db4f488 --- /dev/null +++ b/marked/Rel-16/23_series/23283/f4b570ddd089f54943d46e9f8776f9f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77a46eba0f9b8569ab67e711247b0b70acd876689f5cde41c721a3c3f7d61fb7 +size 39023 diff --git a/marked/Rel-16/23_series/23283/f5698523df298c80a0c6b5d4ca657993_img.jpg b/marked/Rel-16/23_series/23283/f5698523df298c80a0c6b5d4ca657993_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bb75dfcd37276cb37c9f66696283b8bfd58893ae --- /dev/null +++ b/marked/Rel-16/23_series/23283/f5698523df298c80a0c6b5d4ca657993_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9817679406bb96999fa26a91bd3ada58769d58b40e22b54127feaf20a27902dd +size 27326 diff --git a/marked/Rel-16/23_series/23283/f64e1e0997695248c0cd4122c5b1a170_img.jpg b/marked/Rel-16/23_series/23283/f64e1e0997695248c0cd4122c5b1a170_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aed359723f2f39a29ee62c8b13636393f8240ecc --- /dev/null +++ b/marked/Rel-16/23_series/23283/f64e1e0997695248c0cd4122c5b1a170_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fc2497c5d64722569a4617e839367bca07fab1a61c84e4b72bfcedc2b36d28b1 +size 10404 diff --git a/marked/Rel-16/23_series/23283/fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg b/marked/Rel-16/23_series/23283/fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..358e82420763fa64fff78250fef4378e2275ebad --- /dev/null +++ b/marked/Rel-16/23_series/23283/fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:088c1dcc99d1f93f888f35f2144612408f629af82a40ddc1abf44959dcd1148c +size 24118 diff --git a/marked/Rel-16/23_series/23283/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23283/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..532d3016b81ee0a4b4d411c63cf91d55de2ee563 --- /dev/null +++ b/marked/Rel-16/23_series/23283/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9c6e9b615a40fa2222e56781e3a9e901b81dc6948a85d50f2de7ab1f4034829f +size 31770 diff --git a/marked/Rel-16/23_series/23283/raw.md b/marked/Rel-16/23_series/23283/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..00a38713bc406b37503bf40d5527dd68285f614c --- /dev/null +++ b/marked/Rel-16/23_series/23283/raw.md @@ -0,0 +1,6362 @@ + + + + +![](317e0525ef1b2458976c246876f4a948_img.jpg) + +--- + +# Contents + +| | | +|------------------------------------------------------------------------------------|----| +| Foreword..... | 9 | +| 1 Scope..... | 10 | +| 2 References..... | 10 | +| 3 Definitions, symbols and abbreviations..... | 10 | +| 3.1 Definitions..... | 10 | +| 3.2 Abbreviations..... | 11 | +| 4 Introduction..... | 11 | +| 5 Assumptions and architectural requirements..... | 11 | +| 5.1 Key management..... | 11 | +| 5.2 Packet format..... | 12 | +| 6 Involved business relationships..... | 12 | +| 7 Functional model..... | 12 | +| 7.1 General..... | 12 | +| 7.2 Functional model description..... | 12 | +| 7.3 Functional entities description..... | 13 | +| 7.3.1 IWF..... | 13 | +| 7.4 Reference points..... | 13 | +| 7.4.1 Reference point IWF-1 (between the IWF and the MCPTT server)..... | 13 | +| 7.4.2 Reference point IWF-2 (between the IWF and the MCData server)..... | 13 | +| 7.4.3 Reference point IWF-3 (between the IWF and the group management server)..... | 14 | +| 8 Identities..... | 14 | +| 8.1 Identity mapping..... | 14 | +| 9 Application of functional model to deployments..... | 14 | +| 10 Procedures and information flows..... | 14 | +| 10.1 Affiliation..... | 14 | +| 10.1.1 Information flows for affiliation..... | 14 | +| 10.1.1.1 General..... | 14 | +| 10.1.1.2 IWF group affiliation request..... | 14 | +| 10.1.1.3 IWF group affiliation response..... | 15 | +| 10.1.1.4 IWF group de-affiliation request..... | 15 | +| 10.1.1.5 IWF group de-affiliation response..... | 15 | +| 10.1.2 Affiliation procedures..... | 16 | +| 10.1.2.1 General..... | 16 | +| 10.1.2.2 Group affiliation to a group defined in the MC system..... | 17 | +| 10.1.2.3 Group de-affiliation from a group defined in the MC system..... | 18 | +| 10.1.2.4 Group affiliation to group defined in the LMR system..... | 19 | +| 10.1.2.5 Group de-affiliation from a group defined in the LMR system..... | 20 | +| 10.2 Group management..... | 21 | +| 10.2.1 Information flows for group management..... | 21 | +| 10.2.1.1 General..... | 21 | +| 10.2.1.2 IWF group regroup teardown notification..... | 21 | +| 10.2.1.3 IWF group regroup teardown notification response..... | 21 | +| 10.2.1.4 IWF group regroup request..... | 21 | +| 10.2.1.5 IWF group regroup response..... | 21 | +| 10.2.1.6 IWF group regroup notification..... | 22 | +| 10.2.1.7 IWF group regroup notification response..... | 22 | +| 10.2.1.8 IWF group information request..... | 22 | +| 10.2.1.9 IWF group information response..... | 22 | +| 10.2.1.10 IWF group information provision request..... | 23 | +| 10.2.1.11 IWF group information provision response..... | 23 | +| 10.2.1.12 IWF group information subscribe request..... | 23 | +| 10.2.1.13 IWF group information subscribe response..... | 23 | + +| | | | +|------------|-------------------------------------------------------------------------------------------------------------------------------------|----| +| 10.2.1.14 | IWF group information notify request..... | 24 | +| 10.2.1.15 | IWF group information notify response..... | 24 | +| 10.2.2 | Group regrouping..... | 24 | +| 10.2.2.1 | General..... | 24 | +| 10.2.2.2 | MC system initiates the group regroup..... | 24 | +| 10.2.2.3 | IWF initiates the group regroup..... | 26 | +| 10.2.2.4 | Ownership of the group regroup..... | 27 | +| 10.2.2.5 | Simultaneous group regroup requests from each side of the IWF-1 interface..... | 27 | +| 10.2.2.6 | Resolution of vocoder and encryption mode for the group regroup..... | 27 | +| 10.2.3 | Group configuration for interworking..... | 27 | +| 10.2.3.1 | Overview..... | 27 | +| 10.2.3.2 | MC system provides group configuration to the IWF..... | 28 | +| 10.2.3.3 | IWF requests group configuration from the MC system..... | 28 | +| 10.2.3.4 | IWF provides group configuration to the MC system..... | 29 | +| 10.2.3.5 | MC system requests group configuration from the IWF..... | 30 | +| 10.2.3.6 | IWF subscribes to group configuration..... | 30 | +| 10.2.3.7 | MC system notifies group configuration..... | 31 | +| 10.2.3.8 | MC system subscribes to group configuration..... | 31 | +| 10.2.3.9 | IWF notifies group configuration..... | 32 | +| 10.3 | Group call..... | 33 | +| 10.3.1 | General..... | 33 | +| 10.3.2 | Information flows for group call over interworking group..... | 33 | +| 10.3.2.1 | General..... | 33 | +| 10.3.2.2 | IWF group call request..... | 33 | +| 10.3.2.3 | IWF group call response (IWF – MCPTT server)..... | 33 | +| 10.3.2.4 | IWF Group-broadcast group call setup request..... | 34 | +| 10.3.2.5 | IWF Group-broadcast group call setup response..... | 34 | +| 10.3.2.6 | IWF Group-broadcast group call release request..... | 34 | +| 10.3.2.7 | IWF group-broadcast group call release response..... | 35 | +| 10.3.2.8 | IWF group join request..... | 35 | +| 10.3.2.9 | IWF group join response..... | 35 | +| 10.3.2.10 | IWF group call leave request..... | 36 | +| 10.3.2.11 | IWF group call leave response..... | 36 | +| 10.3.2.12 | IWF group call release request..... | 36 | +| 10.3.2.13 | IWF group call release response..... | 37 | +| 10.3.2.14 | IWF pre-configured regroup request..... | 37 | +| 10.3.2.15 | IWF pre-configured regroup response..... | 37 | +| 10.3.2.16 | IWF pre-configured regroup cancel request..... | 37 | +| 10.3.2.17 | IWF pre-configured regroup cancel response..... | 38 | +| 10.3.2.18 | IWF pre-configured regroup reject (IWF – MCPTT server, MCPTT server - IWF)..... | 38 | +| 10.3.3 | Pre-arranged group call..... | 38 | +| 10.3.3.1 | General..... | 38 | +| 10.3.3.2 | Group call setup initiated by MCPTT user on an interworking group defined in MCPTT system..... | 39 | +| 10.3.3.3 | Group call setup initiated by LMR user on an interworking group defined in MCPTT system..... | 40 | +| 10.3.3.4 | Group call setup initiated by MCPTT user on an interworking group defined in the LMR system..... | 41 | +| 10.3.3.5 | Group call setup initiated by LMR user on an interworking group defined in the LMR system..... | 43 | +| 10.3.3.6 | Encrypted group call with transcoding..... | 44 | +| 10.3.3.7 | Late Entry..... | 46 | +| 10.3.3.7.1 | General..... | 46 | +| 10.3.3.7.2 | Group call late entry on an interworking group defined in the MCPTT system..... | 46 | +| 10.3.3.7.3 | Group call late entry on an interworking group defined in the LMR system..... | 47 | +| 10.3.3.8 | Interworking group call release..... | 49 | +| 10.3.3.8.1 | General..... | 49 | +| 10.3.3.8.2 | Group call release on an interworking group defined in the MCPTT system..... | 49 | +| 10.3.3.8.3 | Group call release on an interworking group defined in the LMR system..... | 50 | +| 10.3.4 | Group broadcast..... | 51 | +| 10.3.4.1 | General..... | 51 | +| 10.3.4.2 | Group-broadcast group call procedure with an interworking group where the group-broadcast group is defined in the MCPTT system..... | 51 | +| 10.3.4.3 | Group-broadcast group call procedure with an interworking group where the group-broadcast group is defined in the LMR system..... | 54 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------------------------------------------------|----| +| 10.3.4.4 | Group-broadcast group call release with an interworking group procedure where the group-broadcast group is defined in the MCPTT system..... | 56 | +| 10.3.4.5 | Group-broadcast group call release with an interworking group procedure where the group-broadcast group is defined in the LMR system..... | 58 | +| 10.3.4.6 | Broadcast group regroup call using pre-configured group..... | 59 | +| 10.3.4.6.1 | General..... | 59 | +| 10.3.4.6.2 | Broadcast group regroup call using pre-configured group the MCPTT system..... | 59 | +| 10.3.4.6.3 | Broadcast group regroup call using pre-configured group in the IWF..... | 60 | +| 10.3.5 | Chat group call..... | 61 | +| 10.3.5.1 | General..... | 61 | +| 10.3.5.2 | MCPTT user initiated chat group call in an interworking group defined in LMR system..... | 61 | +| 10.3.5.3 | LMR user initiated chat group call in an interworking group defined in MCPTT system..... | 62 | +| 10.3.5.4 | Release chat group call on an interworking group defined in the LMR system..... | 63 | +| 10.3.5.5 | Release chat group call on an interworking group defined in the MCPTT system..... | 64 | +| 10.3.5.6 | void..... | 65 | +| 10.3.5.7 | void..... | 65 | +| 10.3.5.8 | Newly joined MCPTT group member of a group defined in the LMR system..... | 65 | +| 10.3.5.9 | Newly joined LMR group member of a group defined in the MCPTT system..... | 66 | +| 10.3.5.10 | MCPTT client returning to coverage on a group homed in the LMR system..... | 67 | +| 10.3.6 | Exiting group call due to de-affiliation..... | 68 | +| 10.3.6.1 | General..... | 68 | +| 10.3.6.2 | Exiting group call defined in the LMR system due to de-affiliation..... | 68 | +| 10.3.6.3 | Exiting group call defined in the MCPTT system due to de-affiliation..... | 69 | +| 10.3.7 | Group regroup with pre-configured group..... | 70 | +| 10.3.7.1 | General..... | 70 | +| 10.3.7.2 | Regroup formation using pre-configured group..... | 71 | +| 10.3.7.2.1 | Regroup formation using pre-configured group initiated in the MCPTT system..... | 71 | +| 10.3.7.2.2 | Regroup formation using pre-configured group initiated in the IWF..... | 73 | +| 10.3.7.3 | Regroup cancellation using pre-configured group regroup..... | 74 | +| 10.3.7.3.1 | Regroup cancellation using pre-configured group initiated in the MCPTT system..... | 74 | +| 10.3.7.3.2 | Regroup cancellation using pre-configured group initiated in the IWF..... | 75 | +| 10.3.7.4 | Regroup rejection using pre-configured group..... | 76 | +| 10.3.7.4.1 | Regroup rejection using pre-configured group for regroup initiated in the MCPTT system..... | 76 | +| 10.3.7.4.2 | Regroup rejection using pre-configured group for regroup initiated in the IWF..... | 77 | +| 10.3.7.5 | Pre-configured regroup update procedures..... | 78 | +| 10.3.7.5.1 | MCPTT client PTTs on MCPTT group during an in-progress pre-configured group regroup..... | 78 | +| 10.3.7.6 | Call request on pre-configured regroup group after group regroup has been cancelled..... | 80 | +| 10.3.7.6.1 | MCPTT client PTTs on pre-configured regroup group after group regroup has been cancelled..... | 80 | +| 10.3.7.7 | Adding newly affiliated user to a pre-configured group regroup..... | 81 | +| 10.3.7.7.1 | Adding newly affiliated MCPTT user to a pre-configured group regroup..... | 81 | +| 10.3.7.7.2 | Adding newly affiliated user homed in the IWF to a pre-configured group regroup..... | 82 | +| 10.3.8 | User regroup with pre-configured group..... | 82 | +| 10.3.8.1 | General..... | 82 | +| 10.3.8.2 | Pre-configured user regroup formation..... | 83 | +| 10.3.8.2.1 | Pre-configured user regroup formation by the MCPTT system..... | 83 | +| 10.3.8.2.2 | Pre-configured user regroup formation by the IWF..... | 85 | +| 10.3.8.3 | Pre-configured user regroup cancellation..... | 86 | +| 10.3.8.3.1 | Pre-configured user regroup cancellation by the MCPTT system..... | 86 | +| 10.3.8.3.2 | Pre-configured user regroup cancellation by the IWF..... | 87 | +| 10.4 | Private call..... | 87 | +| 10.4.1 | Information flows for private calls..... | 87 | +| 10.4.1.1 | General..... | 87 | +| 10.4.1.2 | IWF private call request..... | 88 | +| 10.4.1.3 | IWF private call response..... | 88 | +| 10.4.1.4 | IWF ringing..... | 89 | +| 10.4.1.5 | IWF call end request..... | 89 | +| 10.4.1.6 | IWF call end response..... | 89 | +| 10.4.2 | Private call setup in automatic commencement mode..... | 89 | +| 10.4.2.1 | MCPTT user initiating an MCPTT private call..... | 89 | +| 10.4.2.2 | LMR user initiating a private call with MCPTT user..... | 91 | +| 10.4.3 | Private call setup in manual commencement mode..... | 92 | + +| | | | +|------------|----------------------------------------------------------------------------------------------------------------------------|-----| +| 10.4.3.1 | MCPTT user is initiating an MCPTT private call..... | 92 | +| 10.4.3.2 | LMR user initiating a private call with MCPTT user..... | 94 | +| 10.4.4 | Private call release..... | 96 | +| 10.4.4.1 | MCPTT client initiated..... | 96 | +| 10.4.4.2 | MCPTT server initiated..... | 97 | +| 10.4.4.3 | LMR user initiated..... | 98 | +| 10.4.5 | Encryption of private calls..... | 99 | +| 10.5 | Floor control..... | 99 | +| 10.5.1 | General..... | 99 | +| 10.5.2 | Information flows for floor control..... | 99 | +| 10.5.2.1 | General..... | 99 | +| 10.5.2.2 | IWF floor request..... | 99 | +| 10.5.2.3 | IWF floor granted..... | 100 | +| 10.5.2.4 | IWF floor rejected..... | 100 | +| 10.5.2.5 | IWF floor request cancel..... | 100 | +| 10.5.2.6 | IWF floor request cancel response..... | 100 | +| 10.5.2.7 | IWF floor request cancel notify..... | 101 | +| 10.5.2.8 | IWF floor idle..... | 101 | +| 10.5.2.9 | IWF floor release..... | 101 | +| 10.5.2.10 | IWF floor taken..... | 102 | +| 10.5.2.11 | IWF floor revoked..... | 102 | +| 10.5.2.12 | IWF floor acknowledgement..... | 102 | +| 10.5.2.13 | IWF queue position request..... | 102 | +| 10.5.2.14 | IWF queue position info..... | 103 | +| 10.5.2.15 | IWF unicast media stop request..... | 103 | +| 10.5.2.16 | IWF unicast media resume request..... | 103 | +| 10.5.2.17 | IWF floor talker ID update..... | 104 | +| 10.5.3 | Interworking floor control..... | 104 | +| 10.5.4 | Floor override without using floor revoked on an interworking group..... | 104 | +| 10.5.5 | Floor control on an interworking group homed in the LMR system..... | 106 | +| 10.5.6 | Floor control on an interworking group homed in the MCPTT system..... | 107 | +| 10.5.7 | Floor control without local filtering on an interworking group defined in the LMR system..... | 109 | +| 10.5.8 | Floor control without local filtering on an interworking group defined in the MCPTT system..... | 110 | +| 10.5.9 | Floor control in private call controlled by the LMR system..... | 112 | +| 10.5.10 | Floor control in private call controlled by the MCPTT system..... | 113 | +| 10.6 | Emergency and imminent peril..... | 114 | +| 10.6.1 | Information flows for emergency and imminent peril..... | 114 | +| 10.6.1.1 | IWF emergency group call request..... | 114 | +| 10.6.1.2 | IWF emergency group call response..... | 114 | +| 10.6.1.3 | IWF imminent peril group call request..... | 114 | +| 10.6.1.4 | IWF imminent peril group call response..... | 115 | +| 10.6.1.5 | IWF in-progress imminent peril group state cancel request..... | 115 | +| 10.6.1.6 | IWF in-progress imminent peril group state cancel response..... | 115 | +| 10.6.1.7 | IWF emergency alert request..... | 116 | +| 10.6.1.8 | IWF emergency alert response..... | 116 | +| 10.6.1.9 | IWF emergency alert cancel request..... | 116 | +| 10.6.1.10 | IWF emergency alert cancel response..... | 116 | +| 10.6.1.11 | IWF in-progress emergency group state cancel request..... | 117 | +| 10.6.1.12 | IWF in-progress emergency group state cancel response..... | 117 | +| 10.6.2 | Emergency calls..... | 117 | +| 10.6.2.1 | General..... | 117 | +| 10.6.2.2 | Emergency group call..... | 118 | +| 10.6.2.2.1 | Emergency group call setup initiated by a user in the LMR system on an interworking group defined in the MCPTT system..... | 118 | +| 10.6.2.2.2 | Emergency group call setup initiated by a user in the MCPTT system on an interworking group defined in MCPTT system..... | 119 | +| 10.6.2.2.3 | Emergency group call setup initiated by a user in the LMR system on an interworking group defined in the LMR system..... | 121 | +| 10.6.2.2.4 | Emergency group call setup initiated by a user in the MCPTT system to an interworking group defined in the LMR system..... | 122 | +| 10.6.2.3 | In-progress emergency group state cancel of an interworking group..... | 124 | + +| | | | +|------------|-------------------------------------------------------------------------------------------------------------------------|-----| +| 10.6.2.3.1 | LMR user initiated in-progress emergency group state cancel of an interworking group defined in the MCPTT system..... | 124 | +| 10.6.2.3.2 | MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in the MCPTT system..... | 125 | +| 10.6.2.3.3 | LMR user initiated in-progress emergency group state cancel of an interworking group defined in an LMR system..... | 126 | +| 10.6.2.3.4 | MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in an LMR system..... | 127 | +| 10.6.2.4 | Losing audio..... | 129 | +| 10.6.2.5 | Default emergency group..... | 129 | +| 10.6.2.6 | Emergency private call..... | 129 | +| 10.6.2.7 | LMR systems that do not track group emergencies..... | 129 | +| 10.6.3 | Imminent peril calls..... | 129 | +| 10.6.3.1 | General..... | 129 | +| 10.6.3.2 | Imminent peril group call initiated by an MCPTT user on an interworking group..... | 129 | +| 10.6.3.3 | Group call initiated by a user in the LMR system on an interworking group in imminent peril state..... | 131 | +| 10.6.3.4 | In-progress imminent peril state cancel on an interworking group..... | 133 | +| 10.6.4 | Emergency alerts..... | 135 | +| 10.6.4.1 | Emergency alert initiated by LMR user..... | 135 | +| 10.6.4.2 | Emergency alert initiated by MC service user..... | 136 | +| 10.6.5 | Emergency alert cancellation..... | 138 | +| 10.6.5.1 | Emergency alert cancellation of an LMR user..... | 138 | +| 10.6.5.2 | Emergency alert cancellation of an MC service user..... | 139 | +| 10.7 | Codec..... | 141 | +| 10.7.1 | Information flows for codec..... | 141 | +| 10.7.1.1 | IWF codec reconciliation request..... | 141 | +| 10.7.1.2 | IWF codec reconciliation response..... | 141 | +| 10.7.2 | IWF transcoding..... | 141 | +| 10.7.3 | Codec negotiation by the LMR system..... | 141 | +| 10.7.3.1 | Description..... | 141 | +| 10.8 | MCDATA short data service..... | 142 | +| 10.8.1 | General..... | 142 | +| 10.8.2 | Information flows for the short data service..... | 143 | +| 10.8.2.1 | General..... | 143 | +| 10.8.2.2 | IWF MCDATA standalone data request..... | 143 | +| 10.8.2.3 | IWF MCDATA data disposition notification..... | 143 | +| 10.8.2.4 | IWF MCDATA group standalone data request (IWF – MCDATA server)..... | 143 | +| 10.8.2.5 | IWF MCDATA group standalone data request (MCDATA server - IWF)..... | 144 | +| 10.8.2.6 | IWF MCDATA data disposition notification(s) (MCDATA server to IWF)..... | 144 | +| 10.8.2.7 | IWF MCDATA group standalone data request (IWF – MCDATA server)..... | 145 | +| 10.8.2.8 | IWF MCDATA group standalone data request (MCDATA server – IWF)..... | 145 | +| 10.8.2.9 | IWF MCDATA group standalone data response..... | 146 | +| 10.8.3 | Behaviour at the MCDATA Client..... | 146 | +| 10.8.4 | Behaviour at the IWF..... | 146 | +| 10.8.5 | Behaviour at the MCDATA server..... | 146 | +| 10.8.6 | MCDATA user one-to-one SDS request to an LMR user..... | 146 | +| 10.8.6.1 | Signalling control plane..... | 146 | +| 10.8.6.2 | Media plane..... | 147 | +| 10.8.7 | LMR user one-to-one SDS request to an MCDATA user..... | 147 | +| 10.8.7.1 | Signalling control plane..... | 147 | +| 10.8.7.2 | Media plane..... | 147 | +| 10.8.8 | MCDATA user group SDS request to an MCDATA group including LMR users..... | 147 | +| 10.8.8.1 | Signalling control plane..... | 147 | +| 10.8.8.2 | Media plane..... | 147 | +| 10.8.9 | LMR user group SDS request to an MCDATA group..... | 147 | +| 10.8.9.1 | Signalling control plane..... | 147 | +| 10.8.9.2 | Media plane..... | 148 | +| 10.9 | IWF as a security gateway..... | 148 | +| 10.9.1 | Support for transcoding with encrypted speech..... | 148 | +| 10.10 | Simultaneous interworked calls (on-network)..... | 148 | + +| | | | +|------------------------|---------------------------------------------------------------------------------------------------------------------|-----| +| 10.10.1 | General..... | 148 | +| 10.11 | Location..... | 148 | +| 10.11.1 | Location of current talker..... | 148 | +| 10.11.2 | Location of current talker (MCPTT server to IWF)..... | 148 | +| 10.11.3 | Location of current talker (IWF to MCPTT server)..... | 149 | +| 10.12 | LMR security transport..... | 150 | +| 10.12.1 | Information flows for LMR security transport..... | 150 | +| 10.12.1.1 | Non-3GPP security message request..... | 150 | +| 10.12.1.2 | Non-3GPP security message response..... | 151 | +| 10.12.2 | LMR key management messages..... | 151 | +| 10.12.2.1 | General..... | 151 | +| 10.12.2.2 | MC service client initiated..... | 151 | +| 10.12.2.3 | IWF initiated..... | 151 | +| 10.13 | Analogue FM/TIA-603-D and other legacy LMR interworking..... | 152 | +| 10.13.1 | General..... | 152 | +| 10.13.2 | Interworking Concepts..... | 152 | +| 10.13.3 | Procedures..... | 153 | +| 10.13.3.1 | Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system..... | 154 | +| 10.13.3.2 | Group call with talker ID update initiated by an LMR user on an interworking group defined in the LMR system..... | 156 | +| 10.14 | IWF functional alias management..... | 158 | +| 10.15 | Enhanced status..... | 158 | +| 10.15.1 | General..... | 158 | +| 10.15.2 | Preset values for enhanced status..... | 158 | +| 10.15.3 | Enhanced status for on-network..... | 158 | +| 10.15.3.1 | Procedure (MCData to IWF)..... | 158 | +| 10.15.3.2 | Procedure (IWF to MCData)..... | 158 | +| Annex A (informative): | Change history..... | 159 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# 1 Scope + +The objective of this technical specification is to specify interworking between MC systems and LMR systems that satisfy the MCPTT requirements in 3GPP TS 22.179 [3], MCCoRe requirements in 3GPP TS 22.280 [2] and the MCData requirements (SDS only) in 3GPP TS 22.282 [4]. + +The present document refers to an InterWorking Function (IWF). The structure and functionality of the IWF is out of scope of the present document. The definition of reference points between the IWF and MC systems and the interactions between the IWF and MC systems are in scope of the present document. + +# 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.280: "Mission Critical Services Common Requirements (MCCoRe); Stage 1". +- [3] 3GPP TS 22.179: "Mission Critical Push to Talk (MCPTT); Stage 1". +- [4] 3GPP TS 22.282: "Mission Critical Data services". +- [5] 3GPP TS 23.280: "Common functional architecture to support mission critical services; Stage 2". +- [6] 3GPP TS 23.282: "Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2". +- [7] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2". +- [8] 3GPP TS 33.180: "Security of the mission critical service" +- [9] TTA-603-D: "Land Mobile FM or PM Communications Equipment Measurement and Performance Standards". + +# 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +**End-to-End Encryption:** encryption that is applied by an originating terminal or client and is decrypted only by chosen terminating terminals or clients. + +**User homed in the IWF:** is an MC service ID that represents an LMR user in the MC system. + +**Interworking:** a means of communication between mission critical systems and LMR systems whereby MC users obtaining service from a mission critical system can communicate with LMR users who are obtaining service from one or more LMR systems. + +**Interworking function:** adapts LMR Systems to mission critical systems via the IWF interface and supports interworking between LMR systems and mission critical systems. + +**Interworking group:** a group, which is composed of group members from the MC system and the LMR system and defined in the MC system or the LMR system. + +**LMR system:** the collection of applications, services, and enabling capabilities providing a land mobile radio service offering group and private communications. + +**LMR user:** a user of a device which allows participation in an LMR system. + +NOTE: The term LMR user is defined for discussion purposes only and is out of scope of the present document. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +| | | +|-------|-------------------------------------| +| E2EE | End-to-End Encryption | +| IWF | InterWorking Function | +| KEK | Key Encryption Key (TETRA) | +| KMS | Key Management Service | +| MC | Mission Critical | +| MCPTT | Mission Critical Push To Talk | +| LMR | Land Mobile Radio | +| OTAK | Over-The-Air-Key Management (TETRA) | +| OTAR | Over-The-Air Rekeying (P25) | +| P25 | Project 25 | +| SDS | Short Data Service | +| TETRA | TERrestrial Trunked Radio | +| UE | User Equipment | +| UKEK | Unique Key Encryption Key (P25) | +| URI | Uniform Resource Identifier | + +--- + +## 4 Introduction + +Mission critical users currently employ a wide range of LMR mission critical Push To Talk services, and associated data capabilities where available. + +The present document describes the architecture to support the interworking between the MC system and the LMR system to satisfy interworking requirements specified in 3GPP TS 22.179 [3] and 3GPP TS 22.282 [4]. Other LMR technologies may interwork as long as they conform to the present document. + +The IWF, along with its LMR system, will appear as a peer interconnected MC system. This is meant as an approach for defining interactions on the IWF interface but is not intended to specify the functionality of the IWF nor meant to mandate a deployment model. + +--- + +## 5 Assumptions and architectural requirements + +### 5.1 Key management + +Interworking requirements for key management for encrypted interworking include: + +- a) a mechanism to securely (i.e. authenticity, integrity, confidentiality) share an LMR E2EE traffic key for a private call sessions between a party in an MCPTT system and a party in the LMR system; + +- b) a mechanism to securely convey to group members, the LMR E2EE key or set of LMR E2EE keys associated with an MC service group or set of MC service groups, to be used for encryption of interworking group calls spanning the multiple systems; +- c) a mechanism to securely share with temporary group members in MC systems, the LMR E2EE key(s) associated with a temporary MC service group to be used in interworking group calls spanning the multiple systems; +- d) key management solutions shall not preclude the ability of an IWF to allow one or more individual Mission Critical Organizations from having sole control over and sole access to LMR E2EE traffic keys used for the entity's media traffic and users' key encryption keys (UKEKs or KEKs); +- e) key management solutions shall support the ability of the IWF to decrypt/reencrypt the media traffic for zero or more groups; and, +- f) for deployments where Mission Critical Organizations wish to use LMR E2EE mechanisms when interworking with LMR users: + - i) a mechanism to securely provision an MC service client with the user's UKEK or KEK; and, + - ii) a mechanism to convey LMR OTAR or OTAK message contents. + +## 5.2 Packet format + +Each LMR technology defines its own packet format for voice media transmission. For interworking sessions, there might be cases where LMR formatted media is required to be transferred between the IWF and LMR aware MCPTT clients. An example of such a case is where E2EE is used and thus the IWF is not able to decrypt the media. In such cases, media that is sent over the IWF-1 interface needs to be routed within MCPTT systems to/from LMR aware MCPTT clients using methods described in 3GPP TS 23.379 [7]. + +Requirements for media transmission across the IWF-1 interface include: + +- a) media transmission to carry the LMR formatted media between the IWF and LMR aware MCPTT clients; and +- b) the MCPTT system, along with the IWF, may choose to encrypt the LMR formatted media using 3GPP mechanisms. + +NOTE: The contents of the LMR formatted media is out of scope of the present document. + +--- + +## 6 Involved business relationships + +No business relationships have been identified. + +--- + +## 7 Functional model + +### 7.1 General + +### 7.2 Functional model description + +Figure 7.2-1 shows the functional model for the application plane for interworking between MC systems and LMR systems. Functional entities and interfaces depicted on the right-hand side of the IWF-x interfaces are defined in 3GPP TS 23.280 [5], 3GPP TS 23.379 [7], and 3GPP TS 23.282 [6]. + +![Sequence diagram showing the functional model for application plane for interworking between IWF, MCPTT server, and MCPTT client.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +``` +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client as MCPTT client + Note right of MCPTT_client: user + IWF->>MCPTT_server: 1. IWF pre-configured regroup request + MCPTT_server->>MCPTT_client: 2. Pre-configured regroup request + MCPTT_client->>user: 3. Notify + user-->>MCPTT_server: 4. Pre-configured regroup response + MCPTT_server->>IWF: 5. Preconfigured regroup response +``` + +The diagram illustrates a sequence of interactions between three main entities: IWF, MCPTT server, and MCPTT client. The sequence starts with the IWF sending a '1. IWF pre-configured regroup request' to the MCPTT server. The MCPTT server then sends a '2. Pre-configured regroup request' to the MCPTT client. The MCPTT client sends a '3. Notify' message to a 'user' entity. The user then sends a '4. Pre-configured regroup response' back to the MCPTT server. Finally, the MCPTT server sends a '5. Preconfigured regroup response' back to the IWF. + +Sequence diagram showing the functional model for application plane for interworking between IWF, MCPTT server, and MCPTT client. + +Figure 7.2-1: Functional model for application plane for interworking + +## 7.3 Functional entities description + +### 7.3.1 IWF + +The IWF supports most of the functionality of peer MCPTT and MCData systems, with some differences, as specified in the present document. The IWF supports any necessary protocol translation and identity mapping between the MC systems and the IWF. The internal function of the IWF is out of scope of the present document. + +## 7.4 Reference points + +### 7.4.1 Reference point IWF-1 (between the IWF and the MCPTT server) + +The IWF-1 reference point, which exists between the IWF and the MCPTT server, provides peer to peer interconnection between an LMR system and the MCPTT system. IWF-1 supports a subset of MCPTT-3 as defined in 3GPP TS 23.379 [7], with some differences, as specified in the present document. The IWF-1 interface is supported by the same signalling plane protocol(s) as defined for MCPTT-3 except as specified in the present document. + +### 7.4.2 Reference point IWF-2 (between the IWF and the MCData server) + +The IWF-2 reference point, which exists between the IWF and the MCData server, provides SDS interconnection between an LMR system and the MCData system. IWF-2 supports a subset of the functionality of MCData-SDS-1 and MCData-SDS-2, as defined in 3GPP TS 23.282 [6] with some differences, as specified in the present document. The IWF-2 interface is supported by the same signalling plane protocol(s) as defined for MCData-3 except as specified in the present document. + +### 7.4.3 Reference point IWF-3 (between the IWF and the group management server) + +The IWF-3 reference point, which exists between the IWF and the group management server, provides group management interconnection between an LMR system and the MC service system. IWF-3 is based upon CSC-16, as defined in 3GPP TS 23.280 [5] with some differences, as specified in the present document. + +--- + +## 8 Identities + +### 8.1 Identity mapping + +The IWF provides centralised support for interworking between an MCPTT or MCData system and an LMR system. In MCPTT systems, the identity of an LMR user is provided as an MCPTT ID, and the identity of an LMR group is provided as an MCPTT group ID, which can be used by the IWF to derive the corresponding identities used in an LMR system. Similarly, in MCData systems, the identity of an LMR user is provided as an MCData ID, and the identity of an LMR group is provided as an MCData group ID, which can be used by the IWF to derive the corresponding identities used in an LMR system. + +Identities provided on IWF-x reference points are described in clause 8 of 3GPP TS 23.280 [5]. + +The IWF can perform the identity mapping between an MCPTT system or MCData system and an LMR system during exchange of signalling and media messages. + +The assignment of a functional alias that belongs to the MC system to a user homed in the IWF enables the mapping to corresponding role-based addressing schemes applicable in the LMR system. + +--- + +## 9 Application of functional model to deployments + +No applications of functional model to deployments have been identified. + +--- + +## 10 Procedures and information flows + +### 10.1 Affiliation + +#### 10.1.1 Information flows for affiliation + +##### 10.1.1.1 General + +The following subclauses define information flows for affiliation on the IWF-1 interface. Affiliation related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.280 [5]. + +##### 10.1.1.2 IWF group affiliation request + +Table 10.1.1.2-1 describes the information flow IWF group affiliation request between the IWF and an MC service server and between an MC service server and the IWF. + +**Table 10.1.1.2-1: IWF group affiliation request** + +| Information element | Status | Description | +|--------------------------|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator (LMR user or MC service user) who triggers the MC service group affiliation request. (see NOTE) | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to affiliate and is defined in the destination MC service system. | +| MC service type | M | The type(s) of service(s) for which the request is intended (e.g. MCData or MCPTT or both) | +| NOTE: | The IWF is configured with an MC service ID for use when the IWF is affiliating itself to the group on behalf of the LMR system. | | + +### 10.1.1.3 IWF group affiliation response + +Table 10.1.1.3-1 describes the information flow IWF group affiliation response between the IWF and an MC service server and between an MC service server and the IWF. + +**Table 10.1.1.3-1: IWF group affiliation response** + +| Information element | Status | Description | +|--------------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator (LMR user or MC service user) who triggered the MC service group affiliation request. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to affiliate and is defined in the destination MC service system. | +| Affiliation status per MC service group ID | M | Indicates the affiliation result for every MC service group ID in the list. | + +### 10.1.1.4 IWF group de-affiliation request + +Table 10.1.1.4-1 describes the information flow IWF group de-affiliation request between the IWF and an MC service server and between an MC service server and the IWF. + +**Table 10.1.1.4-1: IWF group de-affiliation request** + +| Information element | Status | Description | +|--------------------------|--------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator (LMR user or MC service user) who triggers the MC service group de-affiliation request. (see NOTE) | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to de-affiliate. | +| MC service type | M | The type(s) of service(s) for which the request is intended (e.g. MCData or MCPTT or both) | +| NOTE: | The IWF is configured with an MC service ID for use when the IWF is de-affiliating from the group on behalf of the LMR system. | | + +### 10.1.1.5 IWF group de-affiliation response + +Table 10.1.1.5-1 describes the information flow IWF group de-affiliation response between the IWF and an MC service server and between an MC service server and the IWF. + +**Table 10.1.1.5-1: IWF group de-affiliation response** + +| Information element | Status | Description | +|-----------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------| +| MC service ID | M | The MC service ID of the originator (LMR user or MC service user) who triggers the MC service group de-affiliation request. | +| MC service group ID list | M | A list of one or more MC service group IDs to which the originator intends to de-affiliate. | +| De-affiliation status per MC service group ID | M | Indicates the de-affiliation result for every MC service group ID in the list. | + +## 10.1.2 Affiliation procedures + +### 10.1.2.1 General + +When an interworking group is defined in the MCPTT system, the LMR system (via the IWF) informs the MCPTT system of group affiliations in one of the following ways: + +- Every group affiliation in the LMR system results in an affiliation sent to the MCPTT system, which contains the identity (with appropriate translation by the IWF) of the affiliating group member; or +- A group affiliation is sent on behalf of the group's LMR users (via the IWF) to the MCPTT system when the first group member affiliates to the designated group in the LMR system, and a group de-affiliation is sent on behalf of the group's LMR users (via the IWF) to the MCPTT system when the last group member de-affiliates, and no other group affiliation signalling is sent. + +The first and second options may be used at the same time, such that some group members may explicitly affiliate while the IWF may affiliate on behalf of other group members. + +In the second option, when the IWF is configured to affiliate on behalf of the group's LMR members then: + +- the group list in the MCPTT system contains the IWF's MCPTT ID. This ID is recognized (through configuration) as having the ability to affiliate on behalf of the group's LMR users associated with this IWF; +- the IWF affiliates with its MCPTT ID to the group defined in the MCPTT system; +- the MCPTT system recognizes the affiliation as being from an IWF on behalf of the group's LMR users; +- when the IWF has affiliated to the group, the MCPTT system: + - considers any LMR user associated with the IWF to be affiliated to the group on which the IWF has affiliated. The IWF's users need not be listed ahead of time in the group list for this group in the MCPTT system; + - allows requests such as call setup or floor request, from MCPTT IDs representing LMR users associated with the IWF for actions on the group to which the IWF has affiliated; + - does not carry out an additional affiliation on behalf of LMR users when those users make call requests, and therefore does not send additional messages to those users (e.g. release messages to both the IWF affiliated identity and the LMR user identity performing the action), via the IWF, during call processing; + - recognizes which LMR users are associated with the IWF because their MCPTT IDs belong to the same system as the IWF; and, + - uses special rules for the IWF for limits such as "Limitation of number of affiliations per user (N2)". +- requests from LMR users to the MCPTT system are identified with their individual MCPTT IDs (as translated by the IWF): + - a user in the LMR system can affiliate on its own (via the IWF) as long as the user is a group member (i.e. in the group list), even if the IWF has affiliated to the group. +- the IWF may make requests on behalf of a group's LMR users using the IWF MCPTT ID like a normal group member **including, for example, group join requests for groups using the chat model;** +- the IWF is not allowed to affiliate to a group that is not configured with the IWF's MCPTT ID in the group member list; and, +- if the IWF has not affiliated to an MCPTT group, then call requests to this group from LMR users on the system associated with the IWF, can only be accepted if the LMR user's MCPTT ID is in the group list, and has already affiliated. + +### 10.1.2.2 Group affiliation to a group defined in the MC system + +The LMR system may affiliate its group members to an interworking group defined in the MC system via the IWF. + +For group regroup, the affiliated group members are automatically affiliated to the temporary group. + +The signalling procedure of interworking group affiliation is described in figure 10.1.2.2-1. + +Pre-conditions: + +1. The group to be affiliated to is defined in the MC system. +2. The IWF is connected to and is authorized to interwork with the MC system. +3. The interworking group information is available at the IWF. +4. The mapping relationship of group and user identities between MC system and the LMR system has been configured at the IWF. + +NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Figure 10.1.2.2-1: Group affiliation to a group defined in the MC system. The diagram shows the interaction between MCPTT client 1, MCPTT server, MCPTT client 2, and IWF. The sequence of messages is: 1. Cancel pre-configured user regrouping (MCPTT client 1 to MCPTT server); 2. Pre-configured regroup cancel request (MCPTT client 1 to MCPTT server); 3. Check authorization (MCPTT server to MCPTT server); 4. Pre-configured regroup cancel request (MCPTT server to MCPTT client 2); 5. Notify user (MCPTT client 2 to MCPTT server); 6. Pre-configured regroup cancel response (MCPTT server to MCPTT client 2); 7. IWF pre-configured regroup cancel request (MCPTT server to IWF); 8. IWF pre-configured regroup cancel response (IWF to MCPTT server); 9. Deaffiliate MCPTT clients and the IWF (MCPTT server to MCPTT server); 10. Pre-configured regroup cancel response (MCPTT server to MCPTT client 1).](43837b056625d3d6ce615e4c02f163bb_img.jpg) + +Sequence diagram for Figure 10.1.2.2-1: Group affiliation to a group defined in the MC system. The diagram shows the interaction between MCPTT client 1, MCPTT server, MCPTT client 2, and IWF. The sequence of messages is: 1. Cancel pre-configured user regrouping (MCPTT client 1 to MCPTT server); 2. Pre-configured regroup cancel request (MCPTT client 1 to MCPTT server); 3. Check authorization (MCPTT server to MCPTT server); 4. Pre-configured regroup cancel request (MCPTT server to MCPTT client 2); 5. Notify user (MCPTT client 2 to MCPTT server); 6. Pre-configured regroup cancel response (MCPTT server to MCPTT client 2); 7. IWF pre-configured regroup cancel request (MCPTT server to IWF); 8. IWF pre-configured regroup cancel response (IWF to MCPTT server); 9. Deaffiliate MCPTT clients and the IWF (MCPTT server to MCPTT server); 10. Pre-configured regroup cancel response (MCPTT server to MCPTT client 1). + +**Figure 10.1.2.2-1: Group affiliation to a group defined in the MC system** + +1. The IWF sends an IWF group affiliation request to the MC service server on behalf of the LMR system. +- 2a. The MC service server checks if the group policy is locally cached. If the group policy is not locally cached on the MC service server then the MC service server requests the group policy from the group management server. +- 2b. The MC service server receives the group policy from the group management server. +3. Based on the group policy, the MC service server checks if the MC service group(s) is not disabled and if the user identified by the MCPTT ID supplied by the IWF is authorised to affiliate to the requested MC service group(s). +4. Based on the group policy and user subscription, the MC service server affiliates the IWF to the group. If a separate affiliation for each LMR user is expected, the status of the affiliating user is stored by the MC service server as the status associated with an MC service ID provided by the IWF that corresponds to the identity of that LMR user. If a separate affiliation for each LMR user is not expected, an affiliation status for the group using the MC service ID provided by the IWF is stored. +5. The MCPTT server sends the group affiliation status update message to the group management server, the group management server stores and updates the group affiliation status. +6. The MC service server returns an IWF group affiliation response to the IWF. + +NOTE 2: How the LMR user(s) affiliates to a group is outside the scope of the present document. + +### 10.1.2.3 Group de-affiliation from a group defined in the MC system + +The signalling procedure of interworking group de-affiliation from a group defined in the MC system is described in figure 10.1.2.3-1. + +The LMR system manages the individual de-affiliation requests from the LMR users. The LMR system can de-affiliate its group members from the interworking group via the IWF. + +Pre-conditions: + +1. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF. +2. The affiliation procedure described in subclause 10.1.2.2 was previously performed. + +NOTE 1: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Group de-affiliation from a group defined in the MC system. The diagram shows three lifelines: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF pre-configured regroup cancel request (IWF to MCPTT server); 2. Pre-configured regroup cancel request (MCPTT server to MCPTT client); 3. Notify user (MCPTT client internal message); 4. Pre-configured regroup cancel response (MCPTT client to MCPTT server); 5. IWF pre-configured regroup cancel response (MCPTT server to IWF).](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) + +Sequence diagram for Group de-affiliation from a group defined in the MC system. The diagram shows three lifelines: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF pre-configured regroup cancel request (IWF to MCPTT server); 2. Pre-configured regroup cancel request (MCPTT server to MCPTT client); 3. Notify user (MCPTT client internal message); 4. Pre-configured regroup cancel response (MCPTT client to MCPTT server); 5. IWF pre-configured regroup cancel response (MCPTT server to IWF). + +**Figure 10.1.2.3-1: Group de-affiliation from group defined in the MC system** + +1. The IWF sends an IWF group de-affiliation request to the MC service server on behalf of the LMR system. +2. If a separate de-affiliation from each LMR user is expected and based on the group policy and user subscription, the MC service server may de-affiliate the LMR group member from the group. Further, the MC service server may store the affiliation status of the user(s) for the requested MC service group(s). If a separate de-affiliation from each LMR user is not expected, the de-affiliation signalling de-affiliates the IWF and therefore the entire LMR system from the group. +3. The MC service server sends the group de-affiliation status update message to the group management server, the group management server stores and updates the group affiliation status. +4. The MC service server returns an IWF group de-affiliation response to the IWF. + +NOTE 2: How the LMR user(s) de-affiliate from a group is outside the scope of the present document. + +### 10.1.2.4 Group affiliation to group defined in the LMR system + +The MC service system may affiliate its group members to an interworking group defined in the LMR system via the IWF. + +The signalling procedure of group affiliation via the IWF is described in figure 10.1.2.4-1. + +Pre-conditions: + +1. The group to be affiliated to is defined in the LMR system. +2. The IWF is connected to and is authorized to work with the MC system. + +- 3. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF. + +NOTE 1: For all signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for group affiliation. Lifelines: MC service client, MC service server, IWF, and LMR system. The sequence starts with the client sending a request to the server. The server then sends a request to the IWF. The IWF sends a request to the LMR system. The LMR system returns a response to the IWF, which in turn returns a response to the server. Finally, the server sends a response to the client.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) + +``` + +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + participant IWF as IWF + participant LMR as LMR system + Note left of Client: MC service group affiliation request + Client->>Server: MC service group affiliation request + Note right of Server: MC service group ID(s) + Server->>IWF: IWF group affiliation request + Note right of IWF: IWF group ID + IWF->>LMR: IWF group affiliation request + Note right of LMR: LMR group ID + LMR-->>IWF: IWF group affiliation response + Note right of IWF: IWF group ID + IWF-->>Server: MC service group affiliation response + Note right of Server: MC service group ID(s) + Server-->>Client: MC service group affiliation response + +``` + +Sequence diagram for group affiliation. Lifelines: MC service client, MC service server, IWF, and LMR system. The sequence starts with the client sending a request to the server. The server then sends a request to the IWF. The IWF sends a request to the LMR system. The LMR system returns a response to the IWF, which in turn returns a response to the server. Finally, the server sends a response to the client. + +**Figure 10.1.2.4-1: Group affiliation to group defined in the LMR system** + +- 1. The MC service client sends a MC service group affiliation request, including the MC service group ID(s), to the MC service server. +- 2. The MC service server checks if the MC service group ID(s) is an interworking group defined in the LMR system. +- 3. The MC service server sends an IWF group affiliation request to the IWF. + +NOTE 2: The IWF can forward the request to the LMR system that could check whether the MC service client is authorized to affiliate to this interworking group. + +NOTE 3: The IWF can reject the affiliation if the MC service group ID is either unknown to the IWF or not mapped to an LMR group identity in the IWF configuration. + +- 4. The IWF returns an IWF group affiliation response to the MC service server, informing the successful affiliation to the LMR group. +- 5. The MC service server stores the group affiliation status of the MC service client for the requested interworking group. +- 6. The MC service server sends an MC service group affiliation response to the MC service client. + +NOTE 4: How the affiliation is conducted on the LMR system is outside the scope of the present document. + +### 10.1.2.5 Group de-affiliation from a group defined in the LMR system + +The signalling procedure of interworking group de-affiliation from a group defined in the LMR system is described in figure 10.1.2.5-1. + +The MC system manages the individual de-affiliation requests from the MC service users. The MC service system may de-affiliate its group members from the interworking group via the IWF. + +Pre-conditions: + +1. The mapping relationship of group and user identities between the MC service system and the LMR system has been configured at the IWF. +2. The affiliation procedure described in subclause 10.1.2.4 was previously performed. + +NOTE: For all the signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Group de-affiliation from a group defined in the LMR system. Lifelines: MC service client, MC service server, IWF, and LMR system. The process involves a request from the client to the server, a de-affiliation request from the server to the IWF, a response from the IWF to the server, and a final response from the server to the client.](2eb23c2210154279f8013a1594fbcc5a_img.jpg) + +``` + +sequenceDiagram + participant Client as MC service client + participant Server as MC service server + participant IWF as IWF + participant LMR as LMR system + + Note right of Server: MC service group de-affiliation request + Client->>Server: MC service group de-affiliation request + Note right of Server: MC service group de-affiliation request + Server->>IWF: IWF group de-affiliation request + Note right of IWF: IWF group de-affiliation response + IWF-->>Server: IWF group de-affiliation response + Note right of Server: MC service group de-affiliation response + Server-->>Client: MC service group de-affiliation response + +``` + +Sequence diagram for Group de-affiliation from a group defined in the LMR system. Lifelines: MC service client, MC service server, IWF, and LMR system. The process involves a request from the client to the server, a de-affiliation request from the server to the IWF, a response from the IWF to the server, and a final response from the server to the client. + +**Figure 10.1.2.5-1: Group de-affiliation from a group defined in the LMR system** + +1. The MC service client of the MC service user sends an MC service group de-affiliation request to the MC service server. The MC service client shall provide the initiating MC service ID and the MC service group ID(s) being de-affiliated from. +2. Based on the user subscription and stored group policy, the MC service server checks if the user of the MC service client is affiliated to the requested MC service group(s). The MC service server checks if the MC service group(s) is an interworking group. +- 3a. If the MC service group(s) is an interworking group, the MC service server sends an IWF group de-affiliation request to the IWF. +- 3b. The IWF returns an IWF group de-affiliation response to the MC service server. +4. If the user of the MC service client is authorized to de-affiliate from the requested MC service group(s), the MC service server removes the affiliation status of the user for the requested MC service group(s). +5. The MC service server returns an MC service group de-affiliation response to the MC service client. + +## 10.2 Group management + +### 10.2.1 Information flows for group management + +#### 10.2.1.1 General + +The following subclauses define information flows for group management on the IWF-1 interface. Group management related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.280 [5]. + +### 10.2.1.2 IWF group regroup teardown notification + +Table 10.2.1.2-1 describes the information flow IWF group regroup teardown notification between the group management server and the IWF or between the IWF and the group management server. + +**Table 10.2.1.2-1: IWF group regroup teardown notification** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the temporary group which is torn down | + +### 10.2.1.3 IWF group regroup teardown notification response + +Table 10.2.1.3-1 describes the information flow IWF group regroup teardown notification response between the group management server and the IWF or between the IWF and the group management server. + +**Table 10.2.1.3-1: IWF group regroup teardown notification response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the temporary group which was torn down | +| Result | M | Indicates success or failure of the notification | + +### 10.2.1.4 IWF group regroup request + +Table 10.2.1.4-1 describes the information flow IWF group regroup request between the group management server and the IWF or between the IWF and the group management server. + +**Table 10.2.1.4-1: IWF group regroup request** + +| Information element | Status | Description | +|--------------------------|--------|------------------------------------------| +| MC service group ID list | M | List of constituent MC service group IDs | + +### 10.2.1.5 IWF group regroup response + +Table 10.2.1.5-1 describes the information flow IWF group regroup response between the group management server and the IWF or between the IWF and the group management server. + +**Table 10.2.1.5-1: IWF group regroup response** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------------------------------------------------------------| +| MC service group ID | O (see NOTE) | MC service group ID of the temporary group | +| MC service group ID list | M | List of constituent MC service group IDs. | +| Result | M | Indicates whether the IWF group regroup was accepted or rejected. | +| NOTE: Shall be present if the Result information element indicates that the group regroup operation is successful. Otherwise MC service group ID shall not be present. | | | + +### 10.2.1.6 IWF group regroup notification + +Table 10.2.1.6-1 describes the information flow IWF group regroup notification between the group management server and the IWF or between the IWF and the group management server. + +**Table 10.2.1.6-1: IWF group regroup notification** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------| +| MC service group ID list | M | List of constituent MC service group IDs | +| MC service group ID | M | MC service group ID of the temporary group | +| Priority level | O | Required priority level for the temporary group | +| Security level (see NOTE) | O | Required security level for the temporary group | +| NOTE: Security level refers to the configuration of media and floor control protection parameters as listed in 3GPP TS 23.280 [5] | | | + +### 10.2.1.7 IWF group regroup notification response + +Table 10.2.1.7-1 describes the information flow IWF group regroup notification response between the group management server and the IWF or between the IWF and the group management server. + +**Table 10.2.1.7-1: IWF group regroup notification response** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------| +| MC service group ID list | M | List of constituent MC service group IDs | +| MC service group ID | M | MC service group ID of the temporary group | +| Priority level | M | Required priority level for the temporary group | +| Security level | M | Required security level for the temporary group | + +### 10.2.1.8 IWF group information request + +Table 10.2.1.8-1 describes the IWF group information request from the IWF to the group management server or from the group management server to the IWF. + +**Table 10.2.1.8-1: IWF group information request** + +| Information element | Status | Description | +|---------------------|--------|---------------------------------------| +| MC service group ID | M | The identity of the MC service group. | + +### 10.2.1.9 IWF group information response + +Table 10.2.1.9-1 describes the IWF group information response from the group management server to the IWF or the IWF to the group management server. + +**Table 10.2.1.9-1: IWF group information response** + +| Information element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------| +| MC service group ID | M | The identity of the MC service group. | +| MC service group provisioning information | O (see NOTE 1) | The group information retrieved from the group management server or from the IWF in the case where the IWF is performing the provision. | +| Result | O (see NOTE 2) | Indicates reason for failure to provide MC service group configuration information | +| NOTE 1: Shall be present if the request can be fulfilled.
NOTE 2: Shall be present if the request cannot be fulfilled. | | | + +### 10.2.1.10 IWF group information provision request + +Table 10.2.1.10-1 describes the IWF group information provision request from the group management server to the IWF or the IWF to the group management server. + +**Table 10.2.1.10-1: IWF group information provision request** + +| Information element | Status | Description | +|---------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------| +| MC service group ID | M | The identity of the MC service group. | +| MCPTT group configuration information | M | The group information retrieved from the group management server or from the IWF in the case where the group is defined in the IWF. | + +### 10.2.1.11 IWF group information provision response + +Table 10.2.1.11-1 describes the IWF group information provision response from the IWF to the group management server or from the group management server to the IWF. + +**Table 10.2.1.11-1: IWF group information provision response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------| +| MC service group ID | M | The identity of the MC service group. | +| Result | M | Indicates success or failure of reception, modification and storage of MC service group configuration information | + +#### 10.2.1.12 IWF group information subscribe request + +Table 10.2.1.12-1 describes the information flow IWF group information subscribe request from the IWF to the group management server in the MC system for cases where the MC system is the primary system of the group and from the group management server in the MC system to the IWF for cases there the IWF is the primary system of the group. + +**Table 10.2.1.12-1: IWF group information subscribe request** + +| Information element | Status | Description | +|-----------------------|--------|-------------------------------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| MC services requested | O | Service(s) for which group configuration is requested; one or more of MCPTT, MCData | + +#### 10.2.1.13 IWF group information subscribe response + +Table 10.2.1.13-1 describes the information flow IWF group information subscribe response from the group management server in the MC system to the IWF for cases where the MC system is the primary system of the group and from the IWF to the group management server in the MC system for cases where the IWF is the primary system of the group. + +**Table 10.2.1.13-1: IWF group information subscribe response** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| Result | M | Indicates success or failure of the subscribe request | + +#### 10.2.1.14 IWF group information notify request + +Table 10.2.1.14-1 describes the information flow IWF group information notify request from the group management server in the MC system to the IWF for cases where the MC system is the primary system of the group and from the IWF to the group management server in the MC system for cases where the IWF is the primary system of the group. + +**Table 10.2.1.14-1: IWF group information notify request** + +| Information element | Status | Description | +|--------------------------------------------------------------------|--------|------------------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| MC service group information reference (see NOTE) | O | Reference to information stored relating to the MC service group | +| Group related key material (see NOTE) | O | Key material for use with the MC service group | +| NOTE: At least one of these information elements shall be present. | | | + +#### 10.2.1.15 IWF group information notify response + +Table 10.2.1.15-1 describes the information flow IWF group information notify response from the IWF to the group management server in the MC system for cases where the MC system is the primary system of the group and from the group management server in the MC system to the IWF for cases there the IWF is the primary system of the group. + +**Table 10.2.1.15-1: IWF group information notify response** + +| Information element | Status | Description | +|---------------------|--------|----------------------------------------------------------| +| MC service group ID | M | MC service group ID of the group | +| Result | M | Indicates success or failure of the notification request | + +## 10.2.2 Group regrouping + +### 10.2.2.1 General + +The procedures in 3GPP TS 23.280 [5] are followed, but with changes required for interworking. The IWF will behave on the interface as if it is a peer MC service server with a peer group management client and peer group management server. + +Exceptions to the 3GPP TS 23.280 [5] procedures are detailed in the subclauses below. + +### 10.2.2.2 MC system initiates the group regroup + +The MC system can initiate a group regroup that includes groups defined at the IWF. The IWF is informed and may reject the regroup if conditions do not allow it to support the regroup. This is described in figure 10.2.2.2-1. + +Pre-conditions: + +1. The group management client has retrieved the group configurations of the groups to be regrouped. +2. At least one MC service group has been defined in the MC system. +3. At least one MC service group has been defined in the IWF. + +![Sequence diagram illustrating Group regrouping to an IWF. Lifelines: MC Service User (Dispatcher), MC Service Group Server, and IWF. The process involves a request from the user to the server, a check by the server, a forward to the IWF, a response from the IWF, and final updates from the server to the user.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant User as MC Service User (Dispatcher) + participant Server as MC Service Group Server + participant IWF as IWF + Note right of Server: Temporary Group Management + User->>Server: Request Group Regroup (Group IDs, Security Level, Priority Level) + Server->>IWF: Forward IWF Group Regroup Request + IWF-->>Server: IWF Group Regroup Response + Server-->>User: Update Temporary Group Info + Note right of IWF: Temporary Group Management + +``` + +Sequence diagram illustrating Group regrouping to an IWF. Lifelines: MC Service User (Dispatcher), MC Service Group Server, and IWF. The process involves a request from the user to the server, a check by the server, a forward to the IWF, a response from the IWF, and final updates from the server to the user. + +**Figure 10.2.2.2-1: Group regrouping to an IWF** + +1. The group management client of the MC service user (e.g. dispatcher) requests group regroup operation to the group management server (which is the group management server of one of the MC service groups to be regrouped). The identities of the groups being combined shall be included in this message. The group management client may indicate the security level required for the temporary group. The group management client may indicate the priority level required for the temporary group. +2. The group management server checks whether group regroup operation is performed by an authorised MC service user, based on group policy. The group management server checks whether the group is a temporary group. If the group is a temporary group, then the group regrouping will be rejected, otherwise the group regrouping can proceed. +3. The group management server forwards the IWF group regroup request to the IWF with the information about the IWF's groups. +4. The IWF provides an IWF group regroup response. Due to security aspects concerning sharing information among different MC systems, the IWF does not share the users' information of the groups under its management to the group management server. The IWF may reject the IWF group regroup response. (e.g. if one of its constituent groups is in the emergency state or is already in a regroup, if the IWF does not support temporary groups or the IWF does not support group regrouping) +5. The group management server creates and stores the information of the temporary group, including the temporary MC service group ID, off-network information, and the MC service IDs of the groups being combined, the priority level of the temporary group, and the security level of the temporary group. If the + +authorised MC service user does not specify the security level and the priority level, the group management server shall set the lower security level and the higher priority of the constituent groups. + +- 6. The group management server notifies the IWF about its group regroup operation. + +NOTE: How the IWF uses the MC service group ID that identifies the temporary group is outside the scope of the present document. + +- 7. The IWF acknowledges the group management server. +- 8. The group management server notifies the MC service server of the temporary group creation with the information of the constituent groups. +- 9. The MC service server acknowledges the notification from the group management server. +- 10. The group management server notifies the MC service group members of the constituent MC service groups of the group management server, possibly with an indication of lower security level. +- 11. The group management server provides a group regroup response to the group management client of the authorised MC service user (e.g. dispatcher). + +### 10.2.2.3 IWF initiates the group regroup + +The procedure in 3GPP TS 23.280 [5] is followed, except for steps 1 and 2. The IWF will behave on the interface as if it is a peer MC service server with a peer group management server. This is described in figure 10.2.2.3-1. + +Pre-conditions: + +- 1. At least one MC service group has been defined in the MC system. +- 2. At least one MC service group has been defined in the IWF. + +![Sequence diagram for 'Group regrouping from an IWF' showing interactions between IWF, Group Management Server, MC Service Server, and MC Service Group Members.](ceb48bd7cc8cbb0fa401b366532bbdb0_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant GMS as Group Management Server + participant MSS as MC Service Server + participant MSMS as MC Service Group Members + + Note right of GMS: Temporary Group + IWF->>GMS: IWF group regroup request + GMS->>MSS: Temporary group creation + MSS-->>GMS: Temporary group creation response + GMS->>MSMS: Temporary group creation + MSMS-->>GMS: Temporary group creation response + GMS-->>IWF: Temporary group creation response + +``` + +Sequence diagram for 'Group regrouping from an IWF' showing interactions between IWF, Group Management Server, MC Service Server, and MC Service Group Members. + +Figure 10.2.2.3-1: Group regrouping from an IWF + +- 1. The IWF sends an IWF group regroup request to the group management server. +- 2. The group management server checks whether the group can be included in a temporary group. + +3. The group management server provides an IWF group regroup response. + +NOTE: Due to security aspects concerning sharing information among different systems, the group management server does not share the users' information of the groups under its management to the IWF. + +4. The IWF notifies the group management server regarding the temporary group creation with information of the constituent groups. +5. The group management server notifies the MC service server regarding the temporary group creation with the information of the constituent groups. +6. The MC service server acknowledges the notification from the group management server. The MC service server may reject the IWF group regroup, e.g. if one of its constituent groups is already in a regroup. +7. The group management server acknowledges the notification from the IWF. +8. The group management server notifies the MC service group members of the constituent MC service groups of the group management server, possibly with an indication of a lower security level. + +#### 10.2.2.4 Ownership of the group regroup + +The group management server that performs the group regroup operation owns the temporary group created by the regroup, as implied in 3GPP TS 23.280 [5]. + +#### 10.2.2.5 Simultaneous group regroup requests from each side of the IWF-1 interface + +To prevent routing issues and complexity that could result from regrouping the same users from both sides of the interface, the following rules can be applied: + +- If group regrouping signalling using temporary groups is used on the MC system, the IWF must prevent the regroup signalling from propagating to the LMR system if the LMR system does not support regrouping; +- the IWF must handle the translation between temporary group identities on the MC system and the original interworking group identities used on the LMR system; and +- the regrouping rules in subclause 10.2.4.4 of 3GPP TS 23.280 [5] also apply. + +#### 10.2.2.6 Resolution of vocoder and encryption mode for the group regroup + +If one of the LMR groups to be included in a group regroup requires the use of LMR E2EE the preferred voice codecs for an MCPTT temporary group should be LMR codecs. If any of the mission critical users to be included in this MCPTT temporary group do not support LMR E2EE or the preferred LMR codecs, voice calls using LMR E2EE will fail for those users. + +NOTE 1: How the MC system determines that the temporary group needs to support LMR E2EE is outside the scope of the present document. + +NOTE 2: How the MC system determines that the temporary group needs to support an LMR codec is outside the scope of the present document. + +### 10.2.3 Group configuration for interworking + +#### 10.2.3.1 Overview + +The procedures in the following subclauses describe the process for sharing group configuration from an MC system to an IWF where the IWF needs to make use of the MC service group and from an IWF to an MC system where the MC system's clients need to make use of the group. The procedures in this subclause are based upon subclause 10.2.7 in 3GPP TS 23.280 [5]. + +#### 10.2.3.2 MC system provides group configuration to the IWF + +Figure 10.2.3.2-1 below illustrates the case where the MC system provides the group configuration to the IWF, e.g. due to an action by an administrator or because the primary MC system of some of the MC service group members is the IWF. + +Pre-conditions: + +1. The MC service group is defined in the MC system. +2. One or more LMR users are members of the group. +3. The MC system of the MC service group has been configured with addressing information for the group management function in the IWF. +4. The MC system of the MC service group is authorized to provide group configuration information to the IWF. + +NOTE: The MC system of the MC service group could be configured with an address of the IWF which is a proxy address. + +![Sequence diagram showing the MC system providing group configuration to the IWF. Lifelines include MC SYSTEM, MC SYSTEM GROUP, and IWF. The MC SYSTEM GROUP sends a message to the IWF, which then responds. The MC SYSTEM is shown as a participant in the background.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) + +``` + +sequenceDiagram + participant MC_SYSTEM as MC SYSTEM + participant MC_SYSTEM_GROUP as MC SYSTEM GROUP + participant IWF as IWF + Note left of MC_SYSTEM: 1. GROUP MANAGEMENT + MC_SYSTEM_GROUP->>IWF: 2. GROUP CONFIGURATION + IWF-->>MC_SYSTEM_GROUP: 3. GROUP CONFIGURATION RESPONSE + Note right of IWF: 4. GROUP CONFIGURATION STORED + +``` + +Sequence diagram showing the MC system providing group configuration to the IWF. Lifelines include MC SYSTEM, MC SYSTEM GROUP, and IWF. The MC SYSTEM GROUP sends a message to the IWF, which then responds. The MC SYSTEM is shown as a participant in the background. + +**Figure 10.2.3.2-1: MC system provides group configuration to the IWF** + +1. The group management server in the MC system of the MC service group provides the configuration information related to the MC service group to the IWF. +2. The IWF responds to the group management server of the MC system of the MC service group that the configuration has been received and stored correctly. + +### 10.2.3.3 IWF requests group configuration from the MC system + +Figure 10.2.3.3-1 below illustrates the case where the IWF requests the group configuration from the MC system, for example because a user on the IWF is a member of the group. + +Pre-conditions: + +1. The MC service group is defined in the MC system. +2. One or more LMR users are members of the group. +3. The IWF does not have the configuration for the MC service group stored. + +![Sequence diagram for Figure 10.2.3.3-1 showing the IWF requesting group configuration from the primary MC system.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +This sequence diagram illustrates the interaction between three entities: IWF, MC SYSTEM, and MC GROUP. The IWF sends a '1. REQUEST GROUP CONFIGURATION' message to the MC SYSTEM. The MC SYSTEM responds with '2. RESPONSE GROUP CONFIGURATION'. The IWF then sends '3. REQUEST GROUP MEMBER LIST' to the MC SYSTEM, which responds with '4. RESPONSE GROUP MEMBER LIST'. Finally, the IWF sends '5. REQUEST GROUP MEMBER LIST' to the MC GROUP, which responds with '6. RESPONSE GROUP MEMBER LIST'. + +Sequence diagram for Figure 10.2.3.3-1 showing the IWF requesting group configuration from the primary MC system. + +**Figure 10.2.3.3-1: Partner MC system requests group configuration from primary MC system** + +1. The IWF requests the group configuration from the group management server in the primary MC system of the MC service group. +2. The group management server in the MC system of the MC service group provides the requested group configuration information. + +**10.2.3.4 IWF provides group configuration to the MC system** + +Figure 10.2.3.4-1 below illustrates the case where the IWF provides the group configuration to the MC system, e.g. due to an action by an administrator or because some of the IWF's MC service group members are homed on the MC system. + +Pre-conditions: + +1. The group is defined in the IWF. +2. One or more MC service users are members of the group. + +NOTE: The group management server within the MC system is responsible for providing group configuration information to group members for whom the MC system is their serving MC system. + +![Sequence diagram for Figure 10.2.3.4-1 showing the MC system providing group configuration to the IWF.](1c29dadab94c3fa552d270434db09c81_img.jpg) + +This sequence diagram illustrates the interaction between three entities: IWF, MC SYSTEM, and MC GROUP. The IWF sends a '1. GROUP CONFIGURATION' message to the MC SYSTEM. The MC SYSTEM responds with '2. GROUP CONFIGURATION RESPONSE'. The MC SYSTEM then sends '3. GROUP CONFIGURATION' to the MC GROUP, which responds with '4. GROUP CONFIGURATION RESPONSE'. Finally, the MC SYSTEM sends '5. GROUP CONFIGURATION' to the IWF, which responds with '6. GROUP CONFIGURATION RESPONSE'. + +Sequence diagram for Figure 10.2.3.4-1 showing the MC system providing group configuration to the IWF. + +**Figure 10.2.3.4-1: MC system provides group configuration to the IWF** + +1. The IWF provides the configuration information related to the group to the group management server in the MC system. +2. The group management server in the MC system responds to the IWF that the configuration has been received and stored correctly. + +### 10.2.3.5 MC system requests group configuration from the IWF + +Figure 10.2.3.5-1 below illustrates the case where the MC system requests the group configuration from the IWF, for example because an MC service user receiving service in the MC system has the group configured in the user profile. + +Pre-conditions: + +1. The MC service group is defined in the IWF. +2. One or more MC service users are members of the group. +3. The group management server in the MC system does not have the configuration for the MC service group stored. +4. The MC system has been configured with addressing information for the group management function in the IWF. + +NOTE: The group management server within the MC system is responsible for providing group configuration information to MC service group members for whom the MC system is their serving MC system. + +![Sequence diagram showing the interaction between MC system participants and the IWF for group configuration. Lifelines: MC system Participant A, MC system Controller, IWF. The sequence starts with '1. Group is assigned' (a box spanning all lifelines with the note 'This context is assigned between that participant and that control server. This is passed to the IWF.'). Then, '2. Group wants to join' is sent from Participant A to Controller. '3. Request group configuration' is sent from Controller to IWF. '4. Group configuration' is returned from IWF to Controller. '5. Grant notification' is sent from Controller to Participant A. '6. Grant notification (acknowledged)' is sent from IWF to Controller. A large double-headed arrow at the bottom is labeled '7. Group wants'.](5b6e139e89c6ce90107ea7d7d77620a0_img.jpg) + +Sequence diagram showing the interaction between MC system participants and the IWF for group configuration. Lifelines: MC system Participant A, MC system Controller, IWF. The sequence starts with '1. Group is assigned' (a box spanning all lifelines with the note 'This context is assigned between that participant and that control server. This is passed to the IWF.'). Then, '2. Group wants to join' is sent from Participant A to Controller. '3. Request group configuration' is sent from Controller to IWF. '4. Group configuration' is returned from IWF to Controller. '5. Grant notification' is sent from Controller to Participant A. '6. Grant notification (acknowledged)' is sent from IWF to Controller. A large double-headed arrow at the bottom is labeled '7. Group wants'. + +**Figure 10.2.3.5-1: Partner MC system requests group configuration from primary MC system** + +1. The MC system requests the group configuration from the group management function in the IWF. +2. The IWF provides the requested group configuration information. + +### 10.2.3.6 IWF subscribes to group configuration + +The procedure for subscription from IWF for group configuration information to the group management server in the primary MC system of the MC service group is shown in figure 10.2.3.6-1. + +Pre-conditions: + +1. The MC service group is defined in its MC system. +2. One or more group members are defined in the LMR system. +3. The IWF has received group information from the GMS in the primary MC system of the MC service group. + +![Sequence diagram for Figure 10.2.3.6-1: Subscription from the IWF to the MC system for MC service group configuration. The diagram shows interactions between MC CPIT Client 1, MC CPIT Client 2, MC CPIT Server, and IWF. The IWF sends a subscription request to the MC CPIT Server, which responds. Then the server notifies the clients.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +sequenceDiagram + participant C1 as MC CPIT Client 1 + participant C2 as MC CPIT Client 2 + participant S as MC CPIT Server + participant IWF as IWF + + IWF->>S: 1. Subscribe (Group Config) + S-->>IWF: 2. Subscribe Response + S->>C1: 3. Notify (Group Config) + C1-->>S: 4. Notify Response + S->>C2: 5. Notify (Group Config) + C2-->>S: 6. Notify Response + +``` + +Sequence diagram for Figure 10.2.3.6-1: Subscription from the IWF to the MC system for MC service group configuration. The diagram shows interactions between MC CPIT Client 1, MC CPIT Client 2, MC CPIT Server, and IWF. The IWF sends a subscription request to the MC CPIT Server, which responds. Then the server notifies the clients. + +**Figure 10.2.3.6-1: Subscription from the IWF to the MC system for MC service group configuration** + +1. The IWF subscribes to the group configuration information stored in the group management server in the primary MC system of the MC service group. +2. The group management server in the primary MC system of the MC service group sends an IWF group information subscribe response to IWF indicating success or failure of the request. + +### 10.2.3.7 MC system notifies group configuration + +The procedure for notification of group configuration information from the group management server in the primary MC system of the MC service group to the IWF is shown in figure 10.2.3.7-1. + +Pre-conditions: + +1. The IWF has subscribed to the group configuration information for the MC service group in the group management server in the primary MC system of the MC service group. +2. The group management server in the primary MC system of the MC service group has received and stored new group configuration information for the MC service group. + +![Sequence diagram for Figure 10.2.3.7-1: Notification of group configuration information to the IWF. The diagram shows the MC CPIT Server sending a notification to the IWF, followed by notifications to the MC CPIT Clients.](f64e1e0997695248c0cd4122c5b1a170_img.jpg) + +``` + +sequenceDiagram + participant C1 as MC CPIT Client 1 + participant C2 as MC CPIT Client 2 + participant S as MC CPIT Server + participant IWF as IWF + + S->>IWF: 1. Notify (Group Config) + IWF-->>S: 2. Notify Response + S->>C1: 3. Notify (Group Config) + C1-->>S: 4. Notify Response + S->>C2: 5. Notify (Group Config) + C2-->>S: 6. Notify Response + +``` + +Sequence diagram for Figure 10.2.3.7-1: Notification of group configuration information to the IWF. The diagram shows the MC CPIT Server sending a notification to the IWF, followed by notifications to the MC CPIT Clients. + +**Figure 10.2.3.7-1: Notification of group configuration information to the IWF** + +1. The group management server in the primary MC system of the MC service group sends an IWF group information notify request to the IWF. +2. The IWF sends an IWF group information notify response to the group management server in the primary MC system of the MC service group indicating the success or failure of the notification. + +### 10.2.3.8 MC system subscribes to group configuration + +The procedure for subscription by the group management server in the MC system to the IWF for group configuration information is shown in figure 10.2.3.8-1. + +Pre-conditions: + +1. The group is defined in the LMR system. +2. One or more group members are defined in the MC system. + +3. The group management server in the MC system has received group information from the IWF. + +![Sequence diagram for Figure 10.2.3.8-1: Subscription from the MC system to the IWF for MC service group configuration. The diagram shows four lifelines: MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. The sequence starts with both clients sending '1. User wants to talk' to the MCPTT server. The server then sends '2. Floor request' to both clients. The MCPTT server also sends '3. IWF Floor request' to the IWF. The IWF responds with '4. IWF Floor granted' to the server. The server then sends '5. Floor rejected' to MCPTT client 2 and '6. Floor granted' to MCPTT client 1. The server sends '7. Floor taken' to MCPTT client 2 and '8. Talker notification' to MCPTT client 1. Finally, the server sends '9. Voice media' to both clients, and the IWF sends '9. IWF Voice media' to the server, which then forwards it to the clients.](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) + +Sequence diagram for Figure 10.2.3.8-1: Subscription from the MC system to the IWF for MC service group configuration. The diagram shows four lifelines: MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. The sequence starts with both clients sending '1. User wants to talk' to the MCPTT server. The server then sends '2. Floor request' to both clients. The MCPTT server also sends '3. IWF Floor request' to the IWF. The IWF responds with '4. IWF Floor granted' to the server. The server then sends '5. Floor rejected' to MCPTT client 2 and '6. Floor granted' to MCPTT client 1. The server sends '7. Floor taken' to MCPTT client 2 and '8. Talker notification' to MCPTT client 1. Finally, the server sends '9. Voice media' to both clients, and the IWF sends '9. IWF Voice media' to the server, which then forwards it to the clients. + +**Figure 10.2.3.8-1: Subscription from the MC system to the IWF for MC service group configuration** + +1. The group management server of the MC system subscribes to the group configuration information stored in the IWF. +2. The IWF provides an IWF group information subscribe response to group management server of the MC system indicating success or failure of the request. + +### 10.2.3.9 IWF notifies group configuration + +The procedure for notification of group information from the IWF to the group management server in the MC system is shown in figure 10.2.3.9-1. + +Pre-conditions: + +1. The group management server of the MC system has subscribed to the group configuration information for the group in the IWF. +2. The IWF has new information for the group. + +![Sequence diagram for Figure 10.2.3.9-1: Notification of group configuration information to partner MC system of MC service group. The diagram shows four lifelines: MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. The sequence starts with both clients sending '1. User wants to talk' to the MCPTT server. The server then sends '2. Floor request' to both clients. The MCPTT server sends '3. IWF floor request' to the IWF. The IWF responds with '4. Floor arbitration by policy' to the server. The server then sends '5. IWF floor rejected' to MCPTT client 2 and '6. Floor granted' to MCPTT client 1. The server sends '7. Floor taken' to MCPTT client 2 and '8. Talker notification' to MCPTT client 1. Finally, the server sends '9. Voice media' to both clients, and the IWF sends '9. IWF voice media' to the server, which then forwards it to the clients.](04c7ffb4a475a374f52b88704ecd295f_img.jpg) + +Sequence diagram for Figure 10.2.3.9-1: Notification of group configuration information to partner MC system of MC service group. The diagram shows four lifelines: MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. The sequence starts with both clients sending '1. User wants to talk' to the MCPTT server. The server then sends '2. Floor request' to both clients. The MCPTT server sends '3. IWF floor request' to the IWF. The IWF responds with '4. Floor arbitration by policy' to the server. The server then sends '5. IWF floor rejected' to MCPTT client 2 and '6. Floor granted' to MCPTT client 1. The server sends '7. Floor taken' to MCPTT client 2 and '8. Talker notification' to MCPTT client 1. Finally, the server sends '9. Voice media' to both clients, and the IWF sends '9. IWF voice media' to the server, which then forwards it to the clients. + +**Figure 10.2.3.9-1: Notification of group configuration information to partner MC system of MC service group** + +1. The IWF sends an IWF group information notify request to the group management server in the MC system. +2. The group management server in the MC system sends an IWF notify group information notify response to the IWF indicating the success or failure of the notification. + +## 10.3 Group call + +### 10.3.1 General + +The following subclauses define information flows and signaling procedures for group calls and broadcast group calls. + +Where the group is defined in the MCPTT system and where the IWF has affiliated to an MCPTT group with a single affiliation on behalf of all LMR group members, only a single IWF group call request / IWF group call release request message is sent to the IWF at the commencement / release of a group call. Where the group is defined in the MCPTT system and where the IWF has passed through individual affiliations for each group member in the LMR system, the MCPTT system shall send individual IWF group call request / IWF group call release request messages to the IWF for all affiliated group members in the LMR system in accordance with primary and partner MCPTT system behaviour. In both cases, the distribution of the messages to group members in the LMR system is out of scope of the present document. + +Where the group is defined in the LMR system, the IWF shall send individual IWF group call request / IWF group call release request messages to the IWF for all affiliated MCPTT group members in accordance with primary and partner MCPTT system behaviour. + +## 10.3.2 Information flows for group call over interworking group + +### 10.3.2.1 General + +The following subclauses define information flows for group calls on the IWF-1 interface. Group call related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.379 [7]. + +### 10.3.2.2 IWF group call request + +Table 10.3.2.2-1 describes the information flow IWF group call request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.2-1: IWF group call request information elements** + +| Information Element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------| +| MCPTT ID
(see NOTE 1) | M | The MCPTT ID of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the interworking group on which the call is initiated | +| SDP offer | M | Media parameters of MCPTT server | +| Implicit floor request
(see NOTE 2) | O | Indicates that the originator requests the floor. | +| Broadcast indicator | O | Indicates that the group call request is for a broadcast group call | +| Location | O | Location of the calling party | +| NOTE 1: If the LMR system does not provide the calling party identity when the group call is originated from the LMR system, then this information element may be set to a MCPTT ID reserved for LMR user at the IWF. | | | +| NOTE 2: This element shall be included only when the originating client requests the floor. | | | + +### 10.3.2.3 IWF group call response (IWF – MCPTT server) + +Table 10.3.2.3-1 describes the information flow IWF group call response from the MCPTT server to the IWF and from the IWF to MCPTT server. + +**Table 10.3.2.3-1: IWF group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP answer | M | Media parameters selected | + +### 10.3.2.4 IWF Group-broadcast group call setup request + +Table 10.3.2.4-1 describes the information flow IWF group-broadcast group call setup request from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.3.2.4-1: IWF Group-broadcast group call setup request information elements** + +| Information Element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------| +| MCPTT ID
(see NOTE 1) | M | The MCPTT ID of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP offer | M | Media parameters of MCPTT clients | +| Implicit floor request
(see NOTE 2) | O | Indicates that the originating client requests the floor | +| Location | O | Location of the calling party | +| NOTE 1: If the LMR system does not provide the calling party identity when the group-broadcast group call setup request is originated from the LMR system, then this information element may be set to a MCPTT ID reserved for the LMR user at the IWF. | | | +| NOTE 2: This element shall be included only when the originating client requests the floor. | | | + +### 10.3.2.5 IWF Group-broadcast group call setup response + +Table 10.3.2.5-1 describes the information flow IWF group-broadcast group call setup response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.5-1: IWF Group-broadcast group call setup response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is requested | +| SDP answer | M | Media parameters selected | + +### 10.3.2.6 IWF Group-broadcast group call release request + +Table 10.3.2.6-1 describes the information flow IWF group-broadcast group call release request from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.3.2.6-1: IWF Group-broadcast group call release request information elements** + +| Information Element | Status | Description | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------| +| MCPTT ID | M (see NOTE) | The MCPTT ID of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | +| NOTE: If the LMR system does not provide the calling party identity when the group-broadcast group call release request is originated from the LMR system, then this information element may be set to a MCPTT ID reserved for the LMR user at the IWF. | | | + +### 10.3.2.7 IWF group-broadcast group call release response + +Table 10.3.2.7-1 describes the information flow IWF group-broadcast group call release request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.7-1: IWF Group-broadcast group call release response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | + +### 10.3.2.8 IWF group join request + +Table 10.3.2.8-1 describes the information flow IWF group join request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.8-1: IWF group join request information elements** + +| Information Element | Status | Description | +|-------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the originator of the request. (see NOTE 1) | +| MCPTT group ID | M | The MCPTT group ID of the group to which the group communication is requested | +| SDP offer | M | Media parameters of originator | +| Implicit floor request (see NOTE 2) | O | Indicates that the originating client requests the floor. | +| NOTE 1: The IWF is configured with an MCPTT ID for use when the IWF is affiliating itself to the group on behalf of the LMR system. | | | +| NOTE 2: This element is included only when the originating client requests the floor. | | | + +### 10.3.2.9 IWF group join response + +Table 10.3.2.9-1 describes the information flow group join response from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.3.2.9-1: IWF group join response information elements** + +| Information Element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the originator of the request. (see NOTE) | +| MCPTT group ID | M | The MCPTT group ID of the group to which the group communication is requested | +| SDP answer | M | Media parameters selected | +| NOTE: The IWF is configured with an MCPTT ID for use when the IWF is affiliating itself to the group on behalf of the LMR system. | | | + +### 10.3.2.10 IWF group call leave request + +Table 10.3.2.10-1 describes the information flow IWF group call leave request from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.3.2.10-1: IWF group call leave request information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group from which the user is leaving | + +### 10.3.2.11 IWF group call leave response + +Table 10.3.2.11-1 describes the information flow IWF group call leave response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.11-1: IWF group call leave response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group from which the user is leaving | + +### 10.3.2.12 IWF group call release request + +Table 10.3.2.12-1 describes the information flow IWF group call release request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.12-1: IWF group call release request information elements** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------| +| MCPTT ID (NOTE) | O | The MCPTT ID of the initiating MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released | +| Release reason | O | The reason why the call is released | +| NOTE: This IE is not included if the group call release is initiated by the server (e.g. due to timeout) | | | + +### 10.3.2.13 IWF group call release response + +Table 10.3.2.13-1 describes the information flow IWF group call release response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.13-1: IWF group call release response information elements** + +| Information Element | Status | Description | +|---------------------|--------|----------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the target MCPTT group member | +| MCPTT group ID | M | The MCPTT group ID of the group on which the call is released. | + +### 10.3.2.14 IWF pre-configured regroup request + +Table 10.3.2.14-1 describes the information flow IWF pre-configured regroup request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.14-1 IWF pre-configured regroup request information elements** + +| Information Element | Status | Description | +|---------------------------------------------------|-----------------|------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| MCPTT group ID | M | MCPTT group ID of the MCPTT group from which configuration is to be taken | +| MCPTT group ID list | O
(see NOTE) | List of MCPTT groups to be regrouped into the pre-configured regroup group | +| MCPTT ID list | O
(see NOTE) | List of MCPTT IDs to be regrouped into the pre-configured user regroup group | +| NOTE: One and only one of these shall be present. | | | + +### 10.3.2.15 IWF pre-configured regroup response + +Table 10.3.2.15-1 describes the information flow IWF pre-configured regroup response from IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.15-1 IWF pre-configured regroup response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester of the regrouping operation | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Result | M | Result of the regrouping operation | + +### 10.3.2.16 IWF pre-configured regroup cancel request + +Table 10.3.2.16-1 describes the information flow pre-configured regroup cancel request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.16-1 IWF pre-configured regroup cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester | +| MCPTT group ID | M | MCPTT group ID of the regroup group | + +### 10.3.2.17 IWF pre-configured regroup cancel response + +Table 10.3.2.17-1 describes the information flow IWF pre-configured regroup cancel response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.17-1 IWF pre-configured regroup cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the requester of the regroup removal | +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Result | M | Result of the regroup removal operation | + +### 10.3.2.18 IWF pre-configured regroup reject (IWF – MCPTT server, MCPTT server - IWF) + +Table 10.3.2.18-1 describes the information flow IWF pre-configured regroup reject from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.3.2.18-1 IWF pre-configured regroup reject information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------| +| MCPTT group ID | M | MCPTT group ID of the regroup group | +| Reject reason | M | Reason for rejecting the regrouping operation | + +## 10.3.3 Pre-arranged group call + +### 10.3.3.1 General + +The subclauses 10.3.3.2 and 10.3.3.3 describe the group call setup between the MCPTT system and the LMR system on an interworking group defined in the MCPTT system. The subclauses 10.3.3.4 and 10.3.3.5 describe the group call setup between the MCPTT system and the LMR system on an interworking group defined in the LMR system. The subclause 10.3.3.7 describes the late entry procedures and subclause 10.3.3.8 describes the group call release procedures. Group calls can use MC media encryption between the IWF and the MCPTT clients as described in 3GPP TS 33.180 [8]. A call that uses an LMR vocoder may use LMR E2EE if the calling and called parties have previously been provisioned with the appropriate LMR E2EE keys. + +The procedures in the present subclause are applicable to the following non-broadcast group call types: pre-configured group regroup calls, pre-configured user regroup calls and group regroup calls. + +NOTE: MC media encryption is independent of LMR E2EE techniques. MC media encryption can be applied in addition to LMR E2EE. + +### 10.3.3.2 Group call setup initiated by MCPTT user on an interworking group defined in MCPTT system + +In this procedure, an MCPTT user is initiating a group call on an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.3.2-1. + +This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system. +2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service. +3. The users in this interworking group have been affiliated to the group. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram illustrating the group call setup initiated by an MCPTT user on an interworking group defined in an MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT server, and IWF. The process involves floor release, floor idle, floor taken, voice media exchange, floor request, and floor rejected messages. A user decision to interrupt LMR user transmission is also shown.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT server + participant IWF + Note left of MCPTT Client 1: 8. User decides to interrupt LMR user transmission + MCPTT Client 1->>MCPTT server: 1. Floor release + MCPTT server->>IWF: 2. IWF floor release + IWF-->>MCPTT server: 3. IWF floor idle + MCPTT server-->>MCPTT Client 1: 4. Floor idle + IWF-->>MCPTT server: 5. IWF floor taken + MCPTT server-->>MCPTT Client 1: 6. Floor taken + Note right of MCPTT server: 7a. Voice media + Note left of MCPTT Client 1: 7b. Voice media + MCPTT Client 1->>MCPTT server: 9. Floor request + MCPTT server->>IWF: 10. IWF Floor request + IWF-->>MCPTT server: 11. IWF floor rejected + MCPTT server-->>MCPTT Client 1: 12. Floor rejected + +``` + +Sequence diagram illustrating the group call setup initiated by an MCPTT user on an interworking group defined in an MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT server, and IWF. The process involves floor release, floor idle, floor taken, voice media exchange, floor request, and floor rejected messages. A user decision to interrupt LMR user transmission is also shown. + +**Figure 10.3.3.2-1: Group call setup initiated by MCPTT user on an interworking group defined in MCPTT system** + +1. MCPTT user at MCPTT client 1 initiates a group call for the selected interworking group identified by MCPTT group ID. +2. MCPTT client 1 sends a group call request to the MCPTT server. +3. MCPTT server checks whether the user of MCPTT client 1 is authorized to initiate a group call on the selected interworking group. +4. MCPTT server proceeds group call setup procedures towards the affiliated MCPTT system users as described in 3GPP TS 23.379 [7]. +5. MCPTT server sends IWF group call request(s) towards the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group call request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group call request is sent (to the IWF) for each affiliated LMR user. + +NOTE 2: How the LMR users are called is outside the scope of the present document. + +NOTE 3: Steps 4 and 5 can occur in any order. + +6. The IWF returns IWF group call response(s) to the MCPTT server. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF. +7. The MCPTT server sends group call response to the MCPTT client 1 about successful call establishment. +8. The group call on the interworking group has successfully established media plane for communication and any user can transmit media. The MCPTT system where the interworking group is defined is the controlling system of the group call and manages the floor control. + +### 10.3.3.3 Group call setup initiated by LMR user on an interworking group defined in MCPTT system. + +In this procedure, an LMR user is initiating a group call on an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.3.3-1. + +This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in MCPTT system. +2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service. +3. The users in this interworking group have been affiliated to the interworking group. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +5. LMR user initiates a group call. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for group call setup initiated by LMR user on an interworking group defined in MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT server, and IWF. The sequence starts with MCPTT Client 1 sending a floor request to the MCPTT server, which grants it. The MCPTT server then informs the IWF that the floor is taken. MCPTT Client 1 sends voice media to the MCPTT server, which is then forwarded by the IWF. The IWF receives a request for interruption from an LMR user and sends a floor request to the MCPTT server. The MCPTT server decides to grant the floor to the LMR user and revokes the floor from MCPTT Client 1. The IWF is then granted the floor by the MCPTT server. Finally, voice media from the LMR user is sent to the IWF, which is then forwarded to MCPTT Client 1.](ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT server + participant IWF + Note right of IWF: 5. IWF receives request for interruption from LMR user + + MCPTT Client 1->>MCPTT server: 1. Floor request + MCPTT server-->>MCPTT Client 1: 2. Floor granted + MCPTT server->>IWF: 3. IWF floor taken + MCPTT Client 1->>MCPTT server: 4a. Voice media + MCPTT server->>IWF: 4b. Voice media + Note right of IWF: 5. IWF receives request for interruption from LMR user + IWF->>MCPTT server: 6. IWF floor request + Note right of MCPTT server: 7. MCPTT server decides to grant floor to LMR user + MCPTT server-->>MCPTT Client 1: 8. Floor revoked + MCPTT server->>IWF: 9. IWF floor granted + IWF->>MCPTT server: 10a. Voice media + MCPTT server->>MCPTT Client 1: 10b. Voice media + +``` + +Sequence diagram for group call setup initiated by LMR user on an interworking group defined in MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT server, and IWF. The sequence starts with MCPTT Client 1 sending a floor request to the MCPTT server, which grants it. The MCPTT server then informs the IWF that the floor is taken. MCPTT Client 1 sends voice media to the MCPTT server, which is then forwarded by the IWF. The IWF receives a request for interruption from an LMR user and sends a floor request to the MCPTT server. The MCPTT server decides to grant the floor to the LMR user and revokes the floor from MCPTT Client 1. The IWF is then granted the floor by the MCPTT server. Finally, voice media from the LMR user is sent to the IWF, which is then forwarded to MCPTT Client 1. + +**Figure 10.3.3.3-1: Group call initiated by LMR user on an interworking group defined in MCPTT system** + +1. The IWF sends an IWF group call request to the MCPTT server for call establishment. If floor control is requested by the calling LMR user, an indication of implicit floor request is included. If the group call request contains an implicit floor request it may also include location information. +2. MCPTT server calls the affiliated users from MCPTT system as described in 3GPP TS 23.379 [7]. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF. + +3. If the group has other affiliated LMR users than the calling party and the MCPTT server has received individual affiliations from those LMR users, an individual IWF group call request is sent to the IWF for each affiliated LMR user. + +NOTE 2: Steps 2 and 3 can occur in any order. + +NOTE 3: How the LMR users from the LMR system are being called is outside the scope of the present document. + +4. The IWF returns IWF group call response(s) to the MCPTT server. + +5. The MCPTT server confirms the successful establishment of the group call by sending an IWF Group call response to the IWF. + +NOTE 4: How the group call response is returned to the initiating LMR user is outside the scope of the present document. + +6. The interworking group call has successfully established media plane for communication and any user can transmit media. The MCPTT system where the interworking group is defined is the controlling system of the group call and manages the floor control. + +NOTE 5: How the floor control is managed in the LMR system is outside the scope of the present document. + +### 10.3.3.4 Group call setup initiated by MCPTT user on an interworking group defined in the LMR system + +In this procedure, an MCPTT user is initiating a group call on an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.3.4-1. + +This subclause is based upon subclause for Pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT Server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system. +2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service. +3. The users in this interworking group have been affiliated to the group. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram illustrating a group call initiation by an MCPTT user on an interworking group defined in the LMR system. The diagram shows interactions between MCPTT client 1, MCPTT server, IWF, and MCPTT client 2.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + + Note over MCPTT client 1: 1. MCPTT user initiates group call + MCPTT client 1->>MCPTT server: 2. Group call request + rect rgb(255, 255, 255) + Note over MCPTT server: 3. Check authorization and +identify interworking group + end + MCPTT server->>IWF: 3. IWF group call request + IWF->>MCPTT server: 4. IWF group call request(s) + MCPTT server->>MCPTT client 2: 5. Group call request + MCPTT client 2-->>MCPTT server: 6. Group call response + MCPTT server-->>IWF: 7. IWF group call response + IWF-->>MCPTT server: 8. IWF group call response + MCPTT server-->>MCPTT client 1: 9. Group call response + Note over IWF, MCPTT client 2: 10. Media plane established + +``` + +Sequence diagram illustrating a group call initiation by an MCPTT user on an interworking group defined in the LMR system. The diagram shows interactions between MCPTT client 1, MCPTT server, IWF, and MCPTT client 2. + +**Figure 10.3.3.4-1: Group call initiated by MCPTT user on an interworking group defined in the LMR system** + +1. MCPTT user at MCPTT client 1 initiates a group call on the selected interworking group identified by MCPTT group ID. +2. MCPTT client 1 sends a group call request to the MCPTT server. +3. As the interworking group is defined in the LMR system the MCPTT server sends an IWF group call request to the IWF. +4. The IWF sends individual IWF group call request(s) to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the user in MCPTT client 2. + +NOTE 2: How the LMR users are called is outside the scope of the present document. + +5. The MCPTT server sends a group call request to the MCPTT client 2. +6. The MCPTT client 2 acknowledges towards the MCPTT server by sending a group call response. +7. The MCPTT server acknowledges towards the IWF by sending an IWF group call response. +8. The IWF sends an IWF group call response to the MCPTT server to acknowledge the IWF group call request received in step 3. +9. The MCPTT server sends a group call response to the initiating MCPTT user. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF. +10. The group call over the interworking group has successfully established media plane for communication and any user can transmit media. The LMR system where the interworking group is defined is the controlling system of the group call and manages the floor control. + +### 10.3.3.5 Group call setup initiated by LMR user on an interworking group defined in the LMR system. + +In this procedure, an LMR user is initiating a group call on an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.3.5-1. + +This subclause is based upon subclause for Pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT Server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system. +2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service. +3. The users in this interworking group have been affiliated to the group. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +5. LMR user initiates a group call. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram illustrating the group call setup initiated by an LMR user on an interworking group defined in the LMR system. The diagram shows interactions between MCPTT client 1, MCPTT client 2, MCPTT server, IWF, and LMR user. The sequence starts with the LMR user sending a request to the IWF, which then forwards it to the MCPTT server. The MCPTT server sends requests to the MCPTT clients, which respond back to the server, which in turn responds to the IWF, which finally responds to the LMR user.](0908107b858fa3783d10d93b3a3444b2_img.jpg) + +``` + +sequenceDiagram + participant LMR as LMR user + participant IWF as IWF + participant MS as MCPTT server + participant C1 as MCPTT client 1 + participant C2 as MCPTT client 2 + + Note left of C1: MCPTT client 1 + Note left of C2: MCPTT client 2 + Note left of MS: MCPTT server + Note left of IWF: IWF + + LMR->>IWF: 1. LMR group call request + IWF->>MS: 2. IWF group call request(s) + MS->>C1: 3. MCPTT group call request + MS->>C2: 3. MCPTT group call request + C1->>MS: 4. MCPTT group call response + C2->>MS: 4. MCPTT group call response + MS->>IWF: 5. IWF group call response(s) + IWF->>LMR: 6. LMR group call response + +``` + +Sequence diagram illustrating the group call setup initiated by an LMR user on an interworking group defined in the LMR system. The diagram shows interactions between MCPTT client 1, MCPTT client 2, MCPTT server, IWF, and LMR user. The sequence starts with the LMR user sending a request to the IWF, which then forwards it to the MCPTT server. The MCPTT server sends requests to the MCPTT clients, which respond back to the server, which in turn responds to the IWF, which finally responds to the LMR user. + +**Figure 10.3.3.5-1: Group call initiated by LMR user on an interworking group defined in the LMR system** + +1. The IWF sends an IWF group call request(s) to the MCPTT server for call establishment. An individual IWF group call request is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2. If floor control is requested by the calling LMR user, an indication of implicit floor request is included. If the group call request contains an implicit floor request it may also include location information. +2. MCPTT server sends a group call request(s) to the target MCPTT user(s) as described in 3GPP TS 23.379 [7]. +3. MCPTT client(s) receiving the group call request, acknowledge towards the MCPTT server by sending a group call response. +4. The MCPTT server acknowledges the IWF group call request(s) by sending a IWF group call response(s) to the IWF. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF. + +NOTE 2: How the IWF group call response(s) is handled in the IWF / LMR system and how the other LMR users are being called is outside the scope of the present document. + +5. The interworking group call has successfully established media plane for communication and any user can transmit media. The LMR system where the interworking group is defined is the controlling system of the group call and manages the floor control. + +### 10.3.3.6 Encrypted group call with transcoding + +Pre-conditions: + +1. An MCPTT session is established between an MCPTT client, the interworked LMR system (represented by the IWF), and the MCPTT server. +2. There is an ongoing media transmission. +3. An SDP negotiation has occurred between the IWF and MCPTT Server to establish both the vocoder and the security parameters for the call. +4. The IWF is configured to perform transcoding of voice media and has obtained key material from the MCPTT system using the procedures in 3GPP TS 33.180 [8]. + +![Sequence diagram showing encrypted group call with transcoding. Lifelines: MCPTT client, MCPTT server, IWF, and another participant. The diagram shows media flow from the client to the server, then to the IWF, and finally to the participant, with corresponding feedback arrows.](09e20a17ecd8042b3d9b7fd462f2d9b4_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + participant Participant + Note over MCPTT client, Participant: Encrypted group call with transcoding + MCPTT client->>MCPTT server: 1. Encrypted voice media + MCPTT server->>IWF: 2. Encrypted voice media + MCPTT server->>Participant: 2. Encrypted voice media + Participant-->>MCPTT server: 3. Feedback + IWF-->>MCPTT server: 3. Feedback + MCPTT server-->>MCPTT client: 4. Feedback + +``` + +Sequence diagram showing encrypted group call with transcoding. Lifelines: MCPTT client, MCPTT server, IWF, and another participant. The diagram shows media flow from the client to the server, then to the IWF, and finally to the participant, with corresponding feedback arrows. + +**Figure 10.3.3.6-1: Encrypted group call with transcoding** + +1. The MCPTT client has been given the floor and is transmitting voice media. +2. The MCPTT client encodes audio using a codec defined for the MCPTT group, encrypts the encoded voice using procedures in 3GPP TS 33.180 [8], and forwards the encrypted voice media to the MCPTT server. +3. The MCPTT server forwards the encrypted voice media to other participants in the group call including the IWF. + +4. The IWF decrypts the voice media from the MCPTT client using the procedures in 3GPP TS 33.180 [8]. The IWF transcodes the voice to a LMR codec. If needed, the IWF re-encrypts the transcoded voice media using LMR security procedures (these are out-of-scope of this specification), and forwards the voice media to the LMR system. + +NOTE: Where transcoding occurs is outside the scope of this specification. In this procedure, it is assumed to take place internal to the IWF. + +5. Sometime later the floor becomes idle. +6. The LMR system (represented by the IWF in figure 10.3.3.6-1) requests and is granted the floor. +7. The IWF has been given the floor and is transmitting voice media. +8. The IWF receives voice media from the LMR system. If the voice media is encrypted, the IWF decrypts the voice media using LMR security procedures (these are out-of-scope of this specification). The IWF transcodes the voice to the group's MCPTT codec. The IWF re-encrypts the transcoded voice using the procedures in 3GPP TS 33.180 [8]. +9. The IWF forwards the voice media to the MCPTT server. +10. The MCPTT server forwards the voice media to other participants in the group call. + +### 10.3.3.7 Late Entry + +#### 10.3.3.7.1 General + +Late Entry for an ongoing interworking group call is triggered by a successful group affiliation procedure from the participating system. + +NOTE: These procedures apply to all types of group calls, including, for example, emergency call, imminent peril call and broadcast call. + +#### 10.3.3.7.2 Group call late entry on an interworking group defined in the MCPTT system + +In this procedure, the group affiliation from IWF triggers a late entry procedure in the MCPTT system. The signalling procedure is described in figure 10.3.3.7.2-1. + +For the first affiliating LMR user, this procedure is applicable for both IWF affiliation options (see subclauses 10.1.2.1 and 10.3.1). For the following LMR users affiliating to the same group, this procedure is triggered only if the IWF passes through individual affiliations for each group member. + +This subclause is based upon subclauses in 3GPP TS 23.379 [7] for: + +- Late entry for pre-arranged group call, subclause 10.6.2.3.1.1.4, and +- Group call for an MCPTT group defined in partner MCPTT system, subclause 10.6.2.4.3.1. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system. +2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +3. There is an on-going group call in the interworking group involving MCPTT clients 1 and 2. +4. First LMR user affiliates to the interworking group. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Figure 10.3.3.7.2-1: Group call late entry on an interworking group defined in the MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF. The sequence starts with the IWF sending a group affiliation to the MCPTT Server. The MCPTT Server then initiates a group call late entry and sends an IWF group call request to the IWF. The IWF responds with an IWF group call response. The IWF then adds the LMR user to the group call and notifies MCPTT clients. Finally, the MCPTT Server sends a floor taken or floor idle message to the IWF.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT Server + participant IWF + Note left of MCPTT Client 1: LMR user wants to join group call + IWF->>MCPTT Server: 1. Group Affiliation + MCPTT Server-->>MCPTT Client 1: 2. Group Call Late Entry + MCPTT Server->>IWF: 3. IWF Group Call Request + IWF-->>MCPTT Server: 4. IWF Group Call Response + IWF->>MCPTT Client 1: 5. User Added / Notification + MCPTT Server->>IWF: 6. Floor Taken / Floor Idle + +``` + +Sequence diagram for Figure 10.3.3.7.2-1: Group call late entry on an interworking group defined in the MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF. The sequence starts with the IWF sending a group affiliation to the MCPTT Server. The MCPTT Server then initiates a group call late entry and sends an IWF group call request to the IWF. The IWF responds with an IWF group call response. The IWF then adds the LMR user to the group call and notifies MCPTT clients. Finally, the MCPTT Server sends a floor taken or floor idle message to the IWF. + +**Figure 10.3.3.7.2-1: Group call late entry on an interworking group defined in the MCPTT system** + +1. The IWF triggers a group affiliation towards the MCPTT server (see subclause 10.1.2.2). + 2. The MCPTT server initiates a group call late entry for an interworking group. + 3. The MCPTT server sends an IWF group call request to the IWF. +- NOTE 2: How the IWF delivers the group call request to the LMR system is out of the scope of the present document. +4. The IWF confirms the group call request by sending IWF group call response to the MCPTT server. + 5. The IWF (and the LMR user) is successfully added to the ongoing group call and MCPTT users at MCPTT client 1 and MCPTT client 2 may be notified about the LMR user joining the group call. + 6. If the floor has been granted to another user, the MCPTT server sends a IWF floor taken (6a) to the IWF. If the floor is not granted to any party, an IWF floor idle (6b) is sent to the IWF. + +### 10.3.3.7.3 Group call late entry on an interworking group defined in the LMR system + +In this procedure, the group affiliation from MCPTT system triggers a late entry procedure in the LMR system. The signalling procedure is described in figure 10.3.3.7.3-1. + +This procedure describes the affiliation and late entry of the first MCPTT user into the interworking group, but it is applicable also for all subsequent MCPTT users' affiliations to the same group. + +This subclause is based upon subclauses in 3GPP TS 23.379 [7] for: + +- Late entry pre-arranged group call, subclause 10.6.2.3.1.1.4, and +- Group call setup involving groups from multiple MCPTT systems, subclause 10.6.2.4.1.1. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system. +2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +3. There is an on-going group call in the interworking group, involving only LMR users. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram illustrating 'Group call late entry on an interworking group defined in the LMR system'. The diagram shows three lifelines: MCPTT client 1, MCPTT server, and IWF. The sequence of messages is: 1. MCPTT client 1 sends an IWF group call request to the IWF. 2. The IWF sends an IWF group call request to the MCPTT server. 3. The MCPTT server triggers a group call setup procedure for the newly affiliated user in MCPTT client 1. 4. The MCPTT server confirms the successful establishment of the group call by sending an IWF group call response to the IWF. 5. The IWF sends an IWF floor taken (6a) or IWF floor idle (6b) to the MCPTT server. 6. The MCPTT server sends Floor taken (7a) or Floor idle (7b) to the newly affiliated user in MCPTT client 1.](69e5f1993021af230d08c08aac97d9df_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant IWF + Note right of MCPTT client 1: 1. MCPTT user (client 1) affiliates to the group + MCPTT client 1->>IWF: IWF group call request + Note right of IWF: 2. The IWF sends an IWF group call request to the MCPTT server. + IWF->>MCPTT server: IWF group call request + Note right of MCPTT server: 3. The MCPTT server triggers a group call setup procedure for the newly affiliated user in MCPTT client 1 + Note right of MCPTT server: 4. The MCPTT server confirms the successful establishment of the group call by sending IWF group call response to the IWF. + MCPTT server->>IWF: IWF group call response + Note right of IWF: 5. MCPTT client 1 is successfully added to the ongoing group call. + Note right of IWF: 6. If the floor has been granted to another user, the IWF sends an IWF floor taken (6a) to the MCPTT server. If the floor is not granted to any party, an IWF floor idle (6b) is sent. + IWF->>MCPTT server: IWF floor taken / IWF floor idle + Note right of MCPTT server: 7. The MCPTT server sends Floor taken (7a) or Floor idle (7b) to the newly affiliated user in MCPTT client 1 + MCPTT server->>MCPTT client 1: Floor taken / Floor idle + +``` + +Sequence diagram illustrating 'Group call late entry on an interworking group defined in the LMR system'. The diagram shows three lifelines: MCPTT client 1, MCPTT server, and IWF. The sequence of messages is: 1. MCPTT client 1 sends an IWF group call request to the IWF. 2. The IWF sends an IWF group call request to the MCPTT server. 3. The MCPTT server triggers a group call setup procedure for the newly affiliated user in MCPTT client 1. 4. The MCPTT server confirms the successful establishment of the group call by sending an IWF group call response to the IWF. 5. The IWF sends an IWF floor taken (6a) or IWF floor idle (6b) to the MCPTT server. 6. The MCPTT server sends Floor taken (7a) or Floor idle (7b) to the newly affiliated user in MCPTT client 1. + +**Figure 10.3.3.7.3-1: Group call late entry on an interworking group defined in the LMR system** + +1. MCPTT user (client 1) affiliates to the group (see subclause 10.1.2.4). + +NOTE 2: How the IWF delivers the affiliation to LMR system and how the LMR system handles the late entry is out of scope of the present document. + +2. The IWF sends an IWF group call request to the MCPTT server. +3. The MCPTT server triggers a group call setup procedure for the newly affiliated user in MCPTT client 1, as described in 3GPP TS 23.379 [7]. +4. The MCPTT server confirms the successful establishment of the group call by sending IWF group call response to the IWF. If E2EE is specified, then the MCPTT users and the LMR users shall use the same codec. If E2EE is not specified, the MCPTT users and the LMR users can use different codecs and transcoding is needed at the IWF. +5. MCPTT client 1 is successfully added to the ongoing group call. +6. If the floor has been granted to another user, the IWF sends an IWF floor taken (6a) to the MCPTT server. If the floor is not granted to any party, an IWF floor idle (6b) is sent. +7. The MCPTT server sends Floor taken (7a) or Floor idle (7b) to the newly affiliated user in MCPTT client 1, as described in 3GPP TS 23.379 [7]. + +## 10.3.3.8 Interworking group call release + +### 10.3.3.8.1 General + +The procedures in this subclause define the cases where the group host server releases an ongoing interworking group call for all the participants of that group. + +If the group host server is an MCPTT server, the release conditions are described in 3GPP TS 23.379 [7], subclause 10.6.2.4.1.2. + +If the group host server is an LMR system, represented by an IWF, the release conditions are outside the scope of the present document. + +### 10.3.3.8.2 Group call release on an interworking group defined in the MCPTT system + +In this procedure, the MCPTT system is releasing a group call on an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.3.8.2-1. + +This subclause is based upon subclause 10.6.2.4.1.2 Group call release in 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system. +2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +3. There is an on-going group call involving the IWF and MCPTT clients 1 and 2. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram showing group call release initiated by MCPTT system on an interworking group. Lifelines include MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF. The sequence starts with the MCPTT Server sending a 'GROUP CALL RELEASE' message to the IWF. The IWF then sends 'LMR GROUP CALL RELEASE' to MCPTT Client 1, 'LMR GROUP CALL RELEASE' to MCPTT Client 2, and 'LMR GROUP CALL RELEASE' to the MCPTT Server. The MCPTT Server then sends a 'GROUP CALL RELEASE' message to MCPTT Client 1.](678ac9faaa56bb929499cebeea83a110_img.jpg) + +``` + +sequenceDiagram + participant MCPTT_C1 as MCPTT Client 1 + participant MCPTT_C2 as MCPTT Client 2 + participant MCPTT_S as MCPTT Server + participant IWF as IWF + + Note right of MCPTT_S: GROUP CALL RELEASE + MCPTT_S->>IWF: GROUP CALL RELEASE + Note right of IWF: LMR GROUP CALL RELEASE + IWF->>MCPTT_C1: LMR GROUP CALL RELEASE + Note right of IWF: LMR GROUP CALL RELEASE + IWF->>MCPTT_C2: LMR GROUP CALL RELEASE + Note right of IWF: LMR GROUP CALL RELEASE + IWF->>MCPTT_S: LMR GROUP CALL RELEASE + Note right of MCPTT_S: GROUP CALL RELEASE + MCPTT_S->>MCPTT_C1: GROUP CALL RELEASE + +``` + +Sequence diagram showing group call release initiated by MCPTT system on an interworking group. Lifelines include MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF. The sequence starts with the MCPTT Server sending a 'GROUP CALL RELEASE' message to the IWF. The IWF then sends 'LMR GROUP CALL RELEASE' to MCPTT Client 1, 'LMR GROUP CALL RELEASE' to MCPTT Client 2, and 'LMR GROUP CALL RELEASE' to the MCPTT Server. The MCPTT Server then sends a 'GROUP CALL RELEASE' message to MCPTT Client 1. + +Figure 10.3.3.8.2-1: Group call release initiated by MCPTT system on an interworking group + +1. The MCPTT server initiates a group call release on an interworking group. + +NOTE 2: The MCPTT server may decide to release the group call for different reasons, see subclause 10.6.2.4.1.2 in 3GPP TS 23.379 [7]. + +2. The MCPTT server identifies the participants of the ongoing group call, at least one of them being an LMR user, represented by an IWF. + +3. The MCPTT server sends IWF group call release request(s) to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group call release request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group call release request is sent (to the IWF) for each affiliated LMR user. + +NOTE 3: How the group call release request(s) is(are) forwarded to the LMR system is out of scope of the present document. + +4. The MCPTT server sends the (MCPTT) group call release request(s) to the group's MCPTT users, as described in 3GPP TS 23.379 [7]. + +NOTE 4: Steps 3 and 4 can occur in any order. + +5. The IWF confirms the IWF group call release request(s) received in step 3 by IWF group call release response(s) to the MCPTT server. + +6. The MCPTT client 1, client 2 and the IWF have successfully released the floor control and media plane resources associated with the group call that is released. + +### 10.3.3.8.3 Group call release on an interworking group defined in the LMR system + +In this procedure, the LMR system is releasing a group call on an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.3.8.3-1. + +This subclause is based upon subclause 10.6.2.4.1.2 Group call release in 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system. +2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +3. There is an on-going group call involving the IWF and MCPTT clients 1 and 2. +4. The LMR system initiates release of the group call. + +NOTE 1: The reasons for the LMR system's decision to release the group call are out of scope of the present document. + +NOTE 2: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Group call release initiated by LMR system](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +The diagram shows a sequence of interactions between three entities: IWF, MCPTT server, and MCPTT clients 1 & 2. +1. The IWF sends a message '1. IWF group call release request' to the MCPTT server. +2. The MCPTT server forwards this as '2. IWF group call release request' to the MCPTT clients 1 & 2. +3. The MCPTT clients respond with '3. IWF group call release response' to the MCPTT server. +4. The MCPTT server then sends '4. IWF group call release response' back to the IWF. +5. A final box indicates '5. Floor control and media plane resources released' involving all parties. + +``` + +sequenceDiagram + participant IWF as IWF + participant S as MCPTT server + participant C as MCPTT clients 1 & 2 + IWF->>S: 1. IWF group call release request + S->>C: 2. IWF group call release request + C-->>S: 3. IWF group call release response + S-->>IWF: 4. IWF group call release response + Note over IWF,C: 5. Floor control and media plane resources released + +``` + +Sequence diagram for Group call release initiated by LMR system + +**Figure 10.3.3.8.3-1: Group call release initiated by LMR system on an interworking group defined in the LMR system** + +1. The IWF sends IWF group call release requests to the MCPTT server. An individual IWF group call release request is sent for each MCPTT user in the call. +2. The MCPTT server forwards the release requests to the group's MCPTT users (in this example to users in MCPTT clients 1 and 2), as described in 3GPP TS 23.379 [7]. +3. The MCPTT clients respond with group call release response(s). +4. The MCPTT server confirms the IWF group call release requests received in step 1 by IWF group call release responses to the IWF. +5. The MCPTT client 1, client 2 and the IWF have successfully released the floor control and media plane resources associated with the group call that is released. + +### 10.3.4 Group broadcast + +#### 10.3.4.1 General + +A broadcast group call is a special group call where the initiating user expects no response from the receiving users so that when the transmission is complete, so is the call. The initiating user can be an MCPTT user or can be an LMR user. + +The group-broadcast group is defined as a set of groups, not a set of users. The user that originates the group-broadcast group call is the only one transmitting media during this call. + +The group-broadcast group is defined with a hierarchy. For example, groups A and B may be subordinate to a group-broadcast group. All subordinate groups belonging to a group-broadcast group are defined either in the MCPTT system or the LMR system. + +#### 10.3.4.2 Group-broadcast group call procedure with an interworking group where the group-broadcast group is defined in the MCPTT system + +3GPP TS 23.379 [7], subclause 10.6.2.5.2.1 describes the procedure for a group-broadcast group call within a single MCPTT system. The present procedure describes a group-broadcast group call that includes the IWF. + +In this procedure, the MCPTT server is initiating the broadcast and is the owner of the group-broadcast group. + +The procedure shows the case where the call is initiated by a MCPTT user. However, if the override feature is enabled, then the call originator may be overridden. + +Figure 10.3.4.2-1 illustrates the procedure for group-broadcast group call establishment (the group-broadcast group is defined in the MCPTT system). + +Pre-conditions: + +1. The group (e.g. A) to which MCPTT client 2 and the IWF are members is a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group A as a subordinate group). +2. The group (e.g. A) currently has an on-going MCPTT group call that is not an MCPTT emergency group call. +3. The call initiator of the group-broadcast group is a member of another group (e.g., X, not group A) which is also a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group X as a subordinate group). +4. The group-broadcast group and its subordinate groups are defined in the same group management server and served by the same MCPTT server. + +![Sequence diagram for group-broadcast group call involving IWF](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT server + participant IWF + Note left of MCPTT Client 1: 1. Initiate in-progress emergency group state cancel + MCPTT Client 1->>MCPTT server: 2. MCPTT in-progress emergency group state cancel request + MCPTT server->>IWF: 3. IWF in-progress emergency group state cancel request + IWF-->>MCPTT server: 4. IWF in-progress emergency group state cancel response + Note right of MCPTT server: 5. Bearer priority configuration + Note right of MCPTT server: 6. Inform the affiliated MCPTT clients + MCPTT server-->>MCPTT Client 1: 7. MCPTT in-progress emergency group state cancel response +``` + +The sequence diagram illustrates the interaction for a group-broadcast group call involving the IWF. It features four lifelines: MCPTT Client 1, MCPTT Client 2, MCPTT server, and IWF. The process begins with MCPTT Client 1 initiating an in-progress emergency group state cancel. This is followed by a request from MCPTT Client 1 to the MCPTT server. The MCPTT server then sends a request to the IWF. The IWF responds, and the MCPTT server performs bearer priority configuration and informs affiliated MCPTT clients. Finally, the MCPTT server sends a response back to MCPTT Client 1. + +Sequence diagram for group-broadcast group call involving IWF + +**Figure 10.3.4.2-1: Group-broadcast group call involving IWF (group-broadcast group is defined in the MCPTT system)** + +1. MCPTT user at MCPTT client 1 initiates the group-broadcast group call setup procedure. +2. The MCPTT client 1 sends a group-broadcast group call request to the MCPTT server. +3. The MCPTT server needs to resolve the group-broadcast group ID into its subordinate groups in order to contact the affiliated MCPTT users of those subordinate groups. +4. The MCPTT server then needs to consider any on-going group calls on those subordinate groups because this may affect the behaviour for what happens next. In this case a group call exists on a subordinate group. Thus, the MCPTT users involved in the group call on this subordinate group. +5. The MCPTT server performs group call release procedures of groups defined in the MCPTT system as described in subclause 10.3.3.8.2. + +6. A group-broadcast group call request is sent to MCPTT client 2 and an IWF group-broadcast group call request to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call request is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call request is sent (to the IWF) for each affiliated LMR user. + +NOTE 1: How the group-broadcast group call request(s) is(are) forwarded to the LMR system is out of scope of the present document. + +7. MCPTT client 2 is notified of the incoming group-broadcast group call. + +NOTE 2: How LMR user(s) is(are) notified of the incoming group-broadcast group call is outside the scope of the present document. + +8. MCPTT client 2 and the IWF respond to the IWF group-broadcast group call request by sending an IWF group-broadcast group call response. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call response is sent to the MCPTT server. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call response is sent (to the MCPTT server) for each affiliated LMR user. + +9. The MCPTT server responds to MCPTT client 1 (the call initiator) that the group-broadcast group call has been established by sending a group-broadcast group call response. + +10. The MCPTT client 1 notifies its user that the user can begin transmitting using the group-broadcast group call resources. + +Once the user of MCPTT client 1 completes transmitting, the group-broadcast group call is released. + +#### 10.3.4.3 Group-broadcast group call procedure with an interworking group where the group-broadcast group is defined in the LMR system + +3GPP TS 23.379 [7], subclause 10.6.2.5.2.1 describes the procedure for a group-broadcast group call within a single MCPTT system. The present procedure describes a group-broadcast group call that includes the IWF. + +In this procedure, the IWF is the owner of the group-broadcast group and is initiating the group-broadcast group call. + +The procedure only shows the case where the call is initiated by a MCPTT user. However, if the override feature is enabled, then the call originator may be overridden. + +Figure 10.3.4.3-1 illustrates the procedure for group-broadcast group call establishment (the group-broadcast group is defined in the LMR system). + +Pre-conditions: + +1. The group (e.g. A) to which MCPTT client 2 is a member is a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group A as a subordinate group). +2. The group (e.g. A) currently has an on-going MCPTT group call that is not an MCPTT emergency group call. +3. The call initiator, MCPTT client 1, of the group-broadcast group is a member of another group (e.g., X, not group A) which is also a subordinate group of the group-broadcast group (i.e., the group-broadcast group was defined with group X as a subordinate group). +4. The group-broadcast group and its subordinate groups are defined in the IWF. + +![Sequence diagram showing the group-broadcast group call setup procedure involving MCPTT clients, server, and IWF.](0a73b03fba21af142d619a9a662e6490_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT Server + participant IWF + + Note left of MCPTT Client 1: 1. Initiate group-broadcast group call + MCPTT Client 1->>MCPTT Server: 2. MCPTT group-broadcast call request + Note right of MCPTT Server: 3. AR (take the user) + Note right of MCPTT Server: 4. Check authorization and AR status + Note right of MCPTT Server: 5. Reorder priority configuration + Note right of MCPTT Server: 6. Record the AR in context/priority state at the group + MCPTT Server->>IWF: 7. IWF group-broadcast call request + IWF-->>MCPTT Server: 8. AR (take the user) group-broadcast call response + Note left of MCPTT Client 1: 9. Call(s) AR (take) MCPTT clients + MCPTT Server->>MCPTT Client 1: 10. MCPTT group-broadcast call response + Note bottom: 11. Media plane is established + +``` + +Sequence diagram showing the group-broadcast group call setup procedure involving MCPTT clients, server, and IWF. + +**Figure 10.3.4.3-1: Group-broadcast group call involving IWF (group-broadcast group defined in the LMR system)** + +1. MCPTT user at MCPTT client 1 initiates the group-broadcast group call setup procedure. +2. The MCPTT client 1 sends a group-broadcast group call request to the MCPTT server. +3. As the group-broadcast group is defined in the LMR system the MCPTT server sends an IWF group-broadcast group call setup request to the IWF. + +4. The IWF performs group call release procedures of groups defined in the LMR system as described in subclause 10.3.3.8.3. +5. The IWF issues a group-broadcast group call setup request to establish the group-broadcast call. +6. The MCPTT user of MCPTT client 2 is notified. + +NOTE: How LMR user(s) is(are) notified of the incoming group-broadcast group call is outside the scope of the present document. + +7. Optionally, MCPTT client 2 respond with a group-broadcast group call response to the MCPTT server and then to the IWF. +8. The MCPTT server responds to MCPTT client 1 (the call initiator) that the group-broadcast group call has been established by sending a group-broadcast group call response. +9. The MCPTT client 1 notifies its user that the user can begin transmitting using the group-broadcast group call resources. + +Once the user of MCPTT client 1 completes transmitting, the group-broadcast group call is released. + +#### **10.3.4.4 Group-broadcast group call release with an interworking group procedure where the group-broadcast group is defined in the MCPTT system** + +When the call originator has completed transmitting, the group-broadcast group call is ended and the resources are released. + +Figure 10.3.4.4-1 illustrates the procedure for group-broadcast group call release (the group-broadcast group is defined in the MCPTT system). + +Pre-conditions: + +1. An on-going group-broadcast group call involving MCPTT client 1, the MCPTT client 2 and the IWF exists. + +![Sequence diagram illustrating the termination of a group-broadcast group call. Lifelines: MCPTT user, MCPTT client 1, MCPTT server, MCPTT client 2, IWF. The sequence shows a release request from the user to the server, a release request from the server to clients 2 and the IWF, a notification from client 2 and the IWF to the user, and a final release response from the server to the user.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +``` + +sequenceDiagram + participant User as MCPTT user + participant Client1 as MCPTT client 1 + participant Server as MCPTT server + participant Client2 as MCPTT client 2 + participant IWF as IWF + + Note over User, Client1: 1. MCPTT user on MCPTT client 1 finished transmitting. + Client1->>Server: 2. group-broadcast group call release request + Note over Server: 3. group-broadcast group call release request + Server-->>Client2: + Server-->>IWF: + Note over Client2, IWF: 4. notify users + Client2-->>Server: 5. group-broadcast group call release response + IWF-->>Server: + Server->>Client1: 6. group-broadcast group call release response + Note over User, IWF: group-broadcast group call transmission ended + +``` + +Sequence diagram illustrating the termination of a group-broadcast group call. Lifelines: MCPTT user, MCPTT client 1, MCPTT server, MCPTT client 2, IWF. The sequence shows a release request from the user to the server, a release request from the server to clients 2 and the IWF, a notification from client 2 and the IWF to the user, and a final release response from the server to the user. + +**Figure 10.3.4.4-1: Group-broadcast group call transmission ended (group-broadcast group is defined in the MCPTT system)** + +1. MCPTT user on MCPTT client 1 finished transmitting. + 2. A group-broadcast group call release request is sent to the MCPTT server of the group-broadcast group. + 3. The MCPTT users of MCPTT client 2 and the IWF of the group-broadcast group's subordinate groups are sent a group-broadcast group call release request. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call release request is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call request is sent (to the IWF) for each affiliated LMR user. + 4. MCPTT client 2 and the IWF notify their users that the group-broadcast group call has ended. +- NOTE: How LMR user(s) is(are) notified that the group-broadcast group call has ended is outside the scope of the present document. +5. MCPTT client 2 and the IWF respond to confirm the release of the group-broadcast group call by sending a group-broadcast group call release response. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF group-broadcast group call release response is sent to the MCPTT server. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF group-broadcast group call response is sent (to the MCPTT server) for each affiliated LMR user. + 6. The MCPTT server sends a group-broadcast group call release response indicating to the initiator that the call is now ended. + +### 10.3.4.5 Group-broadcast group call release with an interworking group procedure where the group-broadcast group is defined in the LMR system + +When the call originator has completed transmitting, the group-broadcast group call is ended and the resources are released. + +Figure 10.3.4.5-1 illustrates the procedure for group-broadcast group call release (the group-broadcast group defined in the LMR system). + +Pre-conditions: + +- 1. An on-going group-broadcast group call involving MCPTT client 1, the MCPTT client 2 and the IWF exists. + +![Sequence diagram showing the group-broadcast group call release procedure. Lifelines: MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. The sequence starts with MCPTT client 1 sending a 'GROUP BROADCAST GROUP CALL RELEASE REQUEST' to the MCPTT server. The MCPTT server then sends an 'IWF GROUP BROADCAST GROUP CALL RELEASE REQUEST' to the IWF. The IWF sends a response 'IWF GROUP BROADCAST GROUP CALL RELEASE RESPONSE' back to the MCPTT server. The MCPTT server then sends a 'GROUP BROADCAST GROUP CALL RELEASE REQUEST' to MCPTT client 2. Finally, MCPTT client 2 sends a 'GROUP BROADCAST GROUP CALL RELEASE RESPONSE' back to the MCPTT server.](367378559e35017a5e1a6f5c30798c5a_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT server + participant IWF + Note left of MCPTT client 1: MCPTT user on MCPTT client 1 finished transmitting. + MCPTT client 1->>MCPTT server: GROUP BROADCAST GROUP CALL RELEASE REQUEST + MCPTT server->>IWF: IWF GROUP BROADCAST GROUP CALL RELEASE REQUEST + IWF-->>MCPTT server: IWF GROUP BROADCAST GROUP CALL RELEASE RESPONSE + MCPTT server->>MCPTT client 2: GROUP BROADCAST GROUP CALL RELEASE REQUEST + MCPTT client 2-->>MCPTT server: GROUP BROADCAST GROUP CALL RELEASE RESPONSE + +``` + +Sequence diagram showing the group-broadcast group call release procedure. Lifelines: MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. The sequence starts with MCPTT client 1 sending a 'GROUP BROADCAST GROUP CALL RELEASE REQUEST' to the MCPTT server. The MCPTT server then sends an 'IWF GROUP BROADCAST GROUP CALL RELEASE REQUEST' to the IWF. The IWF sends a response 'IWF GROUP BROADCAST GROUP CALL RELEASE RESPONSE' back to the MCPTT server. The MCPTT server then sends a 'GROUP BROADCAST GROUP CALL RELEASE REQUEST' to MCPTT client 2. Finally, MCPTT client 2 sends a 'GROUP BROADCAST GROUP CALL RELEASE RESPONSE' back to the MCPTT server. + +**Figure 10.3.4.5-1: Group-broadcast group call transmission ended (group-broadcast group defined in the LMR system)** + +- 1. The MCPTT user on MCPTT client 1 finished transmitting. +- 2. A group-broadcast group call release request is sent to the MCPTT server. +- 3. As the group-broadcast group is defined in the LMR system the MCPTT server sends an IWF group-broadcast group call release request to the IWF. +- 4. The IWF sends an IWF group-broadcast group call release request to the MCPTT server hosting client 2. The MCPTT server sends the group-broadcast group call release request to MCPTT client 2. +- 5. MCPTT client 2 is notified that the group-broadcast group call has ended. + +NOTE: How LMR user(s) is(are) notified that the group-broadcast group call has ended is outside the scope of the present document. + +- 6. MCPTT client 2 responds to confirm the release of the group-broadcast group call by sending a group-broadcast group call release response. + +7. The MCPTT server sends an IWF group-broadcast group call release response to the IWF. The IWF becomes aware that MCPTT client 2 has confirmed the group-broadcast group call release and replies with another IWF group-broadcast group call release response back to the MCPTT server to trigger step 8. +8. The MCPTT server sends a group-broadcast group call release response indicating to the initiator that the group-broadcast group call is now ended. + +#### 10.3.4.6 Broadcast group regroup call using pre-configured group + +##### 10.3.4.6.1 General + +The temporary group created using a pre-configured group can be a broadcast group or a non-broadcast group. + +A broadcast group regroup call using pre-configured groups can be achieved by first regrouping users into a pre-configured group regroup, making the broadcast group call on the pre-configured group, and then cancelling the pre-configured group regroup. + +##### 10.3.4.6.2 Broadcast group regroup call using pre-configured group the MCPTT system + +The broadcast group regroup call procedure using pre-configured group allows an authorized MCPTT user to initiate a broadcast call to a set of MCPTT groups, which are regrouped only for the duration of the broadcast call. The regroup is cancelled at the end of the broadcast call to prevent users from talking back on the pre-configured group regroup. This procedure requires that the authorized MCPTT user is a group member of at least one of the MCPTT groups included in the regroup operation. + +Figure 10.3.4.6.2-1 illustrates the procedure to initiate a broadcast group regroup call using a pre-configured MCPTT regroup group owned by the MCPTT system. For simplicity, no receiving clients are shown. + +Pre-conditions: + +- The MCPTT client is registered with the MCPTT service. +- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the MCPTT client and the IWF. The MCPTT client and the IWF have received the relevant security related information to allow them to communicate in the pre-configured group regroup. +- The MCPTT client is authorized to initiate a pre-configured group regroup using the pre-configured group regroup procedure. +- The MCPTT client is aware of a suitable pre-configured group whose configuration has been pre-configured in the IWF and the MC service UEs of the MCPTT users who will be regrouped. +- The MCPTT client is affiliated to group 1. +- The IWF is affiliated to one or more of MCPTT group 1, 2 or 3. +- The pre-configured group regroup is homed in the MCPTT server. +- The IWF is home to at least one group that's a constituent group of the pre-configured group regroup. + +![Sequence diagram illustrating the broadcast group regroup call using pre-configured group in the MCPTT system. Lifelines: IWF, MCPTT Client 1, MCPTT Client 2, MCPTT Client 3. The sequence starts with the IWF sending a '1. Initiate pre-configured group regroup' message to MCPTT Client 1. MCPTT Client 1 responds with '2. Confirm regroup authorization'. The IWF then sends '3. MCPTT group regroup request' to MCPTT Client 2 and '4. MCPTT group regroup request' to MCPTT Client 3. MCPTT Client 2 and 3 both respond with '5. MCPTT group regroup response'. Finally, the IWF sends '6. MCPTT group regroup' to MCPTT Client 1, which responds with '7. MCPTT group regroup response'.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT Client 3 + Note left of IWF: 1. Initiate pre-configured group regroup + IWF->>MCPTT Client 1: 1. Initiate pre-configured group regroup + MCPTT Client 1-->>IWF: 2. Confirm regroup authorization + Note right of MCPTT Client 1: 3. MCPTT group regroup request + MCPTT Client 1->>MCPTT Client 2: 3. MCPTT group regroup request + MCPTT Client 1->>MCPTT Client 3: 4. MCPTT group regroup request + MCPTT Client 2-->>MCPTT Client 1: 5. MCPTT group regroup response + MCPTT Client 3-->>MCPTT Client 1: 5. MCPTT group regroup response + Note right of MCPTT Client 1: 6. MCPTT group regroup + MCPTT Client 1->>IWF: 6. MCPTT group regroup + IWF-->>MCPTT Client 1: 7. MCPTT group regroup response + +``` + +Sequence diagram illustrating the broadcast group regroup call using pre-configured group in the MCPTT system. Lifelines: IWF, MCPTT Client 1, MCPTT Client 2, MCPTT Client 3. The sequence starts with the IWF sending a '1. Initiate pre-configured group regroup' message to MCPTT Client 1. MCPTT Client 1 responds with '2. Confirm regroup authorization'. The IWF then sends '3. MCPTT group regroup request' to MCPTT Client 2 and '4. MCPTT group regroup request' to MCPTT Client 3. MCPTT Client 2 and 3 both respond with '5. MCPTT group regroup response'. Finally, the IWF sends '6. MCPTT group regroup' to MCPTT Client 1, which responds with '7. MCPTT group regroup response'. + +**Figure 10.3.4.6.2-1: Broadcast group regroup call using pre-configured group in the MCPTT system** + +1. The authorized user of the MCPTT client initiates the pre-configured group regroup formation procedure using pre-configured groups as specified in subclause 10.3.7.1. MCPTT groups 1, 2, and 3 are regrouped into group 4. +2. The MCPTT user at the MCPTT client performs the broadcast group call procedure as specified in subclause 10.3.4. +3. The MCPTT client initiates the pre-configured group regroup cancellation procedure using pre-configured groups as specified in subclause 10.3.7.1. + +#### 10.3.4.6.3 Broadcast group regroup call using pre-configured group in the IWF + +The broadcast group regroup call procedure using a pre-configured group allows an IWF user to initiate a broadcast call to a set of MCPTT groups, which are regrouped only for the duration of the broadcast call. + +Figure 10.3.4.6.3-1 illustrates the procedure to initiate a broadcast group regroup call using a pre-configured group owned by the IWF. + +Pre-conditions: + +- MCPTT clients 1 and 2 are registered with the MCPTT service. +- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in MCPTT clients 1 and 2, and MCPTT clients 1 and 2 have received the relevant security related information to allow them to communicate in the pre-configured group regroup. +- MCPTT client 1 is affiliated to group 1, MCPTT client 2 is affiliated to group 2. Group 3 is used as the pre-configured group regroup. +- The pre-configured group regroup is homed in the IWF. +- The MCPTT server is home to at least one group that's a constituent group of the pre-configured group regroup. + +![Sequence diagram for Broadcast group regroup call using pre-configured group in the IWF. Lifelines: MCPTT User 1, MCPTT User 2, MCPTT Server, IWF. The sequence starts with MCPTT User 1 sending a '1. DELGATE MR REQUEST' to the MCPTT Server. The MCPTT Server sends a '2. MCPTT GROUP REGROUP REQUEST' to the IWF. The IWF sends a '3. CREATE GROUP REGROUPING' message to MCPTT User 2. MCPTT User 2 responds with '4. MCPTT GROUP REGROUP RESPONSE'. The IWF then sends '5. MCPTT GROUP REGROUP RESPONSE' to the MCPTT Server. The MCPTT Server sends '6. DELGATE MR RESPONSE' to MCPTT User 1. Finally, the IWF sends '7. CLEAR GROUP REGROUP' to MCPTT User 2.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +``` + +sequenceDiagram + participant MCPTT User 1 + participant MCPTT User 2 + participant MCPTT Server + participant IWF + Note left of MCPTT User 1: 1. DELGATE MR REQUEST + MCPTT User 1->>MCPTT Server: 1. DELGATE MR REQUEST + MCPTT Server->>IWF: 2. MCPTT GROUP REGROUP REQUEST + IWF->>MCPTT User 2: 3. CREATE GROUP REGROUPING + MCPTT User 2-->>IWF: 4. MCPTT GROUP REGROUP RESPONSE + IWF->>MCPTT Server: 5. MCPTT GROUP REGROUP RESPONSE + MCPTT Server-->>MCPTT User 1: 6. DELGATE MR RESPONSE + IWF->>MCPTT User 2: 7. CLEAR GROUP REGROUP + +``` + +Sequence diagram for Broadcast group regroup call using pre-configured group in the IWF. Lifelines: MCPTT User 1, MCPTT User 2, MCPTT Server, IWF. The sequence starts with MCPTT User 1 sending a '1. DELGATE MR REQUEST' to the MCPTT Server. The MCPTT Server sends a '2. MCPTT GROUP REGROUP REQUEST' to the IWF. The IWF sends a '3. CREATE GROUP REGROUPING' message to MCPTT User 2. MCPTT User 2 responds with '4. MCPTT GROUP REGROUP RESPONSE'. The IWF then sends '5. MCPTT GROUP REGROUP RESPONSE' to the MCPTT Server. The MCPTT Server sends '6. DELGATE MR RESPONSE' to MCPTT User 1. Finally, the IWF sends '7. CLEAR GROUP REGROUP' to MCPTT User 2. + +**Figure 10.3.4.6.3-1: Broadcast group regroup call using pre-configured group in the IWF** + +1. The IWF initiates the group regroup formation procedure using pre-configured groups as specified in subclause 10.3.7.1. MCPTT groups 1 and 2 are regrouped into group 3. +2. The IWF performs the broadcast group call procedure as specified in subclause 10.3.4. +3. The IWF initiates the pre-configured group regroup cancellation procedure using pre-configured groups as specified in subclause 10.3.7.1. + +## 10.3.5 Chat group call + +### 10.3.5.1 General + +This subclause is based upon subclause for chat group call in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.2. For LMR systems that do not support the concept of chat groups, the IWF might still adapt its calls to the MCPTT chat model. + +### 10.3.5.2 MCPTT user initiated chat group call in an interworking group defined in LMR system + +In this procedure, an MCPTT user initiates a chat group call in an interworking group defined in the LMR system. The signalling procedure is described in figure 10.3.5.2-1. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system. +2. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +NOTE: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for MCPTT user initiated chat group call in an interworking group defined in the LMR system. Lifelines: UE, MCPTT SERVER, MCPTT CLIENT 1, MCPTT CLIENT 2. The sequence starts with UE sending a GROUP JOIN REQUEST to MCPTT SERVER. MCPTT SERVER responds with a GROUP JOIN RESPONSE. MCPTT SERVER then sends a GROUP JOIN REQUEST to MCPTT CLIENT 1 and MCPTT CLIENT 2. MCPTT CLIENT 1 and MCPTT CLIENT 2 respond with GROUP JOIN RESPONSE. MCPTT SERVER then sends a MEDIA PLANE ESTABLISHED message to UE.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +``` + +sequenceDiagram + participant UE + participant MCPTT_SERVER as MCPTT SERVER + participant MCPTT_CLIENT_1 as MCPTT CLIENT 1 + participant MCPTT_CLIENT_2 as MCPTT CLIENT 2 + + Note right of MCPTT_CLIENT_1: ALREADY AFFILIATED + Note right of MCPTT_CLIENT_2: ALREADY AFFILIATED + + UE->>MCPTT_SERVER: GROUP JOIN REQUEST + MCPTT_SERVER-->>UE: GROUP JOIN RESPONSE + MCPTT_SERVER->>MCPTT_CLIENT_1: GROUP JOIN REQUEST + MCPTT_SERVER->>MCPTT_CLIENT_2: GROUP JOIN REQUEST + MCPTT_CLIENT_1-->>MCPTT_SERVER: GROUP JOIN RESPONSE + MCPTT_CLIENT_2-->>MCPTT_SERVER: GROUP JOIN RESPONSE + MCPTT_SERVER-->>UE: MEDIA PLANE ESTABLISHED + +``` + +Sequence diagram for MCPTT user initiated chat group call in an interworking group defined in the LMR system. Lifelines: UE, MCPTT SERVER, MCPTT CLIENT 1, MCPTT CLIENT 2. The sequence starts with UE sending a GROUP JOIN REQUEST to MCPTT SERVER. MCPTT SERVER responds with a GROUP JOIN RESPONSE. MCPTT SERVER then sends a GROUP JOIN REQUEST to MCPTT CLIENT 1 and MCPTT CLIENT 2. MCPTT CLIENT 1 and MCPTT CLIENT 2 respond with GROUP JOIN RESPONSE. MCPTT SERVER then sends a MEDIA PLANE ESTABLISHED message to UE. + +**Figure 10.3.5.2-1: MCPTT user initiated chat group call in an interworking group defined in the LMR system** + +1. MCPTT user of the MCPTT client indicates to join the group communication for the group. The MCPTT client joins the group by sending a group join request to the MCPTT server. If there is a request to transmit, then the group join request contains an indication of an implicit floor request and the location of the joining party if required. +2. The MCPTT server inspects the Group join request for presence of location information of the calling party. If location information is included in the join request, the MCPTT server checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the requesting MCPTT user to decide if the user's location information may be provided to other MCPTT users on the call and the IWF. +3. The MCPTT server notices that the interworking group is defined in the LMR system and forwards the group join request with or without location depending on the outcome of the privacy check as an IWF group join request to the IWF. +4. The IWF replies with an IWF group join response indicating the acceptance of the group join request and also returns the IWF selected media parameters for the chat group call in the IWF group join response. +5. The MCPTT server forwards the IWF group join response to the MCPTT client as a group join response. +6. If the MCPTT client requests to transmit, the MCPTT server establishes the media plane (if not already established) for the call. +7. Floor control will continue to be used by the floor participants associated with the MCPTT client and the IWF for the duration of the call. Media plane signalling using floor control will be used for subsequent calls for the group as long as one or more users are affiliated. + +### 10.3.5.3 LMR user initiated chat group call in an interworking group defined in MCPTT system + +In this procedure, an LMR user initiates a chat group call in an interworking group defined in the MCPTT system. The signalling procedure is described in figure 10.3.5.3-1. + +Pre-conditions: + +1. The interworking group information is known at the IWF by configuration. The interworking group has been defined in the MCPTT system. + +2. MCPTT user 1 and MCPTT user 2 have previously joined (affiliated) to the group. +3. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +4. LMR user initiates a join to the group. + +NOTE: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for LMR user initiated chat group call in an interworking group defined in the MCPTT system. The diagram shows four lifelines: MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF. The sequence of messages is: 1. MCPTT Client 1 sends a 'JOIN' message to the MCPTT Server. 2. The MCPTT Server sends a 'JOIN RESPONSE' message to the MCPTT Client 1. 3. The MCPTT Server sends a 'JOIN REQUEST' message to the IWF. 4. The IWF sends a 'JOIN RESPONSE' message to the MCPTT Server. 5. The MCPTT Server sends a 'JOIN RESPONSE' message to the MCPTT Client 2. 6. The MCPTT Client 2 sends a 'JOIN' message to the MCPTT Server.](3c04b14104f95eb8f7100f6d497d956e_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT Server + participant IWF + Note left of MCPTT Client 1: MCPTT Client 1 + Note left of MCPTT Client 2: MCPTT Client 2 + Note left of MCPTT Server: MCPTT Server + Note left of IWF: IWF + MCPTT Client 1->>MCPTT Server: JOIN + MCPTT Server-->>MCPTT Client 1: JOIN RESPONSE + MCPTT Server->>IWF: JOIN REQUEST + IWF-->>MCPTT Server: JOIN RESPONSE + MCPTT Server-->>MCPTT Client 2: JOIN RESPONSE + MCPTT Client 2->>MCPTT Server: JOIN + +``` + +Sequence diagram for LMR user initiated chat group call in an interworking group defined in the MCPTT system. The diagram shows four lifelines: MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF. The sequence of messages is: 1. MCPTT Client 1 sends a 'JOIN' message to the MCPTT Server. 2. The MCPTT Server sends a 'JOIN RESPONSE' message to the MCPTT Client 1. 3. The MCPTT Server sends a 'JOIN REQUEST' message to the IWF. 4. The IWF sends a 'JOIN RESPONSE' message to the MCPTT Server. 5. The MCPTT Server sends a 'JOIN RESPONSE' message to the MCPTT Client 2. 6. The MCPTT Client 2 sends a 'JOIN' message to the MCPTT Server. + +**Figure 10.3.5.3-1: LMR user initiated chat group call in an interworking group defined in the MCPTT system** + +1. The IWF sends an IWF group join request to the MCPTT server. The request to join may contain location information of the transmitting party. If there is a request to transmit, then the IWF group join request contains an indication of an implicit floor request and the location of the joining party if required. +2. The MCPTT server checks whether the MCPTT ID is authorized to affiliate to the group. MCPTT server generates an implicit affiliation if the MCPTT ID is not already affiliated to the group. +3. The MCPTT server replies with a group join response indicating the acceptance of the group join request and also returns the MCPTT server selected media parameters for the chat group call in the IWF group join response. +4. If the IWF requests to transmit, the MCPTT server establishes the media plane (if not already established) for the call. +5. Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and the IWF for the duration of the call. Media plane signalling using floor control will be used for subsequent calls for the group as long as one or more users are affiliated. + +#### 10.3.5.4 Release chat group call on an interworking group defined in the LMR system + +This procedure describes the case where the LMR system releases an ongoing MCPTT chat group call on an interworking group defined in the LMR system, for all the participants of that group call. The signalling procedure is described in figure 10.3.5.4-1. + +Pre-conditions: + +1. A chat group call is ongoing involving an MCPTT client and the IWF. + +2. The LMR system initiates release of the chat group call. + +![Sequence diagram showing the release of a chat group call between MCPTT client, MCPTT server, and IWF.](376f80eb8a41369e87da63a0210d173e_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note over IWF: 1. IWF group call release request + IWF->>MCPTT server: + Note over MCPTT server: 2. MCPTT group call release request + MCPTT server->>MCPTT client: + Note over MCPTT client: 3. Release notification + Note over MCPTT client: 4. MCPTT group call release response + MCPTT client->>MCPTT server: + Note over MCPTT server: 5. IWF group call release response + MCPTT server->>IWF: + Note over MCPTT client, IWF: 6. Release floor control and media plane resources + +``` + +Sequence diagram showing the release of a chat group call between MCPTT client, MCPTT server, and IWF. + +**Figure 10.3.5.4-1: Release chat group call on an interworking group defined in the LMR system** + +1. The IWF sends an IWF group call release request to the MCPTT server. An individual IWF group call release request is sent for each MCPTT user in the call. +2. MCPTT server forwards the release request(s) to the group's MCPTT users, as described in 3GPP TS 23.379 [7]. +3. MCPTT users are notified about the release of the group call. +4. Optionally, the MCPTT client confirms the group call release request received in step 2 with a group call release response to the MCPTT server. +5. The MCPTT server forwards the group call release response to the IWF as an IWF group call release response. +6. The MCPTT client and the IWF release the floor control and media plane resources associated with the chat group call that is released. Successful release of the chat group call does not affect the status of affiliation of any of the clients. + +### 10.3.5.5 Release chat group call on an interworking group defined in the MCPTT system + +This procedure describes the case where the MCPTT server releases an ongoing MCPTT chat group call, on an interworking group defined in the MCPTT system, for all the participants of that group call, since at least one of the conditions for release are met e.g. due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or the number of affiliated MCPTT group members is below the minimum number permitted. + +The signalling procedure is described in figure 10.3.5.5-1. + +Pre-conditions: + +1. A chat group call is ongoing involving MCPTT clients 1, 2 and the IWF. + +![Sequence diagram showing the release of a chat group call. Lifelines include MCPTT Client 1, MCPTT Client 2, MCPTT Client 3, and IWF. The MCPTT server (part of the MCPTT system) sends release requests to the IWF and the clients. The IWF sends a response to the server. The server then notifies the clients. The clients and IWF release resources.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT Client 3 + participant IWF + participant MCPTT System as MCPTT System (MCPTT Server) + + Note right of MCPTT System: MCPTT server decides to release the call + MCPTT System->>IWF: IWF group call release request + MCPTT System->>MCPTT Client 1: Group call release request + MCPTT System->>MCPTT Client 2: Group call release request + MCPTT System->>MCPTT Client 3: Group call release request + IWF-->>MCPTT System: IWF group call release response + MCPTT System-->>MCPTT Client 1: Group call release response + MCPTT System-->>MCPTT Client 2: Group call release response + MCPTT System-->>MCPTT Client 3: Group call release response + Note left of MCPTT Client 1: MCPTT client releases resources + Note left of MCPTT Client 2: MCPTT client releases resources + Note left of MCPTT Client 3: MCPTT client releases resources + Note left of IWF: IWF releases resources + +``` + +Sequence diagram showing the release of a chat group call. Lifelines include MCPTT Client 1, MCPTT Client 2, MCPTT Client 3, and IWF. The MCPTT server (part of the MCPTT system) sends release requests to the IWF and the clients. The IWF sends a response to the server. The server then notifies the clients. The clients and IWF release resources. + +**Figure 10.3.5.5-1: Release chat group call on an interworking group defined in the MCPTT system** + +1. The MCPTT server decides to release the MCPTT chat group call which is ongoing e.g., due to hang time expiry, last participant leaving, second last participant leaving, initiator leaving, or minimum number of affiliated MCPTT group members are not present. +2. The MCPTT server sends an IWF group call release request to the IWF to release the ongoing session. If the IWF has joined itself to this group on behalf of all the group's LMR users, only one IWF group call release request message is sent to the IWF. If the MCPTT server has received individual joins from the group's LMR users, an individual IWF group call release request is sent to the IWF for each joined LMR user. +3. The MCPTT server sends a group call release request towards each MCPTT participant of the ongoing group call. +4. The MCPTT users are notified about the release of the group call. +5. The IWF confirms the IWF group call release request(s) received in step 2 by IWF group call release response(s) to the MCPTT server. +6. Optionally, the MCPTT client(s) receiving a group call release request may send a group call release response to the MCPTT server. +7. MCPTT client 1, client 2 and the IWF release the floor control and media plane resources associated with the chat group call that is released. Successful release of the chat group call does not affect the status of affiliation of any of the clients. + +10.3.5.6 void + +10.3.5.7 void + +10.3.5.8 Newly joined MCPTT group member of a group defined in the LMR system + +Procedures in figure 10.3.5.8-1 are those for a group member entering an ongoing MCPTT group call, i.e. performing a late entry. + +Pre-conditions: + +1. The MCPTT client is registered and the MCPTT user has been authenticated and authorized to use the MCPTT service. +2. There is an ongoing group call on the group homed on the LMR system. +3. The MCPTT client has not yet joined the group call. +4. The MCPTT user indicates to join the group call. + +![Sequence diagram for 'Late entry of a newly joined MCPTT group member'. Lifelines: MCPTT Client, MCPTT Server, IWF, LMR System. The client sends a 'GROUP JOIN REQUEST' to the server, which is forwarded to the IWF. The IWF responds with 'GROUP JOIN RESPONSE', which the server forwards to the client. The IWF then establishes the media plane with the client and sends a 'FLOOR TAKEN' message to the server, which is forwarded to the client.](742a5484e7dd016256ab99921bbd635d_img.jpg) + +``` + +sequenceDiagram + participant Client as MCPTT Client + participant Server as MCPTT Server + participant IWF as IWF + participant LMR as LMR System + + Note right of Client: GROUP JOIN REQUEST + Client->>Server: GROUP JOIN REQUEST + Note right of Server: FORWARD TO IWF + Server->>IWF: GROUP JOIN REQUEST + Note right of IWF: GROUP JOIN RESPONSE + IWF->>Server: GROUP JOIN RESPONSE + Note right of Server: FORWARD TO CLIENT + Server->>Client: GROUP JOIN RESPONSE + Note right of IWF: ESTABLISH MEDIA PLANE WITH CLIENT + IWF->>Client: ESTABLISH MEDIA PLANE WITH CLIENT + Note right of IWF: FLOOR TAKEN + IWF->>Server: FLOOR TAKEN + Note right of Server: FORWARD TO CLIENT + Server->>Client: FLOOR TAKEN + +``` + +Sequence diagram for 'Late entry of a newly joined MCPTT group member'. Lifelines: MCPTT Client, MCPTT Server, IWF, LMR System. The client sends a 'GROUP JOIN REQUEST' to the server, which is forwarded to the IWF. The IWF responds with 'GROUP JOIN RESPONSE', which the server forwards to the client. The IWF then establishes the media plane with the client and sends a 'FLOOR TAKEN' message to the server, which is forwarded to the client. + +Figure 10.3.5.8-1: Late entry of a newly joined MCPTT group member + +1. The MCPTT client sends a group join request with the MCPTT group ID of the desired group to the MCPTT server. If there is a request to transmit, then the group joint request contains an indication of an implicit floor request. +2. The MCPTT server forwards the request to the IWF. +3. The IWF replies with a group join response indicating the acceptance of the group join request. +4. The MCPTT server forwards the response to the MCPTT client. +5. The IWF establishes the media plane with the MCPTT client. +6. The IWF may notify its users that an MCPTT user has joined the group. +- 7 a. The IWF sends an IWF floor taken (for the current talker) to the MCPTT server if the floor has been taken. +- 7b. The MCPTT responds to any incoming IWF floor taken message by forwarding a floor taken message to the MCPTT client. +8. Floor control will continue to be used by the floor participants. + +### 10.3.5.9 Newly joined LMR group member of a group defined in the MCPTT system + +Procedures in figure 10.3.5.9-1 are those for the IWF entering an ongoing MCPTT group call, i.e. performing a late entry. + +Pre-conditions: + +1. MCPTT user 1 and MCPTT user 2 have previously joined to the group. +2. MCPTT users using MCPTT client 1 and MCPTT client 2 are in an ongoing group call. +3. The IWF has not yet joined the group call. + +![Sequence diagram illustrating the late entry of a newly joined LMR group member. The diagram shows three lifelines: MCPTT user 1, MCPTT user 2, and IWF. MCPTT user 1 sends a 'Group Join Request' to the IWF. The IWF receives the request and sends a 'Group Join Response' back to MCPTT user 1. MCPTT user 2 is shown receiving a message from the IWF, likely indicating the IWF's joining the group.](74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg) + +``` + +sequenceDiagram + participant MCPTT user 1 + participant MCPTT user 2 + participant IWF + Note right of MCPTT user 1: Group Join Request + MCPTT user 1->>IWF: Group Join Request + Note right of IWF: Group Join Response + IWF-->>MCPTT user 1: Group Join Response + Note right of IWF: Notify MCPTT user 2 + IWF-->>MCPTT user 2: Notify MCPTT user 2 + +``` + +Sequence diagram illustrating the late entry of a newly joined LMR group member. The diagram shows three lifelines: MCPTT user 1, MCPTT user 2, and IWF. MCPTT user 1 sends a 'Group Join Request' to the IWF. The IWF receives the request and sends a 'Group Join Response' back to MCPTT user 1. MCPTT user 2 is shown receiving a message from the IWF, likely indicating the IWF's joining the group. + +**Figure 10.3.5.9-1: Late entry of a newly joined LMR group member** + +1. The IWF sends a group join request with the MCPTT group ID of the desired group and either using the MCPTT ID corresponding to the LMR group member or using the pre-configured MCPTT ID for use when the IWF is affiliating itself on behalf of the group's LMR users. If there is a request to transmit, then the group join request contains an indication of an implicit floor request. If the group join request includes an implicit floor request it may also include location information. +2. The MCPTT server receives the group join request. MCPTT server generates an implicit affiliation using the MCPTT ID used by the IWF (if the IWF or the LMR user is not already affiliated to the group) and verifies that IWF is authorized to affiliate to the group. +3. The MCPTT server replies with a group join response indicating the acceptance of the group join request. +4. The MCPTT server establishes the media plane between the IWF and the MCPTT server. +5. MCPTT users at MCPTT client 1 and MCPTT client 2 may be notified about the IWF joining the group call. +6. The MCPTT server sends a floor taken (for the current talker) to the IWF. +7. Floor control will continue to be used by the floor participants associated with MCPTT client 1, MCPTT client 2 and the IWF. + +#### 10.3.5.10 MCPTT client returning to coverage on a group homed in the LMR system + +Procedures in figure 10.3.5.10-1 are those for an MCPTT client returning to coverage during an ongoing MCPTT chat group call. + +Pre-conditions: + +1. The MCPTT user using an MCPTT client is in an ongoing chat group call when the MCPTT client goes out of radio coverage. + +![Sequence diagram illustrating the late entry of an MCPTT client returning from out of coverage. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The client sends a message to the IWF, which then forwards it to the server. The server sends a response back to the IWF, which then forwards it back to the client.](5801c19431e76330430e92a598cc7a16_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note left of MCPTT client: MCPTT client returns from out of coverage + MCPTT client->>IWF: Media plane control signalling + IWF->>MCPTT server: IWF floor taken + MCPTT server->>MCPTT client: floor taken message + Note right of MCPTT client: Floor control continues + +``` + +Sequence diagram illustrating the late entry of an MCPTT client returning from out of coverage. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The client sends a message to the IWF, which then forwards it to the server. The server sends a response back to the IWF, which then forwards it back to the client. + +**Figure 10.3.5.10-1: Late entry of a MCPTT client returning from out of coverage** + +1. The MCPTT client or MCPTT server detects that MCPTT client has returned to coverage. + +NOTE: How the MCPTT client or MCPTT server detects that the client has returned to coverage is out of scope of the present document. + +2. The media plane between the MCPTT client and the IWF are re-established using media plane control signalling +- 3a. The IWF sends an IWF floor taken to the MCPTT server if anyone currently has the floor. +- 3b. The MCPTT server forwards a floor taken message to the MC Client if anyone currently has the floor. +4. Floor control will continue to be used by the floor participants. + +## 10.3.6 Exiting group call due to de-affiliation + +### 10.3.6.1 General + +The following procedures are applicable both for the pre-arranged and chat group calls. + +### 10.3.6.2 Exiting group call defined in the LMR system due to de-affiliation + +Procedures in figure 10.3.6.2-1 are the signalling control plane procedures for the IWF requesting a newly de-affiliated MCPTT user to leave an ongoing MCPTT group call. + +Pre-conditions: + +1. The MCPTT group is previously defined on the IWF with MCPTT users affiliated to that group. At least one user is an LMR user represented by an MCPTT ID. +2. An MCPTT user on the MCPTT client and an LMR user via the IWF, are on an ongoing call. + +![Sequence diagram for exiting MCPTT group call due to de-affiliation. Lifelines: IWF, MCPTT server, MCPTT client 1, MCPTT client 2. The sequence shows the IWF sending a group call request, the server affiliating users, the IWF receiving responses, the media plane being established, and subsequent floor control messages (granted, taken) between the IWF and the clients.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + + Note left of IWF: Error: - ^ + IWF->>MCPTT server: 1. IWF group call request + MCPTT server->>MCPTT client 1: 2. Call affiliated MCPTT users + MCPTT server->>MCPTT client 2: 2. Call affiliated MCPTT users + MCPTT server-->>IWF: 3. IWF group call request + IWF-->>MCPTT server: 4. IWF group call response + MCPTT server-->>IWF: 5. IWF group call response + Note right of MCPTT server: 6. Media plane is established + IWF->>MCPTT server: 7. IWF floor granted + MCPTT server->>MCPTT client 1: 7. Floor taken + MCPTT server->>MCPTT client 2: 7. Floor taken + MCPTT server-->>IWF: 8. IWF floor taken + Note left of IWF: 9. LMR user talker ID is received by the IWF + IWF->>MCPTT server: 10. IWF Talker ID update + MCPTT server->>MCPTT client 1: 11. Floor taken + MCPTT server->>MCPTT client 2: 11. Floor taken + IWF-->>MCPTT server: 12. IWF floor taken + +``` + +Sequence diagram for exiting MCPTT group call due to de-affiliation. Lifelines: IWF, MCPTT server, MCPTT client 1, MCPTT client 2. The sequence shows the IWF sending a group call request, the server affiliating users, the IWF receiving responses, the media plane being established, and subsequent floor control messages (granted, taken) between the IWF and the clients. + +**Figure 10.3.6.2-1: Exiting MCPTT group call due to de-affiliation** + +1. The MCPTT client is de-affiliated. +2. The IWF sends an IWF group call leave request to the MCPTT client via the MCPTT server. +3. The MCPTT server forwards the IWF group call leave request as a group call leave request to the MCPTT client. +4. The MCPTT user at the MCPTT client is notified about leaving the group call. +5. The MCPTT client sends the group call leave response to the MCPTT server and leaves the group call. +6. The MCPTT server forwards the group call leave response to the IWF as an IWF group call leave response. +7. The MCPTT client is now removed from the ongoing group call. + +### 10.3.6.3 Exiting group call defined in the MCPTT system due to de-affiliation + +Procedures in figure 10.3.6.3-1 are the signalling control plane procedures for the MCPTT server requesting a newly de-affiliated LMR user to leave an ongoing MCPTT group call. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT users affiliated to that group. At least one user is an LMR user represented by an MCPTT ID. +2. An MCPTT user on the MCPTT client and an LMR user via the IWF, are on an ongoing call. + +![Sequence diagram illustrating the exiting of an MCPTT group call due to de-affiliation. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The process involves group call requests, responses, media plane establishment, floor taken messages, and a final LMR user talker ID receipt by the IWF.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + + Note left of IWF: 1. The LMR user represented by the IWF has been de-affiliated. + Note left of IWF: 2. The MCPTT server sends an IWF group call leave request to the LMR user via the IWF. + Note left of IWF: 3. The IWF sends an IWF group call leave response to the MCPTT server and leaves the group call. + Note left of IWF: 4. The LMR user represented by the IWF is now removed from the ongoing group call. + + IWF->>MCPTT server: 1a. IWF group call request + IWF->>MCPTT server: 1b. IWF group call request + MCPTT server->>MCPTT client 1: 2a. Group call request + MCPTT server->>MCPTT client 2: 2b. Group call request + MCPTT client 1->>MCPTT server: 3a. Group call response + MCPTT client 2->>MCPTT server: 3b. Group call response + MCPTT server->>IWF: 4a. IWF group call response + MCPTT server->>IWF: 4b. IWF group call response + + Note over IWF, MCPTT server, MCPTT client 1, MCPTT client 2: 5. Media plane is established + + IWF->>MCPTT server: 6a. IWF floor taken + IWF->>MCPTT server: 6b. IWF floor taken + MCPTT server->>MCPTT client 1: 7a. Floor taken + MCPTT server->>MCPTT client 2: 7b. Floor taken + + Note left of IWF: 8. LMR user talker ID is received by the IWF + + IWF->>MCPTT server: 9a. IWF floor taken + IWF->>MCPTT server: 9b. IWF floor taken + MCPTT server->>MCPTT client 1: 10a. Floor taken + MCPTT server->>MCPTT client 2: 10b. Floor taken + +``` + +Sequence diagram illustrating the exiting of an MCPTT group call due to de-affiliation. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The process involves group call requests, responses, media plane establishment, floor taken messages, and a final LMR user talker ID receipt by the IWF. + +**Figure 10.3.6.3-1: Exiting MCPTT group call due to de-affiliation** + +1. The LMR user represented by the IWF has been de-affiliated. +2. The MCPTT server sends an IWF group call leave request to the LMR user via the IWF. +3. The IWF sends an IWF group call leave response to the MCPTT server and leaves the group call. +4. The LMR user represented by the IWF is now removed from the ongoing group call. + +## 10.3.7 Group regroup with pre-configured group + +### 10.3.7.1 General + +A group regroup may be achieved by regrouping MCPTT groups into a new regroup group which uses the configuration of a separate pre-configured MCPTT group. The MCPTT group configuration needs to be provided to the relevant MCPTT group members of the MCPTT groups that will be regrouped in advance of the regrouping operation. + +NOTE 1: A pre-configured group which is intended only to provide configuration for the pre-configured group regroup process is identified by a parameter in group configuration described in 3GPP TS 23.280 [5]. + +NOTE 2: The configuration may alternatively be taken from any MCPTT group that has been configured in the IWF and the user profile of all the relevant MCPTT users who will be regrouped. + +NOTE 3: Pre-configured group regroups may be defined according to the organizational structure of a mission critical organization, or by some other means which allows the MCPTT client of an authorized user and the IWF to be aware of an appropriate pre-configured group regroup for sets of MCPTT groups that will be regrouped together. + +The pre-configured MCPTT group that provides the configuration is not used as the pre-configured group regroup itself, it only provides configuration for one or more pre-configured group or user regroup. The MCPTT group ID of the pre-configured group regroup is provided by the authorized user or the IWF (for the case where the IWF owns the pre-configured group regroup) when the pre-configured group regrouping is carried out. + +The pre-configured group regroup can be specified to be a broadcast or non-broadcast type according to the configuration of the MCPTT group whose configuration is specified by the pre-configured group regroup request. The broadcast type of pre-configured group regroup is used for one-way communication where only an authorized user or the IWF (for the case where the IWF owns the pre-configured group regroup) is allowed to transmit and all other regroup members are only allowed to receive the communication (e.g. a call from a dispatcher to all regroup members). The non-broadcast type is used for two-way communication where all regroup members can transmit and receive (i.e., the pre-configured group regroup call behaves like a normal non-broadcast group call). + +These procedures provide a regrouping service for MCPTT only and are independent of group regrouping procedures specified in subclause 10.2.2. If one of the MCPTT groups that has been requested for regrouping by means of this procedure has already been regrouped by the group regrouping procedure specified in 3GPP TS 23.280 [5] or subclause 10.2.2, the request for regrouping shall be rejected. The rules for regrouping set forth in subclause 10.2.2.5 apply. + +## 10.3.7.2 Regroup formation using pre-configured group + +### 10.3.7.2.1 Regroup formation using pre-configured group initiated in the MCPTT system + +Figure 10.3.7.2.1-1 illustrates the procedure to initiate a regroup procedure using a pre-configured MCPTT regroup group, where at least one of the groups to be regrouped is configured in the IWF. The group management server in the MCPTT system of the regroup group shares the necessary security related parameters together with the group configuration of the pre-configured group regroup with the group management server in the IWF; the MCPTT system does not need to be aware of the group members of the pre-configured group regroup that are receiving service in the IWF. + +The procedure takes place prior to the establishment of a group call to the pre-configured group regroup. + +In this procedure, any gateway MC servers between the IWF and the MCPTT system are not shown. + +Pre-conditions: + +- The MCPTT client is authorized to initiate a pre-configured group regroup procedure, and is receiving MCPTT service in the MCPTT system. +- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the IWF, and the IWF has received the relevant security related information to allow communication in the pre-configured group regroup. +- In order to be aware whether the group is regrouped, the MCPTT server is subscribed to the group configuration in GMS. +- The GMS has subscribed group dynamic data as specified in subclause 10.1.5.5.1 from the MCPTT server within the same MCPTT system using the procedures defined in subclause 10.1.5.6 in 3GPP TS 23.280 [5]. +- The IWF is affiliated to one or more of the MCPTT groups that will be regrouped; and/or, the IWF may own one or more of MCPTT groups to be regrouped. +- The pre-configured group regroup is homed in the MCPTT server. +- The IWF is home to at least one group that's a constituent group of the pre-configured group regroup. + +NOTE 1: The IWF has the configuration information contained in the pre-configured group regroup, which is normally because at least one member of the pre-configured group regroup is homed on the IWF. + +![Sequence diagram illustrating the regroup procedure using pre-configured group initiated in the MCPTT system. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Initiate Pre-configured regroup (from client to server), 2. Pre-configured regroup request (from client to server), 3. Check authorization and resolve group IDs (internal to server), 4. IWF pre-configured regroup request (from server to IWF), 5. IWF pre-configured regroup response (from IWF to server), and 6. Preconfigured regroup response (from server to client).](5e9af8986a5845504f251d3079da8078_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note left of MCPTT client: 1. Initiate Pre-configured regroup + MCPTT client->>MCPTT server: 2. Pre-configured regroup request + Note right of MCPTT server: 3. Check authorization and resolve group IDs + MCPTT server->>IWF: 4. IWF pre-configured regroup request + IWF-->>MCPTT server: 5. IWF pre-configured regroup response + MCPTT server-->>MCPTT client: 6. Preconfigured regroup response + +``` + +Sequence diagram illustrating the regroup procedure using pre-configured group initiated in the MCPTT system. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Initiate Pre-configured regroup (from client to server), 2. Pre-configured regroup request (from client to server), 3. Check authorization and resolve group IDs (internal to server), 4. IWF pre-configured regroup request (from server to IWF), 5. IWF pre-configured regroup response (from IWF to server), and 6. Preconfigured regroup response (from server to client). + +**Figure 10.3.7.2.1-1: Regroup procedure using pre-configured group initiated in the MCPTT system** + +1. The authorized user of the MCPTT client initiates the pre-configured group regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken. + 2. The MCPTT client sends the pre-configured regroup request to the MCPTT server. + 3. The MCPTT server checks that the MCPTT client is authorized to initiate a pre-configured group regroup procedure, and resolves the group identities of the MCPTT groups requested in step 1. The MCPTT server also checks which group members are affiliated to the requested MCPTT groups that are homed in the MCPTT system. The MCPTT server identifies any partner systems or IWFs which are the group home systems for MCPTT groups identified in the list of groups to be regrouped. The MCPTT server may retrieve the configuration for the regroup group from the GMS if that configuration information is not already known to the MCPTT server. +- NOTE 2: This procedure does not require that that the authorized user of the MCPTT client is a group member of the MCPTT groups listed in the pre-configured group regroup request, or that the authorized user of the MCPTT client is an affiliated group member of any of the listed MCPTT groups. +4. The MCPTT server sends an IWF pre-configured regroup requests to the IWF. +- NOTE 3: Only group members that are affiliated to the MCPTT groups that are to be regrouped are sent a pre-configured regroup request. +5. The IWF sends an IWF pre-configured regroup response to the MCPTT server. The IWF may reject the IWF group regroup response. (e.g. if one of its constituent groups is in the emergency state or is already in a regroup, if the IWF does not support temporary groups or the IWF does not support group regrouping) + 6. The MCPTT server sends the pre-configured regroup response to the MCPTT client. + +After the pre-configured group regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in subclause 10.3.7.3. + +Participation by the IWF in the ongoing pre-configured group regroup persists until the IWF is no longer affiliated to any of the regrouped groups. + +#### 10.3.7.2.2 Regroup formation using pre-configured group initiated in the IWF + +Figure 10.3.7.2.2-1 illustrates the procedure to initiate a pre-configured group regroup procedure using a pre-configured MCPTT group, where at least one of the groups to be regrouped is configured in an MCPTT system. The group + +management server in the IWF shares the necessary security related parameters together with the group configuration of the MCPTT regroup group with the group management server in the MCPTT system and the group management server in the MCPTT system distributes this configuration including those security parameters to its served MCPTT users according to the procedures in 3GPP TS 23.280 [5] subclause 10.2.7; the IWF does not need to be aware of the list of group members of the pre-configured group regroup that are receiving service in the MCPTT system. The group can have multiple MCPTT clients, but only one MCPTT client involved in the session is shown for simplicity. + +The procedure takes place prior to the establishment of a group call to the pre-configured group regroup. + +In this procedure, any gateway MC servers between the IWF and the MCPTT system are not shown. + +Pre-conditions: + +- The MCPTT client is an affiliated member of MCPTT group 1 where MCPTT group 1 is defined in the MCPTT system. +- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the MCPTT client, and the MCPTT client has received the relevant security related information to allow communication in the pre-configured group regroup. +- The pre-configured group regroup is homed in the IWF. +- The MCPTT system is home to at least one group that's a constituent group of the pre-configured group regroup. + +NOTE 1: The MCPTT system has the configuration information contained in the pre-configured group, which is normally because at least one member of the preconfigured group is homed on the MCPTT system. + +![Sequence diagram illustrating the regroup procedure using pre-configured group initiated in the IWF. The diagram shows three lifelines: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF pre-configured regroup request (IWF to MCPTT server); 2. Check requested groups and identify affiliated group members (internal to MCPTT server); 3. Pre-configured regroup request (MCPTT server to MCPTT client); 4. Notify user (internal to MCPTT client); 5. Pre-configured regroup response (MCPTT client to MCPTT server); 6. Affiliate MCPTT clients to regroup group (internal to MCPTT server); 7. IWF pre-configured regroup response (MCPTT server to IWF).](854cb86f664ff62fd23e7607cfeb5727_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client + Note right of MCPTT server: 2. Check requested groups and identify affiliated group members + Note right of MCPTT client: 4. Notify user + Note right of MCPTT server: 6. Affiliate MCPTT clients to regroup group + IWF->>MCPTT server: 1. IWF pre-configured regroup request + MCPTT server->>MCPTT client: 3. Pre-configured regroup request + MCPTT client-->>MCPTT server: 5. Pre-configured regroup response + MCPTT server->>IWF: 7. IWF pre-configured regroup response + +``` + +Sequence diagram illustrating the regroup procedure using pre-configured group initiated in the IWF. The diagram shows three lifelines: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF pre-configured regroup request (IWF to MCPTT server); 2. Check requested groups and identify affiliated group members (internal to MCPTT server); 3. Pre-configured regroup request (MCPTT server to MCPTT client); 4. Notify user (internal to MCPTT client); 5. Pre-configured regroup response (MCPTT client to MCPTT server); 6. Affiliate MCPTT clients to regroup group (internal to MCPTT server); 7. IWF pre-configured regroup response (MCPTT server to IWF). + +**Figure 10.3.7.2.2-1: Regroup procedure using pre-configured group initiated in the IWF** + +1. The IWF initiates the pre-configured group regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken. The IWF sends the IWF pre-configured regroup request to the MCPTT server in the partner MCPTT system. +2. The MCPTT server checks the status of any MCPTT groups hosted by itself, and identifies affiliated group members of any of the identified MCPTT groups (both MCPTT groups that are hosted in the MCPTT system and MCPTT groups that are hosted in the IWF) that are receiving MCPTT service in the MCPTT system, which includes the MCPTT client. +3. The MCPTT server sends a pre-configured regroup request to the MCPTT client. + +NOTE 2: Only group members that are affiliated to the MCPTT groups that are to be regrouped are sent a pre-configured regroup request. + +4. The MCPTT client notifies the user of the regrouping. +5. The MCPTT client 2 may send the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. This acknowledgement is not sent in response to a multicast transmission of the pre-configured regroup request. +6. The MCPTT server affiliates the regrouped MCPTT client to the pre-configured group regroup. +7. The MCPTT server sends an IWF pre-configured regroup response to the IWF. + +After the pre-configured group regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in subclause 10.3.7.3. + +MCPTT client participation in the ongoing pre-configured group regroup persists until the MCPTT client is no longer affiliated to any of the regrouped groups. + +MCPTT client affiliation to the pre-configured group regroup may cease when the clients MCPTT service ceases, e.g. when the UE is powered down, or by the client performing a log-off operation. + +### 10.3.7.3 Regroup cancellation using pre-configured group regroup + +#### 10.3.7.3.1 Regroup cancellation using pre-configured group initiated in the MCPTT system + +Figure 10.3.7.3.1-1 illustrates the procedure to cancel a regrouping that uses a pre-configured MCPTT regroup group where there the regroup had been initiated in the MCPTT system. + +Pre-conditions: + +- The IWF has been regrouped into the pre-configured group regroup. +- The MCPTT client is authorized to cancel a pre-configured group regroup. +- The GMS has subscribed to the group dynamic data specified in 3GPP TS 23.280 [5] subclause 10.1.5.5.1 from the MCPTT server as specified in 3GPP TS 23.280 [5] subclause 10.1.5.6. + +![Sequence diagram for Regroup cancellation using pre-configured group initiated in the MCPTT system. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The process starts with the MCPTT client sending a '1. Initiate Pre-configured regroup' message to the MCPTT server. The MCPTT server then sends a '2. Preconfigured regroup cancel request' to the IWF. The MCPTT server also performs an internal '3. Check authorization' step. The IWF sends a '4. IWF pre-configured regroup cancel request' to the MCPTT server. The MCPTT server sends a '5. IWF pre-configured regroup cancel response' to the IWF. Finally, the MCPTT server sends a '6. Pre-configured regroup cancel response' to the MCPTT client.](df94f7807f02e218ee3c66b9cbd829e5_img.jpg) + +``` +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note left of MCPTT client: 1. Initiate Pre-configured regroup + MCPTT client->>MCPTT server: 2. Preconfigured regroup cancel request + Note right of MCPTT server: 3. Check authorization + MCPTT server->>IWF: 4. IWF pre-configured regroup cancel request + IWF->>MCPTT server: 5. IWF pre-configured regroup cancel response + MCPTT server->>MCPTT client: 6. Pre-configured regroup cancel response +``` + +Sequence diagram for Regroup cancellation using pre-configured group initiated in the MCPTT system. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The process starts with the MCPTT client sending a '1. Initiate Pre-configured regroup' message to the MCPTT server. The MCPTT server then sends a '2. Preconfigured regroup cancel request' to the IWF. The MCPTT server also performs an internal '3. Check authorization' step. The IWF sends a '4. IWF pre-configured regroup cancel request' to the MCPTT server. The MCPTT server sends a '5. IWF pre-configured regroup cancel response' to the IWF. Finally, the MCPTT server sends a '6. Pre-configured regroup cancel response' to the MCPTT client. + +**Figure 10.3.7.3.1-1: Regroup cancellation using pre-configured group initiated in the MCPTT system** + +1. The authorized user of the MCPTT client initiates the cancellation of the pre-configured group regroup. + +2. The MCPTT client sends the pre-configured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the regroup group. +3. The MCPTT server checks that the MCPTT client is authorized to cancel a pre-configured group regroup. +4. The MCPTT server sends the IWF pre-configured regroup cancel request to the IWF. +5. The IWF sends the IWF pre-configured regroup cancel response to the MCPTT server. The IWF may reject the IWF group regroup response. (e.g. if one of its constituent groups is in the emergency state or is already in a regroup, if the IWF does not support temporary groups or the IWF does not support group regrouping) +6. The MCPTT server sends a pre-configured regroup cancel response to the MCPTT client. + +**10.3.7.3.2 Regroup cancellation using pre-configured group initiated in the IWF** + +Figure 10.3.7.3.2-1 illustrates the procedure to cancel a regrouping that uses a pre-configured MCPTT group where the regroup is initiated in the IWF. Only one MCPTT group member is shown for simplicity. + +Pre-conditions: + +- The MCPTT client has been regrouped into a pre-configured group regroup, and is receiving MCPTT service in the MCPTT system. + +![Sequence diagram showing the 'Cancel pre-configured group regroup procedure using pre-configured group in the MCPTT system'. Lifelines: IWF, MCPTT server, MCPTT client, and User. The sequence starts with the IWF sending a 'PRE-CONFIGURED REGROUP CANCEL REQUEST' to the MCPTT server. The MCPTT server then sends a 'PRE-CONFIGURED REGROUP CANCEL REQUEST' to the MCPTT client. The MCPTT client sends a 'PRE-CONFIGURED REGROUP REMOVE RESPONSE' to the MCPTT server. The MCPTT server sends a 'PRE-CONFIGURED REGROUP CANCEL RESPONSE' to the IWF. The MCPTT server also sends a 'PRE-CONFIGURED REGROUP CANCEL RESPONSE' to the MCPTT client. Finally, the MCPTT client sends a 'NOTIFY USER' message to the User.](45578bd3ed11d45af63ce00e28bab2f8_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client as MCPTT client + participant User + + Note right of MCPTT_client: User is regrouped + IWF->>MCPTT_server: PRE-CONFIGURED REGROUP CANCEL REQUEST + MCPTT_server->>MCPTT_client: PRE-CONFIGURED REGROUP CANCEL REQUEST + MCPTT_client-->>MCPTT_server: PRE-CONFIGURED REGROUP REMOVE RESPONSE + MCPTT_server->>IWF: PRE-CONFIGURED REGROUP CANCEL RESPONSE + MCPTT_server-->>MCPTT_client: PRE-CONFIGURED REGROUP CANCEL RESPONSE + MCPTT_client->>User: NOTIFY USER + +``` + +Sequence diagram showing the 'Cancel pre-configured group regroup procedure using pre-configured group in the MCPTT system'. Lifelines: IWF, MCPTT server, MCPTT client, and User. The sequence starts with the IWF sending a 'PRE-CONFIGURED REGROUP CANCEL REQUEST' to the MCPTT server. The MCPTT server then sends a 'PRE-CONFIGURED REGROUP CANCEL REQUEST' to the MCPTT client. The MCPTT client sends a 'PRE-CONFIGURED REGROUP REMOVE RESPONSE' to the MCPTT server. The MCPTT server sends a 'PRE-CONFIGURED REGROUP CANCEL RESPONSE' to the IWF. The MCPTT server also sends a 'PRE-CONFIGURED REGROUP CANCEL RESPONSE' to the MCPTT client. Finally, the MCPTT client sends a 'NOTIFY USER' message to the User. + +**Figure 10.3.7.3.2-1: Cancel pre-configured group regroup procedure using pre-configured group in the MCPTT system** + +1. The IWF initiates the cancellation of the regrouping that uses a pre-configured MCPTT group. The IWF sends the IWF pre-configured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the regroup group. +2. The MCPTT server sends the pre-configured regroup cancel request to the MCPTT client. +3. The MCPTT client notifies the user of the cancellation of the pre-configured group regrouping. +4. The MCPTT client may send the pre-configured regroup remove response to the MCPTT server to acknowledge the cancellation of the pre-configured group regrouping. This acknowledgement is not sent in response to a multi-cast transmission of the pre-configured regroup cancel request. +5. The MCPTT server de-affiliates the MCPTT client from the pre-configured group regroup. +6. The MCPTT server sends the IWF pre-configured regroup cancel response to the IWF. + +### 10.3.7.4 Regroup rejection using pre-configured group + +#### 10.3.7.4.1 Regroup rejection using pre-configured group for regroup initiated in the MCPTT system + +Figure 10.3.7.4.1-1 illustrates the case where the procedure to initiate a pre-configured group regroup procedure with an MCPTT system and an IWF using a pre-configured MCPTT group described in subclause 10.3.7.3.1 commences, but where the request for the regroup is rejected by the IWF, for example because one of the groups hosted by the IWF is already regrouped by other group regrouping procedures. + +In this procedure, any gateway MC servers between the IWF and the MCPTT system are not shown. + +Pre-conditions: + +- The MCPTT client is authorized to initiate a pre-configured group regroup procedure. +- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the IWF, and the IWF has received the relevant security related information to allow communication in the pre-configured group regroup. +- In order to be aware whether the group is regrouped, the MCPTT server is subscribed to the group configuration in GMS. +- The GMS has subscribed group dynamic data as specified in subclause 10.1.5.5.1 from the MCPTT server within the same MCPTT system using the procedures defined in subclause 10.1.5.6 in 3GPP TS 23.280 [5]. +- The IWF is affiliated to one or more of the MCPTT groups that will be regrouped; and/or, the IWF may own one or more of MCPTT groups to be regrouped. + +![Sequence diagram illustrating the regroup rejection procedure. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Initiate preconfigured regroup (from client to server), 2. Preconfigured regroup request (from client to server), 3. Check authorization and resolve group IDs (internal to server), 4. IWF pre-configured regroup request (from server to IWF), 5. IWF pre-configured regroup reject (from IWF to server), 6. Pre-configured regroup reject (from server to client).](f4b570ddd089f54943d46e9f8776f9f9_img.jpg) + +``` +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note left of MCPTT client: 1. Initiate preconfigured regroup + MCPTT client->>MCPTT server: 2. Preconfigured regroup request + Note right of MCPTT server: 3. Check authorization and resolve group IDs + MCPTT server->>IWF: 4. IWF pre-configured regroup request + IWF-->>MCPTT server: 5. IWF pre-configured regroup reject + MCPTT server-->>MCPTT client: 6. Pre-configured regroup reject +``` + +Sequence diagram illustrating the regroup rejection procedure. The diagram shows three lifelines: MCPTT client, MCPTT server, and IWF. The sequence of messages is: 1. Initiate preconfigured regroup (from client to server), 2. Preconfigured regroup request (from client to server), 3. Check authorization and resolve group IDs (internal to server), 4. IWF pre-configured regroup request (from server to IWF), 5. IWF pre-configured regroup reject (from IWF to server), 6. Pre-configured regroup reject (from server to client). + +**Figure 10.3.7.4.1-1: Regroup rejection using pre-configured group for group initiated in the MCPTT system** + +1. The authorized user of the MCPTT client initiates the pre-configured group regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken. +2. The MCPTT client sends the pre-configured regroup request to the MCPTT server. +3. The MCPTT server checks that the MCPTT client is authorized to initiate a pre-configured group regroup procedure, and resolves the group identities of the MCPTT groups requested in step 1. The MCPTT server also checks which group members are affiliated to the requested MCPTT groups that are homed in the MCPTT + +system. The MCPTT server identifies any partner systems or IWFs which are the group home systems for MCPTT groups identified in the list of groups to be regrouped. The MCPTT server may retrieve the configuration for the pre-configured group regroup from the GMS if that configuration information is not already known to the MCPTT server. + +NOTE: This procedure does not require that that the authorized user of the MCPTT client is a group member of the MCPTT groups listed in the regroup request, or that the authorized user of the MCPTT client is an affiliated group member of any of the listed MCPTT groups. + +4. The MCPTT server sends the IWF pre-configured regroup requests to the IWF. +5. The IWF sends a pre-configured regroup reject to the MCPTT server, indicating the reason for rejection, for example because one or more of the MCPTT groups has already been regrouped by another group regrouping procedure, either internal to the IWF or in an MCPTT system. +6. The MCPTT server sends a pre-configured regroup reject to the MCPTT client, indicating the reason for the rejection. + +#### 10.3.7.4.2 Regroup rejection using pre-configured group for regroup initiated in the IWF + +Figure 10.3.7.4.2-1 illustrates the case where the procedure to initiate a regroup procedure with an MCPTT system and an IWF using a pre-configured MCPTT group described in subclause 10.3.7.3.2 commences, but where the request for the pre-configured group regroup is rejected by the MCPTT system, for example because one of the groups hosted by the MCPTT system is already regrouped by other group regrouping procedures. + +In this procedure, any gateway MC servers between the IWF and the MCPTT system are not shown. + +Pre-conditions: + +- The MCPTT client is an affiliated member of MCPTT group 1 where MCPTT group 1 is defined in the MCPTT system. +- The MCPTT group identity and group configuration for the pre-configured group regroup have been pre-configured in the MCPTT client, and the MCPTT client has received the relevant security related information to allow communication in the pre-configured group regroup. + +![Sequence diagram showing regroup rejection using pre-configured group for regroup initiated in the IWF. The diagram shows two lifelines: IWF and MCPTT server. The sequence of messages is: 1. IWF pre-configured regroup request (IWF to MCPTT server), 2. Check requested groups (internal to MCPTT server), 3. IWF pre-configured regroup reject (MCPTT server to IWF).](b882c54d92390b4ca523f230e3e07617_img.jpg) + +``` +sequenceDiagram + participant IWF + participant MCPTT server + Note right of MCPTT server: 2. Check requested groups + IWF->>MCPTT server: 1. IWF pre-configured regroup request + MCPTT server-->>IWF: 3. IWF pre-configured regroup reject +``` + +Sequence diagram showing regroup rejection using pre-configured group for regroup initiated in the IWF. The diagram shows two lifelines: IWF and MCPTT server. The sequence of messages is: 1. IWF pre-configured regroup request (IWF to MCPTT server), 2. Check requested groups (internal to MCPTT server), 3. IWF pre-configured regroup reject (MCPTT server to IWF). + +**Figure 10.3.7.4.2-1: Regroup rejection using pre-configured group for group initiated in the IWF** + +1. The IWF initiates the pre-configured group regroup procedure, specifying the list of MCPTT groups to be regrouped including MCPTT group 1, the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken. The IWF sends the IWF pre-configured regroup request to the MCPTT server. +2. The MCPTT server checks the status of any MCPTT groups hosted by that MCPTT server, and determines that one or more requested MCPTT groups has already been regrouped by another group regrouping procedure. +3. The partner MCPTT server sends an IWF pre-configured regroup reject to the IWF, indicating the reason for rejection. + +### 10.3.7.5 Pre-configured regroup update procedures + +#### 10.3.7.5.1 MCPTT client PTTs on MCPTT group during an in-progress pre-configured group regroup + +Figure 10.3.7.5.1-1 illustrates the procedure when a user attempts to set up a MCPTT group call on a group involved in an in-progress pre-configured group regroup, homed in the IWF. + +Pre-conditions: + +- The MCPTT client is an affiliated member of MCPTT group A that is part of an in-progress pre-configured group regroup with MCPTT groups B and C. MCPTT groups A, B and C can be homed in either the IWF or the MCPTT system. +- MCPTT group D is being used as the pre-configured group regroup. MCPTT group D is homed in the IWF. +- The MCPTT client has missed the pre-configured regroup request message (e.g. poor signalling conditions, race condition). + +![Sequence diagram illustrating the procedure for MCPTT client PTTs on MCPTT group during an in-progress pre-configured group regroup. The diagram shows interactions between MCPTT client, MCPTT server, and IWF.](7f663b2f8632236c6e40ca16272d62df_img.jpg) + +``` +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note left of MCPTT client: 7. Notify user + MCPTT client->>MCPTT server: 1. Group call request + MCPTT server->>IWF: 2. IWF group call request + IWF-->>MCPTT server: 3. IWF group call response + MCPTT server-->>MCPTT client: 4. Group call response + IWF->>MCPTT server: 5. IWF preconfigured regroup request + MCPTT server->>MCPTT client: 6. Preconfigured regroup request + MCPTT client->>MCPTT server: 8. Preconfigured regroup response + MCPTT server->>IWF: 9. IWF preconfigured regroup response +``` + +Sequence diagram illustrating the procedure for MCPTT client PTTs on MCPTT group during an in-progress pre-configured group regroup. The diagram shows interactions between MCPTT client, MCPTT server, and IWF. + +**Figure 10.3.7.5.1-1: Procedure for MCPTT client PTTs on MCPTT group during an in-progress pre-configured group regroup** + +1. The MCPTT client attempts to start a call on MCPTT group A. The MCPTT client sends a group call request message to the MCPTT server containing MCPTT group A as the target group. +2. The MCPTT server forwards the request to the IWF as an IWF group call request. +3. The IWF sends an IWF group call response to the MCPTT server indicating that the call set up is denied because the group is part of an in-progress pre-configured group regroup. +4. The MCPTT server forwards the response to the MCPTT client as a group call response. +5. The IWF sends an IWF pre-configured regroup request to the MCPTT server containing MCPTT group D, the group ID of the pre-configured group regroup. +6. The MCPTT server forwards the request to the MCPTT client as a pre-configured regroup request. +7. The MCPTT client notifies the user of the group call set up failure and of the regrouping procedure. + +NOTE 1: Step 5 can occur prior to step 4 and step 7 can occur after step 4. + +8. The MCPTT client sends the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. +9. The MCPTT server forwards the response to the IWF as an IWF pre-configured regroup response. The IWF affiliates the regrouped MCPTT client to the pre-configured group regroup. + +NOTE 2: If there is a call currently in progress on the pre-configured group regroup then this MCPTT client can be added to the call using the late entry procedure. If there is no call currently in progress, then the MCPTT user can retry the group call set up. + +### 10.3.7.6 Call request on pre-configured regroup group after group regroup has been cancelled + +#### 10.3.7.6.1 MCPTT client PTTs on pre-configured regroup group after group regroup has been cancelled + +Figure 10.3.7.6.1-1 illustrates the procedure when an MCPTT user attempts to set up a MCPTT group call on a pre-configured regroup group after the pre-configured MCPTT group regroup has been cancelled. + +Pre-conditions: + +- The MCPTT client is a member of MCPTT group A that was part of an in-progress pre-configured group regroup with MCPTT groups B and C that has been cancelled. MCPTT group D was used as the pre-configured regroup group. MCPTT group D is homed in the IWF. +- The MCPTT client has missed the pre-configured regroup cancel request message (e.g. poor signalling conditions, race condition). + +![Sequence diagram illustrating the procedure for MCPTT client PTTs on pre-configured regroup group after the group regroup is cancelled. The diagram shows interactions between MCPTT client, MCPTT server, and IWF.](cdc21bbfcba380e98ece42e5b8da50bb_img.jpg) + +``` +sequenceDiagram + participant MCPTT client + participant MCPTT server + participant IWF + Note left of MCPTT client: 7. Notify user + MCPTT client->>MCPTT server: 1. Group call request + MCPTT server->>IWF: 2. IWF group call request + IWF->>MCPTT server: 3. IWF group call response + MCPTT server->>MCPTT client: 4. Group call response + IWF->>MCPTT server: 5. IWF preconfigured regroup cancel request + MCPTT server->>MCPTT client: 6. Preconfigured regroup cancel request + MCPTT client->>MCPTT server: 8. Preconfigured regroup cancel response + MCPTT server->>IWF: 9. IWF preconfigured regroup cancel response +``` + +Sequence diagram illustrating the procedure for MCPTT client PTTs on pre-configured regroup group after the group regroup is cancelled. The diagram shows interactions between MCPTT client, MCPTT server, and IWF. + +**Figure 10.3.7.6.1-1: Procedure for MCPTT client PTTs on pre-configured regroup group after the group regroup is cancelled** + +1. The MCPTT client attempts to start a call on MCPTT group D, the pre-configured regroup group. The MCPTT client sends a group call request message to the MCPTT server containing MCPTT group D as the target group. +2. The MCPTT server forwards the request to the IWF as an IWF group call request. + +NOTE 1: The pre-configured regroup group D can be a group in the MCPTT client's profile, and the MCPTT client can be a member of group D. + +3. The IWF sends an IWF group call response to the MCPTT server indicating that the call set up is denied because the group regroup is no longer active. + +4. The MCPTT server forwards the response to the MCPTT client as a group call response + +NOTE 2: In the following, steps 5, 6, 8 and 9 are optional. + +5. The IWF sends an IWF pre-configured regroup cancel request to the MCPTT server. + +6. The MCPTT server forwards the request as a pre-configured regroup cancel request to the MCPTT client. + +NOTE 3: This message should be sent over unicast. + +7. The MCPTT client notifies the user of the group call set up failure and of the regrouping cancellation. + +8. The MCPTT client sends a pre-configured regroup cancel response to the MCPTT server to acknowledge the regrouping cancellation. + +9. The MCPTT server forwards the response to the IWF as an IWF pre-configured regroup cancel response. + +### 10.3.7.7 Adding newly affiliated user to a pre-configured group regroup + +#### 10.3.7.7.1 Adding newly affiliated MCPTT user to a pre-configured group regroup + +Figure 10.3.7.7.1-1 illustrates the procedure to add a newly affiliated MCPTT user to an in-progress pre-configured group regroup operation. + +Pre-conditions: + +- The MCPTT client is a member of, but not yet affiliated with, a MCPTT group that is part of an in-progress pre-configured group regroup operation. +- The MCPTT group identity and group configuration for the regroup MCPTT group has been pre-configured in the MCPTT client, and the MCPTT client has received the relevant security related information to allow it to communicate in the pre-configured group regroup. + +![Sequence diagram showing the procedure to add a newly affiliated user to a pre-configured group regroup. Lifelines include MCPTT CLIENT, MCPTT SERVER, IWF, and MCPTT GROUP. The sequence starts with a request from MCPTT CLIENT to MCPTT SERVER, followed by a response from MCPTT SERVER to MCPTT CLIENT. Then, a request is sent from MCPTT SERVER to IWF, and a response from IWF to MCPTT SERVER. Finally, a message is sent from MCPTT SERVER to MCPTT GROUP.](ae0a6916b0794a1bd6cf99034401d857_img.jpg) + +``` + +sequenceDiagram + participant MCPTT_CLIENT as MCPTT CLIENT + participant MCPTT_SERVER as MCPTT SERVER + participant IWF as IWF + participant MCPTT_GROUP as MCPTT GROUP + + MCPTT_CLIENT->>MCPTT_SERVER: Request to add user to regroup + MCPTT_SERVER-->>MCPTT_CLIENT: Response + MCPTT_SERVER->>IWF: Request to IWF + IWF-->>MCPTT_SERVER: Response + MCPTT_SERVER->>MCPTT_GROUP: Message to group + +``` + +Sequence diagram showing the procedure to add a newly affiliated user to a pre-configured group regroup. Lifelines include MCPTT CLIENT, MCPTT SERVER, IWF, and MCPTT GROUP. The sequence starts with a request from MCPTT CLIENT to MCPTT SERVER, followed by a response from MCPTT SERVER to MCPTT CLIENT. Then, a request is sent from MCPTT SERVER to IWF, and a response from IWF to MCPTT SERVER. Finally, a message is sent from MCPTT SERVER to MCPTT GROUP. + +Figure 10.3.7.7.1-1: Procedure to add a newly affiliated user to a pre-configured group regroup + +1. The MCPTT client affiliates to an MCPTT group that is currently part of an in-progress pre-configured group regroup. The affiliation follows the procedure in subclause 10.1.2.4. +2. The IWF sends an IWF pre-configured regroup request to the MCPTT server. +3. The MCPTT server sends a pre-configured regroup request to the MCPTT client. +4. The MCPTT client notifies the user of the regrouping. +5. The MCPTT client may send the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the pre-configured regroup request. +6. The MCPTT server sends an IWF pre-configured regroup response to the IWF. The IWF affiliates the MCPTT client to the group regroup. + +### 10.3.7.7.2 Adding newly affiliated user homed in the IWF to a pre-configured group regroup + +Figure 10.3.7.7.2-1 illustrates the procedure to add a newly affiliated user homed in the IWF to an in-progress pre-configured group regroup operation. + +Pre-conditions: + +- The LMR user is a member of, but not yet affiliated to, an MCPTT group that is part of an in-progress pre-configured group regroup operation. +- The MCPTT group identity and group configuration for the pre-configured group regroup has been pre-configured in the IWF, and the IWF has received the relevant security related information to allow it to communicate in the pre-configured group regroup. + +![Sequence diagram illustrating the procedure to add a newly affiliated user to a pre-configured regroup. The diagram shows interactions between the IWF, MCPTT server, MCPTT client, and LMR user.](71f0fd23b2f06b621ba89a65ee3c284c_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client as MCPTT client + participant LMR_user as LMR user + + Note right of MCPTT_server: MCPTT server receives regroup request from IWF + MCPTT_server->>MCPTT_client: MCPTT server sends regroup request to MCPTT client + Note right of MCPTT_client: MCPTT client notifies LMR user + MCPTT_client->>MCPTT_server: MCPTT client sends regroup response to MCPTT server + Note right of MCPTT_server: MCPTT server sends regroup response to IWF + MCPTT_server->>IWF: MCPTT server sends regroup response to IWF + Note right of IWF: IWF affiliates MCPTT client to group regroup + +``` + +Sequence diagram illustrating the procedure to add a newly affiliated user to a pre-configured regroup. The diagram shows interactions between the IWF, MCPTT server, MCPTT client, and LMR user. + +**Figure 10.3.7.7.2-1: Procedure to add a newly affiliated user to a pre-configured regroup** + +1. The IWF affiliates to an MCPTT group that is currently part of an in-progress pre-configured group regroup. The affiliation follows the procedure in subclause 10.1.2.2. +2. The MCPTT server retrieves the MCPTT group ID of the pre-configured group regroup and the MCPTT group ID of the group from which configuration information for the pre-configured group regroup is to be taken. +3. The MCPTT server sends an IWF pre-configured regroup request to the IWF. + +4. The IWF sends an IWF pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. +5. The MCPTT server affiliates the IWF to the group regoup. + +## 10.3.8 User regroup with pre-configured group + +### 10.3.8.1 General + +A user regroup may be achieved by regrouping MCPTT users into a new regroup group which uses the configuration of a separate pre-configured MCPTT group. The MCPTT regroup group configuration needs to be provided to the relevant MCPTT users who will be regrouped in advance of the regrouping operation. A pre-configured user regroup may contain users homed in the IWF and the IWF may host pre-configured user regroups which may contain members homed in an MCPTT system. + +NOTE 1: A pre-configured group which is intended only to provide configuration for the pre-configured user regroup process is identified by a parameter in group configuration described in 3GPP TS 23.280 [5]. + +NOTE 2: The configuration may alternatively be taken from any MCPTT group that has been configured in the user profile of all of the relevant MCPTT users who will be regrouped and that has also been configured to the IWF for the case where the pre-configured user regroup contains members homed in the IWF. + +The pre-configured user regroup that provides the configuration is not used as the pre-configured user regroup itself, it only provides configuration for one or more pre-configured user regroups. The MCPTT group ID of the pre-configured user regroup is provided by the originating authorized user or the originating IWF when the pre-configured user regrouping is carried out. + +### 10.3.8.2 Pre-configured user regroup formation + +#### 10.3.8.2.1 Pre-configured user regroup formation by the MCPTT system + +Figure 10.3.8.2.1-1 illustrates the procedure to initiate a pre-configured user regroup procedure using a pre-configured user regroup. The procedure takes place prior to the establishment of a group call to the pre-configured user regroup. + +Pre-conditions: + +- MCPTT clients 2 and 3 are registered with the MCPTT service. +- An MCPTT group that will be used for configuration of the pre-configured user regroup has been pre-configured in MCPTT clients 2 and 3 and the IWF, and MCPTT clients 2 and 3 and the IWF have received the relevant security related information to allow them to communicate in the pre-configured user regroup. +- MCPTT client 1 is authorized to initiated a pre-configured user regroup using the pre-configured user regroup procedure. +- MCPTT client 1 is aware of a suitable pre-configured group whose configuration has been pre-configured in the MC service clients of the MCPTT users who will be regrouped. +- The pre-configured user regroup is homed in the MCPTT server. + +![Sequence diagram illustrating the User regroup procedure using pre-configured group by the MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3. The process starts with MCPTT client 1 initiating a preconfigured user regroup. MCPTT client 1 sends a preconfigured regroup request to the MCPTT server. The MCPTT server checks authorizations. The MCPTT server sends pre-configured regroup requests to MCPTT clients 2 and 3. MCPTT clients 2 and 3 notify their users. MCPTT clients 2 and 3 send pre-configured regroup responses to the MCPTT server. The MCPTT server sends an IWF pre-configured regroup request. The IWF sends an IWF pre-configured regroup response.](e7010c66da16316c2935dfbbef5056b3_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant MCPTT client 3 + Note left of MCPTT client 1: 1. Initiate preconfigured User regroup + MCPTT client 1->>MCPTT server: 2. Preconfigured regroup request + Note right of MCPTT server: 3. Check authorizations + MCPTT server->>MCPTT client 2: 4a. Pre-configured regroup request + MCPTT server->>MCPTT client 3: 4b. Pre-configured regroup request + Note right of MCPTT client 2: 5a. Notify user + Note right of MCPTT client 3: 5b. Notify user + MCPTT client 2-->>MCPTT server: 6a. Preconfigured regroup response + MCPTT client 3-->>MCPTT server: 6b. Preconfigured regroup response + MCPTT server->>MCPTT client 2: 7. IWF pre-configured regroup request + MCPTT server->>MCPTT client 3: 8. IWF pre-configured regroup response + +``` + +Sequence diagram illustrating the User regroup procedure using pre-configured group by the MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and MCPTT client 3. The process starts with MCPTT client 1 initiating a preconfigured user regroup. MCPTT client 1 sends a preconfigured regroup request to the MCPTT server. The MCPTT server checks authorizations. The MCPTT server sends pre-configured regroup requests to MCPTT clients 2 and 3. MCPTT clients 2 and 3 notify their users. MCPTT clients 2 and 3 send pre-configured regroup responses to the MCPTT server. The MCPTT server sends an IWF pre-configured regroup request. The IWF sends an IWF pre-configured regroup response. + +**Figure 10.3.8.2.1-1: User regroup procedure using pre-configured group by the MCPTT system** + +1. The authorized user of MCPTT client 1 initiates the pre-configured user regroup procedure, specifying the list of MCPTT users to be regrouped (MCPTT clients 2, 3 and one or more IWF users), the MCPTT group ID of the pre-configured user regroup, and the MCPTT group ID of the group from which configuration information for the pre-configured user regroup is to be taken. + 2. MCPTT client 1 sends the pre-configured regroup request to the MCPTT server. The request indicates the list of users to be included in the regroup operation. + 3. The MCPTT server checks that MCPTT client 1 is authorized to initiate a pre-configured user regroup procedure. +- NOTE 1: MCPTT clients and users homed in the IWF can be involved in multiple user and group regroups simultaneously. +4. The MCPTT server sends the pre-configured regroup requests to MCPTT clients 2 and 3 in steps 4a and 4b respectively. + 5. MCPTT clients 2 and 3 notify their users of the regrouping in steps 4a and 4b respectively. + 6. MCPTT clients 2 and 3 may send the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. These acknowledgements are not sent in response to a multicast transmission of the pre-configured regroup request. + 7. The MCPTT server sends the IWF an IWF pre-configured regroup request. + 8. The IWF sends the MCPTT server and IWF pre-configured regroup response. + 9. The MCPTT server affiliates the regrouped MCPTT clients and the IWF to the pre-configured user regroup. + 10. The MCPTT server sends a pre-configured user regroup response to MCPTT client 1. + +NOTE 2: After the pre-configured user regrouping procedure, the regrouping remains in effect until explicitly cancelled by the procedure in subclause 10.3.8.3.1. + +### 10.3.8.2.2 Pre-configured user grop regroup formation by the IWF + +Figure 10.3.8.2.2-1 illustrates the procedure for the IWF to initiate a pre-configured user regroup procedure using a pre-configured MCPTT group. The procedure takes place prior to the establishment of a pre-configured user regroup call to the pre-configured user regroup. For simplicity, only one receiving MCPTT client is shown. + +Pre-conditions: + +- The MCPTT client is registered with the MCPTT service. +- An MCPTT group that will be used for configuration of the pre-configured user regroup has been pre-configured in the MCPTT client and the IWF, and the MCPTT client has received the relevant security related information to allow it to communicate in the pre-configured user regroup. +- The pre-configured user regroup is homed in the IWF. + +![Sequence diagram illustrating the user regroup procedure using pre-configured group by the IWF. The diagram shows three lifelines: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF pre-configured regroup request (IWF to MCPTT server), 2. Pre-configured regroup request (MCPTT server to MCPTT client), 3. Notify user (internal to MCPTT client), 4. Pre-configured regroup response (MCPTT client to MCPTT server), and 5. Preconfigured regroup response (MCPTT server to IWF).](8a94796989f4fcba2688c4faa7991538_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client + IWF->>MCPTT server: 1. IWF pre-configured regroup request + MCPTT server->>MCPTT client: 2. Pre-configured regroup request + Note over MCPTT client: 3. Notify +user + MCPTT client-->>MCPTT server: 4. Pre-configured regroup response + MCPTT server->>IWF: 5. Preconfigured regroup response + +``` + +Sequence diagram illustrating the user regroup procedure using pre-configured group by the IWF. The diagram shows three lifelines: IWF, MCPTT server, and MCPTT client. The sequence of messages is: 1. IWF pre-configured regroup request (IWF to MCPTT server), 2. Pre-configured regroup request (MCPTT server to MCPTT client), 3. Notify user (internal to MCPTT client), 4. Pre-configured regroup response (MCPTT client to MCPTT server), and 5. Preconfigured regroup response (MCPTT server to IWF). + +**Figure 10.3.8.2.2-1: User regroup procedure using pre-configured group by the IWF** + +1. The IWF initiates the pre-configured user regroup, the IWF sends an IWF pre-configured regroup request to the MCPTT server. The request indicates the list of users to be included in the regroup operation, that are homed in the MCPTT system. + +NOTE 1: MCPTT clients and users homed in the IWF can be involved in multiple user and group regroups simultaneously. + +2. The MCPTT server sends the pre-configured regroup request to the MCPTT client. +3. The MCPTT client notifies the MCPTT users of the regrouping. +4. The MCPTT client may send the pre-configured regroup response to the MCPTT server to acknowledge the regrouping action. These acknowledgement is not sent in response to a multicast transmission of the pre-configured regroup request. +5. The MCPTT server sends an IWF pre-configured regroup response to the IWF. + +NOTE 2: After the pre-configured user regroup procedure, the regrouping remains in effect until explicitly cancelled by the procedure in subclause 10.3.8.3.2. + +### 10.3.8.3 Pre-configured user regroup cancellation + +#### 10.3.8.3.1 Pre-configured user regroup cancellation by the MCPTT system + +Figure 10.3.8.3.1-1 illustrates the procedure to cancel a pre-configured user regroup that uses a pre-configured MCPTT group. For simplicity, only one receiving MCPTT client is shown. + +Pre-conditions: + +- MCPTT client 2 and at least one user homed in the IWF have been regrouped into the pre-configured user regroup. +- MCPTT client 1 is authorized to cancel a pre-configured user regroup that uses a pre-configured MCPTT group. + +![Sequence diagram illustrating the 'Cancel pre-configured user regroup procedure by the MCPTT system'. The diagram shows interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and IWF. The process starts with MCPTT client 1 sending a 'Cancel pre-configured user regrouping' message to the MCPTT server. The server checks authorization, then sends a 'Pre-configured regroup cancel request' to MCPTT client 2. MCPTT client 2 notifies the user and sends a response. The server then sends an 'IWF pre-configured regroup cancel request' to the IWF, which responds. Finally, the server deaffiliates clients and sends a response back to MCPTT client 1.](4a390493f601ce1ac6b9201db4e28b5a_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT server + participant MCPTT client 2 + participant IWF + + Note left of MCPTT client 1: 1. Cancel pre-configured user regrouping + MCPTT client 1->>MCPTT server: 2. Pre-configured regroup cancel request + Note right of MCPTT server: 3. Check authorization + MCPTT server->>MCPTT client 2: 4. Pre-configured regroup cancel request + Note right of MCPTT client 2: 5. Notify user + MCPTT client 2-->>MCPTT server: 6. Pre-configured regroup cancel response + MCPTT server->>IWF: 7. IWF pre-configured regroup cancel request + IWF-->>MCPTT server: 8. IWF pre-configured regroup cancel response + Note right of MCPTT server: 9. Deaffiliate MCPTT clients and the IWF + MCPTT server-->>MCPTT client 1: 10. Pre-configured regroup cancel response +``` + +Sequence diagram illustrating the 'Cancel pre-configured user regroup procedure by the MCPTT system'. The diagram shows interactions between MCPTT client 1, MCPTT server, MCPTT client 2, and IWF. The process starts with MCPTT client 1 sending a 'Cancel pre-configured user regrouping' message to the MCPTT server. The server checks authorization, then sends a 'Pre-configured regroup cancel request' to MCPTT client 2. MCPTT client 2 notifies the user and sends a response. The server then sends an 'IWF pre-configured regroup cancel request' to the IWF, which responds. Finally, the server deaffiliates clients and sends a response back to MCPTT client 1. + +**Figure 10.3.8.3.1-1: Cancel pre-configured user regroup procedure by the MCPTT system** + +1. The authorized user of MCPTT client 1 initiates the cancellation of the pre-configured user regroup that uses a pre-configured MCPTT group. +2. MCPTT client 1 sends the pre-configured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the pre-configured user regroup. +3. The MCPTT server checks that MCPTT client 1 is authorized to cancel a pre-configured user regroup. +4. The MCPTT server sends the pre-configured regroup cancel requests to MCPTT client 2. +5. MCPTT clients 2 notifies the MCPTT user of the cancellation of the pre-configured user regroup. +6. MCPTT client 2 may send the MCPTT server a pre-configured regroup cancel response. This acknowledgement is not sent in response to a multicast transmission of the pre-configured regroup cancel request. +7. The MCPTT server sends the IWF an IWF pre-configured regroup cancel request. +8. The IWF sends the MCPTT server an IWF pre-configured regroup cancel response. +9. The MCPTT server de-affiliates MCPTT clients 2 and 3 from the pre-configured user regroup. +10. The MCPTT server sends a pre-configured regroup cancel response to MCPTT client 1. + +### 10.3.8.3.2 Pre-configured user regroup cancellation by the IWF + +Figure 10.3.8.3.2-1 illustrates the procedure to cancel a pre-configured user regroup that uses a pre-configured MCPTT group. For simplicity, only one receiving MCPTT client is shown. + +Pre-conditions: + +- An MCPTT client and at least one user homed in the IWF have been regrouped into the pre-configured user regroup. + +![Sequence diagram illustrating the pre-configured user regroup cancellation procedure by the IWF. The diagram shows five steps: 1. IWF sends a pre-configured regroup cancel request to the MCPTT server. 2. MCPTT server sends a pre-configured regroup cancel request to the MCPTT client. 3. MCPTT client notifies the user. 4. MCPTT client sends a pre-configured regroup cancel response to the MCPTT server. 5. MCPTT server sends an IWF pre-configured regroup cancel response to the IWF.](b71ad9fc874230de9ba4480e12a216f7_img.jpg) + +``` +sequenceDiagram + participant IWF + participant MCPTT_server as MCPTT server + participant MCPTT_client as MCPTT client + Note right of MCPTT_client: user + IWF->>MCPTT_server: 1. IWF pre-configured regroup cancel request + MCPTT_server->>MCPTT_client: 2. Pre-configured regroup cancel request + MCPTT_client->>Note right of MCPTT_client: 3. Notify user + MCPTT_client-->>MCPTT_server: 4. Pre-configured regroup cancel response + MCPTT_server-->>IWF: 5. IWF pre-configured regroup cancel response +``` + +Sequence diagram illustrating the pre-configured user regroup cancellation procedure by the IWF. The diagram shows five steps: 1. IWF sends a pre-configured regroup cancel request to the MCPTT server. 2. MCPTT server sends a pre-configured regroup cancel request to the MCPTT client. 3. MCPTT client notifies the user. 4. MCPTT client sends a pre-configured regroup cancel response to the MCPTT server. 5. MCPTT server sends an IWF pre-configured regroup cancel response to the IWF. + +**Figure 10.3.8.3.2-1: Cancel pre-configured pre-configured user regroup procedure by the IWF** + +1. The IWF initiates the cancellation of the pre-configured user regroup. The IWF sends the pre-configured regroup cancel request to the MCPTT server, specifying the MCPTT group ID of the pre-configured user regroup. +2. The MCPTT server sends the pre-configured regroup cancel requests to the MCPTT client. +3. The MCPTT client notifies the MCPTT user of the cancellation of the pre-configured user regroup. +4. The MCPTT client may send the MCPTT server a pre-configured regroup cancel response. This acknowledgement is not sent in response to a multicast transmission of the pre-configured regroup cancel request. +5. The MCPTT server sends an IWF pre-configured regroup cancel response to the IWF. + +## 10.4 Private call + +### 10.4.1 Information flows for private calls + +#### 10.4.1.1 General + +The following subclauses define information flows for private calls on the IWF-1 interface. Private call related information flows on reference points other than IWF-1 are defined in 3GPP TS 23.379 [7]. + +#### 10.4.1.2 IWF private call request + +Table 10.4.1.2-1 describes the information flow IWF private call request from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.4.1.2-1: IWF private call request information elements** + +| Information Element | Status | Description | +|-----------------------------------|-------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Use floor control indication | M | This element indicates whether floor control will be used for the private call. | +| SDP offer | M | Media parameters of MCPTT client. | +| Encryption Algorithm | O | Encryption algorithm to use for the call. The field can also indicate whether the encryption algorithm choice is determined from information in the media stream. | +| Encryption mode | M | Whether E2EE will be used. | +| Requested commencement mode | O | An indication of the commencement mode to be used. | +| Implicit floor request (see NOTE) | O | An indication that the user is also requesting the floor. | +| Location | O | Location of the calling party | +| NOTE: | This element shall be included only when the originating client requests the floor. | | + +### 10.4.1.3 IWF private call response + +Table 10.4.1.3-1 describes the information flow IWF private call response from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.4.1.3-1: IWF private call response information elements** + +| Information Element | Status | Description | +|---------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | O | The MCPTT ID of the called party | +| Acceptance confirmation | O | An indication whether the user has positively accepted the call. | +| SDP answer | M | Media parameters selected | +| Result | M | Result of the IWF private call request: success or failure | +| Encryption Algorithm(s) response | O | A list of one or more alternative encryption algorithm(s) to use for the call. | +| Use floor control indication response | O | This element indicates whether the floor control indication in the request is acceptable. | +| Implicit floor request response | O | This element indicates whether the indication that the user is also requesting the floor in the request is acceptable. | + +### 10.4.1.4 IWF ringing + +Table 10.4.1.4-1 describes the information flow IWF ringing from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.4.1.4-1: IWF ringing information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | +| Ringing indication | O | Indication to the caller. | + +#### 10.4.1.5 IWF call end request + +Table 10.4.1.5-1 describes the information flow IWF call end request from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.4.1.5-1: IWF call end request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------| +| MCPTT ID | M | The MCPTT ID of the calling party | +| MCPTT ID | M | The MCPTT ID of the called party | + +#### 10.4.1.6 IWF call end response + +Table 10.4.1.6-1 describes the information flow IWF call end response from the IWF to the MCPTT server. + +**Table 10.4.1.6-1: IWF call end response information elements** + +| Information Element | Status | Description | +|---------------------|--------|--------------------------------------| +| MCPTT ID | M | The MCPTT ID of the responding party | + +### 10.4.2 Private call setup in automatic commencement mode + +#### 10.4.2.1 MCPTT user initiating an MCPTT private call + +In this procedure, an MCPTT user is initiating an MCPTT private call (automatic commencement mode) for communicating with a user in an LMR system, with or without floor control enabled. + +This subclause is based on the procedure for private call setup in automatic commencement mode – MCPTT users in multiple MCPTT systems described in 3GPP TS 23.379 [7], subclause 10.7.2.3.1. + +In figure 10.4.2.1-1, an MCPTT client initiates establishment of an MCPTT private call with an LMR user. + +Pre-conditions: + +1. The calling MCPTT user has selected automatic commencement mode for the call; +2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7]. + +![Sequence diagram illustrating Private call setup in automatic commencement mode, initiated by an MCPTT user. The diagram shows interactions between MCPTT Client, MCPTT Server, IWF, and MCPTT User.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +``` + +sequenceDiagram + participant MCPTT User + participant MCPTT Client + participant MCPTT Server + participant IWF + Note right of MCPTT User: MCPTT User initiates private call + MCPTT User->>MCPTT Client: MCPTT Private Call Request + MCPTT Client->>MCPTT Server: MCPTT Private Call Request + MCPTT Server->>IWF: IWF Private Call Request + IWF-->>MCPTT Server: IWF Private Call Response + MCPTT Server-->>MCPTT Client: MCPTT Private Call Response + MCPTT Client-->>MCPTT User: MCPTT Private Call Response + +``` + +Sequence diagram illustrating Private call setup in automatic commencement mode, initiated by an MCPTT user. The diagram shows interactions between MCPTT Client, MCPTT Server, IWF, and MCPTT User. + +**Figure 10.4.2.1-1: Private call setup in automatic commencement mode, initiated by an MCPTT user** + +1. The MCPTT user at the MCPTT client initiates an MCPTT private call. The MCPTT client sends an MCPTT private call request towards the MCPTT server. The MCPTT private call request contains the MCPTT IDs corresponding to the calling MCPTT party and called LMR party and an SDP offer containing one or more media types. The following parameters are also included that describe the MCPTT client's choices: + - the encryption algorithm; + - the encryption mode (encrypted or not); + - an indication of whether the MCPTT client is requesting the floor, and if the MCPTT client is requesting the floor, location information of the calling MCPTT client may be provided; + - requested commencement mode (automatic in this case); and + - an indication of whether the call is to be full or half duplex (whether to establish floor control). +2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized to initiate the private call. Because the IWF private call request is requesting automatic commencement mode, the MCPTT server also checks whether the MCPTT user at the MCPTT client is authorized to initiate a call in automatic commencement mode. If location information was included in the MCPTT private call request, the MCPTT server also checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the requesting MCPTT user to decide if the user's location information may be provided to other MCPTT users on the call and the IWF. +3. If authorized, the MCPTT server sends the IWF private call request that may or may not include location of the requestor, depending on the outcome of the privacy check towards the IWF, including the original parameters and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7]. + +NOTE: How the IWF private call request is forwarded to the LMR system is out of scope of the present document. + +4. The IWF sends an IWF private call response to the MCPTT server, indicating that the IWF does support one of the requested media types. The response indicates success or failure. If the indication is failure, the response may include one or more alternatives to the parameter values contained in step 3. +5. The MCPTT server forwards the MCPTT private call response to the MCPTT client. If the result parameter indicates success, then the MCPTT client proceeds to step 6. Otherwise, if the parameters returned in the MCPTT private call response are acceptable to the MCPTT client, then the MCPTT client can send a new MCPTT private call request with the new parameters and behaves according to those parameters. The calling MCPTT user may be notified of the change in parameters, for example, that the call is to be without floor + +control. The MCPTT user can choose to end the call rather than continue with the new parameters. If the parameters returned are not acceptable to the MCPTT client, then the call fails. + +- 6. The MCPTT client has successfully established media plane for communication to the IWF and either end can transmit media. The MCPTT system initiating the call is responsible of granting the floor, solving competing floor requests and issuing floor revoked indications. + +### 10.4.2.2 LMR user initiating a private call with MCPTT user + +In this procedure, an LMR user is initiating a private call (in automatic commencement mode) for communicating with a user in MCPTT system, with or without floor control enabled. + +This subclause is based on the procedure for private call setup in automatic commencement mode – MCPTT users in multiple MCPTT systems described in 3GPP TS 23.379 [7], subclause 10.7.2.3.1. + +In figure 10.4.2.2-1, an LMR user initiates establishment of a private call with an MCPTT user. + +Pre-conditions: + +- 1. The calling LMR user has selected automatic commencement mode for the call; +- 2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7]. +- 3. The LMR user at the LMR system has initiated a private call towards an MCPTT user. + +NOTE 1: Private call operation between the LMR user and the IWF are out of scope of the present document. + +![Sequence diagram showing the private call setup process between an LMR user, an MCPTT server, and an MCPTT client.](4caed5b90277a5c5ee07547bfc8ff884_img.jpg) + +``` + +sequenceDiagram + participant LMR + participant MCPTT Server + participant MCPTT Client + Note right of MCPTT Server: 2. MCPTT server + LMR->>MCPTT Server: 1. IWF private call request + MCPTT Server->>MCPTT Client: 3. MCPTT private call request + MCPTT Client->>MCPTT Server: 4. MCPTT private call response + MCPTT Server->>LMR: 5. IWF private call response + +``` + +The diagram illustrates the interaction for private call setup. It features three lifelines: LMR (left), MCPTT Server (middle), and MCPTT Client (right). The sequence of messages is as follows: 1. An arrow labeled '1. IWF private call request' points from the LMR lifeline to the MCPTT Server lifeline. 2. A self-message arrow labeled '2. MCPTT server' is shown on the MCPTT Server lifeline. 3. An arrow labeled '3. MCPTT private call request' points from the MCPTT Server lifeline to the MCPTT Client lifeline. 4. An arrow labeled '4. MCPTT private call response' points from the MCPTT Client lifeline back to the MCPTT Server lifeline. 5. An arrow labeled '5. IWF private call response' points from the MCPTT Server lifeline back to the LMR lifeline. At the bottom of the diagram, a horizontal bar spans across all three lifelines, labeled '6. MCPTT server'. Vertical dashed lines extend downwards from each lifeline. + +Sequence diagram showing the private call setup process between an LMR user, an MCPTT server, and an MCPTT client. + +**Figure 10.4.2.2-1: Private call setup in automatic commencement mode, initiated by an LMR user** + +- 1. The IWF sends an IWF private call request towards the MCPTT server. The IWF private call request contains the MCPTT IDs corresponding to the calling LMR party and the called MCPTT party and an SDP offer containing one or more media types. The following parameters are also included that describe the MCPTT client's choices: + - the encryption algorithm; + - the encryption mode (encrypted or not); + - an indication of whether the LMR user is requesting the floor, and if the MCPTT client is requesting the floor, location information of the calling MCPTT client may be provided; + - requested commencement mode (automatic in this case); and + +- an indication of whether the call is to be full or half duplex (whether to establish floor control). +2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized and able to receive the private call. Because the IWF private call request is requesting automatic commencement mode, the MCPTT server also checks whether the MCPTT user at the MCPTT client is authorized to receive a call in automatic commencement mode. + 3. If authorized, the MCPTT server sends the MCPTT private call request towards the MCPTT client, including the original parameters with or without the location of the calling party and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7]. + 4. The MCPTT client sends an MCPTT private call response to the MCPTT server indicating that the MCPTT client does support one of the requested media types. The response indicates success or failure. If the indication is failure, the response may also include one or more alternatives to the parameter values contained in step 3. + 5. The MCPTT server sends the IWF private call response to the IWF offering the same media type as that sent in step 4. If the parameters returned are not acceptable to the IWF, then the call fails. If the parameters returned in the IWF private call response are different but acceptable to the IWF, then the IWF can send a new IWF private call request with the new parameters starting with step 1, which is to essentially restart the call. If there is no change of parameter, then the call proceeds to step 6. +- NOTE 2: The calling LMR user may be notified of the change in parameters, for example, that the call is to be without floor control. +6. The MCPTT client has successfully established media plane for communication to the IWF and either end can transmit media. The LMR system initiating the call is responsible of granting the floor, solving competing floor requests and issuing floor revoked indications. + +## 10.4.3 Private call setup in manual commencement mode + +### 10.4.3.1 MCPTT user is initiating an MCPTT private call + +In this procedure, an MCPTT user is initiating an MCPTT private call (manual commencement mode) for communicating with an LMR user via an IWF, with or without floor control enabled. + +This subclause is based on the procedure for private call setup in manual commencement mode – MCPTT users in multiple MCPTT systems described in 3GPP TS 23.379 [7], subclause 10.7.2.3.2. + +In figure 10.4.3.1-1, an MCPTT client initiates establishment of an MCPTT private call with an LMR user. + +Pre-conditions: + +1. The calling MCPTT user has selected manual commencement mode for the call. +2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7]. + +![Sequence diagram illustrating the private call setup in manual commencement mode initiated by an MCPTT user. The diagram shows three lifelines: MCPTT CLIENT, MCPTT SERVER, and IWF. The process starts with the MCPTT CLIENT sending an IWF PRIVATE CALL REQUEST to the MCPTT SERVER. The MCPTT SERVER then sends an IWF PRIVATE CALL REQUEST to the IWF. The IWF responds with an IWF PRIVATE CALL RESPONSE to the MCPTT SERVER. The MCPTT SERVER then sends three separate responses back to the MCPTT CLIENT: an IWF PRIVATE CALL RESPONSE, an MCPTT PRIVATE CALL RESPONSE, and an MCPTT PRIVATE CALL RESPONSE. Finally, the MCPTT SERVER sends a MESSAGE DELIVERY INDICATION to the MCPTT CLIENT.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +``` + +sequenceDiagram + participant MCPTT CLIENT + participant MCPTT SERVER + participant IWF + Note right of MCPTT SERVER: PRIVATE CALL REQUEST + MCPTT CLIENT->>MCPTT SERVER: IWF PRIVATE CALL REQUEST + MCPTT SERVER->>IWF: IWF PRIVATE CALL REQUEST + IWF-->>MCPTT SERVER: IWF PRIVATE CALL RESPONSE + MCPTT SERVER-->>MCPTT CLIENT: IWF PRIVATE CALL RESPONSE + MCPTT SERVER-->>MCPTT CLIENT: MCPTT PRIVATE CALL RESPONSE + MCPTT SERVER-->>MCPTT CLIENT: MCPTT PRIVATE CALL RESPONSE + Note left of MCPTT CLIENT: MESSAGE DELIVERY INDICATION + MCPTT SERVER-->>MCPTT CLIENT: MESSAGE DELIVERY INDICATION + +``` + +Sequence diagram illustrating the private call setup in manual commencement mode initiated by an MCPTT user. The diagram shows three lifelines: MCPTT CLIENT, MCPTT SERVER, and IWF. The process starts with the MCPTT CLIENT sending an IWF PRIVATE CALL REQUEST to the MCPTT SERVER. The MCPTT SERVER then sends an IWF PRIVATE CALL REQUEST to the IWF. The IWF responds with an IWF PRIVATE CALL RESPONSE to the MCPTT SERVER. The MCPTT SERVER then sends three separate responses back to the MCPTT CLIENT: an IWF PRIVATE CALL RESPONSE, an MCPTT PRIVATE CALL RESPONSE, and an MCPTT PRIVATE CALL RESPONSE. Finally, the MCPTT SERVER sends a MESSAGE DELIVERY INDICATION to the MCPTT CLIENT. + +**Figure 10.4.3.1-1: Private call setup in manual commencement mode – initiated by an MCPTT user** + +1. The MCPTT user at the MCPTT client would like to initiate an MCPTT private call. The MCPTT client sends an MCPTT private call request towards the MCPTT server. The MCPTT private call request contains the MCPTT IDs corresponding to the calling MCPTT party and called LMR party and an SDP offer containing one or more media types. The following parameters are also included that describe the MCPTT client's choices: + - the encryption algorithm; + - the encryption mode (encrypted or not) + - an indication of whether the MCPTT client is requesting the floor; + - requested commencement mode (manual in this case), and if the MCPTT client is requesting the floor, location information of the calling MCPTT client may be provided; and + - an indication of whether the call is to be full or half duplex (whether to establish floor control). +2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized to initiate the private call. Because the IWF private call request is requesting manual commencement mode, the MCPTT server also checks whether the MCPTT user at the MCPTT client is authorized to initiate a call in manual commencement mode. If location information was included in the MCPTT private call request, the MCPTT server also checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the requesting MCPTT user to decide if the user's location information may be provided to other MCPTT users on the call and the IWF. +3. If authorized, the MCPTT server sends the IWF private call request towards the IWF, including the original parameters that may or may not include location of the requestor, depending on the outcome of the privacy check, and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7]. + +NOTE: How the IWF private call request is forwarded to the LMR system is out of scope of the present document. + +4. The IWF may report failure with an IWF private call response to the MCPTT server. The response may include one or more alternatives to the parameter values contained in step 3. If the IWF does not report failure, the process proceeds with step 6. + +5. The MCPTT server forwards the MCPTT private call response to the MCPTT client. If the result parameter indicates failure, the MCPTT client may abandon the call. If the parameters in the MCPTT private call response are acceptable to the MCPTT client, then the MCPTT client can send a new MCPTT private call request with the new parameters to the MCPTT server and behaves according to those parameters. The calling user may be notified of the change in parameters, for example, that the call is to be without floor control. The calling user may choose to end the call rather than continue with the new parameters. +6. The receiving IWF sends an IWF ringing to the MCPTT server while waiting for the call to be accepted. +7. The MCPTT server forwards the MCPTT ringing to the MCPTT client. The MCPTT client may indicate to the MCPTT user that the LMR user has been notified, e.g. by producing ringback audio. +8. Once the call has been accepted by the called user, the IWF sends an IWF private call response to the MCPTT server. The IWF private call response indicates that the IWF does support one of the requested media types. +9. The MCPTT server forwards the MCPTT private call response to the MCPTT client. The MCPTT client may indicate to the MCPTT user that the call is connected, e.g. by stopping the ringback audio. +10. The MCPTT client has successfully established media plane for communication to the IWF. The MCPTT system initiating the call is responsible of granting the floor and solving the competing floor requests, and floor revoked indications. + +### 10.4.3.2 LMR user initiating a private call with MCPTT user + +In this procedure, an LMR user is initiating a private call (in manual commencement mode) for communicating with an MCPTT user via an IWF, with or without floor control enabled. + +This subclause is based on the procedure for private call setup in manual commencement mode – MCPTT users in multiple MCPTT systems described in 3GPP TS 23.379 [7], subclause 10.7.2.3.2. + +In figure 10.4.3.2-1, an LMR user initiates establishment of a private call with an MCPTT user. + +Pre-conditions: + +1. The calling LMR user has selected manual commencement mode for the call. +2. The MCPTT client is registered to the MCPTT service, as per procedure in subclause 10.2 in 3GPP TS 23.379 [7]. +3. The LMR user at the LMR system has initiated a private call towards an MCPTT user. + +NOTE 1: Private call operation between the LMR user and the IWF are out of scope of the present document. + +![UML Sequence diagram showing private call setup between IWF, MCPTT Server, and MCPTT Client.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT Server + participant MCPTT Client + + IWF->>MCPTT Server: 1. IWF private call request + Note over MCPTT Server: 2. Authorize request + MCPTT Server->>MCPTT Client: 3. MCPTT private call request + MCPTT Client-->>MCPTT Server: 4. MCPTT private call response + MCPTT Server-->>IWF: 5. MCPTT private call response + Note over IWF, MCPTT Client: 6. Media plane established + +``` + +The sequence diagram illustrates the private call setup process. 1. The IWF sends a private call request to the MCPTT Server. 2. The MCPTT Server performs authorization checks. 3. The MCPTT Server forwards the private call request to the MCPTT Client. 4. The MCPTT Client sends a private call response back to the MCPTT Server. 5. The MCPTT Server forwards this response to the IWF. Finally, step 6 indicates the media plane is established between the IWF and the MCPTT Client. + +UML Sequence diagram showing private call setup between IWF, MCPTT Server, and MCPTT Client. + +**Figure 10.4.3.2-1: Private call setup in manual commencement mode, initiated by an LMR user** + +1. The IWF sends an IWF private call request towards the MCPTT server. The IWF private call request contains the MCPTT IDs corresponding to the calling LMR party and called MCPTT party and an SDP offer containing one or more media types. The following parameters are also included that describe the IWF's choices: + - the encryption algorithm; + - the encryption mode (encrypted or not) + - an indication of whether the LMR user is requesting the floor, and if the MCPTT client is requesting the floor, location information of the calling MCPTT client may be provided; + - requested commencement mode (manual in this case); and + - an indication of whether the call is to be full or half duplex (whether to establish floor control). +2. The MCPTT server checks whether the MCPTT user at the MCPTT client is authorized and able to receive the private call. Because the IWF private call request is requesting manual commencement mode, the MCPTT server also checks whether the MCPTT user at the MCPTT client is authorized to receive a call in manual commencement mode. +3. If authorized, the MCPTT server sends the MCPTT private call request towards the MCPTT client, including the original parameters with or without the location of the calling party and offering the same media types or a subset of the media types contained in the initial received request as per 3GPP TS 23.379 [7]. + +NOTE 2: How the IWF private call request is forwarded to the LMR system is out of scope of the present document. + +4. The MCPTT client may report failure with an MCPTT private call response to the MCPTT server. The response may include one or more alternatives to the parameter values contained in step 3. If the MCPTT client does not report failure, the process proceeds with step 6. +5. The MCPTT server forwards the MCPTT private call response to the IWF. If the result parameter indicates failure, the IWF may abandon the call. If the parameters in the IWF private call response are acceptable to the IWF, then the IWF can send a new IWF private call request with the new parameters to the MCPTT server and behaves according to those parameters. The IWF may choose to end the call rather than continue with the new parameters. + +6. The MCPTT client sends an MCPTT ringing to the MCPTT server while waiting for the call to be accepted by the MCPTT user. +7. The MCPTT server sends an IWF ringing to IWF while waiting for the call to be accepted. +8. Once the call has been accepted by the called user, the MCPTT client sends an MCPTT private call response to the MCPTT server. The IWF private call response indicates that the IWF does support one of the requested media types. +9. The MCPTT server sends the IWF private call response to the IWF. +10. The MCPTT client has successfully established media plane for communication to the IWF. The LMR system initiating the call is responsible of granting the floor, solving competing floor requests and issuing floor revoked indications. + +## 10.4.4 Private call release + +### 10.4.4.1 MCPTT client initiated + +The procedure describes the case where an MCPTT client requests release of an ongoing MCPTT private call (with or without floor control) that was established in either of the two commencement modes (manual or automatic). This subclause is based upon the subclauses for MCPTT private call release in 3GPP TS 23.379 [7], subclauses 10.7.2.2.3.1 and 10.7.2.3.3. + +Procedures in figure 10.4.4.1-1 are the basic signalling control plane procedures for the MCPTT client initiating the release of an ongoing interworked private call. + +Pre-conditions: + +1. The MCPTT user on the MCPTT client is already registered for receiving MCPTT service and is involved in a private call with an LMR user via the IWF with or without floor control and established either in manual or automatic commencement mode, as described in subclause 10.4.2 and subclause 10.4.3. + +![Sequence diagram for Private call release – client initiated. Lifelines: MCPTT CLIENT, MCPTT SERVER, IWF, and a combined lifeline for LMR USER and MCPTT USER. The sequence starts with the MCPTT CLIENT sending a SIP BYE request to the MCPTT SERVER. The MCPTT SERVER then sends an IWF Call End Request to the IWF. The IWF sends an IWF Call End Response back to the MCPTT SERVER. Finally, the MCPTT SERVER sends a SIP BYE response back to the MCPTT CLIENT.](4ee2de50739c96fd7bd5a38150ec9c78_img.jpg) + +``` + +sequenceDiagram + participant MCPTT_CLIENT + participant MCPTT_SERVER + participant IWF + participant LMR_USER as LMR USER / MCPTT USER + Note right of MCPTT_CLIENT: MCPTT CLIENT + MCPTT_CLIENT->>MCPTT_SERVER: SIP BYE request + MCPTT_SERVER->>IWF: IWF Call End Request + IWF-->>MCPTT_SERVER: IWF Call End Response + MCPTT_SERVER-->>MCPTT_CLIENT: SIP BYE response + +``` + +Sequence diagram for Private call release – client initiated. Lifelines: MCPTT CLIENT, MCPTT SERVER, IWF, and a combined lifeline for LMR USER and MCPTT USER. The sequence starts with the MCPTT CLIENT sending a SIP BYE request to the MCPTT SERVER. The MCPTT SERVER then sends an IWF Call End Request to the IWF. The IWF sends an IWF Call End Response back to the MCPTT SERVER. Finally, the MCPTT SERVER sends a SIP BYE response back to the MCPTT CLIENT. + +**Figure 10.4.4.1-1: Private call release – client initiated** + +1. The user at the MCPTT client would like to release an ongoing interworked private call with the LMR user. +2. The MCPTT client sends an MCPTT private call end request towards the MCPTT server (via SIP core) for tearing down the private call with the other client. +3. The MCPTT server sends the corresponding IWF call end request towards the IWF, addressed to the MCPTT client ID specified in the original MCPTT private call end request. + +NOTE: The LMR user is also notified about the release of the private call. How the LMR user is notified is outside the scope of the present document. + +4. The IWF acknowledges the IWF call end request with an IWF call end response sent towards the MCPTT server. +5. After receiving the MCPTT private call end request acknowledgement from the IWF, the MCPTT server generates an acknowledgement for the MCPTT client's MCPTT private call end request. +6. The MCPTT client and the IWF release all the media plane resources used for the private call. Further, if the private call was established with floor control, floor control resources are released and the MCPTT client cannot make further requests for floor control or send media. + +#### 10.4.4.2 MCPTT server initiated + +The procedure describes the case where an MCPTT server terminates an ongoing interworked private call (with or without floor control) that was established in either of the two commencement modes (manual or automatic). The conditions causing the MCPTT server to terminate the call could include expiry of the MCPTT administrator configured maximum duration for MCPTT private calls or expiry of the maximum time permitted for an MCPTT private call without transmission/reception. This subclause is based upon the subclauses for MCPTT private call release in 3GPP TS 23.379 [7], subclauses 10.7.2.2.3.2 and 10.7.2.3.3. + +Procedures in figure 10.4.4.2-1 are the basic signalling control plane procedures for the MCPTT server initiating termination of an ongoing interworked private call. + +Pre-conditions: + +1. The MCPTT user on the MCPTT client is already registered for receiving MCPTT service and is involved in a private call with an LMR user via the IWF with or without floor control and established either in manual or automatic commencement mode, as described in subclause 10.4.2 and subclause 10.4.3. + +![Sequence diagram for 'End private call – server initiated'. Lifelines: MCPTT Client, MCPTT Server, and IWF. The sequence starts with the MCPTT Server sending an 'MCPTT private call end request' to the MCPTT Client. The MCPTT Client responds with an 'MCPTT private call end request acknowledgement'. Simultaneously, the MCPTT Server sends an 'IWF call end request' to the IWF. The IWF responds with an 'IWF call end response'. Finally, the MCPTT Server sends an 'MCPTT private call end acknowledgement' to the MCPTT Client. A note above the MCPTT Server lifeline indicates the termination conditions: 'Upon conditions to terminate call e.g., MCPTT administrator configured maximum duration for MCPTT private calls expiry or time out due to MCPTT private call without transmission/reception'.](2e8dcf3d807269a64340a9c292ea7f5d_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client + participant MCPTT Server + participant IWF + Note over MCPTT Server: Upon conditions to terminate call e.g., MCPTT administrator configured maximum duration for MCPTT private calls expiry or time out due to MCPTT private call without transmission/reception + MCPTT Server->>MCPTT Client: 2a. MCPTT private call end request + MCPTT Server->>IWF: 2b. IWF call end request + MCPTT Client-->>MCPTT Server: MCPTT private call end request acknowledgement + IWF-->>MCPTT Server: IWF call end response + MCPTT Server->>MCPTT Client: MCPTT private call end acknowledgement + +``` + +Sequence diagram for 'End private call – server initiated'. Lifelines: MCPTT Client, MCPTT Server, and IWF. The sequence starts with the MCPTT Server sending an 'MCPTT private call end request' to the MCPTT Client. The MCPTT Client responds with an 'MCPTT private call end request acknowledgement'. Simultaneously, the MCPTT Server sends an 'IWF call end request' to the IWF. The IWF responds with an 'IWF call end response'. Finally, the MCPTT Server sends an 'MCPTT private call end acknowledgement' to the MCPTT Client. A note above the MCPTT Server lifeline indicates the termination conditions: 'Upon conditions to terminate call e.g., MCPTT administrator configured maximum duration for MCPTT private calls expiry or time out due to MCPTT private call without transmission/reception'. + +**Figure 10.4.4.2-1: End private call – server initiated** + +1. Upon conditions to terminate call e.g., MCPTT administrator configured maximum duration for MCPTT private calls expiry or time out due to MCPTT private call without transmission/reception, the MCPTT server decides to initiate termination of an ongoing interworking private call between the MCPTT client and the LMR user. +- 2a. The MCPTT server sends an MCPTT private call end request towards the MCPTT client (via SIP core) for tearing down the private call. +- 2b. The MCPTT server sends a corresponding IWF call end request towards the MCPTT client identity associated with the LMR user +3. The MCPTT user at the MCPTT client is notified about the termination of the private call. + +NOTE: The LMR user is also notified about the termination of the private call. How the LMR user is notified is outside the scope of the present document. + +4. The MCPTT client and the IWF acknowledge the request. +5. The MCPTT client and the IWF release all the media plane resources used for the private call. Further, if the private call was established with floor control, floor control resources are released and the MCPTT client cannot make further requests for floor control or send media. + +#### 10.4.4.3 LMR user initiated + +The procedure describes the case where either an LMR user or the LMR system is requesting to release an ongoing interworked private call (with or without floor control) and the call established in either of the two commencement modes (manual or automatic). This subclause is based upon the subclauses for MCPTT private call release in 3GPP TS 23.379 [7], subclauses 10.7.2.2.3.1 and 10.7.2.3.3. + +Procedures in figure 10.4.4.3-1 are the basic signalling control plane procedures for the LMR user, via the IWF, initiating the release of an ongoing interworked private call. + +Pre-conditions: + +1. The MCPTT user on the MCPTT client is already registered for receiving MCPTT service and is involved in a private call with an LMR user via the IWF with or without floor control and established either in manual or automatic commencement mode, as described in subclause 10.4.2 and subclause 10.4.3. + +![Sequence diagram for Private call release – IWF initiated. The diagram shows three lifelines: LMR System, MCPTT Server, and MCPTT Client. The sequence of messages is: 1. LMR System sends an IWF call end request to MCPTT Server. 2. MCPTT Server sends an MCPTT private call end request to MCPTT Client. 3. MCPTT Client sends an MCPTT private call end response to MCPTT Server. 4. MCPTT Server sends an IWF call end response to LMR System. The MCPTT Client lifeline has a self-callout box labeled 'Notify user about call termination'.](b44a429660cbf47740ee6777db90e34f_img.jpg) + +``` + +sequenceDiagram + participant LMR System + participant MCPTT Server + participant MCPTT Client + Note right of MCPTT Client: Notify user about call termination + LMR System->>MCPTT Server: IWF call end request + MCPTT Server->>MCPTT Client: MCPTT private call end request + MCPTT Client-->>MCPTT Server: MCPTT private call end response + MCPTT Server-->>LMR System: IWF call end response + +``` + +Sequence diagram for Private call release – IWF initiated. The diagram shows three lifelines: LMR System, MCPTT Server, and MCPTT Client. The sequence of messages is: 1. LMR System sends an IWF call end request to MCPTT Server. 2. MCPTT Server sends an MCPTT private call end request to MCPTT Client. 3. MCPTT Client sends an MCPTT private call end response to MCPTT Server. 4. MCPTT Server sends an IWF call end response to LMR System. The MCPTT Client lifeline has a self-callout box labeled 'Notify user about call termination'. + +**Figure 10.4.4.3-1: Private call release – IWF initiated** + +1. The LMR system would like to release an ongoing interworked private call with the MCPTT user. +2. The IWF sends an IWF call end request towards the MCPTT server for tearing down the private call with the MCPTT client. +3. The MCPTT server sends the corresponding MCPTT private call end request towards the MCPTT client specified in the original IWF call end request. +4. The MCPTT user is notified about the release of the private call. +5. The MCPTT client acknowledges the MCPTT private call end request. + +6. After receiving the MCPTT private call end request acknowledgement from the MCPTT client, the MCPTT server generates an acknowledgement for the IWF's IWF call end request. +7. The MCPTT client and the IWF release all the media plane resources used for the private call. Further, if the private call was established with floor control, floor control resources are released and the MCPTT client cannot make further requests for floor control or send media. + +## 10.4.5 Encryption of private calls + +Private calls can use MC media encryption (see 3GPP TS 33.180 [8]) between the IWF and the MCPTT client. A private call that uses an LMR vocoder may use LMR E2EE if the calling and called parties have previously been provisioned with the appropriate LMR E2EE keys. + +NOTE: MC media encryption is independent of LMR E2EE techniques. MC media encryption can be applied in addition to LMR E2EE. + +## 10.5 Floor control + +### 10.5.1 General + +Floor control for interworking applies to both private call and group call. + +Floor control involving a single MCPTT server is described in 3GPP TS 23.379 [7]. Floor control involving multiple MCPTT servers is also described in 3GPP TS 23.379 [7] in that a primary MCPTT server is interconnected to a partner MCPTT server. Subclause 10.5.2 describes information flows for floor control between an MCPTT server and an IWF, and are based on those defined for interconnection in 3GPP TS 23.379 [7]. Subclause 10.5.3 describes aspects of floor control that apply to interworking groups and interworking private calls. Subclauses 10.5.4/10.5.6 and 10.5.5/10.5.7 describe general cases of floor control on an interworking group defined in the LMR system and in the MCPTT system respectively, where the partner system has been configured to apply/not apply local filtering of floor control requests before communicating with the primary system. Subclauses 10.5.9 and 10.5.10 describe general cases of floor control in a private call, where the controlling role is taken by the LMR system and the MCPTT system respectively. + +### 10.5.2 Information flows for floor control + +#### 10.5.2.1 General + +The following sections describe information flows for interworking floor control. + +In the following information flows the MCPTT ID represents the LMR user, the IWF, or the MCPTT user depending on the interworking methods being used and the message source/destination. + +#### 10.5.2.2 IWF floor request + +Table 10.5.2.2-1 describes the information flow IWF floor request, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to request the floor for media transfer. + +**Table 10.5.2.2-1: IWF floor request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Requester identity | +| Floor priority | M | Priority of the request | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Location | O | Location information of requester | + +#### 10.5.2.3 IWF floor granted + +Table 10.5.2.3-1 describes the information flow IWF floor granted, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that a request for floor is granted and media transfer is possible. + +**Table 10.5.2.3-1: IWF floor granted** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Granted party identity | +| Duration | M | The time for which the granted party is allowed to transmit | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.4 IWF floor rejected + +Table 10.5.2.4-1 describes the information flow IWF floor rejected, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that a request for the floor is rejected. + +**Table 10.5.2.4-1: IWF floor rejected** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Rejected party identity | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Rejection cause | O | Indicates the cause for floor rejection | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.5 IWF floor request cancel + +Table 10.5.2.5-1 describes the information flow IWF floor request cancel, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to request cancelling the floor request from the floor request queue. + +**Table 10.5.2.5-1: IWF floor request cancel** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity for the requester | +| List of MCPTT IDs | M | Target identity (Identities) whose floor request is to be cancelled | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +### 10.5.2.6 IWF floor request cancel response + +Table 10.5.2.6-1 describes the information flow IWF floor request cancel response, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the response for the floor request cancellation. + +**Table 10.5.2.6-1: IWF floor request cancel response** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of party that initiated the cancellation request | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.7 IWF floor request cancel notify + +Table 10.5.2.7-1 describes the information flow IWF floor request cancel notify, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the floor request is cancelled by the administrator/floor control server. + +**Table 10.5.2.7-1: IWF floor request cancel notify** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of the administrator | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.8 IWF floor idle + +Table 10.5.2.8-1 describes the information flow IWF floor idle, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that a session is in idle status, i.e. the floor is not granted to any party. + +**Table 10.5.2.8-1: IWF floor idle** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.9 IWF floor release + +Table 10.5.2.9-1 describes the information flow IWF floor release, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the media transfer is completed and the floor is released. + +**Table 10.5.2.9-1: IWF floor release** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of party that released the floor | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +### 10.5.2.10 IWF floor taken + +Table 10.5.2.10-1 describes the information flow IWF floor taken, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the floor is granted to another MCPTT user. + +**Table 10.5.2.10-1: IWF floor taken** + +| Information element | Status | Description | +|---------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity for the granted party | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Permission to request the floor | O | Indicates whether receiving parties are allowed to request the floor or not (e.g. broadcast call). | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | +| Location | O | Location information of the granted party | + +### 10.5.2.11 IWF floor revoked + +Table 10.5.2.11-1 describes the information flow IWF floor revoked, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the floor is revoked from its current holder (the floor participant who was granted the floor). + +**Table 10.5.2.11-1: IWF floor revoked** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Revoked party identity | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.12 IWF floor acknowledgement + +Table 10.5.2.12-1 describes the information flow IWF floor acknowledgement, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to provide an acknowledgement if the acknowledgement is required in the received floor control message. + +NOTE: The floor acknowledgement flow can be sent by the floor control server after each floor control information flow that includes an indication that an acknowledgement is required. + +**Table 10.5.2.12-1: IWF floor acknowledgement** + +| Information element | Status | Description | +|---------------------|--------|-------------------------| +| MCPTT ID | M | Identity of the sender. | + +### 10.5.2.13 IWF queue position request + +Table 10.5.2.13-1 describes the information flow IWF queue position request, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to request the position in the floor request queue. The MCPTT server and the MCPTT client that support queuing of the floor control requests shall support this information flow. + +**Table 10.5.2.13-1: IWF queue position request** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of party whose floor position is requested | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +### 10.5.2.14 IWF queue position info + +Table 10.5.2.14-1 describes the information flow IWF queue position info, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate the floor request is queued and the queue position to the floor requesting UE. + +**Table 10.5.2.14-1: IWF queue position info** + +| Information element | Status | Description | +|--------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of party whose floor position is provided | +| Queue position info | M | Position of the queued floor request in the queue | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | +| Acknowledgement required | O | Indicates if acknowledgement from the floor participant is required | + +### 10.5.2.15 IWF unicast media stop request + +Table 10.5.2.15-1 describes the information flow IWF unicast media stop request, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that the unicast media flow of the designated communication does not need to be sent to the client indicated by the MCPTT ID. + +**Table 10.5.2.15-1: IWF unicast media stop request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of the requester | +| Source identifier | O | Identifies the communication whose media flow is to be stopped, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +### 10.5.2.16 IWF unicast media resume request + +Table 10.5.2.16-1 describes the information flow IWF unicast media resume request, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used by the floor control server to request that the unicast media flow of the designated communication is to be sent to the client indicated by the MCPTT ID. + +**Table 10.5.2.16-1: IWF unicast media resume request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity of the requester | +| Source identifier | O | Identifies the communication whose media flow is to be resumed, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +### 10.5.2.17 IWF floor talker ID update + +Table 10.5.2.17-1 describes the information flow IWF floor talker ID update, from the IWF to the MCPTT floor control server and from the MCPTT floor control server to the IWF, which is used to indicate that the talker ID has changed for the current MCPTT user granted the floor. + +**Table 10.5.2.17-1: IWF floor talker ID update** + +| Information element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------------------------------------------------| +| MCPTT ID | M | Identity for the party using the floor | +| Source identifier | O | Identifies the communication, e.g. by identifying the media flow within a media multiplex, present only if media multiplexing | + +## 10.5.3 Interworking floor control + +3GPP TS 23.379 [7], subclause 10.9.1.4.1 describes floor control involving groups in multiple MCPTT systems where floor control arbitration resides with the primary MCPTT server and all floor control messages are routed to that primary MCPTT server. The group is homed on the primary MCPTT server. + +An interworking group can be homed on the MCPTT server or on the LMR system. When the group is homed on the MCPTT server the floor control server is on this MCPTT server. When the group is homed on the LMR system the floor control server is represented by the IWF. + +The primary MCPTT system of an MCPTT group is defined by configuration and identified by the MC service group ID. + +3GPP TS 23.379 [7], subclause 10.9.1.4.2 describes floor control involving groups in multiple MCPTT systems where the partner MCPTT system filters its MCPTT users' floor requests before communicating with the floor control server of the primary MCPTT system. When an MCPTT system is interworking with an IWF, depending on where the group + +is homed the MCPTT server, or the IWF can filter floor control requests in the same way as an interconnected MCPTT system. + +In a private call, one of the IWF or MCPTT server acts as the controlling floor control server within the call, and manages arbitration of floor control requests received from both users in the call. The entity (MCPTT server or IWF) that does not fulfil the controlling role shall send all floor control requests from its served call participant to the controlling floor control server without filtering. + +NOTE: Allocation of controlling floor control server functionality to the MCPTT server or IWF may be according to the system within which the call originated, or by some other means. + +### 10.5.4 Floor override without using floor revoked on an interworking group + +This procedure describes the case where a transmitting radio cannot be signalled that the floor has been taken or revoked. Within the context of interworking between MCPTT and LMR systems, this condition can occur due to both MCPTT and LMR users obtaining the floor simultaneously, or the floor granted to an LMR user is taken by an MCPTT user. + +Figure 10.5.4-1 shows the high-level procedure where an MCPTT session is already established between the floor participants (with floor granted to an LMR user represented by the IWF) and the floor control server (with an override based on priority and configured to permit the transmission of overridden floor participant from the IWF). The group is defined in the MCPTT system and the MCPTT Server is the floor control server. Only two UEs involved in the session are shown for simplicity. + +Pre-conditions: + +1. The MCPTT floor control server has been configured to support override. +2. The override supported in this case permits both the overridden floor participant and the overriding floor participant to be transmitting. +3. An MCPTT session is established between an MCPTT client, the interworked system, and MCPTT server. +4. Session is ongoing. + +![Sequence diagram showing floor override procedure. It involves MCPTT Client A, MCPTT Server, and IWF. Steps include session establishment, floor request from Client A, floor arbitration, floor grant to Client A, and override notification to IWF, followed by voice media transmission.](2e18ae7359d8c32e96919956f238ecc5_img.jpg) + +``` + +sequenceDiagram + participant ClientA as MCPTT Client A + participant Server as MCPTT Server + participant IWF as IWF + + Note over ClientA, IWF: 1. Session is established. Floor is granted to the IWF. + ClientA->>Server: 2. MCPTT Floor Request + Note over Server: 3. Floor arbitration by priority + Server->>ClientA: 4. MCPTT Floor Grant + Server->>IWF: 5. Override Notification + Note over ClientA, IWF: 6. Voice Media + +``` + +Sequence diagram showing floor override procedure. It involves MCPTT Client A, MCPTT Server, and IWF. Steps include session establishment, floor request from Client A, floor arbitration, floor grant to Client A, and override notification to IWF, followed by voice media transmission. + +Figure 10.5.4-1: Floor override (overridden continues to transmit) during an interworking session + +1. It is assumed that the floor participant B (represented by the IWF in figure 10.5.4-1) has been given the floor and is transmitting voice media. +2. Floor participant A, having a floor priority which is relatively higher than that of floor participant B, wants to send voice media over the session. +3. Floor participant A sends a floor request message to the floor control server. +4. The floor control server determines to accept the floor request from floor participant A based on arbitration result e.g., according to the floor priority information that is received in the floor request message. +- 5a. Floor control server responds with a floor granted message to floor participant A. +- 5b. Floor control server sends a floor taken message to the other floor participants (via the IWF). Floor participant B continues transmitting the (overridden) voice media transmission. + +NOTE 1: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn who the newly granted talker (overriding) is. + +- 6a. The floor granted causes the user of floor participant A to be notified. +- 6b. Floor participant B cannot be notified of the status because it is unable to receive the message and continues transmitting. +7. Floor participant A (overriding) starts sending voice media over the session established beforehand. + +NOTE 2: Floor participant B is still sending voice (overridden). The list of floor participants that receive the overriding, overridden, or both transmissions is based on configuration. + +NOTE 3: When floor participant A stops transmitting, if floor participant B is still sending voice, then the floor is granted back to floor participant B and audio is routed to all current floor participants. + +## 10.5.5 Floor control on an interworking group homed in the LMR system + +Figure 10.5.5-1 shows the procedure for floor control on an interworking group homed in the LMR system. Simultaneous floor requests are included to show various aspects of interworking floor control. + +Pre-conditions: + +1. The interworking group is homed in the LMR system. +2. The MCPTT server is configured to locally filter competing floor control requests before communicating with the IWF. +3. MCPTT client 1, MCPTT client 2, and LMR users (represented by the IWF) are affiliated to that group. +4. An interworking group call is ongoing involving MCPTT users and LMR users (represented by the IWF). The floor is currently idle. + +![Sequence diagram illustrating floor control on a group homed in the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT Floor Control Server, and IWF. Client 1 and 2 send floor requests to the server. The server forwards the request from Client 1 to the IWF. The IWF returns a floor granted message to the server. The server then sends a floor granted message to Client 1 and a floor taken message to Client 2. Client 1 then begins sending voice media.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT Floor Control Server + participant IWF + Note left of MCPTT Client 1: User wants to send voice media + MCPTT Client 1->>MCPTT Floor Control Server: FLOOR REQUEST (Client 1) + MCPTT Client 2->>MCPTT Floor Control Server: FLOOR REQUEST (Client 2) + MCPTT Floor Control Server->>IWF: FLOOR REQUEST (Client 1) + IWF-->>MCPTT Floor Control Server: FLOOR GRANTED + MCPTT Floor Control Server->>MCPTT Client 1: FLOOR GRANTED + MCPTT Floor Control Server->>MCPTT Client 2: FLOOR TAKEN + Note right of MCPTT Client 1: User granted floor + MCPTT Client 1->>IWF: VOICE MEDIA + +``` + +Sequence diagram illustrating floor control on a group homed in the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT Floor Control Server, and IWF. Client 1 and 2 send floor requests to the server. The server forwards the request from Client 1 to the IWF. The IWF returns a floor granted message to the server. The server then sends a floor granted message to Client 1 and a floor taken message to Client 2. Client 1 then begins sending voice media. + +**Figure 10.5.5-1: Floor control on a group homed in the LMR system** + +1. The users of MCPTT Client 1 and MCPTT Client 2 both want to send voice media over the session. +2. MCPTT Clients 1 and 2 send floor request messages to the floor control server. +3. The MCPTT floor control server determines to accept the floor request from MCPTT Client 1 based on local arbitration results (e.g., according to priority information versus the competing request from MCPTT client 2). +4. The user of MCPTT client 2 is notified that their floor request was rejected. +5. Since the group is homed in the LMR system the MCPTT floor control server forwards the floor request to the IWF for final floor control determination. The IWF performs floor arbitration in conjunction with the LMR system (not shown). The IWF determines that the floor can be granted to the MCPTT user. +6. The IWF sends a floor granted message to the MCPTT floor control server. +7. The MCPTT floor control server sends a floor granted message to MCPTT client 1. +8. The MCPTT floor control server sends a floor taken message to MCPTT client 2 to notify the user of who is granted the floor. +9. MCPTT Client 1 notifies the user that he/she has been granted the floor and may begin speaking. +10. MCPTT Client 1 begins sending voice media over the established session. The media is distributed to affiliated group members including the IWF. + +## 10.5.6 Floor control on an interworking group homed in the MCPTT system + +Figure 10.5.6-1 shows the procedure for floor control on an interworking group homed in the MCPTT system, and the LMR system is configured for local floor control request filtering. Simultaneous floor requests are included to show various aspects of interworking floor control. + +Pre-conditions: + +1. The interworking group is homed in the MCPTT system. +2. The interworking group is previously defined on the group management server. +3. MCPTT client 1, MCPTT client 2, and LMR users (represented by the IWF) are affiliated to that group. +4. An interworking group call is ongoing involving MCPTT users and LMR users (represented by the IWF). The floor is currently idle. + +![Sequence diagram illustrating floor control on a group homed in the MCPTT system. Lifelines: MCPTT CLIENT 1, MCPTT CLIENT 2, MCPTT SERVER, and IWF. The sequence shows simultaneous floor requests from MCPTT CLIENT 1 and IWF to the MCPTT SERVER. The MCPTT SERVER responds with 'FLOOR GRANTED' to MCPTT CLIENT 1 and 'FLOOR DENIED' to IWF. MCPTT CLIENT 1 then sends a 'TRANSMISSION' message to MCPTT CLIENT 2, which responds with 'TRANSMISSION'.](c2f5e14ca0ed0f7944c7606451f67d85_img.jpg) + +``` + +sequenceDiagram + participant MCPTT_CLIENT_1 as MCPTT CLIENT 1 + participant MCPTT_CLIENT_2 as MCPTT CLIENT 2 + participant MCPTT_SERVER as MCPTT SERVER + participant IWF as IWF + + Note left of MCPTT_CLIENT_1: FLOOR REQUESTED + MCPTT_CLIENT_1->>MCPTT_SERVER: FLOOR REQUEST + Note right of IWF: FLOOR REQUESTED + IWF->>MCPTT_SERVER: FLOOR REQUEST + MCPTT_SERVER-->>MCPTT_CLIENT_1: FLOOR GRANTED + Note left of MCPTT_CLIENT_1: TRANSMISSION + MCPTT_CLIENT_1->>MCPTT_CLIENT_2: TRANSMISSION + MCPTT_SERVER-->>IWF: FLOOR DENIED + Note right of MCPTT_CLIENT_2: TRANSMISSION + MCPTT_CLIENT_2->>MCPTT_SERVER: TRANSMISSION + +``` + +Sequence diagram illustrating floor control on a group homed in the MCPTT system. Lifelines: MCPTT CLIENT 1, MCPTT CLIENT 2, MCPTT SERVER, and IWF. The sequence shows simultaneous floor requests from MCPTT CLIENT 1 and IWF to the MCPTT SERVER. The MCPTT SERVER responds with 'FLOOR GRANTED' to MCPTT CLIENT 1 and 'FLOOR DENIED' to IWF. MCPTT CLIENT 1 then sends a 'TRANSMISSION' message to MCPTT CLIENT 2, which responds with 'TRANSMISSION'. + +**Figure 10.5.6-1: Floor control on a group homed in the MCPTT system** + +1. The user of MCPTT Client 1 wants to send voice media over the session. At the same time a user in the LMR system (represented by the IWF) wants to also send voice media over the session. +2. MCPTT Client 1 sends a floor request message to the MCPTT floor control server. +3. The IWF sends a floor request message to the MCPTT floor control server. + +NOTE: If multiple LMR users want to speak, it is assumed that the LMR system has arbitrated these requests based on local policies and only presents one floor request to the MCPTT system. + +4. Since the group is homed in the MCPTT system the MCPTT floor control server performs final floor control determination. In this case the MCPTT floor control server determines to accept the floor request from MCPTT + +Client 1 based on local policy and arbitration results (e.g., according to time of arrival of the request versus the competing request from the IWF). + +5. The IWF is notified that its floor request was rejected. +6. The MCPTT floor control server sends a floor granted message to MCPTT client 1. +7. The MCPTT floor control server sends a floor taken message to both MCPTT client 2 and the IWF to inform them of who is granted the floor. +8. MCPTT Client 1 notifies the user that he/she has been granted the floor and may begin speaking. +9. MCPTT Client 1 begins sending voice media over the established session. The media is distributed to affiliated group members including the IWF. + +### 10.5.7 Floor control without local filtering on an interworking group defined in the LMR system + +Figure 10.5.7-1 shows the procedure for floor control on an interworking group defined in the LMR system where local filtering is not performed by the MCPTT server. Simultaneous floor requests are included to show various aspects of interworking floor control. + +Pre-conditions: + +1. The interworking group is defined in the LMR system. +2. The MCPTT system is configured to send competing floor control requests to the LMR system (represented by the IWF) for floor control arbitration. +3. MCPTT client 1, MCPTT client 2, and LMR users are affiliated to that group. +4. An interworking group call is ongoing involving MCPTT users and LMR users. The floor is currently idle. + +![Sequence diagram illustrating floor control without local filtering on a group defined in the LMR system. The diagram shows interactions between MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. Both clients send floor requests. The server forwards them to the IWF. The IWF grants the floor to client 1, rejects client 2, and sends a floor taken message to client 2. The server then notifies client 1 of the granted floor and client 2 of the taken floor. Finally, client 1 sends voice media, which is distributed by the server and IWF to other members.](0b998e3ad8f9d104768642612605cb35_img.jpg) + +``` + +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT server + participant IWF + Note left of MCPTT client 1: 1. User wants to talk + Note left of MCPTT client 2: 1. User wants to talk + MCPTT client 1->>MCPTT server: 2. Floor request + MCPTT client 2->>MCPTT server: 2. Floor request + MCPTT server->>IWF: 3. IWF Floor request + MCPTT server->>IWF: 3. IWF Floor request + IWF-->>MCPTT server: 4. IWF Floor granted + IWF-->>MCPTT server: 4. IWF Floor rejected + IWF-->>MCPTT server: 4. IWF Floor taken + MCPTT server->>MCPTT client 2: 5. Floor rejected + MCPTT server->>MCPTT client 1: 6. Floor granted + MCPTT server->>MCPTT client 2: 7. Floor taken + Note right of MCPTT client 1: 8. Talker notification + MCPTT client 1->>MCPTT server: 9. Voice media + MCPTT server->>IWF: 9. IWF Voice media + IWF-->>MCPTT client 2: 9. Voice media + +``` + +Sequence diagram illustrating floor control without local filtering on a group defined in the LMR system. The diagram shows interactions between MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. Both clients send floor requests. The server forwards them to the IWF. The IWF grants the floor to client 1, rejects client 2, and sends a floor taken message to client 2. The server then notifies client 1 of the granted floor and client 2 of the taken floor. Finally, client 1 sends voice media, which is distributed by the server and IWF to other members. + +**Figure 10.5.7-1: Floor control without local filtering on a group defined in the LMR system** + +1. The users of MCPTT client 1 and MCPTT client 2 both want to send voice media over the session. + 2. MCPTT clients 1 and 2 send floor request messages to the MCPTT floor control server. + 3. Since the group is defined in the LMR system the MCPTT floor control server forwards these floor requests to the IWF for final floor control determination. The IWF performs floor arbitration in conjunction with the LMR system (not shown). The IWF determines that the floor can be granted to MCPTT client 1. + 4. The IWF sends an IWF floor granted message for MCPTT client 1, an IWF floor rejected message for MCPTT client 2, and an IWF floor taken message for MCPTT client 2 to the MCPTT floor control server. +- NOTE: If other MCPTT clients are affiliated to this group, the IWF sends an IWF floor taken message to the MCPTT floor control server for each one of them. +5. The MCPTT floor control server sends a Floor rejected message to MCPTT client 2 to notify the user that his/her floor request was rejected. + 6. The MCPTT floor control server sends a Floor granted message to MCPTT client 1. + 7. The MCPTT floor control server sends a Floor taken message to MCPTT client 2 to notify the user of who is granted the floor. + 8. MCPTT client 1 notifies the user that he/she has been granted the floor and may begin speaking. + 9. MCPTT client 1 begins sending voice media over the established session. The media is distributed to affiliated group members including the IWF. + +## 10.5.8 Floor control without local filtering on an interworking group defined in the MCPTT system + +Figure 10.5.8-1 shows the procedure for floor control on an interworking group defined in the MCPTT system where local filtering is not performed by the LMR system. Simultaneous floor requests are included to show various aspects of interworking floor control. + +Pre-conditions: + +1. The interworking group is defined in the MCPTT system. +2. MCPTT client 1, MCPTT client 2, and LMR users are affiliated to that group. +3. The LMR system (represented by the IWF) is configured to send all competing floor control requests to the MCPTT system for floor control arbitration. +4. The IWF is not affiliating on behalf of LMR users. All LMR group affiliations are passed through the IWF to the MCPTT server. +5. An interworking group call is ongoing involving MCPTT users and LMR users. The floor is currently idle. + +![Sequence diagram illustrating floor control without local filtering on an interworking group defined in the MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. Steps include: 1. User wants to talk (MCPTT client 1); 2. Floor request (MCPTT client 1 to MCPTT server); 3. IWF floor request (IWF to MCPTT server, two instances); 4. Floor arbitration by policy (MCPTT server); 5. IWF floor rejected (MCPTT server to IWF, two instances); 6. Floor granted (MCPTT server to MCPTT client 1); 7. Floor taken (MCPTT server to MCPTT client 2, two instances); 8. Talker notification (MCPTT client 1); 9. Voice media (MCPTT client 1 to MCPTT server, MCPTT server to IWF, and IWF to MCPTT client 2).](b49477e8f148b5ef044a2fd5a43528f6_img.jpg) + +``` +sequenceDiagram + participant MCPTT client 1 + participant MCPTT client 2 + participant MCPTT server + participant IWF + Note left of MCPTT client 1: 1. User wants to talk + MCPTT client 1->>MCPTT server: 2. Floor request + Note right of IWF: 3. IWF floor request + IWF->>MCPTT server: 3. IWF floor request + Note right of MCPTT server: 4. Floor arbitration by policy + Note right of MCPTT server: 5. IWF floor rejected + MCPTT server->>IWF: 5. IWF floor rejected + MCPTT server->>MCPTT client 1: 6. Floor granted + Note right of MCPTT server: 7. IWF floor taken + MCPTT server->>IWF: 7. IWF floor taken + Note left of MCPTT client 1: 8. Talker notification + MCPTT client 1->>MCPTT server: 9. Voice media + MCPTT server->>IWF: 9. IWF voice media + IWF->>MCPTT client 2: 9. Voice media +``` + +Sequence diagram illustrating floor control without local filtering on an interworking group defined in the MCPTT system. The diagram shows interactions between MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. Steps include: 1. User wants to talk (MCPTT client 1); 2. Floor request (MCPTT client 1 to MCPTT server); 3. IWF floor request (IWF to MCPTT server, two instances); 4. Floor arbitration by policy (MCPTT server); 5. IWF floor rejected (MCPTT server to IWF, two instances); 6. Floor granted (MCPTT server to MCPTT client 1); 7. Floor taken (MCPTT server to MCPTT client 2, two instances); 8. Talker notification (MCPTT client 1); 9. Voice media (MCPTT client 1 to MCPTT server, MCPTT server to IWF, and IWF to MCPTT client 2). + +**Figure 10.5.8-1: Floor control without local filtering on a group defined in the MCPTT system** + +1. The user of MCPTT client 1 wants to send voice media over the session. At the same time multiple users in the LMR system (represented by the IWF) want to also send voice media over the session. +2. MCPTT client 1 sends a floor request message to the MCPTT floor control server. +3. The IWF sends floor request messages to the MCPTT floor control server for each LMR user requesting the floor. In this case two LMR users are requesting the floor. These floor requests contain the MCPTT ID of the LMR user (converted by the IWF). + +4. Since the group is defined in the MCPTT system the MCPTT floor control server performs final floor control determination. In this case the MCPTT floor control server determines to accept the floor request from MCPTT client 1 based on local policy and arbitration results (e.g., according to priority of the request versus the competing requests from the IWF). + 5. The IWF is notified that its floor requests were rejected. The MCPTT floor control server sends an IWF floor rejected message to the IWF for each floor request. + 6. The MCPTT floor control server sends a floor granted message to MCPTT client 1. + 7. The MCPTT floor control server sends floor taken messages to MCPTT client 2 and the IWF to inform them of who is granted the floor. In this case a floor taken message is sent to the IWF corresponding to each affiliated LMR user. +- NOTE: If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF floor taken message is sent to the IWF. +8. MCPTT client 1 notifies the user that he/she has been granted the floor and may begin speaking. + 9. MCPTT client 1 begins sending voice media over the established session. The media is distributed to affiliated group members including the LMR users. + +### 10.5.9 Floor control in private call controlled by the LMR system + +Figure 10.5.9-1 shows a procedure for a private call with floor control where the LMR system controls the floor. A request for transmission by the MCPTT user while the LMR user has the floor is rejected by the IWF, to show various aspects of interworking floor control. + +Pre-conditions: + +1. A private call has been set up between an LMR user and MCPTT client 1. +2. The LMR system is controlling the floor, via the IWF. +3. MCPTT client 1 has the floor. + +![Sequence diagram illustrating floor control in a private call controlled by the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT server, and IWF. The sequence starts with MCPTT Client 1 sending a 'Floor release' to the MCPTT server, which then sends an 'IWF floor release' to the IWF. The IWF responds with 'IWF floor idle', which the MCPTT server relays as 'Floor idle' to the client. The IWF then sends 'IWF floor taken' to the MCPTT server, which relays it as 'Floor taken' to the client. Voice media is exchanged between the client and server (7b) and the server and IWF (7a). A box indicates the user decides to interrupt LMR user transmission. The client then sends a 'Floor request' to the server, which sends an 'IWF Floor request' to the IWF. The IWF responds with 'IWF floor rejected' to the server, which relays it as 'Floor rejected' to the client.](86e1f8551d4922ea8fa197f96fe4098b_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT server + participant IWF + Note left of MCPTT Client 1: 8. User decides to interrupt LMR user transmission + MCPTT Client 1->>MCPTT server: 1. Floor release + MCPTT server->>IWF: 2. IWF floor release + IWF-->>MCPTT server: 3. IWF floor idle + MCPTT server-->>MCPTT Client 1: 4. Floor idle + IWF-->>MCPTT server: 5. IWF floor taken + MCPTT server-->>MCPTT Client 1: 6. Floor taken + Note right of MCPTT Client 1: 7b. Voice media + Note left of IWF: 7a. Voice media + MCPTT Client 1->>MCPTT server: 9. Floor request + MCPTT server->>IWF: 10. IWF Floor request + IWF-->>MCPTT server: 11. IWF floor rejected + MCPTT server-->>MCPTT Client 1: 12. Floor rejected + +``` + +Sequence diagram illustrating floor control in a private call controlled by the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT server, and IWF. The sequence starts with MCPTT Client 1 sending a 'Floor release' to the MCPTT server, which then sends an 'IWF floor release' to the IWF. The IWF responds with 'IWF floor idle', which the MCPTT server relays as 'Floor idle' to the client. The IWF then sends 'IWF floor taken' to the MCPTT server, which relays it as 'Floor taken' to the client. Voice media is exchanged between the client and server (7b) and the server and IWF (7a). A box indicates the user decides to interrupt LMR user transmission. The client then sends a 'Floor request' to the server, which sends an 'IWF Floor request' to the IWF. The IWF responds with 'IWF floor rejected' to the server, which relays it as 'Floor rejected' to the client. + +**Figure 10.5.9-1: Floor control with control by the LMR system** + +1. The user of MCPTT Client 1 finishes transmission and MCPTT client 1 releases the floor. + +2. The MCPTT server informs the IWF of the floor release. + 3. The IWF indicates that the floor is now idle. + 4. MCPTT client 1 is informed that the floor is idle. + 5. The IWF indicates that the floor has been taken by the LMR user. + 6. The MCPTT server informs MCPTT client 1 that the floor has been taken by the LMR user. + 7. Media flows from the LMR user to the IWF (7a) and on to MCPTT client 1 (7b). + 8. The user of MCPTT client 1 decides to interrupt the transmission from the LMR user. + 9. MCPTT Client 1 sends a floor request with an appropriate priority to request interruption of the transmission from the LMR user. + 10. The MCPTT server forwards the floor request to the IWF. + 11. The LMR system rejects the request, and the IWF informs the MCPTT server of the rejection. +- NOTE: The reason that the request is rejected is outside the scope of the present document. +12. The MCPTT server informs MCPTT client 1 that the request for interruption has been rejected. + +### 10.5.10 Floor control in private call controlled by the MCPTT system + +Figure 10.5.10-1 shows a procedure for a private call with floor control where the MCPTT system controls the floor. A request for transmission by the LMR user while the MCPTT user has the floor is accepted by the MCPTT server, to show various aspects of interworking floor control. + +Pre-conditions: + +1. A private call has been set up between the LMR user and MCPTT client 1. +2. The MCPTT server is controlling the floor. +3. The floor is idle. + +![Sequence diagram illustrating floor control in a private call controlled by the MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT server, and IWF. The sequence starts with MCPTT Client 1 sending a floor request to the MCPTT server, which grants it. The MCPTT server then informs the IWF that the floor is taken. Voice media flows from MCPTT Client 1 to the MCPTT server and then to the IWF. The IWF receives a request for interruption from an LMR user and sends a floor request to the MCPTT server. The MCPTT server decides to grant the floor to the LMR user, revokes the floor from MCPTT Client 1, and informs the IWF. The IWF grants the floor to the LMR user, and voice media flows from the LMR user to the IWF and then to MCPTT Client 1.](3b8ac904c44dd47c5ccd03def99a19c4_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT server + participant IWF + Note right of IWF: 5. IWF receives request for interruption from LMR user + Note left of MCPTT server: 7. MCPTT server decides to grant floor to LMR user + + MCPTT Client 1->>MCPTT server: 1. Floor request + MCPTT server-->>MCPTT Client 1: 2. Floor granted + MCPTT server->>IWF: 3. IWF floor taken + MCPTT Client 1->>MCPTT server: 4a. Voice media + MCPTT server->>IWF: 4b. Voice media + IWF->>MCPTT server: 6. IWF floor request + MCPTT server-->>MCPTT Client 1: 8. Floor revoked + MCPTT server->>IWF: 9. IWF floor granted + IWF->>MCPTT server: 10a. Voice media + MCPTT server->>MCPTT Client 1: 10b. Voice media + +``` + +Sequence diagram illustrating floor control in a private call controlled by the MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT server, and IWF. The sequence starts with MCPTT Client 1 sending a floor request to the MCPTT server, which grants it. The MCPTT server then informs the IWF that the floor is taken. Voice media flows from MCPTT Client 1 to the MCPTT server and then to the IWF. The IWF receives a request for interruption from an LMR user and sends a floor request to the MCPTT server. The MCPTT server decides to grant the floor to the LMR user, revokes the floor from MCPTT Client 1, and informs the IWF. The IWF grants the floor to the LMR user, and voice media flows from the LMR user to the IWF and then to MCPTT Client 1. + +Figure 10.5.10-1: Floor control with control by the MCPTT system + +1. MCPTT Client 1 requests the floor. +2. The MCPTT server grants the floor to MCPTT Client 1. +3. The MCPTT server informs the IWF that the floor has been granted to MCPTT client 1. + +NOTE 1: Step 3 may occur before or after step 2. + +4. MCPTT client 1 sends voice media to the MCPTT server (4a) which forwards the voice media to the IWF (4b). +5. The LMR user decides to interrupt the transmission from MCPTT client 1, and the IWF is informed. +6. The IWF sends a floor request to the MCPTT server with sufficient priority to interrupt MCPTT client 1. +7. The MCPTT server decides to allow the interruption from the LMR user, based on the priority of the request and on configuration. +8. The MCPTT server informs MCPTT Client 1 that the transmission permission has been revoked. +9. The floor is granted to the LMR user via the IWF. + +NOTE 2: Step 9 may occur before or after step 8. + +10. Voice media is sent from the LMR user via the IWF to the MCPTT server (10a) and on to MCPTT client 1 (10b). + +## 10.6 Emergency and imminent peril + +### 10.6.1 Information flows for emergency and imminent peril + +#### 10.6.1.1 IWF emergency group call request + +Table 10.6.1.1-1 describes the information flow IWF emergency group call request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.1-1: IWF emergency group call request information elements** + +| Information Element | Status | Description | +|-------------------------------------------------------------------------------------------|--------|------------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Emergency indicator | M | Indicates that the group call request is an MCPTT emergency call | +| Alert indicator | O | May be used to indicate that an emergency alert is to be sent | +| Location | O | Location, if available | +| Implicit floor request (see NOTE) | O | Indicates that the originating client requests the floor | +| NOTE: This element shall be included only when the originating client requests the floor. | | | + +#### 10.6.1.2 IWF emergency group call response + +Table 10.6.1.2-1 describes the information flow IWF emergency group call response from the MCPTT server to the IWF and from the IWF to the MCPTT server. + +**Table 10.6.1.2-1: IWF emergency group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Result | M | The IWF emergency group call request may be rejected. | + +### 10.6.1.3 IWF imminent peril group call request + +Table 10.6.1.3-1 describes the information flow IWF imminent peril group call request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.3-1: IWF imminent peril group call request information elements** + +| Information Element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Imminent peril indicator | M | Indicates that the group call request is an imminent peril call | +| Location | O | Location, if available | +| Implicit floor request (see NOTE) | O | Indicates that the originating client requests the floor | +| NOTE: This element shall be included only when this information flow is from the client to the server and the originator requests the floor. | | | + +### 10.6.1.4 IWF imminent peril group call response + +Table 10.6.1.4-1 describes the information flow IWF imminent peril group call response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.4-1: IWF imminent peril group call response information elements** + +| Information Element | Status | Description | +|---------------------|--------|------------------------------------------------------------| +| MCPTT ID | M | The identity of the calling party | +| MCPTT group ID | M | The MCPTT group ID on which the call is to be conducted | +| Result | M | The IWF imminent peril group call request may be rejected. | + +### 10.6.1.5 IWF in-progress imminent peril group state cancel request + +Table 10.6.1.5-1 describes the information flow IWF in-progress imminent peril group state cancel request from the MCPTT server to the IWF. + +**Table 10.6.1.5-1: IWF in-progress imminent peril group state cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the in-progress imminent peril state is to be cancelled | + +### 10.6.1.6 IWF in-progress imminent peril group state cancel response + +Table 10.6.1.6-1 describes the information flow IWF in-progress imminent peril group state cancel response from the IWF to the MCPTT server. + +**Table 10.6.1.6-1: IWF in-progress imminent peril group state cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the in-progress imminent peril state is to be cancelled | + +### 10.6.1.7 IWF emergency alert request + +Table 10.6.1.7-1 describes the information flow IWF emergency alert request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.7-1: IWF emergency alert request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------| +| MCPTT ID | M | The identity of the alerting party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | +| Organization name | O | The alerting MCPTT user's mission critical organization name. | +| Location | O | The alerting MCPTT client's location | + +### 10.6.1.8 IWF emergency alert response + +Table 10.6.1.8-1 describes the information flow IWF emergency alert response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.8-1: IWF emergency alert response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MCPTT ID | M | The identity of the alerting party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | + +### 10.6.1.9 IWF emergency alert cancel request + +Table 10.6.1.9-1 describes the information flow IWF emergency alert cancel request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.9-1: IWF emergency alert cancel request information elements** + +| Information Element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------| +| MCPTT ID | M | MCPTT user identity of the cancelling party | +| MCPTT ID (see NOTE) | O | MCPTT user identity whose emergency alert is to be cancelled | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | +| Group's in-progress emergency alert cancel request | O | Requests cancellation of the in-progress emergency alert of the group | +| NOTE: This information shall be present if the message is requesting cancellation of another MCPTT user's alert. If not present, then the alert of the MCPTT ID of the cancelling party is being cancelled | | | + +### 10.6.1.10 IWF emergency alert cancel response + +Table 10.6.1.10-1 describes the information flow IWF emergency alert cancel response from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.10-1: IWF emergency alert cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID with which the alert is associated | + +### 10.6.1.11 IWF in-progress emergency group state cancel request + +Table 10.6.1.11-1 describes the information flow IWF in-progress emergency group state cancel request from the IWF to the MCPTT server and from the MCPTT server to the IWF. + +**Table 10.6.1.11-1: IWF in-progress emergency group state cancel request information elements** + +| Information Element | Status | Description | +|---------------------|--------|---------------------------------------------------------------------------------------| +| MCPTT ID | M | The identity of the cancelling party | +| MCPTT group ID | M | The MCPTT group ID on which the MCPTT in-progress emergency state is to be cancelled. | +| Alert indicator | O | Indicates whether the emergency alert of the cancelling party is to be cancelled | + +### 10.6.1.12 IWF in-progress emergency group state cancel response + +Table 10.6.1.12-1 describes the information flow IWF in-progress emergency group state cancel response from the MCPTT server to the IWF and from IWF to MCPTT server. + +**Table 10.6.1.12-1: IWF in-progress emergency group state cancel response information elements** + +| Information Element | Status | Description | +|---------------------|--------|-----------------------------------------------------------------------------------------------| +| MCP TT ID | M | The identity of the cancelling party | +| MCP TT group ID | M | The MCP TT group ID on which the MCP TT in-progress emergency in-progress is to be cancelled. | + +## 10.6.2 Emergency calls + +### 10.6.2.1 General + +This subclause addresses various aspects of emergency call interworking. + +Where the group is defined in the MCP TT system and where the IWF has affiliated to an MCP TT group with a single affiliation on behalf of all LMR group members, only a single IWF emergency group call request / IWF in-progress emergency group state cancel request message is sent to the IWF at the commencement / release of an emergency group call. Where the group is defined in the MCP TT system and where the IWF has passed through individual affiliations for each group member in the LMR system, the MCP TT system shall send individual IWF emergency group call request / IWF in-progress emergency group state cancel request messages to the IWF for all affiliated group members in the LMR system in accordance with primary and partner MCP TT system behaviour. In both cases, the distribution of the messages to group members in the LMR system is out of scope of the present document. + +Where the group is defined in the LMR system, the IWF shall send individual IWF emergency group call request / IWF in-progress emergency group state cancel request messages to the IWF for all affiliated MCP TT group members in accordance with primary and partner MCP TT system behaviour. + +### 10.6.2.2 Emergency group call + +#### 10.6.2.2.1 Emergency group call setup initiated by a user in the LMR system on an interworking group defined in the MCP TT system + +Figure 10.6.2.2.1-1 shows the procedure for an emergency group call setup initiated by a user in the LMR system. The figure is based upon the figure for emergency calls in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.1. This scenario assumes that the group is an interworking group defined in the MCP TT system. + +NOTE 1: For simplicity, a single MCP TT server is shown in place of a user home MCP TT server and a group hosting MCP TT server. + +NOTE 2: The emergency interworking call procedures reuse the information flows defined 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The MCP TT group is an interworking group defined in the MCP TT system +2. MCP TT client 1 and MCP TT client 2 are affiliated to that MCP TT group. +3. The IWF is connected to and is authorized to interwork with the MCP TT system. +4. The mapping relationship of group and user identities between MCP TT system and LMR system has been configured at the IWF. +5. LMR user initiates an emergency group call. + +![Sequence diagram illustrating the emergency group call setup initiated by an LMR user on an interworking group defined in the MCPTT system. The diagram shows interactions between the LMR User, MCPTT Server, MCPTT Client, and IWF. The process involves the LMR User sending a request to the MCPTT Server, which then interacts with the MCPTT Client and IWF to resolve group members and configure bearers. The MCPTT Server then sends a response back to the LMR User via the IWF.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +``` + +sequenceDiagram + participant LMR User + participant MCPTT Server + participant MCPTT Client + participant IWF + + Note left of LMR User: Emergency group call request + LMR User->>MCPTT Server: Request (MCPTT Group ID, Emergency Indication) + Note right of MCPTT Server: Resolve group members & affiliation status + MCPTT Server->>MCPTT Client: Query (Group ID) + MCPTT Client-->>MCPTT Server: Response (Members, Status) + Note right of MCPTT Server: Configure bearers + MCPTT Server->>IWF: Configure (Group ID, Priority) + Note right of IWF: Bearer configuration + MCPTT Server-->>IWF: Response + IWF-->>LMR User: Response + +``` + +Sequence diagram illustrating the emergency group call setup initiated by an LMR user on an interworking group defined in the MCPTT system. The diagram shows interactions between the LMR User, MCPTT Server, MCPTT Client, and IWF. The process involves the LMR User sending a request to the MCPTT Server, which then interacts with the MCPTT Client and IWF to resolve group members and configure bearers. The MCPTT Server then sends a response back to the LMR User via the IWF. + +**Figure 10.6.2.2.1-1: Emergency group call setup, initiated by LMR user on an interworking group defined in the MCPTT system** + +1. The IWF sends an IWF emergency group call request including a MCPTT group ID to the MCPTT server. The request contains an indication of the MCPTT emergency. The IWF may indicate in its request that an MCPTT emergency alert is to be sent when initiating an MCPTT emergency group call. The request may contain an indication of an implicit floor request. +2. The MCPTT server implicitly affiliates the MCPTT ID of the LMR user to the MCPTT emergency group if the user is not already affiliated. If the IWF is configured to affiliate on behalf of all of its group members in a single affiliation step, the MC service server affiliates the IWF instead of an individual MC service ID. +3. The MCPTT server checks whether the MCPTT ID of the LMR user is authorized for initiation of MCPTT emergency calls on the indicated MCPTT group. If authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status. +4. The MCPTT server configures the priority of the underlying bearers for all MCPTT participants in the MCPTT group. All successive calls during the MCPTT group's in-progress emergency state will receive the adjusted bearer priority. +5. The MCPTT server records the emergency state of the group. Once an MCPTT emergency call has been initiated, the MCPTT group is in an in-progress emergency state until that state is cancelled. + +NOTE 3: The IWF actions for priority are out of scope of the present document. + +6. MCPTT server sends the MCPTT emergency group call request towards the MCPTT clients of each of those affiliated MCPTT group members as defined in 3GPP TS 23.379 [7]. +7. If the group has other affiliated LMR users than the calling party and the MCPTT server has received individual affiliations from those LMR users, an individual IWF emergency group call request is sent (to the IWF) for each affiliated LMR user. +8. The IWF returns IWF emergency group call response(s) to the MCPTT server. + +9. The MCPTT server sends the IWF emergency group call response to the IWF (as a response to the request received in step 1) to inform of the successful MCPTT emergency group call establishment. + +NOTE 4: How the LMR group members are called within the LMR system is out scope of the present document. + +NOTE 5: Step 9 can occur at any time following step 5, but at the latest following step 8 depending on the conditions to proceed with the call. + +10. The LMR users via the IWF and the affiliated MCPTTs have successfully established media plane for communication. The MCPTT system where the interworking group is defined is the controlling system of the group call. + +#### 10.6.2.2.2 Emergency group call setup initiated by a user in the MCPTT system on an interworking group defined in MCPTT system + +Figure 10.6.2.2.2-1 shows the procedure for an emergency group call setup initiated by a user in the MCPTT system. The figure is based upon the figure for emergency group call in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.1. This scenario assumes that the MCPTT group is an interworking group defined in the MCPTT system. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 2: The emergency interworking group call procedures reuse the information flows defined 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The MCPTT group is an interworking group defined in the MCPTT system. +2. MCPTT client 2 is affiliated to the MCPTT group. +3. The IWF is connected to and is authorized to interwork with the MCPTT system. +4. The mapping relationship of group and user identities between MCPTT system and LMR system has been configured at the IWF. +5. The initiating MCPTT client 1 has been provisioned with the MCPTT group that has been designated via provisioning as the MCPTT emergency group. + +NOTE 3: Alternatively, the client could have been provisioned for emergency behaviour on the selected group. + +![Sequence diagram illustrating Emergency group call setup, initiated by MCPTT user on an interworking group defined in the MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF. MCPTT Client 1 sends an emergency group call request to the MCPTT Server. The MCPTT Server performs internal processing (indicated by dashed boxes) and then sends an IWF emergency group call request to the IWF. The IWF responds, and the MCPTT Server then sends a response back to MCPTT Client 1.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT Server + participant IWF + + Note left of MCPTT Client 1: MCPTT Client 1 sets its MCPTT emergency state. + MCPTT Client 1->>MCPTT Server: MCPTT emergency group call request + Note right of MCPTT Server: MCPTT Server checks authorization, resolves group ID, configures bearers, records emergency state. + MCPTT Server->>IWF: IWF emergency group call request + IWF-->>MCPTT Server: IWF emergency group call response + MCPTT Server->>MCPTT Client 1: MCPTT emergency group call response + +``` + +Sequence diagram illustrating Emergency group call setup, initiated by MCPTT user on an interworking group defined in the MCPTT system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF. MCPTT Client 1 sends an emergency group call request to the MCPTT Server. The MCPTT Server performs internal processing (indicated by dashed boxes) and then sends an IWF emergency group call request to the IWF. The IWF responds, and the MCPTT Server then sends a response back to MCPTT Client 1. + +**Figure 10.6.2.2.2-1: Emergency group call setup, initiated by MCPTT user on an interworking group defined in the MCPTT system** + +1. An MCPTT user initiates an emergency group call. MCPTT client 1 sets its MCPTT emergency state. The MCPTT emergency state is retained until explicitly cancelled. +2. The MCPTT client sends an MCPTT emergency group call request to the MCPTT server. The request contains an indication of the MCPTT emergency. The MCPTT client may indicate in its request that an MCPTT emergency alert is to be sent when initiating an MCPTT emergency group call. The request may contain an indication of an implicit floor request. +3. The MCPTT server implicitly affiliates MCPTT client 1 to the emergency group if the client is not already affiliated. +4. The MCPTT server checks whether the MCPTT user of the MCPTT client 1 is authorized for initiation of MCPTT emergency calls on the indicated interworking group. If authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status. +5. The MCPTT server configures the priority of the underlying bearers for all participants in the MCPTT group. + +NOTE 4: Successive calls during the group's in-progress emergency state will all receive the adjusted bearer priority. + +6. The MCPTT server records the in-progress emergency state of the group. The MCPTT server also records the identity of the MCPTT user that initiated the MCPTT emergency group call until the MCPTT emergency is cancelled. Once an MCPTT emergency group call has been initiated, the MCPTT group is considered to be in an in-progress emergency state until that state is cancelled. +7. The MCPTT server sends an IWF emergency group call request to IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF emergency group call request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF emergency group call request is sent (to the IWF) for each affiliated LMR user. + +8. IWF responds with the IWF emergency group call response(s) to MCPTT server to inform of the successful MCPTT emergency call establishment. +- NOTE 5: How the LMR group members are called within the LMR system is out of scope of the present document. +- NOTE 6: Steps 7 to 8 can occur at any time between steps 5 and 10. +- NOTE 7: IWF actions for priority are out of scope of the present document. +9. The MCPTT server sends the MCPTT emergency group call request towards the MCPTT clients of each of those affiliated MCPTT group members as defined in 3GPP TS 23.379 [7]. + 10. The MCPTT server sends an MCPTT emergency group call response to the MCPTT client to inform of the successful MCPTT emergency call establishment. +- NOTE 8: Step 10 can occur at any time following step 8, but at the latest following step 9, depending on the conditions to proceed with the call. +11. The LMR users via the IWF and the affiliated MCPTT clients have successfully established media plane for communication. The MCPTT system where the interworking group is defined is the controlling system of the group call. + +**10.6.2.2.3 Emergency group call setup initiated by a user in the LMR system on an interworking group defined in the LMR system** + +Figure 10.6.2.2.3-1 shows the procedure for an emergency group call setup initiated by a user in the LMR system. The figure is based upon the figure for emergency group call in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.1. This scenario assumes that the MCPTT group is an interworking group defined in the LMR system. + +NOTE 1: The emergency interworking group call procedures reuse the information flows defined 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The MCPTT group is an interworking group defined in the LMR system. +2. MCPTT client 1 and MCPTT client 2 are affiliated to that group. +3. The IWF is connected to and is authorized to interwork with the MCPTT system. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +5. LMR user initiates an emergency group call. + +![Sequence diagram for emergency group call setup. Lifelines: LMR User, MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF (Interworking Function). The sequence starts with the LMR User sending a request to MCPTT Client 1. MCPTT Client 1 then sends a request to MCPTT Client 2. MCPTT Client 2 sends a response back to MCPTT Client 1. MCPTT Client 1 then sends a request to the MCPTT Server. The MCPTT Server sends a response back to MCPTT Client 1. Finally, MCPTT Client 1 sends a response to the LMR User. The IWF is shown as a separate box at the bottom, indicating its involvement in the interworking process.](a48594f1a3fecef5e047a7c3a63b1220_img.jpg) + +Sequence diagram for emergency group call setup. Lifelines: LMR User, MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF (Interworking Function). The sequence starts with the LMR User sending a request to MCPTT Client 1. MCPTT Client 1 then sends a request to MCPTT Client 2. MCPTT Client 2 sends a response back to MCPTT Client 1. MCPTT Client 1 then sends a request to the MCPTT Server. The MCPTT Server sends a response back to MCPTT Client 1. Finally, MCPTT Client 1 sends a response to the LMR User. The IWF is shown as a separate box at the bottom, indicating its involvement in the interworking process. + +**Figure 10.6.2.2.3-1: Emergency group call setup, initiated by LMR user on an interworking group defined in the LMR system** + +1. The IWF sends an IWF emergency group call request(s) to the MCPTT server. An emergency group call request is sent individually for each affiliated MCPTT user in the group. The request contains an indication of the MCPTT emergency. + +NOTE 2: IWF actions for priority are out of scope of the present document. + +2. The MCPTT server configures the priority of the underlying bearers and sends the MCPTT emergency group call request(s) as defined in 3GPP TS 23.379 [7]. + +NOTE 3: Successive calls during the MCPTT group's in-progress emergency state will all receive the adjusted bearer priority. + +3. The MCPTT clients respond with MCPTT emergency group call response to the MCPTT server. + +4. The MCPTT server sends the IWF emergency group call response(s) to the IWF to inform of the successful MCPTT emergency call establishment. + +NOTE 4: How the LMR group members are called within the LMR system is out of scope of the present document. + +5. The LMR users via the IWF and the affiliated MCPTT clients have successfully established media plane for communication. The LMR system where the interworking group is defined is the controlling system of the group call. + +#### 10.6.2.2.4 Emergency group call setup initiated by a user in the MCPTT system to an interworking group defined in the LMR system + +Figure 10.6.2.2.4-1 shows the procedure for an emergency group call initiated by a user in the MCPTT system. The figure is based upon the figure for MCPTT emergency group call in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.1. This scenario assumes that the MCPTT group is an interworking group defined in the LMR system. + +NOTE 1: The emergency interworking group call procedures reuse the information flows defined 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The MCPTT group is an interworking group defined in the LMR system. +2. MCPTT client 2 is affiliated to the MCPTT group. +3. The IWF is connected to and is authorized to interwork with the MCPTT system. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +![Sequence diagram illustrating Emergency group call setup, initiated by MCPTT user to an interworking group defined in the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF. The process involves an emergency group call request from Client 1 to the Server, which then triggers an IWF emergency group call request to the IWF. The IWF sends individual requests to MCPTT clients (e.g., Client 2). Responses are returned through the chain: Client 2 to Server, Server to IWF, and IWF to Client 1.](da85343976fdbb19f866d9ddbdad0eae_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT Server + participant IWF + Note left of MCPTT Client 1: MCPTT user initiates emergency group call + MCPTT Client 1->>MCPTT Server: MCPTT emergency group call request + MCPTT Server->>IWF: IWF emergency group call request + IWF->>MCPTT Client 2: IWF emergency group call request + MCPTT Client 2-->>MCPTT Server: MCPTT emergency group call response + MCPTT Server-->>IWF: IWF emergency group call response + IWF-->>MCPTT Client 1: MCPTT emergency group call response + +``` + +Sequence diagram illustrating Emergency group call setup, initiated by MCPTT user to an interworking group defined in the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF. The process involves an emergency group call request from Client 1 to the Server, which then triggers an IWF emergency group call request to the IWF. The IWF sends individual requests to MCPTT clients (e.g., Client 2). Responses are returned through the chain: Client 2 to Server, Server to IWF, and IWF to Client 1. + +**Figure 10.6.2.2.4-1: Emergency group call setup, initiated by MCPTT user to an interworking group defined in the LMR system** + +1. An MCPTT user initiates an emergency group call. + 2. The MCPTT client sends an MCPTT emergency group call request to the MCPTT server. The request contains an indication of the MCPTT emergency. The MCPTT client may indicate in its request that an MCPTT emergency alert is to be sent when initiating an MCPTT emergency group call. The request may contain an indication of an implicit floor request. + 3. The MCPTT server configures the priority of the underlying bearer and sends an IWF emergency group call request to the IWF. + 4. The IWF sends an individual IWF emergency group call request to the MCPTT server for each affiliated MCPTT group member, in this example to a user in MCPTT client 2. +- NOTE 2: How the LMR group members are called within the LMR system is outside the scope of the present document. +- NOTE 3: All successive calls during the MCPTT group's in-progress emergency state will receive the adjusted bearer priority. +- NOTE 4: IWF actions for priority are out of scope of the present document. +5. The MCPTT server configures the priority of the underlying bearer and sends an MCPTT emergency group call request towards the MCPTT clients as defined in 3GPP TS 23.379 [7]. + 6. The MCPTT client responds with MCPTT emergency group call response, as defined in 3GPP TS 23.379 [7]. + 7. The MCPTT server responds to the IWF emergency group call request(s), received in step 4, with IWF emergency group call response(s). + 8. The IWF sends an IWF emergency group call response to the MCPTT server, as a response to the request received in step 3, to inform of the successful MCPTT emergency group call establishment. + 9. The MCPTT server sends MCPTT emergency group call response to the initiating user in MCPTT client 1. + +NOTE 5: Step 8 can occur at any time following step 3, but at the latest following step 7. + +- 10. The LMR users (via the IWF) and the affiliated MCPTT clients have successfully established media plane for communication. The LMR system where the interworking group is defined is the controlling system of the group call. + +### 10.6.2.3 In-progress emergency group state cancel of an interworking group + +#### 10.6.2.3.1 LMR user initiated in-progress emergency group state cancel of an interworking group defined in the MCPTT system + +Figure 10.6.2.3.1-1 shows the procedure for an in-progress emergency group state cancel initiated by an LMR user. The figure is based upon the figure for MCPTT in-progress emergency group state cancel in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 2: The information flows between MCPTT client and MCPTT server are defined 3GPP TS 23.379 [7]. + +NOTE 3: The end of an MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency group state. It is explicitly cancelled by an authorized user by this procedure. + +Pre-conditions: + +- 1. The MCPTT group is in an in-progress emergency group state. +- 2. The MCPTT group is an interworking group defined in the MCPTT system. +- 3. The MCPTT client is affiliated to the MCPTT group. +- 4. The IWF is connected to and is authorized to interwork with the MCPTT system. +- 5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +- 6. An LMR user initiates in-progress emergency group state cancel of an interworking group. + +![Sequence diagram showing the interaction between an LMR User, an IWF, and an MCPTT Server for an in-progress emergency group state cancel. The LMR User sends a request to the IWF, which then sends a request to the MCPTT Server. The MCPTT Server performs internal steps (Emergency Authorization, Emergency Information, Emergency State Update) and finally sends a response back to the IWF, which then responds to the LMR User.](869856cc90b9ef75b821e64a3de8a39c_img.jpg) + +``` + +sequenceDiagram + participant LMR User + participant IWF + participant MCPTT Server + Note right of MCPTT Server: 1. EMERGENCY AUTHORIZATION + Note right of MCPTT Server: 2. EMERGENCY INFORMATION + Note right of MCPTT Server: 3. EMERGENCY STATE UPDATE + Note right of MCPTT Server: 4. UPDATE USER AND GROUP EMERGENCY STATE + LMR User->>IWF: 1. LMR in-progress emergency group state cancel request + IWF->>MCPTT Server: 2. MCPTT in-progress emergency group state cancel request + MCPTT Server-->>IWF: 3. MCPTT in-progress emergency group state cancel response + IWF-->>LMR User: 4. LMR in-progress emergency group state cancel response + +``` + +Sequence diagram showing the interaction between an LMR User, an IWF, and an MCPTT Server for an in-progress emergency group state cancel. The LMR User sends a request to the IWF, which then sends a request to the MCPTT Server. The MCPTT Server performs internal steps (Emergency Authorization, Emergency Information, Emergency State Update) and finally sends a response back to the IWF, which then responds to the LMR User. + +**Figure 10.6.2.3.1-1: LMR user initiated in-progress emergency group state cancel of an interworking group defined in the MCPTT system** + +- 1. The IWF sends an IWF in-progress emergency group state cancel request to the MCPTT server. The IWF in-progress emergency group state cancel request may carry an indication that the emergency alert of the user is also being cancelled. + +2. The MCPTT server checks that the initiator of the request is authorized to cancel the in-progress emergency group state of the group. +3. The MCPTT server cancels the in-progress emergency group state of the MCPTT group. If the emergency alert of the user is also requested to be cancelled, the MCPTT server cancels the emergency alert of the user. +4. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. +5. The MCPTT server handles the MCPTT in-progress emergency group state cancel request towards the affiliated MCPTT clients as defined in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. +6. The MCPTT server sends an IWF in-progress emergency group state cancel response to the IWF to confirm the IWF in-progress emergency group state cancel request. + +NOTE 4: Step 6 can occur at any time following step 3. + +#### 10.6.2.3.2 MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in the MCPTT system + +Figure 10.6.2.3.2-1 shows the procedure for an in-progress emergency group state cancel initiated by an MCPTT user. The figure is based upon the figure for MCPTT in-progress emergency group state cancel in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 2: The information flows between an MCPTT client and an MCPTT server are defined 3GPP TS 23.379 [7]. + +NOTE 3: The end of the MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency group state. It is explicitly cancelled by an authorized user by this procedure. + +##### Pre-conditions: + +1. MCPTT group is in an in-progress emergency group state. +2. The MCPTT group is an interworking group defined in the MCPTT system. +3. MCPTT client 2 is affiliated to that MCPTT group. +4. The IWF is connected to and is authorized to interwork with the MCPTT system. +5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +![Sequence diagram for MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in MCPTT system. Lifelines: MCPTT Client 1, MCPTT Client 2, MCPTT Server, IWF. The sequence starts with MCPTT Client 1 sending a request to MCPTT Server. MCPTT Server then sends a request to IWF. IWF returns a response to MCPTT Server. MCPTT Server then sends a response to MCPTT Client 1. MCPTT Client 1 then sends a response to MCPTT Client 2.](72d448a65347c51989171748789c7d4b_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCPTT CLIENT 1 + participant C2 as MCPTT CLIENT 2 + participant S as MCPTT SERVER + participant IWF as IWF + Note over C1: 1. Initiate in-progress +emergency group state +cancel + C1->>S: 2. MCPTT in-progress emergency group state cancel request + Note over S: 3. Check authorisation + Note over S: 4. Cancel the in-progress +emergency group state of the group + Note over S: 5. Bearer priority +readjustment + S->>IWF: 6. IWF in-progress emergency group state cancel request + IWF-->>S: 7. IWF in-progress emergency group state cancel response + rect rgb(255, 255, 255) + S->>C2: 8. MCPTT in-progress emergency group state cancel request + end + S-->>C1: 9. MCPTT in-progress emergency group state cancel response + +``` + +Sequence diagram for MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in MCPTT system. Lifelines: MCPTT Client 1, MCPTT Client 2, MCPTT Server, IWF. The sequence starts with MCPTT Client 1 sending a request to MCPTT Server. MCPTT Server then sends a request to IWF. IWF returns a response to MCPTT Server. MCPTT Server then sends a response to MCPTT Client 1. MCPTT Client 1 then sends a response to MCPTT Client 2. + +**Figure 10.6.2.3.2-1: MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in MCPTT system** + +1. The MC user of MCPTT client 1 initiates in-progress emergency group state cancel of an interworking group. + 2. The MCPTT client sends an MCPTT in-progress emergency group state cancel request to the MCPTT server. The request may carry an indication that the emergency alert of the user is also being cancelled. + 3. The MCPTT server checks that the initiator of the request is authorised to cancel the in-progress emergency group state of the group. + 4. The MCPTT server cancels the in-progress emergency group state of the MCPTT group. If the emergency alert of the user is also requested to be cancelled, the MCPTT server cancels the emergency alert of the user. + 5. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. + 6. The MCPTT server sends the IWF in-progress emergency group state cancel request to the IWF. +- NOTE 4: IWF actions for cancelling in-progress emergency group state are out of scope of the present document. +7. The IWF sends the IWF in-progress emergency group state cancel response to the MCPTT server to confirm the IWF in-progress emergency group state cancel request. + 8. The MCPTT server handles the MCPTT in-progress emergency group state cancel request towards the affiliated MCPTT clients as defined in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. + 9. The MCPTT server sends the MCPTT in-progress emergency group state cancel response to the MCPTT client 1 to confirm the MCPTT in-progress emergency group state cancel request. + +NOTE 5: Step 9 can occur at any time following step 4, depending on the conditions to proceed with the call. + +### 10.6.2.3.3 LMR user initiated in-progress emergency group state cancel of an interworking group defined in an LMR system + +Figure 10.6.2.3.3-1 shows the procedure for an in-progress emergency group state cancel initiated by an LMR user. + +NOTE 1: The information flows between MCPTT client and MCPTT server are defined 3GPP TS 23.379 [7]. + +NOTE 2: The end of an MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency group state. It is explicitly cancelled by an authorized user by this procedure. + +Pre-conditions: + +1. MCPTT group is in an in-progress emergency group state. +2. The MCPTT group is an interworking group defined in the LMR system. +3. The MCPTT client is affiliated to the MCPTT group. +4. The IWF is connected to and is authorized to interwork with the MCPTT system. +5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +6. An LMR user initiates in-progress emergency group state cancel of an interworking group. + +![Sequence diagram for LMR user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system. The diagram shows three lifelines: LMR User, MCPTT Server, and MCPTT Client. The sequence of messages is: 1. LMR User sends an 'IN-PROGRESS EMERGENCY GROUP STATE CANCEL REQUEST' to the MCPTT Server. 2. MCPTT Server sends an 'IN-PROGRESS EMERGENCY GROUP STATE CANCEL REQUEST' to the MCPTT Client. 3. MCPTT Client sends an 'IN-PROGRESS EMERGENCY GROUP STATE CANCEL RESPONSE' to the MCPTT Server. 4. MCPTT Server sends an 'IN-PROGRESS EMERGENCY GROUP STATE CANCEL RESPONSE' to the LMR User.](02d5078b2b1c8b2c1e8374d5dc17aa86_img.jpg) + +``` + +sequenceDiagram + participant LMR User + participant MCPTT Server + participant MCPTT Client + Note right of MCPTT Client: IN-PROGRESS EMERGENCY GROUP STATE CANCEL + LMR User->>MCPTT Server: IN-PROGRESS EMERGENCY GROUP STATE CANCEL REQUEST + MCPTT Server->>MCPTT Client: IN-PROGRESS EMERGENCY GROUP STATE CANCEL REQUEST + MCPTT Client-->>MCPTT Server: IN-PROGRESS EMERGENCY GROUP STATE CANCEL RESPONSE + MCPTT Server-->>LMR User: IN-PROGRESS EMERGENCY GROUP STATE CANCEL RESPONSE + +``` + +Sequence diagram for LMR user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system. The diagram shows three lifelines: LMR User, MCPTT Server, and MCPTT Client. The sequence of messages is: 1. LMR User sends an 'IN-PROGRESS EMERGENCY GROUP STATE CANCEL REQUEST' to the MCPTT Server. 2. MCPTT Server sends an 'IN-PROGRESS EMERGENCY GROUP STATE CANCEL REQUEST' to the MCPTT Client. 3. MCPTT Client sends an 'IN-PROGRESS EMERGENCY GROUP STATE CANCEL RESPONSE' to the MCPTT Server. 4. MCPTT Server sends an 'IN-PROGRESS EMERGENCY GROUP STATE CANCEL RESPONSE' to the LMR User. + +**Figure 10.6.2.3.3-1: LMR user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system** + +1. The IWF sends an IWF in-progress emergency group state cancel request to the MCPTT server. +2. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. +3. The MCPTT server handles the MCPTT in-progress emergency group state cancel request towards the affiliated MCPTT clients as defined in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. +4. The MCPTT server sends an IWF in-progress emergency group state cancel response to the IWF to confirm the IWF in-progress emergency group state cancel request. + +NOTE 3: Step 4 can occur at any time following step 1, depending on the conditions to proceed with the call. + +#### 10.6.2.3.4 MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in an LMR system + +Figure 10.6.2.3.4-1 shows the procedure for an in-progress emergency group state cancel initiated by an MCPTT user. The figure is based upon the figure for MCPTT in-progress emergency group state cancel in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. + +NOTE 1: The information flows between an MCPTT client and an MCPTT server are defined 3GPP TS 23.379 [7]. + +NOTE 2: The end of the MCPTT emergency group call does not cancel the MCPTT group's in-progress emergency group state. It is explicitly cancelled by an authorized user by this procedure. + +Pre-conditions: + +1. MCPTT group is in an in-progress emergency group state. +2. The MCPTT group is an interworking group defined in the LMR system. + +3. MCPTT client 2 is affiliated to that MCPTT group. +4. The IWF is connected to and is authorized to interwork with the MCPTT system. +5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +![Sequence diagram illustrating the MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT Server, IWF, and LMR System. MCPTT Client 1 sends a request to the MCPTT Server, which then sends a request to the IWF. The IWF sends a request to the LMR System, which returns a response to the IWF. The IWF then sends a response to the MCPTT Server, which finally sends a response to MCPTT Client 1.](f5698523df298c80a0c6b5d4ca657993_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT Server + participant IWF + participant LMR System + + Note left of MCPTT Client 1: MCPTT Client 1 initiates in-progress emergency group state cancel of an interworking group. + MCPTT Client 1->>MCPTT Server: MCPTT in-progress emergency group state cancel request + Note right of MCPTT Server: MCPTT Server sends the IWF in-progress emergency group state cancel request to the IWF. + MCPTT Server->>IWF: IWF in-progress emergency group state cancel request + Note right of IWF: IWF actions for checking authorization and cancelling in-progress emergency group state are out of scope of the present document. + Note right of IWF: The LMR system can also reject the request. + IWF->>LMR System: LMR in-progress emergency group state cancel request + Note right of LMR System: LMR System handles the request and returns a response. + LMR System-->>IWF: LMR in-progress emergency group state cancel response + Note right of IWF: IWF sends the response to the MCPTT Server to confirm the request. + IWF-->>MCPTT Server: IWF in-progress emergency group state cancel response + Note right of MCPTT Server: MCPTT Server adjusts the priority of the underlying bearer; priority treatment is no longer required. + Note right of MCPTT Server: MCPTT Server handles the request towards the affiliated MCPTT clients as defined in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. + MCPTT Server-->>MCPTT Client 1: MCPTT in-progress emergency group state cancel response + Note right of MCPTT Client 1: MCPTT Client 1 receives the response and confirms the request. + +``` + +Sequence diagram illustrating the MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system. The diagram shows interactions between MCPTT Client 1, MCPTT Client 2, MCPTT Server, IWF, and LMR System. MCPTT Client 1 sends a request to the MCPTT Server, which then sends a request to the IWF. The IWF sends a request to the LMR System, which returns a response to the IWF. The IWF then sends a response to the MCPTT Server, which finally sends a response to MCPTT Client 1. + +**Figure 10.6.2.3.4-1: MCPTT user initiated in-progress emergency group state cancel of an interworking group defined in the LMR system** + +1. The MC user of MCPTT client 1 initiates in-progress emergency group state cancel of an interworking group. +2. An MCPTT client sends an MCPTT in-progress emergency group state cancel request to the MCPTT server. The request may carry an indication that the emergency alert of the user is also being cancelled. +3. The MCPTT server sends the IWF in-progress emergency group state cancel request to the IWF. + +NOTE 3: IWF actions for checking authorization and cancelling in-progress emergency group state are out of scope of the present document. + +NOTE 4: The LMR system can also reject the request. + +4. The IWF sends the IWF in-progress emergency group state cancel response to the MCPTT server to confirm the IWF in-progress emergency group state cancel request. +5. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. +6. The MCPTT server handles the MCPTT in-progress emergency group state cancel request towards the affiliated MCPTT clients as defined in 3GPP TS 23.379 [7], subclause 10.6.2.6.1.3. +7. The MCPTT server sends the MCPTT in-progress emergency group state cancel response to the MCPTT client 1 to confirm the MCPTT in-progress emergency group state cancel request. + +NOTE 5: Step 7 can occur at any time following step 4, depending on the conditions to proceed with the call. + +## 10.6.2.4 Losing audio + +For LMR systems where a user cannot be pre-empted, the IWF identifies the audio as losing audio to the system. Subclause 10.5 is applicable to losing audio during emergency calls as well as non-emergency calls. + +### 10.6.2.5 Default emergency group + +In MCPTT, the user's profile determines whether an emergency is raised on the user's currently selected group or on a configured default emergency group. It's up to the IWF and the LMR system to which it is connected to determine what group the emergency is raised on and whether an alert is also sent when the emergency is raised. From the perspective of the MCPTT system, all emergency behavior by the IWF on behalf of its users mapped to MCPTT shall comply with behaviors defined in 3GPP TS 23.379 [7]. The implementation shall ensure that emergency related parameters of a group or private call are adhered to. For example, an MC service group must be configured in the MC service group management system for emergency alerts in order for an emergency alert to be sent on it. This can be enforced through proper configuration of both LMR and MCPTT systems or can be enforced at run time by the IWF. + +### 10.6.2.6 Emergency private call + +An emergency private call to an LMR user will have emergency priority for the portion of the call transported in the MCPTT system and the LTE EPS but will not receive priority on the LMR system in LMR systems that do not support emergency treatment for private calls. + +### 10.6.2.7 LMR systems that do not track group emergencies + +The MCPTT system tracks the emergency state of every group. In interworked LMR systems that do not track the emergency state of groups, only a UE in emergency state will be given emergency priority on the LMR system when talking. For any user talking on an emergency group, the portion of the call transported by the MCPTT system will receive emergency priority. + +## 10.6.3 Imminent peril calls + +### 10.6.3.1 General + +This subclause addresses various aspects of imminent peril call interworking. + +LMR systems do not support imminent peril. Imminent peril calls can be propagated into the LMR system by the IWF as normal group calls or emergency group calls. The decision of the LMR group call type is outside the scope of the present document. + +Where the group is defined in the MCPTT system and where the IWF has affiliated to an MCPTT group with a single affiliation on behalf of all LMR group members, only a single IWF imminent peril group call request / IWF imminent peril cancel request message is sent to the IWF at the commencement / cancel of an imminent peril group call. Where the group is defined in the MCPTT system and where the IWF has passed through individual affiliations for each group member in the LMR system, the MCPTT system shall send individual IWF imminent peril group call request / IWF imminent peril cancel request messages to the IWF for all affiliated group members in the LMR system in accordance with primary and partner MCPTT system behaviour. In both cases, the distribution of the messages to group members in the LMR system is out of scope of the present document. + +Where the group is defined in the LMR system, the IWF shall send individual IWF imminent peril group call request / IWF imminent peril cancel request messages to the MCPTT server for all affiliated MCPTT group members in accordance with primary and partner MCPTT system behaviour. + +### 10.6.3.2 Imminent peril group call initiated by an MCPTT user on an interworking group + +Figure 10.6.3.2-1 shows the procedure for an imminent peril group call initiated by a user in the MCPTT system. The figure is based upon the figure for imminent peril group call in 3GPP TS 23.379 [7], subclause 10.6.2.6.2.1. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 2: The imminent peril interworking group call procedures reuse the information flows defined in 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The initiating MCPTT client 1 has been provisioned with an MCPTT group that has been designated in the provisioning to be used for imminent peril communications + +- 2. The MCPTT group is an interworking group defined in the MCPTT system. +- 3. MCPTT client 2 is affiliated to the MCPTT group. +- 4. The IWF is connected to, and is authorized to, interwork with the MCPTT system. +- 5. At least one LMR user has affiliated to the MCPTT group. +- 6. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +NOTE 3: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for an imminent peril group call. Lifelines: MCPTT user 1, MCPTT user 2, MCPTT server, IWF, LMR user 1. The sequence starts with MCPTT user 1 sending a request to the MCPTT server. The server then interacts with the IWF, which in turn interacts with LMR user 1. The IWF returns a response to the server, which then sends a message to MCPTT user 2. Finally, the server sends a response back to MCPTT user 1.](4f3c8d71b3b182deb469aed61870e3fe_img.jpg) + +``` + +sequenceDiagram + participant MCPTT user 1 + participant MCPTT user 2 + participant MCPTT server + participant IWF + participant LMR user 1 + + Note left of MCPTT user 1: IMMINENT PERIL GROUP CALL REQUEST + MCPTT user 1->>MCPTT server: IMMINENT PERIL GROUP CALL REQUEST + Note right of MCPTT server: IMMINENT PERIL GROUP CALL PROCESSING + MCPTT server->>IWF: IMMINENT PERIL GROUP CALL REQUEST + Note right of IWF: INTERWORKING + IWF->>LMR user 1: IMMINENT PERIL GROUP CALL REQUEST + Note right of LMR user 1: LMR SYSTEM PROCESSING + LMR user 1->>IWF: IMMINENT PERIL GROUP CALL RESPONSE + Note right of IWF: INTERWORKING + IWF->>MCPTT server: IMMINENT PERIL GROUP CALL RESPONSE + Note right of MCPTT server: IMMINENT PERIL GROUP CALL PROCESSING + MCPTT server->>MCPTT user 2: IMMINENT PERIL GROUP CALL MESSAGE + Note right of MCPTT user 2: MCPTT SYSTEM PROCESSING + MCPTT server->>MCPTT user 1: IMMINENT PERIL GROUP CALL RESPONSE + Note right of MCPTT user 1: MCPTT SYSTEM PROCESSING + +``` + +Sequence diagram for an imminent peril group call. Lifelines: MCPTT user 1, MCPTT user 2, MCPTT server, IWF, LMR user 1. The sequence starts with MCPTT user 1 sending a request to the MCPTT server. The server then interacts with the IWF, which in turn interacts with LMR user 1. The IWF returns a response to the server, which then sends a message to MCPTT user 2. Finally, the server sends a response back to MCPTT user 1. + +**Figure 10.6.3.2-1: Imminent peril group call initiated by a MCPTT user to an interworking group defined in the MCPTT system** + +- 1. An MCPTT user initiates an imminent peril group call. +- 2. The MCPTT client sends an MCPTT imminent peril group call request to the MCPTT server. The request contains an indication of the in-progress imminent peril. The request may also contain an indication of an implicit floor request and may also contain the location of the calling party. +- 3. The MCPTT server implicitly affiliates MCPTT client 1 to the imminent peril group if the client is not already affiliated. +- 4. The MCPTT server checks whether the MCPTT user of MCPTT client 1 is authorized for initiation of imminent peril group calls on the indicated interworking group defined in the MCPTT system. If authorized, it resolves the MCPTT group ID to determine the members of that MCPTT group and their affiliation status. The MCPTT server also checks the privacy policy (authorisation to provide location information to other MCPTT users on a + +call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the requesting MCPTT user to decide if the user's location information may be provided to other MCPTT users on the call and the IWF. + +5. The MCPTT server configures the priority of the underlying bearers for all participants in the MCPTT group. + +NOTE 4: Successive calls during the in-progress imminent peril state will all receive the adjusted bearer priority. + +6. The MCPTT server records the imminent peril state of the group. The MCPTT server also records the identity of the MCPTT user that initiated the imminent peril group call until the in-progress imminent peril state is cancelled. Once an imminent peril group call has been initiated, the MCPTT group is considered to be in an in-progress imminent peril state until that state is cancelled. + +7. The MCPTT server sends the IWF imminent peril group call request(s) to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF imminent peril group call request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF imminent peril group call request is sent to the IWF for each affiliated LMR user. + +8. The IWF responds with the IWF imminent peril group call response(s) to MCPTT server to inform of the successful MCPTT imminent peril call establishment. + +NOTE 5: The IWF can reject the request if it does not support imminent peril group calls. IWF actions for priority are out of scope of the present document. + +NOTE 6: How the LMR group members are called within the LMR system is out of scope of the present document. + +9. The MCPTT server sends the imminent peril group call request towards the MCPTT clients of each of those affiliated MCPTT group members. The request contains an indication of the in-progress imminent peril. MCPTT users are notified of the incoming imminent peril call. The MCPTT clients acknowledge the imminent peril call request as specified in 3GPP TS 23.379 [7]. + +10. The MCPTT server sends the MCPTT imminent peril group call response to the MCPTT user 1 to inform the successful imminent peril call establishment. + +NOTE 7: Step 10 can occur at any time following step 5, and prior to step 11 depending on the conditions to proceed with the imminent peril call. + +11. The LMR users via the IWF and the affiliated MCPTT clients have successfully established the media plane for communication. The MCPTT system, where the interworking group is defined, is the controlling system of the group call. + +### 10.6.3.3 Group call initiated by a user in the LMR system on an interworking group in imminent peril state + +Figure 10.6.3.3-1 shows the procedure for a group call initiated by an LMR user (represented by the IWF) on an interworking group where the group is currently in imminent peril state within the MCPTT system. + +NOTE 1: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 2: The imminent peril interworking group call procedures reuse the information flows defined in 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 1, MCPTT client 2, and LMR users (represented by the IWF) affiliated to that MCPTT group. +2. The IWF is connected to, and is authorized to interwork with, the MCPTT system. +3. The interworking group information is available at the IWF. +4. The interworking group is currently in imminent peril state within the MCPTT system. +5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +6. LMR user initiates a group call. + +NOTE 3: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram illustrating the group call initiation by a user in the LMR system on an interworking group in imminent peril state. The diagram shows interactions between an LMR User, MCPTT Server, MCPTT Client 1, MCPTT Client 2, and an Interworking Function (IWF).](c9bcc9f954279dd8f99cdcb0f41fff4a_img.jpg) + +``` + +sequenceDiagram + participant LMR User + participant MCPTT Server + participant MCPTT Client 1 + participant MCPTT Client 2 + participant IWF + + Note right of MCPTT Server: IMMINENT PERIL STATE +IN INTERWORKING GROUP + + LMR User->>MCPTT Server: IWF group call request + MCPTT Server->>MCPTT Client 1: MCPTT imminent peril group call request + MCPTT Server->>MCPTT Client 2: MCPTT imminent peril group call request + MCPTT Client 1-->>MCPTT Server: MCPTT imminent peril group call response + MCPTT Client 2-->>MCPTT Server: MCPTT imminent peril group call response + MCPTT Server->>IWF: IWF imminent peril group call response + IWF-->>LMR User: IWF imminent peril group call response + +``` + +Sequence diagram illustrating the group call initiation by a user in the LMR system on an interworking group in imminent peril state. The diagram shows interactions between an LMR User, MCPTT Server, MCPTT Client 1, MCPTT Client 2, and an Interworking Function (IWF). + +**Figure 10.6.3.3-1: Group call initiated by a user in the LMR system on an interworking group in imminent peril state** + +1. The IWF does not track the imminent peril state of the group and sends an IWF group call request including an MCPTT group ID to the MCPTT server for call establishment. If floor control is requested by the calling LMR user, an indication of implicit floor request is included and the location information of the requestor if required. +2. The MCPTT server determines that the MCPTT group is currently in imminent peril state. +3. The MCPTT server converts the request and sends an MCPTT imminent peril group call request to all of the affiliated MCPTT clients. + - 3a. If the group has other affiliated LMR users than the calling party and the MCPTT server has received individual affiliations from those LMR users, an individual IWF imminent peril group call request is sent to the IWF for each affiliated LMR user. +4. The receiving MCPTT clients send the MCPTT imminent peril group call response to the MCPTT server to acknowledge the MCPTT imminent peril group call request. For a multicast call, these acknowledgements are not sent. + - 4a. The IWF returns IWF imminent peril group call response(s) to the MCPTT server. +5. The MCPTT server sends the IWF imminent peril group call response message to the IWF. +6. The LMR users (via the IWF) and the affiliated MCPTT clients have successfully established the media plane for communication. The MCPTT system where the interworking group is defined is the controlling system of the group call. + +The IWF, MCPTT client 1, and MCPTT client 2 continue with the MCPTT group call, which receives adjusted bearer priority within the MCPTT system due to the MCPTT group being in imminent peril state. + +NOTE 4: IWF actions for priority are out of scope of the present document. + +#### 10.6.3.4 In-progress imminent peril state cancel on an interworking group + +This procedure describes the case where an authorized MCPTT user cancels an interworking group's in-progress imminent peril state. + +Figure 10.6.3.4-1 shows the procedures for the MCPTT client cancelling an interworking group's in-progress imminent peril state. + +NOTE 1: The end of an imminent peril call does not cancel the MCPTT group's in-progress imminent peril state. It is explicitly cancelled by an authorized user. + +NOTE 2: For simplicity, a single MCPTT server is shown in place of a user home MCPTT server and a group hosting MCPTT server. + +NOTE 3: The in-progress imminent peril interworking group state cancel procedures reuse the information flows defined 3GPP TS 23.379 [7]. + +Pre-conditions: + +1. The MCPTT group is previously defined on the group management server with MCPTT client 1, MCPTT client 2, and LMR users (represented by the IWF) affiliated to that MCPTT group. +2. The IWF is connected to, and is authorized to interwork with, the MCPTT system. +3. The interworking group information is available at the IWF. +4. The interworking group is currently in in-progress imminent peril state within the MCPTT system and has prioritized bearer support. +5. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. + +NOTE 4: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +6. MCPTT client 1 previously initiated the imminent peril group call. + +![Sequence diagram showing the interaction between MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF for cancelling an imminent peril group state. The sequence starts with MCPTT Client 1 sending a 'MCPTT_IMMINENT_PERIL_CANCEL' message to the MCPTT Server. The MCPTT Server then sends three messages to the IWF: 'MCPTT_IMMINENT_PERIL_CANCEL', 'MCPTT_IMMINENT_PERIL_CANCEL_RESPONSE', and 'MCPTT_IMMINENT_PERIL_CANCEL_ACK'. The IWF then sends a 'MCPTT_IMMINENT_PERIL_CANCEL' message to MCPTT Client 2. MCPTT Client 2 sends a 'MCPTT_IMMINENT_PERIL_CANCEL' message to the MCPTT Server. Finally, the MCPTT Server sends a 'MCPTT_IMMINENT_PERIL_CANCEL' message to MCPTT Client 1.](b2a75beaa7e485cd651c2a83b30a4adc_img.jpg) + +``` + +sequenceDiagram + participant MCPTT Client 1 + participant MCPTT Client 2 + participant MCPTT Server + participant IWF + + Note left of MCPTT Client 1: MCPTT_IMMINENT_PERIL_CANCEL + MCPTT Client 1->>MCPTT Server: MCPTT_IMMINENT_PERIL_CANCEL + Note right of MCPTT Server: MCPTT_IMMINENT_PERIL_CANCEL + Note right of MCPTT Server: MCPTT_IMMINENT_PERIL_CANCEL_RESPONSE + Note right of MCPTT Server: MCPTT_IMMINENT_PERIL_CANCEL_ACK + MCPTT Server->>IWF: MCPTT_IMMINENT_PERIL_CANCEL + IWF->>MCPTT Client 2: MCPTT_IMMINENT_PERIL_CANCEL + MCPTT Client 2->>MCPTT Server: MCPTT_IMMINENT_PERIL_CANCEL + MCPTT Server->>MCPTT Client 1: MCPTT_IMMINENT_PERIL_CANCEL + +``` + +Sequence diagram showing the interaction between MCPTT Client 1, MCPTT Client 2, MCPTT Server, and IWF for cancelling an imminent peril group state. The sequence starts with MCPTT Client 1 sending a 'MCPTT\_IMMINENT\_PERIL\_CANCEL' message to the MCPTT Server. The MCPTT Server then sends three messages to the IWF: 'MCPTT\_IMMINENT\_PERIL\_CANCEL', 'MCPTT\_IMMINENT\_PERIL\_CANCEL\_RESPONSE', and 'MCPTT\_IMMINENT\_PERIL\_CANCEL\_ACK'. The IWF then sends a 'MCPTT\_IMMINENT\_PERIL\_CANCEL' message to MCPTT Client 2. MCPTT Client 2 sends a 'MCPTT\_IMMINENT\_PERIL\_CANCEL' message to the MCPTT Server. Finally, the MCPTT Server sends a 'MCPTT\_IMMINENT\_PERIL\_CANCEL' message to MCPTT Client 1. + +Figure 10.6.3.4-1: In-progress imminent peril group state cancel on an interworking group + +1. The user at the MCPTT client 1 initiates an in-progress imminent peril state cancel. +2. MCPTT client 1 sends an MCPTT in-progress imminent peril group state cancel request to the MCPTT server. +3. The MCPTT server checks whether the MCPTT user 1 at MCPTT client 1 is authorized to cancel the in-progress imminent peril group state. +4. The MCPTT server cancels/resets the in-progress imminent peril group state. +5. The MCPTT server adjusts the priority of the underlying bearer; priority treatment is no longer required. +6. The MCPTT server sends an IWF in-progress imminent peril group state cancel request(s) to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF in-progress imminent peril group state cancel request is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF in-progress imminent peril group state cancel request is sent (to the IWF) for each affiliated LMR user. +7. The IWF sends the IWF in-progress imminent peril group state cancel response(s) to the MCPTT server. + +NOTE 5: The IWF responds even if it does not support imminent peril group calls. IWF actions for priority are out of scope of the present document. + +8. The MCPTT server sends an MCPTT in-progress imminent peril group state cancel request to the MCPTT group members. + +NOTE 6: Steps 6 and 8 can occur in any order following step 5. + +9. MCPTT group members are notified of the in-progress imminent peril group state cancel. +10. MCPTT client 2 sends the MCPTT in-progress imminent peril group state cancel response to the MCPTT server to acknowledge the in-progress MCPTT in-progress imminent peril group state cancel request. For a multicast scenario, this acknowledgement is not sent. +11. The MCPTT server sends the MCPTT in-progress imminent peril group state cancel response to the MCPTT client 1 to confirm the MCPTT in-progress imminent peril group state cancel request. + +NOTE 7: Step 11 can occur at any time following step 5. + +## 10.6.4 Emergency alerts + +### 10.6.4.1 Emergency alert initiated by LMR user + +In this procedure, an LMR user is initiating an emergency alert via the IWF. Figure 10.6.4.1-1 shows the procedure for an emergency alert initiated by a user in the LMR system. This subclause is based upon subclause for MCPTT emergency alerts in 3GPP TS 23.379 [7], subclause 10.6.2.6.3.1. + +Pre-conditions: + +1. The MC service group is previously defined on the group management server with MC service client 1 and MC service client 2 affiliated to that MC service group. +2. The IWF is connected to and is authorized to interwork with the MC service system. +3. The MC service group information is available at the IWF, including information that the MC service group is an interworking group (defined in the LMR system or MC the system). +4. The mapping relationship of group and user identities between the MC service system and the LMR system has been configured at the IWF. +5. The IWF may or may not have carried out an explicit affiliation procedure with the MC service group. +6. An emergency alert is requested on the LMR system. + +NOTE 1: For all signalling messages passing through the IWF between the MC service system and the LMR system, the IWF performs identity conversion and protocol translation. + +![Sequence diagram illustrating the MC service emergency alert initiated by LMR user. Lifelines: LMR User, IWF, MC Service Server, MC Service Group 1, MC Service Group 2. The sequence starts with the LMR User sending an 'Emergency Alert Request' to the IWF. The IWF then sends an 'IWF Emergency Alert Request' to the MC Service Server. The MC Service Server responds with an 'IWF Emergency Alert Response' to the IWF. Next, the MC Service Server sends 'MC Service Emergency Alert Request' messages to both MC Service Group 1 and MC Service Group 2. Both groups respond with 'MC Service Emergency Alert Response' messages to the MC Service Server. Finally, the MC Service Server sends a dashed 'MC Service Emergency Alert' message to the IWF.](db7a693cf26f527ac6c0d4d41da20858_img.jpg) + +``` + +sequenceDiagram + participant LMR User + participant IWF + participant MC Service Server + participant MC Service Group 1 + participant MC Service Group 2 + + LMR User->>IWF: Emergency Alert Request + IWF->>MC Service Server: IWF Emergency Alert Request + MC Service Server-->>IWF: IWF Emergency Alert Response + MC Service Server->>MC Service Group 1: MC Service Emergency Alert Request + MC Service Server->>MC Service Group 2: MC Service Emergency Alert Request + MC Service Group 1-->>MC Service Server: MC Service Emergency Alert Response + MC Service Group 2-->>MC Service Server: MC Service Emergency Alert Response + MC Service Server-->>IWF: MC Service Emergency Alert + +``` + +Sequence diagram illustrating the MC service emergency alert initiated by LMR user. Lifelines: LMR User, IWF, MC Service Server, MC Service Group 1, MC Service Group 2. The sequence starts with the LMR User sending an 'Emergency Alert Request' to the IWF. The IWF then sends an 'IWF Emergency Alert Request' to the MC Service Server. The MC Service Server responds with an 'IWF Emergency Alert Response' to the IWF. Next, the MC Service Server sends 'MC Service Emergency Alert Request' messages to both MC Service Group 1 and MC Service Group 2. Both groups respond with 'MC Service Emergency Alert Response' messages to the MC Service Server. Finally, the MC Service Server sends a dashed 'MC Service Emergency Alert' message to the IWF. + +**Figure 10.6.4.1-1 MC service emergency alert initiated by LMR user** + +1. The LMR user initiates an emergency alert. + +NOTE 2: How the IWF determines the emergency condition from the LMR system is out of scope of the present document. + +2. The IWF sends an IWF emergency alert request to the designated MC service server. If the location of the LMR user is not available to the IWF, the IWF emergency alert request shall contain an indication that location is not available. +3. MC service server checks whether the MC service user ID that represents the LMR user is authorized for initiation of MC service emergency alerts for the indicated MC service group. The MC service server determines the affiliation status of the group members. +4. The MC service server sends an IWF emergency alert response to the IWF to confirm the IWF emergency alert request. + +NOTE 3: Sending the IWF emergency alert request without making a request to also start an emergency call does not put the group into an ongoing emergency condition. + +5. The MC service server sends an MC service emergency alert request towards the MC service clients of each of those affiliated MC service group members. The MC service emergency alert request message shall contain the following information: Location, MC service ID and MC service group ID (i.e., MC service user's selected MC service group or dedicated MC service emergency group, as per MC service group configuration) and the MC service user's mission critical organization name. +6. MC service users are notified of the MC service emergency. +7. The receiving MC service clients send an MC service emergency alert response to the MC service server to acknowledge the MC service emergency alert request. +8. If the group is an interworking group defined in the MC system, the MC service server implicitly affiliates the individual MC service ID of the LMR user to the emergency group if not already affiliated. If the IWF is configured to affiliate on behalf of all of its group members in a single affiliation step, the MC service server affiliates the IWF ID instead of an individual MC service ID. + +NOTE 4: Step 8 can be performed any time after step 3 but at the latest immediately after step 7. + +NOTE 5: MC service group calls made to this MC service group will be established as emergency calls if this MC service group has an ongoing emergency condition. + +NOTE 6: Sending the emergency alert does not put the other UEs in the group into an emergency state. + +### 10.6.4.2 Emergency alert initiated by MC service user + +In this procedure, an MC service user is initiating an emergency alert that is delivered to the LMR system via the IWF. Figure 10.6.4.2-1 shows the procedure for an emergency alert initiated by a user in the MC service system. This subclause is based upon subclause for MCPTT emergency alerts in 3GPP TS 23.379 [7], subclause 10.6.2.6.3.1. + +Pre-conditions: + +- 1. The MC service group is previously defined on the group management server with MC service client 1 and MC service client 2 affiliated to that MC service group. +- 2. The IWF is connected to and is authorized to interwork with the MC service system. +- 3. The MC service group information is available at the IWF, including information that the MC service group is an interworking group (defined in the LMR system or the MC system). +- 4. The mapping relationship of group and user identities between the MC system and the LMR system has been configured at the IWF. + +NOTE 1: For all signalling messages passing through the IWF between the MC system and the LMR system, the IWF performs identity conversion and protocol translation. + +![Sequence diagram showing the flow of an MC service emergency alert from a user to the LMR system via an IWF.](c71fd22661fbd344a66043940bbd84fc_img.jpg) + +``` + +sequenceDiagram + participant User as MC service user 1 + participant Client1 as MC service client 1 + participant Server as MC service server + participant IWF as IWF + participant LMR as LMR system + + Note over User: 1. Initiate emergency alert + User->>Client1: + Client1->>Server: 2. MC service emergency alert request + Note over Server: 3. Check IWF involvement & authorization + Server->>IWF: 4. MC service emergency alert request + IWF->>LMR: 5. Emergency alert + LMR-->>IWF: 6. Emergency alert response + IWF-->>Server: 7. MC service emergency alert response + Server-->>Client1: 8. MC service emergency alert response + Note over Server: 9. MC service emergency alert + Server->>Client1: + Server->>IWF: + Note over IWF: 10. LMR alert to group + +``` + +Sequence diagram showing the flow of an MC service emergency alert from a user to the LMR system via an IWF. + +**Figure 10.6.4.2-1 MC service emergency alert initiated by MC service user** + +- 1. The MC service user 1 initiates an emergency alert. +- 2. MC service client 1 sends an MC service emergency alert request to the MC service server. +- 3. The MC service server resolves the group ID, determines the affiliation status of the group members and checks whether the IWF should be informed. In this scenario, the group has affiliated members that are homed on the IWF, thus the IWF shall be involved. MC service server also checks whether the MC service user ID is authorized to initiate MC service emergency alerts for the indicated MC service group. + +4. The MC service server sends an MC service emergency alert response to the MC service client 1 to confirm the MC service emergency alert request. + +NOTE 2: Sending the emergency alert without making a request to also start an emergency call does not put the group into an ongoing emergency condition. + +5. MC service server sends an IWF emergency alert request to the IWF. If the location of the MC service client 1 is not available, the IWF emergency alert request shall contain an indication that location is not available. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF emergency alert request is sent to the IWF. If the IWF has sent individual affiliations for each of its LMR users, the MC service server sends an IWF emergency alert request via the IWF to each affiliated LMR group member. +6. The IWF sends an IWF service emergency alert response to the MC service server to confirm the IWF emergency alert request(s). +7. The MC service server sends an MC service emergency alert request towards the MC service clients of each of those affiliated MC service group members. The MC service emergency alert request message shall contain the following information: Location, MC service ID and MC service group ID (i.e., MC service user's selected MC service group or dedicated MC service emergency group, as per MC service group configuration) and the MC service user's mission critical organization name. +8. MC service users are notified of the MC service emergency. +9. The receiving MC service clients send an MC service emergency alert response to the MC service server to acknowledge the MC service emergency alert. +10. The MC service server implicitly affiliates the MC service client 1 to the emergency group if it is not already affiliated. + +NOTE 3: Step 10 can be performed any time after step 3. Steps 5 and 7 can be performed in which ever order. + +NOTE 4: MC service group calls made to this MC service group will be established as emergency calls if the MC service group has an ongoing emergency condition. + +NOTE 5: Sending an emergency alert does not put the other UEs in the group into an emergency state. + +## 10.6.5 Emergency alert cancellation + +### 10.6.5.1 Emergency alert cancellation of an LMR user + +In this procedure, an LMR user is cancelling the emergency alert. Figure 10.6.5.1-1 shows the procedure for emergency alert cancellation of a user in the LMR system. This subclause is based upon subclause for MCPTT emergency alert cancel in 3GPP TS 23.379 [7], subclause 10.6.2.6.3.2. + +Pre-conditions: + +1. The MC service group information is available at the IWF, including information that the MC service group is an interworking group (defined in the LMR system or the MC system). +2. The LMR user had previously successfully initiated an emergency alert via the IWF. +3. The MC service client 1 and MC service client 2 are affiliated to the MC service group. +4. The MC service server may have carried out an explicit or implicit affiliation procedure of the LMR user to the MC service group. +5. The mapping relationship of group and user identities between the MC service system and the LMR system has been configured at the IWF. +6. The LMR user initiates an emergency alert cancel. + +NOTE 1: For all the signalling messages passing through the IWF between the MC service system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for MC service emergency alert cancellation of an LMR user. Lifelines: LMR User, MC Service Server, MC Service Client 1, MC Service Client 2. The sequence shows the LMR User sending a request to the MC Service Server, which then sends responses to the MC Service Clients, who in turn send acknowledgements back to the MC Service Server, which finally sends a response back to the LMR User.](fa1eb5ed4fcf8f8d184ead2a8a5a08e6_img.jpg) + +``` + +sequenceDiagram + participant LMR User + participant MC Service Server + participant MC Service Client 1 + participant MC Service Client 2 + Note right of MC Service Client 1: MC Service Group Member + Note right of MC Service Client 2: MC Service Group Member + LMR User->>MC Service Server: IWF emergency alert cancel request + MC Service Server-->>LMR User: IWF emergency alert cancel response + MC Service Server->>MC Service Client 1: MC service emergency alert cancel request + MC Service Server->>MC Service Client 2: MC service emergency alert cancel request + MC Service Client 1-->>MC Service Server: MC service emergency alert cancel response + MC Service Client 2-->>MC Service Server: MC service emergency alert cancel response + +``` + +Sequence diagram for MC service emergency alert cancellation of an LMR user. Lifelines: LMR User, MC Service Server, MC Service Client 1, MC Service Client 2. The sequence shows the LMR User sending a request to the MC Service Server, which then sends responses to the MC Service Clients, who in turn send acknowledgements back to the MC Service Server, which finally sends a response back to the LMR User. + +**Figure 10.6.5.1-1 MC service emergency alert cancellation of an LMR user** + +1. The IWF sends an IWF emergency alert cancel request to the MC service group to which the IWF had previously successfully sent the IWF emergency alert request on behalf of the LMR user. + +NOTE 2: The IWF emergency alert cancel request may carry an indication to also request that the in-progress emergency state on the group is to be cancelled. + +2. The MC service server sends the IWF emergency alert cancel response to the IWF to confirm the IWF emergency alert cancellation. +3. The MC service server sends an MC service emergency alert cancel request to the MC service clients of the affiliated MC service group members. +4. MC service users are notified of the MC service emergency alert cancellation of the LMR user. +5. The receiving MC service clients send the MC service emergency alert cancel response to the MC service server to acknowledge the MC service emergency alert cancel request. For a multicast call scenario, these acknowledgements are not sent. + +NOTE 3: Steps 2 and 3 can be performed in whichever order. + +## 10.6.5.2 Emergency alert cancellation of an MC service user + +In this procedure, an MC service user is cancelling the emergency alert. Figure 10.6.5.2-1 shows the procedure for emergency alert cancellation from a user in the MC service system. This subclause is based upon subclause for MCPTT emergency alerts in 3GPP TS 23.379 [7], subclause 10.6.2.6.3.2. + +Pre-conditions: + +1. The MC service group information is available at the IWF, including information that the MC service group is an interworking group (defined in the LMR system or the MC system). +2. The MC service client 1 had previously successfully initiated an MC service emergency alert request. +3. The MC service client 1 is still in the emergency state. +4. The MC service client 2 is affiliated to the MC service group. + +5. The MC service server may have carried out an explicit or implicit affiliation procedure of the LMR user with the MC service group. +6. The mapping relationship of group and user identities between the MC service system and the LMR system has been configured at the IWF. + +NOTE 1: For all the signalling messages passing through the IWF between the MC service system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram illustrating MC service emergency alert cancellation of an MC service user. The diagram shows interactions between MC service client 1, MC service server, IWF, and MC service client 2. The process involves an emergency alert cancel request from client 1, a response from the server, an IWF emergency alert cancel request from the server to the IWF, an IWF emergency alert cancel response from the IWF to the server, and finally an MC service emergency alert cancel request from the server to client 2.](6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg) + +``` + +sequenceDiagram + participant MCSC1 as MC service client 1 + participant MSS as MC service server + participant IWF as IWF + participant MCSC2 as MC service client 2 + + Note left of MCSC1: EMERGENCY ALERT REQUEST + MCSC1->>MSS: MC service emergency alert cancel request + Note right of MSS: EMERGENCY ALERT CANCEL REQUEST + MSS->>IWF: IWF emergency alert cancel request(s) + Note right of IWF: EMERGENCY ALERT CANCEL RESPONSE + IWF->>MSS: IWF emergency alert cancel response(s) + Note right of MSS: EMERGENCY ALERT CANCEL RESPONSE + MSS->>MCSC1: MC service emergency alert cancel response + Note left of MCSC1: EMERGENCY ALERT CANCEL RESPONSE + Note right of MSS: EMERGENCY ALERT REQUEST + MSS->>MCSC2: MC service emergency alert cancel request + +``` + +Sequence diagram illustrating MC service emergency alert cancellation of an MC service user. The diagram shows interactions between MC service client 1, MC service server, IWF, and MC service client 2. The process involves an emergency alert cancel request from client 1, a response from the server, an IWF emergency alert cancel request from the server to the IWF, an IWF emergency alert cancel response from the IWF to the server, and finally an MC service emergency alert cancel request from the server to client 2. + +**Figure 10.6.5.2-1 MC service emergency alert cancellation of an MC service user** + +1. The user at the MC service client 1 initiates an emergency alert cancel. + +NOTE 2: The MC service emergency alert cancel request may carry an indication that the in-progress emergency state on the group is to be cancelled. + +2. MC service client 1 requests the MC service server to send an MC service emergency alert cancel to the MC service group to which MC service client 1 had previously sent the emergency alert request. The MC service server resolves the group ID, determines the affiliation status of the group members and checks whether the IWF should be informed. In this scenario, the group has affiliated members that are homed on the IWF, thus the IWF shall be involved. +3. The MC service server sends the MC service emergency alert cancel response to the MC service client 1 to confirm the MC service emergency alert cancel request. MC service client 1 resets its emergency state. +4. The MC service server sends an IWF emergency alert cancel request(s) to the IWF. If the IWF has affiliated to this group on behalf of the group's LMR users, only one IWF emergency alert cancel request message is sent to the IWF. If the MCPTT server has received individual affiliations from the group's LMR users, an individual IWF emergency alert cancel request message is sent to the IWF for each affiliated LMR user. +5. The IWF sends an IWF emergency alert cancel response(s) to the MC service server to acknowledge the IWF emergency alert cancel request(s). +6. The MC service server sends an MC service emergency alert cancel request towards the MC service clients of the affiliated MC service group members. +7. MC service users are notified of the MC service emergency alert cancellation of MC service client 1. + +8. The receiving MC service clients send the MC service emergency alert cancel response to the MC service server to acknowledge the MC service emergency alert cancel request. For a multicast call scenario, these acknowledgements are not sent. + +NOTE 3: Steps 3 and 4 can be performed in which ever order. + +## 10.7 Codec + +### 10.7.1 Information flows for codec + +#### 10.7.1.1 IWF codec reconciliation request + +Table 10.7.1.1-1 describes the information flow IWF codec reconciliation request from the IWF to the MCPTT server. + +**Table 10.7.1.1-1: IWF codec reconciliation request** + +| Information element | Status | Description | +|---------------------|--------|-----------------------------------------------------------| +| MCPTT group ID | M | The MCPTT group ID for which a codec change is requested. | +| Codec type | M | Type of the requested codec | + +#### 10.7.1.2 IWF codec reconciliation response + +Table 10.7.1.2-1 describes the information flow IWF codec reconciliation response from the MCPTT server to the IWF. + +**Table 10.7.1.2-1: IWF codec reconciliation response** + +| Information element | Status | Description | +|---------------------|--------|--------------------------------------------------------------------| +| MCPTT group ID | M | The MCPTT group ID for which a codec change was requested. | +| Result | M | Result indicates success or failure of the requested codec change. | + +## 10.7.2 IWF transcoding + +The IWF can be used to transcode voice packets in transit between the LMR and MCPTT systems. In this scenario, the MCPTT system can operate its own vocoder type and the LMR system can operate its own vocoder type. The type of vocoder used on the LMR side is outside the scope of the present document. + +When operating in this mode, the IWF converts voice media formats between the two sides. Vocoder negotiation is according to procedures in the present document. + +## 10.7.3 Codec negotiation by the LMR system + +### 10.7.3.1 Description + +An MCPTT group may be configured to use an LMR speech codec, such that speech can be carried end to end between all group members in both LMR and MCPTT system without transcoding. + +An LMR system can support more than one speech codec; for example P25 supports both a full rate and a half rate speech codec. Circumstances within the LMR system might require that the codec in use within a group is changed according to the needs of the LMR system. + +Figure 10.7.3.1-1 below illustrates a procedure which allows the LMR system to change the speech codec within an MCPTT group that is connected to the LMR system via the IWF. + +Pre-conditions: + +1. Group members have affiliated to the MCPTT group in both the LMR system and in the MCPTT system +2. A permitted LMR codec has been negotiated for use by MCPTT group members +3. MCPTT group members support the requested second LMR speech codec + +NOTE 1: The exception condition created if the IWF does not support transcoding and the MCPTT client does not support the requested LMR codec is outside the scope of the present document. + +4. The LMR system requires a change to an alternative speech codec. + +![Sequence diagram illustrating the codec reconciliation procedure. Lifelines: LMR System, MCPTT Client, MCPTT Server, and IWF. The sequence starts with the IWF sending a 'Codec Reconciliation Request' to the MCPTT Server. The MCPTT Server then sends a 'Codec Reconciliation Request' to the MCPTT Client. The MCPTT Client responds with a 'Codec Reconciliation Response' to the MCPTT Server. Finally, the MCPTT Server sends a 'Codec Reconciliation Response' back to the IWF.](c2e2b17d61aecbead88a6278e4ba3605_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT_Server as MCPTT Server + participant MCPTT_Client as MCPTT Client + participant LMR_System as LMR System + + Note right of LMR_System: LMR system requires a change to an alternative speech codec + IWF->>MCPTT_Server: Codec Reconciliation Request + MCPTT_Server->>MCPTT_Client: Codec Reconciliation Request + MCPTT_Client-->>MCPTT_Server: Codec Reconciliation Response + MCPTT_Server-->>IWF: Codec Reconciliation Response + +``` + +Sequence diagram illustrating the codec reconciliation procedure. Lifelines: LMR System, MCPTT Client, MCPTT Server, and IWF. The sequence starts with the IWF sending a 'Codec Reconciliation Request' to the MCPTT Server. The MCPTT Server then sends a 'Codec Reconciliation Request' to the MCPTT Client. The MCPTT Client responds with a 'Codec Reconciliation Response' to the MCPTT Server. Finally, the MCPTT Server sends a 'Codec Reconciliation Response' back to the IWF. + +**Figure 10.7.3.1-1: Codec reconciliation procedure** + +1. The IWF sends a codec reconciliation request to the MCPTT server on behalf of the LMR system. +2. The MCPTT server checks that the requested codec is permitted for the MCPTT group. +3. The MCPTT server sends a codec reconciliation request to all of the affiliated MCPTT client(s) to negotiate the use of the speech codec requested by the LMR system. +4. The MCPTT client replies with a codec reconciliation response to the MCPTT server, indicating acceptance of the new speech codec. +5. The MCPTT server sends a codec reconciliation response to the IWF. +6. Further transmissions in the MCPTT group use the new codec in the media plane. + +NOTE 2: The time at which the new codec is first used by a transmitting party is outside the scope of the present document. + +## 10.8 MCData short data service + +### 10.8.1 General + +The present document specifies short data service (SDS) interworking between LMR users and MCData clients using one-to-one standalone SDS messages and group standalone SDS messages. The IWF behaves as a peer MCData server to other MCData servers. + +When an LMR user attempts to send an LMR message to the MCData service, the IWF converts the LMR message into a request to send an MCData SDS. The method by which the IWF converts the LMR message into a request to send an MCData SDS is outside the scope of the present document. + +When the IWF receives a request to send an MCData SDS to an LMR user or a group of LMR users, the IWF converts the request into one or more LMR messages. The method by which the IWF converts the MCData SDS request into an LMR messages is outside the scope of the present document. + +## 10.8.2 Information flows for the short data service + +### 10.8.2.1 General + +The following subclauses define information flows for MCData SDS on the IWF-2 interface. MCData SDS related information flows on reference points other than IWF-2 are defined in 3GPP TS 23.282 [6], subclause 7.4.2.1. In each case, the LMR users behind the IWF are represented by MCData IDs or a MCData group ID as appropriate and so the MCData server shall be capable of routing messages towards identities located behind the IWF. + +### 10.8.2.2 IWF MCData standalone data request + +Table 10.8.2.2-1 describes the information flow for the MCData standalone data request (in 3GPP TS 23.282 [6] subclauses 7.4.2.2.2 and 7.4.2.3.2) sent from the MCData server to the IWF and from the IWF to a MCData server. + +**Table 10.8.2.2-1: IWF MCData standalone data request** + +| Information element | Status | Description | +|------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier (see NOTE 1) | M | Identifies the conversation | +| Transaction Identifier (see NOTE 1) | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier (see NOTE 2) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE 1: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element. | | | +| NOTE 2: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | | + +### 10.8.2.3 IWF MCData data disposition notification + +Table 10.8.2.3-1 describes the information flow for the MCData data disposition notification sent from the IWF to the MCData server and from the MCData server to the IWF. + +**Table 10.8.2.3-1: IWF MCData data disposition notification** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| MCData ID | M | The identity of the MCData user sending notification | +| Conversation Identifier (see NOTE) | M | Identifies the conversation | +| Disposition association | M | Identity of the original MCData transaction | +| Disposition | M | Disposition which is delivered, read, delivered and read, or disposition prevented by system | +| NOTE: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element. | | | + +### 10.8.2.4 IWF MCData group standalone data request (IWF – MCData server) + +Table 10.8.2.4-1 describes the information flow for the MCData group standalone data request (in 3GPP TS 23.282 [6] subclause 7.4.2.5.2) sent from the IWF to the MCData server when the IWF is acting as the initiating MCData client. + +**Table 10.8.2.4-1: IWF MCData group standalone data request (IWF – MCData server)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier (see NOTE 1) | M | Identifies the conversation | +| Transaction Identifier (see NOTE 1) | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier (see NOTE 2) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE 1: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element. | | | +| NOTE 2: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +### 10.8.2.5 IWF MCData group standalone data request (MCData server - IWF) + +Table 10.8.2.5-1 describes the information flow for the MCData group standalone data request (in 3GPP TS 23.282 [6] subclause 7.4.2.5.2) sent from the MCData server to the IWF when the IWF is acting as proxy for MCData clients. + +**Table 10.8.2.5-1: IWF MCData group standalone data request (MCData server – IWF)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the payload is for application consumption or MCData client consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| Payload | M | SDS content | +| NOTE: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | | + +### 10.8.2.6 IWF MCData data disposition notification(s) (MCData server to IWF) + +Table 10.8.2.6-1 describes the information flow for the MCData data disposition notification(s) sent from the MCData server to the IWF when the IWF is acting as proxy for MCData client(s). + +**Table 10.8.2.6-1: IWF MCData data disposition notification(s) (MCData server – IWF)** + +| Information element | Status | Description | +|-------------------------|--------|----------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user towards which the notification is sent | +| MCData ID | M | The identity of the MCData user sending notification | +| Conversation Identifier | M | Identifies the conversation | +| Disposition association | M | Identity of the original MCData transaction | +| Disposition | M | Disposition which is delivered, read, delivered and read, or disposition prevented by system | + +### 10.8.2.7 IWF MCData group standalone data request (IWF – MCData server) + +Table 10.8.2.7-1 describes the information flow for the MCData group standalone data request (in 3GPP TS 23.282 [6] subclause 7.4.2.6.2) sent from the IWF representing the MCData client to the MCData server. + +**Table 10.8.2.7-1: IWF MCData group standalone data request (IWF – MCData server)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| Conversation Identifier (see NOTE 1) | M | Identifies the conversation | +| Transaction Identifier (see NOTE 1) | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Standalone transaction | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Application identifier (see NOTE 2) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| NOTE 1: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element. | | | +| NOTE 2: The application identifier shall be included only if the payload destination type indicates that the SDS message is for application consumption. | | | + +### 10.8.2.8 IWF MCData group standalone data request (MCData server – IWF) + +Table 10.8.2.8-1 describes the information flow for the MCData group standalone data request (in 3GPP TS 23.282 [6] subclause 7.4.2.6.2) sent from the MCData server to the IWF acting as proxy for MCData client(s). + +**Table 10.8.2.8-1: IWF MCData group standalone data request (MCData server – IWF)** + +| Information element | Status | Description | +|----------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------------------------------------| +| MCData ID | M | The identity of the MCData user sending data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user towards which the data is sent | +| Conversation Identifier | M | Identifies the conversation | +| Transaction Identifier | M | Identifies the MCData transaction | +| Reply Identifier | O | Identifies the original MCData transaction to which the current transaction is a reply to | +| Transaction type | M | Standalone transaction | +| Disposition Type | O | Indicates the disposition type expected from the receiver (i.e., delivered or read or both) | +| Payload Destination Type | M | Indicates whether the SDS payload is for application consumption or MCData user consumption | +| Application identifier (see NOTE) | O | Identifies the application for which the payload is intended (e.g. text string, port address, URI) | +| SDP offer | M | Media parameters offered | +| NOTE: The application identifier shall be included only if the payload destination type indicates that the payload is for application consumption. | | | + +### 10.8.2.9 IWF MCData group standalone data response + +Table 10.8.2.9-1 describes the information flow for the MCData group standalone data response (in 3GPP TS 23.282 [6] subclause 7.4.2.6.2) sent from the IWF to the MCData server and from the MCData server to the IWF acting as proxy for other MCData clients. + +**Table 10.8.2.9-1: IWF MCData group standalone data response** + +| Information element | Status | Description | +|-----------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------| +| MCData ID | M | The identity of the MCData user receiving data | +| MCData group ID | M | The MCData group ID to which the data is to be sent | +| MCData ID | M | The identity of the MCData user sent data | +| Conversation Identifier (see NOTE) | M | Identifies the conversation | +| SDP answer | M | Media parameters selected | +| NOTE: A reserved value of the Information Element shall be defined which indicates that the sender does not support this Information Element. | | | + +## 10.8.3 Behaviour at the MCData Client + +The MCData client interfaces with the MCData server as specified in 3GPP TS 23.282 [6]. + +## 10.8.4 Behaviour at the IWF + +The IWF interfaces with the MCData server via the reference points defined in subclause 7.4 of the present document. + +## 10.8.5 Behaviour at the MCData server + +The MCData server behaves as specified in 3GPP TS 23.282 [6], with the addition that the MCData server shall route SDS messages addressed to MCData IDs and MCData group IDs that lie behind IWFs to the appropriate IWFs. + +## 10.8.6 MCData user one-to-one SDS request to an LMR user + +### 10.8.6.1 Signalling control plane + +The procedure for an MCData user requesting to send a signalling control plane SDS to a single LMR user is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.2 for the one-to-one standalone short data service using the signalling control plane, with the exception that MCData client 2 is located behind the IWF. The SDS is addressed to the MCData ID that has been allocated to the LMR user. The IWF behaves as a peer MCData server. + +### 10.8.6.2 Media plane + +The procedure for an MCData user requesting to send a media plane SDS to a single LMR user is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.3 for the one-to-one standalone short data service using the media plane, with the exception that MCData client 2 is located behind the IWF. The SDS is addressed to the MCData ID that has been allocated to the LMR user. The IWF behaves as a peer MCData server. + +## 10.8.7 LMR user one-to-one SDS request to an MCData user + +### 10.8.7.1 Signalling control plane + +The procedure for an IWF requesting, on behalf of an LMR user, to send a signalling control plane SDS to a single MCData user is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.2 for the one-to-one standalone short data service using the signalling control plane, with the exception that MCData client 1 is located behind the IWF. The source address of the SDS is the MCData ID that has been allocated to the LMR user. The IWF behaves as a peer MCData server. + +### 10.8.7.2 Media plane + +The procedure for an IWF requesting, on behalf of an LMR user, to send a media plane SDS to a single MCData user is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.3 for the one-to-one standalone short data service using the media plane, with the exception that MCData client 1 is located behind the IWF. The source address of the SDS is the MCData ID that has been allocated to the LMR user. The IWF behaves as a peer MCData server. + +## 10.8.8 MCData user group SDS request to an MCData group including LMR users + +### 10.8.8.1 Signalling control plane + +The procedure for an MCData user requesting to send a signalling control plane SDS to an MCData group that includes one or more LMR users is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.5 for the group standalone short data service using the signalling control plane. In the case of implementation involving an IWF the difference is that one or more of the MCData clients 2 to n are located behind IWFs that have affiliated to the MCData group (see subclause 10.1.2 of the present document). The SDS is addressed to the MCData group ID. The IWF behaves as a peer MCData server. The IWF can also respond on behalf of a MCData client located behind the IWF to a disposition request with a disposition of 'disposition prevented by system' for forwarding to the originating MCData client. + +### 10.8.8.2 Media plane + +The procedure for an MCData user requesting to send a media plane SDS to an MCData group that includes one or more LMR users is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.6 for the group standalone short data service using the media plane. In the case of implementation involving an IWF the difference is that one or more of the MCData clients 2 to n can be located behind IWFs that have affiliated to the MCData group (see subclause 10.1.2 of the present document). The SDS is addressed to the MCData group ID. The IWF behaves as a peer MCData server. The IWF can also respond on behalf of a MCData client located behind the IWF to a disposition request with a disposition of 'disposition prevented by system' for forwarding to the originating MCData client. + +## 10.8.9 LMR user group SDS request to an MCData group + +### 10.8.9.1 Signalling control plane + +The procedure for an IWF requesting, on behalf of an LMR user, to send a signalling control plane SDS to an MCData group is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.5 for the group standalone short data service using the signalling control plane, with the exception that MCData client 1 is located behind an IWF and one or more of the MCData clients 2 to n can be behind IWFs that have affiliated to the MCData group (see subclause 10.1.2 of the present document). The SDS is addressed to the MCData group ID. The IWF behaves as a peer MCData server to other MCData servers. + +### 10.8.9.2 Media plane + +The procedure for an IWF requesting, on behalf of an LMR user, to send a media plane SDS to an MCData group is as specified in 3GPP TS 23.282 [6] subclause 7.4.2.6 for the group standalone short data service using the media plane, with the exception that MCData client 1 is located behind an IWF and one or more of the MCData clients 2 to n can be behind IWFs that have affiliated to the MCData group (see subclause 10.1.2 of the present document). The SDS is addressed to the MCData group ID. The IWF behaves as a peer MCData server to other MCData servers. + +## 10.9 IWF as a security gateway + +### 10.9.1 Support for transcoding with encrypted speech + +In some cases when encryption of voice media is required in the MC system, the MCPTT user(s) and the LMR user(s) can use different codecs. In these cases, transcoding is needed and before transcoding can occur, encryption applied to the voice media by the MC system needs to be removed. After transcoding, LMR encryption can be applied (out-of-scope of the present document). An IWF can perform these functions and be deployed as a security gateway between the MCPTT system and the LMR system. When the IWF removes the encryption applied by the MC system, the IWF must perform key management procedures defined in 3GPP TS 33.180 [8] to obtain the key material for the group. + +## 10.10 Simultaneous interworked calls (on-network) + +### 10.10.1 General + +An IWF representing an LMR user may support simultaneous interworked calls for the same LMR user. The LMR user can become involved in simultaneous interworked calls when the IWF invites, joins or accepts more than one interworked call on behalf of the LMR user, or when the IWF affiliates the LMR user to multiple groups. This subclause is based on the subclause for simultaneous session for MCPTT calls in 3GPP TS 23.379 [7], subclause 10.8. + +NOTE: An LMR user affiliating to multiple interworked groups with active calls via the IWF can result in the LMR user being invited simultaneously to multiple interworked calls. + +How the IWF accomodates simultaneous interworked calls to a single LMR user is outside the scope of the present document. + +## 10.11 Location + +### 10.11.1 Location of current talker + +3GPP TS 23.379 [7], subclause 10.6.2.7 describes a high-level procedure to provide the location of the current talker to all the receiving MCPTT users. + +### 10.11.2 Location of current talker (MCPTT server to IWF) + +Figure 10.11.2-1 shows the high-level procedure to for MCPTT service to provide the location information about the current talking user to all the receiving MCPTT users and the IWF. + +Pre-conditions: + +1. There is on-going group call involving MCPTT client 1 and MCPTT client 2 and the IWF. +2. MCPTT client 1 is the current talking user. +3. MCPTT server has obtained the location information of MCPTT client 1. + +![Sequence diagram showing the interaction between MCPTT client 1, MCPTT server, MCPTT client 2, and the IWF. It illustrates the process of MCPTT client 1 acquiring the floor, the server checking privacy policies, and then providing location information to other participants.](77b4b155b2bd3a525bbcdb4c10e149df_img.jpg) + +``` + +sequenceDiagram + participant C1 as MCPTT client 1 + participant S as MCPTT server + participant C2 as MCPTT client 2 + participant IWF as IWF + + Note over C1, IWF: 1. MCPTT client 1 acquires the floor for media + Note over S: 2. Check user's privacy policy +for sharing location information + Note over S, IWF: 3. Provide the location information to other current talkers + +``` + +Sequence diagram showing the interaction between MCPTT client 1, MCPTT server, MCPTT client 2, and the IWF. It illustrates the process of MCPTT client 1 acquiring the floor, the server checking privacy policies, and then providing location information to other participants. + +Figure 10.11.2-1: Providing location information of the current talker + +1. MCPTT client 1 gets the floor to transmit voice media. +2. The MCPTT server checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the current talking MCPTT user to decide if the location information of MCPTT client 1 can be provided to other MCPTT users on the call. +3. If the privacy policy permits, the MCPTT server provides the location information of MCPTT client 1 to MCPTT client 2 and the IWF. The procedures for this are described in 3GPP TS 23.280 [5] subclause 10.9.3.6. Optionally, the location information may be provided in the floor taken message sent to MCPTT client 2 and the IWF according to 3GPP TS 23.379 [7] subclause 10.9.1.3.1, if the privacy policy permits. + +### 10.11.3 Location of current talker (IWF to MCPTT server) + +Figure 10.11.3-1 shows the high-level procedure to for the IWF to provide the location information about the current LMR talking user to all the receiving MCPTT users. + +Pre-conditions: + +1. There is on-going group call involving MCPTT client 1 and MCPTT client 2 and the IWF. +2. An LMR user is the current talking user through the IWF. + +NOTE: How the MCPTT server acquires the location of the LMR user is outside the scope of the present document. + +![Sequence diagram showing the interaction between MCPTT clients, the MCPTT server, and the IWF for providing location information. The diagram includes lifelines for MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. A 'Floor taken' message is sent from the IWF to the MCPTT server, which then triggers a 'Floor taken response' from the MCPTT server to the IWF. The IWF then sends a 'Floor taken' message to MCPTT client 1, which in turn sends a 'Floor taken response' back to the IWF. Finally, the IWF sends a 'Floor taken' message to MCPTT client 2.](2bcc7de24074ca97717d10c8c4bfe3ba_img.jpg) + +Sequence diagram showing the interaction between MCPTT clients, the MCPTT server, and the IWF for providing location information. The diagram includes lifelines for MCPTT client 1, MCPTT client 2, MCPTT server, and IWF. A 'Floor taken' message is sent from the IWF to the MCPTT server, which then triggers a 'Floor taken response' from the MCPTT server to the IWF. The IWF then sends a 'Floor taken' message to MCPTT client 1, which in turn sends a 'Floor taken response' back to the IWF. Finally, the IWF sends a 'Floor taken' message to MCPTT client 2. + +**Figure 10.11.3-1: Providing location information of the current talker** + +1. The IWF gets the floor to transmit voice media. +2. The MCPTT server checks the privacy policy (authorisation to provide location information to other MCPTT users on a call when talking, as defined in 3GPP TS 23.379 [7] Annex A.3) of the current talking IWF user to decide if the location information of the user on the IWF can be provided to other MCPTT users on the call. +3. The MCPTT server provides the location information of the IWF user to MCPTT client 1 and MCPTT client 2. The procedures for this are described in 3GPP TS 23.280 [5] subclause 10.9.3.6. Optionally, the location information may be provided in the floor taken message sent to MCPTT client 2 and the IWF according to 3GPP TS 23.379 [7] subclause 10.9.1.3.1. + +## 10.12 LMR security transport + +### 10.12.1 Information flows for LMR security transport + +#### 10.12.1.1 Non-3GPP security message request + +Table 10.12.1.1-1 describes the information flow non-3GPP security message request from the MC service server to the IWF, from the IWF to the MC service server, from the MC service server to the MC service client and from the MC service client to the MC service server. + +**Table 10.12.1.1-1: Non-3GPP security message request** + +| Information Element | Status | Description | +|---------------------------------------|--------|--------------------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user | +| URI of LMR security functional entity | M | URI of LMR key management functional entity user profile parameter defined in 3GPP TS 23.379 [7] | +| LMR type | O | The LMR technology, e.g. TETRA, P25. Required when sent toward the MC service client. | +| Payload | M | Opaque payload. Contents and format are out of 3GPP scope. | + +## 10.12.1.2 Non-3GPP security message response + +Table 10.12.1.2-1 describes the information flow non-3GPP security message response from the MC service server to the IWF, from the IWF to the MC service server, from the MC service server to the MC service client and from the MC service client to the MC service server. + +**Table 10.12.1.2-1: Non-3GPP security message response** + +| Information Element | Status | Description | +|---------------------------------------|--------|--------------------------------------------------------------------------------------------------| +| MC service ID | M | The identity of the MC service user | +| URI of LMR security functional entity | M | URI of LMR key management functional entity user profile parameter defined in 3GPP TS 23.379 [7] | + +## 10.12.2 LMR key management messages + +### 10.12.2.1 General + +This subclause defines end to end messaging to convey the non-3GPP, LMR security information opaquely (message contents are out of 3GPP's scope) across the MC system, between the IWF and the LMR aware MC service client. The end to end messages are service independent, any MC service may support them. + +### 10.12.2.2 MC service client initiated + +Figure 10.12.2.2-1 describes the case where an MC service client sends LMR security information to the IWF. + +Pre-conditions: + +1. The MC service client is registered and the user is authenticated and authorized to use the MC service server. + +![Sequence diagram showing non-3GPP security messaging from MC service client to IWF via MC service server.](20180217c11e0af84b844796a9c68c6a_img.jpg) + +``` + +sequenceDiagram + participant MC Service Client + participant MC Service Server + participant IWF + Note left of MC Service Client: MC Service Client + MC Service Client->>MC Service Server: Request LMR Security Information + MC Service Server->>IWF: Forward LMR Security Information + IWF-->>MC Service Server: Response + MC Service Server-->>MC Service Client: Response + +``` + +Sequence diagram showing non-3GPP security messaging from MC service client to IWF via MC service server. + +**Figure 10.12.2.2-1: Non-3GPP security messaging, MC service client to the IWF** + +1. The MC service client sends a non-3GPP security message request to the MC service server. The contents of the message are opaque to the MC service and are out of scope of 3GPP. +2. The MC service server forwards the contents of the non-3GPP security message request to the IWF. +3. The IWF acknowledges with a non-3GPP security message response to the MC service server. +4. The MC service server acknowledges with a non-3GPP security message response to the MC service client. + +### 10.12.2.3 IWF initiated + +Figure 10.12.2.3-1 describes the case where the IWF sends LMR security information to an MC service client. + +Pre-conditions: + +1. The MC service client is registered and the user is authenticated and authorized to use the MC service server. + +![Sequence diagram for IWF initiated non-3GPP security. Lifelines: MC service client, MC service server, IWF. The IWF sends a request to the MC service server, which then forwards it to the MC service client. The MC service client responds to the MC service server, which then forwards the response back to the IWF.](5199d255473623b85726fdb4f67dec8b_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MC service server + participant MC service client + Note left of IWF: IWF initiated security request + IWF->>MC service server: Request + MC service server->>MC service client: Forward Request + MC service client-->>MC service server: Response + MC service server-->>IWF: Forward Response + +``` + +Sequence diagram for IWF initiated non-3GPP security. Lifelines: MC service client, MC service server, IWF. The IWF sends a request to the MC service server, which then forwards it to the MC service client. The MC service client responds to the MC service server, which then forwards the response back to the IWF. + +**Figure 10.12.2.3-1: Non-3GPP security, from the IWF to MC service client** + +1. The IWF sends a non-3GPP security message request to the MC service server. The contents of the message are opaque to the MC service and are out of scope of 3GPP. +2. The MC service server forwards the contents of non-3GPP security message request to the MC service client. +3. The MC service client acknowledges with a non-3GPP security message response to the MC service server. +4. The MC service server forwards the non-3GPP security message response to the IWF. + +## 10.13 Analogue FM/TIA-603-D and other legacy LMR interworking + +### 10.13.1 General + +An IWF representing an LMR user can support interworking with legacy analogue FM radio systems that are compliant with the TIA-603-D [9] Standard. This type of legacy LMR system is sometimes referred to as conventional FM radio. + +Characteristics of legacy conventional FM radio include: + +- Voice media is conveyed without the use of a voice codec. +- There is no possibility of end-to-end encryption between an LMR user and a MC user. +- Group communication is possible using various means to identify a group such as a single channel / FM frequency, or sub-audible data as defined in [3]. The means for identifying groups within the legacy conventional FM system is outside the scope of the present document. +- The ID of the talking party is generally not available. Various means to identify a talker are available in legacy conventional FM systems, but this is outside the scope of the present document. + +- Indication of call priority (e.g. emergency) is generally not available. Various means to identify priority are available in legacy conventional FM systems, but this is outside the scope of the present document. + +Other legacy LMR systems such as digital conventional (e.g. P25 conventional), trunked analogue FM systems, non-standard legacy LMR systems, both conventional and trunked, can also be supported as long as they conform to the present document. + +## 10.13.2 Interworking Concepts + +Procedures defined in the present document are applicable to interworking with legacy analogue FM radio systems. + +Architecture concepts for interworking are summarized below, including general information for other legacy conventional radio systems. + +- The IWF is configured with knowledge of groups and users from legacy conventional LMR radio systems. Translations to MCPTT Group and MCPTT User IDs is performed by the IWF as specified in the present document. How the legacy LMR conventional system supports groups, such as mapping a group to a channel/frequency, or using a Group ID (i.e. P25 conventional), or mapping some other protocol element or tone signalling to a group is outside the scope of the present document. +- Interworking to a legacy conventional LMR system can make use of the following procedures as defined in the present document: + - affiliation; + - group management including group regrouping + - group calls including pre-arranged, chat, and broadcast; + - priority calls including emergency and imminent peril; and + - private calls. + +NOTE 1: Some analogue FM conventional LMR systems and digital conventional LMR systems support various schemes for private call. These can be supported as long as they conform to the present document. + +- Interworking to a legacy conventional LMR system can make use of the following functions of the MCPTT system, as defined in the present document: + - transcoding. +- Interworking to a legacy conventional LMR system can make use of the following functions of the MCPTT system, as defined in the present document, with some limitations: + - caller ID / talker ID; + - priority indication (e.g. emergency); + - end-to-end encryption; + - location; and + - short data service. + +NOTE 2: Some digital conventional LMR systems, such as P25 Conventional, natively support group IDs, user IDs, short data, and priority indication. In some cases, the talker ID becomes available sometime after the call starts. + +NOTE 3: Some analogue FM conventional LMR systems support various schemes for caller ID, emergency, and other features (e.g. Multi-tone, Type 99). These can be supported as long as they conform to the present document. In some cases, the talker ID becomes available sometime after the call starts. + +NOTE 4: Some digital conventional LMR systems, such as P25 Conventional, can support end-to-end encryption between the LMR user and a MC user. There is no possibility of end-to-end encryption between an analogue FM LMR user and a MC user. + +## 10.13.3 Procedures + +As described above, existing procedures in this document can be used for interworking with legacy conventional LMR radio systems. + +The following procedures describe special cases where the MCPTT ID (i.e. talker ID) is updated during a media transmission within a call. This mechanism of updating the MCPTT ID part way through an MCPTT media transmission may be used for any MCPTT media transmission described elsewhere in the present document. + +### 10.13.3.1 Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system + +In this procedure, an LMR user in a legacy conventional FM radio system initiates a group call on an interworking group defined in the MCPTT system. The talker ID is not known at the start of the call and is updated after media transmission begins. The signalling procedure is described in figure 10.13.3.1-1. + +This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the MCPTT system. +2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service. +3. The users in this interworking group have been affiliated to the interworking group. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +5. The LMR user in a legacy conventional FM radio system initiates a group call. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Figure 10.13.3.1-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT client 2.](2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + + IWF->>MCPTT server: 1. IWF group call request + rect rgb(255, 255, 255) + Note over MCPTT server, MCPTT client 2: 2. Call affiliated MCPTT users + end + MCPTT server-->>IWF: 3. IWF group call request + IWF-->>MCPTT server: 4. IWF group call response + MCPTT server-->>IWF: 5. IWF group call response + rect rgb(255, 255, 255) + Note over IWF, MCPTT client 2: 6. Media plane is established + end + MCPTT server->>IWF: 7. IWF floor granted + MCPTT server->>MCPTT client 1: 7. Floor taken + MCPTT server->>MCPTT client 2: 7. Floor taken + IWF-->>MCPTT server: 8. IWF floor taken + Note left of IWF: 9. LMR user talker ID is +received by the IWF + IWF->>MCPTT server: 10. IWF Talker ID update + MCPTT server->>MCPTT client 1: 11. Floor taken + MCPTT server->>MCPTT client 2: 11. Floor taken + IWF-->>MCPTT server: 12. IWF floor taken + +``` + +Sequence diagram for Figure 10.13.3.1-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. + +**Figure 10.13.3.1-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the MCPTT system** + +1. The IWF sends an IWF group call request to the MCPTT server for call establishment. In this case floor control is also requested and an indication of implicit floor request is included. The IWF uses its pre-configured MCPTT ID in the group call request. + 2. The MCPTT server calls the affiliated users from the MCPTT system as described in 3GPP TS 23.379 [7]. The LMR user is in a legacy conventional FM radio system so E2EE is not specified, and transcoding is needed at the IWF. + 3. If the group has other affiliated LMR users than the calling party and the MCPTT server has received individual affiliations from those LMR users, an individual IWF group call request is sent to the IWF for each affiliated LMR user. +- NOTE 2: Steps 2 and 3 can occur in any order. +- NOTE 3: How the LMR users from the LMR system are being called is outside the scope of the present document. +4. The IWF returns IWF group call response(s) to the MCPTT server. + 5. The MCPTT server confirms the successful establishment of the group call by sending an IWF Group call response to the IWF. + +NOTE 4: How the group call response is returned to the initiating LMR user is outside the scope of the present document. + +6. The interworking group call has successfully established media plane for communication and any user can transmit media. The MCPTT system where the interworking group is defined is the controlling system of the group call and manages the floor control. + +NOTE 5: How the floor control is managed in the LMR system is outside the scope of the present document. + +7. Because the group call request contained an implicit floor request, and no other users are requesting the floor, the MCPTT server sends an IWF floor granted message to the IWF confirming that the IWF has the floor. The MCPTT server also sends Floor taken messages to the affiliated users in the MCPTT system. The MCPTT ID in the floor taken messages is the pre-configured IWF MCPTT ID. + +8. If the group has other affiliated LMR users than the calling party, and the MCPTT server has received individual affiliations from those LMR users, an individual IWF floor taken message is sent to the IWF for each affiliated LMR user. + +9. At some time after media transfer begins, the IWF receives knowledge of the LMR user's talker ID. + +NOTE 6: How the IWF learns the LMR user's talker ID is outside the scope of the present document. In some LMR conventional systems, the talker ID becomes available shortly after the start of the call; in other systems, it is not available until the end of the call. + +10. The IWF sends an IWF talker ID update to the MCPTT server informing the server that a new talker is using the floor, but the floor should not be released. + +11. The MCPTT server sends Floor taken messages to the affiliated users in the MCPTT system. The MCPTT ID in the floor taken messages is the new talker ID contained in the IWF talker ID update. + +NOTE 7: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn the identity of the newly granted talker. + +12. If the group has other affiliated LMR users than the calling party, and the MCPTT server has received individual affiliations from those LMR users, an individual IWF floor taken message is sent to the IWF for each affiliated LMR user. + +### 10.13.3.2 Group call with talker ID update initiated by an LMR user on an interworking group defined in the LMR system + +In this procedure, an LMR user in a legacy conventional FM radio system initiates a group call on an interworking group defined in the LMR system. The talker ID is not known at the start of the call and is updated after media transmission begins. The signalling procedure is described in figure 10.13.3.2-1. + +This subclause is based upon subclause for pre-arranged group call setup in 3GPP TS 23.379 [7], subclause 10.6.2.3.1.1.2. + +Pre-conditions: + +1. The interworking group information is known at the MCPTT server and the IWF by configuration or group creation. The interworking group has been defined in the LMR system. +2. MCPTT client 1 and MCPTT client 2 are registered and their respective users are authenticated and authorized to use the MCPTT service. +3. The users in this interworking group have been affiliated to the interworking group. +4. The mapping relationship of group and user identities between the MCPTT system and the LMR system has been configured at the IWF. +5. The LMR user in a legacy conventional FM radio system initiates a group call. + +NOTE 1: For all the signalling messages passing through the IWF between the MCPTT system and the LMR system, the IWF performs the identity conversion and protocol translation. + +![Sequence diagram for Figure 10.13.3.2-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the LMR system. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The process involves group call requests, responses, media plane establishment, floor taken messages, and an LMR user talker ID update.](09797d4289ec96309d21a9a993153dab_img.jpg) + +``` + +sequenceDiagram + participant IWF + participant MCPTT server + participant MCPTT client 1 + participant MCPTT client 2 + + Note left of IWF: 8. LMR user talker ID is received by the IWF + + IWF->>MCPTT server: 1a. IWF group call request + IWF->>MCPTT server: 1b. IWF group call request + MCPTT server->>MCPTT client 1: 2a. Group call request + MCPTT server->>MCPTT client 2: 2b. Group call request + MCPTT client 1->>MCPTT server: 3a. Group call response + MCPTT client 2->>MCPTT server: 3b. Group call response + MCPTT server->>IWF: 4a. IWF group call response + MCPTT server->>IWF: 4b. IWF group call response + + Note over IWF, MCPTT client 2: 5. Media plane is established + + IWF->>MCPTT server: 6a. IWF floor taken + IWF->>MCPTT server: 6b. IWF floor taken + MCPTT server->>MCPTT client 1: 7a. Floor taken + MCPTT server->>MCPTT client 2: 7b. Floor taken + + Note left of IWF: 8. LMR user talker ID is received by the IWF + + IWF->>MCPTT server: 9a. IWF floor taken + IWF->>MCPTT server: 9b. IWF floor taken + MCPTT server->>MCPTT client 1: 10a. Floor taken + MCPTT server->>MCPTT client 2: 10b. Floor taken + +``` + +Sequence diagram for Figure 10.13.3.2-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the LMR system. The diagram shows interactions between IWF, MCPTT server, MCPTT client 1, and MCPTT client 2. The process involves group call requests, responses, media plane establishment, floor taken messages, and an LMR user talker ID update. + +**Figure 10.13.3.2-1: Group call with talker ID update initiated by an LMR user on an interworking group defined in the LMR system** + +1. The IWF sends an IWF group call request(s) to the MCPTT server for call establishment. An individual IWF group call request is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2. In this case floor control is also requested and an indication of implicit floor request is included. The IWF uses its pre-configured MCPTT ID in the group call request. +2. The MCPTT server sends a group call request(s) to the target MCPTT user(s) as described in 3GPP TS 23.379 [7]. The LMR user is in a legacy conventional FM radio system so E2EE is not specified, and transcoding is needed at the IWF. +3. MCPTT client(s) receiving the group call request, acknowledge towards the MCPTT server by sending a group call response. +4. The MCPTT server acknowledges the IWF group call request(s) by sending an IWF group call response(s) to the IWF. + +NOTE 2: How the IWF group call response(s) is handled in the IWF / LMR system and how the other LMR users are being called is outside the scope of the present document. + +5. The interworking group call has successfully established media plane for communication and any user can transmit media. The LMR system where the interworking group is defined is the controlling system of the group call and manages the floor control. + +NOTE 3: How the floor control is managed in the LMR system is outside the scope of the present document. + +6. Because the group call request contained an implicit floor request, and no other users are requesting the floor, the IWF sends an IWF floor taken message to the MCPTT server confirming that the IWF has the floor. An individual IWF floor taken message is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2. +7. The MCPTT server sends Floor taken to the target MCPTT user(s) in the MCPTT system. The MCPTT ID in the floor taken messages is the pre-configured IWF MCPTT ID. +8. At some time after media transfer begins, the IWF receives knowledge of the LMR user's talker ID. + +NOTE 4: How the IWF learns the LMR user's talker ID is outside the scope of the present document. In some LMR conventional systems, the talker ID becomes available shortly after the start of the call; in other systems, it is not available until the end of the call. + +9. The IWF sends an IWF floor taken to the MCPTT server informing the server that a new talker is using the floor, but the floor should not be released. An individual IWF floor taken message is sent to the MCPTT server for each affiliated MCPTT user in the group, in this example scenario to the users in MCPTT clients 1 and 2 +10. The MCPTT server sends Floor taken messages to the target MCPTT user(s) in the MCPTT system. The MCPTT ID in the floor taken messages is the new talker ID contained in the IWF talker ID update. + +NOTE 5: All other floor participants (not shown) that are part of this group call receive a floor taken message, so that the other floor participants learn the identity of the newly granted talker. + +## 10.14 IWF functional alias management + +NOTE: The IWF functional alias management feature has been deferred from the present document. + +## 10.15 Enhanced status + +### 10.15.1 General + +3GPP TS 23.282 [6] clause 7.9 describes a high-level procedure to provide enhanced status information to all the receiving MCData users. + +### 10.15.2 Preset values for enhanced status + +The configuration of preset values into the group configuration data is described in 3GPP TS 23 282 [6] clause 7.9.2. + +### 10.15.3 Enhanced status for on-network + +#### 10.15.3.1 Procedure (MCData to IWF) + +The procedure for an MCData user requesting to share enhanced status to an MCData group is as specified in 3GPP TS 23.282 [6] clause 7.9.3 for the enhanced status for on-network use; one or more users using MCData clients 2-n may be LMR users behind an IWF that has affiliated to the MCData group (see clause 10.1.2 of the present document). The IWF behaves as a peer MCData server. + +#### 10.15.3.2 Procedure (IWF to MCData) + +The procedure for an IWF requesting, on behalf of an LMR user, to share enhanced status to an MCData group is as specified in 3GPP TS 23.282 [6] subclause 7.9.3 for the enhanced status for on-network use, with the exception that MCData client 1 is located behind an IWF and one or more of the MCData clients 2 to n can be behind IWFs that have affiliated to the MCData group (see clause 10.1.2 of the present document). The IWF behaves as a peer MCData server to other MCData servers. + +--- + +## Annex A (informative): Change history + +| Change history | | | | | | | | | +|----------------|---------|-----------|------|-----|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | | +| 2017-06 | - | - | - | - | - | TS template | 0.0.0 | | +| 2017-07 | SA6#18 | | | | | Implementation of the following p-CRs approved by SA6:
S6-170920, S6-170976, S6-170977, S6-170978, S6-170979,
S6-170981, S6-171013, S6-171016, S6-171019, S6-171065,
S6-171066, S6-171067, S6-171068, S6-171069, S6-171070,
S6-171071 and S6-171072. | 0.1.0 | | +| 2017-10 | SA6#19 | | | | | Implementation of the following p-CRs approved by SA6:
S6-171310, S6-171311, S6-171321, S6-171325, S6-171376,
S6-171420, S6-171421, S6-171423, S6-171424, S6-171427,
S6-171428, S6-171429, S6-171430, S6-171431, S6-171433,
S6-171434, S6-171460, S6-171461, S6-171462 and S6-171489. | 0.2.0 | | +| 2017-12 | SA6#20 | | | | | Implementation of the following p-CRs approved by SA6:
S6-171511, S6-171533, S6-171614, S6-171723, S6-171724,
S6-171725, S6-171726, S6-171727, S6-171728, S6-171733,
S6-171735, S6-171738, S6-171740, S6-171741, S6-171749,
S6-171751, S6-171797, S6-171801, S6-171802, S6-171803,
S6-171806, S6-171808, S6-171809, S6-171827, S6-171828,
S6-171853, S6-171854, S6-171875 | 0.3.0 | | +| 2017-12 | SA6#20 | | | | | Rapporteur's editorial changes | 0.3.1 | | +| 2017-12 | SA#78 | SP-170902 | | | | Submitted to SA#78 for information | 1.0.0 | | +| 2018-01 | SA6#21 | | | | | Implementation of the following p-CRs approved by SA6:
S6-180055, S6-180108, S6-180109, S6-180171, S6-180175,
S6-180190, S6-180199, S6-180200, S6-180214 | 1.1.0 | | +| 2018-02 | | | | | | Editorial changes | 1.1.1 | | +| 2018-03 | SA6#22 | | | | | Implementation of the following p-CRs approved by SA6:
S6-180248, S6-180347, S6-180358, S6-180361, S6-180362,
S6-180363, S6-180364, S6-180374, S6-180390, S6-180440,
S6-180442, S6-180444, S6-180446, S6-180447, S6-180449,
S6-180450, S6-180451, S6-180452, S6-180453, S6-180454,
S6-180461, S6-180462, S6-180481, S6-180491. | 1.2.0 | | +| 2018-03 | | | | | | Editorial fixes, missing LMR abbreviation from S6-180364. | 1.2.1 | | +| 2018-03 | SA#79 | SP-180159 | | | | Submitted for approval at SA#79 | 2.0.0 | | +| 2018-04 | SA#79 | SP-180159 | | | | MCC Editorial update for publication after TSG SA approval (SA#79) | 15.0.0 | | +| 2018-06 | SA#80 | SP-180372 | 0001 | 2 | F | Flow name update from MCPTT call end to MCPTT private call end | 15.1.0 | | +| 2018-06 | SA#80 | SP-180372 | 0002 | 1 | F | Corrections to Imminent peril group call initiated by MCPTT user | 15.1.0 | | +| 2018-06 | SA#80 | SP-180372 | 0003 | 2 | F | Corrections to Imminent peril group call initiated by LMR user | 15.1.0 | | +| 2018-06 | SA#80 | SP-180372 | 0004 | | F | Corrections to Imminent peril cancel | 15.1.0 | | +| 2018-06 | SA#80 | SP-180372 | 0005 | 3 | F | Corrections to chat group call procedures and information flows | 15.1.0 | | +| 2018-06 | SA#80 | SP-180372 | 0006 | 1 | F | Alignment of terminology emergency and imminent peril | 15.1.0 | | +| 2018-06 | SA#80 | SP-180372 | 0007 | 1 | F | Alignment of terminology - pre-arranged group call | 15.1.0 | | +| 2018-06 | SA#80 | SP-180372 | 0008 | 1 | F | IWF actions on Imminent peril group calls | 15.1.0 | | +| 2018-06 | SA#80 | SP-180372 | 0009 | 1 | F | Corrections to emergency group call procedures | 15.1.0 | | +| 2018-09 | SA#81 | SP-180673 | 0017 | 2 | F | IWF SDS fix | 15.2.0 | | +| 2018-09 | SA#81 | SP-180679 | 0014 | 1 | F | IWF affiliation auth update | 16.0.0 | | +| 2018-09 | SA#81 | SP-180679 | 0015 | 1 | F | IWF broadcast call fixes | 16.0.0 | | +| 2018-09 | SA#81 | SP-180679 | 0016 | 1 | F | IWF alert cancel alignment | 16.0.0 | | +| 2018-12 | SA#82 | SP-181179 | 0019 | | F | IWF group call request broadcast indicator correction | 16.1.0 | | +| 2018-12 | SA#82 | SP-181179 | 0021 | 2 | C | Add Implicit floor request to IWF group call request and IWF imminent peril group call request | 16.1.0 | | +| 2018-12 | SA#82 | SP-181179 | 0022 | | C | Add Location information to IWF floor request and IWF floor taken messages | 16.1.0 | | +| 2019-03 | SA#83 | SP-190076 | 0023 | 1 | F | MCPTT ID in interworking floor control | 16.2.0 | | +| 2019-03 | SA#83 | SP-190076 | 0024 | 2 | C | IWF alignment for talker location in requests for Group call and Group-broadcast group call setup | 16.2.0 | | +| 2019-03 | SA#83 | SP-190076 | 0025 | 1 | C | IWF alignment for talker location in Chat group | 16.2.0 | | +| 2019-03 | SA#83 | SP-190076 | 0026 | 2 | C | IWF alignment for talker location in Private call | 16.2.0 | | +| 2019-03 | SA#83 | SP-190076 | 0027 | 1 | C | IWF alignment for talker Location related to Imminent peril groups | 16.2.0 | | +| 2019-03 | SA#83 | SP-190076 | 0028 | 1 | C | IWF alignment for current talker location | 16.2.0 | | +| 2019-03 | SA#83 | SP-190076 | 0029 | 2 | C | TS 23.379 alignment for late join | 16.2.0 | | +| 2019-03 | SA#83 | SP-190076 | 0030 | 2 | B | Analogue FM interworking | 16.2.0 | | +| 2019-06 | SA#84 | SP-190487 | 0033 | 1 | C | 23.283 location with implicit floor request | 16.3.0 | | +| 2019-06 | SA#84 | SP-190488 | 0035 | 2 | B | Functional Alias management for interworking between MC service system and LMR system | 16.3.0 | | +| 2019-09 | SA#85 | SP-190728 | 0038 | 4 | B | IWF preconfigured groups | 16.4.0 | | +| 2019-09 | SA#85 | SP-190728 | 0039 | 4 | B | IWF add user to temporary pre-configured group regroup | 16.4.0 | | +| 2019-09 | SA#85 | SP-190728 | 0041 | 2 | B | IWF temporary group calls | 16.4.0 | | +| 2019-09 | SA#85 | SP-190728 | 0042 | 4 | B | IWF user regroup with pre-configured group | 16.4.0 | | +| 2019-09 | SA#85 | SP-190728 | 0044 | 4 | B | IWF preconfigured broadcast group calls | 16.4.0 | | +| 2019-09 | SA#85 | SP-190728 | 0045 | 2 | B | IWF preconfigured broadcast group calls | 16.4.0 | | +| 2019-09 | SA#85 | SP-190728 | 0047 | 1 | F | IWF identities wording correction | 16.4.0 | | + +| | | | | | | | | +|---------|-------|-----------|------|---|---|---------------------------------------------------------------------------------------------------------------|--------| +| 2019-09 | SA#85 | SP-190728 | 0051 | 1 | F | Remove 10.5.2.17 Editor's Note | 16.4.0 | +| 2020-09 | SA#89 | SP-200838 | 0053 | 1 | F | Interworking private call floor control | 16.5.0 | +| 2021-12 | SA#94 | SP-211520 | 0056 | | F | Correction to Disposition Notification handling when LMR system temporarily disables Disposition Notification | 16.6.0 | +| 2022-03 | SA#95 | SP-220100 | 0060 | 1 | F | Correction of Enhanced Status description | 16.7.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23284/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23284/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0602f7aed46fbc4f4596ae3fce174067a211219 --- /dev/null +++ b/marked/Rel-16/23_series/23284/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:23ba371c82658c3781baf1f90d16cfe93f3165f1aa94a8ff315d80ba9e022169 +size 90260 diff --git a/marked/Rel-16/23_series/23284/0cc154cbdde7cc6c39f394597c7aca0c_img.jpg b/marked/Rel-16/23_series/23284/0cc154cbdde7cc6c39f394597c7aca0c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ac065a0e8fba41abd3c943ef24f4c7d813cd45a3 --- /dev/null +++ b/marked/Rel-16/23_series/23284/0cc154cbdde7cc6c39f394597c7aca0c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15aa7fb47f3605c6ca304bbf37003103081b5c33a7d5f327bc98207a85df916b +size 95143 diff --git a/marked/Rel-16/23_series/23284/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/marked/Rel-16/23_series/23284/0ee9d674085524d589646a6c3fb21ec3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b505a589743e8a0eb4820d67b7d171265201a32 --- /dev/null +++ b/marked/Rel-16/23_series/23284/0ee9d674085524d589646a6c3fb21ec3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cf052d0f6227cc514b41d7e1acff09caf497651eb140d62fc200891c161d13d +size 46782 diff --git a/marked/Rel-16/23_series/23284/1018d0db7bb02c169f646cb9cc244dc6_img.jpg b/marked/Rel-16/23_series/23284/1018d0db7bb02c169f646cb9cc244dc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81fd68c2f072def609ff534c3ce3a9f7ab52dffe --- /dev/null +++ b/marked/Rel-16/23_series/23284/1018d0db7bb02c169f646cb9cc244dc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cd88eed5eadd31a8fa195021e491447188df437faa18d88860d195b12a486e1 +size 48063 diff --git a/marked/Rel-16/23_series/23284/114902bbeea56bda01b64b43fad41920_img.jpg b/marked/Rel-16/23_series/23284/114902bbeea56bda01b64b43fad41920_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..59cc45b5dbb6734602562d161faa566c69f36331 --- /dev/null +++ b/marked/Rel-16/23_series/23284/114902bbeea56bda01b64b43fad41920_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:eb8887926a53eb298a628887654d6b537fbe925e39fd93e970804666943cb60b +size 48386 diff --git a/marked/Rel-16/23_series/23284/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg b/marked/Rel-16/23_series/23284/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7d4b0b2fdd8413a6af84be765f581227a62d230a --- /dev/null +++ b/marked/Rel-16/23_series/23284/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2f6f36842ade44922f34b2a3a1954ff3cbec9284a4ad9951e356cd49925c1f29 +size 77747 diff --git a/marked/Rel-16/23_series/23284/1399c76ef88f22b70d05ed3f781d3c48_img.jpg b/marked/Rel-16/23_series/23284/1399c76ef88f22b70d05ed3f781d3c48_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..12d498b0362a32b07bea902d7b98c8a83c1971ee --- /dev/null +++ b/marked/Rel-16/23_series/23284/1399c76ef88f22b70d05ed3f781d3c48_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f4c6c6dad0ed08d83893575a896126605e6d72662fbf0549bc4dd268dcee634a +size 76229 diff --git a/marked/Rel-16/23_series/23284/13fde41de77bf026013a0b81684d1fc9_img.jpg b/marked/Rel-16/23_series/23284/13fde41de77bf026013a0b81684d1fc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a9491b809b94042cb2f29b433ce5823a1816b9da --- /dev/null +++ b/marked/Rel-16/23_series/23284/13fde41de77bf026013a0b81684d1fc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10a096dbfee2d78dfec15df747618bfc9c39d425eecfc55366b2404e26664e5b +size 209141 diff --git a/marked/Rel-16/23_series/23284/187d05bf7ead21e1394b61320d8b3632_img.jpg b/marked/Rel-16/23_series/23284/187d05bf7ead21e1394b61320d8b3632_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a72b345b872a2d0f62b5cf13ce5bfce70e2fddc --- /dev/null +++ b/marked/Rel-16/23_series/23284/187d05bf7ead21e1394b61320d8b3632_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f44aa9c9bf07c7d558910c87b4476150a724523d833fd836f9e3429bbf7e084 +size 71576 diff --git a/marked/Rel-16/23_series/23284/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23284/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..15d4b7c90f65ba815d1b7bafa493174a37625b12 --- /dev/null +++ b/marked/Rel-16/23_series/23284/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c010e2c418317a4101904d438668da5bc5645aa3de786e1716f8134bd294df7 +size 176878 diff --git a/marked/Rel-16/23_series/23284/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-16/23_series/23284/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2d2b9d010f6bac2a139fae077a1d92e342952e86 --- /dev/null +++ b/marked/Rel-16/23_series/23284/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1a1a735da4f256c1b3002ead6c17949919537e8ea15162ba8b3f5d1c93d64ca4 +size 65842 diff --git a/marked/Rel-16/23_series/23284/215165a27ad7d72bd39fdf55a3cb7486_img.jpg b/marked/Rel-16/23_series/23284/215165a27ad7d72bd39fdf55a3cb7486_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f2a46e525d0201797814cab46bc0a2044a3a305b --- /dev/null +++ b/marked/Rel-16/23_series/23284/215165a27ad7d72bd39fdf55a3cb7486_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8bbd4047ddd0a4f9fc413ceb8ba315a008d46c80f8f567445c3fcf453c3d271 +size 41051 diff --git a/marked/Rel-16/23_series/23284/237b76118be454462fc9b4e96adaa6c7_img.jpg b/marked/Rel-16/23_series/23284/237b76118be454462fc9b4e96adaa6c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4be2360e5b28ea1190d82a11430c8e05674d0d54 --- /dev/null +++ b/marked/Rel-16/23_series/23284/237b76118be454462fc9b4e96adaa6c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d3331ad17a61f14e7a8d24075edf3ee2821a3bda54038796a5cb758e12347d99 +size 71278 diff --git a/marked/Rel-16/23_series/23284/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23284/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..54e22ee575a93bedce52117f6d090211eac6cc82 --- /dev/null +++ b/marked/Rel-16/23_series/23284/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:459c1c2ace4805c6944dfbd33d36e92233ea1632a7ddd5363c22e0a2b8b6ef34 +size 71991 diff --git a/marked/Rel-16/23_series/23284/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/23_series/23284/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ccc9f9da5a581fe6ccdba293e3976153d686c00b --- /dev/null +++ b/marked/Rel-16/23_series/23284/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5ee623b499d2ac659de5bcfcc9aa95cfa7782f69e21add095a83bde7f2cbfa6c +size 98794 diff --git a/marked/Rel-16/23_series/23284/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23284/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bc8bb0ac01af10d7e1c3e5e47cb42c1b6835899 --- /dev/null +++ b/marked/Rel-16/23_series/23284/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02c184ff2af2620f564edae81570fbec7751caf40a3a32165a11b80a0b607379 +size 56237 diff --git a/marked/Rel-16/23_series/23284/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/marked/Rel-16/23_series/23284/2a476a0b3dbc3429436246db4784ff9f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dd5cf8610f78c7fafc2b39d15afcf74ad9dbffe6 --- /dev/null +++ b/marked/Rel-16/23_series/23284/2a476a0b3dbc3429436246db4784ff9f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:461e530c63c819ae5941849eca6c56b5269e21fea3e6a220c84a60e96ee0db78 +size 138069 diff --git a/marked/Rel-16/23_series/23284/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/marked/Rel-16/23_series/23284/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c038651f1ab3f75416b2dce78184c49d8b285124 --- /dev/null +++ b/marked/Rel-16/23_series/23284/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4e490e4850e345210ae34ae56671c7d7e61da89b2bd4c3c02badb5ec8cc6e6ab +size 169466 diff --git a/marked/Rel-16/23_series/23284/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/marked/Rel-16/23_series/23284/2cf3896394a2342a2b46c504ab9a8830_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..236a41f8f996487f72201d774b26a6f9fe73baaa --- /dev/null +++ b/marked/Rel-16/23_series/23284/2cf3896394a2342a2b46c504ab9a8830_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:43a18fb88b65cb565b724da77bc03edf42f30ece9889fb14588a8bb420153f3a +size 170300 diff --git a/marked/Rel-16/23_series/23284/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/Rel-16/23_series/23284/2f587210e4f97c32758c5972e2e83d20_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b485cdc7616cb8397a57d95aa7e9ac64ec202ac3 --- /dev/null +++ b/marked/Rel-16/23_series/23284/2f587210e4f97c32758c5972e2e83d20_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f01d7cb31d3441c8fcffda8d94fa5b34ad915c0aef78705b91e57a73af11904b +size 179220 diff --git a/marked/Rel-16/23_series/23284/30387053b5b3fede6873f6a46a9ca4a9_img.jpg b/marked/Rel-16/23_series/23284/30387053b5b3fede6873f6a46a9ca4a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..117e0be2389dff20abb919fe1aa708f25cab515c --- /dev/null +++ b/marked/Rel-16/23_series/23284/30387053b5b3fede6873f6a46a9ca4a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:314de6908b77d3038ff58c4856763ae4b1eaedaa6f5764cc1c71683d6fe98a36 +size 72515 diff --git a/marked/Rel-16/23_series/23284/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/Rel-16/23_series/23284/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..81dd83063e9689c271bfb2d7290152b7c1bf1b38 --- /dev/null +++ b/marked/Rel-16/23_series/23284/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:984b190984009a864007e2149cbf330527989e3ef0d08eff1fc7d9945c15bf78 +size 51794 diff --git a/marked/Rel-16/23_series/23284/31ef15d175af5babdbf4d2fbac884c1b_img.jpg b/marked/Rel-16/23_series/23284/31ef15d175af5babdbf4d2fbac884c1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8d4f6827b8e94efcfbd07d53eb8dced2a5ee2a80 --- /dev/null +++ b/marked/Rel-16/23_series/23284/31ef15d175af5babdbf4d2fbac884c1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a32f73756ca4de46cbfa58a731b6c99566a69eca0290fbccfa7c33031a38df8e +size 74409 diff --git a/marked/Rel-16/23_series/23284/327ba94498e3381cf08eb41e3fd3d77f_img.jpg b/marked/Rel-16/23_series/23284/327ba94498e3381cf08eb41e3fd3d77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ac3319fdc19010a95f9c51e6abb34f841bfc231 --- /dev/null +++ b/marked/Rel-16/23_series/23284/327ba94498e3381cf08eb41e3fd3d77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0308f5e85684aaba8d43675706a2a0622814e5bd45abcc78bcf6f9874e0b0db3 +size 58306 diff --git a/marked/Rel-16/23_series/23284/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/marked/Rel-16/23_series/23284/329c96049bb432e9c2cbda4e224a0c9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..85ea84aa3d49f2e5bcaa78afa486696434687f73 --- /dev/null +++ b/marked/Rel-16/23_series/23284/329c96049bb432e9c2cbda4e224a0c9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7628d617cfb59ef6f51dad2f9ae22a6e28d5c9defc5f6e6b7d8df7e41ac5d36f +size 157908 diff --git a/marked/Rel-16/23_series/23284/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg b/marked/Rel-16/23_series/23284/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c8b17e2eb17b6fda399c04bc24bebd644ea6e315 --- /dev/null +++ b/marked/Rel-16/23_series/23284/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60855b8df0872054810e10a66c36e10c8a094081533d36b6a7d113ffb09aa3a4 +size 169935 diff --git a/marked/Rel-16/23_series/23284/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/marked/Rel-16/23_series/23284/347010b7ac06d3ae97927fde0f784d7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6be7f7ef2be5f08ed1b0f967cb079d724f360002 --- /dev/null +++ b/marked/Rel-16/23_series/23284/347010b7ac06d3ae97927fde0f784d7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1e4edf31866a0d6470927418db074ebef4f9604630ffc4ba3fee2ef3540d110f +size 83152 diff --git a/marked/Rel-16/23_series/23284/3750b0149a6380885998ab3ca6a8787c_img.jpg b/marked/Rel-16/23_series/23284/3750b0149a6380885998ab3ca6a8787c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3e324390ccb56c7acea3414217d191a3bcf5ed8f --- /dev/null +++ b/marked/Rel-16/23_series/23284/3750b0149a6380885998ab3ca6a8787c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2eaad636cea1311e9e4d42a1b20583247397d66fdc7a3a476d4c9436e2c68c22 +size 86341 diff --git a/marked/Rel-16/23_series/23284/37a6ab1d23efb9dc00cfae09d353b1da_img.jpg b/marked/Rel-16/23_series/23284/37a6ab1d23efb9dc00cfae09d353b1da_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..246206efa5a9b2547bea3e525293e40b6bf24556 --- /dev/null +++ b/marked/Rel-16/23_series/23284/37a6ab1d23efb9dc00cfae09d353b1da_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:654a08ef8c9bd46cf62e1163669ff9a9c19eb0da1e571ff40e19d8cf755fdb98 +size 47865 diff --git a/marked/Rel-16/23_series/23284/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/marked/Rel-16/23_series/23284/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9f843485dde78f9e1e19e40f7c200595d8ce262a --- /dev/null +++ b/marked/Rel-16/23_series/23284/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6a251c8479f1a8727d02021e5269965f3400b720cc24b53f3f0031b4419f4693 +size 62499 diff --git a/marked/Rel-16/23_series/23284/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg b/marked/Rel-16/23_series/23284/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7b10419a50964a56c63bc5d252d79176535d0842 --- /dev/null +++ b/marked/Rel-16/23_series/23284/3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af2d352df3772fe4f6e070c5c1ab1e20cd6d6cd57494f810a7f506b5b4a98d3b +size 166731 diff --git a/marked/Rel-16/23_series/23284/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg b/marked/Rel-16/23_series/23284/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0424451fa61b06213f904415d4dc98169719c827 --- /dev/null +++ b/marked/Rel-16/23_series/23284/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:250e85a569d1e7bf9aa390c460830f326b8372b84b8b71b52728c1e0be45e225 +size 70699 diff --git a/marked/Rel-16/23_series/23284/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/23_series/23284/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21d5792984c0a5df88ec2860a3a926e9abce8a40 --- /dev/null +++ b/marked/Rel-16/23_series/23284/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:13a11e470489b14101fd9b565ac410be92d304e56a3fec0272896dddd7973de0 +size 168021 diff --git a/marked/Rel-16/23_series/23284/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/marked/Rel-16/23_series/23284/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..46f4e8a183c5a162db53eccbeb3b22c307c7dcab --- /dev/null +++ b/marked/Rel-16/23_series/23284/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:279b0896aec23e98e9223d5c953683b4297b1624e2d4e0480f3533d91252bdb5 +size 43560 diff --git a/marked/Rel-16/23_series/23284/458fdbcb4015a4ee90bd84809afc4aac_img.jpg b/marked/Rel-16/23_series/23284/458fdbcb4015a4ee90bd84809afc4aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a55983a7a62c61faec47064e613ee2ebb3629ca4 --- /dev/null +++ b/marked/Rel-16/23_series/23284/458fdbcb4015a4ee90bd84809afc4aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:99014a017def06ff328fadd75960eed44c46fadb980837761fed3bcc7004816d +size 112905 diff --git a/marked/Rel-16/23_series/23284/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/marked/Rel-16/23_series/23284/49fe8fe978c0f7e73112d231feb377eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3054f10c37081d77cc1ca55f98b61de81fd8c142 --- /dev/null +++ b/marked/Rel-16/23_series/23284/49fe8fe978c0f7e73112d231feb377eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a612139333b13474cae402f8a7d1c0178617fa1e197e66a86641c1e393de65fc +size 90057 diff --git a/marked/Rel-16/23_series/23284/4af57aad638888edf2062306f8a54a6c_img.jpg b/marked/Rel-16/23_series/23284/4af57aad638888edf2062306f8a54a6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e811582acb46f85d66810d964c94f23101c41be3 --- /dev/null +++ b/marked/Rel-16/23_series/23284/4af57aad638888edf2062306f8a54a6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bad705dd7cc0e6b1e8b104c107e01b0f1ce262f1160d5aa4debd9df5ba1cfe74 +size 46225 diff --git a/marked/Rel-16/23_series/23284/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/marked/Rel-16/23_series/23284/4b398c5e8c4fd656d5b7a61806400650_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d4b6482c617807e0cd6f7d5867250afc2a00b055 --- /dev/null +++ b/marked/Rel-16/23_series/23284/4b398c5e8c4fd656d5b7a61806400650_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28f5360f28806961c1534dd4796b5d3188b95a0138e6a64067772d916eda726a +size 55142 diff --git a/marked/Rel-16/23_series/23284/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg b/marked/Rel-16/23_series/23284/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b951483cfa35ab5a071c7c32fc5734d1300c9579 --- /dev/null +++ b/marked/Rel-16/23_series/23284/4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:50f0c448e9f288568f82e85e047f855e3fabae4da72f3c396d624cbef028e17e +size 95624 diff --git a/marked/Rel-16/23_series/23284/4ff00a489baaa34a0c01070de1d613db_img.jpg b/marked/Rel-16/23_series/23284/4ff00a489baaa34a0c01070de1d613db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..33c0e2d779440b2bbf3fb30ccaa61d3955945011 --- /dev/null +++ b/marked/Rel-16/23_series/23284/4ff00a489baaa34a0c01070de1d613db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0e355d52c44ded487ff648d30a5b734a2061b5ca724d1c878ef59558ae6a9846 +size 40764 diff --git a/marked/Rel-16/23_series/23284/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/marked/Rel-16/23_series/23284/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f353a45a7b5b178d50838d16a53ac287382f591 --- /dev/null +++ b/marked/Rel-16/23_series/23284/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba3091ccdefc3e8331eeb75a62a4a906fdf875f66227b6c5f597cf88560969cd +size 81146 diff --git a/marked/Rel-16/23_series/23284/56a5265d174ce056c1dbe5e7a60839fc_img.jpg b/marked/Rel-16/23_series/23284/56a5265d174ce056c1dbe5e7a60839fc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f8f38a25656f7d57377e5684762953b4398d4cd --- /dev/null +++ b/marked/Rel-16/23_series/23284/56a5265d174ce056c1dbe5e7a60839fc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dbca5901b4dc4b4a101ec8e28b55860e81a7453de2bde229db036f88d8f7e353 +size 117824 diff --git a/marked/Rel-16/23_series/23284/5801c19431e76330430e92a598cc7a16_img.jpg b/marked/Rel-16/23_series/23284/5801c19431e76330430e92a598cc7a16_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..09b4905d6314d96a645fa43b0f132b596cd0332b --- /dev/null +++ b/marked/Rel-16/23_series/23284/5801c19431e76330430e92a598cc7a16_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7a2e16bf81c16158faf8a18b1f0c9c0cf5855ac9ca35d91db5aff5302cfac57 +size 42828 diff --git a/marked/Rel-16/23_series/23284/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23284/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4c32838fdbf3a3d59a314452767a259736c61a3e --- /dev/null +++ b/marked/Rel-16/23_series/23284/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c92861e7a5f68438c09f7c381bfc6651b8e28030b74922fd9a1e858f20ab325 +size 81179 diff --git a/marked/Rel-16/23_series/23284/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/marked/Rel-16/23_series/23284/5cf80bac69830ea773ac17c87e0ae24d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b45a5e9cc42d11d958abc47aba6a053bf0c33183 --- /dev/null +++ b/marked/Rel-16/23_series/23284/5cf80bac69830ea773ac17c87e0ae24d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:503d545ee617c1acf73c05b5bd6e6a1e81efc0e0219288b30d4c4789f77ce063 +size 188970 diff --git a/marked/Rel-16/23_series/23284/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg b/marked/Rel-16/23_series/23284/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..301e289e9d7e4e0d27085fbd46acd73cbf90767b --- /dev/null +++ b/marked/Rel-16/23_series/23284/5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53f1bb1a9e4fab0874e35ab1e462c335bd7c2a57141b47b87cc03c2d23311020 +size 144055 diff --git a/marked/Rel-16/23_series/23284/5dadcfbae18c4b3f91ea3a5e84d0a47a_img.jpg b/marked/Rel-16/23_series/23284/5dadcfbae18c4b3f91ea3a5e84d0a47a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..78ed6aea543a47ac08943b25a4e17ff9b00b7a0b --- /dev/null +++ b/marked/Rel-16/23_series/23284/5dadcfbae18c4b3f91ea3a5e84d0a47a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5b644441ba794a28aa255c765b4e401c5a698e2bdc8fdaf7e2d7804dbde7fae +size 38188 diff --git a/marked/Rel-16/23_series/23284/605ad256780bc1b6022dfb65a6e24a3b_img.jpg b/marked/Rel-16/23_series/23284/605ad256780bc1b6022dfb65a6e24a3b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b8d56583d77f149efc9da07ab047ebfe31b19ff6 --- /dev/null +++ b/marked/Rel-16/23_series/23284/605ad256780bc1b6022dfb65a6e24a3b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a84fa7146aba805fe5184b1fea12cba67551b7b07aa486b7c29a17a9968afda7 +size 42109 diff --git a/marked/Rel-16/23_series/23284/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg b/marked/Rel-16/23_series/23284/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..184f003313d5a007edd940da83cb6256c3dca451 --- /dev/null +++ b/marked/Rel-16/23_series/23284/60a40901e77feeb97ab6cf9c6d9418c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9ddb9363a1141b687fdfb968d25ee664e081c0d0684ad5dbdf7af93af5ea1376 +size 189830 diff --git a/marked/Rel-16/23_series/23284/64323b705244afc70bf77babdacb6ce5_img.jpg b/marked/Rel-16/23_series/23284/64323b705244afc70bf77babdacb6ce5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..702c84f39823e0721c8d775decfe486a6852bafe --- /dev/null +++ b/marked/Rel-16/23_series/23284/64323b705244afc70bf77babdacb6ce5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6841a938961fc9a32b33db8ac3534a587e305e84b9ffac5fda77169a5b0c4eb0 +size 67025 diff --git a/marked/Rel-16/23_series/23284/6584b95e34ea1f0b67144aa841db0863_img.jpg b/marked/Rel-16/23_series/23284/6584b95e34ea1f0b67144aa841db0863_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7c0f2c1867f9eebe8dcd34575a5a2c399823c7ba --- /dev/null +++ b/marked/Rel-16/23_series/23284/6584b95e34ea1f0b67144aa841db0863_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce170fe59566b2a346aa9e119ca1f434bbc69554bf86fe8725ec3d57b3a6be87 +size 147789 diff --git a/marked/Rel-16/23_series/23284/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/marked/Rel-16/23_series/23284/65e8c0628536d6d4245e9ab46ba070c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cd011fcf3efcc006dd754f96a3d5385a318b8bf --- /dev/null +++ b/marked/Rel-16/23_series/23284/65e8c0628536d6d4245e9ab46ba070c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ec3d54d0f24e53e882cdc232811a439b3fb0b252c4119bd9be312d5da41b130 +size 188078 diff --git a/marked/Rel-16/23_series/23284/677bcb564410628b8b966ad87b394888_img.jpg b/marked/Rel-16/23_series/23284/677bcb564410628b8b966ad87b394888_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bc520a0c65c60a9b65602a7de078edd7cb9b70c --- /dev/null +++ b/marked/Rel-16/23_series/23284/677bcb564410628b8b966ad87b394888_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f04bae7380b4caf12e36651f63c4a940ee3ad9ae16f9f08990489dc32e1c0b5b +size 55983 diff --git a/marked/Rel-16/23_series/23284/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/marked/Rel-16/23_series/23284/694df81535f89c7bfb9ef0df6f130dc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7827eeef6c17237fdb4d5573c8e4184396cb8cf4 --- /dev/null +++ b/marked/Rel-16/23_series/23284/694df81535f89c7bfb9ef0df6f130dc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cb0c1022b1e45d5cea06830f72123ab84a8faada396d5bf10e72c1af5890ba91 +size 171000 diff --git a/marked/Rel-16/23_series/23284/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/marked/Rel-16/23_series/23284/6ca05954842b17f14dfd52f26b9d43d2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b505a589743e8a0eb4820d67b7d171265201a32 --- /dev/null +++ b/marked/Rel-16/23_series/23284/6ca05954842b17f14dfd52f26b9d43d2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9cf052d0f6227cc514b41d7e1acff09caf497651eb140d62fc200891c161d13d +size 46782 diff --git a/marked/Rel-16/23_series/23284/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/23_series/23284/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8f611d815827a315fee665f3b54a57dc72dc3220 --- /dev/null +++ b/marked/Rel-16/23_series/23284/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1bce8988a9e2b3c047639772ed3d560ec7ff7d6822ff04cc63f39c49a87df6bd +size 57075 diff --git a/marked/Rel-16/23_series/23284/719ef0f734259484038b2434e5dc3f24_img.jpg b/marked/Rel-16/23_series/23284/719ef0f734259484038b2434e5dc3f24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc92421a14c1fcff61d72e3cca8ed13a16816881 --- /dev/null +++ b/marked/Rel-16/23_series/23284/719ef0f734259484038b2434e5dc3f24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c4541317ce840ee33c99d76cb797be22e0d8ba2e4c460eecc92c86cc2b916d29 +size 66226 diff --git a/marked/Rel-16/23_series/23284/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg b/marked/Rel-16/23_series/23284/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77464616bdf08f5766446b97a9ab28c0a722887f --- /dev/null +++ b/marked/Rel-16/23_series/23284/74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37e628d5ed3c855a9e2b7c728f7c126f942e33086ba37e2da4b212e562bb6280 +size 48210 diff --git a/marked/Rel-16/23_series/23284/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-16/23_series/23284/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..035c795d2a0d77cc1507646574e0c89e0c04fd76 --- /dev/null +++ b/marked/Rel-16/23_series/23284/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2627e280543a4a28dc570c71710d4b845851bcc1e2eb2e22790c148f3efa7f0a +size 97747 diff --git a/marked/Rel-16/23_series/23284/7722d62e33dcc894cc8555e9474c5606_img.jpg b/marked/Rel-16/23_series/23284/7722d62e33dcc894cc8555e9474c5606_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0cc4223073b4353ac042591818d3c0690ae1adbe --- /dev/null +++ b/marked/Rel-16/23_series/23284/7722d62e33dcc894cc8555e9474c5606_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c113bd3e3f90663c95279058607570bf241044c796133e94feaed9156d8b2346 +size 74938 diff --git a/marked/Rel-16/23_series/23284/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/marked/Rel-16/23_series/23284/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c92e4e5453638c910a214111f662fd35d5bbcdb8 --- /dev/null +++ b/marked/Rel-16/23_series/23284/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:090fe3533343fd166c0879c3c6dbbd60523db3cd7f7b324ead44ed30a984e058 +size 150073 diff --git a/marked/Rel-16/23_series/23284/79aaab5889060cf8264226764a109cdb_img.jpg b/marked/Rel-16/23_series/23284/79aaab5889060cf8264226764a109cdb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6209cafb488e5c91522bb5506d9d36e47450ad1b --- /dev/null +++ b/marked/Rel-16/23_series/23284/79aaab5889060cf8264226764a109cdb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e90abe25a3c723cfd1a7813fa5a9e46c66a5d7519af5814adec5e6d2e99e0520 +size 51288 diff --git a/marked/Rel-16/23_series/23284/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/marked/Rel-16/23_series/23284/79e1709a7317ead45379cbb8ff3ba802_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7720bedb7bbd0fcbf8ef6f2730707bdca1914794 --- /dev/null +++ b/marked/Rel-16/23_series/23284/79e1709a7317ead45379cbb8ff3ba802_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:de8685ed01ca09917bbeeb1a63dcadae3941bbeeacd2fa5c26ccc3aa07d8846f +size 193460 diff --git a/marked/Rel-16/23_series/23284/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/23_series/23284/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0324ce068f6b350676f3bba8ae14274a1bdbcfd --- /dev/null +++ b/marked/Rel-16/23_series/23284/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e555e4442785d0a54f12bef42dd12f856add3fe07256796a4dd7466b2f48eb6d +size 75746 diff --git a/marked/Rel-16/23_series/23284/7e74ac663f3e644b589ed28f5fd29398_img.jpg b/marked/Rel-16/23_series/23284/7e74ac663f3e644b589ed28f5fd29398_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cc79ce3f27364839c13242368aac888b5f860eb9 --- /dev/null +++ b/marked/Rel-16/23_series/23284/7e74ac663f3e644b589ed28f5fd29398_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8be6979752d01c7206b64709b32d060546425f116c15771631b03ebc6c2663bc +size 71168 diff --git a/marked/Rel-16/23_series/23284/7f17c430b9598e4d748a8041457810b3_img.jpg b/marked/Rel-16/23_series/23284/7f17c430b9598e4d748a8041457810b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..634e0aa2b4348d73bbcfc3abd3734507b6f6b371 --- /dev/null +++ b/marked/Rel-16/23_series/23284/7f17c430b9598e4d748a8041457810b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e715431b1577919f505ae34b250c514db551138d00a578effe10c2dacf94e4ce +size 67402 diff --git a/marked/Rel-16/23_series/23284/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23284/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f5be78686aab40d02406a650407dc4b6040edf8 --- /dev/null +++ b/marked/Rel-16/23_series/23284/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24d00d9925e1b5c184ae8d0f017d17acae1790a5c21c350ec0093d4c467a292f +size 56173 diff --git a/marked/Rel-16/23_series/23284/820515db47ded68f5e0b625f4ec7d2c1_img.jpg b/marked/Rel-16/23_series/23284/820515db47ded68f5e0b625f4ec7d2c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3040c48f1320dce98b7aaf9dd15dfc973b04fdc --- /dev/null +++ b/marked/Rel-16/23_series/23284/820515db47ded68f5e0b625f4ec7d2c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:34e58da4eede34c22a94c49a084a852e9633cf689ae2b0951fb11b6c1c7718f7 +size 244014 diff --git a/marked/Rel-16/23_series/23284/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/marked/Rel-16/23_series/23284/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9b0c68323d7d2a8edbfb5d66ae6f8fe1bb9b68fc --- /dev/null +++ b/marked/Rel-16/23_series/23284/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05ea17997608cdf4597dc5cdd3e646b981d88167d69f0ccd89b61b70a05872f6 +size 120532 diff --git a/marked/Rel-16/23_series/23284/8658cfab6a458b4a80ab2e384c61ff89_img.jpg b/marked/Rel-16/23_series/23284/8658cfab6a458b4a80ab2e384c61ff89_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1c92a245cec6a0964c49cb1ef411c1c9a933581e --- /dev/null +++ b/marked/Rel-16/23_series/23284/8658cfab6a458b4a80ab2e384c61ff89_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a224d21a98455aaf8e5c401cfdcdbedaf03b0a5a99f5cd7ccc13752cb278b306 +size 47242 diff --git a/marked/Rel-16/23_series/23284/88b0f3f4393228e9ea4d6542aef7c399_img.jpg b/marked/Rel-16/23_series/23284/88b0f3f4393228e9ea4d6542aef7c399_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cdd0d8a55b79cc28a87f9c63288085e9d5e63ed3 --- /dev/null +++ b/marked/Rel-16/23_series/23284/88b0f3f4393228e9ea4d6542aef7c399_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29632e17c7007bc385b39554317c0b8ced07f4dcff61f8edbfde9bf1e3090ed6 +size 46562 diff --git a/marked/Rel-16/23_series/23284/8e80de0cac529b2c3775d677c5203133_img.jpg b/marked/Rel-16/23_series/23284/8e80de0cac529b2c3775d677c5203133_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a327ed2ccfee2f96e58d9e30631c7bc1d23141a2 --- /dev/null +++ b/marked/Rel-16/23_series/23284/8e80de0cac529b2c3775d677c5203133_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:97ea6d18e675b7dd74f9d5945672d301491668c11915c4426b4d266567c53357 +size 165401 diff --git a/marked/Rel-16/23_series/23284/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23284/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..036f0d09e88bb865f96ade7806bb421efd44bc14 --- /dev/null +++ b/marked/Rel-16/23_series/23284/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:debbaf11b13b44db44ffff45eb5f4d8baf874728a435393143f62adb2c9f044f +size 56834 diff --git a/marked/Rel-16/23_series/23284/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/marked/Rel-16/23_series/23284/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..51cfd60ffeb8ebd5d86c7b396a9fd523a1aa3f91 --- /dev/null +++ b/marked/Rel-16/23_series/23284/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a44d5f40d4c7a4df1c9eef8ff1e023de54788562e23f0f7e59f711cf564d910 +size 145091 diff --git a/marked/Rel-16/23_series/23284/933ecd14c858bf3fc919222d8e357bc8_img.jpg b/marked/Rel-16/23_series/23284/933ecd14c858bf3fc919222d8e357bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bc31adf3ef94d858e4e435535c77705e3feacc9d --- /dev/null +++ b/marked/Rel-16/23_series/23284/933ecd14c858bf3fc919222d8e357bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9611bc9472c8ed92041e180dcb2afda2dac75cfbce01ee1941cee82882b8f8ae +size 47141 diff --git a/marked/Rel-16/23_series/23284/997233d405f0d4b89ddeb7683e047f66_img.jpg b/marked/Rel-16/23_series/23284/997233d405f0d4b89ddeb7683e047f66_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4060cf78c41ef86ff1cdfd1351f17030cb88f9f --- /dev/null +++ b/marked/Rel-16/23_series/23284/997233d405f0d4b89ddeb7683e047f66_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:184b2211eb55a43bd6cffad804a96aae99f8a67ed3e303b38a70622e01fd69aa +size 198897 diff --git a/marked/Rel-16/23_series/23284/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg b/marked/Rel-16/23_series/23284/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d455255560e267205e2c6f57dd0f2900eef221fd --- /dev/null +++ b/marked/Rel-16/23_series/23284/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e7b6ebf91277596a00c2aeaab1c2745f07d1178a8b2b1f02c09107ba549bc41d +size 99332 diff --git a/marked/Rel-16/23_series/23284/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/marked/Rel-16/23_series/23284/9b1ec0090070bdf52ea28763b8d52477_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b315a4f144dfcb0c2ddf5127b3952c6ac9cb1aca --- /dev/null +++ b/marked/Rel-16/23_series/23284/9b1ec0090070bdf52ea28763b8d52477_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:53cf9fcd96225f3d6de5db8111607994732ca6ed8c9e849ad8308dad78f99a36 +size 165046 diff --git a/marked/Rel-16/23_series/23284/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-16/23_series/23284/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9babc0c61ec44854b0a423acf5f2b80479b3a3f8 --- /dev/null +++ b/marked/Rel-16/23_series/23284/9c45844d796e85ae05505870a54e4eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f877c3709114ec842e8aacedba47b7693f875a1b43ff275ea9f9c1de5ce6d88f +size 71107 diff --git a/marked/Rel-16/23_series/23284/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/marked/Rel-16/23_series/23284/9e8ebf03cae78f4f81b697548c2d7250_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a72b345b872a2d0f62b5cf13ce5bfce70e2fddc --- /dev/null +++ b/marked/Rel-16/23_series/23284/9e8ebf03cae78f4f81b697548c2d7250_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8f44aa9c9bf07c7d558910c87b4476150a724523d833fd836f9e3429bbf7e084 +size 71576 diff --git a/marked/Rel-16/23_series/23284/9ed248b025d766251d58be10b01a1cc0_img.jpg b/marked/Rel-16/23_series/23284/9ed248b025d766251d58be10b01a1cc0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42256b8247ba845661944719a4a018ca19556dd4 --- /dev/null +++ b/marked/Rel-16/23_series/23284/9ed248b025d766251d58be10b01a1cc0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60a84f4d168848017c5926ec64234c6c44beb6c3a93a3adc3a7460fa21dc016f +size 74184 diff --git a/marked/Rel-16/23_series/23284/9f51a76cae7309a296cbc6997941eb3f_img.jpg b/marked/Rel-16/23_series/23284/9f51a76cae7309a296cbc6997941eb3f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..825fa64ba26a8a20fbeab75c82549c661d2bcdab --- /dev/null +++ b/marked/Rel-16/23_series/23284/9f51a76cae7309a296cbc6997941eb3f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c00b88af895ecf019458fab8dc55466a28dc4b7c675e07c1ca2d60f9c18a697b +size 75608 diff --git a/marked/Rel-16/23_series/23284/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23284/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8ca33b99eb262f161883c0158651cb29b7893551 --- /dev/null +++ b/marked/Rel-16/23_series/23284/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bf9d200fdd728c9a9abf4d7b8e0d5e26d5b792ca2ffb0712064d3aa3ab38f440 +size 75922 diff --git a/marked/Rel-16/23_series/23284/9f862801bce82634d3b5a1e0a195a799_img.jpg b/marked/Rel-16/23_series/23284/9f862801bce82634d3b5a1e0a195a799_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e44e14b0ece1762f90e78859fc8bec6dd8b2f4b --- /dev/null +++ b/marked/Rel-16/23_series/23284/9f862801bce82634d3b5a1e0a195a799_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e238b3ff3c9fcf9fd40c620e468ef6fb57acb36e10c9ec3684790598fa84ba11 +size 71621 diff --git a/marked/Rel-16/23_series/23284/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/marked/Rel-16/23_series/23284/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22758990bd35da1b79b9e0e262c2c94751dcd0ba --- /dev/null +++ b/marked/Rel-16/23_series/23284/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:407e29bfc648cede57d26fd8ea0abb13cb4006addd82a27a11a104948ebe7e6d +size 160287 diff --git a/marked/Rel-16/23_series/23284/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/marked/Rel-16/23_series/23284/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..664e009ad8487e6a877424ba30205b1dd8389e6d --- /dev/null +++ b/marked/Rel-16/23_series/23284/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57203e970b1bf13f99f38e219f4a64cd24a99cbe0a34a981435cab870f2608f0 +size 218396 diff --git a/marked/Rel-16/23_series/23284/a5184899f915014fa38608754efcc9c7_img.jpg b/marked/Rel-16/23_series/23284/a5184899f915014fa38608754efcc9c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1bc7b2b61c3602b9e0769121fe71ace626cea00f --- /dev/null +++ b/marked/Rel-16/23_series/23284/a5184899f915014fa38608754efcc9c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b07738c94791b59d3e1f1c5096b4123253ca09d16ac968eb4e3eae7428be808 +size 61593 diff --git a/marked/Rel-16/23_series/23284/aa6e28822419dba9f22129fee66c9c4c_img.jpg b/marked/Rel-16/23_series/23284/aa6e28822419dba9f22129fee66c9c4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b0aee9e69fa1933d3e209af992519ecef4a070a6 --- /dev/null +++ b/marked/Rel-16/23_series/23284/aa6e28822419dba9f22129fee66c9c4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8fa67fb7ca4a14c2b0604f623bfc8fd7cbdbd705a023db9618bec9dec23db73 +size 82781 diff --git a/marked/Rel-16/23_series/23284/aa81b9b80bd1e3d723922b3a033564a2_img.jpg b/marked/Rel-16/23_series/23284/aa81b9b80bd1e3d723922b3a033564a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b1575d43b011e1d28b0347acb7c35e3e096a4650 --- /dev/null +++ b/marked/Rel-16/23_series/23284/aa81b9b80bd1e3d723922b3a033564a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:481867455c0a9824bb0e99c4ac6e433b6174bfda6afeb73d843367c430718d78 +size 58949 diff --git a/marked/Rel-16/23_series/23284/ad555483986d7170a46ce72d164b5bc8_img.jpg b/marked/Rel-16/23_series/23284/ad555483986d7170a46ce72d164b5bc8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..249f23a59d2ac5623256d71181a10ac82f086545 --- /dev/null +++ b/marked/Rel-16/23_series/23284/ad555483986d7170a46ce72d164b5bc8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:994f857e22be9aa91d6458e2b8070bc8dafe17bb4dbd3114a36d81c7dbd11379 +size 54072 diff --git a/marked/Rel-16/23_series/23284/aeb2a26a07219661191294dba528067a_img.jpg b/marked/Rel-16/23_series/23284/aeb2a26a07219661191294dba528067a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3135e3521cf4e4cdfad719c58756ae8c08060bdb --- /dev/null +++ b/marked/Rel-16/23_series/23284/aeb2a26a07219661191294dba528067a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0653b919aa86700ab3b7f0ef9caed6011427c1a021d1338d34c4da76e66450a5 +size 189227 diff --git a/marked/Rel-16/23_series/23284/b033fab424e6df728345cfa04df83fcc_img.jpg b/marked/Rel-16/23_series/23284/b033fab424e6df728345cfa04df83fcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..296a1fd44335394719aefc92bdaffd5803ca146f --- /dev/null +++ b/marked/Rel-16/23_series/23284/b033fab424e6df728345cfa04df83fcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f31f137e21d4115e2e0a151b83f5f9982760d11b4c46cea012e811e53110adfb +size 137617 diff --git a/marked/Rel-16/23_series/23284/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23284/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..550d29b61d5f7567eb190d4e753125a3a3836854 --- /dev/null +++ b/marked/Rel-16/23_series/23284/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e794ad74e693ef02b4950efedb40d362ad71e2d6e997642f040af23f394fa362 +size 145694 diff --git a/marked/Rel-16/23_series/23284/b63f41ca262d8ce9ef8affb62607f32b_img.jpg b/marked/Rel-16/23_series/23284/b63f41ca262d8ce9ef8affb62607f32b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c58b940a29af556c2f51174811a59b30eca8674 --- /dev/null +++ b/marked/Rel-16/23_series/23284/b63f41ca262d8ce9ef8affb62607f32b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2ae2eed8a3358714e9fdc345fa5f93fd0d5f6296b5eede8f8af9a33eec014cd0 +size 67797 diff --git a/marked/Rel-16/23_series/23284/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/Rel-16/23_series/23284/bd671b21db63e6fdb2196e9b18502aac_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5522a0475badcb92e4f785dee85f1ade2f2d21f9 --- /dev/null +++ b/marked/Rel-16/23_series/23284/bd671b21db63e6fdb2196e9b18502aac_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6d590eed65344f02b820d1818dad04ae2c1acbb2fbfe1f90a5cc111e9bfebc29 +size 73327 diff --git a/marked/Rel-16/23_series/23284/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/marked/Rel-16/23_series/23284/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..22c57a40e8c8a5da2c255822cde72d4de885cb9c --- /dev/null +++ b/marked/Rel-16/23_series/23284/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0bb76b6a812b03cdcf16b79958160f9e57acf1ec6a1261452e5b6e82dbb79c75 +size 205607 diff --git a/marked/Rel-16/23_series/23284/c07e21a8d65991db04263322f859c94f_img.jpg b/marked/Rel-16/23_series/23284/c07e21a8d65991db04263322f859c94f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4644a1cba8ca6d35d2d549f91e3ec29021a54d6e --- /dev/null +++ b/marked/Rel-16/23_series/23284/c07e21a8d65991db04263322f859c94f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a6501b99e80f2d6bd7e7b6a4572c458141c35a6dab69eff3ae9bc4a6fb68f6a7 +size 78892 diff --git a/marked/Rel-16/23_series/23284/cd48273072c5c3a23e11fde892d1b6b6_img.jpg b/marked/Rel-16/23_series/23284/cd48273072c5c3a23e11fde892d1b6b6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d0a208eac0f1698d335606a6a7419b92acadd6ee --- /dev/null +++ b/marked/Rel-16/23_series/23284/cd48273072c5c3a23e11fde892d1b6b6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:197bfe14d8856d10bbbfe61a102e0102bec069532d76993d6d41cee0f7b1c251 +size 38325 diff --git a/marked/Rel-16/23_series/23284/cf8bd014a50b7c69435e804f67f9617f_img.jpg b/marked/Rel-16/23_series/23284/cf8bd014a50b7c69435e804f67f9617f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..26c43f26257430a2592ea0b592bd8300e5f5b584 --- /dev/null +++ b/marked/Rel-16/23_series/23284/cf8bd014a50b7c69435e804f67f9617f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04eeb4a1698711f265038dcd69ae92e196efbdfc2a0a61ba420d81b8637aded6 +size 32263 diff --git a/marked/Rel-16/23_series/23284/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg b/marked/Rel-16/23_series/23284/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..37f3db8ba6bdade49b3d40c6a9de8cccffe47cac --- /dev/null +++ b/marked/Rel-16/23_series/23284/cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:37fba5b7f51496a9d0c508fca549137f37d2c89955023ec28d8d616c53c25b51 +size 183509 diff --git a/marked/Rel-16/23_series/23284/d6c377ae3e619ff992bd3647dbf43593_img.jpg b/marked/Rel-16/23_series/23284/d6c377ae3e619ff992bd3647dbf43593_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7f448b002714910a13201251275a2b4230456dfc --- /dev/null +++ b/marked/Rel-16/23_series/23284/d6c377ae3e619ff992bd3647dbf43593_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:918a20cb63104e32d0a9fb62d4d2a5dfc6544ecf26ec1490dd828f41878fe30a +size 42780 diff --git a/marked/Rel-16/23_series/23284/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg b/marked/Rel-16/23_series/23284/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbc2b027d8471c4e53bd86b2cf7c18a833ca9558 --- /dev/null +++ b/marked/Rel-16/23_series/23284/dc1f232cfd39be5c20b21374ad4c04c0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8cebca5a1ec32ff795f97a8e90a058fed704c48124be0bfb1c50619f4f910742 +size 46782 diff --git a/marked/Rel-16/23_series/23284/dd380ccd5aca1151074fede04826f1a4_img.jpg b/marked/Rel-16/23_series/23284/dd380ccd5aca1151074fede04826f1a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..67379f38ae0a9468e109d1ec29bf89c698dbaf24 --- /dev/null +++ b/marked/Rel-16/23_series/23284/dd380ccd5aca1151074fede04826f1a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:82ccc0624714bb9dff408db781879f6d4899d7ae6e03b2c8672696c9d6afe270 +size 47316 diff --git a/marked/Rel-16/23_series/23284/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23284/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5a542b87b13d11a9443cbec245be1b8bf69f4695 --- /dev/null +++ b/marked/Rel-16/23_series/23284/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9172814bb97b9807985e495905cf2cdbdace7c2fa8d40634b8f1fb941fc2e19e +size 155886 diff --git a/marked/Rel-16/23_series/23284/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/marked/Rel-16/23_series/23284/ddee3e67e0dfc22e25188fa635a19558_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9522a7f5d79b8101b569449867c8424beb6471f7 --- /dev/null +++ b/marked/Rel-16/23_series/23284/ddee3e67e0dfc22e25188fa635a19558_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aaa34ece5831db9583a0fe6299d6c7bda1f282c70d6b9036df5fe6dd6cd7a3c4 +size 167013 diff --git a/marked/Rel-16/23_series/23284/e05b36c0d46549e681ce6581422c66b2_img.jpg b/marked/Rel-16/23_series/23284/e05b36c0d46549e681ce6581422c66b2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e4626ceb24602a622bdeb907da7afb86807a4af0 --- /dev/null +++ b/marked/Rel-16/23_series/23284/e05b36c0d46549e681ce6581422c66b2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a97d219bdfe9bb16a3611a85680ea7036772125c0d28bcc1bbc3b85c3cef1399 +size 56246 diff --git a/marked/Rel-16/23_series/23284/e417ae35ab07134888be901c201d54cd_img.jpg b/marked/Rel-16/23_series/23284/e417ae35ab07134888be901c201d54cd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..634513d8dad5f26b6feefd21ba582d6baa40e044 --- /dev/null +++ b/marked/Rel-16/23_series/23284/e417ae35ab07134888be901c201d54cd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:355d95e42edfa41edac734ffa2b8fe5c13c8a0ff71420340cad4cc58b999a66b +size 75085 diff --git a/marked/Rel-16/23_series/23284/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-16/23_series/23284/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..337d103240d8fa17359c4b53452ceb7d8b9564a9 --- /dev/null +++ b/marked/Rel-16/23_series/23284/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ab26dde54d1e44af45b8569c7efca02f6dfbccd8e1031d3e06a315db651ece81 +size 46220 diff --git a/marked/Rel-16/23_series/23284/e90b25c8d90cadc3f76c376701cf27ed_img.jpg b/marked/Rel-16/23_series/23284/e90b25c8d90cadc3f76c376701cf27ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a1692d15271a63f25ee21806c9bba1e621cce63 --- /dev/null +++ b/marked/Rel-16/23_series/23284/e90b25c8d90cadc3f76c376701cf27ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1717a901f8784cabead64a588073f34dcb197bafb4a4af9f6675c4d3e281efce +size 64861 diff --git a/marked/Rel-16/23_series/23284/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23284/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b298ccd31e7bca74bcd00a25efff1041c24ec761 --- /dev/null +++ b/marked/Rel-16/23_series/23284/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:579715028113b4b9cc20d4df3518d7ade4b95f05d88c5b7ae63489c058b0b35d +size 132806 diff --git a/marked/Rel-16/23_series/23284/f2486d5031b55e42b300903a716b0a00_img.jpg b/marked/Rel-16/23_series/23284/f2486d5031b55e42b300903a716b0a00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d238890f1d01d6295a9b1fdf40bf756c949e3d41 --- /dev/null +++ b/marked/Rel-16/23_series/23284/f2486d5031b55e42b300903a716b0a00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:19eb0b9644ec65497b43a04176952725715867fe8915cbcfb6a2e5aa009acde5 +size 64379 diff --git a/marked/Rel-16/23_series/23284/f468e577645d646f5157ce3eefb4ed96_img.jpg b/marked/Rel-16/23_series/23284/f468e577645d646f5157ce3eefb4ed96_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9041d681709da136256a24cfd806a981b801ea5f --- /dev/null +++ b/marked/Rel-16/23_series/23284/f468e577645d646f5157ce3eefb4ed96_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5b6478dcb6a0cbb189a948bc8d697274bb4298753fb7d4dfc8e42c171d2b82c8 +size 209110 diff --git a/marked/Rel-16/23_series/23284/f5deee2f3301ee351c4008283ffafbb3_img.jpg b/marked/Rel-16/23_series/23284/f5deee2f3301ee351c4008283ffafbb3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c83db0797b9921f54b5788588d388d02f17c9e8 --- /dev/null +++ b/marked/Rel-16/23_series/23284/f5deee2f3301ee351c4008283ffafbb3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2d1c7bf10ce3be37e82b5f5bfc579a044a8c3fc87c68663ee3f41620273cb7f4 +size 119870 diff --git a/marked/Rel-16/23_series/23284/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/marked/Rel-16/23_series/23284/f61d0925551545b5938b3a4d1bbf63c3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dcc90fb44746c06cf717aadaa4168fe96487cc32 --- /dev/null +++ b/marked/Rel-16/23_series/23284/f61d0925551545b5938b3a4d1bbf63c3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f2d14327ae6080c2ac054259d24e9b9b0436166b5c64813f003fb33ab8e25359 +size 93449 diff --git a/marked/Rel-16/23_series/23284/f76f0f5dfff2511b51f6b875867c029f_img.jpg b/marked/Rel-16/23_series/23284/f76f0f5dfff2511b51f6b875867c029f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6e4cfb99c8f656221961d35b1b8163cbf51037d0 --- /dev/null +++ b/marked/Rel-16/23_series/23284/f76f0f5dfff2511b51f6b875867c029f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e636029e3d84d8238b20957a38cc59afb8915a15d22faafa293cd43b086cda87 +size 61358 diff --git a/marked/Rel-16/23_series/23284/f97535cdaa4fe017f4659512f4f78028_img.jpg b/marked/Rel-16/23_series/23284/f97535cdaa4fe017f4659512f4f78028_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..686ec51c0a408bdff14ff65079929d929a0aac03 --- /dev/null +++ b/marked/Rel-16/23_series/23284/f97535cdaa4fe017f4659512f4f78028_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:926ff442876646a25e4c790ec614fdb6b7f494cda9eae3d38cada0f881f73883 +size 231519 diff --git a/marked/Rel-16/23_series/23284/fd3cbb53e991f8209ba17b398f426e13_img.jpg b/marked/Rel-16/23_series/23284/fd3cbb53e991f8209ba17b398f426e13_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3a8396f273c4af8a66065a8f3995be1f90b938a6 --- /dev/null +++ b/marked/Rel-16/23_series/23284/fd3cbb53e991f8209ba17b398f426e13_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1639c2c345ee341f0b937618875083c6598f48db48ff54711f9f4403a1161056 +size 118509 diff --git a/marked/Rel-16/23_series/23284/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/marked/Rel-16/23_series/23284/ff0952ef692c9d960ce5f6708bcc9711_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e692d8919748faa24ab8c00e87c91c8d99a5cea2 --- /dev/null +++ b/marked/Rel-16/23_series/23284/ff0952ef692c9d960ce5f6708bcc9711_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:abc16d1f00bf3c217606dbcdbdd0212d32bbd0e65ec31300d0030f47f4af20bc +size 56814 diff --git a/marked/Rel-16/23_series/23284/ff7977984f2552f326b2089d7595fff3_img.jpg b/marked/Rel-16/23_series/23284/ff7977984f2552f326b2089d7595fff3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ae7a551a7b76635d4f4b0f9cd5a2b67b17a04907 --- /dev/null +++ b/marked/Rel-16/23_series/23284/ff7977984f2552f326b2089d7595fff3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0748ed6632909e87148d34752ac885d6a0a6b0f29772c93a2a901bb35705671 +size 57882 diff --git a/marked/Rel-16/23_series/23284/raw.md b/marked/Rel-16/23_series/23284/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..985337d4b0d895b0eebc75d1bb41287cc4a5ae9f --- /dev/null +++ b/marked/Rel-16/23_series/23284/raw.md @@ -0,0 +1,6069 @@ +# Contents + +| | | +|---------------------------------------------------------------------------------|----| +| Foreword ..... | 11 | +| 1 Scope..... | 12 | +| 2 References..... | 12 | +| 3 Definitions, symbols and abbreviations..... | 13 | +| 3.1 Definitions..... | 13 | +| 3.2 Symbols..... | 13 | +| 3.3 Abbreviations ..... | 13 | +| 4 Main Concepts ..... | 13 | +| 4.1 General ..... | 13 | +| 4.2 LCLS Negotiation ..... | 14 | +| 4.2.1 General concept of LCLS negotiation ..... | 14 | +| 4.2.2 (void) ..... | 18 | +| 4.2.3 (void) ..... | 18 | +| 4.2.4 General concept of LCLS Configuration Preference Modification..... | 18 | +| 4.3 LCLS Call Leg Correlation ..... | 19 | +| 4.3.1 General ..... | 19 | +| 4.3.2 Optional Intra-Network Call Detection ..... | 20 | +| 4.3.2.1 General..... | 20 | +| 4.3.2.2 Intra-Network Call Detection within the tMSC server..... | 20 | +| 4.3.2.3 Intra-Network Call Detection within the tBSS ..... | 20 | +| 4.3.3 Optional Intra-BSS Call Detection ..... | 20 | +| 4.3.3.1 General..... | 20 | +| 4.3.3.2 Intra-BSS Call Detection within the tMSC server..... | 20 | +| 4.3.3.3 Intra-BSS Call Detection within the tBSS..... | 21 | +| 4.4 LCLS Connection Control ..... | 21 | +| 4.5 LCLS Status Reporting ..... | 22 | +| 4.5.1 LCLS BSS Status between BSS and Core Network ..... | 22 | +| 4.5.2 LCLS Status within the Core Network..... | 22 | +| 4.6 User Plane when LCLS is Active..... | 23 | +| 4.6.1 General ..... | 23 | +| 4.6.2 LCLS Configuration ..... | 23 | +| 5 General Circuit Switched Core Network Domain Architecture ..... | 23 | +| 6 Call Establishment ..... | 24 | +| 6.1 Basic Mobile Originating Call ..... | 24 | +| 6.1.1 Basic Mobile Originating Call with BICC based CS core network ..... | 24 | +| 6.1.1.1 General..... | 24 | +| 6.1.1.2 Initial Addressing..... | 24 | +| 6.1.1.3 Access Bearer Assignment ..... | 24 | +| 6.1.1.3.1 Assignment performed after LCLS Negotiation through Core Network..... | 24 | +| 6.1.1.3.2 Assignment performed before LCLS Negotiation ..... | 24 | +| 6.1.1.3.3 oBSS behavior..... | 24 | +| 6.1.1.4 Backward LCLS Negotiation..... | 25 | +| 6.1.1.5 LCLS Through-Connection ..... | 25 | +| 6.1.1.6 LCLS Status Reporting..... | 25 | +| 6.1.1.7 MGW/User plane..... | 25 | +| 6.1.2 Basic Mobile Originating Call with SIP-I based CS core network ..... | 26 | +| 6.1.2.1 General..... | 26 | +| 6.1.2.2 Initial Addressing..... | 26 | +| 6.1.2.3 Access Bearer Assignment ..... | 26 | +| 6.1.2.4 Backward LCLS Negotiation..... | 26 | +| 6.1.2.5 LCLS Through-Connection ..... | 26 | +| 6.1.2.6 LCLS Status Reporting..... | 26 | +| 6.1.2.7 MGW/User plane..... | 26 | +| 6.2 Basic Mobile Terminating Call..... | 26 | +| 6.2.1 Basic Mobile Terminating Call with BICC based CS core network..... | 26 | + +| | | | +|-----------|-----------------------------------------------------------------------------------------------------------|----| +| 6.2.1.1 | General..... | 26 | +| 6.2.1.2 | Actions at Intermediate Nodes (including GMSC)..... | 27 | +| 6.2.1.2.1 | Initial Addressing ..... | 27 | +| 6.2.1.2.2 | Backward LCLS Negotiation ..... | 27 | +| 6.2.1.2.3 | Through-Connection ..... | 27 | +| 6.2.1.2.4 | LCLS Status Reporting within CN..... | 27 | +| 6.2.1.2.5 | MGW/User plane ..... | 27 | +| 6.2.1.3 | Actions at Terminating Call side ..... | 28 | +| 6.2.1.3.1 | Initial Addressing ..... | 28 | +| 6.2.1.3.2 | Backward LCLS Negotiation ..... | 28 | +| 6.2.1.3.3 | Access Bearer Assignment..... | 28 | +| 6.2.1.3.4 | LCLS Through-Connection..... | 28 | +| 6.2.1.3.5 | LCLS Status Reporting ..... | 29 | +| 6.2.1.3.6 | MGW/User plane ..... | 29 | +| 6.2.2 | Basic Mobile Terminating Call with SIP-I based CS core network..... | 29 | +| 6.2.2.1 | General..... | 29 | +| 6.2.2.2 | Actions at Intermediate Nodes (including GMSC)..... | 29 | +| 6.2.2.2.1 | Initial Addressing ..... | 29 | +| 6.2.2.2.2 | Backward LCLS Negotiation ..... | 29 | +| 6.2.2.2.3 | Through-Connection ..... | 29 | +| 6.2.2.2.4 | LCLS Status Reporting within CN..... | 29 | +| 6.2.2.2.5 | MGW/User plane ..... | 29 | +| 6.2.2.3 | Actions at Terminating Call side ..... | 29 | +| 6.2.2.3.1 | Initial Addressing ..... | 29 | +| 6.2.2.3.2 | Backward LCLS Negotiation ..... | 29 | +| 6.2.2.3.3 | Access Bearer Assignment..... | 30 | +| 6.2.2.3.4 | LCLS Through-Connection..... | 30 | +| 6.2.2.3.5 | LCLS Status Reporting ..... | 30 | +| 6.2.2.3.6 | MGW/User plane ..... | 30 | +| 6.3 | Basic Mobile to Mobile End to End Call Examples ..... | 30 | +| 6.3.1 | Basic Call Establishment Connection Model for LCLS..... | 30 | +| 6.3.2 | LCLS established, Basic Call Example with BICC based CS core network, forward bearer establishment ..... | 31 | +| 6.3.3 | LCLS not established, Basic Call Example with BICC based CS core network ..... | 36 | +| 6.3.4 | LCLS established, Basic Call Example with SIP-I based CS core network ..... | 38 | +| 6.3.5 | LCLS established, Basic Call Example with BICC based CS core network, backward bearer establishment ..... | 44 | +| 7 | Call Clearing and LCLS Break/Re-establishment ..... | 47 | +| 7.1 | Call Clearing ..... | 47 | +| 7.2 | LCLS Break..... | 47 | +| 7.2.1 | MSC server Initiated..... | 47 | +| 7.2.1.1 | Principles ..... | 47 | +| 7.2.1.2 | MSC server actions..... | 48 | +| 7.2.1.3 | GMSC server actions ..... | 48 | +| 7.2.1.4 | BSS actions ..... | 48 | +| 7.2.2 | BSS Initiated..... | 49 | +| 7.2.2.1 | Principles ..... | 49 | +| 7.2.2.2 | Immediate LCLS break..... | 49 | +| 7.2.2.2.1 | BSS actions ..... | 49 | +| 7.2.2.2.2 | MSC server actions ..... | 49 | +| 7.2.2.2.3 | GMSC server actions ..... | 49 | +| 7.2.2.3 | BSS Requesting LCLS Release from Core Network..... | 49 | +| 7.2.2.3.1 | BSS actions ..... | 49 | +| 7.2.2.3.2 | MSC server actions ..... | 50 | +| 7.2.2.3.3 | GMSC server actions ..... | 50 | +| 7.2.3 | Intermediate Node/GMSC Server Initiated ..... | 50 | +| 7.2.3.1 | Principles ..... | 50 | +| 7.2.3.2 | Intermediate Node/GMSC server actions ..... | 50 | +| 7.2.3.3 | MSC server actions..... | 50 | +| 7.2.3.4 | BSS actions ..... | 51 | +| 7.2.4 | LCLS Break Example Call Flows ..... | 51 | + +| | | | +|-------------|----------------------------------------------------------------------------------------|----| +| 7.2.4.1 | LCLS Break Connection Model for LCLS..... | 51 | +| 7.2.4.2 | MSC server Initiated..... | 52 | +| 7.2.4.3 | BSS Initiated, Immediate LCLS Break..... | 53 | +| 7.2.4.4 | BSS Initiated, LCLS Break requested from Core Network..... | 54 | +| 7.2.4.5 | Intermediate Node/GMSC Server Initiated ..... | 56 | +| 7.2.4.6 | MSC server Initiated when Access Side Termination is isolated in MGW..... | 58 | +| 7.3 | LCLS Re-establishment ..... | 59 | +| 7.3.1 | MSC server Initiated..... | 59 | +| 7.3.1.1 | Principles ..... | 59 | +| 7.3.1.2 | MSC server actions..... | 59 | +| 7.3.1.2.1 | LCLS re-establishment to the network side ..... | 59 | +| 7.3.1.2.2 | LCLS re-establishment to the BSS..... | 59 | +| 7.3.1.2.3 | LCLS Status update to the network side ..... | 59 | +| 7.3.1.3 | GMSC server actions ..... | 59 | +| 7.3.1.4 | BSS actions ..... | 60 | +| 7.3.2 | BSS Initiated..... | 60 | +| 7.3.3 | Intermediate Node / GMSC Server Initiated ..... | 60 | +| 7.3.3.1 | Principles ..... | 60 | +| 7.3.3.2 | Intermediate Node / GMSC server actions ..... | 60 | +| 7.3.3.3 | MSC server actions..... | 60 | +| 7.3.3.4 | BSS actions ..... | 61 | +| 7.3.4 | LCLS Re-establishment Example Call Flows..... | 61 | +| 7.3.4.1 | LCLS Re-establishment Connection Model for LCLS..... | 61 | +| 7.3.4.2 | MSC server Initiated Example Call Flow..... | 61 | +| 7.3.4.3 | Intermediate Node / GMSC Server Initiated Example Call Flow ..... | 63 | +| 7.3.4.4 | MSC server Initiated when Access Side Termination is isolated in MGW..... | 64 | +| 8 | Handover/Relocation ..... | 65 | +| 8.1 | UMTS to UMTS..... | 65 | +| 8.2 | UMTS to GSM..... | 66 | +| 8.2.1 | General ..... | 66 | +| 8.2.2 | Intra-MSC UMTS to GSM Handover ..... | 66 | +| 8.2.2.1 | Intra-MSC UMTS to GSM Handover that establishes Local Switching..... | 66 | +| 8.2.2.1.1 | General ..... | 66 | +| 8.2.2.1.2 | Relocation Required..... | 66 | +| 8.2.2.1.3 | Handover Request Acknowledge..... | 66 | +| 8.2.2.1.4 | Handover Complete..... | 66 | +| 8.2.2.1.5 | Example..... | 66 | +| 8.2.2.1.5.1 | Connection Model ..... | 66 | +| 8.2.2.1.5.2 | Basic Sequence for Intra-MSC UMTS to GSM Handover that establishes Local Switching... | 69 | +| 8.2.2.2 | Intra-MSC UMTS to GSM Handover that does not establish LCLS ..... | 70 | +| 8.2.3 | Inter-MSC UMTS to GSM Handover ..... | 70 | +| 8.2.3.1 | Inter-MSC UMTS to GSM Handover that establishes Local Switching..... | 70 | +| 8.2.3.1.1 | General ..... | 70 | +| 8.2.3.1.2 | MSC-1 / MGW-1 ..... | 70 | +| 8.2.3.1.2.1 | Relocation Required ..... | 70 | +| 8.2.3.1.2.1 | Relocation Required ..... | 70 | +| 8.2.3.1.2.2 | Handover Request Acknowledge ..... | 70 | +| 8.2.3.1.2.3 | Bearer establishment between MGW-1 and Target MGW ..... | 71 | +| 8.2.3.1.2.4 | MGW Flow Direction Control ..... | 71 | +| 8.2.3.1.2.5 | Relocation Command/Handover Detect..... | 71 | +| 8.2.3.1.2.6 | Handover Complete..... | 71 | +| 8.2.3.1.3 | Target MSC Server / Target MGW..... | 71 | +| 8.2.3.1.3.1 | Prepare Handover Request message and MGW selection..... | 71 | +| 8.2.3.1.3.2 | Handover Request Acknowledge ..... | 71 | +| 8.2.3.1.3.3 | Bearer establishment towards Target BSS ..... | 71 | +| 8.2.3.1.3.4 | Bearer establishment between MGW-1 and Target MGW ..... | 71 | +| 8.2.3.1.3.5 | Handover Complete..... | 71 | +| 8.2.3.1.4 | Example of Inter-MSC UMTS to GSM Handover that establishes Local Switching..... | 72 | +| 8.2.3.1.4.1 | Connection Model ..... | 72 | +| 8.2.3.1.4.2 | Basic Sequence for Inter-MSC UMTS to GSM Handover that establishes Local Switching.... | 73 | +| 8.2.3.2 | Inter-MSC UMTS to GSM Handover that does not establish Local Switching..... | 77 | + +| | | | +|-------------|--------------------------------------------------------------------------------|-----| +| 8.3 | GSM to UMTS ..... | 77 | +| 8.3.1 | Intra-MSC GSM to UMTS Relocation..... | 77 | +| 8.3.1.1 | General..... | 77 | +| 8.3.1.2 | Handover Required ..... | 77 | +| 8.3.1.3 | Iu Relocation Request Acknowledge..... | 77 | +| 8.3.1.4 | Handover Command/Iu Relocation Detect..... | 77 | +| 8.3.1.5 | Iu Relocation Complete ..... | 78 | +| 8.3.1.6 | Example ..... | 78 | +| 8.3.1.6.1 | Connection Model..... | 78 | +| 8.3.2 | Inter-MSC GSM to UMTS Relocation..... | 84 | +| 8.3.2.1 | General..... | 84 | +| 8.3.2.2 | MSC-1 / MGW-1 ..... | 84 | +| 8.3.2.2.1 | Handover Required ..... | 84 | +| 8.3.2.2.2 | Iu Relocation Request Acknowledge..... | 84 | +| 8.3.2.2.3 | Bearer establishment between MGW-1 and Target MGW ..... | 84 | +| 8.3.2.2.4 | MGW Flow Direction Control ..... | 84 | +| 8.3.2.2.5 | Handover Command/Iu Relocation Detect ..... | 84 | +| 8.3.2.2.6 | Iu Relocation Complete..... | 84 | +| 8.3.2.3 | Target MSC Server / Target MGW ..... | 85 | +| 8.3.2.3.1 | Prepare Handover Request message and MGW selection ..... | 85 | +| 8.3.2.3.2 | Bearer establishment towards Target RNC..... | 85 | +| 8.3.2.3.3 | Bearer establishment between MGW-1 and Target MGW ..... | 85 | +| 8.3.2.4 | Example of Inter-MSC GSM to UMTS Relocation ..... | 85 | +| 8.3.2.4.1 | Connection Model..... | 85 | +| 8.3.2.4.2 | Basic Sequence for Inter-MSC handover that breaks Local Switching ..... | 88 | +| 8.4 | GSM to GSM ..... | 92 | +| 8.4.1 | Intra-MSC Inter-BSS GSM to GSM Handover..... | 92 | +| 8.4.1.1 | Intra-MSC Inter-BSS GSM to GSM Handover that breaks Local Switching ..... | 92 | +| 8.4.1.1.1 | General ..... | 92 | +| 8.4.1.1.2 | Handover Required ..... | 92 | +| 8.4.1.1.3 | MGW Flow Direction Control ..... | 92 | +| 8.4.1.1.4 | Handover Request Acknowledge ..... | 93 | +| 8.4.1.1.5 | Handover Command/Handover Detect ..... | 93 | +| 8.4.1.1.6 | Handover Complete..... | 93 | +| 8.4.1.1.7 | Example..... | 93 | +| 8.4.1.1.7.1 | Connection Model ..... | 93 | +| 8.4.1.1.7.2 | Basic Sequence for Inter-BSS Handover that breaks Local Switching..... | 96 | +| 8.4.1.2 | Intra-MSC Inter-BSS GSM to GSM Handovers that establishes Local Switching..... | 98 | +| 8.4.1.2.1 | General ..... | 98 | +| 8.4.1.2.2 | Handover Required ..... | 98 | +| 8.4.1.2.3 | Bearer establishment towards Target BSS ..... | 98 | +| 8.4.1.2.4 | MGW Flow Direction Control ..... | 98 | +| 8.4.1.2.5 | Handover Request Acknowledge ..... | 98 | +| 8.4.1.2.6 | Handover Command/Handover Detect ..... | 99 | +| 8.4.1.2.7 | Handover Complete..... | 99 | +| 8.4.1.2.8 | Example..... | 99 | +| 8.4.1.2.8.1 | Connection Model ..... | 99 | +| 8.4.1.2.8.2 | Basic Sequence for Inter-BSS Handover that establishes Local Switching..... | 101 | +| 8.4.2 | Inter-MSC GSM to GSM Handover..... | 103 | +| 8.4.2.1 | Inter-MSC GSM to GSM Handover that breaks Local Switching ..... | 103 | +| 8.4.2.1.1 | General ..... | 103 | +| 8.4.2.1.2 | MSC-1 / MGW-1 ..... | 103 | +| 8.4.2.1.2.1 | Handover Required..... | 103 | +| 8.4.2.1.2.2 | Handover Request Acknowledge ..... | 103 | +| 8.4.2.1.2.3 | Bearer establishment between MGW-1 and Target MGW ..... | 104 | +| 8.4.2.1.2.4 | MGW Flow Direction Control ..... | 104 | +| 8.4.2.1.2.5 | Handover Command/Handover Detect ..... | 104 | +| 8.4.2.1.2.6 | Handover Complete..... | 104 | +| 8.4.2.1.3 | Target MSC Server / Target MGW ..... | 105 | +| 8.4.2.1.3.1 | Prepare Handover Request message and MGW selection..... | 105 | +| 8.4.2.1.3.2 | Handover Request Acknowledge ..... | 105 | +| 8.4.2.1.3.3 | Bearer establishment towards Target BSS ..... | 105 | + +| | | | +|-------------|----------------------------------------------------------------------------------------------------------------|-----| +| 8.4.2.1.3.4 | Bearer establishment between MGW-1 and Target MGW ..... | 105 | +| 8.4.2.1.3.5 | LCLS Negotiation in Initial Address message ..... | 105 | +| 8.4.2.1.4 | Example of Inter-MSC Handover that breaks Local Switching ..... | 105 | +| 8.4.2.1.4.1 | Connection Model ..... | 105 | +| 8.4.2.1.4.2 | Basic Sequence for Inter-MSC handover that breaks Local Switching ..... | 108 | +| 8.4.2.2 | Inter-MSC GSM to GSM Handover that establishes Local Switching ..... | 112 | +| 8.4.2.2.1 | General ..... | 112 | +| 8.4.2.2.2 | MSC-1 / MGW-1 ..... | 112 | +| 8.4.2.2.2.1 | Handover Required..... | 112 | +| 8.4.2.2.2.2 | Handover Request Acknowledge ..... | 113 | +| 8.4.2.2.2.3 | Bearer establishment between MGW-1 and Target MGW ..... | 113 | +| 8.4.2.2.2.4 | MGW Flow Direction Control ..... | 113 | +| 8.4.2.2.2.5 | Handover Command/Handover Detect ..... | 113 | +| 8.4.2.2.2.6 | Handover Complete..... | 113 | +| 8.4.2.2.3 | Target MSC Server / Target MGW ..... | 113 | +| 8.4.2.2.3.1 | Prepare Handover Request message and MGW selection..... | 113 | +| 8.4.2.2.3.2 | Handover Request Acknowledge ..... | 113 | +| 8.4.2.2.3.3 | Bearer establishment towards Target BSS ..... | 113 | +| 8.4.2.2.3.4 | Bearer establishment between MGW-1 and Target MGW ..... | 113 | +| 8.4.2.2.3.5 | LCLS Negotiation in Initial Address message ..... | 114 | +| 8.4.2.2.4 | Example of Inter-MSC Handover that establishes Local Switching..... | 114 | +| 8.4.2.2.4.1 | Connection Model ..... | 114 | +| 8.4.2.2.4.2 | Basic Sequence for Inter-MSC GSM to GSM Handover that establishes Local Switching .... | 116 | +| 8.4.2.3 | Inter-MSC Handover that leaves a not Locally Switched Call unchanged ..... | 119 | +| 8.4.3 | Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC ..... | 119 | +| 8.4.4 | Subsequent GSM to GSM Handover to a third MSC..... | 119 | +| 8.4.5 | BSS Internal Handover ..... | 119 | +| 8.4.5.1 | General ..... | 119 | +| 8.4.5.2 | Internal Handover Required..... | 119 | +| 8.4.5.3 | Internal Handover Command..... | 119 | +| 8.4.5.4 | Handover Complete ..... | 120 | +| 8.4.5.5 | Example BSS Internal Handover that Establishes Local Switching..... | 120 | +| 8.4.5.5.1 | Connection Model..... | 120 | +| 8.4.5.5.2 | Basic Sequence for BSS Internal Handover that Establishes Local Switching ..... | 121 | +| 8.4.5.6 | Example BSS Internal Handover that Breaks Local Switching ..... | 123 | +| 8.4.5.6.1 | Connection Model..... | 123 | +| 8.4.5.6.2 | Basic Sequence for BSS Internal Handover that Breaks Local Switching ..... | 124 | +| 8.4.5.7 | Example BSS Internal Handover that Does Not Modify LCLS Status of a Locally Switched Call ... | 126 | +| 8.4.5.7.1 | Connection Model..... | 126 | +| 8.4.5.7.2 | Basic Sequence for BSS Internal Handover that Does Not Modify LCLS Status of a Locally Switched Call ..... | 127 | +| 8.4.5.8 | Example BSS Internal Handover that Does Not Modify LCLS Status of a non-Locally Switched Call..... | 129 | +| 8.4.5.8.1 | Connection Model..... | 129 | +| 8.4.5.8.2 | Basic Sequence for BSS Internal Handover that Does Not Modify LCLS Status of a non-Locally Switched Call ..... | 130 | +| 8.5 | Handling of GSM Services after UMTS to GSM Handover ..... | 131 | +| 9 | Compatibility Issues..... | 132 | +| 10 | General (G)MSC server-MGW Procedures..... | 132 | +| 11 | Identities..... | 132 | +| 11.1 | General ..... | 132 | +| 11.2 | Global Call Reference ..... | 132 | +| 12 | Operational Aspects ..... | 132 | +| 12.1 | Charging..... | 132 | +| 13 | Interactions with Other Services ..... | 132 | +| 13.1 | Enhanced Multi-Level Precedence and Pre-emption service (eMLPP)..... | 132 | +| 13.2 | Call Deflection Service ..... | 133 | +| 13.2.1 | General ..... | 133 | +| 13.2.2 | Notification to the Calling Subscriber ..... | 133 | + +| | | | +|--------------|-----------------------------------------------------------------|-----| +| 13.2.3 | Initial Addressing ..... | 133 | +| 13.2.4 | Backward LCLS Negotiation ..... | 133 | +| 13.2.5 | LCLS Through-Connection..... | 133 | +| 13.2.6 | Example ..... | 133 | +| 13.2.6.1 | Connection Model..... | 133 | +| 13.2.6.2 | Basic Sequence ..... | 135 | +| 13.3 | Line identification Services..... | 137 | +| 13.3.1 | Calling Line Identification Presentation (CLIP) ..... | 137 | +| 13.3.2 | Calling Line Identification Restriction (CLIR) ..... | 137 | +| 13.3.3 | Connected Line Identification Presentation (COLP)..... | 138 | +| 13.3.4 | Connected Line Identification Restriction (COLR) ..... | 138 | +| 13.4 | Call Forwarding Services..... | 138 | +| 13.4.1 | Principles ..... | 138 | +| 13.4.2 | Call Forwarding Unconditional (CFU) ..... | 138 | +| 13.4.2.1 | Notification to the Calling Subscriber ..... | 138 | +| 13.4.2.2 | Initial Addressing..... | 138 | +| 13.4.2.3 | Backward LCLS Negotiation..... | 138 | +| 13.4.2.4 | LCLS Through-Connection ..... | 138 | +| 13.4.2.5 | Example ..... | 139 | +| 13.4.2.5.1 | Connection Model..... | 139 | +| 13.4.2.5.2 | Basic Sequence..... | 139 | +| 13.4.3 | Call Forwarding on mobile subscriber Busy (CFB)..... | 143 | +| 13.4.3.1 | Network Determined User Busy (NDUB)..... | 143 | +| 13.4.3.1.1 | General ..... | 143 | +| 13.4.3.1.2 | Notification to the Calling Subscriber..... | 143 | +| 13.4.3.1.3 | Initial Addressing..... | 143 | +| 13.4.3.1.4 | Backward LCLS Negotiation..... | 144 | +| 13.4.3.1.5 | LCLS Through-Connection..... | 144 | +| 13.4.3.1.6 | Example..... | 144 | +| 13.4.3.2 | User Determined User Busy (UDUB) ..... | 144 | +| 13.4.3.2.1 | General ..... | 144 | +| 13.4.3.2.2 | Call Clearing to the Served Subscriber ..... | 144 | +| 13.4.3.2.3 | Notification to the Calling Subscriber..... | 144 | +| 13.4.3.2.4 | Initial Addressing..... | 144 | +| 13.4.3.2.5 | Backward LCLS Negotiation..... | 145 | +| 13.4.3.1.6 | LCLS Through-Connection..... | 145 | +| 13.4.3.2.7 | Example..... | 145 | +| 13.4.3.2.7.1 | Connection Model ..... | 145 | +| 13.4.3.2.7.2 | Basic Sequence..... | 146 | +| 13.4.4 | Call Forwarding on No Reply (CFNRy) ..... | 148 | +| 13.4.4.1 | General ..... | 148 | +| 13.4.4.2 | Call Clearing to the Served Subscriber..... | 148 | +| 13.4.4.3 | Notification to the Calling Subscriber ..... | 148 | +| 13.4.4.4 | Initial Addressing..... | 148 | +| 13.4.4.5 | Backward LCLS Negotiation..... | 148 | +| 13.4.4.6 | LCLS Through-Connection ..... | 148 | +| 13.4.4.7 | Example ..... | 148 | +| 13.4.4.7.1 | Connection Model..... | 148 | +| 13.4.4.7.2 | Basic Sequence..... | 150 | +| 13.4.5 | Call Forwarding on mobile subscriber Not Reachable (CFNRc)..... | 152 | +| 13.4.5.1 | General ..... | 152 | +| 13.4.5.2 | Rerouting by HLR ..... | 152 | +| 13.4.5.3 | Rerouting by VLR ..... | 152 | +| 13.5 | Call Waiting (CW) ..... | 152 | +| 13.5.1 | Principles ..... | 152 | +| 13.5.2 | Accept the new incoming call, the original call is hold..... | 152 | +| 13.5.2.1 | General ..... | 152 | +| 13.5.2.2 | Example ..... | 153 | +| 13.5.2.2.1 | Connection Model..... | 153 | +| 13.5.2.2.2 | Basic Sequence..... | 154 | +| 13.6 | Call Hold (CH)..... | 155 | +| 13.6.1 | Principles ..... | 155 | + +| | | | +|------------|------------------------------------------------------------------------------------------------------|-----| +| 13.6.2 | Call Hold after Answer, LCLS established ..... | 155 | +| 13.6.2.1 | Hold Request..... | 155 | +| 13.6.2.2 | Retrieval Request..... | 155 | +| 13.6.2.3 | Example ..... | 156 | +| 13.6.2.3.1 | Connection Model..... | 156 | +| 13.6.2.3.2 | Basic Sequence..... | 157 | +| 13.6.3 | Call Hold after Answer, LCLS not established ..... | 158 | +| 13.6.3.1 | Hold Request..... | 158 | +| 13.6.3.2 | Retrieval Request..... | 159 | +| 13.6.4 | Establishment of a new call, the original call is hold ..... | 159 | +| 13.6.4.1 | General Principle ..... | 159 | +| 13.6.4.2 | Assignment Request ..... | 159 | +| 13.6.5 | Retrieval of the held call, ongoing call is on-hold/completed..... | 159 | +| 13.6.5.1 | General Principle ..... | 159 | +| 13.6.5.2 | Example call flow, Retrieval of held call after ongoing call has completed ..... | 160 | +| 13.7 | Multiparty (MPTY)..... | 160 | +| 13.8 | Closed User Group (CUG)..... | 160 | +| 13.9 | Advice of Charge (AoC) ..... | 160 | +| 13.10 | User-to-User Signalling (UUS)..... | 160 | +| 13.11 | Call Barring Services ..... | 160 | +| 13.12 | Explicit Call Transfer (ECT)..... | 161 | +| 13.13 | Completion of Calls to Busy Subscriber (CCBS)..... | 161 | +| 13.14 | Multiple Subscriber Profile (MSP) ..... | 161 | +| 13.15 | Multicall ..... | 161 | +| 13.16 | Calling Name Presentation (CNAP) ..... | 161 | +| 13.17 | Alternate Speech/Fax ..... | 161 | +| 13.18 | Modification of the Access Bearer..... | 161 | +| 13.19 | GSM Fax ..... | 161 | +| 13.20 | Voice group call service (VGCS), Voice broadcast service (VBS) ..... | 161 | +| 14 | Interactions with Other Network Features and Services..... | 162 | +| 14.1 | Customised Applications for Mobile network Enhanced Logic (CAMEL) ..... | 162 | +| 14.2 | IST ..... | 162 | +| 14.3 | Operator Determined Barring (ODB) ..... | 162 | +| 14.4 | DTMF..... | 162 | +| 14.5 | OR ..... | 162 | +| 14.6 | Providing tones or announcements ..... | 162 | +| 14.6.1 | General ..... | 162 | +| 14.6.2 | Handling of tones or announcements during an LCLS call..... | 163 | +| 14.6.2.1 | GMSC Server or intermediate node requiring temporary send access to apply tone or announcement ..... | 163 | +| 14.6.2.2 | oMSC Server..... | 163 | +| 14.6.2.3 | tMSC Server ..... | 164 | +| 14.6.2.4 | BSS ..... | 165 | +| 14.6.2.5 | Example of Playing Mid-Call Announcement/Tone ..... | 165 | +| 14.6.2.5.1 | Connection Model..... | 165 | +| 14.6.2.5.2 | Example Sequence ..... | 166 | +| 14.6.2.6.1 | Connection Model..... | 168 | +| 14.6.2.6.2 | Example Sequences with Uplink Bicasting of User Data..... | 169 | +| 14.6.2.6.3 | Example Sequence when Access Side Termination is isolated in MGW ..... | 171 | +| 14.7 | Global Text Telephony..... | 172 | +| 14.8 | Emergency Calls ..... | 172 | +| 14.9 | Subscriber and equipment trace ..... | 172 | +| 14.10 | Customized Alerting Tone ..... | 172 | +| 14.10.1 | Audio CAT ..... | 172 | +| 14.10.2 | Multimedia CAT ..... | 172 | +| 14.11 | Tandem Free Operation (TFO) ..... | 173 | +| 14.12 | Transcoder Free Operation (TrFO) ..... | 173 | +| 14.13 | CS Data Calls ..... | 173 | +| 14.14 | RTP Multiplexing..... | 173 | + +| | | | +|-------------------------------|-----------------------------------------------------------------------------------|------------| +| 15 | Tunnelling ..... | 173 | +| 16 | Messages/Procedures and their contents ..... | 173 | +| 16.1 | Messages between (G)MSC servers..... | 173 | +| 16.1.1 | General ..... | 173 | +| 16.1.2 | Initial Address ..... | 173 | +| 16.1.3 | Answer..... | 174 | +| 16.1.4 | Bearer and Codec Information ..... | 174 | +| 16.1.5 | Backward LCLS Negotiation ..... | 174 | +| 16.1.6 | Change of LCLS Configuration ..... | 175 | +| 16.1.7 | LCLS Status update ..... | 176 | +| 16.1.8 | Change of LCLS Status ..... | 176 | +| 16.1.9 | MAP_PREPARE_HANDOVER Request..... | 176 | +| 16.2 | Procedures between (G)MSC server and MGW ..... | 177 | +| 16.3 | Messages between MSC server and BSS ..... | 177 | +| 16.3.1 | General ..... | 177 | +| 16.3.2 | Assignment Procedure between MSC-Server and BSS ..... | 177 | +| 16.3.3 | Handover Request Procedure between MSC-Server and BSS..... | 178 | +| 16.3.4 | Handover Complete Procedure between MSC-Server and BSS ..... | 179 | +| 16.3.5 | Handover Performed Procedure between MSC-Server and BSS..... | 179 | +| 16.3.6 | Internal Handover Command Procedure between MSC-Server and BSS..... | 180 | +| 16.3.7 | LCLS Connection Procedure between MSC-Server and BSS ..... | 180 | +| 16.3.8 | LCLS Notification Procedure between MSC-Server and BSS ..... | 180 | +| 17 | Bearer Redirect ..... | 181 | +| 18 | (G)MSC MGW Tandeming ..... | 181 | +| 19 | Timers ..... | 181 | +| 20 | Multiple Realms ..... | 181 | +| Annex A (informative): | Case studies for LCLS Negotiation..... | 182 | +| A.1 | oMSC LCLS-Negotiation handling when receiving UL bicast and sending DL data ..... | 182 | +| A.2 | tMSC LCLS-Negotiation handling when receiving UL bicast and sending DL data ..... | 185 | +| Annex B (informative): | Change history..... | 190 | + +--- + +## Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +--- + +# 1 Scope + +The present document defines the Stage 2 description for the Local Call Local Switch feature. Local Call Local Switch may be implemented in both BICC based CS core networks as defined in 3GPP TS 23.205 [2] and SIP-I based CS core networks as defined in 3GPP TS 23.231 [3], with a GSM/EDGE Radio Access Network supporting either TDM based or IP based A interface. + +This stage 2 shall cover the information flows between the GMSC server, MSC server and media gateways that are required to support Local Call Local Switching highlighting the specific requirements in addition to those defined for BICC based CS core networks 3GPP TS 23.205 [2] and SIP-I based CS core networks 3GPP TS 23.231 [3]. Note that nothing in the present document shall preclude an implementation of a combined MSC Server and MGW. The present document shall show the CS core network termination of the A interface, and the information flows between the BSS and the MSC server, in order to cover the information flow stimulus to the core network and describe the interaction with the supplementary and value added services and capabilities. + +The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced. + +--- + +# 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.205: "Bearer-independent circuit-switched core network; Stage 2". +- [3] 3GPP TS 23.231: "SIP-I based Circuit Switched Core Network; Stage 2". +- [4] 3GPP TS 23.153: "Out of band transcoder control; Stage 2". +- [5] ITU-T Recommendation Q.1902.3 (07/2001): "Bearer independent call control (Capability set 2) and Signalling System No.7 ISDN User part: Formats and Codes". +- [6] 3GPP TS 29.205: "Application of Q.1900 series to bearer-independent Circuit Switched (CS) core network architecture; Stage 3". +- [7] 3GPP TS 48.008: "Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification". +- [8] 3GPP TS 23.002: "Network architecture". +- [9] 3GPP TS 23.009: "Handover procedures". +- [10] 3GPP TS 29.231: "Application of SIP-I Protocols to Circuit Switched (CS) core network architecture; Stage 3". +- [11] 3GPP TS 29.232: "Media Gateway Controller (MGC) - Media Gateway (MGW) interface; Stage 3". +- [12] 3GPP TS 29.002: "Mobile Application Part (MAP) specification". + +## 3 Definitions, symbols and abbreviations + +### 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**BSS ID:** A globally unique identifier of a Base Station Subsystem (BSS). + +**call leg:** The access link between the mobile station and the Core Network. A mobile to mobile call consists of two call legs and the link through the Core Network. + +**call leg correlation:** The process within the BSS to search for the other call-leg(s) of a (potential) Intra-BSS call by appropriate means. + +**intra-BSS call:** A mobile to mobile voice call involving two mobile stations connected to the same BSS. + +**intra-BSS call detection:** Determination that both call legs are within the same BSS. + +**local call:** An Intra-BSS call that can be locally switched by the BSS. + +**locally switched call:** A local call with a direct local path between the Call-legs, switched by the BSS. + +### 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +| | | +|------|--------------------------------------------------------------------------------------------------------------------------------------------| +| A | Interface between the BSC and the MSC-S | +| Abis | Interface between the BSC and the BTS | +| i | intermediate node prefix. | +| Mc | Interface between the (G)MSC-S and the MGW. | +| Nc | The NNI call control interface between (G)MSC servers | +| o | originating side prefix, e.g. oUE, oBSS, oMSC, oMGW for nodes and e.g. oA-interface, oAssignment Request etc for interfaces, messages etc. | +| t | terminating side prefix , e.g. tUE, tBSS, tMSC, tMGW and e.g. tA-interface, tAssignment Request etc for interfaces, messages etc. | + +### 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|-------|----------------------------------------------------------------------| +| AoIP | A over IP, using IP as the bearer of the user plane of A interface | +| AoTDM | A over TDM, using TDM as the bearer of the user plane of A interface | +| APM | Application Transport Mechanism | +| COT | Continuity message | +| GCR | Global Call Reference | +| LCLS | Local Call Local Switch | +| OoBTC | Out of Band Transcoder Control | + +## 4 Main Concepts + +### 4.1 General + +Local Call Local Switch provides the capability for the user plane to be locally switched (e.g. voice data in user plane is not backhauled to the CS core network) for calls that are generated and terminated by users that are served by the same BSS. The result is saving on transmission resource of the Abis and/or A interface. + +Local Call Local Switch shall only be considered for a CS voice call and is transparent to the end user. + +Figure 4.1.1 shows an example of Local Call Local Switching. It highlights only the main nodes and interfaces and differentiates between "originating" nodes and interfaces (oUE, oBTS, oMSC, oMGW, oAbis, oA) and "terminating" nodes and interfaces (tMSC, tMGW, tBTS, tUE, tAbis, tA). It also includes an Intermediate MSC server and MGW (iMSC, iMGW), which may be a (G)MSC server or other intermediate CN control node and its MGW. + +![Diagram illustrating Local Call Local Switching (LCLS) architecture. It shows two User Equipment (UE) units, oUE and tUE, connected to oBTS and tBTS respectively. Both BTS units are connected to a central BSC (Base Station Controller) with local switching capability. The BSC is connected to an originating MSC (oMSC) via oA and oAbis interfaces, and to a terminating MSC (tMSC) via tA and tAbis interfaces. The oMSC is connected to an intermediate MSC (iMSC) via an oMGW and a tMGW. The iMSC is connected to the tMSC via an iMGW. The diagram uses thick solid blue lines for active User Plane paths (speech) and thin dotted blue lines for inactive User Plane paths. Solid red lines represent Control Plane paths (signaling). A legend indicates that blue represents Speech and red represents Signaling.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) + +Diagram illustrating Local Call Local Switching (LCLS) architecture. It shows two User Equipment (UE) units, oUE and tUE, connected to oBTS and tBTS respectively. Both BTS units are connected to a central BSC (Base Station Controller) with local switching capability. The BSC is connected to an originating MSC (oMSC) via oA and oAbis interfaces, and to a terminating MSC (tMSC) via tA and tAbis interfaces. The oMSC is connected to an intermediate MSC (iMSC) via an oMGW and a tMGW. The iMSC is connected to the tMSC via an iMGW. The diagram uses thick solid blue lines for active User Plane paths (speech) and thin dotted blue lines for inactive User Plane paths. Solid red lines represent Control Plane paths (signaling). A legend indicates that blue represents Speech and red represents Signaling. + +**Figure 4.1.1: Example of Local Call Local Switching** + +The "active" User Plane path is shown with a thick, solid blue line for the case that Local Switching is provided between two BTS's, while the "inactive" User Plane path, i.e. the two Abis-links, the two A-links and the links within the Core Network are not carrying traffic and are therefore marked with thin, dotted blue lines. The Control Plane paths are shown in solid red lines. + +Local Call Local Switch is attempted to be instantiated during call establishment. During this phase, negotiation for support of LCLS is performed within the Core Network and requests to correlate and connect the call legs are made to the BSS when LCLS is successfully negotiated. Interaction with existing supplementary services and handover/relocation are supported. Depending on the scenario this may require a break of an existing locally switched call where the voice data on user plane shall be routed via the core network, or a (re)establishment of a locally switched call where the voice data on user plane shall be locally switched in the BSS. + +Local Call Local Switch may be supported on both TDM based A interface (AoTDM) and IP based A interface (AoIP). + +Local Call Local Switch may be implemented on both a BICC based CS core network and a SIP-I based CS core network and therefore the main concepts that are defined within 3GPP TS 23.205 [2] and 3GPP TS 23.231 [3] respectively, also apply to Local Call Local Switch. + +The MSC server is in charge of call control, supplementary services and gives permission (or denies) as to whether local switching may be applied. When the MSC server has granted the permission to apply LCLS, the BSC makes the final operation decision whether to establish LCLS (dependent on alignment of codecs, BTS's supporting local switching, resource available, status of its BTS's, the state of its radio legs). + +## 4.2 LCLS Negotiation + +### 4.2.1 General concept of LCLS negotiation + +LCLS negotiation is required within the Core Network in order to determine if all of the MSC servers and intermediate nodes, including GMSC servers, in the call control path support and allow the activation of the LCLS functionality. LCLS negotiation may result in LCLS not being permitted for the following reasons: + +- An MSC server node or intermediate node, including GMSC server node, has not been upgraded to support the LCLS functionality. +- It is prevented due to specific interactions e.g. Supplementary Services, operator determined restriction of LCLS, etc. + +Additionally the LCLS negotiation may result in local call local switch being permitted but with certain configurations for user plane connectivity to the BSS depending on the network requirements, for example periodic signalling of pre-paid tones. + +The LCLS negotiation Information Elements (LCLS-Negotiation Request, LCLS-Negotiation Response and LCLS-Configuration-Preference) are explicitly signalled on the Nc Interface. The LCLS-Negotiation Request IE and LCLS-Configuration-Preference IE are signalled during call establishment where the originating MSC server starts LCLS negotiation. + +Depending on the support of LCLS, the MSC servers and intermediate nodes, including GMSC server, in the call control path may remove the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE from further signalling on the Nc interface (e.g. if node does not support LCLS), or modify the contents of the LCLS-Negotiation Request IE (e.g. if LCLS is not allowed for the subscriber), or modify the LCLS-Configuration-Preference IE (e.g. if LCLS is allowed and bicasting is required during LCLS). + +The following properties are signalled in the LCLS-Configuration-Preference Information Element for "LCLS is Allowed" to allow each node to indicate what level of user data connection it requires: + +- Need\_Receive\_Forward = No/Yes; this indicates if the node needs to receive UL data from the originating UE. +- Need\_Receive\_Backward = No/Yes; this indicates if the node needs to receive UL data from the terminating UE. +- Need\_Send\_Forward = No/Yes; this indicates if the node needs to insert user data toward the terminating UE. +- Need\_Send\_Backward = No/Yes; this indicates if the node needs to insert user data toward the originating UE + +The default value "No" means that no Core Network user data requirement exists. If a node receives the LCLS Negotiation Request IE and the LCLS-Configuration-Preference IE and if any of the parameters of the LCLS-Configuration-Preference IE is set to "Yes" it shall not change them; it may however change any parameter to "Yes". However in the backward direction, the received parameters of the LCLS Negotiation Response IE and the LCLS-Configuration-Preference IE shall not be modified. + +The LCLS configuration preference that is negotiated on the core network path allows the oMSC server and the tMSC server to request the correct LCLS configuration from the BSS (see sub-clause 4.6.2) on the originating and the terminating leg. + +Table 4.2.1.1 shows all possible LCLS configuration preferences and the related LCLS configurations requested from the BSS on the originating and the terminating leg. + +**Table 4.2.1.1: Final LCLS configuration preference negotiated on the Core Network path and the related LCLS configuration requested from the BSS** + +| | Negotiated value of LCLS-Configuration-Preference IE | | | | Resulting LCLS configuration requested from oMS C to oBSS | Resulting LCLS configuration requested from tMSC to tBSS | +|----|------------------------------------------------------|--------------------|-----------------------|-------------------|-------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| | Need_receive_forward | Need_send_backward | Need_receive_backward | Need_send_forward | | | +| 1 | No | No | No | No | connected both-way in the BSS | connected both-way in the BSS | +| 2 | No | No | No | Yes | connected both-way in the BSS | connected both-way in the BSS and send access DL from the Core Network | +| 3 | No | No | Yes | No | connected both-way in the BSS | connected both-way in the BSS and bi-casted UL to the Core Network | +| 4 | No | No | Yes | Yes | connected both-way in the BSS | connected both-way in the BSS and bi-casted UL to the Core Network and send access DL from the Core Network | +| 5 | No | Yes | No | No | connected both-way in the BSS and send access DL from the Core Network | connected both-way in the BSS | +| 6 | No | Yes | No | Yes | connected both-way in the BSS and send access DL from the Core Network | connected both-way in the BSS and send access DL from the Core Network | +| 7 | No | Yes | Yes | No | connected both-way in the BSS and send access DL from the Core Network, block local DL | connected both-way in the BSS and bi-casted UL to the Core Network | +| 8 | No | Yes | Yes | Yes | connected both-way in the BSS and send access DL from the Core Network, block local DL | connected both-way in the BSS and bi-casted UL to the Core Network and send access DL from the Core Network | +| 9 | Yes | No | No | No | connected both-way in the BSS and bi-casted UL to the Core Network | connected both-way in the BSS | +| 10 | Yes | No | No | Yes | connected both-way in the BSS and bi-casted UL to the Core Network | connected both-way in the BSS and send access DL from the Core Network, block local DL | +| 11 | Yes | No | Yes | No | connected both-way in the BSS and bi-casted UL to the Core Network | connected both-way in the BSS and bi-casted UL to the Core Network | +| 12 | Yes | No | Yes | Yes | connected both-way in the BSS and bi-casted UL to the Core Network | connected both-way in the BSS and bi-casted UL to the Core Network and send access DL from the Core Network, block local DL | +| 13 | Yes | Yes | No | No | connected both-way in the BSS and bi-casted UL to the Core Network and send access DL from the Core Network | connected both-way in the BSS | +| 14 | Yes | Yes | No | Yes | connected both-way in the BSS and bi-casted UL to the Core Network and send access DL from the Core Network | connected both-way in the BSS and send access DL from the Core Network, block local DL | + +| | Negotiated value of LCLS-Configuration-Preference IE | | | | Resulting LCLS configuration requested from oMSC to oBSS | Resulting LCLS configuration requested from tMSC to tBSS | +|----|------------------------------------------------------|--------------------|-----------------------|-------------------|-----------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| +| | Need_receive_forward | Need_send_backward | Need_receive_backward | Need_send_forward | | | +| 15 | Yes | Yes | Yes | No | connected both-way in the BSS and bi-casted UL to the Core Network and send access DL from the Core Network, block local DL | connected both-way in the BSS and bi-casted UL to the Core Network | +| 16 | Yes | Yes | Yes | Yes | connected both-way in the BSS and bi-casted UL to the Core Network and send access DL from the Core Network, block local DL | connected both-way in the BSS and bi-casted UL to the Core Network and send access DL from the Core Network, block local DL | + +A Core Network node can optionally request that its related MGW isolates the access side termination from the network side termination in order to avoid any forwarding of data that it receives from another network entity (Core Network node or BSS). Isolation of the access termination is possible when user data need not be transported from the oBSS or the tBSS through the complete core network and in this case the LCLS configuration, which is sent to the oBSS or the tBSS based on the final LCLS configuration preference does not include the request to block local DL user data. + +Figure 4.2.1.1 shows an example of how the user plane data can be configured as a result of the CN LCLS Negotiation. The precise LCLS configuration settings for each permutation of LCLS configuration preference options are specified in Table 4.2.1.1. + +![Diagram illustrating the general concepts for LCLS configurations as a result of LCLS Negotiation. The diagram shows three MSCs (MSC-S-o, MSC-S-i, MSC-S-t) connected via LCLS-Negotiation Request/Response messages. Below them are three MGWs (MGW-o, MGW-i, MGW-t) connected via a User Plane (connection). MGW-o is connected to UE-o and BSS-1/BSS-2. MGW-t is connected to UE-t. MGW-i is connected to BSS-1/BSS-2. The diagram shows data flows: UL data requested from oUE (yellow arrow from UE-o to MGW-o), UL data requested from tUE (cyan arrow from UE-t to MGW-t), and DL data requested to apply a tone or announcement (red arrow from MGW-o to UE-o). Inside BSS-1/BSS-2, there are labels 'Local DL data not blocked by BSS' and 'Local DL data blocked by BSS' with a red X mark.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) + +Diagram illustrating the general concepts for LCLS configurations as a result of LCLS Negotiation. The diagram shows three MSCs (MSC-S-o, MSC-S-i, MSC-S-t) connected via LCLS-Negotiation Request/Response messages. Below them are three MGWs (MGW-o, MGW-i, MGW-t) connected via a User Plane (connection). MGW-o is connected to UE-o and BSS-1/BSS-2. MGW-t is connected to UE-t. MGW-i is connected to BSS-1/BSS-2. The diagram shows data flows: UL data requested from oUE (yellow arrow from UE-o to MGW-o), UL data requested from tUE (cyan arrow from UE-t to MGW-t), and DL data requested to apply a tone or announcement (red arrow from MGW-o to UE-o). Inside BSS-1/BSS-2, there are labels 'Local DL data not blocked by BSS' and 'Local DL data blocked by BSS' with a red X mark. + +Figure 4.2.1.1: General concepts for LCLS configurations as a result of LCLS Negotiation. + +Annex A provides further examples of LCLS negotiation in the CN and LCLS configuration in the BSS. + +#### 4.2.2 (void) + +#### 4.2.3 (void) + +### 4.2.4 General concept of LCLS Configuration Preference Modification + +LCLS Configuration preferences may be modified during an ongoing call. + +The LCLS Configuration Change Request message may be signalled mid-call to attempt to establish LCLS or modify LCLS configuration preferences, for example for mid-call tones or announcements. Any core network node that requires change of the LCLS configuration preferences may initiate the LCLS Configuration Change Request. + +Change of the LCLS configuration preferences may only be initiated after Answer. + +NOTE 1: Prior to Answer message being returned the call is considered to be in the set-up phase and then subsequent LCLS Negotiation Response and LCLS-Configuration-Preference IEs can be sent within the call establishment messages (e.g. APM, ACM, CPG). + +Only after the node has already handled the LCLS Negotiation procedure it may initiate a Change of the LCLS configuration preferences. If a node does not respond to the LCLS Negotiation then it shall not trigger a change of the LCLS configuration preferences at a later time in the call. + +NOTE 2: Take Call Waiting for example, the call will trigger an LCLS Negotiation towards the called party since it is a call establishment from the calling parties perspective. + +When receiving the LCLS Configuration Change Request message, the other nodes can only accept or reject the request without any modifications. If another node wishes to make further changes to the LCLS configuration preference settings it can initiate its own modification of the LCLS-Configuration-Preference IE settings after the ongoing change of the LCLS configuration preference procedure is completed. + +The initiating node shall signal the LCLS Configuration Change Request message in the direction (originating leg or terminating leg or both – but only for Intermediate Node) that it requires the LCLS configuration preference settings to be changed. + +If the intermediate node receives the LCLS Configuration Change Request message and it does not accept the requested changes to the LCLS configuration preferences it shall immediately return LCLS Configuration Change Request Acknowledge message indicating the same requested LCLS-Configuration-Preference IE settings and with the LCLS-Configuration-Change Result IE indicating rejection of the requested LCLS configuration change. Otherwise if the intermediate node accepts the requested changes to the LCLS configuration preferences it shall forward the received LCLS Configuration Change Request message containing the LCLS-Configuration-Change Request IE and the LCLS-Configuration-Preference IE to its subsequent (succeeding/preceding) node. + +If the node which terminates the LCLS Configuration Change Request is the oMSC server or the tMSC server and it accepts the requested changes to the LCLS configuration preferences it shall return the LCLS Configuration Change Request Acknowledge message indicating the same requested LCLS configuration preferences and with the LCLS=Configuration-Change Result IE indicating acceptance of the LCLS Configuration Change Request. + +If the node which terminates the LCLS Configuration Change Request is the oMSC server or the tMSC server and it does not accept the requested changes to the LCLS configuration preferences it shall return the LCLS Configuration Change Request Acknowledge message indicating the same requested LCLS configuration preferences and with the LCLS-Configuration-Change Result IE indicating rejection of the LCLS Configuration Change Request. + +On receipt of the LCLS Configuration Change Request Acknowledge message from the succeeding/preceding node the intermediate node shall forward it to its subsequent (preceding/succeeding) node. + +The change of the LCLS configuration preferences procedure is completed: + +- for the node that receives the LCLS Configuration Change Request message when it sends the LCLS Configuration Change Request Acknowledge message; +- for the node which initiates the LCLS Configuration Change Request when it receives the LCLS Configuration Change Request Acknowledge message. + +NOTE 3: If the node which initiates the LCLS Configuration Change Request receives the LCLS Configuration Change Request Acknowledge with the LCLS-Configuration-Change Result IE indicating rejection the node can trigger an LCLS Break as described in sub-clause 7.2.1, specific applications such as insertion of tones or announcements will dictate this and are described in subsequent sections. + +If LCLS Negotiation has occurred during call establishment and a handover occurs prior to answer which changes the LCLS configuration preferences (from a previously agreed "No" to a "Yes") then the node shall wait until after Answer before requesting the modification of the LCLS configuration preferences. + +NOTE 4: Inter-MSC Handover during call establishment can result in an outstanding IAM – oMSC has sent IAM forward and then performs Inter-MSC Handover – which could result in the LCLS configuration preferences being out of alignment prior to Answer, the MSC can then defer sending the LCLS-Connect\_Control request to its BSS if it wishes to prevent LCLS until it has performed a modification of the LCLS configuration preferences. + +## 4.3 LCLS Call Leg Correlation + +### 4.3.1 General + +LCLS call leg correlation is required in order to allow the BSS to identify that two call legs that are part of the same call are within the same BSS, and therefore can be correlated together to be a candidate for Local Call Local Switching. + +The originating MSC server shall generate a Global Call Reference (GCR) Information Element which is a globally unique call identifier for the duration of the call and needs to be sent to all nodes in the routing path. The Global Call Reference is further detailed within clause 11. + +The originating MSC server and the terminating MSC server shall include the GCR Information Element in the ASSIGNMENT REQUEST and HANDOVER REQUEST messages. + +See Clause 6 for the detailed descriptions and related call flows for the call establishment procedures. + +The GCR may additionally be signalled within the core network for supplementary service interaction with LCLS and Inter-MSC Handover, this is further detailed in Clause 13 and Clause 8 respectively. + +On receipt of a GCR Information Element, if the BSS supports LCLS, the BSS shall store the GCR for each call leg until the call is released or that call leg is handed over to another BSS. + +NOTE: the inclusion of the LCLS-BSS-Status IE in the response indicates to the MSC server that the BSS supports LCLS. + +If the GCR and LCLS-Configuration Information Elements are included in the ASSIGNMENT REQUEST message, without the LCLS-Correlation-Not-Needed Information Element (see optional Intra-Network Detection, Sub-clause 4.3.2 and optional Intra-BSS Call Detection, Sub-clause 4.3.3), the BSS shall perform call leg correlation and send the LCLS-BSS-Status Information Element with the correct value within the ASSIGNMENT COMPLETE message. + +If the GCR and LCLS-Configuration Information Elements are included in the HANDOVER REQUEST message, the BSS shall perform call leg correlation and send the LCLS-BSS-Status Information Element with the correct value within the HANDOVER COMPLETE messages. + +If the GCR, LCLS-Configuration and LCLS-Correlation-Not-Needed Information Elements are included (see optional Intra-Network Call Detection, Sub-clause 4.3.2 and optional Intra-BSS Call Detection, Sub-clause 4.3.3) in the ASSIGNMENT REQUEST message, the BSS shall either: + +- not perform any call leg correlation, but only store the GCR for the assigned call leg and send the LCLS-BSS-Status Information Element with the value "Call Not Possible to be Locally Switched" within the ASSIGNMENT COMPLETE; + +or + +- ignore the LCLS-Correlation-Not-Needed Information Element, store the GCR and perform call leg correlation, and send the LCLS-BSS-Status Information Element with the correct value within the ASSIGNMENT COMPLETE message. + +## 4.3.2 Optional Intra-Network Call Detection + +### 4.3.2.1 General + +As an option during call establishment, the tMSC server or the tBSS may utilise the Network ID within the Global Call Reference in order to determine whether the call is an intra-network call (e.g. compare the Network ID within the GCR with the Network ID of the tMSC server). + +### 4.3.2.2 Intra-Network Call Detection within the tMSC server + +The terminating MSC-Server may perform an intra-network call detection as follows: + +- if the Network ID in the GCR is the same as the Network ID of the terminating MSC-Server it means that the call is an intra-network call and the terminating MSC-Server shall proceed as for the case if no Intra-Network Call Detection is performed i.e. including the GCR and LCLS-Configuration Information Elements, but not including the LCLS-Correlation-Not-Needed Information Element, within the ASSIGNMENT REQUEST message. +- if the Network ID in the GCR is different from the Network ID of the terminating MSC-Server it means that the call is not an intra-network call and the terminating MSC-Server shall include GCR, LCLS-Configuration, and LCLS-Correlation-Not-Needed Information Elements within the ASSIGNMENT REQUEST message. + +NOTE: Intra-Network call detection within the tMSC server can minimize the processing in some BSS implementations. + +### 4.3.2.3 Intra-Network Call Detection within the tBSS + +When receiving a GCR Information Element the tBSS may perform intra-network call detection as follows: + +- if the Network ID in the GCR is the same as the Network ID of the terminating BSS it means that the call is an intra-network call and the terminating BSS shall perform call leg correlation. +- if the Network ID in the GCR is different from the Network ID of the terminating BSS it means that the call is not an intra-network call and the terminating BSS shall only store the GCR for the assigned call leg and does not need to perform call leg correlation. + +The tBSS shall indicate the resulting outcome to the tMSC server in the LCLS-BSS-Status Information Element within the Assignment Complete. + +## 4.3.3 Optional Intra-BSS Call Detection + +### 4.3.3.1 General + +As an option during call establishment, the tMSC server or tBSS may utilize the oBSS Node ID within the Call Reference ID of the GCR, in order to determine whether the call is an intra-BSS call (e.g. compare the oBSS Node ID with the tBSS Node ID) as described below. + +NOTE: After the oMSC server has generated the GCR IE, an Inter-BSS handover may occur at the originating side, therefore the encapsulated BSS ID is no longer the same as the BSS ID of the new Target BSS (see also sub-clause 8.4.1.1). Due to that, the result of the "BSS ID Pre-Check" procedure may be incorrect leading to "LCLS-Correlation-Not-Needed" indication being sent to the tBSS whilst the new target BSS could in fact be the same as the tBSS. If the tBSS does not perform the correlation of the GCR then the information in the Assignment Complete message may also be inaccurate (the LCLS-BSS-Status IE may indicate "call not possible to be locally switched" instead of "call not yet locally switched"). If the tMSC server indicates "LCLS-Correlation-Not-Needed" and the Inter-BSS handover has occurred at the oUE into the same BSS as the tUE but after signalling the GCR IE and the tBSS does perform full GCR correlation then the LCLS-BSS-Status will indicate accurately that the call can be locally switched. + +### 4.3.3.2 Intra-BSS Call Detection within the tMSC server + +The terminating MSC-Server performs intra-BSS call detection as follows: + +- if the oBSS Node ID in the GCR is the same as the terminating BSS Node ID, the terminating MSC-Server shall proceed as for the case when no Intra-BSS Call Detection is performed i.e. including the GCR and LCLS- + +Configuration Information Elements, but not including the LCLS-Correlation-Not-Needed Information Element, in the ASSIGNMENT REQUEST message (if LCLS is otherwise allowed from CN point of view). + +- if the oBSS Node ID in the GCR is different from the terminating BSS Node ID, the terminating MSC-Server shall include the GCR, LCLS-Configuration, and LCLS-Correlation-Not-Needed Information Elements within the ASSIGNMENT REQUEST message. + +NOTE: Intra-BSS call detection within the tMSC server can minimize the processing in some BSS implementations. + +#### 4.3.3.3 Intra-BSS Call Detection within the tBSS + +When receiving a GCR Information Element the tBSS may perform intra-BSS call detection as follows: + +- if the oBSS Node ID in the GCR is the same as the BSS Node ID of the terminating BSS the terminating BSS shall perform call leg correlation. +- if the oBSS Node ID in the GCR is different from the BSS Node ID of the terminating BSS the terminating BSS shall only store the GCR for the assigned call leg and does not perform call leg correlation. + +The tBSS shall indicate the resulting outcome to the tMSC server in the LCLS-BSS-Status Information Element within the ASSIGNMENT COMPLETE message. + +## 4.4 LCLS Connection Control + +LCLS connection control enables the Core Network to indicate to the BSS when the call is requested to be locally switched within the BSS or not. LCLS connection control is explicitly signalled on the A interface during Call Establishment, Handover and LCLS Break/(Re)Establishment using the LCLS\_CONNECT\_CONTROL message. + +Within the LCLS\_CONNECT\_CONTROL message, the LCLS-Connection-Status-Control Information Element shall indicate whether the BSS is requested to: + +- establish local switching (connect); +- do not establish local switching (this value is used for example in call hold to explicitly prevent LCLS connection); +- bi-cast at handover (This is a temporary status of an LCLS connection which is being broken during handover. The setting applies to the call leg which is not being handed over. After handover has been completed and LCLS is broken, the BSS shall adopt the previous LCLS-Connection-Status-Control value i.e. "connect" unless explicitly changed by the MSC Server. This means that any subsequent handover of the previous call leg back into the same BSS will enable LCLS without any change of LCLS-Connection-Status to this call leg). The temporary status settings shall be cleared by the BSS if set during a handover and the handover fails or is rejected. +- receive DL data at handover (This is a temporary status of an LCLS connection which is being broken during handover. The setting applies to the call leg which is not being handed over. After handover has been completed and LCLS is broken, the BSS shall adopt the previous LCLS-Connection-Status-Control value i.e. "connect" unless explicitly changed by the MSC Server. This means that any subsequent handover of the previous call leg back into the same BSS will enable LCLS without any change of LCLS-Connection-Status to this call leg). This setting does not change the UL bicasting and assumes the call leg to which it is applied is bicasting UL at handover in addition. The temporary status settings shall be cleared by the BSS if set during a handover and the handover fails or is rejected. +- release LCLS for the locally switched call (Release LCLS). + +LCLS through-connection is established when the BSS receives, on both call legs, the LCLS-Connection-Status-Control IE to allow and request LCLS to be established. + +The detailed call flows and procedures for signalling of the LCLS-Connection-Status-Control IE during Call Establishment, LCLS Break/(Re)Establishment, and Handover are defined in clauses 6, 7, and 8 respectively. + +The LCLS\_CONNECT\_CONTROL message and the usage of the LCLS-Connection-Status-Control IE are further detailed in sub-clause 16.3. + +## 4.5 LCLS Status Reporting + +### 4.5.1 LCLS BSS Status between BSS and Core Network + +LCLS BSS status is required between the BSS and the Core Network in order to keep the originating MSC server and the terminating MSC server updated of the LCLS status in the respective BSS. + +The LCLS-BSS-Status Information Element is used to indicate whether: + +- the call is locally switched with requested LCLS configuration +- the call is local but not yet locally switched (this indicates that the call has been correlated but not locally switched) +- the call is not possible to be locally switched (this indicates that the call has been determined not to be a local call) +- the call is no longer locally switched +- the requested LCLS-Configuration is not supported + +The inclusion of the LCLS-BSS-Status Information Element in responses to the MSC server indicates support of LCLS feature by the BSS. The usage of the LCLS-BSS-Status Information Element is further detailed in sub-clause 16.3. + +The LCLS-BSS-Status IE is explicitly signalled on the A interface during Call Establishment, LCLS Break/(Re)Establish LCLS, and Handover procedures. See clauses 6, 7 and 8 respectively. + +The LCLS-BSS-Status IE is also signalled explicitly in the LCLS\_NOTIFICATION message on the A interface, triggered by the BSS to notify the core network of any LCLS status changes in the BSS, e.g. BSS Initiated LCLS Break. The LCLS\_NOTIFICATION message is further detailed in sub-clause 16.3. + +### 4.5.2 LCLS Status within the Core Network + +LCLS status is required within the Core network in order to update all of the (G)MSC server and intermediate nodes in the call control path of the LCLS status of the call. + +LCLS-Status Information Element is explicitly signalled on the Nc interface during Call Establishment, LCLS Break/(Re)Establish, and Handover procedures when the LCLS status changes from before and after handover. See clauses 6, 7, and 8 respectively. The LCLS-Status is either indicated as changed status (LCLS-Status IE) to a change in the BSS or it may be indicated as request to change the LCLS-Status (LCLS-Status-Change IE) due to handover or supplementary service invocation for example. + +The LCLS-Status IE can indicate the following statuses: + +- the call is LCLS connected; +- the call is not LCLS connected; +- the call is LCLS feasible but not yet connected. + +The LCLS-Status-Change IE can indicate the following statuses: + +- LCLS is to be released; +- LCLS is to be released due to handover; +- LCLS is to be re-connected after LCLS break; +- Indicate DL data after handover - Handover Detected. + +The MSC Servers shall only generate or forward the LCLS Status IE through the CN if there is a change to the current CN status (i.e. there is not a one to one mapping of the LCLS-BSS Status and the LCLS Status in the CN). The usage of these elements: the LCLS Status IE signalled in the LCLS\_STATUS\_UPDATE message and the LCLS-Status-Change IE which is signalled in the LCLS\_STATUS\_CHANGE\_REQUEST message and LCLS\_STATUS\_CHANGE\_REQUEST ACKNOWLEDGEMENT message is further detailed in sub-clause 16.1. + +## 4.6 User Plane when LCLS is Active + +### 4.6.1 General + +When LCLS has been established for a call, the voice data on the user plane is locally switched within the BSS. When the call is locally switched the core network shall assume that no user plane data will be received from the BSS for the duration of the locally switched call unless explicitly requested via the LCLS-Configuration IE. + +When user plane data is required to be inserted by the core network, e.g. supplementary services, unless previously negotiated via the LCLS-Negotiation IE (see sub-clause 4.2) an LCLS Break procedure shall precede the insertion of user plane data. + +NOTE: During Handover procedures and LCLS Break procedures, the BSS may start to send the user plane data to the core network before all nodes in the routing path have updated their related LCLS status, see clauses 7 and 8. + +### 4.6.2 LCLS Configuration + +LCLS configuration is required in order to allow the Core Network to indicate to the BSS the LCLS connection preference. + +The LCLS Configuration Information Element is explicitly signalled on the A interface on a per call leg basis during Call Establishment and Handover procedures or at any time during the call using the LCLS\_CONNECT\_CONTROL message. See clauses 6 and 8 respectively. It is used to indicate if the local call shall be: + +- connected both-way in the BSS (basic LCLS connection) +- connected both-way in the BSS and bi-casted UL to the Core Network +- connected both-way in the BSS and send access DL from the Core Network (BSS may combine or replace local DL data with DL data from the Core Network) +- connected both-way in the BSS and send access DL from the Core Network, block local DL +- connected both-way in the BSS and bi-casted UL to the Core Network and send access DL from the Core Network (BSS may combine or replace local DL data with DL data from the Core Network) +- connected both-way in the BSS and bi-casted UL to the Core Network and send access DL from the Core Network, block local DL (BSS shall block local DL data but continue send UL data locally) + +If the BSS does not support a certain configuration this shall be indicated with the LCLS-BSS-Status IE set to "requested LCLS configuration is not supported" to the MSC Server. + +NOTE: If BSS supports LCLS feature, then at least one of the LCLS configurations is required to be supported. + +The usage of the LCLS Configuration IE is further detailed in sub-clause 16.3. + +--- + +## 5 General Circuit Switched Core Network Domain Architecture + +LCLS does not require any modifications to the basic reference architecture. The General CS core network domain architecture is specified in 3GPP TS 23.205 [2]. Network Architecture for CS Core Network Nodes and GSM/EDGE Radio Access Networks is specified in 3GPP TS 23.002 [8]. + +NOTE: LCLS does introduce a number of conceptual changes as described in sub-clause 4.1. + +## 6 Call Establishment + +### 6.1 Basic Mobile Originating Call + +#### 6.1.1 Basic Mobile Originating Call with BICC based CS core network + +##### 6.1.1.1 General + +The basic mobile originating call shall be established in accordance with 3GPP TS 23.205 [2]. The LCLS establishment may use forward or backward bearer establishment. The following sub-clauses describe the additional requirements related to the LCLS functionality. + +##### 6.1.1.2 Initial Addressing + +If the oMSC server supports the LCLS feature it shall generate a Global Call Reference (GCR) IE. The GCR IE is derived from the ITU-T *Global Call Reference IE* [5] and specified in detail in the clause 16 and in 3GPP TS 29.205 [6]. If the serving radio access is GERAN the Call Reference ID field of the GCR IE contains the originating BSS ID. + +The oMSC server shall then include the GCR IE, LCLS-Negotiation Request IE and LCLS-Configuration-Preference IE indicating the preferences for LCLS as defined in the sub-clause 4.2, clause 16 and in 3GPP TS 29.205 [6], together with the Supported Codecs List IE for OoBTC as specified in 3GPP TS 23.153 [4] in the IAM message to the succeeding call control node. + +##### 6.1.1.3 Access Bearer Assignment + +###### 6.1.1.3.1 Assignment performed after LCLS Negotiation through Core Network + +On receipt of the APM from the succeeding MSC server containing the LCLS-Negotiation Response IE, indicating local call connection is permitted, the oMSC server shall continue with the basic call establishment and if the serving radio access is GERAN shall include the GCR IE and the LCLS-Configuration IE (which is derived from the LCLS-Configuration-Preference IE) in the originating BSSAP Assignment Request message (see 3GPP TS 48.008 [7]). + +If the serving radio access is UTRAN the oMSC server shall save the LCLS-Negotiation Response IE and LCLS-Configuration-Preference IE but proceed with the call establishment as described in TS 23.205 [2]. + +###### 6.1.1.3.2 Assignment performed before LCLS Negotiation + +After generation of the GCR IE the oMSC initiates the access bearer assignment on the originating side and includes the GCR IE and the preliminary LCLS-Configuration IE (the final configuration can be different due to the following LCLS negotiation through the core network) in the originating BSSAP Assignment Request message. + +###### 6.1.1.3.3 oBSS behavior + +If the originating BSS supports LCLS and receives the Assignment Request message containing the GCR IE and the LCLS-Configuration IE the originating BSS shall store the GCR IE against the Assigned Call leg and shall check if it can support the requested LCLS-Configuration. The originating BSS shall report the outcome in LCLS-BSS-Status IE returned to the MSC server in the Assignment Complete message. + +If the originating BSS does not support LCLS then the GCR IE and the LCLS-Configuration IE will be ignored and no LCLS-BSS-Status IE will be returned in the Assignment Complete message. The oMSC server shall continue the call establishment as for a Non-LCLS call. + +##### 6.1.1.4 Backward LCLS Negotiation + +At reception of an APM, ACM or CPG message with the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE the oMSC server shall check whether a new value of the LCLS-Configuration-Preference settings require the change of the requested LCLS configuration and if so the oMSC server shall include the updated LCLS-Configuration IE in the BSSAP message LCLS Connect Control to the BSS, see sub-clause 6.1.1.5. If the LCLS-Negotiation Response IE indicates "LCLS Not Allowed" or "LCLS not supported by subsequent node" then the oMSC Server shall not permit LCLS connection unless any subsequent LCLS negotiation results in LCLS being feasible. + +NOTE 1: The oMSC can still signal the GCR to the BSS in order to avoid a subsequent Assignment to pass the GCR if LCLS becomes feasible at a later time during the call. + +At reception of an unsolicited APM message without LCLS-Negotiation Response IE then the oMSC shall handle the APM but not change the LCLS-Configuration or any LCLS behaviour. + +NOTE 2: APM is used for other services or applications and need not include LCLS-Negotiation Response IE. + +If the first backward message (APM or ACM) does not contain the LCLS-Negotiation Response IE then the oMSC Server shall not proceed with further LCLS signalling for this call. + +NOTE 3: This indicates to the oMSC server that the LCLS feature is not supported by succeeding node. + +#### 6.1.1.5 LCLS Through-Connection + +If the originating BSS determines that the call is local and can be locally switched it shall not through-connect the two parties unless explicitly indicated to do so by receiving the LCLS-Connection-Status-Control IE set to "Connect" for both call legs. + +When the oMSC server receives the ANM from the succeeding MSC server with the LCLS-Status IE indicating "LCLS is feasible but not yet connected" it shall send the BSSAP message LCLS-Connect-Control to the originating BSS containing the LCLS-Connection-Status-Control IE set to "Connect". If the value of the required LCLS Configuration is not the same as the value requested within the Assignment Request message, the oMSC Server shall also include the LCLS Configuration IE in the LCLS-Connect-Control message. + +If the BSS has received the LCLS-Connection-Status-Control IE set to "Connect" for both call legs associated to the LCLS call it shall locally switch the user plane between the two call legs and report the through-connection via the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration" in the LCLS-Connect-Control Acknowledge message. The CN user plane shall be kept through-connected as described in the sub-clause 4.6. + +If the call is not yet locally switched when returning the LCLS-Connect-Control Acknowledge message but becomes locally switched at a later time (for example due to the LCLS-Connection-Status-Control IE requesting "Connect" at the second call leg) the BSS shall report the change in status via the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration" within the LCLS-Notification message as specified in 3GPP TS 48.008 [7]. + +NOTE: This should not occur at the oMSC server for normal call establishment as the oMSC server should always be the last (second) node sending the LCLS-Connect-Control message to the BSS. + +#### 6.1.1.6 LCLS Status Reporting + +When the oMSC server receives the LCLS-Connect-Control Acknowledge message from the originating BSS with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration" it shall inform the succeeding MSC server with the APM message containing the LCLS Status IE set to "LCLS connected". + +During the LCLS call establishment and ongoing call any change to the LCLS connection status is reported by the BSS to the core network and only if it results in a change of the LCLS status in the core network, the updated LCLS status shall be signalled by the oMSC server to the succeeding nodes. See also sub-clause 4.5. + +#### 6.1.1.7 MGW/User plane + +The MGW/user plane shall be established in accordance with 3GPP TS 23.205 [2]. + +### 6.1.2 Basic Mobile Originating Call with SIP-I based CS core network + +#### 6.1.2.1 General + +The basic mobile originating call shall be established in accordance with 3GPP TS 23.231 [3]. The LCLS principles introduced in the sub-clause 6.1.1 for BICC protocol messages should also apply to SIP-I signalling cases. + +#### 6.1.2.2 Initial Addressing + +The oMSC server shall send the initial SIP-I INVITE request with the GCR IE, LCLS-Negotiation Request IE and LCLS-Configuration-Preference IE included within the encapsulated IAM message if the LCLS feature is supported. If an access bearer assignment has not been completed the initial SDP offer shall indicate that the local preconditions have not been met. + +### 6.1.2.3 Access Bearer Assignment + +On receipt of the SIP-I 183 Session Progress provisional response from the succeeding MSC server containing the LCLS-Negotiation Response IE and LCLS-Configuration-Preference IE included within the encapsulated APM message, the oMSC server shall continue with the basic call establishment as specified in the sub-clause 6.1.1.3. + +### 6.1.2.4 Backward LCLS Negotiation + +At reception of the SIP-I 183 Session Progress provisional response with the LCLS-Negotiation Response IE and LCLS-Configuration-Preference IE included within the encapsulated APM message the oMSC server shall check the value of the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE as specified in the sub-clause 6.1.1.4. + +If the first 183 Session Progress provisional response does not contain the LCLS Negotiation Response IE then the oMSC Server shall not proceed with further LCLS signalling for this call. + +NOTE: This indicates to the oMSC server that LCLS feature is not supported by succeeding node. + +### 6.1.2.5 LCLS Through-Connection + +On the reception of the 200 OK final response to the initial INVITE with the encapsulated ANM message containing LCLS-Status IE the oMSC server shall apply the LCLS Through-Connection procedure specified in the sub-clause 6.1.1.5. + +### 6.1.2.6 LCLS Status Reporting + +The oMSC server shall send the SIP-I INFO request containing the LCLS Status IE included within the encapsulated APM message to the succeeding MSC server when LCLS Status Reporting needs to be performed according to procedure described in the sub-clause 6.1.1.6. + +### 6.1.2.7 MGW/User plane + +The MGW/user plane shall be established in accordance with 3GPP TS 23.205 [2]. + +## 6.2 Basic Mobile Terminating Call + +### 6.2.1 Basic Mobile Terminating Call with BICC based CS core network + +#### 6.2.1.1 General + +The basic mobile terminating call shall be established in accordance with 3GPP TS 23.205 [2]. The LCLS establishment may use forward or backward bearer establishment. The following sub-clauses describe the additional requirements related to the LCLS functionality. + +#### 6.2.1.2 Actions at Intermediate Nodes (including GMSC) + +##### 6.2.1.2.1 Initial Addressing + +If an intermediate node supports the LCLS feature and receives the LCLS-Negotiation Request IE and LCLS-Configuration-Preference IE from a preceding node in the IAM it may modify the LCLS-Configuration-Preference IE based on its own LCLS configuration requirements, and shall then forward the resulting LCLS-Configuration-Preference IE together with GCR IE and LCLS-Negotiation Request IE to the succeeding node. The rules for modifying the LCLS-Configuration-Preference IE are specified in the sub-clause 4.2. + +If LCLS is not permitted by the intermediate node based on its own LCLS requirements then it shall set the LCLS-Negotiation Request IE to value "LCLS not allowed". The intermediate node shall forward the LCLS-Negotiation Request IE, LCLS-Configuration-Preference IE and GCR IE to the succeeding node. + +##### 6.2.1.2.2 Backward LCLS Negotiation + +If the intermediate node supports the LCLS feature and has sent the GCR IE, the LCLS-Negotiation Request IE and LCLS-Configuration-Preference IE within IAM message towards the succeeding node further action depends on the content of the first received backward message (APM message or ACM). + +- If the intermediate node receives the first backward message (APM or ACM) without the LCLS-Negotiation Response IE it shall include the LCLS-Negotiation Response IE indicating "LCLS not supported by subsequent node into APM/ACM before forwarding the APM/ACM to the preceding node. + +NOTE 1: This indicates to preceding nodes that the LCLS feature is not supported by the succeeding nodes except the intermediate node but that further LCLS negotiation can occur. Specifically this can arise due to subsequent call control signalling to other succeeding nodes, e.g. due to changed routing, handover or supplementary service interactions. If the intermediate node does not include any LCLS-Negotiation Result IE then it implicitly indicates to the preceding node that LCLS feature is not supported by the intermediate node and no further LCLS signalling is permitted for the call. +- When the received APM/ACM contains the LCLS-Negotiation Response IE then the forwarding MSC server shall forward the received LCLS-Negotiation Response IE and LCLS-Configuration-Preference IE to the preceding node. + +If the intermediate node has forwarded LCLS-Negotiation Response IE in the first backward APM/ACM message and receives an APM which does not include LCLS Negotiation Response IE then the intermediate node shall handle the APM but shall not include any LCLS IE when passing on such APM's; no changes to LCLS status shall result. + +NOTE 2: APM is used for other services or applications and need not include LCLS IEs. + +Other information elements shall be treated as specified in 3GPP TS 23.205 [2] and in 3GPP TS 23.231 [3]. + +#### 6.2.1.2.3 Through-Connection + +The procedure specified in 3GPP TS 23.205 [2] shall be applied. + +#### 6.2.1.2.4 LCLS Status Reporting within CN + +If the LCLS status is received from its adjacent node, the MSC server shall update the LCLS status and shall pass on to the next node only if the LCLS status has changed. See also sub-clause 4.5. + +#### 6.2.1.2.5 MGW/User plane + +The MGW/user plane shall be established in accordance with 3GPP TS 23.205 [2]. + +### 6.2.1.3 Actions at Terminating Call side + +#### 6.2.1.3.1 Initial Addressing + +If the tMSC server supports LCLS feature and receives the GCR IE, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE it may modify the LCLS-Configuration-Preference IE based on its own LCLS configuration requirements. The rules for modifying the LCLS-Configuration-Preference IE are specified in the clause 4.2 and in 3GPP TS 29.205 [6]. + +#### 6.2.1.3.2 Backward LCLS Negotiation + +If the tMSC server supports LCLS feature then it shall return the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE to the preceding node in the APM or the ACM message. + +#### 6.2.1.3.3 Access Bearer Assignment + +If the serving radio access is GERAN then when the tMSC server performs the access bearer assignment it shall include the GCR IE and the LCLS-Configuration IE (which is derived from the LCLS-Configuration-Preference IE) in the BSSAP Assignment Request message sent to the terminating BSS (see 3GPP TS 48.008 [7]). + +If the tMSC server supports the optional "intra-Network call detection" procedure and determines that the Network ID within the GCR IE is not equal to the own (tMSC) Network ID, the tMSC server shall also include the "LCLS-Correlation-Not-Needed" IE in the Assignment Request message (see sub-clause 4.3.2). + +If the tMSC server supports the optional "intra-BSS call detection" procedure and determines that the BSS ID within the GCR IE is not equal to the terminating BSS ID, the tMSC server shall also include the "LCLS-Correlation-Not-Needed" IE in the Assignment Request message (see sub-clause 4.3.3). + +If the terminating BSS supports LCLS and receives the Assignment Request message containing the GCR IE and the LCLS-Configuration IE, the BSS shall store the GCR against the Assigned Call leg and check if it can support the requested LCLS-Configuration. Unless the BSS supports the optional "intra-Network call detection" procedure (see sub-clause 4.3.2) or optional "intra-BSS call detection" procedure (see sub-clause 4.3.3) it shall perform a correlation of the received GCR to see if another call leg has been assigned with the same GCR and report the outcome in the LCLS-BSS-Status IE returned to the tMSC server in the Assignment Complete message. + +If the terminating BSS does not support LCLS then the GCR IE and the LCLS-Configuration IE will be ignored and no LCLS-BSS-Status IE will be returned in the Assignment Complete message. The tMSC server shall continue the call establishment as for normal Non-LCLS call. + +#### 6.2.1.3.4 LCLS Through-Connection + +If the terminating BSS determines that the call is local and can be locally switched it shall not through-connect the two parties unless explicitly indicated to do so by receiving the LCLS-Connection-Status-Control IE set to "Connect" for both call legs. + +When the tMSC server receives "answer" from the terminating UE it shall send the BSSAP message LCLS-Connect-Control containing the LCLS-Connection-Status-Control IE set to "Connect" and send the ANM message with the LCLS-Status IE indicating "LCLS is feasible but not yet connected" to the preceding MSC server. + +If the BSS has received the LCLS-Connection-Status-Control IE set to "Connect" for both call legs associated to the LCLS call it shall locally switch the user plane between the two call legs and report the through-connection via LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration" in the LCLS-Connect-Control Acknowledge message. The CN user plane shall be kept through-connected as described in the sub-clause 4.6. + +If the call is not yet locally switched when returning the LCLS-Connect-Control Acknowledge message but becomes locally switched at a later time (for example due to the LCLS-Connection-Status-Control IE requesting "Connect" at the second call leg) the BSS shall report the change in status via LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration" within the LCLS-Notification message as specified in 3GPP TS 48.008 [7]. + +#### 6.2.1.3.5 LCLS Status Reporting + +During the LCLS call establishment and ongoing call any change to the LCLS connection status is reported by the BSS to the core network and only if it results in a change of the LCLS status in the core network the updated LCLS status shall be signalled by the tMSC server to the preceding node. See also sub-clause 4.5. + +#### 6.2.1.3.6 MGW/User plane + +The MGW/user plane shall be established in accordance with 3GPP TS 23.205 [2]. + +### 6.2.2 Basic Mobile Terminating Call with SIP-I based CS core network + +#### 6.2.2.1 General + +The basic mobile terminating call shall be established in accordance with 3GPP TS 23.231 [3]. The LCLS principles using introduced in the sub-clause 6.2.1 for BICC protocol messages should also apply to SIP-I signalling cases. + +#### 6.2.2.2 Actions at Intermediate Nodes (including GMSC) + +##### 6.2.2.2.1 Initial Addressing + +If an intermediate node supports the LCLS feature and receives the GCR IE, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE included within the encapsulated IAM message from a preceding node in the SIP-I INVITE request it may modify the LCLS-Configuration-Preference IE based on its own LCLS configuration requirements, and shall then forward the initial INVITE request with the resulting LCLS-Configuration-Preference IE together with GCR IE and LCLS-Negotiation Request IE included within the encapsulated IAM message to the succeeding node. + +##### 6.2.2.2.2 Backward LCLS Negotiation + +On the receipt of the 183 Session Progress provisional response the intermediate node shall apply the Backward LCLS Negotiation procedure specified in the sub-clause 6.2.1.2.2. + +### 6.2.2.2.3 Through-Connection + +See sub-clause 6.2.1.2.3. + +### 6.2.2.2.4 LCLS Status Reporting within CN + +See sub-clause 6.2.1.2.4. + +### 6.2.2.2.5 MGW/User plane + +See sub-clause 6.2.1.2.5. + +## 6.2.2.3 Actions at Terminating Call side + +### 6.2.2.3.1 Initial Addressing + +See sub-clause 6.2.1.3.1. + +### 6.2.2.3.2 Backward LCLS Negotiation + +If the tMSC server supports LCLS feature then it shall return the final LCLS-Negotiation Response IE and LCLS-Configuration-Preference IE included within the encapsulated APM message to the preceding node in the SIP-I 183 Session Progress provisional response. + +### 6.2.2.3.3 Access Bearer Assignment + +See sub-clause 6.2.1.3.3. + +### 6.2.2.3.4 LCLS Through-Connection + +The tMSC server shall apply the LCLS Through-Connection procedure specified in the sub-clause 6.2.1.3.4. The LCLS-Status IE indicating "LCLS is feasible but not yet connected" shall be included in the ANM message encapsulated in the 200 OK final response to the initial INVITE. + +### 6.2.2.3.5 LCLS Status Reporting + +See sub-clause 6.2.1.3.5. + +### 6.2.2.3.6 MGW/User plane + +See sub-clause 6.2.1.3.6. + +## 6.3 Basic Mobile to Mobile End to End Call Examples + +### 6.3.1 Basic Call Establishment Connection Model for LCLS + +Figure 6.3.1.1 shows the network model for the basic call establishment for a Local Call. The oMSC server seizes one context with two bearer terminations in the oMGW. The bearer termination T1 is used for the bearer towards the oBSS and the bearer termination T2 is used for the bearer towards the iMSC selected iMGW. The iMSC server seizes one context with two bearer terminations in the iMGW. The bearer termination T6 is used for the bearer towards the tMSC server selected tMGW and the bearer termination T5 is used for the bearer towards the preceding oMGW. The tMSC server seizes one context with two bearer terminations in the tMGW. The bearer termination T3 is used for the bearer towards the iMSC selected iMGW and bearer termination T4 is used for the bearer towards the tBSS. + +![Diagram of Connection Model 1: After Alerting, Backward Through Connection. It shows a tUE and oUE connected to an oBSS/tBSS. The oBSS/tBSS is connected to an oMSC-S, which is part of a control signalling path (green dashed line) through iMSC-S and tMSC-S. The oBSS/tBSS is also connected to an oMGW (with ports T1, T2, oC). The oMGW is connected to an iMGW (with ports T5, T6, iC), which is connected to a tMGW (with ports T3, T4, tC). A red solid line represents the user plane link from the tUE to the oUE. A blue dashed line represents the backward user plane link from the oMGW to the oUE.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +- Control plane link which transmits signalling +- User plane link path through CN, connected or disconnected +- User plane link which transmits real user plane data within BSS and UEs +- User plane link which transmits real user plane data in backward direction from the CN towards oUE (e.g. network provided ring-back tone) + +Diagram of Connection Model 1: After Alerting, Backward Through Connection. It shows a tUE and oUE connected to an oBSS/tBSS. The oBSS/tBSS is connected to an oMSC-S, which is part of a control signalling path (green dashed line) through iMSC-S and tMSC-S. The oBSS/tBSS is also connected to an oMGW (with ports T1, T2, oC). The oMGW is connected to an iMGW (with ports T5, T6, iC), which is connected to a tMGW (with ports T3, T4, tC). A red solid line represents the user plane link from the tUE to the oUE. A blue dashed line represents the backward user plane link from the oMGW to the oUE. + +Connection Model 1: After Alerting, Backward Through Connection + +![Diagram of Connection Model 2: After answer, Call is locally switched. This diagram is similar to the first one but shows a different user plane configuration. A red solid line labeled 'User Plane Data' is shown within the oBSS/tBSS, connecting the tUE and oUE. A dotted line labeled 'Non LCLS User Plane' is shown between the oMGW and the iMGW. The control signalling path (green dashed line) remains the same.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) + +Diagram of Connection Model 2: After answer, Call is locally switched. This diagram is similar to the first one but shows a different user plane configuration. A red solid line labeled 'User Plane Data' is shown within the oBSS/tBSS, connecting the tUE and oUE. A dotted line labeled 'Non LCLS User Plane' is shown between the oMGW and the iMGW. The control signalling path (green dashed line) remains the same. + +Connection Model 2: After answer, Call is locally switched + +Figure 6.3.1.1: Basic Call Establishment Connection Model for Local Call + +### 6.3.2 LCLS established, Basic Call Example with BICC based CS core network, forward bearer establishment + +Figures 6.3.2.1, 6.3.2.2 and 6.3.2.3 show the message sequence example for the basic call establishment for LCLS. In this example the oUE and the tUE belong to the same BSS (marked as oBSS and tBSS) and the CN permits LCLS. The example is based on examples from 3GPP TS 23.205 [2] for the basic mobile originating call, forward bearer establishment (case when access bearer assignment is requested on the originating side after reception of Bearer Information message) and the basic mobile terminating call, forward bearer establishment. + +![Sequence diagram showing the Basic Call Establishment Flow when call is locally switched, forward bearer establishment. The diagram involves ten lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. The process starts with the oUE sending a Service Request + CL3 to the oMSC. The oMSC responds with SETUP and CALL PROCEEDING. The oMSC then retrieves the oBSS ID and generates a Global Call Reference. It sends an IAM message to the iMSC, which in turn sends an IAM message to the tMSC. The tMSC pages the tUE, receives a response, sends SETUP, and receives a Call Confirmed. The tMSC then adds network side termination and sends an APM message to the iMSC. The iMSC adds network side termination and sends an APM message to the oMSC. The oMSC then performs network side bearer establishment with the iMGW and tMGW.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +``` + +sequenceDiagram + participant oUE + participant oBSS + participant oMGW + participant oMSC + participant iMGW + participant iMSC + participant tMSC + participant tMGW + participant tBSS + participant tUE + + Note left of oMSC: 3. Retrieve oBSS ID and use it to generate Global Call Reference + + oUE->>oMSC: 1. oUE accesses oMSC: Service Request + CL3 + oMSC-->>oUE: 2. SETUP + oMSC-->>oUE: 2a. CALL PROCEEDING + oMSC->>iMSC: 4. IAM [Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference] + iMSC->>tMSC: 5. IAM [Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference] + tMSC->>tUE: 6. Paging tUE + tUE-->>tMSC: Paging response + CL3 + tMSC->>tUE: 7. SETUP + tUE-->>tMSC: 8. Call Confirmed + tMSC->>tMGW: 9. Add network side termination: ADD request ($)/ADD reply (T3) + Note right of tMSC: Context (tC) + tMSC->>iMSC: 10. APM [SC, ACL, LCLS-Negotiation Response, LCLS-Configuration-Preference] + iMSC->>iMGW: 11a. Add network side termination: ADD request ($) / ADD reply (T6) + Note right of iMSC: Context (iC) + Note over iMGW, tMGW: Network side Bearer Establishment + iMGW->>iMSC: 11b. Add network side termination: ADD request ($) / ADD reply (T5) + Note right of iMSC: Context (iC) + iMSC->>oMSC: 12. APM [SC, ACL, LCLS-Negotiation Response, LCLS-Configuration-Preference] + +``` + +Sequence diagram showing the Basic Call Establishment Flow when call is locally switched, forward bearer establishment. The diagram involves ten lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. The process starts with the oUE sending a Service Request + CL3 to the oMSC. The oMSC responds with SETUP and CALL PROCEEDING. The oMSC then retrieves the oBSS ID and generates a Global Call Reference. It sends an IAM message to the iMSC, which in turn sends an IAM message to the tMSC. The tMSC pages the tUE, receives a response, sends SETUP, and receives a Call Confirmed. The tMSC then adds network side termination and sends an APM message to the iMSC. The iMSC adds network side termination and sends an APM message to the oMSC. The oMSC then performs network side bearer establishment with the iMGW and tMGW. + +**Figure 6.3.2.1: Basic Call Establishment Flow when call is locally switched, forward bearer establishment** + +- Service Request handling. +- Originating Call SETUP. +- 2a. The oMSC server replies with the CALL PROCEEDING message to indicate that the call is being processed. +3. If the oMSC server supports LCLS it retrieves the oBSS ID and generates the Global Call Reference for the call. +4. The oMSC server sends the IAM message including supported codecs list, GCR with encapsulated oBSS ID, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. +5. If the iMSC server supports LCLS it may modify the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE due to CAMEL, supplementary service requirements etc. before sending the IAM message containing the GCR with the encapsulated oBSS ID, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. +6. The tMSC server pages the tUE. +7. The tMSC server performs call Setup. +8. The tUE confirms the call. + +- 9. The tMSC server requests the tMGW to prepare for the network side bearer establishment. +- 10. After the tMGW has replied with the bearer address and the binding reference the tMSC server returns the APM message with the selected codec, available codec list and if LCLS is supported, the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. +- 11a. When the bearer information is received the iMSC server requests the seizure of the outgoing network side bearer termination. +- 11b. After the outgoing side bearer termination is seized the iMSC server requests the seizure of the incoming network side bearer termination. +During the seizure of the outgoing side and the incoming side bearer termination the iMSC server will also request the iMGW to through-connect the bearer terminations so that the bearer will be both way through-connected. +- 12. The iMSC server transfers the APM message with the selected codec, available codec list, the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. + +![Sequence diagram for Basic Call Establishment when call is locally switched, forward bearer establishment. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. The diagram shows steps 13a through 24, including ADD requests, ASSIGNMENT REQUEST/COMPLETE messages, COT messages, and Ring-back tones.](3e2a8dc8c5537dbe703cdcb0e21e4e1b_img.jpg) + +The sequence diagram illustrates the interaction between various network elements for call establishment. The lifelines are oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. + +Key steps include: + + +- 13a.** oMSC sends an 'Add network side termination: ADD request (\$)' to oMGW, which replies with 'ADD reply (T2)'. Context (oC) is passed to iMGW. +- 13b.** oMSC sends an 'Add access side termination: ADD request (\$)' to oBSS, which replies with 'ADD reply (T1)'. Context (oC) is passed to iMSC. +- 14.** oMSC sends an 'ASSIGNMENT REQUEST (GCR, LCLS-Configuration)' to oBSS. +- 15.** oBSS responds with 'ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not possible to be locally switched")' to oMSC. +- 16.** oMSC sends a 'COT' message to iMSC. +- 17.** iMSC sends a 'COT' message to tMSC. +- 18.** tMSC sends an 'Add access side termination: ADD request (\$)' to tMGW, which replies with 'ADD reply (T4)'. Context (tC) is passed to iMSC. +- 19a.** A dashed box indicates an optional intra-network call detection procedure. +- 19b.** tMSC sends an 'ASSIGNMENT REQUEST (GCR, LCLS-Configuration)' to tBSS. +- 20.** tBSS responds with 'ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not yet locally switched")' to tMSC. +- 21.** tUE reports 'Alerting' to tBSS. +- 22a.** tMSC sends an 'ACM' message to iMSC. +- 22b.** tMSC sends a 'MOD request: send Ring-back tone' to tMGW. +- 23.** iMSC sends an 'ACM' message to oMSC. +- 24.** oMSC reports 'Alerting' to oBSS. +- Ring-back Tone:** A thick blue arrow indicates the ring-back tone being sent from tMGW to oUE. + + Green boxes highlight 'Network side Bearer Establishment' (steps 13a, 14, 15) and 'Access side Bearer Establishment' (steps 13b, 16, 17, 18, 19b, 20). + +Sequence diagram for Basic Call Establishment when call is locally switched, forward bearer establishment. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. The diagram shows steps 13a through 24, including ADD requests, ASSIGNMENT REQUEST/COMPLETE messages, COT messages, and Ring-back tones. + +Figure 6.3.2.2: Basic Call Establishment when call is locally switched, forward bearer establishment (continuation of figure 6.3.2.1) + +- 13a. When the bearer information is received the oMSC server requests the seizure of the network side bearer termination. + +- 13b. After the network side bearer information is seized the oMSC server requests the seizure of the access side bearer termination. +During the seizure of the network side or the access side bearer termination the oMSC server will also request the oMGW to through-connect the bearer terminations so that the bearer will be backward through-connected. +14. The oMSC server determines whether LCLS is allowed in the core network based on the returned LCLS-Negotiation IE and if so the oMSC server includes the LCLS-Configuration IE in the ASSIGNMENT REQUEST message along with the GCR IE. +15. The oBSS returns the ASSIGNMENT COMPLETE message with the LCLS-BSS-Status IE indicating "call not possible to be locally switched". +16. When the access assignment is completed the oMSC server sends the Continuity (COT) message to the iMSC server. +17. The iMSC server transfers the COT message to the tMSC server. +18. The tMSC server requests the seizure of the access side bearer termination. If not requested during the seizure of network side bearer termination (in step 9) the tMSC server will also request the tMGW to through-connect the bearer terminations so that the bearer will be backward through-connected. +- 19a. If the tMSC server supports the optional "intra-Network call detection" procedure it compares its own Network ID with the Network ID received within the Global Call Reference IE. +If the tMSC server supports the optional "intra-BSS call detection" procedure it compares the BSS ID of the selected terminating BSS with the oBSS ID received within the Global Call Reference IE at this step. Since the oUE and the tUE belong to the same BSS the call continues the same way as for the basic LCLS establishment without this pre-check. +- 19b. The tMSC server performs the access bearer assignment and sends the ASSIGNMENT REQUEST message containing the GCR IE and the LCLS-Configuration IE if LCLS is permitted in the core network. +20. The oBSS/tBSS performs the GCR correlation. Since the GCR correlation has identified the call as an intra BSS call and LCLS is allowed in the BSS, the tBSS returns the ASSIGNMENT COMPLETE message with the LCLS-BSS-Status IE indicating "Call not yet locally switched". +- 20a. Since the GCR correlation has identified the call as an intra BSS call and LCLS is allowed in the BSS, the oBSS signals the LCLS status change by sending the LCLS\_NOTIFICATION message with the LCLS-BSS-Status IE set to "Call not yet locally switched". +21. The tUE reports alerting. +- 22a, b. The tMSC server returns the ACM message and requests the tMGW to provide a ring-back tone. +23. The iMSC server transfers the ACM message to the oMSC server. +24. The oMSC server reports alerting. + +![Sequence diagram for Basic Call Establishment when call is locally switched, forward bearer establishment. The diagram shows interactions between oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. It details the signaling flow for LCLS (Local Call Switching) and bearer establishment. A large red arrow at the bottom indicates the call is locally switched.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +The sequence diagram illustrates the following steps: + +- 25.** tUE reports: Connect to tMSC. +- 25a.** tMSC returns CONNECT ACK to tUE. +- 26.** tMSC sends LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "connect") to tBSS. +- 27.** tBSS returns LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call not yet locally switched") to tMSC. +- 28.** tMSC sends MOD request: stop tone, bothway through-connect to tMGW. Context (tC) is established. +- 29.** tMSC sends ANM [LCLS status = "LCLS feasible but not yet connected"] to iMSC. +- 30.** iMSC sends ANM [LCLS status = "LCLS feasible but not yet connected"] to oMSC. +- 31.** oMSC sends MOD request: bothway through-connect to oMGW. Context (oC) is established. +- 32.** oMSC reports: Connect to oBSS. +- 32a.** oBSS returns CONNECT ACK to oMSC. +- 33.** oMSC sends LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "connect") to oBSS. +- 34a.** oBSS returns LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") to oMSC. +- 34b.** tMSC sends LCLS\_NOTIFICATION (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") to tBSS. +- 34c.** oMSC sends MOV request (T1)/ MOV reply to oMGW. Context (Cs) Isolate bearer termination is established. (Note: If oMSC supports option to configure oMGW to isolate access side termination from network side termination and LCLS negotiation result allows it:) +- 34d.** tMSC sends MOV request (T4)/ MOV reply to tMGW. Context (Cs) Isolate bearer termination is established. (Note: If tMSC supports option to configure tMGW to isolate access side termination from network side termination and LCLS negotiation result allows it:) +- 35.** oMSC sends LCLS status update: APM [LCLS-Status = "LCLS connected"] to iMSC. +- 36.** tMSC sends LCLS status update: APM [LCLS-Status = "LCLS connected"] to iMSC. + +A large red arrow at the bottom of the diagram points from the oBSS to the tBSS, labeled **"Call is locally Switched"**. + +Sequence diagram for Basic Call Establishment when call is locally switched, forward bearer establishment. The diagram shows interactions between oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. It details the signaling flow for LCLS (Local Call Switching) and bearer establishment. A large red arrow at the bottom indicates the call is locally switched. + +**Figure 6.3.2.3: Basic Call Establishment when call is locally switched, forward bearer establishment (continuation of figure 6.3.2.2)** + +25. The tUE answers the call. +- 25a. The tMSC server returns the CONNECT ACKNOWLEDGE message to the tUE. +26. The tMSC server indicates to the tBSS that this call leg is ready to be locally switched by sending the LCLS\_CONNECT\_CONTROL message (note the BSS cannot through-connect LCLS until it receives the same indication from the oMSC server). +27. The tBSS returns the LCLS\_CONNECT\_CONTROL\_ACK message with the LCLS-BSS-Status IE set to "Call not yet locally switched" since the BSS has not received the same order from the oMSC server. +28. When the tMSC server receives the Connect message it requests the tMGW to stop providing ring-back tone to the calling party and requests to bothway through-connect the bearer. +29. The tMSC server returns the ANM message with the LCLS-Status IE indicating "LCLS is feasible but not yet connected". +30. The oMSC server receives the ANM message with the LCLS-Status IE indicating "LCLS is feasible but not yet connected". +31. The oMSC server request the oMGW to bothway through-connect the bearer. + +32. The oMSC server reports Answer/Connect to the oUE. +- 32a. The oUE completes the call establishment with the CONNECT ACKNOWLEDGE message. +33. The oMSC server requests the oBSS to connect LCLS since the received ANM message indicated "LCLS is feasible but not yet connected". +- 34a. Since the BSS has received the through connect request for both call legs the oBSS returns the LCLS\_CONNECT\_CONTROL\_ACK message with the LCLS-BSS-Status IE set to "call is locally switched with requested LCLS configuration". + - NOTE 1: If the BSS cannot locally through-connect the call at this time then it is indicated by setting the LCLS-BSS-Status IE set to "the call is not yet locally switched". If at a later time the BSS can locally switch the call, this is indicated by sending the LCLS\_NOTIFICATION message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration". +- 34b. Since the BSS has received the through connect request for both call legs the tBSS signals the LCLS status change by sending the LCLS\_NOTIFICATION message with the LCLS-BSS-Status IE set to "call is locally switched with requested LCLS configuration". +- 34c. If the oMSC server supports the option to configure its Access MGW to isolate the access side termination from the network side termination and LCLS negotiation indicated that no succeeding node requires the UL data from the oUE then the oMSC server requests the oMGW to isolate the access side termination T1 from the network side termination T2. +- 34d. If the tMSC server supports the option to configure its Access MGW to isolate the access side termination from the network side termination and LCLS negotiation indicated that no preceding node requires the UL data from the tUE then the tMSC server requests the tMGW to isolate the access side termination T4 from the network side termination T3. + - NOTE 2: The MSC server can also use the Change Through-Connection procedure and requests the MGW to change the through-connection of the bearer to inactive instead of using of the Isolate Bearer termination procedure, see 3GPP TS 23.205 [2]. +35. The oMSC server signals the change of the LCLS status through the Core Network by sending the APM message with the LCLS-Status IE set to "LCLS connected". +36. The iMSC server transfers the change of the LCLS status to the tMSC server. + +### 6.3.3 LCLS not established, Basic Call Example with BICC based CS core network + +The Figure 6.3.1 shows the message sequence example for the basic call establishment for LCLS when the call could not be locally switched. In this example the CN permits LCLS but the oUE and the tUE belong to different BSS's (marked as oBSS and tBSS). The example is based on examples from 3GPP TS 23.205 [2] for the basic mobile originating call, forward bearer establishment and the basic mobile terminating call, forward bearer establishment. + +![Sequence diagram for Basic Call Establishment Flow when call is not locally switched. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. The diagram shows steps 19a through 30b, including optional call detection, assignment requests, and connection establishment.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) + +For preceding signaling sequences for basic call setup steps 1- 18 see figures 6.3.2.1 and 6.3.2.2 + +**19a.** tMSC performs optional Intra-Network Call Detection and/or Intra-BSS Call Detection if supported. + +**19b.** ASSIGNMENT REQUEST (GCR, LCLS-Configuration [, LCLS-Correlation-Not-Needed]) + +**20.** ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not possible to be locally switched") + +Access Side Bearer Establishment + +**21.** tUE reports: Alerting + +**22a.** ACM + +Context (tC) + +**22b.** MOD request: send Ring-back tone + +**23.** ACM + +**24.** oMSC reports: Alerting + +Ring-back Tone + +**25a.** CONNECT + +**25b.** CONNECT ACK + +**26.** MOD request: stop tone, bothway through-connect + +Context (tC) + +**27.** ANM + +**28.** ANM + +**29.** MOD request: bothway through-connect + +Context (oC) + +**30a.** CONNECT + +**30b.** CONNECT ACK + +Sequence diagram for Basic Call Establishment Flow when call is not locally switched. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. The diagram shows steps 19a through 30b, including optional call detection, assignment requests, and connection establishment. + +**Figure 6.3.3.1: Basic Call Establishment Flow when call is not locally switched** + +1 – 18. The basic call establishment procedure between the UE-1 and the UE-2 is the same as specified in steps 1-18 of sub-clause 6.3.2.1. + +19a. If the tMSC server supports the optional "Intra-Network Call Detection" procedure it may compare its own Network ID with the Network ID received within the Global Call Reference (GCR) IE. + If the tMSC server supports the optional "Intra-BSS Call Detection" procedure it may compare the BSS ID of the selected terminating BSS with the value of the originating BSS ID received within the GCR IE at this step. + In this case, the result of the "Intra-Network Call Detection" procedure or "Intra-BSS Call Detection" procedure is that the call is not an intra-Network or an intra-BSS call. + +19b. The tMSC server performs the terminating access bearer assignment and sends the ASSIGNMENT REQUEST message containing the GCR IE and the LCLS-Configuration IE if LCLS is permitted in the core network. + If the tMSC server performed the "Intra-Network Call Detection" procedure in step 19a and/or the tMSC server performed the "Intra-BSS Call Detection" procedure in step 19a, then the tMSC server includes the "LCLS-Correlation-Not-Needed" IE in the ASSIGNMENT REQUEST message since the oUE and the tUE belong to the different BSS's. + +20. The tBSS returns the ASSIGNMENT COMPLETE message with the LCLS-BSS-Status IE indicating "Call Not Possible to be Locally Switched". + +21 - 30. The basic call establishment procedure between the UE-1 and the UE-2 continues as for the normal, non-LCLS call. + +### 6.3.4 LCLS established, Basic Call Example with SIP-I based CS core network + +Figures 6.3.4.1, 6.3.4.2, 6.3.4.3 and 6.3.4.4 show the message sequence example for the basic call establishment when call is locally switched. In this example the oUE and the tUE belong to the same BSS (marked as oBSS and tBSS) and the CN permits LCLS. The example is based on examples for the basic mobile originating call and for the basic mobile terminating call from 3GPP TS 23.231 [3]. + +![Sequence diagram showing the Basic Call Establishment Flow when call is locally switched. The diagram involves ten lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. The process starts with the oUE sending a Service Request + CL3 to the oMSC. The oMSC responds with SETUP, then CALL PROCEEDING. A red box indicates step 4: 'Retrieve oBSS ID and use it to generate Global Call Reference'. The oMSC then sends an ADD request ($) to the oMGW, which replies with ADD reply (T2) and Context (oC). The oMSC sends an INVITE [SDP, IAM (GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference)] to the iMSC, which replies with 100 Trying. The oMSC then sends another ADD request ($) to the iMGW, which replies with ADD reply (T6) and Context (iC). The iMSC sends an INVITE [SDP, IAM (GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference)] to the tMSC, which replies with 100 Trying. The tMSC sends a Paging tUE to the tBSS, which replies with a Paging response + CL3. The tMSC then sends SETUP, CALL CONFIRMED, and an ADD request ($) to the tMGW, which replies with ADD reply (T3) and Context (tC). The tMSC sends a 183 Session Progress [SDP, APM (LCLS-Negotiation Response, LCLS-Configuration-Preference)] to the iMSC, which replies with PRACK. The oMSC sends a MOD request (T6) to the iMGW, which replies with MOD reply (T6) and Context (iC). Finally, the iMSC sends a 200 OK PRACK to the tMSC.](5d782eeb9d1e5871d7f09e0ccdd4cdf1_img.jpg) + +Sequence diagram showing the Basic Call Establishment Flow when call is locally switched. The diagram involves ten lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. The process starts with the oUE sending a Service Request + CL3 to the oMSC. The oMSC responds with SETUP, then CALL PROCEEDING. A red box indicates step 4: 'Retrieve oBSS ID and use it to generate Global Call Reference'. The oMSC then sends an ADD request (\$) to the oMGW, which replies with ADD reply (T2) and Context (oC). The oMSC sends an INVITE [SDP, IAM (GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference)] to the iMSC, which replies with 100 Trying. The oMSC then sends another ADD request (\$) to the iMGW, which replies with ADD reply (T6) and Context (iC). The iMSC sends an INVITE [SDP, IAM (GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference)] to the tMSC, which replies with 100 Trying. The tMSC sends a Paging tUE to the tBSS, which replies with a Paging response + CL3. The tMSC then sends SETUP, CALL CONFIRMED, and an ADD request (\$) to the tMGW, which replies with ADD reply (T3) and Context (tC). The tMSC sends a 183 Session Progress [SDP, APM (LCLS-Negotiation Response, LCLS-Configuration-Preference)] to the iMSC, which replies with PRACK. The oMSC sends a MOD request (T6) to the iMGW, which replies with MOD reply (T6) and Context (iC). Finally, the iMSC sends a 200 OK PRACK to the tMSC. + +Figure 6.3.4.1: Basic Call Establishment Flow when call is locally switched + +1. Service Request handling. +2. Originating Call SETUP. +3. The oMSC server replies with a CALL PROCEEDING message to indicate that the call is being processed. +4. If the oMSC server supports LCLS it retrieves the oBSS ID and generates the Global Call Reference for the call. +5. The oMSC server selects the codec and requests the oMGW to select and provide the IP transport address and port for the network side bearer connection before sending the INVITE message. + +6. The oMSC server sends the INVITE request with the initial SDP offer indicating that local preconditions have not been met, and with the encapsulated IAM message containing the GCR with encapsulated oBSS ID, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. +7. The iMSC server confirms the reception of the INVITE request with a 100 Trying provisional response. +8. The iMSC server selects the codec and requests the iMGW to select and provide the IP transport address and port for the outgoing network side bearer termination. +9. If the iMSC server supports LCLS it may modify the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE due to CAMEL, supplementary service requirements etc. before sending the INVITE request with the SDP offer and with the encapsulated IAM message containing the GCR with the encapsulated oBSS ID, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. +10. The tMSC server confirms the reception of the INVITE request with 100 a Trying provisional response. +11. The tMSC server pages the tUE. +12. The tMSC server performs call Setup. +13. The tUE confirms the call. +14. The tMSC server selects the codec, provides to the tMGW the selected codec and the remote user plane IP address and port information that were received from the preceding node in the SDP offer and requests the tMGW to prepare for the network side bearer establishment. +15. After the tMGW has replied with the local IP address and port information the tMSC server includes in the SDP answer the user plane IP address and UDP port received from the tMGW, the selected codec and any additional accepted payload types. The tMSC server returns a 183 Session Progress provisional response with the SDP answer and if LCLS is supported with encapsulated APM message containing the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. +16. The iMSC server replies to succeeding node with the PRACK request to confirm the reception of the 183 Session Progress provisional response. +17. When the 183 Session Progress provisional response with the SDP answer is received the iMSC server requests the iMGW to configure the remote IP transport address and any additional negotiated payload types of the outgoing side bearer termination. +18. The tMSC server confirms the reception of the PRACK request with a 200 OK final response. + +![Sequence diagram for Basic Call Establishment when call is locally switched. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. The diagram shows steps 19 through 33, including ADD request/reply, 183 Session Progress, PRACK, ASSIGNMENT REQUEST/COMPLETE, and UPDATE [SDP] messages. Contexts (iC, oC, tC) are indicated. Red text highlights LCLS-Negotiation Response, LCLS-Configuration-Preference, and LCLS-BSS-Status. Notes indicate that for AoTDM, step 23 is ADD (T1) and step 27 is not applicable. A dashed box for step 33 indicates optional intra-network call detection checks.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) + +``` + +sequenceDiagram + participant oUE + participant oBSS + participant oMGW + participant oMSC + participant iMGW + participant iMSC + participant tMSC + participant tMGW + participant tBSS + participant tUE + + Note left of oUE: Error! No + Note right of tUE: Error! No text of specified style in + oMSC->>iMGW: 19. Add network side termination: ADD request ($) / ADD reply (T5) + iMGW->>iMSC: Context (iC) + iMSC->>oMSC: 20. 183 Session Progress [SDP, APM (LCLS-Negotiation Response, LCLS-Configuration-Preference)] + oMSC->>iMSC: 21. PRACK + oMSC->>oMGW: 22. Configure remote IP address & port: MOD request (T2) / MOD reply (T2) + oMGW->>oMSC: Context (oC) + oMSC->>oMGW: 23. Add access side termination: ADD request ($) / ADD reply (T1) + Note right of iMSC: NOTE: For AoTDM step 23 is: ADD (T1). + oMGW->>oMSC: Context (oC) + oMSC->>iMSC: 24. 200 OK PRACK + oMSC->>oBSS: 25. ASSIGNMENT REQUEST (GCR, LCLS-Configuration) + oBSS->>oMSC: + oMSC->>oBSS: 26. ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not possible to be locally switched") + oMSC->>oMGW: 27. Configure remote IP address & port: MOD request (T1) / MOD reply (T1) + Note right of iMSC: NOTE: Step 27 is not applicable for AoTDM. + oMGW->>oMSC: Context (oC) + oMSC->>iMSC: 28. UPDATE [SDP] + iMSC->>tMSC: 29. UPDATE [SDP] + tMSC->>iMSC: 30. 200 OK UPDATE [SDP] + tMSC->>tMGW: 31. Add access side termination: ADD request ($) / ADD reply (T4) + Note right of tBSS: NOTE: For AoTDM step 31 is: ADD (T4). + tMGW->>tMSC: Context (tC) + tMSC->>oMSC: 32. 200 OK UPDATE [SDP] + Note right of tMSC: 33. If optional Intra-Network call detection and/or optional Intra-BSS call detection procedure/s supported perform check. + +``` + +Sequence diagram for Basic Call Establishment when call is locally switched. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. The diagram shows steps 19 through 33, including ADD request/reply, 183 Session Progress, PRACK, ASSIGNMENT REQUEST/COMPLETE, and UPDATE [SDP] messages. Contexts (iC, oC, tC) are indicated. Red text highlights LCLS-Negotiation Response, LCLS-Configuration-Preference, and LCLS-BSS-Status. Notes indicate that for AoTDM, step 23 is ADD (T1) and step 27 is not applicable. A dashed box for step 33 indicates optional intra-network call detection checks. + +Figure 6.3.4.2: Basic Call Establishment when call is locally switched (continuation of figure 6.3.4.1) + +19. The iMSC server selects the codec for the incoming side bearer termination, provides to the iMGW the selected codec and the remote user plane IP address and port information that were received from the preceding node in the SDP offer and requests the iMGW to prepare for the incoming side bearer establishment. +During the seizure of the outgoing side and the incoming side bearer termination the iMSC server will also request the iMGW to through-connect the bearer terminations so that the bearer will be bothway through-connected. +20. After the iMGW has replied with the local IP address and port information the iMSC server includes in the SDP answer the user plane IP address and UDP port received from the iMGW, the selected codec and any additional accepted payload types. The iMSC server sends the 183 Session Progress provisional response with the SDP answer and with encapsulated APM message containing the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE to the preceding node. +21. The oMSC server replies to the succeeding node with the PRACK request to confirm the reception of the 183 Session Progress provisional response. +22. The oMSC server requests the oMGW to configure the remote user plane IP address and any additional negotiated payload types of the network side bearer termination. +23. The oMSC server requests the seizure of the access side bearer termination. +During the seizure of the network side or the access side bearer termination the oMSC server will also + +request the oMGW to through-connect the bearer terminations so that the bearer will be backward through-connected. + +24. The iMSC server confirms the reception of the PRACK request with the 200 OK final response. +25. The oMSC server determines whether LCLS is allowed in the core network based on the returned LCLS-Negotiation IE and if so the oMSC server includes the LCLS-Configuration IE in the ASSIGNMENT REQUEST message along with the GCR IE. +26. The oBSS returns the ASSIGNMENT COMPLETE message with the LCLS-BSS-Status IE indicating "call not possible to be locally switched". +27. When the oMSC server receives the ASSIGNMENT COMPLETE message, it requests the oMGW to configure the remote user plane IP address and UDP Port for the access side bearer termination. +28. Since the access bearer assignment is completed the oMSC server sends the UPDATE request with the SDP offer indicating local preconditions met to the succeeding node. +29. The iMSC server forwards the UPDATE request to the succeeding node. +30. The tMSC server confirms the reception of the UPDATE request with the 200 OK final response. +31. When the tMSC server receives the SDP offer indicating remote preconditions met it requests the seizure of the access side bearer termination. +If not requested during the seizure of network side bearer termination (step 14) the tMSC server will request the tMGW to through-connect the bearer terminations so that the bearer will be backward through-connected. +32. The iMSC server forwards the 200 OK (UPDATE) final response to the preceding node. +33. If the tMSC server supports the optional "intra-Network call detection" procedure it compares its own Network ID with the Network ID received within the Global Call Reference IE. +If the tMSC server supports the optional "intra-BSS call detection" procedure it compares the BSS ID of the selected terminating BSS with the oBSS ID received within the Global Call Reference IE at this step. Since the oUE and the tUE belong to the same BSS the call continues the same way as for the basic LCLS establishment without this pre-check. + +![Sequence diagram for Basic Call Establishment when call is locally switched (continuation of figure 6.3.4.2).](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) + +The sequence diagram illustrates the interaction between ten network entities: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. The process begins with the tMSC sending an **34. ASSIGNMENT REQUEST (GCR, LCLS-Configuration)** to the tBSS. The tBSS responds with **35a. ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not yet locally switched")**. The tUE then sends an **36. ALERTING** message. The tMSC sends a **37. MOD request: send Ring-back tone** to the tMGW, which is acknowledged by a **Context (tC)** message. The tMSC then sends a **38. 180 Ringing [ACM]** to the iMSC. The iMSC replies with **39. PRACK**. The tMGW sends a **40. 180 Ringing [ACM]** to the oMSC. The oMSC replies with **41. PRACK**. The iMSC sends a **42. 200 OK PRACK** to the tMSC. The tMSC sends an **43. ALERTING** message to the oUE. The oMSC sends a **44. 200 OK PRACK** to the iMGW. A **Ring-back Tone** is indicated by a blue arrow from the oMSC to the oUE. The tMSC sends a **45. CONNECT** message to the tMGW. The tMGW responds with **46. CONNECT ACK**. The tMSC then sends **47. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "connect")** to the tBSS. The tBSS responds with **48. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call not yet locally switched")**. The tMSC sends a **49. MOD request: stop tone, bothway through-connect** to the tMGW, which is acknowledged by a **Context (tC)** message. The tMSC sends a **50. 200 OK INVITE [ANM (LCLS status = "LCLS feasible but not yet connected")]** to the iMSC. The iMSC sends a **51. 200 OK INVITE [ANM (LCLS status = "LCLS feasible but not yet connected")]** to the oMSC. + +Sequence diagram for Basic Call Establishment when call is locally switched (continuation of figure 6.3.4.2). + +**Figure 6.3.4.3: Basic Call Establishment when call is locally switched (continuation of figure 6.3.4.2)** + +34. The tMSC server sends the ASSIGNMENT REQUEST message containing the GCR IE and the LCLS-Configuration IE if LCLS is permitted in the core network. +35. a) The tBSS performs the GCR correlation. Since the GCR correlation has identified the call as an intra BSS call and LCLS is allowed in the BSS, the tBSS returns the ASSIGNMENT COMPLETE message with the LCLS-BSS-Status IE indicating "Call not yet locally switched". + b) Since the GCR correlation has identified the call as an intra BSS call and LCLS is allowed in the BSS, the oBSS signals the LCLS status change to the oMSC server by sending the LCLS\_NOTIFICATION message with the LCLS-BSS-Status IE set to "Call not yet locally switched". +36. The tUE reports alerting. +37. The tMSC server requests the tMGW to provide a ring-back tone. +38. The tMSC server sends a 180 Ringing provisional response with the encapsulated ACM message to the preceding node. +39. The iMSC server replies to succeeding node with the PRACK request to confirm the reception of the 180 Ringing provisional response. +40. The iMSC server transfers the 180 Ringing provisional response with the encapsulated ACM message to the preceding node. + +41. The oMSC server replies to succeeding node with the PRACK request to confirm the reception of the 180 Ringing provisional response. +42. The tMSC server confirms the reception of the PRACK request with the 200 OK final response. +43. The oMSC server reports alerting. +44. The IMSC server confirms the reception of the PRACK request with the 200 OK final response. +45. The tUE answers the call. +46. The tMSC server returns the CONNECT ACKNOWLEDGE message to the tUE. +47. The tMSC server indicates to the tBSS that this call leg is ready to be locally switched by sending the LCLS\_CONNECT\_CONTROL message. +48. The tBSS returns the LCLS\_CONNECT\_CONTROL\_ACK message with the LCLS-BSS-Status IE set to "Call not yet locally switched" since the BSS has not received the same order from the oMSC server. +49. When the tMSC server receives the Connect message it requests the tMGW to stop providing ring-back tone to the calling party and requests to bothway through-connect the bearer. +50. The tMSC server returns the 200 OK (INVITE) final response with the encapsulated ANM message with the LCLS-Status IE indicating "LCLS is feasible but not yet connected". +51. The oMSC server receives the 200 OK (INVITE) final response with the encapsulated ANM message with the LCLS-Status IE indicating "LCLS is feasible but not yet connected". + +![Sequence diagram for Basic Call Establishment when call is locally switched (continuation of figure 6.3.4.3).](ddee3e67e0dfc22e25188fa635a19558_img.jpg) + +The sequence diagram illustrates the interaction between the following entities: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. The sequence of messages is as follows: + +- 52. ACK:** oMSC sends an ACK message to iMSC. +- 53. MOD request: bothway through-connect:** oMSC sends a MOD request to oMGW. +- Context (oC):** oMGW responds with context information to oMSC. +- 54. ACK:** iMSC sends an ACK message to tMSC. +- 55. CONNECT:** oMSC sends a CONNECT message to oBSS. +- 56. CONNECT ACK:** oBSS sends a CONNECT ACK message to oMSC. +- 57. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "connect"):** oMSC sends this message to oBSS. +- 58a. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration"):** oBSS responds to oMSC. +- 58b. LCLS\_NOTIFICATION (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration"):** tMSC sends this message to tBSS. +- 58c. MOV request (T1) / MOV reply:** oMSC and oMGW exchange MOV messages. A dashed box indicates that if oMSC supports isolating access side termination, the context (Cs) for isolate bearer termination is included. +- 58d. MOV request (T4) / MOV reply:** tMSC and tMGW exchange MOV messages. A dashed box indicates that if tMSC supports isolating access side termination, the context (Cs) for isolate bearer termination is included. +- 59. LCLS status update: INFO [APM (LCLS-Status = "LCLS connected")]:** oMSC sends this update to iMSC. +- 60. 200 OK INFO:** iMSC responds to oMSC. +- 61. LCLS status update: INFO [APM (LCLS-Status = "LCLS connected")]:** iMSC sends this update to tMSC. +- 62. 200 OK INFO:** tMSC responds to iMSC. + +A large red double-headed arrow at the bottom, spanning from oBSS to tBSS, is labeled **Call is locally Switched**. + +Sequence diagram for Basic Call Establishment when call is locally switched (continuation of figure 6.3.4.3). + +Figure 6.3.4.4: Basic Call Establishment when call is locally switched (continuation of figure 6.3.4.3) + +52. The oMSC server replies to the succeeding node with the ACK request to confirm the reception of the 200 OK final response. + +53. The oMSC server request the oMGW to bothway through-connect the bearer. + 54. The iMSC server transfers the ACK request to the succeeding node. + 55. The oMSC server reports Answer/Connect to the oUE. + 56. The oUE returns the CONNECT ACKNOWLEDGE message to the oMSC server. + 57. The oMSC server requests the oBSS to connect LCLS since the received 200 OK (INVITE) final response indicated "LCLS is feasible but not yet connected". + 58. + - a) Since the BSS has received the through connect request for both call legs the oBSS returns the LCLS\_CONNECT\_CONTROL\_ACK message with the LCLS-BSS-Status IE set to "call is locally switched with requested LCLS configuration". + - b) The tBSS signals the LCLS status change to the tMSC server by sending the LCLS\_NOTIFICATION message with the LCLS-BSS-Status IE set to "call is locally switched with requested LCLS configuration". + - c) If the oMSC server supports the option to configure its Access MGW to isolate the access side termination from the network side termination and LCLS negotiation indicated that no succeeding node requires the UL data from the oUE then the oMSC server requests the oMGW to isolate the access side termination T1 from the network side termination T2. + - d) If the tMSC server supports the option to configure its Access MGW to isolate the access side termination from the network side termination and LCLS negotiation indicated that no preceding node requires the UL data from the tUE then the tMSC server requests the tMGW to isolate the access side termination T4 from the network side termination T3. +- NOTE: The MSC server can also use the Change Through-Connection procedure and requests the MGW to change the through-connection of the bearer to inactive instead of using of the Isolate Bearer termination procedure, see 3GPP TS 23.205 [2]. +59. The oMSC server signals the change of the LCLS status through the Core Network by sending the INFO request with the encapsulated APM message with the LCLS-Status IE set to "LCLS connected". + 60. The iMSC server returns the 200 OK (INFO) final response to the preceding node. + 61. The iMSC server transfers the change of the LCLS status to the succeeding node. + 62. The tMSC server returns the 200 OK (INFO) final response to the preceding node. + +### 6.3.5 LCLS established, Basic Call Example with BICC based CS core network, backward bearer establishment + +Figures 6.3.5.1 and 6.3.5.2 show the message sequence example for the basic call establishment for LCLS. In this example the oUE and the tUE belong to the same BSS (marked as oBSS and tBSS) and the CN permits LCLS. The example is based on examples from 3GPP TS 23.205 [2] for the basic mobile originating call, backward bearer establishment (case when access bearer assignment is completed before sending of initial address message) and the basic mobile terminating call, backward bearer establishment. + +![Sequence diagram showing Basic Call Establishment Flow when call is locally switched, backward bearer establishment. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. The diagram illustrates the interaction between these entities for call setup, including Service Request, SETUP, CALL PROCEEDING, and various bearer establishment steps (ADD request/reply, ASSIGNMENT REQUEST/COMPLETE, IAM).](8e80de0cac529b2c3775d677c5203133_img.jpg) + +``` + +sequenceDiagram + participant oUE + participant oBSS + participant oMGW + participant oMSC + participant iMGW + participant iMSC + participant tMSC + participant tMGW + participant tBSS + participant tUE + + Note left of oMSC: 4. Retrieve oBSS ID and use it to generate Global Call Reference + + oUE->>oMSC: 1. oUE accesses oMSC: Service Request + CL3 + oMSC-->>oBSS: + oBSS-->>oUE: + oMSC->>oMSC: 2. SETUP + oMSC-->>oBSS: 3. CALL PROCEEDING + oBSS-->>oUE: + Note right of oMSC: 4. Retrieve oBSS ID and use it to generate Global Call Reference + oMSC->>oBSS: 5. Add access side termination: ADD request ($) / ADD reply (T1) Context (oC) + oBSS-->>oMSC: + oMSC->>oBSS: 6. ASSIGNMENT REQUEST (GCR, LCLS-Configuration) + oBSS-->>oUE: 7. ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not possible to be locally switched") + Note right of oBSS: Access side Bearer Establishment + oMSC->>oBSS: 8. Add network side termination: ADD request ($) / ADD reply (T2) Context (oC) + Note right of iMGW: NOTE: Prepare bearer T2 + oMSC->>iMSC: 9. IAM [Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference] + oMSC->>oBSS: 10. Add network side termination: ADD request ($) / ADD reply (T5) Context (iC) + Note right of oMGW: Network side Bearer Establishment + oMSC->>oBSS: 11. Add network side termination: ADD request ($) / ADD reply (T6) Context (iC) + Note right of tMGW: NOTE: Prepare bearer T6 + oMSC->>tMSC: 12. IAM [Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference] + +``` + +Sequence diagram showing Basic Call Establishment Flow when call is locally switched, backward bearer establishment. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. The diagram illustrates the interaction between these entities for call setup, including Service Request, SETUP, CALL PROCEEDING, and various bearer establishment steps (ADD request/reply, ASSIGNMENT REQUEST/COMPLETE, IAM). + +**Figure 6.3.5.1: Basic Call Establishment Flow when call is locally switched, backward bearer establishment** + +- Service Request handling. +- Originating Call SETUP. +- The oMSC server replies with the CALL PROCEEDING message to indicate that the call is being processed. +- If the oMSC server supports LCLS it retrieves the oBSS ID and generates the Global Call Reference for the call. +- Before the network side bearer information is seized the oMSC server requests the seizure of the access side bearer termination. +- The oMSC server includes a preliminary LCLS-Configuration IE in the ASSIGNMENT REQUEST message along with the GCR IE, because the oMSC server does not know whether LCLS is allowed in the core network at this stage. +- The oBSS returns the ASSIGNMENT COMPLETE message with the LCLS-BSS-Status IE indicating "call not possible to be locally switched". +- The oMSC server prepares the seizure of the network side bearer termination. + +9. Afer the oMGW has replied with the bearer address and the binding reference, the oMSC server sends the IAM to the succeeding node, in which the oMSC server indicates that backward bearer establishment is to be used. The oMSC server sends the IAM message including supported codecs list, GCR with encapsulated oBSS ID, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. +10. When the initial address and the bearer information is received the iMSC server requests the seizure of the network side bearer termination. +11. The iMSC server prepares the seizure of the outgoing side bearer termination. +12. After the iMGW has replied with the bearer address and the binding reference, the iMSC server sends the IAM to the succeeding node. If the iMSC server supports LCLS it may modify the LCLS-Negotiation IE due to CAMEL, supplementary service requirements etc. before sending the IAM message containing the GCR with the encapsulated oBSS ID, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. + +![Sequence diagram for Basic Call Establishment when call is locally switched, backward bearer establishment. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. The diagram shows signaling steps 13 through 27, including paging, setup, call confirmation, bearer establishment, and alerting.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) + +``` + +sequenceDiagram + participant oUE + participant oBSS + participant oMGW + participant oMSC + participant iMGW + participant iMSC + participant tMSC + participant tMGW + participant tBSS + participant tUE + + Note over tMSC, tUE: 13. Paging tUE + tMSC->>tBSS: + tBSS->>tUE: + tUE-->>tBSS: + tBSS-->>tMSC: Paging response + CL3 + + Note over tMSC, tUE: 14. SETUP + tMSC->>tBSS: + tBSS->>tUE: + + Note over tMSC, tUE: 15. Call Confirmed + tUE-->>tBSS: + tBSS-->>tMSC: + + Note over tMSC, tMGW: 16. Add access side termination: Context (tC) + tMSC->>tMGW: ADD request ($) + tMGW-->>tMSC: ADD reply (T3) + + Note over iMGW, tMGW: Network side Bearer Establishment + + Note over tMSC, tMGW: 17. Add access side termination: Context (tC) + tMSC->>tMGW: ADD request ($) + tMGW-->>tMSC: ADD reply (T4) + + Note over iMSC, tMSC: 18. If optional Intra-Network call detection and/or optional Intra-BSS call detection procedure/s supported perform check. + + Note over tMSC, tBSS: 19. ASSIGNMENT REQUEST (GCR, LCLS-Configuration) + tMSC->>tBSS: + + Note over tMSC, tBSS: 20. ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not yet locally switched") + tBSS-->>tMSC: + + Note over oBSS, oMSC: 21. LCLS_NOTIFICATION (LCLS-BSS-Status = "call not yet locally switched") + oBSS->>oMSC: + + Note over tBSS, tUE: Access Side Bearer Establishment + + Note over tMSC, tUE: 22. tUE reports: Alerting + tUE-->>tBSS: + tBSS-->>tMSC: + + Note over iMSC, tMSC: 23. ACM [LCLS-Negotiation Response, LCLS-Configuration-Preference] + tMSC->>iMSC: + + Note over tMSC, tMGW: 24. MOD request: send Ring-back tone + tMSC->>tMGW: + Note over tMSC, tMGW: Context (tC) + + Note over oMSC, iMSC: 25. ACM [LCLS-Negotiation Response, LCLS-Configuration-Preference] + iMSC->>oMSC: + + Note over oUE, oMSC: 26. oMSC reports: Alerting + oMSC->>oBSS: + oBSS->>oUE: + + Note over oUE, tMGW: Ring-back Tone + tMGW-->>oUE: + + Note over oBSS, tBSS: 27. For succeeding signalling sequence see figure 6.3.2.3. + +``` + +Sequence diagram for Basic Call Establishment when call is locally switched, backward bearer establishment. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. The diagram shows signaling steps 13 through 27, including paging, setup, call confirmation, bearer establishment, and alerting. + +**Figure 6.3.5.2: Basic Call Establishment when call is locally switched, backward bearer establishment (continuation of figure 6.3.5.1)** + +13. The tMSC server pages the tUE. +14. The tMSC server performs call Setup. +15. The tUE confirms the call. + +16. The tMSC server requests the tMGW to establish a bearer to the given iMGW. +17. The tMSC server requests the seizure of the access side bearer termination. +18. If the tMSC server supports the optional "intra-Network call detection" procedure it compares its own Network ID with the Network ID received within the Global Call Reference IE. +If the tMSC server supports the optional "intra-BSS call detection" procedure it compares the BSS ID of the selected terminating BSS with the oBSS ID received within the Global Call Reference IE at this step. Since the oUE and the tUE belong to the same BSS the call continues the same way as for the basic LCLS establishment without this pre-check. +19. The tMSC server performs the access bearer assignment and sends the ASSIGNMENT REQUEST message containing the GCR IE and the LCLS-Configuration IE if LCLS is permitted in the core network. +20. The oBSS/tBSS performs the GCR correlation. Since the GCR correlation has identified the call as an intra BSS call and LCLS is allowed in the BSS, the tBSS returns the ASSIGNMENT COMPLETE message with the LCLS-BSS-Status IE indicating "Call not yet locally switched". +21. Since the GCR correlation has identified the call as an intra BSS call and LCLS is allowed in the BSS, the oBSS signals the LCLS status change by sending the LCLS\_NOTIFICATION message with the LCLS-BSS-Status IE set to "Call not yet locally switched". +22. The tUE reports alerting. +23. The tMSC server returns the ACM message and includes the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE if LCLS is supported. +24. The tMSC requests the tMGW to provide a ring-back tone. +25. The iMSC server returns the ACM message and includes the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. +26. The oMSC server reports alerting. +27. When performing further call establishment see figure 6.3.2.3. + +--- + +## 7 Call Clearing and LCLS Break/Re-establishment + +### 7.1 Call Clearing + +The call clearing procedures shall be performed in accordance with 3GPP 23.205 [2] for a BICC based CS core network and in accordance with 3GPP TS 23.231 [3] for a SIP-I based CS core network. + +### 7.2 LCLS Break + +#### 7.2.1 MSC server Initiated + +##### 7.2.1.1 Principles + +When the MSC server determines that local switching should be disconnected: + +- it shall send a LCLS Status Change Request message indicating disconnection preparation through the Core Network. +- on receipt of a LCLS Status Change Request Acknowledge message indicating disconnection preparation with a Result code indicating LCLS Status Change Request accepted the MSC server shall send a LCLS-Connection-Control message indicating LCLS break to the associated BSS. + +On receipt of the LCLS Status Change Request message indicating disconnection preparation the MSC server shall: + +- send a LCLS break request immediately to the associated BSS, and + +- when the acknowledge message is received from the BSS, the MSC server shall return the LCLS Status Change Request Acknowledge message indicating disconnection preparation and a Result code indicating LCLS Status Change Request accepted. + +The BSS needs to receive the LCLS break request on both call legs before releasing local switching. + +### 7.2.1.2 MSC server actions + +When the MSC server determines that local switching should be disconnected it shall send to the succeeding (or preceding) node the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation". If in the related MGW the access side termination is isolated from the network side termination, the MSC Server shall request the MGW to through-connect the access side termination to the network side termination. + +On the reception of the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and a Result code IE indicating LCLS Status Change Request accepted, the MSC server shall send to the BSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS". At reception of the LCLS-Connect-Control Acknowledge message with the LCLS-BSS-Status IE set to "the call is no longer locally switched", the MSC server shall send to the succeeding (or preceding) node the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" if the same LCLS Status Update message was not already received from the succeeding (or preceding) node. + +When the MSC server receives the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" it shall send to the BSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS". If in the related MGW the access side termination is isolated from the network side termination, the MSC Server shall request the MGW to through-connect the access side termination to the network side termination. On reception of the LCLS-Connect-Control Acknowledge message the MSC server shall send to the preceding (or succeeding) node the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and a Result code IE indicating LCLS Status Change Request accepted. + +When the LCLS-Connect-Control Acknowledge or the LCLS-Notification message with the LCLS-BSS-Status IE set to "the call is no longer locally switched" is received, the MSC server shall send to the succeeding (or preceding) node the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" if the same LCLS Status Update message was not already received from the succeeding (or preceding) node. + +### 7.2.1.3 GMSC server actions + +On receipt of the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" from the preceding (or succeeding) node, the GMSC Server shall forward message to the succeeding (or preceding) node. + +The GMSC Server shall forward the received LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and the Result code IE indicating LCLS Status Change Request accepted. + +On receipt of the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" from the preceding (or succeeding) node: + +- the GMSC Server shall forward the message to the succeeding (or preceding) node if the same request was not already received from the succeeding (or preceding) node. +- the GMSC Server shall not forward the message if the same request was already received from the succeeding (or preceding) node. + +### 7.2.1.4 BSS actions + +On receipt of the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS" the following applies: + +- if the request was received for only one call leg associated to the LCLS call, the BSS shall not break the local switching. The BSS shall only send the LCLS-Connect-Control Acknowledge message to the MSC server with LCLS-BSS-Status indicating LCLS is still established. + +- if the request was received for both call legs associated to the LCLS call, the BSS shall break local switching and shall report the LCLS disconnection on both call legs by sending: +- the LCLS-Connect-Control Acknowledge message to the MSC server and +- the LCLS-Notification message to the far end MSC server which previously requested LCLS release for the associated leg. + +## 7.2.2 BSS Initiated + +### 7.2.2.1 Principles + +When the BSS determines that local switching should be disconnected it may: + +- immediately break local switching and then inform the Core Network, or +- first request the Core Network to prepare for LCLS break and on the reception of LCLS break request on both call legs the BSS breaks local switching. + +### 7.2.2.2 Immediate LCLS break + +#### 7.2.2.2.1 BSS actions + +When the BSS determines that local switching should be disconnected it shall immediately break local switching. The BSS shall report the LCLS disconnection by sending the LCLS-Notification message with the LCLS-BSS-Status IE set to "the call is no longer locally switched" to both MSC servers associated to the LCLS call. + +#### 7.2.2.2.2 MSC server actions + +At reception of the LCLS-Notification message with the LCLS-BSS-Status IE set to "the call is no longer locally switched", the MSC server shall send to the succeeding (or preceding) node the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" if the same LCLS Status Update message was not already received from the succeeding (or preceding) node. If in the related MGW the access side termination is isolated from the network side termination, the MSC Server shall request the MGW to through-connect the access side termination to the network side termination. + +#### 7.2.2.2.3 GMSC server actions + +On receipt of the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" from the preceding (or succeeding) node: + +- the GMSC Server shall forward the message to the succeeding (or preceding) node if the same request was not already received from the succeeding (or preceding) node. +- the GMSC Server shall not forward the message if the same request was already received from the succeeding (or preceding) node. + +### 7.2.2.3 BSS Requesting LCLS Release from Core Network + +#### 7.2.2.3.1 BSS actions + +When the BSS determines that local switching should be disconnected but the LCLS release should be ordered from the Core Network the BSS shall request the LCLS disconnection by sending the LCLS-Notification message with a LCLS-Break-Request IE to both MSC servers associated to the LCLS call. + +On receipt of the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS" the BSS shall apply the procedure described in sub-clause 7.2.1.4. + +#### 7.2.2.3.2 MSC server actions + +At reception of the LCLS-Notification message with LCLS-Break-Request IE the MSC server shall send to the succeeding (or preceding) node the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation". If in the related MGW the access side termination is isolated from the network side termination, the MSC Server shall request the MGW to through-connect the access side termination to the network side termination. + +On the reception of the LCLS Status Change Request message with the LCLS-Status-Change IE indicating LCLS disconnection preparation, the MSC server shall apply the procedure described in sub-clause 7.2.1.2 with the following exception: + +- on the reception of the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and a Result code IE indicating LCLS Status Change Request accepted the MSC server shall not request the LCLS break if it already requested due to the reception of the LCLS Status Change Request message from the succeeding (or preceding) node. + +### 7.2.2.3.3 GMSC server actions + +The GMSC server shall perform the same actions as described in sub-clause 7.2.1.3. + +## 7.2.3 Intermediate Node/GMSC Server Initiated + +### 7.2.3.1 Principles + +When an intermediate node or a GMSC server determines that local switching should be disconnected it shall send the LCLS Status Change Request message indicating disconnection preparation to the preceding and to the succeeding node. + +On receipt of LCLS Status Change Request message indicating disconnection preparation the originating or terminating MSC server shall send LCLS break request immediately to the associated BSS. When the acknowledge message is received from the BSS, the MSC server shall return LCLS Status Change Request Acknowledge message indicating disconnection preparation and a Result code indicating LCLS Status Change Request was accepted. + +The BSS needs to receive the LCLS break request on both call legs before releasing local switching. + +### 7.2.3.2 Intermediate Node/GMSC server actions + +When an intermediate node or a GMSC server determines that local switching should be disconnected it shall send the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" to the preceding and to the succeeding node. + +The intermediate node or the GMSC Server not initiating the LCLS break shall forward the received LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation". + +On receipt of the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and a Result code IE indicating LCLS Status Change Request was accepted from the preceding (or succeeding) node, the intermediate node or the GMSC Server not initiating the LCLS break shall forward message to the succeeding (or preceding) node. + +On receipt of the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" from the preceding (or succeeding) node: + +- the intermediate node or the GMSC Server not initiating the LCLS break shall forward the message to the succeeding (or preceding) node. +- the intermediate node or the GMSC Server initiating the LCLS break shall not forward the message. + +### 7.2.3.3 MSC server actions + +When the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" is received from the succeeding (or preceding) node, the MSC Server shall send to the BSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS". If in the related MGW the access side termination is isolated from the network side termination, the MSC Server shall request the MGW to through-connect the access side termination to the network side termination. + +If the LCLS-Connect-Control Acknowledge message with the LCLS-BSS-Status IE set to "call is locally switched with requested LCLS configuration" is received, the MSC server shall send to the preceding (or succeeding) node the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and a Result code IE indicating LCLS Status Change Request accepted. + +At reception of the LCLS-Notification message with the LCLS-BSS-Status IE set to "the call is no longer locally switched", the MSC server shall send to the succeeding (or preceding) node the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected". + +At reception of the LCLS-Connect-Control Acknowledge message with the LCLS-BSS-Status IE set to "the call is no longer locally switched", after sending the LCLS Status Change Request Acknowledge message, the MSC server shall send to the succeeding (or preceding) node the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected". + +### 7.2.3.4 BSS actions + +The BSS shall perform the same actions as described in sub-clause 7.2.1.4. + +## 7.2.4 LCLS Break Example Call Flows + +### 7.2.4.1 LCLS Break Connection Model for LCLS + +Figure 7.2.4.1.1 shows the network model for a LCLS break of the mobile call. The "squared" line represents the call control signalling. The "dotted/full" line represents the bearer terminations in the MGW. Bearer termination T1 and T6 are used for the bearer towards BSC and bearer termination T2, T3, T4 and T5 are used for the bearer towards preceding/succeeding MGW. + +![Diagram showing two connection models for LCLS break. Model 1 (Before LCLS Break) shows control signalling (green dashed) and user plane data (red solid) paths through oMSC-S, iMSC-S, tMSC-S, oBSS/tBSS, oMGW, iMGW, and tMGW. Model 2 (After LCLS Break) shows the user plane data path being rerouted.](6584b95e34ea1f0b67144aa841db0863_img.jpg) + +The diagram illustrates the network model for an LCLS break, divided into two parts: Connection Model 1 (Before LCLS Break) and Connection Model 2 (After LCLS Break). + +**Legend:** + +- - - - Control plane link which transmits signalling +- . . . - User plane link path through CN +- - - - User plane link which transmits real user plane data + +**Connection Model 1: Before LCLS Break** + +In this model, the control signalling (green dashed line) flows from the UE through oBSS/tBSS, oMSC-S, iMSC-S, and tMSC-S. The user plane data (red solid line) flows from the UE through oBSS/tBSS, oMGW, iMGW, and tMGW. The oMGW, iMGW, and tMGW are connected to the MSC servers via their respective bearers (T1, T2, T3, T4, T5, T6). The oMGW is connected to the oMSC-S, the iMGW to the iMSC-S, and the tMGW to the tMSC-S. The oBSS/tBSS is connected to the oMSC-S. The oUE and tUE are connected to the oBSS/tBSS. + +**Connection Model 2: After LCLS Break** + +In this model, the control signalling remains the same as in Model 1. However, the user plane data path has changed. The red solid line representing the user plane data now flows from the UE through oBSS/tBSS, then directly to the tMGW, bypassing the oMGW and iMGW. This indicates that the call is no longer locally switched and the user plane data is being routed directly to the next MGW in the chain. + +Diagram showing two connection models for LCLS break. Model 1 (Before LCLS Break) shows control signalling (green dashed) and user plane data (red solid) paths through oMSC-S, iMSC-S, tMSC-S, oBSS/tBSS, oMGW, iMGW, and tMGW. Model 2 (After LCLS Break) shows the user plane data path being rerouted. + +Figure 7.2.4.1.1: LCLS Break (Network model) + +## 7.2.4.2 MSC server Initiated + +Figure 7.2.4.2.1 shows the message sequence example for the MSC server initiated LCLS Break. + +![Sequence diagram for MSC server initiated LCLS break. Lifelines: oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, tUE. The diagram shows 12 numbered messages and a 'Call is locally Switched' indication. A note indicates that the LCLS Status Update is not sent to the preceding MSC server because the information is already received.](aeb2a26a07219661191294dba528067a_img.jpg) + +The sequence diagram illustrates the message exchange for an MSC server initiated LCLS break. The lifelines are oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, and tUE. A red double-headed arrow at the top indicates that the call is locally switched between oBSS and tBSS. The message sequence is as follows: + +- oMSC-S sends a **1. Release LCLS** message to oMGW. +- oMSC-S sends a **2. LCLS Status Change Request** [LCLS-Status-Change = "LCLS-Disconnection-Preparation"] to iMSC-S. +- iMSC-S sends a **3. LCLS Status Change Request** [LCLS-Status-Change = "LCLS-Disconnection-Preparation"] to tMSC-S. +- tMSC-S sends a **4. LCLS\_CONNECT\_CONTROL** (LCLS-Connection-Status-Control = "Release LCLS") to tBSS. +- tBSS sends a **5. LCLS\_CONNECT\_CONTROL\_ACK** (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") to tMSC-S. +- tMSC-S sends a **6. LCLS Status Change Request Acknowledge** [LCLS-Status-Change = "LCLS-Disconnection-Preparation", Result Code = "Status Change Req Accepted"] to iMSC-S. +- iMSC-S sends a **7. LCLS Status Change Request Acknowledge** [LCLS-Status-Change = "LCLS-Disconnection-Preparation", Result Code = "Status Change Req Accepted"] to oMSC-S. +- oMSC-S sends a **8. LCLS\_CONNECT\_CONTROL** (LCLS-Connection-Status-Control = "Release LCLS") to oBSS. +- oBSS sends a **9a. LCLS\_CONNECT\_CONTROL\_ACK** (LCLS-BSS-Status = "call is no longer locally switched") to oMSC-S. +- oMSC-S sends a **10. LCLS Status Update** [LCLS-Status = "LCLS not connected"] to iMSC-S. +- iMSC-S sends a **11. LCLS Status Update** [LCLS-Status = "LCLS not connected"] to tMSC-S. +- tMSC-S sends a **12. LCLS Status Update** [LCLS-Status = "LCLS not connected"] to tBSS. + +A note in the diagram states: "LCLS Status Update is not sent to the preceding MSC server since the same information is already received from the preceding MSC server." + +Sequence diagram for MSC server initiated LCLS break. Lifelines: oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, tUE. The diagram shows 12 numbered messages and a 'Call is locally Switched' indication. A note indicates that the LCLS Status Update is not sent to the preceding MSC server because the information is already received. + +**Figure 7.2.4.2.1: MSC Server initiated LCLS break** + +- The oMSC server determines that local switching should be disconnected. +- The oMSC server sends to the succeeding node the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation". +- The iMSC server transfers the LCLS Status Change Request message to the succeeding node. +- The tMSC server sends to the tBSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS". +- The tBSS confirms the reception of the LCLS release request with the LCLS-Connect-Control Acknowledge message but does not change the LCLS-BSS status since LCLS release request is not yet received for the associated call leg. +- The tMSC server sends to the preceding node the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and the Result code IE set to LCLS Status Change Request accepted. +- The iMSC server transfers the LCLS Status Change Request Acknowledge message to the preceding node. + +8. The oMSC server sends to the oBSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS". +9. The BSS reports the LCLS disconnection by sending: + - a) The LCLS-Connect-Control Acknowledge message with the LCLS-BSS-Status IE set to "the call is no longer locally switched" to the oMSC server. + - b) The LCLS-Notification message with the LCLS-BSS-Status IE set to "the call is no longer locally switched" to the tMSC server. +10. The oMSC server sends the LCLS Status Update Request message with the LCLS-Status IE set to "LCLS Not Connected" to the succeeding node. +11. The iMSC server transfers the LCLS Status Update message to the succeeding node. +12. On the receipt of the LCLS-Notification message with the LCLS-BSS-Status indicating LCLS disconnection the tMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" to the preceding node. + +NOTE: The iMSC server does not forward the LCLS Status Update message since the same LCLS Status is already received from the oMSC server. + +### 7.2.4.3 BSS Initiated, Immediate LCLS Break + +Figure 7.2.4.3.1 shows the message sequence example for the BSS initiated LCLS Break. + +![Sequence diagram for BSS initiated, immediate LCLS break. Lifelines: oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, tUE. The diagram shows the flow of LCLS messages when a BSS determines local switching should be disconnected. A red double-headed arrow at the top indicates 'Call is locally Switched'. Step 1 shows notifications from oBSS to oMSC-S and tBSS. Step 2b shows LCLS_NOTIFICATION from oBSS to oMSC-S. Step 3b shows LCLS Status Update from oMSC-S to iMSC-S. Step 3a shows LCLS Status Update from tBSS to tMSC-S. A note indicates iMSC-S does not forward the update to tMSC-S. Step 4a shows LCLS Status Update from iMSC-S to oMSC-S.](458fdbcb4015a4ee90bd84809afc4aac_img.jpg) + +``` + +sequenceDiagram + participant oUE + participant oBSS + participant oMGW + participant oMSC-S + participant iMGW + participant iMSC-S + participant tMSC-S + participant tMGW + participant tBSS + participant tUE + + Note over oUE, tUE: Call is locally Switched + Note over oBSS: 1. Locally switched +call is no longer +locally switched + Note over tBSS: 1. Locally switched +call is no longer +locally switched + oBSS->>oMSC-S: 2b. LCLS_NOTIFICATION (LCLS-BSS-Status = "call is no longer locally switched") + oBSS->>tMSC-S: 2a. LCLS_NOTIFICATION (LCLS-BSS-Status = "call is no longer locally switched") + oMSC-S->>iMSC-S: 3b. LCLS Status Update [LCLS-Status = "LCLS not connected"] + tBSS->>tMSC-S: 3a. LCLS Status Update [LCLS-Status = "LCLS not connected"] + Note over tMSC-S, tMGW: LCLS Status Update is not sent to +the succeeding MSC server since +the same info is already received +from the succeeding MSC server. + iMSC-S->>oMSC-S: 4a. LCLS Status Update [LCLS-Status = "LCLS not connected"] + +``` + +Sequence diagram for BSS initiated, immediate LCLS break. Lifelines: oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, tUE. The diagram shows the flow of LCLS messages when a BSS determines local switching should be disconnected. A red double-headed arrow at the top indicates 'Call is locally Switched'. Step 1 shows notifications from oBSS to oMSC-S and tBSS. Step 2b shows LCLS\_NOTIFICATION from oBSS to oMSC-S. Step 3b shows LCLS Status Update from oMSC-S to iMSC-S. Step 3a shows LCLS Status Update from tBSS to tMSC-S. A note indicates iMSC-S does not forward the update to tMSC-S. Step 4a shows LCLS Status Update from iMSC-S to oMSC-S. + +Figure 7.2.4.3.1: BSS initiated, immediate LCLS break + +1. The BSS determines that local switching should be disconnected. +- 2a, b. The BSS reports the LCLS disconnection by sending the LCLS-Notification message with the LCLS-BSS-Status IE set to "the call is no longer locally switched" to the tMSC server and oMSC server. +3. + - a) The tMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" to the preceding node. + - b) The oMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" to the succeeding node. +- 4a. The iMSC server transfers the LCLS Status Update message to the oMSC server. + +NOTE: At reception of the LCLS Status Update message from the oMSC server, the iMSC server does not forward the LCLS Status Update message since the same LCLS Status is already received from the tMSC server. + +### 7.2.4.4 BSS Initiated, LCLS Break requested from Core Network + +Figure 7.2.4.4.1 shows the message sequence example for the BSS initiated but when the LCLS Break is requested from the Core Network. + +![Sequence diagram for BSS initiated, LCLS Release ordered from Core Network. Lifelines: oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, tUE. The diagram shows message exchanges between oBSS and oMSC-S, tBSS and tMSC-S, and various MSC and MGW interactions. A red double-headed arrow at the top indicates 'Call is locally Switched' between oUE and tUE. A blue box at the bottom notes that the iMSC server does not forward the LCLS Status Update message because it already received it from the tMSC server.](7722d62e33dcc894cc8555e9474c5606_img.jpg) + +The sequence diagram illustrates the following message flow: + +- 1. Release LCLS**: Sent from **oBSS** to **oUE** and from **tBSS** to **tUE**. +- 2a. LCLS\_NOTIFICATION (LCLS-Break-Request)**: Sent from **oBSS** to **oMSC-S**. +- 2b. LCLS\_NOTIFICATION (LCLS-Break-Request)**: Sent from **tBSS** to **tMSC-S**. +- 3a. LCLS Status Change Request [LCLS-Status-Change = "LCLS-Disconnection-Preparation"]**: Sent from **oMSC-S** to **iMSC-S**. +- 3b. LCLS Status Change Request [LCLS-Status-Change = "LCLS-Disconnection-Preparation"]**: Sent from **tMSC-S** to **iMSC-S**. +- 4a. LCLS Status Change Request [LCLS-Status-Change = "LCLS-Disconnection-Preparation"]**: Sent from **iMSC-S** to **tMSC-S**. +- 4b. LCLS Status Change Request [LCLS-Status-Change = "LCLS-Disconnection-Preparation"]**: Sent from **iMSC-S** to **oMSC-S**. +- 5a. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "Release LCLS")**: Sent from **tMSC-S** to **tBSS**. +- 5b. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "Release LCLS")**: Sent from **oMSC-S** to **oBSS**. +- 6a. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration")**: Sent from **tBSS** to **tMSC-S**. +- 6b. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call is no longer locally switched")**: Sent from **oBSS** to **oMSC-S**. +- 6c. LCLS\_NOTIFICATION (LCLS-BSS-Status = "call is no longer locally switched")**: Sent from **tMSC-S** to **tBSS**. +- 7a. LCLS Status Change Request Acknowledge [LCLS-Status-Change = "LCLS-Disconnection-Preparation", Result Code="Status Change Req Accepted"]**: Sent from **iMSC-S** to **tMSC-S**. +- 7b. LCLS Status Change Request Acknowledge [LCLS-Status-Change = "LCLS-Disconnection-Preparation", Result Code="Status Change Req Accepted"]**: Sent from **oMSC-S** to **iMSC-S**. +- 8a. LCLS Status Change Request Acknowledge [LCLS-Status-Change = "LCLS-Disconnection-Preparation", Result Code="Status Change Req Accepted"]**: Sent from **iMSC-S** to **oMSC-S**. +- 8b. LCLS Status Change Request Acknowledge [LCLS-Status-Change = "LCLS-Disconnection-Preparation", Result Code="Status Change Req Accepted"]**: Sent from **tMSC-S** to **iMSC-S**. +- 9. LCLS Status Update [LCLS-Status = "LCLS not connected"]**: Sent from **oMSC-S** to **iMSC-S**. +- 10. LCLS Status Update [LCLS-Status = "LCLS not connected"]**: Sent from **iMSC-S** to **tMSC-S**. +- 11. LCLS Status Update [LCLS-Status = "LCLS not connected"]**: Sent from **tMSC-S** to **tBSS**. + +LCLS Status Update message is not forwarded since the same information is already received from the preceding MSC server. + +Sequence diagram for BSS initiated, LCLS Release ordered from Core Network. Lifelines: oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, tUE. The diagram shows message exchanges between oBSS and oMSC-S, tBSS and tMSC-S, and various MSC and MGW interactions. A red double-headed arrow at the top indicates 'Call is locally Switched' between oUE and tUE. A blue box at the bottom notes that the iMSC server does not forward the LCLS Status Update message because it already received it from the tMSC server. + +**Figure 7.2.4.4.1: BSS initiated, LCLS Release ordered from Core Network** + +1. The BSS determines that local switching should be disconnected. +- 2a, b. The BSS requests the LCLS disconnection by sending the LCLS-Notification message with LCLS-Break-Request IE set to "LCLS Break Request" to the oMSC server and tMSC server. +3. + - a) The oMSC server sends to the succeeding node the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation". + - b) The tMSC server sends to the preceding node the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation". +- 4a, b. The iMSC server transfers the LCLS Status Change Request message to the succeeding/preceding node. +5. + - a) The tMSC server sends to the tBSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS". + +- b) The oMSC server sends to the oBSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS". +6. a) The tBSS confirms the reception of the LCLS release request with the LCLS-Connect-Control Acknowledge message but does not change the LCLS-BSS status since LCLS release request is not yet received for the associated call leg. +- b) The oBSS reports the LCLS disconnection by sending the LCLS-Connect-Control Acknowledge message with the LCLS-BSS-Status IE set to "the call is no longer locally switched" to the oMSC server. +- c) The tBSS reports the LCLS disconnection by sending the LCLS-Notification message with the LCLS-BSS-Status IE set to "the call is no longer locally switched to the tMSC server." +7. a) On the receipt of the LCLS-Connect-Control Acknowledge message with the LCLS-BSS status still indicating local switching the tMSC server sends to the preceding node the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and the Result code IE set to LCLS Status Change Request accepted. +- b) On the receipt of the LCLS-Connect-Control Acknowledge message the oMSC server sends to the succeeding node the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and the Result code IE set to LCLS Status Change Request accepted. +8. a) The iMSC server transfers the LCLS Status Change Request Acknowledge message to the preceding node. +- b) The iMSC server transfers the LCLS Status Change Request Acknowledge message to the succeeding node. +- NOTE1: The oMSC server already requested the LCLS break from the oBSS (step 5b) and due to that it does not perform any action on the receipt of the LCLS Status Change Request Acknowledge message. The tMSC server does not perform any action on the receipt of the LCLS Status Change Request Acknowledge message since it already requested the LCLS break from the tBSS (step 5a) and already received LCLS-Notification message indicating LCLS disconnection (step 6c). +9. At reception of the LCLS-Connect-Control Acknowledge message indicating LCLS disconnection the oMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" to the succeeding node. +10. The iMSC server transfers the LCLS Status Update message to the succeeding node. +11. On the receipt of the LCLS-Notification message indicating LCLS disconnection the tMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" to the preceding node. +- NOTE2: At reception of the LCLS Status Update message from the tMSC server, the iMSC server does not forward the LCLS Status Update message since the same LCLS Status is already received from the oMSC server. + +#### 7.2.4.5 Intermediate Node/GMSC Server Initiated + +Figure 7.2.4.5.1 shows the message sequence example for the network initiated LCLS Break. + +![Sequence diagram for Figure 7.2.4.5.1: Intermediate Node / GMSC Server initiated LCLS break. The diagram shows vertical lifelines for oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, and tUE. At the top, a red double-headed arrow spans from oUE to tUE labeled 'Call is locally Switched'. The sequence starts with step 1: 'Release LCLS' at iMSC-S. Step 2a and 2b are 'LCLS Status Change Request' messages from iMSC-S to oMSC-S and tMSC-S respectively. Steps 3a and 3b are 'LCLS_CONNECT_CONTROL' messages from MSCs to BSSs. Steps 4a and 4b are 'LCLS_CONNECT_CONTROL_ACK' messages. Step 4c is 'LCLS_NOTIFICATION'. Steps 5a and 5b are 'LCLS Status Change Request Acknowledge' messages back to iMSC-S. Steps 6a and 6b are 'LCLS Status Update' messages to iMSC-S. A blue box at the bottom states: 'LCLS Status Update indicating LCLS not connected is received from the succeeding MSC server and the preceding MSC server.'](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +Sequence diagram for Figure 7.2.4.5.1: Intermediate Node / GMSC Server initiated LCLS break. The diagram shows vertical lifelines for oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, and tUE. At the top, a red double-headed arrow spans from oUE to tUE labeled 'Call is locally Switched'. The sequence starts with step 1: 'Release LCLS' at iMSC-S. Step 2a and 2b are 'LCLS Status Change Request' messages from iMSC-S to oMSC-S and tMSC-S respectively. Steps 3a and 3b are 'LCLS\_CONNECT\_CONTROL' messages from MSCs to BSSs. Steps 4a and 4b are 'LCLS\_CONNECT\_CONTROL\_ACK' messages. Step 4c is 'LCLS\_NOTIFICATION'. Steps 5a and 5b are 'LCLS Status Change Request Acknowledge' messages back to iMSC-S. Steps 6a and 6b are 'LCLS Status Update' messages to iMSC-S. A blue box at the bottom states: 'LCLS Status Update indicating LCLS not connected is received from the succeeding MSC server and the preceding MSC server.' + +**Figure 7.2.4.5.1: Intermediate Node / GMSC Server initiated LCLS break** + +1. The iMSC server determines that local switching should be disconnected. +- 2a, b. The iMSC server send the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" to the preceding node and to the succeeding node. +3. + - a) The oMSC server sends to the oBSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS". + - b) The tMSC server sends to the tBSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "Release LCLS". +4. + - a) The oBSS confirms the reception of the LCLS release request but does not change the LCLS-BSS status since LCLS release request is not yet received for the associated call leg. + - b) The tBSS reports the LCLS disconnection by sending the LCLS-Connect-Control Acknowledge message with the LCLS-BSS-Status IE set to "the call is no longer locally switched" to the tMSC server. + - c) The oBSS reports the LCLS disconnection by sending the LCLS-Notification message with the LCLS-BSS-Status IE set to "the call is no longer locally switched" to the oMSC server. +5. + - a) On the receipt of the LCLS-Connect-Control Acknowledge message with the LCLS-BSS status still indicating local switching the oMSC server sends to the succeeding node the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and the Result code IE set to LCLS Status Change Request accepted. + - b) On the receipt of the LCLS-Connect-Control Acknowledge message the tMSC server sends to the preceding node the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation" and the Result code IE set to LCLS Status Change Request accepted. + +NOTE1: Since the LCLS disconnection is ordered by the iMSC server it does not forward the LCLS Status Change Request Acknowledge message to the succeeding node. + +- 6. a) At reception of the LCLS-Connect-Control Acknowledge message indicating LCLS disconnection the tMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" to the preceding node. +- b) On the receipt of the LCLS-Notification message the oMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Not Connected" to the succeeding node. + +NOTE2: Since the LCLS disconnection is ordered by the iMSC server it does not forward the LCLS Status Update message to the preceding/succeeding node. + +### 7.2.4.6 MSC server Initiated when Access Side Termination is isolated in MGW + +Figure 7.2.4.6.1 shows the message sequence example for the MSC server initiated LCLS Break for the case when the LCLS negotiation through the Core Network enabled the MSC server to use the option to isolate access side termination from the network side termination. + +In this example the oMSC server moves the originating UE (access side termination T1) back to the context oC with network side termination T2 and requests the oMGW to be bothway through-connected after the oMSC server determined that local switching should be disconnected and sent to the succeeding node the LCLS Status Change Request message indicating LCLS disconnection preparation. + +![Sequence diagram for MSC initiated LCLS break. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. A red double-headed arrow labeled 'Call is locally Switched' spans from oUE to tBSS. Step 1: oMSC sends 'Release LCLS' to oMGW. Step 2a: oMSC sends 'LCLS Status Change Request: APM' to iMSC. Step 2b: oMSC sends 'MOV request (T1) / MOV reply' to oMGW. iMSC sends 'Context oC' and 'Join Bearer Termination' to oMSC. A note at the bottom states: 'For succeeding signaling sequences see figure 7.2.4.2.1 steps 3 - 12'.](7e74ac663f3e644b589ed28f5fd29398_img.jpg) + +Sequence diagram for MSC initiated LCLS break. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. A red double-headed arrow labeled 'Call is locally Switched' spans from oUE to tBSS. Step 1: oMSC sends 'Release LCLS' to oMGW. Step 2a: oMSC sends 'LCLS Status Change Request: APM' to iMSC. Step 2b: oMSC sends 'MOV request (T1) / MOV reply' to oMGW. iMSC sends 'Context oC' and 'Join Bearer Termination' to oMSC. A note at the bottom states: 'For succeeding signaling sequences see figure 7.2.4.2.1 steps 3 - 12'. + +Figure 7.2.4.6.1: MSC initiated LCLS break, access side termination isolated in MGW + +- 1. The oMSC server determines that local switching should be disconnected. +- 2. The oMSC server sends to: + - a) the succeeding node the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Disconnection-Preparation"; + - b) the oMGW request to move the access side termination T1 to context oC with the network side termination T2; + +NOTE 1: Steps 2a and 2b can be performed in parallel. + +NOTE 2: If the MSC server has previously used the Change Through-Connection procedure and requested the MGW to change the through-connection of the bearer to inactive instead of using the Isolate Bearer termination procedure then the MSC server will use the Change Through-Connection procedure to request the MGW to change the through-connection of the bearer to be both-way through-connected. + +- 3. The further steps are performed as defined in sub-clause 7.2.4.2, steps 3 - 12. + +## 7.3 LCLS Re-establishment + +### 7.3.1 MSC server Initiated + +#### 7.3.1.1 Principles + +The following Re-establishment procedures describe the scenario when a node has requested an LCLS-break for a temporary period while applying a supplementary service or CN intervention and once completed wishes to resume the LCLS connection. If the node which broke the LCLS does not re-establish the LCLS via these procedures, LCLS can also be re-established by another interaction such as handovers (as specified in clause 8) or subsequent LCLS negotiations (e.g. due to supplementary service interaction). If a node in the path does not accept the LCLS Status Change Request (e.g. re-establishment) it shall respond with a LCLS Status Change Request Acknowledge message containing a Result Code IE set to "Status Change Request rejected", and not forward the LCLS Status Change Request to the succeeding (or preceding) node. + +#### 7.3.1.2 MSC server actions + +##### 7.3.1.2.1 LCLS re-establishment to the network side + +The MSC server which initiates LCLS re-establishment shall send the LCLS Status Change Request message with the LCLS-Status-Change IE to the succeeding (or preceding) node to requests a change in LCLS Status in the CN. + +Once the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Connection-Preparation" is received from the preceding (or succeeding) node, the MSC server shall check if the requested LCLS Status is allowed and shall send the LCLS Status Change Request Acknowledge message with the correct LCLS-Status-Change IE value and with a Result code back to the preceding (or succeeding) node. The Result code indicates whether LCLS Status Change Request is accepted or not. + +##### 7.3.1.2.2 LCLS re-establishment to the BSS + +Once the LCLS-Status-Change Request message with LCLS-Status-Change IE or the LCLS-Status-Change Request Acknowledge message with the LCLS-Status-Change IE sent from the preceding (or succeeding) node is received, the MSC sever shall check if the requested LCLS Status is allowed or not and if it is allowed then the MSC Server shall send the LCLS-CONNECT-CONTROL message with LCLS-Connection-Status-Control set to "connect" to the BSS + +##### 7.3.1.2.3 LCLS Status update to the network side + +Once the LCLS-Notification message or LCLS-Connect-Control-ACK message sent from BSS is received by MSC server, and if the received LCLS-BSS-Status indicates local switching, the MSC server shall send to the succeeding (or preceding) node the LCLS Status Update message with the LCLS-Status IE set to "LCLS Connected" if the same LCLS status update is not already received from the succeeding (or preceding) node.. + +#### 7.3.1.3 GMSC server actions + +Once the LCLS Status Change Request message with the LCLS-Status-Change IE sent from preceding (or succeeding) node is received, the GMSC sever shall check if the requested LCLS Status is allowed or not and if it is allowed the GMSC server shall forward the LCLS Status Change Request message with correct value to the succeeding (or preceding) node. + +At the reception of the LCLS-Status-Change Request Acknowledge message from the succeeding/preceding node the GMSC server shall forward the received message to the preceding/succeeding node. + +Once the LCLS-Status-Update message with the LCLS Status IE sent from preceding/succeeding node is received by GMSC server, + +- the GMSC Server shall forward the message to the succeeding/preceding node if the same request is not already received from the succeeding/preceding node. +- the GMSC Server shall not forward the message if the same request is already received from the succeeding/preceding node. + +### 7.3.1.4 BSS actions + +On receipt of the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "connect LCLS" the BSS may establish LCLS (following the principles described in sub-clause 4.4) and notify the CN as described for LCLS call establishment. + +## 7.3.2 BSS Initiated + +BSS Initiated LCLS re-establishment is not supported for LCLS. + +## 7.3.3 Intermediate Node / GMSC Server Initiated + +### 7.3.3.1 Principles + +The following Re-establishment procedures describe the scenario when a node has requested an LCLS-break for a temporary period while applying a supplementary service or CN intervention and once completed wishes to resume the LCLS connection. If the node which broke the LCLS does not re-establish the LCLS via these procedures, LCLS can also be re-established by another interaction such as handovers (as specified in clause 8) or subsequent LCLS negotiations (e.g. due to supplementary service interaction). If a node in the path does not accept the LCLS Status Change Request (e.g. re-establishment) it shall respond with a LCLS Status Change Request Acknowledge message containing a Result Code IE set to "Status Change Request rejected", and not forward the LCLS Status Change Request to succeeding/preceding node. + +### 7.3.3.2 Intermediate Node / GMSC server actions + +When an intermediate node or the GMSC server determines that local switching should be re-established it shall send the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Connection-Preparation" to the preceding and to the succeeding node. + +The intermediate node or the GMSC Server not initiating the LCLS re-establishment shall check if the requested LCLS Status is allowed or not and if it is allowed the intermediate node shall forward the received LCLS Status Change Request message. + +On receipt of the LCLS Status Change Request Acknowledge message with the LCLS-Status-Change IE set to "LCLS Connection Preparation" and a Result code IE from the preceding/succeeding node, the intermediate node or the GMSC Server not initiating the LCLS re-establishment shall forward message to the succeeding/preceding node. The Result code indicates whether LCLS Status Change Request is accepted or not. + +On receipt of the LCLS Status Update message with the LCLS-Status IE set to "LCLS Connected" from the preceding/succeeding node: + +- the intermediate node or the GMSC Server not initiating the LCLS re-establishment shall forward the message to the succeeding/preceding node. +- the intermediate node or the GMSC Server initiating the LCLS re-establishment shall not forward the message. + +### 7.3.3.3 MSC server actions + +When the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS Connection Preparation" is received from the succeeding (or preceding) node, the MSC Server shall check if the requested LCLS status is allowed or not and if it is allowed then the MSC Server shall send to BSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "connect". The MSC server shall send LCLS Status Change Request Acknowledge message with the correct LCLS-Status-Change IE value and a Result code back to the preceding (or succeeding) node. The Result code indicates whether LCLS Status Change Request is accepted or not. + +At reception of the LCLS-Connect-Control Acknowledge message or the LCLS-Notification message with the LCLS-BSS-Status IE set to "Call is Locally switched with requested LCLS configuration", the MSC server shall send to the succeeding (or preceding) node the LCLS Status Update message with the LCLS-Status IE set to "LCLS Connected" if the same LCLS status update is not already received from the succeeding (or preceding) node. + +### 7.3.3.4 BSS actions + +The BSS shall perform the same actions as described in sub-clause 7.3.1.4. + +### 7.3.4 LCLS Re-establishment Example Call Flows + +#### 7.3.4.1 LCLS Re-establishment Connection Model for LCLS + +Figure 7.3.4.1.1 shows the network model for a LCLS Re-establishment of the mobile call. The "squared" line represents the call control signalling. The "dotted/full" line represents the bearer terminations in the MGW. Bearer termination T1 and T6 are used for the bearer towards BSC and bearer termination T2, T3, T4 and T5 are used for the bearer towards preceding/succeeding MGW. + +![Diagram of Connection Model 1: Before LCLS Re-establishment. It shows three MSC servers (oMSC-S, iMSC-S, tMSC-S) connected by control signalling (green dashed lines). Below them are three MGWs (oMGW, iMGW, tMGW) with bearers (red solid lines) and terminations (T1-T6). On the left, two UEs (tUE, oUE) are connected to an oBSS/tBSS. The oBSS/tBSS is connected to the oMSC-S via control signalling and to the oMGW via a bearer. The oMGW is connected to the iMGW via a bearer, and the iMGW is connected to the tMGW via a bearer. The tMGW is connected to the tMSC-S via a bearer. The legend indicates: green dashed line for control plane signalling, dotted line for user plane path through CN, and red solid line for user plane data.](3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg) + +Diagram of Connection Model 1: Before LCLS Re-establishment. It shows three MSC servers (oMSC-S, iMSC-S, tMSC-S) connected by control signalling (green dashed lines). Below them are three MGWs (oMGW, iMGW, tMGW) with bearers (red solid lines) and terminations (T1-T6). On the left, two UEs (tUE, oUE) are connected to an oBSS/tBSS. The oBSS/tBSS is connected to the oMSC-S via control signalling and to the oMGW via a bearer. The oMGW is connected to the iMGW via a bearer, and the iMGW is connected to the tMGW via a bearer. The tMGW is connected to the tMSC-S via a bearer. The legend indicates: green dashed line for control plane signalling, dotted line for user plane path through CN, and red solid line for user plane data. + +Connection Model 1: Before LCLS Re-establishment + +![Diagram of Connection Model 2: After LCLS Re-establishment. This diagram is similar to the first one but shows a change in the user plane path. The red solid line representing user plane data now goes from the oBSS/tBSS directly to the oMGW, bypassing the MSC servers. The path from the oMGW through the iMGW to the tMGW is now labeled 'Non LCLS User Plane' and is represented by a dotted line. The control signalling remains the same as in the first model.](e90b25c8d90cadc3f76c376701cf27ed_img.jpg) + +Diagram of Connection Model 2: After LCLS Re-establishment. This diagram is similar to the first one but shows a change in the user plane path. The red solid line representing user plane data now goes from the oBSS/tBSS directly to the oMGW, bypassing the MSC servers. The path from the oMGW through the iMGW to the tMGW is now labeled 'Non LCLS User Plane' and is represented by a dotted line. The control signalling remains the same as in the first model. + +Connection Model 2: After LCLS Re-establishment + +Figure 7.3.4.1.1: LCLS Re-establishment (Network model) + +#### 7.3.4.2 MSC server Initiated Example Call Flow + +Figure 7.3.4.2.1 shows the message sequence example for the MSC server initiated LCLS Re-establishment. In the example the MSC server trigger the LCLS negotiation in the CN. The BSS establishes local switching when both legs are informed LCLS is allowed. + +![Sequence diagram for MSC server Initiated LCLS Re-establishment. Lifelines: oUE, oBSS, oMGW, oMSC-S, iMSC-S, iMGW, tMSC-S, tMGW, tBSS, tUE. The process involves LCLS Status Change Requests, Acknowledges, and Connect Controls between the MSC servers and BSSs. A red arrow indicates the call is locally switched between oBSS and tBSS.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) + +``` + +sequenceDiagram + participant oUE + participant oBSS + participant oMGW + participant oMSC-S + participant iMSC-S + participant iMGW + participant tMSC-S + participant tMGW + participant tBSS + participant tUE + + oMSC-S->>iMSC-S: 1. LCLS Status Change Request (LCLS-Status-Change= "LCLS Connection Preparation") + iMSC-S->>tMSC-S: 2. LCLS Status Change Request (LCLS-Status-Change= "LCLS Connection Preparation") + tMSC-S->>iMSC-S: 3. LCLS Status Change Request Acknowledge (LCLS-Status-Change= "LCLS Connection Preparation", Result Code="Status Change Req Accepted") + tMSC-S->>tBSS: 4. LCLS-Connect-Control (LCLS-Connection-Status-Control = "Connect") + iMSC-S->>oMSC-S: 5. LCLS Status Change Request Acknowledge (LCLS-Status-Change= "LCLS Connection Preparation", Result Code="Status Change Req Accepted") + tBSS->>tMSC-S: 6. LCLS-Connect-Control_ACK (LCLS-BSS-Status = "call is no longer locally switched") + oMSC-S->>oBSS: 7. LCLS-Connect-Control (LCLS-Connection-Status-Control = "Connect") + Note over oBSS: 8. LCLS Re-establishment + oBSS-->tBSS: Call is locally Switched + oBSS->>oMSC-S: 9. LCLS-Connect-Control_ACK (LCLS-BSS-Status = "Call is Locally Switched with requested LCLS configuration") + tBSS->>tMSC-S: 10. LCLS-Notification (LCLS-BSS-Status = "Call is Locally Switched with requested LCLS configuration") + oMSC-S->>iMSC-S: 11. LCLS status update: (LCLS-Status = "LCLS connected") + iMSC-S->>tMSC-S: 12. LCLS status update: (LCLS-Status = "LCLS connected") + tMSC-S->>tBSS: 13. LCLS status update: (LCLS-Status = "LCLS connected") + +``` + +Sequence diagram for MSC server Initiated LCLS Re-establishment. Lifelines: oUE, oBSS, oMGW, oMSC-S, iMSC-S, iMGW, tMSC-S, tMGW, tBSS, tUE. The process involves LCLS Status Change Requests, Acknowledges, and Connect Controls between the MSC servers and BSSs. A red arrow indicates the call is locally switched between oBSS and tBSS. + +**Figure 7.3.4.2.1: MSC server Initiated LCLS Re-establishment** + +1. The oMSC server determines that local switching should be re-established. The oMSC server sends to the succeeding node the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Connection-Preparation". + 2. The iMSC server transfers the LCLS Status Change Request message to the tMSC server. + 3. The tMSC server sends LCLS Status Change Request Acknowledge message to the preceding node. + 4. The tMSC server sends to the tBSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "connect". +- NOTE: Step 3 and 4 can be performed paralleled. +5. The iMSC server transfers the LCLS Status Change Request Acknowledge message to the oMSC server. + 6. The oBSS confirms the reception of the LCLS connect request but does not change the LCLS-BSS status since LCLS connect request is not yet received for the associated call leg. + 7. On receipt of LCLS Status Change Request Acknowledge message, the oMSC server sends to the oBSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "connect". + +8. Because LCLS connect requests are received for the associated call leg, the oBSS/tBSS re-establish the LCLS. +9. The oBSS reports the LCLS connection by sending the LCLS-Connect-Control Acknowledge message to the oMSC server. +10. The tBSS reports the LCLS connection by sending the LCLS-Notification message to the tMSC server. +11. The oMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Connected" to the succeeding node. +12. The iMSC server transfers the LCLS Status Update message to the tMSC server. +13. The tMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Connected" to the preceding node. The iMSC server does not forward the LCLS Status Update message to the oMSC server since the same LCLS Status is already received from the oMSC server. + +### 7.3.4.3 Intermediate Node / GMSC Server Initiated Example Call Flow + +Figure 7.3.4.3.1 shows the message sequence example for the Intermediate Node / GMSC Server initiated LCLS Re-establishment. + +![Sequence diagram for Intermediate Node / GMSC Server Initiated LCLS Re-establishment. Lifelines: oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, tUE. The process involves a 'Re-establish LCLS' trigger at the iMSC-S, followed by a series of LCLS Status Change Requests and Acknowledges between the iMSC-S, oMSC-S, and tMSC-S. The oMSC-S then sends LCLS_CONNECT_CONTROL to the oBSS, which responds with LCLS_CONNECT_CONTROL_ACK. The tMSC-S sends LCLS_CONNECT_CONTROL to the tBSS, which responds with LCLS_CONNECT_CONTROL_ACK. A red arrow labeled 'Call is locally Switched' spans from the oBSS to the tBSS. Finally, the oMSC-S and tMSC-S send LCLS Status updates to the iMSC-S, which receives them and indicates LCLS connected status.](cfc2672ccfdf7b47212ef2b8d72c0ff3_img.jpg) + +Sequence diagram for Intermediate Node / GMSC Server Initiated LCLS Re-establishment. Lifelines: oUE, oBSS, oMGW, oMSC-S, iMGW, iMSC-S, tMSC-S, tMGW, tBSS, tUE. The process involves a 'Re-establish LCLS' trigger at the iMSC-S, followed by a series of LCLS Status Change Requests and Acknowledges between the iMSC-S, oMSC-S, and tMSC-S. The oMSC-S then sends LCLS\_CONNECT\_CONTROL to the oBSS, which responds with LCLS\_CONNECT\_CONTROL\_ACK. The tMSC-S sends LCLS\_CONNECT\_CONTROL to the tBSS, which responds with LCLS\_CONNECT\_CONTROL\_ACK. A red arrow labeled 'Call is locally Switched' spans from the oBSS to the tBSS. Finally, the oMSC-S and tMSC-S send LCLS Status updates to the iMSC-S, which receives them and indicates LCLS connected status. + +**Figure 7.3.4.3.1: Intermediate Node / GMSC Server Initiated LCLS Re-establishment** + +1. The iMSC server determines that local switching should be established. +2. The iMSC server sends the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Connection-Preparation" to the oMSC server. + +3. The iMSC server sends the LCLS Status Change Request message with the LCLS-Status-Change IE set to "LCLS-Connection-Preparation" to the tMSC server. +4. The oMSC server sends LCLS Status Change Request Acknowledge message to the succeeding node. +5. The tMSC server sends LCLS Status Change Request Acknowledge message to the preceding node. +6. The oMSC server sends to the oBSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "connect". +7. The oBSS confirms the reception of the LCLS connect request but does not change the LCLS-BSS status since LCLS connect request is not yet received for the associated call leg. +8. The tMSC server sends to the tBSS the LCLS-Connect-Control message with the LCLS-Connection-Status-Control IE set to "connect". +- 9a. The tBSS reports the LCLS connection by sending the LCLS-Connect-Control Acknowledge message to the tMSC server. +- 9b. The oBSS reports the LCLS connection by sending the LCLS-Notification message to the oMSC server. +10. The tMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Connected" to the preceding node. +11. The oMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Connected" to the succeeding node. + +NOTE: Since LCLS re-establishment is ordered by the iMSC server it does not forward the LCLS Status Update message to the preceding/succeeding node. + +#### 7.3.4.4 MSC server Initiated when Access Side Termination is isolated in MGW + +Figure 7.3.4.4.1 shows the message sequence example for the MSC server initiated LCLS Re-establishment for the case when the LCLS negotiation through the Core Network enabled the MSC server to use the option to isolate access side termination from the network side termination. + +In this example the oMSC server requests the oMGW to interrupt the communication on the bearer by using the Isolate Bearer Termination Procedure (i.e. to isolate access side termination T1 from the network side termination T2) after the oBSS re-established local switching. + +![Sequence diagram for MSC server Initiated LCLS Re-establishment, access side termination isolated in MGW. The diagram shows interactions between oUE, oBSS, oMSC-S, iMSC-S, tMSC-S, tBSS, and tUE, with intermediate MGWs (oMGW, iMGW, tMGW).](31ef15d175af5babdbf4d2fbac884c1b_img.jpg) + +The diagram illustrates the signaling sequence for LCLS re-establishment when access side termination is isolated in the MGW. The participants are oUE, oBSS, oMSC-S, iMSC-S, tMSC-S, tBSS, and tUE. The oMSC-S is connected to oMGW, which is connected to oBSS. The iMSC-S is connected to iMGW, which is connected to tMSC-S. The tMSC-S is connected to tMGW, which is connected to tBSS. The sequence starts with a bar indicating preceding signaling sequences (steps 1-10 from figure 7.3.4.2.1). Step 11a shows a MOV request (T1) / MOV reply between oMSC-S and oMGW, with a Context (Cs) and Isolate bearer termination message. Step 11b shows an LCLS status update (LCLS-Status = "LCLS connected") from oMSC-S to iMSC-S. Step 12 shows an LCLS status update (LCLS-Status = "LCLS connected") from iMSC-S to tMSC-S. Step 13 shows an LCLS status update (LCLS-Status = "LCLS connected") from tMSC-S to tBSS. + +Sequence diagram for MSC server Initiated LCLS Re-establishment, access side termination isolated in MGW. The diagram shows interactions between oUE, oBSS, oMSC-S, iMSC-S, tMSC-S, tBSS, and tUE, with intermediate MGWs (oMGW, iMGW, tMGW). + +Figure 7.3.4.4.1: MSC server Initiated LCLS Re-establishment, access side termination isolated in MGW + +- 1 - 10. When the oMSC server determines that local switching should be re-established it initiates the LCLS Re-establishment procedure specified in sub-clause 7.3.4.2, steps 1 – 10. +11. a) The oMSC server send to the oMGW request to isolate the access side termination T1 from the network side termination T2. +NOTE 1: The MSC server can also use the Change Through-Connection procedure and requests the MGW to change the through-connection of the bearer to inactive instead of using of the Isolate Bearer termination procedure, see 3GPP TS 23.205 [2]. +b) The oMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Connected" to the succeeding node. +NOTE 2: Steps 11a and 11b can be performed in parallel. +12. The iMSC server transfers the LCLS Status Update message to the tMSC server. +13. The tMSC server sends the LCLS Status Update message with the LCLS-Status IE set to "LCLS Connected" to the preceding node. The iMSC server does not forward the LCLS Status Update message to the oMSC server since the same LCLS Status is already received from the oMSC server. + +--- + +## 8 Handover/Relocation + +### 8.1 UMTS to UMTS + +For Inter-MSC Handover UMTS to UMTS the Anchor MSC server shall include the GCR IE, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE in IAM to the Target MSC server. The Target MSC server may modify the LCLS-Configuration-Preference IE based on its own LCLS configuration requirements. The rules for LCLS Configuration settings are defined in clause 4.2. The Target MSC server shall include the final LCLS-Configuration-Preference IE and the LCLS-Negotiation Response IE in the APM or ACM or CPG. The Target MSC server may then use the LCLS parameters to enable LCLS if a subsequent UTRAN to GERAN handover occurs. + +### 8.2 UMTS to GSM + +#### 8.2.1 General + +The procedures specified in 3GPP TS 23.205 [2] for BICC based CS Core Network and 3GPP 23.231 [3] for SIP-I based CS Core Network shall be followed. The following clauses describe the additional requirements for LCLS functionality. + +#### 8.2.2 Intra-MSC UMTS to GSM Handover + +##### 8.2.2.1 Intra-MSC UMTS to GSM Handover that establishes Local Switching + +###### 8.2.2.1.1 General + +When LCLS is not established for a call and an intra-MSC UMTS to GSM handover occurs that makes the call local, the call can be locally switched in the Target BSS. The following clauses describe the additional requirements for intra-MSC UMTS to GSM handover that establish LCLS. + +###### 8.2.2.1.2 Relocation Required + +When the MSC server receives the Relocation Required message from the serving RNC, it requests the MGW to seize a TDM circuit if AoTDM or an IP termination if AoIP for the termination to the Target BSS as for the normal handover procedure. + +The MSC server sends the Handover Request message to the Target BSS as for the normal case but shall include the GCR IE, the LCLS-Configuration IE and the LCLS-Connection-Status-Control IE set to "Connect". + +### 8.2.2.1.3 Handover Request Acknowledge + +If the Target BSS supports LCLS feature then it shall include the LCLS-BSS-Status IE in the Handover Request Acknowledge message in order to inform the MSC Server that the BSS supports the LCLS feature. + +### 8.2.2.1.4 Handover Complete + +The target BSS sends Handover Complete including the LCLS-BSS-Status IE, which indicates to the MSC server that the call is locally switched. + +NOTE: The target BSS will send LCLS-Notification message to the MSC at the other call leg indicating the call is locally switched. + +### 8.2.2.1.5 Example + +#### 8.2.2.1.5.1 Connection Model + +Figure 8.2.2.1.5.1.1 shows the network model for the Basic Intra-MSC UMTS to GSM handover when LCLS is established as a result of the handover. The dashed line in green represents call control signalling and the dashed line in blue represents the user plane connection path via the core network, which should be used if LCLS is not established or after LCLS is broken. The non-dotted lines represent the bearer carrying real user plane data. In MGW-1 the bearer termination $T_S$ is used for the bearer towards RNC, bearer termination $T_A$ is used for the bearer towards the succeeding/preceding MGW, that is MGW-2 and bearer termination $T_T$ is used towards the Target BSS. In MGW-2 the bearer termination $T_2$ is used for the bearer towards BSS-2 and bearer termination $T_1$ is used for the bearer towards MGW-1. + +In this example scenario the Handover Device is located in MGW-1 selected for the call establishment by the MSC-1 server, which controls the call and mobility management. + +- ━━━ User plane link which transmits real user plane data within BSS and to UE +- ━━━ User plane link which transmits real user plane data through the CN and to UE +- ● ● ● User plane link path through CN, connected +- ● ● ● Control plane link which transmits signalling + +![Diagram of Connection Model 1: Before Handover. It shows network nodes BSS-2, RNC, MSC-1 S, MSC-2 S, MGW-1, and MGW-2. MGW-1 has ports T_S and T_A. MGW-2 has ports T_1 and T_2. Solid black lines connect RNC to MGW-1 (T_A) and MGW-1 to MGW-2. A dashed green line represents control signaling between MSCs and BSS/RNC nodes.](74b540f71bcf10a8a66b2f01ea8c08ec_img.jpg) + +Before Handover + $T_S$ = Serving + $T_A$ = Anchor + +Diagram of Connection Model 1: Before Handover. It shows network nodes BSS-2, RNC, MSC-1 S, MSC-2 S, MGW-1, and MGW-2. MGW-1 has ports T\_S and T\_A. MGW-2 has ports T\_1 and T\_2. Solid black lines connect RNC to MGW-1 (T\_A) and MGW-1 to MGW-2. A dashed green line represents control signaling between MSCs and BSS/RNC nodes. + +**Connection Model 1: Before Handover** + +![Diagram of Connection Model 2: During Handover. Similar to Model 1, but MGW-1 now includes a Target port T_T. The RNC is connected to T_T. T_A is one-way connected to T_T. T_S remains connected to BSS-2. Control signaling paths are updated to include the Target BSS.](677bcb564410628b8b966ad87b394888_img.jpg) + +During Handover + $T_S$ = Serving + $T_A$ = Anchor + $T_T$ = Target + +Diagram of Connection Model 2: During Handover. Similar to Model 1, but MGW-1 now includes a Target port T\_T. The RNC is connected to T\_T. T\_A is one-way connected to T\_T. T\_S remains connected to BSS-2. Control signaling paths are updated to include the Target BSS. + +**Connection Model 2: During Handover, $T_T$ is isolated from $T_S$ , $T_A$ is one-way connected to $T_T$** + +![Network model diagram for Connection Model 3 showing a handover from BSS-2 to Target BSS via MGW-1 and MGW-2, controlled by MSC-1 S and MSC-2 S.](5801c19431e76330430e92a598cc7a16_img.jpg) + +The diagram illustrates a network architecture for a handover process. At the top, two Mobile Switching Center Server (MSC-S) units, labeled 'MSC-1 S' and 'MSC-2 S', are connected to each other by a horizontal green dashed line. Below each MSC-S is a Media Gateway (MGW), labeled 'MGW-1' and 'MGW-2', connected by vertical blue solid lines. MGW-1 has two ports labeled 'TT' and 'TA', while MGW-2 has two ports labeled 'T1' and 'T2'. These two MGWs are connected to each other by a horizontal blue dashed line. On the left side, there is a Base Station Server (BSS) labeled 'BSS-2' and 'Target BSS'. A red solid line connects the 'Target BSS' to MGW-1. A green dashed line connects the 'BSS-2' to MSC-1 S. A blue dashed line connects the 'Target BSS' to MGW-1. A green dashed line also connects the 'Target BSS' to MSC-2 S. The entire diagram is enclosed in a green dashed rectangular border. + +Network model diagram for Connection Model 3 showing a handover from BSS-2 to Target BSS via MGW-1 and MGW-2, controlled by MSC-1 S and MSC-2 S. + +**Connection Model 3: After Handover, LCLS is established and both call legs are in Target BSS (=BSS-2)** + +**Figure 8.2.2.1.5.1.1: Basic Intra-MSC UMTS to GSM Handover (network model)** + +## 8.2.2.1.5.2 Basic Sequence for Intra-MSC UMTS to GSM Handover that establishes Local Switching + +![Sequence diagram for Intra-MSC UMTS to GSM Handover that establishes Local Switching. The diagram shows the interaction between UE-1, RNC, MGW-1, MSC-1 S, TargetBSS, MSC-2 S, MGW-2, BSS-2, and UE-2. The process involves 12 steps, with some steps (4a, 4b, 4c) being conditional based on whether the call has been answered and if LCLS is permitted.](343e05a9fd8a8c8743428fa4ae6e2736_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant RNC + participant MGW-1 + participant MSC-1 S + participant TargetBSS + participant MSC-2 S + participant MGW-2 + participant BSS-2 + participant UE-2 + + Note left of MGW-1: MGW-1 + Note right of MGW-2: MGW-2 + + RNC->>MSC-1 S: 1. Relocation Required + MSC-1 S->>MGW-1: 2. Context C1: ADD Termination for Target BSS (TT) – bothway; MOD Ts Isolate + MSC-1 S->>TargetBSS: 3. HO Request (GCR, LCLS-Configuration, LCLS-Connection-Status-Control = "Connect") + TargetBSS->>MSC-1 S: 4. HO Request Ack (LCLS-BSS-Status: "Call not yet locally switched") + MSC-1 S->>RNC: 5. Relocation CMD + Note right of MSC-2 S: IF call has been answered and MSC permits LCLS to be connected then update the Connection Status in BSS + MSC-2 S->>BSS-2: 4a. LCLS_NOTIFICATION (LCLS-BSS-Status: "Call not yet locally switched") + MSC-2 S->>BSS-2: 4b. LCLS_CONNECT_CONTROL (LCLS-Connection-Status-Control = "Connect") + BSS-2->>MSC-2 S: 4c. LCLS_CONNECT_CONTROL_ACK (LCLS-BSS-Status: "Call not yet locally switched") + TargetBSS->>MSC-1 S: 6. HO Detect + TargetBSS->>MSC-1 S: 7. HO Complete (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") + MSC-1 S->>RNC: 8. Release Command + RNC->>MSC-1 S: 10. Release Complete + RNC->>MGW-1: 11. Context C1: SUB Ts + MGW-1->>MSC-1 S: 12. LCLS-Status-Update (LCLS-Status: "LCLS connected") + MSC-1 S->>MSC-2 S: 9. LCLS_NOTIFICATION (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") + +``` + +Sequence diagram for Intra-MSC UMTS to GSM Handover that establishes Local Switching. The diagram shows the interaction between UE-1, RNC, MGW-1, MSC-1 S, TargetBSS, MSC-2 S, MGW-2, BSS-2, and UE-2. The process involves 12 steps, with some steps (4a, 4b, 4c) being conditional based on whether the call has been answered and if LCLS is permitted. + +Figure 8.2.2.1.5.2.1: Intra-MSC UMTS to GSM Handover that establishes Local Switching + +1. Iu Relocation Required message is received from the RNC requesting an intra-MSC UMTS to GSM handover. The call is currently not locally switched. +2. The MSC-1 server requests the MGW-1 to reserve circuit or Connection Point towards the Target-BSS +3. The MSC-1 server sends the Handover Request message to the Target BSS with the GCR IE, the LCLS-Configuration IE and the LCLS-Connection-Status-Control IE indicating "connect" to through-connect the local call. +4. Target BSS performs call leg correlation with GCR to determine if another call leg is active with the same GCR. The Target BSS reports in Handover Request Acknowledge message that the local call was found but LCLS is not yet established. +- 4a. The BSS-2 notifies MSC-2 server the LCLS status is changed by sending the LCLS\_Notification message with the LCLS-BSS-Status IE set to "Call not yet locally switched". +- 4b. If the call has been answered and MSC-2 server permits LCLS to be connected, then the MSC-2 server sends to the BSS-2 the LCLS\_Connect\_Control message with the LCLS-Connection-Status-Control IE set to "connect". +- 4c. The BSS-2 returns the LCLS\_Connect\_Control\_ACK message with the LCLS-BSS-Status IE set to "Call not yet locally switched". + +5. The MSC-1 server triggers the Relocation Command message. +6. The UE-1 is detected at the target BSS. Then the Target BSS/BSS-2 can internally transmit the user plane data. +7. In the Handover Complete message the Target-BSS indicates to the MSC-1 server in the LCLS-BSS-Status IE that the call has been locally switched. +8. The MSC-1 server requests the old serving RNC to release the old call leg. +9. The Serving BSS-2 informs the MSC-2 server that the call has been locally switched via LCLS\_Notification message. +10. Releasing of the old call leg to the RNC is completed. +11. The termination Ts to the old RNC is removed from the Access MGW-1. +12. The MSC-1 server informs succeeding CN nodes that LCLS is connected. + +NOTE : When BICC is used as the call control protocol the APM message is sent. When SIP-I is used the INFO request with the encapsulated APM message is sent. + +## 8.2.2.2 Intra-MSC UMTS to GSM Handover that does not establish LCLS + +Intra-MSC UMTS to GSM Handover that does not establish LCLS follows the procedures in 8.2.2.1. The differences are: + +- in the step 7, the Target BSS informs MSC-1 server that the call is not locally switched in the Handover Complete message. +- steps 4a, 4b, 4c, 9 and step 12 are not triggered. + +## 8.2.3 Inter-MSC UMTS to GSM Handover + +### 8.2.3.1 Inter-MSC UMTS to GSM Handover that establishes Local Switching + +#### 8.2.3.1.1 General + +When LCLS is not established for a call and an inter-MSC UMTS to GSM handover occurs that makes the call local, the call can be locally switched in the Target BSS. The following clauses describe the additional requirements for inter- MSC handovers that establish LCLS. + +#### 8.2.3.1.2 MSC-1 / MGW-1 + +##### 8.2.3.1.2.1 Relocation Required + +##### 8.2.3.1.2.1 Relocation Required + +When MSC-1 Server receives the Relocation Required message from the serving RNC and determines that the call shall be handed over to the Target MSC Server, it shall send the GCR of the call, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE to the Target MSC Server in a MAP Prepare-Handover\_Request message. + +##### 8.2.3.1.2.2 Handover Request Acknowledge + +When MSC-1 Server receives the MAP Prepare\_Handover\_Response including Handover\_Request\_Acknowledgement message with a LCLS-BSS-Status IE the Anchor MSC-1 Server configures the bearer terminations in MGW-1 and sends the GCR IE, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE to the target MSC-Server. + +##### 8.2.3.1.2.3 Bearer establishment between MGW-1 and Target MGW + +The handling of the bearer establishment between MGW-1 and Target MGW is as described in sub-clause 6.1 for a Basic Mobile Originating Call. The MSC server shall also use the Change Flow Direction procedure to request the MGW-1 to set the Handover Device to the initial state. + +#### 8.2.3.1.2.4 MGW Flow Direction Control + +In accordance with the normal handover case the MGW-1 isolates the termination towards the Target MGW ( $T_2$ ) from the termination to the RNC( $T_S$ ) and configures the Anchor termination ( $T_1$ ) one-way DL towards the Target MGW termination ( $T_2$ ). Termination to the RNC ( $T_S$ ) is both-way connected to Anchor termination ( $T_1$ ) since it is also receiving UL user data from termination to the RNC ( $T_S$ ). + +#### 8.2.3.1.2.5 Relocation Command/Handover Detect + +The MSC-1 Server uses the Change Flow Direction procedure to requests the MGW-1 to set the Handover Device to intermediate state. + +#### 8.2.3.1.2.6 Handover Complete + +When the MSC-1 Server receives the Handover Complete message, it releases the related Iu-interface connection towards RNC. The MSC-1 Server also requests MGW-1 to set the Handover Device to its final state by removing the bearer termination towards the RNC. + +The MSC-1 server shall send to the adjacent call node the LCLS-Status-Update message with the LCLS-Status IE indicating that LCLS is established. + +### 8.2.3.1.3 Target MSC Server / Target MGW + +#### 8.2.3.1.3.1 Prepare Handover Request message and MGW selection + +The Target MSC server selects the Target MGW when it receives MAP Prepare Handover Request message. The Target MSC server sends the Handover Request message to the Target BSS as for the normal case but shall include the GCR IE, the LCLS-Configuration IE and the LCLS-Connection-Status-Control IE set to "Connect". + +#### 8.2.3.1.3.2 Handover Request Acknowledge + +If the Target BSS supports the LCLS feature it shall include the LCLS-BSS-Status IE in the Handover Request Acknowledge message in order to inform the Target MSC Server that the BSS supports the LCLS feature. The Target MSC Server sends the same information in the MAP Prepare Handover Response message to the MSC-1 Server. + +#### 8.2.3.1.3.3 Bearer establishment towards Target BSS + +When the Target MSC Server has selected the Target MGW it requests the Target MGW to seize a TDM circuit if AoTDM using the Reserve Circuit procedure, or an IP termination if AoIP using the reserve Connection Point procedure as for the normal handover procedure. The Target MSC Server sends the Handover Request message to the Target BSS containing the CIC for AoTDM or the IP addresses and UDP ports received from the target MGW if AoIP. + +#### 8.2.3.1.3.4 Bearer establishment between MGW-1 and Target MGW + +The handling of the bearer establishment between MGW-1 and Target MGW is as described for basic mobile terminating call in sub-clause 6.2. + +#### 8.2.3.1.3.5 Handover Complete + +When LCLS has been established during the handover procedure, the target BSS informs the target MSC-Server that the call has been locally switched in the Handover Complete message. + +NOTE: The target BSS will send LCLS-Notification message to the MSC at the other call leg indicating the call is locally switched. + +### 8.2.3.1.4 Example of Inter-MSC UMTS to GSM Handover that establishes Local Switching + +#### 8.2.3.1.4.1 Connection Model + +Figure 8.2.3.1.4.1.1 shows the network model for the Basic Inter-MSC UMTS to GSM handover when LCLS is established as a result of the handover. The dashed line in green represents call control signalling and the dashed line in blue represents the user plane connection path via the core network, which should be used if LCLS is not established or after LCLS is broken. The non-dotted lines represent the bearer carrying real user plane data. In MGW-1 the bearer termination $T_S$ is used for the bearer towards RNC, bearer termination $T_1$ is used for the bearer towards the succeeding/preceding MGW, that is MGW-2 and bearer termination $T_2$ is used towards the Target MGW. In MGW-2 the bearer termination $T_4$ is used for the bearer towards BSS-2 and bearer termination $T_3$ is used for the bearer towards + +MGW-1. In Target-MGW the bearer termination $T_T$ is used towards the Target-BSS and bearer termination $T_5$ is used towards MGW-1. + +In this example scenario the Handover Device is located in MGW-1 selected for the call establishment by the MSC-1 server, which controls the call and mobility management. + +- ━━━━ User plane link which transmits real user plane data within BSS and to UE +- ━━━━ User plane link which transmits real user plane data through the CN and to UE +- - - - User plane link path through CN, connected +- - - - Control plane link which transmits signalling + +![Diagram of Connection Model 1: Before Handover. The diagram shows a network topology. At the top, MSC-1 S, MSC-2 S, and Target MSC S are connected by green dashed control plane links. Below them, a chain of media gateways: RNC is connected to MGW-1 (terminations Ts, T1), which connects to MGW-2 (terminations T3, T4), which connects to Target MGW (terminations T5, TT). A black solid user plane link runs from RNC through MGW-1 and MGW-2 to Target MGW. Blue solid lines connect each MSC to its respective MGW. A Target BSS box is shown above the RNC/MGW-1 area, with green dashed lines indicating control signaling paths.](d6c377ae3e619ff992bd3647dbf43593_img.jpg) + +Diagram of Connection Model 1: Before Handover. The diagram shows a network topology. At the top, MSC-1 S, MSC-2 S, and Target MSC S are connected by green dashed control plane links. Below them, a chain of media gateways: RNC is connected to MGW-1 (terminations Ts, T1), which connects to MGW-2 (terminations T3, T4), which connects to Target MGW (terminations T5, TT). A black solid user plane link runs from RNC through MGW-1 and MGW-2 to Target MGW. Blue solid lines connect each MSC to its respective MGW. A Target BSS box is shown above the RNC/MGW-1 area, with green dashed lines indicating control signaling paths. + +**Connection Model 1: Before Handover** + +![Diagram of Connection Model 2: During Handover. This diagram updates Model 1. In MGW-1, a new termination T2 is introduced. The user plane link from RNC now enters MGW-1 at Ts. Inside MGW-1, T1 is shown with a one-way arrow pointing to T2, and T2 is isolated from Ts. The black user plane link continues from T2 to MGW-2 and then to Target MGW. Green dashed control plane links now extend to the Target BSS and BSS-2 boxes.](ff7977984f2552f326b2089d7595fff3_img.jpg) + +Diagram of Connection Model 2: During Handover. This diagram updates Model 1. In MGW-1, a new termination T2 is introduced. The user plane link from RNC now enters MGW-1 at Ts. Inside MGW-1, T1 is shown with a one-way arrow pointing to T2, and T2 is isolated from Ts. The black user plane link continues from T2 to MGW-2 and then to Target MGW. Green dashed control plane links now extend to the Target BSS and BSS-2 boxes. + +**Connection Model 2: During Handover, $T_2$ is isolated from $T_S$ , $T_1$ is one-way connected to $T_2$** + +![Network model diagram for Basic Inter-MSC UMTS to GSM Handover. It shows three Mobile Switching Centers (MSC-1 S, MSC-2 S, Target MSC S) connected to three Media Gateway (MGW) units (MGW-1, MGW-2, Target MGW). MGW-1 is connected to BSS-2 and Target BSS. MGW-2 is connected to MSC-2 S. Target MGW is connected to Target MSC S. Solid lines represent active call paths, while dashed lines represent potential or backup paths. A red box highlights the connection between BSS-2 and Target BSS within MGW-1.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) + +Network model diagram for Basic Inter-MSC UMTS to GSM Handover. It shows three Mobile Switching Centers (MSC-1 S, MSC-2 S, Target MSC S) connected to three Media Gateway (MGW) units (MGW-1, MGW-2, Target MGW). MGW-1 is connected to BSS-2 and Target BSS. MGW-2 is connected to MSC-2 S. Target MGW is connected to Target MSC S. Solid lines represent active call paths, while dashed lines represent potential or backup paths. A red box highlights the connection between BSS-2 and Target BSS within MGW-1. + +**Connection Model 3: After Handover, LCLS is established and both call legs are in Target BSS (=BSS-2)** + +**Figure 8.2.3.1.4.1.1: Basic Inter-MSC UMTS to GSM Handover (network model)** + +**8.2.3.1.4.2 Basic Sequence for Inter-MSC UMTS to GSM Handover that establishes Local Switching** + +Figures 8.2.3.1.4.2.1 and 8.2.3.1.4.2.2 show the message sequence example for the Basic Inter-MSC UMTS to GSM Handover shown in the corresponding network model Figure 8.2.3.1.4.1.1. The Handover Device is located in MGW-1 selected for the call establishment by the MSC-1 server, which controls the call and the mobility management. The description is based on 3GPP TS 23.009 [9], 3GPP TS 23.205 [2] and 3GPP TS 23.231 [3]. + +![Sequence diagram illustrating the initial phase of Inter-MSC UMTS to GSM Handover establishing Local Switching.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +UE-1 (oMS) is communicating with UE-2 (tMS) via the core network + +1. Relocation Required (RNC to MSC-1 S) +2. MAP Prepare-Handover Request (target LAC, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference) (MSC-1 S to Target MSC-S) +- 3a. Add request Access side $T_T$ reserve circuit, Connection Point (Target MSC-S to Target MGW) +- 3b. Add reply $T_T$ (Target MGW to Target MSC-S) +4. Handover Request (GCR, LCLS-Configuration, LCLS-Connection-Status-Control = "Connect") (Target MSC-S to Target BSS) +5. HO Request Ack (LCLS-BSS-Status: "Call not yet locally switched") (Target BSS to Target MSC-S) +- 5a. LCLS\_NOTIFICATION (LCLS-BSS-Status: "Call not yet locally switched") (Target BSS to MSC-2 S) +- IF call has been answered and MSC permits LCLS to be connected then update the Connection Status in BSS +- 5b. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "Connect") (MSC-2 S to BSS-2) +- 5c. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status: "Call not yet locally switched") (BSS-2 to MSC-2 S) +- 6a. MOD request $T_T$ , configure Connection Point, only AoIP (Target MSC-S to Target MGW) +- 6b. MOD reply $T_T$ (Target MGW to Target MSC-S) +7. MAP Prepare-Handover Response (Target MSC-S to MSC-1 S) +- 8a. TopDescr ({\*, $T_2$ , isolate}, { $T_1$ , $T_2$ oneway}) + ADD request( $T_2$ ) (MSC-1 S to MGW-1) +- 8b. TopDescr() + ADD reply ( $T_2$ ) (MGW-1 to MSC-1 S) +9. IAM (Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference), see NOTE 1, NOTE 2 (MSC-1 S to Target MSC-S) +- 10a. Add request Network side $T_5$ (Target MSC-S to Target MGW) +- 10b. Add reply $T_5$ (Target MGW to Target MSC-S) +11. APM (SC, SCL, LCLS-Negotiation Response, LCLS-Configuration-Preference), see NOTE 1 (Target MSC-S to MSC-1 S) + +Sequence diagram illustrating the initial phase of Inter-MSC UMTS to GSM Handover establishing Local Switching. + +**Figure 8.2.3.1.4.2.1: Initial phase of Inter-MSC UMTS to GSM Handover establishing Local Switching** + +1. Iu Relocation Required Request is received from RNC requesting an inter-MSC handover. The call is currently not locally switched. +2. The MSC-1 server determines that inter-MSC handover is required and sends the MAP Prepare-Handover Request message to target MSC-Server which includes LCLS Negotiation Request IE, the LCLS-Configuration-Preference IE and GCR IE. +- 3a, b. The Target-MSC-Server requests the target MGW to reserve circuit or Connection Point towards the Target-BSS +4. The Target MSC-Server sends Handover Request message to the Target BSS with GCR, the LCLS-Configuration IE and the LCLS-Connection-Status-Control IE indicating "connect" to through-connect the local call. +5. Target BSS performs call leg correlation with GCR to find if another call leg is active with same GCR. The BSS reports in Handover Request Acknowledge message that the local call was found but LCLS is not yet established. +- 5a. The BSS-2 notifies MSC-2 server the LCLS status is changed by sending the LCLS\_ Notification message with the LCLS-BSS-Status IE set to "Call not yet locally switched". + +- 5b. If the call has been answered and MSC-2 server permits LCLS to be connected, then the MSC-2 server sends to the BSS-2 the LCLS\_Connect\_Control message with the LCLS-Connection-Status-Control IE set to "connect". +- 5c. The BSS-2 returns the LCLS\_Connect\_Control\_ACK message with the LCLS-BSS-Status IE set to "Call not yet locally switched". +- 6a, b. (These signalling steps are only applicable to AoIP.) When the Target MSC-Server receives the BSSMAP Handover Request-Ack message, it sends the BSC-B IP address and UDP Port number to the MGW-B using the Configure RTP Connection Point procedure. +7. The Target MSC-Server sends the MAP Prepare Handover Response message to MSC-1 server. +- 8a, b. In accordance with normal handover the MSC-1 server requests MGW-1 to isolate the termination towards Target MGW (T2) from the termination to the Serving BSS-1 (TS) and to configure the Anchor termination (T1) one-way DL towards the Target MGW termination (T2). +9. MSC-Server 1 sends IAM (Initial Address Message) to Target MSC-Server including GCR, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. + +NOTE 1: Corresponding SIP-I signalling is specified in 3GPP TS 23.231 [3]. + +NOTE 2: The LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE in step 9 can be different from LCLS Negotiation Request IE and the LCLS-Configuration-Preference IE in step 2, because step 9 is BICC signalling and the LCLS Negotiation Request and the LCLS-Configuration-Preference IE values can be changed by intermediate MSC-Servers. + +10a, b. Target MSC-Server reserves bearer connection TS towards MGW-1. + +11. After Target MGW has replied with the bearer address and the binding reference (Step 10b), the Target MSC-Server returns APM with selected codec, the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. + +![Sequence diagram showing the completion phase of Inter-MSC UMTS to GSM Handover establishing Local Switching. The diagram involves 11 lifelines: UE-1, RNC, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target BSS, MSC-2 S, MGW-2, BSS-2, and UE-2. The sequence of messages is as follows: 12. ACM (see NOTE 1) from Target MSC-S to MSC-1 S; 13. Relocation CMD from MSC-1 S to RNC; 14. HO Detect from Target BSS to Target MSC-S; 15. MAP Process-AccessSignalling Request from Target MSC-S to MSC-1 S; 16a. TopDescr, change flow direction from MSC-1 S to MGW-1; 16b. TopDescr Response from MGW-1 to MSC-1 S; 17. HO Complete (LCLS-BSS-Status: 'Call is locally switched with requested LCLS configuration') from Target BSS to Target MSC-S; 18. LCLS-NOTIFICATION (LCLS-BSS-Status: 'Call is locally switched with requested LCLS configuration') from Target MSC-S to MSC-2 S; 19. MAP Send-End-Sig Request from Target MSC-S to MSC-1 S; 20. Answer from MSC-1 S to Target MSC-S; 21a. Release Command from MSC-1 S to RNC; 21b. Release Complete from RNC to MSC-1 S; 22a. SUB request, release Ts from MSC-1 S to MGW-1; 22b. SUB reply from MGW-1 to MSC-1 S; 23. LCLS Status Update (LCLS-Status = 'LCLS connected') from Target MSC-S to MSC-1 S (see NOTE 3); 24. LCLS Status Update (LCLS Status = 'LCLS connected') from MSC-1 S to MSC-2 S (see NOTE 3); 25. Local switching in BSS (indicated by a long red arrow from MSC-1 S to BSS-2).](2a476a0b3dbc3429436246db4784ff9f_img.jpg) + +Sequence diagram showing the completion phase of Inter-MSC UMTS to GSM Handover establishing Local Switching. The diagram involves 11 lifelines: UE-1, RNC, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target BSS, MSC-2 S, MGW-2, BSS-2, and UE-2. The sequence of messages is as follows: 12. ACM (see NOTE 1) from Target MSC-S to MSC-1 S; 13. Relocation CMD from MSC-1 S to RNC; 14. HO Detect from Target BSS to Target MSC-S; 15. MAP Process-AccessSignalling Request from Target MSC-S to MSC-1 S; 16a. TopDescr, change flow direction from MSC-1 S to MGW-1; 16b. TopDescr Response from MGW-1 to MSC-1 S; 17. HO Complete (LCLS-BSS-Status: 'Call is locally switched with requested LCLS configuration') from Target BSS to Target MSC-S; 18. LCLS-NOTIFICATION (LCLS-BSS-Status: 'Call is locally switched with requested LCLS configuration') from Target MSC-S to MSC-2 S; 19. MAP Send-End-Sig Request from Target MSC-S to MSC-1 S; 20. Answer from MSC-1 S to Target MSC-S; 21a. Release Command from MSC-1 S to RNC; 21b. Release Complete from RNC to MSC-1 S; 22a. SUB request, release Ts from MSC-1 S to MGW-1; 22b. SUB reply from MGW-1 to MSC-1 S; 23. LCLS Status Update (LCLS-Status = 'LCLS connected') from Target MSC-S to MSC-1 S (see NOTE 3); 24. LCLS Status Update (LCLS Status = 'LCLS connected') from MSC-1 S to MSC-2 S (see NOTE 3); 25. Local switching in BSS (indicated by a long red arrow from MSC-1 S to BSS-2). + +**Figure 8.2.3.1.4.2.2: Completion phase of Inter-MSC UMTS to GSM Handover establishing Local Switching** + +12. Target MSC-Server sends ACM (Address Complete Message). Target MSC-Server awaits the capturing of the UE-1 on the radio path when the ACM is sent and MSC-1 server initiates the handover execution when receiving ACM. + +13 - 18. When the local switching has been established during the handover procedure, the target BSS shall inform the target MSC-Server that the call has been locally switched in HANDOVER COMPLETE, and the target BSS shall also send a new message LCLS-Notification with LCLS-BSS-Status IE to inform the MSC-2 server that the local switching has been established. In steps 16a and 16b the MSC-1 server configures MGW-1 for the completion of the handover. + +19. A-HO-DETECT/COMPLETE when received, is included in the MAP-Send-End-Signal request and send back to the MSC-1 server. + +20. Target MSC-Server sends ANSWER when A-HO-DETECT/COMPLETE is received. + +21a, b. MSC-1 Server releases the call leg in RNC. + +22a, b. MSC-1 server releases the bearer termination towards RNC. + +23. Target MSC-Server informs the MSC-1 server about the LCLS Status. + +24. MSC-1 server (Anchor MSC-Server) sends LCLS-Status-Update message to the far end MSC-2 server. + +NOTE 3: When BICC is used as the call control protocol the APM message is sent. When SIP-I is used the INFO request with the encapsulated APM message is sent. + +25. Local switching is established in the BSS. + +### 8.2.3.2 Inter-MSC UMTS to GSM Handover that does not establish Local Switching + +Inter-MSC UMTS to GSM Handover that does not establish Local Switching follows the procedures in 8.2.3.1. The differences are: + +- in the step 17, the target BSS informs target MSC that the call is not locally switched in the Handover Complete. +- steps 5a, 5b, 5c 18, step 23, step 24 and step 25 are not triggered. + +## 8.3 GSM to UMTS + +### 8.3.1 Intra-MSC GSM to UMTS Relocation + +#### 8.3.1.1 General + +When a call is locally switched through the BSS and an intra-MSC GSM to UMTS handover occurs, the LCLS shall be broken and the user plane shall be connected via the core network. The Intra-MSC GSM to UMTS relocation procedure specified in 3GPP TS 23.205 [2] and 3GPP TS 23.231 [3] shall be followed. The following clauses describe the additional requirements for intra-MSC GSM to UMTS handovers of LCLS related calls. + +To this end the BSS which is in local switch which is serving the user equipment which is not moving to the RNC bicasts user data UL to the core network so that immediately the user equipment which is moving is attached to the RNC it can receive DL data from the core network. + +During a Locally Switched (intra-BSS) Connection when no bicasting occurs there is no data transmission through the core network. In this release the use plane is kept active and therefore does not need to be re-activated when the LCLS is broken due to GSM to UMTS handover out of LCLS. + +#### 8.3.1.2 Handover Required + +When the MSC server receives the Handover Required message from the serving BSS, it requests the MGW to provide a binding reference and a bearer address using the Prepare Bearer procedure. The MSC server shall use the Change Flow Direction procedure to request the MGW to set the Handover Device to the initial state, see sub-clause 8.4.1.1.3. + +#### 8.3.1.3 Iu Relocation Request Acknowledge + +Upon receipt of the Relocation Request Acknowledge message, the MSC Server shall send to the adjacent call node the LCLS-Status-Change-Request message to indicate "LCLS Disconnection-Preparation-for handover". + +When the far end MSC server receives the LCLS-Status-Change-Request message indicating LCLS Disconnection preparation-for-handover it shall send to the BSS the LCLS\_Connect\_Control message with the LCLS-Connection-Status-Control IE indicating "BicastatHandover". When the LCLS\_Connect\_Control acknowledge message is received from the BSS, the far end MSC server shall return the LCLS Status Change Request Acknowledge message indicating "LCLS Disconnection-Preparation-for-handover" and a Result code indicating LCLS Status Change Request accepted. + +#### 8.3.1.4 Handover Command/Iu Relocation Detect + +When the MSC server sends the Handover Command message or alternatively if it receives the Relocation Detect message, if the MSC server followed the MGW control procedures for a non-LCLS call and kept the Termination to the Serving BSS connected then it shall use the Change Flow Direction procedure to requests the MGW to set the Handover Device to intermediate state. However if the MSC server isolated $T_S$ and set $T_T$ to bothway through-connected then no MGW control procedure is required at this point. + +Upon receipt of the Relocation Detect message the MSC Server shall send to the adjacent call node the LCLS-Status-Change-Request message with the LCLS-Status-Change-Request IE set to "Indicate DL data after Handover". + +When the far end MSC server receives the LCLS-Status-Change-Request message with the LCLS-Status-Change-Request IE set to "Indicate DL data after Handover" it shall send to the BSS the LCLS\_Connect\_Control message with the LCLS-Connection-Status-Control IE indicating "DL Data at Handover" and after reception of the LCLS\_Connect\_Control acknowledge message from the BSS, return the LCLS-Status-Change-Request-Acknowledge message with "Indicate DL data after Handover" and a Result code indicating LCLS Status Change Request accepted. + +NOTE: this informs this call leg in the BSS that the other UE has left the BSS and has been detected in the new BSS and as such DL data from the CN is now coming from that UE. + +### 8.3.1.5 Iu Relocation Complete + +When the MSC server receives the Iu Relocation Complete message, it releases the A-interface line towards the serving BSS. The MSC server also requests the MGW to set the Handover Device to its final state by removing the bearer termination ( $T_S$ ) towards the serving BSS. + +The MSC server shall send to the adjacent call node the LCLS-Status-Update message with the LCLS-Status IE indicating the LCLS is disconnected. + +When the serving BSS receives Clear Command it shall release any local switch path. The serving BSS shall inform the far end MSC server that LCLS is broken with the LCLS-Notification message. + +NOTE: The LCLS\_Notification message does not need to be sent to the Anchor MSC Server since the Clear Complete message received from the serving BSS also means that LCLS is disconnected. + +### 8.3.1.6 Example + +#### 8.3.1.6.1 Connection Model + +Figure 8.3.1.6.1.1 shows the network model for Intra-MSC GSM to UMTS Handover, where the call leg pertinent to the UE-1 is handed over from the serving BSS-1 to the Target RNC. BSS-1 is the same as BSS-2 when LCLS is established for the call. The bearer termination $T_2$ is used for the bearer towards BSS-2, which is not affected by this handover. Bearer termination $T_S$ is used for the bearer towards BSS-1 and the bearer terminations $T_1$ and $T_A$ are used for the bearer towards the succeeding/preceding MGW. Bearer termination $T_T$ is for the bearer termination towards the Target RNC. The colours and line types used in the figure are defined differently from 3GPP TS 23.205 [2] to indicate LCLS specific issues. + +- User plane link which transmits real user plane data within the BSS and to UEs +- User plane link which transmits real user plane data through the CN and to UEs +- • • User plane path through the CN, connected +- - - Control plane link which transmits signalling + +![Diagram of Connection Model 1: The call is locally switched. It shows UE-1 and UE-2 connected to BSS-1 and BSS-2. BSS-1 is connected to MSC-S-1, which is connected to MGW-1. MGW-1 is connected to MGW-2, which is connected to MSC-S-2. MSC-S-2 is connected to BSS-2. The diagram illustrates the user plane and control plane paths for a call between UE-1 and UE-2, showing the local switching path within the BSS and the path through the CN.](1018d0db7bb02c169f646cb9cc244dc6_img.jpg) + +The diagram illustrates the network architecture for Intra-MSC GSM to UMTS Handover. On the left, UE-1 and UE-2 are connected to BSS-1 and BSS-2. BSS-1 is connected to MSC-S-1, which is connected to MGW-1. MGW-1 is connected to MGW-2, which is connected to MSC-S-2. MSC-S-2 is connected to BSS-2. The diagram shows the user plane (solid lines) and control plane (dashed lines) paths. The user plane path for UE-1 goes from UE-1 to BSS-1, then through MSC-S-1, MGW-1, MGW-2, MSC-S-2, and BSS-2 to UE-2. The control plane path goes from UE-1 to BSS-1, then through MSC-S-1, MGW-1, MGW-2, MSC-S-2, and BSS-2 to UE-2. The diagram also shows the 'Non-LCLS User Plane' and the 'Control Signalling' paths. The 'Before Handover' state is indicated at the bottom left. + +Diagram of Connection Model 1: The call is locally switched. It shows UE-1 and UE-2 connected to BSS-1 and BSS-2. BSS-1 is connected to MSC-S-1, which is connected to MGW-1. MGW-1 is connected to MGW-2, which is connected to MSC-S-2. MSC-S-2 is connected to BSS-2. The diagram illustrates the user plane and control plane paths for a call between UE-1 and UE-2, showing the local switching path within the BSS and the path through the CN. + +Connection Model 1: The call is locally switched + +![Diagram of Connection Model 2 showing network components and data flow during handover. UE-1 and UE-2 are connected to BSS-1/BSS-2. Control signaling (green dashed lines) connects BSS, Target RNC, MSC-S-1, and MSC-S-2. User Plane Data (black dotted line) flows from MSC-S-1 through MGW-1 and MGW-2. Red arrows indicate data flow from BSS-1/BSS-2 towards the Target RNC path. MGW-1 shows internal switching between ports Ts, TA, and TT.](719ef0f734259484038b2434e5dc3f24_img.jpg) + +Control Signalling + +UE-2 + +BSS-1/ +BSS-2 + +UE-1 + +User Plane Data + +Target RNC + +MSC-S-1 + +MSC-S-2 + +MGW-1 + +MGW-2 + +During Handover + TS = Serving + TA = Anchor + TT = Target + +Diagram of Connection Model 2 showing network components and data flow during handover. UE-1 and UE-2 are connected to BSS-1/BSS-2. Control signaling (green dashed lines) connects BSS, Target RNC, MSC-S-1, and MSC-S-2. User Plane Data (black dotted line) flows from MSC-S-1 through MGW-1 and MGW-2. Red arrows indicate data flow from BSS-1/BSS-2 towards the Target RNC path. MGW-1 shows internal switching between ports Ts, TA, and TT. + +Connection Model 2: MGW-1 is both-way connected between TA and TT, TS is isolated; BSS-2 starts to bicast data UL + +![Diagram of Connection Model 3. Similar to Model 2, but UE-1 has moved and is now connected directly to the Target RNC. The User Plane Data path (black dotted line) now goes through the Target RNC to MGW-1. Red arrows show data flow from BSS-2 towards the Target RNC path. MGW-1 continues to show internal switching between Ts, TA, and TT.](b63f41ca262d8ce9ef8affb62607f32b_img.jpg) + +Control Signalling + +UE-2 + +BSS-1/ +BSS-2 + +UE-1 + +User Plane Data + +Target RNC + +MSC-S-1 + +MSC-S-2 + +MGW-1 + +MGW-2 + +During Handover + TS = Serving + TA = Anchor + TT = Target + +Diagram of Connection Model 3. Similar to Model 2, but UE-1 has moved and is now connected directly to the Target RNC. The User Plane Data path (black dotted line) now goes through the Target RNC to MGW-1. Red arrows show data flow from BSS-2 towards the Target RNC path. MGW-1 continues to show internal switching between Ts, TA, and TT. + +Connection Model 3: UE has moved to Target RNC but Iu Relocation Detect has not yet been received by MSC-S-1 + +![Network model diagram for Intra-MSC GSM to UMTS Handover. It shows UE-2 connected to BSS-1/BSS-2, and UE-1 connected to Target RNC. Control signaling (dashed green lines) flows from the Target RNC and BSS-1/BSS-2 to MSC-S-1 and MSC-S-2. User plane data (solid black line) flows from the Target RNC through MGW-1 and MGW-2 to BSS-1/BSS-2. A legend indicates TA = Anchor and TT = Target.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) + +Control Signalling + +UE-2 + +BSS-1/BSS-2 + +UE-1 + +Target RNC + +MSC-S-1 + +MSC-S-2 + +User Plane Data + +MGW-1 + +MGW-2 + +TT TA + +T1 T2 + +After Handover + TA = Anchor + TT = Target + +Network model diagram for Intra-MSC GSM to UMTS Handover. It shows UE-2 connected to BSS-1/BSS-2, and UE-1 connected to Target RNC. Control signaling (dashed green lines) flows from the Target RNC and BSS-1/BSS-2 to MSC-S-1 and MSC-S-2. User plane data (solid black line) flows from the Target RNC through MGW-1 and MGW-2 to BSS-1/BSS-2. A legend indicates TA = Anchor and TT = Target. + +**Connection Model 4: LCLS is released in BSS-2, old serving Termination Ts is removed** + +**Figure 8.3.1.6.1.1: Network model for Intra-MSC GSM to UMTS Handover that breaks LCLS** + +### 8.3.1.6.2 Basic Sequence for GSM to UMTS Handover that breaks Local Switching + +![Sequence diagram for GSM to UMTS handover that breaks Local Switching. The diagram shows the interaction between UE-1, BSS-1, MGW-1, MSC-S-1, Target RNC, MSC-S-2, MGW-2, BSS-2, and UE-2. It details the signaling steps for a handover that breaks local switching, including context updates, relocation requests, and status changes.](f97535cdaa4fe017f4659512f4f78028_img.jpg) + +The sequence diagram illustrates the signaling flow for a GSM to UMTS handover that breaks local switching. The participants involved are UE-1, BSS-1, MGW-1, MSC-S-1, Target RNC, MSC-S-2, MGW-2, BSS-2, and UE-2. + +**Locally Switched User Plane in the BSS:** This phase is indicated by a red double-headed arrow spanning from UE-1 to BSS-2, passing through MGW-1 and MGW-2. + +**Sequence of Messages:** + +- 1. HO Required:** BSS-1 sends a message to MSC-S-1. +- 2. Context C1: ADD Termination for Target RNC (TT) – bothway; MOD Ts Isolate:** MSC-S-1 sends a message to MGW-1. +- 3. Iu Relocation Request:** MSC-S-1 sends a message to Target RNC. +- 4. Iu Relocation Request Ack:** Target RNC sends a message to MSC-S-1. +- 5. LCLS-Status-Change-Request (LCLS-Status-Change: "LCLS-disconnection-preparationForHandover"):** MSC-S-1 sends a message to MSC-S-2. +- 6. HO CMD:** MSC-S-1 sends a message to BSS-1. +- 5a. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "BicastaHandover"):** MSC-S-2 sends a message to BSS-2. +- 5b. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration"):** BSS-2 sends a message to MSC-S-2. +- 7. LCLS Status Change Request Acknowledge (LCLS-Status-Change = "LCLS-Disconnection-PreparationForHandover", Result Code="Status Change Req Accepted"):** MSC-S-2 sends a message to MSC-S-1. +- 8. Iu Relocation Detect:** Target RNC sends a message to MSC-S-1. +- 8a. LCLS-Status-Change-Request (LCLS-Status-Change: "IndicateDLdataAfterHandover"):** MSC-S-1 sends a message to MSC-S-2. +- 8b. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "DLDataAtHandover"):** MSC-S-2 sends a message to BSS-2. +- 9. Iu Relocation Complete:** Target RNC sends a message to MSC-S-1. +- 8c. LCLS\_CONNECT\_CONTROL Ack (LCLS-BSS-Status "the call is locally switched with requested LCLS configuration"):** BSS-2 sends a message to MSC-S-2. +- 8d. LCLS-Status-Change-Request Ack (LCLS-Status-Change: "IndicateDLdataAfterHandover", Result Code="Status Change Req Accepted"):** MSC-S-2 sends a message to MSC-S-1. +- 10. Clear Command:** MSC-S-1 sends a message to BSS-1. A box labeled "Break local switching" is associated with this step. +- 11. LCLS\_NOTIFICATION (LCLS-BSS-Status = "Call is no longer locally switched"):** BSS-2 sends a message to MSC-S-2. +- 12. Clear Complete:** BSS-1 sends a message to MSC-S-1. +- 13. Context C1: SUB Ts:** MSC-S-1 sends a message to MGW-1. +- 14. LCLS-Status-Update (LCLS-Status: "LCLS not connected"):** MGW-1 sends a message to MSC-S-2. + +**Normally Switched User Plane:** This phase is indicated by a black double-headed arrow spanning from UE-1 to UE-2, passing through MGW-1, Target RNC, and MGW-2. + +Sequence diagram for GSM to UMTS handover that breaks Local Switching. The diagram shows the interaction between UE-1, BSS-1, MGW-1, MSC-S-1, Target RNC, MSC-S-2, MGW-2, BSS-2, and UE-2. It details the signaling steps for a handover that breaks local switching, including context updates, relocation requests, and status changes. + +Figure 8.3.1.6.2.1 shows the signalling flow for GSM to UMTS handover that breaks Local Switching. + +![Sequence diagram for Intra-MSC GSM to UMTS Handover that terminates Local Switching. The diagram shows the interaction between UE-1, BSS-1, MGW-1, MSC-S-1, Target RNC, MSC-S-2, MGW-2, BSS-2, and UE-2. It details the steps for a handover that ends local switching, including context updates, relocation requests, and status notifications.](2f587210e4f97c32758c5972e2e83d20_img.jpg) + +The diagram illustrates the signaling sequence for an intra-MSC GSM to UMTS handover that terminates local switching. The participants are UE-1, BSS-1, MGW-1, MSC-S-1, Target RNC, MSC-S-2, MGW-2, BSS-2, and UE-2. A red double-headed arrow at the top indicates the 'Locally Switched User Plane in the BSS' between BSS-1 and BSS-2. A black double-headed arrow at the bottom indicates the 'Normally Switched User Plane' between UE-1 and UE-2. The sequence of messages is as follows: + +1. HO Required: BSS-1 to MSC-S-1 +2. Context C1: ADD Termination for Target RNC (TT) – bothway; MOD TS Isolate: MSC-S-1 to MGW-1 +3. Iu Relocation Request: MSC-S-1 to Target RNC +4. Iu Relocation Request Ack: Target RNC to MSC-S-1 +5. LCLS-Status-Change-Request (LCLS-Status-Change: "LCLS-disconnection-preparationForHandover"): MSC-S-1 to MSC-S-2 +- 5a. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "BicastaHandover"): MSC-S-2 to BSS-2 +- 5b. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration"): BSS-2 to MSC-S-2 +6. HO CMD: MSC-S-1 to BSS-1 +7. LCLS Status Change Request Acknowledge (LCLS-Status-Change = "LCLS-Disconnection-PreparationForHandover", Result Code="Status Change Req Accepted"): MSC-S-2 to MSC-S-1 +8. Iu Relocation Detect: Target RNC to MSC-S-1 +9. Iu Relocation Complete: Target RNC to MSC-S-1 +10. Clear Command: MSC-S-1 to BSS-1 +11. LCLS\_NOTIFICATION (LCLS-BSS-Status = "Call is no longer locally switched"): MSC-S-2 to BSS-2 +12. Clear Complete: BSS-1 to MSC-S-1 +13. Context C1: SUB TS: MSC-S-1 to MGW-1 +14. LCLS-Status-Update (LCLS-Status: "LCLS not connected"): MSC-S-1 to MSC-S-2 + +A red box labeled 'Break local switching' is positioned near the bottom left, indicating the point where the local switching is terminated. + +Sequence diagram for Intra-MSC GSM to UMTS Handover that terminates Local Switching. The diagram shows the interaction between UE-1, BSS-1, MGW-1, MSC-S-1, Target RNC, MSC-S-2, MGW-2, BSS-2, and UE-2. It details the steps for a handover that ends local switching, including context updates, relocation requests, and status notifications. + +**Figure 8.3.1.6.2.1: Intra-MSC GSM to UMTS Handover that terminates Local Switching** + +1. The Handover Required message is received from BSS-1 requesting an intra-MSC GSM to UMTS handover. The call is currently locally switched so the MSC-1 server can know that the GSM to UMTS handover at one end will break local switch (the local switch is not broken in the serving BSS (BSS-1) until the UE-1 has moved from BSS-1 and the MSC-1 server has sent the Clear Command message to the BSS-1). +2. In this example the Anchor MSC-1 server requests from its MGW-1 the seizure of the bearer termination TT towards the Target RNC and through-connects it bothway to TA. Additionally it isolates the old serving Termination TS. This makes the GSM to UMTS handover more efficient than current non-LCLS GSM to UMTS handovers as immediately when the UE-1 is handed over to the target RNC it will be able to send UL user data to the UE-2. + +NOTE 1: This flow shows the termination to the Target RNC as always connected bothway. This is a change to the existing call handling which would normally connect the termination as one-way and then change to bothway after receiving the Iu Relocation Detect message. However the termination does not need to be connected one-way and will in fact make the break in speech worse since UL data cannot be sent from the UE-1 until the MGW topology is modified, also it saves the additional intermediate H.248 modification step. + +3. Anchor MSC-1 server sends the Iu Relocation Request message to the target RNC. +4. The target RNC returns the Iu Relocation Request Acknowledge message. + +5. Anchor MSC-1 server shall send the LCLS-Status-Change-Request message to the succeeding MSC server asking it to prepare for LCLS disconnection due to handover to trigger the far end MSC-2 server to send the LCLS-Connect-Control message to BSS-2. + +NOTE 2: When BICC is used as the call control protocol the APM message is sent. When SIP-I is used the INFO request with the encapsulated APM message is sent. + +- 5a. The far end MSC-2 server requests the BSS-2 to start sending data UL with the LCLS\_Connect\_Control message and the LCLS-Connection-Status-Control IE indicating "BicastAtHandover", see Figure 8.3.1.6.1.1 Connection Model 2. This triggers the BSS-1 to bicast the user plane data in the same way as the Access MGW-1 would be doing in a non-LCLS inter-BSS handover. At this point the BSS-1 shall send any DL data it receives directly to the served UE. Since the BSS-1 cannot receive DL data at the same time as it receives local data ( $T_S$ is isolated) this will minimise the break in user plane data even more than for existing non-LCLS handover. + +NOTE 3: The Serving BSS-1 shall forward the user plane data from the UE-1 to the UE-2 while the UE-1 is served by the BSS-1. The UL user plane data are bi-cast to both MGW2 and local path by the BSS-2. The MGW-2 transmits the user plane data to the MGW-1, and the MGW-1 will transmit the user plane data to the target RNC. When the UE-1 leaves the serving BSS-1 and begins sending UL data from the Target RNC, that data will then be received via the A-interface leg at the serving BSS-2. + +- 5b. BSS-2 sends the LCLS\_Connect\_Control\_Ack message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration". +6. Anchor MSC-1 server triggers the Handover Command message. When the UE-1 moves to the Target RNC in this example it can immediately send UL data through the CN to the UE-2 and also can receive DL data from the UE-2 via the CN since the MGW-1 topology for $T_A$ , $T_T$ is already bothway connected. This is a change from the current non-LCLS solution but is more efficient since the non-LCLS solution needs to set this to one-way DL only until it receives Iu Relocation Detect message. +7. MSC-2 Server sends LCLS-Status-Change-Request-Acknowledgement. +8. UE-1 is detected at the target RNC. BSS-1/BSS-2 may continue to send the user plane data locally until the Clear Command message is received. +- 8a. The MSC-1 Server sends LCLS-Status-Change-Request to indicate that UE-1 has been detected in the target BSS and user data is now being sent through the CN and DL to the distant UE-2. +- 8b. The MSC-2 Server signals to the BSS-2 that DL data received from the CN is now real user data coming from the UE-1. +- 8c. The BSS-2 sends the LCLS\_Connect\_Control\_Ack message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration". +- 8d. Acknowledgement back through the CN that the indication for DL data after Handover Detect has been delivered. +9. When the MSC-1 Server receives the Iu Relocation Complete message MSC-1 Server knows that the call is not possible to be locally switched. +10. MSC-1 server requests the old serving BSS-1 to clear the old call leg. BSS-1 stops sending locally the user data from UE-1, LCLS is broken. +11. Serving BSS-2 informs the MSC-2 server that LCLS is broken via LCLS\_Notification message. +12. Clearing of the old call leg to the Serving BSS-1 is completed. +13. The termination $T_S$ to the old serving BSS-1 is removed from the Access MGW-1. +14. Anchor MSC-1 server informs succeeding CN nodes that LCLS is disconnected. + +NOTE 4: When BICC is used as the call control protocol the APM message is sent. When SIP-I is used the INFO request with the encapsulated APM message is sent. + +## 8.3.2 Inter-MSC GSM to UMTS Relocation + +### 8.3.2.1 General + +When a call is locally switched through the BSS and an inter-MSC GSM to UMTS handover occurs the LCLS shall be broken and the user plane shall be connected through the core network. The Inter-MSC GSM to UMTS handover procedures specified in 3GPP TS 23.009 [9], 3GPP TS 23.205 [2] and 3GPP TS 23.231 [3] shall be followed. The following clauses describe the additional requirements for inter-MSC GSM to UMTS handovers of LCLS related calls. + +### 8.3.2.2 MSC-1 / MGW-1 + +#### 8.3.2.2.1 Handover Required + +When MSC-1 Server receives the Handover Required message from the serving BSS and determines that the call shall be handed over to the Target MSC Server, it shall send the GCR of the call, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE to the Target MSC Server in a MAP Prepare-Handover\_Request message. + +#### 8.3.2.2.2 Iu Relocation Request Acknowledge + +Upon receipt of the MAP Prepare-Handover-Response including Iu Relocation Ack message, the MSC-1 Server shall send to the adjacent call node the LCLS-Status-Change-Request message to indicate "LCLS Disconnection-Preparation-for handover". + +If the far end MSC server receives the LCLS-Status-Change-Request message indicating LCLS Disconnection preparation-for-handover it shall send to the BSS the LCLS\_Connect\_Control message with the LCLS-Connection-Status-Control IE indicating "BicastatHandover". When the LCLS\_Connect\_Control acknowledge message is received from the BSS, the far end MSC server shall return the LCLS Status Change Request Acknowledge message indicating "LCLS Disconnection-Preparation-for-handover" and a Result code indicating LCLS Status Change Request accepted. + +#### 8.3.2.2.3 Bearer establishment between MGW-1 and Target MGW + +The handling of the bearer establishment between MGW-1 and Target MGW is as described in sub-clause 6.1 for a Basic Mobile Originating Call. The MSC server shall also use the Change Flow Direction procedure to request the MGW-1 to set the Handover Device to the initial state. + +#### 8.3.2.2.4 MGW Flow Direction Control + +The MSC Server may perform the MGW Flow Direction Control for GSM to UMTS Relocation as described in sub-clause 8.4.2.1.2.4. + +#### 8.3.2.2.5 Handover Command/Iu Relocation Detect + +When the MSC-1 server sends the Handover Command message or alternatively, if it receives the Iu Relocation detect message inside a MAP Process-Access-Signalling request, the MSC-1 server shall follow the procedures described in sub-clause 8.4.2.1.2.5. + +#### 8.3.2.2.6 Iu Relocation Complete + +When the MSC-1 server receives the Iu Relocation Complete message inside a MAP Send-End-Signalling Request and an ANSWER message including the LCLS status set to LCLS disconnected, it releases the A-interface line towards the serving BSS. The MSC-1 server also requests the MGW-1 to set the Handover Device to its final state by removing the bearer termination (Ts) towards the serving BSS. + +The MSC-1 server shall send to the adjacent call node the LCLS-Status-Update message with the LCLS-Status IE indicating the LCLS is disconnected. + +When the serving BSS receives Clear Command it shall release any local switch path. The serving BSS shall inform the far end MSC server that LCLS is broken with the LCLS-Notification message. + +NOTE: The LCLS\_Notification message does not need to be sent to the Anchor MSC Server since the Clear Complete message received from the serving BSS also means LCLS is disconnected. + +### 8.3.2.3 Target MSC Server / Target MGW + +#### 8.3.2.3.1 Prepare Handover Request message and MGW selection + +The Target MSC server selects the Target MGW when it receives Prepare Handover Request message. The Target MSC server sends the Iu Relocation Request message to the Target RNC as for the normal case. + +#### 8.3.2.3.2 Bearer establishment towards Target RNC + +The procedure specified in 3GPP TS 23.205 [2] sub-clause 8.3.2.2 shall be used. + +#### 8.3.2.3.3 Bearer establishment between MGW-1 and Target MGW + +The handling of the bearer establishment between MGW-1 and Target MGW is as described for basic mobile terminating call in sub-clause 6.2. + +### 8.3.2.4 Example of Inter-MSC GSM to UMTS Relocation + +#### 8.3.2.4.1 Connection Model + +Figure 8.4.2.1.4.1.1 shows the network model for the Inter-MSC GSM to GSM Handover, where call leg UE-1 is handed over from BSS-1 to the Target RNC. BSS-1 is the same as BSS-2 when LCLS is established for the call. The BSS-1 is served by the MSC-Server 1, the Target RNC is served by the Target MSC-Server, and MSC-Server 1 is not the same as Target MSC-Server. The bearer termination T2 in MGW-2 is used for the bearer towards BSS-2, which is not affected by this handover. Bearer termination TS in MGW-1 is used for the bearer towards BSS-1 and the bearer terminations TA and T3 in MGW-1, T1 in MGW-2 and T4 in Target-MGW are used for the bearer towards the succeeding/preceding MGW. Bearer termination TT in Target-MGW is for the bearer termination towards the Target RNC. + +- User plane link which transmits real user plane data within BSS and to UE +- User plane link which transmits real user plane data through the CN and to UE +- - - User plane link path through CN, connected +- - - User plane uplink path through CN from Target BSS, connected +- - - Control plane link which transmits signalling + +![Diagram of Connection Model 1: Before handover, Local Switching is established. It shows a network architecture with two MSC Servers (MSC-1 S and MSC-2 S) connected to two Media Gateways (MGW-1 and MGW-2). MGW-1 is connected to a Base Station (BSS-1/BSS-2). A User Equipment (UE) is connected to the BSS. The diagram illustrates various user plane and control plane links between these components. MSC-1 S is connected to MGW-1, and MSC-2 S is connected to MGW-2. MGW-1 and MGW-2 are interconnected. BSS-1/BSS-2 is connected to MGW-1. UE is connected to BSS-1/BSS-2. A red solid line represents the user plane link within the BSS. A black solid line represents the user plane link through the CN. A blue dashed line represents the user plane link path through the CN. A green dashed line represents the control plane link.](5dadcfbae18c4b3f91ea3a5e84d0a47a_img.jpg) + +Diagram of Connection Model 1: Before handover, Local Switching is established. It shows a network architecture with two MSC Servers (MSC-1 S and MSC-2 S) connected to two Media Gateways (MGW-1 and MGW-2). MGW-1 is connected to a Base Station (BSS-1/BSS-2). A User Equipment (UE) is connected to the BSS. The diagram illustrates various user plane and control plane links between these components. MSC-1 S is connected to MGW-1, and MSC-2 S is connected to MGW-2. MGW-1 and MGW-2 are interconnected. BSS-1/BSS-2 is connected to MGW-1. UE is connected to BSS-1/BSS-2. A red solid line represents the user plane link within the BSS. A black solid line represents the user plane link through the CN. A blue dashed line represents the user plane link path through the CN. A green dashed line represents the control plane link. + +Connection Model 1: Before handover, Local Switching is established + +![Diagram of Connection Model 2 showing network components and their connections before an MSC triggers a handover command.](c07e21a8d65991db04263322f859c94f_img.jpg) + +This diagram illustrates Connection Model 2. It features three Mobile Switching Centers (MSCs): MSC-1 S, MSC-2 S, and Target MSC-S. MSC-1 S and MSC-2 S are connected to MGW-1 and MGW-2 respectively. MGW-1 has interfaces TS, TA, and T3. MGW-2 has interfaces T1 and T2. A dashed blue line connects MGW-1 and MGW-2. Target MSC-S is connected to a Target MGW, which has interfaces T4 and TT. A dashed black line connects MGW-2 and the Target MGW. On the left, BSS-2/BSS-1 is connected to MSC-1 S, and a Target RNC is shown below it. A dashed green line outlines the network area. A red line highlights a specific connection path within the BSS-2/BSS-1 unit. + +Diagram of Connection Model 2 showing network components and their connections before an MSC triggers a handover command. + +Connection Model 2: Before MSC triggers HO command to the BSS, T3 is isolated from TS, TA is one-way connected to T3 and TS is both-way connected to TA + +![Diagram of Connection Model 3 showing network components and their connections when UE-1 is not yet detected in the Target RNC.](9f51a76cae7309a296cbc6997941eb3f_img.jpg) + +This diagram illustrates Connection Model 3. It shows the same network components as Model 2 but with different connection states. A solid black line indicates a new user plane path: from BSS-2/BSS-1, through MSC-1 S, to MGW-1 (TS), then to MGW-2 (T1), then to the Target MGW (T4), and finally to the Target RNC. A dashed blue line connects MGW-1 (TA) and MGW-2 (T2). A dashed green line outlines the network area. A red line highlights a connection path within the BSS-2/BSS-1 unit. + +Diagram of Connection Model 3 showing network components and their connections when UE-1 is not yet detected in the Target RNC. + +Connection Model 3: UE-1 not yet detected in Target RNC, BSS-2 bicasts user plane data UL + +![Diagram of Connection Model 4 showing network architecture with MSC-1 S, MSC-2 S, Target MSC-S, BSS-2/BSS-1, Target RNC, MGW-1, MGW-2, and Target MGW. It includes various interfaces like TS, TA, T1, T2, T3, T4, and TT. A green dashed line outlines the core network area.](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +Diagram of Connection Model 4 showing network architecture with MSC-1 S, MSC-2 S, Target MSC-S, BSS-2/BSS-1, Target RNC, MGW-1, MGW-2, and Target MGW. It includes various interfaces like TS, TA, T1, T2, T3, T4, and TT. A green dashed line outlines the core network area. + +Connection Model 4: UE-1 connected to Target RNC but Target MSC-S has not received HO Detect + +![Diagram of Connection Model 5 showing network architecture similar to Model 4 but with a different user plane routing configuration where MGW-1 reroutes traffic. The green dashed line outlines the core network area.](64323b705244afc70bf77babdacb6ce5_img.jpg) + +Diagram of Connection Model 5 showing network architecture similar to Model 4 but with a different user plane routing configuration where MGW-1 reroutes traffic. The green dashed line outlines the core network area. + +Connection Model 5: MSC-1 instructed MGW-1 to reroute the user plane, TA is both-way connected to T3 + +![Diagram of Connection Model 6: Handover completed, Ts termination was removed. The diagram shows a network architecture with MSC-1 S, MSC-2 S, and Target MSC-S at the top. Below them are BSS-2, Target RNC, MGW-1, MGW-2, and Target MGW. Solid black lines represent the user plane path, while dashed green lines represent the signaling path. MGW-1 and MGW-2 have internal ports labeled T3, TA, T1, and T2. Target MGW has ports labeled T4 and T7.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +Diagram of Connection Model 6: Handover completed, Ts termination was removed. The diagram shows a network architecture with MSC-1 S, MSC-2 S, and Target MSC-S at the top. Below them are BSS-2, Target RNC, MGW-1, MGW-2, and Target MGW. Solid black lines represent the user plane path, while dashed green lines represent the signaling path. MGW-1 and MGW-2 have internal ports labeled T3, TA, T1, and T2. Target MGW has ports labeled T4 and T7. + +**Connection Model 6: Handover completed, Ts termination was removed** + +**Figure 8.3.2.4.1.1: Inter-MSC GSM to UMTS Relocation Connection Model when user plane active** + +**8.3.2.4.2 Basic Sequence for Inter-MSC handover that breaks Local Switching** + +Figures 8.3.2.4.2.1 and 8.3.2.4.2.2 show the message sequence example for the basic Inter-MSC GSM to GSM Handover shown in the corresponding network model Figure 8.3.2.4.1.1. The Handover Device is located in the MGW-1 selected for the call establishment by the MSC-1 Server, which controls the call and the mobility management. The description is based on 3GPP TS 23.009 [9], 3GPP TS 23.205 [2] and 3GPP TS 23.231 [3]. + +![Sequence diagram for Inter-MSC GSM to UMTS Relocation that breaks Local Switching when user plane active, initial phase. The diagram shows the interaction between UE-1, BSS-1, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target RNC, MSC-2 S, MGW-2, BSS-2, and UE-2. A red double-headed arrow at the top indicates that oMS is communicating with tMS via a locally switched path in the BSS. The sequence of messages is: 1. HO Required (target LAC) from BSS-1 to MSC-1 S; 2. MAP Prepare-Handover Request from MSC-1 S to Target MSC-S; 3a. Add request Access side T_T from Target MSC-S to Target MGW; 3b. Add reply T_T from Target MGW to Target MSC-S; 4. Iu Relocation Request from Target MSC-S to Target RNC; 5. Iu Relocation Ack from Target RNC to Target MSC-S; 6. MAP Prepare-Handover Response from Target MSC-S to MSC-1 S; 7. LCLS-Status-Change-Request from MSC-1 S to MSC-2 S; 8a. LCLS_CONNECT_CONTROL from MSC-2 S to BSS-2; 8b. LCLS_CONNECT_CONTROL_ACK from BSS-2 to MSC-2 S; 9a. TopDescr + ADD.request(T3) from MSC-1 S to MGW-1; 9b. TopDescr()+ADD.reply(T3) from MGW-1 to MSC-1 S; 10. LCLS Status Change Request Acknowledge from MSC-1 S to MSC-2 S; 11. IAM from MSC-1 S to Target MSC-S; 12a. Add request Network side T4 from Target MSC-S to Target MGW; 12b. Add reply T4 from Target MGW to Target MSC-S; 13. APM from Target MSC-S to MSC-1 S.](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) + +Sequence diagram for Inter-MSC GSM to UMTS Relocation that breaks Local Switching when user plane active, initial phase. The diagram shows the interaction between UE-1, BSS-1, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target RNC, MSC-2 S, MGW-2, BSS-2, and UE-2. A red double-headed arrow at the top indicates that oMS is communicating with tMS via a locally switched path in the BSS. The sequence of messages is: 1. HO Required (target LAC) from BSS-1 to MSC-1 S; 2. MAP Prepare-Handover Request from MSC-1 S to Target MSC-S; 3a. Add request Access side T\_T from Target MSC-S to Target MGW; 3b. Add reply T\_T from Target MGW to Target MSC-S; 4. Iu Relocation Request from Target MSC-S to Target RNC; 5. Iu Relocation Ack from Target RNC to Target MSC-S; 6. MAP Prepare-Handover Response from Target MSC-S to MSC-1 S; 7. LCLS-Status-Change-Request from MSC-1 S to MSC-2 S; 8a. LCLS\_CONNECT\_CONTROL from MSC-2 S to BSS-2; 8b. LCLS\_CONNECT\_CONTROL\_ACK from BSS-2 to MSC-2 S; 9a. TopDescr + ADD.request(T3) from MSC-1 S to MGW-1; 9b. TopDescr()+ADD.reply(T3) from MGW-1 to MSC-1 S; 10. LCLS Status Change Request Acknowledge from MSC-1 S to MSC-2 S; 11. IAM from MSC-1 S to Target MSC-S; 12a. Add request Network side T4 from Target MSC-S to Target MGW; 12b. Add reply T4 from Target MGW to Target MSC-S; 13. APM from Target MSC-S to MSC-1 S. + +**Figure 8.3.2.4.2.1: Inter-MSC GSM to UMTS Relocation that breaks Local Switching when user plane active, initial phase** + +- The Handover Required message is received from BSS-1 requesting an inter-MSC GSM to UMTS handover. The call is currently locally switched and the MSC-1 server knows that the Inter-MSC GSM to UMTS relocation at one end will break LCLS (the local switch is not broken in the serving BSS (BSS-1) until UE-1 has moved out of the BSS-1 and the MSC-1 server sends the Clear Command message to BSS-1). +- The MSC-1 Server determines that inter-MSC handover is required and sends MAP-Prepare-Handover Request message to target MSC which includes GCR, the LCLS Negotiation Request IE and the LCLS-Configuration-Preference IE. +- a, b. The Target MSC-Server requests Target MGW to provide a binding reference and a bearer address using the Prepare Bearer procedure when reserving $T_T$ towards the Target RNC. +- The Target MSC-Server sends the Iu Relocation Request message to Target RNC. +- The Target RNC sends the Iu Relocation Acknowledge message to Target MSC-Server. +- The Target MSC-Server sends the Prepare Handover Response message to the MSC-1 server. +- The Anchor MSC-1 server may instruct the far end MSC-2 server to prepare for LCLS disconnection due to handover by sending the LCLS-Status-Change-Request message. (If the Anchor MSC-1 server does not + +instruct the MSC-2 server /BSS-2 to prepare for LCLS disconnection for handover, BSS-2 starts bicasting user plane data to the core network after receiving the Handover Command message in Step 15.) + +- 8a. The far end MSC-2 server requests BSS-2 to start sending data UL with the LCLS\_Connect\_Control message and the LCLS-Connection-Status-Control IE indicating "BicestatHandover", see Figure 8.3.2.4.1.1, Connection Model 3. This triggers the BSS-2 to bicast the user plane data in the same way as the Access MGW-1 would be doing in a non-LCLS inter-BSS handover. At this point the BSS-1 shall send any DL data it receives directly to the served UE. + +NOTE 1: The Serving BSS-1 shall forward the user plane data received locally from UE-1 to UE-2 while the UE-1 is served by the BSS-1. BSS-2 bicasts UL user plane data to both MGW2 and local path and MGW-2 transmits the user plane data to MGW-1 and MGW-1 transmits the user plane data to the Target RNC via the Target MGW. When the UE-1 leaves the serving BSS-1 and begins sending UL data to the Target RNC via the Target MGW, that data will then be received via the A-interface leg at the serving BSS-2. + +- 8b. The BSS-2 sends the LCLS\_Connect\_Control\_Ack message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration". + +- 9a, b. In accordance with normal Iu relocation in this example the MSC-1 server requests MGW-1 to isolate the termination towards Target MGW (T3) from the termination to the Serving BSS-1 (Ts) and to configure the Anchor termination (TA) one-way DL towards the Target MGW termination (T3). + +10. MSC-2 Server sends LCLS-Status-Change-Request-Acknowledge message. + +11. MSC-1 Server sends IAM (Initial Address Message) to Target MSC-Server including GCR, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. + +NOTE 2: Corresponding SIP-I signalling is specified in 3GPP TS 23.231 [3]. + +NOTE 3: The MSC-1 Server can send IAM before receiving LCLS-Status-Change-Request-Acknowledge message. + +- 12a, b. Target-MSC-Server reserves bearer connection T4 towards MGW-1. + +13. After Target MGW has replied with the bearer address and the binding reference, Target MSC-Server returns APM with selected codec and LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. + +![Sequence diagram for Inter-MSC GSM to UMTS Relocation that breaks Local Switching when user plane active, completion phase. The diagram shows interactions between UE-1, BSS-1, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target RNC, MSC-2 S, MGW-2, BSS-2, and UE-2. Key messages include ACM, HO CMD, MAP Process-Access-Signalling Request, TopDescr, Iu Relocation Complete, MAP Send-End-Signalling Request, Answer (LCLS-Status), Clear Command/Complete, LCLS Status Update, Clear Complete, SUB request, and SUB reply. A red box indicates 'Break local switching' at MGW-2.](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant BSS-1 + participant MSC-1 S + participant MGW-1 + participant Target MSC-S + participant Target MGW + participant Target RNC + participant MSC-2 S + participant MGW-2 + participant BSS-2 + participant UE-2 + + Note left of UE-1: Error! No + Note right of UE-2: Error! No text of specified style in + MSC-1 S->>Target MSC-S: 14. ACM, see NOTE 2 + MSC-1 S->>BSS-1: 15. HO CMD + BSS-1->>UE-1: 16. HO CMD, see NOTE 4 + Target RNC->>Target MSC-S: 17. Iu Relocation Detect + Target MSC-S->>MSC-1 S: 18. MAP Process-Access-Signalling Request + MSC-1 S->>MGW-1: 19a. TopDescr, change flow direction ({TA, Ts, oneway}, {TA, T3, bothway}) + MGW-1->>MSC-1 S: 19b. TopDescr Response + Target RNC->>Target MSC-S: 20. Iu Relocation Complete + Target MSC-S->>MSC-1 S: 21. MAP Send-End-Signalling Request + MSC-1 S->>Target MSC-S: 22. Answer (LCLS-Status: "LCLS not connected") + Note right of MGW-2: Break local switching + MSC-1 S->>BSS-1: 23. Clear Command /Complete + MSC-1 S->>MSC-2 S: 25. LCLS Status Update: (LCLS-Status: "LCLS not connected"), see NOTE 5 + BSS-2->>MSC-2 S: 24. LCLS NOTIFICATION (LCLS-BSS-Status: "Call is no longer locally switched") + BSS-1->>MSC-1 S: 26. Clear Complete, see NOTE 6 + MSC-1 S->>MGW-1: 27a. SUB request, release Ts + MGW-1->>MSC-1 S: 27b. SUB reply + +``` + +Sequence diagram for Inter-MSC GSM to UMTS Relocation that breaks Local Switching when user plane active, completion phase. The diagram shows interactions between UE-1, BSS-1, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target RNC, MSC-2 S, MGW-2, BSS-2, and UE-2. Key messages include ACM, HO CMD, MAP Process-Access-Signalling Request, TopDescr, Iu Relocation Complete, MAP Send-End-Signalling Request, Answer (LCLS-Status), Clear Command/Complete, LCLS Status Update, Clear Complete, SUB request, and SUB reply. A red box indicates 'Break local switching' at MGW-2. + +**Figure 8.3.2.4.2.2: Inter-MSC GSM to UMTS Relocation that breaks Local Switching when user plane active, completion phase** + +14. The Target MSC-Server sends ACM (Address Complete Message). Target MSC-Server awaits the capturing of the UE-1 on the radio path when the ACM is sent and the Anchor MSC-1 server initiates the Iu relocation execution when receiving ACM. +15. MSC-1 server sends Handover Command message to BSS-1. +16. BSS-1 sends Handover Command message to UE-1. BSS-1 will discard incoming user plane data send to UE-1 received from CN. If BSS-2 was not instructed to prepare for LCLS related handover in Step 8a, the BSS-2 starts bi-casting UP user plane data generated by UE-2 to local path and A interface and also starts to check whether there is incoming DL user plane data from the core network. + +NOTE 4: there is no situation where BSS-2 will receive real DL user plane data from the CN at the same time as it receives local data from UE-1 as part of the handover. + +17. UE-1 is detected at Target RNC. But still no UL data can be sent from Target RNC to MGW-1 because $T_A-T_3$ is one-way DL only. MGW-1 will continue to transmit DL user plane data to the Target RNC. BSS-2 continues to bi-cast user plane data to both local path and to the A interface. +18. Target MSC-Server sends MAP-Process-Access-Signal request message to the MSC-1 server. +- 19a, b. The MSC-1 server uses the Change Flow Direction procedure to request the MGW-1 to set the Handover Device to intermediate state and $T_A-T_3$ to both-way configuration. When BSS-2 finds out there is DL user plane data, BSS-2 will transmit the DL user plane data to UE-2. +20. Iu Relocation Complete message is received from Target RNC with LCLS-BSS-status indicating that the call cannot be locally switched. +21. Iu-Relocation-Complete message when received is included in the MAP SendEndSignalling Request message sent to the MSC-1 server. + +22. Target MSC-Server sends ANSWER with the LCLS-status when Iu-Relocation Complete message is received. + +23. MSC-1 server informs BSS-1 to clear the old call leg. + +24. Serving BSS-2 informs MSC-2 server that LCLS is broken via LCLS-Notification message. + +25. MSC-1 server sends LCLS Status Update message with LCLS status "LCLS not connected" to MSC-2 server. + +NOTE 5: When BICC is used as the call control protocol the APM message is sent. When SIP-I is used the INFO request with the encapsulated APM message is sent. + +26. BSS-1 informs MSC-1 server that the resource for the UE-1 has been released and BSS-2 stops bi-casting. + +NOTE 6: There is no need to send LCLS-Notification message from BSS-1 after receiving the Clear command since Clear Complete message indicates that LCLS was disconnected. + +27a, b. The MSC-1 server requests MGW-1 to set the Handover Device to its final state by removing the bearer termination $T_S$ towards BSC-1 using the Release Termination procedure. + +## 8.4 GSM to GSM + +### 8.4.1 Intra-MSC Inter-BSS GSM to GSM Handover + +#### 8.4.1.1 Intra-MSC Inter-BSS GSM to GSM Handover that breaks Local Switching + +##### 8.4.1.1.1 General + +When a call is locally switched through the BSS and an intra-MSC inter-BSS GSM to GSM handover occurs then the LCLS shall be broken and the user plane shall be connected through the core network. The intra-MSC inter BSS GSM to GSM handover procedures specified in 3GPP TS 23.205 [2] and 3GPP TS 23.231 [3] shall be followed. The following clauses describe the additional requirements for intra-MSC inter BSS GSM to GSM handovers of LCLS related calls. + +During a Locally Switched (intra-BSS) Connection when no bicasting occurs there is no data transmission through the core network. In this release the use plane is kept active and therefore does not need to be re-activated when the LCLS is broken due to inter-BSS handover out of LCLS. + +##### 8.4.1.1.2 Handover Required + +When the MSC server receives the Handover Required message from the serving BSS, it requests the MGW to seize a TDM circuit if AoTDM or an IP termination if AoIP for the termination to the Target BSS as for the normal handover procedure. The MSC server shall use the Change Flow Direction procedure to request the MGW to set the Handover Device to the initial state. + +##### 8.4.1.1.3 MGW Flow Direction Control + +The MSC Server may perform the MGW Flow Direction Control in the following ways: + +- In accordance with the normal handover case by isolating the termination to the Target BSS ( $T_T$ ) from the termination to the Serving BSS ( $T_S$ ) and configuring the Anchor termination ( $T_A$ ) one-way DL to the Target BSS ( $T_T$ ). Termination to the Serving BSS ( $T_S$ ) is bothway connected to Anchor termination ( $T_A$ ) since it is also receiving UL user data from termination to the Serving BSS ( $T_S$ ). + +Or: + +- The MSC server may request the MGW to set termination to Target BSS ( $T_T$ ) to bothway connected to Anchor termination ( $T_A$ ) and isolate termination to Serving BSS ( $T_S$ ) completely. This improves the user plane switching and saves a signalling step to the MGW at Handover Detect message. The MSC server sends the Handover Request message to the Target BSS as for the normal case but shall include the GCR IE, the LCLS-Configuration IE and the LCLS-Connection-Status-Control IE set to "Connect". + +#### 8.4.1.1.4 Handover Request Acknowledge + +If the Target BSS supports LCLS feature then it shall include the LCLS-BSS-Status IE in the Handover Request Acknowledge message in order to inform the anchor MSC Server that the BSS supports the LCLS feature, and therefore the MSC Server shall not act upon the status indicated, i.e. no signalling of LCLS-Status IE through the core network. + +Upon receipt of the Handover Request Acknowledge message the MSC Server shall send to the adjacent call node the LCLS-Status-Change-Request message to indicate "LCLS Disconnection-Preparation-for handover". + +When the far end MSC server receives the LCLS-Status-Change-Request message indicating LCLS Disconnection preparation-for-handover it shall send to the BSS the LCLS\_Connect\_Control message with the LCLS-Connection-Status-Control IE indicating "BicastatHandover". When the LCLS\_Connect\_Control acknowledge message is received from the BSS, the far end MSC server shall return the LCLS Status Change Request Acknowledge message indicating "LCLS Disconnection-Preparation-for-handover" and a Result code indicating LCLS Status Change Request accepted. + +#### 8.4.1.1.5 Handover Command/Handover Detect + +When the MSC server sends the Handover Command message or alternatively if it receives the Handover Detect message, if the MSC server followed the MGW control procedures for a non-LCLS call and kept the Termination to the Serving BSS connected then it shall use the Change Flow Direction procedure to requests the MGW to set the Handover Device to intermediate state however if the MSC server isolated $T_S$ and set $T_T$ to bothway through-connected then no MGW control procedure is required at this point. + +Upon receipt of the Handover Detect message the MSC Server shall send to the adjacent call node the LCLS-Status-Change-Request message with the LCLS-Status-Change-Request IE set to "Indicate DL data after Handover". + +When the far end MSC server receives the LCLS-Status-Change-Request message with the LCLS-Status-Change-Request IE set to "Indicate DL data after Handover" it shall send to the BSS the LCLS\_Connect\_Control message with the LCLS-Connection-Status-Control IE indicating "DL Data at\_Handover" and after reception of the LCLS\_Connect\_Control acknowledge message from the BSS, return the LCLS-Status-Change-Request-Acknowledge message with "Indicate DL data after Handover" and a Result code indicating LCLS Status Change Request accepted. + +NOTE: this informs this call leg in the BSS that the other UE has left the BSS and has been detected in the new BSS and as such DL data from the CN is now coming from that UE. + +#### 8.4.1.1.6 Handover Complete + +When the MSC server receives the Handover Complete message, it releases the A-interface line towards the serving BSS. The MSC server also requests the MGW to set the Handover Device to its final state by removing the bearer termination ( $T_S$ ) towards the serving BSS. + +The MSC server shall send to the adjacent call node the LCLS-Status-Update message with the LCLS-Status IE indicating the LCLS disconnection. + +When the serving BSS receives Clear Command it shall release any local switch path. The serving BSS shall inform the far end MSC server that LCLS is broken with the LCLS\_Notification message. + +NOTE: The LCLS\_Notification message does not need to be sent to the Anchor MSC Server since the Clear Command message received from the serving BSS also means LCLS is disconnected. + +#### 8.4.1.1.7 Example + +##### 8.4.1.1.7.1 Connection Model + +Figure 8.4.1.1.7.1.1 shows the network model for the Intra-MSC Inter-BSS GSM to GSM Handover, where the call leg pertinent to the UE-1 is handed over from the serving BSS-1 to the Target BSS. BSS-1 is the same as BSS-2 when LCLS is established for the call. The bearer termination $T_2$ is used for the bearer towards BSS-2, which is not affected by this handover. Bearer termination $T_S$ is used for the bearer towards BSS-1 and the bearer terminations $T_1$ and $T_A$ are used for the bearer towards the succeeding/preceding MGW. Bearer termination $T_T$ is for the bearer termination towards the Target BSS. The colours and line types used in the figure are defined differently from 3GPP TS 23.205 [2] to indicate LCLS specific issues. + +- User plane link which transmits real user plane data within the BSS and to UEs +- User plane link which transmits real user plane data through the CN and to UEs +- ... User plane path through the CN, connected +- - - - Control plane link which transmits signalling + +![Diagram of Connection Model 1: The call is locally switched. It shows two User Equipment (UE-1, UE-2) connected to a Base Station Subsystem (BSS) containing BSS-1 and BSS-2. Red lines represent user plane data paths between the UEs and the BSS. Green dashed lines represent control signalling paths between the BSS and two Mobile Switching Centers (MSC-S-1, MSC-S-2). MSC-S-1 and MSC-S-2 are connected to Media Gateways (MGW-1, MGW-2) via blue lines. MGW-1 and MGW-2 are connected to a 'Non-LCLS User Plane' represented by a dotted line. The diagram is labeled 'Before Handover'.](114902bbeea56bda01b64b43fad41920_img.jpg) + +**Control Signalling** + +**MSC-S-1**      **MSC-S-2** + +**UE-2** +**BSS-1/BSS-2** +**UE-1** + +**User Plane Data** + +Non-LCLS User Plane + +Before Handover + +$T_S$ $T_A$      $T_1$ $T_2$ + +**MGW-1**      **MGW-2** + +Diagram of Connection Model 1: The call is locally switched. It shows two User Equipment (UE-1, UE-2) connected to a Base Station Subsystem (BSS) containing BSS-1 and BSS-2. Red lines represent user plane data paths between the UEs and the BSS. Green dashed lines represent control signalling paths between the BSS and two Mobile Switching Centers (MSC-S-1, MSC-S-2). MSC-S-1 and MSC-S-2 are connected to Media Gateways (MGW-1, MGW-2) via blue lines. MGW-1 and MGW-2 are connected to a 'Non-LCLS User Plane' represented by a dotted line. The diagram is labeled 'Before Handover'. + +**Connection Model 1: The call is locally switched** + +![Diagram of Connection Model 2: MGW-1 is both-way connected between Ta and Tt, Ts is isolated; BSS-2 starts to bicast data UL. This diagram shows the state 'During Handover'. UE-1 and UE-2 are still connected to BSS-1/BSS-2. A new 'Target BSS' is shown. MGW-1 has a 'Serving' (Ts) port isolated and an 'Anchor' (TA) port connected to the user plane path. A 'Target' (Tt) port on MGW-1 is connected to the Target BSS. User plane data (red lines) is shown being bicast from BSS-2 to both UE-1 and UE-2. Control signalling (green dashed lines) continues to flow between the BSS and MSC-S-1. A legend defines: TS = Serving, TA = Anchor, TT = Target.](f2486d5031b55e42b300903a716b0a00_img.jpg) + +**Control Signalling** + +**MSC-S-1**      **MSC-S-2** + +**UE-2** +**BSS-1/BSS-2** +**UE-1** + +**User Plane Data** + +User Plane Data + +**Target BSS** + +$T_S$ $T_A$      $T_1$ $T_2$ + +$T_T$ + +**MGW-1**      **MGW-2** + +During Handover + $T_S$ = Serving + $T_A$ = Anchor + $T_T$ = Target + +Diagram of Connection Model 2: MGW-1 is both-way connected between Ta and Tt, Ts is isolated; BSS-2 starts to bicast data UL. This diagram shows the state 'During Handover'. UE-1 and UE-2 are still connected to BSS-1/BSS-2. A new 'Target BSS' is shown. MGW-1 has a 'Serving' (Ts) port isolated and an 'Anchor' (TA) port connected to the user plane path. A 'Target' (Tt) port on MGW-1 is connected to the Target BSS. User plane data (red lines) is shown being bicast from BSS-2 to both UE-1 and UE-2. Control signalling (green dashed lines) continues to flow between the BSS and MSC-S-1. A legend defines: TS = Serving, TA = Anchor, TT = Target. + +**Connection Model 2: MGW-1 is both-way connected between Ta and Tt, Ts is isolated; BSS-2 starts to bicast data UL** + +![Diagram of Connection Model 3: UE has moved to Target BSS but HO Detect has not yet been received by MSC-S-1. The diagram illustrates the network architecture during a handover. UE-2 is connected to BSS-1/BSS-2. UE-1 is connected to Target BSS. Control signaling (green dashed lines) connects MSC-S-1, MSC-S-2, BSS-1/BSS-2, and Target BSS. User Plane Data (black solid lines with dots) flows from UE-2 through BSS-1/BSS-2, MGW-2 (terminations T1, T2), and MGW-1 (terminations TA, TT) to Target BSS and UE-1. A red arrow indicates 'User Plane Data' path between BSS-1/BSS-2 and MGW-1 (termination TS).](1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg) + +Control Signalling + +MSC-S-1 + +MSC-S-2 + +UE-2 + +BSS-1/ +BSS-2 + +User Plane Data + +UE-1 + +Target BSS + +TS + +TA + +TT + +MGW-1 + +T1 + +T2 + +MGW-2 + +During Handover +TS = Serving +TA = Anchor +TT = Target + +Diagram of Connection Model 3: UE has moved to Target BSS but HO Detect has not yet been received by MSC-S-1. The diagram illustrates the network architecture during a handover. UE-2 is connected to BSS-1/BSS-2. UE-1 is connected to Target BSS. Control signaling (green dashed lines) connects MSC-S-1, MSC-S-2, BSS-1/BSS-2, and Target BSS. User Plane Data (black solid lines with dots) flows from UE-2 through BSS-1/BSS-2, MGW-2 (terminations T1, T2), and MGW-1 (terminations TA, TT) to Target BSS and UE-1. A red arrow indicates 'User Plane Data' path between BSS-1/BSS-2 and MGW-1 (termination TS). + +**Connection Model 3: UE has moved to Target BSS but HO Detect has not yet been received by MSC-S-1** + +![Diagram of Connection Model 4: LCLS is released in BSS-2, old serving Termination Ts is removed. This diagram shows the state after handover. The connection from BSS-1/BSS-2 to MGW-1 termination TS is gone. User Plane Data now flows from UE-2 through BSS-1/BSS-2, MGW-2, and MGW-1 (terminations TT, TA) to Target BSS and UE-1. Control signaling remains between MSCs and BSSs.](79aaab5889060cf8264226764a109cdb_img.jpg) + +Control Signalling + +MSC-S-1 + +MSC-S-2 + +UE-2 + +BSS-1/BSS-2 + +User Plane Data + +UE-1 + +Target BSS + +TT + +TA + +MGW-1 + +T1 + +T2 + +MGW-2 + +After Handover +TA = Anchor +TT = Target + +Diagram of Connection Model 4: LCLS is released in BSS-2, old serving Termination Ts is removed. This diagram shows the state after handover. The connection from BSS-1/BSS-2 to MGW-1 termination TS is gone. User Plane Data now flows from UE-2 through BSS-1/BSS-2, MGW-2, and MGW-1 (terminations TT, TA) to Target BSS and UE-1. Control signaling remains between MSCs and BSSs. + +**Connection Model 4: LCLS is released in BSS-2, old serving Termination Ts is removed** + +**Figure 8.4.1.1.7.1.1: Intra-MSC Inter-BSS Handover Connection Model that breaks LCLS** + +##### 8.4.1.1.7.2 Basic Sequence for Inter-BSS Handover that breaks Local Switching + +![Sequence diagram for Intra-MSC Inter-BSS Handover that breaks Local Switching. The diagram shows the interaction between UE-1, BSS-1, MGW-1, MSC-S-1, TargetBSS, MSC-S-2, MGW-2, BSS-2, and UE-2. It details the signaling steps for a handover that breaks local switching, including HO Required, Context C1, HO Request, HO Request Ack, LCLS-Status-Change-Request, HO CMD, LCLS Status Change Request Acknowledge, HO Detect, LCLS-Status-Change-Request, HO Complete, Clear Command, LCLS-Status-Change-Request Ack, Clear Complete, Context C1, and LCLS-Status-Update. Red arrows indicate the locally switched user plane, and black arrows indicate the normally switched user plane.](820515db47ded68f5e0b625f4ec7d2c1_img.jpg) + +The diagram illustrates the sequence of messages for an intra-MSC inter-BSS handover that breaks local switching. The participants are UE-1, BSS-1, MGW-1, MSC-S-1, TargetBSS, MSC-S-2, MGW-2, BSS-2, and UE-2. The process starts with UE-1 sending an HO Required message to BSS-1. BSS-1 then sends a Context C1 message to MSC-S-1, which includes ADD Termination for Target BSS (TT) – bothway; and MOD Ts Isolate. MSC-S-1 sends an HO Request to TargetBSS, which includes LCLS-Configuration and LCLS-Connection-Status-Control = "Connect". TargetBSS responds with an HO Request Ack, indicating that the call is not possible to be locally switched. MSC-S-1 then sends an LCLS-Status-Change-Request to MSC-S-2, indicating LCLS-Disconnection-PreparationForHandover. MSC-S-2 sends a 5a. LCLS\_CONNECT\_CONTROL message to MGW-2, with LCLS-Connection-Status-Control = "BicastaHandover". MGW-2 responds with a 5b. LCLS\_CONNECT\_CONTROL\_ACK, indicating that the call is locally switched with the requested LCLS configuration. MSC-S-1 sends an HO CMD to BSS-1. BSS-1 responds with a 7. LCLS Status Change Request Acknowledge, indicating LCLS-Disconnection-PreparationForHandover and a Result Code of "Status Change Req Accepted". BSS-1 then sends an HO Detect message to TargetBSS. TargetBSS sends a 8a. LCLS-Status-Change-Request to MSC-S-2, indicating IndicateDLdataAfterHandover. MSC-S-2 sends a 8b. LCLS\_CONNECT\_CONTROL message to MGW-2, with LCLS-Connection-Status-Control = "DLDataAtHandover". MGW-2 responds with a 8c. LCLS\_CONNECT\_CONTROL Ack, indicating that the call is locally switched with the requested LCLS configuration. BSS-1 sends a 8d. LCLS-Status-Change-Request Ack to TargetBSS, indicating IndicateDLdataAfterHandover and a Result Code of "Status Change Req Accepted". MSC-S-1 sends an HO Complete message to TargetBSS, indicating that the call is not possible to be locally switched. BSS-1 then sends a Clear Command to UE-1, which is labeled "Break local switching". MSC-S-1 sends a Clear Complete message to TargetBSS. TargetBSS sends a 11. LCLS\_NOTIFICATION message to MSC-S-2, indicating that the call is no longer locally switched. MSC-S-1 sends a Context C1 message to BSS-1, which includes SUB Ts. BSS-1 sends a 14. LCLS-Status-Update message to MSC-S-2, indicating that LCLS is not connected. Finally, the user plane switches from the locally switched path (red arrows) to the normally switched path (black arrows). + +Sequence diagram for Intra-MSC Inter-BSS Handover that breaks Local Switching. The diagram shows the interaction between UE-1, BSS-1, MGW-1, MSC-S-1, TargetBSS, MSC-S-2, MGW-2, BSS-2, and UE-2. It details the signaling steps for a handover that breaks local switching, including HO Required, Context C1, HO Request, HO Request Ack, LCLS-Status-Change-Request, HO CMD, LCLS Status Change Request Acknowledge, HO Detect, LCLS-Status-Change-Request, HO Complete, Clear Command, LCLS-Status-Change-Request Ack, Clear Complete, Context C1, and LCLS-Status-Update. Red arrows indicate the locally switched user plane, and black arrows indicate the normally switched user plane. + +Figure 8.4.1.1.7.2.1: Intra-MSC Inter-BSS Handover that breaks Local Switching + +1. The Handover Required message is received from the BSS-1 requesting an inter-BSS handover. The call is currently locally switched so the MSC-1 server can know that the inter-BSS handover at one end will break local switch (the local switch is not broken in the serving BSS (BSS-1) until the UE-1 has moved out of the BSS-1 and the MSC-1 server sends the Clear Command message). +2. In this example the Anchor MSC-1 server requests from its MGW-1 the seizure of the bearer termination Tt towards the Target BSS and through-connects it bothway to Ta. Additionally it isolates the old serving Termination Ts. This makes the handover much more efficient than even current non-LCLS handover as immediately the UE-1 moves into the new target BSS it will be able to send UL user data to the UE-2. + +NOTE 1: This flow shows the termination to the Target BSS as always connected bothway. This is a change to the existing call handling which would normally connect the termination as one-way and then change to bothway after receiving the Handover Detect message. However the termination does not need to be connected one-way and will in fact make the break in speech worse since UL data cannot be sent from the UE-1 until the MGW topology is modified, also it saves the additional intermediate H.248 modification step. + +3. The Anchor MSC-1 server sends the Handover Request message to the Target BSS with the GCR IE, the LCLS-Configuration IE and the LCLS-Connection-Status-Control IE indicating "connect" to through-connect the local call. +4. The Target BSS returns the Handover Request Acknowledge message and also indicates that call is not possible to be locally switched. +5. The Anchor MSC-1 server sends the change in LCLS to the succeeding MSC server and the Anchor MSC-1 server asks it to prepare for the LCLS disconnection for Handover to trigger sending of the LCLS-Connect-Control message at the far end MSC-2 server. + +NOTE 2: When BICC is used as the call control protocol the APM message is sent. When SIP-I is used the INFO request with the encapsulated APM message is sent. + +- 5a. The far end MSC-2 server requests the BSS-2 to start sending data UL with the LCLS\_Connect\_Control message and the LCLS-Connection-Status-Control IE indicating "BicastaHandover", see Figure 8.4.1.7.1.1 Connection Model 2. This triggers the BSS-2 to bicast the user plane data in the same way as the Access MGW-1 would be doing in a non-LCLS inter-BSS handover. At this point the BSS-2 shall send any DL data it receives directly to the served UE. Since the BSS-2 cannot receive DL data at the same time as it receives local data (Ts is isolated) this will minimise the break in user plane data even more than for existing non-LCLS handover. + +NOTE 3: The Serving BSS-1 shall forward the user plane data from the UE-1 to the UE-2 while the UE-1 is served by the BSS-1. The UL user plane data from UE-2 are bi-cast to both MGW2 and local path by the BSS-2. The MGW-2 transmits the user plane data to the MGW-1, and the MGW-1 will transmit the user plane data to the target BSS. When the UE-1 leaves the serving BSS-1 and begins sending UL data from the Target BSS, that data will then be received via the A-interface leg at the serving BSS-2. + +NOTE 4: Possible bicasting may have been activated earlier when LCLS was established in the BSS-1 /BSS-2 (not shown in the figure 8.4.1.8.2.1) and was indicated with the LCLS-Configuration IE in step 3 and applies to both call legs. If LCLS bicasting was not activated the LCLS-Configuration value is "Connect" (i.e. no bicasting) in step 3, but the value of the LCLS-Connection-Status-Control in step 5 is "BicastaHandover", which applies only for this call leg. + +- 5b. The BSS-2 sends the LCLS\_Connect\_Control\_Ack message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration". +6. The Anchor MSC-1 server triggers the Handover Command message. When the UE-1 moves to the Target BSS in this example it can immediately send UL data through the CN to the UE-2 and also can receive DL data from the UE-2 via the CN since the MGW-1 topology for Ta, Tt is already bothway connected. This is a change from the current non-LCLS solution but is more efficient since the non-LCLS solution needs to set this to one-way DL only until it receives Handover Detect message. +7. MSC-2 Server sends LCLS-Status-Change-Request-Acknowledgement. +8. The UE-1 is detected at the target BSS. The BSS-1/BSS-2 may continue to send the user plane data locally until the Clear Command message is received. +- 8a. The MSC-1 Server sends LCLS-Status-Change-Request to indicate that UE-1 has been detected in the target BSS and user data is now being sent through the CN and DL to the distant UE-2. +- 8b. The MSC-2 Server signals to the BSS-2 that DL data received from the CN is now real user data coming from the UE-1. +- 8c. The BSS-2 sends the LCLS\_Connect\_Control\_Ack message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration". +- 8d. Acknowledgement back through the CN that the indication for DL data after Handover Detect has been delivered. +9. In the Handover Complete message the Target-BSS indicates to the MSC-1 server in the LCLS-BSS-Status IE that the call is not possible to be locally switched. + +10. The MSC-1 server requests the old serving BSS-1 to clear the old call leg. The BSS-1 now stops sending local the user data from UE-1, LCLS is finally broken. +11. The Serving BSS-2 informs the MSC-2 server that LCLS is broken via LCLS\_Notification message. +12. Clearing of the old call leg to the Serving BSS-1 is completed. +13. The termination Ts to the old serving BSS-1 is removed from the Access MGW-1. +14. The Anchor MSC-1 server informs succeeding CN nodes that LCLS is finally disconnected. + +NOTE 5: When BICC is used as the call control protocol the APM message is sent. When SIP-I is used the INFO request with the encapsulated APM message is sent. + +LCLS is impossible after an Inter-BSS handover which makes the call not local (as described above). While a handover is being performed for one call leg, it is possible that a handover also is started for the other call leg, possibly moving both call legs to the same target BSS, thereby creating a local call. The target BSS shall only establish LCLS for a local call when both call legs are connected and e.g. any handover process has been successfully completed on both call legs. + +#### 8.4.1.2 Intra-MSC Inter-BSS GSM to GSM Handovers that establishes Local Switching + +##### 8.4.1.2.1 General + +When LCLS is not established for a call and an intra-MSC inter-BSS GSM to GSM handover occurs that makes the call local, the call should be locally switched in the BSS. The Intra-MSC inter-BSS GSM to GSM handover procedures specified in 3GPP TS 23.009 [9], 3GPP TS 23.205 [2] and 3GPP TS 23.231 [3] shall be followed. The following clauses describe the additional requirements for intra-MSC handovers that establish LCLS. + +##### 8.4.1.2.2 Handover Required + +When the MSC server receives the Handover Required message from the serving BSS, it requests the MGW to seize a TDM circuit if AoTDM or an IP termination if AoIP for the termination to the Target BSS as for the normal handover procedure. The MSC server shall use the Change Flow Direction procedure to request the MGW to set the Handover Device to the initial state. + +##### 8.4.1.2.3 Bearer establishment towards Target BSS + +When the MSC-Server has selected the Target MGW it requests the Target MGW to seize a TDM circuit if AoTDM using the Reserve Circuit procedure, or an IP termination if AoIP using the reserve Connection Point procedure as for the normal handover procedure. The MSC-Server sends the Handover Request message to the Target BSS containing the CIC for AoTDM or the IP addresses and UDP ports received from the target MGW if AoIP. + +##### 8.4.1.2.4 MGW Flow Direction Control + +In accordance with the normal handover case the MGW-1 isolates the termination towards the Target BSS (TT) from the termination to the Serving BSS (TS) and configures the Anchor termination (TA) one-way DL towards the Target BSS termination (TT). Termination to the Serving BSS (TS) is both-way connected to Anchor termination (TA) since it is also receiving UL user data from termination to the Serving BSS (TS). + +##### 8.4.1.2.5 Handover Request Acknowledge + +If the Target BSS supports the LCLS feature it shall include the LCLS-BSS-Status IE in the Handover Request Acknowledge message in order to inform the anchor MSC Server that the BSS supports the LCLS feature. + +The anchor MSC Server shall not act upon the status indicated, i.e. no signalling of LCLS-Status IE through the core network. + +##### 8.4.1.2.6 Handover Command/Handover Detect + +The anchor MSC Server shall use the Change Flow Direction procedure to requests the MGW-1 to set the Handover Device to intermediate state. + +##### 8.4.1.2.7 Handover Complete + +When the MSC-Server receives the Handover Complete message, it releases the A-interface line towards the serving BSS. The MSC-Server also requests the MGW to set the Handover Device to its final state by removing the bearer termination towards the serving BSS. + +When LCLS has been established during the handover procedure, the target BSS informs the anchor MSC-Server that the call has been locally switched in the Handover Complete message. + +The MSC-Server shall send to the adjacent call node the LCLS-Status-Update message with the LCLS-Status IE indicating that LCLS was established. + +##### 8.4.1.2.8 Example + +##### 8.4.1.2.8.1 Connection Model + +Figure 8.4.1.2.8.1.1 shows the network model for the Intra-MSC Inter-BSS GSM to GSM Handover, where the call leg pertinent to the UE-1 is handed over from the serving BSS-1 to the Target BSS. Target BSS is the same as BSS-2 when LCLS is established for the call. The bearer termination T2 is used for the bearer towards BSS-2, which is not affected by this handover. Bearer termination TS is used for the bearer towards BSS-1 and the bearer terminations T1 and TA are used for the bearer towards the succeeding/preceding MGW. Bearer termination TT is for the bearer termination towards the Target BSS. The colours and line types used in the figure are defined differently from 3GPP TS 23.205 [2] to indicate LCLS specific issues. + +- User plane link which transmits real user plane data within the BSS and to UEs +- User plane link which transmits real user plane data through the CN and to UEs +- • • User plane path through the CN, connected +- - - Control plane link which transmits signalling + +![Diagram of Connection Model 1: Before handover. It shows UE-1 connected to BSS-1, which is connected to MGW-1 (terminations T_S and T_A). MGW-1 is connected to MGW-2 (terminations T_1 and T_2), which is connected to BSS-2 (Target BSS) and then to UE-2. MSC-1 S and MSC-2 S are connected to MGW-1 and MGW-2 respectively. Control signalling is shown as green dashed lines between the UEs, BSSs, and MSCs. User plane data is shown as a solid black line between UE-1 and UE-2.](37a6ab1d23efb9dc00cfae09d353b1da_img.jpg) + +Diagram of Connection Model 1: Before handover. It shows UE-1 connected to BSS-1, which is connected to MGW-1 (terminations T\_S and T\_A). MGW-1 is connected to MGW-2 (terminations T\_1 and T\_2), which is connected to BSS-2 (Target BSS) and then to UE-2. MSC-1 S and MSC-2 S are connected to MGW-1 and MGW-2 respectively. Control signalling is shown as green dashed lines between the UEs, BSSs, and MSCs. User plane data is shown as a solid black line between UE-1 and UE-2. + +Connection Model 1: Before handover + +![Diagram of Connection Model 1 showing UE-1 and UE-2 connected to BSS-1 and BSS-2/Target BSS respectively, with control signalling and user plane data paths through MGW-1 and MGW-2 to MSC-1 S and MSC-2 S.](aa81b9b80bd1e3d723922b3a033564a2_img.jpg) + +This diagram illustrates Connection Model 1. UE-2 is connected to BSS-2/Target BSS, which is connected to MGW-1. UE-1 is connected to BSS-1, which is also connected to MGW-1. MGW-1 is connected to MGW-2. MSC-1 S is connected to MGW-1, and MSC-2 S is connected to MGW-2. Control signalling is shown as green dashed lines, and user plane data is shown as red dashed lines. A blue solid line represents the user plane data path from UE-2 through BSS-2/Target BSS, MGW-1, and MGW-2 to MSC-2 S. + +Diagram of Connection Model 1 showing UE-1 and UE-2 connected to BSS-1 and BSS-2/Target BSS respectively, with control signalling and user plane data paths through MGW-1 and MGW-2 to MSC-1 S and MSC-2 S. + +Connection Model 2: During handover, $T_S$ and $T_A$ are both-way connected, $T_T$ is isolated from $T_S$ + +![Diagram of Connection Model 2 during handover, showing UE-1 moving from BSS-1 to Target BSS. Control signalling and user plane data paths are shown, with a red arrow indicating the user plane data path from UE-1 to Target BSS.](f76f0f5dfff2511b51f6b875867c029f_img.jpg) + +This diagram illustrates Connection Model 2 during a handover. UE-1 is moving from BSS-1 to Target BSS, indicated by a blue upward arrow. UE-2 remains connected to BSS-2/Target BSS. Control signalling (green dashed lines) and user plane data (red dashed lines) paths are shown. A red arrow indicates the user plane data path from UE-1 to Target BSS. The diagram shows $T_S$ and $T_A$ both-way connected in MGW-1, while $T_T$ is isolated from $T_S$ . + +Diagram of Connection Model 2 during handover, showing UE-1 moving from BSS-1 to Target BSS. Control signalling and user plane data paths are shown, with a red arrow indicating the user plane data path from UE-1 to Target BSS. + +Connection Model 3: UE has moved to Target BSS but HO Detect has not yet been received by MSC-1-S + +![Diagram of Connection Model 4: The call is locally switched. It shows two User Equipment (UE) units, UE-1 and UE-2, connected to a Target BSS. The Target BSS is connected to MSC-1 S via Control Signalling (green dashed line) and User Plane Data (red solid line). MSC-1 S is connected to MGW-1 via a Non-LCLS User Plane (blue solid line). MSC-2 S is connected to MGW-2 via a Non-LCLS User Plane (blue solid line). The diagram illustrates the local switching of the call within the Target BSS.](88b0f3f4393228e9ea4d6542aef7c399_img.jpg) + +Diagram of Connection Model 4: The call is locally switched. It shows two User Equipment (UE) units, UE-1 and UE-2, connected to a Target BSS. The Target BSS is connected to MSC-1 S via Control Signalling (green dashed line) and User Plane Data (red solid line). MSC-1 S is connected to MGW-1 via a Non-LCLS User Plane (blue solid line). MSC-2 S is connected to MGW-2 via a Non-LCLS User Plane (blue solid line). The diagram illustrates the local switching of the call within the Target BSS. + +**Connection Model 4: The call is locally switched** + +**Figure 8.4.1.2.8.1.1: Connection Models for Inter-BSS Handover that establishes Local Switching** + +###### **8.4.1.2.8.2 Basic Sequence for Inter-BSS Handover that establishes Local Switching** + +Figures 8.4.1.2.8.2.1 and 8.4.1.2.8.2.2 show the message sequence example for the Basic Intra-MSC GSM to GSM Handover shown in the corresponding network model Figure 8.4.1.2.8.1.1. The Handover Device is located in MGW-1 selected for the call establishment by the MSC-1 server, which controls the call and the mobility management. The description is based on 3GPP TS 23.009 [9], 3GPP TS 23.205 [2] and 3GPP TS 23.231 [3]. + +![Sequence diagram for Inter-BSS Handover that establishes Local Switching. The diagram shows the interaction between UE-1, BSS-1, MGW-1, MSC-1 S, TargetBSS, MSC-2 S, MGW-2, BSS-2, and UE-2. It details the steps for a handover that results in local switching within the BSS.](997233d405f0d4b89ddeb7683e047f66_img.jpg) + +The sequence diagram illustrates the following steps: + +- 1. HO Required:** BSS-1 sends a message to MSC-1 S. +- 2a. TopDescr({\*TS, isolate}, {TA, TT oneway})+ADD.request (TT):** MSC-1 S sends a message to MGW-1. +- 2b. TopDescr()+ADD reply (TT):** MGW-1 sends a reply to MSC-1 S. +- 3. HO Request (GCR, LCLS-Configuration, LCLS-Connection-Status-Control = "Connect"):** MSC-1 S sends a message to TargetBSS. +- 4. HO Request Ack (LCLS-BSS-Status: "Call not yet locally switched"):** TargetBSS sends a reply to MSC-1 S. +- 4a. LCLS\_NOTIFICATION (LCLS-BSS-Status: "Call not yet locally switched"):** TargetBSS sends a message to MSC-2 S. +- IF call has been answered and MSC permits LCLS to be connected then update the Connection Status in BSS:** A dashed box indicates a conditional step. +- 4b. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "Connect"):** MSC-2 S sends a message to BSS-2. +- 4c. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status: "Call not yet locally switched"):** BSS-2 sends a reply to MSC-2 S. +- 5a. MOD request TT, configure Connection Point, only AoIP:** MSC-1 S sends a message to MGW-1. +- 5b. MOD reply TT:** MGW-1 sends a reply to MSC-1 S. +- 6. HO CMD:** MSC-1 S sends a message to BSS-1. +- 7. HO Detect:** TargetBSS sends a message to MSC-1 S. +- 8a. TopDescr, change flow direction ({TA, TS oneway}, {TA, TT bothway}):** MSC-1 S sends a message to MGW-1. +- 8b. TopDescr reply:** MGW-1 sends a reply to MSC-1 S. +- Locally Switched User Plane in the BSS:** A red arrow indicates the user plane path from UE-1 through BSS-1 and TargetBSS to BSS-2 and UE-2. +- 9. HO Complete (LCLS-BSS-Status: "call is locally switched with requested LCLS configuration"):** TargetBSS sends a message to MSC-1 S. +- 10. LCLS\_NOTIFICATION (LCLS-BSS-Status: "call is locally switched with requested LCLS configuration"):** TargetBSS sends a message to MSC-2 S. +- 11. Clear Command:** MSC-1 S sends a message to BSS-1. +- 12. Clear Complete:** BSS-1 sends a reply to MSC-1 S. +- 13. Context C1: SUB TS:** MSC-1 S sends a message to MGW-1. +- 14. LCLS-Status-Update (LCLS-Status: "LCLS connected"):** MSC-1 S sends a message to MSC-2 S. + +Sequence diagram for Inter-BSS Handover that establishes Local Switching. The diagram shows the interaction between UE-1, BSS-1, MGW-1, MSC-1 S, TargetBSS, MSC-2 S, MGW-2, BSS-2, and UE-2. It details the steps for a handover that results in local switching within the BSS. + +**Figure 8.4.1.2.8.2.1: Inter-BSS Handover that establishes Local Switching** + +- Handover Required message is received from BSS-1 requesting an inter-MSC handover. The call is currently not locally switched. +- MSC-1 Server determines that an intra-MSC handover is required and checks that LCLS negotiation in the core network permitted LCLS. The MSC-1 Server reserves a new Termination for Target BSS and configures this as one-way connected to the Anchor Termination (as per existing handover procedures). +- MSC-1 Server sends Handover Request message to target BSS with GCR and instructs the BSS to prepare to connect LCLS. The LCLS-Configuration IE can instruct the BSS to bi-cast user plane data, if applicable. +- Target BSS performs call leg correlation with GCR to find if another call leg is active with the same GCR. The BSS reports in Handover Request Acknowledge message that the local call was found but LCLS is not yet established. +- 4a. The BSS-2 notifies MSC-2 server the LCLS status is changed by sending the LCLS\_Notification message with the LCLS-BSS-Status IE set to "Call not yet locally switched". +- 4b. If the call has been answered and MSC-2 server permits LCLS to be connected, then the MSC-2 server sends to the BSS-2 the LCLS\_Connect\_Control message with the LCLS-Connection-Status-Control IE set to "connect". + +- 4c. The BSS-2 returns the LCLS\_Connect\_Control\_ACK message with the LCLS-BSS-Status IE set to "Call not yet locally switched". +- 5a, b. (These signalling steps are only applicable to AoIP.) MSC-1 Server sends the IP address and UDP Port number of the Target BSS to MGW-1 using the Configure RTP Connection Point procedure. +6. MSC-1 Server sends the Handover Command message. +7. UE-1 gets connected to the Target BSS, which sends Handover Detect. +- 8a, b. In accordance with normal handover the MSC-1 Server requests MGW-1 to isolate the termination towards Target BSS (TT) from the termination to the Serving BSS-1 (TS) and to configure the Anchor termination (TA) one-way DL towards the Target BSS termination (TT). +9. Target BSS indicates in the Handover Complete message that the call is locally switched. +10. BSS-2 sends the LCLS\_Notification message to MSC-2 Server with the LCLS-BSS-Status IE set to "call is locally switched with requested LCLS configuration". +11. MSC-1 Server requests the old serving BSS-1 to clear the old call leg. +12. Clearing of the old call leg to the Serving BSS-1 is completed. +13. The termination TS to the old serving BSS-1 is removed from MGW-1. +14. MSC-1 Server informs succeeding CN nodes that LCLS is connected. + +NOTE: When BICC is used as the call control protocol the APM message is sent. When SIP-I is used the INFO request with the encapsulated APM message is sent. + +LCLS becomes possible after an Inter-BSS handover which makes the call local (as described above). While a handover is being performed for one call leg, it is possible that a handover also is started for the other call leg, possibly moving that call leg to another BSS and in that case the call does not become local. The target BSS shall only establish LCLS for a local call when both call legs are connected and e.g. any handover process has been successfully completed on both call legs. + +### 8.4.2 Inter-MSC GSM to GSM Handover + +#### 8.4.2.1 Inter-MSC GSM to GSM Handover that breaks Local Switching + +##### 8.4.2.1.1 General + +If LCLS is established for a call and an inter-MSC GSM to GSM handover occurs that makes the call not local the LCLS shall be broken in the BSS and the user plane data shall be connected through the core network. The Inter-MSC GSM to GSM handover procedures specified in 3GPP TS 23.009 [9], 3GPP TS 23.205 [2] and 3GPP TS 23.231 [3] shall be followed. The following clauses describe the additional requirements for inter-MSC handovers of LCLS related calls. + +##### 8.4.2.1.2 MSC-1 / MGW-1 + +###### 8.4.2.1.2.1 Handover Required + +When MSC-1 Server receives the Handover Required message from the serving BSS and determines that the call shall be handed over to the Target MSC Server, it shall send the GCR of the call, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE to the Target MSC Server in a MAP Prepare-Handover\_Request message. + +###### 8.4.2.1.2.2 Handover Request Acknowledge + +When MSC-1 Server receives the MAP Prepare\_Handover\_Response including Handover\_Request\_Acknowledgement message with a LCLS-BSS-Status IE the Anchor MSC-1 Server shall send to the adjacent call node, MSC-2 Server, the LCLS-Status-Change Request message containing the LCLS-Status-Change-Request IE to signal the change of LCLS status. In the LCLS-Status-Change-Request IE the MSC-1 server shall indicate "LCLS Disconnection-Preparation-for handover". + +When the MSC-2 Server receives the LCLS-Status-Change Request message with the LCLS-Status-Change-Request IE that requires LCLS Disconnection preparation-for-handover it shall send to BSS-2 the LCLS\_Connect\_Control message + +with the LCLS-Connection-Status-Control IE indicating "BicastatHandover". When the LCLS\_Connect\_Control acknowledge message is received from the BSS-2, the MSC-2 server shall return the LCLS Status Change Request Acknowledge message indicating "LCLS Disconnection-Preparation-for-handover" and a Result code indicating LCLS Status Change Request accepted. + +###### 8.4.2.1.2.3 Bearer establishment between MGW-1 and Target MGW + +The handling of the bearer establishment between MGW-1 and Target MGW is as described in sub-clause 6.1 for a Basic Mobile Originating Call. The MSC server shall also use the Change Flow Direction procedure to request the MGW-1 to set the Handover Device to the initial state. + +###### 8.4.2.1.2.4 MGW Flow Direction Control + +The MSC Server may perform the MGW Flow Direction Control in the following ways: + +- In accordance with the normal handover case by isolating the termination in MGW-1 towards the Target MGW (T2) from the termination to the Serving BSS (TS) and configuring the Anchor termination (TA) one-way DL towards the Target MGW termination (T2). Termination to the Serving BSS (TS) is both-way connected to Anchor termination (TA) since it is also receiving UL user data from termination to the Serving BSS (TS). The basic example in sub-clause 8.4.2.1.4 illustrates this type of functionality. + +Or: + +- The MSC-1 Server may request the MGW-1 to set termination towards Target-MGW (T2) to both-way connected to Anchor termination (TA) and isolate termination to Serving BSS (TS) completely. This improves the user plane switching and saves a signalling step to the MGW-1 at Handover Detect message. + +###### 8.4.2.1.2.5 Handover Command/Handover Detect + +When the MSC-1 server sends the Handover Command message or alternatively if it receives the Handover Detect message inside a MAP Process-Access-Signalling request, if the MSC-1 server followed the MGW control procedures for a non-LCLS call and kept the Termination to the Serving BSS connected then it shall use the Change Flow Direction procedure to requests the MGW-1 to set the Handover Device to intermediate state, however if the MSC server-1 isolated TS and set T2 to bothway then no MGW control procedure is required at this point. + +Upon receipt of the Handover Detect message the MSC Server shall send to the adjacent call node the LCLS-Status-Change Request message with the LCLS-Status-Change-Request IE set to "Indicate DL data after Handover". + +When the far end MSC server receives the LCLS-Status-Change-Request message with the LCLS-Status-Change-Request IE set to "Indicate DL data after Handover" it shall send to the BSS the LCLS\_Connect\_Control message with the LCLS-Connection-Status-Control IE indicating "DL Data\_at\_Handover" and after reception of the LCLS\_Connect\_Control acknowledge message from the BSS, return the LCLS-Status-Change-Request-Acknowledge message with "Indicate DL data after Handover" and a Result code indicating LCLS Status Change Request accepted. + +NOTE: this informs this call leg in the BSS that the other UE has left the BSS and has been detected in the new BSS and as such DL data from the CN is now coming from that UE. + +###### 8.4.2.1.2.6 Handover Complete + +When the MSC-1 Server receives the Handover Complete message, it releases the A-interface line towards BSS-1. The MSC-1 Server also requests MGW-1 to set the Handover Device to its final state by removing the bearer termination towards the BSS-1. + +After the MSC-1 Server receives the Answer message including the LCLS-Status set to LCLS feasible but not yet locally switched, MSC-1 Server shall send to the adjacent call node the LCLS-Status-Update message with the LCLS-Status IE indicating that LCLS is not established. + +##### 8.4.2.1.3 Target MSC Server / Target MGW + +###### 8.4.2.1.3.1 Prepare Handover Request message and MGW selection + +The Target MSC server selects the Target MGW when it receives Prepare Handover Request message. The Target MSC server sends the Handover Request message to the Target BSS as for the normal case but shall include the GCR IE, the LCLS-Configuration IE and the LCLS-Connection-Status-Control IE set to "Connect". + +###### 8.4.2.1.3.2 Handover Request Acknowledge + +If the Target BSS supports the LCLS feature it shall include the LCLS-BSS-Status IE in the Handover Request Acknowledge message in order to inform the Target MSC Server that the BSS supports the LCLS feature. The Target MSC Server sends the same information in the MAP Prepare Handover Response message to the MSC-1 Server. + +###### 8.4.2.1.3.3 Bearer establishment towards Target BSS + +When the Target MSC Server has selected the Target MGW it requests the Target MGW to seize a TDM circuit if AoTDM using the Reserve Circuit procedure, or an IP termination if AoIP using the reserve Connection Point procedure as for the normal handover procedure. The Target MSC Server sends the Handover Request message to the Target BSS containing the CIC for AoTDM or the IP addresses and UDP ports received from the target MGW if AoIP. + +###### 8.4.2.1.3.4 Bearer establishment between MGW-1 and Target MGW + +The handling of the bearer establishment between MGW-1 and Target MGW is as described for basic mobile terminating call in sub-clause 6.2. + +###### 8.4.2.1.3.5 LCLS Negotiation in Initial Address message + +If the Target MSC Server receives an Initial Address message that does not include a LCLS-Negotiation Request IE or includes a LCLS-Negotiation Request IE set to LCLS is not permitted, the Target MSC Server shall update the previously sent LCLS-Configuration by sending a LCLS\_CONNECT\_CONTROL message to BSS with a LCLS-Configuration IE set to LCLS-not allowed and a LCLS\_Connection\_Status\_Control IE set to "do not connect LCLS". + +##### 8.4.2.1.4 Example of Inter-MSC Handover that breaks Local Switching + +###### 8.4.2.1.4.1 Connection Model + +Figure 8.4.2.1.4.1.1 shows the network model for the Inter-MSC GSM to GSM Handover, where call leg UE-1 is handed over from BSS-1 to the Target BSS. BSS-1 is the same as BSS-2 when LCLS is established for the call. The BSS-1 is served by the MSC-Server 1, the Target BSS is served by the Target MSC-Server, and MSC-Server 1 is not the same as Target MSC-Server. The bearer termination T2 in MGW-2 is used for the bearer towards BSS-2, which is not affected by this handover. Bearer termination TS in MGW-1 is used for the bearer towards BSS-1 and the bearer terminations TA and T3 in MGW-1, T1 in MGW-2 and T4 in Target-MGW are used for the bearer towards the succeeding/preceding MGW. Bearer termination TT in Target-MGW is for the bearer termination towards the Target BSS. + +- User plane link which transmits real user plane data within BSS and to UE +- User plane link which transmits real user plane data through the CN and to UE +- - - User plane link path through CN, connected +- - - User plane uplink path through CN from Target BSS, connected +- - - Control plane link which transmits signalling + +![Diagram showing Connection Model 1: Before handover, LCLS is established. It illustrates the network architecture with BSS-1/BSS-2, MSC-1 S, MSC-2 S, MGW-1, and MGW-2. A red line shows the user plane path within the BSS. A blue dashed line shows the user plane path through the CN. A green dashed line shows the control plane path. Various bearers are labeled with terminations like T_S, T_A, T_1, T_2, T_3, T_4, and T_T.](cd48273072c5c3a23e11fde892d1b6b6_img.jpg) + +Diagram showing Connection Model 1: Before handover, LCLS is established. It illustrates the network architecture with BSS-1/BSS-2, MSC-1 S, MSC-2 S, MGW-1, and MGW-2. A red line shows the user plane path within the BSS. A blue dashed line shows the user plane path through the CN. A green dashed line shows the control plane path. Various bearers are labeled with terminations like T\_S, T\_A, T\_1, T\_2, T\_3, T\_4, and T\_T. + +Connection Model 1: Before handover, LCLS is established + +![Diagram of Connection Model 2 showing network architecture with MSCs, MGWs, and BSSs.](5a4e62bead259c258d069fd3663ea670_img.jpg) + +This diagram illustrates Connection Model 2. At the top, three MSCs are shown: MSC-1 S, MSC-2 S, and Target MSC-S. MSC-1 S and MSC-2 S are connected to MGW-1 and MGW-2 respectively. Target MSC-S is connected to Target MGW. MGW-1 has interfaces TS, TA, and T3. MGW-2 has interfaces T1 and T2. Target MGW has interfaces T4 and TT. On the left, BSS-2/BSS-1 is connected to MSC-1 S, and Target BSS is connected to Target MGW. A green dashed line encloses the MSCs and MGWs. A blue dashed line encloses the MGWs and Target BSS. A red line highlights a specific connection path within BSS-2/BSS-1. + +Diagram of Connection Model 2 showing network architecture with MSCs, MGWs, and BSSs. + +Connection Model 2: Before MSC triggers HO command to the BSS, T3 is isolated from TS, TA is one-way connected to T3 and TS is both-way connected to TA + +![Diagram of Connection Model 3 showing network architecture with additional data flow paths.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +This diagram illustrates Connection Model 3. It builds upon the architecture of Connection Model 2 but adds new data flow paths. A solid black line represents the user plane data flow, starting from BSS-2/BSS-1, passing through MGW-1, MGW-2, and then to Target MGW. Another solid black line shows data being bicast from BSS-2/BSS-1 directly to Target BSS. The green and blue dashed lines from the previous model are still present. + +Diagram of Connection Model 3 showing network architecture with additional data flow paths. + +Connection Model 3: UE-1 not yet detected in Target BSS, BSS-2 bcasts user plane data UL + +![Diagram of Connection Model 4 showing network architecture with MSC-1 S, MSC-2 S, Target MSC-S, BSS-2/BSS-1, Target BSS, MGW-1, MGW-2, and Target MGW. It illustrates a state where the Target MSC-S has not yet received a Handover (HO) Detect message.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +This diagram illustrates Connection Model 4. At the top, three MSC-S units (MSC-1 S, MSC-2 S, and Target MSC-S) are shown. Below them, three MGW units (MGW-1, MGW-2, and Target MGW) are shown. On the left, a BSS-2/BSS-1 unit and a Target BSS unit are shown. MSC-1 S is connected to MGW-1, and MSC-2 S is connected to MGW-2. Target MSC-S is connected to Target MGW. BSS-2/BSS-1 is connected to MGW-1, and Target BSS is connected to MGW-1. MGW-1 is connected to MGW-2, and MGW-2 is connected to Target MGW. A green dashed line outlines the network boundaries. A red line indicates a connection from BSS-2/BSS-1 to MGW-1. A blue dashed line indicates a connection from MGW-1 to MGW-2. A black line indicates a connection from Target BSS to MGW-1. + +Diagram of Connection Model 4 showing network architecture with MSC-1 S, MSC-2 S, Target MSC-S, BSS-2/BSS-1, Target BSS, MGW-1, MGW-2, and Target MGW. It illustrates a state where the Target MSC-S has not yet received a Handover (HO) Detect message. + +Connection Model 4: UE-1 connected to Target BSS but Target MSC-S has not received HO Detect + +![Diagram of Connection Model 5 showing network architecture similar to Model 4, but with MGW-1 rerouting the user plane so that T_A is both-way connected to T_3.](7f17c430b9598e4d748a8041457810b3_img.jpg) + +This diagram illustrates Connection Model 5. It has the same network architecture as Model 4, but with a key difference in the user plane routing. In MGW-1, the TA interface is now shown as being both-way connected to the T3 interface. The green dashed line, red line, blue dashed line, and black line connections remain the same as in Model 4. + +Diagram of Connection Model 5 showing network architecture similar to Model 4, but with MGW-1 rerouting the user plane so that T\_A is both-way connected to T\_3. + +Connection Model 5: MSC-1 instructed MGW-1 to reroute the user plane, TA is both-way connected to T3 + +![Diagram of Connection Model 6 for Inter-MSC Inter-BSS Handover. It shows MSC-1 S and MSC-2 S connected to MGW-1 and MGW-2 respectively. BSS-2 is connected to MSC-1 S. A Target BSS is connected to a Target MGW. A dashed green line outlines the active user plane path from MSC-1 S through MGW-1 to the Target MGW. MGW-1 has interfaces T3 and TA; MGW-2 has T1 and T2; Target MGW has T4 and T. The path from MGW-1 to Target MGW bypasses MGW-2.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) + +Diagram of Connection Model 6 for Inter-MSC Inter-BSS Handover. It shows MSC-1 S and MSC-2 S connected to MGW-1 and MGW-2 respectively. BSS-2 is connected to MSC-1 S. A Target BSS is connected to a Target MGW. A dashed green line outlines the active user plane path from MSC-1 S through MGW-1 to the Target MGW. MGW-1 has interfaces T3 and TA; MGW-2 has T1 and T2; Target MGW has T4 and T. The path from MGW-1 to Target MGW bypasses MGW-2. + +**Connection Model 6: Handover completed, Ts termination was removed** + +**Figure 8.4.2.1.4.1.1: Inter-MSC Inter-BSS Handover Connection Model when user plane active** + +###### **8.4.2.1.4.2 Basic Sequence for Inter-MSC handover that breaks Local Switching** + +Figures 8.4.2.1.4.2.1 and 8.4.2.1.4.2.2 show the message sequence example for the basic Inter-MSC GSM to GSM Handover shown in the corresponding network model Figure 8.4.2.1.4.1.1. The Handover Device is located in the MGW-1 selected for the call establishment by the MSC-1 Server, which controls the call and the mobility management. The description is based on 3GPP TS 23.009 [9], 3GPP TS 23.205 [2] and 3GPP TS 23.231 [3]. + +![Sequence diagram for Inter-MSC Handover that breaks LCLS when user plane active, initial phase. The diagram shows the interaction between UE-1, BSS-1, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target BSS, MSC-2 S, MGW-2, BSS-2, and UE-2. A red double-headed arrow at the top indicates that UE-1(oMS) is communicating with UE-2(tMS) via a locally switched path in the BSS. The sequence of messages includes: 1. HO Required (target LAC) from BSS-1 to MSC-1 S; 2. MAP Prepare-Handover Request (target LAC, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference) from MSC-1 S to Target MSC-S; 3a. Add request Access side T_T, reserve circuit, Connection Point from Target MSC-S to Target MGW; 3b. Add reply T_T from Target MGW to Target MSC-S; 4. Handover Request (Global Call Reference, LCLS-Configuration, LCLS-Connection-Status-Control: 'Connect') from Target MSC-S to Target BSS; 5. Handover Request Ack (LCLS-BSS-Status: 'Call not possible to be locally switched') from Target BSS to Target MSC-S; 6a. MOD request T_T, configure Connection Point, only AoIP from Target MSC-S to Target MGW; 6b. MOD reply T_T from Target MGW to Target MSC-S; 7. MAP Prepare-Handover Response from Target MSC-S to MSC-1 S; 8a. LCLS-Status-Change-Request (LCLS-Status-Change: 'LCLS-Disconnection-PreparationForHandover'), see NOTE 1 and NOTE 2 from MSC-1 S to Target MSC-S; 8b. LCLS-Connect-Control (LCLS-Connection-Status-Control = 'BicastatHandover') from Target MSC-S to Target BSS; 8c. LCLS-Connect-Control-Ack (LCLS-BSS-Status = 'Call is locally switched with requested LCLS configuration') from Target BSS to Target MSC-S; 8d. LCLS Status Change Request Acknowledge (LCLS-Status-Change = 'LCLS-Disconnection-PreparationForHandover', Result Code = 'Status Change Req. Accepted'), see NOTE 3 from Target MSC-S to MSC-1 S; 9a. TopDescr ({*, T3, isolate}, {T_A, T3, oneway}) + ADD request(T3) from MSC-1 S to MGW-1; 9b. TopDescr() + ADD reply (T3) from MGW-1 to MSC-1 S; 10. Initial Address (Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference), see NOTE 4 from MSC-1 S to MSC-2 S; 11a. Add request Network side T4 from MSC-2 S to MGW-2; 11b. Add reply T4 from MGW-2 to MSC-2 S; 12. Bearer and Codec Information (SC, ACL, LCLS-Negotiation Response, LCLS-Configuration-Preference), see NOTE 4 from MSC-2 S to MSC-1 S.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) + +Sequence diagram for Inter-MSC Handover that breaks LCLS when user plane active, initial phase. The diagram shows the interaction between UE-1, BSS-1, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target BSS, MSC-2 S, MGW-2, BSS-2, and UE-2. A red double-headed arrow at the top indicates that UE-1(oMS) is communicating with UE-2(tMS) via a locally switched path in the BSS. The sequence of messages includes: 1. HO Required (target LAC) from BSS-1 to MSC-1 S; 2. MAP Prepare-Handover Request (target LAC, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference) from MSC-1 S to Target MSC-S; 3a. Add request Access side T\_T, reserve circuit, Connection Point from Target MSC-S to Target MGW; 3b. Add reply T\_T from Target MGW to Target MSC-S; 4. Handover Request (Global Call Reference, LCLS-Configuration, LCLS-Connection-Status-Control: 'Connect') from Target MSC-S to Target BSS; 5. Handover Request Ack (LCLS-BSS-Status: 'Call not possible to be locally switched') from Target BSS to Target MSC-S; 6a. MOD request T\_T, configure Connection Point, only AoIP from Target MSC-S to Target MGW; 6b. MOD reply T\_T from Target MGW to Target MSC-S; 7. MAP Prepare-Handover Response from Target MSC-S to MSC-1 S; 8a. LCLS-Status-Change-Request (LCLS-Status-Change: 'LCLS-Disconnection-PreparationForHandover'), see NOTE 1 and NOTE 2 from MSC-1 S to Target MSC-S; 8b. LCLS-Connect-Control (LCLS-Connection-Status-Control = 'BicastatHandover') from Target MSC-S to Target BSS; 8c. LCLS-Connect-Control-Ack (LCLS-BSS-Status = 'Call is locally switched with requested LCLS configuration') from Target BSS to Target MSC-S; 8d. LCLS Status Change Request Acknowledge (LCLS-Status-Change = 'LCLS-Disconnection-PreparationForHandover', Result Code = 'Status Change Req. Accepted'), see NOTE 3 from Target MSC-S to MSC-1 S; 9a. TopDescr ({\*, T3, isolate}, {T\_A, T3, oneway}) + ADD request(T3) from MSC-1 S to MGW-1; 9b. TopDescr() + ADD reply (T3) from MGW-1 to MSC-1 S; 10. Initial Address (Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference), see NOTE 4 from MSC-1 S to MSC-2 S; 11a. Add request Network side T4 from MSC-2 S to MGW-2; 11b. Add reply T4 from MGW-2 to MSC-2 S; 12. Bearer and Codec Information (SC, ACL, LCLS-Negotiation Response, LCLS-Configuration-Preference), see NOTE 4 from MSC-2 S to MSC-1 S. + +**Figure 8.4.2.1.4.2.1: Inter-MSC Handover that breaks LCLS when user plane active, initial phase** + +1. The Handover Required message is received from BSS1 requesting an inter-MSC handover. The call is currently locally switched and the MSC-1 server can know that the Inter-MSC handover at one end will break LCLS (the local switch is not broken in the serving BSS (BSS-1) until UE-1 has moved out of the BSS-1 and the MSC-1 server sends the Clear Command message to BSS-1). +2. The MSC-1 Server determines that inter-MSC handover is required and sends MAP-Prepare-Handover Request to target MSC which includes LCLS Negotiation Request, the LCLS-Configuration-Preference and GCR IEs. +- 3a, b. The Target MSC-Server reserves circuit or Connection Point $T_T$ towards the Target BSS. +4. The Target MSC-Server sends the Handover Request message to target BSS with the GCR IE, the LCLS-Configuration IE and the LCLS-Connection-Status-Control IE indicating "connect" to through-connect the local call. +5. The Target BSS reports in Handover Request Acknowledge message that the call is not possible to be locally switched. + +- 6a, b. (These signalling steps are only applicable to AoIP) When the Target MSC-Server receives the BSSMAP Handover Request-Ack message, it sends the target BSC IP address and UDP Port number to the target MGW using the Configure RTP Connection Point procedure. +7. The Target MSC-Server sends the Prepare Handover Response message to the MSC-1 server. +- 8a. The Anchor MSC-1 server instructs the far end MSC-2 server to prepare for LCLS disconnection for Handover by sending the LCLS-Status-Change-Request message. +- 8b. The far end MSC-2 server requests BSS-2 to start sending data UL with the LCLS\_Connect\_Control message and the LCLS-Connection-Status-Control IE indicating "BicestatHandover", see Figure 8.4.2.1.4.1.1, Connection Model 3. This triggers the BSS-2 to bicast the user plane data in the same way as the Access MGW-1 would be doing in a non-LCLS inter-BSS handover. At this point the BSS-1 shall send any DL data it receives directly to the served UE. + +NOTE 1: The Serving BSS-1 shall forward the user plane data received locally from UE-1 to UE-2 while the UE-1 is served by the BSS-1. BSS-2 bcasts UL user plane data to both MGW2 and local path and MGW-2 transmits the user plane data to MGW-1 and MGW-1 transmits the user plane data to the Target BSS via the Target MGW. When the UE-1 leaves the serving BSS-1 and begins sending UL data to the Target BSS via the Target MGW, that data will then be received via the A-interface leg at the serving BSS-2. + +NOTE 2: Possible bicasting may have been activated earlier when LCLS was established in the BSS-1 /BSS-2 (not shown here) and was indicated with the LCLS-Configuration IE in step 4 and applies to both call legs. If LCLS bicasting was not activated the LCLS-Configuration value is "Connect" (i.e. no bicasting) in step 4, but the value of the LCLS-Connection-Status-Control in step 8b is "BicestatHandover", which applies only for this call leg. + +- 8c. The BSS-2 sends the LCLS\_Connect\_Control\_Ack message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration". +- 8d. MSC-2 Server sends LCLS-Status-Change-Request-Acknowledge message. + +NOTE 3: Handover sequence is independent of the LCLS-Status-Change-Request-Acknowledge message. + +- 9a, b. In accordance with normal handover the MSC-1 server requests MGW-1 to isolate the termination towards Target MGW (T3) from the termination to the Serving BSS-1 (TS) and to configure the Anchor termination (TA) one-way DL towards the Target MGW termination (T3). +10. MSC-Server 1 sends IAM (Initial Address Message) to Target MSC-Server including GCR, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. + +NOTE 4: Corresponding SIP-I signalling is specified in 3GPP TS 23.231 [3]. + +- 11a, b. Target-MSC-Server reserves bearer connection T4 towards MGW-1. +12. After Target MGW has replied with the bearer address and the binding reference, Target MSC-Server returns Bearer and Codec Information (APM) message with selected codec, available codec list, the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. + +![Sequence diagram for Inter-MSC Handover that breaks LCLS when user plane active, completion phase. The diagram shows interactions between UE-1, BSS-1, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target BSS, MSC-2 S, MGW-2, BSS-2, and UE-2. Key messages include ACM, HO CMD, HO Detect, MAP Process-Access-Signalling Request, LCLS-Status-Change-Request, TopDescr, LCLS_CONNECT_CONTROL, Handover Complete, MAP Send-End-Signalling Request, Answer, Clear Command, LCLS Status Update, and SUB request/release.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant UE-1 + participant BSS-1 + participant MSC-1 S + participant MGW-1 + participant Target MSC-S + participant Target MGW + participant Target BSS + participant MSC-2 S + participant MGW-2 + participant BSS-2 + participant UE-2 + + Note right of MSC-1 S: 13. ACM, see NOTE 3 + MSC-1 S->>BSS-1: 14. HO CMD + BSS-1->>UE-1: 15. HO CMD + Target BSS->>Target MGW: 16. HO Detect + Target MGW->>MSC-1 S: 17. MAP Process-Access-Signalling Request + Note right of MSC-1 S: 17a. LCLS-Status-Change-Request (LCLS-Status-Change: "IndicatedDLdataAfterHandover") + MSC-1 S->>MSC-2 S: 17a. LCLS-Status-Change-Request (LCLS-Status-Change: "IndicatedDLdataAfterHandover") + Note right of MSC-2 S: 17b. LCLS_CONNECT_CONTROL (LCLS-Connection-Status-Control = "DLDataAtHandover") + MSC-2 S->>BSS-2: 17b. LCLS_CONNECT_CONTROL (LCLS-Connection-Status-Control = "DLDataAtHandover") + Note right of BSS-2: 17c. LCLS_CONNECT_CONTROL Ack (LCLS-BSS-Status "the call is locally switched with requested LCLS configuration") + BSS-2->>MSC-2 S: 17c. LCLS_CONNECT_CONTROL Ack (LCLS-BSS-Status "the call is locally switched with requested LCLS configuration") + Note right of MSC-1 S: 18a. TopDescr, change flow direction ({TA, TS, oneway}, {TA, TS, bothway}) + MSC-1 S->>MGW-1: 18a. TopDescr, change flow direction ({TA, TS, oneway}, {TA, TS, bothway}) + Note right of MGW-1: 18b. TopDescr reply + MGW-1->>MSC-1 S: 18b. TopDescr reply + Note right of MSC-1 S: 17d. LCLS-Status-Change-Request Ack (LCLS-Status-Change: "IndicatedDLdataAfterHandover", Result Code="Status Change Req Accepted") + MSC-1 S->>Target MSC-S: 17d. LCLS-Status-Change-Request Ack (LCLS-Status-Change: "IndicatedDLdataAfterHandover", Result Code="Status Change Req Accepted") + Note right of Target MSC-S: 19. Handover Complete (LCLS-BSS-Status: "Call not possible to be locally switched") + Target MSC-S->>Target BSS: 19. Handover Complete (LCLS-BSS-Status: "Call not possible to be locally switched") + Target BSS->>MSC-1 S: 20. MAP Send-End-Signalling Request + Note right of MSC-1 S: 21. Answer (LCLS-Status: "LCLS not connected") + MSC-1 S->>Target BSS: 21. Answer (LCLS-Status: "LCLS not connected") + Note right of BSS-2: Break local switching + BSS-2->>MSC-2 S: Break local switching + Note right of MSC-2 S: 24. LCLS-Notification (LCLS-BSS-Status: "Call is no longer locally switched") + MSC-2 S->>MSC-1 S: 24. LCLS-Notification (LCLS-BSS-Status: "Call is no longer locally switched") + Note right of MSC-1 S: 23. LCLS Status Update (LCLS-Status: "LCLS not connected"), see NOTE 6 + MSC-1 S->>MSC-2 S: 23. LCLS Status Update (LCLS-Status: "LCLS not connected"), see NOTE 6 + MSC-1 S->>BSS-1: 22. Clear Command + BSS-1->>UE-1: 25. Clear Complete + Note right of MSC-1 S: 26a. SUB request, release TS + MSC-1 S->>MGW-1: 26a. SUB request, release TS + Note right of MGW-1: 26b. SUB reply + MGW-1->>MSC-1 S: 26b. SUB reply + +``` + +Sequence diagram for Inter-MSC Handover that breaks LCLS when user plane active, completion phase. The diagram shows interactions between UE-1, BSS-1, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target BSS, MSC-2 S, MGW-2, BSS-2, and UE-2. Key messages include ACM, HO CMD, HO Detect, MAP Process-Access-Signalling Request, LCLS-Status-Change-Request, TopDescr, LCLS\_CONNECT\_CONTROL, Handover Complete, MAP Send-End-Signalling Request, Answer, Clear Command, LCLS Status Update, and SUB request/release. + +**Figure 8.4.2.1.4.2.2: Inter-MSC Handover that breaks LCLS when user plane active, completion phase** + +13. The Target MSC-Server sends ACM (Address Complete Message). Target MSC-Server awaits the capturing of the UE-1 on the radio path when the ACM is sent and the Anchor MSC-1 server initiates the handover execution when receiving ACM. + +14. MSC-1 server sends Handover Command message to BSS-1. + +15. BSS-1 sends Handover Command message to UE-1. BSS-1 will discard incoming user plane data send to UE-1 received from CN. If BSS-2 was not instructed to prepare for LCLS related handover in Step 8a, the BSS-2 starts bi-casting UP user plane data generated by UE-2 to local path and A interface and also starts to check whether there is incoming DL user plane data from the core network. + +NOTE 5: there is no situation where BSS-2 will receive real DL user plane data from the CN at the same time as it receives local data from UE-1 as part of the handover. + +16. UE-1 is detected at target BSS. But still no UL data can be sent from target BSS to MGW-1 because $T_A-T_3$ is one-way DL only. MGW-1 will continue to transmit DL user plane data to the target BSS-1. BSS-2 continues to bi-cast user plane data to both local path and to the A interface. 17. Target MSC-Server sends MAP-Process-Access-Signal request to the MSC-1 server. + +- 17a. The MSC-1 Server sends LCLS-Status-Change-Request to indicate that UE-1 has been detected in the target BSS and user data is now being sent through the CN and DL to the distant UE-2 +- 17b. The MSC-2 Server shall signal to the BSS-2 that DL data received from the CN is now real user data coming from the UE-1. +- 17c. The BSS-2 sends the LCLS\_Connect\_Control\_Ack message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration". +- 17d. Acknowledgement back through the CN that the indication for DL data after Handover Detect has been delivered. +- 18a, b. The MSC-1 server uses the Change Flow Direction procedure to request the MGW-1 to set the Handover Device to intermediate state and $T_A-T_3$ to both-way configuration. When BSS-2 finds out there is DL user plane data, BSS-2 will transmit the DL user plane data to UE-2. +19. Handover Complete message is received from target BSS with LCLS-BSS-status indicating that the call cannot be locally switched. +20. A Handover-Detect/Complete when received is included in the MAP SendEndSignalling Request message sent to the MSC-1 server. +21. Target MSC-Server sends ANSWER message with the LCLS-status when a Handover-Detect/Complete is received. +22. MSC-1 server informs BSS-1 to clear the old call leg. +23. MSC-1 server sends LCLS Status Update message with LCLS status "LCLS not connected" to MSC-2 server. +- NOTE 6: When BICC is used as the call control protocol the APM message is sent. When SIP-I is used the INFO request with the encapsulated APM message is sent. +24. Serving BSS-2 informs MSC-2 server that LCLS is broken via LCLS-Notification message. +- NOTE 7: There is no need to send LCLS-Notification message from BSS-1 after receiving the Clear Command message since Clear Complete indicates that LCLS was disconnected. +25. BSS-1 informs MSC-1 server that the resource for the UE-1 has been released and BSS-2 stops bi-casting. +- 26a, b. The MSC-1 server requests MGW-1 to set the Handover Device to its final state by removing the bearer termination $T_S$ towards BSC-1 using the Release Termination procedure. + +#### 8.4.2.2 Inter-MSC GSM to GSM Handover that establishes Local Switching + +##### 8.4.2.2.1 General + +When LCLS is not established for a call and an inter-MSC handover occurs that makes the call local, the call should be locally switched in the BSS. The Inter-MSC handover procedures specified in 3GPP TS 23.009 [9], 3GPP TS 23.205 [2] and 3GPP TS 23.231 [3] shall be followed. The following clauses describe the additional requirements for inter-MSC handovers that establish LCLS and the differences compared to Inter-MSC handovers that break LCLS are identified. + +##### 8.4.2.2.2 MSC-1 / MGW-1 + +###### 8.4.2.2.2.1 Handover Required + +When MSC-1 Server receives the Handover Required message from the serving BSS and determines that the call shall be handed over to the Target MSC Server, it shall send the GCR of the call, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE to the Target MSC Server in a MAP Prepare-Handover\_Request message. + +###### 8.4.2.2.2.2 Handover Request Acknowledge + +When MSC-1 Server receives the MAP Prepare\_Handover\_Response including Handover\_Request\_Acknowledgement message with a LCLS-BSS-Status IE the Anchor MSC-1 Server configures the bearer terminations in MGW-1 and + +sends the GCR IE, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE to the target MSC-Server. + +##### 8.4.2.2.2.3 Bearer establishment between MGW-1 and Target MGW + +The handling of the bearer establishment between MGW-1 and Target MGW is as described in sub-clause 6.1 for a Basic Mobile Originating Call. The MSC server shall also use the Change Flow Direction procedure to request the MGW-1 to set the Handover Device to the initial state. + +###### 8.4.2.2.2.4 MGW Flow Direction Control + +In accordance with the normal handover case the MGW-1 isolates the termination towards the Target MGW (T2) from the termination to the Serving BSS (TS) and configures the Anchor termination (T1) one-way DL towards the Target MGW termination (T2). Termination to the Serving BSS (TS) is both-way connected to Anchor termination (T1) since it is also receiving UL user data from termination to the Serving BSS (TS). + +###### 8.4.2.2.2.5 Handover Command/Handover Detect + +The MSC-1 Server shall use the Change Flow Direction procedure to requests the MGW-1 to set the Handover Device to intermediate state. + +###### 8.4.2.2.2.6 Handover Complete + +When the MSC-1 Server receives the Handover Complete message, it releases the A-interface line towards BSS-1. The MSC-1 Server also requests MGW-1 to set the Handover Device to its final state by removing the bearer termination towards the BSS-1. + +When LCLS has been established during the handover procedure, the target BSS informs the target MSC-Server that the call has been locally switched in the Handover Complete message, + +##### 8.4.2.2.3 Target MSC Server / Target MGW + +##### 8.4.2.2.3.1 Prepare Handover Request message and MGW selection + +The Target MSC server selects the Target MGW when it receives Prepare Handover Request message. The Target MSC server sends the Handover Request message to the Target BSS as for the normal case but shall include the GCR IE, the LCLS-Configuration IE and the LCLS-Connection-Status-Control IE set to "Connect". + +##### 8.4.2.2.3.2 Handover Request Acknowledge + +If the Target BSS supports the LCLS feature it shall include the LCLS-BSS-Status IE in the Handover Request Acknowledge message in order to inform the Target MSC Server that the BSS supports the LCLS feature. The Target MSC Server sends the same information in the MAP Prepare Handover Response message to the MSC-1 Server. + +##### 8.4.2.2.3.3 Bearer establishment towards Target BSS + +When the Target MSC Server has selected the Target MGW it requests the Target MGW to seize a TDM circuit if AoTDM using the Reserve Circuit procedure, or an IP termination if AoIP using the reserve Connection Point procedure as for the normal handover procedure. The Target MSC Server sends the Handover Request message to the Target BSS containing the CIC for AoTDM or the IP addresses and UDP ports received from the target MGW if AoIP. + +##### 8.4.2.2.3.4 Bearer establishment between MGW-1 and Target MGW + +The handling of the bearer establishment between MGW-1 and Target MGW is as described for basic mobile terminating call in sub-clause 6.2. + +##### 8.4.2.2.3.5 LCLS Negotiation in Initial Address message + +If the Target MSC Server receives an Initial Address message that does not include a LCLS-Negotiation Request IE or includes a LCLS-Negotiation Request IE set to LCLS is not permitted, the Target MSC Server shall update the previously sent LCLS-Configuration by sending a LCLS\_CONNECT\_CONTROL message to BSS with a LCLS-Configuration IE set to LCLS-not allowed and a LCLS\_Connection\_Status\_Control IE set to "do not connect LCLS". The inter-MSC handover continues as described in sub-clause 8.4.2.3 Inter-MSC Handover that leaves a not locally Switched Call unchanged. + +##### 8.4.2.2.4 Example of Inter-MSC Handover that establishes Local Switching + +###### 8.4.2.2.4.1 Connection Model + +Figure 8.4.2.2.4.1.1 shows the network model for the Basic Inter-MSC GSM to GSM handover when LCLS is established as a result of the handover. The dashed line in green represents call control signalling and the dashed line in blue represents the user plane connection path via the core network, which should be used if LCLS is not established or after LCLS is broken. The non-dotted lines represent the bearer carrying real user plane data. In MGW-1 the bearer termination TS is used for the bearer towards BSS-1, bearer termination TA is used for the bearer towards the succeeding/preceding MGW, that is MGW-2 and bearer termination T3 is used towards the Target MGW. In MGW-2 the bearer termination T2 is used for the bearer towards BSS-2 and bearer termination T1 is used for the bearer towards MGW-1. In Target-MGW the bearer termination TT is used towards the Target-BSS and bearer termination T4 is used towards MGW-1. + +In this example scenario the Handover Device is located in MGW-1 selected for the call establishment by the MSC-1 server, which controls the call and mobility management. + +- ━━━━ User plane link which transmits real user plane data within BSS and to UE +- ━━━━ User plane link which transmits real user plane data through the CN and to UE +- - - - User plane link path through CN, connected +- - - - Control plane link which transmits signalling + +![Diagram showing the network configuration 'Before Handover'. It includes BSS-1, BSS-2, Target BSS, MSC-1 S, MSC-2 S, Target MSC-S, MGW-1, MGW-2, and Target MGW. MGW-1 has terminations T_S, T_A, and T_3. MGW-2 has T_1 and T_2. Target MGW has T_4 and T_T. Solid lines represent user plane data paths, and dashed green lines represent control plane signalling paths.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) + +Diagram showing the network configuration 'Before Handover'. It includes BSS-1, BSS-2, Target BSS, MSC-1 S, MSC-2 S, Target MSC-S, MGW-1, MGW-2, and Target MGW. MGW-1 has terminations T\_S, T\_A, and T\_3. MGW-2 has T\_1 and T\_2. Target MGW has T\_4 and T\_T. Solid lines represent user plane data paths, and dashed green lines represent control plane signalling paths. + +**Before Handover** + +![Diagram showing the network configuration 'During Handover'. The state has changed from the 'Before Handover' state. MGW-1's termination T_3 is now isolated. MGW-1's termination T_A is now one-way connected to T_3. The user plane path (solid lines) and control plane path (dashed green lines) have been reconfigured to reflect these changes.](327ba94498e3381cf08eb41e3fd3d77f_img.jpg) + +Diagram showing the network configuration 'During Handover'. The state has changed from the 'Before Handover' state. MGW-1's termination T\_3 is now isolated. MGW-1's termination T\_A is now one-way connected to T\_3. The user plane path (solid lines) and control plane path (dashed green lines) have been reconfigured to reflect these changes. + +**During Handover, T3 is isolated from TS, TA is one-way connected to T3** + +![Network model diagram for Basic Inter-MSC GSM to GSM Handover. It shows three MSC servers (MSC-1 S, MSC-2 S, Target MSC-S) connected to three MGWs (MGW-1, MGW-2, Target MGW). MGW-1 is connected to BSS-2 and Target BSS. MGW-2 is connected to MSC-2 S. Target MGW is connected to Target MSC-S. A red line indicates the call path from MSC-1 S through MGW-1 to Target BSS. A green dashed line shows the signaling path from MSC-1 S through MSC-2 S to Target MSC-S. A blue dashed line shows the signaling path from MSC-1 S through MGW-1 to Target MGW.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +Network model diagram for Basic Inter-MSC GSM to GSM Handover. It shows three MSC servers (MSC-1 S, MSC-2 S, Target MSC-S) connected to three MGWs (MGW-1, MGW-2, Target MGW). MGW-1 is connected to BSS-2 and Target BSS. MGW-2 is connected to MSC-2 S. Target MGW is connected to Target MSC-S. A red line indicates the call path from MSC-1 S through MGW-1 to Target BSS. A green dashed line shows the signaling path from MSC-1 S through MSC-2 S to Target MSC-S. A blue dashed line shows the signaling path from MSC-1 S through MGW-1 to Target MGW. + +**After Handover, LCLS is established and both call legs are in Target BSS (=BSS-2)** + +**Figure 8.4.2.2.4.1.1: Basic Inter-MSC GSM to GSM Handover (network model)** + +###### **8.4.2.2.4.2 Basic Sequence for Inter-MSC GSM to GSM Handover that establishes Local Switching** + +Figures 8.4.2.2.4.2.1 and 8.4.2.2.4.2.2 show the message sequence example for the Basic Inter-MSC GSM to GSM Handover shown in the corresponding network model Figure 8.4.2.2.4.1.1. The Handover Device is located in MGW-1 selected for the call establishment by the MSC-1 server, which controls the call and the mobility management. The description is based on 3GPP TS 23.009 [9], 3GPP TS 23.205 [2] and 3GPP TS 23.231 [3]. + +![Sequence diagram showing the initial phase of Inter-MSC Handover establishing Local Switching. The diagram illustrates the interaction between UE-1, BSS-1, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target BSS, MSC-2 S, MGW-2, BSS-2, and UE-2. The process starts with a Handover Required message from BSS-1 to MSC-1 S. MSC-1 S sends a MAP Prepare-Handover Request to Target MSC-S. Target MSC-S sends an Add request to Target BSS. Target BSS responds with an Add reply. Target MSC-S sends a Handover Request to Target BSS. Target BSS responds with a HO Request Ack. Target BSS sends an LCLS_NOTIFICATION to MSC-2 S. MSC-2 S sends an LCLS_CONNECT_CONTROL to Target BSS. Target BSS responds with an LCLS_CONNECT_CONTROL_ACK. Target MSC-S sends a MAP Prepare-Handover Response to MSC-1 S. MSC-1 S sends a TopDescr to Target MGW. Target MGW responds with a TopDescr(). Target MSC-S sends an IAM to MSC-1 S. MSC-1 S sends an Add request to Target MGW. Target MGW responds with an Add reply. MSC-1 S sends an APM to Target MSC-S.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) + +UE-1 (oMS) is communicating with UE-2 (tMS) via the core network + +1. HO Required (target LAC) + +2. MAP Prepare-Handover Request (target LAC, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference) + +3a. Add request Access side TT reserve circuit, Connection Point + +3b. Add reply TT + +4. Handover Request (GCR, LCLS-Configuration, LCLS-Connection-Status-Control = "Connect") + +5. HO Request Ack (LCLS-BSS-Status: "Call not yet locally switched") + +5a. LCLS\_NOTIFICATION (LCLS-BSS-Status: "Call not yet locally switched") + +6a. MOD request TT, configure Connection Point, only AoIP + +6b. MOD reply TT + +IF call has been answered and MSC permits LCLS to be connected then update the Connection Status in BSS + +7. MAP Prepare-Handover Response + +8a. TopDescr ({\*, T3, isolate}, {TA, T3 oneway}) + ADD request(T3) + +8b. TopDescr() + ADD reply (T3) + +5b. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "Connect") + +5c. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status: "Call not yet locally switched") + +9. IAM (Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference), see NOTE 1, NOTE 2 + +10a. Add request Network side T4 + +10b. Add reply T4 + +11. APM (SC, SCL, LCLS-Negotiation Response, LCLS-Configuration-Preference), see NOTE 1 + +Sequence diagram showing the initial phase of Inter-MSC Handover establishing Local Switching. The diagram illustrates the interaction between UE-1, BSS-1, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target BSS, MSC-2 S, MGW-2, BSS-2, and UE-2. The process starts with a Handover Required message from BSS-1 to MSC-1 S. MSC-1 S sends a MAP Prepare-Handover Request to Target MSC-S. Target MSC-S sends an Add request to Target BSS. Target BSS responds with an Add reply. Target MSC-S sends a Handover Request to Target BSS. Target BSS responds with a HO Request Ack. Target BSS sends an LCLS\_NOTIFICATION to MSC-2 S. MSC-2 S sends an LCLS\_CONNECT\_CONTROL to Target BSS. Target BSS responds with an LCLS\_CONNECT\_CONTROL\_ACK. Target MSC-S sends a MAP Prepare-Handover Response to MSC-1 S. MSC-1 S sends a TopDescr to Target MGW. Target MGW responds with a TopDescr(). Target MSC-S sends an IAM to MSC-1 S. MSC-1 S sends an Add request to Target MGW. Target MGW responds with an Add reply. MSC-1 S sends an APM to Target MSC-S. + +**Figure 8.4.2.2.4.2.1: Initial phase of Inter-MSC Handover establishing Local Switching** + +1. Handover Required message is received from BSS-1 requesting an inter-MSC handover. The call is currently not locally switched. +2. The MSC-1 server determines that inter-MSC handover is required and sends the Pre-Handover Request message to target MSC-Server which includes LCLS Negotiation Request, the LCLS-Configuration-Preference and GCR IEs and GCR. +- 3a, b. Target-MSC-Server reserves circuit or Connection Point towards the Target-BSS +4. Target MSC-Server sends Handover request message to target BSS with GCR and instructs the BSS to prepare to connect LCLS. The LCLS-Configuration IE can instruct the BSS to bi-cast user plane data, if applicable. +5. Target BSS performs call leg correlation with GCR to find if another call leg is active with same GCR. The BSS reports in Handover Request Acknowledge message that the local call was found but LCLS is not yet established. +- 5a. The BSS-2 notifies MSC-2 server the LCLS status is changed by sending the LCLS\_Notification message with the LCLS-BSS-Status IE set to "Call not yet locally switched". + +- 5b. If the call has been answered and MSC-2 server permits LCLS to be connected, then the MSC-2 server sends to the BSS-2 the LCLS\_Connect\_Control message with the LCLS-Connection-Status-Control IE set to "connect". +- 5c. The BSS-2 returns the LCLS\_Connect\_Control\_ACK message with the LCLS-BSS-Status IE set to "Call not yet locally switched". +- 6a, b. (These signalling steps are only applicable to AoIP.) When the Target MSC-Server receives the BSSMAP Handover Request-Ack message, it sends the BSC-B IP address and UDP Port number to the MGW-B using the Configure RTP Connection Point procedure. +7. The Target MSC-Server sends the Prepare Handover Response message to MSC-1 server. +- 8, b. In accordance with normal handover the MSC-1 server requests MGW-1 to isolate the termination towards Target MGW ( $T_3$ ) from the termination to the Serving BSS-1 ( $T_S$ ) and to configure the Anchor termination ( $T_A$ ) one-way DL towards the Target MGW termination ( $T_3$ ). +9. MSC-Server 1 sends IAM (Initial Address Message) to Target MSC-Server including GCR, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. + +NOTE 1: Corresponding SIP-I signalling is specified in 3GPP TS 23.231 [3]. + +NOTE 2: The LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE in step 9 can be different from LCLS Negotiation Request IE and the LCLS-Configuration-Preference IE in step 2, because step 9 is BICC signalling and the IE values can be changed by intermediate MSC-Servers. + +- 10a, b. Target MSC-Server reserves bearer connection $T_4$ towards MGW-1. + +11. After Target MGW has replied with the bearer address and the binding reference (Step 10b), the Target MSC-Server returns the Bearer and Codec Information (APM) message with selected codec, available codec list and the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. + +![Sequence diagram showing the completion phase of Inter-MSC Handover establishing Local Switching. The diagram involves 11 lifelines: UE-1, BSS-1, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target BSS, MSC-2 S, MGW-2, BSS-2, and UE-2. The sequence of messages is as follows: 12. ACM (see NOTE 1) from Target MSC-S to MSC-1 S; 13. HO CMD from MSC-1 S to BSS-1; 14. HO Detect from Target BSS to Target MSC-S; 15. MAP Process-AccessSignalling Request from Target MSC-S to MSC-1 S; 16a. TopDescr, change flow direction from MSC-1 S to MGW-1; 16b. TopDescr reply from MGW-1 to MSC-1 S; 17. Handover Complete (LCLS-BSS-Status: 'Call is locally switched with requested LCLS configuration') from Target BSS to Target MSC-S; 18. LCLS-Notification (LCLS-BSS-Status: 'Call is locally switched with requested LCLS configuration') from Target MSC-S to MSC-2 S; 19. MAP Send-End-Signalling Request from MSC-1 S to Target MSC-S; 20. Answer (LCLS-Status: 'LCLS Connected') from Target MSC-S to MSC-1 S; 21. Clear Command from MSC-1 S to BSS-1; 22. LCLS Status Update (LCLS-Status: 'LCLS Connected'), see NOTE 3 from MSC-1 S to MSC-2 S; 23. Clear Complete from BSS-1 to MSC-1 S; 24a. SUB request, release Ts from MSC-1 S to MGW-1; 24b. SUB reply from MGW-1 to MSC-1 S; 25. Local Switching in BSS (indicated by a red double-headed arrow between Target BSS and BSS-2).](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) + +Sequence diagram showing the completion phase of Inter-MSC Handover establishing Local Switching. The diagram involves 11 lifelines: UE-1, BSS-1, MSC-1 S, MGW-1, Target MSC-S, Target MGW, Target BSS, MSC-2 S, MGW-2, BSS-2, and UE-2. The sequence of messages is as follows: 12. ACM (see NOTE 1) from Target MSC-S to MSC-1 S; 13. HO CMD from MSC-1 S to BSS-1; 14. HO Detect from Target BSS to Target MSC-S; 15. MAP Process-AccessSignalling Request from Target MSC-S to MSC-1 S; 16a. TopDescr, change flow direction from MSC-1 S to MGW-1; 16b. TopDescr reply from MGW-1 to MSC-1 S; 17. Handover Complete (LCLS-BSS-Status: 'Call is locally switched with requested LCLS configuration') from Target BSS to Target MSC-S; 18. LCLS-Notification (LCLS-BSS-Status: 'Call is locally switched with requested LCLS configuration') from Target MSC-S to MSC-2 S; 19. MAP Send-End-Signalling Request from MSC-1 S to Target MSC-S; 20. Answer (LCLS-Status: 'LCLS Connected') from Target MSC-S to MSC-1 S; 21. Clear Command from MSC-1 S to BSS-1; 22. LCLS Status Update (LCLS-Status: 'LCLS Connected'), see NOTE 3 from MSC-1 S to MSC-2 S; 23. Clear Complete from BSS-1 to MSC-1 S; 24a. SUB request, release Ts from MSC-1 S to MGW-1; 24b. SUB reply from MGW-1 to MSC-1 S; 25. Local Switching in BSS (indicated by a red double-headed arrow between Target BSS and BSS-2). + +**Figure 8.4.2.2.4.2.2: Completion phase of Inter-MSC Handover establishing Local Switching** + +12. Target MSC-Server sends ACM (Address Complete Message). Target MSC-Server awaits the capturing of the UE-1 on the radio path when the ACM is sent and MSC-1 server initiates the handover execution when receiving ACM. +- 13 - 18. When the local switching has been established during the handover procedure, the target BSS shall inform the target MSC-Server that the call has been locally switched in Handover Complete message, and the target BSS shall also send a new message LCLS-Notification with LCLS-BSS-Status IE to inform the MSC-2 server that the local switching has been established. In steps 16a and 16b the MSC-1 server configures MGW-1 for the completion of the handover. +19. A Handover-Detect/Complete when received is included in the MAP-Send-End-Signalling request and sent back to the MSC-1 server. +20. Target MSC-Server sends ANSWER message with the LCLS-status when A-HO-DETECT/COMPLETE is received. +21. MSC-Server 1 clears the call in BSS-1. +22. MSC-1 server (Anchor MSC-Server) sends LCLS-Status-Update message to the far end MSC-2 server. + + +NOTE 3: When BICC is used as the call control protocol the APM message is sent. When SIP-I is used the INFO request with the encapsulated APM message is sent. +23. BSS-1 informs MSC-1 server that the resource for the UE-1 has been released +- 24a, b. MSC-1 server releases the bearer termination towards BSS-1. +25. Local switching is established in the BSS. + +#### 8.4.2.3 Inter-MSC Handover that leaves a not Locally Switched Call unchanged + +In this scenario it is assumed that LCLS was not established before the Inter-MSC handover. When one call leg is handed over to another MSC-Server, the call still remains not local. LCLS cannot be established for the call and the LCLS status of the call is not changed. + +For the Anchor MSC-1 server and Target MSC server this Inter-MSC handover is similar to the Inter-MSC handover that establishes LCLS as described in sub-clause 8.4.2.2.4.2 until Step 5, but in this case in Step 5 the Target BSS sends the Handover Request ACK message, where the LCLS-BSS-Status IE indicates that the call is not possible to be locally switched since the GCR correlation will indicate that the call is not local. Steps 5a, 5b, 5c will not be triggered. The handover procedure is completed as for a non-local call, LCLS is not established and the LCLS Status in the core network is not changed. + +### 8.4.3 Subsequent Inter-MSC GSM to GSM Handover back to the Anchor MSC + +The basic Inter-MSC GSM to GSM handover procedure as specified in this specification shall be applied. + +### 8.4.4 Subsequent GSM to GSM Handover to a third MSC + +The basic GSM to GSM handover procedure as specified in this specification shall be applied. + +### 8.4.5 BSS Internal Handover + +#### 8.4.5.1 General + +The following procedures describe the specific handling compared to the basic principles described in 3GPP TS 23.205 [2] sub-clause 8.4.5 to achieve BSS Internal Handover with LCLS for an A-interface User Plane over IP (AoIP). + +If the call is not locally switched but both call legs have been correlated and an internal handover occurs that makes the call local, the call should be locally switched in the BSS. + +If a call is currently locally switched and an internal handover occurs that makes the call not local, the local switching should be broken in the BSS and the user plane data shall be connected through the core network. + +NOTE1: For A-interface User Plane over TDM (AoTDM), a BSS internal handover that results in LCLS break will trigger a BSS Initiated LCLS Break according to procedures in sub-clause 7.2.2. + +If an internal handover procedure occurs that does not modify the LCLS status of a call, the local switching should not be modified within the BSS. + +#### 8.4.5.2 Internal Handover Required + +If the MSC Server accepts the Internal Handover Required message it shall send an Internal Handover Command message to the BSS. If the call is currently locally switched in the BSS, the MSC Server shall also signal LCLS-Status-Change Request message containing LCLS-Status-Change IE set to "LCLS Disconnection Preparation for Handover" through the core network to enable UL bi-casting during handover. + +The MSC Server shall not wait for the LCLS-Status-Change Request Acknowledge message before proceeding with the Internal Handover. + +#### 8.4.5.3 Internal Handover Command + +If local switching is permitted by the core network and the MSC Server has not previously requested that the BSS should connect the local call, (e.g. no previous LCLS-Connection-Status-Control = "Connect"), the MSC Server shall include the LCLS-Connection-Status-Control IE indicating "Connect" in the Internal Handover Command message. + +Otherwise, the MSC Server shall send the Internal Handover Command message according to the procedures in 3GPP TS 48.008 [7]. + +#### 8.4.5.4 Handover Complete + +The BSS sends Handover Complete message including the LCLS-BSS-Status that indicates whether the call is locally switched (e.g. "Call is Locally Switched with requested LCLS configuration " or "the call is no longer locally switched"). + +The MSC server shall send to an adjacent call node the LCLS-Status-Update message with the LCLS-Status IE indicating the new LCLS Status (e.g. "LCLS connected" or "LCLS Not Connected"). + +#### 8.4.5.5 Example BSS Internal Handover that Establishes Local Switching + +##### 8.4.5.5.1 Connection Model + +Figure 8.4.5.5.1.1 shows the network model for the Intra-MSC BSS Internal Handover, where the call leg pertinent to the UE-1 is handed over from the serving BSS-1 to BSS-2. BSS-1 is the same as BSS-2 for BSS Internal Handover. The bearer termination T2 is used for the bearer towards BSS-2, which is not affected by this handover. Bearer termination TS is used for the bearer towards BSS-1 and the bearer terminations T1 and TA are used for the bearer towards the succeeding/preceding MGW. Bearer termination TT is for the bearer termination towards the BSS after internal handover. The colours and line types used in the figure are defined differently from 3GPP TS 23.205 [2] to indicate LCLS specific issues. + +- User plane link which transmits real user plane data within the BSS and to UEs +- User plane link which transmits real user plane data through the CN and to UEs +- ... User plane path through the CN, connected +- - - Control plane link which transmits signalling + +![Diagram showing the network model for Intra-MSC BSS Internal Handover. It includes UE-1, UE-2, BSS-1/BSS-2, MSC-S-1, MSC-S-2, MGW-1, and MGW-2. UE-1 is connected to BSS-1/BSS-2. UE-2 is connected to BSS-1/BSS-2. BSS-1/BSS-2 is connected to MSC-S-1. MSC-S-1 is connected to MGW-1. MGW-1 is connected to MGW-2. MGW-2 is connected to MSC-S-2. MSC-S-2 is connected to BSS-1/BSS-2. Control signalling is shown between UE-1 and MSC-S-1, and between MSC-S-1 and MSC-S-2. Non-LCLS User Plane Data is shown between MGW-1 and MGW-2.](dd380ccd5aca1151074fede04826f1a4_img.jpg) + +The diagram illustrates the network architecture for an Intra-MSC BSS Internal Handover. On the left, two User Equipment (UE) units, UE-1 and UE-2, are connected to a combined Base Station (BSS) unit labeled 'BSS-1/ BSS-2'. UE-1 is shown with a connection to the BSS, and UE-2 is also connected. The BSS is connected to an MSC server labeled 'MSC-S-1'. 'MSC-S-1' is connected to a Media Gateway labeled 'MGW-1'. 'MGW-1' has two bearer terminations, TS and TA, and is connected to another Media Gateway labeled 'MGW-2'. 'MGW-2' has two bearer terminations, T1 and T2, and is connected to another MSC server labeled 'MSC-S-2'. 'MSC-S-2' is also connected to the 'BSS-1/ BSS-2' unit. A thick black line represents the 'Non-LCLS User Plane Data' path, connecting UE-1 through the BSS, MSC-S-1, MGW-1, MGW-2, and MSC-S-2. A dashed green line represents 'Control Signalling', connecting UE-1 to MSC-S-1 and MSC-S-1 to MSC-S-2. The text 'Before Handover' is placed near the BSS unit. + +Diagram showing the network model for Intra-MSC BSS Internal Handover. It includes UE-1, UE-2, BSS-1/BSS-2, MSC-S-1, MSC-S-2, MGW-1, and MGW-2. UE-1 is connected to BSS-1/BSS-2. UE-2 is connected to BSS-1/BSS-2. BSS-1/BSS-2 is connected to MSC-S-1. MSC-S-1 is connected to MGW-1. MGW-1 is connected to MGW-2. MGW-2 is connected to MSC-S-2. MSC-S-2 is connected to BSS-1/BSS-2. Control signalling is shown between UE-1 and MSC-S-1, and between MSC-S-1 and MSC-S-2. Non-LCLS User Plane Data is shown between MGW-1 and MGW-2. + +Connection Model 1: Before BSS Internal Handover - Call is not locally switched + +![Diagram of Connection Model 2: During BSS Internal Handover. It shows two User Equipment (UE) units, UE-1 and UE-2, connected to a Base Station Subsystem (BSS) containing BSS-1/ and BSS-2. UE-1 is being handed over from BSS-1/ to BSS-2. Control signaling is shown as green dashed lines connecting the BSS to MSC-S-1 and MSC-S-2. MSC-S-1 and MSC-S-2 are connected to Media Gateway 1 (MGW-1) and MGW-2 respectively. MGW-1 has three ports: Serving (T_S), Anchor (T_A), and Target (T_T). MGW-2 has two ports: T_1 and T_2. Non-LCLS User Plane Data is shown as a thick black line from MGW-2 to the BSS. During handover, data flows from MGW-2 to MGW-1 (T_1 to T_S), then from MGW-1 (T_A to T_T) to the BSS. A legend defines T_S = Serving, T_A = Anchor, T_T = Target.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +Diagram of Connection Model 2: During BSS Internal Handover. It shows two User Equipment (UE) units, UE-1 and UE-2, connected to a Base Station Subsystem (BSS) containing BSS-1/ and BSS-2. UE-1 is being handed over from BSS-1/ to BSS-2. Control signaling is shown as green dashed lines connecting the BSS to MSC-S-1 and MSC-S-2. MSC-S-1 and MSC-S-2 are connected to Media Gateway 1 (MGW-1) and MGW-2 respectively. MGW-1 has three ports: Serving (T\_S), Anchor (T\_A), and Target (T\_T). MGW-2 has two ports: T\_1 and T\_2. Non-LCLS User Plane Data is shown as a thick black line from MGW-2 to the BSS. During handover, data flows from MGW-2 to MGW-1 (T\_1 to T\_S), then from MGW-1 (T\_A to T\_T) to the BSS. A legend defines T\_S = Serving, T\_A = Anchor, T\_T = Target. + +Connection Model 2: During BSS Internal Handover + +![Diagram of Connection Model 3: After BSS Internal Handover – Call is Locally Switched. This diagram is similar to the previous one but shows the state after the handover. UE-1 is now connected to BSS-2. User Plane Data (red lines) is now locally switched within the BSS between BSS-1/ and BSS-2. The connection to MGW-1 (T_T) is no longer active for UE-1. The label 'After Handover' is present.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) + +Diagram of Connection Model 3: After BSS Internal Handover – Call is Locally Switched. This diagram is similar to the previous one but shows the state after the handover. UE-1 is now connected to BSS-2. User Plane Data (red lines) is now locally switched within the BSS between BSS-1/ and BSS-2. The connection to MGW-1 (T\_T) is no longer active for UE-1. The label 'After Handover' is present. + +Connection Model 3: After BSS Internal Handover – Call is Locally Switched + +Figure 8.4.5.5.1.1: BSS Internal Handover Connection Model that Establishes Local Switching + +##### 8.4.5.5.2 Basic Sequence for BSS Internal Handover that Establishes Local Switching + +Figure 8.4.5.5.2.1 shows the message sequence example for the BSS Internal Handover that Establishes Local Switching. + +In the example, the MSC server receives the Internal Handover Required message and requests the MGW to reserve an RTP bearer termination (TT) using the Reserve and Configure RTP Connection Point procedure with specific flow directions. + +![Sequence diagram for BSS Internal Handover for AoIP that Establishes Local Switching. The diagram shows interactions between UE-1, BSS-1, MSC-S-1, MGW-1, MSC-S-2, MGW-2, BSS-2, and UE-2. It details the flow of messages for handover and local switching status updates. A 'Normally Switched User Plane' is shown at the top, and a 'Locally Switched User Plane in the BSS' is shown at the bottom, established after the handover process.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) + +The diagram illustrates the sequence of messages for a BSS Internal Handover for AoIP that Establishes Local Switching. The participants are UE-1, BSS-1, MSC-S-1, MGW-1, MSC-S-2, MGW-2, BSS-2, and UE-2. The process starts with an internal handover request from BSS-1 to MSC-S-1. MSC-S-1 adds a termination point (TT) and sends an internal handover command to BSS-1 with LCLS-Connection-Status-Control = "Connect". BSS-1 detects the handover in the target cell. BSS-2 notifies MSC-S-2 of the LCLS status change with LCLS-BSS-Status = "Call not yet locally switched". A dashed box indicates that if the call has been answered and MSC-S-2 permits LCLS, it updates the connection status in BSS. MSC-S-2 sends LCLS\_CONNECT\_CONTROL to BSS-2 with LCLS-Connection-Status-Control = "Connect". BSS-2 responds with LCLS\_CONNECT\_CONTROL\_ACK with LCLS-BSS-Status = "Call not yet locally switched". BSS-1 sends a handover detected message to MSC-S-1. MSC-S-1 modifies the termination point (TA, TS) and sends a handover complete message to BSS-1 with LCLS-BSS-Status = "call is locally switched with requested LCLS configuration". MSC-S-1 sends an LCLS-Status-Update to MSC-S-2 with LCLS-Status = "LCLS connected". MSC-S-2 sends an LCLS\_NOTIFICATION to BSS-2 with LCLS-BSS-Status = "call is locally switched with requested LCLS configuration". Finally, MSC-S-1 sends a context C1: SUB TS message to BSS-1. The diagram shows the transition from a "Normally Switched User Plane" to a "Locally Switched User Plane in the BSS". + +Sequence diagram for BSS Internal Handover for AoIP that Establishes Local Switching. The diagram shows interactions between UE-1, BSS-1, MSC-S-1, MGW-1, MSC-S-2, MGW-2, BSS-2, and UE-2. It details the flow of messages for handover and local switching status updates. A 'Normally Switched User Plane' is shown at the top, and a 'Locally Switched User Plane in the BSS' is shown at the bottom, established after the handover process. + +**Figure 8.4.5.5.2.1: BSS Internal Handover for AoIP that Establishes Local Switching** + +1 – 2. As for normal Internal Handover, see TS 23.205 [2] sub-clause 8.4.5. + +3. The MSC-1 Server determines that local switching is permitted by the core network and sends the Internal Handover Command message, including the LCLS-Connection-Control-Status message indicating "Connect" if not previously indicated to BSS-1. + +3a. The BSS-2 notifies MSC-2 server the LCLS status is changed by sending the LCLS\_Notification message with the LCLS-BSS-Status IE set to "Call not yet locally switched". + +3b. If the call has been answered and MSC-2 server permits LCLS to be connected, then the MSC-2 server sends to the BSS-2 the LCLS\_Connect\_Control message with the LCLS-Connection-Status-Control IE set to "connect". + +3c. The BSS-2 returns the LCLS\_Connect\_Control\_ACK message with the LCLS-BSS-Status IE set to "Call not yet locally switched". + +4 – 5. As for normal Internal Handover, see TS 23.205 [2] sub-clause 8.4.5. + +6. The Handover Complete message includes the LCLS-BSS-Status IE indicating that call is locally switched. + +NOTE: alternatively the BSS-1 could indicate LCLS-BSS-Status IE in LCLS-Notification message. + +7. The LCLS Status is propagated through the Core Network. + +8. The BSS-2 sends the LCLS\_Notification message to MSC-2 server with the LCLS-BSS-Status IE set to "call is locally switched with requested LCLS configuration". + +- 9. The termination ( $T_S$ ) is removed from the Access MGW-1. + +#### 8.4.5.6 Example BSS Internal Handover that Breaks Local Switching + +##### 8.4.5.6.1 Connection Model + +Figure 8.4.5.6.1.1 shows the network model for the Intra-MSC BSS Internal Handover, where the call leg pertinent to the UE-1 is handed over from the serving BSS-1 to BSS-2. BSS-1 is the same as BSS-2 for BSS Internal Handover. The bearer termination $T_2$ is used for the bearer towards BSS-2, which is not affected by this handover. Bearer termination $T_S$ is used for the bearer towards BSS-1 and the bearer terminations $T_1$ and $T_A$ are used for the bearer towards the succeeding/preceding MGW. Bearer termination $T_T$ is for the bearer termination towards the BSS after internal handover. The colours and line types used in the figure are defined differently from 3GPP TS 23.205 [2] to indicate LCLS specific issues. + +- User plane link which transmits real user plane data within the BSS and to UEs +- User plane link which transmits real user plane data through the CN and to UEs +- • • User plane path through the CN, connected +- - - Control plane link which transmits signalling + +![Diagram showing the connection model before BSS internal handover. UE-1 and UE-2 are connected to BSS-1/BSS-2. UE-1's user plane data (red line) goes from BSS-1 to MGW-1 (termination TA) and then through the CN (dotted line) to MGW-2 (termination T2). UE-2's user plane data (red line) goes from BSS-1 to MGW-1 (termination TS). Control signalling (green dashed lines) connects the UEs to the BSS, the BSS to MSC-S-1, and MSC-S-1 to MSC-S-2.](4af57aad638888edf2062306f8a54a6c_img.jpg) + +``` + +graph TD + subgraph "Control Signalling" + MSCS1[MSC-S-1] + MSCS2[MSC-S-2] + end + + subgraph "BSS" + BSS[BSS-1/BSS-2] + end + + UE1[UE-1] + UE2[UE-2] + + subgraph "MGWs" + MGW1[MGW-1] + MGW2[MGW-2] + end + + UE1 --- BSS + UE2 --- BSS + BSS -.-> MSCS1 + MSCS1 -.-> MSCS2 + + BSS == User Plane Data ==> MGW1 + MGW1 -.-> MGW2 + + MGW1 --- TS[TS] + MGW1 --- TA[TA] + MGW2 --- T1[T1] + MGW2 --- T2[T2] + +``` + +Diagram showing the connection model before BSS internal handover. UE-1 and UE-2 are connected to BSS-1/BSS-2. UE-1's user plane data (red line) goes from BSS-1 to MGW-1 (termination TA) and then through the CN (dotted line) to MGW-2 (termination T2). UE-2's user plane data (red line) goes from BSS-1 to MGW-1 (termination TS). Control signalling (green dashed lines) connects the UEs to the BSS, the BSS to MSC-S-1, and MSC-S-1 to MSC-S-2. + +**Connection Model 1: Before BSS Internal Handover - Call is locally switched** + +![Diagram of Connection Model 2: During BSS Internal Handover. It shows two User Equipment (UE) units, UE-1 and UE-2, connected to a Base Station Subsystem (BSS) containing BSS-1/ and BSS-2. UE-2 is currently connected to BSS-1/ and UE-1 to BSS-2. A dashed green line labeled 'Control Signalling' connects the BSS to MSC-S-1 and MSC-S-2. MSC-S-1 and MSC-S-2 are connected to MGW-1 and MGW-2 respectively. MGW-1 has ports T_S (Serving), T_A (Anchor), and T_T (Target). MGW-2 has ports T_1 and T_2. A red line labeled 'User Plane Data' shows the path from UE-2 through BSS-1/ to MGW-1. A legend at the bottom left defines T_S = Serving, T_A = Anchor, and T_T = Target.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +Diagram of Connection Model 2: During BSS Internal Handover. It shows two User Equipment (UE) units, UE-1 and UE-2, connected to a Base Station Subsystem (BSS) containing BSS-1/ and BSS-2. UE-2 is currently connected to BSS-1/ and UE-1 to BSS-2. A dashed green line labeled 'Control Signalling' connects the BSS to MSC-S-1 and MSC-S-2. MSC-S-1 and MSC-S-2 are connected to MGW-1 and MGW-2 respectively. MGW-1 has ports T\_S (Serving), T\_A (Anchor), and T\_T (Target). MGW-2 has ports T\_1 and T\_2. A red line labeled 'User Plane Data' shows the path from UE-2 through BSS-1/ to MGW-1. A legend at the bottom left defines T\_S = Serving, T\_A = Anchor, and T\_T = Target. + +Connection Model 2: During BSS Internal Handover + +![Diagram of Connection Model 3: After BSS Internal Handover – Call is not Locally Switched. This diagram is similar to the previous one but shows the state after a handover. UE-2 has moved from BSS-1/ to BSS-2. The user plane data path is now labeled 'Non-LCLS User Plane' and routes from UE-2 through BSS-2, then down to MGW-2, across to MGW-1, and up through BSS-1/ to UE-1. The control signalling path remains the same.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) + +Diagram of Connection Model 3: After BSS Internal Handover – Call is not Locally Switched. This diagram is similar to the previous one but shows the state after a handover. UE-2 has moved from BSS-1/ to BSS-2. The user plane data path is now labeled 'Non-LCLS User Plane' and routes from UE-2 through BSS-2, then down to MGW-2, across to MGW-1, and up through BSS-1/ to UE-1. The control signalling path remains the same. + +Connection Model 3: After BSS Internal Handover – Call is not Locally Switched + +Figure 8.4.5.6.1.1: BSS Internal Handover Connection Model that Breaks Local Switching + +##### 8.4.5.6.2 Basic Sequence for BSS Internal Handover that Breaks Local Switching + +Figure 8.4.5.6.2.1 shows the message sequence example for the BSS Internal Handover that Breaks Local Switching. + +In the example, the MSC server receives the Internal Handover Required message and requests the MGW to reserve an RTP bearer termination (TT) using the Reserve and Configure RTP Connection Point procedure with specific flow directions. + +![Sequence diagram for BSS Internal Handover for AoIP that Breaks Local Switching. The diagram shows interactions between UE-1, BSS-1, MGW-1, MSC-S-1, MSC-S-2, MGW-2, BSS-2, and UE-2. It details the transition from a 'Locally Switched User Plane in the BSS' to a 'Normally Switched User Plane' through a series of 8 main steps including handover requests, status changes, and connection controls.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant UE1 as UE-1 + participant BSS1 as BSS-1 + participant MGW1 as MGW-1 + participant MSCS1 as MSC-S-1 + participant MSCS2 as MSC-S-2 + participant MGW2 as MGW-2 + participant BSS2 as BSS-2 + participant UE2 as UE-2 + + Note over BSS1, BSS2: Locally Switched User Plane in the BSS + BSS1->>MSCS1: 1. Internal Handover Required + MSCS1->>MGW1: 2. Context C1: ADD Termination T_T +(*, T_T) - isolate; +(T_A, T_T) - bothway + MSCS1->>MSCS2: 3. LCLS-Status-Change Request +[LCLS-Status-Change: "LCLS- +disconnection-preparationforHandover"] + MSCS2->>BSS2: 3a. LCLS_CONNECT_CONTROL +(LCLS-Connection-Status-Control = +"BicastatHandover") + BSS2->>MSCS2: 3b. LCLS_CONNECT_CONTROL ACK +(LCLS-BSS-Status = "call is locally switched +with requested LCLS configuration") + MSCS2->>MSCS1: 3c. LCLS-Status-Change Request +Acknowledge [LCLS-Status-Change: +"LCLS-disconnection- +preparationforHandover", Result Code +="Status Change Req Accepted"] + MSCS1->>BSS1: 4. Internal Handover Command +(LCLS-Connection-Control-Status = +"Connect") + Note left of BSS1: Handover +Detected In +Target Cell + BSS1->>MSCS1: [4a. Handover Detected] + BSS1->>MSCS1: 5. HandoverComplete +(LCLS-BSS-Status = +"Call is no longer locally switched") + MSCS1->>MSCS2: 6. LCLS-Status-Update +[LCLS-Status: "LCLS not +connected"] + MSCS2->>BSS2: 7. LCLS_NOTIFICATION (LCLS- +BSS-Status = "Call is no longer +locally switched") + MSCS1->>MGW1: 8. Context C1: SUB T_S + Note over UE1, UE2: Normally Switched User Plane + +``` + +Sequence diagram for BSS Internal Handover for AoIP that Breaks Local Switching. The diagram shows interactions between UE-1, BSS-1, MGW-1, MSC-S-1, MSC-S-2, MGW-2, BSS-2, and UE-2. It details the transition from a 'Locally Switched User Plane in the BSS' to a 'Normally Switched User Plane' through a series of 8 main steps including handover requests, status changes, and connection controls. + +**Figure 8.4.5.6.2.1: BSS Internal Handover for AoIP that Breaks Local Switching** + +- 1 – 2. As for normal Internal Handover, see TS 23.205 [2] sub-clause 8.4.5. +3. MSC-1 Server indicates preparation for disconnection due to handover through the Core Network. +- 3a. MSC-2 Server indicates to BSS-2 to start UL bicasting. +- 3b. The BSS-2 sends the LCLS\_Connect\_Control\_Ack message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration ". +- 3c. MSC-2 Server sends LCLS-Status-Change-Request-Acknowledgement. +4. The MSC-1 Server determines that local switching is permitted by the core network and sends the Internal Handover Command message, optionally including the LCLS-Connection-Control-Status message indicating "Connect". +- 4a BSS-1 may indicate Handover Detected. +5. BSS-1 sends the Handover Complete message to MSC-1 Server to indicate LCLS-BSS-Status is set to "Call is no longer locally switched". +6. MSC-1 Server propagates the change of the LCLS Status through the Core Network. + + +NOTE: If the Internal Handover did not in the end result in LCLS break then the MSC Server will send LCLS-Status-Update message indicating that the call is locally switched. +7. BSS-2 indicates that the call is no longer locally switched in the LCLS\_NOTIFICATION message. + +- 8. The old termination ( $T_S$ ) is removed and the call is normally switched through the Core Network. + +#### 8.4.5.7 Example BSS Internal Handover that Does Not Modify LCLS Status of a Locally Switched Call + +##### 8.4.5.7.1 Connection Model + +Figure 8.4.5.7.1.1 shows the network model for the Intra-MSC BSS Internal Handover, where the call leg pertinent to the UE-1 is handed over from the serving BSS-1 to BSS-2. BSS-1 is the same as BSS-2 for BSS Internal Handover. The bearer termination $T_2$ is used for the bearer towards BSS-2, which is not affected by this handover. Bearer termination $T_S$ is used for the bearer towards BSS-1 and the bearer terminations $T_1$ and $T_A$ are used for the bearer towards the succeeding/preceding MGW. Bearer termination $T_T$ is for the bearer termination towards the BSS after internal handover. The colours and line types used in the figure are defined differently from 3GPP TS 23.205 [2] to indicate LCLS specific issues. + +- ━━ User plane link which transmits real user plane data within the BSS and to UEs +- ━━ User plane link which transmits real user plane data through the CN and to UEs +- . . . User plane path through the CN, connected +- - - Control plane link which transmits signalling + +![Network diagram showing the connection model before BSS internal handover. UE-1 and UE-2 are connected to a combined BSS-1/BSS-2 node. This node has a red 'User Plane Data' link between the UE connections. Control signalling (green dashed lines) goes from BSS-1/BSS-2 to MSC-S-1, which is linked to MSC-S-2. MSC-S-1 is connected to MGW-1, and MSC-S-2 is connected to MGW-2. MGW-1 has terminations Ts and TA. MGW-2 has terminations T1 and T2. A dotted line represents the user plane path through the CN connecting MGW-1 and MGW-2. The diagram is labeled 'Before Handover'.](dc1f232cfd39be5c20b21374ad4c04c0_img.jpg) + +Network diagram showing the connection model before BSS internal handover. UE-1 and UE-2 are connected to a combined BSS-1/BSS-2 node. This node has a red 'User Plane Data' link between the UE connections. Control signalling (green dashed lines) goes from BSS-1/BSS-2 to MSC-S-1, which is linked to MSC-S-2. MSC-S-1 is connected to MGW-1, and MSC-S-2 is connected to MGW-2. MGW-1 has terminations Ts and TA. MGW-2 has terminations T1 and T2. A dotted line represents the user plane path through the CN connecting MGW-1 and MGW-2. The diagram is labeled 'Before Handover'. + +**Connection Model 1: Before BSS Internal Handover - Call is locally switched** + +![Diagram of Connection Model 2: During BSS Internal Handover. It shows two User Equipment (UE) units, UE-1 and UE-2, connected to a Base Station Subsystem (BSS) containing BSS-1 and BSS-2. UE-1 is connected to BSS-2 and UE-2 to BSS-1. A red line represents 'User Plane Data' flowing from the UEs through the BSS. A green dashed line represents 'Control Signalling' flowing from the BSS to MSC-S-1, which is connected to MGW-1. MGW-1 has three ports: T_S (Serving), T_A (Anchor), and T_T (Target). MSC-S-1 is also connected to MSC-S-2, which is connected to MGW-2. A legend at the bottom left defines T_S as Serving, T_A as Anchor, and T_T as Target. The text 'During Handover' is present.](e05b36c0d46549e681ce6581422c66b2_img.jpg) + +Diagram of Connection Model 2: During BSS Internal Handover. It shows two User Equipment (UE) units, UE-1 and UE-2, connected to a Base Station Subsystem (BSS) containing BSS-1 and BSS-2. UE-1 is connected to BSS-2 and UE-2 to BSS-1. A red line represents 'User Plane Data' flowing from the UEs through the BSS. A green dashed line represents 'Control Signalling' flowing from the BSS to MSC-S-1, which is connected to MGW-1. MGW-1 has three ports: T\_S (Serving), T\_A (Anchor), and T\_T (Target). MSC-S-1 is also connected to MSC-S-2, which is connected to MGW-2. A legend at the bottom left defines T\_S as Serving, T\_A as Anchor, and T\_T as Target. The text 'During Handover' is present. + +Connection Model 2: During BSS Internal Handover + +![Diagram of Connection Model 3: After BSS Internal Handover – Call is Locally Switched. This diagram is similar to the previous one but shows the state after the handover. UE-1 and UE-2 are now both connected to BSS-2. The red 'User Plane Data' line is now localized within BSS-2, indicating a locally switched call. The green 'Control Signalling' line remains. The text 'After Handover' is present.](933ecd14c858bf3fc919222d8e357bc8_img.jpg) + +Diagram of Connection Model 3: After BSS Internal Handover – Call is Locally Switched. This diagram is similar to the previous one but shows the state after the handover. UE-1 and UE-2 are now both connected to BSS-2. The red 'User Plane Data' line is now localized within BSS-2, indicating a locally switched call. The green 'Control Signalling' line remains. The text 'After Handover' is present. + +Connection Model 3: After BSS Internal Handover – Call is Locally Switched + +Figure 8.4.5.7.1.1: BSS Internal Handover Connection Model that Does Not Modify LCLS Status of a Locally Switched Call + +##### 8.4.5.7.2 Basic Sequence for BSS Internal Handover that Does Not Modify LCLS Status of a Locally Switched Call + +Figure 8.4.5.7.2.1 shows the message sequence example for the BSS Internal Handover that Does Not Modify LCLS Status of a Locally Switched Call. + +In the example, the MSC server receives the Internal Handover Required message and requests the MGW to reserve an RTP bearer termination (TT) using the Reserve and Configure RTP Connection Point procedure with specific flow directions. + +![Sequence diagram for BSS Internal Handover for AoIP that Does Not Modify LCLS Status of a Locally Switched Call. The diagram shows interactions between UE-1, BSS-1, MGW-1, MSC-S-1, MSC-S-2, MGW-2, BSS-2, and UE-2. Red arrows indicate the locally switched user plane in the BSS. The sequence includes: 1. Internal Handover Required; 2. Context C1: ADD Termination T_T; 3. LCLS-Status-Change Request; 3a. LCLS_CONNECT_CONTROL; 3b. LCLS_CONNECT_CONTROL ACK; 3c. LCLS-Status-Change Request Acknowledge; 4. Internal Handover Command; 4a. Handover Detected; 5. HandoverComplete; 6. Context C1: SUB T_S.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +The diagram illustrates the sequence of messages for a BSS Internal Handover for AoIP that does not modify the LCLS status of a locally switched call. The participants are UE-1, BSS-1, MGW-1, MSC-S-1, MSC-S-2, MGW-2, BSS-2, and UE-2. Red double-headed arrows at the top and bottom indicate the 'Locally Switched User Plane in the BSS' between UE-1 and UE-2 via BSS-1 and BSS-2. + +- 1. Internal Handover Required**: BSS-1 sends this message to MSC-S-1. +- 2. Context C1: ADD Termination TT**: MSC-S-1 sends this to MGW-1. The message includes parameters: (\*, TT) - isolate; (TA, TT) - bothway. +- 3. LCLS-Status-Change Request**: MSC-S-1 sends this to MSC-S-2 with the value: "LCLS-disconnection-preparationforHandover". +- 3a. LCLS\_CONNECT\_CONTROL**: MSC-S-2 sends this to BSS-2 with the value: (LCLS-Connection-Status-Control = "BicastaHandover"). +- 3b. LCLS\_CONNECT\_CONTROL ACK**: BSS-2 sends this to MSC-S-2 with the value: (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration"). +- 3c. LCLS-Status-Change Request Acknowledge**: MSC-S-2 sends this to MSC-S-1 with the value: [LCLS-Status-Change: "LCLS-disconnection-preparationforHandover", Result Code = "Status Change Req Accepted"]. +- 4. Internal Handover Command**: MSC-S-1 sends this to BSS-1 with the value: (LCLS-Connection-Control-Status = "Connect"). +- 4a. Handover Detected**: BSS-1 sends this to MSC-S-1. +- 5. HandoverComplete**: BSS-1 sends this to MSC-S-1 with the value: (LCLS-BSS-Status = "Call is locally switched with requested LCLS configuration"). +- 6. Context C1: SUB TS**: MSC-S-1 sends this to MGW-1. + +Sequence diagram for BSS Internal Handover for AoIP that Does Not Modify LCLS Status of a Locally Switched Call. The diagram shows interactions between UE-1, BSS-1, MGW-1, MSC-S-1, MSC-S-2, MGW-2, BSS-2, and UE-2. Red arrows indicate the locally switched user plane in the BSS. The sequence includes: 1. Internal Handover Required; 2. Context C1: ADD Termination T\_T; 3. LCLS-Status-Change Request; 3a. LCLS\_CONNECT\_CONTROL; 3b. LCLS\_CONNECT\_CONTROL ACK; 3c. LCLS-Status-Change Request Acknowledge; 4. Internal Handover Command; 4a. Handover Detected; 5. HandoverComplete; 6. Context C1: SUB T\_S. + +**Figure 8.4.5.7.2.1: BSS Internal Handover for AoIP that Does Not Modify LCLS Status of a Locally Switched Call** + +1 – 2. As for normal Internal Handover, see TS 23.205 [2] sub-clause 8.4.5. + +3. MSC-1 Server indicates preparation for disconnection due to handover through the Core Network. + +3a. MSC-2 Server indicates to BSS-2 to start UL bicasting. + +3b. The BSS-2 sends the LCLS\_Connect\_Control\_Ack message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration". + +3c. MSC-2 Server sends LCLS-Status-Change-Request-Acknowledgement. + +4. The MSC-1 Server determines that local switching is permitted by the core network and sends the Internal Handover Command message, optionally including the LCLS-Connection-Control-Status message indicating "Connect". + +4a BSS-1 may indicate Handover Detected. + +5. BSS-1 sends the Handover Complete message to MSC-1 Server to indicate LCLS-BSS-Status is set to "the call is locally switched with requested LCLS configuration". + +6. The old termination (TS) is removed and the call is normally switched through the Core Network. + +#### 8.4.5.8 Example BSS Internal Handover that Does Not Modify LCLS Status of a non-Locally Switched Call + +##### 8.4.5.8.1 Connection Model + +Figure 8.4.5.8.1.1 shows the network model for the Intra-MSC BSS Internal Handover, where the call leg pertinent to the UE-1 is handed over from the serving BSS-1 to BSS-2. BSS-1 is the same as BSS-2 for BSS Internal Handover. The bearer termination $T_2$ is used for the bearer towards BSS-2, which is not affected by this handover. Bearer termination $T_S$ is used for the bearer towards BSS-1 and the bearer terminations $T_1$ and $T_A$ are used for the bearer towards the succeeding/preceding MGW. Bearer termination $T_T$ is for the bearer termination towards the BSS after internal handover. The colours and line types used in the figure are defined differently from 3GPP TS 23.205 [2] to indicate LCLS specific issues. + +- User plane link which transmits real user plane data within the BSS and to UEs +- User plane link which transmits real user plane data through the CN and to UEs +- ... User plane path through the CN, connected +- - - Control plane link which transmits signalling + +![Diagram of Connection Model 1: Before BSS Internal Handover - Call is not locally switched. The diagram shows two User Equipment (UE) units, UE-1 and UE-2, connected to a combined BSS-1/BSS-2 unit. UE-1 is connected via a solid black line (User plane link) to a Media Gateway (MGW-1) through termination T_S. UE-2 is connected via a solid black line to MGW-1 through termination T_A. MGW-1 is connected to MGW-2 via a solid black line. MGW-2 is connected to MSC-S-2 via termination T_2. MSC-S-1 is connected to MGW-1 via termination T_1. Control signalling (dashed green lines) is shown between the BSS-1/BSS-2 unit and both MSC-S-1 and MSC-S-2. A label 'Non-LCLS User Plane Data' is placed on the link between MGW-1 and MGW-2. The text 'Before Handover' is at the bottom left.](8658cfab6a458b4a80ab2e384c61ff89_img.jpg) + +Diagram of Connection Model 1: Before BSS Internal Handover - Call is not locally switched. The diagram shows two User Equipment (UE) units, UE-1 and UE-2, connected to a combined BSS-1/BSS-2 unit. UE-1 is connected via a solid black line (User plane link) to a Media Gateway (MGW-1) through termination T\_S. UE-2 is connected via a solid black line to MGW-1 through termination T\_A. MGW-1 is connected to MGW-2 via a solid black line. MGW-2 is connected to MSC-S-2 via termination T\_2. MSC-S-1 is connected to MGW-1 via termination T\_1. Control signalling (dashed green lines) is shown between the BSS-1/BSS-2 unit and both MSC-S-1 and MSC-S-2. A label 'Non-LCLS User Plane Data' is placed on the link between MGW-1 and MGW-2. The text 'Before Handover' is at the bottom left. + +Connection Model 1: Before BSS Internal Handover - Call is not locally switched + +![Diagram of Connection Model 2: During BSS Internal Handover. It shows UE-1 and UE-2 connected to a BSS (BSS-1/BSS-2). UE-1 is being handed over from a Serving (S) termination point to a Target (T) termination point on MGW-1. UE-2 remains connected to the Anchor (A) termination point on MGW-1. Control signaling is shown between the BSS, MSC-S-1, and MSC-S-2. The Non-LCLS User Plane Data path is shown between MGW-1 and MGW-2.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +Control Signalling + +UE-2 + +BSS-1/ BSS-2 + +UE-1 + +Non-LCLS User Plane Data + +MSC-S-1 + +MSC-S-2 + +MGW-1 + +MGW-2 + +During Handover + TS = Serving + TA = Anchor + TT = Target + +Diagram of Connection Model 2: During BSS Internal Handover. It shows UE-1 and UE-2 connected to a BSS (BSS-1/BSS-2). UE-1 is being handed over from a Serving (S) termination point to a Target (T) termination point on MGW-1. UE-2 remains connected to the Anchor (A) termination point on MGW-1. Control signaling is shown between the BSS, MSC-S-1, and MSC-S-2. The Non-LCLS User Plane Data path is shown between MGW-1 and MGW-2. + +Connection Model 2: During BSS Internal Handover + +![Diagram of Connection Model 3: After BSS Internal Handover – Call is not Locally Switched. This diagram is similar to the previous one but shows the state after the handover. UE-1 is now connected to the Target (T) termination point on MGW-1. UE-2 remains connected to the Anchor (A) termination point. The label 'After Handover' is present.](0ee9d674085524d589646a6c3fb21ec3_img.jpg) + +Control Signalling + +UE-2 + +BSS-1/ BSS-2 + +UE-1 + +Non-LCLS User Plane + +MSC-S-1 + +MSC-S-2 + +MGW-1 + +MGW-2 + +After Handover + +Diagram of Connection Model 3: After BSS Internal Handover – Call is not Locally Switched. This diagram is similar to the previous one but shows the state after the handover. UE-1 is now connected to the Target (T) termination point on MGW-1. UE-2 remains connected to the Anchor (A) termination point. The label 'After Handover' is present. + +Connection Model 3: After BSS Internal Handover – Call is not Locally Switched + +Figure 8.4.5.8.1.1: BSS Internal Handover Connection Model that Does Not Modify LCLS Status of a non-Locally Switched Call + +##### 8.4.5.8.2 Basic Sequence for BSS Internal Handover that Does Not Modify LCLS Status of a non-Locally Switched Call + +Figure 8.4.5.8.2.1 shows the message sequence example for the BSS Internal Handover that Does Not Modify LCLS Status of a Locally Switched Call. + +In the example, the MSC server receives the Internal Handover Required message and requests the MGW to reserve an RTP bearer termination (TT) using the Reserve and Configure RTP Connection Point procedure with specific flow directions. + +![Sequence diagram for BSS Internal Handover for AoIP. Lifelines: UE-1, BSS-1, MGW-1, MSC-1, MSC-2, MGW-2, BSS-2, UE-2. The diagram shows the signaling flow for an internal handover where the call remains normally switched through the user plane.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +The diagram illustrates the signaling sequence for a BSS Internal Handover for AoIP. The lifelines involved are UE-1, BSS-1, MGW-1, MSC-1, MSC-2, MGW-2, BSS-2, and UE-2. The process begins with a 'Normally Switched User Plane' across the network. The sequence of messages is as follows: + +- 1. Internal Handover Required:** BSS-1 sends a message to MSC-1. +- 2. Context C1: ADD Termination TT:** MSC-1 sends a message to MGW-1. The message includes parameters: (\*, TT) - isolate; (TA, TT) - bothway. +- 3. Internal Handover Command:** MSC-1 sends a message to BSS-1. The message includes the parameter LCLS-Connection-Control-Status = "Connect". +- Handover Detected In Target Cell:** A red box indicates that BSS-1 detects the handover in the target cell. +- 3a. Handover Detected:** BSS-1 sends a message to MSC-1. +- 4. HandoverComplete:** BSS-1 sends a message to MSC-1. The message includes the parameter LCLS-BSS-Status = "Call is not locally switched". +- 5. Context C1: SUB TS:** MSC-1 sends a message to MGW-1. +- Normally Switched User Plane:** The user plane remains normally switched across the network after the handover. + +Sequence diagram for BSS Internal Handover for AoIP. Lifelines: UE-1, BSS-1, MGW-1, MSC-1, MSC-2, MGW-2, BSS-2, UE-2. The diagram shows the signaling flow for an internal handover where the call remains normally switched through the user plane. + +Figure 8.4.5.8.2.1: BSS Internal Handover for AoIP that Does Not Modify LCLS Status of a non-Locally Switched Call + +- 1 – 2. As for normal Internal Handover, see TS 23.205 [2] sub-clause 8.4.5. +- 3. The MSC-1 Server determines that local switching is permitted by the core network and sends the Internal Handover Command, optionally including the LCLS-Connection-Control-Status message indicating "Connect". +- 3a BSS-1 may indicate Handover Detected. +- 4. BSS-1 sends the Handover Complete message to MSC-1 Server to indicate LCLS-BSS-Status is set to "Call is not locally switched". +- 5. The old termination (TS) is removed and the call is normally switched through the Core Network. + +## 8.5 Handling of GSM Services after UMTS to GSM Handover + +No impact. There are no LCLS related requirements for the handling of GSM Services after UMTS to GSM Handover. + +The handling of GSM services after UMTS to GSM Handover shall be applied in accordance with 3GPP TS 23.205 [2] sub-clause 8.5 for Bearer-Independent CS Core Networks. + +# --- 9 Compatibility Issues + +None; this feature is backward compatible with existing features and earlier releases. + +# --- 10 General (G)MSC server-MGW Procedures + +LCLS does not modify the general (G)MSC server-MGW procedures as shown in 3GPP TS 23.205 [2]. + +# --- 11 Identities + +## 11.1 General + +The Identities defined in 3GPP TS 23.205 [2] for BICC based CS Core network and in 3GPP TS 23.231 [3] for SIP-I with the following additions. + +## 11.2 Global Call Reference + +The Global Call Reference (GCR) IE is derived from the ITU-T *Global Call Reference* parameter (defined by ITU-T Q.1902.3 [5]). + +The Global Call Reference (GCR) information element is a combination of a Network ID field, a Node ID field and a Call Reference ID field. The Call Reference ID field for LCLS is defined to contain a unique call ID. + +If the serving radio access is GERAN the Call Reference ID subfield created by originating MSC server contains a unique call ID and the originating BSS ID which is a unique identifier of a Base Station Subsystem (BSS) Node within an operator's network. + +The complete parameter layout is specified in 3GPP TS 29.205 [6]. + +The GCR is exchanged on the Nc and A interfaces to globally identify the call. + +# --- 12 Operational Aspects + +## 12.1 Charging + +No impact. + +# --- 13 Interactions with Other Services + +## 13.1 Enhanced Multi-Level Precedence and Pre-emption service (eMLPP) + +No impact. eMLPP is always done during call set-up and handled by the MSC Server and therefore such calls can be locally switched. + +## 13.2 Call Deflection Service + +### 13.2.1 General + +The procedures specified for the Call Deflection (CD) supplementary services in 3GPP TS 23.205 [2] sub-clause 13.2 for BICC based CS Core Network and in 3GPP TS 23.231 [3] sub-clause 13.2 for SIP-I based CS Core Network shall be followed. The following sub-clauses describe the additional requirements related to the LCLS functionality. + +The incoming call shall be offered to the served subscriber as a basic mobile terminated call as described in the first part of sub-clause 6.3.2. If the Call Deflection (CD) supplementary service is active and a Call Deflection request from the served subscriber is accepted the call shall be forwarded towards the forwarded-to subscriber. + +The basic call establishment procedures defined in Clause 6 shall be followed for the call towards the forwarded-to (deflected-to) subscriber. The MSC server shall release the call leg towards the served subscriber as described in the sub-clause 7.1 for call clearing. + +### 13.2.2 Notification to the Calling Subscriber + +If the served mobile subscriber has requested that the calling subscriber shall receive a notification about the call forwarding, a notification is sent to the calling party. + +If the notification is implemented using intermediate tones or announcements the MSC server requests the MGW to play an announcement/tone to the calling party, as described in sub-clause 14.6, before establishing the call to the forwarded-to subscriber. + +### 13.2.3 Initial Addressing + +After the possible generation of in-band information has been completed the initial addressing towards the forwarded-to subscriber is performed as described in Clause 6 for the basic mobile terminating call. If the forwarding MSC server supports the LCLS feature and has received the GCR IE, the LCLS-Negotiation Request IE and LCLS-Configuration-Preference IE from a preceding node in the IAM it shall then forward the GCR IE and the resulting LCLS-Configuration-Preference IE and the LCLS-Negotiation Request IE to the succeeding node. + +### 13.2.4 Backward LCLS Negotiation + +The procedure specified in sub-clause 6.2.1.2.2 for the intermediate node and in sub-clause 6.1.1.4 for the oMSC server shall be applied. + +### 13.2.5 LCLS Through-Connection + +The procedure specified in sub-clause 6.1.1.5 shall be applied. + +### 13.2.6 Example + +#### 13.2.6.1 Connection Model + +Figure 13.2.6.1.1 shows the network model for Call Deflection (CD). + +The oMSC server seizes one context with two bearer terminations in the oMGW. The bearer termination T1 is used for the bearer towards the oBSS (calling subscriber) and the bearer termination T2 is used for the bearer towards the GMSC selected iMGW. The GMSC server seizes one context with two bearer terminations in the iMGW. The bearer termination T4 is used for the bearer towards the sMSC server selected sMGW and the bearer termination T3 is used for the bearer towards the preceding oMGW. The sMSC server seizes one context with two bearer terminations in the sMGW. The bearer termination T5 is used for the bearer towards the GMSC selected iMGW and bearer termination Ts is used for the bearer towards the sBSS (served subscriber). + +After a call deflection request is accepted the sMSC server replaces the bearer termination for the served mobile subscriber Ts with the bearer termination for the forwarded-to subscriber T6 in an existing context in the sMGW. + +The tMSC server seizes one context with two bearer terminations in the tMGW. The bearer termination T7 is used for the bearer towards the sMSC selected sMGW and bearer termination T8 is used for the bearer towards the tBSS (forwarded-to subscriber). + +![Diagram showing network components and link types. Legend: Green dashed line for Control plane link; Black dotted line for User plane link path through CN; Red solid line for User plane link within BSS and UEs; Blue dash-dot line for User plane link in backward direction from CN towards oUE. Network components include oUE, oBSS, oMSC-S, GMSC-S, sMSC-S, oMGW, iMGW, sMGW, and sBSS with sUE.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) + +Diagram showing network components and link types. Legend: Green dashed line for Control plane link; Black dotted line for User plane link path through CN; Red solid line for User plane link within BSS and UEs; Blue dash-dot line for User plane link in backward direction from CN towards oUE. Network components include oUE, oBSS, oMSC-S, GMSC-S, sMSC-S, oMGW, iMGW, sMGW, and sBSS with sUE. + +Connection Model 1: Before Call Deflection (CD) Request from Served UE + +![Diagram for Connection Model 1. It shows the network state before a CD request. Control signalling is active between oBSS and oMSC-S. User plane data flows from oUE through oBSS, oMGW, iMGW, and sMGW towards sUE. A blue dash-dot line indicates a backward user plane link from sMGW back to oUE.](4ff00a489baaa34a0c01070de1d613db_img.jpg) + +Diagram for Connection Model 1. It shows the network state before a CD request. Control signalling is active between oBSS and oMSC-S. User plane data flows from oUE through oBSS, oMGW, iMGW, and sMGW towards sUE. A blue dash-dot line indicates a backward user plane link from sMGW back to oUE. + +Connection Model 2: After CD is accepted, Announcement towards calling party + +![Diagram for Connection Model 2. After a CD request is accepted, an announcement is sent towards the calling party (tUE). Control signalling is extended to tMSC-S. User plane data for the announcement is routed from tMSC-S through tMGW, sMGW, iMGW, and oMGW to oBSS/tBSS, then to tUE. A red solid line shows the user plane path from oUE to oBSS/tBSS.](9f862801bce82634d3b5a1e0a195a799_img.jpg) + +Diagram for Connection Model 2. After a CD request is accepted, an announcement is sent towards the calling party (tUE). Control signalling is extended to tMSC-S. User plane data for the announcement is routed from tMSC-S through tMGW, sMGW, iMGW, and oMGW to oBSS/tBSS, then to tUE. A red solid line shows the user plane path from oUE to oBSS/tBSS. + +Connection Model 3: CD, After Answer, Call locally switched + +Figure 13.2.6.1.1: Connection Model for Call Deflection + +#### 13.2.6.2 Basic Sequence + +Figures 13.2.6.2.1 and 13.2.6.2.2 show the message sequence example for the call deflection with a possible notification to the calling party using an announcement. In the example the sMSC server optionally requests the sMGW to play an announcement and to notify the announcement completion. The sMSC server requests the establishment of the call and the bearer towards the forward-to subscriber after the possible announcement has completed. In this example the calling + +subscriber (oUE) and the forwarded-to subscriber (tUE) belong to the same BSS (marked as oBSS and tBSS) and the CN permits LCLS. This example is based on examples from clause 6. + +![Sequence diagram for CD, Call Establishment Flow. The diagram shows interactions between oUE, oBSS, oMGW, oMSC, iMGW, GMSC, sMSC, sMGW, sBSS, and sUE. A header indicates that for call establishment towards served subscriber sUE, basic call establishment steps 1-24 of subclause 6.3.2 apply. The sequence then continues with steps 1-13 specific to Call Deflection (CD).](f5deee2f3301ee351c4008283ffafbb3_img.jpg) + +Sequence diagram illustrating the Call Deflection (CD) Call Establishment Flow. The diagram shows interactions between the following entities: oUE, oBSS, oMGW, oMSC, iMGW, GMSC, sMSC, sMGW, sBSS, and sUE. + +For call establishment towards served subscriber sUE see basic call establishment, subclause 6.3.2, Steps 1 - 24 + +The sequence of messages is as follows: + +1. Call Deflection Request (sMSC to sUE) +2. Call Deflection Ack (sUE to sMSC) +3. DISCONNECT (sMSC to sUE) +4. RELEASE (sUE to sMSC) +5. RELEASE COMPLETE (sMSC to sUE) +6. CLEAR COMMAND (sMSC to sBSS) +7. CLEAR COMPLETE (sBSS to sMSC) +8. Release termination to served UE: SUB request (Ts) / SUB reply (Ts) (sMSC to sMGW) +9. CPG [Generic Notification indicator=call is diverting] (sMSC to oMSC) +10. MOD (T5): play announcement / send tone (sMSC to sMGW) +11. CPG [Generic Notification indicator=call is diverting] (oMSC to oMGW) +12. FACILITY with call forwarding notification (oMGW to oUE) +- Announcement / Tone (sMGW to oUE) - shown as a thick blue arrow +13. NOTIFY (T5): Announcement / Tone completed (sMGW to sMSC) + +Sequence diagram for CD, Call Establishment Flow. The diagram shows interactions between oUE, oBSS, oMGW, oMSC, iMGW, GMSC, sMSC, sMGW, sBSS, and sUE. A header indicates that for call establishment towards served subscriber sUE, basic call establishment steps 1-24 of subclause 6.3.2 apply. The sequence then continues with steps 1-13 specific to Call Deflection (CD). + +Figure 13.2.6.2.1: CD, Call Establishment Flow + +1. The incoming call is offered to the served subscriber as a basic mobile terminated call as described in the first part of sub-clause 6.3.2. The Call Deflection (CD) supplementary service is active and a Call Deflection is requested from the served subscriber sUE. +2. The Call Deflection is accepted. +3. The sMSC server initiates call clearing towards the sUE by sending a DISCONNECT message. +4. Upon receiving the DISCONNECT message the sUE sends a RELEASE message to the core network. +5. The sMSC server sends the RELEASE COMPLETE message to the sUE. +6. The sMSC server request the sBSS to release the associated dedicated resource(s) by sending CLEAR COMMAND message. +7. The sBSS informs the sMSC server that the associated dedicated resource(s) has been successfully cleared with the CLEAR COMPLETE message. +8. The sMSC server orders the sMGW to remove the bearer termination (Ts) towards the served mobile subscriber (in case when the radio resources had already been allocated in the sMGW). +9. The sMSC server sends the CPG message with the Generic Notification Indicator parameter set to "Call is diverting". +10. The sMSC server provides the sMGW with the announcement/tone identification and requests the sMGW to notify the announcement/tone completion using the Play Announcement or Send Tone procedure. + +11. The GMSC server forwards the CPG message with the Generic Notification Indicator parameter set to "Call is diverting" to the preceding node. +12. The oMSC server notifies the calling user (oUE) about call forwarding. +13. The sMGW notifies the sMSC server when the announcement/tone is completed using the Announcement Completed or Tone Completed procedure. + +![Sequence diagram for Call Establishment Flow (continuation of figure 13.2.6.2.1). The diagram shows interactions between oUE, oBSS, oMGW, oMSC, iMGW, GMSC, sMSC, tMSC, tMGW, tBSS, and tUE. It details steps 14 through 29, including IAM, Paging, SETUP, Call Confirmed, and LCLS status updates. A red arrow at the bottom indicates 'Call is locally Switched'.](13fde41de77bf026013a0b81684d1fc9_img.jpg) + +The sequence diagram illustrates the call establishment flow between various network elements. The participants are oUE, oBSS, oMGW, oMSC, iMGW, GMSC, sMSC, tMSC, tMGW, tBSS, and tUE. The sequence of messages is as follows: + +- 14. sMSC to tMSC: IAM [Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference] +- 15. tMSC to tUE: Paging tUE +- 16. tUE to tMSC: Paging response + CL3 +- 17. tMSC to tUE: SETUP +- 18. tMSC to tUE: Call Confirmed +- 19. tMSC to tMGW: Add network side termination: ADD request (\$)/ADD reply (T7) +- 20. tMGW to sMSC: APM [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] +- 21. sMSC to iMGW: APM [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] +- 22. oMSC to oMGW: Store new value of LCLS-Configuration-Preference IE if different from previously received value and mark "LCLS-Configuration update needed". If codec modification is required performed it according to 3GPP TS 23.153. +- 23. For succeeding signalling sequence see basic call establishment, figures 6.3.2.2 and 6.3.2.3, steps 18 - 32 +- 24. oMSC to oBSS: if "LCLS-Configuration update needed" determine new value of LCLS-Configuration IE +- 25. oBSS to oMSC: LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "connect", [LCLS-Configuration]) +- 26a. oMSC to oBSS: LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") +- 27. oMSC to iMGW: LCLS status update: APM [LCLS-Status = "LCLS connected"] +- 28. iMGW to GMSC: LCLS status update: APM [LCLS-Status = "LCLS connected"] +- 29. GMSC to sMSC: LCLS status update: APM [LCLS-Status = "LCLS connected"] +- 26b. tMSC to tBSS: LCLS\_NOTIFICATION (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") + +A large red arrow at the bottom of the diagram, spanning from oBSS to tBSS, is labeled "Call is locally Switched". + +Sequence diagram for Call Establishment Flow (continuation of figure 13.2.6.2.1). The diagram shows interactions between oUE, oBSS, oMGW, oMSC, iMGW, GMSC, sMSC, tMSC, tMGW, tBSS, and tUE. It details steps 14 through 29, including IAM, Paging, SETUP, Call Confirmed, and LCLS status updates. A red arrow at the bottom indicates 'Call is locally Switched'. + +Figure 13.2.6.2.2: CD, Call Establishment Flow (continuation of figure 13.2.6.2.1) + +14. If the sMSC server supports LCLS it may modify the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE before sending the IAM message containing the GCR with the encapsulated oBSS ID, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. +15. The tMSC server pages the forwarded-to subscriber (tUE). +16. The tMSC server performs call Setup. +17. The tUE confirms the call. +18. The tMSC server requests the tMGW to prepare for the network side bearer establishment (T7). + +19. After the tMGW has replied with the bearer address and the binding reference the tMSC server returns the APM message with the selected codec and if LCLS is supported, the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. +20. The sMSC server transfers the APM message with the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. If codec modification is required then the sMSC server includes the codec related information within the same APM message. +21. The GMSC server transfers the APM message. +22. Based on the returned LCLS-Negotiation Response IE IE and the LCLS-Configuration-Preference IE the oMSC server determines whether LCLS is allowed in the core network and if LCLS-Configuration update is needed. +If codec modification is required then the oMSC server performs codec negotiation according to 3GPP TS 23.153 [4]. +23. When performing further call establishment the procedure between the calling subscriber (oUE) and the forwarded-to subscriber (tUE) is the same as specified in steps 18 - 32 of sub-clause 6.3.2.1. +24. Since the received ANM message indicated "LCLS is feasible but not yet connected" the oMSC server checks if LCLS-Configuration updated is needed and if so the oMSC server calculates the new LCLS-Configuration value based on the latest received LCLS-Negotiation IE. +25. The oMSC server requests the oBSS to connect LCLS and if configuration updated is needed, it includes the LCLS-Configuration IE in the LCLS\_CONNECT\_CONTROL message. +- 26a. Since the BSS has received the through connect request for both call legs the oBSS returns the LCLS\_CONNECT\_CONTROL\_ACK message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration". +- 26b. Since the BSS has received the through connect request for both call legs the tBSS signals the LCLS status change by sending the LCLS\_NOTIFICATION message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration". +27. The oMSC server signals the change of the LCLS status through the Core Network by sending the APM message with the LCLS-Status IE set to "LCLS connected". +28. The iMSC server transfers the change of the LCLS status to the sMSC server. +29. The sMSC server transfers the change of the LCLS status to the tMSC server. + +## 13.3 Line identification Services + +### 13.3.1 Calling Line Identification Presentation (CLIP) + +No impact. The line identification related services are signalling based and there are no LCLS related requirements for the Calling Line Identification Presentation (CLIP) service. + +### 13.3.2 Calling Line Identification Restriction (CLIR) + +No impact. The line identification related services are signalling based and there are no LCLS related requirements for the Calling Line Identification Restriction (CLIR) service. + +### 13.3.3 Connected Line Identification Presentation (COLP) + +No impact. The line identification related services are signalling based and there are no LCLS related requirements for the Connected Line Identification Presentation (COLP) service. + +### 13.3.4 Connected Line Identification Restriction (COLR) + +No impact. The line identification related services are signalling based and there are no LCLS related requirements for the Connected Line Identification Restriction (COLR) service. + +## 13.4 Call Forwarding Services + +### 13.4.1 Principles + +The procedures specified for the Call Forwarding services in 3GPP TS 23.205 [2] sub-clause 13.4 for BICC based CS Core Network and in 3GPP TS 23.231 [3] sub-clause 13.4 for SIP-I based CS Core Network shall be followed. The following sub-clauses describe the additional requirements related to the LCLS functionality. + +### 13.4.2 Call Forwarding Unconditional (CFU) + +#### 13.4.2.1 Notification to the Calling Subscriber + +If the GMSC server determines that a call should be forwarded without being offered to the served mobile subscriber and the served mobile subscriber has requested that the calling subscriber shall receive a notification about the call forwarding, the GMSC server shall send a notification to the preceding node. If the GMSC server supports the LCLS feature and receives the GCR IE, the LCLS-Negotiation Request IE and LCLS-Configuration-Preference IE from the preceding node it may modify the LCLS-Configuration-Preference IE based on its own LCLS configuration requirements, as described in sub-clause 4.2, and it shall return the resulting LCLS-Configuration-Preference IE and the LCLS-Negotiation Response IE to the preceding node. + +If the notification is implemented using intermediate tones or announcements the GMSC server requests the MGW to play an announcement/tone to the calling party, as described in sub-clause 14.6, before establishing the call to the forwarded-to subscriber. + +#### 13.4.2.2 Initial Addressing + +If the incoming call is to be forwarded without being offered to the served mobile subscriber the call towards the forwarded-to subscriber is established as for a basic call. After the possible generation of in-band information has been completed the initial addressing towards the forwarded-to subscriber is performed as described in the clause 6 for the basic mobile terminating call. If the GMSC server supports the LCLS feature and receives the GCR IE, the LCLS-Negotiation Request IE and LCLS-Configuration-Preference IE from a preceding node in the IAM it shall forward the GCR IE and the resulting LCLS-Configuration-Preference IE and the LCLS-Negotiation Request IE to the succeeding node. + +#### 13.4.2.3 Backward LCLS Negotiation + +The procedure specified in sub-clause 6.2.1.2.2 for the intermediate node and in sub-clause 6.1.1.4 for the oMSC server shall be applied. + +#### 13.4.2.4 LCLS Through-Connection + +The procedure specified in sub-clause 6.1.1.5 shall be applied. + +#### 13.4.2.5 Example + +##### 13.4.2.5.1 Connection Model + +Figure 13.4.2.5.1.1 shows the network model for call forwarding unconditional. The oMSC server seizes one context with two bearer terminations in the oMGW. The bearer termination T1 is used for the bearer towards the oBSS (calling subscriber) and the bearer termination T2 is used for the bearer towards the GMSC selected iMGW. The GMSC server seizes one context with two bearer terminations in the iMGW. The bearer termination T4 is used for the bearer towards the tMSC server selected tMGW and the bearer termination T3 is used for the bearer towards the preceding oMGW. The tMSC server seizes one context with two bearer terminations in the tMGW. The bearer termination T5 is used for the bearer towards the GMSC selected iMGW and bearer termination T6 is used for the bearer towards the tBSS (forwarded-to subscriber). + +- Control plane link which transmits signalling +- ● ● ● ● User plane link path through CN, connected or disconnected +- ━━━━━ User plane link which transmits real user plane data within BSS and UEs +- ━ ∙ ━ ∙ ━ User plane link which transmits real user plane data in backward direction from the CN towards oUE (e.g. announcement/tone, network provided ring-back tone) + +![Diagram of Connection Model 1: Before CFU, Announcement towards Calling Party. It shows an oUE connected to an oBSS. The oBSS is connected to an oMSC-S via a green dashed control plane link. The oMSC-S is connected to a GMSC-S via another green dashed control plane link. The oMSC-S is also connected to an oMGW (with ports T1, T2, oC) via a solid blue user plane link. The oMGW is connected to an iMGW (with ports T3, T4, iC) via a solid blue user plane link. A blue dashed line with an arrow points from the oMGW back to the oBSS, representing a backward user plane link for announcement/tone.](cf8bd014a50b7c69435e804f67f9617f_img.jpg) + +Diagram of Connection Model 1: Before CFU, Announcement towards Calling Party. It shows an oUE connected to an oBSS. The oBSS is connected to an oMSC-S via a green dashed control plane link. The oMSC-S is connected to a GMSC-S via another green dashed control plane link. The oMSC-S is also connected to an oMGW (with ports T1, T2, oC) via a solid blue user plane link. The oMGW is connected to an iMGW (with ports T3, T4, iC) via a solid blue user plane link. A blue dashed line with an arrow points from the oMGW back to the oBSS, representing a backward user plane link for announcement/tone. + +**Connection Model 1: Before CFU, Announcement towards Calling Party** + +![Diagram of Connection Model 2: After CFU and answer, Call is locally switched. It shows a tUE and an oUE both connected to a combined oBSS/tBSS. The oBSS/tBSS is connected to an oMSC-S via a green dashed control plane link. The oMSC-S is connected to a gMSC-S via a green dashed control plane link. The gMSC-S is connected to a tMSC-S via a green dashed control plane link. The oBSS/tBSS is also connected to an oMGW (with ports T1, T2, oC) via a solid red user plane link labeled 'User Plane Data'. The oMGW is connected to an iMGW (with ports T3, T4, iC) via a solid blue user plane link. The iMGW is connected to a tMGW (with ports T5, T6, tC) via a solid blue user plane link. A dotted line labeled 'Non LCLS User Plane' connects the oBSS/tBSS to the tMGW.](a5184899f915014fa38608754efcc9c7_img.jpg) + +Diagram of Connection Model 2: After CFU and answer, Call is locally switched. It shows a tUE and an oUE both connected to a combined oBSS/tBSS. The oBSS/tBSS is connected to an oMSC-S via a green dashed control plane link. The oMSC-S is connected to a gMSC-S via a green dashed control plane link. The gMSC-S is connected to a tMSC-S via a green dashed control plane link. The oBSS/tBSS is also connected to an oMGW (with ports T1, T2, oC) via a solid red user plane link labeled 'User Plane Data'. The oMGW is connected to an iMGW (with ports T3, T4, iC) via a solid blue user plane link. The iMGW is connected to a tMGW (with ports T5, T6, tC) via a solid blue user plane link. A dotted line labeled 'Non LCLS User Plane' connects the oBSS/tBSS to the tMGW. + +**Connection Model 2: After CFU and answer, Call is locally switched** + +**Figure 13.4.2.5.1.1: Connection Model for Call Forwarding Unconditional** + +##### **13.4.2.5.2 Basic Sequence** + +Figures 13.4.2.5.2.1 and 13.4.2.5.2.2 show the message sequence example for the call forwarding unconditional with a possible notification to the calling party using an announcement. In the example the GMSC server optionally requests the MGW to play an announcement and to notify the announcement completion, after the bearer to the incoming side has been established. When the possible announcement has completed the GMSC server requests the establishment of the call and the bearer towards the forward-to subscriber. + +In this example the calling subscriber (oUE) and the forwarded-to subscriber (tUE) belong to the same BSS (marked as oBSS and tBSS) and the CN permits LCLS. The example is based on examples from clause 6. + +![Sequence diagram for CFU, Call Establishment Flow. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, GMSC, tMSC, tMGW, tBSS, tUE. The diagram shows 14 steps of message exchange for call establishment and bearer handling.](8e80de0cac529b2c3775d677c5203133_img.jpg) + +``` + +sequenceDiagram + participant oUE + participant oBSS + participant oMGW + participant oMSC + participant iMGW + participant GMSC + participant tMSC + participant tMGW + participant tBSS + participant tUE + + Note left of oUE: 1. oUE accesses oMSC: Service Request + CL3 + oUE->>oMSC: 1. oUE accesses oMSC: Service Request + CL3 + Note right of oMSC: 2. SETUP + oMSC->>oMGW: 2. SETUP + Note right of oMGW: 3. Retrieve oBSS ID and use it to generate Global Call Reference. + oMGW->>oMSC: 4. IAM [Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference] + Note right of oMSC: 5. HLR Interrogation: CFU service active and calling party should be notified + oMSC->>GMSC: 6. Add network side termination: ADD request ($) / ADD reply (T3) Context (iC) + Note right of GMSC: 7. APM [SC, ACL, LCLS-Negotiation Response, LCLS-Configuration-Preference] + GMSC->>oMSC: 8a. Add network side termination: ADD request ($) / ADD reply (T2) Context (oC) + Note right of oMSC: Network side Bearer Establishment + oMSC->>oMGW: 8b. Add access side termination: ADD request ($) / ADD reply (T1) Context (oC) + Note right of oMGW: NOTE: For AoTDM step 8b is: ADD (T1). + oMGW->>oMSC: 9. ASSIGNMENT REQUEST (GCR, LCLS-Configuration) + oMSC->>oBSS: 10. ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call not possible to be locally switched") + Note right of oBSS: Access side Bearer Establishment + oBSS->>oMSC: 11. BICC COT + oMSC->>iMGW: 12. ACM [BCI=no indication, Generic Notification indicator=call is diverting] + Note right of iMGW: 13. MOD (T3): play announcement / send tone Context (iC) + iMGW->>GMSC: 14. FACILITY with call forwarding notification + Note right of oUE: Announcement / Tone + oUE->>oMGW: Announcement / Tone + +``` + +Sequence diagram for CFU, Call Establishment Flow. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, GMSC, tMSC, tMGW, tBSS, tUE. The diagram shows 14 steps of message exchange for call establishment and bearer handling. + +Figure 13.4.2.5.2.1: CFU, Call Establishment Flow + +- Service Request handling. +- Originating Call SETUP. +- If the oMSC server supports LCLS it retrieves the oBSS ID and generates the Global Call Reference for the call. +- The oMSC server sends the IAM message including supported codecs list, GCR with encapsulated oBSS ID, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. +- The GMSC server determines that call should be forwarded because of the Call Forwarding Unconditional supplementary service and that notification should be sent towards the calling party (oUE). +- Since bearer must be established for the announcement/tone to be sent to the calling party the GMSC server selects the MGW and requests the seizure of the incoming network side bearer termination (T3). +- The GMSC server transfers the APM message with the selected codec and since LCLS is supported the currently negotiated LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. +- When the bearer information is received the oMSC server requests the seizure of the network side bearer termination (T2). + +- 8b. After the network side bearer information is seized the oMSC server requests the seizure of the access side bearer termination (T1). +During the seizure of the network side or the access side bearer termination the oMSC server will also request the oMGW to through-connect the bearer terminations so that the bearer will be backward through-connected. +9. The oMSC server determines whether LCLS is allowed in the core network based on the returned LCLS-Negotiation IE and if so the oMSC server includes the LCLS-Configuration IE in the ASSIGNMENT REQUEST message along with the GCR IE. +10. The oBSS returns the ASSIGNMENT COMPLETE message with the LCLS-BSS-Status IE indicating "call not possible to be locally switched". +11. When the access assignment is completed the oMSC server sends the Continuity (COT) message to the GMSC server. +12. The GMSC server sends the ACM message with the Generic Notification Indicator parameter set to "Call is diverting". +13. The GMSC server provides the iMGW with the announcement/tone identification and requests the iMGW to notify the announcement/tone completion using the Play Announcement or Send Tone procedure. +14. The oMSC server notifies the calling user (oUE) about call forwarding. + +![Sequence diagram for CFU Call Establishment Flow (continuation of figure 13.4.2.5.2.1). The diagram shows interactions between oUE, oBSS, oMGW, oMSC, iMGW, GMSC, tMSC, tMGW, tBSS, and tUE. It details steps 15 through 29, including NOTIFY, IAM, Paging, SETUP, Call Confirmed, and LCLS status updates. A red box at step 23 notes storing the LCLS-Configuration-Preference IE. A red arrow at the bottom indicates 'Call is locally Switched'.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) + +The sequence diagram illustrates the call establishment flow for CFU. The participants are oUE, oBSS, oMGW, oMSC, iMGW, GMSC, tMSC, tMGW, tBSS, and tUE. The sequence of messages is as follows: + +- 15. NOTIFY (T3): Announcement / Tone completed (iMGW to GMSC) +- 16. IAM [Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference] (GMSC to tMSC) +- 17. Paging tUE (tMSC to tBSS) +- Paging response + CL3 (tBSS to tMSC) +- 18. SETUP (tMSC to tBSS) +- 19. Call Confirmed (tBSS to tMSC) +- 20. Add network side termination: ADD request (\$)/ADD reply (T5) (tMSC to tMGW) +- Context (tC) (tMGW to tMSC) +- Network side Bearer Establishment (tMGW to tBSS) +- 21. APM [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] (tMSC to GMSC) +- 22. APM [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] (GMSC to iMGW) +- 23. Store new value of LCLS-Configuration-Preference IE if different from previously received value and mark "LCLS-Configuration update needed". If codec modification is required performed it according to 3GPP TS 23.153 . (iMGW to oMSC) +- 24. For succeeding signalling sequence see basic call establishment, figures 6.3.2.2 and 6.3.2.3, steps 18 - 32 +- 25. If "LCLS-Configuration update needed" determine new value of LCLS-Configuration IE (oMSC to oBSS) +- 26. LCLS\_CONNECT\_CONTROL (LCLS-Connection-Status-Control = "connect", [LCLS-Configuration]) (oBSS to oMSC) +- 27a. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") (oMSC to oBSS) +- 27b. LCLS\_NOTIFICATION (LCLS-BSS-Status = "call is locally switched with requested LCLS configuration") (oBSS to tBSS) +- 28. LCLS status update: BICC APM [LCLS-Status = "LCLS connected"] (oMSC to tMSC) +- 29. LCLS status update: BICC APM [LCLS-Status = "LCLS connected"] (tMSC to tMGW) + +A red arrow at the bottom of the diagram, spanning from oBSS to tBSS, is labeled "Call is locally Switched". + +Sequence diagram for CFU Call Establishment Flow (continuation of figure 13.4.2.5.2.1). The diagram shows interactions between oUE, oBSS, oMGW, oMSC, iMGW, GMSC, tMSC, tMGW, tBSS, and tUE. It details steps 15 through 29, including NOTIFY, IAM, Paging, SETUP, Call Confirmed, and LCLS status updates. A red box at step 23 notes storing the LCLS-Configuration-Preference IE. A red arrow at the bottom indicates 'Call is locally Switched'. + +**Figure 13.4.2.5.2.2: CFU, Call Establishment Flow (continuation of figure 13.4.2.5.2.1)** + +- The iMGW notifies the GMSC server when the announcement/tone is completed using the Announcement Completed or Tone Completed procedure. +- If the GMSC server supports LCLS it may modify the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE before sending the IAM message containing the GCR with the encapsulated oBSS ID, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. +- The tMSC server pages the forwarded-to subscriber (tUE). +- The tMSC server performs call Setup. +- The tUE confirms the call. +- The tMSC server requests the tMGW to prepare for the network side bearer establishment (T5). +- After the tMGW has replied with the bearer address and the binding reference the tMSC server returns the APM message with the selected codec and if LCLS is supported, the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. +- The GMSC server transfers the APM message with the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. If codec modification is required then the GMSC server initiates codec + +negotiation according to 3GPP TS 23.153 [4], and includes the codec related information within the same APM message. + +23. Based on the returned LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE the oMSC server determines whether LCLS is allowed in the core network and if LCLS-Configuration update is needed. If codec modification is required then the oMSC server performs codec negotiation according to 3GPP TS 23.153 [4]. +24. When performing further call establishment the procedure between the calling subscriber (oUE) and the forwarded-to subscriber (tUE) is the same as specified in steps 18 - 32 of sub-clause 6.3.2.1. +25. Since the received ANM message indicated "LCLS is feasible but not yet connected" the oMSC server checks if LCLS-Configuration updated is needed and if so the oMSC server calculates the new LCLS-Configuration value based on the latest received LCLS-Negotiation IE. +26. The oMSC server requests the oBSS to connect LCLS and if configuration updated is needed, it includes the LCLS-Configuration IE in the LCLS\_CONNECT\_CONTROL message. +NOTE: If codecs need to be modified for TrFO (AoIP), then the oMSC can utilize Assignment (modify) or Internal Handover Enquiry before sending LCLS\_CONNECT\_CONTROL message. +- 27a. Since the BSS has received the through connect request for both call legs the oBSS returns the LCLS\_CONNECT\_CONTROL\_ACK message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration". +- 27b. Since the BSS has received the through connect request for both call legs the tBSS signals the LCLS status change by sending the LCLS\_NOTIFICATION message with the LCLS-BSS-Status IE set to "the call is locally switched with requested LCLS configuration". +28. The oMSC server signals the change of the LCLS status through the Core Network by sending the APM message with the LCLS-Status IE set to "LCLS connected". +29. The iMSC server transfers the change of the LCLS status to the tMSC server. + +### 13.4.3 Call Forwarding on mobile subscriber Busy (CFB) + +#### 13.4.3.1 Network Determined User Busy (NDUB) + +##### 13.4.3.1.1 General + +The incoming call that meets mobile subscriber busy with the condition Network Determined User Busy (NDUB) shall be forwarded towards the forwarded-to subscriber without being offered to the served mobile subscriber. The basic call establishment procedures defined in the clause 6 shall be followed for the call towards the forwarded-to subscriber. + +##### 13.4.3.1.2 Notification to the Calling Subscriber + +If the GMSC server determines that a call should be forwarded without being offered to the served mobile subscriber and the served mobile subscriber has requested that the calling subscriber shall receive a notification about the call forwarding, the GMSC server shall send a notification to the preceding node. If the GMSC server supports the LCLS feature and receives the GCR IE, the LCLS-Negotiation Request IE and LCLS-Configuration-Preference IE from the preceding node it may modify the LCLS-Configuration-Preference IE based on its own LCLS configuration requirements, as described in sub-clause 4.2, and it shall return the resulting LCLS-Configuration-Preference IE and the LCLS-Negotiation Response IE to the preceding node. + +If the notification is implemented using intermediate tones or announcements the GMSC server requests the MGW to play an announcement/tone to the calling party, as described in sub-clause 14.6, before establishing the call to the forwarded-to subscriber. + +##### 13.4.3.1.3 Initial Addressing + +If the incoming call is to be forwarded without being offered to the served mobile subscriber the call towards the forwarded-to subscriber is established as for a basic call. After the possible generation of in-band information has been completed the initial addressing towards the forwarded-to subscriber is performed as described in the clause 6 for the basic mobile terminating call. If the GMSC server supports the LCLS feature and receives the GCR IE, the LCLS-Negotiation Request IE and LCLS-Configuration-Preference IE from a preceding node in the IAM it shall forward the + +GCR IE and the resulting LCLS-Configuration-Preference IE and the LCLS-Negotiation Request IE to the succeeding node. + +##### 13.4.3.1.4 Backward LCLS Negotiation + +The procedure specified in sub-clause 6.2.1.2.2 for the intermediate node and in sub-clause 6.1.1.4 for the oMSC server shall be applied. + +##### 13.4.3.1.5 LCLS Through-Connection + +The procedure specified in sub-clause 6.1.1.5 shall be applied. + +##### 13.4.3.1.6 Example + +The same example as for Call Forwarding Unconditional applies. + +#### 13.4.3.2 User Determined User Busy (UDUB) + +##### 13.4.3.2.1 General + +The incoming call shall be offered to the served subscriber as a normal call. When the call meets mobile subscriber busy with the condition User Determined User Busy (UDUB) it shall be forwarded towards the forwarded-to subscriber. The basic call establishment procedures defined in the clause 6 shall be followed for the call towards the forwarded-to subscriber. + +##### 13.4.3.2.2 Call Clearing to the Served Subscriber + +When the MSC server determines that the call shall be forwarded due to the UDUB it shall release the call leg towards the served subscriber as described in the sub-clause 7.1 for call clearing. + +##### 13.4.3.2.3 Notification to the Calling Subscriber + +If the MSC server determines that a call should be forwarded and the served mobile subscriber has requested that the calling subscriber shall receive a notification about the call forwarding, the MSC server shall send a notification to the preceding node. + +If the notification is implemented using intermediate tones or announcements the MSC server requests the MGW to play an announcement/tone to the calling party, as described in sub-clause 14.6, before establishing the call to the forwarded-to subscriber. + +##### 13.4.3.2.4 Initial Addressing + +If the incoming call is to be forwarded the call towards the forwarded-to subscriber is established as for a basic call. After the possible generation of in-band information has been completed the initial addressing towards the forwarded-to subscriber is performed as described in the clause 6 for the basic mobile terminating call. If the forwarding MSC server supports the LCLS feature and has received the GCR IE, the LCLS-Negotiation Request IE and LCLS-Configuration-Preference IE from a preceding node in the IAM it shall then forward the GCR IE and the resulting LCLS-Configuration-Preference IE and the LCLS-Negotiation Request IE to the succeeding node. + +NOTE: If LCLS has been successfully negotiated to this point the oMSC have received back the LCLS-Negotiation Response IE and LCLS-Configuration-Preference IE and LCLS Status may have indicated that the call can be locally switched but since the called subscriber did not answer the call is still switched through the CN at this point. + +##### 13.4.3.2.5 Backward LCLS Negotiation + +The procedure specified in sub-clause 6.2.1.2.2 for the intermediate node and in sub-clause 6.1.1.4 for the oMSC server shall be applied. + +##### 13.4.3.1.6 LCLS Through-Connection + +The procedure specified in sub-clause 6.1.1.5 shall be applied. + +##### 13.4.3.2.7 Example + +###### 13.4.3.2.7.1 Connection Model + +Figure 13.4.3.2.7.1.1 shows the network model for call forwarding busy UDUB. + +The oMSC server seizes one context with two bearer terminations in the oMGW. The bearer termination T1 is used for the bearer towards the oBSS (calling subscriber) and the bearer termination T2 is used for the bearer towards the GMSC selected iMGW. The GMSC server seizes one context with two bearer terminations in the iMGW. The bearer termination T4 is used for the bearer towards the sMSC server selected sMGW and the bearer termination T3 is used for the bearer towards the preceding oMGW. The sMSC server seizes one context with two bearer terminations in the sMGW. The bearer termination T5 is used for the bearer towards the GMSC selected iMGW and bearer termination Ts is used for the bearer towards the sBSS (served subscriber). + +After call forwarding busy UDUB is detected the sMSC server replaces the bearer termination for the served mobile subscriber Ts with the bearer termination for the forwarded-to subscriber T6 in an existing context in the sMGW. + +The tMSC server seizes one context with two bearer terminations in the tMGW. The bearer termination T7 is used for the bearer towards the sMSC selected sMGW and bearer termination T8 is used for the bearer towards the tBSS (forwarded-to subscriber). + +![Diagram showing network components and link types. Legend: Green dashed line for control plane signalling; Black dotted line for user plane link path through CN; Red solid line for user plane link within BSS and UEs; Blue dashed line for backward user plane link from CN towards oUE.](9ed248b025d766251d58be10b01a1cc0_img.jpg) + +The diagram illustrates the network architecture for call forwarding busy UDUB. It includes three MSC servers (oMSC-S, GMSC-S, sMSC-S) connected in a chain via control plane links (green dashed). Below them are corresponding gateways (oMGW, iMGW, sMGW) connected to Base Station Subsystems (oBSS, sBSS). User plane links are shown as solid red lines within BSS/UEs and dotted black lines through the CN. Bearer terminations are labeled T1, T2, T3, T4, T5, and Ts. + +Diagram showing network components and link types. Legend: Green dashed line for control plane signalling; Black dotted line for user plane link path through CN; Red solid line for user plane link within BSS and UEs; Blue dashed line for backward user plane link from CN towards oUE. + +Connection Model 1: Before CFB (UDUB) + +![Diagram showing the network state after CFB (UDUB) with announcements towards the calling party. It shows the same components as the previous diagram but with blue dashed lines indicating backward user plane links from the gateways towards the oUE for announcements.](215165a27ad7d72bd39fdf55a3cb7486_img.jpg) + +This diagram shows the network state after a busy call forwarding (CFB) event. The primary difference is the addition of blue dashed lines representing backward user plane links from the gateways (oMGW, iMGW, sMGW) back towards the originating UE (oUE) to provide announcements like ring-back tones. + +Diagram showing the network state after CFB (UDUB) with announcements towards the calling party. It shows the same components as the previous diagram but with blue dashed lines indicating backward user plane links from the gateways towards the oUE for announcements. + +Connection Model 2: After CFB (UDUB), Announcement towards calling party + +![Diagram of Connection Model 3: CFB (UDUB), After Answer, Call locally switched. The diagram shows two planes: Control Signalling (top, green dashed box) and Non LCLS User Plane (bottom, black dotted box). The Control Signalling plane contains oMSC-S, GMSC-S, sMSC-S, and tMSC-S connected in a line. The User Plane contains oMGW, iMGW, sMGW, and tMGW connected in a line. Vertical blue lines connect each MSC-S to its corresponding MGW. On the left, tUE and oUE connect to an oBSS/tBSS block. A red 'User Plane Data' path loops within the oBSS/tBSS block, indicating a locally switched call. Termination points T1 through T8 are labeled within the MGWs.](187d05bf7ead21e1394b61320d8b3632_img.jpg) + +Diagram of Connection Model 3: CFB (UDUB), After Answer, Call locally switched. The diagram shows two planes: Control Signalling (top, green dashed box) and Non LCLS User Plane (bottom, black dotted box). The Control Signalling plane contains oMSC-S, GMSC-S, sMSC-S, and tMSC-S connected in a line. The User Plane contains oMGW, iMGW, sMGW, and tMGW connected in a line. Vertical blue lines connect each MSC-S to its corresponding MGW. On the left, tUE and oUE connect to an oBSS/tBSS block. A red 'User Plane Data' path loops within the oBSS/tBSS block, indicating a locally switched call. Termination points T1 through T8 are labeled within the MGWs. + +**Connection Model 3: CFB (UDUB), After Answer, Call locally switched** + +**Figure 13.4.3.2.7.1.1: Connection Model for Call Forwarding Busy UDUB** + +###### **13.4.3.2.7.2 Basic Sequence** + +Figure 13.4.3.2.7.2.1 shows the message sequence example for the call forwarding UDUB with a possible notification to the calling party using an announcement. In the example the sMSC server optionally requests the sMGW to play an announcement and to notify the announcement completion, after the bearer to the incoming side has been established. When the possible announcement has completed the sMSC server requests the establishment of the call and the bearer towards the forward-to subscriber. This example is based on examples from clause 6. + +![Sequence diagram for CFB UDUB Call establishment flow. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, GMSC, sMSC, sMGW, tMSC, tUE. The diagram shows 13 steps for call establishment, including CPG, FACILITY, MOD (T5), NOTIFY (T5), IAM, and APM messages.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +The diagram illustrates the call establishment flow for CFB UDUB. It involves the following components and steps: + +- oUE**: Originating User Equipment +- oBSS**: Originating Base Station System +- oMGW**: Originating Media Gateway +- oMSC**: Originating Mobile Switching Center +- iMGW**: Interworking Media Gateway +- GMSC**: Gateway Mobile Switching Center +- sMSC**: Serving Mobile Switching Center +- sMGW**: Serving Media Gateway +- tMSC**: Terminating Mobile Switching Center +- tUE**: Terminating User Equipment + +**Sequence of Messages:** + +- For call establishment towards served subscriber sUE see basic call establishment, figures 6.3.2.1 and 6.3.2.2 +1. CFB service active & calling party should be notified; expiry of no reply condition timer +2. Release termination to served UE: SUB request(Ts) / SUB reply (Ts) +3. CPG [Generic Notification indicator = call is diverting] (sMSC to sMGW) +4. MOD (T5): play announcement / send tone (sMSC to sMGW) +5. CPG [Generic Notification indicator = call is diverting] (sMSC to oMSC) +6. FACILITY with call forwarding notification (oMSC to oUE) +- Announcement / Tone (sMGW to oUE) +7. NOTIFY (T5): Announcement / Tone completed (sMGW to sMSC) +8. IAM [Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference] (sMSC to tMSC) +9. For call establishment towards forwarded-to subscriber tUE see basic call establishment, figure 6.3.2.1 +10. APM [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] (tMSC to sMSC) +11. APM [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] (sMSC to oMSC) +12. APM [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] (oMSC to oMGW) +13. For succeeding signalling sequence see Call Forwarding Unconditional, figure 13.4.2.5.2.2 steps 23 - 29. + +Sequence diagram for CFB UDUB Call establishment flow. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, GMSC, sMSC, sMGW, tMSC, tUE. The diagram shows 13 steps for call establishment, including CPG, FACILITY, MOD (T5), NOTIFY (T5), IAM, and APM messages. + +**Figure 13.4.3.2.7.2.1: CFB UDUB, Call establishment flow** + +- The sMSC server determines that call should be forwarded because of the Call Forwarding Busy UDUB supplementary service and that notification should be send towards the calling party (oUE). +- The sMSC server orders the sMGW to remove the bearer termination (Ts) towards the served mobile subscriber (in case when the radio resources had already been allocated in the sMGW). +- The sMSC server sends the CPG message with the Generic Notification Indicator parameter set to "Call is diverting". +- The sMSC server provides the sMGW with the announcement/tone identification and requests the sMGW to notify the announcement/tone completion using the Play Announcement or Send Tone procedure. +- The GMSC server sends the CPG message with the Generic Notification Indicator parameter set to "Call is diverting". +- The oMSC server notifies the calling user (oUE) about call forwarding. +- The sMGW notifies the sMSC server when the announcement/tone is completed using the Announcement Completed or Tone Completed procedure. +- If the sMSC server supports LCLS it may modify the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE before sending the IAM message containing the GCR with the encapsulated oBSS ID and the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. +- When performing further call establishment towards the forwarded-to subscriber see clause 6 and the procedure specified for mobile originating call. + +10. The tMSC server returns the APM message with the selected codec and if LCLS is supported, the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. +11. The sMSC server transfers the APM message with the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. If codec modification is required then the sMSC server includes the codec related information within the same APM message. +12. The GMSC server transfers the APM message. +13. When performing further call establishment see signalling sequence for Call Forwarding Unconditional, figure 13.4.2.5.2.2, steps 23 - 29. + +### 13.4.4 Call Forwarding on No Reply (CFNRy) + +#### 13.4.4.1 General + +The incoming call shall be offered to the served subscriber as a normal call. When the Call Forwarding on No Reply (CFNRy) supplementary service is active and if the call is not answered within the period of time defined by the no reply condition timer it shall be forwarded towards the forwarded-to subscriber. The basic call establishment procedures defined in the clause 6 shall be followed for the call towards the forwarded-to subscriber. + +#### 13.4.4.2 Call Clearing to the Served Subscriber + +When the MSC server determines that the call shall be forwarded due to the CFNRy it shall release the call leg towards the served subscriber as described in the sub-clause 7.1 for call clearing. + +#### 13.4.4.3 Notification to the Calling Subscriber + +If the MSC server determines that a call should be forwarded and the served mobile subscriber has requested that the calling subscriber shall receive a notification about the call forwarding, the MSC server shall send a notification to the preceding node. + +If the notification is implemented using intermediate tones or announcements the MSC server requests the MGW to play an announcement/tone to the calling party, as described in sub-clause 14.6, before establishing the call to the forwarded-to subscriber. + +#### 13.4.4.4 Initial Addressing + +If the incoming call is to be forwarded the call towards the forwarded-to subscriber is established as for a basic call. After the possible generation of in-band information has been completed the initial addressing towards the forwarded-to subscriber is performed as described in the clause 6 for the basic mobile terminating call. If the MSC server supports the LCLS feature and has received the GCR IE, the LCLS-Negotiation Request IE and LCLS-Configuration-Preference IE from a preceding node in the IAM it shall then forward the GCR IE and the resulting LCLS-Configuration-Preference IE and the LCLS-Negotiation Request IE to the succeeding node. + +#### 13.4.4.5 Backward LCLS Negotiation + +The procedure specified in sub-clause 6.2.1.2.2 for the intermediate node and in sub-clause 6.1.1.4 for the oMSC server shall be applied. + +#### 13.4.4.6 LCLS Through-Connection + +The procedure specified in sub-clause 6.1.1.5 shall be applied. + +#### 13.4.4.7 Example + +##### 13.4.4.7.1 Connection Model + +Figure 13.4.4.7.1.1 shows the network model for Call Forwarding on No Reply (CFNRy). + +The oMSC server seizes one context with two bearer terminations in the oMGW. The bearer termination T1 is used for the bearer towards the oBSS (calling subscriber) and the bearer termination T2 is used for the bearer towards the GMSC selected iMGW. The GMSC server seizes one context with two bearer terminations in the iMGW. The bearer termination T4 is used for the bearer towards the sMSC server selected sMGW and the bearer termination T3 is used for + +the bearer towards the preceding oMGW. The sMSC server seizes one context with two bearer terminations in the sMGW. The bearer termination T5 is used for the bearer towards the GMSC selected iMGW and bearer termination Ts is used for the bearer towards the sBSS (served subscriber). + +After Call Forwarding on No Reply is detected the sMSC server replaces the bearer termination for the served mobile subscriber Ts with the bearer termination for the forwarded-to subscriber T6 in an existing context in the sMGW. + +The tMSC server seizes one context with two bearer terminations in the tMGW. The bearer termination T7 is used for the bearer towards the sMSC selected sMGW and bearer termination T8 is used for the bearer towards the tBSS (forwarded-to subscriber). + +![Diagram showing network architecture with oUE, oBSS, oMGW, iMGW, sMGW, sBSS, sUE, oMSC-S, GMSC-S, and sMSC-S. Includes a legend for control plane and user plane links.](7722d62e33dcc894cc8555e9474c5606_img.jpg) + +- Control plane link which transmits signalling +- User plane link path through CN, connected or disconnected +- User plane link which transmits real user plane data within BSS and UEs +- • — User plane link which transmits real user plane data in backward direction from the CN towards oUE (e.g. announcement/tone, network provided ring-back tone) + +The diagram illustrates a network architecture. At the top, three MSC servers (oMSC-S, GMSC-S, sMSC-S) are connected horizontally by green dashed control plane links. Below them, corresponding gateways (oMGW, iMGW, sMGW) are connected vertically to their respective MSCs by solid blue lines. The gateways are connected horizontally by dotted black user plane links. On the far left, an oUE is connected to an oBSS via a red solid line. The oBSS is connected to the oMGW. On the far right, an sUE is connected to an sBSS via a red solid line, which is connected to the sMGW. A green dashed line labeled 'Control Signalling' connects the oBSS to the oMSC-S. Within the MGWs, terminations are labeled: oMGW (T1, T2, oC), iMGW (T3, T4, iC), sMGW (T5, Ts, sC). + +Diagram showing network architecture with oUE, oBSS, oMGW, iMGW, sMGW, sBSS, sUE, oMSC-S, GMSC-S, and sMSC-S. Includes a legend for control plane and user plane links. + +**Connection Model 1: Before CFNRy** + +![Diagram similar to the first one but with a blue dashed line indicating an announcement path from the sMGW back towards the oUE.](605ad256780bc1b6022dfb65a6e24a3b_img.jpg) + +This diagram, titled "Connection Model 2", shows the network state after CFNRy. It features the same components: oMSC-S, GMSC-S, sMSC-S, oBSS, oMGW, iMGW, and sMGW. A green dashed line for 'Control Signalling' connects oBSS to oMSC-S. A blue dash-dot line represents a backward user plane link for announcements, originating from the sMGW (at termination sC), passing through the iMGW (at termination iC), and the oMGW (at termination oC) towards the oBSS and oUE. The terminations are labeled: oMGW (T1, T2), iMGW (T3, T4), and sMGW (T5, Ts). + +Diagram similar to the first one but with a blue dashed line indicating an announcement path from the sMGW back towards the oUE. + +**Connection Model 2: After CFNRy, Announcement towards calling party** + +![Diagram of Connection Model 3: CFNRy, After Answer, Call locally switched. It shows a network architecture with oMSC-S, GMSC-S, sMSC-S, and tMSC-S in the control plane, and oMGW, iMGW, sMGW, and tMGW in the user plane. A UE is connected to an oBSS/tBSS which is linked to the oMGW. Control signaling is shown in green dashed lines, and user plane data in red solid lines.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) + +The diagram illustrates a network architecture for Connection Model 3: CFNRy, After Answer, Call locally switched. It consists of two main planes: Control Signalling (green dashed lines) and User Plane Data (red solid lines). + - **Control Signalling Path**: A UE (tUE/oUE) connects to an oBSS/tBSS. The oBSS/tBSS is connected to an oMSC-S via green dashed lines. The oMSC-S is connected to a GMSC-S, which is connected to an sMSC-S, which is connected to a tMSC-S, all via green dashed lines forming a control signaling loop. + - **User Plane Data Path**: The oBSS/tBSS is connected to an oMGW. The oMGW is connected to an iMGW, which is connected to an sMGW, which is connected to a tMGW. The path between these MGWs is labeled 'Non LCLS User Plane'. The red solid line indicates 'User Plane Data' flowing from the UEs through the oBSS/tBSS and looping back within it. + - **Internal Components**: Each MGW (oMGW, iMGW, sMGW, tMGW) contains internal termination points labeled T1 through T8, and control interfaces labeled oC, iC, sC, and tC connected to their respective MSC servers. + +Diagram of Connection Model 3: CFNRy, After Answer, Call locally switched. It shows a network architecture with oMSC-S, GMSC-S, sMSC-S, and tMSC-S in the control plane, and oMGW, iMGW, sMGW, and tMGW in the user plane. A UE is connected to an oBSS/tBSS which is linked to the oMGW. Control signaling is shown in green dashed lines, and user plane data in red solid lines. + +**Connection Model 3: CFNRy, After Answer, Call locally switched** + +**Figure 13.4.4.7.1.1: Connection Model for Call Forwarding on No Reply** + +##### 13.4.4.7.2 Basic Sequence + +Figure 13.4.4.7.2.1 shows the message sequence example for the Call Forwarding on No Reply with a possible notification to the calling party using an announcement. In the example the sMSC server optionally requests the sMGW to play an announcement and to notify the announcement completion, after the bearer to the incoming side has been established. When the possible announcement has completed the sMSC server requests the establishment of the call and the bearer towards the forward-to subscriber. This example is based on examples from clause 6. + +![Sequence diagram for CFNRy Call establishment flow. Lifelines from left to right: oUE, oBSS, oMGW, oMSC, iMGW, GMSC, sMSC, sMGW, tMSC, tUE. The diagram shows 13 steps including service activation, bearer termination, CPG messages, FACILITY notification, announcement/tone playback, and LCLS negotiation via IAM and APM messages.](2cf3896394a2342a2b46c504ab9a8830_img.jpg) + +For call establishment towards served subscriber sUE see basic call establishment, figures 6.3.2.1 and 6.3.2.2 + +1. CFNRy service active & calling party should be notified; expiry of no reply condition timer (at sMSC) +2. Release termination to served UE: SUB request(Ts) / SUB reply (Ts) (between sMSC and sMGW) +3. CPG [Generic Notification indicator = call is diverting] (from sMSC to GMSC) +4. MOD (T5): play announcement / send tone (between sMSC and sMGW) +5. CPG [Generic Notification indicator = call is diverting] (from GMSC to oMSC) +6. FACILITY with call forwarding notification (from oMSC to oUE) +- Announcement / Tone (from sMGW towards oUE) +7. NOTIFY (T5): Announcement / Tone completed (from sMGW to sMSC) +8. IAM [Codec List, GCR, LCLS-Negotiation Request, LCLS-Configuration-Preference] (from sMSC to tMSC) +9. For call establishment towards forwarded-to subscriber tUE see basic call establishment, figure 6.3.2.1 +10. APM [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] (from tMSC to sMSC) +11. APM [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] (from sMSC to GMSC) +12. APM [SCt, ACLt, LCLS-Negotiation Response, LCLS-Configuration-Preference] (from GMSC to oMSC) +13. For succeeding signalling sequence see Call Forwarding Unconditional, figure 13.4.2.5.2.2 steps 23 - 29. + +Sequence diagram for CFNRy Call establishment flow. Lifelines from left to right: oUE, oBSS, oMGW, oMSC, iMGW, GMSC, sMSC, sMGW, tMSC, tUE. The diagram shows 13 steps including service activation, bearer termination, CPG messages, FACILITY notification, announcement/tone playback, and LCLS negotiation via IAM and APM messages. + +**Figure 13.4.4.7.2.1: CFNRy, Call establishment flow** + +- The sMSC server determines that call should be forwarded because of the Call Forwarding on No Reply supplementary service and that notification should be send towards the calling party (oUE). +- The sMSC server orders the sMGW to remove the bearer termination (Ts) towards the served mobile subscriber (in case when the radio resources had already been allocated in the sMGW). +- The sMSC server sends the CPG message with the Generic Notification Indicator parameter set to "Call is diverting". +- The sMSC server provides the sMGW with the announcement/tone identification and requests the sMGW to notify the announcement/tone completion using the Play Announcement or Send Tone procedure. +- The GMSC server sends the CPG message with the Generic Notification Indicator parameter set to "Call is diverting". +- The oMSC server notifies the calling user (oUE) about call forwarding. +- The sMGW notifies the sMSC server when the announcement/tone is completed using the Announcement Completed or Tone Completed procedure. +- If the sMSC server supports LCLS it may modify the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE before sending the IAM message containing the GCR with the encapsulated oBSS ID, the LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. + +9. When performing further call establishment towards the forwarded-to subscriber see clause 6, the procedure specified for mobile originating call. +10. The tMSC server returns the APM message with the selected codec and if LCLS is supported, the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. +11. The sMSC server transfers the APM message with the LCLS-Negotiation Response IE and the LCLS-Configuration-Preference IE. If codec modification is required then the sMSC server includes the codec related information within the same APM message. +12. The GMSC server transfers the APM message. +13. When performing further call establishment see signalling sequence for Call Forwarding Unconditional, figure 13.4.2.5.2.2, steps 23 -29. + +### 13.4.5 Call Forwarding on mobile subscriber Not Reachable (CFNRc) + +#### 13.4.5.1 General + +The incoming call that meets mobile subscriber unreachable shall be forwarded towards the forwarded-to subscriber without being offered to the served mobile subscriber. The basic call establishment procedures defined in the clause 6 shall be followed for the call towards the forwarded-to subscriber. + +#### 13.4.5.2 Rerouting by HLR + +The same handling as for Call Forwarding Unconditional applies. + +#### 13.4.5.3 Rerouting by VLR + +The same handling as for Call Forwarding Unconditional applies. + +## 13.5 Call Waiting (CW) + +### 13.5.1 Principles + +The procedures specified for the Call Waiting supplementary service in 3GPP TS 23.205 [2] sub-clause 13.6 for BICC based CS Core Network and in 3GPP TS 23.231 [3] sub-clause 13.6 for SIP-I based CS Core Network shall be followed with the following modifications: + +- The call establishment and call clearing procedures defined in clauses 6 and 7 shall be applied. +- If the new call is accepted, the GCR of the new call is sent to the BSS in the ASSIGNMENT procedure + +The following sub-clauses describe the additional requirements related to the LCLS functionality when the Call Waiting supplementary service is activated for the locally switched call. + +### 13.5.2 Accept the new incoming call, the original call is hold + +#### 13.5.2.1 General + +When new call arrives and is accepted, the GCR and LCLS-Configuration of the local access bearer shall be modified according to the new call. The MSC Server shall initiate an ASSIGNMENT REQUEST message towards the BSS including the GCR and LCLS-Configuration of the new call. + +#### 13.5.2.2 Example + +##### 13.5.2.2.1 Connection Model + +Figure 13.5.2.2.1.1 shows the network model for Call Waiting supplementary service of holding the original call to accept the new call. Termination T1 to T6 is established for original call between UE-A and UE-B. When UE-A and UE-B have an active call established, UE-C, which is roaming under BSS-B and MSC-B, initiates a new call towards UE-A. To accept the new call, UE-A holds the call with UE-B and relocates its access bearer for the new call. + +After the new call between UE-C and UE-A is established, a new context (C1-2) is seized in MGW-A. The access bearer termination T6 is moved from C1 to C1-2 and a new network bearer towards the iMGW is created (T7). In the iMGW, a new context (iC-2) is created with terminations for the bearers with MGW-A (T8) and with MGW-B (T9). In MGW-B, new terminations are created for the access bearer towards UE-C (T11) and for bearer towards iMGW (T10). + +![Diagram showing Connection Model 1: Before new call incoming. It illustrates the network architecture with MSC-B, iMSC, MSC-A, BSS-A/BSS-B, MGW-B, iMGW, and MGW-A. UE-A and UE-B are connected to BSS-A/BSS-B. Control plane links are shown as green dashed lines, user plane links as red solid lines, and announcement/tone links as blue dashed lines. Termination points T1 through T6 are labeled on the MGWs.](e417ae35ab07134888be901c201d54cd_img.jpg) + +- - - - - Control plane link which transmits signalling +- . . . . . User plane link path through CN, connected or disconnected +- User plane link which transmits real user plane data within BSS and UEs +- · — · Announcement / tone + +Diagram showing Connection Model 1: Before new call incoming. It illustrates the network architecture with MSC-B, iMSC, MSC-A, BSS-A/BSS-B, MGW-B, iMGW, and MGW-A. UE-A and UE-B are connected to BSS-A/BSS-B. Control plane links are shown as green dashed lines, user plane links as red solid lines, and announcement/tone links as blue dashed lines. Termination points T1 through T6 are labeled on the MGWs. + +**Connection Model 1: Before new call incoming** + +![Diagram showing Connection Model 2: Incoming call is established, UE-B held, Announcement towards UE-B. This diagram shows the state after a new call is established between UE-A and UE-C, while the original call with UE-B is held. New termination points T7 through T11 are shown, and a blue dashed announcement line is directed towards UE-B.](237b76118be454462fc9b4e96adaa6c7_img.jpg) + +Diagram showing Connection Model 2: Incoming call is established, UE-B held, Announcement towards UE-B. This diagram shows the state after a new call is established between UE-A and UE-C, while the original call with UE-B is held. New termination points T7 through T11 are shown, and a blue dashed announcement line is directed towards UE-B. + +**Connection Model 2: Incoming call is established, UE-B held, Announcement towards UE-B** + +**Figure 13.5.2.2.1.1: Connection Model for Accept Incoming call, original call is held** + +##### **13.5.2.2.2 Basic Sequence** + +Figure 13.5.2.2.2.1 shows the message sequence example for the acceptance of new call and hold the original one. The ASSIGNMENT REQUEST message is sent from MSC-A to BSS-A to update the GCR stored within the BSS-A. + +![Sequence diagram for Figure 13.5.2.2.2.1: Accept Incoming call, original call is held. The diagram shows the interaction between UE-A, BSS-A, MGW-A, MSC-A, iMGW, iMSC, MSC-B, MGW-B, BSS-B, UE-B, and UE-C. The process involves an incoming call from UE-C to UE-A, which results in the existing call between UE-A and UE-B being put on hold. The diagram includes numbered steps 1 through 14, with some steps being normal LCLS call establishment procedures. Red arrows indicate 'Call is locally Switched' at the beginning and end of the sequence.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) + +The sequence diagram illustrates the following interactions: + +- Initial State:** A call between UE-A and UE-B is active. A red arrow labeled "Call is locally Switched" spans from UE-A to UE-B. +- Incoming Call (UE-C to UE-A):** + - UE-C sends a **1. SETUP** message to MSC-B. + - MSC-B responds with **2. CALL PROCEEDING**. + - MSC-B sends an **3. IAM** message (Codec List, GCR(new), LCLS-Negotiation Request, LCLS-Configuration-Preference) to iMSC. + - iMSC transfers the **4. IAM** message to MSC-A. + - MSC-A determines **5. UE-A busy, Call waiting available**. + - MSC-A sends a **6. SETUP** message to UE-A. + - UE-A responds with **7. CALL CONFIRMED**. + - 8. normal LCLS call establishment procedure between UE-A and UE-C from step 8 to 17 in 6.3.2** is initiated. +- Hold Original Call (UE-A to UE-B):** + - UE-A sends a **9. HOLD** message to MSC-A. + - 10. The session between UE-A and UE-B is put on hold**. + - MSC-A sends a **11. HOLD ACKNOWLEDGE** message to UE-A. +- Finalize Incoming Call:** + - MSC-A sends a **12. CONNECT** message to UE-A. + - MSC-A performs **13. Move access side termination: MOV request (T6) / MOV reply (T6)** with Context (C1-2). + - 14. normal LCLS call establishment procedure between UE-A and UE-C from step 19 in 6.3.2, skipping step 21, 22, 23 and 24.** is completed. + - Final State:** A red arrow labeled "Call is locally Switched" spans from UE-A to UE-C. + +Sequence diagram for Figure 13.5.2.2.2.1: Accept Incoming call, original call is held. The diagram shows the interaction between UE-A, BSS-A, MGW-A, MSC-A, iMGW, iMSC, MSC-B, MGW-B, BSS-B, UE-B, and UE-C. The process involves an incoming call from UE-C to UE-A, which results in the existing call between UE-A and UE-B being put on hold. The diagram includes numbered steps 1 through 14, with some steps being normal LCLS call establishment procedures. Red arrows indicate 'Call is locally Switched' at the beginning and end of the sequence. + +**Figure 13.5.2.2.2.1: Accept Incoming call, original call is held** + +- UE-C sends a SETUP message to the Core Network. +- MSC-B responds with CALL PROCEEDING message. +- MSC-B sends the IAM message including supported codecs list, GCR with encapsulated BSS-B ID, LCLS-Negotiation Request IE and the LCLS-Configuration-Preference IE. +- iMSC transfers the IAM message to MSC-A. +- MSC-A determines that UE-A is busy and that call waiting is available. +- MSC-A sends a SETUP message to UE-A. +- UE-A responds with CALL CONFIRM message. +- The normal LCLS call establishment procedures from step 8 to 17 in 6.3.2 are applied. +- UE-A requests to hold the call with UE-B. +- The session between UE-A and UE-B is put on hold. The procedure in 13.6.2.3.2 is applied. +- After the session between UE-A and UE-B is put on hold, MSC-A sends the acknowledgement to UE-A. + +12. UE-A accepts the incoming call by sending CONNECT message to MSC-A. +13. MSC-A requests the MGW to move the termination T6 to the context of incoming call (C1-2). +14. The normal LCLS call establishment procedures from step 19 in 6.3.2 are applied, skipping step 21, 22 a, 22b, 23 and 24. BSS-A shall update the GCR and the LCLS-Configuration on receipt of the ASSIGNMENT REQUEST message for the access bearer. + +## 13.6 Call Hold (CH) + +### 13.6.1 Principles + +The procedures specified for the Call Hold supplementary service in 3GPP TS 23.205 [2] sub-clause 13.6 for BICC based CS Core Network and in 3GPP TS 23.231 [3] sub-clause 13.6 for SIP-I based CS Core Network shall be followed with the following modifications: + +- The call establishment and call clearing procedures defined in clauses 6 and 7 shall be applied. +- If a new call is established after the original call is held, the MSC shall generate a new GCR for the new call. + +The following sub-clauses describe the additional requirements related to the LCLS functionality when the Call Hold supplementary service is activated for the locally switched call. + +### 13.6.2 Call Hold after Answer, LCLS established + +#### 13.6.2.1 Hold Request + +When the UE makes a request for the hold function for the locally switched call the MSC server shall request a LCLS break procedure described in sub-clause 7.2.1. + +The MSC server shall request the MGW to interrupt the communication on the bearer by changing the through-connection of the bearer termination towards the served mobile subscriber to "inactive" or by using the Isolate Bearer Termination Procedure. + +If an announcement is to be applied to the held party the MSC shall apply the procedure for non LCLS call defined in 3GPP TS 23.205 [2] sub-clause 14.6 for BICC based CS Core Network and in 3GPP TS 23.231 [3] sub-clause 14.6 for SIP-I based CS Core Network. + +If a handover occurs to the UE making the request for the hold function (UE-A) while the party is not intended to be re-connected locally then the MSC Server shall include LCLS-Connection-Status-Control set to "do not establish LCLS" in the HO Request message. + +#### 13.6.2.2 Retrieval Request + +When the UE makes a request to retrieve a held call the MSC server shall stop an announcement that was applied to the held party. The MSC shall request the MGW to re-establish communication to the held party by changing the through-connection of the bearer termination towards the served mobile subscriber to be both-way through-connected or by using the Join Bearer Termination Procedure. + +If the call has been successfully negotiated for LCLS and an LCLS break was triggered by the CN the MSC server shall perform a LCLS re-establishment as described in sub-clause 7.3.1. + +NOTE: LCLS re-negotiation can occur while the call is on hold or the held call is connected to a new party (ECT) which may change the LCLS configuration and thus permit or prevent LCLS. + +#### 13.6.2.3 Example + +##### 13.6.2.3.1 Connection Model + +Figure 13.6.2.3.1.1 shows the network model for Call Hold supplementary service when LCLS was established. The MSC-B server seizes one context with two bearer terminations in the MGW-B. The bearer termination T1 is used for the bearer towards the BSS-B and the bearer termination T2 is used for the bearer towards the iMSC selected iMGW. The iMSC server seizes one context with two bearer terminations in the iMGW. The bearer termination T4 is used for the bearer towards the MSC-A server selected MGW-A and the bearer termination T3 is used for the bearer towards the + +preceding MGW-B. The MSC-A server seizes one context with two bearer terminations in the MGW-A. The bearer termination T5 is used for the bearer towards the iMSC selected iMGW and bearer termination T6 is used for the bearer towards the BSS-A. + +![Diagram showing Connection Model 1: Before Call Hold, LCLS established. It illustrates control signaling (green dashed lines) and user plane data (red solid lines) paths between UE-A, UE-B, BSS-A/B, MSC-S-B, iMSC-S, MSC-S-A, MGW-B, iMGW, and MGW-A. A legend at the top defines the line types: green dashed for control plane, black dotted for user plane through CN, red solid for user plane within BSS/UEs, and blue dash-dot for announcements.](50ef8602c7c9edd2da0e2133e772c2a2_img.jpg) + +Legend: + --- Control plane link which transmits signalling + ... User plane link path through CN, connected or disconnected + \_\_\_ User plane link which transmits real user plane data within BSS and UEs + -.- Announcement / tone + +Diagram showing Connection Model 1: Before Call Hold, LCLS established. It illustrates control signaling (green dashed lines) and user plane data (red solid lines) paths between UE-A, UE-B, BSS-A/B, MSC-S-B, iMSC-S, MSC-S-A, MGW-B, iMGW, and MGW-A. A legend at the top defines the line types: green dashed for control plane, black dotted for user plane through CN, red solid for user plane within BSS/UEs, and blue dash-dot for announcements. + +**Connection Model 1: Before Call Hold, LCLS established and** + +**Connection Model 3: After Retrieval procedure, LCLS established** + +![Diagram showing Connection Model 2: After Hold procedure, LCLS released; Announcement towards held party. This diagram shows the state after a hold procedure where the user plane is released (indicated by an 'X' on the red line from UE-B) and an announcement path (blue dash-dot line) is established from MGW-A back towards the BSS.](ad555483986d7170a46ce72d164b5bc8_img.jpg) + +Diagram showing Connection Model 2: After Hold procedure, LCLS released; Announcement towards held party. This diagram shows the state after a hold procedure where the user plane is released (indicated by an 'X' on the red line from UE-B) and an announcement path (blue dash-dot line) is established from MGW-A back towards the BSS. + +**Connection Model 2: After Hold procedure, LCLS released; Announcement towards held party** + +**Figure 13.6.2.3.1.1: Connection Model for Call Hold** + +##### 13.6.2.3.2 Basic Sequence + +Figure 13.6.2.3.2.1 shows the message sequence example for the Hold procedure with a possible notification to the held party using an announcement. In the example the MSC server requests the MGW to play an announcement towards the held party. + +![Sequence diagram for Hold Request on LCLS call. The diagram shows the interaction between UE-B, BSS-B, MGW-B, MSC-B, iMGW, iMSC, MSC-A, MGW-A, BSS-A, and UE-A. A red arrow at the top indicates 'Call is locally Switched' between UE-B and UE-A. The sequence of messages is: 1. HOLD from UE-A to MSC-A; 2. MSC accepts HOLD request; 3. Release LCLS; 4. MOD request (T6): inactive / Context (tC) from MSC-A to MGW-A; 5. CPG [Generic Notification Indicator = 'remote hold'] from MSC-A to iMSC; 6. CPG [Generic Notification Indicator = 'remote hold'] from iMSC to MSC-B; 7. FACILITY with call hold notification from MSC-B to UE-B; 8. HOLD ACKNOWLEDGE from MSC-A to UE-A; 9. MOD request (T5): Play announcement / Context (tC) from MSC-A to MGW-A. A blue arrow at the bottom indicates 'Announcement' from MGW-A to UE-B. A note between steps 3 and 4 states: 'For LCLS release procedure initiated by MSC server see the corresponding signalling sequence in sub-clause 7.2.1'.](56a5265d174ce056c1dbe5e7a60839fc_img.jpg) + +Sequence diagram for Hold Request on LCLS call. The diagram shows the interaction between UE-B, BSS-B, MGW-B, MSC-B, iMGW, iMSC, MSC-A, MGW-A, BSS-A, and UE-A. A red arrow at the top indicates 'Call is locally Switched' between UE-B and UE-A. The sequence of messages is: 1. HOLD from UE-A to MSC-A; 2. MSC accepts HOLD request; 3. Release LCLS; 4. MOD request (T6): inactive / Context (tC) from MSC-A to MGW-A; 5. CPG [Generic Notification Indicator = 'remote hold'] from MSC-A to iMSC; 6. CPG [Generic Notification Indicator = 'remote hold'] from iMSC to MSC-B; 7. FACILITY with call hold notification from MSC-B to UE-B; 8. HOLD ACKNOWLEDGE from MSC-A to UE-A; 9. MOD request (T5): Play announcement / Context (tC) from MSC-A to MGW-A. A blue arrow at the bottom indicates 'Announcement' from MGW-A to UE-B. A note between steps 3 and 4 states: 'For LCLS release procedure initiated by MSC server see the corresponding signalling sequence in sub-clause 7.2.1'. + +**Figure 13.6.2.3.2.1: Hold Request on LCLS call** + +1. HOLD message is received from the UE-A. +2. The MSC-A server accepts the HOLD request. +3. The MSC-A server requests a LCLS break procedure described in sub-clause 7.2.1. +4. The MSC-A server requests the MGW-A to interrupt the communication on the bearer by changing the through-connection of the bearer termination towards the UE-A to "inactive". +5. The MSC-A server sends the CPG message with the Generic Notification Indicator parameter set to "remote hold" to the iMSC. +6. The iMSC server transfers the CPG message to the MSC-B server. +7. The MSC-B server sends FACILITY message with the call hold notification to the UE-B. +8. The MSC-A server informs the UE-A that call hold is accepted with the HOLD ACKNOWLEDGE message. +9. The MSC-A server requests the MGW-A to play an announcement towards the held party. + +Figure 13.6.2.3.2.2 shows the message sequence for the Retrieval procedure. + +![Sequence diagram for Retrieval Request and LCLS re-establishment. The diagram shows interactions between UE-B, BSS-B, MGW-B, MSC-B, iMGW, iMSC, MSC-A, MGW-A, BSS-A, and UE-A. A blue arrow labeled 'Announcement' points from UE-A to UE-B. A red arrow labeled 'Call is locally Switched' points from UE-A to UE-B. A red box labeled '9. LCLS Re-establishment' is shown.](fd3cbb53e991f8209ba17b398f426e13_img.jpg) + +The diagram illustrates the signaling sequence for Retrieval Request and LCLS re-establishment. The participants are UE-B, BSS-B, MGW-B, MSC-B, iMGW, iMSC, MSC-A, MGW-A, BSS-A, and UE-A. The sequence of messages is as follows: + +- UE-A sends a RETRIEVE message to MSC-A. +- MSC-A accepts the RETRIEVE request. +- MSC-A sends a MOD request (T5) to MGW-A to stop an announcement towards the held party. Context (tC) is included. +- MSC-A sends a MOD request (T6) to MGW-A to re-establish communication to the held party. Context (tC) is included. +- MSC-A sends a CPG message with the Generic Notification Indicator parameter set to "remote retrieval" to the iMSC. +- The iMSC server transfers the CPG message to the MSC-B server. +- The MSC-B server sends a FACILITY message with the call hold notification to the UE-B. +- The MSC-A server informs the UE-A that retrieve request is accepted with the RETRIEVE ACKNOWLEDGE message. +- If the call has been successfully negotiated for LCLS the MSC-A server requests a LCLS re-establishment procedure as described in sub-clause 7.3.1. + +For LCLS re-establishment procedure initiated by MSC server see the corresponding signalling sequence in sub-clause 7.3.1 + +Sequence diagram for Retrieval Request and LCLS re-establishment. The diagram shows interactions between UE-B, BSS-B, MGW-B, MSC-B, iMGW, iMSC, MSC-A, MGW-A, BSS-A, and UE-A. A blue arrow labeled 'Announcement' points from UE-A to UE-B. A red arrow labeled 'Call is locally Switched' points from UE-A to UE-B. A red box labeled '9. LCLS Re-establishment' is shown. + +**Figure 13.6.2.3.2.2: Retrieval Request and LCLS re-establishment** + +1. RETRIEVE message is received from the UE-A. +2. The MSC-A server accepts the RETRIEVE request. +3. The MSC-A server requests the MGW-A to stop an announcement towards the held party. +4. The MSC-A server requests the MGW-A to re-establish communication to the held party by changing the through-connection of the bearer termination towards the UE-A to be both-way through-connected. +5. The MSC-A server sends the CPG message with the Generic Notification Indicator parameter set to "remote retrieval" to the iMSC. +6. The iMSC server transfers the CPG message to the MSC-B server. +7. The MSC-B server sends FACILITY message with the call hold notification to the UE-B. +8. The MSC-A server informs the UE-A that retrieve request is accepted with the RETRIEVE ACKNOWLEDGE message. +9. If the call has been successfully negotiated for LCLS the MSC-A server requests a LCLS re-establishment procedure as described in sub-clause 7.3.1. + +### 13.6.3 Call Hold after Answer, LCLS not established + +#### 13.6.3.1 Hold Request + +When the UE makes a request for the hold function for the non-local call the MSC server shall signal LCLS-CONNECT\_CONTROL message with LCLS-Connection-status-control set to "do not establish LCLS". + +NOTE: this is to avoid the case that the party requesting hold (which is no longer intended to be connected to the held party) performs a handover into the same BSS and triggers local switching in the BSS. + +#### 13.6.3.2 Retrieval Request + +When the UE makes a request to retrieve a held call the MSC server shall stop an announcement that was applied to the held party. The MSC shall request the MGW to re-establish communication to the held party by changing the through-connection of the bearer termination towards the served mobile subscriber to be both-way through-connected or by using the Join Bearer Termination Procedure. + +If the call has been successfully negotiated for LCLS then MSC server shall signal LCLS-CONNECT\_CONTROL message with LCLS-Connection-status-control set to "connect". If the BSS established local switching it shall notify the core network. + +### 13.6.4 Establishment of a new call, the original call is hold + +#### 13.6.4.1 General Principle + +The call hold procedures and call establishment procedures shall be applied with the following enhancements. + +To avoid the local switching between remote parties of the new call and the held call, the new call shall have a different GCR than the GCR of the original call. During the new call establishment, the MSC server serving the UE which has the held call and has initiated the new call shall generate a new GCR for the new call. + +The MSC server shall use the ASSIGNMENT REQUEST message to update the BSS serving the UE which has the held call and has initiated the new call with the new GCR and LCLS-Configuration for the new call. + +The access bearer is kept unchanged. + +#### 13.6.4.2 Assignment Request + +During the new call establishment, the MSC server serving the UE which has the held call and has initiated the new call shall send the Assignment Request message to update the BSS with the new GCR and LCLS-Configuration for the new call. + +On receipt of Assignment Request, the BSS shall save the GCR and LCLS-Configuration in this message. + +### 13.6.5 Retrieval of the held call, ongoing call is on-hold/completed + +#### 13.6.5.1 General Principle + +When the UE requests to place the new call on hold and retrieve the original call, the MSC server shall initiate normal call hold procedures as described in sub-clause 13.6.1 for the new call. The MSC server sends the ASSIGNMENT REQUEST message with the GCR and LCLS-Configuration of the original call to the BSS. The MSC server continues the retrieval procedure as described in sub-clause 13.6.2.2. + +When the UE requests to retrieve the original call after the active session has completed, the MSC server shall send the ASSIGNMENT REQUEST message to the BSS to update the GCR and LCLS-Configuration for the original call. The MSC server continues the retrieval procedures as described in sub-clause 13.6.2.2. + +#### 13.6.5.2 Example call flow, Retrieval of held call after ongoing call has completed + +![Sequence diagram for Figure 13.6.5.2.1: Retrieval of held call, ongoing call has completed. The diagram shows a sequence of messages between various network elements: UE-B, BSS-B, MGW-B, MSC-B, iMGW, iMSC, MSC-A, MGW-A, BSS-A, UE-A, MSC-C, MGW-C, BSS-C, and UE-C. The sequence starts with an 'Announcement' message from UE-B to UE-A. Then, a message 'There are ongoing session between UE-A and UE-C' is shown. Step 1: 'The session is release' from UE-A to MSC-A. Step 2: 'RETRIEVE' from UE-A to MSC-A. Step 3: 'MSC accepts RETRIEVE request' from MSC-A to UE-A. Step 4: 'ASSIGNMENT REQUEST (GCR(held), LCLS-Configuration(held))' from MSC-A to BSS-A. Step 5: 'ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call cannot be locally switched")' from BSS-A to MSC-A. Step 6: 'continues retrieval signalling sequence in sub-clause 13.6.2.3.2' from MSC-A to UE-A.](30387053b5b3fede6873f6a46a9ca4a9_img.jpg) + +Sequence diagram for Figure 13.6.5.2.1: Retrieval of held call, ongoing call has completed. The diagram shows a sequence of messages between various network elements: UE-B, BSS-B, MGW-B, MSC-B, iMGW, iMSC, MSC-A, MGW-A, BSS-A, UE-A, MSC-C, MGW-C, BSS-C, and UE-C. The sequence starts with an 'Announcement' message from UE-B to UE-A. Then, a message 'There are ongoing session between UE-A and UE-C' is shown. Step 1: 'The session is release' from UE-A to MSC-A. Step 2: 'RETRIEVE' from UE-A to MSC-A. Step 3: 'MSC accepts RETRIEVE request' from MSC-A to UE-A. Step 4: 'ASSIGNMENT REQUEST (GCR(held), LCLS-Configuration(held))' from MSC-A to BSS-A. Step 5: 'ASSIGNMENT COMPLETE (LCLS-BSS-Status = "call cannot be locally switched")' from BSS-A to MSC-A. Step 6: 'continues retrieval signalling sequence in sub-clause 13.6.2.3.2' from MSC-A to UE-A. + +**Figure 13.6.5.2.1: Retrieval of held call, ongoing call has completed** + +1. The active session between UE-A and UE-C is released. +2. The RETRIEVE message is sent from UE-A to MSC-A Server. +3. MSC-A server accepts the RETRIEVE request. +4. MSC-A server retrieves the LCLS-Configuration and GCR for the held session and sends the ASSIGNMENT REQUEST message to BSS-A including the LCLS-Configuration IE and the GCR IE. +5. The BSS-A returns the ASSIGNMENT COMPLETE message with the LCLS-BSS-Status IE indicating "call not possible to be locally switched". +6. MSC-A server continues the sequence handling described in sub-clause 13.6.2.3.2. + +## 13.7 Multiparty (MPTY) + +If LCLS is established for a call it shall be released while the Multiparty (MPTY) service is utilised, see LCLS break procedure in clause 7.2 of this specification. After MPTY is ended LCLS may be re-established if it is still feasible, see LCLS re-establishment procedure in clause 7.3 of this specification. + +## 13.8 Closed User Group (CUG) + +No impact. There are no LCLS related requirements for the Closed User Group (CUG) service. + +## 13.9 Advice of Charge (AoC) + +No impact. There are no LCLS related requirements for the Advice of Charge (AoC) service. + +## 13.10 User-to-User Signalling (UUS) + +No impact. There are no LCLS related requirements for the User-to-User Signalling (UUS) service. + +## 13.11 Call Barring Services + +No impact. There are no LCLS related requirements for the Call Barring Services. + +## 13.12 Explicit Call Transfer (ECT) + +In order to perform Explicit Call Transfer, if LCLS is established for the first call this will be broken when it is put on hold as per the procedures specified in sub-clause 13.6. If LCLS is established for the second call then the local switching of the call shall be released in order to be connected to the held party. + +Procedures to establish LCLS for the transferred call are not supported. + +## 13.13 Completion of Calls to Busy Subscriber (CCBS) + +No impact. There are no LCLS related requirements for the Completion of Calls to Busy Subscriber (CCBS) service. + +## 13.14 Multiple Subscriber Profile (MSP) + +No impact. There are no LCLS related requirements for the Multiple Subscriber Profile (MSP) service. + +## 13.15 Multicall + +There are no specific LCLS related requirements for the Multicall service. + +NOTE: If LCLS is established for any call as part of the Multicall service, then the local switching of the call will be released when it is put on hold as per the procedures specified in sub-clause 13.6. + +## 13.16 Calling Name Presentation (CNAP) + +No impact. There are no LCLS related requirements for the Calling Name Presentation (CNAP) service. + +## 13.17 Alternate Speech/Fax + +LCLS shall not be allowed for the Alternate Speech/Fax calls. + +## 13.18 Modification of the Access Bearer + +During the call establishment phase, the modification of the access bearer procedure shall be performed in accordance with 3GPP 23.205 [2] for a BICC based CS core network and in accordance with 3GPP TS 23.231 [3] for a SIP-I based CS core network. + +When the call is locally switched, if the MSC Server requires modification of the access bearer, an LCLS Break procedure as specified in sub-clause 7.2.1 may occur. + +## 13.19 GSM Fax + +LCLS shall not be allowed for the GSM Fax calls. + +## 13.20 Voice group call service (VGCS), Voice broadcast service (VBS) + +LCLS shall not be allowed when the Voice group call service (VGCS) or the Voice broadcast service (VBS) is utilised. + +# --- 14 Interactions with Other Network Features and Services + +## 14.1 Customised Applications for Mobile network Enhanced Logic (CAMEL) + +No impact. There are no LCLS related requirements for Customised Applications for Mobile network Enhanced logic (CAMEL). + +If LCLS is established for the call and a CAMEL service requires the insertion of Tones/Announcements, the LCLS procedures for Providing Tones or Announcements shall be applied as specified in sub-clause 14.6. + +If LCLS is established for the call and a CAMEL service requires the user-plane to be manipulated within the Core Network, the LCLS procedures for breaking LCLS shall be applied as specified in sub-clause 7.2. + +## 14.2 IST + +No impact. There are no LCLS related requirements for Immediate Service Termination (IST). + +## 14.3 Operator Determined Barring (ODB) + +No impact. There are no LCLS related requirements for Operator Determined Barring (ODB). + +## 14.4 DTMF + +No impact. There are no LCLS related requirements for DTMF. + +If LCLS is established for the call and a DTMF tone is required to be sent to the UE, the LCLS procedures for Providing Tones or Announcements shall be applied as specified in sub-clause 14.6. + +## 14.5 OR + +No impact. There are no LCLS related requirements for Optimal Routing (OR). + +## 14.6 Providing tones or announcements + +### 14.6.1 General + +Tones or announcements may be applied at any time during the call establishment or mid-call. Also periodic tones may be applied during the call. Prior to answer, an LCLS compatible call is still connected through the core network and so any tones or announcements applied at this time are handled as for normal non-LCLS calls. + +If a node wishes to apply periodic tones during the call it may either reject the LCLS entirely or may indicate that it requires send access in a certain direction. This is achieved during the LCLS negotiation phase as described in sub-clause 4.2. + +If the call is established and local switching is performed and at a later point in the call a (G)MSC Server needs to send a tone or announcement there are two options it may apply: + +- perform a (G)MSC initiated LCLS break as described in sub-clause 7.2.1 and once the LCLS break is complete then begin applying the tone or announcement, or +- request temporary send access to the user plane as described in 14.6.2 + +If a node (subsequent CN node or BSS) does not support the procedures described for requesting temporary send access then a full LCLS break shall occur. + +### 14.6.2 Handling of tones or announcements during an LCLS call + +#### 14.6.2.1 GMSC Server or intermediate node requiring temporary send access to apply tone or announcement + +A GMSC Server or intermediate node wishing to insert a tone or announcement may signal LCLS Configuration Change Request message with LCLS-Configuration-Preference IE setting "Need Send Backward = yes" if it needs to insert a tone or announcement towards the originating subscriber or "Need Send Forward = yes" if it needs to insert a tone or announcement towards the terminating subscriber. When GMSC Server sends the LCLS Configuration Change Request message it shall start LCLS\_configuration\_modification timer. + +NOTE: The (G)MSC Server or intermediate node only needs to signal the LCLS Configuration Change Request message in the direction in which it wishes to apply the tone or announcement. The other LCLS-Configuration-Preference IE settings remain unchanged. + +When the (G)MSC receives the LCLS Configuration Change Request Acknowledge message it shall stop the LCLS\_configuration\_modification timer. If the received LCLS-Configuration-Change Result IE indicates acceptance of the requested LCLS Configuration change it shall proceed to insert its tone or announcement as per a normal call handling. + +Otherwise, if the received LCLS-Configuration-Change Result IE indicates the requested LCLS Configuration change is rejected or if the LCLS\_configuration\_modification timer expires, the (G)MSC Server shall perform an intermediate node initiated LCLS break as described in sub-clause 7.2.3 and when the LCLS break is complete shall apply the tone or announcement. On the completion of the tone or announcement if LCLS break occurred the LCLS may be re-established as described in sub-clause 7.3.3. + +On completion of the tone or announcement if LCLS break was not required the (G)MSC Server may signal LCLS-Configuration Change Request message with LCLS-Configuration-Preference IE indicating "Need Send Backward= no" or "Need Send Forward = no" towards preceding/succeeding node respectively. If the (G)MSC Server sends the LCLS Configuration Change Request message it shall start the LCLS\_configuration\_modification timer. At reception of the LCLS Configuration Change Request Acknowledge message the (G)MSC Server shall stop the LCLS\_configuration\_modification timer. If the LCLS\_configuration\_modification timer expires, the (G)MSC Server shall perform an intermediate node initiated LCLS break as described in sub-clause 7.2.3. + +The appropriate LCLS configurations which result from the new LCLS-Configuration-Preference settings are specified in Table 4.2.1.1. + +#### 14.6.2.2 oMSC Server + +An oMSC Server wishing to insert a tone or announcement towards the terminating UE may signal LCLS Configuration Change Request message with LCLS-Configuration-Preference IE set to "Need Send Forward = yes". When oMSC Server sends the LCLS Configuration Change Request message it shall start LCLS\_configuration\_modification timer. + +NOTE: The other LCLS-Configuration-Preference settings remain unchanged. + +When the oMSC Server receives the LCLS Configuration Change Request Acknowledge message it shall stop the LCLS\_configuration\_modification timer. If the received LCLS-Configuration-Change Result IE indicates acceptance of the requested LCLS Configuration change then it shall proceed to insert its tone or announcement as per a normal call handling. Otherwise, if the received LCLS-Configuration-Change Result IE indicates the requested LCLS configuration change is rejected or if the LCLS\_configuration\_modification timer expires, the oMSC Server shall perform a MSC initiated LCLS break as described in sub-clause 7.2.1 and once the LCLS break is complete then begin applying the tone or announcement. On the completion of the tone or announcement LCLS may be re-established as described in sub-clause 7.3.1. + +On completion of the tone or announcement (without LCLS Break) in the forward direction the oMSC Server may signal the LCLS Configuration Change Request message to succeeding node with the LCLS-Configuration-Preference IE indicating "Need Send Forward = no". If the oMSC Server sends the LCLS Configuration Change Request message it shall start the LCLS\_configuration\_modification timer. At reception of the LCLS Configuration Change Request Acknowledge message the oMSC Server shall stop the LCLS\_configuration\_modification timer. If the LCLS\_configuration\_modification timer expires, the oMSC Server shall perform an intermediate node initiated LCLS break as described in sub-clause 7.2.1. + +If the oMSC Server wishes to insert a tone or announcement only towards its locally served UE it does not need to request any change to the LCLS configuration preferences in the Core Network and may send the LCLS-Connect-Control message to the oBSS containing the appropriate LCLS-Configuration IE settings as specified in Table 4.2.1.1 and if supported by the oBSS, the oMSC, oMGW shall begin applying the tone or announcement. On completion of the tone or announcement the oMSC shall return the LCLS Configuration to the previous setting. + +If the oMSC Server receives LCLS-BSS-Status indicating that the oBSS does not support the requested LCLS-Configuration then the oMSC Server shall initiate LCLS Break towards the oBSS and succeeding node, as described in sub-clause 7.2.1. On completion of the tone or announcement after LCLS Break LCLS may be re-established as described in sub-clause 7.3.1. + +If the oMSC Server receives the LCLS Configuration Change Request message with LCLS-Configuration-Preference IE indicating "Need Send Backward= yes" it shall send LCLS-Connect-Control message containing the appropriate LCLS-Configuration IE settings as specified in Table 4.2.1.1 and if supported by the oBSS it shall return the LCLS Configuration Change Request Acknowledge with a LCLS-Configuration-Change Result IE indicating success to the succeeding node. + +If the oMSC Server receives LCLS-BSS-Status indicating that the oBSS does not support the requested LCLS-Configuration then the oMSC Server shall return the LCLS Configuration Change Request Acknowledge message to the succeeding node with a LCLS-Configuration-Change Result IE indicating that the request is rejected. + +#### 14.6.2.3 tMSC Server + +A tMSC Server wishing to insert a tone or announcement towards the originating UE may signal LCLS Configuration Change Request message with LCLS-Configuration-Preference IE set to "Need Send Backward = yes". When tMSC Server sends the LCLS Configuration Change Request message it shall start LCLS\_configuration\_modification timer. + +NOTE: The other LCLS-Configuration-Preference IE settings remain unchanged. + +When the tMSC Server receives the LCLS Configuration Change Request Acknowledge message it shall stop the LCLS\_configuration\_modification timer. If the received LCLS-Configuration-Change Result IE indicates acceptance of the requested LCLS Configuration change then it shall proceed to insert its tone or announcement as per a normal call handling. Otherwise, if the received LCLS-Configuration-Change Result IE indicates the requested LCLS Configuration change is rejected or if the LCLS\_configuration\_modification timer expires, the tMSC Server shall perform a MSC initiated LCLS break as described in sub-clause 7.2.1 and once the LCLS break is complete then begin applying the tone or announcement (on the completion of the tone or announcement LCLS may be re-established as described in sub-clause 7.3.1). + +If the LCLS Configuration Change Request was successful, on completion of the tone or announcement the tMSC Server may signal the LCLS Configuration Change Request to the preceding node to return the LCLS configuration preference to the previously agreed value. If the tMSC Server sends the LCLS Configuration Change Request message it shall start the LCLS\_configuration\_modification timer. At reception of the LCLS Configuration Change Request Acknowledge message the tMSC Server shall stop the LCLS\_configuration\_modification timer. If the LCLS\_configuration\_modification timer expires, the tMSC Server shall perform an intermediate node initiated LCLS break as described in sub-clause 7.2.1. + +If the tMSC Server wishes to insert a tone or announcement only towards its locally served UE it does not need to request any change to the LCLS configuration preferences in the Core Network and may send the LCLS-Connect-Control message to the tBSS containing the appropriate LCLS-Configuration IE settings as specified in Table 4.2.1.1 and if supported by the tBSS it shall begin applying the tone or announcement. On completion of the tone or announcement the tMSC shall return the LCLS Configuration to the previous setting. + +If the tMSC Server receives LCLS-BSS-Status indicating that the tBSS does not support the requested LCLS-Configuration then the tMSC Server shall initiate LCLS Break towards the tBSS and preceding nodes, as described in sub-clause 7.2.1. On completion of the tone or announcement after LCLS Break the tMSC Server may re-establish LCLS (with the previous LCLS Configuration) as described in sub-clause 7.3.1. + +If the tMSC Server receives the LCLS Configuration Change Request message with the LCLS-Configuration-Preference IE indicating "Need Send Forward = yes" it shall send LCLS-Connect-Control message containing the appropriate LCLS-Configuration IE settings as specified in Table 4.2.1.1 and if supported by the tBSS it shall return the LCLS Configuration Change Request Acknowledge message with a LCLS-Configuration-Change Result IE to the preceding node. + +If the tMSC Server receives LCLS-BSS-Status indicating that the tBSS does not support the requested LCLS-Configuration then the tMSC Server shall return the LCLS Configuration Change Request Acknowledge message to the preceding node with a LCLS-Configuration-Change Result IE indicating that the request is rejected. + +#### 14.6.2.4 BSS + +When the BSS receives a LCLS-Connect-Control message containing a LCLS-Configuration IE set to: + +- "connected both-way in the BSS and send access DL from the Core Network" and it supports this configuration it shall return LCLS-BSS-Status indicating that the requested LCLS configuration is supported and from then on detect any incoming data packets and insert them in the stream towards the locally served UE. +- "connected both-way in the BSS and send access DL from the Core Network, block local DL" and it supports this configuration it shall return LCLS-BSS-Status indicating that the requested LCLS configuration is supported and it shall block the local DL path from the opposite call leg. When detecting user data packets from the Core Network, the BSS shall insert this user data in the stream towards the locally served UE. +- "connected both-way in the BSS and bi-casted UL to the Core Network and send access DL from the Core Network" and it supports this configuration it shall return LCLS-BSS-Status indicating that the requested LCLS configuration is supported. When detecting user data packets from the Core Network, the BSS shall insert this user data in the stream towards the locally served UE and send UL user data to the Core Network. + +- "connected both-way in the BSS and bi-casted UL to the Core Network and send access DL from the Core Network, block local DL" and it supports this configuration it shall block the local DL path from the opposite call leg and return LCLS-BSS-Status indicating that the requested LCLS configuration is supported. From then on it shall insert the data packets coming from the Core Network for that call leg in the stream towards the locally served UE and send UL user data to the Core Network. + +If the BSS does not support the requested LCLS-Configuration it shall return LCLS-BSS-Status indicating that the requested configuration is not supported; the LCLS configuration is kept as it was prior to receiving the LCLS-Connect-Control message. + +#### 14.6.2.5 Example of Playing Mid-Call Announcement/Tone + +##### 14.6.2.5.1 Connection Model + +Figure 14.6.2.5.1.1 shows the network model where the iMSC server requests the iMGW to play the announcement/tone directly on the bearer termination T3 (used towards the preceding oMGW) from which the signal shall be sent towards the oUE. The bearer termination T4 is used for the bearer towards the succeeding tMGW (i.e. towards the tUE). Before the start of mid-call announcement/tone procedure the call was locally switched with the LCLS Configuration set to "connected both-way in the BSS". + +![Diagram showing two connection models for mid-call announcement/tone. It includes a legend for control plane links (green dashed), user plane links through CN (black dotted), user plane links within BSS (red solid), and announcement/tone signals (blue dashed). Model 1 shows a locally switched call. Model 2 shows the same call with an announcement/tone being played from the iMGW to the oUE.](b033fab424e6df728345cfa04df83fcc_img.jpg) + +**Legend:** + +- Control plane link which transmits signalling (green dashed line) +- User plane link path through CN (black dotted line) +- User plane link which transmits real user plane data within BSS and UEs (red solid line) +- Announcement / tone (blue dashed line) + +**Connection Model 1: Locally switched call** + +In this model, the oUE and tUE are connected via the oBSS/tBSS. The oBSS/tBSS is connected to oMSC-S, which is part of the Control Signalling path (green dashed). The oBSS/tBSS also has a User Plane Data path (red solid) to the oMGW. The oMGW is connected to iMGW and tMGW via Non LCLS User Plane paths (black dotted). The iMGW is connected to iMSC-S, which is also part of the Control Signalling path. The tMGW is connected to tMSC-S, which is part of the Control Signalling path. The oUE and tUE are also connected to the oBSS/tBSS via User Plane Data paths (red solid). + +**Connection Model 2: Locally switched call, playing of Announcement/tone** + +This model is identical to Connection Model 1, but with an additional Announcement/tone signal (blue dashed line) being played from the iMGW (specifically from bearer termination T3) towards the oUE. The oUE's User Plane Data path (red solid) is blocked (indicated by an 'X'), and the Announcement/tone signal is instead sent to the oUE via the oBSS/tBSS. + +Diagram showing two connection models for mid-call announcement/tone. It includes a legend for control plane links (green dashed), user plane links through CN (black dotted), user plane links within BSS (red solid), and announcement/tone signals (blue dashed). Model 1 shows a locally switched call. Model 2 shows the same call with an announcement/tone being played from the iMGW to the oUE. + +Connection Model 2: Locally switched call, playing of Announcement/tone + +Figure 14.6.2.5.1.1: Connection Model, Mid-Call Announcement/tone + +##### 14.6.2.5.2 Example Sequence + +Figure 14.6.2.5.2.1 shows the message sequence example for providing the oUE with an announcement/tone. In the example the iMSC server requests the iMGW to play an announcement/tone and to notify the announcement/tone completion. + +![Sequence diagram titled 'Mid-Call Announcement/Tone Flow' showing interactions between oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. The diagram illustrates the flow of messages for playing an announcement/tone and updating LCLS configuration.](f468e577645d646f5157ce3eefb4ed96_img.jpg) + +The sequence diagram illustrates the following interactions: + +- Initial State:** A blue box at the top indicates "LCLS-Configuration requested from oBSS: 'connected both-way in the BSS'". A red double-headed arrow spans from oBSS to tBSS, labeled "Call is locally Switched". +- Step 1:** iMSC sends a message to iMGW: "1. Play announcement/ tone towards oUE". +- Step 2:** iMSC sends a "2. LCLS Configuration Change Request: APM [LCLS-Configuration-Change Request = 'LCLS Configuration Preference Modification Request', LCLS-Configuration-Preference: Need Send Backward = yes]" to oMSC. +- Step 3:** oMSC sends a "3. LCLS\_CONNECT\_CONTROL (LCLS-Configuration = 'connected both-way in the BSS and send access DL from the Core Network')" to oBSS. +- Step 4:** oBSS responds with "4. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = 'call is locally switched with requested LCLS configuration')" to oMSC. +- Step 5:** oMSC sends a "5. LCLS Configuration Change Request ACK: APM [LCLS-Configuration-Change Result = 'LCLS Configuration Change request accepted', LCLS-Configuration-Preference: Need Send Backward = yes]" to iMSC. +- Step 6:** oMSC sends a "6. MOD request (T3): Play announcement/Send Tone / MOD reply" to iMGW. Context (iC) is indicated. +- Announcement:** A blue arrow labeled "Announcement / tone" goes from oBSS to oUE. +- Step 7:** iMGW sends a "7. NOTIFY (T3): Announcement completed/ Tone completed" to oMSC. Context (iC) is indicated. +- Step 8:** iMSC sends a "8. LCLS Configuration Change Request: APM [LCLS-Configuration-Change Request = 'LCLS Configuration Preference Modification Request', LCLS-Configuration-Preference: Need Send Backward = no]" to oMSC. +- Step 9:** oMSC sends a "9. LCLS\_CONNECT\_CONTROL (LCLS-Configuration = 'connected both-way in the BSS')" to oBSS. +- Step 10:** oBSS responds with "10. LCLS\_CONNECT\_CONTROL\_ACK (LCLS-BSS-Status = 'call is locally switched with requested LCLS configuration')" to oMSC. +- Step 11:** oMSC sends a "11. LCLS Configuration Change Request ACK: APM [LCLS-Configuration-Change Result = 'LCLS Configuration Change request accepted', LCLS-Configuration-Preference: Need Send Backward = no]" to iMSC. + +Sequence diagram titled 'Mid-Call Announcement/Tone Flow' showing interactions between oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. The diagram illustrates the flow of messages for playing an announcement/tone and updating LCLS configuration. + +Figure 14.6.2.5.2.1: Mid-Call Announcement/Tone Flow + +1. The iMSC server identifies that mid-call announcement/tone needs to be played towards the oUE. +2. The iMSC server modifies the LCLS-Configuration-Preference IE due to the announcement/tone it needs to play towards the oUE and sends LCLS Configuration Change Request message towards the preceding node with the LCLS-Configuration-Change Request IE indicating a request to change the LCLS Configuration and with the modified LCLS-Configuration-Preference IE indicating "Need Send Backward = yes". When LCLS Configuration Change Request message is sent the iMSC server starts LCLS\_configuration\_modification timer. + +NOTE: Other values for the initially agreed LCLS-Configuration-Preference IE for receive or send access are unmodified. + +3. The oMSC server informs the oBSS the user plane data needs to be provided to the oUE from the CN by sending the LCLS-Connect-Control message containing LCLS-Configuration IE set to "connected both-way in the BSS and send access DL from the Core Network". + +4. The oBSS confirms the requested configuration is enabled with the LCLS-Connect-Control Ack message. +5. The oMSC server confirms the oBSS is prepared for the reception of announcement/tone by sending the LCLS Configuration Change Request Acknowledge message with a LCLS-Configuration-Change Result IE indicating acceptance of the requested LCLS Configuration change. +6. At reception of the LCLS Configuration Change Request Acknowledge message the iMSC server stops the LCLS\_configuration\_modification timer. Since the received LCLS-Configuration-Change Result IE indicates that requested send access is enabled the iMSC server provides the iMGW with the announcement/tone identification and requests the iMGW to notify the announcement/tone completion using the Play Announcement or Send Tone procedure. +7. The iMGW notifies the iMSC server when the announcement/tone is completed using the Announcement Completed or Tone Completed procedure. +8. The iMSC server signals to the preceding node the send access is not needed anymore by sending the LCLS Configuration Change Request message with the LCLS-Configuration-Change Request IE indicating a request to change the LCLS Configuration and with the LCLS-Configuration-Preference IE indicating "Need Send Backward = no" and starts LCLS\_configuration\_modification timer. +9. The oMSC server notifies the oBSS with the LCLS-Connect-Control message that no user plane data from the CN will be provided that is the LCLS-Configuration IE is set to "connected both-way in the BSS". +10. The oBSS replies with the LCLS-Connect-Control Ack message indicating local switching with the requested LCLS configuration. +11. The oMSC server confirms the oBSS has returned the LCLS connection to the status prior to the announcement/tone by sending the LCLS Configuration Change Request Acknowledge message with the LCLS-Configuration-Change Result IE indicating acceptance of the requested LCLS Configuration change. At reception of the LCLS Configuration Change Request Acknowledge message the iMSC server stops the LCLS\_configuration\_modification timer. + +#### 14.6.2.6 Examples with Uplink Bicasting of User Data + +##### 14.6.2.6.1 Connection Model + +Figure 14.6.2.6.1.1 shows the network model for the locally switched call with bicasting of user data to the Core Network where the oMSC server requests the oMGW to play the announcement/tone towards the originating UE. The dashed line in green represents call control signalling. Non-dotted lines represent the bearer carrying real user plane data: the solid line in turquoise represents the data from the originating UE and the solid line in yellow represents the data from the terminating UE. The solid line in blue represents an announcement played to the originating UE. The bearer termination T1 is used for the bearer towards the oBSS and the bearer termination T2 is used for the bearer towards the succeeding iMGW (i.e. towards the tUE). The announcement is applied directly on the bearer termination T1 from which the signal shall be sent towards the originating UE. + +If the oMSC server requires receiving UL data from the originating UE and the terminating UE and was sent a LCLS Configuration Preference IE set to "Need\_Receive\_Backward = yes; Need\_Receive\_Forward = yes" to the succeeding node then when it needs to send the DL data to the originating UE the oMSC server will require from the oBSS to connect LCLS with bicasting UL and with DL send access and to block local DL. Connection model 2a is applied when the oBSS supports the required LCLS configuration and the announcement is played towards the originating UE. + +If the oMSC server requires receiving UL data from the originating UE and the terminating UE but was sent the LCLS Configuration Preference IE set to "Need\_Receive\_Backward = yes, Need\_Receive\_Forward = no" to the succeeding node and was received the LCLS Configuration Preference IE set to "Need\_Receive\_Forward = no" then it may configure its oMGW to isolate the access side termination (T1) from the network side termination (T2). When the oMSC server needs to send the DL data to the originating UE it requests the oBSS to connect LCLS with bicasting UL and with DL send access. Connection model 2b applies when the oBSS supports the required LCLS configuration and then the oBSS inserts the announcement from the Core Network towards the originating UE. + +![Diagram of Connection Model 1: Locally switched call with bicasting of user data to CN. It shows a tUE and oUE connected to an oBSS/tBSS. Control signaling (green dashed lines) connects the BSS to oMSC-S, iMSC-S, and tMSC-S. User plane data (yellow solid lines) is bicasted from the BSS to the oMGW, iMGW, and tMGW, and then to the MSCs. The oMGW, iMGW, and tMGW are connected in a chain, with the oMGW having ports T1, T2, oC; iMGW having T3, T4, iC; and tMGW having T5, T6, iC.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) + +Diagram of Connection Model 1: Locally switched call with bicasting of user data to CN. It shows a tUE and oUE connected to an oBSS/tBSS. Control signaling (green dashed lines) connects the BSS to oMSC-S, iMSC-S, and tMSC-S. User plane data (yellow solid lines) is bicasted from the BSS to the oMGW, iMGW, and tMGW, and then to the MSCs. The oMGW, iMGW, and tMGW are connected in a chain, with the oMGW having ports T1, T2, oC; iMGW having T3, T4, iC; and tMGW having T5, T6, iC. + +Connection Model 1: Locally switched call with bicasting of user data to CN + +![Diagram of Connection Model 2a: Locally Switched Call with Bicasting of User Data to CN and with Blocked Local DL Data, Playing of Announcement/tone. This diagram is similar to Model 1 but includes a red 'X' on the local downlink path between the oBSS/tBSS and the oMGW, indicating that local downlink data is blocked. The oMGW is shown playing an announcement/tone.](aa6e28822419dba9f22129fee66c9c4c_img.jpg) + +Diagram of Connection Model 2a: Locally Switched Call with Bicasting of User Data to CN and with Blocked Local DL Data, Playing of Announcement/tone. This diagram is similar to Model 1 but includes a red 'X' on the local downlink path between the oBSS/tBSS and the oMGW, indicating that local downlink data is blocked. The oMGW is shown playing an announcement/tone. + +Connection Model 2a: Locally Switched Call with Bicasting of User Data to CN and with Blocked Local DL Data, Playing of Announcement/tone + +![Diagram of Connection Model 2b: Locally Switched Call with Bicasting of User Data to CN and Isolation of Access Side, Playing of Announcement/tone. In this model, the downlink path from the oMGW back to the oBSS/tBSS is isolated (indicated by a break in the yellow line). The oMGW plays the announcement/tone, and the downlink data is not sent back to the access side.](1399c76ef88f22b70d05ed3f781d3c48_img.jpg) + +Diagram of Connection Model 2b: Locally Switched Call with Bicasting of User Data to CN and Isolation of Access Side, Playing of Announcement/tone. In this model, the downlink path from the oMGW back to the oBSS/tBSS is isolated (indicated by a break in the yellow line). The oMGW plays the announcement/tone, and the downlink data is not sent back to the access side. + +Connection Model 2b: Locally Switched Call with Bicasting of User Data to CN and Isolation of Access Side, Playing of Announcement/tone + +Figure 14.6.2.6.1.1: Connection Model, LCLS with UL Bicasting and Mid-Call Announcement/tone + +##### 14.6.2.6.2 Example Sequences with Uplink Bicasting of User Data + +Figure 14.6.2.6.2.1 shows the message sequence example for providing the originating UE with an announcement/tone. In the example the call is locally switched with bicasting of user data to the Core Network. The oMSC server requests the oBSS to connect LCLS with bicasting UL and with DL send access and to block local DL. The oMSC server requests the oMGW to play an announcement/tone and to notify the announcement/tone completion. + +![Sequence diagram showing Mid-Call Announcement/Tone Flow with Block Local Data Request. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. The diagram illustrates the interaction between the oMSC server and other network elements to play an announcement/tone towards the oUE while locally switching the call.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) + +The diagram shows the following sequence of events: + +- Result of LCLS negotiation:** LCLS-Negotiation Response = "LCLS is allowed"; LCLS-Configuration-Preference [Need Receive Forward = yes; Need Receive Backward = yes]; LCLS-Configuration requested from oBSS: "connected both-way in the BSS and bi-casted UL to CN". +- Call is locally Switched:** Indicated by a red double-headed arrow between oBSS and tBSS. +- 1. Play announcement/ tone towards oUE:** oMSC sends a request to oMGW. +- 2. LCLS\_CONNECT\_CONTROL:** oMSC sends a message to oBSS with LCLS-Configuration = "connected both-way in the BSS and bi-casted UL to CN and send access DL from CN, block local DL". +- 3. LCLS\_CONNECT\_CONTROL\_ACK:** oBSS responds with LCLS-BSS-Status = "call is locally switched with requested LCLS configuration". +- 4. MOD request (T1):** oMSC sends a request to oMGW to play announcement/send tone. Context (oC) is exchanged. +- Announcement / tone:** Indicated by a blue arrow from oMGW to oUE. +- 5. NOTIFY (T1):** oMGW notifies oMSC that the announcement/tone is completed. Context (oC) is exchanged. +- 6. LCLS\_CONNECT\_CONTROL:** oMSC sends a message to oBSS with LCLS-Configuration = "connected both-way in the BSS and bi-casted UL to the Core Network". +- 7. LCLS\_CONNECT\_CONTROL\_ACK:** oBSS responds with LCLS-BSS-Status = "call is locally switched with requested LCLS configuration". + +Sequence diagram showing Mid-Call Announcement/Tone Flow with Block Local Data Request. Lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, tUE. The diagram illustrates the interaction between the oMSC server and other network elements to play an announcement/tone towards the oUE while locally switching the call. + +**Figure 14.6.2.6.2.1: Mid-Call Announcement/Tone Flow with Block Local Data Request** + +1. The oMSC server identifies that mid-call announcement/tone needs to be played towards the oUE. +2. The oMSC server informs the oBSS the user plane data needs to be provided to the oUE from the CN by sending the LCLS-Connect-Control message containing LCLS-Configuration IE set to "connected both-way in the BSS and bi-casted UL to CN and send access DL from the Core Network, block local DL". +3. The oBSS confirms the requested configuration is enabled with the LCLS-Connect-Control Ack message. +4. At reception of the LCLS-Connect-Control Ack message indicating that requested LCLS configuration is supported the oMSC server provides the oMGW with the announcement/tone identification and requests the oMGW to notify the announcement/tone completion using the Play Announcement or Send Tone procedure. +5. The oMGW notifies the oMSC server when the announcement/tone is completed using the Announcement Completed or Tone Completed procedure. +6. The oMSC server notifies the oBSS with the LCLS-Connect-Control message that DL send access is no longer needed that is the LCLS-Configuration IE is set to "connected both-way in the BSS and bi-casted UL to the Core Network". +7. The oBSS replies with the LCLS-Connect-Control Ack message indicating local switching with the requested LCLS configuration. + +##### 14.6.2.6.3 Example Sequence when Access Side Termination is isolated in MGW + +Figure 14.6.2.6.3.1 shows the message sequence example for providing the originating UE with an announcement/tone. Since other CN nodes didn't request receiving UL data from the originating UE the oMSC server may configure its oMGW to isolate the access side termination from the network side termination. In the example the oMSC server requests the oMGW to play an announcement/tone and to notify the announcement/tone completion. + +![Sequence diagram showing the mid-call announcement/tone flow when access side termination is isolated in MGW. The diagram involves ten lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. A red double-headed arrow labeled 'Call is locally Switched' spans from oUE to tUE. The sequence of messages is: 1. oMSC sends 'Play announcement/ tone towards oUE' to oMGW; 2. oMGW sends 'MOV request (T1) / MOV reply' to oMSC with context (Cg) and 'Isolate bearer termination'; 3. oMSC sends 'LCLS_CONNECT_CONTROL' to oBSS with configuration 'connected both-way in the BSS and bi-casted UL to the CN and send access DL from the CN'; 4. oBSS sends 'LCLS_CONNECT_CONTROL_ACK' to oMSC with status 'call is locally switched with requested LCLS configuration'; 5. oMSC sends 'MOD request (T1): Play announcement/Send Tone / MOD reply' to oMGW; 6. oMGW sends 'NOTIFY (T1): Announcement completed/ Tone completed' to oMSC; 7. oMSC sends 'LCLS_CONNECT_CONTROL' to oBSS with configuration 'connected both-way in the BSS and bi-casted UL to the Core Network'; 8. oBSS sends 'LCLS_CONNECT_CONTROL_ACK' to oMSC with status 'call is locally switched with requested LCLS configuration'; 9. oMGW sends 'MOV request (T1) / MOV reply' to oMSC with context oC and 'Join Bearer Termination'. A blue arrow labeled 'Announcement / tone' points from oMGW to oUE.](60a40901e77feeb97ab6cf9c6d9418c3_img.jpg) + +Sequence diagram showing the mid-call announcement/tone flow when access side termination is isolated in MGW. The diagram involves ten lifelines: oUE, oBSS, oMGW, oMSC, iMGW, iMSC, tMSC, tMGW, tBSS, and tUE. A red double-headed arrow labeled 'Call is locally Switched' spans from oUE to tUE. The sequence of messages is: 1. oMSC sends 'Play announcement/ tone towards oUE' to oMGW; 2. oMGW sends 'MOV request (T1) / MOV reply' to oMSC with context (Cg) and 'Isolate bearer termination'; 3. oMSC sends 'LCLS\_CONNECT\_CONTROL' to oBSS with configuration 'connected both-way in the BSS and bi-casted UL to the CN and send access DL from the CN'; 4. oBSS sends 'LCLS\_CONNECT\_CONTROL\_ACK' to oMSC with status 'call is locally switched with requested LCLS configuration'; 5. oMSC sends 'MOD request (T1): Play announcement/Send Tone / MOD reply' to oMGW; 6. oMGW sends 'NOTIFY (T1): Announcement completed/ Tone completed' to oMSC; 7. oMSC sends 'LCLS\_CONNECT\_CONTROL' to oBSS with configuration 'connected both-way in the BSS and bi-casted UL to the Core Network'; 8. oBSS sends 'LCLS\_CONNECT\_CONTROL\_ACK' to oMSC with status 'call is locally switched with requested LCLS configuration'; 9. oMGW sends 'MOV request (T1) / MOV reply' to oMSC with context oC and 'Join Bearer Termination'. A blue arrow labeled 'Announcement / tone' points from oMGW to oUE. + +**Figure 14.6.2.6.3.1: Mid-Call Announcement/Tone Flow when Access Side Termination is Isolated in MGW** + +1. The oMSC server identifies that mid-call announcement/tone needs to be played towards the oUE. +2. If the LCLS negotiation indicated that any succeeding node does not require the UL data from the oUE then the oMSC server requests the oMGW to isolate the access side termination T1 from the network side termination T2. + +NOTE 1: the MOVE command (Isolate Bearer termination procedure) is not required if T1 has been already moved from the context oC during the call establishment procedure. + +NOTE 2: The MSC server can also use the Change Through-Connection procedure and requests the MGW to change the through-connection of the bearer to inactive instead of using of the Isolate Bearer termination procedure, see 3GPP TS 23.205 [2]. + +3. The oMSC server informs the oBSS the user plane data needs to be provided to the oUE from the CN by sending the LCLS-Connect-Control message containing LCLS-Configuration IE set to "connected both-way in the BSS and bi-casted UL to the Core Network and send access DL from the Core Network". +4. The oBSS confirms the requested configuration is enabled with the LCLS-Connect-Control Ack message. +5. At reception of the LCLS-Connect-Control Ack message indicating that requested LCLS configuration is supported the oMSC server provides the oMGW with the announcement/tone identification and requests the oMGW to notify the announcement/tone completion using the Play Announcement or Send Tone procedure. +6. The oMGW notifies the oMSC server when the announcement/tone is completed using the Announcement Completed or Tone Completed procedure. +7. The oMSC server notifies the oBSS with the LCLS-Connect-Control message that DL send access is no longer needed that is the LCLS-Configuration IE is set to "connected both-way in the BSS and bi-casted UL to the Core Network". +8. The oBSS replies with the LCLS-Connect-Control Ack message indicating local switching with the requested LCLS configuration. +9. The oMSC server may send to the oMGW request to move the access side termination T1 to context oC with the network side termination T2. + +NOTE 3: Steps 9 is optional and not needed if step 2 is not performed. + +NOTE 4: If the MSC server has used the Change Through-Connection procedure in step 2 instead of the Isolate Bearer termination procedure then the MSC server will use the Change Through-Connection procedure to request the MGW to change the through-connection of the bearer to be both-way through-connected. + +## 14.7 Global Text Telephony + +LCLS shall not be allowed for Global Text Telephony. + +## 14.8 Emergency Calls + +LCLS shall not be allowed for Emergency Calls. + +## 14.9 Subscriber and equipment trace + +No impact. There are no LCLS related requirements for Subscriber and Equipment Trace. + +## 14.10 Customized Alerting Tone + +### 14.10.1 Audio CAT + +No impact. There are no LCLS related requirements for Audio CAT. + +### 14.10.2 Multimedia CAT + +LCLS shall not be allowed for multimedia calls. + +## 14.11 Tandem Free Operation (TFO) + +No impact. There are no LCLS related requirements for Tandem Free Operation (TFO). + +LCLS may be activated for calls that use TFO, but the TFO operation is interrupted for the time that the call is locally switched. If LCLS is broken in the middle of a call, the TFO operation may resume, if still applicable. + +## 14.12 Transcoder Free Operation (TrFO) + +No impact. There are no LCLS related requirements for Transcoder Free Operation (TrFO). + +## 14.13 CS Data Calls + +LCLS shall not be allowed for CS Data Calls. + +## 14.14 RTP Multiplexing + +No impact. There are no LCLS related requirements for RTP Multiplexing. + +# 15 Tunnelling + +The tunnelling procedures shall be applied in accordance with 3GPP TS 23.205 [2]. + +# 16 Messages/Procedures and their contents + +## 16.1 Messages between (G)MSC servers + +### 16.1.1 General + +The BICC messages between (G)MSC servers on Nc interface are specified in 3GPP TS 23.205 [2]. The SIP methods and corresponding responses that shall be supported between (G)MSC servers on Nc interface are specified in 3GPP TS 29.231 [10]. The LCLS related information exchanged in these messages and encapsulated in the corresponding SIP messages is specified below and in 3GPP TS 29.205 [6]. + +The MAP messages used for inter-MSC handover between Anchor and Target MSC-Server (E-interface) are specified in 3GPP TS 23.205 [2] and 3GPP TS 23.009[9]. The LCLS related information exchanged in these messages is specified below and in 3GPP TS 29.002 [12]. + +### 16.1.2 Initial Address + +Table 16.1.2.1 indicates the LCLS related information which is exchanged between the MSC servers in the Initial Address (BICC: IAM or SIP-I: INVITE request with encapsulated ISUP IAM) message. Only the Information Elements required by LCLS are shown. + +**Table 16.1.2.1: LCLS related information in Initial Address message** + +| Message | Message direction | Information element name | Information element required | Information element description | +|----------------------------------------------------|-------------------|-------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Initial Address (BICC: IAM or SIP-I: INVITE [IAM]) | Forward | Global Call Reference | C | This information element identifies the call. This information element shall be included when LCLS is supported in the core network. | +| | | LCLS-Negotiation Request | C | This information element indicates the initial negotiation request and LCLS permissions. This information element shall be included when LCLS is supported in the core network. | +| | | LCLS-Configuration-Preference | C | This information element indicates the LCLS configuration preference while LCLS is established. This information element shall be included when LCLS is supported in the core network. | + +### 16.1.3 Answer + +Table 16.1.3.1 indicates the LCLS related information which is exchanged between the MSC servers in the Answer (BICC: ANM or SIP-I: 200 OK final response to initial INVITE request with encapsulated ANM) message. Only the Information Elements required by LCLS are shown. + +**Table 16.1.3.1: LCLS related information in Answer message** + +| Message | Message direction | Information element name | Information element required | Information element description | +|------------------------------------------------------------|--------------------------|---------------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| Answer
(BICC: ANM or
SIP-I: 200 OK-
INVITE [ANM]) | Backward | LCLS-Status | C | This information element identifies the LCLS connection status. This information element shall be included when LCLS is negotiated in the core network. | + +### 16.1.4 Bearer and Codec Information + +Table 16.1.4.1 indicates the LCLS related information which is exchanged between the MSC servers in the Bearer and Codec Information (BICC: APM) message. Only the Information Elements required by LCLS are shown. + +**Table 16.1.4.1: LCLS related information in Bearer and Codec Information message** + +| Message | Message direction | Information element name | Information element required | Information element description | +|------------------------------------------------|--------------------------|-----------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Bearer and Codec
Information
(BICC: APM) | Backward | LCLS-Negotiation
Response | O | This information element indicates the initial negotiation response. This information element shall be included when the APM is related to LCLS negotiation in Bearer and Codec Information messages and LCLS is supported in the core network. | +| | | LCLS-Configuration-
Preference | C | This information element indicates the LCLS configuration preference while LCLS is established. This IE shall be included if the LCLS-Negotiation Response is included. | + +### 16.1.5 Backward LCLS Negotiation + +Table 16.1.5.1 indicates the LCLS related information which is exchanged between the MSC servers in the LCLS Negotiation (BICC: APM; SIP-I: 183 Session Progress provisional response with encapsulated APM) message or in the Address Complete (BICC: ACM; SIP-I: 183 Session Progress provisional response with encapsulated ACM) message or in the Call Progress (BICC: CPG; SIP-I: 183 Session Progress provisional response with encapsulated CPG) message. Only the Information Elements required by LCLS are shown. + +**Table 16.1.5.1: LCLS related information in the LCLS Negotiation message** + +| Message | Message direction | Information element name | Information element required | Information element description | +|--------------------------------------------------------------------------|--------------------------|-----------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------| +| LCLS Negotiation
(BICC: APM;
SIP-I: 183 Session
Progress [APM]) | Backward | LCLS-Negotiation
Response | M | This information element indicates the initial negotiation response. | +| | | LCLS-Configuration-
Preference | M | This information element indicates the LCLS configuration preference while LCLS is established. | + +**Table 16.1.5.2: LCLS related information in the Address Complete message** + +| Message | Message direction | Information element name | Information element required | Information element description | +|--------------------------------------------------------------------------|--------------------------|-----------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Address Complete
(BICC: ACM;
SIP-I: 183 Session
Progress [ACM]) | Backward | LCLS-Negotiation
Response | O | This information element indicates the initial negotiation response. | +| | | LCLS-Configuration-
Preference | C | This information element indicates the LCLS configuration preference while LCLS is established. This IE shall be included if the LCLS-Negotiation Response is included. | + +**Table 16.1.5.3: LCLS related information in the Call Progress message** + +| Message | Message direction | Information element name | Information element required | Information element description | +|--------------------------------------------------------------|--------------------------|---------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Call Progress (BICC: CPG; SIP-I: 183 Session Progress [CPG]) | Backward | LCLS-Negotiation Response | O | This information element indicates the initial negotiation response. | +| | | LCLS-Configuration-Preference | C | This information element indicates the LCLS configuration preference while LCLS is established. This IE shall be included if the LCLS-Negotiation Response is included. | + +### 16.1.6 Change of LCLS Configuration + +Table 16.1.6.1 indicates the LCLS related information which is exchanged between the MSC servers in the LCLS Configuration Change Request (BICC: APM or SIP-I: INFO request with encapsulated APM) messages. + +**Table 16.1.6.1: LCLS related information in the LCLS Configuration Change Request message** + +| Message | Message direction | Information element name | Information element required | Information element description | +|--------------------------------------------------------------------------------|--------------------------|-----------------------------------|-------------------------------------|-----------------------------------------------------------------------------------------------------| +| LCLS Configuration Change Request (BICC: APM or SIP-I: INFO [APM]) | Both | LCLS-Configuration-Change Request | M | This information element indicates a request to change the requested LCLS configuration preference. | +| | | LCLS-Configuration-Preference | M | This information element indicates the LCLS configuration preference to be changed to. | +| LCLS Configuration Change Request Acknowledge (BICC: APM or SIP-I: INFO [APM]) | Both | LCLS-Configuration-Change Result | M | This information element indicates if the LCLS Configuration Change Request is accepted or not. | +| | | LCLS-Configuration-Preference | M | This information element has the same value as in LCLS Configuration Change Request. | + +### 16.1.7 LCLS Status update + +Table 16.1.7.1 indicates the LCLS related information which is exchanged between the MSC servers in the LCLS Status update (BICC: APM or SIP-I: INFO request with encapsulated ISUP APM) message. + +**Table 16.1.7.1: LCLS related information in LCLS Status update message** + +| Message | Message direction | Information element name | Information element required | Information element description | +|-----------------------------------------------------|--------------------------|---------------------------------|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| +| LCLS Status update (BICC: APM or SIP-I: INFO [APM]) | Both | LCLS-Status | M | This information element indicates the LCLS connection status. This information element shall be included when LCLS connection status has changed in the BSS. | + +### 16.1.8 Change of LCLS Status + +Table 16.1.8.1 indicates the LCLS related information which is exchanged between the MSC servers in the LCLS Status Change Request (BICC: APM or SIP-I: INFO request with encapsulated ISUP APM) messages. + +**Table 16.1.8.1: LCLS related information in LCLS Status Change Request message** + +| Message | Message direction | Information element name | Information element required | Information element description | +|-------------------------------------------------------------------------|-------------------|--------------------------|------------------------------|--------------------------------------------------------------------------------------------------| +| LCLS Status Change Request (BICC: APM or SIP-I: INFO [APM]) | Both | LCLS-Status-Change | M | This information element indicates a request to change the LCLS connection status in the BSS. | +| LCLS Status Change Request Acknowledge (BICC: APM or SIP-I: INFO [APM]) | Both | LCLS-Status-Change | M | This information element has the same value as in the LCLS-Status-Change-Request message. | +| | | Result Code | M | This information element indicates if the LCLS Status Change request is accepted or not.
NOTE | + +NOTE: A request to break LCLS shall not be rejected. + +### 16.1.9 MAP\_PREPARE\_HANDOVER Request + +Table 16.1.9.1 indicates the LCLS related information which is exchanged between the Anchor MSC-Server and the Target MSC-Server (E-interface) in the MAP\_PREPARE\_HANDOVER Request message. + +**Table 16.1.9.1: LCLS related information in MAP-Prepare-Handover Request message** + +| Message | Message direction | Information element name | Information element required | Information element description | +|------------------------------|---------------------------------------------|-------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| MAP_PREPARE_HANDOVER Request | From Anchor MSC-Server to Target MSC-Server | LCLS GCR | C | This information element identifies the call. This information element shall be included when LCLS is supported in the core network. | +| | | LCLS-Negotiation Request | C | This information element indicates request for LCLS. This information element shall be included when LCLS is supported in the core network. | +| | | LCLS-Configuration-Preference | C | This information element indicates the LCLS configuration preference while LCLS is established. This information element shall be included when LCLS is supported in the core network. | + +## 16.2 Procedures between (G)MSC server and MGW + +The (G)MSC server and MGW procedures shall be performed in accordance with 3GPP 23.205 [2] for a BICC based CS core network and in accordance with 3GPP TS 23.231 [3] for a SIP-I based CS core network. + +## 16.3 Messages between MSC server and BSS + +### 16.3.1 General + +The procedures used on the Base Station System (BSS) to Mobile-services Switching Centre (MSC) interface for control of GSM services are specified in 3GPP TS 48.008 [7]. The LCLS related information exchanged in these procedures is specified below. + +### 16.3.2 Assignment Procedure between MSC-Server and BSS + +Table 16.3.2.1 indicates the LCLS related information which is exchanged between the MSC server and the BSS in the BSSMAP Assignment Procedure. Only the Information Elements required by LCLS are shown. + +**Table 16.3.2.1: LCLS related information in Assignment Procedure** + +| Procedure | Message direction | Information element name | Information element required | Information element description | +|---------------------|--------------------------|---------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Assignment Request | From MSC-S | Global Call Reference | C | This information element identifies the call. This information element shall be included if local switching is requested by the MSC server. | +| | | LCLS-Configuration | C | This information element indicates the LCLS connection preference which shall persist in the BSS while LCLS is established. This information element shall be included if local switching is requested by the MSC server. | +| | | LCLS-Connection-Status-Control | C | This information element indicates to BSS whether it is permitted to locally through-connect the call. This information element shall be included if local switching is requested by the MSC server and when the Assignment Request message is sent after Answer. | +| | | LCLS-Correlation-Not-Needed | O | This information element indicates to the BSS that call correlation is not needed. This information element shall be sent if the MSC-Server has detected that the call is not an Intra-BSS call or an Intra-network call. | +| Assignment Complete | From BSS | LCLS-BSS-Status | C | This information element notifies CN of the LCLS connection status in the BSS. This information element shall be included if BSS supports LCLS and both Global Call Reference IE and LCLS-Configuration IE were included in the ASSIGNMENT REQUEST message. | + +### 16.3.3 Handover Request Procedure between MSC-Server and BSS + +Table 16.3.3.1 indicates the LCLS related information, which is exchanged between the MSC server and the BSS in the BSSMAP Handover Request Procedure. Only the Information Elements required by LCLS are shown. + +**Table 16.3.3.1: LCLS related information in Handover Request Procedure** + +| Procedure | Message direction | Information element name | Information element required | Information element description | +|------------------------------|--------------------------|---------------------------------|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Handover Request | From MSC-S | Global Call Reference | C | This information element identifies the call. This information element shall be included if local switching is requested by the MSC server. | +| | | LCLS-Connection-Status-Control | C | This information element indicates to BSS whether it is permitted to locally through-connect the call. This information element shall be included if local switching is requested by the MSC server. | +| | | LCLS-Configuration | C | This information element indicates the LCLS connection preference which shall persist in the BSS while LCLS is established. This information element shall be included if local switching is requested by the MSC server. | +| Handover Request Acknowledge | From BSS | LCLS-BSS-Status | C | This information element notifies CN of the LCLS connection status in the BSS. This information element shall be included if BSS supports LCLS and Global Call Reference IE, LCLS-Configuration IE and LCLS-Connection-Status-Control IE were included in the HANDOVER REQUEST message. | + +### 16.3.4 Handover Complete Procedure between MSC-Server and BSS + +Table 16.3.4.1 indicates the LCLS related information, which is exchanged between the MSC server and the BSS in the BSSMAP Handover Complete Procedure. Only the Information Elements required by LCLS are shown. + +**Table 16.3.4.1: LCLS related information in Handover Request Procedure** + +| Procedure | Message direction | Information element name | Information element required | Information element description | +|-------------------|--------------------------|---------------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Handover Complete | From BSS | LCLS-BSS-Status | C | This information element notifies CN of the LCLS connection status in the BSS. This information element shall be included if BSS supports LCLS and if local switching was previously requested for this call leg by the MSC server. | + +### 16.3.5 Handover Performed Procedure between MSC-Server and BSS + +Table 16.3.5.1 indicates the LCLS related information, which is exchanged between the MSC server and the BSS in the BSSMAP Handover Performed Procedure. Only the Information Elements required by LCLS are shown. + +**Table 16.3.5.1: LCLS related information in Handover Request Procedure** + +| Procedure | Message direction | Information element name | Information element required | Information element description | +|--------------------|-------------------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Handover Performed | From BSS | LCLS-BSS-Status | C | This information element notifies CN of the LCLS connection status in the BSS. This information element shall be included if BSS supports LCLS and if local switching was previously requested for this call leg by the MSC server. | + +### 16.3.6 Internal Handover Command Procedure between MSC-Server and BSS + +Table 16.3.6.1 indicates the LCLS related information, which is exchanged between the MSC server and the BSS in the BSSMAP Internal Handover Command Procedure. Only the Information Elements required by LCLS are shown. + +**Table 16.3.6.1: LCLS related information in Internal Handover Command Procedure** + +| Procedure | Message direction | Information element name | Information element required | Information element description | +|---------------------------|-------------------|--------------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Internal Handover Command | From MSC-S | LCLS-Connection-Status-Control | C | This information element indicates to BSS whether it is permitted to locally through-connect the call. This information element shall be included if local switching is requested by the MSC server, and LCLS-Connection-Status-Control indicating "Connect" has not previously been sent to the BSS for this particular call leg. | + +### 16.3.7 LCLS Connection Procedure between MSC-Server and BSS + +Table 16.3.7.1 indicates the LCLS Connection Procedure and related information, which is exchanged between the MSC server and the BSS. Only the Information Elements required by LCLS are shown. + +**Table 16.3.7.1: LCLS Connection Procedure between MSC-Server and BSS** + +| Procedures | Message direction | Information element name | Information element required | Information element description | +|--------------------------|-------------------|--------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------| +| LCLS-Connect-Control | From MSC-S | LCLS-Connection-Status-Control | O | This information element indicates to BSS whether it is permitted to locally through-connect the call. | +| | | LCLS-Configuration | O | This information element indicates the LCLS-Configuration. | +| LCLS Connect Control Ack | From BSS | LCLS-BSS-Status | M | This information element notifies CN of the LCLS connection status in the BSS. | + +### 16.3.8 LCLS Notification Procedure between MSC-Server and BSS + +Table 16.3.8.1 indicates the LCLS Notification Procedure and related information, which is exchanged between the MSC server and the BSS. Only the Information Elements required by LCLS are shown. + +**Table 16.3.8.1: LCLS Notification Procedures between MSC-Server and BSS** + +| Procedures | Message direction | Information element name | Information element required | Information element description | +|-------------------------------------------------------------------------------|-------------------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| LCLS-Notification | From BSS | LCLS-BSS-Status | C | This information element notifies CN of the LCLS connection status in the BSS. This information element shall be included when BSS changes the LCLS connection status. | +| | | LCLS-Break-Request | C | This information element indicates if the LCLS break request is ordered from CN. This information element shall be included when BSS requests to disconnect local switching. | +| NOTE: Only one of those IE shall be present in the LCLS Notification message. | | | | | + +# 17 Bearer Redirect + +Bearer Redirect mechanisms within BICC based CS core network may be applied as specified in 3GPP TS 23.205 [2]. + +Bearer Redirect is not supported within SIP-I based CS core network, see 3GPP TS 23.231 [3]. + +# 18 (G)MSC MGW Tandeming + +It is FFS the impacts to (G)MSC MGW Tandeming procedure as specified in 3GPP TS 23.205 [2]. + +# 19 Timers + +The Timers as defined for a BICC based CS Core Network shall be applied as defined in 3GPP TS 23.205 [2]. + +The Timers as defined for a SIP-I based CS Core Network shall be applied as defined in 3GPP TS 23.231 [3]. + +In addition to the timers mentioned above Table 19.1 defines new timers for LCLS. + +**Table 19.1: LCLS specific timers** + +| Timer identity | Timer value | Timer started | Timer stopped | Timer expiry | +|---------------------------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|--------------------------------------| +| LCLS_configuration_modification | 5 – 30 seconds | When the core network node which initiates LCLS Configuration Preference Modification procedure sends the LCLS Configuration Change Request message. | When the initiating node receives the LCLS Configuration Change Request Acknowledge message. | The LCLS Break procedure is started. | + +# 20 Multiple Realms + +The principles for multiple IP realms shall be applied as defined in 3GPP TS 23.205 [2]. + +# Annex A (informative): Case studies for LCLS Negotiation + +Annex A provides examples of LCLS negotiation in the CN and LCLS configuration in the BSS. The examples also illustrate optional isolation scenarios and the change of the initial set of preferences during LCLS negotiation. + +## A.1 oMSC LCLS-Negotiation handling when receiving UL bicast and sending DL data + +Case study 1: If the oMSC server requires receiving UL data from the terminating UE and sending DL data to the originating UE then it shall perform one of the following: + +- send LCLS-Negotiation (request) set to "LCLS-Not-Allowed" or; +- send LCLS-Negotiation (request) set to "Need\_Receive Backward = Yes, Need\_Send Backward = Yes", set LCLS-Configuration IE to "connected both-way in the BSS and send access DL from the Core Network, block local DL" on the originating call leg (as shown in Figure X.1.1). If the BSS supports this configuration then LCLS will be allowed; otherwise LCLS will not be permitted. + +NOTE 1: On the terminating leg the LCLS configuration IE is set to "connected both-way in the BSS and bi-cast UL to the Core Network" by the tMSC. + +![Diagram of oMSC requesting UL data from tUE plus sending DL data to oUE. The diagram shows a network architecture with three MSCs (MSC-S-o, MSC-S-I, MSC-S-t) connected in a chain. Below each MSC is a corresponding MGW (MGW-o, MGW-I, MGW-t). The MGWs are connected to a User Plane (connection). At the bottom, a BSS (BSS-1/ BSS-2) contains two UEs (UE-o and UE-t). The diagram illustrates the flow of UL data from UE-t to UE-o and DL data from UE-o to UE-t, with LCLS-Negotiation messages being exchanged between the MSCs and MGWs. A red box on the left indicates 'UL data requested from tUE' and 'DL send requested to apply a tone or announcement'. A red text box at the bottom left indicates an option with LCLS-Configuration IE to 'connected both-way in the BSS and send access DL from the Core Network, block local DL'. A red 'X' marks the 'Local DL data blocked by BSS'.](99e9a4791d2e5bb5afa1bb884652d4db_img.jpg) + +Diagram of oMSC requesting UL data from tUE plus sending DL data to oUE. The diagram shows a network architecture with three MSCs (MSC-S-o, MSC-S-I, MSC-S-t) connected in a chain. Below each MSC is a corresponding MGW (MGW-o, MGW-I, MGW-t). The MGWs are connected to a User Plane (connection). At the bottom, a BSS (BSS-1/ BSS-2) contains two UEs (UE-o and UE-t). The diagram illustrates the flow of UL data from UE-t to UE-o and DL data from UE-o to UE-t, with LCLS-Negotiation messages being exchanged between the MSCs and MGWs. A red box on the left indicates 'UL data requested from tUE' and 'DL send requested to apply a tone or announcement'. A red text box at the bottom left indicates an option with LCLS-Configuration IE to 'connected both-way in the BSS and send access DL from the Core Network, block local DL'. A red 'X' marks the 'Local DL data blocked by BSS'. + +Figure A.1.1: oMSC requesting UL data from tUE plus sending DL data to oUE + +Case study 2: If the oMSC server requires receiving UL data from the originating UE it shall either: + +- send LCLS-Negotiation (request) set to "Need\_Receive Forward = Yes" and set LCLS-Configuration IE to "connected both-way in the BSS and bi-cast UL" on the originating call leg after confirmation (as shown in Figure X1.2). If the BSS supports this configuration then LCLS will be allowed; otherwise LCLS will not be permitted. The data in the forward direction is passed to the tBSS due to the result of LCLS negotiation process on the originating call leg. + +NOTE 2: On the terminating leg the LCLS configuration IE is set to "connected both-way in the BSS" if LCLS connection preference that is negotiated through the Core Network only requires UL data from the oUE as shown in Figure X1.2. For the requested LCLS configuration on the terminating call leg the tBSS does not expect to receive any user data from the Core Network but is specified to discard if received. + +![Diagram of oMSC requesting UL data from oUE indicated in LCLS-Negotiation. It shows MSC-S-o, MSC-S-l, and MSC-S-t connected via LCLS-Negotiation (Need Receive Forward=yes). Below are MGW-o, MGW-l, and MGW-t connected via a User Plane (connection). At the bottom, a BSS-1/BSS-2 contains UE-o and UE-t. A purple arrow labeled 'UL data requested from oUE' points from MSC-S-o to UE-o. Another purple arrow labeled 'Local User Plane Data' points from UE-t back to MSC-S-o. A large 'X' is placed over the path from MGW-t to the right, indicating isolation.](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +Diagram of oMSC requesting UL data from oUE indicated in LCLS-Negotiation. It shows MSC-S-o, MSC-S-l, and MSC-S-t connected via LCLS-Negotiation (Need Receive Forward=yes). Below are MGW-o, MGW-l, and MGW-t connected via a User Plane (connection). At the bottom, a BSS-1/BSS-2 contains UE-o and UE-t. A purple arrow labeled 'UL data requested from oUE' points from MSC-S-o to UE-o. Another purple arrow labeled 'Local User Plane Data' points from UE-t back to MSC-S-o. A large 'X' is placed over the path from MGW-t to the right, indicating isolation. + +Figure A.1.2: oMSC requesting UL data from oUE indicated in LCLS-Negotiation + +- In order to avoid the forwarding of the data in the forward direction to the tMGW the oMSC can send LCLS-Negotiation (request) to the succeeding node set to "Need\_Receive\_Forward = No" and if it does not receive "Need\_Receive\_Forward = Yes" in the LCLS-Negotiation (response) then it may configure its MGW to isolate the network side termination from the access side termination (as shown in Figure X.1.3). + +![Diagram of oMSC requesting UL data from oUE not indicated in LCLS-Negotiation. It shows MSC-S-o, MSC-S-l, and MSC-S-t connected via LCLS-Negotiation (Need Receive Forward=no). Below are MGW-o, MGW-l, and MGW-t connected via a User Plane (connection). At the bottom, a BSS-1/BSS-2 contains UE-o and UE-t. A purple arrow labeled 'UL data requested from oUE' points from MSC-S-o to UE-o. Another purple arrow labeled 'Local User Plane Data' points from UE-t back to MSC-S-o. A red dashed arrow points from the text 'Option with Need_Receive_Forward = No: Isolate access side termination from network side termination' to the MGW-o node.](1314748d1fff41b2d57a8ba9e9687c6a_img.jpg) + +Diagram of oMSC requesting UL data from oUE not indicated in LCLS-Negotiation. It shows MSC-S-o, MSC-S-l, and MSC-S-t connected via LCLS-Negotiation (Need Receive Forward=no). Below are MGW-o, MGW-l, and MGW-t connected via a User Plane (connection). At the bottom, a BSS-1/BSS-2 contains UE-o and UE-t. A purple arrow labeled 'UL data requested from oUE' points from MSC-S-o to UE-o. Another purple arrow labeled 'Local User Plane Data' points from UE-t back to MSC-S-o. A red dashed arrow points from the text 'Option with Need\_Receive\_Forward = No: Isolate access side termination from network side termination' to the MGW-o node. + +Figure A.1.3: oMSC requesting UL data from oUE not indicated in LCLS-Negotiation + +- If the initial setting "Need\_Receive\_Forward = No" is overwritten by a succeeding Core Network node and the oMSC server receives "Need\_Receive\_Forward = Yes" in the LCLS-Negotiation (response) then it shall configure its MGW to be bothway through-connected (as shown in Figure X.1.4). + +![Diagram of UL data requested from oUE by iMSC/tMSC, oMGW bothway through-connected. It shows three MSCs (MSC-S-o, MSC-S-I, MSC-S-t) connected via LCLS-Negotiation messages. MSC-S-o sends 'UL data requested from oUE by oMSC & (iMSC and/or tMSC)'. MSC-S-I and MSC-S-t both have 'LCLS-Negotiation (Need Receive Forward=yes)'. Below the MSCs are MGWs (MGW-o, MGW-I, MGW-t) connected by a 'User Plane (connection)'. A red dashed arrow points from the text 'Result of LCLS-Negotiation Need_Receive_Forward = yes: oMGW bothway through connected' to the MGW-o. At the bottom, a BSS (BSS-1/ BSS-2) contains 'Local User Plane Data' and two UEs (UE-o, UE-t). A red 'X' is shown over a path from MGW-t.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) + +Diagram of UL data requested from oUE by iMSC/tMSC, oMGW bothway through-connected. It shows three MSCs (MSC-S-o, MSC-S-I, MSC-S-t) connected via LCLS-Negotiation messages. MSC-S-o sends 'UL data requested from oUE by oMSC & (iMSC and/or tMSC)'. MSC-S-I and MSC-S-t both have 'LCLS-Negotiation (Need Receive Forward=yes)'. Below the MSCs are MGWs (MGW-o, MGW-I, MGW-t) connected by a 'User Plane (connection)'. A red dashed arrow points from the text 'Result of LCLS-Negotiation Need\_Receive\_Forward = yes: oMGW bothway through connected' to the MGW-o. At the bottom, a BSS (BSS-1/ BSS-2) contains 'Local User Plane Data' and two UEs (UE-o, UE-t). A red 'X' is shown over a path from MGW-t. + +Figure A.1.4: UL data requested from oUE by iMSC/tMSC, oMGW bothway through-connected + +Case study 3: If the oMSC server receives a LCLS-Negotiation (response) set to "Need\_Send\_Backward = Yes" and "Need\_Receive\_Backward = Yes" (succeeding node of the oMSC server requires to send data to the oUE and to receive data from the tUE) then it shall perform one of the following: + +- send an LCLS-Negotiation (request) set to "LCLS-Not-Allowed" or; +- set the LCLS-Configuration IE to "connected both-way in the BSS and send access DL from the Core Network, block local DL" on the originating leg (as shown in Figure X.1.5). +If the BSS supports this configuration then LCLS will be allowed and the requested LCLS configuration will be confirmed; otherwise LCLS will not be permitted. + +NOTE 3: On the terminating leg the LCLS configuration IE is set to "connected both-way in the BSS and bi-cast UL to the Core Network" by the tMSC. + +![Diagram of iMSC requesting UL data from tUE plus sending DL data to oUE. It shows three MSCs (MSC-S-o, MSC-S-I, MSC-S-t) connected via LCLS-Negotiation messages. MSC-S-o sends 'DL send requested to apply a tone or announcement'. MSC-S-I and MSC-S-t both have 'LCLS-Negotiation (Need Receive Backward, Need Send Backward)'. Below the MSCs are MGWs (MGW-o, MGW-I, MGW-t) connected by a 'User Plane (connection)'. A red arrow points from the text 'Option with LCLS-Configuration IE: "connected both-way in the BSS and send access DL from the Core Network, block local DL"' to the MGW-o. At the bottom, a BSS (BSS-1/ BSS-2) contains 'Local User Plane Data' and two UEs (UE-o, UE-t). A red 'X' is shown over a path from MGW-o to UE-o, with the text 'Local DL data blocked by BSS'.](0cc154cbdde7cc6c39f394597c7aca0c_img.jpg) + +Diagram of iMSC requesting UL data from tUE plus sending DL data to oUE. It shows three MSCs (MSC-S-o, MSC-S-I, MSC-S-t) connected via LCLS-Negotiation messages. MSC-S-o sends 'DL send requested to apply a tone or announcement'. MSC-S-I and MSC-S-t both have 'LCLS-Negotiation (Need Receive Backward, Need Send Backward)'. Below the MSCs are MGWs (MGW-o, MGW-I, MGW-t) connected by a 'User Plane (connection)'. A red arrow points from the text 'Option with LCLS-Configuration IE: "connected both-way in the BSS and send access DL from the Core Network, block local DL"' to the MGW-o. At the bottom, a BSS (BSS-1/ BSS-2) contains 'Local User Plane Data' and two UEs (UE-o, UE-t). A red 'X' is shown over a path from MGW-o to UE-o, with the text 'Local DL data blocked by BSS'. + +Figure A.1.5: iMSC requesting UL data from tUE plus sending DL data to oUE + +## A.2 tMSC LCLS-Negotiation handling when receiving UL bicast and sending DL data + +Case study 1: If the tMSC server receives LCLS-Negotiation (request) with "Need\_Send\_Forward = Yes" and "Need\_Receive\_Forward = Yes" then it shall either: + +- return LCLS-Negotiation (response) set to "LCLS-Not-Allowed" or; +- return LCLS-Negotiation (response) with value "Need\_Send\_Forward = Yes" and "Need\_Receive\_Forward = Yes" and set LCLS-Configuration IE to "Send Access DL, block local DL" (as shown in Figure X.2.1). If the BSS supports this configuration then LCLS will be allowed; otherwise LCLS will not be permitted. + +NOTE 1: On the originating leg the LCLS configuration IE is set to "connected both-way in the BSS and bi-cast UL to the Core Network" by the oMSC. + +![Diagram illustrating the tMSC LCLS-Negotiation handling when receiving UL bicast and sending DL data. The diagram shows three MSCs (MSC-S-o, MSC-S-l, MSC-S-t) connected to three MGWs (MGW-o, MGW-l, MGW-t) via the User Plane (connection). The MGWs are connected to two UEs (UE-o, UE-t) via a BSS (BSS-1/ BSS-2). The diagram shows the flow of LCLS-Negotiation messages and the handling of UL and DL data. A red box indicates 'DL send requested to apply a tone or announcement' and a purple box indicates 'UL data requested from oUE'. The diagram also shows 'Local User Plane Data' being blocked by the BSS and an option with LCLS-Configuration IE: 'Send Access DL, block local DL'.](4bb669bb31262e53e4f3c8ec0fd7624a_img.jpg) + +The diagram illustrates the network architecture and data flow for LCLS negotiation. At the top, three MSCs (MSC-S-o, MSC-S-l, MSC-S-t) are shown. MSC-S-o and MSC-S-l are connected via LCLS-Negotiation messages. MSC-S-l and MSC-S-t are also connected via LCLS-Negotiation messages. Below the MSCs are three MGWs (MGW-o, MGW-l, MGW-t) connected via the User Plane (connection). The MGWs are connected to two UEs (UE-o, UE-t) via a BSS (BSS-1/ BSS-2). The diagram shows the flow of LCLS-Negotiation messages and the handling of UL and DL data. A red box indicates 'DL send requested to apply a tone or announcement' and a purple box indicates 'UL data requested from oUE'. The diagram also shows 'Local User Plane Data' being blocked by the BSS and an option with LCLS-Configuration IE: 'Send Access DL, block local DL'. + +Diagram illustrating the tMSC LCLS-Negotiation handling when receiving UL bicast and sending DL data. The diagram shows three MSCs (MSC-S-o, MSC-S-l, MSC-S-t) connected to three MGWs (MGW-o, MGW-l, MGW-t) via the User Plane (connection). The MGWs are connected to two UEs (UE-o, UE-t) via a BSS (BSS-1/ BSS-2). The diagram shows the flow of LCLS-Negotiation messages and the handling of UL and DL data. A red box indicates 'DL send requested to apply a tone or announcement' and a purple box indicates 'UL data requested from oUE'. The diagram also shows 'Local User Plane Data' being blocked by the BSS and an option with LCLS-Configuration IE: 'Send Access DL, block local DL'. + +Figure A.2.1: tMSC requesting UL data from oUE and sending DL data to tUE + +Case study 2: If the tMSC server requires sending DL data to the terminating UE and receives LCLS-Negotiation (request) with "Need\_Receive\_Forward = Yes" and "Need\_Send\_Forward = No" during a LCLS negotiation request it shall either: + +- return LCLS-Negotiation (response) set to "LCLS-Not-Allowed" or; +- set LCLS-Configuration IE to "connected both-way in the BSS and send access DL", return LCLS-Negotiation (response) with value "Need\_Send\_Forward = No" and "Need\_Receive\_Forward = Yes" and configure its Access MGW to isolate the network side termination from the access side termination when LCLS is established in order to avoid the forwarding of data from the oMGW/iMGW in the forward direction (as shown in Figure X.2.2), or; + +NOTE 2: On the originating leg the LCLS configuration IE is set to "connected both-way in the BSS and bi-cast UL to the Core Network" by the oMSC. + +![Diagram of iMSC requesting UL data from oUE and tMSC requesting DL data to tUE. The diagram shows three MSCs (MSC-S-o, MSC-S-l, MSC-S-t) connected via LCLS-Negotiation messages. Below them are MGWs (MGW-o, MGW-l, MGW-t) connected by a User Plane. At the bottom, a BSS contains UE-o and UE-t. Arrows show data flow: UL from UE-o to MSC-S-o, and DL from MSC-S-t to UE-t. A red box indicates an option to isolate access side termination.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +The diagram illustrates the network architecture and data flow for iMSC and tMSC operations. At the top, three MSCs are shown: MSC-S-o (Originating), MSC-S-l (Intermediate), and MSC-S-t (Terminating). They are interconnected by LCLS-Negotiation messages. MSC-S-o sends an LCLS-Negotiation to MSC-S-l. MSC-S-l sends an LCLS-Negotiation (Need Receive Forward) to MSC-S-t. MSC-S-t responds with an LCLS-Negotiation (Need Send Forward) back to MSC-S-l. MSC-S-l then sends an LCLS-Negotiation (Need Receive Forward) back to MSC-S-o. Below the MSCs are three MGWs: MGW-o, MGW-l, and MGW-t. MGW-o is connected to MSC-S-o and UE-o. MGW-l is connected to MSC-S-l. MGW-t is connected to MSC-S-t and UE-t. A thick purple line represents the User Plane connection between MGW-o and MGW-t, passing through MGW-l. At the bottom, a BSS (Base Station System) contains UE-o and UE-t. UE-o is connected to MGW-o, and UE-t is connected to MGW-t. A red box on the right indicates that a DL send is requested to apply a tone or announcement. A red dashed line from the BSS to MGW-t indicates an option with received LCLS-Negotiation Need\_Send\_Forward = No: Isolate access side termination from network side termination. + +Diagram of iMSC requesting UL data from oUE and tMSC requesting DL data to tUE. The diagram shows three MSCs (MSC-S-o, MSC-S-l, MSC-S-t) connected via LCLS-Negotiation messages. Below them are MGWs (MGW-o, MGW-l, MGW-t) connected by a User Plane. At the bottom, a BSS contains UE-o and UE-t. Arrows show data flow: UL from UE-o to MSC-S-o, and DL from MSC-S-t to UE-t. A red box indicates an option to isolate access side termination. + +**Figure A.2.2: iMSC requesting UL data from oUE and tMSC requesting DL data to tUE: option isolate access side termination from network side termination** + +- return LCLS-Negotiation (response) with value "Need\_Send\_Forward = Yes" and "Need\_Receive\_Forward = Yes" and set LCLS-Configuration IE to "Send Access DL, block local DL" (as shown in Figure X.2.3). If the BSS supports this configuration then LCLS will be allowed; otherwise LCLS will not be permitted. + +NOTE 3: On the originating leg the LCLS configuration IE is set to "connected both-way in the BSS and bi-cast UL to the Core Network" by the oMSC. + +![Diagram illustrating the network architecture for Figure A.2.3. It shows three MSCs (MSC-S-o, MSC-S-l, MSC-S-t) connected to a User Plane (connection) via MGWs (MGW-o, MGW-l, MGW-t). MSC-S-o is requesting UL data from oUE. MSC-S-t is requesting DL data to tUE. The diagram shows data flows for UL and DL, with a specific option highlighted for the tMSC: 'Option with LCLS-Configuration IE: "Send Access DL, block local DL"'. A red box indicates 'DL send requested to apply a tone or announcement.' and another red box indicates 'Local DL data blocked by BSS'.](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) + +The diagram shows a network architecture with three MSCs (MSC-S-o, MSC-S-l, MSC-S-t) connected to a User Plane (connection) via MGWs (MGW-o, MGW-l, MGW-t). MSC-S-o is requesting UL data from oUE. MSC-S-t is requesting DL data to tUE. The diagram shows data flows for UL and DL, with a specific option highlighted for the tMSC: 'Option with LCLS-Configuration IE: "Send Access DL, block local DL"'. A red box indicates 'DL send requested to apply a tone or announcement.' and another red box indicates 'Local DL data blocked by BSS'. + +Diagram illustrating the network architecture for Figure A.2.3. It shows three MSCs (MSC-S-o, MSC-S-l, MSC-S-t) connected to a User Plane (connection) via MGWs (MGW-o, MGW-l, MGW-t). MSC-S-o is requesting UL data from oUE. MSC-S-t is requesting DL data to tUE. The diagram shows data flows for UL and DL, with a specific option highlighted for the tMSC: 'Option with LCLS-Configuration IE: "Send Access DL, block local DL"'. A red box indicates 'DL send requested to apply a tone or announcement.' and another red box indicates 'Local DL data blocked by BSS'. + +**Figure A.2.3: iMSC requesting UL data from oUE and tMSC requesting DL data to tUE: option send Access DL, block local DL** + +Case study 3: If the tMSC server requires receiving UL data from the terminating UE and it receives LCLS-Negotiation (request) with "Need\_Receive\_Backward = No" (as shown in Figure X.2.4) during a LCLS negotiation request then it shall either: + +- set LCLS-Configuration IE to "connected both-way in the BSS and bi-cast UL" and return LCLS-Negotiation (response) with "Need\_Receive\_Backward = Yes" or; +- set LCLS-Configuration IE to "connected both-way in the BSS and bi-cast UL", return LCLS-Negotiation (response) with "Need\_Receive\_Backward = No" and configure its MGW to isolate its access side termination from the network side termination in order to avoid the forwarding of data in the backward direction through the CN. + +![Diagram of tMSC architecture showing MSC-S-o, MSC-S-l, MSC-S-t, MGW-o, MGW-l, MGW-t, UE-o, UE-t, and BSS-1/BSS-2 with various signaling and data flows.](3750b0149a6380885998ab3ca6a8787c_img.jpg) + +The diagram illustrates a network architecture involving three Mobile Switching Centers (MSC-S-o, MSC-S-l, MSC-S-t) and three Media Gateway (MGW) units (MGW-o, MGW-l, MGW-t). Each MSC is connected to its corresponding MGW via a vertical line. The MGWs are interconnected horizontally by a 'User Plane (connection)' line. Below the MGWs, there is a section containing two User Equipment (UE) units, UE-o and UE-t, and a Base Station Subsystem (BSS-1/BSS-2). UE-o and UE-t are connected to the BSS-1/BSS-2. The BSS-1/BSS-2 is connected to the User Plane connection. A red dashed arrow points from the BSS-1/BSS-2 to the MGW-t. A red text box on the right side of the diagram contains the text 'UL data requested from tUE'. A red text box at the bottom right contains the text 'Option with Need\_Receive\_Backward = No: Isolate access side termination from network side termination'. The MSC-S-o, MSC-S-l, and MSC-S-t units are connected to each other via horizontal lines. The MSC-S-o and MSC-S-l connection is labeled 'LCLS-Negotiation'. The MSC-S-l and MSC-S-t connection is labeled 'LCLS-Negotiation (Need Receive Backward=No)'. The MGW-o, MGW-l, and MGW-t units are connected to each other via horizontal lines. The MGW-o and MGW-l connection is labeled 'LCLS-Negotiation (Need Receive Backward=No)'. The MGW-l and MGW-t connection is labeled 'LCLS-Negotiation (Need Receive Backward=No)'. The UE-o and UE-t units are connected to the BSS-1/BSS-2 via vertical lines. The BSS-1/BSS-2 is connected to the User Plane connection via a horizontal line. The User Plane connection is labeled 'Local User Plane Data'. + +Diagram of tMSC architecture showing MSC-S-o, MSC-S-l, MSC-S-t, MGW-o, MGW-l, MGW-t, UE-o, UE-t, and BSS-1/BSS-2 with various signaling and data flows. + +Figure A.2.4: tMSC requires DL data from tUE: option isolate access side termination from network side termination + +# --- Annex B (informative): Change history + +| Change history | | | | | | | | +|----------------|--------|-----------|------|-----|-----------------------------------------------------------------------------------|--------|--------| +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | Old | New | +| 2011-03 | CT#51 | CP-110295 | | | V2.1.0 approved in CT#51 | 2.1.0 | 10.0.0 | +| 2011-06 | CT#52 | CP-110376 | 0001 | - | LCLS Handover Result Code update | 10.0.0 | 10.1.0 | +| 2011-06 | CT#52 | CP-110376 | 0002 | 1 | LCLS Re-establishment Result Code update | 10.0.0 | 10.1.0 | +| 2011-06 | CT#52 | CP-110376 | 0003 | 1 | LCLS Break Result Code update | 10.0.0 | 10.1.0 | +| 2011-06 | CT#52 | CP-110532 | 0004 | 1 | LCLS Call deflection clarification | 10.0.0 | 10.1.0 | +| 2011-06 | CT#52 | CP-110376 | 0005 | 1 | Update of Call Clearing and LCLS Break/Re-establishment | 10.0.0 | 10.1.0 | +| 2011-06 | CT#52 | CP-110376 | 0006 | 3 | Update of Handover | 10.0.0 | 10.1.0 | +| 2011-06 | CT#52 | CP-110376 | 0008 | 1 | Update of LCLS Call Establishment | 10.0.0 | 10.1.0 | +| 2011-06 | CT#52 | CP-110376 | 0009 | 2 | Clarification of LCLS Configuration and LCLS Negotiation | 10.0.0 | 10.1.0 | +| 2011-06 | CT#52 | CP-110376 | 0010 | 2 | Usage of option to isolate access side termination from network side | 10.0.0 | 10.1.0 | +| 2011-06 | CT#52 | CP-110376 | 0011 | - | Clarification of LCLS Configuration and LCLS Negotiation | 10.0.0 | 10.1.0 | +| 2011-09 | CT#53 | CP-110571 | 0012 | - | LCLS BSS Status update, call establishment subclauses | 10.1.0 | 10.2.0 | +| 2011-09 | CT#53 | CP-110571 | 0013 | - | LCLS BSS Status update, LCLS break and re-establishment subclauses | 10.1.0 | 10.2.0 | +| 2011-09 | CT#53 | CP-110571 | 0015 | 1 | LCLS BSS Status update, Call Forwarding subclauses | 10.1.0 | 10.2.0 | +| 2011-09 | CT#53 | CP-110571 | 0016 | 1 | Clarification of LCLS negotiation and handling of tones or announcements | 10.1.0 | 10.2.0 | +| 2011-09 | CT#53 | CP-110571 | 0017 | 1 | LCLS Configuration Applicability | 10.1.0 | 10.2.0 | +| 2011-09 | CT#53 | CP-110571 | 0019 | 1 | LCLS Connect during Handover | 10.1.0 | 10.2.0 | +| 2011-09 | CT#53 | CP-110571 | 0021 | - | Update of mid-call announcement/tone examples | 10.1.0 | 10.2.0 | +| 2011-09 | CT#53 | CP-110571 | 0022 | 1 | Negotiation of LCLS support | 10.1.0 | 10.2.0 | +| 2011-09 | CT#53 | CP-110723 | 0014 | 3 | LCLS BSS Status update, handover subclauses | 10.1.0 | 10.2.0 | +| 2011-12 | CT#54 | CP-110799 | 0023 | 3 | LCLS Negotiation clarifications and correction | 10.2.0 | 10.3.0 | +| 2011-12 | CT#54 | CP-110799 | 0025 | - | LCLS status update corrections | 10.2.0 | 10.3.0 | +| 2011-12 | CT#54 | CP-110799 | 0026 | 1 | Speech path restoration for LCLS break | 10.2.0 | 10.3.0 | +| 2011-12 | CT#54 | CP-110799 | 0027 | 1 | Correction on IE descriptions for the LCLS Notification procedure | 10.2.0 | 10.3.0 | +| 2011-12 | CT#54 | CP-110799 | 0028 | 1 | Correction on IE descriptions for the Handover procedure | 10.2.0 | 10.3.0 | +| 2011-12 | CT#54 | CP-110799 | 0029 | 1 | Correction on IE descriptions for the Assignment procedure | 10.2.0 | 10.3.0 | +| 2011-12 | CT#54 | CP-110799 | 0030 | 3 | Correction on Call Waiting procedure | 10.2.0 | 10.3.0 | +| 2011-12 | CT#54 | CP-110799 | 0032 | 3 | Clarifications and rules for LCLS re-negotiation | 10.2.0 | 10.3.0 | +| 2011-12 | CT#54 | CP-110799 | 0033 | 1 | Further corrections due to update to LCLS Connect during Handover | 10.2.0 | 10.3.0 | +| 2011-12 | CT#54 | CP-110799 | 0034 | 2 | Re-specifying the naming for LCLS Negotiation and LCLS Re-Negotiation | 10.2.0 | 10.3.0 | +| 2012-03 | CT#55 | CP-120207 | 0035 | 5 | Additional Control procedure during Inter-BSS Handover | 10.3.0 | 10.4.0 | +| 2012-03 | CT#55 | CP-120030 | 0036 | 1 | Correction on general concepts for modification of LCLS configuration preferences | 10.3.0 | 10.4.0 | +| 2012-03 | CT#55 | CP-120030 | 0037 | - | Update of basic call examples | 10.3.0 | 10.4.0 | +| 2012-03 | CT#55 | CP-120030 | 0038 | 1 | Update of call handover examples | 10.3.0 | 10.4.0 | +| 2012-03 | CT#55 | CP-120030 | 0039 | - | Update of service interworking examples | 10.3.0 | 10.4.0 | +| 2012-03 | CT#55 | CP-120030 | 0040 | - | Update of Mid-Call Announcement/tone examples | 10.3.0 | 10.4.0 | +| 2012-03 | CT#55 | CP-120030 | 0041 | 1 | Introduction of LCLS Configuration Modification timer | 10.3.0 | 10.4.0 | +| 2012-03 | CT#55 | CP-120030 | 0042 | 1 | Clarification of LCLS Connect_Control settings due to handover failure | 10.3.0 | 10.4.0 | +| 2012-09 | CT#57 | | | - | Automatic update from previous Release version 10.4.0 (MCC) | 10.4.0 | 11.0.0 | +| 2012-12 | CT#57 | CP-120724 | 0044 | 1 | LCLS Negotiation Procedures | 11.0.0 | 11.1.0 | +| 2013-12 | CT#62 | CP-130641 | 0045 | - | GERAN Iu Mode | 11.1.0 | 12.0.0 | +| 2015-12 | CT#70 | - | - | - | Update to Rel-13 version (MCC) | 12.0.0 | 13.0.0 | +| 2017-03 | CT#75 | - | - | - | Update to Rel-14 version (MCC) | 13.0.0 | 14.0.0 | +| 2018-06 | CT#80 | - | - | - | Update to Rel-15 version (MCC) | 14.0.0 | 15.0.0 | +| 2020-07 | CT#80e | - | - | - | Update to Rel-16 version (MCC) | 15.0.0 | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23285/0b87abe67b21a93777287649c33e755d_img.jpg b/marked/Rel-16/23_series/23285/0b87abe67b21a93777287649c33e755d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..086982a07062dc6aa8d7281a6896c5098c168294 --- /dev/null +++ b/marked/Rel-16/23_series/23285/0b87abe67b21a93777287649c33e755d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5107aaff02526efed60f8b94036c2d853dc81222f97106e6cb271cfaae03d9d0 +size 83511 diff --git a/marked/Rel-16/23_series/23285/1ad662a678c4f002de911d403f00de8e_img.jpg b/marked/Rel-16/23_series/23285/1ad662a678c4f002de911d403f00de8e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7aa30bfe7143db8f08a540e719f81d30dfebdc02 --- /dev/null +++ b/marked/Rel-16/23_series/23285/1ad662a678c4f002de911d403f00de8e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9aaa7a9b9e0770ebea75009a8768202abddb8b7ee5511c6a05d58d32dadc1ed4 +size 48856 diff --git a/marked/Rel-16/23_series/23285/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg b/marked/Rel-16/23_series/23285/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42b02e45142a35c8382e74bf10c4d1bdb315ae16 --- /dev/null +++ b/marked/Rel-16/23_series/23285/1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7b44d0a54348c9bd4f0fb9a78911fd153998255c286dbdb31b5905c09f20ae5e +size 27067 diff --git a/marked/Rel-16/23_series/23285/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23285/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7e0f845249893b6faf5cbe8f3deee2fc77bdc84b --- /dev/null +++ b/marked/Rel-16/23_series/23285/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7597d0b061b2bcddef31f63cf2ca9e378b0a0d95de6c1834359629f90b9dba9b +size 29489 diff --git a/marked/Rel-16/23_series/23285/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg b/marked/Rel-16/23_series/23285/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3881a37d739784f585317701ddb7a288d80fea4f --- /dev/null +++ b/marked/Rel-16/23_series/23285/4b587081b669e7c6695b0e5db5ea7f6d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:917b77937b28f2b4c25f720c9e495650c1fd71c1ed99c7d6b710cd1389296163 +size 42967 diff --git a/marked/Rel-16/23_series/23285/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/marked/Rel-16/23_series/23285/58f4167687de8d7339594e5f6fbe0bc6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2217685dccb5bbcd9f5ca4316a18f7e8daca819a --- /dev/null +++ b/marked/Rel-16/23_series/23285/58f4167687de8d7339594e5f6fbe0bc6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a05018ec991978fe156af17f9bfc648bb4f9231d8989fdc8de2c71c0e710bd1f +size 66638 diff --git a/marked/Rel-16/23_series/23285/5a4e62bead259c258d069fd3663ea670_img.jpg b/marked/Rel-16/23_series/23285/5a4e62bead259c258d069fd3663ea670_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c3cb97e2266a3684ec7e7998f93644e1352d032c --- /dev/null +++ b/marked/Rel-16/23_series/23285/5a4e62bead259c258d069fd3663ea670_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2136bf017ad22712c87b6ef53ce92ee79506e9e26852ffe6a62e269121d10f26 +size 77205 diff --git a/marked/Rel-16/23_series/23285/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/23_series/23285/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3f23e770db301242179e8e792ceaa780c6c9bd23 --- /dev/null +++ b/marked/Rel-16/23_series/23285/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e02e8b2c7a5a87ddb79871e7d80829865932adb2b8cd475041250dbbd0bae9a1 +size 9413 diff --git a/marked/Rel-16/23_series/23285/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/23_series/23285/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b4074eb2148617c3041a7d4a8b585759f3bad9b1 --- /dev/null +++ b/marked/Rel-16/23_series/23285/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:64f0958b56960ec38ba378c80d097d14a8504ab506e76f1b1da9e96f248d390d +size 5809 diff --git a/marked/Rel-16/23_series/23285/8e14350b4b669119a3bdfca7869110ca_img.jpg b/marked/Rel-16/23_series/23285/8e14350b4b669119a3bdfca7869110ca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0a88c721a7a438023bd3ca46a85ecd728c46d4bf --- /dev/null +++ b/marked/Rel-16/23_series/23285/8e14350b4b669119a3bdfca7869110ca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7db31590dbba4a03a5396544a4a4fd61ae0b147350ef8e04a92e4ae38c37073c +size 30734 diff --git a/marked/Rel-16/23_series/23285/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23285/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3bc7d94ebfa4f7a10af23056ef03ca7fd84cef2f --- /dev/null +++ b/marked/Rel-16/23_series/23285/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:11ce473db1faad77a05e34ae893d7ed30def6fa7e337cd5e5529614decc48ec2 +size 70377 diff --git a/marked/Rel-16/23_series/23285/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/marked/Rel-16/23_series/23285/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fc15acf94a6af94c94e6f55ba6814042c326a40 --- /dev/null +++ b/marked/Rel-16/23_series/23285/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a921c137e75e60a734916abac4f92d921d71b0ffa8e9733a66c529ae18a536b +size 24015 diff --git a/marked/Rel-16/23_series/23285/a4b963a07cc368283154762c4b156fe7_img.jpg b/marked/Rel-16/23_series/23285/a4b963a07cc368283154762c4b156fe7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..58e51905b06c80a8b0667fb1c44bd6402158012b --- /dev/null +++ b/marked/Rel-16/23_series/23285/a4b963a07cc368283154762c4b156fe7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67f0499a6544898e7d68bb06e80fcc29ff95b4e5e60bc49acc0841af3536d0fc +size 54438 diff --git a/marked/Rel-16/23_series/23285/e6df2733626a85205c1db682e6259c46_img.jpg b/marked/Rel-16/23_series/23285/e6df2733626a85205c1db682e6259c46_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50e96ee577bb3e0a9655420ff0a704d6cb7f7896 --- /dev/null +++ b/marked/Rel-16/23_series/23285/e6df2733626a85205c1db682e6259c46_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8536bf9c3d773e2aeef16a346e783c4fe37cf6e4f5a88d724ac27e89524faa73 +size 80383 diff --git a/marked/Rel-16/23_series/23285/f324fbc5d5af1e4da9cd932389f0064c_img.jpg b/marked/Rel-16/23_series/23285/f324fbc5d5af1e4da9cd932389f0064c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e311354a9fe620e8f29af23beacfd6604dfbb600 --- /dev/null +++ b/marked/Rel-16/23_series/23285/f324fbc5d5af1e4da9cd932389f0064c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3ce5d86e7102727708f78a82783ba505b3d0aaab5fa9f38cfbbd0ff5818c1b5d +size 37577 diff --git a/marked/Rel-16/23_series/23285/raw.md b/marked/Rel-16/23_series/23285/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..dd23fc454358831b8ff8604e9e4128fb436f9530 --- /dev/null +++ b/marked/Rel-16/23_series/23285/raw.md @@ -0,0 +1,1223 @@ + + +# 3GPP TS 23.285 V16.4.0 (2020-09) + +Technical Specification + +## **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for V2X services (Release 16)** + +![5G logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The 5G logo, featuring the text "5G" in a bold, black, sans-serif font. Above the "5G" text is a green graphic consisting of three curved lines, resembling a signal strength indicator or a stylized wave. + +5G logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, featuring the text "3GPP" in a bold, black, sans-serif font. Below the "3GPP" text is a red graphic consisting of three curved lines, resembling a signal strength indicator or a stylized wave. Below the logo, the text "A GLOBAL INITIATIVE" is written in a smaller, black, sans-serif font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +# **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +Internet + +--- + + + +## --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|----------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 6 | +| 2 References..... | 6 | +| 3 Definitions and abbreviations ..... | 7 | +| 3.1 Definitions..... | 7 | +| 3.2 Abbreviations ..... | 8 | +| 4 Architecture model and concepts..... | 8 | +| 4.1 General concept..... | 8 | +| 4.2 Architectural reference model..... | 9 | +| 4.2.1 PC5 and LTE-Uu based V2X architecture reference model ..... | 9 | +| 4.2.1.1 Non-roaming architecture for PC5 and LTE-Uu based V2X communication ..... | 9 | +| 4.2.1.2 Roaming architecture for PC5 and LTE-Uu based V2X communication ..... | 9 | +| 4.2.1.3 Inter-PLMN architecture for PC5 and LTE-Uu based V2X communication..... | 10 | +| 4.2.2 MBMS for LTE-Uu based V2X architecture reference model ..... | 11 | +| 4.2.3 Reference points ..... | 12 | +| 4.3 Functional entities ..... | 13 | +| 4.3.1 V2X Control Function ..... | 13 | +| 4.3.1.1 General..... | 13 | +| 4.3.1.2 V2X Control Function discovery..... | 13 | +| 4.3.2 UE..... | 13 | +| 4.3.3 V2X Application Server ..... | 14 | +| 4.3.4 MME..... | 14 | +| 4.3.5 BM-SC..... | 14 | +| 4.3.6 MBMS-GW ..... | 14 | +| 4.4 High level function..... | 15 | +| 4.4.1 Authorization and Provisioning for V2X communications ..... | 15 | +| 4.4.1.1 Authorization and provisioning for V2X communications over PC5 reference point ..... | 15 | +| 4.4.1.1.1 General ..... | 15 | +| 4.4.1.1.2 Policy/Parameter provisioning ..... | 15 | +| 4.4.1.1.3 Principles for applying parameters for V2X communications over PC5 reference point..... | 16 | +| 4.4.1.2 Authorization and provisioning for V2X communications over LTE-Uu reference point..... | 17 | +| 4.4.1.2.1 General ..... | 17 | +| 4.4.1.2.2 Policy/Parameter provisioning ..... | 17 | +| 4.4.2 V2X message transmission/reception over PC5 reference point..... | 18 | +| 4.4.3 V2X message transmission/reception over LTE-Uu reference point..... | 18 | +| 4.4.3.1 General..... | 18 | +| 4.4.3.2 V2X message transmission/reception via unicast..... | 19 | +| 4.4.3.3 V2X message reception via MBMS ..... | 19 | +| 4.4.4 V2X Application Server discovery ..... | 20 | +| 4.4.4.1 General..... | 20 | +| 4.4.4.2 Multiple V2X Application Server and Localized V2X Application Server discovery and routing ..... | 20 | +| 4.4.5 QoS handling for V2X communication..... | 20 | +| 4.4.5.1 QoS handling for V2X communication over PC5 reference point..... | 20 | +| 4.4.5.1a QoS handling for V2X communication over NR PC5 reference point ..... | 21 | +| 4.4.5.2 QoS handling for V2X communication over LTE-Uu reference point ..... | 21 | +| 4.4.6 Subscription to V2X services ..... | 21 | +| 4.4.7 MBMS bearer announcement for V2X use ..... | 22 | +| 4.4.7.1 General..... | 22 | +| 4.4.7.2 User Service Description for V2X Communication (V2X USD)..... | 22 | +| 4.4.7.3 User Service Description for V2X Application Server Discovery (V2X Server USD) ..... | 22 | +| 4.4.8 Support for V2X communication for UEs in limited service state ..... | 23 | +| 4.4.9 Charging support for V2X communication ..... | 23 | +| 4.4.9.1 Charging support for V2X communication over PC5 reference point ..... | 23 | +| 4.4.9.2 Charging support for V2X communication over LTE-Uu reference point ..... | 23 | +| 4.4.10 Security and privacy protection support for V2X communication..... | 24 | + +| | | | +|--------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|-----------| +| 4.5 | Identifiers ..... | 24 | +| 4.5.1 | Identifiers for V2X communication over PC5 reference point ..... | 24 | +| 5 | Functional description and information flows ..... | 24 | +| 5.1 | Control and user plane stacks..... | 24 | +| 5.1.1 | User plane for PC5 reference point supporting V2X services..... | 24 | +| 5.2 | Service authorization and update for V2X communications ..... | 25 | +| 5.2.1 | Service authorization procedures..... | 25 | +| 5.2.2 | Service authorization update procedures..... | 25 | +| 5.3 | Procedure for V2X communication over PC5 reference point ..... | 25 | +| 5.4 | Procedure for V2X communication over LTE-Uu reference point..... | 25 | +| 5.4.1 | V2X Application Server discovery using MBMS..... | 25 | +| 5.4.1.1 | General..... | 25 | +| 5.4.1.2 | Procedures for receiving V2X Application Server information via MBMS ..... | 26 | +| 5.4.2 | Procedure for V2X communication with MBMS ..... | 26 | +| 5.4.2.1 | MBMS service area mapping ..... | 26 | +| 5.4.2.1.1 | General ..... | 26 | +| 5.4.2.1.2 | Functional Description..... | 27 | +| 5.4.2.2 | Local MBMS based MBMS data delivery ..... | 27 | +| 5.5 | V2X impacts to EPC procedures..... | 29 | +| 5.5.1 | E-UTRAN attach procedure for UE ..... | 29 | +| 5.5.2 | Service Request procedures for UE..... | 29 | +| 5.5.3 | S1 Handover procedures for UE..... | 29 | +| 5.5.4 | X2 Handover procedures for UE..... | 30 | +| 5.5.5 | Tracking Area Update procedure for UE ..... | 30 | +| 5.5.6 | Insert Subscriber Data procedure for UE ..... | 30 | +| 5.5.7 | Delete Subscriber Data procedure for UE..... | 30 | +| 5.5.8 | V2X capability indication and V2X related information per PC5 RAT ..... | 30 | +| 5.5.9 | Support of V2X communication over NR PC5 reference point..... | 30 | +| Annex A (informative): Road Side Unit (RSU) implementation options..... | | 32 | +| Annex B (informative): Localized MBMS deployment options..... | | 33 | +| B.1 | General Description ..... | 33 | +| B.2 | Option of localized MBMS CN functions ..... | 33 | +| B.3 | Option of localized user plane of MBMS CN functions..... | 34 | +| Annex C (informative): Example hybrid operation modes for V2X communication over PC5 and LTE-Uu ..... | | 35 | +| C.1 | General..... | 35 | +| C.2 | PC5 based V2X communication with MBMS reception ..... | 35 | +| C.3 | Simultaneous LTE-Uu based and PC5 based V2X communication without MBMS..... | 35 | +| Annex D (informative): V2X Message Distribution Server deployment option..... | | 37 | +| D.1 | General Description ..... | 37 | +| Annex E (informative): Change history ..... | | 38 | + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- 1 Scope + +The present document specifies architecture enhancements to facilitate vehicular communications for Vehicle-to-Everything (V2X) services, which includes Vehicle-to-Vehicle (V2V), Vehicle-to-Pedestrian (V2P), Vehicle-to-Infrastructure (V2I), and Vehicle-to-Network (V2N), according to the use cases and service requirements defined in TS 22.185 [2] and TS 22.186 [28]. + +The following vehicular communications for V2X services are specified: + +- V2X communication over PC5 reference point. +- V2X communication over LTE-Uu reference point. + +V2X communication over NR PC5 reference point specified in TS 23.287 [30] is supported. + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 22.185: "Service requirements for V2X services". +- [3] ISO 17419:2018: "Intelligent transport systems - Cooperative systems - Globally unique identification". +- [4] IEEE Std 1609.12-2016: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE) - Identifier Allocations". +- [5] 3GPP TS 23.303: "Proximity-based Services (ProSe); Stage 2". +- [6] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [7] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE\_LTE)". +- [8] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description". +- [9] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification". +- [10] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +- [11] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs". +- [12] 3GPP TS 23.203: "Policy and charging control architecture". +- [13] IEEE Std 1609.3-2010: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE) - Networking Services". + +- [14] ISO 29281-1:2013: "Intelligent Transport Systems - Communications access for land mobiles (CALM) - Non-IP networking - Part 1: Fast networking & transport layer protocol (FNTP)". +- [15] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol". +- [16] ETSI TS 102 637-2 V1.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 2: Specification of Cooperative Awareness Basic Service". +- [17] ETSI TS 102 637-3 V1.1.1: "Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 3: Specifications of Decentralized Environmental Notification Basic Service". +- [18] 3GPP TS 32.277: "Proximity-based Services (ProSe) charging". +- [19] Void. +- [20] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging". +- [21] 3GPP TS 32.273: "Telecommunication management; Charging management; Multimedia Broadcast and Multicast Service (MBMS) charging". +- [22] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode". +- [23] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode". +- [24] Void. +- [25] 3GPP TS 33.185: "Security aspect for LTE support of V2X services". +- [26] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification". +- [27] 3GPP TS 24.386: "User Equipment (UE) to V2X control function; protocol aspects; Stage 3". +- [28] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios; Stage 1". +- [29] 3GPP TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point". +- [30] 3GPP TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services". +- [31] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions". +- [32] CCSA YD/T 3707-2020: "Technical requirements of network layer of LTE-based vehicular communication". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**Tx Profile:** The transmission format (i.e. which 3GPP Release) to be used by the UE over LTE PC5 RAT, see TS 36.300 [10]. + +For the purposes of the present document, the following terms and definitions given in ISO 17419 [3] apply: + +### Intelligent Transport Systems + +### ITS Application Identifier + +For the purposes of the present document, the following term and definition given in IEEE Std 1609.12-2016 [4] apply: + +### Provider Service Identifier + +For the purposes of the present document, the following term and definition given in TS 22.185 [2] apply: + +### Road Side Unit + +For the purposes of the present document, the following term and definition given in TS 23.303 [5] apply: + +### Geographical Area + +For the purposes of the present document, the following term and definition given in CCSA YD/T 3707-2020 [32] apply: + +### Application Identifier + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|----------|-----------------------------------| +| AID | Application Identifier | +| C-TEID | Common-Tunnel Endpoint IDentifier | +| ITS | Intelligent Transport Systems | +| ITS-AID | ITS Application Identifier | +| PSID | Provider Service Identifier | +| RSU | Road Side Unit | +| SIPTO@LN | SIPTO at the Local Network | +| USD | User Service Description | +| V2X | Vehicle-to-Everything | + +# --- 4 Architecture model and concepts + +## 4.1 General concept + +There are two modes of operation for V2X communication, namely over the PC5 and over LTE-Uu. LTE-Uu can be unicast and/or MBMS. These two operation modes may be used by a UE independently for transmission and reception, e.g. a UE can use MBMS for reception without using LTE-Uu for transmission. A UE may also receive V2X messages via LTE-Uu unicast downlink. + +For both operation modes, the following principles apply: + +- V2X Application Servers e.g. in different domains can communicate with each other for the exchange of V2X messages. The interface between V2X Application Servers and the methods of the exchange of messages between V2X Application Servers is out of scope of 3GPP. +- ProSe discovery feature (TS 23.303 [5] clause 5.3 ProSe Direct Discovery) is not required for V2X Services. + +NOTE: ProSe discovery feature can be used by a V2X supporting UE, but that is up to UE implementation. + +- Subject to regional regulations, lawful interception requirements apply to V2X Services. +- An RSU is not an architectural entity, but an implementation option. This is achieved by collocating a V2X application logic/server with some entities of the 3GPP system, as shown in examples in Annex A. + +## 4.2 Architectural reference model + +### 4.2.1 PC5 and LTE-Uu based V2X architecture reference model + +#### 4.2.1.1 Non-roaming architecture for PC5 and LTE-Uu based V2X communication + +Figure 4.2.1.1-1 shows the high level view of the non-roaming architecture for PC5 and LTE-Uu based V2X communication. + +![Figure 4.2.1.1-1: Non-roaming reference architecture for PC5 and LTE-Uu based V2X communication. The diagram shows a V2X Application Server connected to a V2X Control Function (V2). The V2X Control Function is connected to UE C (pedestrian) via V3, UE B (Vehicle) via V3 and PC5, and UE A (Vehicle) via V3 and PC5. UE C is connected to a V2X Application via V5 and PC5. UE B is connected to a V2X Application via V5 and PC5. UE A is connected to a V2X Application via V5 and PC5. UE A is connected to E-UTRAN via LTE-Uu. E-UTRAN is connected to MME via S1. MME is connected to S/P-GW via S6a. S/P-GW is connected to HSS via S6i. S/P-GW is connected to V2X Application via V3. UE D (stationary) is connected to a V2X Application via V5 and PC5. UE D is connected to E-UTRAN via LTE-Uu. The V2X Application Server is also connected to V3 and V1.](0b87abe67b21a93777287649c33e755d_img.jpg) + +Figure 4.2.1.1-1: Non-roaming reference architecture for PC5 and LTE-Uu based V2X communication. The diagram shows a V2X Application Server connected to a V2X Control Function (V2). The V2X Control Function is connected to UE C (pedestrian) via V3, UE B (Vehicle) via V3 and PC5, and UE A (Vehicle) via V3 and PC5. UE C is connected to a V2X Application via V5 and PC5. UE B is connected to a V2X Application via V5 and PC5. UE A is connected to a V2X Application via V5 and PC5. UE A is connected to E-UTRAN via LTE-Uu. E-UTRAN is connected to MME via S1. MME is connected to S/P-GW via S6a. S/P-GW is connected to HSS via S6i. S/P-GW is connected to V2X Application via V3. UE D (stationary) is connected to a V2X Application via V5 and PC5. UE D is connected to E-UTRAN via LTE-Uu. The V2X Application Server is also connected to V3 and V1. + +Figure 4.2.1.1-1: Non-roaming reference architecture for PC5 and LTE-Uu based V2X communication + +#### 4.2.1.2 Roaming architecture for PC5 and LTE-Uu based V2X communication + +Figure 4.2.1.2-1 shows the high level view of the roaming architecture for PC5 and LTE-Uu based V2X communication. In this figure, UE A uses a subscription of PLMN A and UE B uses a subscription of PLMN B; UE A is roaming in PLMN B while UE B is not roaming. + +A V2X Application Server may connect to multiple PLMNs, e.g. one V2X Application Server can connect with the V2X Control Function in PLMN A and the V2X Control Function in PLMN B in the figure. + +![Roaming reference architecture for PC5 and LTE-Uu based V2X communication diagram showing PLMN A and PLMN B components and interfaces.](e6df2733626a85205c1db682e6259c46_img.jpg) + +The diagram illustrates the roaming reference architecture for PC5 and LTE-Uu based V2X communication, divided into two main network domains: PLMN A and PLMN B, separated by a dashed vertical line. + +**PLMN A (Left):** Contains a V2X Application Server connected to a V2X Control Function (PLMN A) via interface V2. The V2X Control Function is connected to an HSS via interface V4 and to the V2X Control Function (PLMN B) via interface V6. The HSS is connected to the MME in PLMN B via interface S6a. + +**PLMN B (Right):** Contains a V2X Application Server connected to a V2X Control Function (PLMN B) via interface V2. The V2X Control Function is connected to an HSS via interface V4 and to the MME via interface S1. The HSS is connected to the MME via interface S6a. The MME is connected to an S/P-GW, which is connected to the SGi interface. The SGi interface is connected to the V2X Application Server via interface V3. The MME is also connected to an E-UTRAN via interface S1. The E-UTRAN is connected to UE A via interface LTE-Uu and to UE B via interface LTE-Uu. UE A is connected to a V2X Application via interface V5. UE B is connected to a V2X Application via interface V1. The V2X Application in PLMN B is also connected to the V2X Control Function (PLMN B) via interface V3. + +**Interfaces:** V1, V2, V3, V4, V5, V6, S1, S6a, S6b, S11, SGi, LTE-Uu, PC5. + +Roaming reference architecture for PC5 and LTE-Uu based V2X communication diagram showing PLMN A and PLMN B components and interfaces. + +Figure 4.2.1.2-1: Roaming reference architecture for PC5 and LTE-Uu based V2X communication + +#### 4.2.1.3 Inter-PLMN architecture for PC5 and LTE-Uu based V2X communication + +Figure 4.2.1.3-1 shows the high level view of the inter-PLMN architecture for PC5 and LTE-Uu based V2X communication. In this figure, UE A uses a subscription of PLMN A and UE B uses a subscription of PLMN B; UE A is roaming in PLMN C while UE B is not roaming. + +![Figure 4.2.1.3-1: Inter-PLMN reference architecture for PC5 and LTE-Uu based V2X communication. The diagram shows three PLMNs: PLMN A, PLMN B, and PLMN C. PLMN A contains a V2X Application Server, V2X Control Function (PLMN A), HSS, and UE A. PLMN B contains a V2X Application Server, V2X Control Function (PLMN B), HSS, MME, S/P-GW, E-UTRAN, and UE B. PLMN C contains a V2X Control Function (PLMN C), HSS, MME, S/P-GW, E-UTRAN, and UE A. Interfaces include V1 (between UE A and UE B), V2 (between V2X Application Servers), V3 (between UE A and V2X Control Function in PLMN A), V4 (between V2X Control Function in PLMN A and HSS in PLMN A), V5 (between UE A and V2X Application Server in PLMN B), V6 (between V2X Control Function in PLMN A and V2X Control Function in PLMN C), V7 (between V2X Control Function in PLMN B and HSS in PLMN B), V8 (between V2X Control Function in PLMN B and MME in PLMN B), V9 (between MME in PLMN B and S/P-GW in PLMN B), V10 (between S/P-GW in PLMN B and E-UTRAN in PLMN B), V11 (between E-UTRAN in PLMN B and UE B), V12 (between UE B and V2X Application in PLMN B), V13 (between UE B and V2X Control Function in PLMN B), V14 (between UE B and V2X Application Server in PLMN B), V15 (between UE B and V2X Control Function in PLMN C), V16 (between UE B and V2X Application Server in PLMN A), V17 (between UE B and V2X Control Function in PLMN A), V18 (between UE B and HSS in PLMN A), V19 (between UE B and MME in PLMN A), V20 (between UE B and S/P-GW in PLMN A), V21 (between UE B and E-UTRAN in PLMN A), V22 (between UE B and LTE-Uu in PLMN A), V23 (between UE B and V2X Control Function in PLMN A), V24 (between UE B and V2X Application Server in PLMN A), V25 (between UE B and V2X Control Function in PLMN A), V26 (between UE B and HSS in PLMN A), V27 (between UE B and MME in PLMN A), V28 (between UE B and S/P-GW in PLMN A), V29 (between UE B and E-UTRAN in PLMN A), V30 (between UE B and LTE-Uu in PLMN A).](5a4e62bead259c258d069fd3663ea670_img.jpg) + +Figure 4.2.1.3-1: Inter-PLMN reference architecture for PC5 and LTE-Uu based V2X communication. The diagram shows three PLMNs: PLMN A, PLMN B, and PLMN C. PLMN A contains a V2X Application Server, V2X Control Function (PLMN A), HSS, and UE A. PLMN B contains a V2X Application Server, V2X Control Function (PLMN B), HSS, MME, S/P-GW, E-UTRAN, and UE B. PLMN C contains a V2X Control Function (PLMN C), HSS, MME, S/P-GW, E-UTRAN, and UE A. Interfaces include V1 (between UE A and UE B), V2 (between V2X Application Servers), V3 (between UE A and V2X Control Function in PLMN A), V4 (between V2X Control Function in PLMN A and HSS in PLMN A), V5 (between UE A and V2X Application Server in PLMN B), V6 (between V2X Control Function in PLMN A and V2X Control Function in PLMN C), V7 (between V2X Control Function in PLMN B and HSS in PLMN B), V8 (between V2X Control Function in PLMN B and MME in PLMN B), V9 (between MME in PLMN B and S/P-GW in PLMN B), V10 (between S/P-GW in PLMN B and E-UTRAN in PLMN B), V11 (between E-UTRAN in PLMN B and UE B), V12 (between UE B and V2X Application in PLMN B), V13 (between UE B and V2X Control Function in PLMN B), V14 (between UE B and V2X Application Server in PLMN B), V15 (between UE B and V2X Control Function in PLMN C), V16 (between UE B and V2X Application Server in PLMN A), V17 (between UE B and V2X Control Function in PLMN A), V18 (between UE B and HSS in PLMN A), V19 (between UE B and MME in PLMN A), V20 (between UE B and S/P-GW in PLMN A), V21 (between UE B and E-UTRAN in PLMN A), V22 (between UE B and LTE-Uu in PLMN A), V23 (between UE B and V2X Control Function in PLMN A), V24 (between UE B and V2X Application Server in PLMN A), V25 (between UE B and V2X Control Function in PLMN A), V26 (between UE B and HSS in PLMN A), V27 (between UE B and MME in PLMN A), V28 (between UE B and S/P-GW in PLMN A), V29 (between UE B and E-UTRAN in PLMN A), V30 (between UE B and LTE-Uu in PLMN A). + +Figure 4.2.1.3-1: Inter-PLMN reference architecture for PC5 and LTE-Uu based V2X communication + +### 4.2.2 MBMS for LTE-Uu based V2X architecture reference model + +Figure 4.2.2-1a and figure 4.2.2-1b show the high level view of the reference architectures with MBMS for LTE-Uu based V2X communication. V2X Application Server may apply either MB2 or xMB reference points when managing MBMS service related information via BM-SC, MB2 reference point as defined in TS 23.468 [7] provides functionality related to group communication and xMB reference point as defined in TS 26.348 [29] provides functionality overall for any content and also supports security framework between content provider and BM-SC. + +![Figure 4.2.2-1a: Reference architecture for MBMS for LTE-Uu based V2X communication via MB2. The diagram shows a UE connected to an E-UTRAN via LTE-Uu. The E-UTRAN is connected to an MME via S1-MME. The MME is connected to an MBMS GW via M3. The MBMS GW is connected to a BM-SC via SGmb. The BM-SC is connected to a V2X Application Server via MB2-C and MB2-U. The V2X Application Server is connected to the UE via V1. The MBMS GW is also connected to the BM-SC via SGi-mb. The MME is also connected to the BM-SC via Sm.](8e14350b4b669119a3bdfca7869110ca_img.jpg) + +Figure 4.2.2-1a: Reference architecture for MBMS for LTE-Uu based V2X communication via MB2. The diagram shows a UE connected to an E-UTRAN via LTE-Uu. The E-UTRAN is connected to an MME via S1-MME. The MME is connected to an MBMS GW via M3. The MBMS GW is connected to a BM-SC via SGmb. The BM-SC is connected to a V2X Application Server via MB2-C and MB2-U. The V2X Application Server is connected to the UE via V1. The MBMS GW is also connected to the BM-SC via SGi-mb. The MME is also connected to the BM-SC via Sm. + +Figure 4.2.2-1a: Reference architecture for MBMS for LTE-Uu based V2X communication via MB2 + +![Figure 4.2.2-1b: Reference architecture for MBMS for LTE-Uu based V2X communication via xMB. The diagram shows a UE connected to an E-UTRAN via the LTE-Uu interface. The E-UTRAN is connected to an MME via the S1-MME interface. The MME is connected to an MBMS GW via the M1 interface. The MBMS GW is connected to a BM-SC via the SGmb interface. The BM-SC is connected to a V2X Application Server via the xMB-C and xMB-U interfaces. A reference point V1 is indicated between the UE and the V2X Application Server.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +graph LR + UE[UE] -- LTE-Uu --> E-UTRAN[E-UTRAN] + E-UTRAN -- S1-MME --> MME[MME] + MME -- M1 --> MBMS_GW[MBMS GW] + MBMS_GW -- SGmb --> BM_SC[BM-SC] + BM_SC -- xMB-C --> V2X_Application_Server[V2X Application Server] + BM_SC -- xMB-U --> V2X_Application_Server + V2X_Application_Server -- V1 --> UE + +``` + +Figure 4.2.2-1b: Reference architecture for MBMS for LTE-Uu based V2X communication via xMB. The diagram shows a UE connected to an E-UTRAN via the LTE-Uu interface. The E-UTRAN is connected to an MME via the S1-MME interface. The MME is connected to an MBMS GW via the M1 interface. The MBMS GW is connected to a BM-SC via the SGmb interface. The BM-SC is connected to a V2X Application Server via the xMB-C and xMB-U interfaces. A reference point V1 is indicated between the UE and the V2X Application Server. + +Figure 4.2.2-1b: Reference architecture for MBMS for LTE-Uu based V2X communication via xMB + +### 4.2.3 Reference points + +- V1:** The reference point between the V2X application in the UE and in the V2X Application Server. This reference point is out of scope of this specification. +- V2:** The reference point between the V2X Application Server and the V2X Control Function in the operator's network. The V2X Application Server may connect to V2X Control Functions belonging to multiple PLMNs. +- V3:** The reference point between the UE and the V2X Control Function in UE's home PLMN. It is based on the service authorization and provisioning part of the PC3 reference point defined in clause 5.2 of TS 23.303 [5]. It is applicable to both PC5 and LTE-Uu based V2X communication and optionally MBMS and LTE-Uu based V2X communication. +- V4:** The reference point between the HSS and the V2X Control Function in the operator's network. +- V5:** The reference point between the V2X applications in the UEs. This reference point is not specified in this release of the specification. +- V6:** The reference point between the V2X Control Function in the HPLMN and the V2X Control Function in the VPLMN. +- PC5:** The reference point between the UEs used for user plane for ProSe Direct Communication for V2X Service. +- S6a:** In addition to the relevant functions defined in TS 23.401 [6] for S6a, in case of V2X Service S6a is used to download V2X Service related subscription information to MME during E-UTRAN attach procedure or to inform MME subscription information in the HSS has changed. +- S1-MME:** In addition to the relevant functions defined in TS 23.401 [6] for S1-MME, in case of V2X Service it is also used to convey the V2X Service authorization from MME to eNodeB. +- xMB:** The reference point between the V2X Application Server (e.g. Content Provider) and the BM-SC, and defined in TS 26.348 [29]. +- MB2:** The reference point between the V2X Application Server and the BM-SC, and defined in TS 23.468 [7]. +- SGmb/SGi-mb/M1/M3:** The SGmb/SGi-mb/M1/M3 reference points are internal to the MBMS system and are defined in TS 23.246 [8]. +- LTE-Uu:** The reference point between the UE and the E-UTRAN. + +## 4.3 Functional entities + +### 4.3.1 V2X Control Function + +#### 4.3.1.1 General + +The V2X Control Function is the logical function that is used for network related actions required for V2X. In this version of the specification it is assumed that there is only one logical V2X Control Function in each PLMN that supports V2X Services. + +NOTE 1: If multiple V2X Control Functions are deployed within the same PLMN (e.g., for load reasons), then the method to locate the specific V2X Control Function (e.g., through a database lookup, etc.) is not defined in this version of the specification. + +V2X Control Function is used to provision the UE with necessary parameters in order to use V2X communication. It is used to provision the UEs with PLMN specific parameters that allow the UE to use V2X in this specific PLMN. V2X Control Function is also used to provision the UE with parameters that are needed when the UE is "not served by E-UTRAN". + +V2X Control Function may also be used to obtain V2X USDs for UEs to receive MBMS based V2X traffic, through V2 reference point from the V2X Application Server. + +V2X Control Function may also obtain the parameters required for V2X communications over PC5 reference point, from the V2X Application Server via V2 reference point. + +NOTE 2: The V2X Control Function in HPLMN can be always reached if Home Routed configuration is applied for PDN connection (e.g., the PDN GW is located in the HPLMN), when such function is supported by the HPLMN. In case of Local Breakout (e.g., the PDN GW is located in the VPLMN), a V2X Control Function Proxy can be deployed by the VPLMN to support UE to Home V2X Control Function communication, if inter-PLMN signalling is required. Whether a PDN connection is provided by Local Breakout or Home Routed is determined by the HSS configuration described in TS 23.401 [6]. The UE is not aware of this and, as such, it will not know which APN can be used for communication with the V2X Control Function, unless the specific APN information is configured in the UE indicating that this APN provides signalling connectivity between the UE and the Home V2X Control Function. + +#### 4.3.1.2 V2X Control Function discovery + +The V2X Control Function of HPLMN is discovered through interaction with the Domain Name Service function. The FQDN of a V2X Control Function in the Home PLMN may either be pre-configured in the UE, provisioned by the network or self-constructed by the UE, e.g., derived from the PLMN ID of the HPLMN. The IP address of a V2X Control Function in the Home PLMN may also be provisioned to the UE. + +### 4.3.2 UE + +The UE may support the following functions: + +- Exchange of V2X control information between UE and the V2X Control Function over the V3 reference point. +- Procedures for V2X communication over PC5 reference point and/or LTE-Uu reference point. +- Configuration of parameters for V2X communication (e.g., destination Layer-2 IDs, radio resource parameters, V2X Application Server address information, mapping between service types and V2X frequencies). These parameters can be pre-configured in the UE, or, if in coverage, provisioned by signalling over the V3 reference point from the V2X Control Function in the HPLMN. +- Provided with V2X USDs for receiving MBMS based V2X traffic via existing MBMS service announcement mechanisms, or provisioned from V2X Control Function, or provisioned from the V2X Application Server via V1 reference point. +- Provisioned with V2X Server USDs for receiving V2X Application Server information via MBMS. + +### 4.3.3 V2X Application Server + +The V2X Application Server (V2X AS) may support the following capabilities: + +- Receiving uplink data from the UE over unicast. +- Delivering data to the UE(s) in a target area using Unicast Delivery and/or MBMS Delivery. +- Mapping from geographic location information to appropriate target MBMS SAI(s) for the broadcast. +- Mapping from geographic location information to appropriate target 3GPP ECGI(s) for the broadcast. +- Mapping from UE provided ECGI to appropriate target MBMS SAI(s) for the broadcast. +- Providing the appropriate ECGI(s) and/or MBMS SAI(s) to BM-SC. +- Pre-configured with Local MBMS (L.MBMS) information (e.g. IP multicast address, multicast source (SSM), C-TEID). +- Pre-configured with L.MBMS's IP address and port number for the user-plane. +- Sending L.MBMS information to the BM-SC. +- Requests BM-SC for allocation/de-allocation of a set of TMGIs. +- Requests BM-SC for activating/deactivating/modifying the MBMS bearer. +- Providing the V2X USDs for UE to receive MBMS based V2X traffic to V2X Control Function. +- Providing the parameters for V2X communications over PC5 reference point to V2X Control Function. +- Providing the parameters for V2X communications over PC5 reference point to UE. + +### 4.3.4 MME + +In addition to the functions defined in TS 23.401 [6] and TS 23.246 [8], in case of V2X the MME performs the following functions: + +- Obtains subscription information related to V2X as part of the subscription data. +- Provides indication to the E-UTRAN about the UE authorization status on V2X use. + +### 4.3.5 BM-SC + +In addition to the functions defined in TS 23.246 [8] and TS 23.468 [7], in case of V2X the BM-SC performs the following functions: + +- Receives L.MBMS information from V2X Application Server. +- Sends L.MBMS information to the MBMS-GW. + +### 4.3.6 MBMS-GW + +In addition to the functions defined in TS 23.246 [8], in case of V2X the MBMS-GW performs the following functions: + +- If receiving L.MBMS information from the BM-SC, skipping the allocation procedure for IP multicast distribution, e.g., allocating an IP multicast address. + +## 4.4 High level function + +### 4.4.1 Authorization and Provisioning for V2X communications + +#### 4.4.1.1 Authorization and provisioning for V2X communications over PC5 reference point + +##### 4.4.1.1.1 General + +The basic principles of service authorization for V2X communications over PC5 reference point: + +- The UE gets authorization to use V2X communications over PC5 reference point on a per PLMN basis in the serving PLMN by the V2X Control Function in the HPLMN. +- The V2X Control Function in the HPLMN requests authorization information from the V2X Control Function of the serving PLMN. +- The V2X Control Function in the HPLMN merges authorization information from home and serving PLMNs and informs the UE of the final authorization information. +- The V2X Control Function in the VPLMN or HPLMN may revoke the authorization at any time. The V2X Control Function in the HPLMN shall be notified when authorization is revoked by the VPLMN. + +##### 4.4.1.1.2 Policy/Parameter provisioning + +The following information for V2X communications over PC5 reference point is provisioned to the UE: + +###### 1) Authorization policy: + +- When the UE is "served by E-UTRAN": + - PLMNs in which the UE is authorized to perform V2X communications over PC5 reference point. +- When the UE is "not served by E-UTRAN": + - Indicates whether the UE is authorized to perform V2X communications over PC5 reference point when "not served by E-UTRAN". + +###### 2) Radio parameters for when the UE is "not served by E-UTRAN": + +- Includes the radio parameters with Geographical Area(s) and an indication of whether they are "operator managed" or "non-operator managed". These radio parameters (e.g. frequency bands) are defined in TS 36.331 [9]. The UE uses the radio parameters to perform V2X communications over PC5 reference point when "not served by E-UTRAN" only if the UE can reliably locate itself in the corresponding Geographical Area. Otherwise, the UE is not authorized to transmit. + +NOTE 1: Whether a frequency band is "operator managed" or "non-operator managed" in a given Geographical Area is defined by local regulations. + +###### 3) Policy/parameters: + +- The mapping of Destination Layer-2 ID(s) and the V2X services, e.g. PSIDs, ITS-AIDs or AIDs of the V2X application. + +NOTE 2: PLMN operators coordinate to make sure Destination Layer-2 ID(s) for different V2X services are configured in a consistent manner. + +NOTE 3: To pre-configure a UE with the provisioning parameters, at least the "not served by E-UTRAN" parameters of 1) and 2), and the parameters of 3) need to be included. + +- The mapping of ProSe Per-Packet Priority and packet delay budget for V2X communication (autonomous resources selection mode). + +- The list of V2X services, e.g. PSIDs, ITS-AIDs or AIDs of the V2X applications, with Geographical Area(s) that require privacy support. +- The mapping of service types (e.g. PSIDs, ITS-AIDs or AIDs) to V2X frequencies (see TS 36.300 [10] for further information) with Geographical Area(s). +- The mapping of service types (e.g. PSIDs, ITS-AIDs or AIDs) to Tx Profiles (see TS 36.300 [10] for further information). +- The list of V2X services, e.g. PSIDs, ITS-AIDs or AIDs of the V2X applications, allowed to use a specific PPPR value. + +###### 4) Policy/parameters for NR PC5: + +- Same as specified in TS 23.287 [30] clause 5.1.2.1 item 6) Policy/parameters when NR PC5 is selected. + +Alternatively, the above parameters in 2) and 3) may be configured on the UE through the V1 reference point from the V2X Application Server. The V2X Control Function may also obtain these parameters through the V2 reference point from the V2X Application Server. + +The parameters provisioned by the V2X Control Function take precedence over the configured parameters on the UE. + +NOTE 4: The V2 reference point procedure is not specified in this Release. + +##### 4.4.1.1.3 Principles for applying parameters for V2X communications over PC5 reference point + +For V2X communication over PC5, the operator may pre-configure the UEs with the required provisioning parameters for V2X Communication, without the need for the UEs to connect to the V2X Control Function to get this initial configuration. The following apply: + +- The provisioning parameters for V2X communications over PC5 may be configured in the UICC, in the ME, or in both the UICC and the ME. +- The ME provisioning parameters shall not be erased when a USIM is deselected or replaced. +- If both the UICC and the ME contain the same set of provisioning parameters, the set of parameters from the UICC shall take precedence. +- The UE shall use radio resources for V2X communications over PC5 reference point as follows: + - While a UE has a serving cell and is camped on a cell and the UE intends to use for V2X service the radio resources (i.e. carrier frequency) operated by this cell, then the UE shall use the radio resource description indicated by this cell the UE is camped on and ignore any radio resource description of the same radio resource provisioned in the ME or the UICC. If the cell does not provide radio resources for V2X service, the UE shall not perform V2X message transmission and reception on radio resources operated by this cell. + - If the UE intends to use "operator-managed" radio resources (i.e. carrier frequency) for V2X service that are not operated by the UE's serving cell, as specified in clause 4.4.1.1.2, or if the UE is out of coverage, the UE shall search for a cell in any PLMN that is operating the provisioned radio resources (i.e. carrier frequency) as defined in TS 36.300 [10] and TS 36.304 [22], and: + - If the UE finds such cell in the registered PLMN or a PLMN equivalent to the registered PLMN, and authorization for V2X communications over PC5 reference point to this PLMN is confirmed, the UE shall use the radio resource description indicated by that cell. If that cell does not provide radio resources for V2X service, the UE shall not perform V2X message transmission and reception on those radio resources. + - If the UE finds such cell but not in the registered PLMN or a PLMN equivalent to the registered PLMN, and that cell belongs to a PLMN authorized for V2X communications over PC5 reference point and provides radio resources for V2X service then the UE shall perform PLMN selection triggered by V2X communications over PC5 reference point as defined in TS 23.122 [23]. If the UE has an ongoing emergency session, it shall not trigger any PLMN selection due to V2X communication over PC5 reference point. + +NOTE 1: An ongoing emergency session could be either using IMS or CS as described in TS 23.167 [31]. + +- If the UE finds such cell but not in a PLMN authorized for V2X communications over PC5 reference point the UE shall not use V2X communications over PC5 reference point. +- If the UE does not find any such cell in any PLMN, then the UE shall consider itself "not served by E-UTRAN" and use radio resources provisioned in the ME or the UICC. If no such provision exists in the ME or the UICC or the provision does not authorize V2X communications over PC5 reference point then the UE is not authorized to transmit. +- If the UE intends to use "non-operator-managed" radio resources (i.e. carrier frequency) for V2X service, according to TS 36.331 [9] and as specified in clause 4.4.1.1.2, then the UE shall perform V2X communication over PC5 using resource provisioned in the ME or the UICC. If no such provision exists in the ME or the UICC or the provision does not authorize V2X communications over PC5 reference point then the UE is not authorized to transmit. +- The UE provisioning shall support setting Geographical Areas. + +NOTE 2: It is possible for a UE to use other radio resources for V2X service based on the Geographical Area instead of those operated by the serving E-UTRAN cell, when provisioned in the UE, even if the UE's serving cell offers normal service and the SIB21 indicates that the service (V2X communication) is available. This is to cover the scenario when e.g. the radio resources used for V2X communications over PC5 reference point are not owned by the serving network of the UE. + +NOTE 3: When cross-carrier operation is supported, according to TS 36.331 [9], a UE can be instructed by its serving cell to perform V2X communication over a different carrier frequency. The UE is still considered as "served by E-UTRAN" in this case. + +NOTE 4: The scenario that a cell is detected and the cell does not provide support for V2X communications over PC5 reference point when the UE attempts to use a carrier frequency configured for V2X communications over PC5 reference point, is considered a configuration error. Therefore the UE does not transmit on that frequency to avoid interference to the network. + +- The V2X communications over PC5 reference point is only specified for E-UTRA. + +NOTE 5: It is out of scope of the present specification to define how the UE can locate itself in a specific Geographical Area. When the UE is in coverage of a 3GPP RAT, it can for example, use information derived from the serving PLMN. When the UE is not in coverage of a 3GPP RAT, it can use other techniques, e.g. Global Navigation Satellite System (GNSS). User provided location is not a valid input. + +#### 4.4.1.2 Authorization and provisioning for V2X communications over LTE-Uu reference point + +##### 4.4.1.2.1 General + +Additional information may be provisioned to the UE for the use of V2X communications over LTE-Uu reference point, e.g. for unicast or MBMS. + +NOTE: A single V2X Application Server can support multiple V2X applications. + +##### 4.4.1.2.2 Policy/Parameter provisioning + +The following information may be configured in V2X Control Function and optionally provisioned to the UE for V2X communications over LTE-Uu reference point: + +1) PLMNs in which the UE is authorized to use MBMS based V2X communication. + +- Corresponding V2X USD(s) for receiving MBMS based V2X traffic in the PLMN. The V2X USD(s) may be obtained through the V2 reference point from the V2X Application Server. + +NOTE: The V2 reference point procedure is not specified in this Release. + +2) V2X Application Server address information. + +- List of FQDNs or IP addresses of the V2X Application Servers, associated with served geographical area information and list of PLMNs that the configuration applies to. + +###### 3) V2X Application Server discovery using MBMS. + +- List of PLMNs and corresponding V2X Server USDs for receiving V2X Application Server information via MBMS. + +###### 4) Mapping of the V2X services, e.g. PSIDs, ITS-AIDs or AIDs of the V2X application to: + +- V2X Application Server address (consisting of IP address/FQDN and TCP or UDP port) for unicast; +- V2X USD for MBMS. + +Information of the V2X USD is described in clause 4.4.7.2 and information of the V2X Server USD is described in clause 4.4.7.3. + +### 4.4.2 V2X message transmission/reception over PC5 reference point + +PC5 reference point as defined in TS 23.303 [5] is used for the transmission and reception of V2X messages. The V2X communication over PC5 reference point supports roaming and inter-PLMN operations. V2X communication over PC5 reference point is supported when the UE is "served by E-UTRAN" and when the UE is "not served by E-UTRAN". + +A UE is authorized to transmit and receive V2X messages by the V2X Control Function in its home PLMN as described in clause 5.2. + +The V2X communication over PC5 reference point is a type of ProSe Direct Communication with the following characteristics: + +- The V2X communication over PC5 reference point is connectionless, and there is no signalling over PC5 control plane for connection establishment. +- V2X messages are exchanged between UEs over PC5 user plane. +- Both IP based and non-IP based V2X messages are supported. +- For IP based V2X messages, only IPv6 is used. IPv4 is not supported in this release. + +The identifiers used in the V2X communication over PC5 reference point are described in clause 4.5.1. UE decides on the Tx Profile to use for the transmission of a particular packets based on the configuration described in clause 4.4.1.1.2. + +When the network scheduled operation mode is used, following additional principle applies: + +- When the eNB receives a request for PC5 resource from a UE, the eNB may deduce the Tx Profile from the Destination L2 ID. + +NOTE 1: The mapping from Destination L2 ID to Tx Profile is configured in the eNB. The eNB can determine the Tx Profiles that the UE needs to use for transmitting the packets thus utilising the resources available appropriately -i.e. handling of sidelink grant), see TS 36.321 [26] for details. + +If the UE has an ongoing emergency session, the communication over the emergency session shall be prioritized over V2X communication over PC5 reference point. + +NOTE 2: An ongoing emergency session could be either using IMS or CS as described in TS 23.167 [31]. + +NOTE 3: The emergency session setup is based on appropriate regional/national regulatory requirements and operator policies as defined in TS 23.401 [6]. + +### 4.4.3 V2X message transmission/reception over LTE-Uu reference point + +#### 4.4.3.1 General + +The LTE-Uu reference point is used for the transmission and reception of V2X messages. The V2X message transmission and reception via unicast is described in clause 4.4.3.2, while the V2X message reception via MBMS is described in clause 4.4.3.3. + +#### 4.4.3.2 V2X message transmission/reception via unicast + +The V2X communication via unicast over the LTE-Uu reference point supports roaming operations. Latency reduction for V2X message transfer via unicast may be achieved by using SIPTO@LN or SIPTO above RAN as defined in TS 23.401 [6]. + +NOTE 1: In case of SIPTO@LN with L-GW function collocated with an eNB, mobility is not supported. + +For transport of IP based or non-IP based V2X messages using uplink unicast V2X communication in case of applications identified by e.g. PSID, ITS-AID, or AID for the same applications as over PC5 reference point: + +- V2X messages are transported over TCP/IP or UDP/IP packets. The UE may learn from V2X Application Server or UE may be configured explicitly about a transport layer protocol to be used, or no restriction is imposed by configuration; + +NOTE 2: When IP multicast is used, only UDP/IP is supported. + +- the UE sends a V2X message over TCP/IP or UDP/IP to a V2X Application Server address. The destined V2X Application Server address is derived from e.g. the PSID (or the ITS-AID, or the AID) and the UE configuration as described in clause 4.4.1.2.2; and +- the V2X Application Server receives the V2X message in a TCP/IP or UDP/IP packet on a V2X Application Server address. + +For transport of V2X messages: + +- for applications different from the applications with e.g. PSID, ITS-AID or AID for PC5 reference point, or +- for configured applications with e.g. PSID, ITS-AID or AID sending IP based V2X messages, + +existing unicast routing towards application server applies. + +NOTE 3: In case V2X application uses TCP/IP or UDP/IP transport then existing unicast routing towards application server applies, i.e. no further encapsulation is performed. + +#### 4.4.3.3 V2X message reception via MBMS + +V2X messages can be broadcasted via MBMS in which the V2X Application Server transfers V2X messages via MBMS bearer service(s) as shown in Figure 4.2.2-1a. + +For MBMS reception of V2X messages, V2X USD per PLMN for V2X services is required for the UE. The UE is provisioned with mapping of e.g. PSID (or ITS-AID, or AID) and V2X USD as described in clause 4.4.1.2.2. + +To provide the UE with the V2X USD(s), the following ways may be used: + +- Existing MBMS service announcement mechanisms specified in TS 23.246 [8] and TS 26.346 [11]. +- Provisioning as described in clause 4.4.1.2.2, i.e. pre-configuration in the UE and/or configuration from V2X Control Function. +- Provisioning from the V2X Application Server via V1 reference point. + +NOTE 1: The UE can receive the downlink broadcast from the PLMN other than Serving PLMN based on the V2X USD(s) obtained as described in this clause. + +NOTE 2: The operator can configure multiple MBMS Service Areas for a specific V2X service. If any of these MBMS Service Areas overlap, the UE needs to be configured with different TMGIs for these overlapping MBMS Service Areas for this V2X service. + +The V2X Application Server providing the V2X service identified by e.g. the PSID (or the ITS-AID, or the AID) sends the V2X message via UDP/IP transport using information provided in the V2X USD. + +For latency improvements for MBMS, localized MBMS can be considered for localized routing of V2X messages destined to UEs. Some localized MBMS deployment options are described in Annex B. + +### 4.4.4 V2X Application Server discovery + +#### 4.4.4.1 General + +A UE needs to discover the V2X Application Server(s), when V2X communication over LTE-Uu operation mode is used. The V2X Application Server address information may be configured on the UE or provisioned via V3 interface, as specified in clause 4.4.1.2.2. + +When the configuration contains the FQDN(s), the UE shall perform DNS to resolve the address(es) of the V2X Application Server. The UE may use the configured V2X Application Server information only in the designated geographical area. When the UE changes serving PLMN or crosses configured geographic areas, it should perform address resolution again. + +For a network that has deployed broadcast mechanisms, e.g. MBMS, additional information to assist V2X Application Server discovery can be provided via the MBMS broadcast channel. When a UE has the configuration for receiving V2X Application Server information via MBMS, as specified in clause 4.4.1.2.2, it can perform the procedures specified in clause 5.4.1 to obtain additional local V2X Application Server information. The local V2X Application Server information obtained by MBMS as described in clause 5.4.1 takes precedence over the V2X Application Server information in the UE. + +#### 4.4.4.2 Multiple V2X Application Server and Localized V2X Application Server discovery and routing + +Multiple V2X Application Servers may be involved in the V2X communication, each providing particular V2X services and/or serving a particular geographical region. Therefore, the V2X Application Server address information as specified in clause 4.4.1.2.2 can contain multiple servers' information. When multiple V2X Application Servers are configured, the application layer will choose the proper V2X Application Server to use. + +When localized V2X Application Servers are deployed, Anycast may be used to conceal the server change from the UE. In this case, a FQDN is configured for a large region, e.g. the entire PLMN, and the UE only needs to resolve it once to an Anycast address. The PDN GW or LGW is responsible for routing the traffic to the appropriate local V2X Application Servers based on Anycast address. + +### 4.4.5 QoS handling for V2X communication + +#### 4.4.5.1 QoS handling for V2X communication over PC5 reference point + +Core Network, i.e. MME, provides the UE-PC5-AMBR based on subscription information to the eNB as part of the UE context information. + +When PC5 is used for the transmission of V2X messages, the following principles are followed for both network scheduled operation mode and UE autonomous resources selection mode: + +- ProSe Per-Packet Priority (PPPP) defined in clause 5.4.6.1 of TS 23.303 [5] applies to the V2X communication over PC5. +- ProSe Per-Packet Reliability (PPPR) applies to the V2X communication over PC5 as defined in TS 23.303 [5]. PPPR has a value range of 1 to 8, where the higher value represents the lower reliability requirement for that message. The UE may be configured with a list of V2X services, e.g. PSIDs, ITS-AIDs or AIDs allowed to use the specific PPPR value. +- The application layer sets the PPPP for each V2X message when passing it to lower layer for transmission. +- The application layer may set the PPPR for each V2X message when passing it to lower layer for transmission. +- The mapping of application layer V2X message priority to PPPP is configuration on the UE. +- The mapping of application layer V2X message reliability to PPPR is configuration on the UE. +- The setting of the PPPP value should reflect the latency required in both UE and eNB, i.e. the low PDB is mapped to the high priority PPPP value. + +- The mapping between V2X service types and V2X frequencies is as defined in clause 4.3.2 and clause 4.4.1.1.2. +- The mapping of Destination Layer-2 ID(s) and the V2X services, e.g. PSIDs, ITS-AIDs or AIDs of the V2X application is as described in clause 4.4.1.1.2. + +NOTE: The mapping of PPPP to packet delay budget is not specified in this specification. + +When the network scheduled operation mode is used, following additional principles apply: + +- UE provides priority information reflecting PPPP to the eNB for resources request. +- When the eNB receives a request for PC5 resource from a UE, the eNB can deduce the packet delay budget from the priority information reflecting PPPP from the UE. +- eNB can use the priority information reflecting PPPP for priority handling and UE-PC5-AMBR for capping the UE PC5 transmission in the resources management. +- UE may provide PPPR information reflecting reliability requirement described in TS 22.186 [28] to the eNB for resources request. +- UE provides Destination Layer-2 ID(s) of the V2X services to the eNB for resources requested as defined in TS 36.321 [26]. +- When the eNB receives a request for PC5 resource from a UE, the eNB determines the V2X frequency(ies) in which the V2X service is to be scheduled as defined in TS 36.300 [10]. + +When the autonomous resources selection mode is used, following additional principle applies: + +- The UE derives the packet delay budget of the V2X message from PPPP based on the provisioned mapping information described in clause 4.4.1.1.2. +- The UE derives the frequency in which a V2X service is to be transmitted, from the mapping between V2X service types and V2X frequencies as described in clause 4.4.1.1.2. + +#### 4.4.5.1a QoS handling for V2X communication over NR PC5 reference point + +The QoS handling for V2X communication over NR PC5 reference point as defined in TS 23.287 [30] clause 5.4 is applied. + +#### 4.4.5.2 QoS handling for V2X communication over LTE-Uu reference point + +The V2X messages can be delivered via Non-GBR bearer as well as GBR bearer. + +The following standardized QCI values defined in TS 23.203 [12] can be used: + +- QCI 3 and QCI 79 can be used for the unicast delivery of V2X messages; +- QCI 75 is only used for the delivery of V2X messages over MBMS bearers. + +### 4.4.6 Subscription to V2X services + +The user's profile in the HSS contains the subscription information to give the user permission to use V2X services. + +At any time, the operator can remove the UE subscription rights for V2X services from user's profile in the HSS, and revoke the user's permission to use V2X services. + +The following subscription information is defined for V2X services: + +- a) whether the UE is authorized to perform V2X communication over PC5 reference point as Vehicle UE, Pedestrian UE, or both, including for LTE PC5 and for NR PC5. +- b) UE-PC5-AMBR for V2X communication over PC5 reference point, including UE-PC5-AMBR for LTE PC5 and for NR PC5. + +- c) the list of the PLMNs where the UE is authorized to perform V2X communication over PC5 reference point. For each PLMN in the list, the RAT(s) over which the UE is authorized to perform V2X communication over PC5 reference point. +- d) PC5 QoS parameters for V2X communication over NR PC5 reference point as defined in TS 23.287 [30] clause 5.4.2. + +The HSS provides a), b) and d) to MME as subscription information and the MME provides a), b) and d) to eNB as part of the UE context information. + +The HSS provides c) to V2X Control Function. + +### 4.4.7 MBMS bearer announcement for V2X use + +#### 4.4.7.1 General + +MBMS bearer announcements are needed for V2X message reception via MBMS as defined in clause 4.4.3.3, or V2X Application Server discovery via MBMS as defined in clauses 4.4.4.1 and 5.4.1. + +The method for delivering the per PLMN configuration to the UE is specified in clause 4.4.3.3. The announced service information for V2X use should follow the guidance in clauses 4.4.7.2 and 4.4.7.3. + +#### 4.4.7.2 User Service Description for V2X Communication (V2X USD) + +As the V2X Application Server is out of scope of 3GPP, the exact information to be included in the V2X USD cannot be controlled. However, the V2X Application Server should make sure that the information listed in table 4.4.7.2-1 is included in the V2X USD it provides. + +The V2X message formats are handled by upper layer via Session Description Protocol (SDP). + +**Table 4.4.7.2-1: Information for V2X USD** + +| Information element | Description | +|--------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TMGI | TMGI information | +| List of service area identifier | A list of service area identifier for the applicable MBMS broadcast area. | +| Frequency | Identification of frequency if multi carrier support is provided | +| SDP information (NOTE 1) | SDP with IP multicast address and port number used for V2X communication via MBMS. Depending on the V2X application, the V2X message can be carried directly on top of UDP, without any streaming protocols. | +| NOTE 1: Typical V2X application does not require Codec information in the SDP information. | | + +#### 4.4.7.3 User Service Description for V2X Application Server Discovery (V2X Server USD) + +The V2X Server USD is used to configure the UE for receiving local V2X Application Server information when it is provided over MBMS, as specified in clause 5.4.1. + +The local Service Information contained in the broadcast is as described in clause 5.4.1.2, and should include similar information defined in clause 4.4.1.2.2. + +NOTE: Stage 3 defines the format of the local Service information. + +**Table 4.4.7.3-1: Information for V2X Server USD** + +| Information element | Description | +|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| TMGI | TMGI information | +| List of service area identifier | A list of service area identifier for the applicable MBMS broadcast area. | +| Frequency | Identification of frequency if multi carrier support is provided | +| SDP information | SDP with IP multicast address and port number used for V2X Application Server discovery via MBMS.
The content of the message carries the local Service Information and should include following information:
- Mapping of the V2X services, e.g. PSIDs, ITS-AIDs or AIDs of the V2X application of a PSID, ITS-AID and AID to V2X Application Server address (consisting of IP address/FQDN and TCP or UDP port) for unicast, and V2X USD for V2X communication via MBMS. | + +### 4.4.8 Support for V2X communication for UEs in limited service state + +For UE in limited service state, only V2X communication over PC5 is allowed. + +UEs that are authorized to use V2X communication over PC5 reference point shall be able to use V2X communication over PC5 reference point when in limited service state following the principles defined in clause 4.4.1.1.3 for V2X communication over PC5 reference point when the UE enters in limited service state: + +- because it cannot find a suitable cell of the selected PLMN as described in TS 23.122 [23] or +- as the result of receiving one of the following reject reasons defined in TS 23.122 [23]: + - a "PLMN not allowed" response to a registration request or; + - a "GPRS not allowed" response to a registration request + +A UE in limited service state shall only use the radio resources and procedure available in ECM-IDLE mode for V2X communication over PC5 reference point, for details see TS 36.300 [10]. + +UEs shall not use V2X communication over PC5 reference point using the "operator-managed" radio resources, as specified in clause 4.4.1.1.2, if the UE has entered in limited service state due to all other situations (e.g. no SIM in the MS, an "illegal MS" or "illegal ME" response to a registration request, or an "IMSI unknown in HLR" response to a registration request) defined in TS 23.122 [23], where the UE is unable to obtain normal service from a PLMN. The UEs may use V2X communication over PC5 reference point using the "non-operator-managed" radio resources, as specified in clause 4.4.1.1.2, according to the principles defined in clause 4.4.1.1.3. + +### 4.4.9 Charging support for V2X communication + +#### 4.4.9.1 Charging support for V2X communication over PC5 reference point + +For V2X communication over PC5, the mechanism defined in TS 32.277 [18] for ProSe Direct Communication can be reused for charging support. No enhancement to charging support for V2X communication over PC5 is specified in this Release. + +#### 4.4.9.2 Charging support for V2X communication over LTE-Uu reference point + +For V2X communication over LTE-Uu, there are unicast traffic and/or MBMS based broadcast traffic. + +For unicast V2X communication, charging is provided with the existing unicast communication mechanism as specified in TS 32.251 [20] where applicable. + +For MBMS based broadcast traffic, charging is provided with the existing mechanism as specified in TS 32.273 [21] where applicable. + +No enhancement to charging support for V2X communication over LTE-Uu is specified in this Release. + +### 4.4.10 Security and privacy protection support for V2X communication + +The security for the V3 and PC5 reference points is provided with mechanisms defined in TS 33.185 [25]. + +The security and privacy protection for the PC5 based V2X communication is provided by application layer schemes developed in other SDOs. In addition, the V2X layer also provides an additional mechanism to change Layer-2 ID and source IP address to protect privacy, as described in clause 4.5.1. + +The security of LTE-Uu based V2X communication reuses existing EPS security. No privacy enhancement for V2X communication over LTE-Uu is specified for this release. + +Details of security and privacy protection mechanisms for V2X communication over PC5 or LTE-Uu reference points are defined in TS 33.185 [25]. + +## 4.5 Identifiers + +### 4.5.1 Identifiers for V2X communication over PC5 reference point + +Each UE has a Layer-2 ID for the V2X communication over PC5 reference point, which is included in the source Layer-2 ID field of every frame that it sends on the layer-2 link. The UE self-assigns the Layer-2 ID for the V2X communication over PC5 reference point. + +When IP based V2X messages are supported, the UE auto-configures a link local IPv6 address to be used as the source IP address, as defined in clause 4.5.3 of TS 23.303 [5]. The UE may use the auto-configured link local IP address for V2X communication over PC5 reference point without sending Neighbor Solicitation and Neighbor Advertisement message for Duplicate Address Detection. + +If the UE has an active V2X application that requires privacy support in the current Geographical Area, as identified by configuration described in clause 4.4.1.1.2, in order to ensure that a source UE (e.g. vehicle) cannot be tracked or identified by any other UEs (e.g. vehicles) beyond a certain short time-period required by the application, the source Layer-2 ID must be changed over time and randomized. For IP based V2X communication over PC5 reference point, the source IP address must be also changed over time and randomized. The change of the identifiers of a source UE must be synchronized across layers used for PC5, e.g. when application layer identifier changes, the source Layer-2 ID and the source IP address need to be changed. + +The UE is configured with the destination Layer-2 ID(s) to be used for V2X services. The Layer-2 ID for a V2X message is selected based on the configuration as described in clause 4.4.1.1. + +# --- 5 Functional description and information flows + +## 5.1 Control and user plane stacks + +### 5.1.1 User plane for PC5 reference point supporting V2X services + +The PC5-U stack as defined in clause 5.1.2.1 of TS 23.303 [5] is used for the V2X communication over PC5 reference point. IP and Non-IP PDCP SDU types are supported for the V2X communication over PC5. + +For IP PDCP SDU type, only IPv6 is supported. The IP address allocation and configuration are as defined in clause 4.5.1. + +The Non-IP PDCP SDU contains a Non-IP Type header, which indicates the V2X message family used by the application layer, e.g. IEEE 1609 family's WSMP [13], ISO defined FNTP [14], CCSA defined DSMP [32], etc. + +NOTE: The Non-IP Type header and allowed values are defined in TS 24.386 [27]. + +## 5.2 Service authorization and update for V2X communications + +### 5.2.1 Service authorization procedures + +The service authorization procedures as specified in clause 5.2.1 of TS 23.303 [5] are reused for the authorization of a UE for V2X communications, with the V2X Control Functions in the corresponding PLMNs acting as the ProSe Functions. + +### 5.2.2 Service authorization update procedures + +The service authorization update procedures as specified in clause 5.2.2 of TS 23.303 [5] are reused for the updating of service authorization information in the UE. + +## 5.3 Procedure for V2X communication over PC5 reference point + +To perform V2X communication over PC5 reference point, the UE is configured with the related information as described in clause 4.4.1.1. + +The procedure for one-to-many ProSe Direct Communication transmission described in clause 5.4.2 of TS 23.303 [5] is applied to V2X communication over PC5 reference point with following differences: + +- The source Layer-2 ID is set to the Layer-2 ID described in clause 4.5.1. +- A UE shall be configured with a set of Layer-2 ID corresponding to different type of services. +- A UE shall be configured with the mapping of services types to Tx Profiles as described in clause 4.4.1.1.2, and selects a Tx Profile to use based on the upper layer provided service type (e.g. PSID/ITS-AID/AID). + +The procedure for one-to-many ProSe Direct Communication reception described in clause 5.4.3 of TS 23.303 [5] is applied to V2X communication over PC5 reference point. + +## 5.4 Procedure for V2X communication over LTE-Uu reference point + +### 5.4.1 V2X Application Server discovery using MBMS + +#### 5.4.1.1 General + +This procedure is applicable for local V2X Application Server discovery if supported by the network. It may be used by the UE only when it is configured with the information to receive V2X Application Server information via MBMS, as specified in clause 4.4.1.2.2. + +#### 5.4.1.2 Procedures for receiving V2X Application Server information via MBMS + +![Sequence diagram illustrating V2X Application Server discovery using broadcast. The diagram shows four main entities: UE (any PLMN), Serving PLMN, DNS Server, and V2X Application Server. A double-headed arrow at the top indicates the 'Serving PLMN' scope. The sequence of steps is: 1. UE attaches to Serving PLMN; 2. UE receives local Service Info via MBMS from Serving PLMN; 3. UE resolves local V2X Application Server address by querying the DNS Server; 4. UE establishes a service connection with the V2X Application Server. Steps 3 and 4 are enclosed in dashed boxes.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) + +``` + +sequenceDiagram + participant UE as UE (any PLMN) + participant Serving PLMN + participant DNS Server + participant V2X Application Server + + Note over UE, V2X Application Server: Serving PLMN + + UE->>Serving PLMN: 1. Attach to serving PLMN + Serving PLMN-->>UE: 2. Receive local Service Info via MBMS + Note right of UE: 3. Resolve local V2X Application Server address + UE->>DNS Server: + DNS Server-->>UE: + Note right of UE: 4. Establish service connection with V2X Application Server + UE->>V2X Application Server: + V2X Application Server-->>UE: + +``` + +Sequence diagram illustrating V2X Application Server discovery using broadcast. The diagram shows four main entities: UE (any PLMN), Serving PLMN, DNS Server, and V2X Application Server. A double-headed arrow at the top indicates the 'Serving PLMN' scope. The sequence of steps is: 1. UE attaches to Serving PLMN; 2. UE receives local Service Info via MBMS from Serving PLMN; 3. UE resolves local V2X Application Server address by querying the DNS Server; 4. UE establishes a service connection with the V2X Application Server. Steps 3 and 4 are enclosed in dashed boxes. + +**Figure 5.4.1.2-1: V2X Application Server discovery using broadcast** + +1. When a UE desires V2X communications via LTE-Uu, it attaches to the serving PLMN if it has not done so. + 2. If the UE has configuration for receiving V2X Application Server information via MBMS, as specified in clause 4.4.1.2.2, it receives the local Service Information from the corresponding broadcast traffic channel. The local Service Information includes the address information of the local V2X Application Servers, e.g. the FQDNs of the servers. In addition, the local Service Information may include the V2X USD for the corresponding V2X Application Servers, if MBMS downlink is to be used. +- NOTE: The UE can be in MBMS receive only mode for obtaining the local Service Information. +3. Based on the information received from step 2, the UE obtains the local V2X Application Server address, e.g. via a query of the DNS with the received FQDN. + 4. The UE may establish connection with the V2X Application Server for the service, e.g. obtaining the V2X USD if it is not provided in step 2 to allow the UE to receive V2X messages over MBMS. + +### 5.4.2 Procedure for V2X communication with MBMS + +#### 5.4.2.1 MBMS service area mapping + +##### 5.4.2.1.1 General + +MBMS service areas for V2X services may be configured at the V2X Application Server. Such service areas are not expected to change frequently. V2X Application Server performs the following procedures for managing the MBMS sessions: + +- MBMS bearer activation/deactivation procedures specified in TS 23.468 [7] and clause 5.4.2.2 are used for managing MBMS sessions. V2X Application Server acting as the GCS AS uses the configured MBMS Service Area Identities (SAIs) and/or list of Cell IDs (ECGIs) of the target broadcast area for such procedures. + +- If the UE provides its geographic location or Cell ID information over V1 reference point, the V2X Application Server may use such information for the determination of the target broadcast area (e.g. MBMS SAI(s) and/or ECGI(s)) for the downlink broadcast of V2X messages. +- From such procedures, the V2X Application Server knows which TMGI/Flow-ID (i.e. MBMS session) is serving a geographical area. Hence, V2X Application Server forwards a V2X message to the appropriate MBMS session. + +NOTE: V2X messages may be broadcasted to an area larger than needed. The V2X application in the UE discards the messages that are not relevant to the UE based on procedures internal to the UE. + +##### 5.4.2.1.2 Functional Description + +V2X Application Server shall map UE provided location information to a form that is understood by the 3GPP MBMS system, e.g. MBMS SAI(s) and/or ECGI(s). + +A UE may include its geographic location information in the V2X message, e.g. as defined ETSI ITS (ETSI TS 102 637-2 [16], ETSI TS 102 637-3 [17]) or other ITS specifications. The V2X Application Server shall provide the MBMS broadcast area parameters to BM-SC and BM-SC process the MBMS broadcast area parameters as defined in TS 23.468 [7]. + +Additionally, a UE may provide its geographic location information in the V2X message and Cell ID (i.e. ECGI) information in the signalling to the V2X Application Server. The V2X Application Server may use such information for determining the target MBMS broadcast area as defined in TS 23.468 [7]. + +The BM-SC derives the MBMS Service Area and the SAI list for the availability information from Geographical Area as provided by the V2X Application Server as defined in TS 26.348 [29] when using xMB interface. + +NOTE: As specified in TS 23.246 [8], the BM-SC provides both the MBMS SAI(s) and Cell ID(s) towards the downlink signalling path towards the RAN nodes. + +#### 5.4.2.2 Local MBMS based MBMS data delivery + +For MBMS latency improvements, the V2X Application Server may provide the BM-SC with L.MBMS (Local MBMS) information, i.e., M1 interface information including transport network IP Multicast Address, IP address of multicast source and C-TEID, as well as MB2-U interface information including IP address and UDP port number for the user plane. This L.MBMS information is preconfigured in the V2X Application Server. + +Figure 5.4.2.2-1 shows the procedure that the L.MBMS information (both M1 interface information and MB2-U interface information) is provided from the V2X Application Server to the BM-SC, and in turn M1 interface information is provided from BM-SC to MBMS-GW when activating MBMS bearer and V2X message is delivered per the provided L.MBMS information. + +![Sequence diagram for L.MBMS based MBMS data delivery. Lifelines: E-UTRAN, MME, MBMS-GW, BM-SC, V2X Application Server. The sequence starts with preconfigured L.MBMS information in the V2X server, followed by TMGI allocation, bearer activation, session start requests/responses, and finally the V2X message delivery via MB2-U.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant V2X as V2X Application Server + participant BM-SC + participant MBMS-GW + participant MME + participant E-UTRAN + + Note right of V2X: 0. L.MBMS information is preconfigured + V2X->>BM-SC: 1. Allocate TMGI Request/Response + V2X->>BM-SC: 2. Activate MBMS Bearer Request (L.MBMS information) + BM-SC->>V2X: 3. Activate MBMS Bearer Response (MB2-U address,...) + BM-SC->>MBMS-GW: 4. Session Start Request (M1 information, ...) + MBMS-GW->>BM-SC: 5. Session Start Response + MBMS-GW->>MME: 6. Session Start Request + MME->>E-UTRAN: 7. Session Start Request + E-UTRAN->>MME: 8. Session Start Response + MME->>MBMS-GW: 9. Session Start Response + Note left of E-UTRAN: 10. IP Multicast join + Note right of V2X: 11. Send V2X message via MB2-U + +``` + +Sequence diagram for L.MBMS based MBMS data delivery. Lifelines: E-UTRAN, MME, MBMS-GW, BM-SC, V2X Application Server. The sequence starts with preconfigured L.MBMS information in the V2X server, followed by TMGI allocation, bearer activation, session start requests/responses, and finally the V2X message delivery via MB2-U. + +**Figure 5.4.2.2-1: L.MBMS based MBMS data delivery** + +0. The L.MBMS information is preconfigured in the V2X Application Server. +1. The V2X Application Server performs the TMGI Allocation procedure as specified in TS 23.468 [7]. +- 2-3. Steps 2 and 3 are similar to in clause 5.1.2.3.2 of TS 23.468 [7], with the following differences: + - In step 2, the V2X Application Server includes L.MBMS information in an Activate MBMS Bearer Request message. The L.MBMS information is preconfigured in the V2X Application Server. + - In step 3, if the BM-SC uses the L.MBMS information from the V2X Application Server then it copies the MB2-U interface information received from step 2 as MB2-U address (i.e., "BM-SC IP address and port number for the user-plane" information element) in the Activate MBMS Bearer Response message to the V2X Application Server. +- 4-5. Steps 4 and 5 are similar to in clause 8.3.2 of TS 23.246 [8], with the following differences: + - In step 4, the BM-SC includes the M1 interface information of the L.MBMS information received from the V2X Application Server in the Session Start Request message if the BM-SC decided to use the L.MBMS information. + - In steps 4 and 5, if the MBMS-GW uses the M1 interface information received from the BM-SC then it skips the allocation procedure for IP multicast distribution, e.g. allocate an IP multicast address. +- 6-10. Same to steps 3 to 6 and step 8 in clause 8.3.2 of TS 23.246 [8]. +11. The V2X Application Server sends V2X message to the L.MBMS's IP address via MB2-U. + +If BM-SC does not use L.MBMS information received from V2X Application Server, then BM-SC allocates the addresses related to MB2-U interface as currently specified in TS 23.468 [7]. V2X Application Server is aware that the BM-SC is not using L.MBMS information when the MB2-U address received from step 3 is different than the one in the L.MBMS information provided in step 2. In this case, V2X Application Server shall continue with procedure as defined in TS 23.468 [7]. + +The L.MBMS support using xMB interface requires same information to be provided via xMB-C using Service Management Procedures as defined in TS 26.348 [29]. For MBMS latency improvements, the V2X Application Server may provide the BM-SC with L.MBMS (Local MBMS) information, i.e., M1 interface information including transport network IP Multicast Address, IP address of multicast source and C-TEID, as well as xMB-U interface information + +including IP address and UDP port number for the user plane. This L.MBMS information is preconfigured in the V2X Application Server. + +## 5.5 V2X impacts to EPC procedures + +### 5.5.1 E-UTRAN attach procedure for UE + +The E-UTRAN attach procedure for UE is performed as defined in TS 23.401 [6] with the following additions: + +- The UE includes the V2X capability indication as part of the "UE Network Capability" in the Attach Request message. The MME stores this information for V2X operation. The V2X capability can indicate whether the UE is capable of supporting V2X communication over PC5 reference point. +- If the UE indicated V2X capability, and the UE is authorized to use V2X communication over PC5 reference point based on the subscription data, then the MME shall include a "V2X services authorized" indication in the S1-AP Initial Context Setup Request, indicating the UE is authorized to use V2X communication over PC5 reference point as Vehicle UE, Pedestrian UE or both. +- The MME obtains the UE-PC5-AMBR from the HSS as part of the subscription data and includes it in the S1-AP Initial Context Setup Request to the eNodeB, which use it in resource management of UE's PC5 transmission for V2X services in network scheduled mode. + +### 5.5.2 Service Request procedures for UE + +The Service Request procedures for UE are performed as defined in TS 23.401 [6] with the following additions: + +- If the UE is V2X capable, and the UE is authorized to use V2X communication over PC5 reference point based on the subscription data, then the MME shall include a "V2X services authorized" indication in the S1-AP Initial Context Setup Request, indicating the UE is authorized to use V2X communication over PC5 reference point as Vehicle UE, Pedestrian UE or both. +- The MME includes the UE-PC5-AMBR in the S1-AP Initial Context Setup Request to the eNodeB which stores it as part of the UE context and may use it in resource management of UE's PC5 transmission for V2X services in network scheduled mode. + +### 5.5.3 S1 Handover procedures for UE + +The Intra-E-UTRAN S1-based handover or the Inter-RAT to E-UTRAN handover procedures for UE are performed as defined in TS 23.401 [6] with the following additions: + +- If the UE is V2X capable, and the UE is authorized to use V2X communication over PC5 reference point based on the subscription data, then the target MME shall send the "V2X services authorized" indication and UE-PC5-AMBR to the target eNodeB as follows: + - For the intra MME handover, the "V2X services authorized" indication and UE-PC5-AMBR are included in the S1-AP Handover Request message. If after the handover procedure, the "V2X services authorized" indication or the UE-PC5-AMBR or both are changed, the updated "V2X services authorized" indication or the updated UE-PC5-AMBR or both are included in the S1-AP UE Context Modification Request message sent to the target eNodeB. + - For the inter MME handover or Inter-RAT handover to E-UTRAN, the "V2X services authorized" indication and UE-PC5-AMBR are included in the S1-AP UE Context Modification Request message sent to the target eNodeB after the handover procedure. + +The "V2X services authorized" indication sent to target eNodeB denotes the UE is authorized to use V2X communication over PC5 reference point as Vehicle UE, Pedestrian UE or both. + +### 5.5.4 X2 Handover procedures for UE + +For the X2-based handover, the "V2X services authorized" indication and the UE-PC5-AMBR are sent to target eNodeB as follows: + +- If the source eNodeB is V2X-enabled and the "V2X services authorized" indication is included in the UE context, then the source eNodeB shall include a "V2X services authorized" indication and UE-PC5-AMBR in the X2-AP Handover Request message to the target eNodeB. +- If the UE is V2X capable, and the UE is authorized to use V2X communication over PC5 reference point based on the subscription data, then the MME shall send the "V2X services authorized" indication and the UE-PC5-AMBR to the target eNodeB in the Path Switch Request Acknowledge message. If, after the handover procedure, the "V2X services authorized" indication or the UE-PC5-AMBR or both are changed, the updated "V2X services authorized" indication or the updated UE-PC5-AMBR or both are included in the S1-AP UE Context Modification Request message sent to the target eNodeB. + +The "V2X services authorized" indication sent to target eNodeB denotes the UE is authorized to use V2X communication over PC5 reference point as Vehicle UE, Pedestrian UE or both. + +The UE-PC5-AMBR is sent to target eNodeB for the resources management of UE's PC5 transmission in V2X communication. + +### 5.5.5 Tracking Area Update procedure for UE + +The Tracking Area Update procedures for UE are performed as defined in TS 23.401 [6] with the following additions: + +- The UE includes the V2X capability indication as part of the "UE Network Capability" in the Tracking Area Update Request message. The MME stores this information for the V2X operation. +- If the MME determines to re-establish the radio and S1 bearers for all active EPS bearer contexts due to the "active" flag included in the Tracking Area Update Request message or the pending downlink data or signalling, the UE is V2X capable, and the UE is authorized to use V2X communication over PC5 reference point based on the subscription data, then the MME shall include a "V2X services authorized" indication and UE-PC5-AMBR in the S1-AP Initial Context Setup Request. The "V2X services authorized" indication sent to eNodeB denotes the UE is authorized to use V2X communication over PC5 reference point as Vehicle UE, Pedestrian UE or both. + +### 5.5.6 Insert Subscriber Data procedure for UE + +The Insert Subscriber Data procedures for UE are performed as defined in TS 23.401 [6] with the following additions: + +- If the "V2X services authorized" indication or the UE-PC5-AMBR or both need to be changed due to the changed subscription data and the S1 bearer is established, then the MME shall notify the eNodeB the updated "V2X services authorized" indication or the UE-PC5-AMBR or both via the S1-AP UE Context Modification Request message. + +### 5.5.7 Delete Subscriber Data procedure for UE + +Delete Subscriber Data procedure for UE is performed as defined in TS 29.272 [15] with the same additions as in clause 5.5.6. + +### 5.5.8 V2X capability indication and V2X related information per PC5 RAT + +A UE may support multiple PC5 RATs (i.e. LTE PC5 and NR PC5). For such UE, the V2X capability indication for NR PC5 and V2X related information (i.e. "V2X services authorized" indication and UE-PC5-AMBR) described in clauses 5.5.1 to 5.5.7 is per PC5 RAT. + +### 5.5.9 Support of V2X communication over NR PC5 reference point + +To support V2X communication over NR PC5 reference point, the EPC procedures described in clauses 5.5.1 to 5.5.7 are applied with the following differences: + +- The PC5 QoS parameters may be included in the S1-AP Initial Context Setup Request, S1-AP Handover Request, S1-AP UE Context Modification Request, X2-AP Handover Request, and Path Switch Request Acknowledge messages. + +NOTE: Non-UE specific PC5 QoS parameters, e.g. default PC5 QoS parameters, can also be locally configured in E-UTRAN. How such configuration is performed is out of scope of this specification. + +# Annex A (informative): Road Side Unit (RSU) implementation options + +This Annex presents examples how RSU can be implemented. With reference to the architectural reference models defined in clause 4.2, the RSU can receive V2X messages via SGi, PC5 or LTE-Uu interface depending on implementation option. + +Figure A-1 shows a UE-type RSU, which combines a UE with the V2X application logic. + +![Diagram of UE-type RSU implementation option](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) + +The diagram illustrates a UE-type RSU. On the left, a 'V2X Application' oval is connected to a 'UE A (Vehicle)' rectangle. On the right, a dashed box labeled 'RSU' contains a 'V2X Application' oval connected to a 'UE B (Stationary)' rectangle. A horizontal dashed line labeled 'V5' connects the two 'V2X Application' ovals. A horizontal solid line labeled 'PC5' connects the 'UE A (Vehicle)' rectangle and the 'UE B (Stationary)' rectangle. + +Diagram of UE-type RSU implementation option + +**Figure A-1: RSU includes a UE and the V2X application logic** + +Figure A-2 shows one example of eNB-type RSUs. In this example, the RSU comprises an eNB, a collocated L-GW, and a V2X Application Server. + +![Diagram of eNB-type RSU implementation option](1c9a5a80a4ed18fdfda1c8ae915966bf_img.jpg) + +The diagram illustrates an eNB-type RSU. On the left, a 'V2X Application' oval is connected to a 'UE A (Vehicle)' rectangle. On the right, a dashed box labeled 'RSU' contains three stacked components: a 'V2X Application Server' oval at the top, an 'L-GW' rectangle in the middle, and an 'eNB' rectangle at the bottom. A horizontal dashed line labeled 'V1' connects the 'V2X Application' oval to the 'V2X Application Server' oval. A horizontal solid line labeled 'LTE-Uu' connects the 'UE A (Vehicle)' rectangle to the 'eNB' rectangle. + +Diagram of eNB-type RSU implementation option + +**Figure A-2: RSU includes an eNB, L-GW and a V2X Application Server** + +# Annex B (informative): Localized MBMS deployment options + +## B.1 General Description + +In current MBMS system, the BM-SC, MBMS-GW and MME are located in the Core Network. The backhaul delay between the BM-SC and the eNB is non-negligible when calculating the end-to-end delay, especially when MBMS is used to delivery downlink V2X messages in the V2X system. To minimize the latency, possible deployment can consider the following options: + +- To move the MBMS CN functions (e.g. BM-SC, MBMS-GW) closer to the eNB. +- To move the user plane of MBMS CN functions (BM-SC, MBMS-GW) closer to the eNB. + +These options are illustrated in clause B.2 and clause B.3. The list of deployment options is not exhaustive and that they are shown for illustration purposes only. + +If the V2X Application Server utilizes xMB interface, the options B.2 and B.3 replace MB2-C and MB2-U with xMB-C and xMB-U respectively. + +## B.2 Option of localized MBMS CN functions + +In this case BM-SC, and MBMS-GW are located close to the eNB. This option is shown in Figure B.2-1. + +![Figure B.2-1: Localized MBMS CN functions. This block diagram shows the network architecture for localized MBMS. On the left, a 'Vehicle UE' is connected to an 'E-UTRAN' via an 'LTE-Uu' interface. The 'E-UTRAN' is connected to an 'MME' via an 'M1' interface and to an 'MBMS GW' via an 'M3' interface. The 'MME' is connected to an 'S-GW' via an 'S11' interface and to a 'P-GW' via an 'S5' interface. The 'S-GW' is connected to the 'P-GW' via an 'S1-U' interface. The 'P-GW' is connected to a 'V2X Application Server' via an 'SGi' interface. The 'MBMS GW' is connected to the 'BM-SC' via 'SGmb' and 'SGi-mb' interfaces. The 'BM-SC' is connected to the 'V2X Application Server' via 'MB2-C' and 'MB2-U' interfaces. The 'V2X App' is shown as a circle connected to the 'Vehicle UE'.](f324fbc5d5af1e4da9cd932389f0064c_img.jpg) + +Figure B.2-1: Localized MBMS CN functions. This block diagram shows the network architecture for localized MBMS. On the left, a 'Vehicle UE' is connected to an 'E-UTRAN' via an 'LTE-Uu' interface. The 'E-UTRAN' is connected to an 'MME' via an 'M1' interface and to an 'MBMS GW' via an 'M3' interface. The 'MME' is connected to an 'S-GW' via an 'S11' interface and to a 'P-GW' via an 'S5' interface. The 'S-GW' is connected to the 'P-GW' via an 'S1-U' interface. The 'P-GW' is connected to a 'V2X Application Server' via an 'SGi' interface. The 'MBMS GW' is connected to the 'BM-SC' via 'SGmb' and 'SGi-mb' interfaces. The 'BM-SC' is connected to the 'V2X Application Server' via 'MB2-C' and 'MB2-U' interfaces. The 'V2X App' is shown as a circle connected to the 'Vehicle UE'. + +Figure B.2-1: Localized MBMS CN functions + +## B.3 Option of localized user plane of MBMS CN functions + +In this case user plane of MBMS CN functions (BM-SC and MBMS-GW) is located close to the eNB. This option is shown in Figure B.3-1. + +![Figure B.3-1: Localized user plane of MBMS CN functions. This block diagram illustrates the network architecture for localized MBMS. At the top, a standard core network path consists of an MME connected to an S-GW, which is connected to a P-GW, which in turn connects to the SGi interface. The MME is connected to the E-UTRAN via the S1-U interface. The S-GW is connected to the P-GW via the S5 interface. The P-GW is connected to the SGi interface. Below the core network, a 'Control plane of MBMS CN functions' block contains two sub-components: 'Control plane of MBMS GW' and 'Control plane of BM-SC', which are connected to each other via the SGmb interface. This control plane block is connected to the MME via the S1-U and Sm interfaces, and to the E-UTRAN via the M3 interface. The 'User plane of MBMS CN functions' block is connected to the E-UTRAN via the M1 interface and to a 'V2X Application Server' via the MB2-U interface. The V2X Application Server is also connected to the SGi interface via the MB2-C interface. On the left, a 'Vehicle UE' is connected to the E-UTRAN via the LTE-Uu interface. The Vehicle UE is associated with a 'V2X App'.](a4b963a07cc368283154762c4b156fe7_img.jpg) + +Figure B.3-1: Localized user plane of MBMS CN functions. This block diagram illustrates the network architecture for localized MBMS. At the top, a standard core network path consists of an MME connected to an S-GW, which is connected to a P-GW, which in turn connects to the SGi interface. The MME is connected to the E-UTRAN via the S1-U interface. The S-GW is connected to the P-GW via the S5 interface. The P-GW is connected to the SGi interface. Below the core network, a 'Control plane of MBMS CN functions' block contains two sub-components: 'Control plane of MBMS GW' and 'Control plane of BM-SC', which are connected to each other via the SGmb interface. This control plane block is connected to the MME via the S1-U and Sm interfaces, and to the E-UTRAN via the M3 interface. The 'User plane of MBMS CN functions' block is connected to the E-UTRAN via the M1 interface and to a 'V2X Application Server' via the MB2-U interface. The V2X Application Server is also connected to the SGi interface via the MB2-C interface. On the left, a 'Vehicle UE' is connected to the E-UTRAN via the LTE-Uu interface. The Vehicle UE is associated with a 'V2X App'. + +**Figure B.3-1: Localized user plane of MBMS CN functions** + +The user plane of MBMS CN functions can implement the following user plane functionalities: + +- Receive user data from V2X Application Server over MB2-U. +- IP multicast distribution of MBMS user plane data to E-UTRAN (M1 reference point). +- Data synchronization (as for the BM-SC in legacy MBMS mechanisms). +- If used, apply favourable error resilient schemes, e.g. specialized MBMS codecs or Forward Error Correction schemes. +- If used, MBMS data encryption. + +The procedure for Local MBMS based MBMS data delivery described in clause 5.4.2.2 makes this type of deployment option possible to improve V2X latency. + +The separation of control and user plane functions in this option is for illustration only. + +# Annex C (informative): Example hybrid operation modes for V2X communication over PC5 and LTE-Uu + +## C.1 General + +This Annex presents examples on how two operation modes for V2X communication, i.e. over the PC5 and over LTE-Uu, can be used in a hybrid manner. + +## C.2 PC5 based V2X communication with MBMS reception + +In this operation mode, a UE always transmits the V2X messages via PC5. The UE receives V2X messages via PC5 and via MBMS as well. + +A stationary infrastructure entity acting as a UE, e.g. an RSU, receives V2X messages via PC5, and forwards the application layer processed V2X messages to a V2X Application Server via V1 interface, e.g. using a PDN connection over LTE-Uu or other type of connection (for example fixed). The V2X messages processed by the V2X Application Server can be distributed to UEs via the MBMS system as required. + +In this manner, a UE can directly receive V2V messages from other UEs in close proximity. Additionally, in this operation mode, the mobile network provides information from an extended range and satisfies the needs of soft safety (e.g. situational awareness at range) or enables more advanced driving assistance applications. This combined sources of information are especially useful in high density use cases, where the UE may not be able to reliably receive V2X messages directly from distant UEs over PC5. + +## C.3 Simultaneous LTE-Uu based and PC5 based V2X communication without MBMS + +In this operation mode, UEs communicate with other UEs that are in proximity, including with UE-type RSUs, via PC5 for both the transmission and reception of V2X messages. The UE-type RSUs can communicate with the V2X Application Servers in the mobile network, e.g. over LTE-Uu, as needed, for managing the communication of V2X messages beyond the direct PC5 communication range. With such hybrid use of PC5 and LTE-Uu based V2X communication, MBMS broadcast on the downlink is not needed. + +![Diagram illustrating V2X message transmission and reception using UE-type RSU via LTE-Uu and PC5. The diagram shows a V2X Application Server connected to an EPC cloud. Two RSUs (stationary UEs) are connected to the EPC via LTE-Uu links. UEs (User Equipment) are shown communicating with the RSUs via PC5 links. Arrows indicate the flow of V2X messages: from UEs to RSUs over PC5, from RSUs to the EPC over LTE-Uu, from the EPC to the RSUs over LTE-Uu, and from RSUs to UEs over PC5.](4b587081b669e7c6695b0e5db5ea7f6d_img.jpg) + +The diagram illustrates a network architecture for V2X communication. At the top center is a 'V2X Application Server' connected to a cloud labeled 'EPC'. Below the EPC are two 'RSU (stationary UE)' units. Each RSU is connected to the EPC via a bidirectional arrow labeled 'V2X message over LTE-Uu'. On the left, two UEs (represented by a car and a smartphone icon) are shown sending 'V2X message over PC5' to the left RSU. On the right, the right RSU is shown sending 'V2X message over PC5' to two UEs (car and smartphone icon). The UEs are also shown with their own PC5 communication links between them. + +Diagram illustrating V2X message transmission and reception using UE-type RSU via LTE-Uu and PC5. The diagram shows a V2X Application Server connected to an EPC cloud. Two RSUs (stationary UEs) are connected to the EPC via LTE-Uu links. UEs (User Equipment) are shown communicating with the RSUs via PC5 links. Arrows indicate the flow of V2X messages: from UEs to RSUs over PC5, from RSUs to the EPC over LTE-Uu, from the EPC to the RSUs over LTE-Uu, and from RSUs to UEs over PC5. + +Figure C.3-1: V2X message transmission and reception using UE-type RSU via LTE-Uu and PC5 + +Figure C.3-1 is a high level illustration of this operation mode. This operation mode consists of three components: + +- Stationary infrastructure entities acting as UEs, e.g. UE-type RSUs, are deployed to provide adequate coverage to vehicular traffic infrastructure. The UEs and the UE-type RSUs are configured or provisioned with information for V2X communication over PC5 as specified in clause 4.4.1. The UE-type RSUs may communicate with the V2X Application Servers. +- The UE-type RSUs receive V2X messages from other UEs via PC5. The V2X application of the RSU(s) decides if the messages need to be routed to the V2X Application Server(s) over LTE-Uu connection, e.g. when the target area is larger than its V2X communication range over PC5. The V2X Application Server(s) determines the target area and the size of the area where the V2X messages need to be distributed. The V2X Application Server may coordinate and communicate with other V2X Application Servers for the determination of the target area and distribution of V2X messages in the target area. +- V2X Application Server(s) send V2X messages downlink to the RSUs in the target distribution area, e.g. over LTE-Uu. The RSUs broadcast the received V2X messages using V2X communication over PC5. UEs within the region receive the RSU broadcasted V2X messages over PC5. + +In this manner, a UE, e.g. vehicle UE only needs to operate in the operation mode of V2X communication over PC5, for V2V/V2P services. Only the UEs implemented as RSUs operate in the hybrid mode of simultaneous V2X communication over PC5 and LTE-Uu. Such combination of PC5 based and LTE-Uu based V2X communications is also useful in use cases where the UE may not be able to receive V2X messages directly from distant UEs via PC5. In addition, the UE-type RSUs can use SIPTO connection for the communication with local V2X Servers to reduce latency. + +# Annex D (informative): V2X Message Distribution Server deployment option + +## D.1 General Description + +In the case of non-session based V2X services (i.e. Road Status Notification), it is possible that a single V2X message needs to be delivered to multiple locally relevant V2X Application Servers. In order to provide network support for the distribution of these V2X messages to multiple V2X Application Servers, a possible deployment option includes a V2X Message Distribution Server behind the L/PGW as illustrated in Figure D.1-1. It is configured to distinguish whether a V2X message needs to be delivered to multiple V2X Application Servers and send them accordingly. + +UEs discover and send V2X messages to these network deployed distribution servers in the same way as to V2X Application Servers. From the UE perspective, it is communicating with a V2X Application Server and is not aware whether any of the V2X messages are further distributed onward to other servers. + +NOTE: The V2X Message Distribution Server is used for illustrative purpose and not further described in any 3GPP specification. + +![Diagram illustrating the V2X message distribution server deployment option. Two User Equipment (UE) units are shown, each connected to an eNB, which is connected to an L/PGW. Each L/PGW is connected to a V2X Message Distribution Server. These servers are connected to 3rd Party V2X Service Providers, which are organized into two areas. Area #1 contains V2X Application Server #1 and V2X Application Server #2. Area #2 contains V2X Application Server #3 and V2X Application Server #4.](1ad662a678c4f002de911d403f00de8e_img.jpg) + +``` +graph LR; UE1[UE] --> eNB1[eNB]; eNB1 --> L/PGW1[L/PGW]; L/PGW1 --> V2X_MDS1[V2X Message Distribution Server]; UE2[UE] --> eNB2[eNB]; eNB2 --> L/PGW2[L/PGW]; L/PGW2 --> V2X_MDS2[V2X Message Distribution Server]; V2X_MDS1 --> V2X_AS1[V2X Application Server #1]; V2X_MDS1 --> V2X_AS2[V2X Application Server #2]; V2X_MDS2 --> V2X_AS3[V2X Application Server #3]; V2X_MDS2 --> V2X_AS4[V2X Application Server #4]; subgraph Area1 [Area #1 relevant servers]; V2X_AS1; V2X_AS2; end; subgraph Area2 [Area #2 relevant servers]; V2X_AS3; V2X_AS4; end; +``` + +Diagram illustrating the V2X message distribution server deployment option. Two User Equipment (UE) units are shown, each connected to an eNB, which is connected to an L/PGW. Each L/PGW is connected to a V2X Message Distribution Server. These servers are connected to 3rd Party V2X Service Providers, which are organized into two areas. Area #1 contains V2X Application Server #1 and V2X Application Server #2. Area #2 contains V2X Application Server #3 and V2X Application Server #4. + +Figure D.1-1: V2X message distribution server deployment option + +# Annex E (informative): Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|------|-----|-----|--------------------------------------------------------------------------------------------------------------------------------------|---------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2016-09 | SP-73 | SP-160663 | - | - | - | Editorial clean up for presentation to TSG SA#73 for information. This version also presented to TSG SA#73 for approval in SP-160626 | 1.0.0 | +| 2016-09 | SP-73 | - | - | - | - | Editorial clean up for publication after TSG SA#73 Approval | 14.0.0 | +| 2016-12 | SP-74 | SP-160814 | 0001 | 2 | F | V2X message handling over LTE Uu | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0003 | 1 | B | Update of V2X impacts to EPC procedures | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0004 | 1 | B | Mapping between PPPP and latency for autonomous resources selection mode | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0005 | 2 | F | Update of Functional entities description | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0006 | 1 | B | Subscription to V2X services | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0007 | - | F | Clarification on MBMS for LTE-Uu based V2X architecture reference model | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0009 | 1 | F | Uplink distribution deployment option | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0010 | 1 | F | Clarification on location mapping at V2X Application Server | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0012 | 1 | F | Definition of the USD for Uu based V2X communication and V2X Application Server discovery | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0013 | 1 | F | Clarification of multiple TMGIs uses in overlapping areas | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0015 | 1 | F | V2X communication over PC5 is used for UEs in limited service state | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0016 | 2 | F | Resolve EN related to source IP change for IP based V2X communication over PC5 | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0017 | 1 | B | Charging support for V2X Communication | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0018 | 1 | B | Parameter pre-configuration and usage of the UE for V2X communication | 14.1.0 | +| 2016-12 | SP-74 | SP-160814 | 0020 | 1 | F | Procedure for V2 reference point | 14.1.0 | +| 2017-03 | SP-75 | SP-170045 | 0023 | 1 | F | Clarify relation of PPPP, PDB & priority | 14.2.0 | +| 2017-03 | SP-75 | SP-170045 | 0024 | 1 | C | Support for xMB for V2X application | 14.2.0 | +| 2017-03 | SP-75 | SP-170045 | 0025 | 1 | F | Clarify IP routing of V2X service over LTE Uu with PSID, ITS-AID | 14.2.0 | +| 2017-03 | SP-75 | SP-170045 | 0026 | 1 | C | Clarification for V2X communication over PC5 in limited service state | 14.2.0 | +| 2017-03 | SP-75 | SP-170045 | 0027 | 2 | C | Support of V2X communication over PC5 during IMS eCall | 14.2.0 | +| 2017-03 | SP-75 | SP-170045 | 0028 | 1 | F | Clarification for V2X charging | 14.2.0 | +| 2017-03 | SP-75 | SP-170045 | 0029 | 1 | B | Clarification for V2X Security | 14.2.0 | +| 2017-06 | SP-76 | SP-170364 | 0030 | 1 | F | Clarification for definition of "not served by E-UTRAN" | 14.3.0 | +| 2017-06 | SP-76 | SP-170364 | 0031 | 2 | F | Clarification on privacy requirements for V2X communication | 14.3.0 | +| 2017-06 | SP-76 | SP-170364 | 0032 | 2 | F | Mapping between service types and V2X frequencies | 14.3.0 | +| 2017-09 | SP-77 | SP-170722 | 0034 | 1 | F | Correction on radio resources | 14.4.0 | +| 2017-12 | SP-78 | SP-170917 | 0036 | 1 | F | Clarification to mapping between service types and V2X frequencies | 14.5.0 | +| 2018-03 | SP-79 | SP-180088 | 0039 | 1 | F | Clarification on PC5 parameters from V2X Application Server | 14.6.0 | +| 2018-03 | SP-79 | SP-180114 | 0037 | 1 | C | Support of Reliable transmission over PC5 using extended PPPP | 15.0.0 | +| 2018-06 | SP-80 | SP-180472 | 0042 | 1 | A | Optional Duplicate Address Detection for V2X Communication over PC5 | 15.1.0 | +| 2018-06 | SP-80 | SP-180473 | 0040 | 1 | F | Reliability for eV2X for LTE clarification | 15.1.0 | +| 2018-06 | SP-80 | SP-180473 | 0044 | 2 | F | Support of PC5 transmission mechanism selection using Tx Profile | 15.1.0 | +| 2018-12 | SP-82 | SP-181092 | 0045 | 1 | F | Tx profiles provisioning for PC5 | 15.2.0 | +| 2019-03 | SP-83 | SP-190152 | 0049 | 1 | A | Update reference for ITS-AID | 15.3.0 | +| 2019-03 | SP-83 | SP-190175 | 0047 | 1 | F | Change xMB reference | 16.0.0 | +| 2019-09 | SP-85 | SP-190615 | 0056 | 2 | B | NR PC5 QoS modelling and operations in EPC | 16.1.0 | +| 2019-12 | SP-86 | SP-191066 | 0052 | 5 | A | Support of Non UE detected Emergency session | 16.2.0 | +| 2019-12 | SP-86 | SP-191083 | 0057 | 1 | F | TCP support for non-IP V2X traffic over Uu | 16.2.0 | +| 2019-12 | SP-86 | SP-191083 | 0058 | 2 | F | EPC controlled NR PC5 operations | 16.2.0 | +| 2019-12 | SP-86 | SP-191083 | 0059 | 2 | F | Support of NR PC5 QoS under EPC | 16.2.0 | +| 2020-07 | SP-88E | SP-200434 | 0060 | - | F | Introduction of missing definition for Tx Profile | 16.3.0 | +| 2020-09 | SP-89E | SP-200682 | 0063 | 2 | F | Introducing new V2X service type | 16.4.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23333/04cfca33e3fc26513abe649d7474f733_img.jpg b/marked/Rel-16/23_series/23333/04cfca33e3fc26513abe649d7474f733_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2b2af68bda4ecb9980d85fcd74610de4bdceda81 --- /dev/null +++ b/marked/Rel-16/23_series/23333/04cfca33e3fc26513abe649d7474f733_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c784519fceba576ca0c4de8707314574440b71284e424364cda8bbb99fe3e1b +size 188907 diff --git a/marked/Rel-16/23_series/23333/19d7a7ce68d3e9036613910b761c4b24_img.jpg b/marked/Rel-16/23_series/23333/19d7a7ce68d3e9036613910b761c4b24_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..87d5e4ed935f0adea971847780b4b48882afe2c0 --- /dev/null +++ b/marked/Rel-16/23_series/23333/19d7a7ce68d3e9036613910b761c4b24_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dd717de906adddfe7c93a14e45365247392d20acba669918e1bf7f666df51fee +size 40516 diff --git a/marked/Rel-16/23_series/23333/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23333/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d1cc84249b30af344e8d6a448f862a071e4cc2b3 --- /dev/null +++ b/marked/Rel-16/23_series/23333/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:681b6b139f63176951ea1f20e937ef6ae5cb995afe1e21c8024d29fabc63a1f9 +size 53299 diff --git a/marked/Rel-16/23_series/23333/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-16/23_series/23333/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cec3672a237a85aa3d09c40660c03ffae101b32b --- /dev/null +++ b/marked/Rel-16/23_series/23333/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c8672c379610367d13b0c9e3572fe2d69009b7de5915f249a87ae1660ab8e932 +size 71823 diff --git a/marked/Rel-16/23_series/23333/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/23_series/23333/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8033e5b742feb36ef622fef43a0ae4f40a96c8e1 --- /dev/null +++ b/marked/Rel-16/23_series/23333/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2a49c1254b2fdd4095fce5bd21fd524f3d40924c3660ee383e8f591fb6282825 +size 16072 diff --git a/marked/Rel-16/23_series/23333/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23333/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ee53d8de2e44738cc52733806a2df9b2dc564c7f --- /dev/null +++ b/marked/Rel-16/23_series/23333/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:712041d919918ed36366b74bac25a0a4e849dc75a58c0500571c0bb159b6f39b +size 53463 diff --git a/marked/Rel-16/23_series/23333/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg b/marked/Rel-16/23_series/23333/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4ce6eae30478ed6c86e4a82bc7e9295a6347dfc8 --- /dev/null +++ b/marked/Rel-16/23_series/23333/8d325fc12b494e42c9ea7ed2a7f327a6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:547a74070db4118230e0f707af2ae0f4a4ab917c921d912d90154a3567b7a7ce +size 112751 diff --git a/marked/Rel-16/23_series/23333/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/marked/Rel-16/23_series/23333/9f6dec4d4e9fde40bce018861ef1278e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..994d25138666fe0c677caf114eac55f018a13343 --- /dev/null +++ b/marked/Rel-16/23_series/23333/9f6dec4d4e9fde40bce018861ef1278e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90452dbd8a60673582c20a3b7f298e0db7018f01575fde67c1bd7bfd375ace3b +size 398087 diff --git a/marked/Rel-16/23_series/23333/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23333/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f5245df72dca81d1777cff6a0ab29fef2dfb291b --- /dev/null +++ b/marked/Rel-16/23_series/23333/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d0090dd6488b8cd5e9529b52dd26c5d75efe500267d0ec7d860866d5546525ab +size 244533 diff --git a/marked/Rel-16/23_series/23333/cd1731bf5e9e6baa73b786b2dcc80168_img.jpg b/marked/Rel-16/23_series/23333/cd1731bf5e9e6baa73b786b2dcc80168_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f3de8c568e67d882d2571af8714bda9c557cacb4 --- /dev/null +++ b/marked/Rel-16/23_series/23333/cd1731bf5e9e6baa73b786b2dcc80168_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9e73dfbb6a4f6715113b54afc78d29c7e442fef021c0089015dd94ed3e361f90 +size 39670 diff --git a/marked/Rel-16/23_series/23333/d0abac95583b52a3b35f74a215567334_img.jpg b/marked/Rel-16/23_series/23333/d0abac95583b52a3b35f74a215567334_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5b01016fc114505c73b4c53af32e08bc86e0c4d4 --- /dev/null +++ b/marked/Rel-16/23_series/23333/d0abac95583b52a3b35f74a215567334_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:20b94fd80e54b2193bd3145baf85869505499a9fe6475251a1cb7134417c0bf4 +size 19950 diff --git a/marked/Rel-16/23_series/23333/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/marked/Rel-16/23_series/23333/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8efdd8705836613f28ed38d182376cd4c988a5e2 --- /dev/null +++ b/marked/Rel-16/23_series/23333/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33d2604c7883bec0eebd82cc78e27a42fb246585d409e7a4820b21b5444da2ef +size 18677 diff --git a/marked/Rel-16/23_series/23333/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/marked/Rel-16/23_series/23333/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1b277301d4e023a7e9dbef852733032688ea00d0 --- /dev/null +++ b/marked/Rel-16/23_series/23333/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ebdc11311cb5b909b12d18740b09068600a6641bceae45ecb8b83fd7f3865870 +size 19149 diff --git a/marked/Rel-16/23_series/23334/0b998e3ad8f9d104768642612605cb35_img.jpg b/marked/Rel-16/23_series/23334/0b998e3ad8f9d104768642612605cb35_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7637b3aecd3373c7eec5861f0a503260caac89d6 --- /dev/null +++ b/marked/Rel-16/23_series/23334/0b998e3ad8f9d104768642612605cb35_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d4756e6b670da33ae8af36bca31bea3d248f16c7f4382a1948139a67602cfcdd +size 232767 diff --git a/marked/Rel-16/23_series/23334/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/marked/Rel-16/23_series/23334/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e85f857a7d23609ff54b11bf71b3c06b8cfe0b1 --- /dev/null +++ b/marked/Rel-16/23_series/23334/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:14cc0190b2df7b9a568c297670cdf1724651f6a032db7d35bd49aa6f2d44eb8b +size 245959 diff --git a/marked/Rel-16/23_series/23334/0eb348bf17d67bf96326e07011d1c1ad_img.jpg b/marked/Rel-16/23_series/23334/0eb348bf17d67bf96326e07011d1c1ad_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ff01aa6b5e03792ebba5f7a727288cdab3334c3a --- /dev/null +++ b/marked/Rel-16/23_series/23334/0eb348bf17d67bf96326e07011d1c1ad_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d825c41f6a084ac9bc0a452bc0628ca44caa25ec5e49b8494f49ad2cab34ba2e +size 153910 diff --git a/marked/Rel-16/23_series/23334/11f18bf0233d812ad2604f88f3385d60_img.jpg b/marked/Rel-16/23_series/23334/11f18bf0233d812ad2604f88f3385d60_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..64c07f759a148054ff26f2eddd7acb7ab82291b3 --- /dev/null +++ b/marked/Rel-16/23_series/23334/11f18bf0233d812ad2604f88f3385d60_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2bdd964e34170ecbd0822b24dabbe55888527ae47dc7a282ce5bd4d8419cf6d0 +size 20774 diff --git a/marked/Rel-16/23_series/23334/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg b/marked/Rel-16/23_series/23334/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..245d416d9408c0a1306d403c43c0d927bde4aec5 --- /dev/null +++ b/marked/Rel-16/23_series/23334/1314748d1fff41b2d57a8ba9e9687c6a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:053365a34a495752dd48e62d8369a8b211cb02ddaf3483fdfd89a26a858aec32 +size 21040 diff --git a/marked/Rel-16/23_series/23334/137bcfed81ada68ca5162ca5afed35c7_img.jpg b/marked/Rel-16/23_series/23334/137bcfed81ada68ca5162ca5afed35c7_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c0b918de15b05902a1afbcae9f18cbcc33d4a0d5 --- /dev/null +++ b/marked/Rel-16/23_series/23334/137bcfed81ada68ca5162ca5afed35c7_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a2c92329d3b17b537f526af7af04c34e6e38ca114d4759b3bbd882334c4b521 +size 167596 diff --git a/marked/Rel-16/23_series/23334/18722c46c9e8475524e634dedd08bac2_img.jpg b/marked/Rel-16/23_series/23334/18722c46c9e8475524e634dedd08bac2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..924ebd30572ece591cc6ef6c8f591fa984613c40 --- /dev/null +++ b/marked/Rel-16/23_series/23334/18722c46c9e8475524e634dedd08bac2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:792aa733d473a0628e6b95dd39eb191a0a6de98b279e17e996cab6b1a0901686 +size 61877 diff --git a/marked/Rel-16/23_series/23334/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23334/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..14930de4f394fd32801cdc01eecdda358658d78f --- /dev/null +++ b/marked/Rel-16/23_series/23334/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:06bcd024b92946a43729663ce2a5892073d54dac4bf7e80e23d62dec55129d0b +size 55272 diff --git a/marked/Rel-16/23_series/23334/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg b/marked/Rel-16/23_series/23334/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..50f736b5f002b49ae92dc378b1d152f619d0e027 --- /dev/null +++ b/marked/Rel-16/23_series/23334/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf57b6c97f02b284ea183a8aef3deea17e63e32ca12b5b74999a760f3cbba2a9 +size 47158 diff --git a/marked/Rel-16/23_series/23334/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg b/marked/Rel-16/23_series/23334/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a1617c82aca5d11994907c4f6e0d62b693929ad5 --- /dev/null +++ b/marked/Rel-16/23_series/23334/1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c977b07a6b668f288a8d576f06aedb11cbed09e78e6411b29848779652ae6d0c +size 254796 diff --git a/marked/Rel-16/23_series/23334/205c14458d7f4e2d22c75354bb451e99_img.jpg b/marked/Rel-16/23_series/23334/205c14458d7f4e2d22c75354bb451e99_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c16295fada78c48f04b9269bee90ffd1007d0a70 --- /dev/null +++ b/marked/Rel-16/23_series/23334/205c14458d7f4e2d22c75354bb451e99_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:58cd9fa1f39fbfe0e147ad5fa591584adb3fad2dc038f3c3c7d7a26b788d3f15 +size 19567 diff --git a/marked/Rel-16/23_series/23334/223792b3652794024244c277cc46394b_img.jpg b/marked/Rel-16/23_series/23334/223792b3652794024244c277cc46394b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f81950fc00935fa88449c2f11d92d7320c011a54 --- /dev/null +++ b/marked/Rel-16/23_series/23334/223792b3652794024244c277cc46394b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4889ab0cef7318bb26d8a63d240d580e7f6b5510da36e0d9fc365136f6653fde +size 96903 diff --git a/marked/Rel-16/23_series/23334/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg b/marked/Rel-16/23_series/23334/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0940f15ce475e6d07a4289e948bbad27eb53789f --- /dev/null +++ b/marked/Rel-16/23_series/23334/24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4ee32dc945508dc23c0d719fbc64e7b935c9a445c1f4985f220c1334d861c4ad +size 36232 diff --git a/marked/Rel-16/23_series/23334/288220dc8e18b23fc8f294cf1ca909b4_img.jpg b/marked/Rel-16/23_series/23334/288220dc8e18b23fc8f294cf1ca909b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5eb95cc5d7a1294af89f5b85ff3fcf7eaa405a2f --- /dev/null +++ b/marked/Rel-16/23_series/23334/288220dc8e18b23fc8f294cf1ca909b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b850ffe9269de19e42616400dc8ba556a38a77e9f82e056c43cb4b2e84c64fc7 +size 56567 diff --git a/marked/Rel-16/23_series/23334/2b00743506f6a3bbd17af764162dc76d_img.jpg b/marked/Rel-16/23_series/23334/2b00743506f6a3bbd17af764162dc76d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..53b7107b6baadf431857b9929415bf28118e7ada --- /dev/null +++ b/marked/Rel-16/23_series/23334/2b00743506f6a3bbd17af764162dc76d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4f95ce660d0fa86bccd46924fa36b043d485edef2ba926a8d21e7299e3573f03 +size 214702 diff --git a/marked/Rel-16/23_series/23334/2df1e34671c73d7c0d047d4e9009251e_img.jpg b/marked/Rel-16/23_series/23334/2df1e34671c73d7c0d047d4e9009251e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..998c62289cc8b1f69e274016bbfc3ac9ade068b1 --- /dev/null +++ b/marked/Rel-16/23_series/23334/2df1e34671c73d7c0d047d4e9009251e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:592ab944c4bf35752f6bd1160ae62fbd3126474e0c45a1fd4f1fadb5d9d7e41e +size 153667 diff --git a/marked/Rel-16/23_series/23334/35f0cb888f4aa1b5fd01738a3ea3f0c1_img.jpg b/marked/Rel-16/23_series/23334/35f0cb888f4aa1b5fd01738a3ea3f0c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7509bab132d07c11714922dadf0b99b1294e0816 --- /dev/null +++ b/marked/Rel-16/23_series/23334/35f0cb888f4aa1b5fd01738a3ea3f0c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:10f35ba8a12ca5788606f063f232f2fd9e8a078fbed96ca70bf556661ae3fa69 +size 43951 diff --git a/marked/Rel-16/23_series/23334/38d82ffe820e339811b396206f40a201_img.jpg b/marked/Rel-16/23_series/23334/38d82ffe820e339811b396206f40a201_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0bb33199a95c02c098c91d0c9a4a9e6e712f84f3 --- /dev/null +++ b/marked/Rel-16/23_series/23334/38d82ffe820e339811b396206f40a201_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ea0379a8ae6db2e0a7b91599027a4fa86a9a2ed64869ee95d86edb2f6a541c31 +size 21675 diff --git a/marked/Rel-16/23_series/23334/3941735fafadf9a59b811f67fcdca7b3_img.jpg b/marked/Rel-16/23_series/23334/3941735fafadf9a59b811f67fcdca7b3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f6ed418ee80f25d0413b07f221f241aff1abfd5 --- /dev/null +++ b/marked/Rel-16/23_series/23334/3941735fafadf9a59b811f67fcdca7b3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5626c71f2791f7fb546194e9a99920b291fc747819ded120d331873e418a5f0 +size 19556 diff --git a/marked/Rel-16/23_series/23334/3e88de626facff0ce44cb3cb12c40d29_img.jpg b/marked/Rel-16/23_series/23334/3e88de626facff0ce44cb3cb12c40d29_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ead2a6aac4b2747ef90162819ecdafa7c11458e7 --- /dev/null +++ b/marked/Rel-16/23_series/23334/3e88de626facff0ce44cb3cb12c40d29_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:788a6ad41a8590478e8dd5b25f15aa75f2fd993fd523f5f0edeaba37de9df3a4 +size 123537 diff --git a/marked/Rel-16/23_series/23334/3ec35c497a0765a1a885c85f214b1bef_img.jpg b/marked/Rel-16/23_series/23334/3ec35c497a0765a1a885c85f214b1bef_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..319c13ed458098ccd6f0992522afd668115e0ba3 --- /dev/null +++ b/marked/Rel-16/23_series/23334/3ec35c497a0765a1a885c85f214b1bef_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7d348970ceff1d3acd17b10c65c2071052581fbc8a60710fccdf6a86b2b7578c +size 35733 diff --git a/marked/Rel-16/23_series/23334/41fa90d03d7195caa162c74d289817a4_img.jpg b/marked/Rel-16/23_series/23334/41fa90d03d7195caa162c74d289817a4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e78036ec9571e895f474f10559e1c274485395fc --- /dev/null +++ b/marked/Rel-16/23_series/23334/41fa90d03d7195caa162c74d289817a4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:98e185ecd1a7edede68e55845b0b6d7d795960cfdad1a5e3dd24db27816b1913 +size 57804 diff --git a/marked/Rel-16/23_series/23334/497d7e14540664a2914557cad79f3791_img.jpg b/marked/Rel-16/23_series/23334/497d7e14540664a2914557cad79f3791_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4f81fe9c48937e9c3a39bd1f40ded4f3b09babdd --- /dev/null +++ b/marked/Rel-16/23_series/23334/497d7e14540664a2914557cad79f3791_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5bc6a24a427a544745745dbd0c42f2b5972ac654534f6c8b182d71ccd9cd969 +size 42606 diff --git a/marked/Rel-16/23_series/23334/4a390493f601ce1ac6b9201db4e28b5a_img.jpg b/marked/Rel-16/23_series/23334/4a390493f601ce1ac6b9201db4e28b5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..421a85d4a10621efb54680b73243e626e41104dd --- /dev/null +++ b/marked/Rel-16/23_series/23334/4a390493f601ce1ac6b9201db4e28b5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:af0da0d517406ee9d0463041975abb68cc84bc6954654549fcfe7ad871a04420 +size 23235 diff --git a/marked/Rel-16/23_series/23334/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg b/marked/Rel-16/23_series/23334/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25ab986bd882f1e1bed21fc30451da52942de744 --- /dev/null +++ b/marked/Rel-16/23_series/23334/4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c13081803213c455df9bc7525b62a82c16321c62aabc7aaaccb39281c747a263 +size 21317 diff --git a/marked/Rel-16/23_series/23334/511f9b05a4c458937dd12c30936fd7d6_img.jpg b/marked/Rel-16/23_series/23334/511f9b05a4c458937dd12c30936fd7d6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..41935846d367bbb771c3b01dcd6f1cfe8f65d022 --- /dev/null +++ b/marked/Rel-16/23_series/23334/511f9b05a4c458937dd12c30936fd7d6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ce15866519a8a0ddac1eaea2e4c73a70841aae72378ea06f07f6c64be12c2ad8 +size 130388 diff --git a/marked/Rel-16/23_series/23334/516174e327ed8fcb75cb3af20f110de8_img.jpg b/marked/Rel-16/23_series/23334/516174e327ed8fcb75cb3af20f110de8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..39a20e7ddc531976b67282f6e5db188bc222c158 --- /dev/null +++ b/marked/Rel-16/23_series/23334/516174e327ed8fcb75cb3af20f110de8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:768420fd8efed0a4f495624d9929d9bb8d368273a5133e836f0ae513b6084a59 +size 99892 diff --git a/marked/Rel-16/23_series/23334/53001b5ae3f65139f78db410bb41ae30_img.jpg b/marked/Rel-16/23_series/23334/53001b5ae3f65139f78db410bb41ae30_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e012fd8f85685d7f0e0cd740965c633573649808 --- /dev/null +++ b/marked/Rel-16/23_series/23334/53001b5ae3f65139f78db410bb41ae30_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5e20a63a8c5671a0dcbcf0519ff4a9ea2699d26c960175613e39e612ea5b7bf8 +size 21137 diff --git a/marked/Rel-16/23_series/23334/55736d2180d01f631782ce0784caafa3_img.jpg b/marked/Rel-16/23_series/23334/55736d2180d01f631782ce0784caafa3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..aa403c74dca716b093e79369c0885cddac6a4588 --- /dev/null +++ b/marked/Rel-16/23_series/23334/55736d2180d01f631782ce0784caafa3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:67922b93bda2347a3b0526f0bc645a2d3dabfc02409a0ddb70c85b60108c04fa +size 23074 diff --git a/marked/Rel-16/23_series/23334/5e787be3a9da44aa97f5fcdcd41c0123_img.jpg b/marked/Rel-16/23_series/23334/5e787be3a9da44aa97f5fcdcd41c0123_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..97f7ba84d6b57cb4f6b53f5911bf98e3339ca4de --- /dev/null +++ b/marked/Rel-16/23_series/23334/5e787be3a9da44aa97f5fcdcd41c0123_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b6224ff678ce887544579333c79d6d7836ccd42bb0b30ec44f53a2999ba0e211 +size 90531 diff --git a/marked/Rel-16/23_series/23334/5fb340ad68b0c71df0b56698b137e35b_img.jpg b/marked/Rel-16/23_series/23334/5fb340ad68b0c71df0b56698b137e35b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6df1d62c169bbf8122ce6fc7761cd49dd8838644 --- /dev/null +++ b/marked/Rel-16/23_series/23334/5fb340ad68b0c71df0b56698b137e35b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b9f21a4e8d54c59b90e380bce77f1e9159e0a189c71ca5ec5768841726b4bf9 +size 9603 diff --git a/marked/Rel-16/23_series/23334/6059b0a3a051cc20b414d51a4e412f3e_img.jpg b/marked/Rel-16/23_series/23334/6059b0a3a051cc20b414d51a4e412f3e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..155189cdd91e6f383f3c891446d566ad8b88b9c0 --- /dev/null +++ b/marked/Rel-16/23_series/23334/6059b0a3a051cc20b414d51a4e412f3e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3aabdcec9b74b12af8f80006720f98fd3f2cbc595638b0d3235657577b817ebd +size 207723 diff --git a/marked/Rel-16/23_series/23334/64662465bba247703fdec49c8f3309f9_img.jpg b/marked/Rel-16/23_series/23334/64662465bba247703fdec49c8f3309f9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c12d1acabc0f0eecdd9ee9b71a95dc65d480a2d --- /dev/null +++ b/marked/Rel-16/23_series/23334/64662465bba247703fdec49c8f3309f9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1f045e6f326e45e293afc46bcef8e7a763a01fab821dbffcd0d7d49b864e975c +size 6442 diff --git a/marked/Rel-16/23_series/23334/649426750a89fa0e5d7c1736d5cf72c6_img.jpg b/marked/Rel-16/23_series/23334/649426750a89fa0e5d7c1736d5cf72c6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..25ecac7c5ef70f49676a3760167d3e1a4257a6f7 --- /dev/null +++ b/marked/Rel-16/23_series/23334/649426750a89fa0e5d7c1736d5cf72c6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:242c7ec2733f0f50c9877d4951d2ba24a88b2dbfd354b1e3cc871804f25e006d +size 224629 diff --git a/marked/Rel-16/23_series/23334/67c232883c119b120d2fb337bf588e05_img.jpg b/marked/Rel-16/23_series/23334/67c232883c119b120d2fb337bf588e05_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c99ca44eca5ae7d748a7dac5dc8b1ed20ea1b3c3 --- /dev/null +++ b/marked/Rel-16/23_series/23334/67c232883c119b120d2fb337bf588e05_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7fa8ecb4f1d0b7086b5fc13691fc6a64d3dea04a6c0e7d1b29f14e4bb4d0459c +size 19291 diff --git a/marked/Rel-16/23_series/23334/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/marked/Rel-16/23_series/23334/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2962d1c671750d925d32ef3fc0bf36882ac37dfa --- /dev/null +++ b/marked/Rel-16/23_series/23334/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:02e34dde44d2932bd79572e5765e5e5a7980f3c35bd1524c6eb69279fa7e8f18 +size 238682 diff --git a/marked/Rel-16/23_series/23334/710ff83dc4a77abbe489fbf1a462845a_img.jpg b/marked/Rel-16/23_series/23334/710ff83dc4a77abbe489fbf1a462845a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fe5640512e7e1dfc23798ab384aee654440dd1da --- /dev/null +++ b/marked/Rel-16/23_series/23334/710ff83dc4a77abbe489fbf1a462845a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:24f1e0f327d2431f71290dc3cb726ac17198c71d499d1ed7bb9618988e74f89b +size 78473 diff --git a/marked/Rel-16/23_series/23334/72d448a65347c51989171748789c7d4b_img.jpg b/marked/Rel-16/23_series/23334/72d448a65347c51989171748789c7d4b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..90dd85b0f1b3eb1fb11f9323ffe48022553d0212 --- /dev/null +++ b/marked/Rel-16/23_series/23334/72d448a65347c51989171748789c7d4b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04f156c8bff1cd00ecf71cda8ebe6bcf1a6fa317db0d04d81bf39bf0cbde6ec4 +size 32633 diff --git a/marked/Rel-16/23_series/23334/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/marked/Rel-16/23_series/23334/750b1652a4f4791b84c02aa755a1dedd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2ec3743d3a4684f22191ab9329a063935b86992 --- /dev/null +++ b/marked/Rel-16/23_series/23334/750b1652a4f4791b84c02aa755a1dedd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:afbe01e2e0c51cdd42364917ab4de6be658d1525ca252121059d4a1a372ca524 +size 133940 diff --git a/marked/Rel-16/23_series/23334/7b2d685b805535c1e94aee1365753b92_img.jpg b/marked/Rel-16/23_series/23334/7b2d685b805535c1e94aee1365753b92_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6c2f89cb0f41ef7f482809305110c62ac389bf0b --- /dev/null +++ b/marked/Rel-16/23_series/23334/7b2d685b805535c1e94aee1365753b92_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1fa021d508b29b33febf3fc01dad4ee45f33ca11a486c612c03caac9544496ab +size 21439 diff --git a/marked/Rel-16/23_series/23334/7fe4241eea8865aa6d2686d711c13ba6_img.jpg b/marked/Rel-16/23_series/23334/7fe4241eea8865aa6d2686d711c13ba6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2def82b5f5beae1ce96ffab9a4c09a9eb35c2013 --- /dev/null +++ b/marked/Rel-16/23_series/23334/7fe4241eea8865aa6d2686d711c13ba6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:86f0757d130f0ade07370aa8e68ea73179c437d5d85303077251594b38ce0b80 +size 22401 diff --git a/marked/Rel-16/23_series/23334/8f8caebe58364416a2eda21039d8c7bf_img.jpg b/marked/Rel-16/23_series/23334/8f8caebe58364416a2eda21039d8c7bf_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bfb608f50cf718d9798ec1203b9438647a966307 --- /dev/null +++ b/marked/Rel-16/23_series/23334/8f8caebe58364416a2eda21039d8c7bf_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:908e9516a6c6b455702fc675a6c613a8d861709c32167dc48d24a675fbfbcc8f +size 32275 diff --git a/marked/Rel-16/23_series/23334/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg b/marked/Rel-16/23_series/23334/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8cd44259023d970797a7b127b224edf87d9d8139 --- /dev/null +++ b/marked/Rel-16/23_series/23334/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d941857e3ef578f21118b1c0c081f83f9c4dcb70ef3a96073708c6af62256270 +size 91753 diff --git a/marked/Rel-16/23_series/23334/967e98a12645f89cb4a7620f42bf8c2e_img.jpg b/marked/Rel-16/23_series/23334/967e98a12645f89cb4a7620f42bf8c2e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6b06e882121c55b90544c406d28498c5ab1a9582 --- /dev/null +++ b/marked/Rel-16/23_series/23334/967e98a12645f89cb4a7620f42bf8c2e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:116929d05575e54c47debb05f086771e7c2434a7f76da9657fa35b9ca66982f3 +size 22470 diff --git a/marked/Rel-16/23_series/23334/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/Rel-16/23_series/23334/99bae07626f60f9ede10e2e387ef7051_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eee27b8838dc79f9c64aaa204f2c38954d7681a4 --- /dev/null +++ b/marked/Rel-16/23_series/23334/99bae07626f60f9ede10e2e387ef7051_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a8c2a3b6d0c7d34a1babebb1f1ea213665c6ed7c15a51f44108096714da9067a +size 51736 diff --git a/marked/Rel-16/23_series/23334/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg b/marked/Rel-16/23_series/23334/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf26ddd14de33ae287298ead609004c7856a8388 --- /dev/null +++ b/marked/Rel-16/23_series/23334/99e9a4791d2e5bb5afa1bb884652d4db_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bc6a076043572d49c580f206bd92b0336b7567655045218fec7ee9cecd03e7ae +size 24229 diff --git a/marked/Rel-16/23_series/23334/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/marked/Rel-16/23_series/23334/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..72c05c72662ac9cb0513e12929777678d6f311a4 --- /dev/null +++ b/marked/Rel-16/23_series/23334/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5c356f57fd8763b5e07249fee36a8e44cfceb97e86b1555b38c4d2f66e787114 +size 287486 diff --git a/marked/Rel-16/23_series/23334/9c45844d796e85ae05505870a54e4eb4_img.jpg b/marked/Rel-16/23_series/23334/9c45844d796e85ae05505870a54e4eb4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0899293db4dec22907cee43270df79527c749bde --- /dev/null +++ b/marked/Rel-16/23_series/23334/9c45844d796e85ae05505870a54e4eb4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0a71cd55dd10b9c8f0370038085707ea5f137180d90294301dcb6d7821f99aeb +size 20405 diff --git a/marked/Rel-16/23_series/23334/9ef15a4afab1416db28b91184862a3a5_img.jpg b/marked/Rel-16/23_series/23334/9ef15a4afab1416db28b91184862a3a5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..61bc0532ae9e7efa387e74651ca0e0138c2b5aec --- /dev/null +++ b/marked/Rel-16/23_series/23334/9ef15a4afab1416db28b91184862a3a5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:61d0a2da75505554ef7bc997afe7bdec8f1c5628d5d6b0782d2e26fb5c85d948 +size 325022 diff --git a/marked/Rel-16/23_series/23334/9f4aa7e5ba7f250b1c6d190b26b9cb6c_img.jpg b/marked/Rel-16/23_series/23334/9f4aa7e5ba7f250b1c6d190b26b9cb6c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..38cf90f2f63ff705bfd57b759d94ca4316e95702 --- /dev/null +++ b/marked/Rel-16/23_series/23334/9f4aa7e5ba7f250b1c6d190b26b9cb6c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:90e74b1d9dff0b6ca35f580894f674e344a242d0668581e37dd31dc9c61dd3d4 +size 50117 diff --git a/marked/Rel-16/23_series/23334/9f51a76cae7309a296cbc6997941eb3f_img.jpg b/marked/Rel-16/23_series/23334/9f51a76cae7309a296cbc6997941eb3f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bf3ac5bd353d2d37cab334ccacd5e7a64f93fea0 --- /dev/null +++ b/marked/Rel-16/23_series/23334/9f51a76cae7309a296cbc6997941eb3f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aa7908cf7984c7ab926af246fab0ac6946171a0b95ec88110924c069112315e3 +size 24613 diff --git a/marked/Rel-16/23_series/23334/a70e0adcabc973b01b413b6a141884f3_img.jpg b/marked/Rel-16/23_series/23334/a70e0adcabc973b01b413b6a141884f3_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6f8257ad103a169fa8dfd09fcd52627ec5a1c04e --- /dev/null +++ b/marked/Rel-16/23_series/23334/a70e0adcabc973b01b413b6a141884f3_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:77561fe2cbade85b589d527ff2cad7ac729af738eb364f0c2126921219f2161d +size 21626 diff --git a/marked/Rel-16/23_series/23334/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/marked/Rel-16/23_series/23334/a7450c80e88ad3f6ca1427ad84020998_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6d157bc7492fdbdd3b371fe817c9eb16b64de4a0 --- /dev/null +++ b/marked/Rel-16/23_series/23334/a7450c80e88ad3f6ca1427ad84020998_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b4894b3f3a7890f68cd0188fc946c7aa55d9b11f9b67057a5891aa06b636d9f1 +size 207277 diff --git a/marked/Rel-16/23_series/23334/a829326cd51f70316b996493833ec86c_img.jpg b/marked/Rel-16/23_series/23334/a829326cd51f70316b996493833ec86c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d7ac6c7e82ee0a60a882a928c4cc85bbf7b91825 --- /dev/null +++ b/marked/Rel-16/23_series/23334/a829326cd51f70316b996493833ec86c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:26e90f5fd8529dcfcef9da5d5e07030a0bfc54e5bd399d4307a6b8c5ad9e4934 +size 40999 diff --git a/marked/Rel-16/23_series/23334/a9241101d638c568cd5a84ab7ad39f15_img.jpg b/marked/Rel-16/23_series/23334/a9241101d638c568cd5a84ab7ad39f15_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d5daf965ccf75e58fbd7c3f288fe8e634f811c7e --- /dev/null +++ b/marked/Rel-16/23_series/23334/a9241101d638c568cd5a84ab7ad39f15_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e8a45a41bb764a0a9ca18a8686daf2566858993abc43546981095d3e6e179c9 +size 48047 diff --git a/marked/Rel-16/23_series/23334/a963ca41bde1669b18a4b783616f228b_img.jpg b/marked/Rel-16/23_series/23334/a963ca41bde1669b18a4b783616f228b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1d66a037d1dbb99d399c2894090c6b9c54ed9015 --- /dev/null +++ b/marked/Rel-16/23_series/23334/a963ca41bde1669b18a4b783616f228b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d840200320faa5aca09b7f1d3e14b18ccef35290ccd80830a9397ef3fa05260e +size 249056 diff --git a/marked/Rel-16/23_series/23334/ac8194ec0d833d53a0a36adada95b39e_img.jpg b/marked/Rel-16/23_series/23334/ac8194ec0d833d53a0a36adada95b39e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d872abb02fe47fe8e6df00429420b0107fcca102 --- /dev/null +++ b/marked/Rel-16/23_series/23334/ac8194ec0d833d53a0a36adada95b39e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ec340848c018fa2989f8fd6e5f8019af0cf88250ec6992addc7d39d26f208240 +size 20156 diff --git a/marked/Rel-16/23_series/23334/b13465efdac63129aef9b6f1787d0d00_img.jpg b/marked/Rel-16/23_series/23334/b13465efdac63129aef9b6f1787d0d00_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ec97903c3b5d5ca69ddb0eadc438388d48edc497 --- /dev/null +++ b/marked/Rel-16/23_series/23334/b13465efdac63129aef9b6f1787d0d00_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e345626bdcb5c2f81247d2196ff82bf534862621a1a5fd9cd2d455dc1458e73 +size 151727 diff --git a/marked/Rel-16/23_series/23334/b50f38be091844d58b11e3d47bc71e73_img.jpg b/marked/Rel-16/23_series/23334/b50f38be091844d58b11e3d47bc71e73_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9573ca1f4d6428b64b018ec5fd603083ee5dca3e --- /dev/null +++ b/marked/Rel-16/23_series/23334/b50f38be091844d58b11e3d47bc71e73_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d975301e0a6fa4e0dcd34db6d92166eee548238e56011d253ba8980ad4314599 +size 43282 diff --git a/marked/Rel-16/23_series/23334/b550cb515008f6bab9f295adcb28b5f6_img.jpg b/marked/Rel-16/23_series/23334/b550cb515008f6bab9f295adcb28b5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..68a263885b34dbfaf281de1199f2f832a732df98 --- /dev/null +++ b/marked/Rel-16/23_series/23334/b550cb515008f6bab9f295adcb28b5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3e30f63ad1016d83d614497488e7e8bc7c26e92b89f64ba7768d3ce64b4709d3 +size 197325 diff --git a/marked/Rel-16/23_series/23334/b55cd9b5721bd8aabc979c85316924e4_img.jpg b/marked/Rel-16/23_series/23334/b55cd9b5721bd8aabc979c85316924e4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..531340a23823154367a9653400bf9df37e8a38f5 --- /dev/null +++ b/marked/Rel-16/23_series/23334/b55cd9b5721bd8aabc979c85316924e4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0da09fb7208a3bf1c2b37b8c579d6cc4b83aa31d30c641acd0e6a33e60aac3f2 +size 54785 diff --git a/marked/Rel-16/23_series/23334/bbe5fb08522c43eab0afefcac30e719b_img.jpg b/marked/Rel-16/23_series/23334/bbe5fb08522c43eab0afefcac30e719b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..1abd3980d96705acd0bdca4db93d6750fa3a9f16 --- /dev/null +++ b/marked/Rel-16/23_series/23334/bbe5fb08522c43eab0afefcac30e719b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a94416f75bd0afe8771312fdf1997214f42e6c2d64c32916da81192855dff7d2 +size 24173 diff --git a/marked/Rel-16/23_series/23334/c0438093a10a593c42106b1e5dbb4331_img.jpg b/marked/Rel-16/23_series/23334/c0438093a10a593c42106b1e5dbb4331_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bed3a73592bbc6a08708c4594cbf318bbc2af59b --- /dev/null +++ b/marked/Rel-16/23_series/23334/c0438093a10a593c42106b1e5dbb4331_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:aed2c96d8beaa9673e0cf351e0c5b78b17e07fe481950ae6aa628d039c63a1d2 +size 166115 diff --git a/marked/Rel-16/23_series/23334/c0ca823603794512478906b302176bca_img.jpg b/marked/Rel-16/23_series/23334/c0ca823603794512478906b302176bca_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..560f84ae80b3c53652d4c5f6877d7990ebee443c --- /dev/null +++ b/marked/Rel-16/23_series/23334/c0ca823603794512478906b302176bca_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05614e015ff59f8c7b07f93591e93cda171f79ae82d3897fb570ba4b03cfe8a1 +size 246873 diff --git a/marked/Rel-16/23_series/23334/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg b/marked/Rel-16/23_series/23334/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7532257d97373651c930dbf637d909835776c835 --- /dev/null +++ b/marked/Rel-16/23_series/23334/c15cb6383bc35906e6b3c7c3aac621ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:15b40a015fb3d7f3402ae68fa9a3f093ecded0f5f03b7a76acf8755b355092d5 +size 105810 diff --git a/marked/Rel-16/23_series/23334/c64555b7f91435b01997807dbb4bcc4c_img.jpg b/marked/Rel-16/23_series/23334/c64555b7f91435b01997807dbb4bcc4c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..af3f3c06a12c33b51d922bcf5aeb9dd2b99f1b22 --- /dev/null +++ b/marked/Rel-16/23_series/23334/c64555b7f91435b01997807dbb4bcc4c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a125bfc969ed360a91a789dd195c4b158fa6d60ffd1f04bc8feb45b60ce0b197 +size 16764 diff --git a/marked/Rel-16/23_series/23334/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/marked/Rel-16/23_series/23334/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8840506d93f36004dd5cebb2434b297a8e64fcce --- /dev/null +++ b/marked/Rel-16/23_series/23334/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:000e77863a63d831db8a6ca93b4bf3546b981c8d5e3bdfb8921b031374cb7973 +size 44057 diff --git a/marked/Rel-16/23_series/23334/d16e5a3857155ee2837d851305ee8036_img.jpg b/marked/Rel-16/23_series/23334/d16e5a3857155ee2837d851305ee8036_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..9162e7cd944c6e5f998c5697938ea362b01cb313 --- /dev/null +++ b/marked/Rel-16/23_series/23334/d16e5a3857155ee2837d851305ee8036_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d5c6635a435968ddb80ef0dc1f41cf1a4caece87e35be1134e29059f3ce74c78 +size 20794 diff --git a/marked/Rel-16/23_series/23334/e01c6273c4177746475715ee9c17a882_img.jpg b/marked/Rel-16/23_series/23334/e01c6273c4177746475715ee9c17a882_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f74e004e1b9ea84e33946c6d0fdd16f224dfa275 --- /dev/null +++ b/marked/Rel-16/23_series/23334/e01c6273c4177746475715ee9c17a882_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c029643ad36127f43de4d38d9bb6063c10bfc1b14888682458d531f7c0897127 +size 326942 diff --git a/marked/Rel-16/23_series/23334/e5ded42f8e352da02ee86cb55550c45d_img.jpg b/marked/Rel-16/23_series/23334/e5ded42f8e352da02ee86cb55550c45d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8034d01f382581c629d96865144e3aaf4c06fdb0 --- /dev/null +++ b/marked/Rel-16/23_series/23334/e5ded42f8e352da02ee86cb55550c45d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f8f99192488add50b82c23a523c91eaec16c5bd5a31b766c50a8d1c3a981ffef +size 44598 diff --git a/marked/Rel-16/23_series/23334/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg b/marked/Rel-16/23_series/23334/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e8af947e15a4595cd58bf0e5754bff9a6922581 --- /dev/null +++ b/marked/Rel-16/23_series/23334/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f3099c3b1e29d39c7d09457f9c7d897361dd77874db2f71805651a40c1380f6 +size 118720 diff --git a/marked/Rel-16/23_series/23334/ef45b00396c293be0b18d32b97118bf4_img.jpg b/marked/Rel-16/23_series/23334/ef45b00396c293be0b18d32b97118bf4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4a8b03dd9afa866461d0d0cd8f65dc0dff31f13 --- /dev/null +++ b/marked/Rel-16/23_series/23334/ef45b00396c293be0b18d32b97118bf4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84aa7b03b5f1066885177a077b04242806df7c2722f57a97e381a119d3e6d9c3 +size 195935 diff --git a/marked/Rel-16/23_series/23334/ef86416097668984aee7611317e77bb9_img.jpg b/marked/Rel-16/23_series/23334/ef86416097668984aee7611317e77bb9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..17b75025414332a573455ea0834b06e9f77946f5 --- /dev/null +++ b/marked/Rel-16/23_series/23334/ef86416097668984aee7611317e77bb9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c95fa5d35a097f26be7aaf3673caf3923c0dc1d6cc5cfa0a62c0b118087c0827 +size 72384 diff --git a/marked/Rel-16/23_series/23334/f57a881fcbcaf494a7dedc4f61224991_img.jpg b/marked/Rel-16/23_series/23334/f57a881fcbcaf494a7dedc4f61224991_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..77c224bed680d55620da6454dc9c418573c9b989 --- /dev/null +++ b/marked/Rel-16/23_series/23334/f57a881fcbcaf494a7dedc4f61224991_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:375175d0885c6061e7f64090401cd4405108399ac72c44620c365f01b55349ec +size 60271 diff --git a/marked/Rel-16/23_series/23334/raw.md b/marked/Rel-16/23_series/23334/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..bb6d5e81e7c118f5fbab70bd5a1cddd6f7763234 --- /dev/null +++ b/marked/Rel-16/23_series/23334/raw.md @@ -0,0 +1,6291 @@ + + +# 3GPP TS 23.334 V16.3.0 (2021-03) + +*Technical Specification* + +## **3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW) interface: Procedures descriptions (Release 16)** + +![LTE Advanced Pro logo](64662465bba247703fdec49c8f3309f9_img.jpg) + +The logo for LTE Advanced Pro, featuring the letters 'lte' in a bold, lowercase font. Above the 'e' is the text 'Advanced Pro' in a smaller font. To the right of the 'e' is a green signal icon with three bars. + +LTE Advanced Pro logo + +![3GPP logo](5fb340ad68b0c71df0b56698b137e35b_img.jpg) + +The 3GPP logo, consisting of the letters '3GPP' in a stylized, bold font. Below the 'P' is a red signal icon with three bars. Below the logo, the text 'A GLOBAL INITIATIVE' is written in a smaller, uppercase font. + +3GPP logo + +The present document has been developed within the 3rd Generation Partnership Project (3GPP™) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and Reports for implementation of the 3GPP™ system should be obtained via the 3GPP Organizational Partners' Publications Offices. + +## **3GPP** + +--- + +Postal address + +--- + +3GPP support office address + +--- + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +--- + +Internet + +--- + + + +# --- **Copyright Notification** --- + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2021, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTS™ is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|---------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 8 | +| 1 Scope..... | 9 | +| 2 References..... | 9 | +| 3 Definitions, symbols and abbreviations ..... | 13 | +| 3.1 Definitions..... | 13 | +| 3.2 Symbols..... | 14 | +| 3.3 Abbreviations ..... | 14 | +| 4 Architecture..... | 15 | +| 4.1 Reference architecture..... | 15 | +| 4.2 NAT Function ..... | 16 | +| 4.3 ATCF/ATGW Function ..... | 17 | +| 4.4 eP-CSCF/eIMS-AGW Function..... | 17 | +| 5 Functional Requirements ..... | 18 | +| 5.1 General ..... | 18 | +| 5.2 Gate Control & Local NAT..... | 18 | +| 5.3 IP realm indication and availability ..... | 18 | +| 5.4 Remote NAT traversal support ..... | 19 | +| 5.5 Remote Source Address/Port Filtering..... | 19 | +| 5.6 Traffic Policing ..... | 19 | +| 5.7 Hanging Termination Detection..... | 19 | +| 5.8 QoS Packet Marking ..... | 20 | +| 5.9 Handling of RTCP streams ..... | 20 | +| 5.9.1 General ..... | 20 | +| 5.9.2 RTP/RTCP transport multiplexing ..... | 21 | +| 5.10 Media Inactivity Detection..... | 21 | +| 5.11 IMS Media Plane Security ..... | 22 | +| 5.11.1 General ..... | 22 | +| 5.11.2 End-to-access-edge Security..... | 22 | +| 5.11.2.1 End-to-access-edge security for RTP based media using SDES ..... | 22 | +| 5.11.2.2 End-to-access-edge security for TCP based media using TLS..... | 23 | +| 5.11.2.2.1 General ..... | 23 | +| 5.11.2.2.2 e2ae security for session based messaging (MSRP) ..... | 24 | +| 5.11.2.2.3 e2ae security for conferencing (BFCP)..... | 25 | +| 5.11.2.3 End-to-access-edge security for UDP based media using DTLS ..... | 25 | +| 5.11.2.3.1 General ..... | 25 | +| 5.11.2.3.2 e2ae security for T.38 fax over UDP/UDPTL transport ..... | 25 | +| 5.11.2.4 End-to-access-edge security for RTP based media using DTLS-SRTP ..... | 26 | +| 5.11.2.5 End-to-access-edge security for RTP based voice and video media using DTLS-SRTP over TCP ..... | 27 | +| 5.11.2.6 End-to-access-edge security for WebRTC data channels using UDP/DTLS/SCTP transport ..... | 28 | +| 5.11.3 End-to-end Security ..... | 28 | +| 5.11.3.1 End-to-end security for RTP based media..... | 28 | +| 5.11.3.2 End-to-end security for TCP-based media using TLS..... | 28 | +| 5.12 Explicit Congestion Notification support..... | 29 | +| 5.12.1 General ..... | 29 | +| 5.12.2 Incoming SDP offer with ECN..... | 29 | +| 5.12.3 Incoming SDP offer without ECN ..... | 29 | +| 5.12.4 Detection of ECN failures by IMS-AGW ..... | 29 | +| 5.13 Transcoding..... | 30 | +| 5.13.1 General ..... | 30 | +| 5.13.2 Handling of common codec parameters ..... | 30 | +| 5.13.3 Handling of the EVS speech codec ..... | 31 | +| 5.13.4 Handling of the OPUS speech and audio codec for WebRTC ..... | 44 | +| 5.14 Multimedia Priority Service (MPS) Support..... | 47 | +| 5.15 Coordination of Video Orientation ..... | 48 | + +| | | | +|------------|---------------------------------------------------------------------------------------------------------------------------------|----| +| 5.16 | Generic image attributes..... | 49 | +| 5.17 | TCP bearer connection control..... | 49 | +| 5.17.1 | Stateless TCP handling..... | 49 | +| 5.17.2 | State-aware TCP handling..... | 50 | +| 5.17.2.1 | General..... | 50 | +| 5.17.2.2 | State-aware TCP handling without support of modifying the TCP setup direction ..... | 50 | +| 5.17.2.3 | State-aware TCP handling with support of modifying the TCP setup direction ..... | 51 | +| 5.18 | Interactive Connectivity Establishment (ICE) ..... | 53 | +| 5.18.1 | General ..... | 53 | +| 5.18.2 | ICE lite..... | 53 | +| 5.18.3 | Full ICE ..... | 55 | +| 5.18.4 | STUN consent freshness for WebRTC..... | 57 | +| 5.19 | MSRP handling ..... | 57 | +| 5.19.1 | General ..... | 57 | +| 5.19.2 | IMS-ALG procedures to support IETF RFC 6714 with application agnostic MSRP handling by the IMS-AGW ..... | 58 | +| 5.19.3 | IMS-ALG procedures to support IETF draft-ietf-simple-msrp-sessmatch with application agnostic MSRP handling by the IMS-AGW..... | 58 | +| 5.19.4 | IMS-ALG procedures for application aware MSRP interworking by the IMS-AGW ..... | 59 | +| 5.19.5 | Application-aware MSRP interworking at the IMS-AGW ..... | 59 | +| 5.19.6 | MSRP data channels..... | 59 | +| 5.20 | Web Real-Time Communication (WebRTC) ..... | 60 | +| 5.20.1 | General ..... | 60 | +| 5.20.2 | WebRTC data channel..... | 61 | +| 5.20.2.1 | General..... | 61 | +| 5.20.2.2 | Data Channel Establishment..... | 61 | +| 5.20.2.3 | Data Channel Release ..... | 66 | +| 5.20.2.3.1 | General ..... | 66 | +| 5.20.2.3.2 | Release of one WebRTC data channel..... | 67 | +| 5.20.2.3.3 | Release of all or last active WebRTC data channels within an SCTP Association ..... | 68 | +| 5.20.2.4 | MSRP within WebRTC data channel..... | 68 | +| 5.20.2.5 | Void ..... | 69 | +| 5.20.2.6 | T.140 within WebRTC data channel ..... | 69 | +| 5.20.3 | Media Plane Optimization..... | 69 | +| 5.20.3.1 | General..... | 69 | +| 5.20.3.2 | WIC originating call ..... | 70 | +| 5.20.3.3 | WIC terminating call ..... | 71 | +| 5.21 | Alternate Connection (ALTC) Addresses Management ..... | 73 | +| 5.21.1 | General ..... | 73 | +| 5.22 | Video Region-of-Interest (ROI) ..... | 73 | +| 5.22.1 | General ..... | 73 | +| 5.22.2 | "Far End Camera Control" mode..... | 73 | +| 5.22.3 | "Predefined ROI" mode ..... | 74 | +| 5.22.4 | "Arbitrary ROI" mode ..... | 75 | +| 5.23 | SDP Capability Negotiation (SDPCapNeg)..... | 75 | +| 5.24 | RTP-level pause and resume..... | 76 | +| 5.25 | RTCP Codec Control Commands and Indications..... | 77 | +| 5.26 | Delay Budget Information (DBI) ..... | 78 | +| 6 | IMS-ALG to IMS-AGW Procedures ..... | 79 | +| 6.1 | Non-Call Related Procedures..... | 79 | +| 6.1.1 | General ..... | 79 | +| 6.1.2 | IMS-AGW Unavailable..... | 79 | +| 6.1.3 | IMS-AGW Available..... | 80 | +| 6.1.4 | IMS-AGW Recovery..... | 81 | +| 6.1.5 | IMS-ALG Recovery ..... | 81 | +| 6.1.5.1 | General..... | 81 | +| 6.1.5.2 | IMS-ALG Restoration ..... | 82 | +| 6.1.6 | IMS-AGW Re-register ..... | 82 | +| 6.1.7 | IMS-AGW Re-registration Ordered by IMS-ALG ..... | 83 | +| 6.1.8 | Audit of IMS-AGW..... | 83 | +| 6.1.8.1 | Audit of Value ..... | 83 | + +| | | | +|----------------|-------------------------------------------------------------------------------------------------------------------|-----| +| 6.1.8.2 | Audit of Capability ..... | 84 | +| 6.1.9 | IMS-AGW Capability Change ..... | 84 | +| 6.1.10 | IMS-ALG Out of service ..... | 84 | +| 6.1.11 | IMS-AGW Resource Congestion Handling - Activate ..... | 85 | +| 6.1.12 | MGW Resource Congestion Handling -Indication ..... | 85 | +| 6.1.13 | Control association monitoring ..... | 85 | +| 6.1.14 | Realm Availability Monitoring ..... | 86 | +| 6.1.15 | Failure of IP Port, Interface or Group of Interfaces ..... | 87 | +| 6.2 | Call Related Procedures ..... | 87 | +| 6.2.1 | Gate Control & Local NA(P)T procedure ..... | 87 | +| 6.2.2 | IP realm indication procedure..... | 90 | +| 6.2.3 | Remote NA(P)T traversal support procedure..... | 90 | +| 6.2.4 | Remote Source Address/Port Filtering..... | 90 | +| 6.2.5 | Traffic Policing..... | 91 | +| 6.2.6 | Hanging Termination Detection..... | 91 | +| 6.2.7 | QoS Packet Marking..... | 92 | +| 6.2.8 | Media Inactivity Detection..... | 92 | +| 6.2.9 | Handling of RTCP streams..... | 93 | +| 6.2.10 | IMS end-to-access-edge Media Plane Security ..... | 93 | +| 6.2.10.1 | General ..... | 93 | +| 6.2.10.2 | End-to-access-edge security for RTP based media using SDES ..... | 93 | +| 6.2.10.3 | End-to-access-edge security for TCP-based media using TLS ..... | 93 | +| 6.2.10.3.1 | End-to-access-edge security for session based messaging (MSRP) ..... | 93 | +| 6.2.10.3.1.1 | IMS UE originating procedures for e2ae..... | 93 | +| 6.2.10.3.1.1.1 | Incoming TCP bearer establishment triggers an outgoing TCP bearer establishment ..... | 93 | +| 6.2.10.3.1.1.2 | IMS-ALG requests sending an outgoing TCP bearer establishment..... | 96 | +| 6.2.10.3.1.2 | IMS UE terminating procedures for e2ae..... | 98 | +| 6.2.10.3.1.2.1 | Incoming TCP bearer establishment triggers an outgoing TCP bearer establishment ..... | 98 | +| 6.2.10.3.1.2.2 | IMS-ALG requests sending an outgoing TCP bearer establishment..... | 101 | +| 6.2.10.3.2 | End-to-access-edge security for conferencing (BFCP) ..... | 103 | +| 6.2.10.3.2.1 | IMS UE originating procedures for e2ae..... | 103 | +| 6.2.10.3.2.1.1 | Incoming TCP bearer establishment triggers an outgoing TCP bearer establishment ..... | 103 | +| 6.2.10.3.2.2 | IMS UE terminating procedures for e2ae..... | 106 | +| 6.2.10.3.2.2.1 | Incoming TCP bearer establishment triggers an outgoing TCP bearer establishment ..... | 106 | +| 6.2.10.4 | End-to-access-edge security for UDP based media using DTLS ..... | 109 | +| 6.2.10.4.1 | General ..... | 109 | +| 6.2.10.4.2 | Session establishment from IMS access network for T.38 fax using "UDP/TLS/UDPTL" ..... | 109 | +| 6.2.10.4.3 | Session establishment towards IMS access network for T.38 fax using "UDP/TLS/UDPTL" ..... | 112 | +| 6.2.10.4.4 | IMS-AGW procedure for e2ae security of T.38 fax using "UDP/TLS/UDPTL" ..... | 114 | +| 6.2.10.4.5 | DTLS session establishment failure indication..... | 114 | +| 6.2.10.5 | End-to-access-edge security for RTP based media using DTLS-SRTP ..... | 115 | +| 6.2.10.6 | End-to-access-edge security for WebRTC data channels using SCTP-over-DTLS transport..... | 119 | +| 6.2.10.6.1 | General ..... | 119 | +| 6.2.10.6.2 | Call flow for data channel establishment from WIC towards IMS access network and MSRP session establishment ..... | 119 | +| 6.2.10A | IMS end-to-end Media Plane Security ..... | 122 | +| 6.2.10A.1 | End-to-end security for RTP based media using SDES ..... | 122 | +| 6.2.10A.2 | End-to-end security for TCP-based media using TLS..... | 122 | +| 6.2.11 | Change Through-Connection ..... | 122 | +| 6.2.12 | Emergency Calls..... | 122 | +| 6.2.13 | Explicit Congestion Notification support..... | 122 | +| 6.2.13.1 | General ..... | 122 | +| 6.2.13.2 | ECN Active Indicated (ECN transparent) ..... | 122 | +| 6.2.13.3 | ECN support requested (ECN endpoint) ..... | 123 | +| 6.2.13.4 | ECN Failure Indication (ECN endpoint) ..... | 123 | +| 6.2.14 | Access Transfer procedures with media anchored in IMS-AGW (ATGW) ..... | 124 | +| 6.2.14.1 | General ..... | 124 | +| 6.2.14.2 | H.248 context model..... | 124 | +| 6.2.14.3 | PS session origination or termination with media anchoring in IMS-AGW (ATGW) signaling procedures..... | 126 | +| 6.2.14.4 | PS to CS Access Transfer procedure with media anchored in IMS-AGW (ATGW) ..... | 128 | + +| | | | +|------------|--------------------------------------------------------------------------------------------------|-----| +| 6.2.14.5 | ECN support during PS to CS Access Transfer procedure with media anchored in IMS-AGW (ATGW)..... | 129 | +| 6.2.14.6 | Support of generic image attributes ..... | 130 | +| 6.2.14.6.1 | General ..... | 130 | +| 6.2.14.6.2 | Indication of generic image attributes..... | 131 | +| 6.2.14.7 | Handling of common codec parameters ..... | 131 | +| 6.2.14.8 | EVS speech codec support..... | 132 | +| 6.2.15 | Multimedia Priority Congestion Control Procedures ..... | 144 | +| 6.2.15.1 | General..... | 144 | +| 6.2.15.2 | IMS-AGW Resource Congestion in ADD response, request is queued..... | 144 | +| 6.2.15.3 | IMS-AGW Resource Congestion in ADD response, IMS-ALG seizes new IMS-AGW ..... | 145 | +| 6.2.15.4 | IMS-AGW Priority Resource Allocation ..... | 145 | +| 6.2.15.5 | IMS-AGW Priority User Data marking..... | 146 | +| 6.2.15.6 | IMS-AGW Priority Modification ..... | 146 | +| 6.2.16 | Coordination of Video Orientation..... | 147 | +| 6.2.17 | Procedures for Interactive Connectivity Establishment (ICE) ..... | 148 | +| 6.2.17.1 | ICE lite ..... | 148 | +| 6.2.17.2 | Full ICE..... | 148 | +| 6.2.17.3 | Connectivity check result notification (full ICE) ..... | 149 | +| 6.2.17.4 | New peer reflexive candidate notification (full ICE) ..... | 149 | +| 6.2.17.5 | STUN consent freshness test ..... | 150 | +| 6.2.17.6 | STUN Consent Freshness Test Failure Notification..... | 151 | +| 6.2.18 | TCP bearer connection control..... | 151 | +| 6.2.18.1 | General..... | 151 | +| 6.2.18.2 | Stateless TCP handling..... | 151 | +| 6.2.18.3 | State-aware TCP handling without support of modifying the TCP setup direction ..... | 151 | +| 6.2.18.4 | State-aware TCP handling with support of modifying the TCP setup direction ..... | 151 | +| 6.2.19 | Application-aware MSRP interworking at the IMS-AGW ..... | 153 | +| 6.2.20 | Alternate Connection (ALTC) Addresses Management ..... | 154 | +| 6.2.21 | Video Region-of-Interest (ROI) ..... | 156 | +| 6.2.21.1 | Video Region-of-Interest (ROI) using FECC ..... | 156 | +| 6.2.21.2 | "Predefined ROI" mode ..... | 157 | +| 6.2.21.3 | "Arbitrary ROI" mode..... | 158 | +| 6.2.22 | WebRTC..... | 159 | +| 6.2.22.1 | Establishment of a WebRTC data channel ..... | 159 | +| 6.2.22.2 | Release of a WebRTC data channel ..... | 159 | +| 6.2.22.3 | Media Plane Optimization ..... | 161 | +| 6.2.22.3.1 | Media Plane Optimization including DTLS layer for WIC originating call..... | 161 | +| 6.2.22.3.2 | Media Plane Optimization excluding DTLS layer for WIC originating call ..... | 163 | +| 6.2.23 | RTP-level pause and resume ..... | 165 | +| 6.2.24 | RTCP Codec Control Commands and Indications ..... | 165 | +| 6.2.25 | Delay Budget Information (DBI) ..... | 166 | +| 7 | Charging..... | 167 | +| 8 | Messages/Procedures and Contents ..... | 168 | +| 8.1 | General ..... | 168 | +| 8.2 | Reserve and Configure AGW Connection Point..... | 169 | +| 8.3 | Reserve AGW Connection Point Procedure ..... | 177 | +| 8.4 | Configure AGW Connection Point Procedure ..... | 183 | +| 8.5 | Release AGW Termination ..... | 190 | +| 8.6 | Termination heartbeat indication ..... | 190 | +| 8.7 | IMS-AGW Out-of-Service ..... | 191 | +| 8.8 | IMS-AGW Communication Up ..... | 191 | +| 8.9 | IMS-AGW Restoration ..... | 192 | +| 8.10 | IMS-AGW Register..... | 192 | +| 8.11 | IMS-ALG Restoration..... | 193 | +| 8.12 | IMS-AGW Re-register ..... | 193 | +| 8.13 | IMS-ALG Ordered Re-registration ..... | 194 | +| 8.14 | Audit Value ..... | 194 | +| 8.15 | Audit Capability ..... | 195 | +| 8.16 | Capability Update..... | 195 | + +| | | | +|---------------------------------------------------|--------------------------------------------------------------|------------| +| 8.17 | IMS-ALG Out of Service ..... | 196 | +| 8.18 | IMS-AGW Resource Congestion Handling - Activate ..... | 196 | +| 8.19 | IMS-AGW Resource Congestion Handling - Indication ..... | 197 | +| 8.20 | Inactivity Timeout Activate ..... | 197 | +| 8.21 | Inactivity Timeout Notification..... | 198 | +| 8.22 | Command Reject..... | 198 | +| 8.23 | Realm Availability Activate..... | 199 | +| 8.24 | Realm Availability Notification ..... | 199 | +| 8.25 | IP Bearer Released ..... | 200 | +| 8.26 | Media Inactivity Notification ..... | 200 | +| 8.27 | Termination Out-of-Service ..... | 201 | +| 8.28 | Change Through-Connection ..... | 201 | +| 8.29 | Change Flow Direction ..... | 202 | +| 8.30 | ECN Failure Indication ..... | 202 | +| 8.31 | Notify (D)TLS session establishment Failure Indication..... | 203 | +| 8.32 | Notify TCP connection establishment Failure Indication ..... | 203 | +| 8.33 | ICE Connectivity Check Result Notification ..... | 204 | +| 8.34 | ICE New Peer Reflexive Candidate Notification..... | 204 | +| 8.35 | STUN Consent Freshness Test Failure Notification ..... | 205 | +| 8.36 | Notify SCTP Stream Reset..... | 205 | +| 8.37 | Notify SCTP Stream Reset Result ..... | 206 | +| Annex A (informative): Change history..... | | 207 | + +# Foreword + +This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +In the present document, modal verbs have the following meanings: + +- shall** indicates a mandatory requirement to do something +- shall not** indicates an interdiction (prohibition) to do something + +The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in Technical Reports. + +The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced, non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a referenced document. + +- should** indicates a recommendation to do something +- should not** indicates a recommendation not to do something +- may** indicates permission to do something +- need not** indicates permission not to do something + +The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions "might not" or "shall not" are used instead, depending upon the meaning intended. + +- can** indicates that something is possible +- cannot** indicates that something is impossible + +The constructions "can" and "cannot" are not substitutes for "may" and "need not". + +- will** indicates that something is certain or expected to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- will not** indicates that something is certain or expected not to happen as a result of action taken by an agency the behaviour of which is outside the scope of the present document +- might** indicates a likelihood that something will happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +**might not** indicates a likelihood that something will not happen as a result of action taken by some agency the behaviour of which is outside the scope of the present document + +In addition: + +**is** (or any other verb in the indicative mood) indicates a statement of fact + +**is not** (or any other negative verb in the indicative mood) indicates a statement of fact + +The constructions "is" and "is not" do not indicate requirements. + +# 1 Scope + +Annex G of 3GPP TS 23.228 [2] gives out an IMS Application Level Gateway (IMS-ALG) and IMS Access Media Gateway (IMS-AGW) based reference model to support NAT-P-T, gate control and traffic policing between IP-CAN and IMS domain. + +![Figure 1.1: Scope of the specification. A diagram showing the network architecture for the Iq reference point. On the left, a UE (User Equipment) is connected to an IP-CAN (IP Connectivity Access Network). The IP-CAN is connected to a NAT (Network Address Translation) box. A dashed line labeled 'Gm' represents the IP signalling-path between the UE and the P-CSCF (PDN Connectivity Session Control Function). The P-CSCF contains an IMS-ALG (IMS Application Level Gateway). A bold horizontal line labeled 'Media' represents the IP media-path, passing through the NAT box and into the IMS Access Gateway. The IMS Access Gateway is connected to the IM CN domain (IMS Core Network domain). A vertical line labeled 'Iq' represents the control-path between the IMS-ALG and the IMS Access Gateway. A dashed box labeled 'Scope of this specification' encloses the P-CSCF (IMS-ALG) and the IMS Access Gateway.](99bae07626f60f9ede10e2e387ef7051_img.jpg) + +Figure 1.1: Scope of the specification. A diagram showing the network architecture for the Iq reference point. On the left, a UE (User Equipment) is connected to an IP-CAN (IP Connectivity Access Network). The IP-CAN is connected to a NAT (Network Address Translation) box. A dashed line labeled 'Gm' represents the IP signalling-path between the UE and the P-CSCF (PDN Connectivity Session Control Function). The P-CSCF contains an IMS-ALG (IMS Application Level Gateway). A bold horizontal line labeled 'Media' represents the IP media-path, passing through the NAT box and into the IMS Access Gateway. The IMS Access Gateway is connected to the IM CN domain (IMS Core Network domain). A vertical line labeled 'Iq' represents the control-path between the IMS-ALG and the IMS Access Gateway. A dashed box labeled 'Scope of this specification' encloses the P-CSCF (IMS-ALG) and the IMS Access Gateway. + +**Figure 1.1: Scope of the specification** + +Figure 1.1 illustrates the reference model for Iq: + +- the dashed line represents the IP signalling-path with SIP (at Gm) as call/session control protocol between the UE and the P-CSCF (IMS-ALG); +- the bold, horizontal line represents the IP media-path (also known as (IP) bearer-path or (IP) data-path; the notion 'media' is used as generic term for "IP application data"); and +- the vertical line represents the Iq control-path with H.248 as gateway/policy control protocol between the IMS-ALG and the IMS-AGW (H.248 messages are transported over IP). + +The Iq reference point is between the P-CSCF (IMS-ALG) and the IMS-AGW. It conveys the necessary information that is needed to allocate, modify and release (IP) transport addresses. + +The present document defines the stage 2 description for the Iq reference point. The stage 2 shall cover the information flow between the P-CSCF (IMS-ALG) and IMS-AGW. The protocol used over the Iq interface is the gateway control protocol according ITU-T Recommendation H.248 (which is specified for Iq by an H.248 profile according 3GPP TS 29.334 [3]). + +# 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS), stage 2". +- [3] 3GPP TS 29.334: "IMS Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW) Iq interface, stage 3". +- [4] IETF RFC 2663: "IP Network Address Translator (NAT) Terminology and Considerations". +- [5] 3GPP TS 32.260: "Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging". +- [6] IETF RFC 3556: "Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) Bandwidth". +- [7] IETF RFC 3605: "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)". +- [8] 3GPP TS 23.205: "Bearer independent circuit-switched core network; Stage 2". +- [9] ITU-T Recommendation H.248.1 (05/2002): "Gateway Control Protocol: Version 2" including the Corrigendum1 for Version 2 (03/04). +- [10] IETF RFC 2216: "Network Element Service Template". +- [11] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP". +- [12] 3GPP TS 33.328: "IMS Media Plane Security". +- [13] IETF RFC 4568: "Session Description Protocol (SDP) Security Descriptions for Media Streams". +- [14] IETF RFC 3711: "The Secure Real-time Transport Protocol (SRTP)". +- [15] IETF RFC 5124: "Extended Secure RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/SAVPF)". +- [16] IETF RFC 3168: "The Addition of Explicit Congestion Notification (ECN) to IP". +- [17] IETF RFC 6679: "Explicit Congestion Notification (ECN) for RTP over UDP". +- [18] 3GPP TS 23.237: "IP Multimedia subsystem (IMS) Service Continuity; Stage 2". +- [19] 3GPP TS 24.237: "IP Multimedia subsystem (IMS) Service Continuity; Stage 3". +- [20] 3GPP TS 29.162: "Interworking between the IM CN subsystem and IP networks". +- [21] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". +- [22] 3GPP TS 22.153: "Multimedia Priority Service". +- [23] IETF RFC 5285: "A General Mechanism for RTP Header Extensions". +- [24] IETF RFC 6236: "Negotiation of Generic Image Attributes in the Session Description Protocol (SDP)". +- [25] IETF RFC 4975: "The Message Session Relay Protocol (MSRP)". + +- [26] IETF RFC 6714: "Connection Establishment for Media Anchoring (CEMA) for the Message Session Relay Protocol (MSRP)". +- [27] IETF RFC 4583: "Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams". +- [28] IETF RFC 5246: "The Transport Layer Security (TLS) Protocol Version 1.2". +- [29] IETF RFC 793: "Transmission Control Protocol – DARPA Internet Program – Protocol Specification". +- [30] IETF RFC 4145: "TCP-Based Media Transport in the Session Description Protocol (SDP)". +- [31] IETF RFC 4582: "The Binary Floor Control Protocol (BFCP)". +- [32] IETF RFC 6347: "Datagram Transport Layer Security Version 1.2". +- [33] IETF RFC 7345: "UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)". +- [34] IETF draft-schwarz-mmusic-sdp-for-gw-05: "SDP codepoints for gateway control". + +**Editor's note:** The above document cannot be formally referenced until it is published as an RFC. + +- [35] GSM Association RCC.07: "Rich Communication Suite 5.1 Advanced Communications Services and Client Specification, Version 2.0, 03 May 2013". +- [36] GSM Association RCC.07: "Rich Communication Suite 5.1 Advanced Communications Services and Client Specification, Version 3.0, 25 September 2013". +- [37] Void. +- [38] ITU-T Recommendation H.248.84 (07/2012): "Gateway control protocol: NAT-traversal for peer-to-peer services". +- [39] IETF RFC 5245: "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols". +- [40] IETF RFC 5389: "Session Traversal Utilities for NAT (STUN)". +- [41] IETF RFC 5766: "Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)". +- [42] IETF RFC 5763: "Framework for Establishing a Secure Real-time Transport Protocol (SRTP) Security Context Using Datagram Transport Layer Security (DTLS)". +- [43] IETF RFC 5764: "Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)". +- [44] 3GPP TS 24.371: "Web Real-Time Communications (WebRTC) client access to the IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification". +- [45] IETF RFC 6135: "An Alternative Connection Model for the Message Session Relay Protocol (MSRP)". +- [46] OMA-TS-CPM\_Conversation\_Function-V2\_0-20150113-C: "CPM Conversation Functions, Candidate Version 2.0 – 13 Jan 2015". +- [47] IETF RFC 5746: "Transport Layer Security (TLS) Renegotiation Indication Extension". +- [48] 3GPP TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)". +- [49] IETF RFC 7675: "Session Traversal Utilities for NAT (STUN) Usage for Consent Freshness". +- [50] IETF RFC 6716: "Definition of the Opus Audio Codec". +- [51] 3GPP TS 26.441: "Codec for Enhanced Voice Services (EVS); General Overview". + +- [52] 3GPP TS 26.445: "Codec for Enhanced Voice Services (EVS); Detailed Algorithmic Description". +- [53] IETF RFC 4566: "SDP: Session Description Protocol". +- [54] IETF RFC 4867: "RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs". +- [55] IETF RFC 4566: "SDP: Session Description Protocol". +- [56] IETF RFC 7587: "RTP Payload Format for the Opus Speech and Audio Codec". +- [57] IETF RFC 6544: "TCP Candidates with Interactive Connectivity Establishment (ICE)". +- [58] IETF RFC 4571: "Framing Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP) Packets over Connection-Oriented Transport". +- [59] IETF RFC 6947: "The Session Description Protocol (SDP) Alternate Connectivity (ALTC) Attribute". +- [60] IETF RFC 5761: "Multiplexing RTP Data and Control Packets on a Single Port". +- [61] IETF RFC 8831: "WebRTC Data Channels". +- [62] IETF RFC 8873: "Message Session Relay Protocol (MSRP)". +- [63] IETF RFC 4960: "Stream Control Transmission Protocol". +- [64] IETF RFC 8841: "Session Description Protocol (SDP) Offer/Answer Procedures for Stream Control Transmission Protocol (SCTP) over Datagram Transport Layer Security (DTLS) Transport". +- [65] IETF RFC 8864: "Negotiation Data Channels Using the Session Description Protocol (SDP)". +- [66] IETF RFC 5939: "Session Description Protocol (SDP) Capability Negotiation". +- [67] IETF RFC 6871: "Session Description Protocol (SDP) Media Capabilities Negotiation". +- [68] IETF RFC 4573: "MIME Type Registration for RTP Payload Format for H.224". +- [69] ITU-T Recommendation H.224 (01/2005): "A real time control protocol for simplex applications using the H.221 LSD/HSD/MLP channels". +- [70] ITU-T Recommendation H.281 (11/1994): "A far end camera control protocol for videoconferences using H.224". +- [71] IETF RFC 8858: "Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)". +- [72] IETF RFC 8035: "Session Description Protocol (SDP) Offer/Answer Clarifications for RTP/RTCP Multiplexing". +- [73] ITU-T Recommendation T.140 (02/98): "Text conversation presentation protocol". +- [74] IETF RFC 4103: "RTP Payload for Text Conversation". +- [75] IETF RFC 8865: "T.140 Real-Time Text Conversation over WebRTC Data Channels". +- [76] Void. +- [77] IETF RFC 4585: "Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback (RTP/AVPF)". +- [78] IETF RFC 5104: "Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)". +- [79] IETF RFC 7728: "RTP Stream Pause and Resume". + +- [80] IETF RFC 8122: "Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)". +- [81] IETF RFC 8842: "Session Description Protocol (SDP) Offer/Answer Considerations for Datagram Transport Layer Security (DTLS) and Transport Layer Security (TLS)". + +# --- 3 Definitions, symbols and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**End-to-access edge security:** media protection extending between an IMS UE and the first IMS core network node in the media path without being terminated by any intermediary node. + +**End-to-end security:** media protection between two IMS UEs without being terminated by any intermediary node. + +**Full ICE:** The full implementation of the Interactive Connectivity Establishment (ICE) specified in IETF RFC 5245 [39]. + +**ICE lite:** The lite implementation of the Interactive Connectivity Establishment (ICE) specified in IETF RFC 5245 [39]. + +**Local (near-end) NAPT control:** the operation of providing network address mapping information and NAPT policy rules to a near-end NAT in the media flow. + +**NAT-PT/NAPT-PT:** see definition in 3GPP TS 23.228 [2]. + +**NAPT control and NAT traversal:** controls network address translation for both near-end NA(P)T and far-end NA(P)T + +**Network Address Translation (NA(P)T):** see definition in 3GPP TS 23.228 [2]. + +**Remote (far-end) NAT traversal:** the operation of adapting the IP addresses so that the packets in the media flow can pass through a far-end (remote) NAT. + +**RTP / RTCP transport multiplexing:** a single IP transport (L4) port for RTP and RTCP packets. + +**TLS-client:** the entity that initiates a TLS session establishment to a server (see IETF RFC 5246 [28]). + +**TLS-server:** the entity that responds to requests for TLS session establishment from clients (see IETF RFC 5246 [28]). + +**TLS endpoint:** either a TLS-client or a TLS-server. + +### **Convention:** + +Wherever the **term NAT** is used in this specification, it may be replaced by **NA(P)T** or **NA(P)T-PT**. + +For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.237 [18] apply: + +- Access Leg** +- Access Transfer Control Function (ATCF)** +- Access Transfer Gateway (ATGW)** +- Remote Leg** +- Target Access Leg** +- Source Access Leg** + +## 3.2 Symbols + +For the purposes of the present document, the following symbols apply: + +Iq                      Interface between the IMS Application Level Gateway and the IMS Access Media Gateway + +## 3.3 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|---------------|-------------------------------------------------------------------------------| +| ALTC | Alternate Connectivity | +| AMR | Adaptive Multi-Rate | +| AMR-WB | Adaptive Multi-Rate - WideBand | +| AMR-WB IO | Adaptive Multi-Rate - WideBand Inter-operable Mode, included in the EVS codec | +| APP | APplication-defined RTCP packet | +| ATCF | Access Transfer Control Function | +| ATGW | Access Transfer Gateway | +| BFCP | Binary Floor Control Protocol | +| CCM | Codec Control Messages | +| CVO | Coordination of Video Orientation | +| DBI | Delay Budget Information | +| DC | Data Channel | +| DTLS | Datagram Transport Layer Security | +| DTX | Discontinuous Transmission | +| e2ae security | End-to-access-edge security | +| e2e security | End-to-end security | +| ECN | Explicit Congestion Notification | +| ECN-CE | ECN Congestion Experienced | +| eIMS-AGW | IMS Access Gateway enhanced for WebRTC | +| eP-CSCF | P-CSCF enhanced for WebRTC | +| EVS | Enhanced Voice Services | +| FECC | Far End Camera Control | +| FIR | Full Intra Request | +| GTT | Global Text Telephony | +| ICE | Interactive Connectivity Establishment | +| IMS-AGW | IMS Access Media Gateway | +| IMS-ALG | IMS Application Level Gateway | +| IM CN | IMS Core Network | +| MSRP | Message Session Relay Protocol | +| MTSI | Multimedia Telephony Service for IMS | +| NA(P)T | Network Address and optional Port Translation | +| NAPT | Network Address Port Translation | +| NAT | Network Address Translation | +| NA(P)T-PT | NAT Address (and optional Port-) Translation and Protocol Translation | +| P-CSCF | Proxy-CSCF | +| ROI | Region of Interest | +| RTCP | RTP Control Protocol | +| RTP | Real-time Transport Protocol | +| SDPCapNeg | SDP Capability Negotiation | +| SRTP | Secure Real-time Transport Protocol | +| SRVCC | Single Radio Voice Call Continuity | +| STUN | Session Traversal Utilities for NAT | +| TLS | Transport Layer Security | +| TMMBN | Temporary Maximum Media Stream Bit Rate Notification | +| TMMBR | Temporary Maximum Media Stream Bit Rate Request | +| TURN | Traversal Using Relay NAT | +| UDPTL | User Datagram Protocol Transport Layer | +| URN | Uniform Resource Name | +| WebRTC | Web Real-Time Communication | +| WIC | WebRTC IMS Client | + +# 4 Architecture + +## 4.1 Reference architecture + +The reference architecture for the IMS-ALG and the IMS-AGW when NAT is invoked between the UE and the IMS domain is shown in figure 4.1.1 below. + +![Figure 4.1.1: Reference Architecture with NAT invoked between the UE and the IMS domain. The diagram shows a UE connected to an IP-CAN, which is connected to a NAT device. The NAT device is connected to an IMS Access Gateway (IMS-AGW) via a Media Access domain. The IMS-AGW is connected to a P-CSCF via an Iq interface. The P-CSCF contains an IMS-ALG. The IMS-ALG is connected to an IMS I/S-CSCF SCC AS via Mw/Mx interfaces. A Gm interface is shown between the UE and the P-CSCF, passing through the NAT device.](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) + +Figure 4.1.1: Reference Architecture with NAT invoked between the UE and the IMS domain. The diagram shows a UE connected to an IP-CAN, which is connected to a NAT device. The NAT device is connected to an IMS Access Gateway (IMS-AGW) via a Media Access domain. The IMS-AGW is connected to a P-CSCF via an Iq interface. The P-CSCF contains an IMS-ALG. The IMS-ALG is connected to an IMS I/S-CSCF SCC AS via Mw/Mx interfaces. A Gm interface is shown between the UE and the P-CSCF, passing through the NAT device. + +**Figure 4.1.1: Reference Architecture with NAT invoked between the UE and the IMS domain** + +See 3GPP TS 23.228 [2] Annexes G.1 and G.2 for a comprehensive description of the reference models. + +The reference architecture for the IMS-ALG and the IMS-AGW supporting the ATCF/ATGW function is shown in figure 4.1.2 below. + +![Figure 4.1.2: Reference Architecture for IMS-ALG/IMS-AGW with ATCF/ATGW function. The diagram shows a UE connected to a CS access (via an MSC Server) and an IP-CAN (via an MGW). The MSC Server is connected to a P-CSCF (containing an IMS-ALG (ATCF)) via Mw/12 interfaces. The MGW is connected to an IMS-AGW (ATGW) via a Media Access domain. The IMS-AGW is connected to the P-CSCF via an Iq interface. The P-CSCF is connected to an IMS I/S-CSCF SCC AS via Mw/Mx interfaces. Red arrows indicate 'Access Transfer' from the MGW to the IMS-ALG (ATCF) and from the IMS-AGW (ATGW) to the IMS-ALG (ATCF). A Gm interface is shown between the UE and the P-CSCF, passing through the NAT device.](18722c46c9e8475524e634dedd08bac2_img.jpg) + +Figure 4.1.2: Reference Architecture for IMS-ALG/IMS-AGW with ATCF/ATGW function. The diagram shows a UE connected to a CS access (via an MSC Server) and an IP-CAN (via an MGW). The MSC Server is connected to a P-CSCF (containing an IMS-ALG (ATCF)) via Mw/12 interfaces. The MGW is connected to an IMS-AGW (ATGW) via a Media Access domain. The IMS-AGW is connected to the P-CSCF via an Iq interface. The P-CSCF is connected to an IMS I/S-CSCF SCC AS via Mw/Mx interfaces. Red arrows indicate 'Access Transfer' from the MGW to the IMS-ALG (ATCF) and from the IMS-AGW (ATGW) to the IMS-ALG (ATCF). A Gm interface is shown between the UE and the P-CSCF, passing through the NAT device. + +**Figure 4.1.2: Reference Architecture for IMS-ALG/IMS-AGW with ATCF/ATGW function** + +See 3GPP TS 23.237 [18] clause 5.2 for a comprehensive description of the reference model. + +The reference architecture for the IMS-ALG and IMS-AGW supporting Interactive Connectivity Establishment (ICE) is shown in figure 4.1.3, for the case when both the signalling and media traverses NAT devices. There might be an ICE process towards access network domain and/or an ICE process towards core network domain. Both ICE processes are independent of each other. The network entities that support Session Traversal Utilities for NAT (STUN) and Traversal Using Relays NAT (TURN) are described in IETF RFC 5389 [40] and IETF RFC 5766 [41] respectively. + +![Figure 4.1.3: Reference architecture for ICE. This diagram shows a User Equipment (UE) connected to a NAT/FW. The UE contains an 'Outbound support' block and an 'ICE support' block with a 'STUN Client/Server'. The NAT/FW is connected to a 'TURN server' and a 'STUN Server'. The 'TURN server' and 'STUN Server' are connected to a 'Media in access domain' circle. This circle is connected to a 'P-CSCF' block which contains 'IMS-ALG (ATCF)' and 'ICE support' blocks. The 'P-CSCF' is connected to an 'IMS I/S-CSCF SCC AS' via an 'Mw/Mx' interface. The 'P-CSCF' is also connected to an 'IMS-AGW (ATGW)' block via an 'Iq' interface. The 'IMS-AGW (ATGW)' contains 'STUN Client/Server' blocks and is connected to a 'Media in CN domain' circle.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +Figure 4.1.3: Reference architecture for ICE. This diagram shows a User Equipment (UE) connected to a NAT/FW. The UE contains an 'Outbound support' block and an 'ICE support' block with a 'STUN Client/Server'. The NAT/FW is connected to a 'TURN server' and a 'STUN Server'. The 'TURN server' and 'STUN Server' are connected to a 'Media in access domain' circle. This circle is connected to a 'P-CSCF' block which contains 'IMS-ALG (ATCF)' and 'ICE support' blocks. The 'P-CSCF' is connected to an 'IMS I/S-CSCF SCC AS' via an 'Mw/Mx' interface. The 'P-CSCF' is also connected to an 'IMS-AGW (ATGW)' block via an 'Iq' interface. The 'IMS-AGW (ATGW)' contains 'STUN Client/Server' blocks and is connected to a 'Media in CN domain' circle. + +NOTE 1: If the IMS-AGW only supports ICE lite, it will only contain a STUN server. + +NOTE 2: The IMS-AGW and IMS-ALG may support ICE only towards the served UE, and will then only contain a STUN client/server and ICE support on related terminations. + +NOTE 3: The TURN server is a deployment option but not required for all ICE deployments. + +NOTE 4: The separate STUN server is used by the served UE while it gathers ICE candidates. The STUN server in the IMS-AGW is used to answer ICE connectivity checks. + +**Figure 4.1.3: Reference architecture for ICE** + +The reference architecture for the P-CSCF enhanced for WebRTC (eP-CSCF) and the IMS-AGW enhanced for WebRTC (eIMS-AGW) to support WebRTC client access to IMS is shown in figure 4.1.4 as below, see Annex U in 3GPP TS 23.228 [2] for a comprehensive description of the reference model. + +![Figure 4.1.4: Reference Architecture for eP-CSCF/eIMS-AGW supporting WebRTC access to IMS. This diagram shows a UE connected to a NAT/P-CAN/PCEF block. The UE contains a 'WIC' block. The NAT/P-CAN/PCEF block is connected to a 'WWSF' block via a 'W1' interface. The 'WWSF' block is connected to a 'WAF' block via a 'W4' interface. The 'WAF' block is connected to an 'eP-CSCF' block via a 'W5' interface. The 'eP-CSCF' block contains an 'IMS-ALG' block and is connected to an 'I/S-CSCF' block via an 'Mw' interface. The 'eP-CSCF' block is also connected to an 'H/V-PCRF' block via an 'Rx' interface. The 'H/V-PCRF' block is connected to the 'NAT/P-CAN/PCEF' block via a 'Gx' interface. The 'eP-CSCF' block is also connected to an 'eIMS-AGW' block via an 'Iq' interface. The 'eIMS-AGW' block is connected to the 'NAT/P-CAN/PCEF' block via a 'W3' interface.](f57a881fcbcaf494a7dedc4f61224991_img.jpg) + +Figure 4.1.4: Reference Architecture for eP-CSCF/eIMS-AGW supporting WebRTC access to IMS. This diagram shows a UE connected to a NAT/P-CAN/PCEF block. The UE contains a 'WIC' block. The NAT/P-CAN/PCEF block is connected to a 'WWSF' block via a 'W1' interface. The 'WWSF' block is connected to a 'WAF' block via a 'W4' interface. The 'WAF' block is connected to an 'eP-CSCF' block via a 'W5' interface. The 'eP-CSCF' block contains an 'IMS-ALG' block and is connected to an 'I/S-CSCF' block via an 'Mw' interface. The 'eP-CSCF' block is also connected to an 'H/V-PCRF' block via an 'Rx' interface. The 'H/V-PCRF' block is connected to the 'NAT/P-CAN/PCEF' block via a 'Gx' interface. The 'eP-CSCF' block is also connected to an 'eIMS-AGW' block via an 'Iq' interface. The 'eIMS-AGW' block is connected to the 'NAT/P-CAN/PCEF' block via a 'W3' interface. + +**Figure 4.1.4: Reference Architecture for eP-CSCF/eIMS-AGW supporting WebRTC access to IMS** + +NOTE 1: The presence of dashed elements in the figure depends on the configuration. + +PCC functional elements are present only for EPC access with QoS. + +The corresponding PCC elements for fixed access are also optionally supported but not shown. + +The NAT in figure 4.1.4 is meant for non-cellular access to IMS. + +## 4.2 NAT Function + +An operator may need NAT function between UE and IMS domain. Such function can be provided by the IMS-AGW and can be called local (near-end) NAT or IM CN hosted NAT (see clause 5.2). There can also be an independent NAT device between UE and IMS domain (see clause 5.4), referred as remote (far end) NAT. Thus the IMS-AGW shall support remote NA(P)T traversal. + +Figure 4.1.1 illustrates the particular IP media-path scenario with both a remote NAT and local NAT function. Each NAT function is partitioning an IP domain into two address domains, or partitioning the used IP address space (realm) into two realms. + +The reference architecture of Figure 4.1.1 may be mapped on various network scenarios, like e.g. to three IPv4 realms, indicated by a) IP-CAN (connectivity access network), b) (Media) Access Domain and c) (Media) IM CN domain. If there would not be any remote NAT device between the UE and IMS-AGW, then there would be just two IP domains (a and c). + +The two types of NATs are also typically different from control perspective: local (near-end) NAT can be controlled by the operators directly, and remote (far-end) NAT that cannot be controlled by the operators directly. + +The support of local NAT is thus implicitly leading to the requirement for IP realm indication at Iq (see clause 5.3). + +The edge node of the IP-CAN may be a remote (far-end) NAT device (see Figure 4.1.1). This NAT device provides NAT or NAPT or NA(P)T-PT for IP traffic in the media-path and signalling path (e.g. IP network addresses and possibly L4 transport port values may be translated of SIP Gm messages). + +The remote NAT device cannot be directly controlled by the operators of the (Media) Access and IP CN domain. The IMS-ALG is consequently lacking the direct information with regards to the applied NAT bindings by the remote NAT device. + +## 4.3 ATCF/ATGW Function + +The ATCF/ATGW functions may be supported by the IMS-ALG/IMS-AGW when SRVCC enhanced with ATCF is used. In this case, the Iq reference point is used for IMS sessions that the IMS-ALG (ATCF) decides to anchor at the IMS-AGW (ATGW) to provide the following functions: + +- reservation and configuration of IMS-AGW (ATGW) resources for media anchoring during PS session origination or termination; +- reconfiguration of IMS-AGW (ATGW) resources during access transfer to the CS domain; +- release of IMS-AGW (ATGW) resources upon completion of the access transfer or release of the session; +- media transcoding if the media that was used prior to the access transfer is not supported by the MSC server; +- IP version interworking if different IP versions are used between the access and the remote legs; +- Indication of IP realm during allocation of transport addresses/resources (the PS and CS accesses may be reachable via different IP realms); +- the ability to configure ECN properties towards the transferred to Access if ECN is supported/requested; +- the ability to reconfigure the ECN mode e.g. from ECN transparent to ECN endpoint towards the IMS CN if ECN transparent cannot be maintained after access transfer to the CS domain; +- provide priority treatment to calls identified as Multimedia Priority Service (see 3GPP TS 22.153 [22]). + +See 3GPP TS 23.237 [18] and 3GPP TS 24.237 [19] for a comprehensive description of the ATCF and ATGW functions. + +## 4.4 eP-CSCF/eIMS-AGW Function + +The Iq reference point is used between the P-CSCF enhanced for WebRTC (eP-CSCF) and the IMS-AGW enhanced for WebRTC (eIMS-AGW), with the following additional functions: + +- media plane interworking extensions as needed for WICs; +- media security of type "e2ae" (as specified in 3GPP TS 33.328 [12]) for media protocols specific to WebRTC, including media consent, and DTLS-SRTP as key exchange mechanism for media components using SRTP; +- media security of type "e2ae" (as specified in 3GPP TS 33.328 [12]) for data channels using DTLS-SCTP. + +- NAT traversal support including ICE; +- the ability to perform any transcoding needed for audio and video codecs supported by the browser; and +- transport level interworking between data channels and other transport options supported by IMS. + +See 3GPP TS 23.228 [2] Annex U for a comprehensive description of the eP-CSCF and eIMS-AGW functions. + +# --- 5 Functional Requirements + +## 5.1 General + +A single IMS-ALG may control one or multiple IMS-AGW(s). + +## 5.2 Gate Control & Local NAT + +The IMS-ALG shall provide the NAPT control function, i.e. obtain the address binding information (according to IETF RFC 2663 [4]) and perform the NAPT policy control along with gate control (i.e. instruct the opening/closing of a gate). + +The IMS-ALG shall request the IMS-AGW to allocate transport addresses/resources to enable media to traverse the IMS-AGW. The IMS-ALG may indicate the corresponding IP realm to the IMS-AGW – see clause 5.3. The IMS-AGW shall provide the corresponding external transport addresses to the IMS-ALG. + +Terminations for the Iq interface may be pre-defined with different levels of granularity for specific IP ports, interfaces, or groups of interfaces. These may then be defined as an IP realm (see clause 5.3) known by both the IMS-ALG and the IMS-AGW, however IP Realms may also be defined for multiple physical interfaces. In order to efficiently report a failure affecting a large number of terminations associated to specific physical interfaces, the IMS-AGW shall, when allocating a new termination, return to the IMS-ALG an associated Interface ID. + +An IMS-AGW not supporting this procedure may allocate the same Interface ID for all IP terminations. + +An IMS-AGW supporting the Termination Out-of-Service procedure (see clause 6.1.15) shall maintain a local mapping of Interface ID to its internal resources. + +The IMS-AGW shall provide the NAPT enforcement function, i.e. change the address and port number of the media packets as they traverse the IMS-AGW, along with gate control (i.e. open/close a gate under the control of the IMS-ALG). + +The IMS-AGW may provide IP version interworking. If the IP version interworking is performed and the IMS-ALG passes an SDP offer or answer, the IMS-ALG may adjust any SDP bandwidth information contained in the SDP offer or answer in accordance with 3GPP TS 29.162 [20] clause 9.1.5. + +The IMS-ALG shall request the IMS-AGW to release its transport resources at the end of a session. + +## 5.3 IP realm indication and availability + +The IMS-ALG and the IMS-AGW shall support IP realm indication. + +The IMS-ALG, when requesting the allocation of transport resources at the IMS-AGW, may indicate the correspondent IP realm to the IMS-AGW. The IMS-AGW shall assign the IP termination in the IP realm indicated. The same IP realm shall be applied to all media streams associated with the termination. The IP realm identifier cannot be changed after the initial assignment. + +A default IP realm may be configured such that if the IMS-AGW has not received the IP realm identifier and the IMS-AGW supports multiple IP realms then the default IP realm shall be used. + +In order to prevent the IMS-ALG requesting an unavailable IP Realm, the IMS-ALG may audit the list of currently available realms on the IMS-AGW and may request the IMS-AGW to report any changes to that list as they occur over time. + +The monitoring of IP realm availability is optional and if supported by IMS-AGW may be requested by the IMS-ALG. + +## 5.4 Remote NAT traversal support + +The IMS-ALG and the IMS-AGW shall support remote NA(P)T traversal support using procedures according to the present clause. In addition they may support remote NA(P)T traversal support using Interactive Connectivity Establishment (ICE) according to clause 5.17. + +The IMS-ALG is responsible for determining whether there is a remote NAT device (the mechanism by which this achieved is out of scope of the current document). + +If a remote NAT device is present, the IMS-ALG shall request the IMS-AGW to perform latching or re-latching when requesting the IMS-AGW to reserve transport addresses/resources. + +If remote NAT is applicable, the IMS-AGW shall not use the remote media address/port information (supplied by the IMS-ALG) as the destination address for outgoing media. Instead, the IMS-AGW shall dynamically learn the required destination address via the source address/port of incoming media. This mechanism is known as "latching". + +When remote NAT Traversal is applied to a stream associated with multiple flows (e.g. RTP and RTCP), the IMS-AGW shall perform individual latching and/or re-latching on the various flows. This means that an RTP and an RTCP flow of a single stream can be latched to different remote addresses and/or ports. + +## 5.5 Remote Source Address/Port Filtering + +The IMS-ALG may support and the IMS-AGW shall support policing of the remote source address/port of incoming media flow(s). + +The IMS-ALG may determine that the source address/port of received media packets should be policed. + +When the IMS-ALG requests the IMS-AGW to reserve transport addresses/resources, the IMS-ALG may indicate to the IMS-AGW that policing of source address and/or port of received media packets is required. + +If such policing is applicable, the IMS-AGW shall check the source address and/or port of all received media packets and silently discard any packets that do not conform to the expected source address and/or port. + +## 5.6 Traffic Policing + +The IMS-ALG may support traffic policing of incoming media flows. + +The IMS-AGW shall support traffic policing of the maximum average bitrate, defined as sustainable data rate (see IETF RFC 2216 [10]) of incoming media flows and may support traffic policing of the peak data rate of incoming media flows. + +The IMS-ALG may require the IMS-AGW to police the media flows to ensure that they conform to the expected data rates. + +When the IMS-ALG requests the IMS-AGW to reserve transport addresses/resources, the IMS-ALG may indicate to the IMS-AGW that policing of the related media streams is required and provide traffic policing related parameters as detailed in clause 6.2.5. + +If such policing is requested, the IMS-AGW shall police the corresponding media streams as detailed in clause 6.2.5 by measuring the data rate for the received packets within that media stream. If the permissible data rate provided by the IMS-ALG is exceeded, the IMS-AGW shall discard packets to reduce their data rate to the permissible data rate. + +For RTP flows where RTCP resources are reserved together with the RTP resources (see clause 5.9), the permissible data rate shall include the bandwidth used by RTP and RTCP together. + +## 5.7 Hanging Termination Detection + +The IMS-ALG and the IMS-AGW shall support detection of hanging termination. + +The IMS-ALG, when requesting the IMS-AGW to reserve an AGW connection point, shall indicate to the IMS-AGW to perform detection of hanging terminations. + +The IMS-AGW shall determine a termination to be hanging if there is no signalling sent/received within a specified period. + +On being informed of the hanging termination, the IMS-ALG shall check/determine whether the cited termination is valid and initiate any appropriate corrective action, e.g. release an invalid termination. + +## 5.8 QoS Packet Marking + +The IMS-ALG may support and the IMS-AGW shall support control via the Iq interface of the setting of the DiffServ Code Point (DSCP) for media packets sent on a termination. + +When the IMS-ALG requests the IMS-AGW to reserve transport addresses/resources, the IMS-ALG may indicate to the IMS-AGW that the DSCP of outgoing media packets shall be explicitly set or copied from the DSCP of the corresponding received packet. + +If such modification of the DSCP is required by the IMS-ALG, the IMS-AGW shall set the DSCP for outgoing packets on a termination. + +## 5.9 Handling of RTCP streams + +### 5.9.1 General + +The IMS-ALG and the IMS-AGW shall support control via the Iq interface of the specific RTCP behaviour associated to an RTP flow. + +When the IMS-ALG requests the IMS-AGW to reserve transport addresses/resources for an RTP flow, the IMS-ALG should also request the IMS-AGW to reserve resources for the corresponding RTCP flow, but may alternatively request the IMS-AGW not to reserve resources for the corresponding RTCP flow. When the IMS-ALG requests the IMS-AGW to reserve transport addresses/resources for a non-RTP flow, the IMS-ALG shall not request the IMS-AGW to reserve resources for an RTCP flow. + +To request the IMS-AGW to reserve resources for an RTCP flow, the IMS ALG shall provide the RTCP handling information element with a value indicating that resources for RTCP shall be reserved. + +To request the IMS-AGW not to reserve resources for an RTCP flow, the IMS ALG shall either provide the RTCP handling information element with a value indicating that resources for RTCP shall not be reserved or omit the RTCP handling information element. + +If the IMS-AGW receives the indication to reserve RTCP resources, the IMS-AGW shall allocate a local port with even number for an RTP flow and shall allocate the consecutive local port with odd number for the associated RTCP flow, and it shall send and be prepared to receive RTCP packets. + +If the IMS-AGW receives the indication to not reserve RTCP resources, or if it does not receive any indication at all, it shall not allocate an RTCP port when allocating a port for an RTP flow. The IMS-AGW shall not send any RTCP packets and shall silently discard any received RTCP packets. + +When RTCP resources are requested, the IMS-ALG may also specify: + +- the explicit RTCP transport address information element containing the remote RTCP port, and optionally the remote address, where to send RTCP packets; if not specified, the IMS-AGW shall send RTCP packets to the port contiguous to the remote RTP port; and +- bandwidth allocation requirements for RTCP, if the RTCP bandwidth level for the session is different than the default RTCP bandwidth as specified in RFC 3556 [6]. + +The explicit RTCP transport address information element contains the "a=rtcp" SDP attribute (as specified in IETF RFC 3605 [7]) received within the SDP body. The explicit RTCP transport address information element is only allowed for remote endpoints and shall not be used for the local endpoint. When the IMS-ALG requests the IMS-AGW to reserve resources for an RTCP flow and provides in addition the explicit RTCP port information element, then the + +IMS-AGW shall use this network address and transport port as destination when sending RTCP packets towards the remote endpoint. + +The IMS-AGW shall return an error if it can not allocate the requested RTCP resources. + +### 5.9.2 RTP/RTCP transport multiplexing + +The procedure in clause 5.9.1 describing the default case of RTP/RTCP transport non-multiplexed scenarios may be extended for the transport multiplexed mode by addition of the RTP/RTCP transport multiplexing information element to indicate to the IMS-AGW that RTP and RTCP traffic shall be multiplexed on a single port (as described in IETF RFC 5761 [60]). The RTP/RTCP transport multiplexing information element may only be sent to the IMS-AGW in combination with the RTCP handling information element with the value indicating that resources for RTCP shall be reserved. The support of these procedures is optional for the IMS ALG and the IMS-AGW. The IMS-ALG shall only use these procedures when knowing support at IMS-AGW side (e.g., via configuration management). + +The usage is conditional, given by following restrictions: + +- 1) The transport multiplexed mode may be only supported for terminations at the access network side of the IMS-AGW. +- 2) The transport multiplexed mode shall be only enabled for the local connection endpoint if agreed via SIP SDP offer/answer negotiation with the served UE using: + - the "a=rtp-mux" SDP attribute, see IETF RFC 5761 [60], as updated by IETF RFC 8035 [72]; and/or + - the "a=rtp-mux-only" SDP attribute, see IETF RFC 8858 [71]. + +NOTE 1: Usage of an "rtp-mux-only" attribute in an SDP answer is forbidden, see IETF RFC 8858 [71]. If the associated SDP answer does not contain an SDP "rtp-mux" attribute, the offerer (the IMS ALG or the UE) needs to disable the associated RTP based media by sending a new SDP offer: + +- with a zero port value associated with the SDP media description ("m=" line); or +- without associating an SDP "rtp-mux-only" attribute with the SDP media description ("m=" line). + +- 3) When transport multiplexed mode is agreed with the served UE, then it may be applied in both traffic directions. + +NOTE 2: The last two conditions enforce a symmetrical usage of RTP/RTCP transport multiplexing in the related network domain (here the access network). + +## 5.10 Media Inactivity Detection + +The IMS-ALG and the IMS-AGW may support the detection of inactive media flows. + +The IMS-ALG may require an IMS-AGW that supports media inactivity detection to detect if a media flow is inactive. + +NOTE: The decision to apply or not media inactivity is general for all sessions with the same media characteristics (i.e. not user specific). It is for further study under which conditions inactivity media detection may be requested. + +When the IMS-ALG requests the IMS-AGW to reserve transport addresses/resources, the IMS-ALG may indicate to the IMS-AGW that detection of an inactive media flow is required and may additional specify inactivity detection time and inactivity detection direction. + +The IMS-AGW shall determine a media flow on termination to be inactive if there is no media sent and/or received within the inactivity detection time period. + +On being informed of the inactive media, the IMS-ALG shall initiate any appropriate corrective action. + +## 5.11 IMS Media Plane Security + +### 5.11.1 General + +The IMS-ALG and the IMS-AGW may support IMS media plane security as specified in 3GPP TS 33.328 [12]. They may support end-to-access edge security, or end-to-end security, or both, for + +- RTP based media (such as e.g. audio, video information) using SRTP security, and/or +- TCP based media (such as MSRP and BFCP) using TLS security; and/or +- UDP based media (such as T.38 fax over UDPTL/UDP) using DTLS security. + +If supported the IMS-ALG and the IMS-AGW shall use the procedures in the following clauses. + +NOTE: For the support of end-to-end security, the presence of an IMS-ALG is not required. + +Procedures for the IMS-ALG to determine if end-to-access edge security or end-to-end security is applicable to a session are specified in 3GPP TS 33.328 [12] and 3GPP TS 24.229[11]. + +### 5.11.2 End-to-access-edge Security + +#### 5.11.2.1 End-to-access-edge security for RTP based media using SDES + +Procedures for the IMS-ALG to determine if end-to-access edge security is applicable to RTP based media and to exchange cryptography related SDP parameters with the served UE during the SIP session setup are specified in 3GPP TS 33.328 [12] and 3GPP TS 24.229[11]. + +For media lines that can be subject to e2ae security, the IMS-ALG will receive "RTP/AVP" or "RTP/AVPF" as transport protocol in SDP from the core network. When the IMS-ALG determines that e2ae security is applicable, it will indicate "RTP/SAVP" (see IETF RFC 3711 [14]) or "RTP/SAVPF" (see IETF RFC 5124 [15]), respectively, as transport protocol in the corresponding SDP media lines send towards the served UE. When e2ae security is applied, the IMS-ALG will also receive "RTP/SAVP" or "RTP/SAVPF" in SDP from the served UE. The IMS-ALG will then indicate "RTP/AVP" or "RTP/AVPF" respectively, as transport protocol in the corresponding SDP media lines send towards the core network. When the IMS-ALG requests the IMS-AGW to reserve transport addresses/resources for media to which e2ae security is applicable, the IMS ALG shall configure "RTP/SAVP" or "RTP/SAVPF" as transport protocol at the access side termination. The IMS ALG shall configure "RTP/AVP" or "RTP/AVPF" as transport protocol at the core network side termination for media where e2ae security is applicable. + +When the IMS-ALG determines that e2ae security is applicable, it will generate appropriate cryptographic context parameters, in particular key(s), and will transfer them to the served UE within SDES SDP "crypto" attribute(s) according to IETF RFC 4568 [13]. The IMS-ALG will also receive cryptographic context parameters, in particular key(s), from the served UE within SDES SDP "crypto" attribute(s). When the IMS-ALG requests the IMS-AGW to reserve or configure transport addresses/resources for media to which e2ae security is applicable, the IMS-ALG shall provide cryptography related parameters as SDES SDP "crypto" attributes applicable at the access side termination. + +On the originating side of the SIP session setup, the IMS-ALG shall provide as "Remote cryptographic SDES attribute" the SDES crypto attribute it selected from the ones received from the IMS UE in the SDP Offer . The IMS-ALG shall provide as "Local cryptographic SDES attribute" the SDES crypto attribute the IMS-ALG generated and inserted in the SDP Answer sent to IMS UE. + +On the terminating side of the SIP session setup, the IMS-ALG shall provide as "Remote cryptographic SDES attribute" the SDES crypto attribute received from the IMS UE in the SDP Answer. The IMS-ALG shall provide as "Local cryptographic SDES attribute" the SDES crypto attribute selected by the UE from the ones the IMS-ALG generated and inserted in the SDP Offer sent to UE. If the IMS-ALG offers only one SDES crypto attribute to the UE, the IMS-ALG may provide this attribute as "Local cryptographic SDES attribute" within the Reserve AGW Connection Point Procedure before receiving the SDP answer from the UE. In the present release, a modification of an established e2ae crypto session is not supported. Thus, the IMS-ALG shall not modify any previously provided "Local cryptographic SDES attribute" or "Remote cryptographic SDES attribute". + +If the IMS-ALG applies e2ae media security for a media stream and receives an SDP bandwidth modifier related to that media stream in SIP/SDP signalling, it should modify this bandwidth modifier to adjust the bandwidth overhead due to + +e2ae security before forwarding the SDP. The IMS-ALG should add the bandwidth overhead caused by e2ae media security to the bandwidth information received from the remote peer. The IMS-ALG should subtract the bandwidth overhead caused by e2ae media security from the bandwidth information received from the served UE. + +The IMS Access GW shall, upon reception of an SDES crypto attribute, establish an SRTP security context (as described in RFC 4568 [13] and RFC 3711 [14]) and be prepared to convert RTP packets to SRTP packets and vice versa, using the corresponding SRTP security contexts. + +#### 5.11.2.2 End-to-access-edge security for TCP based media using TLS + +### 5.11.2.2.1 General + +E2ae security for TCP based media using TLS is applicable for MSRP (see IETF RFC 4975 [25]; used in IMS session-based messaging) and BFCP (see IETF RFC 4582 [31]; used in IMS conferencing). The IMS-ALG and IMS-AGW may support e2ae security for MSRP, BFCP, or both protocols. + +E2ae protection of MSRP and BFCP media is based on TLS, according to the TLS profile specified in Annex E of 3GPP TS 33.310 [48] and Annex M of 3GPP TS 33.328 [12]. TLS shall be supported over the TCP transport (see IETF RFC 793 [29]). + +Key management for e2ae protection of MSRP and BFCP is based on the ciphersuites and session keys negotiated via the TLS handshake protocol between the UE and the IMS-AGW (see 3GPP TS 33.328 [12]). + +Procedures for the IMS-ALG to determine if e2ae security for MSRP and/or BFCP is applicable to a session and to exchange the cryptographic information (i.e. certificate fingerprints, see IETF RFC 8122 [80]) over SDP with the served UE during the SIP session setup are specified in 3GPP TS 33.328 [12] and 3GPP TS 24.229 [11]. If e2ae security is not required, the e2e security procedures may apply, see clause 5.11.3. + +According to the TLS profile specified in Annex E of 3GPP TS 33.310 [48], the IMS-AGW shall accept TLS renegotiation only if it is secured according to IETF RFC 5746 [47]. + +NOTE 1: IETF RFC 5746 [47] defines a "TLS secure renegotiation" procedure, which leaves the definition of a basic TLS renegotiation still open. H.248 based support to enable the IMS-ALG to allow or not allow the IMS-AGW to perform client initiated or server initiated TLS renegotiation is not addressed in the present release. The behaviour of the IMS-AGW for "TLS session renegotiation" procedure is hence not further defined in the present release. + +If the IMS-ALG applies e2ae media security for a media stream and receives an SDP bandwidth modifier related to that media stream in SIP/SDP signalling, it should modify this bandwidth modifier to adjust the bandwidth overhead due to e2ae security before forwarding the SDP. The IMS-ALG should add the bandwidth overhead caused by e2ae media security to the bandwidth information received from the remote peer. The IMS-ALG should subtract the bandwidth overhead caused by e2ae media security from the bandwidth information received from the served UE. + +For each MSRP or BFCP media stream to be set-up with e2ae security, the P-CSCF (IMS-ALG) shall: + +- include the IMS-AGW in the media path and allocate the required resources for the media stream in the IMS-AGW; +- request a certificate fingerprint from the IMS-AGW; +- include the certificate fingerprint received from the IMS-AGW in the SDP it sends to the IMS UE; +- send the certificate fingerprint(s) received in the SDP from the IMS UE to the IMS-AGW; +- instruct the IMS-AGW to perform state-aware TCP handling by including information about the TCP setup direction; +- for each termination determine via SDP negotiation as specified in IETF RFC 4145 [30] if the IMS-AGW needs to act as TCP client or server for the terminations towards the core network and towards the access network; +- indicate to the IMS-AGW how to perform the TCP connection establishment by: + - a) either instructing the IMS-AGW to start a TCP connection establishment on any terminations where it needs to act as TCP client; or + +- b) indicating to the IMS-AGW to use an incoming TCP connection establishment request at one termination as a trigger to send a TCP connection establishment request at the interconnected termination in the same context (support of this alternative is optional for the IMS-AGW and IMS-ALG); +- determine via SDP negotiation if the IMS-AGW needs to act as TLS client or server as specified in the clauses below; + +NOTE 2: The determination of the TLS client/server role relies on different rules for MSRP and BFCP. + +- if the IMS-AGW needs to act as TLS client, request the IMS-AGW to start the TLS session setup once the TCP connection is established towards the UE; and +- apply additional specific procedures for MSRP in clause 5.11.2.2.2 or for BFCP in clause 5.11.2.2.3. + +For each MSRP or BFCP media stream to be set-up with e2ae security the IMS-AGW shall: + +- upon request from the IMS-ALG, select an own certificate for the media stream, uniquely associate own certificate with the media stream, and send the fingerprint of the own certificate to the IMS-ALG; +- uniquely associate the certificate fingerprint(s) received from the IMS-ALG with the corresponding MSRP or BFCP media stream, and subsequently use the certificate fingerprint(s) (as described in IETF RFC 4975 [25]) to verify the establishment of the TLS session of the corresponding media stream to belong to the served user; +- if the verification of the remote certificate fingerprint(s) during the TLS session establishment fails, regard the remote TLS endpoint as not authenticated, terminate the TLS session and report the unsuccessful TLS session setup to the IMS-ALG; +- negotiate the TLS protocol configurations with the TLS peer based on locally provisioned TLS profile parameters; +- when the TLS session has been established, convert unprotected media received from the network to protected media to send to the served UE and vice versa; +- be capable to support both the TLS server and TLS client roles; +- when being instructed to start the TLS session setup, act as a TLS client and establish the TLS session as soon as the underlying TCP bearer connection is established; +- upon instruction of the IMS-ALG to perform state-aware TCP handling, not forward any TCP connection establishment request received on one termination towards the interconnected termination; +- upon corresponding instructions from the IMS-ALG, start a TCP connection establishment on the indicated termination by sending a TCP SYN, or use an incoming TCP connection establishment request received at one termination as a trigger to send a TCP connection establishment request at the interconnected termination in the same context; +- release the underlying TCP bearer connection as soon as the TLS session is released; and +- apply additional specific procedures for MSRP in clause 5.11.2.2.2 or for BFCP in clause 5.11.2.2.3. + +#### 5.11.2.2.2 e2ae security for session based messaging (MSRP) + +For each MSRP media stream outside WebRTC data channels requiring e2ae security, the IMS-ALG shall indicate to the IMS-AGW as transport protocol: + +- a) for application-agnostic e2ae security support: + - "TCP" at the termination towards the core network; and + - "TCP/TLS" at the termination towards the access network; or +- b) for application-aware e2ae security support: + - "TCP/MSRP" at the termination towards the core network; and + - "TCP/TLS/MSRP" at the termination towards the access network. + +The IMS-ALG shall determine via SDP negotiation if the IMS-AGW needs to act as TLS client or TLS server using the IETF RFC 4145 [30] "a=setup" SDP attribute as follows: + +- if the IMS-ALG send an "a=setup:active" SDP attribute in an SDP answer towards the UE, the IMS-AGW shall act as TLS client; +- if the IMS-ALG send an "a=setup:passive" SDP attribute in an SDP answer towards the UE, the IMS-AGW shall act as TLS server; +- if the IMS-ALG receives an "a=setup:active" SDP attribute in an SDP answer from the UE, the IMS-AGW shall act as TLS server; and +- if the IMS-ALG receives an "a=setup:passive" SDP attribute in an SDP answer from the UE, the IMS-AGW shall act as TLS client. + +#### 5.11.2.2.3 e2ae security for conferencing (BFCP) + +For each BFCP media stream requiring e2ae security, the IMS-ALG shall indicate to the IMS-AGW as transport protocol: + +- "TCP" at the termination towards the core network; and +- "TCP/TLS" at the termination towards the access network. + +The IMS-ALG shall determine via SDP negotiation (see IETF RFC 4583 [27]) if the IMS-AGW needs to act as TLS client or TLS server as follows: + +- if the IMS-ALG receives an initial SDP offer from the UE, the IMS-AGW shall act as TLS server; and +- if the IMS-ALG sends an initial SDP offer towards the UE, the IMS-AGW shall act as TLS client. + +#### 5.11.2.3 End-to-access-edge security for UDP based media using DTLS + +##### 5.11.2.3.1 General + +The IMS-ALG and the IMS-AGW may support end-to-access-edge (e2ae) security for an UDP based media. The e2ae protection of the UDP based media relies on the usage of DTLS (see IETF RFC 6347 [32]), according to the DTLS profile specified in Annex E of 3GPP TS 33.310 [48] and exchange of self-signed certificates as defined in 3GPP TS 33.328 [12]. + +Key management solution for the e2ae media security of UDP is based on the cipher suites and session keys negotiated via the DTLS handshake protocol between the served UE and the IMS-AGW as specified in 3GPP TS 33.328 [12]. Procedures for the IMS-ALG to determine if e2ae security is applicable to UDP based media and to exchange the cryptographic information (i.e. certificate fingerprints, see IETF RFC 8122 [80]) via SDP negotiation with the served UE during the SIP session establishment are specified in 3GPP TS 33.328 [12] and 3GPP TS 24.229 [11]. + +If the IMS-ALG applies e2ae media security for a media stream and receives an SDP bandwidth modifier related to that media stream in SIP/SDP signalling, it should modify this bandwidth modifier to adjust the bandwidth overhead due to e2ae security before forwarding the SDP. The IMS-ALG should add the bandwidth overhead caused by e2ae media security to the bandwidth information received from the remote peer. The IMS-ALG should subtract the bandwidth overhead caused by e2ae media security from the bandwidth information received from the served UE. + +Clause 5.11.2.3.2 defines specific requirements for e2ae protection of T.38 fax media stream over UDPTL/UDP transport. The usage of UDPTL over DTLS is defined in IETF RFC 7345 [33] and IETF RFC 8842 [81]. + +##### 5.11.2.3.2 e2ae security for T.38 fax over UDP/UDPTL transport + +If the IMS-ALG and the IMS-AGW support e2ae security for the UDP based media using DTLS and certificate fingerprints, then for each T.38 fax media stream over UDPTL/UDP transport to be setup with e2ae security, the IMS-ALG shall: + +- include the IMS-AGW in the media path and allocate the required resources for the media stream in the IMS-AGW; + +- determine via SDP negotiation with the served UE if the IMS-AGW needs to act as DTLS client or DTLS server as specified in IETF RFC 7345 [33] and IETF RFC 8842 [81]; +- when requesting resources towards the access network: + - a) indicate to the IMS-AGW "UDP/DTLS" as transport protocol; + +NOTE 1: For IANA registry of "UDP/DTLS" see IETF draft-schwarz-mmusic-sdp-for-gw [34]. + +- b) send the certificate fingerprint(s) received from the served UE to the IMS-AGW; and + - c) request from the IMS-AGW the certificate fingerprint; +- include the certificate fingerprint received from the IMS-AGW in the SDP body it sends to the served UE; +- if the IMS-ALG received from the served UE an SDP offer with "a=tls-id" media-level SDP attribute (as specified in IETF RFC 8842 [81]), create a new DTLS association identity and include the "a=tls-id" SDP attribute with the new DTLS association identity in the SDP answer which the IMS-ALG sends to the served UE; +- if the IMS-ALG sends to the served UE an SDP offer, create a new DTLS association identity and include the "a=tls-id" SDP attribute with the new DTLS association identity in the SDP offer; + +NOTE 2: Already used certificate fingerprints can be assigned to a new DTLS association. If the IMS-AGW uses the same set of fingerprints for a new DTLS association then the IMS-ALG creates a new local "tls-id" attribute value so that the combination of the "tls-id" attribute values of the IMS-ALG and the served UE is unique across all DTLS associations that might be handled by the IMS-ALG and the served UE, as specified in IETF RFC 8842 [81]. + +- request the IMS-AGW to start the DTLS session setup if the IMS-AGW needs to act as DTLS client; and +- when requesting resources towards the core network: + - a) indicate to the IMS-AGW "UDP" as transport protocol. + +For each T.38 fax media stream over UDPTL/UDP transport to be setup with e2ae security, the IMS-AGW shall: + +- be capable to support both the DTLS server and DTLS client roles; +- upon request from the IMS-ALG, act as DTLS client and start DTLS session establishment; +- upon request from the IMS-ALG, select an own certificate for the T.38 fax media stream, uniquely associate its own certificate with the media stream, and send the fingerprint of the own certificate to the IMS-ALG; +- uniquely associate the certificate fingerprint(s) received from the IMS-ALG with the corresponding T.38 fax media stream; and +- verify during the subsequent DTLS handshake with the served UE (as described in IETF RFC 7345 [33] and IETF RFC 8842 [81]) that the fingerprint of the certificate passed by the served UE during DTLS handshake matches the certificate fingerprint received from the IMS-ALG: + - a) if the verification fails, the IMS-AGW shall regard the remote DTLS endpoint as not authenticated, terminate the DTLS session and report the unsuccessful DTLS session setup to the IMS-ALG; + - b) otherwise, the IMS-AGW shall continue with DTLS session setup and when the DTLS session is established, the IMS-AGW shall be prepared to receive and convert unprotected media from the core network to the protected media to be sent to the served UE and vice versa. + +#### 5.11.2.4 End-to-access-edge security for RTP based media using DTLS-SRTP + +The eP-CSCF (IMS-ALG) and eIMS-AGW for WebRTC provide end-to-access edge security by using DTLS-SRTP, where DTLS is used to establish keys for SRTP according to IETF RFC 5763 [42], IETF RFC 8842 [81] and IETF RFC 5764 [43]. + +During the establishment of a WebRTC session, the IMS-ALG receives "UDP/TLS/RTP/SAVP" or "UDP/TLS/RTP/SAVPF" as the transport protocol in SDP from the served WebRTC IMS Client (WIC). The IMS-ALG + +then shall indicate "RTP/AVP" or "RTP/AVPF" over UDP, respectively, as the transport protocol in the corresponding SDP media lines send towards the core network. When an IMS-ALG receives "RTP/AVP" or "RTP/AVPF" in SDP from the core network, the IMS-ALG shall indicate "UDP/TLS/RTP/SAVP" or "UDP/TLS/RTP/SAVPF" as transport protocol in SDP send towards the served WIC. When the IMS-ALG requests the eIMS-AGW to reserve transport addresses/resources for e2ae media security, the IMS ALG shall configure "UDP/TLS/RTP/SAVP" or "UDP/TLS/RTP/SAVPF" as transport protocol at the access side termination, and "RTP/AVP" or "RTP/AVPF" over UDP as transport protocol at the core network side termination. + +The IMS-ALG shall send the received WIC certificate fingerprint(s) to the eIMS-AGW that is then able to correlate the fingerprint within the media stream uniquely. For each SRTP/SRTCP media stream to be established with e2ae media security, the eIMS-AGW shall send the fingerprint of its certificate via Iq interface to the IMS-ALG. + +If the IMS-ALG received from the WIC an SDP offer with "a=tls-id" media-level SDP attribute (as specified in IETF RFC 8842 [81]), create a new DTLS association identity and include the "a=tls-id" SDP attribute with the new DTLS association identity in the SDP answer which the IMS-ALG sends to the WIC. + +If the IMS-ALG sends to the WIC an SDP offer, create a new DTLS association identity and include the "a=tls-id" SDP attribute with the new DTLS association identity in the SDP offer. + +**NOTE:** Already used certificate fingerprints can be assigned to a new DTLS association. If the IMS-AGW uses the same set of fingerprints for a new DTLS association then the IMS-ALG creates a new local "tls-id" attribute value so that the combination of the "tls-id" attribute values of the IMS-ALG and the WIC is unique across all DTLS associations that might be handled by the IMS-ALG and the WIC, as specified in IETF RFC 8842 [81]. + +According to procedures defined in 3GPP TS 24.371 [44], the eIMS-AGW shall act as either a DTLS server or client in the DTLS session. + +In DTLS-SRTP case, RTP and RTCP data are encrypted using SRTP and SRTCP as defined in IETF RFC 3711 [14]. + +When the DTLS session is established between the WIC and the eIMS-AGW, the eIMS-AGW shall be prepared to send and receive SRTP/SRTCP packets of the incoming network side from the WIC, and convert SRTP/SRTCP packets to RTP/RTCP packets to the outgoing network side and vice versa, if the media stream toward the IMS core network is using RTP/RTCP. + +#### 5.11.2.5 End-to-access-edge security for RTP based voice and video media using DTLS-SRTP over TCP + +The eP-CSCF (IMS-ALG) and eIMS-AGW for WebRTC may support end-to-access-edge security for RTP based voice and video media using DTLS-SRTP over TCP. If they do so, they shall apply the procedures in the present clause. + +**NOTE 1:** RTP over TCP may be used to traverse NAT/Firewalls that perform UDP blocking. + +TCP transport may be offered as an alternative to UDP transport using the ICE procedures in clause 5.18. The eP-CSCF (IMS-ALG) and eIMS-AGW for WebRTC shall then provide end-to-access edge security for voice and video by using DTLS-SRTP over TCP, where DTLS is used to establish keys for SRTP according to IETF RFC 5763 [42], IETF RFC 8842 [81] and IETF RFC 5764 [43]. Framing according to RFC 4571 [58] shall be used for RTP streams transferred over TCP. + +The IMS-ALG shall send the received WIC certificate fingerprint(s) to the eIMS-AGW that is then able to correlate the fingerprint within the media stream uniquely. For each SRTP/SRTCP media stream to be established with e2ae media security, the eIMS-AGW shall send the fingerprint of its certificate via Iq interface to the IMS-ALG. + +**NOTE 2:** The same fingerprint also applies for End-to-access-edge security for RTP based media using DTLS-SRTP, as described in clause 5.11.2.4. + +If the IMS-ALG received from the WIC an SDP offer with "a=tls-id" media-level SDP attribute (as specified in IETF RFC 8842 [81]) create a new DTLS association identity and include the "a=tls-id" SDP attribute with the new DTLS association identity in the SDP answer which the IMS-ALG sends to the WIC. + +If the IMS-ALG sends to the WIC an SDP offer, create a new DTLS association identity and include the "a=tls-id" SDP attribute with the new DTLS association identity in the SDP offer. + +NOTE 3: Already used certificate fingerprints can be assigned to a new DTLS association. If the IMS-AGW uses the same set of fingerprints for a new DTLS association then the IMS-ALG creates a new local "tls-id" attribute value so that the combination of the "tls-id" attribute values of the IMS-ALG and the WIC is unique across all DTLS associations that might be handled by the IMS-ALG and the WIC, as specified in IETF RFC 8842 [81]. + +According to procedures defined in 3GPP TS 24.371 [44], the eIMS-AGW shall act as either a DTLS server or client in the DTLS session. + +In DTLS-SRTP over TCP case, RTP and RTCP data are encrypted using SRTP and SRTCP as defined in IETF RFC 3711 [14]. + +When the DTLS session is established between the WIC and the eIMS-AGW, the eIMS-AGW shall be prepared to send and receive SRTP/SRTCP packets over TCP of the incoming network side from the WIC, and convert SRTP/SRTCP packets to RTP/RTCP packets over UDP to the outgoing network side and vice versa, if the media stream towards the IMS core network is using RTP/RTCP over UDP. + +### 5.11.2.6 End-to-access-edge security for WebRTC data channels using UDP/DTLS/SCTP transport + +The procedures in clause 5.20.2 are applicable. + +## 5.11.3 End-to-end Security + +### 5.11.3.1 End-to-end security for RTP based media + +For the support of e2e-security, the IMS-ALG and the IMS-AGW shall support "RTP/SAVP" (see IETF RFC 3711 [14]) and/or "RTP/SAVPF" (see IETF RFC 5124 [15]) as transport protocol. + +If the IMS-ALG receives SDP containing media lines with "RTP/SAVP" (see IETF RFC 3711 [14]) or "RTP/SAVPF" (see IETF RFC 5124 [15]) as transport protocol, but did not receive any request for end-to-access-edge security, the IMS-ALG shall: + +- forward the SDP with unmodified transport protocol for those media lines; +- provide "RTP/SAVP" or "RTP/SAVPF", as received in the SDP, to the IMS-AGW as transport protocol for all related terminations, and provide no media related information to these terminations, to configure the IMS-AGW to pass media transparently. + +If the IMS-ALG receives SDP containing SDES SDP attribute(s) according to IETF RFC 4568 [13], and did not receive any request for end-to-access-edge security, it shall forward the SDP with unmodified SDES SDP attribute(s), but shall not provide the SDES SDP attribute(s) to the IMS-AGW. + +### 5.11.3.2 End-to-end security for TCP-based media using TLS + +End-to-end protection of MSRP (used in IMS session-based messaging) and BFCP (used in IMS conferencing) media is based on TLS, according to the TLS profile specified in Annex E of 3GPP TS 33.310 [48] and Annex M of 3GPP TS 33.328 [12]. + +If the IMS-ALG receives SDP containing media lines with "TCP/TLS/MSRP" (see IETF RFC 4975 [25] and IETF RFC 6714 [26]) and/or "TCP/TLS/BFCP" (see IETF RFC 4583 [27]) as transport protocol but did not receive any request for end-to-access-edge security, the IMS-ALG shall: + +- forward the SDP with unmodified transport protocol for those media lines and unmodified TLS related SDP attribute(s); +- indicate "TCP" to the IMS-AGW as transport protocol for all related terminations, and provide no media related information to these terminations, to configure the IMS-AGW to pass media transparently. + +NOTE: End-to-end security for TCP-based media using TLS is not supported between two terminals being located behind firewalls/NATs. + +## 5.12 Explicit Congestion Notification support + +### 5.12.1 General + +An IMS-ALG and IMS-AGW may support Explicit Congestion Notification (see IETF RFC 3168 [16], IETF RFC 6679 [17] and 3GPP TS 26.114 [21]). + +An IMS-ALG and IMS-AGW which supports ECN shall support the ECN transparent procedure i.e. the transparent forwarding of ECN bits in the IP header (see IETF RFC 3168 [16]). If the IMS-AGW does not support the transparent forwarding of ECN bits then the IMS-ALG shall not permit ECN in the SDP Offer/Answer negotiation. + +The IMS-AGW shall treat RTCP for ECN as a RTP translator with no media translation. + +An IMS-ALG and IMS-AGW which supports ECN may then act as an ECN endpoint to enable ECN towards the IMS access network or/and towards the IMS Core Network. The subsequent clauses describe the general support for ECN, further details on the support of ECN during PS to CS access transfer is described in clause 6.2.14.3. + +NOTE: It is out of the scope of this profile to support interworking with a non-3GPP ECN IP terminal. + +An IMS-ALG and IMS-AGW that support ECN Transparent as well as transcoding shall also support the ECN endpoint procedure. + +An IMS-ALG/IMS-AGW supporting the ATCF/ATGW function and ECN shall support ECN Endpoint (see clause 6.2.14). + +When acting as an ECN endpoint, the IMS-AGW shall be capable of enabling end-to-end rate adaptation between the local terminal and the remote entity by performing the following towards the ECN-capable peer: + +- trigger rate adaptation request towards the ECN-capable peer when receiving in the incoming IMS media flow IP packets marked with ECN-CE, regardless of whether the IMS-AGW applies or does not apply transcoding; +- forward adaptation requests between the local and the remote peer when the IMS-AGW bridges compatible codec configurations between the interfaces without applying a transcoding function; +- perform media adaptation (e.g. reduce media bit-rate) towards the ECN-capable peer when receiving from the latter an adaptation request. and the IMS-AGW applies transcoding. + +### 5.12.2 Incoming SDP offer with ECN + +The IMS-ALG and IMS-AGW shall apply the requirements specified in clause 10.2.13.2 of 3GPP TS 29.162 [20] replacing the IBCF and TrGW with IMS-ALG and IMS-AGW respectively. + +### 5.12.3 Incoming SDP offer without ECN + +The IMS-ALG and IMS-AGW shall apply the requirements specified in clause 10.2.13.3 of 3GPP TS 29.162 [20] replacing the IBCF and TrGW with IMS-ALG and IMS-AGW respectively with the following additions: + +- if the IMS-ALG or IMS-AGW does not support the procedure to act as an ECN endpoint, the IMS-ALG shall not include the "a=ecn-capable-rtp" attribute in the SDP offer it forwards to the succeeding node. + +### 5.12.4 Detection of ECN failures by IMS-AGW + +An IMS-ALG and IMS-AGW that support the procedure to act as an ECN endpoint shall support the requirements specified in clause 10.2.13.3a of 3GPP TS 29.162 [20] replacing the IBCF and TrGW with IMS-ALG and IMS-AGW respectively. + +## 5.13 Transcoding + +### 5.13.1 General + +The transcoding functionality, where the IMS-AGW processes and possibly converts media data (like e.g. RTP payload) is optional for the P-CSCF and IMS-AGW to support. Transcoding should be supported if the IMS-ALG and IMS-AGW support the ATCF and ATGW functions for use after an SRVCC handover if the media that was used prior to the access transfer is not supported by the MSC Server. + +An IMS-ALG and IMS-AGW that support transcoding shall support the requirements specified for Media Control in clause 10.2.5 of 3GPP TS 29.162 [20] respectively for the IBCF and TrGW, with the following additions: + +- During an originating or terminating PS session establishment, the IMS-ALG (ATCF) may remove codecs when passing SDP offers (e.g. codecs known not to be supported by either the IMS-AGW (ATGW) or the MSC Server), but the IMS-ALG (ATCF) should pass SDP offers without adding codecs to the SDP offer and pass SDP answers without modification to the contained codecs to avoid the potential need for transcoding in the IMS-AGW (ATGW) before the PS to CS access transfer; +- During the PS to CS access transfer procedure, the IMS-ALG (ATCF) shall preferentially select from the SDP offer it receives from the MSC Server the codec already configured on the corresponding remote leg, if available. + +The procedures for the IMS-ALG (ATCF) and IMS-AGW (ATGW) are further detailed in clause 6.2.14. + +### 5.13.2 Handling of common codec parameters + +When receiving an SDP offer, the IMS-ALG may add a payload type to offer transcoding before forwarding the SDP offer (denoted as "codec 3" in figures 10.2.5.1 and 10.2.5.2 of 3GPP TS 29.162 [20]). If that payload type is selected in the SDP answer, the IMS-ALG needs to transcode. Table 5.13.2.1 describes the IMS-ALG handling of codec related parameters applicable to multiple codecs when the IMS-ALG adds the payload type to the SDP offer, and that payload type is selected in the SDP answer. + +**Table 5.13.2.1: IMS-ALG handling of common codec parameters for transcoding.** + +| Parameter | Handling of common codec parameter in the sent SDP offer | Handling of common codec parameter in the received SDP answer | +|-------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ptime
(NOTE) | If the ptime parameter is included in the received SDP offer, the IMS-ALG shall supply the parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. If the value is supported by the IMS-AGW for receiving media, the IMS-ALG should keep the value from the received SDP offer unchanged in the SDP offer it sends. If the IMS-AGW only supports a lower ptime value, the IMS-ALG shall supply the ptime value according to configured preferences in the SDP offer it forwards. If no ptime value was contained in the received SDP offer, the IMS-ALG may add the parameter with a value according to configured preferences to the SDP offer. | If the ptime parameter is included in the received SDP answer, the IMS-ALG shall supply the parameter to the IMS-AGW for the termination towards the SDP answerer in the remote descriptor. If the value is supported by the IMS-AGW for receiving media, the IMS-ALG should keep the value from the received SDP answer unchanged in the SDP answer it sends. If the IMS-AGW only supports a lower ptime value, the IMS-ALG shall supply the ptime value according to configured preferences in the SDP answer it forwards. If no ptime value was contained in the received SDP answer, the IMS-ALG may add the parameter with a value according to configured preferences to the SDP answer. | +| maxptime
(NOTE) | If the maxptime parameter is included in the received SDP offer, the IMS-ALG shall supply the parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. If the value is supported by the IMS-AGW for receiving media, the IMS-ALG should keep the value from the received SDP offer unchanged in the SDP offer it sends. If the IMS-AGW only supports a lower maxptime value, the IMS-ALG shall supply the maxptime value according to the IMS-AGW capabilities in the SDP offer it forwards. If no maxptime value was contained in the received SDP offer, the IMS-ALG may add the parameter with a value according to the IMS-AGW capabilities to the SDP offer. | If the maxptime parameter is included in the received SDP answer, the IMS-ALG shall supply the parameter to the IMS-AGW for the termination towards the SDP answerer in the remote descriptor. If the value is supported by the IMS-AGW for receiving media, the IMS-ALG should keep the value from the received SDP answer unchanged in the SDP answer it sends. If the IMS-AGW only supports a lower maxptime value, the IMS-ALG shall supply the maxptime value according to the IMS-AGW capabilities in the SDP answer it forwards. If no maxptime value was contained in the received SDP answer, the IMS-ALG may add the parameter with a value according to the IMS-AGW capabilities to the SDP answer. | +| NOTE: This SDP attribute is defined in IETF RFC 4566 [53]. It applies to all codecs offered in an SDP media line. | | | + +Table 5.13.2.2 describes the IMS-AGW handling of codec related parameters applicable to multiple codecs. + +**Table 5.13.2.2: IMS-AGW handling of common codec parameters** + +| Parameter | Handling in local descriptor | Handling in remote descriptor | +|-------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------| +| ptime
(NOTE) | The IMS-AGW should expect to receive packets with this ptime value and may use this information when deciding upon the required resources. | The IMS-AGW should use this ptime value when sending packets. | +| maxptime
(NOTE) | The IMS-AGW should expect to receive packets with this maxptime value and may use this information when deciding upon the required resources. | The IMS-AGW shall use this maxptime value when sending packets. | +| NOTE: This SDP attribute is defined in IETF RFC 4566 [53]. It applies to all codecs offered in an SDP media line. | | | + +### 5.13.3 Handling of the EVS speech codec + +The Enhanced Voice Services (EVS) speech codec is defined in 3GPP TS 26.441 [51]. Its RTP payload type is defined in 3GPP TS 26.445 [52], and procedures for its usage as IMS Multimedia Telephony speech codec are defined in 3GPP TS 26.114 [21]. + +The IMS-ALG and the IMS-AGW may support transcoding to and from the EVS speech codec. If they do so, the procedures in the present clause apply. + +When receiving an SDP offer, the IMS-ALG may add an EVS codec payload type before forwarding the SDP offer (denoted as "codec 3" in figures 10.2.5.1 and 10.2.5.2 of 3GPP TS 29.162 [20]). If that EVS payload type is selected in + +the SDP answer, the IMS-ALG needs to transcode the EVS codec. Table 5.13.3.1 describes the IMS-ALG handling of EVS codec parameters when the IMS-ALG adds the EVS payload type to the SDP offer, and that EVS payload type is selected in the SDP answer. In addition, rules for the parameter handling in 3GPP TS 26.445 [52] shall apply. + +**Table 5.13.3.1: IMS-ALG handling of EVS related SDP parameters when the IMS-ALG adds the EVS payload type to the SDP offer.** + +| Parameter | Handling for EVS payload type added to the SDP offer to offer transcoding | Handling if offered EVS payload type is accepted in the SDP answer | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| evs-mode-switch
(NOTE 1) | If the IMS-ALG expects that interworking between AMR-WB and EVS is required (e.g. because AMR-WB was the first payload type in the received SDP offer), it shall include the evs-mode-switch with value 1. Otherwise the IMS-ALG shall not include the evs-mode-switch. | If the evs-mode-switch parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor. | +| hf-only
(NOTE 1) | If the IMS-ALG is configured to negotiate using only the header-full EVS RTP payload format, the IMS-ALG shall include the hf-only parameter with a value 1. | If the hf-only parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| dtx
(NOTE 1) | If the usage of DTX is not desired in the sending and receiving direction (e.g. due to DTX capabilities of expected codecs to transcode with, e.g. other codecs in the received SDP offer), the IMS-ALG shall include the dtx parameter with a value 0. | If the dtx parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| dtx-recv
(NOTE 1) | If receiving DTX is not desired and the dtx parameter is not included, the IMS-ALG shall include the dtx-recv parameter with a value 0. If both the dtx and dtx-recv parameters are included, those parameters shall have the same value; however, inclusion of the dtx-recv parameter is not required if the dtx parameter is included. | If the dtx-recv parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| br
(NOTE 1) | If the IMS-ALG desires the same bit rate range for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range to match IMS-AGW capabilities and possible configured policies, it shall supply the br parameter in the SDP offer it sends. Otherwise the IMS-ALG shall not include this parameter in the SDP offer.
If the IMS-ALG also supplies the bw, bw-send or bw-recv parameter, the value of the br parameter shall be compatible with the values of those parameters. | If the br parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| br-send
(NOTE 1) | If the IMS-ALG desires a different bit rate (range) for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range for the send direction to match IMS-AGW capabilities and possible configured policies, it shall supply the br-send parameter in the SDP offer it sends. Otherwise the IMS-ALG shall not include this parameter in the SDP offer.
If the IMS-ALG also supplies the bw or bw-send parameter, the value of the br-send parameter shall be compatible with the values of those parameters. | If the br-send parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| br-recv
(NOTE 1) | If the IMS-ALG desires a different bit rate (range) for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range for the receive direction to match IMS-AGW capabilities and possible configured policies, it shall supply the br-recv parameter in the SDP offer it sends. Otherwise the IMS-ALG shall not include this parameter in the SDP offer.
If the IMS-ALG also supplies the bw or bw-recv parameter, the value of the br-recv parameter shall be compatible with the values of those parameters. | If the br-recv parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| bw
(NOTE 1) | If the IMS-ALG desires the same sampling bandwidth(s) for the send and receive direction in EVS primary mode, and wants to restrict the | If the bw parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | + +| | | | +|--------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| +| | sampling bandwidths to match IMS-AGW capabilities, sampling bandwidths of expected codecs EVS will be transcoded to (e.g. the first payload type in the received SDP offer), and possible configured policies, it shall supply the bw parameter in the SDP offer it sends. Otherwise the IMS-ALG shall not include this parameter in the SDP offer. | | +| bw-send
(NOTE 1) | If the IMS-ALG desires different sampling bandwidths for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidths in the send direction to match IMS-AGW capabilities, sampling bandwidths of expected codecs EVS will be transcoded to (e.g. the first payload type in the received SDP offer) and possible configured policies, it shall supply the bw-send parameter in the SDP offer it sends. Otherwise the IMS-ALG shall not include this parameter in the SDP offer. | If the bw-send parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| bw-recv
(NOTE 1) | If the IMS-ALG desires different sampling bandwidths for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidths in the receive direction to match IMS-AGW capabilities, sampling bandwidths of expected codecs EVS will be transcoded to (e.g. the first payload type in the received SDP offer), and possible configured policies, it shall supply the bw-recv parameter in the SDP offer it sends. Otherwise the IMS-ALG shall not include this parameter in the SDP offer. | If the bw-recv parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| cmr
(NOTE 1) | If the IMS-ALG desires to disable codec mode requests within the RTP payload of the EVS primary mode (due to the IMS-AGW capabilities or policies), it shall include the cmr parameter with value -1 in the SDP offer it sends. | If the cmr parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| ch-aw-recv
(NOTE 1) | The IMS-ALG shall include the ch-aw-recv parameter in the SDP offer if it desires to control the channel-aware mode of EVS in the receive direction, e.g. to disable it with value -1. The IMS-ALG shall consider the capabilities of the IMS-AGW when it chooses an appropriate value. | If the ch-aw-recv parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| number of channels
(NOTE 2) | The IMS-ALG shall only include the "number of channels" parameter in the SDP offer if it desires to send or receive multiple channels. If the desired number of channels in the send and receive direction differs, the IMS-ALG shall include the higher value. The IMS-ALG should consider the number of channels of expected codecs EVS will be transcoded to (e.g. the first payload type in the received SDP offer). | If the "number of channels" parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| ch-send
(NOTE 1) | The IMS-ALG shall only include the ch-send parameter in the SDP offer if it desires to send multiple channels, with different numbers of channels in the send and receive direction. The IMS-ALG should consider the number of channels of expected codecs EVS will be transcoded to (e.g. the first payload type in the received SDP offer). | If the ch-send parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| ch-recv
(NOTE 1) | The IMS-ALG shall only include the ch-recv parameter in the SDP offer if it desires to receive multiple channels, with different numbers of channels in the send and receive direction. The IMS-ALG should consider the number of channels of expected codecs EVS will be transcoded to (e.g. the first payload type in the received SDP offer). | If the ch-recv parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| mode-set
(NOTE 3) | The IMS-ALG shall only include the mode-set parameter in the SDP offer if it desires to restrict | If the mode-set parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | the mode-set of AMR-WB IO mode. The IMS-ALG should only restrict the mode-set if the expected codec EVS will be interworked with (e.g. the first payload type in the received SDP offer) is AMR-WB and has a restricted mode-set. | to the IMS-AGW in the remote descriptor.
If the IMS-ALG decides that EVS will be transcoded to AMR-WB, the IMS-ALG should include the mode-set parameter for the AMR-WB payload in the SDP offer it forwards if this is permissible by AMR-WB offer answer rules in IETF RFC 4867 [54]. | +| mode-change-period (NOTE 3) | The IMS-ALG shall only include the mode-change-period parameter with value 2 in the SDP offer if it desires to restrict the mode-change-period of received packets in AMR-WB IO mode. The IMS-ALG should only restrict the mode-change-period if the expected codec EVS will be interworked with (e.g. the first payload type in the received SDP offer) is AMR-WB and has such a restriction. | If the mode-change-period parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor.
If the IMS-ALG decides that EVS will be transcoded to AMR-WB, the IMS-ALG should include the mode-change-period parameter for the AMR-WB payload in the SDP offer it forwards. | +| mode-change-capability (NOTE 3) | The IMS-ALG shall include the mode-change-capability parameter with value 2 in the SDP offer if it is capable of restricting the mode-change-period of packets it sends in AMR-WB IO mode. The IMS-ALG should consider the mode-change-period of the expected codec EVS will be interworked with (e.g. the first payload type in the received SDP offer) if this is AMR-WB. | If the mode-change-capability parameter is contained in the SDP answer, the IMS-ALG may forward this parameter to the IMS-AGW in the remote descriptor.
If the IMS-ALG decides that EVS will be transcoded to AMR-WB, the IMS-ALG should include the mode-change-capability parameter for the AMR-WB payload in the SDP offer it forwards. | +| mode-change-neighbor (NOTE 3) | The IMS-ALG shall only include the mode-change-neighbor parameter in the SDP offer if it desires to restrict the mode-change within received packets of AMR-WB IO mode to neighboring modes. The IMS-ALG should consider the mode-change-neighbor parameter of the expected codec EVS will be interworked with (e.g. the first payload type in the received SDP offer) if this is AMR-WB. | If the mode-change-neighbor parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor.
If the IMS-ALG decides that EVS will be transcoded to AMR-WB, the IMS-ALG should include the mode-change-neighbor parameter for the AMR-WB payload in the SDP offer it forwards. | +| max-red (NOTE 5) | The IMS-ALG shall only include the max-red parameter in the SDP offer if it desires to restrict the maximum redundancy of received packets. IMS-ALG shall consider the capabilities of the IMS-AGW, and should consider the max-red parameter of the expected codec EVS will be interworked with (e.g. the first payload type in the received SDP offer) if this is AMR-WB. | If the max-red parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor.
If the IMS-ALG decides that EVS will be interworked with AMR-WB, the IMS-ALG should include the max-red parameter for the AMR-WB payload in the SDP offer it forwards. | +| 3gpp_mtsi_app_adapt (NOTE 4) | If the IMS-AGW supports RTCP APP based adaptation messages defined in 3GPP TS 26.114 [21], and the IMS-ALG has a policy to negotiate the usage of those messages, the IMS-ALG shall include the 3gpp_mtsi_app_adapt SDP attribute indicating the supported APP messages in the SDP offer. | If the 3gpp_mtsi_app_adapt attribute is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| NOTE 1: This MIME parameter of the EVS RTP payload type is defined in 3GPP TS 26.445 [51]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [53]. | | | +| NOTE 2: This number of channels are encoded as "encoding parameters" of the SDP "a=rtpmap" attribute defined in IETF RFC 4566 [53]. | | | +| NOTE 3: This MIME parameter of the EVS RTP payload type relates to AMR-WB IO mode and is defined in IETF RFC 4867 [54]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [53]. | | | +| NOTE 4: This SDP attribute is defined in 3GPP TS 26.114 [21]. It applies to all codecs offered in an SDP media line. However, some values are specific to EVS. | | | +| NOTE 5: This MIME parameter of the EVS RTP payload type is defined in IETF RFC 4867 [54]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [53]. | | | + +When receiving an SDP offer that contains an EVS codec payload type (denoted as "codec 1" in figure 10.2.5.2 of 3GPP TS 29.162 [20]), the IMS-ALG may add other payload types before forwarding the SDP offer (denoted as "codec 3" in figure 10.2.5.2 of 3GPP TS 29.162 [20]). If that added payload type is selected in the SDP answer, the IMS-ALG needs to transcode, and may select to transcode to the EVS codec. Table 5.13.3.2 describes the IMS-ALG handling of EVS codec parameters when the IMS-ALG receives an EVS payload type in an SDP offer, and selects to transcode between the EVS codec and some other codec. In addition, rules for the parameter handling in 3GPP TS 26.445 [52] shall apply. + +**Table 5.13.3.2: IMS-ALG handling of EVS related SDP parameters when the IMS-ALG receives the EVS payload type in the SDP offer and decides to transcode between the EVS payload type and some other codec.** + +| Parameter | Handling of EVS payload type parameter received in the SDP offer | EVS payload type supplied in the SDP answer | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| evs-mode-switch
(NOTE 1) | If the evs-mode-switch parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the evs-mode-switch parameter is contained in the SDP offer, the IMS-ALG shall include the evs-mode-switch parameter with unmodified value in the SDP answer.
Otherwise, if the IMS-ALG decides to interwork between AMR-WB and EVS (e.g. because AMR-WB was selected in the received SDP answer), it shall include the evs-mode-switch with value 1.
Otherwise the IMS-ALG shall not include the evs-mode-switch.
If the IMS-ALG supplies the evs-mode-switch in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| hf-only
(NOTE 1) | If the hf-only parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the hf-only parameter is contained in the SDP offer, the IMS-ALG shall include the hf-only parameter with unmodified value in the SDP answer.
Otherwise, if the IMS-ALG is configured to negotiate using only the header-full EVS RTP payload format, the IMS-ALG shall include the hf-only parameter with a value 1.
If the IMS-ALG supplies the hf-only parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| dtx
(NOTE 1) | If the dtx parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the dtx parameter is contained in the SDP offer, the IMS-ALG shall include the dtx parameter with unmodified value in the SDP answer.
If the dtx parameter is not contained in the SDP offer and if a dtx-recv parameter is contained in the SDP offer, the IMS-ALG may include the dtx parameter in the SDP answer, and the value of the dtx parameter shall then be identical to that of the dtx-recv parameter in the SDP offer (e.g. if that value matches DTX capabilities of expected codecs to transcode with).
If the dtx parameter is not contained in the SDP offer and if the dtx-recv parameter is not contained in the SDP offer, and if the usage of DTX is not desired (e.g. due to DTX capabilities of expected codecs to transcode with, e.g. other codecs in the received SDP answer), the IMS-ALG shall include in the SDP answer the dtx parameter with a value 0.
If the IMS-ALG supplies the dtx parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| dtx-recv
(NOTE 1) | If the dtx-recv parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If no dtx parameter is included in the SDP answer and if the reception of DTX is not desired, the IMS-ALG shall include in the SDP answer the dtx-recv parameter with a value 0.
If both the dtx and dtx-recv parameters are included, those parameters shall have the same value; however, inclusion of the dtx-recv parameter is not required if the dtx parameter is included.
If the IMS-ALG supplies the dtx-recv parameter in the SDP answer, it should also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| br
(NOTE 1) | If the br parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW | If the br parameter is contained in the SDP offer, the IMS-ALG shall select a bitrate value, which is either | + +| | | | +|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

supports the indicated bitrates, or a subset of them, in EVS primary mode in the send and receive direction. If the indicated bitrates, and even each subset of them, are not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type, it shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor.

|

the received br value or a subset of it, based on IMS-AGW capabilities and possible configured policies, and shall include the br parameter with the selected value that is also supplied towards the IMS-AGW in the SDP answer.

Otherwise, if the IMS-ALG desires the same bit rate range for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range to match IMS-AGW capabilities and possible configured policies, it shall supply the br parameter in the SDP answer it sends.

Otherwise the IMS-ALG shall not include this parameter in the SDP answer.

If the IMS-ALG also supplies the bw, bw-send or bw-recv parameter, the value of the br parameter shall be compatible with the values of those parameters.

If the IMS-ALG supplies the br parameter in the SDP answer, it shall also supply to the IMS-AGW the br parameter in the local descriptor for the termination towards the offerer with the same value.

| +| br-send
(NOTE 1) |

If the br-send parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated bitrates, or a subset of them, in EVS primary mode in the receive direction. If the indicated bitrates, and even each subset of them, are not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type, it shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor.

|

If the br-recv parameter is contained in the SDP offer, the IMS-ALG shall select a bitrate value, which is either the received br-recv value or a subset of it, based on IMS-AGW capabilities and possible configured policies, and shall include the br-send parameter with the selected value that is also supplied towards the IMS-AGW in the SDP answer.

Otherwise, if the IMS-ALG desires a different bit rate (range) for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range for the send direction to match IMS-AGW capabilities and possible configured policies, it shall supply the br-send parameter in the SDP answer it sends.

Otherwise the IMS-ALG shall not include the br-send parameter in the SDP answer.

If the IMS-ALG also supplies the bw or bw-send parameter, the value of the br-send parameter shall be compatible with the values of those parameters.

If the IMS-ALG supplies the br-send parameter in the SDP answer, it shall also supply to the IMS-AGW the br-send parameter in the local descriptor for the termination towards the offerer with the same value.

| +| br-recv
(NOTE 1) |

If the br-recv parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated bitrates, or a subset of them, in EVS primary mode in the send direction. If the indicated bitrates, and even each subset of them, are not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type, it shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor.

|

If the br-send parameter is contained in the SDP offer, the IMS-ALG shall select a bitrate value, which is either the received br-send value or a subset of it, based on IMS-AGW capabilities and possible configured policies, and shall include the br-recv parameter with the selected value that is also supplied towards the IMS-AGW in the SDP answer.

Otherwise, if the IMS-ALG desires a different bit rate (range) for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range for the receive direction to match IMS-AGW capabilities and possible configured policies, it shall supply the br-recv parameter in the SDP answer it sends.

Otherwise the IMS-ALG shall not include the br-recv parameter in the SDP answer.

If the IMS-ALG also supplies the bw or bw-recv parameter, the value of the br-recv parameter shall be compatible with the values of those parameters.

If the IMS-ALG supplies the br-recv parameter in the SDP answer, it shall also supply to the IMS-AGW

| + +| | | | +|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | the br-recv parameter in the local descriptor for the termination towards the offerer with the same value. | +| bw
(NOTE 1) | If the bw parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated sampling bandwidth(s), or a subset of them, in EVS primary mode in the send and receive direction. If the indicated sampling bandwidth(s), and even each subset of them, are not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type, it shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the bw parameter is contained in the SDP offer, the IMS-ALG shall select a sampling bandwidth value, which is either the received bw value or a subset of it, based on IMS-AGW capabilities and possible configured policies, and shall include the bw parameter with the selected value that is also supplied towards the IMS-AGW in the SDP answer. Otherwise, if the IMS-ALG desires the same sampling bandwidth(s) for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidth(s) to match IMS-AGW capabilities and possible configured policies, it shall supply the bw parameter in the SDP answer it sends. Otherwise the IMS-ALG shall not include this parameter in the SDP answer. If the IMS-ALG also supplies the br, br-send or br-recv parameter, the value of the bw parameter shall be compatible with the values of those parameters. If the IMS-ALG supplies the bw parameter in the SDP answer, it shall also supply to the IMS-AGW the bw parameter in the local descriptor for the termination towards the offerer with the same value. | +| bw-send
(NOTE 1) | If the bw-send parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated sampling bandwidths, or a subset of them, in EVS primary mode in the receive direction. If the indicated sampling bandwidths, and even each subset of them, are not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type, it shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the bw-recv parameter is contained in the SDP offer, the IMS-ALG shall select a sampling bandwidths value, which is either the received bw-recv value or a subset of it, based on IMS-AGW capabilities and possible configured policies, and shall include the bw-send parameter with the selected value in the SDP answer. Otherwise, if the IMS-ALG desires different sampling bandwidths for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidths for the send direction to match IMS-AGW capabilities and possible configured policies, it shall supply the bw-send parameter in the SDP answer it sends. Otherwise the IMS-ALG shall not include the br-send parameter in the SDP answer. If the IMS-ALG also supplies the bw or bw-send parameter, the value of the br-send parameter shall be compatible with the values of those parameters. If the IMS-ALG supplies the bw-send parameter in the SDP answer, it shall also supply to the IMS-AGW the bw-send parameter in the local descriptor for the termination towards the offerer with the same value. | +| bw-recv
(NOTE 1) | If the br-recv parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated sampling bandwidths, or a subset of them, in EVS primary mode in the send direction. If the indicated sampling bandwidths, and even each subset of them, are not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type, it shall forward the bw-recv parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the bw-send parameter is contained in the SDP offer, the IMS-ALG shall select a sampling bandwidths value, which is either the received bw-send value or a subset of it, based on IMS-AGW capabilities and possible configured policies, and shall include the bw-recv parameter with the selected value in the SDP answer. Otherwise, if the IMS-ALG desires a different sampling bandwidths for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidths for the receive direction to match IMS-AGW capabilities and possible configured policies, it shall supply the bw-recv parameter in the SDP answer it sends. Otherwise the IMS-ALG shall not include the bw-recv parameter in the SDP answer. If the IMS-ALG also supplies the br or br-recv parameter, the value of the bw-recv parameter shall be compatible with the values of those parameters. | + +| | | | +|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | If the IMS-ALG supplies the bw-send parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| cmr
(NOTE 1) | If the cmr parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the cmr parameter is contained in the SDP offer, the IMS-ALG shall include the cmr parameter with unmodified value in the SDP answer.
Otherwise, if the IMS-AGW desires to disable codec mode requests within the RTP payload of the EVS primary mode (due to the IMS-AGW capabilities or policies), it shall include the cmr parameter with value -1 in the SDP answer it sends
If the IMS-ALG supplies the cmr parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| ch-aw-recv
(NOTE 1) | If the ch-aw-recv parameter is contained in the SDP offer the IMS-ALG shall check if the IMS-AGW supports the indicated mode in the send direction. If the indicated mode is not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the IMS-ALG it desires to control the channel-aware mode of EVS in the receive direction, e.g. to disable it with value -1, it shall include the ch-aw-recv parameter in the SDP offer and shall also supply the ch-aw-recv parameter to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. The IMS-ALG shall consider the capabilities of the IMS-AGW when it chooses an appropriate value. | +| number of channels
(NOTE 2) | If the "number of channels" parameter is contained in the SDP offer the IMS-ALG shall check if the IMS-AGW supports the indicated number of channels. If the indicated number of channels is not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the "number of channels" parameter is contained in the SDP offer, the IMS-ALG shall include the "number of channels" parameter with unmodified value in the SDP answer and shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| ch-send
(NOTE 1) | If the ch-send parameter is contained in the SDP offer the IMS-ALG shall check if the IMS-AGW supports the indicated number of channels in the receive direction. If the indicated number of channels is not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type for transcoding, the IMS-ALG shall forward the ch-send parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the ch-recv parameter is contained in the SDP offer, the IMS-ALG shall include the ch-send parameter with unmodified value in the SDP answer and shall also supply the ch-send parameter to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| ch-recv
(NOTE 1) | If the ch-recv parameter is contained in the SDP offer the IMS-ALG shall check if the IMS-AGW supports the indicated number of channels in the send direction. If the indicated number of channels is not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type for transcoding, the IMS-ALG shall forward the ch-recv parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the ch-send parameter is contained in the SDP offer, the IMS-ALG shall include the ch-recv parameter with unmodified value in the SDP answer and shall also supply the ch-recv parameter to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| mode-set
(NOTE 3) | If the mode-set parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor.
If the mode-set parameter is contained in the SDP offer and the IMS-ALG expects that EVS will be interworked with AMR-WB (e.g. if EVS is the first payload type in the received SDP offer, | If the mode-set parameter is contained in the SDP offer, the IMS-ALG shall include the mode-set parameter with unmodified value in the SDP answer.
Otherwise, if the mode-set parameter is contained in the SDP answer for an AMR-WB payload type and the IMS-ALG decides that the EVS codec will be interworked with that AMR-WB payload type, the IMS-ALG should include that mode-set parameter for the EVS payload in the SDP offer it forwards. | + +| | | | +|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | and the IMS-ALG adds a AMR-WB payload type), the IMS-ALG should include the mode-set parameter with the same value for the AMR-WB payload in the SDP offer it forwards. | If the IMS-ALG supplies the mode-set parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| mode-change-period (NOTE 3) |

If the mode-change-period parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor.

If the mode-change-period parameter is contained in the SDP offer and the IMS-ALG expects that EVS will be interworked with AMR-WB (e.g. if EVS is the first payload type in the received SDP offer, and the IMS-ALG adds the AMR-WB payload type), the IMS-ALG should include the mode-change-period parameter with the same value for the AMR-WB payload type in the SDP offer it forwards.

|

If the mode-change-period parameter is contained in the SDP answer for the AMR-WB payload type and the IMS-ALG decides the EVS codec will be interworked with that AMR-WB payload type, the IMS-ALG should include the mode-change-period parameter for the EVS payload in the SDP offer it forwards.

If the IMS-ALG supplies the mode-change-period parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value.

| +| mode-change-capability (NOTE 3) |

If the mode-change-capability parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG may forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor.

If the IMS-ALG expects that EVS will be interworked with AMR-WB (e.g. if EVS is the first payload type in the received SDP offer, and the IMS-ALG adds the AMR-WB payload type), the IMS-ALG should include the mode-change-capability parameter with value 2 for the AMR-WB payload in the SDP offer it forwards.

|

If the IMS-ALG decides that the EVS codec is selected, the IMS-ALG shall either include the mode-change-capability parameter with value 2 or omit the parameter for the EVS payload in the SDP offer it forwards.

If the IMS-ALG supplies the mode-change-capability parameter in the SDP answer, it may also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value.

| +| mode-change-neighbor (NOTE 3) |

If the mode-change-neighbor parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor.

If the mode-change-neighbor parameter is contained in the SDP offer and the IMS-ALG expects that EVS will be interworked with AMR-WB (e.g. if EVS is the first payload type in the received SDP offer, and the IMS-ALG adds the AMR-WB payload type), the IMS-ALG should include the mode-change-neighbor with the same value for the AMR-WB payload in the SDP offer it forwards.

|

If the mode-change-neighbor parameter is contained in the SDP answer for the AMR-WB payload type and the IMS-ALG decides that the EVS codec will be interworked with that AMR-WB payload type, the IMS-ALG should include the mode-change-neighbor parameter for the EVS payload in the SDP offer it forwards.

If the IMS-ALG supplies the mode-change-neighbor parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value.

| +| max-red (NOTE 5) |

If the max-red parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor.

If the max-red parameter is contained in the SDP offer and the IMS-ALG expects that EVS will be interworked with AMR-WB (e.g. if EVS is the first payload type in the received SDP offer, and the IMS-ALG adds the AMR-WB payload type), the IMS-ALG should include the max-red parameter with the same value for the AMR-WB payload in the SDP offer it forwards with a value that considers the received value and the capabilities of the IMS-AGW.

|

The IMS-ALG shall only include the max-red parameter in the SDP answer if it desires to restrict the maximum redundancy of received packets. When selecting the value of the max-red parameter, the IMS-ALG shall consider the capabilities of the IMS-AGW and, if the max-red parameter is contained in the SDP answer for the AMR-WB payload type and the IMS-ALG decides that the EVS codec will be interworked with that AMR-WB payload type, the received value.

If the IMS-ALG supplies the max-red parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value.

| +| 3gpp_mtsi_app_adapt (NOTE 4) | If the 3gpp_mtsi_app_adapt parameter is contained in the SDP answer, and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW the IMS-ALG shall forward this | If the IMS-AGW supports RTCP APP based adaptation messages defined in 3GPP TS 26.114 [21], and the IMS-ALG has a policy to negotiate the usage of those messages, the IMS-ALG shall include the | + +| | | | +|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|--------------------------------------------------------------------------------------------| +| | parameter to the IMS-AGW in the remote descriptor. | 3gpp_mtsi_app_adapt SDP attribute indicating the supported APP messages in the SDP answer. | +| NOTE 1: This MIME parameter of the EVS RTP payload type is defined in 3GPP TS 26.445 [51]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [53]. | | | +| NOTE 2: This number of channels are encoded as "encoding parameters" of the SDP "a=rtpmap" attribute defined in IETF RFC 4566 [53]. | | | +| NOTE 3: This MIME parameter of the EVS RTP payload type relates to AMR-WB IO mode and is defined in IETF RFC 4867 [54]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [53]. | | | +| NOTE 4: This SDP attribute is defined in 3GPP TS 26.114 [21]. It applies to all codecs offered in an SDP media line. However, some values are specific to EVS. | | | +| NOTE 5: This MIME parameter of the EVS RTP payload type is defined in IETF RFC 4867 [54]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [53]. | | | + +Table 5.13.3.3 describes the IMS-AGW handling of EVS codec parameters. The IMS-AGW should support transcoding of EVS with bandwidths (sampling rates) which are supported by codec the IMS-AGW is capable to transcode EVS to/from (e.g. NB for AMR, and WB for AMR-WB). + +Table 5.13.3.3: IMS-AGW handling of EVS codec parameters + +| Parameter | Handling in local descriptor | Handling in remote descriptor | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| evs-mode-switch
(NOTE 1) | The IMS-AGW should expect to receive packets with the indicated EVS mode and may use this information when deciding upon the required resources. | The IMS-AGW shall use the indicated EVS mode (e.g. AMR-WB interoperable mode for value 1) when sending packets. | +| hf-only
(NOTE 1) | The IMS-AGW should expect to receive packets with the indicated mode and may use this information when deciding upon the required resources. | The IMS-AGW shall use the indicated mode (e.g. header-full EVS RTP payload format for value 1) when sending packets. | +| dtx
(NOTE 1) | The IMS-AGW should expect to receive packets with this dtx mode and may use this information when deciding upon the required resources.
(NOTE 8) | The IMS-AGW shall use this dtx mode (i.e. no usage of DTX for value 0) when sending packets.
(NOTE 8) | +| dtx-recv
(NOTE 1) | The IMS-AGW should expect to receive packets with this dtx mode and may use this information when deciding upon the required resources.
(NOTE 8) | The IMS-AGW shall use this dtx mode (i.e. no usage of DTX for value 0) when sending packets.
(NOTE 8) | +| br
(NOTE 1) | If different values for the br parameter are provided in the local and remote descriptors, one will be a subset of the other, and the smaller range shall apply.
The IMS-AGW should expect to receive packets with this bitrate range and may use this information when deciding upon the required resources.
The IMS-AGW shall use this bitrate range when sending packets. | If different values for the br parameter are provided in the local and remote descriptors, one will be a subset of the other, and the smaller range shall apply.
The IMS-AGW should expect to receive packets with this bitrate range and may use this information when deciding upon the required resources.
The IMS-AGW shall use this bitrate range when sending packets. | +| br-send
(NOTE 1) | If different values for the br-send parameter in the local descriptor and for the br-recv parameter in the remote descriptor are provided, one will be a subset of the other, and the smaller range shall apply.
The IMS-AGW shall use this bitrate range when sending packets. | If different values for the br-send parameter in the remote descriptor and for the br-recv parameter in the local descriptor are provided, one will be a subset of the other, and the smaller range shall apply.
The IMS-AGW should expect to receive packets with this bitrate range and may use this information when deciding upon the required resources. | +| br-recv
(NOTE 1) | If different values for the br-send parameter in the remote descriptor and for the br-recv parameter in the local descriptor are provided, one will be a subset of the other, and the smaller range shall apply.
The IMS-AGW should expect to receive packets with this bitrate range and may use this information when deciding upon the required resources. | If different values for the br-send parameter in the local descriptor and for the br-recv parameter in the remote descriptor are provided, one will be a subset of the other, and the smaller range shall apply.
The IMS-AGW shall use this bitrate range when sending packets. | +| bw
(NOTE 1) | If different values for the bw parameter are provided in the local and remote descriptors, one will be a subset of the other, and the smaller range shall apply.
The IMS-AGW should expect to receive packets with these sampling bandwidth(s) and may use this information when deciding upon the required resources.
The IMS-AGW shall use these sampling bandwidth(s) when sending packets. | If different values for the bw parameter are provided in the local and remote descriptors, one will be a subset of the other, and the smaller range shall apply.
The IMS-AGW should expect to receive packets with these sampling bandwidth(s) and may use this information when deciding upon the required resources.
The IMS-AGW shall use these sampling bandwidth(s) when sending packets. | +| bw-send
(NOTE 1) | If different values for the bw-send parameter in the local descriptor and for the bw-recv parameter in the remote descriptor are provided, one will be a subset of the other, and the smaller range shall apply.
The IMS-AGW shall use these sampling bandwidth(s) when sending packets. | If different values for the bw-send parameter in the remote descriptor and for the bw-recv parameter in the local descriptor are provided, one will be a subset of the other, and the smaller range shall apply.
The IMS-AGW should expect to receive packets with these sampling bandwidth(s) and may use this information when deciding upon the required resources. | +| bw-recv
(NOTE 1) | If different values for the bw-send parameter in the remote descriptor and for the bw-recv parameter in the local descriptor are provided, | If different values for the bw-send parameter in the local descriptor and for the bw-recv parameter in the remote descriptor are provided, one will be a subset | + +| | | | +|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | one will be a subset of the other, and the smaller range shall apply.
The IMS-AGW should expect to receive packets with these sampling bandwidth(s) and may use this information when deciding upon the required resources. | of the other, and the smaller range shall apply.
The IMS-AGW shall use these sampling bandwidth(s) when sending packets. | +| cmr
(NOTE 1) | For cmr with value -1 or 0, the IMS-AGW should expect to receive no RTP packets containing codec mode requests for EVS primary mode and may use this information when deciding upon the required resources.
For cmr with value -1 or 0, the IMS-AGW shall also send no RTP packets containing codec mode requests for EVS primary mode.
Different cmr values in the local and remote descriptors are an error situation, but it is permissible that this parameter is only supplied in one of those descriptors. | For cmr with value -1 or 0, the IMS-AGW should expect to receive no RTP packets containing codec mode requests for EVS primary mode and may use this information when deciding upon the required resources.
For cmr with value -1 or 0, the IMS-AGW shall also send no RTP packets containing codec mode requests for EVS primary mode.
Different cmr values in the local and remote descriptors are an error situation, but it is permissible that this parameter is only supplied in one of those descriptors. | +| ch-aw-recv
(NOTE 1,
NOTE 7) | The IMS-AGW should expect to receive RTP packets containing the indicated partial redundancy mode and may use this information when deciding upon the required resources. | The IMS-AGW shall send RTP packets containing the indicated partial redundancy mode. | +| number of
channels
(NOTE 2) | If no ch-recv parameter in the local descriptor and no ch-send parameter in the remote descriptors are received, the IMS-AGW should expect to receive RTP packets containing the indicated number of channels and may use this information when deciding upon the required resources.
If no ch-send parameter in the local descriptor and no ch-recv parameter in the remote descriptors are received, the IMS-AGW shall also send RTP packets containing the indicated number of channels.
Different number of channels values in the local and remote descriptors is an error situation, but it is permissible that this parameter is only supplied in one of those descriptors. | If no ch-recv parameter in the local descriptor and no ch-send parameter in the remote descriptors are received, the IMS-AGW should expect to receive RTP packets containing the indicated number of channels and may use this information when deciding upon the required resources.
If no ch-send parameter in the local descriptor and no ch-recv parameter in the remote descriptors are received, the IMS-AGW shall also send RTP packets containing the indicated number of channels.
Different number of channels values in the local and remote descriptors is an error situation, but it is permissible that this parameter is only supplied in one of those descriptors. | +| ch-send
(NOTE 1) | The IMS-AGW shall send RTP packets containing the indicated number of channels.
Different number of channels in the ch-send parameter in the local descriptor and the ch-recv parameter in the remote descriptors is an error situation, but it is permissible that this parameter is only supplied in one of those descriptors. | The IMS-AGW should expect to receive RTP packets containing the indicated number of channels and may use this information when deciding upon the required resources.
Different number of channels in the ch-send parameter in the local descriptor and the ch-recv parameter in the remote descriptors is an error situation, but it is permissible that this parameter is only supplied in one of those descriptors. | +| ch-recv
(NOTE 1) | The IMS-AGW should expect to receive RTP packets containing the indicated number of channels and may use this information when deciding upon the required resources.
Different number of channels in the ch-send parameter in the local descriptor and the ch-recv parameter in the remote descriptors is an error situation, but it is permissible that this parameter is only supplied in one of those descriptors. | The IMS-AGW shall send RTP packets containing the indicated number of channels.
Different number of channels in the ch-send parameter in the local descriptor and the ch-recv parameter in the remote descriptors is an error situation, but it is permissible that this parameter is only supplied in one of those descriptors. | +| mode-set
(NOTE 4) | For AMR-WB IO mode, the IMS-AGW should expect to receive RTP packets using only the indicated mode-set and may use this information when deciding upon the required resources.
The IMS-AGW shall also send RTP packets only using the indicated mode-set.
Different mode-set values in the local and remote descriptors are an error situation, but it is permissible that this parameter is only supplied in one of those descriptors. | For AMR-WB IO mode, the IMS-AGW should expect to receive RTP packets using only the indicated mode-set and may use this information when deciding upon the required resources.
The IMS-AGW shall also send RTP packets only using the indicated mode-set.
Different mode-set values in the local and remote descriptors are an error situation, but it is permissible that this parameter is only supplied in one of those descriptors. | +| mode-
change- | For AMR-WB IO mode, the IMS-AGW should expect to receive packets with this mode- | For AMR-WB IO mode, the IMS-AGW shall use this mode-change-period when sending packets. | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| period
(NOTE 3) | change-period and may use this information when deciding upon the required resources. | | +| mode-change-capability
(NOTE 6) | For AMR-WB IO mode, mode-change-capability with value 2 indicates that the IMS-AGW should expect to be requested to send packets with restricted mode-change-period and may use this information when deciding upon the required resources. | No IMS-AGW handling of this parameter is defined. | +| mode-change-neighbor
(NOTE 3) | The IMS-AGW should expect to receive packets with this mode-change-period and may use this information when deciding upon the required resources. | The IMS-AGW shall use this mode-change-period when sending packets. | +| max-red
(NOTE 5) | The IMS-AGW should expect to receive packets with redundancy up to the indicated max-red value and may use this information when deciding upon the required resources. | The IMS-AGW shall only send packet with redundancy up to the indicated max-red value. | +| 3gpp_mtsi_app_adapt
(NOTE 4) | The IMS-AGW should expect to receive RTCP APP packets of the indicated types and may use this information when deciding upon the required resources. | The IMS-AGW may send RTCP APP packets of the indicated types. The IMS-AGW shall not send other RTCP APP packets. If the parameter is not supplied, the IMS-AGW shall not send any RTCP APP packets. | +| NOTE 1: This MIME parameter of the EVS RTP payload type is defined in 3GPP TS 26.445 [51]. The values and the defaults if a parameter is omitted, as defined in 3GPP TS 26.445 [51] shall apply. | | | +| NOTE 2: This number of channels are encoded as "encoding parameters" of the SDP "a=rtpmap" attribute defined in IETF RFC 4566 [53]. | | | +| NOTE 3: This MIME parameter of the EVS RTP payload type relates to AMR-WB IO mode and is defined in IETF RFC 4867 [54]. The values and the defaults if a parameter is omitted, as defined in IETF RFC 4867 [54] shall apply. | | | +| NOTE 4: This SDP attribute is defined in 3GPP TS 26.114 [21]. It applies to all codecs offered in an SDP media line. However, some values are specific to EVS. | | | +| NOTE 5: This MIME parameter of the EVS RTP payload type is defined in IETF RFC 4867 [54]. The values and the defaults if a parameter is omitted, as defined in IETF RFC 4867 [54] shall apply. | | | +| NOTE 6: This MIME parameter of the EVS RTP payload type relates to AMR-WB IO mode and is defined in IETF RFC 4867 [54]. The values and the defaults if a parameter is omitted, as defined in 3GPP TS 26.445 [51], shall apply. | | | +| NOTE 7: The frame erasure rate indicator for the channel-aware mode has two permissible values (LO, HI) and this indicator has to be initialized to HI, as specified in clause 5.8.4 of 3GPP TS 26.445 [51]. | | | +| NOTE 8: If both the dtx and the dtx-recv parameter are provided either in the local or in the remote descriptor, both parameters will have the same value within that descriptor. | | | + +### 5.13.4 Handling of the OPUS speech and audio codec for WebRTC + +The OPUS speech and audio codec is defined in IETF RFC 6716 [50]. Its RTP payload type is defined in IETF RFC 7587 [56]. + +The eP-CSCF and the eIMS-AGW should support transcoding to and from the OPUS speech codec. If they do so, the procedures in the present clause apply. + +When receiving an SDP offer from the core network, the IMS-ALG may add an OPUS codec payload type (as specified in IETF RFC 7587 [56]) before forwarding the SDP offer towards the served WebRTC UE (denoted as "codec 3" in figure 10.2.5.2 of 3GPP TS 29.162 [20]). If that OPUS payload type is selected in the SDP answer, the IMS-ALG needs to transcode the OPUS codec. Table 5.13.4.1 describes the IMS-ALG handling of the OPUS codec parameters when the IMS-ALG adds an OPUS payload type to the SDP offer, and that OPUS payload type is selected in the SDP answer. In addition, rules for the parameter handling in IETF RFC 7587 [56] shall apply. + +**Table 5.13.4.1: IMS-ALG handling of OPUS related SDP parameters when the IMS-ALG adds the OPUS payload type to the SDP offer.** + +| Parameter | Handling for OPUS payload type added to the SDP offer to offer transcoding | Handling if offered OPUS payload type is accepted in the SDP answer | +|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxplaybackrate (NOTE) | Should be set according to IMS-AGW capabilities and sampling rates of expected codecs to transcode with (E.g. other codecs in the received SDP offer). | If parameter is contained in the SDP answer, the IMS-ALG should forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor. | +| sprop-maxcapturetrate (NOTE) | Should be set according to IMS-AGW capabilities and sampling rates of expected codecs to transcode with (E.g. other codecs in the received SDP offer). | If parameter is contained in the SDP answer, the IMS-ALG should forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor. | +| maxaveragebitrate (NOTE) | Should be set according to IMS-AGW capabilities and sampling rates of expected codecs to transcode with (E.g. other codecs in the received SDP offer), see IETF RFC 7587 [56]. | If parameter is contained in the SDP answer, the IMS-ALG should forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor. | +| stereo (NOTE) | Should be set to 0 or omitted, unless the expected codecs to transcode with (E.g. other codecs in the received SDP offer) support stereo and the IMS-AGW supports stereo transcoding. | If parameter is contained in the SDP answer, the IMS-ALG should forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor. | +| sprop-stereo (NOTE) | Should be set to 0 or omitted, unless the expected codecs to transcode with (E.g. other codecs in the received SDP offer) support stereo and the IMS-AGW supports stereo transcoding. | If parameter is contained in the SDP answer, the IMS-ALG should forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor. | +| cbr (NOTE) | Should be set or omitted according to IMS-AGW capabilities and used encryption. | If parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor. | +| useinbandfec (NOTE) | Should be set or omitted according to IMS-AGW capabilities and delay budget. | If parameter is contained in the SDP answer, the IMS-ALG should forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor. | +| usedtx (NOTE) | Should be set according to IMS-AGW preferences and DTX capabilities of expected codecs to transcode with (E.g. other codecs in the received SDP offer). | If parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor. | +| NOTE: This MIME parameter of the OPUS RTP payload type is defined in IETF RFC 7587 [56]. It is encapsulated within the SDP "a=fmtp" attribute defined in IETF RFC 4566 [55]. | | | + +When receiving an SDP offer from the served WebRTC UE that contains an OPUS codec payload type, the IMS-ALG may add other payload types before forwarding the SDP offer (denoted as "codec 3" in figure 10.2.5.2 of 3GPP TS 29.162 [20]). If that added payload type is selected in the SDP answer, the IMS-ALG needs to transcode, and may select to transcode to the OPUS codec. Table 5.13.4.2 describes the IMS-ALG handling of the OPUS codec parameters when the IMS-ALG receives the OPUS payload type in the SDP offer, and selects to transcode between the OPUS codec and some other codec. In addition, rules for the parameter handling in IETF RFC 7587 [56] shall apply. + +**Table 5.13.4.2: IMS-ALG handling of OPUS related SDP parameters when the IMS-ALG receives the OPUS payload type to the SDP offer and decides to transcode between the OPUS payload type and some other codec.** + +| Parameter | Handling of OPUS payload type parameter received in the SDP offer | OPUS payload type supplied in the SDP answer | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxplaybackrate (NOTE) | If parameter is contained in the SDP offer, the IMS-ALG should forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | Should be set according to IMS-AGW capabilities and sampling rates of expected codecs to transcode with (E.g. other codecs in the received SDP offer). | +| sprop-maxcapturerate (NOTE) | If parameter is contained in the SDP offer, the IMS-ALG should forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | Should be set according to IMS-AGW capabilities and sampling rates of expected codecs to transcode with (E.g. other codecs in the received SDP offer). | +| maxaveragebitrate (NOTE) | If parameter is contained in the SDP offer, the IMS-ALG should forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | Should be set according to IMS-AGW capabilities and sampling rates of expected codecs to transcode with (E.g. other codecs in the received SDP offer), see IETF RFC 7587 [56]. | +| stereo (NOTE) | If parameter is contained in the SDP offer, the IMS-ALG should forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | Should be set to 0 or omitted, unless the expected codecs to transcode with (E.g. other codecs in the received SDP offer) support stereo and the IMS-AGW supports stereo transcoding. | +| sprop-stereo (NOTE) | If parameter is contained in the SDP offer, the IMS-ALG should forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | Should be set to 0 or omitted, unless the expected codecs to transcode with (E.g. other codecs in the received SDP offer) support stereo and the IMS-AGW supports stereo transcoding. | +| cbr (NOTE) | If parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | Should be set or omitted according to IMS-AGW capabilities and used encryption. | +| useinbandfec (NOTE) | If parameter is contained in the SDP offer, the IMS-ALG should forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | Should be set or omitted according to IMS-AGW capabilities and delay budget. | +| usedtx (NOTE) | If parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | Should be set according to IMS-AGW preferences and DTX capabilities of expected codecs to transcode with (E.g. other codecs in the received SDP offer). | +| NOTE 1: This MIME parameter of the OPUS RTP payload type is defined in IETF RFC 7587 [56]. It is encapsulated within the SDP "a=fmtp" attribute defined in IETF RFC 4566 [55]. | | | + +Table 5.13.4.3 describes the IMS-AGW handling of the OPUS codec parameters. The IMS-AGW should support transcoding of OPUS with at least the bandwidths (sampling rates) which are supported by codec the IMS-AGW is capable to transcode OPUS to/from (e.g. NB for AMR, and WB for AMR-WB). + +**Table 15.3.4.3: IMS-AGW handling of OPUS codec parameters.** + +| Parameter | Handling in local descriptor | Handling in remote descriptor | +|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| maxplaybackrate (NOTE) | The IMS-AGW should expect to receive RTP packets with sampling rates up to the indicated maximum and may use this information when deciding upon the required resources. | The IMS-AGW should send RTP packets with the indicated sampling rate. | +| sprop-maxcapturerate (NOTE) | No IMS-AGW handling of this parameter is defined. | The IMS-AGW should expect to receive RTP packets with sampling rates up to the indicated maximum and may use this information when deciding upon the required resources. | +| maxaveragebitrate (NOTE) | The IMS-AGW should expect to receive RTP packets with average bit rates up to the indicated maximum and may use this information when deciding upon the required resources. | The IMS-AGW shall send RTP packets with average bit rates up to the indicated maximum. | +| stereo (NOTE) | The IMS-AGW should expect to receive RTP packets containing the indicated stereo mode and may use this information when deciding upon the required resources. | The IMS-AGW should send RTP packets containing the indicated stereo mode. | +| sprop-stereo (NOTE) | No IMS-AGW handling of this parameter is defined. | The IMS-AGW should expect to receive RTP packets containing the indicated stereo mode and may use this information when deciding upon the required resources. | +| cbr (NOTE) | The IMS-AGW should expect to receive RTP packets containing the indicated constant bit rate mode and may use this information when deciding upon the required resources. | The IMS-AGW should send RTP packets containing the indicated constant bit rate mode. | +| useinbandfec (NOTE) | The IMS-AGW should expect to receive RTP packets containing the indicated forward error correction mode and may use this information when deciding upon the required resources. | The IMS-AGW should send RTP packets containing the indicated forward error correction mode. | +| usedtx (NOTE) | The IMS-AGW should expect to receive RTP packets containing the indicated DTX mode and may use this information when deciding upon the required resources. | The IMS-AGW should send RTP packets using the indicated DTX mode. | + +NOTE 1: This MIME parameter of the OPUS RTP payload type is defined in IETF RFC 7587 [56]. The default value if a parameter is omitted, as defined in IETF RFC 7587 [56], shall apply. + +## 5.14 Multimedia Priority Service (MPS) Support + +The Multimedia Priority Service (MPS) is specified in 3GPP TS 22.153 [22]. The IMS-ALG and IMS-AGW may support the priority treatment of a call/session identified as an MPS call/session. If MPS is supported, the following functional requirements apply: + +- Upon receipt of the MPS priority information in the call control signalling: + - The IMS-ALG shall recognise the call/session as having priority. + - The IMS-ALG shall send the priority information for a context to the IMS-AGW to enable the priority treatment described below related to the IMS-AGW. + - The IMS-ALG shall apply priority handling to H.248 transactions related to priority calls/sessions when network resources are congested , e.g., preferential treatment in any queues or buffers. + - The IMS-ALG may send the updated priority information and, if DiffServ is used, provision a suitable DSCP marking for the updated MPS priority level to the IMS-AGW if it needs to change the priority information previously communicated to the IMS-AGW for an MPS call/session. + - If the H.248 control association utilises a transport with the possibility for prioritisation, the IMS-ALG may apply priority using the appropriate prioritisation procedures. + +- If the MPS Priority service requires a specific MPS DSCP setting the IMS-ALG shall configure the IMS-AGW to apply a specific MPS DSCP marking to the user data transport packets to indicate that the packets are of a higher priority than those for normal calls. +- If the IMS-AGW receives an indication to apply a specific MPS DSCP marking to the user data transport packets, it shall apply this DSCP marking to the IP headers. + +NOTE 1: Support of Diffserv procedures by the IMS-AGW assumes an operator uses Diffserv for prioritising user plane traffic related to an MPS call/session. + +- When the IMS-ALG marks a Context with priority information, the IMS-AGW may use the priority information for selecting resources for the media and signaling transport with priority. The following actions may be taken by the IMS-AGW if it has reached a congested state: + - i) seize priority reserved resources; or + - ii) if resources are congested, indicate that in aCommand Response error code. + +NOTE 2: The Priority information can be used to derive Layer 2 QoS marking and trigger priority identification and priority treatment for other QoS technologies than Diffserv. + +## 5.15 Coordination of Video Orientation + +The IMS-ALG and the IMS-AGW may support the Coordination of Video Orientation (CVO) as defined in 3GPP TS 26.114 [21]. + +If the IMS-ALG receives an SDP body containing "a=extmap" attribute(s), as defined in IETF RFC 5285 [23], and the "a=extmap" attribute(s) contain CVO URN(s) (i.e. the CVO URN for a 2 bit granularity of rotation and/or the CVO URN for a higher granularity of rotation) as defined in 3GPP TS 26.114 [21], then: + +- a) if the IMS-ALG and the IMS-AGW support the CVO feature: + - the IMS-ALG shall include the "extended RTP header for CVO" information element when seizing resources in the IMS-AGW to indicate the IMS-AGW that it shall allow the RTP header extension for CVO to pass; and + +**Editor's Note:** It is ffs if the IMS-ALG needs to include the "extended RTP header for CVO" information element when seizing terminations of a media agnostic IMS-AGW, or if a media agnostic IMS-AGW always passes any RTP header extension. + +- the IMS-ALG shall forward within SIP signalling, the SDP body received from the preceding node with unmodified "a=extmap" attribute(s) to the succeeding node; or +- b) if the IMS-AGW does not support the CVO feature, the IMS-ALG shall forward within SIP signalling, the SDP body received from the preceding node without any "a=extmap" attributes to the succeeding node. + +NOTE 1: The UE supporting the CVO feature will not send the extended RTP headers for CVO if the UE did not receive any SDP body with the CVO related "a=extmap" attribute. + +If the IMS-AGW supports the CVO feature and has been instructed to pass on the extended RTP header for CVO as described above for both incoming and outgoing terminations then: + +- if the IMS AGW does not apply video transcoding, it shall pass any received RTP CVO header extension to succeeding RTP streams; or +- if the IMS-AGW applies video transcoding, it shall keep the video orientation unchanged during the transcoding and copy the received RTP CVO header extension to the succeeding outgoing RTP stream(s) after transcoding the associated group of packets. + +NOTE 2: IETF RFC 5285 [23] provides a framework for header extensions and can also be used for non-CVO related purposes. It is an implementation decision of the IMS-AGW if it only passes CVO related RTP header extensions, or if it passes any RTP header extension when being instructed with the "extended RTP header for CVO" information element. + +NOTE 3: The behaviour of the IMS-AGW when being instructed with an "extended RTP header for CVO" information element only at one termination is an implementation decision. + +NOTE 4: Unknown IETF RFC 5285 [23] RTP header extensions are ignored by the destination RTP end system. + +## 5.16 Generic image attributes + +The IMS-ALG and the IMS-AGW may support a media-level SDP image attribute "a=imageattr" defined in IETF RFC 6236 [24] to negotiate the image size for sending and receiving video as required by 3GPP TS 26.114 [21]. + +NOTE: The image attribute may be used within the SDP capability negotiation framework and its use is then specified using the "a=acap" parameter. + +If the IMS-ALG: + +- supports the negotiation of the image size; +- receives an SDP body containing the image attribute(s) "imageattr" defined in IETF RFC 6236 [24]; and +- does not support or does not apply the video transcoding procedure defined in clause 5.13; + +the IMS-ALG shall forward the SDP body with unmodified image attribute(s). + +If the IMS-ALG and the IMS-AGW support the ATCF/ATGW functions then during the access transfer procedures the IMS-ALG may apply the procedure described in clause 6.2.14.6 to negotiate and adjust the image size for sending and receiving video of the session. + +## 5.17 TCP bearer connection control + +### 5.17.1 Stateless TCP handling + +An IMS-ALG and IMS-AGW that supports TCP as transport protocol (see IETF RFC 793 [29] and IETF RFC 4145 [30]) shall support the following procedures. + +NOTE 1: It is assumed that pre-Release 12 IMS-ALGs and IMS-AGWs also apply these procedures. + +When receiving an SDP offer or answer containing a media line for a new TCP based media stream (e.g. with "TCP", "TCP/MSRP" as transport protocol), the IMS-ALG: + +- shall indicate "TCP" (for application-agnostic interworking) or "TCP/MSRP" (for application-aware MSRP interworking) as transport protocol to the IMS-AGW; +- shall indicate the TCP port numbers received in the SDP from the remote peer as destination port in the remote descriptor at the termination towards the SDP sender; +- shall request the IMS-AGW to allocate a TCP port number at the destination towards the SDP receiver; +- shall replace the TCP port in the received SDP with the TCP port number allocated by the IMS-AGW and forward the SDP; and +- shall indicate to the IMS-AGW to perform TCP stateless handling by not including the TCP session setup direction attribute at the interconnected terminations in the same context. + +An IMS-AGW receiving an indication of "TCP", or "TCP/MSRP" as transport protocol, but no indication to perform TCP state-aware handling (via information about the directionality of the TCP session setup): + +- shall send a TCP SYN when receiving a TCP SYN at the interconnected termination in the same context; +- shall forward received TCP payload; and +- shall use its own port number as TCP source port numbers and the remote port number received from the IMS-ALG as TCP destination port numbers and calculate a new TCP checksum for all TCP packets it sends. + +NOTE 2: This mode of operation corresponds to the "TCP Relay" mode in ITU-T Recommendation H.248.84 [38]. + +## 5.17.2 State-aware TCP handling + +### 5.17.2.1 General + +An IMS-ALG and IMS-AGW that supports TCP as transport protocol (see IETF RFC 793 [29] and IETF RFC 4145 [30]) may support the procedures specified in clause 5.17.2 for state-aware TCP handling. + +NOTE 1: State-aware TCP handling enables modifications of TCP payloads by the IMS-AGW such as changing the size of the payload and inserting extra protocol layers, e.g. for e2ae media security. + +An IMS-ALG and IMS-AGW that supports state-aware TCP handling shall support the procedures specified in clause 5.17.2.2 and may additionally support the procedures specified in clause 5.17.2.3. + +NOTE 2: The procedures in clause 5.17.2.3 enable TCP connections between two peers behind remote (far-end) NATs without any other intermediate server capable of acting as a TCP B2BUA (such as a messaging server). However, they are not possible if e2e security is applied for MSRP based media. + +### 5.17.2.2 State-aware TCP handling without support of modifying the TCP setup direction + +When the IMS-ALG receives an SDP offer containing a media line for a new TCP based media stream (e.g. with "TCP", "TCP/MSRP" as transport protocol), for that TCP based media stream the IMS-ALG: + +- if no media security is applied, shall indicate "TCP" (for application-agnostic interworking) or "TCP/MSRP" (for application-aware MSRP interworking) as transport protocol to the IMS-AGW; +- if media security is applied, shall indicate a transport protocol according to clause 5.11 to the IMS-AGW; +- shall request the IMS-AGW to allocate a TCP port at the destination towards the SDP answerer; +- shall request the IMS-AGW to allocate a TCP port at the destination towards the SDP offerer; +- shall indicate the TCP port numbers received in the SDP offer as destination in the remote descriptor at the termination towards the SDP offerer; +- shall indicate to the IMS-AGW to perform TCP state-aware handling (by indicating the "actpass" TCP session setup direction at both interconnected terminations in the same context in the local descriptor); +- if supported by the IMS-AGW, may indicate to the IMS-AGW for a given termination to use an incoming TCP connection establishment request (TCP SYN) at that termination as a trigger for sending a TCP connection establishment request at the interconnected termination in the same context; +- if supported by the IMS-AGW, may indicate to the IMS-AGW to discard incoming TCP connection establishment requests; and +- shall replace the TCP port in the received SDP offer with the TCP port number allocated by the IMS-AGW at the termination towards the SDP answerer, shall maintain a received "a=setup:active" or "a=setup:passive" SDP attribute (see IETF RFC 4145 [30]) in the SDP offer without modification, and shall forward the SDP offer. + +When the IMS-ALG then receives the SDP answer containing a media line for a new TCP based media stream, for that TCP based media stream the IMS-ALG: + +- shall indicate the TCP port numbers received in the SDP answer as destination in the remote descriptor at the termination towards the SDP answerer; +- if supported by the IMS-AGW, may indicate to the IMS-AGW for a given termination to use an incoming TCP connection establishment request (TCP SYN) at that termination as a trigger for sending a TCP connection establishment request at the interconnected termination in the same context; +- if the IMS-ALG did not indicate to the IMS-AGW to use the incoming TCP connection establishment request (TCP SYN) at one termination as a trigger for sending a TCP connection establishment request at the interconnected termination in the same context, + +- if the SDP answer contains an "a=setup:active" SDP attribute (see IETF RFC 4145 [30]), shall indicate to the IMS-AGW to start a TCP connection establishment at the termination towards the SDP offerer; and +- if the SDP answer contains an "a=setup:passive" SDP attribute, shall indicate to the IMS-AGW to start a TCP connection establishment at the termination towards the SDP answerer; + +NOTE 1: Clients only supporting MSRP according to IETF RFC 4975 [25] will not use the SDP "a=setup" attribute, but will assign the TCP client role to the SDP offerer. However, in 3GPP (Release 8 onwards), OMA and GSMA the support of IETF RFC 6135 [45] is mandated, and the "a=setup" attribute will thus be used. + +- if the IMS-ALG previously indicated to the IMS-AGW to discard incoming TCP connection establishment requests, shall indicate to the IMS-AGW to process incoming TCP connection establishment requests; and +- shall replace the destination TCP port in the received SDP answer with the TCP port number allocated by the IMS-AGW at the termination towards the SDP offerer, shall maintain the received "a=setup" SDP attribute (RFC 4145 [30]) in the SDP answer without modification, and shall forward the SDP answer. + +An IMS-AGW receiving an indication of "TCP", or "TCP/MSRP" as transport protocol and an indication to perform TCP state-aware handling (via information about the directionality of the TCP session setup): + +- if the IMS-ALG indicated to start a TCP connection establishment at a given termination, shall start the TCP connection establishment at that TCP termination by sending a TCP SYN; +- if the IMS-ALG indicated to discard incoming TCP connection establishment requests, shall discard any incoming TCP connection establishment requests (support optional for the IMS-AGW); +- if + - a) the IMS-ALG indicated to use the incoming TCP connection establishment request (TCP SYN) at one termination as a trigger for sending a TCP connection establishment request at the interconnected termination in the same context, and + - b) the IMS-ALG did not indicate to discard incoming TCP connection establishment requests, + shall send a TCP SYN when receiving a TCP SYN at the interconnected termination in the same context (support optional for the IMS-AGW); +- if + - a) the IMS-ALG did not indicate to use the incoming TCP connection establishment request (TCP SYN) at one termination as a trigger for sending a TCP connection establishment request at the interconnected termination in the same context, and + - b) the IMS-ALG did not indicate to discard incoming TCP connection establishment requests, and + - c) the IMS-ALG already configured the remote IP address and port or requested latching, + shall answer any received TCP SYN at a given termination with appropriate messages according to TCP procedures; +- shall forward received TCP payload, performing any required modifications on the TCP payload according to procedures in other parts of this specification; and +- shall use its own port number as TCP source port and the remote port number indicated by the IMS-ALG as TCP destination port numbers and shall calculate a new TCP checksum for all TCP packets it sends. + +NOTE 2: This mode of operation corresponds to the "TCP Proxy" mode in ITU-T Recommendation H.248.84 [38]. + +### 5.17.2.3 State-aware TCP handling with support of modifying the TCP setup direction + +The IMS-ALG and IMS-AGW shall perform the same procedures as in clause 5.17.2.2 with modification according to the present clause. + +When the IMS-ALG receives an SDP offer containing a media line for a new TCP based media stream (e.g. with "TCP", "TCP/MSRP" as transport protocol), for that TCP based media stream the IMS-ALG: + +- if an "a=setup:active" SDP attribute (see IETF RFC 4145 [30]) is received in an SDP offer towards a served UE that is possibly behind a remote NAT, the IMS-ALG + - should replace this attribute with a "a=setup:actpass" or "a=setup:passive" SDP attribute; and + - shall then not indicate to the IMS-AGW to use the incoming TCP connection establishment request (TCP SYN) at the termination towards the offerer as a trigger for sending a TCP connection establishment request at the interconnected termination in the same context towards the answerer; +- if an "a=setup:active" SDP attribute (see IETF RFC 4145 [30]) is received in an SDP offer from a served UE, the IMS-ALG + - may replace this attribute with a "a=setup:actpass" SDP attribute; and + - shall then not indicate to the IMS-AGW to use the incoming TCP connection establishment request (TCP SYN) at the termination towards the answerer as a trigger for sending a TCP connection establishment request at the interconnected termination in the same context towards the offerer; + +**NOTE 1:** Clients only supporting MSRP according to IETF RFC 4975 [25] will not use the SDP "a=setup" attribute, but will assign the TCP client role to the SDP offerer. However, in 3GPP (Release 8 onwards), OMA and GSMA the support of IETF RFC 6135 [45] is mandated, and the "a=setup" attribute will thus be used. + +- shall indicate to the IMS-AGW to perform TCP state-aware handling, either by indicating the "actpass" TCP session setup direction at both interconnected terminations in the same context in the local descriptors, or by indicating the "passive" TCP session setup direction at both interconnected terminations in the same context. + +When the IMS-ALG then receives the SDP answer containing a media line for a new TCP based media stream, for that TCP based media stream the IMS-ALG: + +- if + - a) the IMS-ALG received an "a=setup:active" SDP attribute in the SDP offer, and + - b) the SDP answer contains an "a=setup:active" SDP attribute, + then + - if the IMS-ALG previously indicated "actpass" TCP session setup direction at both interconnected terminations to the IMS-AGW, shall indicate to the IMS-AGW the "passive" TCP session setup direction at both interconnected terminations in the same context in the local descriptors, and + - shall replace the "a=setup:active" SDP attribute in the SDP answer with an "a=setup:passive" SDP attribute before forwarding the answer. +- if + - a) the IMS-ALG received an "a=setup:active" SDP attribute in the SDP offer, and + - b) the SDP answer contains an "a=setup:passive" SDP attribute, + then + - if the IMS-ALG previously indicated "passive" TCP session setup direction at both interconnected terminations to the IMS-AGW, shall indicate to the IMS-AGW the "actpass" TCP session setup direction at both interconnected terminations in the same context in the local descriptors, and + - shall retain the "a=setup:passive" SDP attribute in the forwarded SDP answer; +- if the IMS-ALG did not indicate to the IMS-AGW to use the incoming TCP connection establishment request (TCP SYN) at one termination as a trigger for sending a TCP connection establishment request at the interconnected termination in the same context, + - if the sent SDP answer towards the offerer contains an "a=setup:active" SDP attribute (RFC 4145 [30]), indicate to the IMS-AGW to start a TCP connection establishment at the termination towards the SDP offerer; and + +- if the received SDP answer contains an "a=setup:passive" SDP attribute, indicate to the IMS-AGW to start a TCP connection establishment at the termination towards the SDP answerer. + +When the IMS-ALG indicated a "passive" TCP setup direction for a termination, the IMS-AGW shall wait for an incoming TCP connection establishment at that termination and shall not start a TCP connection establishment on its own. + +NOTE 2: If the "passive" TCP session setup direction has been indicated to the IMS-AGW at both interconnected terminations, the mode of operation corresponds to the "TCP Merge" mode in ITU-T Recommendation H.248.84 [38]. If the "actpass" TCP session setup direction has been indicated to the IMS-AGW at both interconnected terminations, the mode of operation corresponds to the "TCP Proxy" mode in ITU-T Recommendation H.248.84 [38]. + +## 5.18 Interactive Connectivity Establishment (ICE) + +### 5.18.1 General + +The IMS-ALG and the IMS-AGW may support ICE functionality as specified in IETF RFC 5245 [39] and 3GPP TS 24.229 [11] to support a UE residing behind a remote NAT. The present clause describes the requirements for P-CSCF (IMS-ALG) and IMS-AGW when the ICE procedures are supported. + +Support of full ICE functionality is optional, but if ICE is supported, the IMS-ALG and IMS-AGW shall at least support ICE lite as specified in IETF RFC 5245 [39]. + +An IMS-ALG and IMS-AGW supporting ICE lite may in addition support ICE for TCP according to IETF RFC 6544 [57]. + +NOTE 1: ICE for TCP can be used to offer an alternative transport for media streams with default UDP transport to enable a traversal of UDP-blocking NATs or firewalls. In the present release, the support of ICE for TCP is restricted to media streams with default UDP transport, and to ICE lite. + +The IMS-ALG and IMS-AGW shall only use host candidates as local ICE candidates. + +NOTE 2: IMS-ALG and IMS-AGW are not located behind a NAT (from perspective of the ICE deployment model according to Figure 1 in IETF RFC 5245 [39]). + +The IMS-ALG with IMS-AGW inserted on the media plane shall perform separate ICE negotiation and procedures with the offerer and the answerer and ICE may be applied independently at either side. Furthermore, the IMS-ALG may be configured to apply ICE procedures only towards the access network side. + +When the P-CSCF (IMS-ALG) detects no ICE parameters in the received SDP, it shall not configure the IMS-AGW to apply any ICE and STUN related procedures toward the call leg from where the SDP has been received, and if applicable may apply the remote NAT traversal using latching according to clause 5.4. + +Any IMS-AGW supporting ICE shall advertise its support of incoming STUN continuity check procedures. An IMS-AGW supporting full ICE procedures shall in addition advertise its support for originating STUN connectivity check procedures. + +If the IMS-AGW does not indicate the support of STUN procedures, or if the IMS-ALG is configured not to apply ICE toward a call leg, the IMS-ALG: + +- shall not configure the IMS-AGW to apply STUN procedures; +- shall remove any received SDP candidate information from the SDP it forwards; and +- may apply remote NAT traversal using latching according to clause 5.4. + +### 5.18.2 ICE lite + +If the IMS-ALG is configured to use ICE lite, or supports only ICE lite, or controls an IMS-AGW that only support ICE lite, the procedures in the present clause apply. + +If the IMS-ALG receives an initial SDP offer with ICE candidate information but no "a=ice-lite" attribute, the IMS-ALG: + +- shall not forward the received candidate information in the SDP it sends towards the answerer; +- shall request the IMS-AGW for each media line with UDP as default transport where it decides to use ICE to reserve an ICE host candidate and provide its address information and a related ICE user name fragment and password; + +NOTE 1: Requesting only one host candidate per m-line prevents that the IMS-ALG will receive "a=remote-candidates" SDP attributes in a subsequent SDP. Requesting separate ufrag and password for each media line simplifies H.248 encoding. + +- may request the IMS-AGW for each media line with UDP as default transport where it decides to use ICE to reserve an additional passive TCP ICE host candidate and provide its address information and a related ICE user name fragment and password; +- shall configure the IMS-AGW to act as STUN server at the host candidate address, i.e. to answer STUN connectivity checks; +- may provide received remote ICE candidates and the received related ICE user name fragment and password to the IMS-AGW; +- shall include the host candidate and related ICE user name fragment and password received from the IMS-AGW in the SDP answer it forwards; +- shall include the "a=ice-lite" attribute in the SDP answer it forwards; and +- shall not apply the remote NAT traversal using latching according to clause 5.4. + +If the IMS-ALG receives SDP offer with ICE candidate information and an "a=ice-lite" attribute, the IMS-ALG shall not apply ICE towards that call leg and not include any ICE related SDP attributes in the SDP answer. + +NOTE 2: This avoids that the ICE lite peer needs to send extra SDP offers to complete ICE procedures. + +If the IMS-ALG sends an SDP offer (or forwards a received SDP offer) towards a call leg where ICE is to be applied, the IMS-ALG: + +- shall request the IMS-AGW to reserve a host candidate for each media line with UDP as default transport where it decides to use ICE and provide its address information, user name fragment and password; +- may request the IMS-AGW for each media line with UDP as default transport where it decides to use ICE to reserve an additional passive TCP ICE host candidate and provide its address information and a related ICE user name fragment and password; +- shall configure the IMS-AGW to act as STUN server at the host candidate address, i.e. to answer STUN connectivity checks; +- shall include the host candidate provided by the IMS-AGW and related ICE user name fragment and password in the SDP offer it forwards; and +- shall include the "a=ice-lite" attribute in the SDP offer. + +If the IMS-ALG then receives an SDP answer with candidate information from the call leg where ICE is to be applied, the IMS-ALG: + +- shall not forward the received candidate information in the SDP it sends towards the offerer; +- may provide received remote ICE candidates and the received related ICE user name fragment and password to the IMS-AGW; and +- shall not apply the remote NAT traversal using latching according to clause 5.4. + +After the initial SDP offer-answer exchange, the IMS-ALG can receive a new offer from the peer that includes updated address and port information in the SDP "c=" line, "m=" line, or "a=rtpc" line SDP attributes. If the ICE user name + +fragment and password in the SDP offer differ from the ones received in the previous SDP (i.e. the peer restarts ICE), the IMS-ALG shall apply the same procedures as for the initial SDP offer. + +When receiving a request for a host candidate for a media line, the IMS-AGW shall allocate one host candidate for that media line and send it to the IMS-ALG within the reply. The IP address and port shall be the same as indicated separately as Local IP Resources. The IMS-AGW shall also indicate that it supports ICE lite in the reply. + +For a passive TCP ICE host candidate, the IMS-AGW shall be prepared to receive and answer the TCP connection establishment requests. + +NOTE 3: The TCP connection control procedures in clause 5.17 do not apply to TCP host candidates. + +When receiving a request for an ICE user name fragment and password, the IMS-AGW shall generate an ICE user name fragment and password and send it to the IMS-ALG within the reply. The IMS-AGW shall store the password and user name fragment to be able to authenticate incoming STUN binding request according to clause 7.2 of IETF RFC 5245 [39]. + +When receiving a request to act as STUN server, the IMS-AGW shall be prepared to answer STUN binding request according to clause 7.2 of IETF RFC 5245 [39]. Once a STUN binding request with the "USE-CANDIDATE" flag has been received, the IMS-AGW may send media towards the source of the binding request. + +### 5.18.3 Full ICE + +If the IMS-ALG supports and is configured to use full ICE, and controls an IMS-AGW that supports full ICE, the procedures in the present clause apply. + +If the IMS-ALG receives an initial SDP offer with ICE candidate information, the IMS-ALG: + +- shall not forward the received candidate information in the SDP it sends towards the answerer; +- shall request the IMS-AGW for each media line where it decides to use ICE to reserve an ICE host candidate and provide its address information and a related ICE user name fragment and password; + +NOTE: Requesting only one host candidate per m-line prevents that the IMS-ALG will receive "a=remote-candidates" SDP attributes in a subsequent SDP. Requesting separate ufrag and password for each media line simplifies H.248 encoding. + +- shall configure the IMS-AGW to act as STUN server at the host candidate address, i.e. to answer STUN connectivity checks; +- shall provide received remote ICE candidates and the received related ICE user name fragment and password to the IMS-AGW; +- shall include the host candidate and related ICE user name fragment and password received from the IMS-AGW in the SDP answer it forwards; +- shall determine the role of IMS-ALG in ICE (controlling or controlled) according to clause 5.2 of IETF RFC 5245 [39]; +- shall configure the IMS-AGW to perform connectivity checks in accordance with the determined ICE role; +- shall configure the IMS-AGW to report connectivity check results; +- shall configure the IMS-AGW to report a new peer reflexive candidate if discovered during the connectivity check; and +- shall not apply the remote NAT traversal using latching according to clause 5.4. + +If the IMS-ALG sends an SDP offer (or forwards a received SDP offer) towards a call leg where ICE is to be applied, the IMS-ALG: + +- shall request the IMS-AGW to reserve a host candidate for each media line where it decides to use ICE and provide its address information, ICE user name fragment and password; + +- shall configure the IMS-AGW to act as STUN server at the host candidate address, i.e. to answer STUN connectivity checks; and +- shall include the host candidate provided by the IMS-AGW and related ICE user name fragment and password in the SDP offer it forwards. + +If the IMS-ALG then receives an SDP answer with candidate information from the call leg where ICE is to be applied, the IMS-ALG: + +- shall not forward the received candidate information in the SDP it sends towards the offerer; +- shall provide received remote ICE candidates and the received related ICE user name fragment and password to the IMS-AGW; +- shall determine the role of IMS-ALG in ICE (controlling or controlled) according to clause 5.2 of IETF RFC 5245 [39]; +- shall configure the IMS-AGW to perform connectivity checks in accordance with the determined ICE role; +- shall configure the IMS-AGW to report connectivity check results; +- shall configure the IMS-AGW to report a new peer reflexive candidate if discovered during the connectivity check; and +- shall not apply the remote NAT traversal using latching according to clause 5.4. + +When the IMS-ALG is informed by the IMS-AGW about new peer reflexive candidate(s) discovered by the connectivity checks, it shall configure the IMS-AGW to perform additional connectivity checks for those candidates. + +When the IMS-ALG is informed by the IMS-AGW about successful candidate pairs determined by the connectivity checks, the IMS-ALG shall send a new SDP offer to its peer with contents according to clause 9.2.2.2 of IETF RFC 5245 [39] if it has the controlling role and the highest-priority candidate pair differs from the default candidates in previous SDP. + +After the initial SDP offer-answer exchange, the IMS-ALG can receive a new offer from the peer that includes updated address and port information in the SDP "c=" line, "m=" line, or "a=rtpc" line SDP attributes. If the ICE user name fragment and password in the SDP offer differ from the ones received in the previous SDP (i.e. the peer restarts ICE), the IMS-ALG shall apply the same procedures as for the initial SDP offer. + +When receiving a request for a host candidate for a media line, the IMS-AGW shall allocate one host candidate for that media line and send it to the IMS-ALG within the reply. The IP address and port shall be the same as indicated separately as Local IP Resources. + +When receiving a request for an ICE user name fragment and password, the IMS-AGW shall generate an ICE user name fragment and password and send it to the IMS-ALG within the reply. The IMS-AGW shall store the password and user name fragment to be able to authenticate incoming STUN binding request according to clause 7.2 of IETF RFC 5245 [39]. + +When receiving a request to act as STUN server, the IMS-AGW shall be prepared to answer STUN binding request according to clause 7.2 of IETF RFC 5245 [39]. Once a STUN binding request with the "USE-CANDIDATE" flag has been received, the IMS-AGW may send media towards the source of the binding request. + +When receiving a request to perform connectivity checks and to report connectivity check results, the IMS AGW: + +- shall compute ICE candidate pairs according to clause 5.7 of IETF RFC 5245 [39]; +- shall schedule checks for the ICE candidate pairs according to clause 5.8 of IETF RFC 5245 [39]; +- shall send STUN connectivity checks for the scheduled checks according to clause 7.1 of IETF RFC 5245 [39]; +- shall inform the IMS-ALG about successful candidate pairs determined by the connectivity checks; +- shall inform the IMS-ALG about new peer reflexive candidate(s) discovered by the connectivity checks; and +- should send media using the highest priority candidate pair for which connectivity checks have been completed. + +## 5.18.4 STUN consent freshness for WebRTC + +The eIMS-AGW, which implements ICE, shall support the STUN consent freshness test defined in IETF RFC 7675 [49]. + +If the eP-CSCF supports and is configured to use full ICE, and controls an eIMS-AGW that supports full ICE, to initiate the STUN consent freshness procedures, the eP-CSCF shall request the eIMS-AGW to perform periodic STUN consent tests towards the WIC (WebRTC IMS Client). On receipt of requesting STUN consent test signal, the eIMS-AGW shall start sending STUN binding requests in order to verify consent, based on the interval value indicated by the eP-CSCF, after the transport address has been selected via the ICE-related connectivity check. + +If the eP-CSCF is configured to use ICE lite, or supports only ICE lite, or controls an IMS-AGW that only support ICE lite, the eIMS-AGW shall not send STUN consent request checks. Instead, the IMS-AGW shall act as STUN server and only respond to incoming STUN binding requests received from the WIC (WebRTC IMS Client). + +If STUN consent expires on a given transport address, the eIMS-AGW shall stop forwarding media on that transport address, and inform the eP-CSCF about the failure. In addition, the eIMS-AGW shall stop sending STUN consent request checks on the transport address. Once upon an indicated test failure, the eP-CSCF may request for appropriate action related to the H.248 stream, such as the removal of the H.248 stream. + +## 5.19 MSRP handling + +### 5.19.1 General + +The IMS-ALG and IMS-AGW may support MSRP handling. If they support MSRP handling, they shall apply the procedures as specified in the present clause 5.19. + +For WebRTC terminations, MSRP is transferred over data channels. For WebRTC terminations the procedures in the present clause 5.19 shall apply with the modifications described in clause 5.19.6. + +The IMS-AGW shall support application-agnostic MSRP handling. + +NOTE 1: Application-agnostic MSRP handling suffices when IETF RFC 6714 [26] or IETF draft-ietf-simple-msrp-sessmatch is supported by both ends (e.g. between Rel-8 onwards IMS UEs) and no MSRP relays are used. + +NOTE 2: The expired IETF draft-ietf-simple-msrp-sessmatch modifies the session matching procedure defined by IETF RFC 4975 [25]. A peer applying IETF draft-ietf-simple-msrp-sessmatch will only compare the session-id part of the first MSRP URI in the SDP "a=path" attribute with the session-id part of the first MSRP URI in the "To-Path" header field of the received MSRP packets. This draft is still used by OMA and GSMA as an alternative option to IETF RFC 6714 [26]. + +The IMS-AGW may in addition support application-aware MSRP interworking, as described in clause 5.19.5.. + +NOTE 3: Application-aware MSRP interworking enables direct communication: + +- between an MSRP client applying IETF RFC 6714 [26] and an MSRP client applying IETF RFC 4975 [25] without extensions by either IETF RFC 6714 [25] or IETF draft-ietf-simple-msrp-sessmatch. +- between an MSRP client applying IETF draft-ietf-simple-msrp-sessmatch and an MSRP client applying IETF RFC 4975 [25] without extensions by either IETF RFC 6714 [26] or IETF draft-ietf-simple-msrp-sessmatch. +- between an MSRP client applying IETF RFC 6714 [26] and an MSRP client applying IETF draft-ietf-simple-msrp-sessmatch. +- between two MSRP clients applying IETF RFC 4975 [25] without extensions by either IETF RFC 6714 [26] or IETF draft-ietf-simple-msrp-sessmatch. + +However, to address these scenarios, application aware MSRP interworking can also be applied in other network elements than the IMS-ALG and IMS-AGW, for instance in an CPM Participating Function or CPM Interworking Function as defined in OMA-TS-CPM\_Conversation\_Function-V2 [46]. + +NOTE 4: MSRP relays external to the IMS-AGW are not supported in the present release. + +The IMS-ALG procedures depend on whether the IMS-AGW applies application-agnostic MSRP interworking or application-aware MSRP interworking, and on the MSRP extensions applied on the interconnected call legs. The support of related procedures in clauses 5.19.2 to 5.19.4 below are all optional, but the IMS-ALG shall support at least one of them. + +**Table 5.19.1-1: Behaviour of MSRP clients and related IMS-ALG and IMS-AGW procedures for MSRP with different extensions.** + +| IETF document: | MSRP client takes destination address for TCP connection setup from | Session matching at MSRP client between SDP path and "To-Path" in MSRP messages includes address information | IMS-AGW needs to insert own address into "To-Path" in MSRP messages | IMS-ALG needs to modify SDP path attribute | Support of extension is negotiated | +|------------------------------------------|---------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|--------------------------------------------|------------------------------------| +| IETF RFC 4975 [25] | SDP MSRP path attribute | Yes | Yes | Yes | - | +| Expired draft-ietf-simple-msrp-sessmatch | SDP MSRP path attribute | No | No | Yes | No | +| IETF RFC 6714 [26] | SDP c-line and m-line | Yes | No
(Yes if fallback to IETF RFC 4975 [6] occurs and is supported) | No | Yes, via SDP CEMA attribute | + +## 5.19.2 IMS-ALG procedures to support IETF RFC 6714 with application agnostic MSRP handling by the IMS-AGW + +A peer applying IETF RFC 6714 [26] will include the "a=msrp-cema" SDP attribute in the first SDP offer it sends. + +If the "a=msrp-cema" SDP attribute is contained in an SDP offer, the IMS-ALG: + +- shall ensure that the IMS-AGW performs application agnostic MSRP handling by not configuring the IMS-AGW to apply application-aware MSRP interworking; +- shall indicate "TCP" or "TCP/TLS" (if e2ae media security is applied) as transport protocol to the IMS-AGW; +- shall forward the "a=path" attribute and the "a=msrp-cema" SDP attribute in the SDP offer without modification; and +- shall forward the "a=path" SDP attribute in the corresponding SDP answer without modification (even if the "a=msrp-cema" SDP attribute is not contained in the answer). + +NOTE: If the "a=msrp-cema" SDP attribute is not contained in the SDP answer and the "a=path" SDP attribute is not modified, the offerer will discover a mismatch and send a new SDP offer without the "a=msrp-cema" SDP attribute according to IETF RFC 6714 [26] procedures. + +If the "a=msrp-cema" SDP attribute is not contained in an SDP offer, the IMS ALG shall either apply the procedures in clause 5.19.3 or clause 5.19.4 (if supported). + +## 5.19.3 IMS-ALG procedures to support IETF draft-ietf-simple-msrp-sessmatch with application agnostic MSRP handling by the IMS-AGW + +A peer applying the expired IETF draft-ietf-simple-msrp-sessmatch will not include the "a=msrp-cema" SDP attribute in the SDP it sends, and will only compare the session-id part of the first MSRP URI in the SDP "a=path" attribute with the session-id part of the first MSRP URI in the "To-Path" header field of the first received MSRP packet. + +If the "a=msrp-cema" SDP attribute is not contained in an SDP offer, the IMS-ALG: + +- shall ensure that the IMS-AGW performs application agnostic MSRP handling by not configuring the IMS-AGW to apply application-aware MSRP interworking; + +- shall indicate "TCP" or "TCP/TLS" (if e2ae media security is applied) as transport protocol to the IMS-AGW; and +- shall replace the IP address and TCP port in the only entry of the "a=path" SDP attribute in received SDP offer or answer with the IP address and TCP port allocated for the media stream at the IMS-AGW before forwarding the SDP. + +#### 5.19.4 IMS-ALG procedures for application aware MSRP interworking by the IMS-AGW + +The IMS ALG: + +- shall provide the SDP "a=path" attribute, as received in SIP/SDP signalling, to the IMS-AGW as "MSRP Path" with the remote descriptor of the corresponding call leg; +- shall ensure that the IMS-AGW performs application aware MSRP interworking by configuring the IMS-AGW to apply application-aware MSRP interworking; and +- shall indicate "TCP/MSRP" or "TCP/TLS/MSRP" (if e2ae media security is applied) as transport protocol to the IMS-AGW. + +If interworking between an MSRP client applying IETF RFC 6714 [26] and an MSRP client applying IETF RFC 4975 [25] without extensions by either IETF RFC 6714 [26] or IETF draft-ietf-simple-msrp-sessmatch needs to be supported, the IMS ALG should: + +- when receiving an SDP offer including the "a=msrp-cema" SDP attribute, include the "a=msrp-cema" SDP attribute in the SDP answer on that call leg; +- when sending an SDP offer, include the "a=msrp-cema" SDP attribute; and +- if the "a=msrp-cema" SDP attribute is not contained in a received SDP answer and the SDP c/m-line address information does not match the "a=path" attribute, send a new SDP offer without the "a=msrp-cema" SDP attribute according to IETF RFC 6714 [26] procedures. + +NOTE: The second SDP offer can be omitted if the IMS-ALG knows that there is no SBC in the path (e.g. between the IMS-ALG and the UE). + +#### 5.19.5 Application-aware MSRP interworking at the IMS-AGW + +The IMS-AGW shall apply application-aware MSRP interworking either if being statically configured to do so, or if being instructed from the IMS-ALG. Support of dynamic instructions from the IMS-ALG is optional. + +To apply application-aware MSRP interworking, the IMS-AGW: + +- shall modify the MSRP "To-Path" header field in application (i.e. MSRP) data by replacing the IP address and TCP port of the only entry with the corresponding information in the "MSRP path" provided by the IMS\_ ALG while retaining the MSRP session ID part of the entry as received in the MSRP "To-Path"; and +- shall forward the MSRP data without further modification. + +NOTE: MSRP session matching will be performed only by the MSRP clients. + +#### 5.19.6 MSRP data channels + +MSRP signalling can be transferred over WebRTC data channels as a data channel sub-protocol using the SDP offer/answer negotiation according to IETF RFC 8873 [62]. WebRTC data channels are described in clause 5.20.2. For WebRTC terminations the procedures in clause 5.19 shall apply with the modifications described in the present clause. + +Within received SIP/SDP signalling related to a WebRTC termination MSRP contents within a data channel will be marked with the "subprotocol=""MSRP"" subfield in the "a=dcmmap" SDP attribute according to IETF RFC 8864 [65]. The MSRP related "a=msrp-cema", "a=path", "a=accept-types" and "a=setup" SDP attributes will be encapsulated in "a=dcsa" SDP attributes according to IETF RFC 8864 [65]. The "a=msrp-cema" can be present or omitted in received SIP/SDP signalling related to a termination where no WebRTC data channel is to be used, but IETF RFC 6714 [26] is + +always applicable for MSRP within WebRTC data channels and the "a=msrp-cema" shall be present in SIP/SDP signalling related to a WebRTC termination. + +When receiving an SDP offer including such MSRP related information in SIP/SDP signalling related to a WebRTC data channel, and forwarding the SDP offer towards a termination where no WebRTC data channel is to be used, the IMS-ALG shall: + +- describe each MSRP data channel in a separate SDP media line in the SDP offer it forwards; +- include "a=msrp-cema", "a=path", "a=accept-types" and "a=setup" SDP attributes received encapsulated in "a=dcsa" SDP attributes in the forwarded SDP offer for the corresponding MSRP media line(s) without the encapsulation; and +- execute the procedures in the clause 5.19 as if an "a=msrp-cema" SDP attribute had been received. +- execute the procedures in the clause 5.19 as if an "a=msrp-cema" SDP attribute had been received. + +When receiving an SDP offer including MSRP related information without an indication of WebRTC data channel usage in SIP/SDP signalling, and forwarding the SDP offer towards a termination where a WebRTC data channel is to be used, the IMS-ALG shall: + +- describe each received MSRP media line as a separate data channel; +- include any received "a=msrp-cema", "a=path", "a=accept-types" and "a=setup" SDP attributes received for the MSRP media line(s) encapsulated in "a=dcsa" SDP attributes in the forwarded SDP offer; +- if the "a=msrp-cema" SDP attribute was not received for the MSRP media line(s), include "a=msrp-cema" SDP attribute for the corresponding MSRP media line(s) encapsulated in "a=dcsa" SDP attribute in the forwarded SDP offer; +- include an "subprotocol="MSRP"" subfield in a "a=demap" SDP attribute; and +- not include the "max-retr", "max-time" and "ordered" parameters in the "a=demap" SDP attribute. + +For terminations with MSRP within a WebRTC data channel, the IMS-ALG shall: + +- indicate a transport protocol according to clause 5.20.2 to the eIMS-AGW; and +- for application aware MSRP interworking: + - a) indicate that MSRP is used within the data channel to the eIMS-AGW; and + - b) provide the SDP "a=path" attribute encapsulated in "a=dcsa" SDP attribute, as received in SIP/SDP signalling, to the eIMS-AGW as "Encapsulated MSRP Path" with the remote descriptor of the corresponding call leg. + +## 5.20 Web Real-Time Communication (WebRTC) + +### 5.20.1 General + +The following requirements apply for a "P-CSCF enhanced for WebRTC (eP-CSCF)" and an "IMS-AGW enhanced for WebRTC (eIMS-AGW)": + +- End-to-access-edge security for RTP based media using DTLS-SRTP, clause 5.11.2.4, shall be supported. +- End-to-access-edge security for RTP based media using DTLS-SRTP over TCP transport, clause 5.11.2.5, may be supported. +- Interactive Connectivity Establishment (ICE), clause 5.18, shall be supported. ICE for TCP may be supported in addition to offer an alternative transport for UDP based media as specified in clause 5.18. +- STUN Consent Freshness, clause 5.18.4, shall be supported. + +- RTP/RTCP transport multiplexing, clause 5.9.2 shall be supported. +- Audio transcoding, clause 5.13, shall be supported. Video transcoding may be supported. +- Transcoding to/from the Opus Audio Codec, IETF RFC 6716 [50], clause 5.13.4, should be supported. +- Procedures for the eIMS-AGW to act as a data channel endpoint should be supported according to IETF draft ietf-rtcweb-data-channel [61], see clause 5.20.2. +- Data channels used for WebRTC to transport MSRP as a data channel sub-protocol, i.e. MSRP data channels between the UE and the eIMS-AGW should be supported according to IETF RFC 8873 [62] and the procedures in clause 5.19.6. SCTP/DTLS/UDP should be transported as protocol stack for data channels and SCTP/DTLS/TCP may be supported. +- Data channels used for WebRTC to transport T.140 (used for Global Text Telephony, GTT) as a data channel sub-protocol, i.e. T.140 data channels between the UE and the eIMS-AGW may be supported according to IETF RFC 8865 [75] and the procedures in clause 5.20.2.6. +- The media plane optimization procedures in clause 5.20.3 may be supported. + +## 5.20.2 WebRTC data channel + +### 5.20.2.1 General + +In the WebRTC framework, non-media data communication between UEs is handled by using data channels according to IETF RFC 8831 [61]; within SCTP (see IETF RFC 4960 [63]), encapsulated in DTLS (see IETF RFC 6347 [32]). The related SDP signalling is described in IETF RFC 8841 [64] and IETF RFC 8864 [65]. + +### 5.20.2.2 Data Channel Establishment + +Data channels can use either a SCTP/DTLS/UDP or SCTP/DTLS/TCP based transport. If the eP-CSCF (IMS-ALG) and the eIMS-AGW support data channels, they shall support the SCTP/DTLS/UDP based transport and may support the SCTP/DTLS/TCP based transport. + +NOTE 1: This clause assumes that the UDP based option is used as default ICE candidate for WebRTC terminations. TCP based transport can be offered in addition as alternative transport using ICE for TCP as specified in clause 5.18. + +Upon receipt of an SDP offer containing SDP attributes for new SCTP associations and/or new data channels according to IETF RFC 8841 [64] and IETF RFC 8864 [65] from the WebRTC access network, the eP-CSCF (IMS-ALG): + +- shall check if a new DTLS association and SCTP association is to be set up or an existing DTLS association and SCTP association are to be reused (NOTE 1) according to IETF RFC 8842 [81] and IETF RFC 8841 [64]; + +NOTE 2: The present procedures assume that the DTLS association and SCTP association are established together. A separate establishment of DTLS association and SCTP association is not supported in the present release. + +- if a new DTLS connection and SCTP association are to be set up: + - 1) shall request a new H.248 stream group (see details below) on a new termination towards the WebRTC access network from the eIMS-AGW; + - 2) shall request a deaggregation stream to handle the SCTP association and DTLS association, and for the H.248 deaggregation stream: + - a) shall send the remote UDP port and SCTP port to the eIMS-AGW; + - b) shall request the local UDP port and SCTP port from the eIMS-AGW; + - c) shall insert the local UDP port and SCTP port received from the eIMS-AGW into the SDP answer towards the WebRTC access network; + +- d) shall provide the remote SCTP maximum message size, as received within the "a=max-message-size" SDP attribute, to the eIMS-AGW; +- e) shall request the eIMS-AGW to provide its own local SCTP maximum message size; +- f) shall insert the SCTP maximum message size received from the eIMS-AGW into the SDP answer towards the WebRTC access network; +- g) shall check the received value of the "a=setup" SDP attribute to determine if the eIMS-AGW needs to act as DTLS client or DTLS server. When the received value is equal to: + - i) "active" the eIMS-AGW needs to act as DTLS server; + - ii) "passive" the eIMS-AGW needs to act as DTLS client; or + - iii) "actpass" the eP-CSCF (IMS-ALG) shall decide if the eIMS-AGW needs to act as DTLS client or DTLS server; +- h) if the eIMS-AGW needs to act as DTLS client; + - i) shall provide the Establish (D)TLS session information element to request the eIMS-AGW to start the DTLS session setup; and + - ii) shall provide the Establish SCTP association information element to request the eIMS-AGW to start the SCTP association setup as soon as DTLS association is data transfer ready; + +NOTE 3: Such an H.248 control leads to the emulation of "simultaneous SCTP association establishment" (i.e., the eIMS-AGW behaves according to clause 5.2.1 of IETF RFC 4960 [63]). + +- i) if the eIMS-AGW needs to act as DTLS server, may include the Notify (D)TLS session establishment information element to request the eIMS-AGW to notify the eP-CSCF (IMS-ALG) about an incoming DTLS session setup; + - j) shall indicate to the eIMS-AGW "UDP/DTLS/SCTP" as transport protocol; + - k) shall provide to the eIMS-AGW the Remote certificate fingerprint information element with the value of the received fingerprint SDP attribute(s) from the WIC; + - l) shall include the Local certificate fingerprint Request information element to request the certificate fingerprint of the eIMS-AGW; and + - m) shall indicate to the eIMS-AGW the SCTP stream identifiers of H.248 component stream(s) (i.e. SCTP streams corresponding to data channels) to be de-multiplexed; +- 3) shall indicate the grouping of the H.248 deaggregation stream and the H.248 component stream(s) with SCTP semantics to the eIMS-AGW; and + - 4) shall request the eIMS-AGW to provide a notification when receiving an SCTP stream reset request and to autonomously answer that SCTP stream reset request; +- if an existing DTLS association and SCTP association are to be reused, shall modify the existing termination for that SCTP association by: + - 1) indicating to the eIMS-AGW the SCTP stream identifiers of H.248 component stream(s) (i.e. SCTP streams corresponding to data channels) to be de-multiplexed; and + - 2) indicating the H.248 stream grouping of the H.248 deaggregation stream and the H.248 component stream(s) with SCTP semantics to the eIMS-AGW; + +NOTE 4: The information element relates to an H.248 Stream Group (SG) which allows: + +- a) to separate the protocol stack in the levels of data channels (DC) and the commonly shared lower transport, and +- b) to support multiple DCs. The SG is part of the WebRTC termination. + +- for each data channel to be established: + +- 1) shall reserve a separate H.248 stream at the termination towards the WebRTC access network; + +- 2) shall provide the SCTP stream identifier to the eIMS-AGW; +- 3) shall provide the information received in the SDP "a=dcmmap" attribute to the eIMS-AGW; + +NOTE 5: For MSRP and T.140 within data channels, the default values of the "max-retr" parameter, the "max-time" parameter and the "ordered" parameter apply and those parameters are not included. + +- 4) if application aware handling of the contents within the data channel is required, may provide the information received in SDP "a=dcsa" attributes to the eIMS-AGW as "remote dcsa" information elements, taking into account the specific procedures defined for the subprotocols within the data channel; + - 5) if the first data channel is to be established, shall reserve a termination towards the core network; + - 6) shall reserve a H.248 stream towards the core network; + - 7) shall indicate to the eIMS-AGW how to interwork the information send or received in data channels with information send or received on streams towards the IMS core network by using the same H.248 stream identifier for the H.248 stream towards the WebRTC access network and towards the core network; + - 8) shall indicate to the eIMS-AGW an appropriate transport protocol towards the IMS core network (e.g. "TCP" for MSRP) for the media described in the dcmmap attribute for the data channel when reserving the transport addresses/resources towards the IMS core network; + - 9) shall provide an appropriate media line for the media described in the dcmmap attribute in the SDP offer towards the IMS core network; and + - 10) should de-encapsulate SDP attributes within the received SDP "a=dcsa" attributes in the SDP offer and include the de-encapsulated SDP attributes in the SDP offer towards the IMS core network as media attributes for the media line corresponding to the data channel, taking into account specific procedures defined for the subprotocol within the data channel; and +- shall remove the "a=setup", "a=connection" "a=dcmmap" and possible "a=dcsa" SDP attributes and fingerprint information from the SDP offer towards the IMS core network. + +Upon receipt of a corresponding SDP answer from the IMS core network, if the SDP answer does not indicate that media plane optimization is to be applied (see clause 5.20.3.2), the eP-CSCF (IMS-ALG): + +- instead of the media line(s) describing media that are to be transported within data channel(s), shall provide an "m=" line with the transport protocol "UDP/DTLS/SCTP"; +- shall insert the fingerprint SDP attribute with the value of the Local certificate fingerprint information element received from the eIMS-AGW; +- if the IMS-ALG received from the WIC an SDP offer with "a=tls-id" media-level SDP attribute for the DTLS association: + - 1) if an existing DTLS association is reused, shall include the "a=tls-id" SDP attribute with the value assigned to that DTLS association in the SDP answer which the IMS-ALG sends to the WIC; and + - 2) if a new DTLS association is to be established, shall include the "a=tls-id" SDP attribute with a new unique value in the SDP answer which the IMS-ALG sends to the WIC; +- shall insert the "a=setup" SDP attribute with the value: + - 1) "active" if the eP-CSCF (IMS-ALG) requested the eIMS-AGW to act as DTLS client; or + - 2) "passive" if the eIMS-AGW shall take the DTLS server role; and +- for each received media line describing media that are to be transported within a data channel: + - 1) shall insert an "a=dcmmap" attribute with the same values for the SCTP stream identifier, "subprotocol" and "label" parameters as received in the SDP offer, and with possible values for the "max-retr", "max-time", and "ordered" parameters according to the requirements of the transported data flow and capabilities of the eIMS-AGW; + +NOTE 6: For MSRP and T.140 within data channels, the default values of the "max-retr" parameter, the "max-time" parameter and the "ordered" parameter apply and those parameters are not included. + +- 2) should insert SDP "a=dcsa" attributes into the SDP answer towards the WebRTC access network encapsulating subprotocol specific SDP attributes received in the SDP answer, taking into account specific procedures defined for the subprotocol within the data channel; +- 3) shall provide the information in the sent SDP "a=dmap" attribute to the eIMS-AGW; and +- 4) may provide the information within the sent SDP "a=dcsa" attributes to the eIMS-AGW as "local dcsa" information elements, taking into account specific procedures defined for the subprotocol within the data channel. + +Upon receipt of an SDP offer from the IMS core network for new media streams that need to be transported within a WebRTC data channel on the WebRTC access network, if the SDP offer does not indicate that media plane optimization is to be applied (see clause 5.20.3.3), the eP-CSCF (IMS-ALG): + +- shall determine if it can reuse an existing DTLS association and SCTP association or if it needs to set up a new DTLS association and SCTP association; +- if a new DTLS association and SCTP association are to be set up: + - 1) shall request a new termination towards the WebRTC access network from the eIMS-AGW; + - 2) shall request a deaggregation stream to handle the SCTP association and DTLS association, and for the H.248 deaggregation stream: + - a) shall request the local UDP port and SCTP port from the eIMS-AGW; + - b) shall insert the local UDP port and SCTP port received from the eIMS-AGW into the SDP offer towards the WebRTC access network; + - c) shall request the eIMS-AGW to provide its own local SCTP maximum message size; + - d) shall insert the SCTP maximum message size received from the eIMS-AGW into the SDP offer towards the WebRTC access network; + - e) shall add an SDP "a=setup" attribute with value "actpass" into the SDP offer; + - f) shall indicate to the eIMS-AGW "UDP/DTLS/SCTP" as transport protocol; + - g) shall include the Local certificate fingerprint Request information element to request the certificate fingerprint of the eIMS-AGW; + - h) shall insert the fingerprint SDP attribute with the value of the Local certificate fingerprint information element received from the eIMS-AGW into the SDP offer towards the WebRTC access network; and + - i) shall indicate to the eIMS-AGW the SCTP stream identifiers of H.248 component stream(s) (i.e. SCTP streams corresponding to data channels) to be de-multiplexed; + - 3) shall indicate the H.248 stream grouping of the H.248 deaggregation stream and the H.248 component stream(s) with SCTP semantics to the eIMS-AGW; and + - 4) shall request the eIMS-AGW to provide a notification when receiving an SCTP stream reset request and to autonomously answer that SCTP stream reset request; +- if an existing DTLS association and SCTP association are to be reused, shall modify the existing termination towards the WebRTC access network for that SCTP association by: + - 1) indicating to the eIMS-AGW the SCTP stream identifiers of H.248 component stream(s) (i.e. SCTP streams corresponding to data channels) to be de-multiplexed; and + - 2) indicating the H.248 stream grouping of the H.248 deaggregation stream and the H.248 component stream(s) with SCTP semantics to the eIMS-AGW; +- instead of the media line(s) describing media that are to be transported within data channel(s), shall provide an "m=" line with the transport protocol "UDP/DTLS/SCTP"; + +- shall insert an "a=tls-id" SDP attribute in the SDP offer with a new or reused value (depending on whether an existing DTLS association is reused); and +- for each received media line describing media that are to be transported within a data channel: + - 1) shall reserve a separate H.248 stream at the termination towards the WebRTC access network; + - 2) shall insert an "a=dcmap" attribute with an unused SCTP stream identifier, and with "subprotocol" and "label" parameters according to the requirements of the transported data flow, and with possible values for the "max-retr", "max-time", and "ordered" parameters according to the requirements of the transported data flow and capabilities of the eIMS-AGW; + +NOTE 7: For MSRP and T.140 within data channels, the default values of the "max-retr" parameter, the "max-time" parameter and the "ordered" parameter apply and those parameters are not included. + +- 3) shall provide the SCTP stream identifier to the eIMS-AGW; +- 4) shall provide the information in the sent SDP "a=dcmap" attribute to the eIMS-AGW; +- 5) should insert SDP "a=dcsa" attributes into the SDP offer towards the WebRTC access network encapsulating any subprotocol specific SDP attributes received in the SDP offer, taking into account specific procedures defined for the subprotocol within the data channel; +- 6) if application aware handling of the contents within the data channel is required, may provide the information within the sent SDP "a=dcsa" attributes to the eIMS-AGW as "local dcsa" information elements, taking into account specific procedures defined for the subprotocol within the data channel; +- 7) if the first data channel is to be established, shall reserve a termination towards the core network; +- 8) shall reserve a H.248 stream towards the core network; and +- 9) shall indicate to the eIMS-AGW how to interwork the information sent or received in data channels with information sent or received on terminations and/or streams towards the IMS core network by using the same H.248 stream identifier for the stream towards the WebRTC access network and towards the core network. + +Upon receipt of a corresponding SDP answer from the WebRTC access network, the eP-CSCF (IMS-ALG): + +- if a new DTLS association and SCTP association are to be set up, for the H.248 deaggregation stream to handle the SCTP association and DTLS connection: + - 1) shall send the received remote UDP port and SCTP port to the eIMS-AGW; + - 2) shall include the Remote certificate fingerprint information element with the value of the received fingerprint SDP attribute(s) from the WebRTC access network; + - 3) shall check the received value of the "a=setup" SDP attribute to determine if the eIMS-AGW needs to act as DTLS client or DTLS server. When the received value is equal to: + - a) "active" the eIMS-AGW needs to act as DTLS server; or + - b) "passive" the eIMS-AGW needs to act as DTLS client; + - 4) if the eIMS-AGW needs to act as DTLS client: + - a) shall include the Establish (D)TLS session information element to request the eIMS-AGW to start the DTLS session setup; and + - b) shall provide the Establish SCTP association information element to request the eIMS-AGW to start the SCTP association setup as soon as DTLS connection is data transfer ready; + - 5) if the eIMS-AGW needs to act as DTLS server, may include the Notify (D)TLS session establishment information element to request the eIMS-AGW to notify the eP-CSCF (IMS-ALG) about an incoming DTLS session setup; and + - 6) shall provide the remote SCTP maximum message size, as received within the "a=max-message-size" SDP attribute, to the eIMS-AGW; + +- shall remove the "a=setup", "a=connection" "a=dcmmap" and possible "a=dcsa" SDP attributes and fingerprint information from the SDP answer and indicate the transport protocol "TCP" in the SDP answer towards the IMS core network; and +- for each accepted data channel: + - 1) shall provide the information received in the SDP "a=dcmmap" attribute to the eIMS-AGW; + - 2) if application aware handling of the contents within the data channel is required, may provide the information within the received SDP "a=dcsa" attributes in the SDP answer to the eIMS-AGW as "remote dcsa" information elements, taking into account specific procedures defined for the subprotocol within the data channel; and + - 3) should de-encapsulate SDP attributes within the received SDP "a=dcsa" attributes in the SDP answer and include the de- encapsulated SDP attributes in the SDP answer towards the IMS core network, taking into account specific procedures defined for the subprotocol within the data channel. + +If requested to set up a new DTLS association and SCTP association, the eIMS-AGW shall: + +- allocate the local UDP port and SCTP port, and send them to the eP-CSCF (IMS-ALG); +- when being instructed to start the DTLS bearer session setup, act as a DTLS client and establish the DTLS bearer session; +- upon request from the eP-CSCF (IMS-ALG), provide the SCTP maximum message size; +- upon request from the eP-CSCF (IMS-ALG), select an own certificate, and send the fingerprint of the own certificate to the eP-CSCF (IMS-ALG); +- uniquely associate the certificate fingerprint(s) received from the eP-CSCF (IMS-ALG) with the corresponding DTLS association, and subsequently use the certificate fingerprint(s) to verify the establishment of the DTLS bearer session; +- if the verification of the remote certificate fingerprint(s) during the DTLS bearer session establishment fails, regard the remote DTLS endpoint as not authenticated, terminate the DTLS bearer session and report the unsuccessful DTLS bearer session setup to the eP-CSCF (IMS-ALG); +- upon completion of the DTLS association establishment, set up the SCTP association according to IETF RFC 4960 [63]; and +- deaggregate H.248 component streams upon request from the eP-CSCF (IMS-ALG). + +If the eP-CSCF (IMS-ALG) requests that a termination with an existing SCTP association is being modified, the eIMS-AGW shall reuse an existing DTLS association and SCTP association. + +If the eP-CSCF (IMS-ALG) requests that a new H.248 component stream with a H.248 stream group related to an SCTP association is being reserved, the eIMS-AGW shall set up the data channel according to IETF RFC 8831 [61] procedures. The eIMS-AGW shall also interwork the information sent or received in data channels with information sent or received on terminations and/or streams towards the IMS core network according to the configuration received by the eP-CSCF (IMS-ALG). + +NOTE 8: The handling of priority information that is part of the dcmmap information received from the eP-CSCF (IMS-ALG) is left to the eIMS-AGW implementation. + +## 5.20.2.3 Data Channel Release + +### 5.20.2.3.1 General + +In the present Release, the closure of individual WebRTC data channels (clause 5.20.2.3.2) and the complete release of the entire WebRTC data service (clause 5.20.2.3.3) are supported. + +NOTE 1: The hierarchical protocol stack for WebRTC data ("DC/SCTP/DTLS/(UDP|TCP/IP)") contains up to four levels of user plane bearer control procedures, from top to bottom: + +- 1) DC: SCTP Stream reconfiguration procedures for resetting SCTP Streams; +- 2) SCTP Association: shutdown procedure; +- 3) DTLS: DTLS connection release procedure (apart from resumption and renegotiation procedures); and +- 4) TCP: TCP connection release procedure. (However, TCP transport of WebRTC data channels is not supported in the present Release). + +The present Release does not consider specific release variations at levels 2 to 4, such as the shutdown of an SCTP Association without a DTLS connection release. + +A data channel can be closed before the end of the WebRTC call. In the present Release, the H.248 Stream endpoint related to a data channel may be removed after the closure of the data channel, but a subsequent reuse of the corresponding SCTP Stream identifier is possible via an SDP offer-answer exchange triggering the reservation of new H.248 Stream endpoint. + +NOTE 2: There are multiple variations possible because the "CLOSURE of a data channel" results in a reset of the SCTP Stream (see clause 6.7 of IETF RFC 8831 [61]), i.e. the concerned SCTP Stream still exists from protocol stack perspective. Such a reset SCTP Stream could be reused again (for the same or another WebRTC data application). There are consequently two options from the eP-CSCF (IMS-ALG) perspective: the correspondent H.248 Stream endpoint remains allocated and part of the H.248 Stream Group for a possible future reuse, or the H.248 Stream endpoint is completely removed from the termination. + +### 5.20.2.3.2 Release of one WebRTC data channel + +When the eP-CSCF (IMS-ALG) receives: + +- an SDP offer or answer from the WebRTC access network releasing a particular WebRTC data channel while maintaining the corresponding SCTP Association, encoded according to IETF RFC 8864 [65]; or + +NOTE 1: Such an SDP offer or answer is characterized by the exclusion of the "a=dcmmap:" and "a=dcsha:" attribute lines for an existing data channel (DC). See clause 5.2.4 of IETF RFC 8864 [65] related to the general closure of an application-agnostic DC and clause 5.1.5 of IETF RFC 8873 [62] for an example of an application-aware DC closure. + +- an SDP offer or answer from the IMS core network disabling media streams that need to be transported within a WebRTC data channel on the WebRTC access network (i.e. media line with port zero) while maintaining other media streams that are transported within another data channel within the same SCTP Association enabled; or +- a notification from the eIMS-AGW that the peer has reset the incoming SCTP Stream that corresponds to a data channel; + +then the eP-CSCF (IMS-ALG): + +- 1) shall provide the *Send SCTP Stream Reset Requests Indicator* information element to the eIMS-AGW to request the eIMS-AGW to start the SCTP Stream reset for the corresponding outgoing SCTP Stream; + +NOTE 2: This will trigger the peer to also reset the corresponding incoming SCTP Stream, unless the peer has already done so before. + +- 2) may provide the *Received SCTP Stream Reset Response* information element to the eIMS-AGW if the eP-CSCF (IMS-ALG) wants to receive an explicit notification from the eIMS-AGW that the peer has reset the corresponding incoming SCTP Stream; +- 3) upon the reception of a Notification from the eIMS-AGW that the peer has reset the corresponding incoming SCTP Stream and the additional notification from the eIMS-AGW about the result of the outgoing SCTP Stream (if requested), may release the corresponding H.248 Stream endpoints at the terminations towards the WebRTC access network and towards the IMS core network; +- 4) if an received SDP offer or answer from the WebRTC access network triggered the release of the data channel, shall forward the SDP offer or answer to IMS core network with the media line corresponding to the media stream in the data channel disabled by port zero; + +- 5) if an received SDP offer or answer from the IMS core network triggered the release of the data channel, shall forward the SDP offer or answer to WebRTC access network with the corresponding WebRTC data channel released with encoding according to IETF RFC 8864 [65]; and +- 6) if all of the following conditions apply: + - a notification from the eIMS-AGW that the peer has reset the incoming SCTP Stream triggered the release of the data channel; + - the application subprotocol does not mandate that the closing of a data channel is also signalled via a new SDP offer/answer exchange; and + - no corresponding SIP/SDP information is received in due time; + +should send the appropriate SIP message with the SDP body to the IMS core network with the media line corresponding to the media stream in the data channel disabled by port zero. + +NOTE 3: According to IETF RFC 8864 [65], it is specific to the subprotocol whether this closing of a data channel MUST in addition the the SCTP SCTP SSN reset also be signalled to the peer via a new SDP offer/answer exchange. For MSRP, if the peer triggers a data channel release by resetting the incoming SCTP Stream, it is also mandated to send corresponding SIP/SDP information. + +### 5.20.2.3.3 Release of all or last active WebRTC data channels within an SCTP Association + +When the eP-CSCF (IMS-ALG) receives: + +- an SDP offer or answer from the WebRTC access network requesting to release the SCTP Association used to transport data channels, encoded according to IETF RFC 8864 [65] (i.e. media line with port zero); or +- an SDP offer or answer from the IMS core network disabling all media stream(s) that need to be transported within a WebRTC data channel on the WebRTC access network (i.e. media line(s) with port zero); + +then the eP-CSCF (IMS-ALG): + +- 1) shall release the corresponding H.248 Stream group or termination towards the WebRTC access network; + +NOTE 1: In the present release, a separate DTLS connection is used for each for each SCTP Association and for each audio or video media stream (for their DTLS-SRTP-based key exchange). + +- 2) shall release the corresponding H.248 streamendpoint(s) or termination towards the IMS core network; + +NOTE 2: If a new SDP offer from the access network arrives that requests a new data channel, then a stream end point and possibly a termination towards the IMS core network has to be added again. + +- 3) if an received SDP offer or answer from the WebRTC access network triggered the release of the SCTP Association, shall forward the SDP offer or answer to the IMS core network with all media line(s) corresponding to the media stream(s) in the data channel(s) within that SCTP Association disabled by port zero; and +- 4) if an received SDP offer or answer from the IMS core network triggered the release of the SCTP Association, shall forward the SDP offer or answer to WebRTC access network with the corresponding release of the SCTP Association with encoding according to IETF RFC 8864 [65] (i.e. media line with port zero). + +When the eP-CSCF (IMS-ALG) requests the eIMS-AGW to release an entire H.248 Stream group or termination associated with an SCTP Association, then the eIMS-AGW should execute appropriate bearer control procedures to release the DTLS connection. + +NOTE 3: If one DTLS connection endpoint closes the DTLS connection (e.g. sends a DTLS fatal alert), then the other DTLS connection endpoint unambiguously knows that also the SCTP association and all previously existing data channel instances are implicitly closed. + +NOTE 4: 'TCP' as L4 protocol is supported for WebRTC audio and video, but not for data in the present release. + +### 5.20.2.4 MSRP within WebRTC data channel + +See clause 5.19.6. + +### 5.20.2.5 Void + +### 5.20.2.6 T.140 within WebRTC data channel + +T.140 (see ITU-T Recommendation T.140 [73]) is used for Global Text Telephony (GTT). T.140 signalling can be transferred over WebRTC data channels as a data channel sub-protocol according to IETF RFC 8865 [75]. The WebRTC data channel procedures in clause 5.20.2.2 shall apply with the modifications described in the present clause. + +T.140 within a data channel is identified via the "t140" value of the "subprotocol" parameter of the SDP "a=dcmmap" attribute. + +T.140 transported outside the data channel in the IMS core network is identified via the "RTP/AVP" or "RTP/AVPF" value of the "proto" parameter and the "text" value of the "media" parameter of the SDP m-line, and via the "t140" MIME subtype signalled in the SDP "a=rtpmap" attribute (see IETF RFC 4103 [74]). + +The eIMS-ALG shall apply the procedures in clause 5.20.2.2 to configure the eIMS-AGW for an application-aware handling of the contents within the data channel. + +For the termination toward the IMS core network, the eIMS-ALG: + +- shall provision "RTP/AVP" or "RTP/AVPF" as transport and the "t140" payload type; +- shall de-encapsulate the SDP "fmtp:t140 cps" attributes, "sendrecv", "sendonly", "recvonly", "inactive", "hlang-send" and "hlang-recv" received within "a=dcsa" attributes from the served WIC; +- shall forward those attributes within the SDP body in the corresponding SIP message sent to the IMS core network; and +- shall provision the SDP "fmtp:t140 cps" attributes to the eIMS-AGW. + +For the termination towards the WebRTC access network, the eIMS-ALG: + +- shall not include the "max-retr", "max-time" and "ordered" parameters in the "a=dcmmap" SDP attribute; +- shall encapsulate SDP "fmtp:t140 cps", "sendrecv", "sendonly", "recvonly", "inactive", "hlang-send" and "hlang-recv" attributes received from the IMS core network within "a=dcsa" attributes and forward those attributes within the SDP body in the corresponding SIP message sent to the served WIC; and +- shall provision SDP "fmtp:t140 cps" attributes received from the IMS core network to the eIMS-AGW. + +The eIMS-AGW should handle T.140 protocol layer in the following application specific manner: + +- the eIMS-AGW should detect inactivity of T.140 traffic from the served WIC and then send empty RTP packets towards the IMS core network; +- the eIMS-AGW should buffer the T.140 payload received within incoming RTP packets from the IMS core network to correct out-of-order delivery; and +- the eIMS-AGW should detect missing RTP packets from the IMS core network and then send new T140 blocks with "missing text marker" information to the served WIC. + +## 5.20.3 Media Plane Optimization + +### 5.20.3.1 General + +Media plane optimization procedures for WebRTC are described in 3GPP TS 23.228 [2], annex U.2.4, and in 3GPP TS 24.371 [44], subclause 7.4.5. The purpose of media plane optimization procedures is to convey media between WebRTC clients without bearer level protocol conversion. When both ends are WebRTC IMS clients (WIC), the eIMS-AGWs remain allocated but media plane interworking is disabled, except when LI is needed. Depending on configuration in the eP-CSCF (IMS-ALG), the eIMS-AGW then forwards all protocol layers either including DTLS, or on top of DTLS transparently. + +NOTE 1: Terminating the DTLS protocol layer for all calls can improve the transparency of LI. + +NOTE 2: In Rel-13, the media plane optimization procedure only supports the transparent forwarding of all protocol layers including DTLS, and no related configuration in the eP-CSCF (IMS-ALG) is thus required. The configuration in the eP-CSCF (IMS-ALG) needs to take into account if the eIMS-AGW supports the media plane optimization procedures with DTLS layer termination added in Rel-14. + +The SDP attributes associated with WebRTC media plane optimization procedures "tra-contact", "tra-m-line", "tra-att", "tra-SCTP-association", "tra-media-line-number" and "tra-bw" are defined in 3GPP TS 24.229 [11], clause 7.5.4. + +### 5.20.3.2 WIC originating call + +If an eP-CSCF (IMS-ALG) forwards an SDP offer from the WIC, and supports media plane optimization, and does not need to perform legal interception, then the eP-CSCF (IMS-ALG) will include media suitable for non-WebRTC IMS UEs, but also encapsulate information about the media in the original encoding as received in the SDP offer from the WIC in "tra-m-line", "tra-att" and "tra-bw" SDP attributes, as described in 3GPP TS 24.371 [44]. The eP-CSCF (IMS-ALG) shall: + +- configure the eIMS-AGW to reserve resources suitable for the media described in the SDP offer outside the "tra-m-line", "tra-att" and "tra-bw" SDP attributes; +- include the IP address received from the eIMS-AGW for the termination towards the IMS core network in the SDP contact line and also encapsulate the address information provided by the eIMS-AGW into a "tra-contact" attribute; +- if the eP-CSCF (IMS-ALG) is configured to apply media plane optimization including the DTLS layer, for each media line in the SDP offer sent on the Mw interface that does not relate to a data channel or that is the first media line within the SDP offer that relates to a data channel, replace the UDP port number with a port number provided by the eIMS-AGW and encapsulate the UDP port number allocated by the eIMS-AGW in the "tra-m-line" SDP attribute; and +- if the eP-CSCF (IMS-ALG) is configured to apply media plane optimization excluding the DTLS layer, in addition for each media line in the SDP offer sent on the Mw interface that does not relate to a data channel or that is the first media line within the SDP offer that relates to a data channel within one SCTP association: + - a) reserve a stream endpoint or termination towards the IMS core network in "inactive" mode with "UDP/DTLS" as transport protocol, and the same IP address as allocated by the eIMS-AGW for the termination or stream endpoint with resources suitable for the media described in the SDP offer outside the "tra-m-line", "tra-att" and "tra-bw" SDP attributes; + - b) request from the eIMS-AGW a certificate fingerprint for that stream endpoint or termination; + - c) encapsulate a "fingerprint" attribute as provided by the eIMS-AGW into an "tra-att" attribute, and add this attribute as a media level attribute in the SDP offer; and + - d) for a DTLS association that will be established towards the IMS core network create a DTLS association identity; + - e) encapsulate an "a=tls-id" SDP attribute with the new DTLS association identity into an "tra-att" attribute, and add this attribute as a media level attribute in the SDP offer; and + - f) replace the UDP port number with a port number provided by the eIMS-AGW and encapsulate the UDP port number allocated by the eIMS-AGW for the stream endpoint or termination towards the IMS core network with "UDP/DTLS" transport in the "tra-m-line" SDP attribute. + +If an eP-CSCF (IMS-ALG) receives an SDP answer from the IMS core network and the SDP answer includes "tra-m-line" media level SDP attributes, the eP-CSCF (IMS-ALG) will de-encapsulate information to the optimized media from the received SDP answer and construct the SDP answer towards the WIC based on that de-encapsulated information as described in 3GPP TS 24.371 [44]. The eP-CSCF (IMS-ALG) shall: + +- for each media line in the SDP answer, which is not marked with a "tra-SCTP-association" SDP attribute or which is the first media line in the SDP answer marked with a "tra-SCTP-association" SDP attribute that indicates an SCTP association: + +1. if the eP-CSCF (IMS-ALG) is configured to apply media plane optimization including the DTLS layer, reconfigure the terminations or stream endpoints towards the IMS core network and towards the WIC related to that media line to transport "UDP" and media format agnostic information; or + +NOTE: If interconnected H.248 Stream endpoints or terminations at the eIMS-AGW are configured with transport "UDP", they will pass the payload within UDP without modifications, known as UDP transparent forwarding. For WebRTC media plane optimization, the UDP payload will be either DTLS encapsulating SCTP and data channel(s), DTLS-SRTP encapsulating key management information, or SRTP encapsulating audio or video media. However, the eIMS-AGW will be configured at terminations towards the WIC to apply ICE procedures according to clause 5.18. + +2. if the eP-CSCF (IMS-ALG) is configured to apply media plane optimization excluding the DTLS layer: + +- a) configure the eIMS-AGW to release the termination or stream endpoint towards the IMS core network with resources suitable for the media described in the SDP offer outside the "tra-m-line", "tra-att" and "tra-bw" SDP attributes; +- b) configure the eIMS-AGW to through-connect the stream endpoint or termination towards the IMS core network with "UDP/DTLS" as transport protocol; + +provide the fingerprint(s) received in the corresponding "tra-att" SDP attribute(s) to the eIMS-AGW for the stream endpoint or termination towards the IMS core network and do not provide those fingerprint attribute(s) towards the WIC; + +- d) reserve a stream endpoint or termination towards the WIC with "UDP/DTLS" as transport protocol; +- e) provide the fingerprint(s) received in the corresponding "fingerprint" SDP attribute(s) in the previous SDP offer from the WIC to the eIMS-AGW for the stream endpoint or termination towards the WIC; +- f) request from the eIMS-AGW a certificate fingerprint for the stream endpoint or termination towards the WIC; +- g) include fingerprint provided by the eIMS-AGW into an "fingerprint" attribute, and add this attribute as a media level attribute in the SDP answer sent towards the WIC; +- h) for a DTLS association that will be established towards WIC create a DTLS association identity and include an "a=tls-id" attribute with the new DTLS association identity in the SDP answer sent towards the WIC; +- i) determine via the SDP "a=setup" attribute (see IETF RFC 7345 [33]) encapsulated in "tra-att" SDP attribute if the eIMS-AGW needs to act as DTLS client or DTLS server towards the IMS core network and towards the WIC; and +- j) for the termination where the eIMS-AGW needs to act as DTLS server, provide the Establish (D)TLS session information element to request the eIMS-AGW to start the DTLS session setup; and + +3. include the UDP port number allocated by the eIMS-AGW for the termination or stream endpoint towards the WIC in the SDP media line in the SDP answer to the WIC; + +- include the IP address received from the eIMS-AGW for the termination towards the WIC in the SDP contact line sent toward the WIC; and +- if several media lines in the SDP answer are marked with "tra-SCTP-association" SDP attributes indicating the same SCTP association, release the stream endpoints related to the second and subsequent of those media lines (in the order they appear in the SDP answer). + +### 5.20.3.3 WIC terminating call + +If an eP-CSCF (IMS-ALG) receives an SDP offer from the IMS core network and the eP-CSCF (IMS-ALG) supports media plane optimization, then the eP-CSCF (IMS-ALG) will determine whether media plane optimization is to be applied as described in 3GPP TS 24.371 [44]. If media plane optimization is to be applied, then the eP-CSCF (IMS-ALG) will de-encapsulate information to the optimized media from the received SDP offer and construct the SDP offer towards the WIC based on that de-encapsulated information as described in 3GPP TS 24.371 [44], and the eP-CSCF (IMS-ALG) shall: + +- for each media line in the SDP offer, which is not marked with a "tra-SCTP-association" SDP attribute or which is the first media line in the SDP answer marked with "tra-SCTP-association" SDP attribute that indicates an SCTP association: + +1. reserve a termination or stream endpoint towards the WIC related to that media line; +2. if the eP-CSCF (IMS-ALG) is configured to apply media plane optimization including the DTLS layer, provide transport "UDP" and media format agnostic information for the termination or stream endpoint towards the WIC; + +NOTE: If interconnected H.248 Stream endpoints or terminations at the eIMS-AGW are configured with transport "UDP", they will pass the payload within UDP without modifications, known as UDP transparent forwarding. For WebRTC media plane optimization, the UDP payload will be either DTLS encapsulating SCTP and data channel(s) or DTLS-SRTP encapsulating key management information, or SRTP encapsulating audio or video media. However, the eIMS-AGW will be configured at terminations towards the WIC to apply ICE procedures according to clause 5.18. + +3. if the eP-CSCF (IMS-ALG) is configured to apply media plane optimization excluding the DTLS layer: + - a) provide transport "UDP/DTLS" and media format agnostic information for the termination or stream endpoints toward the WIC; + - b) request from the eIMS-AGW a certificate fingerprint for the stream endpoint or termination towards the WIC; + - c) encapsulate fingerprint provided by the eIMS-AGW into an "fingerprint" attribute, and add this attribute as a media level attribute in the SDP offer sent towards the WIC; and + - d) do not provide the fingerprint received in the SDP offer in the corresponding "tra-att" SDP attributes towards the WIC; + - e) for a DTLS association that will be established towards WIC create a DTLS association identity, and add an "a=tls-id" SDP attribute with the new DTLS association identity in the SDP offer sent towards the WIC; and + 4. include the UDP port number allocated by the eIMS-AGW for the stream endpoint or termination towards the WIC in the SDP media line; and +- include the IP address received from the eIMS-AGW for the termination towards the WIC in the SDP contact line sent toward the WIC. + +If the eP-CSCF (IMS-ALG) receives an SDP answer from the WIC and the eP-CSCF (IMS-ALG) decided to apply media plane optimization when processing the corresponding SDP offer, then the eP-CSCF (IMS-ALG) will construct the SDP answer towards the IMS core network encapsulating received information as described in 3GPP TS 24.371 [44], and the eP-CSCF (IMS-ALG) shall: + +- reserve a termination or stream endpoint towards the IMS core network; +- for each media line in the received SDP answer: + 1. if the eP-CSCF (IMS-ALG) is configured to apply media plane optimization including the DTLS layer, provide transport "UDP" and media format agnostic information for the termination or stream endpoint towards the IMS core network; + 2. if the eP-CSCF (IMS-ALG) is configured to apply media plane optimization excluding the DTLS layer: + - a) provide the fingerprint(s) received in the "fingerprint" SDP attribute from the WIC to the eIMS-AGW for the stream endpoint or termination towards the WIC; + - b) provide transport "UDP/DTLS" and media format agnostic information for the termination or stream endpoint towards the IMS core network; + - c) request from the eIMS-AGW a certificate fingerprint for the stream endpoint or termination towards the IMS core network; + +- d) encapsulate fingerprint provided by the eIMS-AGW for the termination or stream endpoint towards the IMS core network into a "tra-att" SDP attribute, and add this attribute as a media level attribute in the SDP answer sent towards the IMS core network; + - e) for a DTLS association that will be established towards the IMS core network create a DTLS association identity; + - f) encapsulate an "a=tls-id" SDP attribute with the new DTLS association identity into an "tra-att" attribute, and add this attribute as a media level attribute in the SDP answer sent towards the IMS core network; + - g) determine via the SDP "a=setup" attribute (see IETF RFC 7345 [33]) if the eIMS-AGW needs to act as DTLS client or DTLS server towards the IMS core network and towards the WIC; and + - h) for the termination where the eIMS-AGW needs to act as DTLS server, provide the Establish (D)TLS session information element to request the eIMS-AGW to start the DTLS session setup; and +3. encapsulate the UDP port number allocated by the eIMS-AGW for the stream endpoint or termination towards the IMS core network in the "tra-m-line" SDP attribute; and +- include the IP address received from the eIMS-AGW for the termination towards the IMS core network in the SDP contact line. + +## 5.21 Alternate Connection (ALTC) Addresses Management + +### 5.21.1 General + +The IMS-ALG and the IMS-AGW may support the functionalities related to the support of the ALTC functionality as specified in IETF RFC 6947 [59] and 3GPP TS 24.229 [11] to support dual stack UEs. The present clause describes the requirements for P-CSCF (IMS-ALG) and IMS-AGW when the ALTC procedures are supported. + +If the IMS-ALG supports ALTC and, based on local policies, decides to insert ALTC information in the SDP offer sent to the terminating side, the IMS-ALG shall request the IMS-AGW to reserve two sets of transport addresses/resources towards the access network to enable media to traverse the IMS-AGW, one for each media line associated to ALTC information. The IMS-ALG shall request the IMS-AGW to release the transport resources reserved for the address type finally not used. + +## 5.22 Video Region-of-Interest (ROI) + +### 5.22.1 General + +The IMS-ALG and the IMS-AGW may support the video Region-of-Interest (ROI) as defined in 3GPP TS 26.114 [21]. Three modes are specified for supporting ROI, including "Far End Camera Control (FECC)", "Arbitrary ROI" and "Predefined ROI". The IMS-ALG and the IMS-AGW may independently support any of these modes. + +### 5.22.2 "Far End Camera Control" mode + +The IMS-ALG and IMS-AGW may support the "Far End Camera Control" mode as specified in 3GPP TS 26.114 [21]. If the IMS-ALG and IMS-AGW support the "Far End Camera Control" mode, the IMS-ALG and IMS-AGW shall apply the procedures in the present clause. + +If the IMS-ALG receives an SDP body containing an "m=" line with a media type "application/h224", as defined by IETF RFC 4573 [68] which indicates support for FECC (ITU-T Recommendation H.281 [70]) using ITU-T Recommendation H.224 [69], the IMS-ALG shall: + +- forward within SIP signalling the SDP body received from the preceding node with unmodified SDP "m=" and "a=" lines related to the "application/h224" media types (see the related SDP examples in annex A.4.2e of 3GPP TS 26.114 [21]) to the succeeding node; and + +NOTE 1: There may be one media type "application/h224" "m=" line for each video "m=" line. + +- request the IMS-AGW to provide a separate IP/UDP/RTP transport for the "application/h224" media stream by setting the "m=" line media type to "application" and "RTP/AVP" or "RTP/AVPF" over UDP as transport protocol when reserving the transport addresses/resources towards the MTSI client and IMS core network. + +NOTE 2: The use of FECC itself is internal to the H.224 frame and is identified by the client ID field of the H.224 packet. The IMS-ALG only indicates the use of IP/UDP/RTP. The use of FECC is signalled via H.224 by a MTSI client. + +The IMS-AGW shall then: + +- assign resources for the requested media stream, i.e., resources for a media-format agnostic RTP flow; and +- forward transparently RTP/UDP packets (with the transparent (H.224)-PDU) between the incoming and outgoing network. + +### 5.22.3 "Predefined ROI" mode + +The IMS-ALG and IMS-AGW may support the "Predefined ROI" mode as specified in 3GPP TS 26.114 [21]. If the IMS-ALG and IMS-AGW support the "Predefined ROI", the IMS-ALG and IMS-AGW shall apply the procedures in the present clause. + +If the IMS-ALG receives an SDP body containing an "a=rtcp-fb" line with the "Predefined ROI" type expressed by the parameter "3gpp-roi-predefined", as described in 3GPP TS 26.114 [21], the IMS-ALG shall: + +- forward within SIP signalling the SDP body received from the preceding node with unmodified SDP "a=rtcp-fb" lines related to the "3gpp-roi-predefined" parameter to the succeeding node (see the related SDP examples in annex A.4.2e of 3GPP TS 26.114 [21]); and +- include the "Predefined ROI" information element when seizing resources in the IMS-AGW to request the IMS-AGW to assign the resources for the corresponding RTCP control flow to convey pre-defined ROI information. + +The IMS-AGW shall then assign resources for the requested RTCP control flow and forward transparently the RTCP "FB ROI" packets between the incoming and outgoing network. The procedures described in clause 5.9 shall also apply. + +NOTE 1: The RTCP control flow contains multiple RTCP packet types. + +If the IMS-ALG receives an SDP body containing the predefined ROI attribute(s) "a=predefined\_ROI" defined in 3GPP TS 26.114 [21], the IMS-ALG shall forward the SDP body with unmodified predefined ROI attribute(s) for the send and receive directions when seizing or modifying resources in the IMS-AGW. + +If the IMS-ALG receives an SDP body containing "a=extmap" attribute(s), as defined in IETF RFC 5285 [23], and the "a=extmap" attribute(s) contain the pre-defined ROI URN(s) (i.e. the ROI URN for carriage of pre-defined region of interest information in the sent video stream is given by "urn:3gpp:predefined-roi-sent") as defined in 3GPP TS 26.114 [21], then the IMS-ALG shall: + +- include the "Extended RTP header for Sent ROI" information element when seizing resources in the IMS-AGW to indicate to the IMS-AGW that it shall allow the RTP header extension for predefined ROI to pass; and +- forward within SIP signalling, the SDP body received from the preceding node with unmodified "a=extmap" attribute(s) to the succeeding node (see the related SDP examples in annex A.4.2e of 3GPP TS 26.114 [21]). + +NOTE 2: The UE supporting the Predefined ROI feature will not send the extended RTP headers for Sent ROI if the UE did not receive any SDP body with the Predefined ROI related "a=extmap" attribute. + +If the IMS-AGW has been instructed to pass on the extended RTP header for predefined ROI as described above for both incoming and outgoing terminations then: + +- if the IMS AGW does not apply video transcoding, it shall pass any received RTP header extension for Predefined ROI to succeeding RTP streams; or +- if the IMS-AGW applies video transcoding, it shall keep the predefined ROI information unchanged during the transcoding and copy the received RTP header extension for Predefined ROI to the succeeding outgoing RTP stream(s) after transcoding the associated group of packets. + +## 5.22.4 "Arbitrary ROI" mode + +The IMS-ALG and IMS-AGW may support the "Arbitrary ROI" mode as specified in 3GPP TS 26.114 [21]. If the IMS-ALG and IMS-AGW support the "Arbitrary ROI", the IMS-ALG and IMS-AGW shall apply the procedures in the present clause. + +If the IMS-ALG receives an SDP body containing an "a=rtcp-fb" line with the "Arbitrary ROI" type expressed by the parameter "3gpp-roi-arbitrary", as described in 3GPP TS 26.114 [21], the IMS-ALG shall: + +- forward within SIP signalling the SDP body received from the preceding node with unmodified SDP "a=rtcp-fb" lines related to the "3gpp-roi-arbitrary" parameter to the succeeding node (see the related SDP examples in annex A.4.2e of 3GPP TS 26.114 [21]); and +- include the "Arbitrary ROI" information element when seizing resources in the IMS-AGW to request the IMS-AGW to assign the resources for the corresponding RTCP control flow to convey arbitrary ROI information. + +The IMS-AGW shall then assign resources for the requested RTCP control flow and forward transparently the RTCP "FB ROI" packets between the incoming and outgoing network. The procedures described in clause 5.9 shall also apply. + +NOTE 1: The RTCP control flow contains multiple RTCP packet types. + +If the IMS-ALG receives an SDP body containing "a=extmap" attribute(s), as defined in IETF RFC 5285 [23], and the "a=extmap" attribute(s) contain the arbitrary ROI URN(s) (i.e. the ROI URN for carriage of arbitrary region of interest information in the sent video stream is given by "urn:3gpp:roi-sent") as defined in 3GPP TS 26.114 [21], then the IMS-ALG shall: + +- include the "Extended RTP header for Sent ROI" information element when seizing resources in the IMS-AGW to indicate to the IMS-AGW that it shall allow the RTP header extension for arbitrary ROI to pass; and +- forward within SIP signalling, the SDP body received from the preceding node with unmodified "a=extmap" attribute(s) to the succeeding node (see the related SDP examples in annex A.4.2e of 3GPP TS 26.114 [21]). + +NOTE 2: The UE supporting the Arbitrary ROI feature will not send the extended RTP headers for Sent ROI if the UE did not receive any SDP body with the Arbitrary ROI related "a=extmap" attribute. + +If the IMS-AGW has been instructed to pass on the extended RTP header for arbitrary ROI as described above for both incoming and outgoing terminations then: + +- if the IMS AGW does not apply video transcoding, it shall pass any received RTP header extension for Arbitrary ROI to succeeding RTP streams; or +- if the IMS-AGW applies video transcoding, it shall keep the arbitrary ROI information unchanged during the transcoding and copy the received RTP header extension for Arbitrary ROI to the succeeding outgoing RTP stream(s) after transcoding the associated group of packets. + +## 5.23 SDP Capability Negotiation (SDPCapNeg) + +The SDP Capability Negotiation (SDPCapNeg) as specified in IETF RFC 5939 [66] is adopted as an optional functionality to negotiate capabilities and their associated configurations according to 3GPP TS 24.229 [11]. If the ICS service is supported then the IMS-ALG and the IMS-AGW may further optionally support SDP Media Capability Negotiation as specified in IETF RFC 6871 [67] for alternative CS configuration. + +Upon receipt of an incoming SDP offer containing the attributes of SDP capability negotiation, e.g. offer AVPF and AVP together for the RTP profile negotiation using "a=tcap", "a=pcfg" and "a=acfg" attributes, the IMS-ALG shall: + +- request the IMS-AGW to reserve resources only for the default configuration without SDPCapNeg, and make the decision on support of the alternative configurations based on the IMS-ALG/IMS-AGW capability as provisioned before forwarding the SDP offer, i.e. handling SDPCapNeg at the controller level; or +- request the IMS-AGW to reserve resources for all of these configurations by signalling SDPCapNeg to the IMS-AGW, and update the SDP offer based on the response from the IMS-AGW before forwarding. + +NOTE: The additional benefit of signalling SDPCapNeg between the IMS-ALG and the IMS-AGW is to check the resource availability for the corresponding configurations and to avoid the further session failure in case of inadequate resources for the configuration changes in the final confirmation. However, due to the extra resources reserved only during the call establishment phase, there is increased risk of call establishment failure. + +In case the IMS-ALG decides to request the IMS-AGW to reserve resources for all of those configurations, the IMS-ALG shall: + +- use legacy SDP attributes as specified in IETF RFC 4566 [53] to do the mapping of actual and potential configurations with the H.248 ReserveGroup concept; or +- use SDP extensions for SDP capability negotiation as specified in IETF RFC 5939 [66], if supported by the IMS-AGW. + +Before using SDP extensions for SDP capability negotiation as specified in IETF RFC 5939 [66] towards the IMS-AGW, the IMS-ALG shall perform the necessary checks (i.e. through auditing or via prior provisioning) to ensure that the IMS-AGW supports the syntax and capabilities requested. For an auditing the procedure in clause 6.1.8.1 is used with the "SDPCapNeg Supported Capabilities" as the object. + +When receiving a request from the IMS-ALG with information element "SDPCapNeg configuration" indicating the potential use of multiple configurations, the IMS-AGW shall reserve resources for all of those configurations that it supports and shall send indicate the configurations for which it reserved resources in an "SDPCapNeg configuration" information element in the response. The IMS-ALG shall update the SDP offer with SDPCapNeg configurations in the response from the IMS-AGW and shall forward the SDP offer to the next hop. + +The IMS-ALG may also provide SDP configurations to the IMS-AGW with no dependency on the incoming SDP offer, e.g. the IMS-ALG may wildcard the supported configurations in order to construct or update an SDP offer with the addition of alternative configurations via SDPCapNeg attributes. + +On receipt of an SDP answer with SDPCapNeg, the IMS-ALG shall request the IMS-AGW to configure the resources for the selected configuration. If the IMS-AGW previously reserved any temporary resources for configurations that were not selected, the IMS-ALG shall also request the IMS-AGW to release those resources. + +## 5.24 RTP-level pause and resume + +The IMS-ALG and the IMS-AGW may support the "RTP-level pause and resume" signalling as defined in 3GPP TS 26.114 [21] and IETF RFC 7728 [79]. + +RTCP feedback messages to request for pause and resume of media streams can be used by conference participants supporting Multi-stream Multiparty Conferencing Media Handling feature, as specified in 3GPP TS 26.114 [21] annex S. Usage of the RTCP feedback "pause and resume" messages is negotiated via SDP offer/answer exchange through an extension of RTCP feedback capability attribute "a=rtcp-fb" (defined in IETF RFC 4585 [77]). + +If the IMS-ALG and IMS-AGW support the "RTP-level pause and resume" signalling, the IMS-ALG and IMS-AGW shall apply the procedures in the present clause. + +If the IMS-ALG receives an SDP offer containing "a=rtcp-fb" line(s) with a "CCM" parameter (as defined in IETF RFC 5104 [78]) and a "pause" CCM parameter (as defined in IETF RFC 7728 [79]), and if the IMS-ALG does not support or does not apply the transcoding procedure defined in clause 5.13, the IMS-ALG shall forward within SIP signalling, the SDP offer received from the preceding node with unmodified "a=rtcp-fb" line(s) with a "pause" CCM parameter. Otherwise, if the IMS-ALG does insert any transcoding or if the IMS-AGW does not support the "RTP-level pause and resume" signalling, the IMS-ALG shall forward within SIP signalling, the SDP offer received from the preceding node without any "a=rtcp-fb" line(s) with a "pause" CCM parameter. + +If the IMS-ALG forwarded the SDP offer containing the "a=rtcp-fb" line(s) with a "pause" CCM parameter and receives an SDP answer also containing the "a=rtcp-fb" line(s) with a "pause" CCM parameter (the reception of the attribute indicates a successful "RTP-level pause and resume" negotiation) then the IMS-ALG shall: + +- a) when requesting the IMS-AGW to configure resources towards the succeeding node and towards the preceding node, include the "CCM pause-resume" information element to indicate that the IMS-AGW shall forward RTCP feedback "CCM PAUSE-RESUME" messages transparently; and +- b) forward the SDP answer containing the "a=rtcp-fb" line(s) with a "pause" CCM parameter to its preceding node. + +The IMS-AGW shall then assign resources for the requested RTCP control flow and shall transparently forward the RTCP "CCM PAUSE" packets between incoming and outgoing networks. + +## 5.25 RTCP Codec Control Commands and Indications + +The IMS-ALG and the IMS-AGW may support signalling of "RTCP Codec Control Commands and Indications", as defined in 3GPP TS 26.114 [21] and IETF RFC 5104 [78]. + +NOTE 1: 3GPP TS 26.114 [21] specifies support of the following RTCP feedback codec control messages (CCM): "Full Intra Request (FIR)", "Temporary Maximum Media Stream Bit Rate Request (TMMBR)" and "Temporary Maximum Media Stream Bit Rate Notification (TMMBN)". + +The RTCP feedback FIR message can be used both by point-to-point video calls, and by conference participants supporting Multi-stream Multiparty Conferencing Media Handling feature, as specified in 3GPP TS 26.114 [21] annex S, to request the media sender to send a decoder refresh point. + +The RTCP TMMBR and TMMBN feedback messages can also be used in reaction to the Explicit Congestion Notification, as specified in clause 5.12. + +Usage of the RTCP feedback "CCM" messages is negotiated via SDP offer/answer exchange through an extension (defined in IETF RFC 5104 [78]) of the RTCP feedback capability attribute "a=rtcp-fb" (defined in IETF RFC 4585 [77]). + +NOTE 2: The SDP offer/answer negotiation is performed with a separate "a=rtcp-fb" attribute line for each CCM message type. + +If the IMS-ALG and IMS-AGW support the "RTCP Codec Control Commands and Indications" signalling, the IMS-ALG and IMS-AGW shall apply the procedures in the present clause. + +If the IMS-ALG receives an SDP offer containing "a=rtcp-fb" line(s) with a "CCM" parameter and with a "fir" and/or "tmmbr" CCM parameters (defined in IETF RFC 5104 [78]) under video "m=" line(s), and if the IMS-ALG does not configure the IMS-AGW to transcode the corresponding video media stream and/or to act as ECN endpoint for the corresponding video media stream, the IMS-ALG shall forward within SIP signalling, the SDP offer received from the preceding node with unmodified "a=rtcp-fb" line(s) with the "CCM" parameter and with "fir" and/or "tmmbr" CCM parameters. + +NOTE 3: If the IMS-ALG configures the IMS-AGW to transcode a video media stream and/or to act as ECN endpoint for the corresponding video media stream, the IMS-ALG can insert "a=rtcp-fb" line(s) with the "CCM" parameter and with "fir" and/or "tmmbr" CCM parameters within SDP offer irrespective of whether they were received from the preceding node. + +If the IMS-ALG does not configure the IMS-AGW to transcode the corresponding video media stream and/or to act as ECN endpoint, and if the IMS-ALG received an SDP answer also containing the "a=rtcp-fb" line(s) with the "CCM" parameter and with the same "fir" and/or "tmmbr" CCM parameters (the presence of the same "a=rtcp-fb ccm" line(s) in the SDP answer indicates a successful negotiation of the particular CCM message), then the IMS-ALG shall: + +- when requesting the IMS-AGW to configure resources towards the succeeding node and towards the preceding node, include the "CCM BASE" information element with the "fir" and/or "tmmbr" CCM parameters to indicate that the IMS-AGW shall be prepared to receive and is allowed to send the RTCP CCM "FIR" and/or "TMMBR/TMMBN" feedback messages; and +- forward the SDP answer containing the "a=rtcp-fb" line(s) with the "fir" and/or "tmmbr" CCM parameters (from the received SDP answer) to its preceding node. + +If the IMS-ALG configures the IMS-AGW to transcode the corresponding video media stream and/or to act as ECN endpoint: + +- if the IMS-ALG did not send towards the succeeding node the SDP offer containing the "a=rtcp-fb" line(s) with the "CCM" parameter and the with "fir" and/or "tmmbr" CCM parameters, then the IMS-ALG may: + - a) when requesting the IMS-AGW to configure resources towards the preceding node, include the "CCM BASE" information element with the "fir" and/or "tmmbr" CCM parameters to indicate that the IMS-AGW shall be prepared to receive and is allowed to send the RTCP CCM "FIR" and/or "TMMBR/TMMBN" feedback messages; and + +- b) include in the SDP answer it sends to the preceding node the "a=rtcp-fb" line(s) with the "fir" and/or "tmmbr" CCM parameters (as received SDP offer); and +- if the IMS-ALG sent towards the succeeding node the SDP offer containing the "a=rtcp-fb" line(s) with the "CCM" parameter and the with "fir" and/or "tmmbr" CCM parameters, and received an SDP answer also containing the "a=rtcp-fb" line(s) with the "CCM" parameter and with the same "fir" and/or "tmmbr" CCM parameters, then the IMS-ALG shall: + - a) when requesting the IMS-AGW to configure resources towards the succeeding node, include the "CCM BASE" information element with the "fir" and/or "tmmbr" CCM parameters to indicate that the IMS-AGW shall be prepared to receive and is allowed to send the RTCP CCM "FIR" and/or "TMMBR/TMMBN" feedback messages; and + - b) if the the IMS-ALG received from the preceding node the SDP offer containing the "a=rtcp-fb" line(s) with the "CCM" parameter and the with "fir" and/or "tmmbr" CCM parameters, include in the SDP answer it sends to the preceding node the "a=rtcp-fb" line(s) with the "fir" and/or "tmmbr" CCM parameters (as received SDP offer). + +The IMS-AGW shall then assign resources for the requested RTCP control flow: + +- if the IMS-AGW acts as an ECN endpoint (as described in clause 5.12) or applies the video transcoding procedure, the IMS-AGW: + - a) may send the RTCP TMMBR feedback message with an "IMS-AGW-generated" value in an "SSRC of media sender" field that is kept constant for the duration of the session, different from any SSRC value in the active RTP streams for the session, to request the media sender to limit the maximum bit rate for a media stream to, or below, the provided value; + +NOTE 4: Trigger for sending of the RTCP TMMBR feedback message can be reception of RTP packets marked with ECN-CE, as described in clause 5.12. The reason to use an "IMS-AGW-generated" value in "SSRC of media sender" and to keep that value constant in the session is that the IMS-AGW must be possible to identify as being a separate source of sending TMMBR messages, to avoid TMMBR induced by ECN restrictions interfering with other TMMBR restrictions set by other media receivers in the media path, as described in clause 3.5.4 of IETF RFC 5104 [78]. + +- b) upon reception of the RTCP TMMBR feedback message and if performing transcoding, shall adjust the sent media rate to the requested rate or lower and shall respond by sending the RTCP TMMBN feedback message; and +- c) may send the RTCP FIR feedback message to request the media sender to send a decoder refresh point; or +- if the IMS-AGW does not act as an ECN endpoint and does not apply the video transcoding procedure, the IMS-AGW shall transparently forward received RTCP FIR feedback message, and received RTCP TMMBR and TMMBN feedback messages between the incoming and outgoing networks. + +## 5.26 Delay Budget Information (DBI) + +The IMS-ALG and the IMS-AGW may support the "DBI" signalling as defined in 3GPP TS 26.114 [21]. + +RTCP feedback messages to report or request additional delay budget for voice and video media streams (as defined in 3GPP TS 26.114 [21] clause 7.3.8) can be used by participants in a point-to-point MTSI session, and by conference participants, as specified in 3GPP TS 26.114 [21]. + +If the IMS-ALG and IMS-AGW support the "DBI" signalling, the IMS-ALG and IMS-AGW shall apply the procedures in the present clause. + +If the IMS-ALG receives an SDP offer containing an "a=rtcp-fb" line(s) with a "3GPP-delay-budget" parameter as defined in 3GPP TS 26.114 [21], the IMS-ALG shall forward within SIP signalling, the SDP offer received from the preceding node with the unmodified "a=rtcp-fb" line(s) with "3GPP-delay-budget" parameter. Otherwise, if the IMS-AGW does not support the "DBI" signalling, the IMS-ALG shall forward within SIP signalling, the SDP offer received from the preceding node without any "a=rtcp-fb" line(s) with a "3GPP-delay-budget" parameter. + +If the IMS-ALG forwarded the SDP offer containing the "a=rtcp-fb" line(s) with a "3GPP-delay-budget" parameter and receives an SDP answer also containing the "a=rtcp-fb" line(s) with a "3GPP-delay-budget" parameter (the reception of the attribute indicates a successful "3GPP-delay-budget" negotiation) then the IMS-ALG shall: + +- a) when requesting the IMS-AGW to configure resources towards the succeeding node and towards the preceding node, include the "DBI" information element to indicate that the IMS-AGW shall forward RTCP DBI feedback messages transparently; and +- b) forward the SDP answer containing the "a=rtcp-fb" line(s) with a "3GPP-delay-budget" parameter to its preceding node. + +The IMS-AGW shall then assign resources for the requested RTCP control flow and shall transparently forward the RTCP DBI feedback messages between incoming and outgoing networks. + +## 6 IMS-ALG to IMS-AGW Procedures + +### 6.1 Non-Call Related Procedures + +#### 6.1.1 General + +The non-call related procedures are based on corresponding procedures of 3GPP TS 23.205 [8] where the IMS-ALG takes the place of the MSC server and the IMS-AGW takes the place of the MGW. + +#### 6.1.2 IMS-AGW Unavailable + +The IMS-ALG server recognises that the IMS-AGW is unavailable in the following 4 cases: + +1. The signalling connection is unavailable + +![Diagram illustrating a signalling connection failure between IMS-ALG and IMS-AGW.](c64555b7f91435b01997807dbb4bcc4c_img.jpg) + +The diagram shows two vertical lifelines for IMS-ALG and IMS-AGW. A dashed horizontal line represents the signalling connection. A zigzag arrow points from the IMS-ALG lifeline to the IMS-AGW lifeline, crossing the dashed line. Below the zigzag, the text "Signaling connection failure" is written. + +Diagram illustrating a signalling connection failure between IMS-ALG and IMS-AGW. + +Figure 6.1.2.1: Signalling connection failure + +2. The IMS-AGW indicates the failure or the maintenance locking condition to all connected IMS-ALG servers + +![Diagram illustrating the IMS-AGW indicating a failure or maintenance locking condition to the IMS-ALG.](3941735fafadf9a59b811f67fcdca7b3_img.jpg) + +The diagram shows two vertical lifelines for IMS-ALG and IMS-AGW. A solid horizontal arrow points from the IMS-AGW lifeline to the IMS-ALG lifeline, labeled "IMS-AGW Out of Service". A second solid horizontal arrow points from the IMS-ALG lifeline back to the IMS-AGW lifeline, labeled "IMS-AGW Out of Service Ack". + +Diagram illustrating the IMS-AGW indicating a failure or maintenance locking condition to the IMS-ALG. + +Figure 6.1.2.2: IMS-AGW indicates the Failure/Maintenance locking + +The failure or maintenance locking indication indicates that the IMS-AGW is locked for new calls or will soon go out of service and that no new connections should be established using this IMS-AGW. The IMS-AGW can choose + +between the "graceful" and the "forced" method. In the graceful method the connections are cleared when the corresponding calls are disconnected. In the forced method all connection are cleared immediately. + +3. The IMS-ALG recognises that the IMS-AGW is not functioning correctly, e.g. because there is no reply on periodic sending of Audits. The periodic sending of Audits by IMS-ALG should go on. + +In all of the above cases the IMS-ALG shall prevent the usage of the IMS-AGW until the IMS-AGW has recovered or the communication with the IMS-AGW is restored. + +### 6.1.3 IMS-AGW Available + +The IMS-ALG discovers that the IMS-AGW is available when it receives an IMS-AGW Communication Up message or an IMS-AGW Restoration message. If the IMS-ALG does not wish to sustain an association with the IMS-AGW, the response sent to the IMS-AGW may indicate an alternative IMS-ALG signalling address, in which case the IMS-AGW shall not consider itself registered and should preferably attempt to re-register with this alternative IMS-ALG before any further alternate IMS-ALGs. Otherwise, the response shall not indicate any alternative IMS-ALG signalling address. + +When the IMS-ALG discovers that the IMS-AGW is available the following shall occur: + +1. Signalling recovery + +The IMS-AGW indicates to all connected IMS-ALGs that the signalling connection is restored. + +![Sequence diagram for Figure 6.1.3.1: Communication goes up. The diagram shows two vertical lifelines: IMS-ALG on the left and IMS-AGW on the right. The sequence of messages is: 1. A dashed arrow from IMS-AGW to IMS-ALG labeled 'Signaling in service'. 2. A solid arrow from IMS-AGW to IMS-ALG labeled 'IMS-AGW communication Up'. 3. A solid arrow from IMS-ALG to IMS-AGW labeled 'IMS-AGW communication Up Ack'.](55736d2180d01f631782ce0784caafa3_img.jpg) + +Sequence diagram for Figure 6.1.3.1: Communication goes up. The diagram shows two vertical lifelines: IMS-ALG on the left and IMS-AGW on the right. The sequence of messages is: 1. A dashed arrow from IMS-AGW to IMS-ALG labeled 'Signaling in service'. 2. A solid arrow from IMS-AGW to IMS-ALG labeled 'IMS-AGW communication Up'. 3. A solid arrow from IMS-ALG to IMS-AGW labeled 'IMS-AGW communication Up Ack'. + +Figure 6.1.3.1: Communication goes up + +2. IMS-AGW restoration/maintenance unlocking indication. + +The IMS-AGW indicates to all connected IMS-ALGs that normal operation has resumed. + +![Sequence diagram for Figure 6.1.3.2: IMS-AGW indicates recovery from a failure/or maintenance unlocking. The diagram shows two vertical lifelines: IMS-ALG on the left and IMS-AGW on the right. The sequence of messages is: 1. A dashed arrow from IMS-AGW to IMS-ALG labeled 'Signaling in service'. 2. A solid arrow from IMS-AGW to IMS-ALG labeled 'IMS-AGW Restoration'. 3. A solid arrow from IMS-ALG to IMS-AGW labeled 'IMS-AGW Restoration Ack'.](bbe5fb08522c43eab0afefcac30e719b_img.jpg) + +Sequence diagram for Figure 6.1.3.2: IMS-AGW indicates recovery from a failure/or maintenance unlocking. The diagram shows two vertical lifelines: IMS-ALG on the left and IMS-AGW on the right. The sequence of messages is: 1. A dashed arrow from IMS-AGW to IMS-ALG labeled 'Signaling in service'. 2. A solid arrow from IMS-AGW to IMS-ALG labeled 'IMS-AGW Restoration'. 3. A solid arrow from IMS-ALG to IMS-AGW labeled 'IMS-AGW Restoration Ack'. + +Figure 6.1.3.2: IMS-AGW indicates recovery from a failure/or maintenance unlocking + +NOTE: This procedure may be used after recovery from a signalling failure. + +3. The IMS-ALG recognises that the IMS-AGW is now functioning correctly, e.g. because there is a reply on periodic sending of Audits. + +After this the IMS-ALG can use the IMS-AGW. + +If none of 1, 2, and 3 happens the IMS-ALG server can initiate the IMS-ALG Ordered Re-register procedure. + +## 6.1.4 IMS-AGW Recovery + +If the IMS-AGW recovers from a failure, is maintenance unlocked, or it has been restarted, it registers to its known IMS-ALGs using the IMS-AGW Restoration procedure or the IMS-AGW Registration procedure. The IMS-AGW can indicate whether the Service has been restored or whether it has restarted with a cold or warm boot. If the IMS-ALG does not wish to sustain an association with the IMS-AGW, the response sent to the IMS-AGW may indicate an alternative IMS-ALG signalling address, in which case the IMS-AGW shall not consider itself registered and should preferably attempt to re-register with this alternative IMS-ALG before any further alternate IMS-ALGs. Otherwise, the response shall not indicate any alternative IMS-ALG signalling address. + +![Sequence diagram for IMS-AGW Restoration](a70e0adcabc973b01b413b6a141884f3_img.jpg) + +``` +sequenceDiagram + participant IMS-AGW + participant IMS-ALG + Note left of IMS-AGW: IMS-AGW Recovery + IMS-AGW->>IMS-ALG: IMS-AGW Restoration (Service restored) + IMS-ALG-->>IMS-AGW: IMS-AGW Restoration Ack (IMS-ALG address) +``` + +The diagram illustrates the IMS-AGW Restoration procedure. It shows two vertical lifelines: IMS-ALG on the left and IMS-AGW on the right. The IMS-AGW sends a message labeled "IMS-AGW Restoration (Service restored)" to the IMS-ALG. The IMS-ALG responds with a message labeled "IMS-AGW Restoration Ack (IMS-ALG address)" back to the IMS-AGW. + +Sequence diagram for IMS-AGW Restoration + +Figure 6.1.4.1: IMS-AGW Restoration + +![Sequence diagram for IMS-AGW Registration](53001b5ae3f65139f78db410bb41ae30_img.jpg) + +``` +sequenceDiagram + participant IMS-AGW + participant IMS-ALG + Note left of IMS-AGW: IMS-AGW Restart (Cold/Warm boot) + IMS-AGW->>IMS-ALG: IMS-AGW Register (Cold/Warm boot) + IMS-ALG-->>IMS-AGW: IMS-AGW Register Ack (IMS-ALG address) +``` + +The diagram illustrates the IMS-AGW Registration procedure. It shows two vertical lifelines: IMS-ALG on the left and IMS-AGW on the right. The IMS-AGW sends a message labeled "IMS-AGW Register (Cold/Warm boot)" to the IMS-ALG. The IMS-ALG responds with a message labeled "IMS-AGW Register Ack (IMS-ALG address)" back to the IMS-AGW. + +Sequence diagram for IMS-AGW Registration + +Figure 6.1.4.2 IMS-AGW Registration + +After the recovery the IMS-ALG can use the IMS-AGW. + +## 6.1.5 IMS-ALG Recovery + +### 6.1.5.1 General + +If an IMS-AGW-unavailable condition is provoked by a failure/recovery action, the IMS-ALG recovery sequence will, from an information flow point of view, look like IMS-AGW unavailable and then IMS-AGW available. If an IMS-AGW-unavailable condition is not provoked, the IMS-ALG recovery sequence will look like IMS-AGW available. + +After the information flow, the terminations affected by the recovery action are released. + +### 6.1.5.2 IMS-ALG Restoration + +![Sequence diagram for IMS-ALG Restoration](e5ded42f8e352da02ee86cb55550c45d_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note left of IMS-ALG: Tw + IMS-ALG->>IMS-AGW: IMS-ALG Recovery complete, Signaling working + IMS-AGW->>IMS-ALG: Communication Up/ IMS-AGW Restoration + IMS-ALG->>IMS-AGW: Communication Up Ack/ IMS-AGW Restoration Ack + IMS-ALG->>IMS-AGW: IMS-ALG Restoration Warm, cold (boot) note + IMS-AGW->>IMS-ALG: IMS-ALG Restoration Ack +``` + +The diagram illustrates the IMS-ALG Restoration process. It begins with the IMS-ALG sending a message "IMS-ALG Recovery complete, Signaling working" to the IMS-AGW. A timer *Tw* is indicated on the IMS-ALG side. The IMS-AGW responds with "Communication Up/ IMS-AGW Restoration". The IMS-ALG then replies with "Communication Up Ack/ IMS-AGW Restoration Ack". Next, the IMS-ALG sends an "IMS-ALG Restoration Warm, cold (boot) note" to the IMS-AGW, which finally responds with "IMS-ALG Restoration Ack". + +Sequence diagram for IMS-ALG Restoration + +NOTE: Normal release procedure may also be initiated. + +**Figure 6.1.5.2.1: IMS-ALG Restoration** + +After the recovery action is complete and it is possible to signal to the IMS-AGW the IMS-ALG starts a timer *Tw*. If recovery indications are not received (IMS-AGW Communication Up or IMS-AGW Restoration) from the IMS-AGW during *Tw* an Audit is sent. If the IMS-ALG receives a recovery indication or IMS-AGW communication up indication, it shall acknowledge the indication before the IMS-ALG Restoration may be sent or the release procedure is initiated. + +### 6.1.6 IMS-AGW Re-register + +When the IMS-ALG requests an IMS-AGW to perform a registration (see clauses 6.1.3, 6.1.4 and 6.1.7), the IMS-AGW performs a re-registration to the IMS-ALG which is defined in the IMS-ALG address. + +![Sequence diagram for IMS-AGW Re-register](67c232883c119b120d2fb337bf588e05_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + IMS-AGW->>IMS-ALG: IMS-AGW Re-register + IMS-ALG->>IMS-AGW: IMS-AGW Re-register Ack +``` + +The diagram illustrates the IMS-AGW Re-register process. The IMS-AGW sends a message "IMS-AGW Re-register" to the IMS-ALG. The IMS-ALG then responds with "IMS-AGW Re-register Ack". + +Sequence diagram for IMS-AGW Re-register + +**Figure 6.1.6.1: Re-registration of an IMS-AGW** + +## 6.1.7 IMS-AGW Re-registration Ordered by IMS-ALG + +If the IMS-ALG knows that communication is possible, but the IMS-AGW has not registered, the IMS-ALG can order re-registration of the IMS-AGW. + +![Sequence diagram for IMS-AGW Re-registration Ordered by IMS-ALG](967e98a12645f89cb4a7620f42bf8c2e_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note left of IMS-ALG: IMS-ALG knows communication is possible, but IMS-AGW has not registered + IMS-ALG->>IMS-AGW: IMS-ALG Ordered Re-register (IMS-ALG address) + IMS-AGW-->>IMS-ALG: IMS-ALG Ordered Re-register Ack +``` + +The diagram shows a sequence of messages between the IMS-ALG and the IMS-AGW. The IMS-ALG sends a message labeled "IMS-ALG Ordered Re-register (IMS-ALG address)" to the IMS-AGW. The IMS-AGW responds with a message labeled "IMS-ALG Ordered Re-register Ack". + +Sequence diagram for IMS-AGW Re-registration Ordered by IMS-ALG + +Figure 6.1.7.1: Re-registration ordered by the IMS-ALG + +If the re-registration request is accepted the IMS-AGW uses the IMS-AGW Re-register procedure to register with the IMS-ALG. + +## 6.1.8 Audit of IMS-AGW + +### 6.1.8.1 Audit of Value + +The IMS-ALG may request the IMS-AGW to report the current values assigned to distinct objects in the IMS-AGW. This procedure may be used when a change has occurred in the IMS-ALG such that the IMS-ALG is unsure of the current Service State of Terminations. + +![Sequence diagram for Audit Value](7b2d685b805535c1e94aee1365753b92_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + IMS-ALG->>IMS-AGW: Audit Value (Object(s)) + IMS-AGW-->>IMS-ALG: Audit Value Ack (values per requested object) +``` + +The diagram shows a sequence of messages between the IMS-ALG and the IMS-AGW. The IMS-ALG sends a message labeled "Audit Value (Object(s))" to the IMS-AGW. The IMS-AGW responds with a message labeled "Audit Value Ack (values per requested object)". + +Sequence diagram for Audit Value + +Figure 6.1.8.1.1: Audit Value + +### 6.1.8.2 Audit of Capability + +The IMS-ALG may request the IMS-AGW to report the capabilities of distinct objects in the MGW. + +![Sequence diagram for Audit Capability](4a390493f601ce1ac6b9201db4e28b5a_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note left of IMS-ALG: IMS-ALG + Note right of IMS-AGW: IMS-AGW + IMS-ALG->>IMS-AGW: Audit Capability (Object(s)) + IMS-AGW-->>IMS-ALG: Audit Capability Ack (capabilities per requested object) +``` + +A sequence diagram showing the interaction between IMS-ALG and IMS-AGW for auditing capabilities. The IMS-ALG sends an 'Audit Capability (Object(s))' message to the IMS-AGW, and the IMS-AGW responds with an 'Audit Capability Ack (capabilities per requested object)' message. + +Sequence diagram for Audit Capability + +Figure 6.1.8.2.1: Audit Capability + +### 6.1.9 IMS-AGW Capability Change + +The IMS-AGW reports a change of capability of distinct objects in the MGW. + +![Sequence diagram for Capability Update](205c14458d7f4e2d22c75354bb451e99_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note left of IMS-ALG: IMS-ALG + Note right of IMS-AGW: IMS-AGW + IMS-AGW-->>IMS-ALG: Capability Update (Object(s)) + IMS-ALG-->>IMS-AGW: Capability Update Ack +``` + +A sequence diagram showing the interaction between IMS-AGW and IMS-ALG for capability updates. The IMS-AGW sends a 'Capability Update (Object(s))' message to the IMS-ALG, and the IMS-ALG responds with a 'Capability Update Ack' message. + +Sequence diagram for Capability Update + +Figure 6.1.9.1: Capability Update + +The IMS-ALG may use the Audit Value and/or Audit Capability procedures to obtain further information, about the objects whose capabilities have changed. + +### 6.1.10 IMS-ALG Out of service + +![Sequence diagram for IMS-ALG Out of Service](d16e5a3857155ee2837d851305ee8036_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note left of IMS-ALG: IMS-ALG + Note right of IMS-AGW: IMS-AGW + IMS-ALG->>IMS-AGW: IMS-ALG Out of Service (Forced/graceful) + IMS-AGW-->>IMS-ALG: IMS-ALG Out of Service Ack +``` + +A sequence diagram showing the interaction between IMS-ALG and IMS-AGW for going out of service. The IMS-ALG sends an 'IMS-ALG Out of Service (Forced/graceful)' message to the IMS-AGW, and the IMS-AGW responds with an 'IMS-ALG Out of Service Ack' message. + +Sequence diagram for IMS-ALG Out of Service + +Figure 6.1.10.1: IMS-ALG Out of Service + +If an IMS-ALG discovers that it wants to go out of service it may start an IMS-ALG Out of Service procedure. The IMS-ALG can indicate whether it requires the context to be cleared immediately (forced) or cleared as the bearer control protocol clears the bearer (Graceful). + +### 6.1.11 IMS-AGW Resource Congestion Handling - Activate + +When the IMS-ALG requires that an IMS-AGW congestion notification mechanism be applied in the MGW, the IMS-ALG shall use the IMS-AGW Resource Congestion Handling - Activate procedure towards the IMS-AGW. + +![Sequence diagram for IMS-AGW Resource Congestion Handling - Activate](9f51a76cae7309a296cbc6997941eb3f_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note left of IMS-ALG: IMS-ALG + Note right of IMS-AGW: IMS-AGW + IMS-ALG->>IMS-AGW: IMS-AGW Resource Congestion Handling - Activate + IMS-AGW-->>IMS-ALG: IMS-AGW Resource Congestion Handling - Activate - Ack +``` + +The diagram shows a sequence of messages between the IMS-ALG and the IMS-AGW. The IMS-ALG sends a message labeled 'IMS-AGW Resource Congestion Handling - Activate' to the IMS-AGW. The IMS-AGW responds with a message labeled 'IMS-AGW Resource Congestion Handling - Activate - Ack' back to the IMS-ALG. + +Sequence diagram for IMS-AGW Resource Congestion Handling - Activate + +Figure 6.1.11.1: IMS-AGW Resource Congestion Handling - Activate + +### 6.1.12 MGW Resource Congestion Handling -Indication + +When the IMS-ALG receives a load reduction notification from the IMS-AGW via the IMS-AGW Resource Congestion Handling - Indication procedure, the IMS-ALG tries to reduce the processing load that the IMS-ALG creates on the IMS-AGW. The IMS-AGW shall decide the actual level of traffic reduction. + +![Sequence diagram for IMS-AGW Resource Congestion Handling - Indication](99e9a4791d2e5bb5afa1bb884652d4db_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note left of IMS-ALG: IMS-ALG + Note right of IMS-AGW: IMS-AGW + IMS-AGW->>IMS-ALG: IMS-AGW Resource Congestion Handling - Indication + IMS-ALG-->>IMS-AGW: IMS-AGW Resource Congestion Handling - Indication - Ack +``` + +The diagram shows a sequence of messages between the IMS-AGW and the IMS-ALG. The IMS-AGW sends a message labeled 'IMS-AGW Resource Congestion Handling - Indication' to the IMS-ALG. The IMS-ALG responds with a message labeled 'IMS-AGW Resource Congestion Handling - Indication - Ack' back to the IMS-AGW. + +Sequence diagram for IMS-AGW Resource Congestion Handling - Indication + +Figure 6.1.12.1: IMS-AGW Resource Congestion Handling – Indication + +### 6.1.13 Control association monitoring + +Monitoring of the H.248 control association may be performed by monitoring the status of the transport link association where the transport protocol provides sufficient coupling to the H.248.1 protocol, i.e. if the transport link association is disconnected when no local H.248.1 protocol connection exists. + +An alternative method for the IMS-AGW to detect loss of the IMS-ALG may be achieved by requesting the IMS-AGW to poll the IMS-ALG periodically + +Upon registration of an IMS-AGW, the IMS-ALG may use the Inactivity Timeout - Activate procedure towards the IMS-AGW to request the IMS-AGW to monitor incoming messages for periods of silence exceeding the maximum inactivity timer value. + +![Sequence diagram for Inactivity Timeout - Activate](9c45844d796e85ae05505870a54e4eb4_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note left of IMS-ALG: Inactivity Timeout + IMS-ALG->>IMS-AGW: Inactivity Timeout - Activate + IMS-AGW-->>IMS-ALG: Inactivity Timeout - Activate - Ack +``` + +A sequence diagram showing the interaction between IMS-ALG and IMS-AGW. The IMS-ALG sends a message labeled 'Inactivity Timeout - Activate' to the IMS-AGW. The IMS-AGW responds with a message labeled 'Inactivity Timeout - Activate - Ack'. + +Sequence diagram for Inactivity Timeout - Activate + +**Figure 6.1.13.1: Inactivity Timeout - Activate** + +Upon receipt of an inactivity timeout notification from the IMS-AGW via the Inactivity Timeout - Indication procedure, the IMS-ALG shall send a reply to the IMS-AGW. If the IMS-ALG has failed, the IMS-AGW will not receive a reply. + +![Sequence diagram for Inactivity Timeout - Indication](1314748d1fff41b2d57a8ba9e9687c6a_img.jpg) + +``` +sequenceDiagram + participant IMS-AGW + participant IMS-ALG + IMS-AGW->>IMS-ALG: Inactivity Timeout - Indication + IMS-ALG-->>IMS-AGW: Inactivity Timeout - Indication - Ack +``` + +A sequence diagram showing the interaction between IMS-AGW and IMS-ALG. The IMS-AGW sends a message labeled 'Inactivity Timeout - Indication' to the IMS-ALG. The IMS-ALG responds with a message labeled 'Inactivity Timeout - Indication - Ack'. + +Sequence diagram for Inactivity Timeout - Indication + +**Figure 6.1.13.2: Inactivity Timeout - Indication** + +If no Inactivity Timeout – Indication Ack reply is received, the IMS-AGW shall consider the IMS-ALG to have failed. The IMS-AGW may then attempt to re-contact its controlling IMS-ALG by performing IMS-AGW Communication Up. If not successful, the IMS-AGW may then attempt to register to a new IMS-ALG. + +## 6.1.14 Realm Availability Monitoring + +If the IMS-AGW supports IP Realm Availability monitoring, the IMS-ALG may request the monitoring of the available IP Realms by the IMS-AGW; the IMS-AGW shall inform the IMS-ALG of any changes in realm availability. + +NOTE: The IMS-ALG can use the AuditValue procedure to determine which IP realms are currently available. + +The IMS-ALG may use the Realm Availability - Activate procedure towards the IMS-AGW to request the IMS-AGW to monitor the status of its IP Realms. + +![Sequence diagram for Realm Availability - Activate](ac8194ec0d833d53a0a36adada95b39e_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + IMS-ALG->>IMS-AGW: Realm Availability - Activate + IMS-AGW-->>IMS-ALG: Realm Availability - Activate - Ack +``` + +A sequence diagram showing the interaction between IMS-ALG and IMS-AGW. The IMS-ALG sends a message labeled 'Realm Availability - Activate' to the IMS-AGW. The IMS-AGW responds with a message labeled 'Realm Availability - Activate - Ack'. + +Sequence diagram for Realm Availability - Activate + +**Figure 6.1.14.1: Realm Availability - Activate** + +The IMS-AGW shall inform the IMS-ALG via the Realm Availability – Notification procedure. + +![Sequence diagram for Realm Availability - Indication procedure between IMS-ALG and IMS-AGW.](4dd5f00d74e7db5bbb2d011609bcc43d_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note left of IMS-ALG: IMS-ALG + Note right of IMS-AGW: IMS-AGW + IMS-AGW->>IMS-ALG: Realm Availability - Indication + IMS-ALG->>IMS-AGW: Realm Availability - Indication - Ack +``` + +The diagram shows a sequence of messages between the IMS-ALG and the IMS-AGW. The IMS-ALG is on the left and the IMS-AGW is on the right. The IMS-AGW sends a 'Realm Availability - Indication' message to the IMS-ALG. The IMS-ALG responds with a 'Realm Availability - Indication - Ack' message to the IMS-AGW. + +Sequence diagram for Realm Availability - Indication procedure between IMS-ALG and IMS-AGW. + +**Figure 6.1.14.2: Realm Availability - Indication** + +On being informed of newly available/unavailable realms, IMS-ALG shall take appropriate action (e.g. update its list of available realms etc.). + +## 6.1.15 Failure of IP Port, Interface or Group of Interfaces + +This procedure only applies when text encoding is used on the H.248 interface. + +The IMS-ALG shall and the IMS-AGW may support the Termination Out-of-Service procedure. + +If the IMS AGW suffers a loss of physical IP device(s) that pertain to a whole IP Realm it may report the IP Realm as unavailable (see clause 6.1.14). However, it is possible that a failure affects a physical port or group of ports that forms a subset of the IP Realm and therefore many terminations are affected. In such cases the IMS-AGW may initiate a Termination Out of Service procedure to inform the IMS-ALG that the set of terminations is out of service. This is shown in Figure 6.1.15.1. + +![Sequence diagram for Termination Out of Service procedure between IMS-ALG and IMS-AGW.](7fe4241eea8865aa6d2686d711c13ba6_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note left of IMS-ALG: IMS-ALG + Note right of IMS-AGW: IMS-AGW + IMS-AGW->>IMS-ALG: Termination Out Of Service (Termination(s)) + IMS-ALG->>IMS-AGW: Termination Out Of Service Ack +``` + +The diagram shows a sequence of messages between the IMS-ALG and the IMS-AGW. The IMS-ALG is on the left and the IMS-AGW is on the right. The IMS-AGW sends a 'Termination Out Of Service (Termination(s))' message to the IMS-ALG. The IMS-ALG responds with a 'Termination Out Of Service Ack' message to the IMS-AGW. + +Sequence diagram for Termination Out of Service procedure between IMS-ALG and IMS-AGW. + +**Figure 6.1.15.1: Termination Out of Service** + +On receipt of the Termination Out Of Service the IMS-ALG shall initiate the appropriate actions, e.g. by subtracting the affected terminations and releasing the affected calls. + +**NOTE:** This procedure provides an alternative failure reporting to the IP Bearer Released procedure (which allows reporting the failure of one IP Bearer / termination). The Termination Out-of-Service procedure avoids sending an avalanche of notifications when the failure affects multiple ephemeral terminations. + +## 6.2 Call Related Procedures + +### 6.2.1 Gate Control & Local NA(P)T procedure + +The session establishment and session release procedures are specified in 3GPP TS 23.228 [2] Annex G.4.3 and G.4.4. + +Figure 6.2.1.2 depicts the signalling flow for a session setup from the IMS access network towards the IMS core network when the P-CSCF invokes the IMS-ALG function for a session. The same signalling flow applies for a session setup from the IMS core network towards the IMS access network with the exception that terminations T1 and T2 are then exchanged. + +![Diagram of the H.248 Context Model showing the IMS-ALG and IMS-AGW components between the IMS Access Network and the IMS CN.](8f8caebe58364416a2eda21039d8c7bf_img.jpg) + +The diagram illustrates the H.248 Context Model. It features two main components: an IMS-ALG (IMS Application Layer Gateway) and an IMS-AGW (IMS Access Gateway). The IMS-ALG is a yellow rectangular box at the top, connected to the IMS Access Network on the left and the IMS CN on the right by green dashed lines. Below the IMS-ALG is the IMS-AGW, which is a yellow rectangular box containing a green diamond shape with an 'X' inside. The IMS-AGW is connected to the IMS Access Network on the left and the IMS CN on the right by red dotted lines. Inside the IMS-AGW, there are two terminations labeled T1 and T2, with a small 'X' between them. Below the IMS-AGW box is the label 'CTX C1'. The IMS Access Network is represented by a white rounded rectangle on the left, and the IMS CN is represented by a white rounded rectangle on the right. + +Diagram of the H.248 Context Model showing the IMS-ALG and IMS-AGW components between the IMS Access Network and the IMS CN. + +Figure 6.2.1.1: H.248 Context Model + +![Sequence diagram showing IMS-ALG and IMS-AGW interaction at session establishment. The diagram includes steps for SDP offer/answer exchange, H.248 ADD/MOD requests, and AGW connection point configuration. Brackets on the left indicate 'Reserve AGW Connection Point', 'Configure AGW Connection Point', and 'Reserve And Configure AGW Connection Point' procedures.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) + +``` + +sequenceDiagram + participant External + participant IMS-ALG + participant IMS-AGW + + Note left of IMS-ALG: Reserve AGW Connection Point, (Change Through-Connection) + External-->>IMS-ALG: 1. SDP offer (IP1o, P1o) + IMS-ALG->>IMS-AGW: 2. H.248 ADD req (C= ?, T= ?, LAddr=?, LPort=?) + IMS-AGW->>IMS-ALG: 3. Create outgoing termination T2 + IMS-AGW->>IMS-ALG: 4. H.248 ADD resp. (C=C1, T=T2, LAddr=IP2o, LPort=P2o) + IMS-ALG->>IMS-AGW: 5. Modify SDP offer + IMS-AGW->>External: 6. SDP offer (IP2o, P2b) + External-->>IMS-AGW: 7. SDP answer (IP1a, P1a) + Note left of IMS-ALG: Configure AGW Connection Point, (Change Through-Connection) + IMS-ALG->>IMS-AGW: 8. H.248 MOD req (C= C1, T= T2, RAddr=IP1a, RPort=P1a) + IMS-AGW->>IMS-ALG: 9. Configure Outgoing Termination T2 + IMS-AGW->>IMS-ALG: 10. H.248 MOD Resp (C= C1, T= T2) + Note left of IMS-ALG: Reserve And Configure AGW Connection Point, (Change Through-Connection) + IMS-ALG->>IMS-AGW: 11. H.248 ADD req (C= C1, T= ?, LAddr=?, LPort=?, RAddr=IP1o, RPort=P1o) + IMS-AGW->>IMS-ALG: 12. Create incoming Termination T1 + IMS-AGW->>IMS-ALG: 13. H.248 ADD Resp (C= C1, T= T1, LAddr=IP2a, LPort=P2a, RAddr=IP1o, RPort=P1o) + IMS-ALG->>IMS-AGW: 14. Modify SDP answer + IMS-ALG-->>External: 15. SDP answer(IP2a, P2a) + +``` + +Sequence diagram showing IMS-ALG and IMS-AGW interaction at session establishment. The diagram includes steps for SDP offer/answer exchange, H.248 ADD/MOD requests, and AGW connection point configuration. Brackets on the left indicate 'Reserve AGW Connection Point', 'Configure AGW Connection Point', and 'Reserve And Configure AGW Connection Point' procedures. + +Figure 6.2.1.2: IMS-ALG and IMS-AGW interaction at session establishment + +Upon receipt of a session initiation request, the IMS-ALG shall extract the offerer's destination network address(es) and port number(s) from the signalling message body received from the calling party endpoint. It shall then request the IMS-AGW to allocate transport resources (T2) via the Reserve AGW Connection Point procedure. Upon receipt of the + +response from the IMS-AGW, the IMS-ALG shall modify the offerer's destination address(es) and/or port(s) contained in the application signalling message body and propagate the session establishment toward the terminating party. + +On receipt of the terminating end SDP in the session establishment response, the IMS-ALG shall pass the information to the IMS-AGW in the Configure AGW Connection Point procedure and shall request the IMS-AGW to allocate transport resources (T1) via the Reserve and Configure AGW Connection Point. Upon receiving the response from the IMS-AGW, the IMS-ALG shall modify the answerer's destination address(es) and/or port(s) contained in the application signalling message body and pass the information to the originating party. + +On session termination, the IMS-ALG shall request the IMS-AGW to release its transport resources via the Release AGW Termination procedure. + +## 6.2.2 IP realm indication procedure + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally specifying the required IP Realm to the IMS-AGW when requesting the allocation of transport resources on the IMS-AGW. + +## 6.2.3 Remote NA(P)T traversal support procedure + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally indicating to the IMS-AGW that the remote media address/port information (supplied by the IMS-ALG) shall not be used as the destination address for outgoing media. Instead, the IMS-AGW shall "latch" or "relatch" onto the required destination address via the source address/port of the incoming media. The IMS-ALG may command the IMS-AGW to latch once (on the first received packet) or to re-latch (i.e. to check for a change of source address on the incoming media stream and latch once on this new address). + +## 6.2.4 Remote Source Address/Port Filtering + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally specifying the required IP address and/or port to be used to screen received media packets on a termination. + +This clause considers when the IMS-ALG is acting as an Entry point and remote source transport address filtering is required towards the external network. + +As a security related option, on request from the IMS-ALG, filtering may be enabled to check/validate the source address or source address and port number of incoming packets from the external network. If the IMS-ALG requests address filtering, it may additionally provide an address specification, which may identify either a single address or a range of addresses, against which filtering is to be performed. The absence of such an address specification in the request shall implicitly request filtering against the IP address of the remote connection address. In addition to address filtering, the IMS-ALG may also request port filtering. If the IMS-ALG requests port filtering, it may additionally include either a port or a range of ports, against which filtering is to be performed. The absence of a port specification in the request shall implicitly request filtering against the port of the remote connection address. + +If the IMS-AGW is requested to apply source IP address and possibly source port filtering, it shall only pass incoming IP packets from the identified source, and discard IP packets from other sources. + +If remote source address filtering is required for the created termination, then the IMS-ALG shall include the information element "Remote source address filtering" in the request sent to the IMS-AGW. In addition, it may also include the information element "Remote source address mask" in order to request filtering of a range of addresses. + +If remote source port filtering is required for the created termination (in addition to remote source address filtering), then the IMS-ALG shall include the information element "Remote source port filtering" in the request sent to the IMS-AGW. It may also include one of the information elements "Remote source port" or "Remote source port range". + +Subsequently, the IMS-AGW shall apply filtering as requested to the packets arriving from the external network. Any packet arriving, which does not meet the filtering requirement, shall be discarded. + +## 6.2.5 Traffic Policing + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally requesting the IMS-AGW to police the media stream flow according to one or more of the following media policing(s) through the IMS-AGW, in accordance with IETF RFC 2216 [10]. + +NOTE 1: In order to support services that generate media with variable bitrate (e.g. video), the policing function needs to provide sufficient buffer space. The derivation of the correspondent token bucket size can be based on the estimated traffic volume over the expected maximum burst length (supposed time interval of the burst). For example, for MTSI media, 3GPP TS 26.114 [21] clause 7.5.5 recommends a default period of 2 seconds for the derivation of average bitrates and provides further considerations regarding suitable time periods for speech and video. + +NOTE 2: The decision to apply or not traffic policing is general for all sessions with the same media characteristics (i.e. not user specific). The conditions which media policing to apply are beyond the scope of this specification. This can be based on the media characteristics of the session (e.g. media type). + +The following media policing shall be supported at the IMS-AGW: + +- **Sustainable Data Rate (SDR) Policing:** + +To request policing of the sustainable data rate of a media stream, the IMS-ALG shall request media policing for that media stream and shall provide the sustainable data rate, and shall provide a maximum burst size (MBS) indicating the expected maximum size of packet bursts for that media stream. The IMS-AGW shall then measure the data rate for the received packets within that media stream as per IETF RFC 2216 [10] for "Token Bucket", where $r$ = SDR and $b$ = MBS. If the permissible sustainable data rate is exceeded, the IMS-AGW shall discard packets to reduce the data rate to the permissible sustainable data rate. + +NOTE 3: The IMS-ALG can derive the sustainable data rate from bandwidth parameters if it receives them within an SDP media description. The IMS-ALG can: + +- use the "b=AS" bandwidth modifier if received within an SDP body; or +- if the IMS-ALG supports the enhanced bandwidth negotiation mechanism, use the "maximum supported bandwidth for the receiving direction" property value from the "a=bw-info" SDP attribute received within an SDP answer. + +If the value of the "maximum supported bandwidth for the receiving direction" for the selected RTP payload type differs from the value of the "b=AS" bandwidth modifier then the IMS-ALG can use "maximum supported bandwidth for the receiving direction" property value from the "a=bw-info" SDP attribute to determine the sustainable data rate for the selected RTP payload. + +The following media policing may be supported in addition at the IMS-AGW ; if supported then the following applies: + +- **Peak Data Rate Policing:** + +To request policing of the peak data rate of a media stream, the IMS-ALG shall request media policing for that media stream and shall provide the peak data rate, and may provide a Delay Variation Tolerance indicating the expected maximum delay variation due to jitter for that media stream. The IMS-AGW shall then measure the data rate for the received packets within that media stream. If the permissible peak data rate is exceeded, the IMS-AGW shall discard packets to reduce the data rate to the permissible peak data rate. If both peak data rate and sustainable data rate have been provided for the same media stream, the IMS-AGW shall discard packets to reduce the data rate to the permissible peak data rate and should discard packets to reduce the data rate to the permissible sustainable data rate. + +## 6.2.6 Hanging Termination Detection + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG requesting the IMS-AGW to periodically report termination heartbeat indications to detect hanging context and termination in the IMS-AGW that may result e.g. from a loss of communication between the IMS-ALG and the IMS-AGW. + +When the IMS-ALG receives a termination heartbeat notification from the IMS-AGW via the Termination heartbeat - Indication procedure, the IMS-ALG shall return a Termination heartbeat -Indication Ack (without an error) if the context id / termination identity combination exists in the IMS-ALG. If it does not exist, the IMS-ALG shall return an error and shall correct the mismatch, e.g. by requesting the IMS-AGW to subtract the indicated termination and to clear any associated context. + +![Sequence diagram showing Termination heartbeat - Indication and Termination heartbeat - Indication - Ack between IMS-ALG and IMS-AGW.](38d82ffe820e339811b396206f40a201_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note left of IMS-ALG: IMS-ALG + Note right of IMS-AGW: IMS-AGW + IMS-AGW->>IMS-ALG: Termination heartbeat - Indication + IMS-ALG-->>IMS-AGW: Termination heartbeat - Indication - Ack +``` + +Sequence diagram showing Termination heartbeat - Indication and Termination heartbeat - Indication - Ack between IMS-ALG and IMS-AGW. + +Figure 6.2.6.1: Termination heartbeat – Indication + +## 6.2.7 QoS Packet Marking + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally specifying the setting of the DSCP for outgoing packets on a termination. The DSCP value may be explicitly set by the IMS-AGW or else copied from that received in the corresponding received packet. + +If differentiated services are required for the created termination, then the IMS-ALG shall include the information elements "DiffServ Code Point" and/or "DiffServ Tagging Behaviour" in the request sent to the IMS-AGW. + +Subsequently, for all egress packets, the IMS-AGW shall set the DiffServ Code Point in the IP header as specified by the IMS-ALG: + +- If the DiffServ Tagging Behaviour information element was received with a value to indicate that the DiffServ Code Point should be copied, then the DiffServ Code Point in the IP header of the egress packet is copied from the ingress packet. +- If the Diffserv Tagging Behaviour information element was not received, or was received with a value to indicate that the DiffServ Code Point should be set to a specific value, then: + - If the DiffServ Code Point information element was received, then the DiffServ Code Point in the IP header of the egress packet shall be set to the value received in the DiffServ Code Point information element. + - If the DiffServ Code Point information element was not received, then the DiffServ Code Point in the IP header of the egress packet shall be set to a configured default value. + +## 6.2.8 Media Inactivity Detection + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally requesting the IMS-AGW to detect inactive media. + +If media inactivity detection is required for the created termination, the IMS-ALG may include the information elements "Inactivity detection time" and "Inactivity detection direction" in the request sent to the IMS-AGW. The IMS-ALG may request the detection of media inactivity on a termination or a stream basis. + +When the IMS-ALG receives a notification of inactive media from the IMS-AGW via the Media Inactivity Notification procedure, the IMS-ALG shall return a Media Inactivity Notification Ack and shall take appropriate action (e.g. release the termination). + +![Sequence diagram showing Media Inactivity Notification between IMS-ALG and IMS-AGW. The IMS-AGW sends a 'Media Inactivity Notification' message to the IMS-ALG, and the IMS-ALG responds with a 'Media Inactivity Notification - Ack' message.](11f18bf0233d812ad2604f88f3385d60_img.jpg) + +``` + +sequenceDiagram + participant IMS-AGW + participant IMS-ALG + Note right of IMS-AGW: Media Inactivity Notification + IMS-AGW->>IMS-ALG: Media Inactivity Notification + Note left of IMS-ALG: Media Inactivity Notification - Ack + IMS-ALG->>IMS-AGW: Media Inactivity Notification - Ack + +``` + +Sequence diagram showing Media Inactivity Notification between IMS-ALG and IMS-AGW. The IMS-AGW sends a 'Media Inactivity Notification' message to the IMS-ALG, and the IMS-ALG responds with a 'Media Inactivity Notification - Ack' message. + +**Figure 6.2.8.1: Media Inactivity Notification** + +## 6.2.9 Handling of RTCP streams + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally requesting the IMS-AGW to allocate or not allocate RTCP resources. Additionally if RTCP handling is requested, the IMS ALG may include: + +- the explicit RTCP transport address information element; +- the RTP/RTCP transport multiplexing information element; and +- the bandwidth allocation for RTCP, + +as described in clause 5.9. + +## 6.2.10 IMS end-to-access-edge Media Plane Security + +### 6.2.10.1 General + +All message sequence charts in this clause are examples. + +The H.248 context model is defined in Figure 6.2.1.1. + +### 6.2.10.2 End-to-access-edge security for RTP based media using SDES + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally requesting the IMS-AGW to provide IMS media plane security in accordance with 3GPP TS 33.328 [12]. + +The IMS-ALG shall provide the following media plane security related parameters to the IMS-AGW: + +- the SDES crypto attributes + +### 6.2.10.3 End-to-access-edge security for TCP-based media using TLS + +#### 6.2.10.3.1 End-to-access-edge security for session based messaging (MSRP) + +##### 6.2.10.3.1.1 IMS UE originating procedures for e2ae + +###### 6.2.10.3.1.1.1 Incoming TCP bearer establishment triggers an outgoing TCP bearer establishment + +Figure 6.2.10.3.1.1.1 shows an example call flow for the originating session set-up procedures for one MSRP media stream using e2ae security, where an incoming TCP bearer establishment triggers an outgoing TCP bearer establishment. + +![Sequence diagram showing the interaction between UE-A, P-CSCF (IMS-ALG), and IMS-AGW for media path setup and modification. The diagram includes SDP offers/answers, H.248 ADD/MOD requests/responses, and TCP/TLS handshake messages. Brackets on the left indicate AGW connection point changes at steps 2, 5, 13, and 16.](1e5a58dcaf0936bf18dc3dd0d9cd43ff_img.jpg) + +**Sequence of Messages:** + +- UE-A → P-CSCF (IMS-ALG): 1. SDP offer (c=IP1o, m=P1o TCP/TLS/MSRP, a=3ge2ae:requested, a=setup:actpass, a=fingerprint:ue-a) +- P-CSCF (IMS-ALG) → IMS-AGW: 2. H.248 ADD req (C=?, T=?, m=TCP/MSRP, a=setup:actpass, LAddr=?, LPort=?, interlinkage=[\*:TCP:TCP,est]) +- IMS-AGW → P-CSCF (IMS-ALG): 3. Create outgoing termination T2 +- IMS-AGW → P-CSCF (IMS-ALG): 4. H.248 ADD resp (C=C1, T=T2, LAddr=IP2o, LPort=P2o) +- P-CSCF (IMS-ALG) → IMS-AGW: 5. H.248 ADD req (C=C1, T=?, m=TCP/TLS/MSRP, a=setup:actpass, LAddr=?, LPort=?, a=fingerprint ?, RAddr=IP1o, RPort=P1o, a=fingerprint:ue-a) +- IMS-AGW → P-CSCF (IMS-ALG): 6. Create incoming termination T1 +- IMS-AGW → P-CSCF (IMS-ALG): 7. H.248 ADD resp (C=C1, T=T1, LAddr=IP2a, LPort=P2a, a=fingerprint:agw, RAddr=IP1o, RPort=P1o) +- P-CSCF (IMS-ALG) → UE-A: 8. Modify SDP offer +- P-CSCF (IMS-ALG) → UE-A: 9. SDP offer (c=IP2o, m=P2o TCP/MSRP, a=setup:actpass) +- IMS-AGW → P-CSCF (IMS-ALG): 10. TCP SYN +- P-CSCF (IMS-ALG) → IMS-AGW: 11. TCP SYN +- IMS-AGW → P-CSCF (IMS-ALG): TCP SYN ACK +- P-CSCF (IMS-ALG) → IMS-AGW: TCP SYN ACK +- IMS-AGW → P-CSCF (IMS-ALG): TCP ACK +- P-CSCF (IMS-ALG) → IMS-AGW: TCP ACK +- P-CSCF (IMS-ALG) → UE-A: 12. SDP answer (c=IP1a, m=P1a TCP/MSRP, a=setup:active) +- P-CSCF (IMS-ALG) → IMS-AGW: 13. H.248 MOD req (C=C1, T=T2, RAddr=IP1a, RPort=P1a) +- IMS-AGW → P-CSCF (IMS-ALG): 14. Configure outgoing termination T2 +- IMS-AGW → P-CSCF (IMS-ALG): 15. H.248 MOD resp (C=C1, T=T2) +- P-CSCF (IMS-ALG) → IMS-AGW: 16. H.248 MOD req (C=C1, T=T1, TLS:EstablishBNC) +- IMS-AGW → P-CSCF (IMS-ALG): 17. Configure incoming termination T1 +- IMS-AGW → P-CSCF (IMS-ALG): 18. H.248 MOD resp (C=C1, T=T1) +- P-CSCF (IMS-ALG) → UE-A: 19. Modify SDP answer +- P-CSCF (IMS-ALG) → UE-A: 20. SDP answer (c=IP2a, m=P2a TCP/TLS/MSRP, a=3ge2ae:requested, a=setup:active, a=fingerprint:agw) +- IMS-AGW → P-CSCF (IMS-ALG): 10'. TCP SYN +- P-CSCF (IMS-ALG) → IMS-AGW: 11'. TCP SYN +- IMS-AGW → P-CSCF (IMS-ALG): TCP SYN ACK +- P-CSCF (IMS-ALG) → IMS-AGW: TCP SYN ACK +- IMS-AGW → P-CSCF (IMS-ALG): TCP ACK +- P-CSCF (IMS-ALG) → IMS-AGW: TCP ACK +- P-CSCF (IMS-ALG) → IMS-AGW: 21. TLS Setup + +**AGW Connection Point Changes:** + +- Step 2: Reserve AGW Connection Point (, Change Through-Connection) +- Step 5: Reserve and Configure AGW Connection Point (, Change Through-Connection) +- Step 13: Configure AGW Connection Point (, Change Through-Connection) +- Step 16: Configure AGW Connection Point (, Change Through-Connection) + +Sequence diagram showing the interaction between UE-A, P-CSCF (IMS-ALG), and IMS-AGW for media path setup and modification. The diagram includes SDP offers/answers, H.248 ADD/MOD requests/responses, and TCP/TLS handshake messages. Brackets on the left indicate AGW connection point changes at steps 2, 5, 13, and 16. + +**Figure 6.2.10.3.1.1.1.1: Originating example call flow for e2ae security for MSRP where an incoming TCP bearer establishment triggers an outgoing TCP bearer establishment** + +The IMS UE A performs an IMS originating session set-up according to 3GPP TS 23.228 [2], with modifications as described in 3GPP TS 33.328 [12]. + +The procedure in the above figure for requesting e2ae security for a media stream is described step-by-step with an emphasis on the additional aspects for IMS-ALG and IMS-AGW of media protection using TLS. + +1. IMS UE A sends an SDP offer for a media stream containing cryptographic information, together with an "a=3ge2ae:requested" SDP attribute for the MSRP-related SDP m-line, to the P-CSCF (IMS-ALG). For e2ae protection of MSRP the cryptographic information contained in the SDP offer consists of the fingerprint of the certificate of IMS UE A in accordance to IETF RFC 4975 [25]. For each media stream that uses transport "TCP/TLS/MSRP", the P-CSCF (IMS-ALG) checks for the presence of the "a=3ge2ae:requested" SDP attribute. If that indication is present and the P-CSCF (IMS-ALG) indicated support of e2ae-security for MSRP during registration, the P-CSCF (IMS-ALG) allocates the required resources, includes the IMS-AGW in the media path and proceeds as specified in this clause. + +NOTE 1: An operator can choose to terminate TLS in the IMS-AGW according to the following steps for all media streams that are signalled in SIP INVITE messages with transport TCP/TLS/MSRP and a certificate fingerprint attribute, even if the UE did not indicate support for e2ae security during registration and did not indicate usage of e2ae security for the respective media streams in the INVITE. This can lead to session failures for pre-Rel-12 IMS UEs or non-IMS UEs due to a mismatch of security parameters sent by the network and expected by the UE, but on the other hand, it will ensure compatibility with GSMA RCS 5.1 [35, 36], which specifies that TLS for MSRP is always terminated in the network. + +- 2.-4. The IMS-ALG uses the "Reserve AGW Connection Point" procedure to request a termination for "TCP" media (for application-agnostic interworking) or "TCP/MSRP" media (for application-aware interworking) towards the core network. To indicate that the IMS-AGW shall operate in TCP Proxy mode, the IMS-ALG provides "a=setup:actpass" attribute. The IMS-ALG sets the interlinkage topology on the termination T2 to configure the IMS-AGW to use the TCP connection establishment request (TCP SYN) received at the termination T2 as a trigger to send a TCP connection establishment on the termination T1. + +NOTE 2: If "a=setup:passive" is received in the SDP answer in step 12, the IMS-ALG then needs to set the interlinkage topology on the termination T1 (not depicted). + +- 5.-7. The IMS-ALG uses the "Reserve And Configure AGW Connection Point" procedure to request a termination for "TCP/TLS" media (for application-agnostic interworking) or "TCP/TLS/MSRP" media (for application-aware interworking) towards the access network. In the remote descriptor, it provides the IP address, port and fingerprint attribute received from the UE containing the fingerprint of the UE's certificate in accordance to IETF RFC 4975 [25]. This instructs the IMS-AGW to verify during the subsequent TLS handshake with the IMS UE that the fingerprint of the certificate passed by the IMS UE during this TLS handshake matches the fingerprint passed by the P-CSCF (IMS-ALG) to the IMS-AGW. In turn, the IMS-AGW communicates the fingerprint of the certificate it is going to use for setting up protection for this media stream to the P-CSCF (IMS-ALG). To indicate that the IMS-AGW shall operate in TCP Proxy mode, the IMS-ALG provides "a=setup:actpass" attribute. + +NOTE 3: These steps could be combined with steps 16.-18. This saves H.248 signalling interactions but can delay the TCP connection setup. + +8. The P-CSCF (IMS-ALG) changes the transport from "TCP/TLS/MSRP" to "TCP/MSRP" in the SDP offer, removes the "a=3ge2ae:requested" SDP attribute and the fingerprint SDP attribute, and inserts the address information received from the IMS-AGW. +9. The P-CSCF (IMS-ALG) forwards the SDP offer. +10. The remote peer chooses to become the active party in the TCP connection establishment and sends a TCP SYN to establish the TCP connection. If the P-CSCF (IMS-ALG) indicated to the IMS-AGW at step 2 that it shall ignore any incoming TCP connection establishment requests (TCP SYN), e.g. to enable a remote source transport address filtering, or if the P-CSCF (IMS-ALG) did not indicate to the IMS-AGW at step 2 that it shall latch onto the required destination address via the source address/port of the incoming media, the IMS-AGW shall drop the TCP SYN received from the remote peer. +If the TCP SYN is not answered before a timer expiry, the remote peer will send the TCP SYN a second time + +(step 10'). The IMS-AGW will answer a repeated TCP SYN if it is received after step 13 (step 10'). +The IMS-AGW answers the TCP SYN and the remote peer completes the TCP connection establishment. + +11. The IMS-AGW uses the TCP SYN received at the termination T2 (at step 10 or step 10' if the TCP SYN is dropped at step 10) as a trigger to send a TCP SYN towards the UE to establish a TCP connection (effectively making the IMS-AGW acting as the TCP client towards the UE).. The UE answers the TCP SYN and the IMS-AGW completes the TCP connection establishment. +12. The P-CSCF (IMS-ALG) receives the SDP answer. +- 13.-15. The IMS-ALG uses the "Configure AGW Connection Point" procedure to configure the termination towards the core network with remote address information. If the P-CSCF (IMS-ALG) indicated to the IMS-AGW at step 2 that it shall ignore any incoming TCP connection establishment requests (TCP SYN), the IMS-ALG indicates to the IMS-AGW to accept incoming TCP connection establishment (TCP SYN) only from the indicated remote transport address. + +NOTE 4: For "a=setup:active" in the SDP answer, these steps could possibly be skipped if the P-CSCF (IMS-ALG) indicated to the IMS-AGW at step 2 that it shall latch onto the required destination address via the source address/port of the incoming media, as the IMS-AGW will then use the address information in the TCP SYN when replying. + +- 16.-18. The IMS-ALG uses the "Configure AGW Connection Point" procedure to configure the termination towards the access network with the request to establish the TLS session once the TCP connection is established (effectively making the IMS-AGW acting as the TLS client), in accordance with the information in the "a=setup" attribute in the SDP answer. +19. The P-CSCF (IMS-ALG) modifies the SDP answer before sending it to the UE A. The P-CSCF (IMS-ALG) sets the transport to "TCP/TLS/MSRP" and includes the fingerprint of the IMS-AGW's certificate in accordance to IETF RFC 4975 [25]. +20. The P-CSCF (IMA-ALG) then sends the updated SDP answer to IMS UE A. After receiving this message IMS UE A completes the media security setup. +21. Upon completion of the TCP connection establishment, the IMS-AGW starts the establishment of the TLS session. + +#### 6.2.10.3.1.1.2 IMS-ALG requests sending an outgoing TCP bearer establishment + +Figure 6.2.10.3.1.1.2.1 shows an example call flow for the originating session set-up procedures for one MSRP media stream using e2ae security, where the IMS-ALG requests sending an outgoing TCP bearer establishment. + +![Sequence diagram showing the interaction between UE-A, P-CSCF (IMS-ALG), and IMS-AGW for a media session setup. The diagram includes SDP offers/answers, H.248 ADD/MOD requests/responses, and TCP/TLS handshake messages. Brackets on the UE-A side indicate actions like 'Reserve AGW Connection Point' and 'Configure AGW Connection Point'.](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) + +``` + +sequenceDiagram + participant UE-A + participant P-CSCF as P-CSCF (IMS-ALG) + participant IMS-AGW + + Note left of UE-A: 1. SDP offer (c=IP1o, m=P1o TCP/TLS/MSRP, a=3ge2ae:requested, a=setup:actpass, a=fingerprint:ue-a) + UE-A->>P-CSCF: 1. SDP offer + Note right of P-CSCF: Reserve AGW Connection Point (, Change Through-Connection) + P-CSCF->>IMS-AGW: 2. H.248 ADD req (C=?, T=?, m=TCP/MSRP, a=setup:actpass, LAddr=?, LPort=?) + IMS-AGW->>IMS-AGW: 3. Create outgoing termination T2 + IMS-AGW->>P-CSCF: 4. H.248 ADD resp (C=C1, T=T2, LAddr=IP2o, LPort=P2o) + P-CSCF->>IMS-AGW: 5. H.248 ADD req (C=C1, T=?, m=TCP/TLS/MSRP, a=setup:actpass, LAddr=?, LPort=?, a=fingerprint ?, RAddr=IP1o, RPort=P1o, a=fingerprint:ue-a) + Note right of P-CSCF: Reserve and Configure AGW Connection Point (, Change Through-Connection) + IMS-AGW->>IMS-AGW: 6. Create incoming termination T1 + IMS-AGW->>P-CSCF: 7. H.248 ADD resp (C=C1, T=T1, LAddr=IP2a, LPort=P2a, a=fingerprint:agw, RAddr=IP1o, RPort=P1o) + P-CSCF->>P-CSCF: 8. Modify SDP offer + P-CSCF->>UE-A: 9. SDP offer (c=IP2o, m=P2o TCP/MSRP, a=setup:actpass) + Note right of IMS-AGW: 10. TCP SYN + IMS-AGW->>IMS-AGW: TCP SYN ACK + IMS-AGW->>IMS-AGW: TCP ACK + Note left of UE-A: 11. SDP answer (c=IP1a, m=P1a TCP/MSRP, a=setup:active) + P-CSCF->>UE-A: 11. SDP answer + Note right of P-CSCF: Configure AGW Connection Point (, Change Through-Connection) + P-CSCF->>IMS-AGW: 12. H.248 MOD req (C=C1, T=T2, RAddr=IP1a, RPort=P1a) + IMS-AGW->>IMS-AGW: 13. Configure outgoing termination T2 + IMS-AGW->>P-CSCF: 14. H.248 MOD resp (C=C1, T=T2) + Note right of P-CSCF: Configure AGW Connection Point (, Change Through-Connection) + P-CSCF->>IMS-AGW: 15. H.248 MOD req (C=C1, T=T1, TCP:EstablishBNC, TLS:EstablishBNC) + IMS-AGW->>IMS-AGW: 16. Configure incoming termination T1 + IMS-AGW->>P-CSCF: 17. H.248 MOD resp (C=C1, T=T1) + Note right of IMS-AGW: 18. TCP SYN + IMS-AGW->>IMS-AGW: TCP SYN ACK + IMS-AGW->>IMS-AGW: TCP ACK + Note right of IMS-AGW: 19. TLS Setup + P-CSCF->>P-CSCF: 20. Modify SDP answer + P-CSCF->>UE-A: 21. SDP answer (c=IP2a, m=P2a TCP/TLS/MSRP, a=3ge2ae:requested, a=setup:active, a=fingerprint:agw) + Note right of IMS-AGW: 10'. TCP SYN + IMS-AGW->>IMS-AGW: TCP SYN ACK + IMS-AGW->>IMS-AGW: TCP ACK + +``` + +Sequence diagram showing the interaction between UE-A, P-CSCF (IMS-ALG), and IMS-AGW for a media session setup. The diagram includes SDP offers/answers, H.248 ADD/MOD requests/responses, and TCP/TLS handshake messages. Brackets on the UE-A side indicate actions like 'Reserve AGW Connection Point' and 'Configure AGW Connection Point'. + +**Figure 6.2.10.3.1.1.2.1: Originating example call flow for e2ae security for MSRP where the IMS-ALG requests sending an outgoing TCP bearer establishment** + +The IMS UE A performs an IMS originating session set-up according to 3GPP TS 23.228 [2], with modifications as described in 3GPP TS 33.328 [12]. + +The procedure in the above figure for requesting e2ae security for a media stream is described step-by-step with an emphasis on the additional aspects for IMS-ALG and IMS-AGW of media protection using TLS. + +1. As step 1 in figure 6.2.10.3.1.1.1.1. + - 2.-4. As steps 2-4 in figure 6.2.10.3.1.1.1.1 with the exception that the IMS-ALG does not set the interlinkage topology on the termination T2. + - 5.-7. As steps 5-7 in figure 6.2.10.3.1.1.1.1. + 8. As step 8 in figure 6.2.10.3.1.1.1.1. + 9. As step 9 in figure 6.2.10.3.1.1.1.1. + 10. As step 10 in figure 6.2.10.3.1.1.1.1. +- NOTE: The incoming TCP SYN does not trigger the sending of an outgoing TCP SYN, and step 11 in figure 6.2.10.3.1.1.1.1 thus does not apply. +11. As step 12 in figure 6.2.10.3.1.1.1.1. + - 12.-14. As steps 13-15 in figure 6.2.10.3.1.1.1.1. + - 15.-17. As steps 16-18 in figure 6.2.10.3.1.1.1.1 with the exception that the IMS-ALG uses the "Configure AGW Connection Point" procedure also to configure the termination towards the access network with the request to establish the TCP connection (effectively making the IMS-AGW acting as the TCP client), in accordance with the information in the "a=setup" attribute in the SDP answer. + 18. The IMS-AGW sends a TCP SYN towards the UE to establish a TCP connection. The UE answers with a TCP SYN ACK and the IMS-AGW replies with a TCP ACK, completing the TCP connection establishment. + 19. As step 21 in figure 6.2.10.3.1.1.1.1. + 20. As step 19 in figure 6.2.10.3.1.1.1.1. + 21. As step 20 in figure 6.2.10.3.1.1.1.1. + +**6.2.10.3.1.2 IMS UE terminating procedures for e2ae****6.2.10.3.1.2.1 Incoming TCP bearer establishment triggers an outgoing TCP bearer establishment** + +Figure 6.2.10.3.1.2.1.1 shows an example call flow for the terminating session set-up procedures for one MSRP media stream using e2ae security, where an incoming TCP bearer establishment triggers an outgoing TCP bearer establishment. + +![Sequence diagram showing the interaction between P-CSCF (IMS-ALG), IMS-AGW, and UE-B. The diagram details the setup of media paths, including SDP offers, H.248 ADD/MOD requests, and TCP/TLS handshakes. Brackets on the left indicate phases for 'Reserve AGW Connection Point', 'Reserve and Configure AGW Connection Point', and 'Configure AGW Connection Point'.](a963ca41bde1669b18a4b783616f228b_img.jpg) + +**Sequence Diagram: IMS Media Path Setup** + +**Participants:** P-CSCF (IMS-ALG), IMS-AGW, UE-B + +**Phases:** + +- Reserve AGW Connection Point (, Change Through-Connection)** (Steps 1-4) +- Reserve and Configure AGW Connection Point (, Change Through-Connection)** (Steps 5-7) +- Configure AGW Connection Point (, Change Through-Connection)** (Steps 14-16) + +**Sequence of Messages:** + +- SDP offer (c=IP1o, m=P1o TCP/MSRP, a=setup:actpass) [UE-B to P-CSCF] +- H.248 ADD req (C=?, T=?, m=TCP/TLS/MSRP, a=setup:actpass, LAddr=?, LPort=?, a=fingerprint?, interlinkage=[\*:TCP:TCP,est]) [P-CSCF to IMS-AGW] +- Create outgoing termination T1 [IMS-AGW internal] +- H.248 ADD resp (C=C1, T=T1, LAddr=IP2o, LPort=P2o, a=fingerprint:agw) [IMS-AGW to P-CSCF] +- H.248 ADD req (C=C1, T=?, m=TCP/MSRP, a=setup:actpass, LAddr=?, LPort=?, RAddr=IP1o, RPort=P1o) [P-CSCF to IMS-AGW] +- Create incoming termination T2 [IMS-AGW internal] +- H.248 ADD resp (C=C1, T=T2, LAddr=IP2a, LPort=P2a, RAddr=IP1o, RPort=P1o) [IMS-AGW to P-CSCF] +- Modify SDP offer [P-CSCF internal] +- SDP offer (c=IP2o, m=P2o TCP/TLS/MSRP, a=3ge2ae:applied, a=setup:actpass, a=fingerprint:agw) [P-CSCF to UE-B] +- TCP SYN [UE-B to IMS-AGW] +- TCP SYN [IMS-AGW to P-CSCF] +- TCP SYN ACK [IMS-AGW to UE-B] +- TCP ACK [UE-B to IMS-AGW] +- TLS Setup [IMS-AGW to UE-B] +- SDP answer (c=IP1a, m=P1a TCP/TLS/MSRP, a=setup:active, a=fingerprint:ue-b) [UE-B to P-CSCF] +- H.248 MOD req (C=C1, T=T1, RAddr=IP1a, RPort=P1a, a=fingerprint:ue-b) [P-CSCF to IMS-AGW] +- Configure outgoing termination T1 [IMS-AGW internal] +- H.248 MOD resp (C=C1, T=T1) [IMS-AGW to P-CSCF] +- Modify SDP answer [P-CSCF internal] +- SDP answer (c=IP2a, m=P2a TCP/MSRP, a=setup:active) [P-CSCF to UE-B] +- TCP SYN [UE-B to IMS-AGW] +- TCP SYN [IMS-AGW to P-CSCF] +- TCP SYN ACK [IMS-AGW to UE-B] +- TCP ACK [UE-B to IMS-AGW] +- TLS Setup [IMS-AGW to UE-B] + +Sequence diagram showing the interaction between P-CSCF (IMS-ALG), IMS-AGW, and UE-B. The diagram details the setup of media paths, including SDP offers, H.248 ADD/MOD requests, and TCP/TLS handshakes. Brackets on the left indicate phases for 'Reserve AGW Connection Point', 'Reserve and Configure AGW Connection Point', and 'Configure AGW Connection Point'. + +**Figure 6.2.10.3.1.2.1.1: Terminating example call flow for e2ae security for MSRP where an incoming TCP bearer establishment triggers an outgoing TCP bearer establishment** + +The IMS UE B performs an IMS terminating session set-up according to 3GPP TS 23.228 [2], with modifications as described in 3GPP TS 33.328 [12]. + +The procedure in the above figure for requesting e2ae security for a media stream is described step-by-step with an emphasis on the additional aspects for IMS-ALG and IMS-AGW of media protection using TLS. + +1. The P-CSCF (IMS-ALG) receives an SDP offer for an MSRP media stream. For each MSRP media stream offered with transport "TCP/MSRP", if both the IMS UE and P-CSCF (IMS-ALG) indicated support for e2ae-security for MSRP during registration, the P-CSCF (IMS-ALG) allocates the required resources, includes the IMS-AGW in the media path and proceeds as specified in this clause. + +NOTE 1: An operator can choose to terminate TLS in the IMS-AGW according to the following steps for all media streams that are signalled in SIP INVITE messages with transport TCP/MSRP, even if the UE did not indicate support for e2ae security during registration. This can lead to session failures for pre-Rel-12 IMS UEs or non-IMS UEs due to a mismatch of security parameters sent by the network and expected by the UE, but on the other hand, it will ensure compatibility with GSMA RCS 5.1 [35, 36], which recommends to always use e2ae security for MSRP on the terminating leg. + +- 2.-4. The IMS-ALG uses the "Reserve AGW Connection Point" procedure to request a termination for "TCP/TLS" media (for application-agnostic interworking) or "TCP/TLS/MSRP" media (for application-aware interworking) towards the access network. In turn, the IMS-AGW communicates the fingerprint of the certificate it is going to use for setting up protection for this media stream to the P-CSCF (IMS-ALG). To indicate that the IMS-AGW shall operate in TCP Proxy mode, the IMS-ALG provides "a=setup:actpass" attribute. The IMS-ALG sets the interlinkage topology on the termination T1 to configure the IMS-AGW to use the TCP connection establishment request (TCP SYN) received at the termination T1 as a trigger to send a TCP connection establishment on the termination T2. + +NOTE 2: If "a=setup:passive" is received in the SDP answer in step 13, the IMS-ALG then needs to sets the interlinkage topology on the termination T2 (not depicted) + +- 5.-7. The IMS-ALG uses the "Reserve And Configure AGW Connection Point" procedure to request a termination for "TCP" media (for application-agnostic interworking) or "TCP/ MSRP" media (for application-aware interworking) towards the core network. To indicate that the IMS-AGW shall operate in TCP Proxy mode, the IMS-ALG provides "a=setup:actpass" attribute. +8. The P-CSCF (IMS-ALG) changes the transport from "TCP/ MSRP" to "TCP/TLS/MSRP" in the SDP offer, adds the "a=3ge2ae:applied" SDP attribute and the fingerprint SDP attribute received from the IMS-AGW, and inserts the address information received from the IMS-AGW. +9. The P-CSCF (IMS-ALG) forwards the SDP offer. +10. The UE B chooses to become the active party in the TCP connection establishment and sends a TCP SYN to establish the TCP connection. If the P-CSCF (IMS-ALG) indicated to the IMS-AGW at step 2 that it shall ignore any incoming TCP connection establishment requests (TCP SYN), e.g. to enable a remote source transport address filtering, or if the P-CSCF (IMS-ALG) did not indicate to the IMS-AGW at step 2 that it shall latch onto the required destination address via the source address/port of the incoming media, the IMS-AGW shall drop the TCP SYN received from the UE. + If the TCP SYN is not answered before a timer expiry, the UE will send the TCP SYN a second time (step 10'). + The IMS-AGW will answer a repeated TCP SYN if it is received after step 14 (step 10'). + The IMS-AGW answers the TCP SYN and the remote peer completes the TCP connection establishment. +11. The IMS-AGW uses the TCP SYN received at the termination T1 (at step 10 or step 10' if the TCP SYN is dropped at step 10) as a trigger to send a TCP SYN towards the core network to establish a TCP connection (effectively making the IMS-AGW acting as the TCP client towards the core network). The remote peer answers the TCP SYN and the IMS-AGW completes the TCP connection establishment. +12. Upon completion of the TCP connection establishment, the UE B starts the establishment of the TLS session. The IMS-AGW needs to wait until step 14 to verify the received fingerprint. +13. The P-CSCF (IMS-ALG) receives the SDP answer. It contains the fingerprint attribute with the UE's certificate in accordance to IETF RFC 4975 [25]. + +- 14.-16. The IMS-ALG uses the "Configure AGW Connection Point" procedure to configure the termination towards the UE B with remote address information. In the remote descriptor, it also provides fingerprint attribute received from the UE. This instructs the IMS-AGW to verify during the subsequent TLS handshake with the IMS UE that the fingerprint of the certificate passed by the IMS UE during this TLS handshake matches the fingerprint passed by the P-CSCF (IMS-ALG) to the IMS-AGW. If the P-CSCF (IMS-ALG) indicated to the IMS-AGW at step 2 that it shall ignore any incoming TCP connection establishment requests (TCP SYN), the IMS-ALG indicates to the IMS-AGW to accept incoming TCP connection establishment (TCP SYN) only from the indicated remote transport address. +17. The P-CSCF (IMS-ALG) modifies the SDP answer before sending it to the core network. The P-CSCF (IMS-ALG) sets the transport to "TCP/ MSRP" and removes the SDP fingerprint attribute. +18. The P-CSCF (IMA-ALG) then sends the updated SDP answer to core network. + +#### 6.2.10.3.1.2.2 IMS-ALG requests sending an outgoing TCP bearer establishment + +Figure 6.2.10.3.1.2.2.1 shows an example call flow for the terminating session set-up procedures for one MSRP media stream using e2ae security, where the IMS-ALG requests sending an outgoing TCP bearer establishment. + +![Sequence diagram showing the interaction between P-CSCF (IMS-ALG), IMS-AGW, and UE-B. The diagram details the setup of media paths, including SDP offers, H.248 ADD/MOD requests, and TCP/TLS handshakes. Brackets on the left indicate specific AGW connection point actions: 'Reserve AGW Connection Point (, Change Through-Connection)', 'Reserve and Configure AGW Connection Point (, Change Through-Connection)', 'Configure AGW Connection Point (, Change Through-Connection)', and 'Configure AGW Connection Point (, Change Through-Connection)'.](c0ca823603794512478906b302176bca_img.jpg) + +**Sequence of Interactions:** + +- SDP offer (c=IP1o, m=P1o TCP/MSRP, a=setup:actpass) from UE-B to P-CSCF (IMS-ALG). +- P-CSCF (IMS-ALG) sends H.248 ADD req to IMS-AGW (C=?, T=?, m=TCP/TLS/MSRP, a=setup:actpass, LAddr=?, LPort=?, a=fingerprint?). +- IMS-AGW performs **3. Create outgoing termination T1**. +- IMS-AGW sends H.248 ADD resp to P-CSCF (IMS-ALG) (C=C1, T=T1, LAddr=IP2o, LPort=P2o, a=fingerprint:agw). +- P-CSCF (IMS-ALG) sends H.248 ADD req to IMS-AGW (C=C1, T=?, m=TCP/MSRP, a=setup:actpass, LAddr=?, LPort=?, RAddr=IP1o, RPort=P1o). +- IMS-AGW performs **6. Create incoming termination T2**. +- IMS-AGW sends H.248 ADD resp to P-CSCF (IMS-ALG) (C=C1, T=T2, LAddr=IP2a, LPort=P2a, RAddr=IP1o, RPort=P1o). +- P-CSCF (IMS-ALG) performs **8. Modify SDP offer**. +- P-CSCF (IMS-ALG) sends SDP offer to UE-B (c=IP2o, m=P2o TCP/TLS/MSRP, a=3ge2ae:applied, a=setup:actpass, a=fingerprint:agw). +- UE-B sends TCP SYN to IMS-AGW. +- IMS-AGW responds with TCP SYN ACK, TCP ACK, and TLS Setup. +- UE-B sends SDP answer to P-CSCF (IMS-ALG) (c=IP1a, m=P1a TCP/TLS/MSRP, a=setup:active, a=fingerprint:ue-b). +- P-CSCF (IMS-ALG) sends H.248 MOD req to IMS-AGW (C=C1, T=T1, RAddr=IP1a, RPort=P1a, a=fingerprint:ue-b). +- IMS-AGW performs **14. Configure outgoing termination T1**. +- IMS-AGW sends H.248 MOD resp to P-CSCF (IMS-ALG) (C=C1, T=T1). +- P-CSCF (IMS-ALG) sends H.248 MOD req to IMS-AGW (C=C1, T=T2, TCP:EstablishBNC). +- IMS-AGW performs **17. Configure incoming termination T2**. +- IMS-AGW sends H.248 MOD resp to P-CSCF (IMS-ALG) (C=C1, T=T2). +- IMS-AGW sends TCP SYN to P-CSCF (IMS-ALG). +- P-CSCF (IMS-ALG) responds with TCP SYN ACK, TCP ACK, and TLS Setup. +- P-CSCF (IMS-ALG) performs **20. Modify SDP answer**. +- P-CSCF (IMS-ALG) sends SDP answer to UE-B (c=IP2a, m=P2a TCP/MSRP, a=setup:active). +- UE-B sends TCP SYN to IMS-AGW. +- IMS-AGW responds with TCP SYN ACK, TCP ACK, and TLS Setup. + +Sequence diagram showing the interaction between P-CSCF (IMS-ALG), IMS-AGW, and UE-B. The diagram details the setup of media paths, including SDP offers, H.248 ADD/MOD requests, and TCP/TLS handshakes. Brackets on the left indicate specific AGW connection point actions: 'Reserve AGW Connection Point (, Change Through-Connection)', 'Reserve and Configure AGW Connection Point (, Change Through-Connection)', 'Configure AGW Connection Point (, Change Through-Connection)', and 'Configure AGW Connection Point (, Change Through-Connection)'. + +**Figure 6.2.10.3.1.2.2.1: Terminating example call flow for e2ae security for MSRP where the IMS-ALG requests sending an outgoing TCP bearer establishment** + +The IMS UE B performs an IMS terminating session set-up according to 3GPP TS 23.228 [2], with modifications as described in 3GPP TS 33.328 [12]. + +The procedure in the above figure for requesting e2ae security for a media stream is described step-by-step with an emphasis on the additional aspects for IMS-ALG and IMS-AGW of media protection using TLS. + +1. As step 1 in figure 6.2.10.3.1.2.1.1. +- 2.-4. As steps 2-4 in figure 6.2.10.3.1.2.1.1 with the exception that the IMS-ALG does not set the interlinkage topology on the termination T1. +- 5.-7. As steps 7-7 in figure 6.2.10.3.1.2.1.1. +8. As step 8 in figure 6.2.10.3.1.2.1.1. +9. As step 9 in figure 6.2.10.3.1.2.1.1. +10. As step 10 in figure 6.2.10.3.1.2.1.1. + +NOTE: The incoming TCP SYN does not trigger the sending of an outgoing TCP SYN, and step 11 in figure 6.2.10.3.1.2.1.1 thus does not apply. + +11. As step 12 in figure 6.2.10.3.1.2.1.1. +12. As step 13 in figure 6.2.10.3.1.2.1.1. +- 13.-15. As steps 14-16 in figure 6.2.10.3.1.2.1.1. +- 16.-18. The IMS-ALG uses the "Configure AGW Connection Point" procedure to configure the termination towards the core network with the request to establish the TCP connection, in accordance with the information in the "a=setup" attribute in the SDP answer. +19. The IMS-AGW sends a TCP SYN towards the core network to establish a TCP connection. The remote peer answers with a TCP SYN ACK and the IMS-AGW replies with a TCP ACK, completing the TCP connection establishment. +20. As step 17 in figure 6.2.10.3.1.2.1.1. +21. As step 18 in figure 6.2.10.3.1.2.1.1. + +### 6.2.10.3.2 End-to-access-edge security for conferencing (BFCP) + +#### 6.2.10.3.2.1 IMS UE originating procedures for e2ae + +##### 6.2.10.3.2.1.1 Incoming TCP bearer establishment triggers an outgoing TCP bearer establishment + +Figure 6.2.10.3.2.1.1.1 shows the originating session set-up procedures for one or more BFCP media stream(s) using e2ae security. + +![Sequence diagram showing the interaction between UE-A, P-CSCF (IMS-ALG), and IMS-AGW for a session modification procedure. The diagram includes steps for SDP offer/answer exchange, H.248 ADD/MOD requests and responses, and the creation and configuration of outgoing and incoming terminations (T1, T2).](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) + +**Sequence Diagram: Session Modification Procedure** + +**Participants:** UE-A, P-CSCF (IMS-ALG), IMS-AGW + +**Key Messages:** + +- 1. SDP offer** (c=IP1o, m=P1o TCP/TLS/BFCP, a=3ge2ae:requested, a=setup:actpass, a=fingerprint:ue-a) from UE-A to P-CSCF +- 2. H.248 ADD req** (C=?, T=?, m=TCP, a=setup:actpass, LAddr=?, LPort=?, interlinkage=[\*:TCP:TCP,est]) from P-CSCF to IMS-AGW +- 3. Create outgoing termination T2** (IMS-AGW internal action) +- 4. H.248 ADD resp** (C=C1, T=T2, LAddr=IP2o, LPort=P2o) from IMS-AGW to P-CSCF +- 5. H.248 ADD req** (C=C1, T=?, m=TCP/TLS, a=setup:actpass, LAddr=?, LPort=?, a=fingerprint ?, RAddr=IP1o, RPort=P1o, a=fingerprint:ue-a) from P-CSCF to IMS-AGW +- 6. Create incoming termination T1** (IMS-AGW internal action) +- 7. H.248 ADD resp** (C=C1, T=T1, LAddr=IP2a, LPort=P2a, a=fingerprint:agw, RAddr=IP1o, RPort=P1o) from IMS-AGW to P-CSCF +- 8. Modify SDP offer** (P-CSCF internal action) +- 9. SDP offer** (c=IP2o, m=P2o TCP/BFCP, a=setup:actpass) from P-CSCF to UE-A +- 10. TCP SYN** (UE-A to IMS-AGW), **11. TCP SYN ACK** (IMS-AGW to UE-A), **TCP SYN ACK** (IMS-AGW to P-CSCF), **TCP ACK** (P-CSCF to IMS-AGW) +- 12. TLS Setup** (IMS-AGW to P-CSCF) +- 13. SDP answer** (c=IP1a, m=P1a TCP/BFCP, a=setup:active) from P-CSCF to UE-A +- 14. H.248 MOD req** (C=C1, T=T2, RAddr=IP1a, RPort=P1a) from P-CSCF to IMS-AGW +- 15. Configure outgoing termination T2** (IMS-AGW internal action) +- 16. H.248 MOD resp** (C=C1, T=T2) from IMS-AGW to P-CSCF +- 17. Modify SDP answer** (P-CSCF internal action) +- 18. SDP answer** (c=IP2a, m=P2a TCP/TLS/BFCP, a=3ge2ae:requested, a=setup:active, a=fingerprint:agw) from P-CSCF to UE-A +- 10'. TCP SYN** (UE-A to IMS-AGW), **11'. TCP SYN ACK** (IMS-AGW to UE-A), **TCP SYN ACK** (IMS-AGW to P-CSCF), **TCP ACK** (P-CSCF to IMS-AGW) +- 12'. TLS Setup** (IMS-AGW to P-CSCF) + +**Local Actions:** + +- Reserve AGW Connection Point (, Change Through-Connection)** at P-CSCF between steps 2 and 5. +- Reserve and Configure AGW Connection Point (, Change Through-Connection)** at P-CSCF between steps 5 and 7. +- Configure AGW Connection Point (, Change Through-Connection)** at P-CSCF between steps 14 and 16. + +Sequence diagram showing the interaction between UE-A, P-CSCF (IMS-ALG), and IMS-AGW for a session modification procedure. The diagram includes steps for SDP offer/answer exchange, H.248 ADD/MOD requests and responses, and the creation and configuration of outgoing and incoming terminations (T1, T2). + +**Figure 6.2.10.3.2.1.1.1: Originating example call flow for e2ae security for BFCP where an incoming TCP bearer establishment triggers an outgoing TCP bearer establishment** + +The IMS UE A performs an IMS originating session set-up according to 3GPP TS 23.228 [2], with modifications as described in 3GPP TS 33.328 [12]. + +The procedure in the above figure for requesting e2ae security for a media stream is described step-by-step with an emphasis on the additional aspects for IMS-ALG and IMS-AGW of media protection using TLS. + +1. IMS UE A sends an SDP offer for a media stream containing cryptographic information, together with an "a=3ge2ae:requested" SDP attribute for the BFCP-related SDP m-line, to the P-CSCF (IMS-ALG). For e2ae protection of BFCP the cryptographic information contained in the SDP offer consists of the fingerprint of the certificate of IMS UE A in accordance to IETF RFC 4975 [25]. For each media stream that uses transport "TCP/TLS/BFCP", the P-CSCF (IMS-ALG) checks for the presence of the "a=3ge2ae:requested" SDP attribute. If that indication is present and the P-CSCF (IMS-ALG) indicated support of e2ae-security for BFCP during registration, the P-CSCF (IMS-ALG) allocates the required resources, includes the IMS-AGW in the media path and proceeds as specified in this clause. +- 2.-4. The IMS-ALG uses the "Reserve AGW Connection Point" procedure to request a termination for "TCP" media towards the core network. To indicate that the IMS-AGW shall operate in TCP Proxy mode, the IMS-ALG provides "a=setup:actpass" attribute. The IMS-ALG sets the interlinkage topology on the termination T2 to configure the IMS-AGW to use the TCP connection establishment request (TCP SYN) received at the termination T2 as a trigger to send a TCP connection establishment on the termination T1. + +NOTE 1: If "a=setup:passive" is received in the SDP answer in step 13, the IMS-ALG then needs to set the interlinkage topology on the termination T1 (not depicted). + +- 5.-7. The IMS-ALG uses the "Reserve And Configure AGW Connection Point" procedure to request a termination for "TCP/TLS" media towards the access network. In the remote descriptor, it provides the IP address, port and fingerprint attribute received from the UE containing the fingerprint of the UE's certificate in accordance to IETF RFC 4975 [25]. This instructs the IMS-AGW to verify during the subsequent TLS handshake with the IMS UE that the fingerprint of the certificate passed by the IMS UE during this TLS handshake matches the fingerprint passed by the P-CSCF (IMS-ALG) to the IMS-AGW. In turn, the IMS-AGW communicates the fingerprint of the certificate it is going to use for setting up protection for this media stream to the P-CSCF (IMS-ALG). To indicate that the IMS-AGW shall operate in TCP Proxy mode, the IMS-ALG provides "a=setup:actpass" attribute. +8. The P-CSCF (IMS-ALG) changes the transport from "TCP/TLS/BFCP" to "TCP/BFCP" in the SDP offer, removes the "a=3ge2ae:requested" SDP attribute and the fingerprint SDP attribute, and inserts the address information received from the IMS-AGW. +9. The P-CSCF (IMS-ALG) forwards the SDP offer. +10. The remote peer chooses to become the active party in the TCP connection establishment and sends a TCP SYN to establish the TCP connection. If the P-CSCF (IMS-ALG) indicated to the IMS-AGW at step 2 that it shall ignore any incoming TCP connection establishment requests (TCP SYN), e.g. to enable a remote source transport address filtering, or if the P-CSCF (IMS-ALG) did not indicate to the IMS-AGW at step 2 that it shall latch onto the required destination address via the source address/port of the incoming media, the IMS-AGW shall drop the TCP SYN received from the remote peer. +If the TCP SYN is not answered before a timer expiry, the remote peer will send the TCP SYN a second time (step 10'). The IMS-AGW will answer a repeated TCP SYN if it is received after step 14 (step 10'). +The IMS-AGW answers the TCP SYN and the remote peer completes the TCP connection establishment. +11. The IMS-AGW uses the TCP SYN received at the termination T2 (at step 10 or step 10' if the TCP SYN is dropped at step 10) as a trigger to send a TCP SYN towards the UE to establish a TCP connection (effectively making the IMS-AGW acting as the TCP client towards the UE). The UE answers the TCP SYN and the IMS-AGW completes the TCP connection establishment. +12. Upon completion of the TCP connection establishment, the UE B starts the establishment of the TLS session. The IMS-AGW needs to wait until step 14 to verify the received fingerprint. +13. The P-CSCF (IMS-ALG) receives the SDP answer. + +14.-16. The IMS-ALG uses the "Configure AGW Connection Point" procedure to configure the termination towards the core network with remote address information. If the P-CSCF (IMS-ALG) indicated to the IMS-AGW at step 2 that it shall ignore any incoming TCP connection establishment requests (TCP SYN), the IMS-ALG indicates to the IMS-AGW to accept incoming TCP connection establishment (TCP SYN) only from the indicated remote transport address. + +NOTE 2: For "a=setup:active" in the SDP answer, these steps could possibly be skipped if the P-CSCF (IMS-ALG) indicated to the IMS-AGW at step 2 that it shall latch onto the required destination address via the source address/port of the incoming media, as the IMS-AGW will then use the address information in the TCP SYN when replying. + +17. The P-CSCF (IMS-ALG) modifies the SDP answer before sending it to the UE A. The P-CSCF (IMS-ALG) sets the transport to "TCP/TLS/BFCP" and includes the fingerprint of the IMS-AGW's certificate in accordance to IETF RFC 4975 [25]. + +18. The P-CSCF (IMA-ALG) then sends the updated SDP answer to IMS UE A. After receiving this message IMS UE A completes the media security setup. + +#### 6.2.10.3.2.2 IMS UE terminating procedures for e2ae + +##### 6.2.10.3.2.2.1 Incoming TCP bearer establishment triggers an outgoing TCP bearer establishment + +Figure 6.2.10.3.2.2.1.1 shows the terminating session set-up procedures for one or more BFCP media stream(s) using e2ae security. + +![](0b998e3ad8f9d104768642612605cb35_img.jpg) + +Sequence diagram illustrating the interaction between P-CSCF (IMS-ALG), IMS-AGW, and UE-B. + +**1. SDP offer (c=IP1o, m=P1o TCP/BFCP, a=setup:actpass)** (from UE-B to P-CSCF) + +**2. H.248 ADD req (C=?, T=?, m=TCP/TLS, a=setup:actpass, LAddr=?, LPort=?, a=fingerprint?, interlinkage=[\*:TCP:TCP,est], TLS:EstablishBNC)** (from P-CSCF to IMS-AGW) + +**Reserve AGW Connection Point (, Change Through-Connection)** + +**3. Create outgoing termination T1** (from IMS-AGW) + +**4. H.248 ADD resp (C=C1, T=T1, LAddr=IP2o, LPort=P2o, a=fingerprint:agw)** (from IMS-AGW to P-CSCF) + +**5. H.248 ADD req (C=C1, T=?, m=TCP, a=setup:actpass, LAddr=?, LPort=?, RAddr=IP1o, RPort=P1o)** (from P-CSCF to IMS-AGW) + +**Reserve and Configure AGW Connection Point (, Change Through-Connection)** + +**6. Create incoming termination T2** (from IMS-AGW) + +**7. H.248 ADD resp (C=C1, T=T2, LAddr=IP2a, LPort=P2a, RAddr=IP1o, RPort=P1o)** (from IMS-AGW to P-CSCF) + +**8. Modify SDP offer** (from P-CSCF) + +**9. SDP offer (c=IP2o, m=P2o TCP/TLS/BFCP, a=3ge2ae:applied, a=setup:actpass, a=fingerprint:agw)** (from P-CSCF to UE-B) + +**10. TCP SYN** (from UE-B to IMS-AGW) + +**11. TCP SYN** (from IMS-AGW to P-CSCF) + +**TCP SYN ACK** (from IMS-AGW to UE-B) + +**TCP ACK** (from UE-B to IMS-AGW) + +**TCP ACK** (from IMS-AGW to P-CSCF) + +**12. TLS Setup** (from UE-B to IMS-AGW) + +**13. SDP answer (c=IP1a, m=P1a TCP/TLS/BFCP, a=setup:active, a=fingerprint:ue-b)** (from UE-B to P-CSCF) + +**14. H.248 MOD req (C=C1, T=T1, RAddr=IP1a, RPort=P1a, a=fingerprint:ue-b)** (from P-CSCF to IMS-AGW) + +**Configure AGW Connection Point (, Change Through-Connection)** + +**15. Configure outgoing termination T1** (from IMS-AGW) + +**16. H.248 MOD resp (C=C1, T=T1)** (from IMS-AGW to P-CSCF) + +**17. Modify SDP answer** (from P-CSCF) + +**18. SDP answer (c=IP2a, m=P2a TCP/BFCP, a=setup:active)** (from P-CSCF to UE-B) + +**10'. TCP SYN** (from UE-B to IMS-AGW) + +**11'. TCP SYN** (from IMS-AGW to P-CSCF) + +**TCP SYN ACK** (from IMS-AGW to UE-B) + +**TCP ACK** (from UE-B to IMS-AGW) + +**TCP ACK** (from IMS-AGW to P-CSCF) + +**12'. TLS Setup** (from UE-B to IMS-AGW) + +**Figure 6.2.10.3.2.2.1.1: Terminating example call flow for e2ae security for MSRP where an incoming TCP bearer establishment triggers an outgoing TCP bearer establishment** + +The IMS UE B performs an IMS terminating session set-up according to 3GPP TS 23.228 [2], with modifications as described in 3GPP TS 33.328 [12]. + +The procedure in the above figure for requesting e2ae security for a media stream is described step-by-step with an emphasis on the additional aspects for IMS-ALG and IMS-AGW of media protection using TLS. + +1. The P-CSCF (IMS-ALG) receives an SDP offer for an MSRP media stream. For each BFCP media stream offered with transport "TCP/BFCP", if both the IMS UE and P-CSCF (IMS-ALG) indicated support for e2ae-security for BFCP during registration, the P-CSCF (IMS-ALG) allocates the required resources, includes the IMS-AGW in the media path and proceeds as specified in this clause. +- 2.-4. The IMS-ALG uses the "Reserve AGW Connection Point" procedure to request a termination for "TCP/TLS" media towards the access network. The IMS-ALG configures the IMS-AGW with the request to start the establishment of the TLS session once the TCP connection is established (effectively making the IMS-AGW acting as the TLS client). . To indicate that the IMS-AGW shall operate in TCP Proxy mode, the IMS-ALG provides "a=setup:actpass" attribute. The IMS-ALG sets the interlinkage topology on the termination T1 to configure the IMS-AGW to use the TCP connection establishment request (TCP SYN) received at the termination T1 as a trigger to send a TCP connection establishment on the termination T2. The IMS-AGW communicates the fingerprint of the certificate it is going to use for setting up protection for this media stream to the P-CSCF (IMS-ALG). + +NOTE: If "a=setup:passive" is received in the SDP answer in step 13, the IMS-ALG then needs to sets the interlinkage topology on the termination T2 (not depicted) + +- 5.-7. The IMS-ALG uses the "Reserve And Configure AGW Connection Point" procedure to request a termination for "TCP" media towards the core network. To indicate that the IMS-AGW shall operate in TCP Proxy mode, the IMS-ALG provides "a=setup:actpass" attribute. +8. The P-CSCF (IMS-ALG) changes the transport from "TCP/ BFCP" to "TCP/TLS/BFCP" in the SDP offer, adds the "a=3ge2ae:applied" SDP attribute and the fingerprint SDP attribute received from the IMS-AGW, and inserts the address information received from the IMS-AGW. +9. The P-CSCF (IMS-ALG) forwards the SDP offer. +10. The UE B chooses to become the active party in the TCP connection establishment and sends a TCP SYN to establish the TCP connection. If the P-CSCF (IMS-ALG) indicated to the IMS-AGW at step 2 that it shall ignore any incoming TCP connection establishment requests (TCP SYN), e.g. to enable a remote source transport address filtering, or if the P-CSCF (IMS-ALG) did not indicate to the IMS-AGW at step 2 that it shall latch onto the required destination address via the source address/port of the incoming media, the IMS-AGW shall drop the TCP SYN received from the UE. +If the TCP SYN is not answered before a timer expiry, the UE will send the TCP SYN a second time (step 10'). +The IMS-AGW will answer a repeated TCP SYN if it is received after step 14 (step 10'). +The IMS-AGW answers the TCP SYN and the remote peer completes the TCP connection establishment. +11. The IMS-AGW sends a TCP SYN towards the core network to establish a TCP connection. The remote peer answers the TCP SYN and the IMS-AGW completes the TCP connection establishment. +12. Upon completion of the TCP connection establishment, the IMS-AGW starts the establishment of the TLS session. The IMS-AGW needs to wait until step 14 to verify the received fingerprint. +13. The P-CSCF (IMS-ALG) receives the SDP answer. It contains the fingerprint attribute with the UE's certificate in accordance to IETF RFC 4975 [25]. +- 14.-16. The IMS-ALG uses the "Configure AGW Connection Point" procedure to configure the termination towards the UE B with remote address information. In the remote descriptor, it also provides fingerprint attribute received from the UE. This instructs the IMS-AGW to verify during the TLS handshake with the IMS UE (see step 12) that the fingerprint of the certificate passed by the IMS UE during this TLS handshake matches the fingerprint passed by the P-CSCF (IMS-ALG) to the IMS-AGW. If the P-CSCF (IMS-ALG) indicated to the IMS-AGW at step 2 that it shall ignore any incoming TCP connection establishment requests (TCP SYN), the IMS-ALG indicates to the IMS-AGW to accept incoming TCP connection establishment (TCP SYN) only from the indicated remote transport address. + +17. The P-CSCF (IMS-ALG) modifies the SDP answer before sending it to the core network. The P-CSCF (IMS-ALG) sets the transport to "TCP/ BFCP" and removes the SDP fingerprint attribute. +18. The P-CSCF (IMS-ALG) then sends the updated SDP answer to core network. + +## 6.2.10.4 End-to-access-edge security for UDP based media using DTLS + +### 6.2.10.4.1 General + +The IMS-ALG and the IMS-AGW may support e2ae security for the UDP based media using DTLS and certificate fingerprints. + +The following clauses describe extensions to the Iq signalling procedures and their interactions with SIP signalling in the control plane and with user plane procedures if the e2ae security for the UDP based media using DTLS and certificate fingerprints is supported by the IMS-ALG and the IMS-AGW and if the IMS-ALG indicated support of e2ae security for the UDPTL using DTLS and certificate fingerprints during registration. + +### 6.2.10.4.2 Session establishment from IMS access network for T.38 fax using "UDP/TLS/UDPTL" + +Upon receipt of an SDP offer from the IMS access network containing T.38 fax media using the "UDP/TLS/UDPTL" transport protocol with the associated: + +- 3ge2ae SDP attribute, as defined in 3GPP TS 24.229 [11], with a value "requested"; +- fingerprint SDP attribute(s) as defined in IETF RFC 8122 [80]; +- DTLS association identity SDP attribute "a=tls-id" defined in IETF RFC 8842 [81]; and +- setup SDP attribute as defined in IETF RFC 4145 [30]; + +the IMS-ALG shall: + +- check the received value of the setup SDP attribute to determine if the IMS-AGW needs to act as DTLS client or DTLS server. When the received value is equal to: + - a) "active" the IMS-AGW needs to act as DTLS server; + - b) "passive" the IMS-AGW needs to act as DTLS client; or + - c) "actpass" the IMS-ALG shall decide if the IMS-AGW needs to act as DTLS client or DTLS server; +- when reserving the transport addresses/resources towards the IMS access network: + - a) indicate to the IMS-AGW "UDP/DTLS" as transport protocol; + - b) if the IMS-AGW needs to act as DTLS client, include the Establish (D)TLS session information element to request the IMS-AGW to start the DTLS session setup; + - c) include the Notify (D)TLS session establishment Failure Event information element to request the IMS-AGW to report the unsuccessful DTLS session setup; + - d) include the Remote certificate fingerprint information element with the value of the received fingerprint SDP attribute(s); and + - e) include the Local certificate fingerprint Request information element to request the certificate fingerprint of the IMS-AGW; +- indicate to the IMS-AGW "UDP" as transport protocol when reserving the transport addresses/resources towards the IMS core network; and +- remove the setup SDP attribute and indicate the transport protocol "UDPTL" in the SDP offer towards the IMS core network. + +Upon receipt of an SDP answer from the IMS core network, the IMS-ALG shall: + +- in the "m=" line indicating T.38 fax using UDPTL, change the transport protocol to "UDP/TLS/UDPTL"; +- insert the fingerprint SDP attribute with the value of the Local certificate fingerprint information element received from the IMS-AGW; +- insert the "a=tls-id" SDP attribute containing a new DTLS association identity; and +- insert the setup SDP attribute with the value: + - a) "active" if the IMS-ALG requested the IMS-AGW to act as DTLS client; or + - b) "passive" if the IMS-AGW shall take the DTLS server role. + +The message sequence chart shown in the figure 6.2.10.4.2.1 gives an example of a session establishment from the IMS access network with an emphasis on the additional aspects for the IMS-ALG and the IMS-AGW for the e2ae protection of the T.38 fax media using UDPTL over DTLS. + +![Sequence diagram showing session setup from the IMS access network with e2ae protection of T.38 fax. The diagram involves IMS-ALG and IMS-AGW. It details the exchange of SDP offers/answers and H.248 ADD/MOD requests/responses to establish connections and terminations (T1, T2). The process includes DTLS handshake steps (ClientHello and remaining messages) and various AGW connection point configurations.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) + +**Sequence Diagram: Session setup from the IMS access network with e2ae protection of T.38 fax** + +**Participants:** IMS-ALG, IMS-AGW + +**Sequence of Messages:** + +- SDP offer (c=IP1o, m=P1o UDP/TLS/UDPTL, a=3ge2ae:requested, a=setup:actpass, a=fingerprint:cue-a, a=tls-id:ueanew1) [Red dotted line] +- H.248 ADD req (C=?, T=?, m=UDP, LAddr=?, LPort=?) [Solid line] +- Create outgoing termination T2 [Rounded box] +- H.248 ADD resp (C=C1, T=T2, LAddr=IP2o, LPort=P2o) [Solid line] +- Modify SDP offer [Rounded box] +- SDP offer (c=IP2o, m=P2o udptl) [Red dotted line] +- SDP answer (c=IP1a, m=P1a udptl) [Red dotted line] +- H.248 MOD req (C=C1, T=T2, RAddr=IP1a, RPort=P1a) [Solid line] +- Configure outgoing termination T2 [Rounded box] +- H.248 MOD resp (C=C1, T=T2) [Solid line] +- H.248 ADD req (C=C1, T=?, m=UDP/DTLS, Est\_DTLS, Notify\_DTLS\_Est\_failure, LAddr=?, LPort=?, a=fingerprint?, RAddr=IP1o, RPort=P1o, a=fingerprint:cue-a) [Solid line] +- Create incoming termination T1 [Rounded box] +- H.248 ADD resp (C=C1, T=T1, LAddr=IP2a, LPort=P2a, a=fingerprint:cagw, RAddr=IP1o, RPort=P1o) [Solid line] +- DTLS ClientHello [Blue dash-dot line] +- Remaining messages of DTLS handshake [Blue dash-dot line] +- Modify SDP answer [Rounded box] +- SDP answer (c=IP2a, m=P2a UDP/TLS/UDPTL, a=setup:active, a=fingerprint:cagw, a=tls-id:algnew1) [Red dotted line] + +**Annotations:** + +- Reserve AGW Connection Point (, Change Through-Connection) [Grouping steps 2, 3, 4] +- Configure AGW Connection Point (, Change Through-Connection) [Grouping steps 8, 9, 10] +- Reserve and Configure AGW Connection Point (, Change Through-Connection) [Grouping steps 11, 12, 13] + +Sequence diagram showing session setup from the IMS access network with e2ae protection of T.38 fax. The diagram involves IMS-ALG and IMS-AGW. It details the exchange of SDP offers/answers and H.248 ADD/MOD requests/responses to establish connections and terminations (T1, T2). The process includes DTLS handshake steps (ClientHello and remaining messages) and various AGW connection point configurations. + +Figure 6.2.10.4.2.1: Session setup from the IMS access network with e2ae protection of T.38 fax + +#### 6.2.10.4.3 Session establishment towards IMS access network for T.38 fax using "UDP/TLS/UDPTL" + +Upon receipt of an SDP offer from the IMS core network containing T.38 fax media using the "UDPTL" transport protocol the IMS-ALG shall: + +- when reserving the transport addresses/resources towards the IMS access network: + - a) indicate to the IMS-AGW "UDP/DTLS" as transport protocol; + - b) include the Notify (D)TLS session establishment Failure Event information element to request the IMS-AGW to report the unsuccessful DTLS session setup; and + +NOTE 1: The IMS-ALG may omit this information element when reserving resources and instead send it to the IMS-AGW when modifying the resources towards the IMS access network. + +- c) include the Local certificate fingerprint Request information element to request the certificate fingerprint of the IMS-AGW; and +- when reserving the transport addresses/resources towards the IMS core network indicate to the IMS-AGW "UDP" as transport protocol. +- modify the SDP offer that will be sent to the IMS access network by: + - in the "m=" line indicating T.38 fax using UDPTL, changing the transport protocol to "UDP/TLS/UDPTL"; + - inserting the 3ge2ae SDP attribute, as defined in 3GPP TS 24.229 [11], with a value "applied"; + - inserting the fingerprint SDP attribute, as defined in IETF RFC 8122 [80], with the value of the Local certificate fingerprint information element received from the IMS-AGW; + - inserting the "tls-id" SDP attribute with the new DTLS association identity; and + - inserting the setup SDP attribute, as defined in IETF RFC 4145 [30], e.g. with the value "actpass". + +NOTE 2: Alternatively, the IMS-ALG can set the value of the setup SDP attribute to "active" if the IMS-ALG wants that the IMS-AGW provides the DTLS client role or to "passive" if the IMS-ALG wants that the IMS-AGW provides the DTLS server role e.g. for NAT traversal. + +Upon receipt of an SDP answer from the IMS access network containing T.38 fax media using the "UDP/TLS/UDPTL" transport protocol with the associated fingerprint and setup SDP attributes, the IMS-ALG shall: + +- check the value of the received setup SDP attribute to determine if the IMS-AGW needs to act as DTLS client or DTLS server. When the received value is equal to: + - a) "active" the IMS-AGW needs to act as DTLS server; or + - b) "passive" the IMS-AGW needs to act as DTLS client; +- when modifying the transport addresses/resources towards the IMS access network: + - a) if the IMS-AGW needs to act as DTLS client, include the Establish (D)TLS session information element to request the IMS-AGW to start the DTLS session setup; + - b) include the Remote certificate fingerprint information element with the value of the received fingerprint SDP attribute(s); and + - c) if not already provided, include the Notify (D)TLS session establishment Failure Event information element to request the IMS-AGW to report the unsuccessful DTLS session setup; and +- remove the setup SDP attribute and indicate the transport protocol "UDPTL" in the SDP answer sent towards the IMS core network. + +The message sequence chart shown in the figure 6.2.10.4.3.1 gives an example of a session establishment towards the IMS access network with an emphasis on the additional aspects for the IMS-ALG and the IMS-AGW for the e2ae protection of the T.38 fax media using UDPTL over DTLS. + +NOTE 3: In the shown example it is assumed that the IMS-ALG requested the IMS-AGW at step 2 to latch onto the address of the received media packets to determine the corresponding destination address. Otherwise, the DTLS ClientHello message received at the step 10 will be dropped until the IMS-AGW receives a repeated DTLS ClientHello message after the step 13. + +![Sequence diagram showing session setup towards the IMS access network with e2ae protection of T.38 fax. The diagram involves two main entities: IMS-ALG and IMS-AGW. The process includes SDP offers, H.248 ADD/MOD requests and responses, and DTLS handshake messages. Brackets on the left indicate AGW connection point changes at steps 2, 5, and 13.](b550cb515008f6bab9f295adcb28b5f6_img.jpg) + +``` + +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + + Note left of IMS-ALG: 1. SDP offer (c=IP1o, m=P1o udptl) + IMS-ALG->>IMS-AGW: 2. H.248 ADD req (C=?, T=?, m=UDP/DTLS, Notify_DTLS_Est_failure, LAddr=?, LPort=?, a=fingerprint?) + Note right of IMS-AGW: 3. Create outgoing termination T1 + IMS-AGW-->>IMS-ALG: 4. H.248 ADD resp (C=C1, T=T1, LAddr=IP2o, LPort=P2o, a=fingerprint:cagw) + Note left of IMS-ALG: Reserve AGW Connection Point (, Change Through-Connection) + IMS-ALG->>IMS-AGW: 5. H.248 ADD req (C=C1, T=?, m=UDP, LAddr=?, LPort=?, RAddr=IP1o, RPort=P1o) + Note right of IMS-AGW: 6. Create incoming termination T2 + IMS-AGW-->>IMS-ALG: 7. H.248 ADD resp (C=C1, T=T2, LAddr=IP2a, LPort=P2a, RAddr=IP1o, RPort=P1o) + Note left of IMS-ALG: Reserve and Configure AGW Connection Point (, Change Through-Connection) + Note left of IMS-ALG: 8. Modify SDP offer + IMS-ALG->>IMS-AGW: 9. SDP offer (c=IP2o, m=P2o UDP/TLS/UDPTL, a=3ge2ae:applied, a=setup:actpass, a=fingerprint:cagw, a=tls-id:algnew1) + Note right of IMS-AGW: 10. DTLS ClientHello + Note right of IMS-AGW: 11. Remaining messages of DTLS handshake + IMS-AGW-->>IMS-ALG: 12. SDP answer (c=IP1a, m=P1a UDP/TLS/UDPTL, a=setup:active, a=fingerprint:cue-b, a=tls-id:uebnew1) + IMS-ALG->>IMS-AGW: 13. H.248 MOD req (C=C1, T=T1, RAddr=IP1a, RPort=P1a, a=fingerprint:cue-b) + Note left of IMS-ALG: Configure AGW Connection Point (, Change Through-Connection) + Note right of IMS-AGW: 14. Configure outgoing termination T1 + IMS-AGW-->>IMS-ALG: 15. H.248 MOD resp (C=C1, T=T1) + Note left of IMS-ALG: 16. Modify SDP answer + Note left of IMS-ALG: 17. SDP answer (c=IP2a, m=P2a udptl) + +``` + +Sequence diagram showing session setup towards the IMS access network with e2ae protection of T.38 fax. The diagram involves two main entities: IMS-ALG and IMS-AGW. The process includes SDP offers, H.248 ADD/MOD requests and responses, and DTLS handshake messages. Brackets on the left indicate AGW connection point changes at steps 2, 5, and 13. + +Figure 6.2.10.4.3.1: Session setup towards the IMS access network with e2ae protection of T.38 fax + +#### 6.2.10.4.4 IMS-AGW procedure for e2ae security of T.38 fax using "UDP/TLS/UDPTL" + +The IMS-AGW shall: + +- upon reception of the Local certificate fingerprint Request information element, select an own certificate for the T.38 fax media stream, uniquely associate the own certificate with the T.38 media stream, and send to the IMS-ALG the Local certificate fingerprint information element with the fingerprint of the own certificate; +- uniquely associate the value of the Remote certificate fingerprint information element, received from the IMS-ALG, with the corresponding T.38 fax media stream; +- take a DTLS server role and be prepared to receive a DTLS ClientHello message from the served UE; +- upon reception of the Establish (D)TLS session information element, take a DTLS client role and start DTLS session establishment by sending the DTLS ClientHello message to the served UE; and +- verify during the subsequent DTLS handshake with the served UE (as described in IETF RFC 7345 [33] and IETF RFC 8842 [81]) that the fingerprint of the certificate passed by the served UE during DTLS handshake matches the value of the Remote certificate fingerprint information element received from the IMS-ALG: + - a) if the verification fails, the IMS-AGW shall regard the remote DTLS endpoint as not authenticated, terminate the DTLS session and as specified in clause 6.2.10.4.5, shall report the unsuccessful DTLS session setup to the IMS-ALG; or + - b) if the verification succeeds, the IMS-AGW shall continue with DTLS session setup and when the DTLS session is established, the IMS-AGW shall be prepared to receive and convert the protected media from the served UE to the unprotected media to be sent to the core network and vice versa. + +#### 6.2.10.4.5 DTLS session establishment failure indication + +The IMS-AGW shall use a Notify (D)TLS session establishment Failure Indication procedure to report DTLS session establishment related failures. + +The figure 6.2.10.4.5.1 shows the message sequence chart example when the IMS-AGW reports the unsuccessful DTLS session setup to the IMS-ALG. + +![Sequence diagram showing DTLS session establishment failure indication between IMS-ALG and IMS-AGW.](41fa90d03d7195caa162c74d289817a4_img.jpg) + +``` +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note right of IMS-AGW: Detection of DTLS session establishment failure + IMS-AGW->>IMS-ALG: H.248 NOTIFY req [(D)TLS session establishment Error Indication] (C=C1, T=T1, cause=DTLS_establishment_error) + Note left of IMS-ALG: Notify (D)TLS session establishment Failure Indication + IMS-ALG->>IMS-AGW: H.248 NOTIFY resp [(D)TLS session establishment Error Indication] (C=C1) +``` + +The diagram illustrates the message sequence for a DTLS session establishment failure. It features two lifelines: IMS-ALG and IMS-AGW. The IMS-AGW lifeline includes a rounded rectangle labeled "Detection of DTLS session establishment failure". A solid arrow points from the IMS-AGW to the IMS-ALG, labeled "H.248 NOTIFY req [(D)TLS session establishment Error Indication] (C=C1, T=T1, cause=DTLS\_establishment\_error)". A bracket on the left side of the IMS-ALG lifeline, labeled "Notify (D)TLS session establishment Failure Indication", encompasses the return arrow. A solid arrow points from the IMS-ALG back to the IMS-AGW, labeled "H.248 NOTIFY resp [(D)TLS session establishment Error Indication] (C=C1)". + +Sequence diagram showing DTLS session establishment failure indication between IMS-ALG and IMS-AGW. + +Figure 6.2.10.4.5.1: DTLS session establishment failure indication + +## 6.2.10.5 End-to-access-edge security for RTP based media using DTLS-SRTP + +**Editor's Note:** There are two served user instances of the DTLS service within WebRTC: the data channel and the key exchange for SRTP. Thus, there are either two DTLS connections behind a single DTLS session, or two separate DTLS sessions. + +The procedures are similar to that of clause 6.2.1 apart from the IMS-ALG optionally requesting the eIMS-AGW to provide IMS media plane security using DTLS. + +Upon receipt of an SDP offer from the IMS access network, the IMS-ALG shall: + +- check the received value of the setup SDP attribute to determine if the IMS-AGW needs to act as DTLS client or DTLS server. When the received value is equal to: + - a) "active" the IMS-AGW needs to act as DTLS server; + - b) "passive" the IMS-AGW needs to act as DTLS client; or + - c) "actpass" the IMS-ALG shall decide if the IMS-AGW needs to act as DTLS client or DTLS server; +- if the received SDP offer contains "a=tls-id" media-level SDP attribute (as specified in IETF RFC 8842 [81]), create a new DTLS association identity; +- when reserving the transport addresses/resources towards the IMS access network: + - a) indicate to the eIMS-AGW "UDP/TLS/RTP/SAVP" or "UDP/TLS/RTP/SAVPF" as transport protocol; + - b) include the Remote certificate fingerprint information element with the value of the received fingerprint SDP attribute from the WIC; + - c) include the Local certificate fingerprint Request information element to request the certificate fingerprint of the eIMS-AGW; and + - d) if the IMS-AGW needs to act as DTLS client, include the Establish (D)TLS session information element to request the IMS-AGW to start the DTLS session setup; +- indicate to the eIMS-AGW "RTP/AVP" or "RTP/AVPF" over UDP as transport protocol when reserving the transport addresses/resources towards the IMS core network; and +- remove the setup SDP attribute and indicate the transport protocol "RTP/AVP" in the offer towards the IMS core network. + +Upon receipt of an SDP answer from the IMS core network, the IMS-ALG shall: + +- in the "m=" line indicating the use of SRTP, change the transport protocol to "UDP/TLS/RTP/SAVP" or "UDP/TLS/RTP/SAVPF"; +- insert the fingerprint SDP attribute with the value of the Local certificate fingerprint information element received from the eIMS-AGW; and +- insert the "a=tls-id" SDP attribute containing a new DTLS association identity; and +- insert the setup SDP attribute with the value: + - a) "active" if the IMS-ALG requested the IMS-AGW to act as DTLS client; or + - b) "passive" if the IMS-AGW shall take the DTLS server role. + +Figure 6.2.10.5.1 shows the message sequence chart example of WIC originated procedure using DTLS-SRTP. + +NOTE 1: Below establishment procedures are based on the assumption that there wasn't yet any DTLS procedure triggered from WebRTC data channel side. + +![Sequence diagram showing the WIC originated procedure using DTLS-SRTP between IMS-ALG and IMS-AGW. The diagram includes 17 numbered steps, with various annotations for AGW connection point changes and DTLS handshake details.](2b00743506f6a3bbd17af764162dc76d_img.jpg) + +``` + +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + + Note left of IMS-ALG: 1. SDP offer (c=IP1o, m=P1o UDP/TLS/RTP/SAVP, a=setup:actpass, a=fingerprint:WIC-a, a=tls-id:wicanew1) + IMS-ALG->>IMS-AGW: 2. H.248 ADD req (C=?, T=?, m=RTP/AVP, LAddr=?, LPort=?) + Note right of IMS-AGW: Reserve AGW Connection Point (, Change Through-Connection) + IMS-AGW->>IMS-AGW: 3. Create outgoing termination T2 + IMS-AGW->>IMS-ALG: 4. H.248 ADD resp (C=C1, T=T2, LAddr=IP2o, LPort=P2o) + Note left of IMS-ALG: 5. Modify SDP offer + IMS-ALG->>IMS-AGW: 6. SDP offer (c=IP2o, m=P2o RTP/AVP) + Note right of IMS-AGW: 7. SDP answer (c=IP1a, m=P1a RTP/AVP) + IMS-ALG->>IMS-AGW: 8. H.248 MOD req (C=C1, T=T2, RAddr=IP1a, RPort=P1a) + Note right of IMS-AGW: Configure AGW Connection Point (, Change Through-Connection) + IMS-AGW->>IMS-AGW: 9. Configure outgoing termination T2 + IMS-AGW->>IMS-ALG: 10. H.248 MOD resp (C=C1, T=T2) + IMS-ALG->>IMS-AGW: 11. H.248 ADD req (C=C1, T=?, m=UDP/TLS/RTP/SAVP, Est_DTLS, Notify_DTLS_Est_failure, LAddr=?, LPort=?, a=fingerprint?, RAddr=IP1o, RPort=P1o, a=fingerprint:WIC-a) + Note right of IMS-AGW: Reserve and Configure AGW Connection Point (, Change Through-Connection) + IMS-AGW->>IMS-AGW: 12. Create incoming termination T1 + IMS-AGW->>IMS-ALG: 13. H.248 ADD resp (C=C1, T=T1, LAddr=IP2a, LPort=P2a, a=fingerprint:IMS-AGW-a, RAddr=IP1o, RPort=P1o) + Note left of IMS-ALG: 14. Modify SDP answer + Note left of IMS-ALG: 15. SDP answer (c=IP2a, m=P2a UDP/TLS/RTP/SAVP, a=setup:active, a=fingerprint:IMS-AGW-a, a=tls-id:algnew1) + IMS-AGW->>IMS-ALG: 16. DTLS ClientHello + IMS-ALG->>IMS-AGW: 17. Remaining messages of DTLS handshake + +``` + +Sequence diagram showing the WIC originated procedure using DTLS-SRTP between IMS-ALG and IMS-AGW. The diagram includes 17 numbered steps, with various annotations for AGW connection point changes and DTLS handshake details. + +Figure 6.2.10.5.1: WIC originated procedure using DTLS-SRTP + +NOTE 2: The WIC may receive the ClientHello prior the SDP answer, thus the handshake might be initiated, but the handshake will not complete until the SDP answer has been received by the WIC. + +Upon receipt of an SDP offer from the IMS core network using the "RTP/AVP" or "RTP/AVPF" over UDP as transport protocol the IMS-ALG shall: + +- when reserving the transport addresses/resources towards the IMS access network: + - a) indicate to the eIMS-AGW "UDP/TLS/RTP/SAVP" or "UDP/TLS/RTP/SAVPF" as transport protocol; and + - b) include the Local certificate fingerprint Request information element to request the certificate fingerprint of the eIMS-AGW; +- when reserving the transport addresses/resources towards the IMS core network indicate to the eIMS-AGW "RTP/AVP" or "RTP/AVPF" over UDP as transport protocol; and +- modify the SDP offer that will be sent to the IMS access network by: + - a) in the "m=" line that is indicating the use of SRTP, changing the transport protocol to "UDP/TLS/RTP/SAVP" or "UDP/TLS/RTP/SAVPF"; + - b) inserting the fingerprint SDP attribute with the value of the Local certificate fingerprint information element received from the eIMS-AGW; + - c) inserting the "tls-id" SDP attribute with the new DTLS association identity; and + - d) inserting the setup SDP attribute, as defined in IETF RFC 4145 [30], with the value "actpass". + +Upon receipt of an SDP answer from the IMS access network containing the use of the "UDP/TLS/RTP/SAVP" or "UDP/TLS/RTP/SAVPF" transport protocol with the associated fingerprint and setup SDP attributes, the IMS-ALG shall: + +- check the value of the received setup SDP attribute to determine if the IMS-AGW needs to act as DTLS client or DTLS server. When the received value is equal to: + - a) "active" the IMS-AGW needs to act as DTLS server; or + - b) "passive" the IMS-AGW needs to act as DTLS client; +- when modifying the transport addresses/resources towards the IMS access network: + - a) if the IMS-AGW needs to act as DTLS client, include the Establish (D)TLS session information element to request the IMS-AGW to start the DTLS session setup; + - b) include the Remote certificate fingerprint information element with the value of the received fingerprint SDP attribute; and + - c) if not already provided, include the Notify (D)TLS session establishment Failure Event information element to request the IMS-AGW to report the unsuccessful DTLS session setup; and +- remove the setup SDP attribute and indicate the transport protocol "RTP/AVP" in the SDP answer towards the IMS core network. + +The message sequence chart shown in the figure 6.2.10.5.2 shows the message sequence chart example of WIC terminated procedure using DTLS-SRTP. + +![Sequence diagram showing the WIC terminated procedure using DTLS-SRTP between IMS-ALG and IMS-AGW. The diagram includes 17 numbered steps, with annotations for AGW connection point changes and DTLS handshake details.](ef45b00396c293be0b18d32b97118bf4_img.jpg) + +The sequence diagram illustrates the interaction between IMS-ALG and IMS-AGW for a WIC terminated procedure using DTLS-SRTP. The process is divided into three main phases indicated by curly braces on the left: + +- Reserve AGW Connection Point (, Change Through-Connection)**: Steps 1 through 4. The IMS-ALG sends an SDP offer (c=IP1o, m=P1o RTP/AVP) to the IMS-AGW. The IMS-AGW responds with an H.248 ADD req (C=?, T=?, m=UDP/DTLS, Notify\_DTLS\_Est\_failure, LAddr=?, LPort=?, a=fingerprint?). The IMS-AGW then creates an outgoing termination T1 and responds with an H.248 ADD resp (C=C1, T=T1, LAddr=IP2o, LPort=P2o, a=fingerprint:eIMS-AGW-b). +- Reserve and Configure AGW Connection Point (, Change Through-Connection)**: Steps 5 through 7. The IMS-ALG sends an H.248 ADD req (C=C1, T=?, m=UDP, LAddr=?, LPort=?, RAddr=IP1o, RPort=P1o) to the IMS-AGW. The IMS-AGW creates an incoming termination T2 and responds with an H.248 ADD resp (C=C1, T=T2, LAddr=IP2a, LPort=P2a, RAddr=IP1o, RPort=P1o). +- Configure AGW Connection Point (, Change Through-Connection)**: Steps 8 through 17. The IMS-ALG sends a Modify SDP offer. The IMS-AGW responds with an SDP offer (c=IP2o, m=P2o UDP/TLS/RTP/SAVP, a=setup:actpass, a=fingerprint:eIMS-AGW-b, a=tls-id:algnew1). The IMS-ALG responds with an SDP answer (c=IP1a, m=P1a UDP/TLS/RTP/SAVP, a=setup:active, a=fingerprint:WIC-b, a=tls-id:wicbnew1). The IMS-ALG then sends an H.248 MOD req (C=C1, T=T1, RAddr=IP1a, RPort=P1a, a=fingerprint:WIC-b) to the IMS-AGW. The IMS-AGW configures the outgoing termination T1 and responds with an H.248 MOD resp (C=C1, T=T1). The IMS-AGW then sends a DTLS ClientHello and the remaining messages of the DTLS handshake. Finally, the IMS-ALG sends a Modify SDP answer, and the IMS-AGW responds with an SDP answer (c=IP2a, m=P2a RTP/AVP). + +The DTLS handshake messages (steps 14 and 15) are shown as dashed blue arrows between the IMS-AGW and the external entity (WIC). + +Sequence diagram showing the WIC terminated procedure using DTLS-SRTP between IMS-ALG and IMS-AGW. The diagram includes 17 numbered steps, with annotations for AGW connection point changes and DTLS handshake details. + +Figure 6.2.10.5.2: WIC terminated procedure using DTLS-SRTP + +NOTE 3: The eIMS-AGW might receive the ClientHello prior receiving the MOD-request, but the DTLS handshake will not finish before the MOD-request (more specific: the fingerprint from WIC-b) has been received. + +## 6.2.10.6 End-to-access-edge security for WebRTC data channels using SCTP-over-DTLS transport + +### 6.2.10.6.1 General + +The requirements on eP-CSCF (IMS-ALG) and eIMS-AGW for the procedures to establish WebRTC data channels are specified in clause 5.20.2. + +The following clauses describe extensions to the Iq signalling procedures and their interactions with SIP signalling in the control plane and with user plane procedures if the e2ae security for the WebRTC data channels using "SCTP over DTLS" is supported by the eP-CSCF (IMS-ALG) and the eIMS-AGW. + +All message sequence charts in this clause are examples. The example high-level H.248 context model is defined in Figure 6.2.1.1 and further detailed below. + +### 6.2.10.6.2 Call flow for data channel establishment from WIC towards IMS access network and MSRP session establishment + +Support of multiple WebRTC data channels per WebRTC calls implies support of so called H.248 stream grouping. Figure 6.2.10.6.2.1 shows an example H.248 Context model for a WebRTC call with unbundled audio and video, and with multiple data components. + +![Figure 6.2.10.6.2.1: eIMS-AGW – H.248 Context model for WebRTC gateway inclusive H.248 Stream Group for WebRTC data components. The diagram shows a WebRTC domain on the left and a non-WebRTC domain on the right, separated by an eIMS-AGW. Inside the eIMS-AGW, there is an H.248 Context C1. On the WebRTC side, there are media & transport unmultiplexed RTP 'sessions' for audio/SRTP and video/SRTP, and data channels (DC) realized by SCTP streams: IM(text)/DC, ..., /DC, and Transport 'SCTP/DTLS/L4/IP'. These connect to component streams (S1, S2, ...) and a stream group (SG1) within Context C1. The component streams connect to IWF (Interworking Function) blocks: IWF 'audio', IWF 'video', IWF 'MSRP', and IWF '...'. These IWF blocks connect to component streams (S1, S2, ...) on the non-WebRTC side, which then connect to audio/(S)RTP, video/(S)RTP, IM(text)/MSRP/TCP, and ... The diagram also includes a 'TerminationState' descriptor: grouse( 'SCTP 2, ...' ) and a 'LocalControl' descriptor: strdeagg(2, ...). A legend defines the symbols for real traffic (solid line), logical traffic (dashed line), DC (WebRTC Data Channel), SG (H.248 Stream Group), component Stream or legacy Stream (S), and (de-)aggregation Stream (S1).](3e88de626facff0ce44cb3cb12c40d29_img.jpg) + +Figure 6.2.10.6.2.1: eIMS-AGW – H.248 Context model for WebRTC gateway inclusive H.248 Stream Group for WebRTC data components. The diagram shows a WebRTC domain on the left and a non-WebRTC domain on the right, separated by an eIMS-AGW. Inside the eIMS-AGW, there is an H.248 Context C1. On the WebRTC side, there are media & transport unmultiplexed RTP 'sessions' for audio/SRTP and video/SRTP, and data channels (DC) realized by SCTP streams: IM(text)/DC, ..., /DC, and Transport 'SCTP/DTLS/L4/IP'. These connect to component streams (S1, S2, ...) and a stream group (SG1) within Context C1. The component streams connect to IWF (Interworking Function) blocks: IWF 'audio', IWF 'video', IWF 'MSRP', and IWF '...'. These IWF blocks connect to component streams (S1, S2, ...) on the non-WebRTC side, which then connect to audio/(S)RTP, video/(S)RTP, IM(text)/MSRP/TCP, and ... The diagram also includes a 'TerminationState' descriptor: grouse( 'SCTP 2, ...' ) and a 'LocalControl' descriptor: strdeagg(2, ...). A legend defines the symbols for real traffic (solid line), logical traffic (dashed line), DC (WebRTC Data Channel), SG (H.248 Stream Group), component Stream or legacy Stream (S), and (de-)aggregation Stream (S1). + +**Figure 6.2.10.6.2.1: eIMS-AGW – H.248 Context model for WebRTC gateway inclusive H.248 Stream Group for WebRTC data components** + +The example flow in this clause focuses on the WebRTC data channel part only. Thus, only H.248 Streams S1 (for deaggregation of multiple data channels) and S2 (for MSRP traffic) are indicated subsequently. + +Figure 6.2.10.6.2.2 shows the message sequence chart example for the WIC originated procedure to establish a WebRTC MSRP data channel using SCTP-over-DTLS transport. + +![Sequence diagram showing the WIC originated procedure for WebRTC data channel establishment and MSRP stream establishment between WIC-A, IMS-ALG, and e-IMS-AGW.](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) + +The sequence diagram illustrates the interaction between WIC-A, IMS-ALG, and e-IMS-AGW for WebRTC data channel establishment and MSRP stream establishment. The process is divided into three main phases indicated by curly braces on the left: + +- Reserve IMS Resources:** Steps 1 through 5. WIC-A sends an SDP offer (Step 1). IMS-ALG sends an H.248 ADD req (Step 2). e-IMS-AGW creates an outgoing termination T2 (Step 3). IMS-ALG receives an H.248 ADD resp (Step 4) and modifies the SDP offer (Step 5). +- Configure IMS Resources:** Steps 6 through 14. IMS-ALG sends a modified SDP offer (Step 6). WIC-A responds with an SDP answer (Step 7). IMS-ALG sends an H.248 MOD req (Step 8). e-IMS-AGW configures the outgoing termination T2 (Step 9). IMS-ALG receives an H.248 MOD resp (Step 10). IMS-ALG then sends a complex H.248 ADD req (Step 11) to e-IMS-AGW. e-IMS-AGW creates an incoming termination T1 (Step 12). IMS-ALG receives an H.248 ADD resp (Step 13) and modifies the SDP answer (Step 14). +- Reserve and Configure IMS Resources:** Steps 15 through 18. WIC-A sends a final SDP answer (Step 15). e-IMS-AGW sends a DTLS ClientHello (Step 16). Remaining messages of the DTLS handshake (Step 17) and SCTP association establishment (Step 18) occur between WIC-A and e-IMS-AGW. + +Detailed message descriptions: + +- 1. SDP offer** (c=IP1o, m= application P1o UDP/DTLS/SCTP webrtc-datachannel, a=max-message-size:UE-Sa, a=sctp-port:UE-Pa, a=setup:actpass, a=tls-id:wic-x, a=fingerprint:UE-a, a=dcmap:SCTPstreamID-a subprotocol=MSRP, a=dcsa:SCTPstreamID-a msrp-cema, a=dcsa:SCTPstreamID-a setup=actpass, a=dcsa:SCTPstreamID-a path:path-a) +- 2. H.248 ADD req** (C=?, T=?, Stream=2 ( Local (LAddr=?, LPort=?, m=TCP) ) ) +- 3. Create outgoing termination T2** +- 4. H.248 ADD resp** (C=C1, T=T2, Stream=2 ( Local (LAddr=IP2o, LPort=P2o) ) ) +- 5. Modify SDP offer** +- 6. SDP offer** (c=IP2o, m=P2o TCP/MSRP, a=setup:actpass, a=msrp-cema, a=path:path-a) +- 7. SDP answer** (c=IP1a, m=P1a TCP/MSRP, a=setup:active, a=msrp-cema, a=path:path-b) +- 8. H.248 MOD req** (C=C1, T=T2, Stream=2 (Remote (RAddr=IP1a, RPort=P1a) ) ) +- 9. Configure outgoing termination T2** +- 10. H.248 MOD resp** (C=C1, T=T2) +- 11. H.248 ADD req** (C=C1, T=?, groupse = ["SCTP 2"] Stream=1 ( strdeagg=[2] Remote (RAddr=IP1o, RPort=P1o, m=UDP/DTLS/SCTP webrtc-datachannel, a=max-message-size:UE-Sa, a=sctp-port:UE-Pa, a=fingerprint:UE-a, a=dcmap:SCTPstreamID-a subprotocol=MSRP) Local (Est\_DTLS, Notify\_DTLS\_Est\_failure, LAddr=?, LPort=?, a=fingerprint?, m=UDP/DTLS/SCTP, a=sctp-port?, a=max-message-size?, a=dcmap:SCTPstreamID-a subprotocol=MSRP)) Stream=2 (sctpId=SCTPstreamID-a) Signal (Est\_DTLS, Est\_SCTP) Events (Detreset("accept") ) ) +- 12. Create incoming termination T1** +- 13. H.248 ADD resp** (C=C1, T=T1, Stream=1 ( Local (LAddr=IP2a, LPort=P2a, a=fingerprint:IMS-AGW-a, a=sctp-port:IMS-AGW-Pa, a=max-message-size:IMS-AGW-Sa) ) ) +- 14. Modify SDP answer** +- 15. SDP answer** (c=IP2a, m=application P2a UDP/DTLS/SCTP webrtc-datachannel, a=max-message-size:IMS-AGW-Sa, a=sctp-port:IMS-AGW-Pa, a=setup:active, a=tls-id:alg-y, a=fingerprint:IMS-AGW-a, a=dcmap:SCTPstreamID-a subprotocol=MSRP, a=dcsa:SCTPstreamID-a msrp-cema, a=dcsa:SCTPstreamID-a setup:active, a=dcsa:SCTPstreamID-a path:path-b) +- 16. DTLS ClientHello** +- 17. Remaining messages of DTLS handshake** +- 18. SCTP association establishment** + +Sequence diagram showing the WIC originated procedure for WebRTC data channel establishment and MSRP stream establishment between WIC-A, IMS-ALG, and e-IMS-AGW. + +Figure 6.2.10.6.2.2: WIC originated procedure for WebRTC data channel establishment and MSRP stream establishment + +The IMS UE A embedded WIC-A performs an IMS originating session set-up according to 3GPP TS 23.228 [2] with modifications for support of WebRTC service control. + +The procedure in the above figure for requesting an MSRP profiled WebRTC data channel is described step-by-step with an emphasis on the additional aspects for eP-CSCF (IMS-ALG) and eIMS-AGW with regards to the creation of an H.248 Context for interworking MSRP-over-DC to MSRP-over-TCP: + +1. IMS UE-A (WIC-A) sends an SDP offer for an MSRP WebRTC data channel. A new "SCTP association over DTLS association " is requested. +2. - 4. The eP-CSCF (IMS-ALG) uses the "Reserve AGW Connection Point" procedure to request a termination and H.248 Stream '2' for "MSRP-over-TCP" media towards the core network. +5. The eP-CSCF (IMS-ALG) modifies the SDP offer to offers TCP transport for MSRP, and to requests the remote peer to select the TCP setup direction. +6. The eP-CSCF (IMS-ALG) forwards the SDP offer. +7. - 10. The configuration of core network side H.248 Stream endpoint S2/T2 is completed based on the received SDP answer (7). +11. The eP-CSCF (IMS-ALG) uses the "Reserve and Configure AGW Connection Point" procedure to request a termination inclusive an H.248 Stream Group for WebRTC DC traffic. The eP-CSCF (IMS-ALG) uses an H.248 Context model with H.248 Stream grouping as required for WebRTC DC support. The Stream Group (SG) configurations according to Figure 6.2.10.6.2.1 is applied: The eP-CSCF (IMS-ALG) decides to assign H.248 StreamID value '1' to the H.248 deaggregation stream and to use H.248 StreamID value '2' for the WebRTC data channel. The following aspects should be emphasized: + - a) H.248 deaggregation stream (S1): + - covers the protocol stack segment "SCTP Association over DTLS connection over L4/IP"; + - the 'UDP' is indicated as L4 protocol; + - the SDP information related to the underlying ICE procedures is omitted in the abstracted ADD.req command; + - the deaggregation stream embedded SDP covers the attributes for configuration of the SCTP Association; + - b) H.248 component stream (S2): + - covers the upper protocol levels of the logical DC and the IP application layer (here 'MSRP'); + - c) DTLS session/DTLS association establishment: + - an outgoing establishment procedure is enabled ("which will be executed by the eIMS-AGW after successful L4 connectivity"); + - d) SCTP association establishment: + - both, an incoming and outgoing establishment procedure is enabled ("in order to emulate "SCTP simultaneous open" behaviour"); + - the eIMS-AGW would start to send an SCTP INIT chunk as soon as the DTLS connection is "data transfer ready" (see step 16); + - e) Preparation of DC release already in DC establishment phase: + - Background: DC release is based on SCTP Association level SCTP Stream reset procedures. Incoming reset requests could be either autonomously handled by the eIMS-AGW or explicitly controlled by the eP-CSCF (IMS-ALG). + - The activation of a notification mechanism is required in any case (indicating the autonomous behaviour by the default value 'accept' of the correspondent event parameter). +- 12./13. The eIMS-AGW confirms the successful creation and configuration of the requested H.248 Stream Group for WebRTC DC traffic. +- 14./15. The eP-CSCF (IMS-ALG) then sends the updated SDP answer to the IMS UE-A embedded WIC-A. + +NOTE: In figure 6.2.10.6.2.2. "a=dmap" does not contain priority information and the default priority thus applies. + +## 6.2.10A IMS end-to-end Media Plane Security + +### 6.2.10A.1 End-to-end security for RTP based media using SDES + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG providing "RTP/SAVP" or "RTP/SAVPF", as received in the SDP, to the IMS-AGW as transport protocol and not providing any other media related information to the corresponding terminations, and configuring the IMS-AGW to pass media transparently. + +The IMS-ALG shall forward the SDP with unmodified transport protocol for those media lines and unmodified SDES SDP attribute(s). + +### 6.2.10A.2 End-to-end security for TCP-based media using TLS + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG providing "TCP" to the IMS-AGW as transport protocol and not providing any TLS related information nor any other media related information to the corresponding terminations, and configuring the IMS-AGW to pass media transparently. + +The IMS-ALG shall forward the SDP with unmodified transport protocol for those media lines and unmodified TLS related SDP attribute(s). + +NOTE: End-to-end security for TCP-based media using TLS is not supported between two terminals being located behind firewalls/NATs. + +## 6.2.11 Change Through-Connection + +The Change Through-Connection procedure is used for opening and closing of gates and is mandatory for IMS-ALG and IMS-AGW to support. The IMS-ALG sets the Stream mode parameter using the Change Through-Connection procedure to request the IMS-AGW to one-way or both-way through-connect or block media streams on a termination. + +The IMS-ALG may combine the Change Through-Connection procedure with the Reserve and Configure AGW Connection Point, Reserve AGW Connection Point or Configure AGW Connection Point procedure as in Figure 6.2.1.2., or may apply this procedure separately. + +## 6.2.12 Emergency Calls + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG requesting the IMS-AGW to treat the call as emergency call with a preferential handling by including the information element "Emergency Call Indicator" within the "Reserve and Configure AGW Connection Point" or "Reserve AGW Connection Point procedure". + +## 6.2.13 Explicit Congestion Notification support + +### 6.2.13.1 General + +An IMS-ALG may configure the IMS-AGW to transfer the ECN bits in the IP header transparent (see clause 6.2.13.2) or to act as an ECN endpoint (see clause 6.2.13.3). See clause 5.12. + +### 6.2.13.2 ECN Active Indicated (ECN transparent) + +Figure 6.2.13.2.1 shows the message sequence chart example for indicating ECN transparent. + +![Sequence diagram for Figure 6.2.13.2.1: Procedure to indicate ECN transparent negotiated. The diagram shows two lifelines: IMS-ALG and IMS-AGW. The IMS-ALG sends an H.248:ADD.req message to the IMS-AGW with parameters: Termination X, Transport = RTP/AVPF, ECN_enable = True, and Initialisation_Method = Inactive. The IMS-AGW responds with H.248:ADD.resp[Termination X]. Annotations indicate that the IMS-AGW reserves and configures the AGW connection point, and indicates transport support for explicit congestion notification transparently.](b50f38be091844d58b11e3d47bc71e73_img.jpg) + +``` + +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note left of IMS-ALG: Context(Cx) + IMS-ALG->>IMS-AGW: H.248:ADD.req[ +Termination X, +Transport = RTP/AVPF, +ECN_enable = True, +Initialisation_Method = Inactive] + Note right of IMS-AGW: Reserve and Configure AGW Connection Point + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[Termination X] + Note right of IMS-AGW: Indicates Transport and requests IMS-AGW to support explicit congestion notification transparently + Note left of IMS-ALG: Context(Cx) + +``` + +Sequence diagram for Figure 6.2.13.2.1: Procedure to indicate ECN transparent negotiated. The diagram shows two lifelines: IMS-ALG and IMS-AGW. The IMS-ALG sends an H.248:ADD.req message to the IMS-AGW with parameters: Termination X, Transport = RTP/AVPF, ECN\_enable = True, and Initialisation\_Method = Inactive. The IMS-AGW responds with H.248:ADD.resp[Termination X]. Annotations indicate that the IMS-AGW reserves and configures the AGW connection point, and indicates transport support for explicit congestion notification transparently. + +**Figure 6.2.13.2.1: Procedure to indicate ECN transparent negotiated** + +Upon receipt of the indication that ECN transparent has been negotiated, the IMS-AGW shall forward ECN bits within IP packets unmodified. Any RTCP feedback received shall be passed unchanged. + +### 6.2.13.3 ECN support requested (ECN endpoint) + +Figure 6.2.13.3.1 shows the message sequence chart example for requesting ECN endpoint. + +![Sequence diagram for Figure 6.2.13.3.1: Procedure to Request ECN endpoint. The diagram shows two lifelines: IMS-ALG and IMS-AGW. The IMS-ALG sends an H.248:ADD.req message to the IMS-AGW with parameters: Termination X, Transport = RTP/AVPF, ECN_enable = True, and Initialisation_Method ≠ inactive, {Notify_ECN_Error}. The IMS-AGW responds with H.248:ADD.resp[Termination X]. Annotations indicate that the IMS-AGW reserves and configures the AGW connection point, and indicates transport support and requests the IMS-AGW to act as an ECN endpoint.](497d7e14540664a2914557cad79f3791_img.jpg) + +``` + +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note left of IMS-ALG: Context(Cx) + IMS-ALG->>IMS-AGW: H.248:ADD.req[ +Termination X, +Transport = RTP/AVPF, +ECN_enable=True, +Initialisation_Method ≠ inactive, +{Notify_ECN_Error}] + Note right of IMS-AGW: Reserve and Configure AGW Connection Point + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[Termination X] + Note right of IMS-AGW: Indicates Transport and requests IMS-AGW to act as an ECN endpoint + Note left of IMS-ALG: Context(Cx) + +``` + +Sequence diagram for Figure 6.2.13.3.1: Procedure to Request ECN endpoint. The diagram shows two lifelines: IMS-ALG and IMS-AGW. The IMS-ALG sends an H.248:ADD.req message to the IMS-AGW with parameters: Termination X, Transport = RTP/AVPF, ECN\_enable = True, and Initialisation\_Method ≠ inactive, {Notify\_ECN\_Error}. The IMS-AGW responds with H.248:ADD.resp[Termination X]. Annotations indicate that the IMS-AGW reserves and configures the AGW connection point, and indicates transport support and requests the IMS-AGW to act as an ECN endpoint. + +**Figure 6.2.13.3.1: Procedure to Request ECN endpoint** + +Upon receipt of a request to apply ECN the IMS-AGW shall set the ECN field of the IP header in accordance with 3GPP TS 26.114 [21] when sending any data packets. + +Upon receipt of any IP headers indicating ECN Congestion Experienced (ECN-CE) the IMS-AGW shall trigger rate adaptation in accordance with 3GPP TS 26.114 [21]. + +NOTE: ECN endpoint requires the IMS-ALG to configure the IMS-AGW with all media attributes to allow rate adaptation even if no transcoding is required/supported in the IMS-AGW. + +### 6.2.13.4 ECN Failure Indication (ECN endpoint) + +Figure 6.2.13.4.1 shows the message sequence chart example for an ECN Failure Event. + +![Sequence diagram showing the procedure to report ECN failure between IMS-ALG and IMS-AGW.](72d448a65347c51989171748789c7d4b_img.jpg) + +``` + +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + Note right of IMS-AGW: ECN Failure Indication + IMS-AGW->>IMS-ALG: H.248:NOTIFY.req(ECN Failure) +[Termination =x, cause=ecn_cause] + Note left of IMS-ALG: Context(Cx) + IMS-ALG-->>IMS-AGW: H.248:NOTIFY.resp(ECN Failure) +[Termination x] + Note right of IMS-AGW: Context(Cx) + +``` + +The diagram illustrates the interaction between an IMS-ALG and an IMS-AGW to report an ECN failure. It starts with an 'ECN Failure Indication' from the IMS-AGW. The IMS-AGW sends an 'H.248:NOTIFY.req(ECN Failure)' message to the IMS-ALG, with parameters 'Termination =x' and 'cause=ecn\_cause'. The IMS-ALG responds with 'Context(Cx)'. The IMS-ALG then sends an 'H.248:NOTIFY.resp(ECN Failure)' message back to the IMS-AGW, with parameter 'Termination x'. The IMS-AGW receives this response with 'Context(Cx)'. + +Sequence diagram showing the procedure to report ECN failure between IMS-ALG and IMS-AGW. + +**Figure 6.2.13.4.1: Procedure to Report ECN Failure** + +When the IMS-ALG receives a Notification indicating that a failure has occurred, the IMS-ALG may trigger a new SDP offer to disable ECN. + +## 6.2.14 Access Transfer procedures with media anchored in IMS-AGW (ATGW) + +### 6.2.14.1 General + +This clause describes extensions to the Iq signalling procedures and their interactions with SIP signalling in the control plane and with user plane procedures to support the "SRVCC enhanced with ATCF" procedures between the IMS-ALG (ATCF) and IMS-AGW (ATGW) when the IMS-ALG and IMS-AGW support the ATCF and ATGW functionality, as specified in 3GPP TS 23.237 [18] and 3GPP TS 24.237 [19]. + +The Access Transfer procedures are optional to support on the Iq reference point. The requirements in this clause shall apply if these procedures are supported. + +All message sequence charts in this clause are examples. + +### 6.2.14.2 H.248 context model + +Figure 6.2.14.2.1 shows the H.248 context model after the PS originating or terminating session establishment and before the PS to CS access transfer procedure. The "squared" line represents the call control signalling. The "dotted" line represents the bearer. The bearer termination T1 is used for the media path of the PS access leg, the bearer termination T2 is used for the media path of the remote leg. + +![Figure 6.2.14.2.1: H.248 Context Model before Access Transfer. The diagram shows three main components: IMS Access Network (left), IMS CN (right), and IMS-AGW (ATGW) (center). The IMS-AGW (ATGW) contains a box labeled CTX C1 with two terminations, T1 and T2. A solid blue line connects the IMS-ALG (ATCF) to the IMS-AGW (ATGW). A dashed green line connects the IMS Access Network to the IMS-ALG (ATCF). A dashed red line connects the IMS Access Network to the IMS-AGW (ATGW) via termination T1. A dashed red line connects the IMS-AGW (ATGW) via termination T2 to the IMS CN.](3ec35c497a0765a1a885c85f214b1bef_img.jpg) + +Figure 6.2.14.2.1: H.248 Context Model before Access Transfer. The diagram shows three main components: IMS Access Network (left), IMS CN (right), and IMS-AGW (ATGW) (center). The IMS-AGW (ATGW) contains a box labeled CTX C1 with two terminations, T1 and T2. A solid blue line connects the IMS-ALG (ATCF) to the IMS-AGW (ATGW). A dashed green line connects the IMS Access Network to the IMS-ALG (ATCF). A dashed red line connects the IMS Access Network to the IMS-AGW (ATGW) via termination T1. A dashed red line connects the IMS-AGW (ATGW) via termination T2 to the IMS CN. + +**Figure 6.2.14.2.1: H.248 Context Model before Access Transfer** + +Figure 6.2.14.2.2 shows the H.248 context model during the PS to CS access transfer procedure. The IMS-ALG (ATCF) may seize a new bearer termination T3 for the new media path of the CS access leg, e.g. if the PS and CS nodes before and after the handover are reachable via different IP realms or use a different IP version. The IMS-ALG (ATCF) may alternatively reconfigure the T1 termination with the new remote configuration (e.g. IP address and media) instead of seizing a new termination; in that case, the H.248 context model remains as before access transfer. + +Bi-casting is not supported during access transfer, i.e. the IMS-AGW (ATGW) does not duplicate downlink media packets received from the remote leg to the source and target access legs simultaneously. + +![Figure 6.2.14.2.2: H.248 Context Model during Access Transfer. This diagram builds on the previous one by adding a third component: MSC Server / CS MGW (bottom left). A dashed green line connects the MSC Server / CS MGW to the IMS-AGW (ATGW) via a new termination, T3. The other connections remain the same: IMS-ALG (ATCF) to IMS-AGW (ATGW) via a solid blue line, IMS Access Network to IMS-ALG (ATCF) via a dashed green line, IMS Access Network to IMS-AGW (ATGW) via termination T1 (dashed red line), and IMS-AGW (ATGW) via termination T2 to IMS CN (dashed red line).](a9241101d638c568cd5a84ab7ad39f15_img.jpg) + +Figure 6.2.14.2.2: H.248 Context Model during Access Transfer. This diagram builds on the previous one by adding a third component: MSC Server / CS MGW (bottom left). A dashed green line connects the MSC Server / CS MGW to the IMS-AGW (ATGW) via a new termination, T3. The other connections remain the same: IMS-ALG (ATCF) to IMS-AGW (ATGW) via a solid blue line, IMS Access Network to IMS-ALG (ATCF) via a dashed green line, IMS Access Network to IMS-AGW (ATGW) via termination T1 (dashed red line), and IMS-AGW (ATGW) via termination T2 to IMS CN (dashed red line). + +**Figure 6.2.14.2.2: H.248 Context Model during Access Transfer** + +Figure 6.2.14.2.3 shows the H.248 context model after the PS to CS access transfer procedure if the source access leg is released. If the UE chooses to retain some media flow(s) in the transferred-out access, the H.248 context model remains as during access transfer. + +![Diagram of H.248 Context Model after Access Transfer. It shows three main components: MSC Server / CS MGW (left), IMS-ALG (ATCF) (top center), and IMS CN (right). The IMS-ALG (ATCF) is connected to the IMS CN via a dashed green line. Below the IMS-ALG (ATCF) is the IMS-AGW (ATGW), which contains a context box labeled 'CTX C1' with two termination points, T3 and T2. The IMS-AGW (ATGW) is connected to the MSC Server / CS MGW via a dashed red line and to the IMS CN via a dashed red line. A solid blue line connects the IMS-ALG (ATCF) to the IMS-AGW (ATGW).](24ee23a8f3995ecfd3aae31a37a1d40c_img.jpg) + +Diagram of H.248 Context Model after Access Transfer. It shows three main components: MSC Server / CS MGW (left), IMS-ALG (ATCF) (top center), and IMS CN (right). The IMS-ALG (ATCF) is connected to the IMS CN via a dashed green line. Below the IMS-ALG (ATCF) is the IMS-AGW (ATGW), which contains a context box labeled 'CTX C1' with two termination points, T3 and T2. The IMS-AGW (ATGW) is connected to the MSC Server / CS MGW via a dashed red line and to the IMS CN via a dashed red line. A solid blue line connects the IMS-ALG (ATCF) to the IMS-AGW (ATGW). + +**Figure 6.2.14.2.3: H.248 Context Model after Access Transfer** + +### 6.2.14.3 PS session origination or termination with media anchoring in IMS-AGW (ATGW) signaling procedures + +If the IMS-ALG (ATCF) decides to anchor the media of a session in the IMS-AGW (ATGW) the call related procedures shall follow the basic procedures for IMS ALG (i.e. as specified in clause 6.2.1) with the following differences: + +- The IMS-ALG (ATCF) shall seize a termination towards the terminating user, using the "Reserve AGW Connection Point" procedure before sending a SDP offer to the terminating user. The IMS-ALG (ATCF) may signal media related information to the IMS-AGW (ATGW) or omit media when adding the IP termination at this stage. + +NOTE : The signalling of media related information to a MGW requires that it reserve the indicated resources before returning a positive response to the H.248 command, by omitting media related information the IMS-AGW (ATGW) does not need to reserve any associated resources at this stage. + +- When the IMS-ALG (ATCF) receives the SDP answer from the terminating user, the IMS-ALG (ATCF) shall configure the IMS-AGW (ATGW) accordingly by either supplying the same media related information for all interconnected terminations or by omitting the media related information. + +![Sequence diagram showing PS session establishment with media anchoring in IMS-AGW (ATGW).](b13465efdac63129aef9b6f1787d0d00_img.jpg) + +``` + +sequenceDiagram + participant ExtL as External (Left) + participant ALG as IMS-ALG (ATCF) + participant AGW as IMS-AGW (ATGW) + participant ExtR as External (Right) + + Note over ALG: Reserve AGW Connection Point, (Change Through-Connection) + ExtL-->>ALG: 1. SDP offer (IP1o, P1o, codec1, codec2) + ALG->>AGW: 2. H.248 ADD req (C=?, T=?, LAddr=?, LPort=?, Local Resources="-" or codec1 or codec2) + Note right of AGW: 3. Create outgoing termination T2 + AGW->>ALG: 4. H.248 ADD resp. (C=C1, T=T2, LAddr=IP2o, LPort=P2o) + + Note over ALG: 5. Modify SDP offer + ALG-->>ExtR: 6. SDP offer (IP2o, P2o, codec 1, codec 2) + + Note over ALG: Configure AGW Connection Point, (Change Through-Connection) + ExtR-->>ALG: 7. SDP answer (IP1a, P1a, codec 1) + ALG->>AGW: 8. H.248 MOD req (C=C1, T=T2, RAddr=IP1a, RPort=P1a, Local Resources="-" or codec1, Remote Resources="-" or codec1) + Note right of AGW: 9. Configure Outgoing Termination T2 + AGW->>ALG: 10. H.248 MOD Resp (C=C1, T=T2) + + Note over ALG: Reserve And Configure AGW Connection Point, (Change Through-Connection) + ALG->>AGW: 11. H.248 ADD req (C=C1, T=?, LAddr=?, LPort=?, RAddr=IP1o, RPort=P1o, Local Resources="-" or codec1, Remote Resources="-" or codec1) + Note right of AGW: 12. Create incoming Termination T1 + AGW->>ALG: 13. H.248 ADD Resp (C=C1, T=T1, LAddr=IP2a, LPort=P2a, RAddr=IP1o, RPort=P1o) + + Note over ALG: 14. Modify SDP answer + ALG-->>ExtL: 15. SDP answer (Ip2a, P2a, codec 1) + +``` + +The sequence diagram illustrates the PS session establishment with media anchoring in IMS-AGW (ATGW). The interaction between IMS-ALG (ATCF) and IMS-AGW (ATGW) is as follows: + +1. SDP offer (IP1o, P1o, *codec1, codec2*) is received by IMS-ALG. +2. IMS-ALG sends an H.248 ADD req to IMS-AGW with parameters: C=?, T=?, LAddr=?, LPort=?, Local Resources="-" or *codec1* or *codec2*. +3. IMS-AGW creates an outgoing termination T2. +4. IMS-AGW sends an H.248 ADD resp to IMS-ALG with parameters: (C=C1, T=T2, LAddr=IP2o, LPort=P2o). +5. IMS-ALG modifies the SDP offer. +6. IMS-ALG sends an SDP offer (IP2o, P2o, *codec 1, codec 2*) to the network. +7. IMS-ALG receives an SDP answer (IP1a, P1a, *codec 1*). +8. IMS-ALG sends an H.248 MOD req to IMS-AGW with parameters: (C=C1, T=T2, RAddr=IP1a, RPort=P1a, Local Resources="-" or *codec1*, Remote Resources="-" or *codec1*). +9. IMS-AGW configures the outgoing termination T2. +10. IMS-AGW sends an H.248 MOD Resp to IMS-ALG with parameters: C=C1, T=T2. +11. IMS-ALG sends an H.248 ADD req to IMS-AGW with parameters: C=C1, T=?, LAddr=?, LPort=?, RAddr=IP1o, RPort=P1o, Local Resources="-" or *codec1*, Remote Resources="-" or *codec1*. +12. IMS-AGW creates an incoming termination T1. +13. IMS-AGW sends an H.248 ADD Resp to IMS-ALG with parameters: C=C1, T=T1, LAddr=IP2a, LPort=P2a, RAddr=IP1o, RPort=P1o. +14. IMS-ALG modifies the SDP answer. +15. IMS-ALG sends an SDP answer (Ip2a, P2a, *codec 1*) back to the originator. + +Brackets on the left side of the diagram indicate the following high-level procedures: + +- Reserve AGW Connection Point, (Change Through-Connection)**: Encompasses steps 1 through 4. +- Configure AGW Connection Point, (Change Through-Connection)**: Encompasses steps 7 through 10. +- Reserve And Configure AGW Connection Point, (Change Through-Connection)**: Encompasses steps 11 through 13. + +Sequence diagram showing PS session establishment with media anchoring in IMS-AGW (ATGW). + +**Figure 6.2.14.3.1: PS session establishment with media anchoring in IMS-AGW (ATGW)** + +1. The IMS-ALG (ATCF) receives an SDP offer in SIP signalling. The IMS-ALG (ATCF) requires an IMS-AGW (ATGW) for media anchoring (or for another IMS-AGW use case) but does not offer transcoding. +2. The IMS-ALG (ATCF) sends a H.248 ADD request command to create the outgoing termination and to request IP resources to execute ATGW function. As no media transcoding is required this may be indicated by signalling "-". Alternatively any codec (e.g. Codec 1) can be signalled. If the IMS-ALG (ATCF) selects an IMS-AGW (ATGW) that does not support transcoding, the IMS-ALG (ATCF) may signal media related sub-fields in the media descriptor to the IMS-AGW (ATGW) if the IMS-AGW (ATGW) supports media encoding. The IMS-AGW (ATGW) shall accept the ADD request even though it cannot reserve any transcoding resources for the indicated media. +3. The IMS-AGW (ATGW) creates the outgoing termination. +4. The IMS-AGW (ATGW) replies to IMS-ALG (ATCF) with a H.248 ADD reply command and provides the local address and port of the outgoing termination. +5. The IMS-ALG (ATCF) replaces the IP address inside the SDP using the information coming from IMS-AGW (ATGW). +6. The IMS-ALG (ATCF) forwards the new offer to the succeeding node. +7. The SDP answer is received by IMS-ALG (ATCF). In this example the codec1 received in the original SDP offer in step1 has been selected. +8. The IMS-ALG (ATCF) sends a H.248 MOD request command to configure the outgoing termination with address and port information. As no media transcoding is needed this may be indicated by signalling "-". Alternatively the selected codec (Codec 1) can be signalled. +9. The IMS-AGW (ATGW) configures the outgoing termination. +10. The IMS-AGW (ATGW) replies to IMS-ALG (ATCF) with a H.248 MOD reply command. +11. The IMS-ALG (ATCF) sends a H.248 ADD command to create the incoming termination to configure this termination with remote address and port information and to request resources to execute ATGW function. As no media transcoding is needed this may be indicated by signalling "-". Alternatively media related sub-fields in the media descriptor for the codec indicated to the incoming termination may be signalled (e.g. the selected codec received in step 7 (Codec 1)). +12. The IMS-AGW (ATGW) creates the incoming termination. +13. The IMS-AGW (ATGW) replies to the IMS-ALG (ATCF) with a H.248 ADD reply command and provides the local address and port of the incoming termination. +14. The IMS-ALG (ATCF) replaces the IP address inside the SDP answer using the information coming from IMS-AGW (ATGW). +15. SDP answer is sent to the network at the incoming side. + +Similar principles shall apply during the establishment of a mobile terminating session. + +#### 6.2.14.4 PS to CS Access Transfer procedure with media anchored in IMS-AGW (ATGW) + +The signalling flow shown in figure 6.2.14.4.1 gives an example for PS to CS access transfer with media anchored in the IMS-AGW (ATGW). In this case, the media has been anchored in IMS-AGW (ATGW) as specified in clause 6.2.14.3. + +![Sequence diagram showing PS to CS Access Transfer with transcoding in IMS-AGW (ATGW). The diagram illustrates the interaction between IMS-ALG (ATCF) and IMS-AGW (ATGW) for media transfer. The process involves an SDP offer, H.248 ADD request, creation of a new termination T3, H.248 ADD response, SDP answer, BYE request, H.248 SUB request, release of the old termination T1, and H.248 SUB response. A bracket on the left indicates the 'Reserve And Configure AGW Connection Point, (Change Through-Connection, Change Flow Direction)' phase.](921f8fa0f7ce2c9956f20d33162c13a2_img.jpg) + +``` + +sequenceDiagram + participant MSC Server + participant IMS-ALG as IMS-ALG (ATCF) + participant IMS-AGW as IMS-AGW (ATGW) + + Note left of IMS-ALG: Reserve And Configure AGW Connection Point, (Change Through-Connection, Change Flow Direction) + + MSC Server->>IMS-ALG: 1. SDP offer (IP1o, P1o, codec3, codec4) + IMS-ALG->>IMS-AGW: 2. TopDesc({T1,*,isolate},{T2,$,bothway}) H.248 ADD req +C= C1, T= ?, LAddr=?, LPort=?, Local Resources= codec3 + IMS-AGW->>IMS-ALG: 3. Create incoming termination T3 and applying transcoding between T3 and T2 if necessary + IMS-AGW->>IMS-ALG: 4. TopDesc() H.248 ADD resp. +(C=C1, T=T3, LAddr=IP3o, LPort=P3o) + IMS-ALG->>MSC Server: 5. SDP answer(IP3a, P3a, codec 3) + MSC Server->>IMS-ALG: 6. BYE (Dialog for source access leg) + IMS-ALG->>IMS-AGW: 7. H.248 SUB req +C= C1, T=T1) + IMS-AGW->>IMS-ALG: 8. Release incoming termination T1 + IMS-AGW->>IMS-ALG: 9. H.248 SUB resp. +(C=C1, T=T1) + +``` + +Sequence diagram showing PS to CS Access Transfer with transcoding in IMS-AGW (ATGW). The diagram illustrates the interaction between IMS-ALG (ATCF) and IMS-AGW (ATGW) for media transfer. The process involves an SDP offer, H.248 ADD request, creation of a new termination T3, H.248 ADD response, SDP answer, BYE request, H.248 SUB request, release of the old termination T1, and H.248 SUB response. A bracket on the left indicates the 'Reserve And Configure AGW Connection Point, (Change Through-Connection, Change Flow Direction)' phase. + +- The IMS-ALG (ATCF) receives an SDP offer in SIP signalling from the MSC Server. The IMS-ALG (ATCF) checks whether transcoding is required. 2. The IMS-ALG (ATCF) sends a H.248 ADD request command to create the target access leg termination and to request IP resources to execute ATGW function. Topology is changed and media reconfigured to connect media between T2 and T3. +If no media transcoding is required this may be indicated by signalling "-" or by signalling the same media information on T3 as is configured on T2, following the principles specified in clause 6.2.14.3. +If media transcoding is required (as illustrated in this example), the IMS-ALG (ATCF) signals media related sub-fields in the media descriptor to the IMS-AGW (ATGW). The IMS-AGW (ATGW) determines from the media configuration whether transcoding is required on a stream between two terminations between which data flow is permitted. +- The IMS-AGW (ATGW) creates the target access leg termination T3 and starts to apply transcoding between T2 and T3 (if required). +- The IMS-AGW (ATGW) replies to IMS-ALG (ATCF) with a H.248 ADD reply command and provides the local address and port of the outgoing termination. +- The IMS-ALG (ATCF) returns an SDP answer to the MSC Server; the IP address inside the SDP uses the information coming from IMS-AGW (ATGW). +- Upon successful completion of the access transfer procedure, the IMS-ALG (ATCF) receives a BYE request from the SCC AS if there is no more media flows on the PS access. +- The IMS-ALG (ATCF) sends a H.248 SUB request command to subtract the source access leg termination. +- The IMS-AGW (ATGW) releases the source access leg termination. +- The IMS-AGW (ATGW) replies to IMS-ALG (ATCF) with a H.248 SUB reply command. + +Figure 6.2.14.4.1: PS to CS Access Transfer with transcoding in IMS-AGW (ATGW) + +## 6.2.14.5 ECN support during PS to CS Access Transfer procedure with media anchored in IMS-AGW (ATGW) + +The signalling flow shown in figure 6.2.14.4.1 gives an example for PS to CS access transfer with media anchored in the IMS-AGW (ATGW). The following additional actions are required if ECN is supported by the IMS-ALG/IMS-AGW: + +1. + - a) If ECN was supported during the PS session transparently and the SDP offer received from the MSC Server does not indicate ECN support, it is not possible to maintain transparent ECN support to the IMS CN. The IMS-ALG (ATCF) shall modify the Termination T2 to act as an ECN endpoint toward the IMS CN (see Clause 5.12). Additionally the IMS-ALG (ATCF) shall disable ECN on the termination T3 (or T1). + - b) If ECN was supported during the PS session transparently and the SDP offer received from the MSC Server does indicate ECN support and no transcoding is required (codec types and modes are aligned between ICS side and IMS CN), then the IMS-ALG (ATCF) shall request ECN transparent properties when seizing T3 and respond to the MSC Server with ECN supported in the SDP answer (step 5). + - c) If ECN was supported during the PS session transparently and the SDP offer received from the MSC Server does indicate ECN support and transcoding is required between the CS leg and the IMS-CN, then the IMS-ALG (ATCF) shall request ECN endpoint properties when seizing T3 (or modify the termination T1 with ECN endpoint properties) and respond to the MSC Server with ECN supported in the SDP answer (step 5). Additionally the IMS-ALG (ATCF) shall modify the Termination T2 to act as an ECN endpoint toward the IMS CN (see Clause 5.12). + - d) If ECN was not supported during the PS session and the SDP Offer received from the MSC Server indicates ECN support, the IMS-ALG (ATCF) shall not accept ECN support in the SDP answer (step 5). + +## 6.2.14.6 Support of generic image attributes + +### 6.2.14.6.1 General + +The IMS-ALG (ATCF) and the IMS-AGW (ATGW) may support a media-level SDP image attribute "a=imageattr" defined in IETF RFC 6236 [24] to negotiate the image size for sending and receiving video. + +The list of image sizes per payload type supported by the IMS-AGW (ATGW) shall be preconfigured in the IMS-ALG (ATCF). If the image sizes received within an SDP body on the Mw/Mx interface are not all supported by the IMS-AGW (ATGW) then the IMS-ALG (ATCF) shall only send the list of corresponding IMS-AGW (ATGW) supported image sizes to the IMS-AGW (ATGW). If no image size is supported by the IMS-AGW (ATGW), the IMS-ALG (ATCF) shall not send the generic image attribute parameter to the IMS-AGW (ATGW). + +The signalling flow shown in figure 6.2.14.3.1 gives an example for a PS session establishment with media anchored in the IMS-AGW (ATGW). The following additional actions may be performed if the negotiation of the image size is supported by the IMS-ALG/IMS-AGW: + +- a) upon receipt of an SDP offer containing the image attribute(s) and if the received image sizes are supported by the IMS-AGW (ATGW) then the IMS-ALG (ATCF) may send the generic image attribute parameters for the send and receive directions to the IMS-ALG (ATCF) (step 2 or step 8) when seizing or modifying an outgoing termination; + +NOTE 1: If the offered image attributes are not supported by the IMS-AGW (ATGW) then the IMS-ALG (ATCF) will not send the generic image attribute parameter to the IMS-AGW (ATGW). + +- b) the IMS-ALG (ATCF) shall include the SDP image attribute(s) "a=imageattr" indicating the supported image sizes in the modified SDP offer (step 5); +- c) upon receipt of an SDP answer containing the generic image attribute(s) and if the received image sizes are supported by the IMS-AGW (ATGW) then the IMS-ALG (ATCF) may include the generic image attribute parameter to the IMS-AGW (ATGW) (step 11) when seizing an incoming termination; and +- d) the IMS-ALG (ATCF) shall include the SDP image attribute(s) "a=imageattr" indicating the supported image sizes in the modified SDP answer (step 14). + +NOTE 2: The IMS-ALG (ATCF) not supporting the negotiation of generic image attributes will ignore the SDP image attribute received in the SDP offer and will send the SDP offer/answer without any associated SDP image attribute. + +When sending the SDP body with image attribute(s) on the Mw/Mx interface the IMS-ALG (ATCF) shall include in the "a=imageattr": + +- "recv" keyword and corresponding image sizes which the IMS-AGW (ATGW) supports in the receiving direction; and + +- "send" keyword and corresponding image sizes which the IMS-AGW (ATGW) supports in the sending direction. + +The signalling flow shown in figure 6.2.14.4.1 gives an example for PS to CS access transfer with media anchored in the IMS-AGW (ATGW). The following additional actions may be performed if the negotiation of the image size is supported by the IMS-ALG/IMS-AGW: + +- if the image sizes were negotiated during the PS session and if the IMS-AGW (ATGW) applies the video transcoding (step 3) and if the IMS-AGW (ATGW) is configured with different image sizes on the receive direction of one termination and the send direction of another interconnected termination, then it shall adjust the frame sizes accordingly when forwarding video media streams and use the image size as described in 3GPP TS 26.114 [21] when sending media. + +NOTE 3: The relation between the negotiated image sizes and CVO are specified in 3GPP TS 26.114 [21]. + +NOTE 4: The generic image attribute includes information related to the send and receive capabilities of a single termination, and the adjustment of image sizes is typically based on the setting of two connected terminations in a single context. + +#### 6.2.14.6.2 Indication of generic image attributes + +The IMS-ALG (ATCF) may include the generic image attributes to the IMS-AGW (ATGW). The example sequence is shown in figure 6.2.14.6.2.1. + +![Sequence diagram showing the interaction between IMS-ALG (ATCF) and IMS-AGW (ATGW) to reserve an AGW connection point with generic image attributes.](288220dc8e18b23fc8f294cf1ca909b4_img.jpg) + +``` + +sequenceDiagram + participant External + participant IMS-ALG as IMS-ALG (ATCF) + participant IMS-AGW as IMS-AGW (ATGW) + + External->>IMS-ALG: SIP msg with SDP offer ["imageattr:" ...] + IMS-ALG->>IMS-AGW: H.248: ADD Req [C=?, T= ?, Laddr = ?, Lport = ?, Local Resources, Generic Image Attribute] + IMS-AGW-->>IMS-ALG: H.248: ADD Resp [Termination X ... ] + IMS-ALG->>External: SIP msg with SDP answer ["imageattr:" ...] + + Note right of IMS-AGW: IMS-AGW(ATGW) receives generic image attribute to be used when transcoding video. + +``` + +The diagram illustrates the following sequence of messages: + +- An external entity sends a **SIP msg with SDP offer ["imageattr:" ...]** to the **IMS-ALG (ATCF)**. +- The **IMS-ALG (ATCF)** sends a **H.248: ADD Req [C=?, T= ?, Laddr = ?, Lport = ?, Local Resources, Generic Image Attribute]** to the **IMS-AGW (ATGW)**. +- The **IMS-AGW (ATGW)** sends a **H.248: ADD Resp [Termination X ... ]** back to the **IMS-ALG (ATCF)**. +- The **IMS-ALG (ATCF)** sends a **SIP msg with SDP answer ["imageattr:" ...]** back to the external entity. + +A note on the right side of the diagram indicates: **IMS-AGW(ATGW) receives generic image attribute to be used when transcoding video.** + +Sequence diagram showing the interaction between IMS-ALG (ATCF) and IMS-AGW (ATGW) to reserve an AGW connection point with generic image attributes. + +Figure 6.2.14.6.2.1: Request to reserve AGW connection point with generic image attribute + +#### 6.2.14.7 Handling of common codec parameters + +For PS session origination, figure 6.2.14.3.1 shall apply with the handling of codec related parameters applicable to multiple codecs in table 6.2.14.7.1, assuming that codec related information is signalled to the IMS-AGW(ATGW) at this stage. If no codec related information is signalled to the IMS-AGW at this stage, the common codec related parameters for the termination towards the SDP answerer in table 6.2.14.7.1 shall be signalled towards the IMS-AGW during a PS to CS Access Transfer procedure. + +**Table 6.2.14.7.1: IMS-ALG handling of common codec related SDP parameters during PS session origination.** + +| Parameter | Handling in SDP offer | Handling in the SDP answer | +|-------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ptime
(NOTE) | If the ptime parameter is included in the received SDP offer, the IMS-ALG shall supply the parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. If the value is supported by the IMS-AGW for receiving media, the IMS-ALG should keep the value from the received SDP offer unchanged in the SDP offer it sends. If the IMS-AGW only supports a lower ptime value, the IMS-ALG shall supply the ptime value according to configured preferences in the SDP offer it forwards. If no ptime value was contained in the received SDP offer, the IMS-ALG may add the parameter with a value according to configured preferences to the SDP offer. | If the ptime parameter is included in the received SDP answer, the IMS-ALG shall supply the parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor. If the value is supported by the IMS-AGW for receiving media, the IMS-ALG should keep the value from the received SDP answer unchanged in the SDP answer it sends. If the IMS-AGW only supports a lower ptime value, the IMS-ALG shall supply the ptime value according to configured preferences in the SDP answer it forwards. If no ptime value was contained in the received SDP answer, the IMS-ALG may add the parameter with a value according to configured preferences to the SDP answer. | +| maxptime
(NOTE) | If the maxptime parameter is included in the received SDP offer, the IMS-ALG shall supply the parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. If the value is supported by the IMS-AGW for receiving media, the IMS-ALG should keep the value from the received SDP offer unchanged in the SDP offer it sends. If the IMS-AGW only supports a lower maxptime value, the IMS-ALG shall supply the maxptime value according to the IMS-AGW capabilities in the SDP offer it forwards. If no maxptime value was contained in the received SDP offer, the IMS-ALG may add the parameter with a value according to the IMS-AGW capabilities to the SDP offer. | If the maxptime parameter is included in the received SDP answer, the IMS-ALG shall supply the parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor. If the value is supported by the IMS-AGW for receiving media, the IMS-ALG should keep the value from the received SDP answer unchanged in the SDP answer it sends. If the IMS-AGW only supports a lower maxptime value, the IMS-ALG shall supply the maxptime value according to the IMS-AGW capabilities in the SDP answer it forwards. If no maxptime value was contained in the received SDP answer, the IMS-ALG may add the parameter with a value according to the IMS-AGW capabilities to the SDP answer. | +| NOTE: This SDP attribute is defined in IETF RFC 4566 [53]. It applies to all codecs offered in an SDP media line. | | | + +For PS to CS Access Transfer, figure 6.2.14.4.1 shall apply with the handling of codec related parameters applicable to multiple codecs in in table 6.2.14.A.2. + +**Table 6.2.14.7.2: IMS-ALG handling of common codec related SDP parameters during PS to CS Access Transfer.** + +| Parameter | Handling of common codec parameters received in the SDP offer | Common Codec parameters supplied in the SDP answer | +|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------| +| ptime
(NOTE) | If the ptime parameter is included in the received SDP offer, the IMS-ALG shall supply the parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | The IMS-ALG may add the parameter with a value according to configured preferences to the SDP answer. | +| maxptime
(NOTE) | If the maxptime parameter is included in the received SDP offer, the IMS-ALG shall supply the parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | The IMS-ALG may add the parameter with a value according to the IMS-AGW capabilities to the SDP answer. | +| NOTE: This SDP attribute is defined in IETF RFC 4566 [53]. It applies to all codecs offered in an SDP media line. | | | + +## 6.2.14.8 EVS speech codec support + +For PS session origination, figure 6.2.14.3.1 shall apply with the EVS parameter handling in table 6.2.14.8.1, assuming that EVS is "codec 1", which is selected, and that "codec 1" related information is signalled to the IMS-AGW(ATGW) at this stage. If no codec related information is signalled to the IMS-AGW at this stage, the EVS related parameters for the termination towards the SDP answerer in table 6.2.14.8.1 shall be signalled towards the IMS-AGW during a PS to CS Access Transfer procedure. + +Table 6.2.14.8.1: IMS-ALG handling of EVS related SDP parameters during PS session origination. + +| Parameter | Handling for EVS payload type in SDP offer | Handling if offered EVS payload type is accepted in the SDP answer | +|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| evs-mode-switch
(NOTE 1) | If the evs-mode-switch parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer and shall retain the parameter in the SDP offer it forwards. | If the evs-mode-switch parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor, and the IMS-ALG shall retain this parameter in the SDP answer it forwards. | +| hf-only
(NOTE 1) | If the n hf-only parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer and shall retain the parameter in the SDP offer it forwards.
Otherwise, if the IMS-ALG is configured to negotiate using only the header-full EVS RTP payload format, the IMS-ALG shall provide the hf-only parameter with a value 1 to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer, and within the SDP offer it forwards. | If the hf-only parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards. | +| dtx
(NOTE 1) | If the dtx parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer and shall retain the parameter in the SDP offer it forwards.
Otherwise, if the dtx-recv parameter is contained in the SDP offer, the IMS-ALG may include the dtx parameter in the SDP offer it forwards with the same value as the dtx-recv parameter in the SDP offer.
Otherwise, if the usage of DTX is not desired in the sending and receiving direction, the IMS-ALG shall include the dtx parameter with a value 0 to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer, and within the SDP offer it forwards. | If the dtx parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards. | +| dtx-recv
(NOTE 1) | If the dtx-recv parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer and shall retain the parameter in the SDP offer it forwards.
Otherwise, if the reception of DTX is not desired and the dtx parameter is not included in the forwarded SDP offer, the IMS-ALG shall include the dtx-recv parameter with a value 0 to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer, and within the SDP offer it forwards.
If both the dtx and dtx-recv parameters are included, those parameters shall have the same value; however, inclusion of the dtx-recv parameter is not required if the dtx parameter is included. | If the dtx-recv parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards. | +| br
(NOTE 1) | If the br parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated bitrates, or a subset of them, in EVS primary mode in the send and receive direction. If the indicated bitrates, and even each subset of them, are not supported, the IMS-ALG should remove the EVS payload from the SDP offer.
Otherwise, If the br parameter is contained in the SDP offer, the IMS-ALG shall select a bitrate value, which is either the received br value or a subset of it, based on IMS-AGW capabilities and | If the br parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards. | + +| | | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

possible configured policies, and shall include that br parameter with the selected value in the SDP offer if forwards.

Otherwise, if the IMS-ALG desires the same bit rate range for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range to match IMS-AGW capabilities and possible configured policies, it shall supply the br parameter in the SDP offer it sends.

If the IMS-ALG also supplies the bw, bw-send or bw-recv parameter, the value of the br parameter shall be compatible with the values of those parameters.

If the IMS-ALG supplies the br parameter in the SDP offer if forwards, it shall also supply to the IMS-AGW the br parameter in the local descriptor for the termination towards the offerer with the same value.

| | +| br-send
(NOTE 1) |

If the br-send parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated bitrates, or a subset of them, in EVS primary mode in the send and receive direction. If the indicated bitrates, and even each subset of them, are not supported, the IMS-ALG should remove the EVS payload from the SDP offer.

Otherwise, If the br-send parameter is contained in the SDP offer, the IMS-ALG shall select a bitrate value, which is either the received br-send value or a subset of it, based on IMS-AGW capabilities and possible configured policies, and shall include that br-send parameter with the selected value in the SDP offer if forwards.

Otherwise, if the IMS-ALG desires a different bit rate (range) for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range for the send direction towards the offerer to match IMS-AGW capabilities and possible configured policies, it shall supply the br-send parameter in the SDP offer it sends.

Otherwise the IMS-ALG shall not include this parameter in the SDP offer.

If the IMS-ALG also supplies the bw or bw-send parameter, the value of the br-send parameter shall be compatible with the values of those parameters.

If the IMS-ALG supplies the br-send parameter in the SDP offer if forwards, it shall also supply to the IMS-AGW the br-send parameter in the local descriptor for the termination towards the offerer with the same value.

|

If the br-send parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards.

| +| br-recv
(NOTE 1) |

If the br-recv parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated bitrates, or a subset of them, in EVS primary mode in the send and receive direction. If the indicated bitrates, and even each subset of them, are not supported, the IMS-ALG should remove the EVS payload from the SDP offer.

Otherwise, If the br-recv parameter is contained in the SDP offer, the IMS-ALG shall select a bitrate value, which is either the received br-recv value or a subset of it, based on IMS-AGW capabilities and possible configured policies, and shall include that br-recv parameter with the selected value in the SDP offer if forwards.

Otherwise, if the IMS-ALG desires a different bit rate (range) for the send and receive direction in

|

If the br-recv parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards.

| + +| | | | +|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

EVS primary mode, and wants to restrict the bit rate range for the recv direction towards the offerer to match IMS-AGW capabilities and possible configured policies, it shall supply the br-recv parameter in the SDP offer it sends. Otherwise the IMS-ALG shall not include this parameter in the SDP offer.

If the IMS-ALG also supplies the bw or bw-recv parameter, the value of the br-recv parameter shall be compatible with the values of those parameters.

If the IMS-ALG supplies the br-recv parameter in the SDP offer if forwards, it shall also supply to the IMS-AGW the br-recv parameter in the local descriptor for the termination towards the offerer with the same value.

| | +| bw
(NOTE 1) |

If the bw parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated sampling bandwidth(s), or a subset of them, in EVS primary mode in the send and receive direction. If the indicated sampling bandwidth(s), and even each subset of them, are not supported, the IMS-ALG should remove the EVS payload from the SDP offer. Otherwise, If the bw parameter is contained in the SDP offer, the IMS-ALG shall select a bitrate value, which is either the received bw value or a subset of it, based on IMS-AGW capabilities and possible configured policies, and shall include that bw parameter with the selected value in the SDP offer if forwards.

Otherwise, if the IMS-ALG desires the same sampling bandwidth(s) for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidth(s) to match IMS-AGW capabilities and possible configured policies, it shall supply the bw parameter in the SDP offer it sends.

If the IMS-ALG also supplies the br, br-send or br-recv parameter, the value of the bw parameter shall be compatible with the values of those parameters.

If the IMS-ALG supplies the bw parameter in the SDP offer if forwards, it shall also supply to the IMS-AGW the bw parameter in the local descriptor for the termination towards the offerer with the same value.

|

If the bw parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards.

| +| bw-send
(NOTE 1) |

If the bw-send parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated sampling bandwidth(s), or a subset of them, in EVS primary mode in the send and receive direction. If the indicated bitrates, and even each subset of them, are not supported, the IMS-ALG should remove the EVS payload from the SDP offer. Otherwise, If the bw-send parameter is contained in the SDP offer, the IMS-ALG shall select a sampling bandwidth value, which is either the received bw-send value or a subset of it, based on IMS-AGW capabilities and possible configured policies, and shall include that bw-send parameter with the selected value in the SDP offer if forwards.

Otherwise, if the IMS-ALG desires different sampling bandwidth(s) for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidth(s) for the send direction towards the offerer to match IMS-AGW

|

If the bw-send parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards.

| + +| | | | +|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| |

capabilities and possible configured policies, it shall supply the bw-send parameter in the SDP offer it sends. Otherwise the IMS-ALG shall not include this parameter in the SDP offer.

If the IMS-ALG also supplies the br or br-send parameter, the value of the bw-send parameter shall be compatible with the values of those parameters.

If the IMS-ALG supplies the bw-send parameter in the SDP offer it forwards, it shall also supply to the IMS-AGW the bw-send parameter in the local descriptor for the termination towards the offerer with the same value.

| | +| bw-recv
(NOTE 1) |

If the bw-recv parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated sampling bandwidth(s), or a subset of them, in EVS primary mode in the send and receive direction. If the indicated sampling bandwidth(s), and even each subset of them, are not supported, the IMS-ALG should remove the EVS payload from the SDP offer. Otherwise, If the bw-recv parameter is contained in the SDP offer, the IMS-ALG shall select a sampling bandwidth(s) value, which is either the received bw-recv value or a subset of it, based on IMS-AGW capabilities and possible configured policies, and shall include that bw-recv parameter with the selected value in the SDP offer it forwards.

Otherwise, if the IMS-ALG desires different sampling bandwidth(s) for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidth(s) for the recv direction towards the offerer to match IMS-AGW capabilities and possible configured policies, it shall supply the bw-recv parameter in the SDP offer it sends. Otherwise the IMS-ALG shall not include this parameter in the SDP offer.

If the IMS-ALG also supplies the br or br-recv parameter, the value of the bw-recv parameter shall be compatible with the values of those parameters.

If the IMS-ALG supplies the bw-recv parameter in the SDP offer it forwards, it shall also supply to the IMS-AGW the bw-recv parameter in the local descriptor for the termination towards the offerer with the same value.

|

If the bw-recv parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards.

| +| cmr
(NOTE 1) |

If the cmr parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer and shall retain the parameter in the SDP offer it forwards. Otherwise, if the IMS-ALG desires to disable codec mode requests within the RTP payload of the EVS primary mode (due to the IMS-AGW capabilities or policies), it shall include the cmr parameter with value -1 to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer, and within the SDP offer it forwards.

|

If the cmr parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards.

| +| ch-aw-recv
(NOTE 1) |

If the ch-aw-recv parameter is contained in the SDP offer the IMS-ALG shall check if the IMS-AGW supports the indicated mode in the send direction. If the indicated mode is not supported, the IMS-ALG shall remove the payload type from the SDP offer. If the IMS-AGW supports the indicated mode in the send direction for transcoding, the IMS-ALG shall forward this

|

If the ch-aw-recv parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards.

| + +| | | | +|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor, and shall include the unmodified parameter within the SDP offer it forwards. Otherwise, if the IMS-ALG desires to disable partial redundancy mode, it shall include the ch-aw-send parameter with value -1 in the SDP offer it forwards. | | +| number of channels (NOTE 2) | If the "number of channels" parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated number of channels. If the indicated number of channels is not supported, the IMS-ALG should remove the EVS payload from the SDP offer. Otherwise, if the "number of channels" parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor and shall retain the parameter in the SDP offer it forwards. | If the "number of channels" parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards. | +| ch-send (NOTE 1) | If the ch-send parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated number of channels in the send and receive direction. If the indicated number of channels is not supported, the IMS-ALG should remove the EVS payload from the SDP offer. Otherwise, if the ch-send parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor and shall retain the parameter in the SDP offer it forwards. | If the ch-send parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards. | +| ch-recv (NOTE 1) | If the ch-recv parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated number of channels in the send and receive direction. If the indicated number of channels is not supported, the IMS-ALG should remove the EVS payload from the SDP offer. Otherwise, if the ch-recv parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor and shall retain the parameter in the SDP offer it forwards. | If the ch-recv parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the answerer, and the IMS-ALG shall retain this parameter in the SDP answer it forwards. | +| mode-set (NOTE 3) | If the mode-set parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer and shall retain the parameter in the SDP offer it forwards. | If the mode-set parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor, and the IMS-ALG shall retain this parameter in the SDP answer it forwards. | +| mode-change-period (NOTE 3) | If the mode-change-period parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer and shall retain the parameter in the SDP offer it forwards. | If the mode-change-period parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor, and the IMS-ALG shall retain this parameter in the SDP answer it forwards. | +| mode-change-capability (NOTE 3) | If the mode-change-capability parameter is contained in the SDP offer, the IMS-ALG may forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer and shall retain the parameter in the SDP offer it forwards. | If the mode-change-capability parameter is contained in the SDP answer, the IMS-ALG may forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor, and the IMS-ALG shall retain this parameter in the SDP answer it forwards. | +| mode-change-neighbor (NOTE 3) | If the mode-change-neighbor parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer and shall retain the parameter in the SDP offer it forwards. | If the mode-change-neighbor parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor, and the IMS-ALG shall retain this parameter in the SDP answer it forwards. | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | SDP offer it forwards. | parameter in the SDP answer it forwards. | +| max-red
(NOTE 5) | If the max-red parameter is contained in the SDP offer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor for the termination towards the SDP offerer and shall retain the parameter in the SDP offer it forwards with a value that considers the received value and the capabilities of the IMS-AGW. | If the max-red parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the answerer in the remote descriptor, and the IMS-ALG shall retain this parameter in the SDP answer it forwards with a value that considers the received value and the capabilities of the IMS-AGW. | +| 3gpp_mtsi_app_adapt
(NOTE 4) | If the IMS-AGW supports RTCP APP based adaptation messages defined in 3GPP TS 26.114 [21], and the IMS-ALG has a policy to negotiate the usage of those messages, the IMS-ALG shall include the 3gpp_mtsi_app_adapt SDP attribute indicating the supported APP messages in the SDP offer. | If the 3gpp_mtsi_app_adapt parameter is contained in the SDP answer, the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | +| NOTE 1: This MIME parameter of the EVS RTP payload type is defined in 3GPP TS 26.445 [51]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [53].
NOTE 2: This number of channels are encoded as "encoding parameters" of the SDP "a=rtpmap" attribute defined in IETF RFC 4566 [53].
NOTE 3: This MIME parameter of the EVS RTP payload type relates to AMR-WB IO mode and is defined in IETF RFC 4867 [54]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [53].
NOTE 4: This SDP attribute is defined in 3GPP TS 26.114 [21]. It applies to all codecs offered in an SDP media line. However, some values are specific to EVS.
NOTE 5: This MIME parameter of the EVS RTP payload type is defined in IETF RFC 4867 [54]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [53]. | | | + +For PS to CS Access Transfer, figure 6.2.14.4.1 shall apply with the EVS parameter handling in table 6.2.14.8.2, assuming that EVS is "codec 3", which is selected. + +Table 6.2.14.8.2: IMS-ALG handling of EVS related SDP parameters during PS to CS Access Transfer. + +| Parameter | Handling of EVS payload type parameter received in the SDP offer | EVS payload type supplied in the SDP answer | +|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| evs-mode-switch
(NOTE 1) | If the evs-mode-switch parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the evs-mode-switch parameter is contained in the SDP offer, the IMS-ALG shall include the evs-mode-switch parameter with unmodified value in the SDP answer.
Otherwise, if EVS was used before the access transfer, the IMS-ALG should include the evs-mode-switch parameter with a value indicating the mode that was negotiated before the access transfer.
Otherwise, if the IMS-ALG decides to transcode between AMR-WB and EVS (e.g. because AMR-WB was used before the access transfer), it shall include the evs-mode-switch with value 1.
Otherwise the IMS-ALG shall not include the evs-mode-switch.
If the IMS-ALG supplies the evs-mode-switch in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| hf-only
(NOTE 1) | If the hf-only parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the hf-only parameter is contained in the SDP offer, the IMS-ALG shall include the hf-only parameter with unmodified value in the SDP answer.
Otherwise, if the IMS-AGW is configured to negotiate using only the header-full EVS RTP payload format, the IMS-ALG shall include the hf-only parameter with a value 1.
Otherwise, if EVS was used before the access transfer, the IMS-ALG should include the hf-only parameter with a value indicating the mode that was negotiated before the access transfer.
If the IMS-ALG supplies the hf-only parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| dtx
(NOTE 1) | If the dtx parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the dtx parameter is contained in the SDP offer, the IMS-ALG shall include the dtx parameter with unmodified value in the SDP answer.
Otherwise, if the dtx-recv parameter is contained in the SDP offer, the IMS-ALG may include the dtx parameter in the SDP answer with the same value as the dtx-recv parameter in the SDP offer.
Otherwise, if the usage of DTX is not desired (e.g. due to DTX capabilities of expected codecs to transcode with), the IMS-ALG shall include the dtx parameter with a value 0.
Otherwise, if EVS was used before the access transfer, the IMS-ALG should include the dtx parameter with a value indicating the mode that was negotiated before the access transfer.
If the IMS-ALG supplies the dtx parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| dtx-recv
(NOTE 1) | If the dtx-recv parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the reception of DTX is not desired and the dtx parameter is not included, the IMS-ALG shall include the dtx-recv parameter with a value 0.
If both the dtx and dtx-recv parameters are included, those parameters shall have the same value; however, inclusion of the dtx-recv parameter is not required if the dtx parameter is included.
If the IMS-ALG supplies the dtx-recv parameter in the SDP answer, it should also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | + +| | | | +|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| br
(NOTE 1) | If the br parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated bitrates, or a subset of them, in EVS primary mode in the send and receive direction. If the indicated bitrates, and even each subset of them, are not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type, it shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the br parameter is contained in the SDP offer, the IMS-ALG shall select a bitrate value, which is either the received br value or a subset of it, based on IMS-AGW capabilities, possible configured policies, and the negotiated br range of an EVS codec used before the access transfer, and shall include the br parameter with the selected value that is also supplied towards the IMS-AGW in the SDP answer. Otherwise, if the IMS-ALG desires the same bit rate range for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range to match IMS-AGW capabilities possible configured policies, and the negotiated br range of the EVS codec used before the access transfer, the IMS-ALG shall supply the br parameter in the SDP answer it sends. Otherwise the IMS-ALG shall not include this parameter in the SDP answer. If the IMS-ALG also supplies the bw, bw-send or bw-recv parameter, the value of the br parameter shall be compatible with the values of those parameters. If the IMS-ALG supplies the br parameter in the SDP answer, it shall also supply to the IMS-AGW the br parameter in the local descriptor for the termination towards the offerer with the same value. | +| br-send
(NOTE 1) | If the br-send parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated bitrates, or a subset of them, in EVS primary mode in the receive direction. If the indicated bitrates, and even each subset of them, are not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type, it shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the br-recv parameter is contained in the SDP offer, the IMS-ALG shall select a bitrate value, which is either the received br-recv value or a subset of it, based on IMS-AGW capabilities possible configured policies, and the negotiated br range of an EVS codec used before the access transfer, and the IMS-ALG shall include the br-send parameter with the selected value that is also supplied towards the IMS-AGW in the SDP answer. Otherwise, if the IMS-ALG desires a different bit rate (range) for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range for the send direction to match IMS-AGW capabilities and possible configured policies, it shall supply the br-send parameter in the SDP answer it sends. Otherwise the IMS-ALG shall not include the br-send parameter in the SDP answer. If the IMS-ALG also supplies the bw or bw-send parameter, the value of the br-send parameter shall be compatible with the values of those parameters. If the IMS-ALG supplies the br-send parameter in the SDP answer, it shall also supply to the IMS-AGW the br-send parameter in the local descriptor for the termination towards the offerer with the same value. | +| br-recv
(NOTE 1) | If the br-recv parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated bitrates, or a subset of them, in EVS primary mode in the send direction. If the indicated bitrates, and even each subset of them, are not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type, it shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the br-send parameter is contained in the SDP offer, the IMS-ALG shall select a bitrate value, which is either the received br-send value or a subset of it, based on IMS-AGW capabilities, possible configured policies, and the negotiated br range of an EVS codec used before the access transfer, and the IMS-ALG shall include the br-recv parameter with the selected value that is also supplied towards the IMS-AGW in the SDP answer. Otherwise, if the IMS-ALG desires a different bit rate (range) for the send and receive direction in EVS primary mode, and wants to restrict the bit rate range for the receive direction to match IMS-AGW capabilities and possible configured policies, it shall supply the br-recv parameter in the SDP answer it sends. | + +| | | | +|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | |

Otherwise the IMS-ALG shall not include the br-recv parameter in the SDP answer.
If the IMS-ALG also supplies the bw or bw-recv parameter, the value of the br-recv parameter shall be compatible with the values of those parameters.
If the IMS-ALG supplies the br-recv parameter in the SDP answer, it shall also supply to the IMS-AGW the br-recv parameter in the local descriptor for the termination towards the offerer with the same value.

| +|

bw
(NOTE 1)

|

If the bw parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated sampling bandwidth(s), or a subset of them, in EVS primary mode in the send and receive direction. If the indicated sampling bandwidth(s), and even each subset of them, are not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type, it shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor.

|

If the bw parameter is contained in the SDP offer, the IMS-ALG shall select a sampling bandwidth value, which is either the received bw value or a subset of it, based on IMS-AGW capabilities, possible configured policies, and the negotiated bw range of an EVS codec used before the access transfer, and the IMS-ALG shall include the bw parameter with the selected value that is also supplied towards the IMS-AGW in the SDP answer.
Otherwise, if the IMS-ALG desires the same sampling bandwidth(s) for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidth(s) to match IMS-AGW capabilities, possible configured policies, and the negotiated bw range of the EVS codec used before the access transfer, the IMS-ALG shall supply the bw parameter in the SDP answer it sends.
Otherwise the IMS-ALG shall not include this parameter in the SDP answer.
If the IMS-ALG also supplies the br, br-send or br-recv parameter, the value of the bw parameter shall be compatible with the values of those parameters.
If the IMS-ALG supplies the bw parameter in the SDP answer, it shall also supply to the IMS-AGW the bw parameter in the local descriptor for the termination towards the offerer with the same value.

| +|

bw-send
(NOTE 1)

|

If the bw-send parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated sampling bandwidths, or a subset of them, in EVS primary mode in the receive direction. If the indicated sampling bandwidths, and even each subset of them, are not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type, it shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor.

|

If the bw-recv parameter is contained in the SDP offer, the IMS-ALG shall select a sampling bandwidths value, which is either the received bw-recv value or a subset of it, based on IMS-AGW capabilities, possible configured policies, and the negotiated bw range of an EVS codec used before the access transfer, and the IMS-ALG shall include the bw-send parameter with the selected value in the SDP answer.
Otherwise, if the IMS-ALG desires a different sampling bandwidths for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidths for the send direction to match IMS-AGW capabilities, possible configured policies, and the negotiated bw range of the EVS codec used before the access transfer, the IMS-ALG shall supply the bw-send parameter in the SDP answer it sends.
Otherwise the IMS-ALG shall not include the br-send parameter in the SDP answer.
If the IMS-ALG also supplies the bw or bw-send parameter, the value of the br-send parameter shall be compatible with the values of those parameters.
If the IMS-ALG supplies the bw-send parameter in the SDP answer, it shall also supply to the IMS-AGW the bw-send parameter in the local descriptor for the termination towards the offerer with the same value.

| +|

br-recv
(NOTE 1)

|

If the br-recv parameter is contained in the SDP offer, the IMS-ALG shall check if the IMS-AGW supports the indicated sampling bandwidths, or a subset of them, in EVS primary mode in the send direction. If the indicated sampling

|

If the bw-send parameter is contained in the SDP offer, the IMS-ALG shall select a sampling bandwidths value, which is either the received bw-send value or a subset of it, based on IMS-AGW capabilities, possible configured policies, and the

| + +| | | | +|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | bandwidths, and even each subset of them, are not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type, it shall forward the bw-recv parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | negotiated bw range of an EVS codec used before the access transfer, and the IMS-ALG shall include the bw-recv parameter with the selected value in the SDP answer.
Otherwise, if the IMS-ALG desires a different sampling bandwidths for the send and receive direction in EVS primary mode, and wants to restrict the sampling bandwidths for the receive direction to match IMS-AGW capabilities, possible configured policies, and the negotiated bw range of the EVS codec used before the access transfer, the IMS-ALG shall supply the bw-recv parameter in the SDP answer it sends.
Otherwise the IMS-ALG shall not include the bw-recv parameter in the SDP answer.
If the IMS-ALG also supplies the br or br-recv parameter, the value of the bw-recv parameter shall be compatible with the values of those parameters.
If the IMS-ALG supplies the bw-send parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| cmr
(NOTE 1) | If the cmr parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the cmr parameter is contained in the SDP offer, the IMS-ALG shall include the cmr parameter with unmodified value in the SDP answer.
Otherwise, if the IMS-AGW desires to disable codec mode requests within the RTP payload of the EVS primary mode (due to the IMS-AGW capabilities, possible configured policies, and the negotiated CMR mode of an EVS codec used before the access transfer), it shall include the cmr parameter with value -1 in the SDP answer it sends
If the IMS-ALG supplies the cmr parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| ch-aw-recv
(NOTE 1) | If the ch-aw-recv parameter is contained in the SDP offer the IMS-ALG shall check if the IMS-AGW supports the indicated mode in the send direction. If the indicated mode is not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the IMS-ALG it desires to control the channel-aware mode of EVS in the receive direction, e.g. to disable it with value -1, it shall include the ch-aw-recv parameter in the SDP offer and shall also supply the ch-aw-recv parameter to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. The IMS-ALG shall consider the capabilities of the IMS-AGW and the negotiated ch-aw-recv mode of an EVS codec used before the access transfer when it chooses an appropriate value. | +| number of channels
(NOTE 2) | If the "number of channels" parameter is contained in the SDP offer the IMS-ALG shall check if the IMS-AGW supports the indicated number of channels. If the indicated number of channels is not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the "number of channels" parameter is contained in the SDP offer, the IMS-ALG shall include the "number of channels" parameter with unmodified value in the SDP answer and shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| ch-send
(NOTE 1) | If the ch-send parameter is contained in the SDP offer the IMS-ALG shall check if the IMS-AGW supports the indicated number of channels in the receive direction. If the indicated number of channels is not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type for transcoding, the IMS-ALG shall forward the ch-send parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the ch-recv parameter is contained in the SDP offer, the IMS-ALG shall include the ch-send parameter with unmodified value in the SDP answer and shall also supply the ch-send parameter to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | + +| | | | +|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ch-recv
(NOTE 1) | If the ch-recv parameter is contained in the SDP offer the IMS-ALG shall check if the IMS-AGW supports the indicated number of channels in the send direction. If the indicated number of channels is not supported, the IMS-ALG shall not select the EVS payload type for transcoding. If the IMS-ALG selects the EVS payload type for transcoding, the IMS-ALG shall forward the ch-recv parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the ch-send parameter is contained in the SDP offer, the IMS-ALG shall include the ch-recv parameter with unmodified value in the SDP answer and shall also supply the ch-recv parameter to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| mode-set
(NOTE 3) | If the mode-set parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If the mode-set parameter is contained in the SDP offer, the IMS-ALG shall include the mode-set parameter with unmodified value in the SDP answer.
Otherwise, if EVS or AMR-WB was used before the access transfer, the IMS-ALG should include the mode-set parameter with a value indicating the mode that was negotiated before the access transfer (or omit it if no restrictions applied before).
If the IMS-ALG supplies the mode-set parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| mode-change-period
(NOTE 3) | If the mode-change-period parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If EVS or AMR-WB was used before the access transfer, the IMS-ALG should include the mode-change-period parameter with a value indicating the mode that was negotiated before the access transfer (or omit it if no restrictions applied before).
the IMS-ALG should include the mode-change-period parameter for the EVS payload in the SDP offer it forwards.
If the IMS-ALG supplies the mode-change-period parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| mode-change-capability
(NOTE 3) | If the mode-change-capability parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG may forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | The IMS-ALG shall either include the mode-change-capability parameter with a value 2 or omit the parameter.
If the IMS-ALG supplies the mode-change-capability parameter in the SDP answer, it may also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| mode-change-neighbor
(NOTE 3) | If the mode-change-neighbor parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | If EVS or AMR-WB was used before the access transfer, the IMS-ALG should include the mode-change-neighbor parameter with a value indicating the mode that was negotiated before the access transfer (or omit it if no restrictions applied before).
If the IMS-ALG supplies the mode-change-neighbor parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| max-red
(NOTE 5) | If the max-red parameter is contained in the SDP offer and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the IMS-AGW for the termination towards the offerer in the remote descriptor. | The IMS-ALG shall only include the max-red parameter in the SDP answer if it desires to restrict the maximum redundancy of received packets.
When selecting the value of the max-red parameter, the IMS-ALG shall consider the capabilities of the IMS-AGW and, If EVS or AMR-WB was used before the access transfer, the redundancy that was negotiated before the access transfer.
If the IMS-ALG supplies the max-red parameter in the SDP answer, it shall also supply it to the IMS-AGW in the local descriptor for the termination towards the offerer with the same value. | +| 3gpp_mtsi_app_adapt
(NOTE 4) | If the 3gpp_mtsi_app_adapt parameter is contained in the SDP answer, and the IMS-ALG select the EVS payload type for transcoding, the IMS-ALG shall forward this parameter to the | If the IMS-AGW supports RTCP APP based adaptation messages defined in 3GPP TS 26.114 [21], and the IMS-ALG has a policy to negotiate the usage of those messages, | + +| | | | +|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | IMS-AGW the IMS-ALG shall forward this parameter to the IMS-AGW in the remote descriptor. | the IMS-ALG shall include the 3gpp_mtsi_app_adapt SDP attribute indicating the allowed APP messages in the SDP answer. If EVS was used before the access transfer, the IMS-ALG should consider the negotiated RTCP APP packet types the access transfer in addition to the IMS AGW capabilities when selecting the allowed RTCP APP messages. | +| NOTE 1: This MIME parameter of the EVS RTP payload type is defined in 3GPP TS 26.445 [51]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [53].
NOTE 2: This number of channels are encoded as "encoding parameters" of the SDP "a=rtpmap" attribute defined in IETF RFC 4566 [53].
NOTE 3: This MIME parameter of the EVS RTP payload type relates to AMR-WB IO mode and is defined in IETF RFC 4867 [54]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [53].
NOTE 4: This SDP attribute is defined in 3GPP TS 26.114 [21]. It applies to all codecs offered in an SDP media line. However, some values are specific to EVS.
NOTE 5: This MIME parameter of the EVS RTP payload type is defined in IETF RFC 4867 [54]. It is encapsulated within the SDP "a=fmtp" attribute defined IETF RFC 4566 [53]. | | | + +## 6.2.15 Multimedia Priority Congestion Control Procedures + +### 6.2.15.1 General + +The IMS-ALG and IMS-AGW may support the priority treatment of a call/session identified as an MPS call/session. This clause describes the Iq signalling procedures and their interactions with SIP signalling in the control plane and with user plane procedures to support the requirements for Multimedia Priority Service. These Iq signalling procedures may or may not apply depending on the network configuration (e.g. whether the IMS-AGW is shared by multiple IMS-ALGs or whether the IMS-ALG controls multiple IMS-AGWs for a given route – Media Gateway Group). + +The IMS-ALG can receive a SIP INVITE with MPS priority information (see 3GPP TS 23.228 [2], clause 5.21). + +### 6.2.15.2 IMS-AGW Resource Congestion in ADD response, request is queued + +If the IMS-ALG requests a resource via the procedure Reserve and Configure AGW Connection Point or Reserve AGW Connection Point and receives an error indicating that the requested resource could not be seized (e.g. H.248 error code #510 "insufficient resources") and the IMS-ALG does not have alternative IMS-AGW through which it can route the call it queues the priority session and gives it priority over any further Reserve and Configure AGW Connection Point or Reserve AGW Connection Point procedures for lower priority sessions towards this IMS-AGW until the requested resource for this queued session is successfully seized. The example sequence is shown in Figure 6.2.15.2.1. + +![Sequence diagram showing the interaction between IMS-ALG and IMS-AGW for reserving MPS priority call resources. The diagram illustrates a congestion scenario where the first request is rejected, and the second request is successful after queuing.](710ff83dc4a77abbe489fbf1a462845a_img.jpg) + +``` + +sequenceDiagram + participant External + participant IMS-ALG + participant IMS-AGW + + Note left of IMS-ALG: Reserve AGW connection point + External->>IMS-ALG: 1. INVITE [MPS priority indication] + IMS-ALG->>IMS-AGW: 2. H.248 ADD Req [C=?, T=?, Laddr=?, Lport=?, Local Resources, priority] + IMS-AGW-->>IMS-ALG: 3. H.248 ADD Reject [Error = #510] + Note right of IMS-AGW: IMS-AGW is Congested + Note left of IMS-ALG: IMS-ALG queues MPS request + Note left of IMS-ALG: Reserve AGW connection point + IMS-ALG->>IMS-AGW: 5. H.248 ADD Req [C=?, T=?, Laddr=?, Lport=?, Local Resources, priority] + IMS-AGW-->>IMS-ALG: 6. H.248 ADD Resp [C=C1, T=T2, Laddr=IP2o, LPort=P2o] + Note right of IMS-AGW: IMS-AGW successfully seizes required resources + +``` + +Sequence diagram showing the interaction between IMS-ALG and IMS-AGW for reserving MPS priority call resources. The diagram illustrates a congestion scenario where the first request is rejected, and the second request is successful after queuing. + +**Figure 6.2.15.2.1: Request to reserve IMS-AGW MPS Priority call resources when IMS-AGW is congested** + +### 6.2.15.3 IMS-AGW Resource Congestion in ADD response, IMS-ALG seizes new IMS-AGW + +If the IMS-ALG requests a resource via the procedure Reserve and Configure AGW Connection Point or Reserve AGW Connection Point and receives an error indicating that the requested resources could not be seized (e.g. H.248 error code #510 "insufficient resources") and Media Gateway Groups are implemented it should seize a new IMS-AGW from the same Media Gateway Group before resorting to any queuing of the priority session (as described in 6.2.15.2) to enable the MPS call/session to proceed as early as possible. + +### 6.2.15.4 IMS-AGW Priority Resource Allocation + +If the IMS-AGW supports the Priority information (e.g. determined through provisioning or package profile) the IMS-ALG requests a resource via the procedure Reserve and Configure AGW Connection Point or Reserve AGW Connection Point and includes the Priority information. The IMS-AGW may then provide priority allocation of resources once a congestion threshold is reached. If the IMS-AGW is completely congested it shall indicate this to the IMS-ALG as described in 6.2.15.2. The example sequence is shown in Figure 6.2.15.4.1. + +![Sequence diagram for Figure 6.2.15.4.1 showing the request to reserve IMS-AGW MPS Priority call resources when IMS-AGW is congested.](1cd38e4f2ffcae2871964fa6313a9a27_img.jpg) + +The diagram illustrates a sequence of messages between an IMS-ALG and an IMS-AGW. The IMS-ALG sends an INVITE message with an MPS priority indication to the IMS-AGW. The IMS-AGW responds with an H.248 ADD Req message containing parameters: C=?, T=?, Laddr=?, Lport=?, Local Resources, and Priority. The IMS-ALG then sends an H.248 ADD Resp message containing parameters: C=C1, T=T2, Laddr=IP2o, and LPort=P2o. A bracket on the left side of the diagram, labeled 'Reserve AGW Connection point', encompasses the H.248 ADD Req and H.248 ADD Resp messages. On the right side, a note indicates that the IMS-AGW is in a congested state but allocates priority resources to this call. + +Sequence diagram for Figure 6.2.15.4.1 showing the request to reserve IMS-AGW MPS Priority call resources when IMS-AGW is congested. + +**Figure 6.2.15.4.1: Request to reserve IMS-AGW MPS Priority call resources when IMS-AGW is congested, priority resources are allocated** + +## 6.2.15.5 IMS-AGW Priority User Data marking + +The IMS-ALG may request the streams associated to an MPS Priority Call to be marked with certain priority code point as described in clause 6.2.7. The IMS-AGW shall then mark each IP packet header accordingly. The example sequence is shown in Figure 6.2.15.5.1. + +![Sequence diagram for Figure 6.2.15.5.1 showing the request to reserve IMS-AGW call resources and apply DCSP marking for MPS.](9f4aa7e5ba7f250b1c6d190b26b9cb6c_img.jpg) + +The diagram illustrates a sequence of messages between an IMS-ALG and an IMS-AGW. The IMS-ALG sends an INVITE message with an MPS priority indication to the IMS-AGW. The IMS-AGW responds with an H.248 ADD Req message containing parameters: C=?, T=?, Laddr=?, Lport=?, Local Resources, Diffserv Mark = DSCP1, and priority. The IMS-ALG then sends an H.248 ADD Resp message containing parameters: C=C1, T=T2, Laddr=IP2o, and LPort=P2o. A bracket on the left side of the diagram, labeled 'Reserve AGW Connection point', encompasses the H.248 ADD Req and H.248 ADD Resp messages. On the right side, a note indicates that the IMS-AGW is requested to apply DSCP value in the IP header of user data packets. + +Sequence diagram for Figure 6.2.15.5.1 showing the request to reserve IMS-AGW call resources and apply DCSP marking for MPS. + +**Figure 6.2.15.5.1: Request to reserve IMS-AGW call resources and apply DCSP marking for MPS** + +The IMS-AGW may also provide priority allocation for resources requested via a subsequent Configure AGW Connection Point procedure not including Priority information if the related context has been marked with priority information during the Reserve AGW Connection Point or Reserve and Configure AGW Connection Point procedure. + +## 6.2.15.6 IMS-AGW Priority Modification + +If the IMS-ALG seized an IP termination for a priority call/session with a default priority and subsequently needs to modify the priority information previously communicated to the IMS-AGW (e.g. subject to subsequent authorisation by an authorisation point, see 3GPP TS 24.229 [11] clause 4.11), the IMS-ALG may modify the existing IP termination for the MPS call/session with the actual priority and, if DiffServ is used, provision a suitable DSCP marking for the updated MPS priority level to the IMS-AGW via the Configure AGW Connection Point Procedure. + +NOTE: The specific Iq related call sequence which details the handling to support the requirements defined in 3GPP TS 24.229 [11], clause 4.11 and 3GPP TS 23.228 [2], clause 5.21 is not specified, and therefore implementations might exist which fulfil these requirements but do not require modification of the priority information across the Iq interface. + +## 6.2.16 Coordination of Video Orientation + +Figure 6.2.16.1 shows the message sequence chart example for indicating extended RTP header for Coordination of Video Orientation. + +![Sequence diagram showing the procedure to indicate RTP extension header for CVO between IMS-ALG and IMS-AGW.](ef86416097668984aee7611317e77bb9_img.jpg) + +``` + +sequenceDiagram + participant External + participant IMS-ALG + participant IMS-AGW + + Note right of IMS-AGW: Reserve AGW Connection Point + + External->>IMS-ALG: INVITE/SDP offer ["a=extmap:URN=CVO"] + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=?, T=?, Laddr=?, Lport=?, Local Resources, Extended RTP header(CVO)] + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[Termination T2...] + Note right of IMS-AGW: Reserve and Configure AGW Connection Point + + IMS-ALG->>External: INVITE/SDP offer ["a=extmap:URN=CVO"] + External-->>IMS-ALG: SDP answer ["a=extmap:URN=CVO"] + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=C, T=?, Laddr=?, Lport=?, Local Resources, Extended RTP header(CVO)] + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[Termination T1...] + IMS-ALG-->>External: SDP answer ["a=extmap:URN=CVO"] + +``` + +The sequence diagram illustrates the interaction between an IMS-ALG and an IMS-AGW for video orientation coordination. It starts with an external INVITE/SDP offer to the IMS-ALG. The IMS-ALG sends an H.248:ADD.req message to the IMS-AGW, which reserves an AGW connection point. The IMS-AGW responds with H.248:ADD.resp. The IMS-ALG then sends an INVITE/SDP offer to the external entity, which responds with an SDP answer. Finally, the IMS-ALG sends another H.248:ADD.req to the IMS-AGW, which reserves and configures the AGW connection point and responds with H.248:ADD.resp. The IMS-ALG then sends the final SDP answer to the external entity. + +Sequence diagram showing the procedure to indicate RTP extension header for CVO between IMS-ALG and IMS-AGW. + +Figure 6.2.16.1: Procedure to indicate RTP extension header for CVO + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally requesting the IMS-AGW to support the RTP Header Extension capability as defined in IETF RFC 5285 [23]. + +NOTE: If the IMS-ALG receives an SDP answer, which includes the "a=extmap" attribute with a CVO URN with a granularity that the IMS-AGW has not included in its response, or if the SDP answer does not include any "a=extmap" CVO related attribute, it is not necessary to modify the IMS-AGW settings for this reason alone. Doing that would only add unnecessary signalling without requiring any action or changes in the IMS-AGW. However, if the IMS-ALG needs to modify the media attributes for other purposes, in particular due to transcoding, then the IMS-AGW is updated in accordance with the received SDP answer, that is, either with the received CVO related "a=extmap" attribute if present in the received SDP answer or without it if not included in the received SDP answer (thus removing the requirement for supporting "a=extmap" and for sending the header and CVO bits for the transcoded stream). + +## 6.2.17 Procedures for Interactive Connectivity Establishment (ICE) + +### 6.2.17.1 ICE lite + +Figure 6.2.17.1.1 shows a message sequence chart example for performing the ICE lite procedure towards the offerer. + +![Sequence diagram for ICE lite procedure between IMS-ALG and IMS-AGW.](5e787be3a9da44aa97f5fcdcd41c0123_img.jpg) + +``` + +sequenceDiagram + participant External + participant IMS-ALG + participant IMS-AGW + + Note right of IMS-ALG: INVITE/SDP offer +["a=candidate rc, +a=ice-pwd rpw, +a=ice-ufrag ruf"] + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=?, T=?, Local Resources (Laddr=?, Lport=?)] + Note right of IMS-AGW: Reserve AGW Connection Point + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[C=C1, T=T2] + IMS-ALG->>IMS-AGW: INVITE/SDP offer [] + IMS-ALG-->>IMS-AGW: SDP Answer [] + IMS-ALG->>IMS-AGW: H.248:MOD.req[C=C1, T=T2] + Note right of IMS-AGW: Configure AGW Connection Point + IMS-AGW-->>IMS-ALG: H.248:MOD.resp[C=C1, T=T2] + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=C1, T=?, STUN server request, +Local Resources (Laddr=?, Lport=?, ice-pwd=?, +ice-ufrag=?; candidate host=?), +Remote Resources (candidate rc, ice-pwd rpw, +ice-ufrag ruf)] + Note right of IMS-AGW: Reserve and Configure AGW Connection Point + IMS-AGW-->>IMS-ALG: H.248:ADD.req[C=C1, T=T1, +Local Resources (Laddr=l1, Lport=p1, ice- +pwd=lpw, ice-ufrag=luf; candidate=lc, ice-lite)] + Note left of IMS-ALG: SDP Answer +[a=ice-pwd lpw, +a=ice-ufrag luf, +a=candidate lc, +a=ice-lite] + +``` + +The sequence diagram illustrates the ICE lite procedure between an IMS-ALG and an IMS-AGW. The process begins with an INVITE/SDP offer from an external source to the IMS-ALG. The IMS-ALG sends an H.248:ADD.req message to the IMS-AGW to reserve a connection point. The IMS-AGW responds with H.248:ADD.resp. The IMS-ALG then sends an INVITE/SDP offer to the IMS-AGW and receives an SDP Answer. Next, the IMS-ALG sends an H.248:MOD.req to configure the connection point, which the IMS-AGW confirms with H.248:MOD.resp. The IMS-ALG then sends a detailed H.248:ADD.req including STUN server requests and remote resources. The IMS-AGW reserves and configures the connection point and responds with an H.248:ADD.req containing local resources and candidate information. Finally, the IMS-ALG sends an SDP Answer back to the external source. + +Sequence diagram for ICE lite procedure between IMS-ALG and IMS-AGW. + +Figure 6.2.17.1.1: Procedure for interactive connectivity establishment using ICE lite towards the offerer + +### 6.2.17.2 Full ICE + +Figure 6.2.17.2.1 shows a message sequence chart example for performing the full ICE procedure towards the offerer. + +![Sequence diagram for interactive connectivity establishment using full ICE towards the offerer. The diagram shows the interaction between an IMS-ALG and an IMS-AGW. The IMS-ALG receives an INVITE/SDP offer from the left. It sends an H.248:ADD.req to the IMS-AGW to reserve a connection point. The IMS-AGW responds with H.248:ADD.resp. The IMS-ALG then sends an INVITE/SDP offer to the IMS-AGW, which responds with an SDP Answer. The IMS-ALG then sends an H.248:MOD.req to configure the connection point. The IMS-AGW responds with H.248:MOD.resp. The IMS-ALG then sends an H.248:ADD.req with STUN server request and ICE connectivity check details. The IMS-AGW responds with H.248:ADD.req with local and remote resources. The IMS-ALG then sends an SDP Answer to the left.](223792b3652794024244c277cc46394b_img.jpg) + +``` + +sequenceDiagram + participant Client + participant IMS-ALG + participant IMS-AGW + + Note left of Client: INVITE/SDP offer +["a=candidate rc, +a=ice-pwd rpw, +a=ice-uf rag ruf"] + Client->>IMS-ALG: INVITE/SDP offer + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=?, T=?, Local Resources (Laddr=?, Lport=?)] + Note right of IMS-AGW: Reserve AGW Connection Point + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[C=C1, T=T2] + IMS-ALG->>IMS-AGW: INVITE/SDP offer [] + IMS-AGW-->>IMS-ALG: SDP Answer [] + IMS-ALG->>IMS-AGW: H.248:MOD.req[C=C1, T=T2] + Note right of IMS-AGW: Configure AGW Connection Point + IMS-AGW-->>IMS-ALG: H.248:MOD.resp[C=C1, T=T2] + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=C1, T=?, STUN server request, ICE connectivity check {Notify connectivity check result, Notify new peer reflexive candidate}, Local Resources (Laddr=?, Lport=?, ice-pwd=?, ice-uf rag=?; candidate host=?), Remote Resources (candidate rc, ice-pwd rpw, ice-uf rag ruf)] + IMS-AGW-->>IMS-ALG: H.248:ADD.req[C=C1, T=T1, Local Resources (Laddr=l1, Lport=p1, ice-pwd=lpw, ice-uf rag=luf; candidate=lc)] + Note right of IMS-AGW: Reserve and Configure AGW Connection Point + IMS-ALG-->>Client: SDP Answer +[a=ice-pwd lpw, +a=ice-uf rag luf, +a=candidate lc,] + +``` + +Sequence diagram for interactive connectivity establishment using full ICE towards the offerer. The diagram shows the interaction between an IMS-ALG and an IMS-AGW. The IMS-ALG receives an INVITE/SDP offer from the left. It sends an H.248:ADD.req to the IMS-AGW to reserve a connection point. The IMS-AGW responds with H.248:ADD.resp. The IMS-ALG then sends an INVITE/SDP offer to the IMS-AGW, which responds with an SDP Answer. The IMS-ALG then sends an H.248:MOD.req to configure the connection point. The IMS-AGW responds with H.248:MOD.resp. The IMS-ALG then sends an H.248:ADD.req with STUN server request and ICE connectivity check details. The IMS-AGW responds with H.248:ADD.req with local and remote resources. The IMS-ALG then sends an SDP Answer to the left. + +Figure 6.2.17.2.1: Procedure for interactive connectivity establishment using full ICE towards the offerer + +### 6.2.17.3 Connectivity check result notification (full ICE) + +Figure 6.2.17.3.1 shows the message sequence chart example for an ICE connectivity check result Event. + +![Sequence diagram for reporting ICE connectivity check result. The diagram shows the interaction between an IMS-ALG and an IMS-AGW. The IMS-AGW sends an H.248:NOTIFY.Req (ICE connectivity check result) to the IMS-ALG. The IMS-ALG responds with H.248:NOTIFY.resp (ICE connectivity check result). The IMS-AGW then sends an ICE Connectivity Check Result Notification to the IMS-ALG.](a829326cd51f70316b996493833ec86c_img.jpg) + +``` + +sequenceDiagram + participant IMS-ALG + participant IMS-AGW + + Note right of IMS-AGW: ICE Connectivity Check Result Notification + IMS-AGW->>IMS-ALG: H.248:NOTIFY.Req (ICE connectivity check result) [Termination =x, Candidate/Transport pair] + IMS-ALG-->>IMS-AGW: H.248:NOTIFY.resp (ICE connectivity check result) [Termination x] + IMS-AGW->>IMS-ALG: Context(Cx) + IMS-ALG-->>IMS-AGW: Context(Cx) + +``` + +Sequence diagram for reporting ICE connectivity check result. The diagram shows the interaction between an IMS-ALG and an IMS-AGW. The IMS-AGW sends an H.248:NOTIFY.Req (ICE connectivity check result) to the IMS-ALG. The IMS-ALG responds with H.248:NOTIFY.resp (ICE connectivity check result). The IMS-AGW then sends an ICE Connectivity Check Result Notification to the IMS-ALG. + +Figure 6.2.17.3.1: Procedure to report ICE connectivity check result + +### 6.2.17.4 New peer reflexive candidate notification (full ICE) + +Figure 6.2.17.4.1 shows the message sequence chart example for additional connectivity check when new peer reflexive candidate is discovered in full ICE. + +![Sequence diagram showing the procedure to perform an additional connectivity check upon the report of a new peer reflexive candidate between IMS-ALG and IMS-AGW.](b55cd9b5721bd8aabc979c85316924e4_img.jpg) + +``` + +sequenceDiagram + participant IMS-AGW + participant IMS-ALG + Note right of IMS-AGW: Additional connectivity check based on new peer reflexive candidate notification + IMS-AGW->>IMS-ALG: H.248:NOTIFY.Req (New peer reflexive candidate) [C=Cx, T=Tx, Candidate] + IMS-ALG-->>IMS-AGW: H.248:NOTIFY.resp (New peer reflexive candidate) [C=Cx, T=Tx] + IMS-ALG->>IMS-AGW: H.248:MODIFY.Req [C=Cx, T=Tx, Additional connectivity check] + IMS-AGW-->>IMS-ALG: H.248:MODIFY.resp [C=Cx, T=Tx] + +``` + +Sequence diagram showing the procedure to perform an additional connectivity check upon the report of a new peer reflexive candidate between IMS-ALG and IMS-AGW. + +Figure 6.2.17.4.1: Procedure to perform additional connectivity check upon the report of new peer reflexive candidate + +## 6.2.17.5 STUN consent freshness test + +Figure 6.2.17.5.1 shows a message sequence chart example for requesting the STUN consent freshness test procedure towards the offerer when full ICE is supported by the eIMS-AGW. + +![Sequence diagram showing the procedure for STUN consent freshness test towards the offerer between eP-CSCF and eIMS-AGW.](516174e327ed8fcb75cb3af20f110de8_img.jpg) + +``` + +sequenceDiagram + participant eP-CSCF + participant eIMS-AGW + Note left of eP-CSCF: INVITE/SDP offer +["a=candidate rc, +a=ice-pwd rpw, +a=ice-uf rag ruf"] + eP-CSCF->>eIMS-AGW: H.248:ADD.req[C=?, T=?, Local Resources (Laddr = ?, Lport = ?)] + Note right of eIMS-AGW: Reserve AGW Connection Point + eIMS-AGW-->>eP-CSCF: H.248:ADD.resp[C=C1, T=T2] + Note left of eP-CSCF: INVITE/SDP offer [] + eP-CSCF->>eP-CSCF: SDP Answer [] + Note right of eIMS-AGW: Configure AGW Connection Point + eP-CSCF->>eIMS-AGW: H.248:MOD.req[C=C1, T=T2] + eIMS-AGW-->>eP-CSCF: H.248:MOD.resp[C=C1, T=T2] + Note right of eIMS-AGW: STUN consent freshness test + eP-CSCF->>eIMS-AGW: H.248:ADD.req[C=C1, T=?, STUN server request, ICE connectivity check {Notify connectivity check result, Notify new peer reflexive candidate}, STUN consent freshness test, Local Resources (Laddr = ?, Lport = ?, ice-pwd=?, ice-uf rag=?; candidate host=?), Remote Resources (candidate rc, ice-pwd rpw, ice-uf rag ruf)] + Note right of eIMS-AGW: Reserve and Configure AGW Connection Point + eP-CSCF->>eIMS-AGW: H.248:ADD.req[C=C1, T=T1, Local Resources (Laddr = l1, Lport = p1, ice-pwd=lpw, ice-uf rag=luf; candidate=lc)] + eIMS-AGW-->>eP-CSCF: SDP Answer [a=ice-pwd lpw, a=ice-uf rag luf, a=candidate lc,] + +``` + +Sequence diagram showing the procedure for STUN consent freshness test towards the offerer between eP-CSCF and eIMS-AGW. + +Figure 6.2.17.5.1: Procedure for STUN consent freshness test towards the offerer + +## 6.2.17.6 STUN Consent Freshness Test Failure Notification + +Figure 6.2.17.6.1 shows the message sequence chart example for an ICE STUN consent freshness test failure Event. + +![Sequence diagram showing the procedure to report STUN consent freshness test failure between eIMS-ALG and eIMS-AGW.](35f0cb888f4aa1b5fd01738a3ea3f0c1_img.jpg) + +``` + +sequenceDiagram + participant eIMS-ALG + participant eIMS-AGW + Note right of eIMS-AGW: STUN Consent Freshness Test Failure Notification + eIMS-AGW->>eIMS-ALG: H.248:NOTIFY.Req (STUN consent freshness test failure) [Termination =x, Candidate/Transport pair] + Note left of eIMS-ALG: Context(Cx) + eIMS-ALG->>eIMS-AGW: H.248:NOTIFY.resp (STUN consent freshness test failure) [Termination x] + Note right of eIMS-AGW: Context(Cx) + +``` + +The diagram illustrates the message exchange between an eIMS-ALG and an eIMS-AGW. The eIMS-AGW sends an H.248:NOTIFY.Req message to the eIMS-ALG, indicating a STUN consent freshness test failure. The eIMS-ALG responds with an H.248:NOTIFY.resp message. The eIMS-AGW also sends a STUN Consent Freshness Test Failure Notification. Context(Cx) labels are present on both sides of the exchange. + +Sequence diagram showing the procedure to report STUN consent freshness test failure between eIMS-ALG and eIMS-AGW. + +Figure 6.2.17.6.1: Procedure to report STUN consent freshness test failure + +## 6.2.18 TCP bearer connection control + +### 6.2.18.1 General + +All message sequence charts in this clause are examples. The H.248 context model is defined in Figure 6.2.1.1. + +### 6.2.18.2 Stateless TCP handling + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG and IMS-AGW applying the requirements specified in clause 5.16.1. + +### 6.2.18.3 State-aware TCP handling without support of modifying the TCP setup direction + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG and IMS-AGW applying the requirements specified in clause 5.16.2.2. + +Clause 6.2.10.3.1 provides example call flows for TCP bearer connection establishment without modifying the TCP setup direction. + +### 6.2.18.4 State-aware TCP handling with support of modifying the TCP setup direction + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG and IMS-AGW applying the requirements specified in clause 5.16.2.3. + +Figure 6.2.18.4.1 shows an example call flow for a terminating session set-up procedure, where the IMS-ALG receives an incoming SDP offer containing media line for a new MSRP media stream with an "a=setup:active" SDP attribute towards a served UE located behind a remote NAT. + +![Sequence diagram showing the terminating example call flow for MSRP between UEs located behind NAT. The diagram involves three main entities: P-CSCF (IMS-ALG), IMS-AGW, and UE-B. The process includes SDP offers, H.248 ADD/MOD requests and responses, and TCP SYN/ACK exchanges. Brackets on the left indicate specific actions: 'Reserve AGW Connection Point (, Change Through-Connection)', 'Reserve and Configure AGW Connection Point (, Change Through-Connection)', and 'Configure AGW Connection Point (, Change Through-Connection)'.](6059b0a3a051cc20b414d51a4e412f3e_img.jpg) + +``` + +sequenceDiagram + participant P-CSCF as P-CSCF (IMS-ALG) + participant IMS-AGW as IMS-AGW + participant UE-B as UE-B + + Note left of P-CSCF: 1. SDP offer (c=IP1o, m=P1o TCP/MSRP, a=setup:active) + P-CSCF->>IMS-AGW: 2. H.248 ADD req (C=?, T=?, m=TCP, a=setup:passive, LAddr=?, LPort=?) + Note right of IMS-AGW: 3. Create outgoing termination T1 + IMS-AGW-->>P-CSCF: 4. H.248 ADD resp (C=C1, T=T1, LAddr=IP2o, LPort=P2o) + Note left of P-CSCF: Reserve AGW Connection Point (, Change Through-Connection) + P-CSCF->>IMS-AGW: 5. H.248 ADD req (C=C1, T=?, m=TCP, a=setup:passive, LAddr=?, LPort=?, RAddr=IP1o, RPort=P1o) + Note right of IMS-AGW: 6. Create incoming termination T2 + IMS-AGW-->>P-CSCF: 7. H.248 ADD resp (C=C1, T=T2, LAddr=IP2a, LPort=P2a, RAddr=IP1o, RPort=P1o) + Note left of P-CSCF: Reserve and Configure AGW Connection Point (, Change Through-Connection) + P-CSCF->>P-CSCF: 8. Modify SDP offer + P-CSCF->>IMS-AGW: 9. SDP offer (c=IP2o, m=P2o TCP/MSRP, a=setup:actpass) + Note right of UE-B: 10. TCP SYN + IMS-AGW-->>P-CSCF: 11. SDP answer (c=IP1a, m=P1a TCP/MSRP, a=setup:active) + P-CSCF->>IMS-AGW: 12. H.248 MOD req (C=C1, T=T1, RAddr=IP1a, RPort=P1a) + Note right of IMS-AGW: 13. Configure outgoing termination T1 + IMS-AGW-->>P-CSCF: 14. H.248 MOD resp (C=C1, T=T1) + Note left of P-CSCF: Configure AGW Connection Point (, Change Through-Connection) + P-CSCF-->>IMS-AGW: 10'. TCP SYN + P-CSCF->>P-CSCF: 15. Modify SDP answer + P-CSCF-->>P-CSCF: 16. SDP answer (c=IP2a, m=P2a TCP/MSRP, a=setup:passive) + Note right of IMS-AGW: 17. TCP SYN + Note right of UE-B: 18. TCP SYN ACK + IMS-AGW-->>IMS-AGW: TCP SYN ACK + IMS-AGW-->>IMS-AGW: TCP ACK + IMS-AGW-->>IMS-AGW: TCP ACK + +``` + +Sequence diagram showing the terminating example call flow for MSRP between UEs located behind NAT. The diagram involves three main entities: P-CSCF (IMS-ALG), IMS-AGW, and UE-B. The process includes SDP offers, H.248 ADD/MOD requests and responses, and TCP SYN/ACK exchanges. Brackets on the left indicate specific actions: 'Reserve AGW Connection Point (, Change Through-Connection)', 'Reserve and Configure AGW Connection Point (, Change Through-Connection)', and 'Configure AGW Connection Point (, Change Through-Connection)'. + +Figure 6.2.18.4.1: Terminating example call flow for MSRP between UEs located behind NAT + +The IMS UE B performs an IMS terminating session set-up according to 3GPP TS 23.228 [2], with modifications as described in 3GPP TS 33.328 [12]. + +The procedure in the above figure is described step-by-step with an emphasis on the additional aspects for IMS-ALG and IMS-AGW of TCP bearer connection control. + +1. The P-CSCF (IMS-ALG) receives an SDP offer for an MSRP media stream with an "a=setup:active" attribute. For the MSRP media stream offered with transport "TCP/MSRP", the P-CSCF (IMS-ALG) allocates the required resources, includes the IMS-AGW in the media path and proceeds as specified in this clause. +- 2.-4. The IMS-ALG uses the "Reserve AGW Connection Point" procedure to request a termination for "TCP" media (for application-agnostic interworking) or "TCP/MSRP" media (for application-aware interworking) towards the access network. The IMS-ALG preconfigures the IMS-AGW to operate in TCP merge mode by providing the "a=setup:passive" attribute. +- 5.-7. The IMS-ALG uses the "Reserve And Configure AGW Connection Point" procedure to request a termination for "TCP" media (for application-agnostic interworking) or "TCP/ MSRP" media (for application-aware interworking) towards the core network. The IMS-ALG preconfigures the IMS-AGW to operate in TCP Merge mode by providing the "a=setup:passive" attribute. +8. The P-CSCF (IMS-ALG) changes the "a=setup" SDP attribute to "actpass" in the SDP offer and inserts the address information received from the IMS-AGW. +9. The P-CSCF (IMS-ALG) forwards the SDP offer. +10. The UE B chooses to become the active party in the TCP connection establishment and sends a TCP SYN to establish the TCP connection. If the P-CSCF (IMS-ALG) indicated to the IMS-AGW at step 2 that it shall ignore any incoming TCP connection establishment requests (TCP SYN), e.g. to enable a remote source transport address filtering, or if the P-CSCF (IMS-ALG) did not indicate to the IMS-AGW at step 2 that it shall latch onto the required destination address via the source address/port of the incoming media, the IMS-AGW shall drop the TCP SYN received from the UE. +If the TCP SYN is not answered before a timer expiry, the UE will send the TCP SYN a second time (step 10'). +11. The P-CSCF (IMS-ALG) receives the SDP answer. It contains the SDP answer with an "a=setup:active" attribute. +- 12.-14. The IMS-ALG uses the "Configure AGW Connection Point" procedure to configure the termination towards the UE B with remote address information. +15. The P-CSCF (IMS-ALG) modifies the SDP answer before sending it to the core network. The P-CSCF (IMS-ALG) sets the "a=setup:passive" SDP attribute. +16. The P-CSCF (IMA-ALG) then sends the updated SDP answer to core network. +17. The IMS-AGW answers the TCP SYN and the remote peer completes the TCP connection establishment. +18. The IMS-AGW answers the TCP SYN and UE B completes the TCP connection establishment. + +## 6.2.19 Application-aware MSRP interworking at the IMS-AGW + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG: + +- indicating "TCP/MSRP" or "TCP/TLS/MSRP" (if e2ae media security is applied) as transport protocol to the IMS-AGW; +- configuring the IMS-AGW to apply application-aware MSRP interworking; and +- providing the SDP "a=path" attribute, as received in SIP/SDP signalling, to the IMS-AGW as "MSRP Path" with the remote descriptor of the corresponding call leg. + +The IMS-AGW applies application-aware MSRP interworking if being instructed from the IMS-ALG. Support of dynamic instructions from the IMS-ALG is optional. + +If the IMS-AGW applies application-aware MSRP interworking, it modifies the MSRP "To-Path" header field in MSRP packets by replacing the IP address and TCP port of the only entry with the corresponding information in the "MSRP + +path" provided by the IMS\_ALG while retaining the MSRP session ID part of the entry as received in the MSRP "To-Path" and then forward the MSRP data without further modification. + +## 6.2.20 Alternate Connection (ALTC) Addresses Management + +Figure 6.2.20.1 shows a message sequence chart example for a terminating session setup with a dual stack UE using the SDP attributes "altc" inserted by the IMS-ALG in the SDP offer to indicate the IP addresses for potential alternative connection addresses. + +![Sequence diagram showing the terminating session setup with insertion of the SDP attribute 'altc' by the IMS-ALG. The diagram involves three main participants: P-CSCF (IMS-ALG), IMS-AGW, and UE-A. The process starts with an SDP offer from UE-A to P-CSCF. P-CSCF then sends H.248 ADD requests to IMS-AGW to reserve connection points and create outgoing terminations T2 and T3. P-CSCF modifies the SDP offer to include 'altc' attributes and sends it to UE-A. UE-A responds with an SDP answer. P-CSCF then sends H.248 MOD requests to IMS-AGW to configure the connection points and create an incoming termination T1. P-CSCF modifies the SDP answer and sends it to UE-A. Finally, P-CSCF sends H.248 SUB requests to IMS-AGW to release the outgoing termination T3.](137bcfed81ada68ca5162ca5afed35c7_img.jpg) + +The sequence diagram illustrates the interaction between P-CSCF (IMS-ALG), IMS-AGW, and UE-A for terminating session setup. The steps are as follows: + +- UE-A sends an SDP offer (c=IP1o P1o) to P-CSCF (IMS-ALG). +- P-CSCF (IMS-ALG) sends an H.248 ADD req (C=?, T=?, AddrType=IPv6, LAddr=?, LPort=?) to IMS-AGW. +- IMS-AGW performs "Reserve AGW Connection Point (Change Through-Connection)" and sends a "Create outgoing termination T2" message to P-CSCF (IMS-ALG). +- P-CSCF (IMS-ALG) receives an H.248 ADD resp (C=C1, T=T2, LAddr=IP2o, LPort=P2o) from IMS-AGW. +- P-CSCF (IMS-ALG) sends an H.248 ADD req (C=C1, T=?, AddrType=IPv4, LAddr=?, LPort=?) to IMS-AGW. +- IMS-AGW performs "Reserve AGW Connection Point (Change Through-Connection)" and sends a "Create outgoing termination T3" message to P-CSCF (IMS-ALG). +- P-CSCF (IMS-ALG) receives an H.248 ADD resp (C=C1, T=T3, LAddr=IP2a, LPort=P2a) from IMS-AGW. +- P-CSCF (IMS-ALG) sends a "Modify SDP offer" message to IMS-AGW. +- P-CSCF (IMS-ALG) sends an SDP offer (c=IP2o P2o, a=altc:1 IP6 IP2o P2o, a=altc:2 IP4 IP2a P2a) to UE-A. +- UE-A sends an SDP answer (c=IP1a P1a) to P-CSCF (IMS-ALG). +- P-CSCF (IMS-ALG) sends an H.248 MOD req (C=C1, T=T2, RAddr=IP1a, RPort=P1a) to IMS-AGW. +- IMS-AGW performs "Configure AGW Connection Point (Change Through-Connection)" and sends a "Configure outgoing termination T2" message to P-CSCF (IMS-ALG). +- P-CSCF (IMS-ALG) receives an H.248 MOD resp (C=C1, T=T2) from IMS-AGW. +- P-CSCF (IMS-ALG) sends an H.248 ADD req (C=C1, T=?, LAddr=?, LPort=?, RAddr=IP1o, RPort=P1o) to IMS-AGW. +- IMS-AGW performs "Reserve AGW and Configure Connection Point (Change Through-Connection)" and sends a "Create incoming termination T1" message to P-CSCF (IMS-ALG). +- P-CSCF (IMS-ALG) receives an H.248 ADD resp (C=C1, T=T1, LAddr=IP2b, LPort=P2b, RAddr=IP1o, RPort=P1o) from IMS-AGW. +- P-CSCF (IMS-ALG) sends a "Modify SDP answer" message to IMS-AGW. +- P-CSCF (IMS-ALG) sends an SDP answer (c=IP2b P2b) to UE-A. +- P-CSCF (IMS-ALG) sends an H.248 SUB req (C=C1, T=T3) to IMS-AGW. +- IMS-AGW performs "Release AGW Termination" and sends a "Release outgoing termination T3" message to P-CSCF (IMS-ALG). +- P-CSCF (IMS-ALG) receives an H.248 SUB resp (C=C1, T=T3) from IMS-AGW. + +Sequence diagram showing the terminating session setup with insertion of the SDP attribute 'altc' by the IMS-ALG. The diagram involves three main participants: P-CSCF (IMS-ALG), IMS-AGW, and UE-A. The process starts with an SDP offer from UE-A to P-CSCF. P-CSCF then sends H.248 ADD requests to IMS-AGW to reserve connection points and create outgoing terminations T2 and T3. P-CSCF modifies the SDP offer to include 'altc' attributes and sends it to UE-A. UE-A responds with an SDP answer. P-CSCF then sends H.248 MOD requests to IMS-AGW to configure the connection points and create an incoming termination T1. P-CSCF modifies the SDP answer and sends it to UE-A. Finally, P-CSCF sends H.248 SUB requests to IMS-AGW to release the outgoing termination T3. + +Figure 6.2.20.1: Terminating session setup with insertion of the SDP attribute "altc" by the IMS-ALG + +Upon receipt of a session initiation request, the IMS-ALG shall extract the offerer's destination network address(es) and port number(s) from the SDP offer received from the calling party endpoint. Based on local policies, the IMS-ALG may decide to provide an alternative IP address and to insert then "altc" attributes in the SDP offer sent to the terminating side. The IMS-ALG shall then request the IMS-AGW to allocate transport resources for the terminating side (e.g. terminations T2 for IPv6 and T3 for IPv4) via two Reserve AGW Connection Point procedures, one per address type. + +NOTE: The IMS-AGW is "ALTC agnostic" and does not have any awareness about preferred and alternate IP connection resources as described in the in IETF RFC 6947 [59]. Moreover, there is not any context-internal topology between terminations T1, T2 and T3 (via the H.248 topology descriptor) defined: T1 is either implicitly interlinked with T2 or T3 dependent on the used H.248 Stream identifier values. However, such aspects are ignored due to the expected short-term aspects of the temporary context configuration with three terminations. + +Based on the responses received from the IMS-AGW, the IMS-ALG shall modify the offerer's destination addresses and/or ports initially contained in the SDP offer, insert the "altc" SDP attributes carrying the preferred and alternate IP addresses and propagate the session establishment toward the terminating party. + +On receipt of the SDP answer of the called party endpoint, the IMS-ALG shall pass the IP address, port and address type chosen by the called party endpoint for the session to the IMS-AGW in the Configure AGW Connection Point procedure and shall request the IMS-AGW to allocate transport resources (T1) for the calling party endpoint via the Reserve and Configure AGW Connection Point. Upon receiving the response from the IMS-AGW, the IMS-ALG shall modify the answerer's destination address(es) and/or port(s) contained in the application SDP answer and pass the information to the calling party endpoint. The IMS-ALG shall also request the IMS-AGW to release the transport resources (e.g. termination T3 with IPv4) reserved for the unused address type via the Release AGW Termination procedure. + +## 6.2.21 Video Region-of-Interest (ROI) + +### 6.2.21.1 Video Region-of-Interest (ROI) using FECC + +Figure 6.2.21.1.1 shows the message sequence chart example for indicating Video Region-of-Interest (ROI) using FECC. + +![Sequence diagram showing the procedure to indicate Video ROI using FECC between IMS-ALG and IMS-AGW.](c15cb6383bc35906e6b3c7c3aac621ed_img.jpg) + +``` + +sequenceDiagram + participant External + participant IMS-ALG + participant IMS-AGW + + Note right of IMS-AGW: Reserve AGW Connection Point + + External->>IMS-ALG: INVITE with SDP offer +["m=application port RTP/AVP x" "a=rtpmap:x h224/4800" "a=sendrecv"] + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=?, T= ?, Laddr = ?, Lport = ?, Local Resources] + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[Termination T2...] + IMS-ALG->>IMS-AGW: INVITE with SDP offer +["m=application port RTP/AVP x" "a=rtpmap:x h224/4800" "a=sendrecv"] + IMS-AGW-->>IMS-ALG: SDP answer +["m=application port RTP/AVP x" "a=rtpmap:x h224/4800" "a=sendrecv"] + Note right of IMS-AGW: Reserve and Configure AGW Connection Point + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=C, T= ?, Laddr = ?, Lport = ?] + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[Termination T1...] + IMS-ALG-->>External: SDP answer +["m=application port RTP/AVP x" "a=rtpmap:x h224/4800" "a=sendrecv"] + +``` + +The sequence diagram illustrates the interaction between an IMS-ALG and an IMS-AGW to indicate a Video ROI using FECC. The process begins with an external INVITE with an SDP offer. The IMS-ALG sends an H.248:ADD.req to the IMS-AGW to reserve an AGW connection point. The IMS-AGW responds with H.248:ADD.resp. The IMS-ALG then sends another INVITE with an SDP offer to the IMS-AGW. The IMS-AGW responds with an SDP answer. The IMS-ALG sends a second H.248:ADD.req to reserve and configure the AGW connection point. The IMS-AGW responds with H.248:ADD.resp. Finally, the IMS-ALG sends an SDP answer back to the external entity. + +Sequence diagram showing the procedure to indicate Video ROI using FECC between IMS-ALG and IMS-AGW. + +**Figure 6.2.21.1.1: Procedure to indicate Video ROI using FECC** + +This procedure is identical to that of clause 6.2.1. + +## 6.2.21.2 "Predefined ROI" mode + +Figure 6.2.21.2.1 shows the message sequence chart example for indicating Predefined ROI mode. + +![Sequence diagram showing the procedure to indicate Predefined ROI mode between IMS-ALG and IMS-AGW.](511f9b05a4c458937dd12c30936fd7d6_img.jpg) + +``` + +sequenceDiagram + participant External + participant IMS-ALG + participant IMS-AGW + + Note left of IMS-ALG: INVITE with SDP offer +["a=rtcp-fb: 3gpp-roi-predefined" +"a=extmap: URN=Predefined ROI" "a=predefined_ROI"] + External->>IMS-ALG: INVITE with SDP offer + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=?, T= ?, Laddr = ?, Lport = ?, +Local Resources, RTCP Feedback(Predefined ROI), Extended RTP header(Predefined ROI)] + Note right of IMS-AGW: Reserve AGW Connection Point + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[Termination T2...] + IMS-ALG->>IMS-AGW: INVITE with SDP offer +["a=rtcp-fb:3gpp-roi-predefined" "a=extmap: +URN=Predefined ROI" "a=predefined_ROI"] + IMS-AGW-->>IMS-ALG: SDP answer +["a=rtcp-fb:3gpp-roi-predefined" "a=extmap: +URN=Predefined ROI" "a=predefined_ROI"] + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=C, T= ?, Laddr = ?, Lport = ?, +Local Resources, RTCP Feedback(Predefined ROI), Extended RTP header(Predefined ROI)] + Note right of IMS-AGW: Reserve and Configure AGW Connection Point + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[Termination T1...] + IMS-ALG-->>External: SDP answer +["a=rtcp-fb:3gpp-roi-predefined" "a=extmap: +URN=Predefined ROI" "a=predefined_ROI"] + +``` + +The sequence diagram illustrates the interaction between an IMS-ALG and an IMS-AGW to indicate Predefined ROI mode. The process begins with an external INVITE with SDP offer containing specific ROI-related parameters. The IMS-ALG sends an H.248:ADD.req message to the IMS-AGW, which responds with H.248:ADD.resp. The IMS-ALG then sends another INVITE with SDP offer to the IMS-AGW, which responds with an SDP answer. Finally, the IMS-ALG sends another H.248:ADD.req message to the IMS-AGW, which responds with H.248:ADD.resp, and the IMS-ALG sends the final SDP answer back to the external entity. + +Sequence diagram showing the procedure to indicate Predefined ROI mode between IMS-ALG and IMS-AGW. + +**Figure 6.2.21.2.1: Procedure to indicate Predefined ROI mode** + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally requesting the IMS-AGW to support the RTCP feedback message capability for "Predefined ROI" type expressed by the parameter "3gpp-roi-predefined", as described in 3GPP TS 26.114 [21], and the RTP Header Extension capability for carriage of predefined ROI information as defined in IETF RFC 5285 [23] and 3GPP TS 26.114 [21]. + +### 6.2.21.3 "Arbitrary ROI" mode + +Figure 6.2.21.3.1 shows the message sequence chart example for indicating Arbitrary ROI mode. + +![Sequence diagram showing the procedure to indicate Arbitrary ROI mode between IMS-ALG and IMS-AGW.](e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg) + +``` + +sequenceDiagram + participant External + participant IMS-ALG + participant IMS-AGW + + Note right of IMS-AGW: Reserve AGW Connection Point + + External->>IMS-ALG: INVITE with SDP offer +["a=rtcp-fb: 3gpp-roi-arbitrary" +"a=extmap: URN=Arbitrary ROI"] + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=?, T= ?, Laddr = ?, Lport = ?, +Local Resources, RTCP Feedback(Arbitrary ROI), +Extended RTP header(Arbitrary ROI)] + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[Termination T2...] + IMS-ALG->>IMS-AGW: INVITE with SDP offer +["a=rtcp-fb: 3gpp-roi-arbitrary" +"a=extmap: URN=Arbitrary ROI"] + IMS-AGW-->>IMS-ALG: SDP answer +["a=rtcp-fb: 3gpp-roi-arbitrary" +"a=extmap: URN=Arbitrary ROI"] + Note right of IMS-AGW: Reserve and Configure AGW Connection Point + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=C, T= ?, Laddr = ?, Lport = ?, +Local Resources, RTCP Feedback(Arbitrary ROI), +Extended RTP header(Arbitrary ROI)] + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[Termination T1...] + IMS-ALG-->>External: SDP answer +["a=rtcp-fb: 3gpp-roi-arbitrary" +"a=extmap: URN=Arbitrary ROI"] + +``` + +The diagram illustrates the message exchange for indicating Arbitrary ROI mode. It starts with an INVITE with SDP offer from an external source to the IMS-ALG. The IMS-ALG then sends an H.248:ADD.req to the IMS-AGW. The IMS-AGW responds with H.248:ADD.resp. The IMS-ALG then sends another INVITE with SDP offer to the IMS-AGW. The IMS-AGW responds with an SDP answer. The IMS-ALG then sends another H.248:ADD.req to the IMS-AGW. The IMS-AGW responds with H.248:ADD.resp. Finally, the IMS-ALG sends an SDP answer back to the external source. Annotations on the right indicate that the first H.248:ADD.req is for reserving the AGW connection point, and the second H.248:ADD.req is for reserving and configuring the AGW connection point. + +Sequence diagram showing the procedure to indicate Arbitrary ROI mode between IMS-ALG and IMS-AGW. + +**Figure 6.2.21.3.1: Procedure to indicate Arbitrary ROI mode** + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally requesting the IMS-AGW to support the RTCP feedback message capability for "Arbitrary ROI" type expressed by the parameter "3gpp-roi-arbitrary", as described in 3GPP TS 26.114 [21], and the RTP Header Extension capability for carriage of arbitrary ROI information as defined in IETF RFC 5285 [23] and 3GPP TS 26.114 [21]. + +## 6.2.22 WebRTC + +### 6.2.22.1 Establishment of a WebRTC data channel + +See clause 6.2.10.6.2. + +### 6.2.22.2 Release of a WebRTC data channel + +The H.248 Context model for a WebRTC call in figure 6.2.10.6.2.1 is assumed. However, the example flow in this clause focuses on the WebRTC data channel part only. Thus, only H.248 Streams S1 (for de-aggregation of multiple data channels) and S2 (for MSRP traffic) are indicated subsequently. + +Figure 6.2.22.2.1 shows the message sequence chart example for the WIC originated procedure to release a WebRTC MSRP data channel following the procedures in clause 5.20.2.3.2. + +![Sequence diagram showing the call flow for the release of a single WebRTC data channel between WIC-A, IMS-ALG, and e-IMS-AGW. The diagram includes 22 steps involving SDP offers/answers, H.248 MOD/NOTIFY messages, and SCTP reset requests. Brackets on the left indicate logical groupings: 'Configure IMS Resources', 'Notify SCTP Stream Reset Result', 'Notify SCTP Stream Reset', and 'Configure IMS Resources'.](649426750a89fa0e5d7c1736d5cf72c6_img.jpg) + +Figure. 6.2.10.6.2.2: MSRP data channel with SCTP stream ID SCTPstreamID-a established. + +``` + +sequenceDiagram + participant WIC-A + participant IMS-ALG + participant e-IMS-AGW + + Note right of WIC-A: Figure. 6.2.10.6.2.2: MSRP data channel with SCTP stream ID SCTPstreamID-a established. + + WIC-A->>IMS-ALG: 1. SDP offer (c=IP1o, m= application P1o UDP/DTLS/SCTP webrtc-datachannel) + IMS-ALG-->>WIC-A: 2. Modify SDP offer + IMS-ALG->>e-IMS-AGW: 3. SDP offer (c=IP2o, m= 0 TCP/MSRP) + e-IMS-AGW-->>IMS-ALG: 4. SDP answer (c=IP1a, m= 0 TCP/MSRP) + IMS-ALG-->>WIC-A: 6. SDP answer (c=IP2a, m=application P2a UDP/DTLS/SCTP webrtc-datachannel) + IMS-ALG-->>IMS-ALG: 5. Modify SDP answer + + Note left of IMS-ALG: Configure IMS Resources + IMS-ALG->>e-IMS-AGW: 7. H.248 MOD req (C=C1, T=T1, groupse = ["SCTP 2"] Stream=1 ( strdeagg=[2] ) Stream=2 (scpid=SCTPstreamID-a) Signal (sctpreset/initreset(SCTPstreamID-a) ) Events(sctpreset/result) ) + e-IMS-AGW-->>IMS-ALG: 8. H.248 MOD resp (C=C1, T=T1, ) + + WIC-A->>IMS-ALG: 9. SCTP Outgoing SSN Reset Request (SCTPstreamID-a) + IMS-ALG-->>WIC-A: 10. SCTP Re-configuration Response + + Note left of IMS-ALG: Notify SCTP Stream Reset Result + IMS-ALG->>e-IMS-AGW: 11. H.248 NOTIFY req (C=C1, T=T1, ObservedEvent( sctpreset/result(SCTPstreamID-a) ) ) + e-IMS-AGW-->>IMS-ALG: 12. H.248 NOTIFY resp (C=C1, T=T1) + + WIC-A->>IMS-ALG: 13. SCTP Outgoing SSN Reset Request (SCTPstreamID-a) + IMS-ALG-->>WIC-A: 14. SCTP Re-configuration Response + + Note left of IMS-ALG: Notify SCTP Stream Reset + IMS-ALG->>e-IMS-AGW: 15. H.248 NOTIFY req (C=C1, T=T1, ObservedEvent( sctpreset/detreset(SCTPstreamID-a) ) ) + e-IMS-AGW-->>IMS-ALG: 16. H.248 NOTIFY resp (C=C1, T=T1) + + Note left of IMS-ALG: Configure IMS Resources + IMS-ALG->>e-IMS-AGW: 17. H.248 MOD req (C=C1, T=T2, Stream=2 ( Local(). Remote() ) ) + e-IMS-AGW-->>IMS-ALG: 18. Release Stream Endpoint for Stream 2 on Termination T2 + e-IMS-AGW-->>IMS-ALG: 19. H.248 MOD resp (C=C1, T=T2) + + Note left of IMS-ALG: Configure IMS Resources + IMS-ALG->>e-IMS-AGW: 20. H.248 MOD req (C=C1, T=T1, groupse = ["SCTP 2"] Stream=1 ( strdeagg=[] ) Stream=2 ( Local(). Remote() ) ) + e-IMS-AGW-->>IMS-ALG: 21. Release Stream Endpoint for Stream 2 on Termination T1 + e-IMS-AGW-->>IMS-ALG: 22. H.248 MOD resp (C=C1, T=T1) + +``` + +Sequence diagram showing the call flow for the release of a single WebRTC data channel between WIC-A, IMS-ALG, and e-IMS-AGW. The diagram includes 22 steps involving SDP offers/answers, H.248 MOD/NOTIFY messages, and SCTP reset requests. Brackets on the left indicate logical groupings: 'Configure IMS Resources', 'Notify SCTP Stream Reset Result', 'Notify SCTP Stream Reset', and 'Configure IMS Resources'. + +Figure 6.2.22.2.1: Call flow for the Release of a single WebRTC data channel + +NOTE: Steps 9, 10, 13 and 14: A data channel is constituted by a pair of unidirectional SCTP Streams (with the same SCTP Stream identifier value in above flow). The SCTP Outgoing SSN Reset Request procedure does reset a single SCTP Stream only (due to the configuration in this example), hence the procedure will be executed twice (towards and from remote WIC). + +### 6.2.22.3 Media Plane Optimization + +#### 6.2.22.3.1 Media Plane Optimization including DTLS layer for WIC originating call + +The H.248 Context model for a WebRTC call in figure 6.2.10.6.2.1 is assumed. However, the example flow in this clause focuses on the WebRTC data channel part only. Thus, only H.248 Streams S1 (for de-aggregation of multiple data channels) and S2 (for MSRP traffic) are indicated subsequently. + +Figure 6.2.22.3.1.1 shows the message sequence chart example for the WIC originated procedure to establish a WebRTC data channel with media plane optimization following the procedures in clause 5.20.3.2. + +![Sequence diagram showing the WIC originated procedure for WebRTC data channel establishment with media plane optimization including DTLS layer. The diagram involves three main entities: WIC-A, IMS-ALG, and e-IMS-AGW. The process includes SDP offers/answers, H.248 ADD/MOD requests/responses, and DTLS handshake messages. Annotations on the left indicate actions like 'Reserve AGW Connection Point', 'Configure AGW Connection Point', and 'Reserve and Configure AGW Connection Point'.](9ef15a4afab1416db28b91184862a3a5_img.jpg) + +**WIC-A** + +1. SDP offer [c=IP1o, m= application P1o UDP/DTLS/SCTP webrtc-datachannel, a=max-message-size:UE-Sa, a=sctp-port:UE-Pa, a=setup:actpass, a=tls-id:wicx, a=fingerprint:UE-a, a=connection:new, a=dcmmap:SCTPstreamID-a subprotocol=MSRP, a=dcsa:SCTPstreamID-a msrp-cema, a=dcsa:SCTPstreamID-a setup=actpass, a=dcsa:SCTPstreamID-a path:path-a] + +Reserve AGW Connection Point + +**IMS-ALG** + +2. H.248 ADD req [C=?, T=?, Stream=2 {Local (LAddr=?, LPort=?, m=TCP)}] + +**e-IMS-AGW** + +3. Create outgoing termination T2 + +4. H.248 ADD resp [C=C1, T=T2, Stream=2 { Local (LAddr=IP2o, LPort=P2o)}] + +5. Modify SDP offer + +6. SDP offer [c=IP2o, a=tra-contact=IP2o, a=tra-media-line-number=x, m=P2o TCP/MSRP, a=setup:actpass, a=msrp-cema, a=path:path-a, a=tra-SCTP-association=1, a=tra-m-line= application P2o UDP/DTLS/SCTP webrtc-datachannel, a=tra-att=max-message-size:UE-Sa, a=tra-att=sctp-port:UE-Pa, a=tra-att=setup:actpass, a=tra-att=connection:new, a=tra-att=tls-id:wicx, a=tra-att=fingerprint:UE-a, a=tra-att=dcmmap:SCTPstreamID-a subprotocol=MSRP, a=tra-att=dcsa:SCTPstreamID-a msrp-cema, a=tra-att=dcsa:SCTPstreamID-a setup=actpass, a=tra-att=dcsa:SCTPstreamID-a path:path-a] + +7. SDP answer [c=IP1a, m=P1a TCP/MSRP, a=tra-SCTP-association=1, a=tra-m-line=application P1a UDP/DTLS/SCTP webrtc-datachannel, a=tra-att=max-message-size:RSa, a=tra-att=sctp-port:RPa, a=tra-att=setup:active, a=tra-att=connection:new, a=tra-att=tls-id:Rid, a=tra-att=fingerprint:R-a, a=tra-att=dcmmap:SCTPstreamID-a subprotocol=MSRP, a=tra-att=dcsa:SCTPstreamID-a msrp-cema, a=tra-att=dcsa:SCTPstreamID-a setup:active, a=tra-att=dcsa:SCTPstreamID-a path:path-b] + +Configure AGW Connection Point + +8. H.248 MOD req [C=C1, T=T2, Stream=2 { Remote (RAddr=IP1a, RPort=P1a) Local (m=UDP)}] + +9. Configure outgoing termination T2 + +10. H.248 MOD resp [C=C1, T=T2] + +11. H.248 ADD req [C=C1, T=?, Stream=2 { Remote (RAddr=IP1o, RPort=P1o, m=UDP), Local (LAddr=?, LPort=?, m=UDP)}] + +Reserve and Configure AGW Connection Point + +12. Create incoming termination T1 + +13. H.248 ADD resp [C=C1, T=T1, Stream=2 { Local (LAddr=IP2a, LPort=P2a, m=UDP)}] + +14. Modify SDP answer + +15. SDP answer [c=IP2a, m=application P2a UDP/DTLS/SCTP webrtc-datachannel, a=max-message-size:RSa, a=sctp-port:RPa, a=setup:active, a=connection:new, a=tls-id:Rid, a=fingerprint:R-a, a=dcmmap:SCTPstreamID-a subprotocol=MSRP, a=dcsa:SCTPstreamID-a msrp-cema, a=dcsa:SCTPstreamID-a setup:active, a=dcsa:SCTPstreamID-a path:path-b] + +16. DTLS ClientHello + +17. Remaining messages of DTLS handshake + +18. SCTP association establishment + +Sequence diagram showing the WIC originated procedure for WebRTC data channel establishment with media plane optimization including DTLS layer. The diagram involves three main entities: WIC-A, IMS-ALG, and e-IMS-AGW. The process includes SDP offers/answers, H.248 ADD/MOD requests/responses, and DTLS handshake messages. Annotations on the left indicate actions like 'Reserve AGW Connection Point', 'Configure AGW Connection Point', and 'Reserve and Configure AGW Connection Point'. + +NOTE: Message 16 (DTLS ClientHello) can be received by the eIMS-AGW from the remote peer before the eIMS-AGW is configured to pass it (in steps 8.-13.) and will then be dropped by the eIMS-AGW. However, the remote peer will then resend message 16 after a timeout while waiting for a response. + +Figure 6.2.22.3.1.1: WIC originated procedure for WebRTC data channel establishment with media plane optimization including DTLS layer + +### 6.2.22.3.2 Media Plane Optimization excluding DTLS layer for WIC originating call + +The H.248 Context model for a WebRTC call in figure 6.2.10.6.2.1 is assumed. However, the example flow in this clause focuses on the WebRTC data channel part only. Thus, only H.248 Streams S1 (for de-aggregation of multiple data channels) and S2 (for MSRP traffic) are indicated subsequently. Furthermore, there is an additional termination T3 towards the IMS core network to handle DTLS. + +Figure 6.2.22.3.2.1 shows the message sequence chart example for the WIC originated procedure to establish a WebRTC data channel with media plane optimization following the procedures in clause 5.20.3.2. + +![Sequence diagram showing the WIC originated procedure for WebRTC data channel establishment with media plane optimization excluding DTLS layer. The diagram involves three main entities: WIC-A, IMS-ALG, and e-IMS-AGW. The process includes SDP offers/answers, H.248 ADD/SUB/MOD requests, and internal termination creation steps. Brackets on the left indicate actions like 'Reserve AGW Connection Point', 'Configure AGW Connection Point', 'Release AGW Connection Point', and 'Reserve and Configure AGW Connection Point'. The final steps involve DTLS ClientHello and SCTP association establishment between the UE and the GW.](e01c6273c4177746475715ee9c17a882_img.jpg) + +**Sequence of Messages:** + +- WIC-A sends an SDP offer to IMS-ALG. +- IMS-ALG sends an H.248 ADD req to e-IMS-AGW. +- e-IMS-AGW creates an outgoing termination T2. +- e-IMS-AGW sends an H.248 ADD resp to IMS-ALG. +- IMS-ALG sends another H.248 ADD req to e-IMS-AGW. +- e-IMS-AGW creates an outgoing termination T3. +- e-IMS-AGW sends an H.248 ADD resp to IMS-ALG. +- IMS-ALG sends a Modify SDP offer to WIC-A. +- IMS-ALG sends an SDP offer to e-IMS-AGW. +- e-IMS-AGW sends an SDP answer to IMS-ALG. +- IMS-ALG sends an H.248 MOD req to e-IMS-AGW. +- e-IMS-AGW configures the outgoing termination T3. +- e-IMS-AGW sends an H.248 MOD resp to IMS-ALG. +- IMS-ALG sends an H.248 SUB req to e-IMS-AGW. +- e-IMS-AGW removes the outgoing termination T2. +- e-IMS-AGW sends an H.248 SUB resp to IMS-ALG. +- IMS-ALG sends an H.248 ADD req to e-IMS-AGW. +- e-IMS-AGW creates an incoming termination T1. +- e-IMS-AGW sends an H.248 ADD resp to IMS-ALG. +- IMS-ALG sends a Modify SDP answer to WIC-A. +- e-IMS-AGW sends a DTLS ClientHello to WIC-A. +- WIC-A sends a DTLS ClientHello to e-IMS-AGW. +- WIC-A and e-IMS-AGW exchange remaining messages of the DTLS handshake. +- WIC-A and e-IMS-AGW perform SCTP association establishment. + +**Annotations:** + +- Reserve AGW Connection Point:** Associated with steps 2-4 and 5-7. +- Configure AGW Connection Point:** Associated with steps 11-13. +- Release AGW Connection Point:** Associated with steps 14-16. +- Reserve and Configure AGW Connection Point:** Associated with steps 17-19. + +Sequence diagram showing the WIC originated procedure for WebRTC data channel establishment with media plane optimization excluding DTLS layer. The diagram involves three main entities: WIC-A, IMS-ALG, and e-IMS-AGW. The process includes SDP offers/answers, H.248 ADD/SUB/MOD requests, and internal termination creation steps. Brackets on the left indicate actions like 'Reserve AGW Connection Point', 'Configure AGW Connection Point', 'Release AGW Connection Point', and 'Reserve and Configure AGW Connection Point'. The final steps involve DTLS ClientHello and SCTP association establishment between the UE and the GW. + +Figure 6.2.22.3.2.1: WIC originated procedure for WebRTC data channel establishment with media plane optimization excluding DTLS layer + +## 6.2.23 RTP-level pause and resume + +Figure 6.2.23.1 shows the message sequence chart example for indicating RTP-level pause and resume. + +![Sequence diagram showing the procedure to indicate RTP-level pause and resume between an IMS-ALG and an IMS-AGW.](2df1e34671c73d7c0d047d4e9009251e_img.jpg) + +``` + +sequenceDiagram + participant External + participant IMS-ALG + participant IMS-AGW + + Note right of External: INVITE with SDP offer +["m=video port RTP/AVPF x" +"a=rtpmap:x ..." "a=rtcp-fb:* +ccm pause"] + + External->>IMS-ALG: INVITE with SDP offer + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=?, T=?, Laddr=?, Lport=?, +Local Resources] + Note right of IMS-AGW: Reserve AGW +Connection Point + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[C=C1,T=T2, ...] + IMS-ALG->>IMS-AGW: INVITE with SDP offer +["m=video port RTP/AVPF x" +"a=rtpmap:x ..." "a=rtcp-fb:* ccm pause"] + IMS-AGW-->>IMS-ALG: SIP message with SDP answer +["m=video port RTP/AVPF x" +"a=rtpmap:x ..." "a=rtcp-fb:* ccm pause"] + IMS-ALG->>IMS-AGW: H.248:MOD.req[C=C1, T=T2, LD(CCM pause- +resume{a=rtcp-fb:* ccm pause}) RD(Raddr = ra2, +Rport = rp2 CCM pause-resume{a=rtcp-fb:* ccm +pause})] + Note right of IMS-AGW: Configure AGW +Connection Point + IMS-AGW-->>IMS-ALG: H.248:MOD.resp[C=C1, T=T2] + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=C1, T=?, LD(Laddr=?, Lport= +? CCM pause-resume{a=rtcp-fb:* ccm pause}) +RD(Raddr = ra1, Rport = rp1 CCM pause- +resume{a=rtcp-fb:* ccm pause})] + Note right of IMS-AGW: Reserve and +Configure AGW +Connection Point + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[C=C1, T=T1, ...] + IMS-ALG-->>External: SIP message with SDP answer +["m=video port RTP/AVPF x" +"a=rtpmap:x ..." "a=rtcp-fb:* +ccm pause"] + +``` + +The sequence diagram illustrates the interaction between an IMS-ALG and an IMS-AGW for RTP-level pause and resume. It begins with an external INVITE with an SDP offer containing "ccm pause". The IMS-ALG sends an H.248:ADD.req to the IMS-AGW to reserve a connection point. The IMS-AGW responds with H.248:ADD.resp. The IMS-ALG then forwards the INVITE to the IMS-AGW, which returns a SIP answer. Next, the IMS-ALG sends an H.248:MOD.req to configure the connection point with pause-resume capabilities. The IMS-AGW responds with H.248:MOD.resp. Finally, the IMS-ALG sends another H.248:ADD.req to reserve and configure another connection point, receiving H.248:ADD.resp in return, and then forwards the SIP answer to the external party. + +Sequence diagram showing the procedure to indicate RTP-level pause and resume between an IMS-ALG and an IMS-AGW. + +Figure 6.2.23.1: Procedure to indicate RTP-level pause and resume + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally requesting the IMS-AGW to transparently forward the RTCP "CCM PAUSE" packets (as defined in IETF RFC 7728 [79]) between incoming and outgoing network. + +## 6.2.24 RTCP Codec Control Commands and Indications + +Figure 6.2.24.1 shows the message sequence chart example for indicating "RTCP Codec Control Commands and Indications". + +![Sequence diagram showing the procedure to indicate RTCP Codec Control Commands and Indications between IMS-ALG and IMS-AGW.](c0438093a10a593c42106b1e5dbb4331_img.jpg) + +``` + +sequenceDiagram + participant External + participant IMS-ALG + participant IMS-AGW + + Note left of IMS-ALG: INVITE with SDP offer +["m=video port RTP/AVPF x" +"a=rtpmap:x ... "a=rtcp-fb:* +ccm fir" "a=rtcp-fb:* ccm +tmmbr"] + External->>IMS-ALG: INVITE with SDP offer + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=?, T= ?, Laddr = ?, Lport = ?, +Local Resources] + Note right of IMS-AGW: Reserve AGW +Connection Point + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[C=C1,T=T2, ...] + Note left of IMS-ALG: INVITE with SDP offer +["m=video port RTP/AVPF x" "a=rtpmap:x +..." "a=rtcp-fb:* ccm fir" "a=rtcp-fb:* ccm +tmmbr"] + IMS-ALG->>External: INVITE with SDP offer + Note left of IMS-ALG: SIP message with SDP answer +["m=video port RTP/AVPF x" "a=rtpmap:x +..." "a=rtcp-fb:* ccm fir" "a=rtcp-fb:* ccm +fir" "a=rtcp-fb:* ccm tmmbr"] + External-->>IMS-ALG: SIP message with SDP answer + IMS-ALG->>IMS-AGW: H.248:MOD.req[C=C1, T=T2, LD( CCM +BASE{a=rtcp-fb:* ccm fir, a=rtcp-fb:* ccm tmmbr}) +RD(Raddr = ra2, Rport = rp2 CCM BASE{a=rtcp- +fb:* ccm fir, a=rtcp-fb:* ccm tmmbr} )] + Note right of IMS-AGW: Configure AGW +Connection Point + IMS-AGW-->>IMS-ALG: H.248:MOD.resp[C=C1, T=T2] + Note left of IMS-ALG: H.248:ADD.req[C=C1, T= ?, LD(Laddr = ?, Lport += ? CCM BASE{a=rtcp-fb:* ccm fir, a=rtcp-fb:* +ccm tmmbr}) RD(Raddr = ra1, Rport = rp1 CCM +BASE{a=rtcp-fb:* ccm fir, a=rtcp-fb:* ccm +tmmbr})] + IMS-ALG->>IMS-AGW: H.248:ADD.req + Note right of IMS-AGW: Reserve and +Configure AGW +Connection Point + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[C=C1, T=T1, ...] + Note left of IMS-ALG: SIP message with SDP answer +["m=video port RTP/AVPF x" +"a=rtpmap:x ... "a=rtcp-fb:* +ccm fir" "a=rtcp-fb:* ccm +tmmbr"] + IMS-ALG-->>External: SIP message with SDP answer + +``` + +Sequence diagram showing the procedure to indicate RTCP Codec Control Commands and Indications between IMS-ALG and IMS-AGW. + +Figure 6.2.24.1: Procedure to indicate RTCP Codec Control Commands and Indications + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally indicates that the IMS-AGW shall be prepared to receive and is allowed to send the RTCP CCM "FIR" and/or "TMMBR/TMMBN" feedback messages (as defined in IETF RFC 5104 [78]). + +## 6.2.25 Delay Budget Information (DBI) + +Figure 6.2.25.1 shows a message sequence chart example for indicating DBI. + +![Sequence diagram showing the procedure to indicate DBI between IMS-ALG and IMS-AGW.](0eb348bf17d67bf96326e07011d1c1ad_img.jpg) + +``` + +sequenceDiagram + participant Ext_L as External (Left) + participant IMS-ALG + participant IMS-AGW + participant Ext_R as External (Right) + + Ext_L->>IMS-ALG: INVITE with SDP offer +["m=audio port RTP/AVPF x" +"a=rtpmap:x ..." "a=rtcp-fb:* +3gpp-delay-budget"] + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=?, T= ?, Laddr = ?, Lport = ?, +Local Resources] + Note right of IMS-AGW: Reserve AGW +Connection Point + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[C=C1,T=T2, ...] + IMS-ALG->>Ext_R: INVITE with SDP offer +["m=audio port RTP/AVPF x" "a=rtpmap:x +..." "a=rtcp-fb:* 3gpp-delay-budget"] + Ext_R-->>IMS-ALG: SIP message with SDP answer +["m=audio port RTP/AVPF x" "a=rtpmap:x +..." "a=rtcp-fb:* 3gpp-delay-budget"] + IMS-ALG->>IMS-AGW: H.248:MOD.req[C=C1, T=T2, LD(DBI{a=rtcp-fb:* +3gpp-delay-budget}) RD(Raddr = ra2, Rport = rp2 +DBI{a=rtcp-fb:* 3gpp-delay-budget})] + Note right of IMS-AGW: Configure AGW +Connection Point + IMS-AGW-->>IMS-ALG: H.248:MOD.resp[C=C1, T=T2] + IMS-ALG->>IMS-AGW: H.248:ADD.req[C=C1, T= ?, LD(Laddr = ?, Lport = +? DBI{a=rtcp-fb:* 3gpp-delay-budget}) RD(Raddr = +ra1, Rport = rp1 DBI{a=rtcp-fb:* 3gpp-delay- +budget})] + Note right of IMS-AGW: Reserve and +Configure AGW +Connection Point + IMS-AGW-->>IMS-ALG: H.248:ADD.resp[C=C1, T=T1, ...] + IMS-ALG-->>Ext_L: SIP message with SDP answer +["m=audio port RTP/AVPF x" +"a=rtpmap:x ..." "a=rtcp-fb:* +3gpp-delay-budget"] + +``` + +Sequence diagram showing the procedure to indicate DBI between IMS-ALG and IMS-AGW. + +**Figure 6.2.25.1: Procedure to indicate DBI** + +This procedure is identical to that of clause 6.2.1 apart from the IMS-ALG optionally requesting the IMS-AGW to transparently forward the RTCP feedback DBI packets (as defined in 3GPP TS 26.114 [21]) between incoming and outgoing network. + +# 7 Charging + +The charging is specified in 3GPP TS 32.260 [5]. No requirements are identified for the Iq interface. + +--- + +## 8 Messages/Procedures and Contents + +### 8.1 General + +This clause describes logical signalling procedures between the IMS-ALG and IMS-AGW. The procedures within this clause are intended to be implemented using the standard H.248 procedure as defined in ITU recommendation H.248.1 [9] with appropriate parameter combinations. + +NOTE: Whenever the stage 2 description is referring to a "(stage 2) information element", then there is the premise of a one-to-one mapping to a stage 3 signalling element. + +## 8.2 Reserve and Configure AGW Connection Point + +This procedure is used to reserve multimedia-processing resources for the Iq interface connection. + +**Table 8.2.1: Procedures between IMS-ALG and IMS-AGW: Reserve and Configure AGW Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------------|-----------|----------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve and Configure AGW Connection Point | IMS-ALG | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Emergency Call Indicator | O | This information element identifies the call as emergency call that requires a preferential handling. | +| | | Priority information | O | This information element requests the IMS-AGW to apply priority treatment for the terminations and bearer connections in the specified context. | +| | | Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new bearer termination for the bearer to be established. | +| | | Local IP Resources | O | This information element indicates the resource(s) for which the IMS-AGW shall be prepared to receive user data. May be excluded (i.e. "-" is used in SDP m-line) if no transcoding or media related functions are required.

For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. | +| | | ReserveValue | O | This information element indicates if multiple local resources are to be reserved.

This information element shall be included if a speech codec and auxiliary payload types are configured. | +| | | Remote IP Resources | O | This information element indicates the resource(s) for which the IMS-AGW shall send data.

For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream.

May be excluded (i.e. "-" is used in SDP m-line) if no transcoding or media related functions are required. | +| | | Local Connection Address Request | M | This information element requests an IP address and port number(s) on the IMS-AGW that the remote end can send user plane data to.

For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. | + +| | | | +|-------------------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Remote Connection Address | M | This information element indicates the remote IP address and port number(s) that the IMS-AGW can send user plane data to.

For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. | +| Notify termination heartbeat | M | This information element requests termination heartbeat indications. This information element shall be included when requesting a new bearer termination. Otherwise the information element is optional. | +| Notify Released Bearer | O | This information element requests a notification of a released bearer. | +| Latching Requirement | O | This information element indicates that the IMS-AGW should (re)latch onto the address of received media packets to determine the corresponding destination address. | +| IP Realm Identifier | O | This information element indicates the IP realm of the bearer termination. | +| Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This is required if a range of remote source address filtering is required. | +| Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | +| Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. (NOTE 1) | +| Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. (NOTE 1) | +| Traffic Policing Required | O | This information element indicates that policing of the media flow is required. | +| Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 2).. | +| Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 2). | +| Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the bearer termination. | +| DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the bearer termination shall be copied from the received value or set to a specific value. | +| Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | + +| | | | | +|--|--------------------------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Media Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| | Media Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| | RTCP handling | O | This information element is present if IMS-ALG wants to explicitly control the reservation of RTCP resources (NOTE 4). | +| | RTP/RTCP transport multiplexing | C | This information element requests the IMS-AGW to apply the RTP/RTCP transport multiplexing. This information element may only be present if RTCP handling is required. | +| | Explicit RTCP transport address | C | This information element indicates the remote RTCP port and optionally the remote network address where to send RTCP packets. This information element may only be present if RTCP handling is required. | +| | Local cryptographic SDES attribute | C | This information element is present if IMS-ALG wants that the media is encrypted and/or integrity protected by the IMS-AGW (NOTE 3). It indicates the SDES local cryptographic parameters such as key(s) | +| | Remote cryptographic SDES attribute | C | This information element is present if IMS-ALG wants that the media is decrypted, and/or integrity checked by the IMS-AGW (NOTE 3). It indicates the SDES remote cryptographic parameters such as key(s) | +| | ECN Enable | O | This information element requests the IMS-AGW to apply ECN procedures. | +| | ECN Initiation Method | C | This information element specifies the ECN Initiation method and requests the IMS-AGW to perform IP header settings as an ECN endpoint, or indicates that ECN bits shall be passed transparently. It may be included only if ECN is enabled. | +| | Notify ECN Failure Event | C | This information element requests a notification if a ECN failure occurs due to ECN. It may only be supplied if ECN is enabled and the IMS-AGW acts as ECN endpoint. | +| | Extended RTP Header for CVO | O | This information element requests the IMS-AGW to pass on the CVO extended RTP header as defined by IETF RFC 5285 [23]. | +| | Extended RTP Header for Sent ROI | O | This information element requests the IMS-AGW to pass on the ROI extended RTP header for carriage of predefined and/or arbitrary ROI information as defined by IETF RFC 5285 [23] and 3GPP TS 26.114 [21]. | +| | Predefined ROI | O | This information element requests the IMS-AGW to support the RTCP feedback message capability for "Predefined ROI" type expressed by the parameter "3gpp-roi-predefined", as described in 3GPP TS 26.114 [21]. | +| | Arbitrary ROI | O | This information element requests the IMS-AGW to support the RTCP feedback message capability for "Arbitrary ROI" type expressed by the parameter "3gpp-roi-arbitrary", as described in 3GPP TS 26.114 [21]. | +| | Generic Image Attributes | O | This information element indicates image attributes (e.g. image size) as defined by IETF RFC 6236 [24]. | + +| | | | +|------------------------------------------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Local certificate fingerprint Request | O | This information element is present if the IMS-ALG wants that the media is decrypted, and/or integrity protected by the IMS-AGW (NOTE 3). It requests the IMS-AGW to provide a local certificate fingerprint. | +| Remote certificate fingerprint | O | This information element is present if the IMS-ALG wants that the media is decrypted, and/or integrity checked by the IMS-AGW (NOTE 3). It indicates the remote certificate fingerprint. | +| Establish (D)TLS session | O | This information element requests the IMS-AGW to take the (D)TLS client role and to initiate the establishment of the (D)TLS session. (NOTE 3) | +| Notify (D)TLS session establishment Failure Event | O | This information element requests a notification if a (D)TLS session establishment failure occurs. (NOTE 3) | +| TCP State-aware Handling Indicator and Setup Direction | C | This information element indicates that TCP state-aware handling is required and indicates the TCP setup direction. It may only be included if the IMS-AGW supports TCP state-aware handling. | +| Discard Incoming TCP Connection Establishment Requests Indicator | C | This information element indicates whether incoming TCP connection establishment requests (TCP SYN) shall be discarded. It may only be included if the IMS-AGW supports TCP state-aware handling and discarding incoming TCP connection establishment requests. | +| Forward Incoming TCP Connection Establishment Requests Indicator | C | This information element indicates for a given termination to use the incoming TCP connection establishment request (TCP SYN) at that termination as a trigger for sending a TCP connection establishment request at the interconnected termination in the same context. It may only be included if the IMS-AGW supports TCP state-aware handling and the Forward Incoming TCP Connection Establishment Requests Indicator. | +| Notify TCP Connection Establishment Failure Event | C | This information element requests a notification if a TCP connection establishment failure occurs. It may only be included if the IMS-AGW supports TCP state-aware handling. | +| STUN server request | O | This information element is present if IMS-ALG requests the IMS-AGW to answer STUN connectivity checks for ICE. | +| ICE Connectivity Check | C | This information element requests the IMS-AGW to perform ICE connectivity check as defined by IETF RFC 5245 [39]. It is only applicable for full ICE. | +| Notify ICE Connectivity Check Result | C | This information element requests a notification of ICE connectivity check result. It is only applicable for full ICE. | +| Notify New Peer Reflexive Candidate | C | This information element requests a notification of new peer reflexive candidate was discovered during a connectivity check. It is only applicable for full ICE. | +| ICE password request | O | This information element is present if IMS-ALG requests an ICE password. | +| ICE Ufrag request | O | This information element is present if IMS-ALG requests an ICE ufrag. | +| ICE host candidate request | O | This information element is present if IMS-ALG requests an ICE host candidate. | +| ICE received candidate | O | This information element is present if IMS-ALG indicates a received candidate for ICE. | + +| | | | +|--------------------------------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| ICE received password | O | This information element is present if IMS-ALG indicates a received password for ICE. | +| ICE received Ufrag | O | This information element is present if IMS-ALG indicates a received Ufrag for ICE. | +| MSRP Path | O | This information element is present for application-aware MSRP Interworking. It provides the path information that the IMS-AGW shall insert in the MSRP layer "To-Path" Information element. | +| Application-aware MSRP interworking request | O | This information element is present if IMS-ALG requests the IMS-AGW to perform application-aware MSRP Interworking. | +| Notify STUN consent freshness test failure Event | O | This information element requests a notification if a STUN consent freshness test failure occurs (full ICE only). | +| STUN consent freshness test request | O | This information element is present if eP-CSCF requests the eIMS-AGW to perform a STUN consent freshness test (full ICE only). | +| Local SCTP Port Request | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an SCTP association. It requests the IMS-AGW to provide a local SCTP Port. | +| Remote SCTP Port | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an SCTP association. It indicates the remote SCTP port. | +| Local SCTP maximum message size Request | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an SCTP association. It requests the IMS-AGW to provide a local max message size. | +| Remote SCTP maximum message size | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an SCTP association. It indicates the remote max message size. | +| SCTP Group Semantics | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an SCTP association. It indicates the H.248 component streams that are grouped in the same SCTP association. | +| SCTP stream deaggregation | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an SCTP association. It indicates the H.248 component streams that transport media that are to be deaggregated from the H.248 deaggregation stream used to control the SCTP association. | +| SCTP stream ID | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an WEBRTC data channel. It indicates the SCTP stream ID to be used for that data channel. | +| Local Dcmmap | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish the WEBRTC data channel. It indicates the information within an SDP "dcmmap" attribute sent towards the remote peer, including the Subprotocol to exchange via the data channel. | +| Remote Dcmmap | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish the WEBRTC data channel. It indicates the information within an SDP "dcmmap" attribute received from the remote peer, including the Subprotocol to exchange via the data channel. | + +| | | | | | +|------------------------------------------------|---------|------------------------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Local Dcsa | O | This information element can be present if the IMS-ALG requests the IMS-AGW to establish the WEBRTC data channel and to handle its contents in an application-aware manner. It indicates the information within an SDP "dcsa" attribute sent towards the remote peer, encapsulating a subprotocol specific SDP attribute. | +| | | Remote Dcsa | O | This information element can be present if the IMS-ALG requests the IMS-AGW to establish the WEBRTC data channel and to handle its contents in an application-aware manner. It indicates the information within an SDP "dcsa" attribute received from the remote peer, encapsulating a subprotocol specific SDP attribute. | +| | | Received SCTP Stream Reset Request | O | This information element is present if the eP-CSCF (IMS-ALG) requests the eIMS-AGW to establish the WEBRTC data channel. It requests the eIMS-AGW to provide a notification when receiving an SCTP Stream reset request and to autonomously answer that SCTP Stream reset request | +| | | Allowed RTCP APP message types | O | This information element is present if IMS-ALG allows the IMS-AGW to send RTCP APP packets of the indicated types. The IMS-AGW shall not send other RTCP APP packets. If the parameter is not supplied, the IMS-AGW shall not send any RTCP APP packets. | +| | | SDPCapNeg configuration | O | This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| | | Additional Bandwidth Properties | O | This information element indicates additional bandwidth properties using "a=bw-info" SDP attribute(s) as defined by 3GPP TS 26.114 [21]. | +| | | CCM BASE | O | This information element indicates that the IMS-AGW shall be prepared to receive and is allowed to send, respectively, the RTCP feedback "CCM FIR" and/or "CCM TMMBR" messages (defined in IETF RFC 5104 [78]). | +| | | CCM pause-resume | O | This information element indicates to the IMS-AGW that RTCP feedback "CCM PAUSE-RESUME" messages shall be passed transparently. | +| | | DBI | O | This information element indicates to the IMS-AGW that RTCP DBI feedback messages (as defined in 3GPP TS 26.114 [21] clause 7.3.8) shall be passed transparently. | +| Reserve and Configure AGW Connection Point Ack | IMS-AGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +| | | | | +|--|-------------------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Local IP Resources | C | This information element indicates the resource(s) for which the IMS-AGW shall be prepared to receive user data. This IE shall be present if it was contained in the request. If the IE was not contained in the request, it may be present in the reply.

For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. | +| | Remote IP Resources | O | This information element indicates the resource(s) for which the IMS-AGW shall send data.

For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. | +| | Local Connection Address | M | This information element indicates the IP address and port number(s) the IMS-AGW shall receive user plane data from IMS.

For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. | +| | Remote Connection Address | O | This information element indicates the remote IP address and port number(s) that the IMS-AGW can send user plane data to.

For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. | +| | Local cryptographic SDES attribute | C | This information element may be present only if it was contained in the request. It indicates the SDES local cryptographic parameters such as key(s) | +| | Remote cryptographic SDES attribute | C | This information element may be present only if it was contained in the request. It indicates the SDES remote cryptographic parameters such as key(s) | +| | Local certificate fingerprint | C | This information element may be present only if the Local certificate fingerprint Request was contained in the request. It indicates the local certificate fingerprint. (NOTE 3) | +| | ICE password | C | This information element shall be present only if it was contained in the request. It indicates the ICE password assigned by the IMS-AGW. | +| | ICE Ufrag | C | This information element shall be present only if it was contained in the request. It indicates the ICE Ufrag assigned by the IMS-AGW. | +| | ICE host candidate | C | This information element shall be present only if it was contained in the request. It indicates the ICE host candidate assigned by the IMS-AGW. | +| | Local SCTP Port | C | This information element may be present only if the Local SCTP Port Request was contained in the request. It indicates the local SCTP Port. | + +| | | | | | | +|----------------------------------------------------------------------------------|--|---------------------------------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| +| | | Local SCTP maximum message size | C | This information element may be present only if the Local max message size Request was contained in the request. It indicates the local max message size. | | +| | | ICE lite indication | C | This information element shall be present only if an ICE host candidate request was contained in the request, and the IMS-AGW supports ICE lite, but not full ICE. It indicates that the IMS-AGW only supports ICE lite. | | +| | | SDPCapNeg configuration | C | This information element shall be present only if it was contained in the request. It provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | | +| NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive. | | | | | | +| NOTE 2: One of those IEs shall at least be present when policing is required. | | | | | | +| NOTE 3: This IE may only be present for access network terminations. | | | | | | +| NOTE 4: The concerned RTCP resource component is related to the RTCP port value. | | | | | | + +## 8.3 Reserve AGW Connection Point Procedure + +This procedure is used to reserve local connection addresses and local resources in IMS-AGW. + +**Table 8.3.1: Procedures between IMS-ALG and IMS-AGW: Reserve AGW Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------|-----------|----------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Reserve AGW Connection Point | IMS-ALG | Context /Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Emergency Call Indicator | O | This information element identifies the call as emergency call that requires a preferential handling. | +| | | Priority information | O | This information element requests the IMS-AGW to apply priority treatment for the terminations and bearer connections in the specified context. | +| | | Bearer Termination Request | M | This information element requests a new bearer termination | +| | | Local IP Resources | O | This information element indicates the resource(s) for which the IMS-AGW shall be prepared to receive user data.

For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream.

May be excluded (i.e. "-" is used in SDP m-line) if no transcoding or media related functions are required. | +| | | ReserveValue | O | This information element indicates if multiple local resources are to be reserved.

This information element shall be included if a speech codec and auxiliary payload types are configured. | +| | | Local Connection Address Request | M | This information element requests an IP address and port number(s) on the IMS-AGW that the remote end can send user plane data to.

For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. | +| | | Notify termination heartbeat | M | This information element requests termination heartbeat indications. | +| | | Notify Released Bearer | O | This information element requests a notification of a released bearer. | +| | | Latching Requirement | O | This information element indicates that the IMS-AGW should (re)latch onto the address of received media packets to determine the corresponding destination address. | +| | | IP Realm Identifier | O | This information element indicates the IP realm of the bearer termination. | +| | | Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| | | Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This is required if a range of remote source address filtering is required. | + +| | | | +|--------------------------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | +| Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. (NOTE 1) | +| Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. (NOTE 1) | +| Policing Required | O | This information element indicates that policing of the media flow is required. | +| Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 2). | +| Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 2). | +| Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the bearer termination. | +| DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the bearer termination should be copied from the received value or set to a specific value. | +| Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | +| Media Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| Media Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | +| RTCP handling | O | This information element is present if IMS-ALG wants explicitly control the reservation of RTCP resources by the IMS-AGW. | +| RTP/RTCP transport multiplexing | C | This information element requests the IMS-AGW to apply the RTP/RTCP transport multiplexing. This information element may only be present if RTCP handling is required. | +| Local cryptographic SDES attribute | C | This information element is present if IMS-ALG wants that the media is encrypted and/or integrity protected by the IMS-AGW (NOTE 3). It indicates the SDES local cryptographic parameters such as key(s). | +| ECN Enable | O | This information element requests the IMS-AGW to apply ECN procedures. | +| ECN Initiation Method | C | This information element specifies the ECN Initiation method and requests the IMS-AGW to perform IP header settings as an ECN endpoint, or indicates that ECN bits shall be passed transparently. It may be included only if ECN is enabled. | + +| | | | | +|--|------------------------------------------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | Notify ECN Failure Event | C | This information element requests a notification if a ECN failure occurs due to ECN. It may only be supplied if ECN is enabled and the IMS-AGW acts as ECN endpoint. | +| | Extended RTP Header for CVO | O | This information element requests the IMS-AGW to pass on the CVO extended RTP header as defined by IETF RFC 5285 [23]. | +| | Extended RTP Header for Sent ROI | O | This information element requests the IMS-AGW to pass on the ROI extended RTP header for carriage of predefined and/or arbitrary ROI information as defined by IETF RFC 5285 [23] and 3GPP TS 26.114 [21]. | +| | Predefined ROI | O | This information element requests the IMS-AGW to support the RTCP feedback message capability for "Predefined ROI" type expressed by the parameter "3gpp-roi-predefined", as described in 3GPP TS 26.114 [21]. | +| | Arbitrary ROI | O | This information element requests the IMS-AGW to support the RTCP feedback message capability for "Arbitrary ROI" type expressed by the parameter "3gpp-roi-arbitrary", as described in 3GPP TS 26.114 [21]. | +| | Generic Image Attributes | O | This information element indicates image attributes (e.g. image size) as defined by IETF RFC 6236 [24]. | +| | Local certificate fingerprint Request | O | This information element is present if the IMS-ALG wants that the media is decrypted, and/or integrity protected by the IMS-AGW (NOTE 4). It requests the IMS-AGW to provide a local certificate fingerprint. | +| | Establish (D)TLS session | O | This information element requests the IMS-AGW to take the (D)TLS client role and to initiate the establishment of the (D)TLS session. (NOTE 4) | +| | Notify (D)TLS session establishment Failure Event | O | This information element requests a notification if a (D)TLS session establishment failure occurs. (NOTE 4) | +| | TCP State-aware Handling Indicator and Setup Direction | C | This information element indicates that TCP state-aware handling is required and indicates the TCP setup direction. It may only be included if the IMS-AGW supports TCP state-aware handling. | +| | Discard Incoming TCP Connection Establishment Requests Indicator | C | This information element indicates whether incoming TCP connection establishment requests (TCP SYN) shall be discarded. It may only be included if the IMS-AGW supports TCP state-aware handling and discarding incoming TCP connection establishment requests. | +| | Forward Incoming TCP Connection Establishment Requests Indicator | C | This information element indicates for a given termination to use the incoming TCP connection establishment request (TCP SYN) at that termination as a trigger for sending a TCP connection establishment request at the interconnected termination in the same context. It may only be included if the IMS-AGW supports TCP state-aware handling and the Forward Incoming TCP Connection Establishment Requests Indicator. | + +| | | | +|---------------------------------------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notify TCP Connection Establishment Failure Event | C | This information element requests a notification if a TCP connection establishment failure occurs. It may only be included if the IMS-AGW supports TCP state-aware handling. | +| ICE password request | O | This information element is present if IMS-ALG requests an ICE password. | +| ICE Ufrag request | O | This information element is present if IMS-ALG requests an ICE ufrag. | +| ICE host candidate request | O | This information element is present if IMS-ALG requests an ICE host candidate. | +| STUN server request | O | This information element is present if IMS-ALG requests the IMS-AGW to answer STUN connectivity checks for ICE. | +| Application-aware MSRP interworking request | O | This information element is present if IMS-ALG requests the IMS-AGW to perform application-aware MSRP Interworking. | +| Notify STUN consent freshness test failure Event | O | This information element requests a notification if a STUN consent freshness test failure occurs (full ICE only). | +| | | | +| STUN consent freshness test request | O | This information element is present if eP-CSCF requests the eIMS-AGW to perform a STUN consent freshness test (full ICE only). | +| Local SCTP Port Request | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an SCTP association. It requests the IMS-AGW to provide a local SCTP Port. | +| Local SCTP maximum message size Request | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an SCTP association. It requests the IMS-AGW to provide a local max message size. | +| Local Dcmap | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish the WEBRTC data channel. It indicates the information within an SDP "dcmap" attribute sent towards the remote peer, including the Subprotocol to exchange via the data channel. | +| Local Dcsa | O | This information element can be present if the IMS-ALG requests the IMS-AGW to establish the WEBRTC data channel and to handle its contents in an application-aware manner. It indicates the information within an SDP "dcsa" attribute sent towards the remote peer, encapsulating a subprotocol specific SDP attribute. | +| SCTP Group Semantics | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an SCTP association. It indicates the H.248 component streams that are grouped in the same SCTP association. | +| SCTP stream deaggregation | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an SCTP association. It indicates the H.248 component streams that transport media that are to be deaggregated from the H.248 deaggregation stream used to control the SCTP association. | +| SCTP stream ID | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an WEBRTC data channel. It indicates the SCTP stream ID to be used for that data channel. | + +| | | | | | +|----------------------------------|---------|------------------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Received SCTP Stream Reset Request | O | This information element is present if the eP-CSCF (IMS-ALG) requests the eIMS-AGW to establish the WEBRTC data channel. It requests the eIMS-AGW to provide a notification when receiving an SCTP Stream reset request and to autonomously answer that SCTP Stream reset request | +| | | SDPCapNeg configuration | O | This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| Reserve AGW Connection Point Ack | IMS-AGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | +| | | Local IP Resources | C | This information element indicates the resource(s) for which the IMS-AGW shall be prepared to receive user data. This IE shall be present if it was contained in the request. If the IE was not contained in the request, it may be present in the reply.

For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. | +| | | Local Connection Address | M | This information element indicates the IP address and port number(s) the IMS-AGW shall receive user plane data from IMS.

For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. | +| | | Local cryptographic SDES attribute | C | This information element may be present only if it was contained in the request. It indicates the SDES local cryptographic parameters such as key(s) | +| | | Local certificate fingerprint | C | This information element may be present only if the Local certificate fingerprint Request was contained in the request. It indicates the local certificate fingerprint. (NOTE 4) | +| | | ICE password | C | This information element shall be present only if it was contained in the request. It indicates the ICE password assigned by the IMS-AGW. | +| | | ICE Ufrag | C | This information element shall be present only if it was contained in the request. It indicates the ICE Ufrag assigned by the IMS-AGW. | +| | | ICE host candidate | C | This information element shall be present only if it was contained in the request. It indicates the ICE host candidate assigned by the IMS-AGW. | +| | | ICE lite indication | C | This information element shall be present only if an ICE host candidate request was contained in the request, and the IMS-AGW supports ICE lite, but not full ICE. It indicates that the IMS-AGW only supports ICE lite. | + +| | | | | | +|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|---------------------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Local SCTP Port | C | This information element may be present only if the Local SCTP Port Request was contained in the request. It indicates the local SCTP Port. | +| | | Local SCTP maximum message size | C | This information element may be present only if the Local max message size Request was contained in the request. It indicates the local max message size. | +| | | SDPCapNeg configuration | C | This information element shall be present only if it was contained in the request. It provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive.
NOTE 2: One of those IEs shall at least be present when policing is required.
NOTE 3: This IE may only be present for access network terminations, and only if the IMS-ALG includes only one SDES crypto attribute in the SDP sent towards the served UE.
NOTE 4: This IE may only be present for access network terminations. | | | | | + +## 8.4 Configure AGW Connection Point Procedure + +This procedure is used to select or modify multimedia-processing resources for the Iq interface connection. + +**Table 8.4.1: Procedures between IMS-ALG and IMS-AGW: Configure AGW Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------|-----------|---------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Configure AGW Connection Point | IMS-ALG | Context | M | This information element indicates the context for the bearer termination. | +| | | Priority information | O | This information element shall be present if the priority information needs to be modified, it may be present otherwise. | +| | | Bearer Termination | M | This information element indicates the existing bearer termination. | +| | | Local IP Resources | O | This information element indicates the resource(s) for which the IMS-AGW shall be prepared to receive user data.

For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream.

May be excluded (i.e. "-" is used in SDP m-line) if no transcoding or media related functions are required. | +| | | Remote IP Resources | O | This information element indicates the resource(s) for which the IMS-AGW shall send data.

For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream.

May be excluded (i.e. "-" is used in SDP m-line) if no transcoding or media related functions are required. | +| | | Local Connection Address | O | This information element indicates the IP address and port number(s) on the IMS-AGW that the IMS user can send user plane data to.

For terminations supporting video any combination of video, audio and messaging may contain multiple addresses. | +| | | Remote Connection Address | O | This information element indicates the remote IP address and port number(s) that the IMS-AGW can send user plane data to.

For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. | +| | | Latching Requirement | O | This information element indicates that the IMS-AGW should (re)latch onto the address of received media packets to determine the corresponding destination address. | +| | | IP Realm Identifier | O | This information element indicates the IP realm of the bearer termination. (NOTE 3) | + +| | | | +|--------------------------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Remote Source Address Filtering | O | This information element indicates that remote source address filtering is required. | +| Remote Source Address Mask | C | This information element provides information on the valid remote source addresses. This is required if a range of remote source address filtering is required. | +| Remote Source Port Filtering | O | This information element indicates that remote source port filtering is required. | +| Remote Source Port | C | This information element identifies the valid remote source port. This may be included if remote source port filtering is included. (NOTE 1) | +| Remote Source Port Range | C | This information element identifies a range of valid remote source ports. This may be included if remote source port filtering is included. (NOTE 1) | +| Policing Required | O | This information element indicates that policing of the media flow is required. | +| Peak Data Rate | O | This information element may be present if Policing is required and specifies the permissible peak data rate for a media stream. (NOTE 2). | +| Sustainable Data Rate | O | This information element may be present if Policing is required and specifies the permissible sustainable data rate for a media stream. (NOTE 2). | +| Delay Variation Tolerance | O | This information element may be present if Policing on Peak Data Rate is required and specifies the maximum expected delay variation tolerance for the corresponding media stream. | +| Maximum Burst Size | C | This information element shall be present if Policing on Sustainable Data Rate is required and specifies the maximum expected burst size for the corresponding media stream. | +| DiffServ Code Point | O | This information element indicates a specific DiffServ code point to be used in the IP header in packets sent on the bearer termination. | +| DiffServ Tagging Behaviour | O | This information element indicates whether the Diffserv code point in the IP header in packets sent on the bearer termination should be copied from the received value or set to a specific value. | +| Media Inactivity Detection Required | O | This information element indicates that detection of inactive media flows is required. | +| Media Inactivity Detection Time | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection time. | +| Media Inactivity Detection Direction | C | This information element may be present if Inactive Media Detection is required and specifies the Inactivity Detection direction. | + +| | | | | +|--|-------------------------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | RTCP handling | O | This information element is present if IMS-ALG wants to explicitly control the reservation of RTCP resources (NOTE 5). | +| | RTP/RTCP transport multiplexing | C | This information element requests the IMS-AGW to apply the RTP/RTCP transport multiplexing. This information element may only be present if RTCP handling is required. | +| | Explicit RTCP transport address | C | This information element indicates the remote RTCP port and optionally the remote network address where to send RTCP packets. This information element may only be present if RTCP handling is required. | +| | Local cryptographic SDES attribute | C | This information element is present if IMS-ALG wants that the media is encrypted and/or integrity protected by the IMS-AGW (NOTE 4). It indicates the SDES local cryptographic parameters such as key(s). | +| | Remote cryptographic SDES attribute | C | This information element is present if IMS-ALG wants that the media is decrypted, and/or integrity checked by the IMS-AGW (NOTE 4). It indicates the SDES remote cryptographic parameters such as key(s). | +| | ECN Enable | O | This information element requests the IMS-AGW to apply ECN procedures. | +| | ECN Initiation Method | C | This information element specifies the ECN Initiation method and requests the IMS-AGW to perform IP header settings as an ECN endpoint, or indicates that ECN bits shall be passed transparently. It may be included only if ECN is enabled. | +| | Notify ECN Failure Event | C | This information element requests a notification if a ECN failure occurs due to ECN. It may only be supplied if ECN is enabled and the IMS-AGW acts as ECN endpoint. | +| | Extended RTP Header for CVO | O | This information element requests the IMS-AGW to pass on the CVO extended RTP header as defined by IETF RFC 5285 [23]. | +| | Extended RTP Header for Sent ROI | O | This information element requests the IMS-AGW to pass on the ROI extended RTP header for carriage of predefined and/or arbitrary ROI information as defined by IETF RFC 5285 [23] and 3GPP TS 26.114 [21]. | +| | Predefined ROI | O | This information element requests the IMS-AGW to support the RTCP feedback message capability for "Predefined ROI" type expressed by the parameter "3gpp-roipredefined", as described in 3GPP TS 26.114 [21]. | +| | Arbitrary ROI | O | This information element requests the IMS-AGW to support the RTCP feedback message capability for "Arbitrary ROI" type expressed by the parameter "3gpp-roiarbitrary", as described in 3GPP TS 26.114 [21]. | + +| | | | +|------------------------------------------------------------------|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Generic Image Attributes | O | This information element indicates image attributes (e.g. image size) as defined by IETF RFC 6236 [24]. | +| Remote certificate fingerprint | O | This information element is present if the IMS-ALG wants that the media is decrypted, and/or integrity checked by the IMS-AGW (NOTE 4). It indicates the remote certificate fingerprint. | +| Establish (D)TLS session | O | This information element requests the IMS-AGW to take the (D)TLS client role and to initiate the establishment of the (D)TLS session. (NOTE 4) | +| Release (D)TLS session | O | This information element requests the IMS-AGW to release the (D)TLS session. (NOTE 4) | +| Notify (D)TLS session establishment Failure Event | O | This information element requests a notification if a TLS session establishment failure occurs. (NOTE 4) | +| TCP State-aware Handling Indicator and Setup Direction | C | This information element indicates that TCP state-aware handling is required and indicates the TCP setup direction. It may only be included if the IMS-AGW supports TCP state-aware handling. | +| Discard Incoming TCP Connection Establishment Requests Indicator | C | This information element indicates whether incoming TCP connection establishment requests (TCP SYN) shall be discarded. It may only be included if the IMS-AGW supports TCP state-aware handling and discarding incoming TCP connection establishment requests. | +| Forward Incoming TCP Connection Establishment Requests Indicator | C | This information element indicates for a given termination to use the incoming TCP connection establishment request (TCP SYN) at that termination as a trigger for sending a TCP connection establishment request at the interconnected termination in the same context. It may only be included if the IMS-AGW supports TCP state-aware handling and the Forward Incoming TCP Connection Establishment Requests Indicator. | +| Send TCP Connection Establishment Requests Indicator | C | This information element indicates for a given termination to send a TCP connection establishment request (TCP SYN). It may only be included if the IMS-AGW supports TCP state-aware handling. | +| Notify TCP Connection Establishment Failure Event | C | This information element requests a notification if a TCP connection establishment failure occurs. It may only be included if the IMS-AGW supports TCP state-aware handling. | +| ICE Connectivity Check | C | This information element requests the IMS-AGW to perform ICE connectivity check as defined by IETF RFC 5245 [39]. It is only applicable for full ICE. | + +| | | | +|--------------------------------------------------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Notify ICE Connectivity Check Result | C | This information element requests a notification of ICE connectivity check result. It is only applicable for full ICE. | +| Notify New Peer Reflexive Candidate | C | This information element requests a notification of new peer reflexive candidate was discovered during a connectivity check. It is only applicable for full ICE. | +| Additional ICE Connectivity Check | C | This information element requests the IMS-AGW to perform additional ICE connectivity check as defined by IETF RFC 5245 [39]. It is only applicable for full ICE. | +| ICE received candidate | O | This information element is present if IMS-ALG indicates a received candidate for ICE. | +| ICE received password | O | This information element is present if IMS-ALG indicates a received password for ICE. | +| ICE received Ufrag | O | This information element is present if IMS-ALG indicates a received Ufrag for ICE. | +| MSRP Path | O | This information element is present for application-aware MSRP Interworking. It provides the path information that the IMS-AGW shall insert in the MSRP layer "To-Path" Information element. | +| Notify STUN consent freshness test failure Event | O | This information element requests a notification if a STUN consent freshness test failure occurs (full ICE only). | +| STUN consent freshness test request | O | This information element is present if eP-CSCF requests the eIMS-AGW to perform a STUN consent freshness test (full ICE only). | +| Allowed RTCP APP message types | O | This information element is present if IMS-ALG allows the IMS-AGW to send RTCP APP packets of the indicated types. The IMS-AGW shall not send other RTCP APP packets. If the parameter is not supplied, the IMS-AGW shall not send any RTCP APP packets. | +| Local Dcmap | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish the WEBRTC data channel. It indicates the information within an SDP "dcmap" attribute sent towards the remote peer, including the Subprotocol to exchange via the data channel. | +| Remote Dcmap | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish the WEBRTC data channel. It indicates the information within an SDP "dcmap" attribute received from the remote peer, including the Subprotocol to exchange via the data channel. | +| Local Dcsa | O | This information element can be present if the IMS-ALG requests the IMS-AGW to establish the WEBRTC data channel and to handle its contents in an application-aware manner. It indicates the information within an SDP "dcsa" attribute sent towards the remote peer, encapsulating a subprotocol specific SDP attribute. | + +| | | | +|-------------------------------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| Remote Dcsa | O | This information element can be present if the IMS-ALG requests the IMS-AGW to establish the WEBRTC data channel and to handle its contents in an application-aware manner. It indicates the information within an SDP "dcsa" attribute received from the remote peer, encapsulating a subprotocol specific SDP attribute. | +| Remote SCTP port | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an SCTP association. It indicates the remote SCTP port. | +| Remote SCTP max message size | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an SCTP association. It indicates the remote max message size. | +| SCTP Group Semantics | O | This information element is present if the IMS-ALG requests the IMS-AGW to modify an SCTP association. It indicates the H.248 component streams that are grouped in the same SCTP association. | +| SCTP stream deaggregation | O | This information element is present if the IMS-ALG requests the IMS-AGW to modify an SCTP association. It indicates the H.248 component streams that transport media that are to be deaggregated from the H.248 deaggregation stream used to control the SCTP association. | +| SCTP stream ID | O | This information element is present if the IMS-ALG requests the IMS-AGW to establish an WEBRTC data channel. It indicates the SCTP stream ID to be used for that data channel. | +| Received SCTP Stream Reset Request | O | This information element is present if the eP-CSCF (IMS-ALG) requests the eIMS-AGW to establish the WEBRTC data channel. It requests the eIMS-AGW to provide a notification when receiving an SCTP Stream reset request and to autonomously answer that SCTP Stream reset request. | +| Send SCTP Stream Reset Requests Indicator | O | This information element is present if the eP-CSCF (IMS-ALG) requests the eIMS-AGW to reset an SCTP Stream to release the WEBRTC data channel. It requests the eIMS-AGW to send an SCTP Stream reset request. | +| Received SCTP Stream Reset Response | O | This information element may be present if the eP-CSCF (IMS-ALG) requests the eIMS-AGW to reset an SCTP Stream to release the WEBRTC data channel. It requests the eIMS-AGW to provide a notification when receiving a response to an SCTP Stream reset request. | +| Initiate Outgoing SCTP Stream Reset | O | This information element is present if the IMS-ALG requests the IMS-AGW to close an individual WEBRTC data channel. | +| Outgoing SCTP Stream Response | O | This information element is present if the IMS-ALG requests the IMS-AGW to acknowledge the request to close an individual WEBRTC data channel. | +| Notify Detect Outgoing SCTP Stream Reset | O | This information element requests a notification of outgoing SCTP Stream reset requests from remote peers (here IMS WebRTC client). | +| Notify Outgoing SCTP Stream Reset Result | O | This information element requests a notification of the result of an outgoing SCTP Stream reset sent to the remote peer (here IMS WebRTC client). | + +| | | | | | +|------------------------------------|---------|------------------------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | SDPCapNeg configuration | O | This information element provides SDPCapNeg configuration(s) using as "a=acap", "a=tcap", "a=pcfg" and "a=acfg" SDP attributes. | +| | | Additional Bandwidth Properties | O | This information element indicates additional bandwidth properties using "a=bw-info" SDP attribute(s) as defined by 3GPP TS 26.114 [21]. | +| | | CCM BASE | O | This information element indicates that the IMS-AGW shall be prepared to receive and is allowed to send, respectively, the RTCP feedback "CCM FIR" and/or "CCM TMMBR" messages (defined in IETF RFC 5104 [78]). | +| | | CCM pause-resume | O | This information element indicates to the IMS-AGW that RTCP feedback "CCM PAUSE-RESUME" messages shall be passed transparently. | +| | | DBI | O | This information element indicates to the IMS-AGW that RTCP DBI feedback messages (as defined in 3GPP TS 26.114 [21] clause 7.3.8) shall be passed transparently. | +| Configure AGW Connection Point Ack | IMS-AGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | +| | | Local IP Resources | O | This information element indicates the resource(s) for which the IMS-AGW shall be prepared to receive user data

For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. | +| | | Remote IP Resources | O | This information element indicates the resource(s) for which the IMS-AGW shall send data.

For terminations supporting any combination of video, audio and messaging this IE shall contain separate resources per stream. | +| | | Local Connection Address | O | This information element indicates the IP address and port number(s) on the IMS-AGW that the IMS user can send user plane data to.

For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. | +| | | Remote Connection Address | O | This information element indicates the remote IP address and port number(s) that the IMS-AGW can send user plane data to.

For terminations supporting any combination of video, audio and messaging this may contain multiple addresses. | +| | | Local cryptographic SDES attribute | C | This information element may be present only if it was contained in the request. It indicates the SDES local cryptographic parameters such as key(s) | + +| | | | | | +|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|-------------------------------------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------| +| | | Remote cryptographic SDES attribute | C | This information element may be present only if it was contained in the request. It indicates the SDES remote cryptographic parameters such as key(s) | +| NOTE 1: Remote Source Port and Remote Source Port Range are mutually exclusive. | | | | | +| NOTE 2: One of those IEs shall at least be present when policing is required. | | | | | +| NOTE 3: Additional streams may be added by the Configure AGW Connection Point procedure. The additional streams shall then carry the same IP Realm Identifier as the very first Stream. | | | | | +| NOTE 4: This IE may only be present for access network terminations. | | | | | +| NOTE 5: The concerned RTCP resource component is related to the RTCP port value. | | | | | + +**Editor's Note :** The details of how the transparent indication included in ECN Control is subject of stage 3 specification. It also needs to be determined if this indication is needed on both incoming and outgoing terminations. + +## 8.5 Release AGW Termination + +This procedure is used to release a termination towards the IMS and free all related resources. + +**Table 8.5.1: Procedures between IMS-ALG and IMS-AGW: Release AGW Termination** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Release AGW Termination | IMS-ALG | Context | M | This information element indicates the existing context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination to be released. | +| Release AGW Termination Ack | IMS-AGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +## 8.6 Termination heartbeat indication + +This procedure is used to report a termination heartbeat. + +**Table 8.6.1: Procedures between IMS-ALG and IMS-AGW: Termination heartbeat indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------|-----------|--------------------------|------------------------------|------------------------------------------------------------------------------------------------------------| +| Termination heartbeat indication | IMS-AGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the termination heartbeat is reported. | +| | | Termination heartbeat | M | Hanging Termination event, as defined in 3GPP TS 29.334 [3]. | +| Termination heartbeat indication Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +## 8.7 IMS-AGW Out-of-Service + +This procedure is used to indicate that the IMS-AGW will go out of service or is maintenance locked. + +**Table 8.7.1: Procedures between IMS-ALG and IMS-AGW: IMS-AGW Out-of-Service** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------| +| IMS-AGW Out-of-Service | IMS-AGW | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for service change. | +| | | Method | M | This information element indicates the method for service change. | +| IMS-AGW Out-of-Service Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | + +## 8.8 IMS-AGW Communication Up + +This procedure is used to indicate that the IMS-AGW is back in service using an existing control association. + +**Table 8.8.1: Procedures between IMS-ALG and IMS-AGW: IMS-AGW Communication Up** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------|-----------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| IMS-AGW Communication Up | IMS-AGW | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for service change. | +| | | Method | M | This information element indicates the method for service change. | +| IMS-AGW Communication Up Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | +| | | IMS-ALG Address | O | This information element indicates the IMS-ALG signalling address to which the IMS-AGW should preferably attempt to re-register. | + +## 8.9 IMS-AGW Restoration + +This procedure is used to indicate the IMS-AGW has recovered from a failure. + +**Table 8.9.1: Procedures between IMS-ALG and IMS-AGW: IMS-AGW Restoration** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| IMS-AGW Restoration | IMS-AGW | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for the service change. | +| | | Method | M | This information element indicates the method for service change. | +| IMS-AGW Restoration Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | +| | | IMS-ALG Address | O | This information element indicates the IMS-ALG signalling address to which the IMS-AGW should preferably attempt to re-register. | + +## 8.10 IMS-AGW Register + +This procedure is used to register the IMS-AGW after a cold/warm boot. + +**Table 8.10.1: Procedures between IMS-ALG and IMS-AGW: IMS-AGW Register** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------------|-----------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| IMS-AGW Register | IMS-AGW | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for the service change. | +| | | Method | M | This information element indicates the method for service change. | +| | | Protocol Version | M | This information element indicates the protocol version for Iq interface requested by the IMS-AGW. | +| | | Service Change Profile | M | This information element indicates the profile for the Iq interface requested by the IMS-AGW. | +| IMS-AGW Register Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | +| | | Protocol Version | O | This information element indicates the protocol version for Iq interface supported by the IMS-ALG. | +| | | Service Change Profile | O | This information element indicates the profile for the Iq interface supported by the IMS-ALG. | +| | | IMS-ALG Address | O | This information element indicates the IMS-ALG signalling address to which the IMS-AGW should preferably attempt to re-register. | + +## 8.11 IMS-ALG Restoration + +This procedure is used to indicate the IMS-ALG has recovered from a failure. + +**Table 8.11.1: Procedures between IMS-ALG and IMS-AGW: IMS-ALG Restoration** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------| +| IMS-ALG Restoration | IMS-ALG | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for the service change. | +| | | Method | M | This information element indicates the method for service change. | +| IMS-ALG Restoration Ack | IMS-AGW | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | + +## 8.12 IMS-AGW Re-register + +This procedure is used to re-register the IMS-AGW (having been requested to do so by the IMS-ALG). + +**Table 8.12.1: Procedures between IMS-ALG and IMS-AGW: IMS-AGW Re-register** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------|-----------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------| +| IMS-AGW Re-register | IMS-AGW | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for the service change. | +| | | Method | M | This information element indicates the method for service change. | +| | | Protocol Version | M | This information element indicates the protocol version for Iq interface requested by the IMS-AGW. | +| | | Service Change Profile | M | This information element indicates the profile for the Iq interface requested by the IMS-AGW. | +| IMS-AGW Re-register Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | +| | | Protocol Version | O | This information element indicates the protocol version for Iq interface supported by the IMS-ALG. | +| | | Service Change Profile | O | This information element indicates the profile for the Iq interface supported by the IMS-ALG. | +| | | IMS-ALG Address | O | This information element indicates the IMS-ALG signalling address to which the IMS-AGW should preferably attempt to re-register. | + +## 8.13 IMS-ALG Ordered Re-registration + +This procedure is used by the IMS-ALG to request the IMS-AGW to re-register. + +**Table 8.13.1: Procedures between IMS-ALG and IMS-AGW: IMS-ALG Ordered Re-register** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------| +| IMS-ALG Ordered Re-register | IMS-ALG | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for the service change. | +| | | IMS-ALG Address | O | This information element indicates the IMS-ALG signalling address. | +| IMS-ALG Ordered Re-register Ack | IMS-AGW | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | + +## 8.14 Audit Value + +This procedure is used to audit values of different object(s). + +**Table 8.14.1: Procedures between IMS-ALG and IMS-AGW: Audit Value** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Audit Value | IMS-ALG | Context | M | This information element indicates the context for the command. | +| | | Bearer Termination | M | This information element indicates the bearer termination(s) for the command. | +| | | Object(s) | M | This information element indicates the object(s) to be audited. | +| Audit Value Ack | IMS-AGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | +| | | Value(s) | M | This information element indicates the value(s) of the object(s). | + +## 8.15 Audit Capability + +This procedure is used to audit capabilities of different object(s). + +**Table 8.15.1: Procedures between IMS-ALG and IMS-AGW: Audit Capability** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Audit Capability | IMS-ALG | Context | M | This information element indicates the context for the command. | +| | | Bearer Termination | M | This information element indicates the bearer termination(s) for the command. | +| | | Object(s) | M | This information element indicates the object(s) which capability is requested. | +| Audit Capability Ack | IMS-AGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | +| | | Capabilities(s) | M | This information element indicates the capabilities of the object(s). | + +## 8.16 Capability Update + +This procedure is used to indicate update of an object capability. + +**Table 8.16.1: Procedures between IMS-ALG and IMS-AGW: Capability Update** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Capability Update | IMS-AGW | Context | M | This information element indicates the context for the command. | +| | | Bearer Termination | M | This information element indicates the bearer termination(s) for the command. | +| | | Reason | M | This information element indicates the reason for service change. | +| | | Method | M | This information element indicates the method for service change. | +| Capability Update Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +## 8.17 IMS-ALG Out of Service + +This procedure is used to indicate that IMS-ALG has gone out of service. + +**Table 8.17.1: Procedures between IMS-ALG and IMS-AGW: IMS-ALG Out of Service** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------| +| IMS-ALG Out of Service | IMS-ALG | Context | M | This information element indicates the context for the command. | +| | | Root Termination | M | This information element indicates the root termination for the command. | +| | | Reason | M | This information element indicates the reason for the service change. | +| | | Method | M | This information element indicates the method for service change. | +| IMS-ALG Out of Service Ack | IMS-AGW | Context | M | This information element indicates the context where the command was executed. | +| | | Root Termination | M | This information element indicates the root termination where the command was executed. | + +## 8.18 IMS-AGW Resource Congestion Handling - Activate + +This procedure is used to activate the congestion handling mechanism. + +**Table 8.18.1: Procedures between IMS-ALG and IMS-AGW: IMS-AGW Resource Congestion Handling - Activate** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------------------------|-----------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------------------| +| IMS-AGW Resource Congestion Handling – Activate | IMS-ALG | Context | M | This information element indicates that all context are applicable for the root termination. | +| | | Root Termination | M | This information element indicates that root termination is where the congestion mechanism is activated. | +| | | Congestion Activate | M | This information element requests to activate the congestion mechanism. | +| IMS-AGW Resource Congestion Handling - Activate Ack | IMS-AGW | Context | M | This information element indicates that all context are where the command was executed. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +## 8.19 IMS-AGW Resource Congestion Handling - Indication + +This procedure is used to inform the IMS-ALG that traffic restriction is advised. + +**Table 8.19.1: Procedures between IMS-ALG and IMS-AGW: IMS-AGW Resource Congestion Handling -Indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------| +| IMS-AGW Resource Congestion Handling - Indication | IMS-AGW | Context | M | This information element indicates all context are applicable for the root termination. | +| | | Root Termination | M | This information element indicates that root termination is where the congestion mechanism was activated. | +| | | Reduction | M | This information element indicates the load percentage to be reduced. | +| IMS-AGW Resource Congestion Handling - Indication Ack | IMS-ALG | Context | M | This information element indicates all context are where the command was executed. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +## 8.20 Inactivity Timeout Activate + +This procedure is used to activate the inactivity timeout mechanism. + +**Table 8.20.1: Procedures between IMS-ALG and IMS-AGW: Inactivity Timeout Activate** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------|-----------|-----------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------| +| Inactivity Timeout Activate | IMS-ALG | Context | M | This information element indicates all context are applicable for the root termination. | +| | | Root Termination | M | This information element indicates that root termination is where inactivity timeout mechanism was activated. | +| | | Inactivity Timeout Activate | M | This information element activates the Inactivity Timeout request. | +| | | Inactivity Timeout | O | This information element indicates the maximum length of time before triggering the related notification. | +| Inactivity Timeout Activate Ack | IMS-AGW | Context | M | This information element indicates all context are where the command was executed. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +## 8.21 Inactivity Timeout Notification + +This command is used to notify the IMS-ALG of an inactive control association. + +**Table 8.21.1: Procedures between IMS-AGW and IMS-ALG: Inactivity Timeout Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------------|-----------|---------------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------| +| Inactivity Timeout Notification | IMS-AGW | Context | M | This information element indicates all context are applicable for the root termination. | +| | | Root Termination | M | This information element indicates that root termination is where the inactivity timeout mechanism was activated. | +| | | Inactivity Timeout Notification | M | This information element notifies the IMS-ALG of an inactivity time period. | +| Inactivity Timeout Notification Ack | IMS-ALG | Context | M | This information element indicates all context are where the command was executed. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +## 8.22 Command Reject + +This command is used to reject the received command request. It may be used as response to any of the procedures. + +**Table 8.22.1: Procedures between IMS-ALG and IMS-AGW: Command Reject** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------| +| Command Reject | Both | Context | O | This information element indicates the context where the command was rejected. | +| | | Bearer Termination | O | This information element indicates the bearer termination where the command was rejected. | +| | | Error | M | This information element indicates the error that caused command rejection. | + +## 8.23 Realm Availability Activate + +This command is used to request the IMS-AGW to monitor the status of its IP Realms and to report any changes to the IMS-ALG. + +**Table 8.23.1: Procedures between IMS-ALG and IMS-AGW: Realm Availability Activate** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------|-----------|-----------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------| +| Realm Availability Activate | IMS-ALG | Context | M | This information element indicates all context are applicable for the root termination. | +| | | Root Termination | M | This information element indicates that root termination is where the realm availability monitoring was activated. | +| | | Realm Availability Activate | M | This information element activates the monitoring of the availability of IP Realms on the IMS-AGW. | +| Realm Availability Activate Ack | IMS-AGW | Context | M | This information element indicates all context are where the command was executed. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +## 8.24 Realm Availability Notification + +This command is used to notify the IMS-ALG of any changes in the availability of IP Realms on the IMS-AGW. + +**Table 8.24.1: Procedures between IMS-ALG and IMS-AGW: Realm Availability Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------------|-----------|----------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------| +| Realm Availability Notification | IMS-AGW | Context | M | This information element indicates all context are applicable for the root termination. | +| | | Root Termination | M | This information element indicates that root termination is where the realm availability monitoring was activated. | +| | | Realm Availability Changes | M | This information element notifies the IMS-ALG of newly available/unavailable IP Realms. | +| Realm Availability Notification Ack | IMS-ALG | Context | M | This information element indicates all context are where the command was executed. | +| | | Root Termination | M | This information element indicates that root termination is where the command was executed. | + +## 8.25 IP Bearer Released + +**Table 8.25.1: Procedures between IMS-ALG and IMS-AGW: IP Bearer Released** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------|-----------|--------------------------|------------------------------|-----------------------------------------------------------------------------------------------| +| IP Bearer Released | IMS-AGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the bearer was released. | +| | | Bearer Released | M | This information element notifies a bearer release. | +| | | Release Cause | M | This information element indicates the cause of a bearer release. | +| IP Bearer Released Ack | IMS-ALG | Context | M | This information element indicates all context are where the command was executed. | +| | | Bearer Termination | M | This information element indicates that Bearer termination is where the command was executed. | + +## 8.26 Media Inactivity Notification + +This command is used to notify the IMS-ALG of media inactivity on the IMS-AGW. + +**Table 8.26.1: Procedures between IMS-ALG and IMS-AGW: Media Inactivity Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------|-----------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------| +| Media Inactivity Notification | IMS-AGW | Context | M | This information element indicates the existing context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates that bearer termination is where the media inactivity detection was activated. | +| | | Media Inactivity | M | This information element notifies the IMS-ALG of Media inactivity detection on the bearer termination. | +| Media Inactivity Notification Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +## 8.27 Termination Out-of-Service + +This procedure is used to indicate that a termination on the IMS-AGW has gone out of service + +**Table 8.27.1: Procedures between IMS-ALG and IMS-AGW: Termination Out-of-Service** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------|-----------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------| +| Termination Out-of-Service | IMS-AGW | Context | M | This information element indicates the context for the command. | +| | | Bearer Termination | M | This information element indicates the bearer termination(s) for the command. | +| | | Reason | M | This information element indicates the reason for service change. | +| | | Method | M | This information element indicates the method for service change. | +| Termination Out-of-Service Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination(s) where the command was executed. | + +## 8.28 Change Through-Connection + +This procedure is used to change the through-connection in the bearer termination + +**Table 8.28.1: Procedures between IMS-ALG and IMS-AGW: Change Through-Connection** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------|-----------|-----------------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| +| Change Through-Connection | IMS-ALG | Context/Context Request | M | This information element indicates the existing context or requests a new context for the bearer termination. | +| | | Bearer Termination/Bearer Termination Request | M | This information element indicates the existing bearer termination or requests a new bearer termination where the through-connection is changed. | +| | | Through-Connection | M | This information element indicates the through-connection of the bearer termination | +| Change Through-Connection Ack | IMS-AGW | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +NOTE: This procedure may be combined with Reserve and Configure AGW Connection Point, Reserve AGW Connection Point or Configure AGW Connection Point procedure. This list of procedures is not exhaustive. + +## 8.29 Change Flow Direction + +This procedure is used to change the flow direction between bearer terminations within the context. + +**Table 8.29: Procedures between IMS-ALG and IMS-AGW: Configure AGW Connection Point** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------|-----------|----------------------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| Change Flow Direction | IMS-ALG | Context/Context Request | M | This information element indicates the existing context or a new context where the flow direction is changed. | +| | | Bearer Termination 1/ Bearer Termination 1 Request | M | This information element indicates the existing bearer termination or a new bearer termination from where the new flow direction is applied. | +| | | Bearer Termination 2/ Bearer Termination 2 Request | M | This information element indicates the existing bearer termination or a new bearer termination where to the new flow direction is applied. | +| | | Flow Direction | M | This information element indicates the flow direction from the bearer termination 1 to bearer termination 2 within the context. | +| Change Flow Direction Ack | IMS-AGW | Context | M | This information element indicates the context where the command was executed. | + +## 8.30 ECN Failure Indication + +This procedure is used to report ECN related failures (see clause 6.2.13.4). + +**Table 8.30.1: Procedures between IMS-ALG and IMS-AGW: ECN Failure Indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|----------------------------|-----------|--------------------------|------------------------------|--------------------------------------------------------------------------------------------------| +| ECN Failure Indication | IMS-AGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the ECN failure is reported. | +| | | ECN Error Indication | M | This information element indicates an ECN failure event. | +| ECN Failure Indication Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +## 8.31 Notify (D)TLS session establishment Failure Indication + +This procedure is used to report (D)TLS session establishment failures. + +**Table 8.31.1: Procedures between IMS-ALG and IMS-AGW: (D)TLS session establishment Failure Indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------------------------|-----------|-----------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| (D)TLS session establishment Failure Indication | IMS-AGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the (D)TLS session establishment failure is reported. | +| | | (D)TLS session establishment Error Indication | M | This information element indicates a (D)TLS session establishment failure event. | +| (D)TLS session establishment Failure Indication Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +## 8.32 Notify TCP connection establishment Failure Indication + +This procedure is used to report TCP connection establishment failures. + +**Table 8.32.1: Procedures between IMS-ALG and IMS-AGW: TCP connection establishment Failure Indication** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-----------------------------------------------------|-----------|-----------------------------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------| +| TCP connection establishment Failure Indication | IMS-AGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the TCP connection establishment failure is reported. | +| | | TCP connection establishment Error Indication | M | This information element indicates a TCP connection establishment failure event. | +| TCP connection establishment Failure Indication Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +## 8.33 ICE Connectivity Check Result Notification + +This procedure is used to report ICE connectivity check result for Full ICE (see clause 6.2.17.3). + +**Table 8.33.1: Procedures between IMS-ALG and IMS-AGW: ICE Connectivity Check Result Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------------------------|-----------|-------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------| +| ICE Connectivity Check Result Notification | IMS-AGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the ICE Connectivity Check Result is reported. | +| | | ICE Connectivity Check Result | M | This information element indicates an ICE Connectivity Check Result event. | +| ICE Connectivity Check Result Notification Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +## 8.34 ICE New Peer Reflexive Candidate Notification + +This procedure is used to report ICE new peer reflexive candidate for Full ICE (see clause 6.2.17.4). + +**Table 8.34.1: Procedures between IMS-ALG and IMS-AGW: ICE New Peer Reflexive Candidate Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|---------------------------------------------------|-----------|----------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------| +| ICE New Peer Reflexive Candidate Notification | IMS-AGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the ICE New Peer Reflexive Candidate is reported. | +| | | ICE New Peer Reflexive Candidate | M | This information element indicates an ICE New Peer Reflexive Candidate event. | +| ICE New Peer Reflexive Candidate Notification Ack | IMS-ALG | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +## 8.35 STUN Consent Freshness Test Failure Notification + +This procedure is used to report STUN consent freshness test failures. + +**Table 8.35.1: Procedures between eP-CSCF and eIMS-AGW: STUN Consent Freshness Test Failure Notification** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|--------------------------------------------------|-----------|-------------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------| +| STUN consent freshness test Failure Notification | eIMS-AGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination for which the STUN consent freshness test failure is reported. | +| | | STUN consent freshness test failure | M | This information indicates a STUN consent freshness failure event. | +| STUN consent freshness test Failure Notification | eP-CSCF | Context | M | This information element indicates the context where the command was executed. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the command was executed. | + +## 8.36 Notify SCTP Stream Reset + +**Table 8.36.1: Procedures between IMS-ALG and IMS-AGW: Notify SCTP Stream Reset** + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|------------------------------|-----------|------------------------------------|------------------------------|-----------------------------------------------------------------------------------------------| +| Notify SCTP Stream Reset | IMS-AGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the bearer was released. | +| | | Received SCTP Stream Reset Request | M | This information element indicates that an SCTP Stream reset request has been received | +| | | SCTP Stream ID | M | This information element indicates the SCTP Stream ID of the related SCTP Stream. | +| Notify SCTP Stream Reset Ack | IMS-ALG | Context | M | This information element indicates all context are where the command was executed. | +| | | Bearer Termination | M | This information element indicates that Bearer termination is where the command was executed. | + +## 8.37 Notify SCTP Stream Reset Result + +Table 8.37.1: Procedures between IMS-ALG and IMS-AGW: Notify SCTP Stream Reset Result + +| Procedure | Initiated | Information element name | Information element required | Information element description | +|-------------------------------------|-----------|-----------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------| +| Notify SCTP Stream Reset Result | IMS-AGW | Context | M | This information element indicates the context for the bearer termination. | +| | | Bearer Termination | M | This information element indicates the bearer termination where the bearer was released. | +| | | Received SCTP Stream Reset Result | M | This information element indicates that an SCTP Stream reset result has been received and the received result. | +| | | SCTP Stream ID | M | This information element indicates the SCTP Stream ID of the related SCTP Stream. | +| Notify SCTP Stream Reset Result Ack | IMS-ALG | Context | M | This information element indicates all context are where the command was executed. | +| | | Bearer Termination | M | This information element indicates that Bearer termination is where the command was executed. | + +## Annex A (informative): Change history + +| Date | TSG # | TSG Doc. | CR | Rev | Subject/Comment | New | +|---------|-------|-----------|------|-----|------------------------------------------------------------------------------------------------|--------| +| 2009-12 | CT#46 | CP-090822 | | | 3GPP TS Presented for approval in CT#46 | 9.0.0 | +| 2009-12 | | | | | Editorial clean up | 9.0.1 | +| 2010-03 | CT#47 | CP-100050 | 0001 | 2 | IMS media plane security stage 2 | 9.1.0 | +| 2010-06 | CT#48 | CP-100289 | 0003 | 1 | Transport protocol to be indicated to gateway for end-to-end media security | 9.2.0 | +| 2010-06 | CT#48 | CP-100284 | 0004 | 1 | Handling of Through Connection | 9.2.0 | +| 2010-06 | CT#48 | | 0005 | - | Handling of RTCP streams requirement update | 9.2.0 | +| 2010-09 | CT#49 | CP-100461 | 0006 | 1 | Procedures for Emergency call | 9.3.0 | +| 2010-09 | CT#49 | | 0007 | 1 | Local IP Resources IE: changing of property | 9.3.0 | +| 2010-12 | CT#50 | CP-100685 | 0008 | - | Support of ECN | 10.0.0 | +| 2011-03 | CT#51 | CP-110058 | 0009 | 2 | Handling of ICE Initialisation method for ECN | 10.1.0 | +| 2011-03 | CT#51 | | 0010 | 2 | ECN Support in Iq Interface | 10.1.0 | +| 2011-09 | CT#53 | CP-110573 | 0011 | 2 | Transcoding at ATCF/ATGW during eSRVCC | 10.2.0 | +| 2011-12 | CT#54 | CP-110798 | 0012 | 1 | Explicit Congestion Notification | 10.3.0 | +| 2011-12 | CT#54 | CP-110798 | 0013 | 1 | Corrections to Stage 2 Procedures for Access Transfer Function | 10.3.0 | +| 2012-03 | CT#55 | CP-120046 | 0014 | 2 | Functional Requirements for eMPS MGW control | 11.0.0 | +| 2012-06 | CT#56 | CP-120239 | 0015 | 3 | Multimedia Priority Control of Media Gateway resources | 11.1.0 | +| 2012-06 | CT#56 | CP-120226 | 0018 | 1 | Reference update: draft-ietf-avtcore-ecn-for-rtp | 11.1.0 | +| 2012-11 | | | | | Version in the header corrected | 11.1.1 | +| 2012-12 | CT#58 | CP-120723 | 0025 | - | Reference update: RFC 6679 | 11.2.0 | +| 2012-12 | CT#58 | CP-120734 | 0026 | 3 | Support of Multimedia Priority Service (MPS) in Modify over Iq Interface | 11.2.0 | +| 2013-06 | CT#60 | CP-130299 | 0029 | 3 | Introduction of support for Coordination of Video Orientation (CVO) | 12.0.0 | +| 2013-09 | CT#61 | CP-130471 | 0030 | 3 | Introduction of support for Generic Image Attribute/signalling of image size | 12.1.0 | +| 2013-09 | CT#61 | CP-130452 | 0034 | 2 | CVO Procedural Clarifications | 12.1.0 | +| 2013-12 | CT#62 | CP-130636 | 0035 | 1 | Usage of generic image attributes | 12.2.0 | +| 2013-12 | CT#62 | CP-130636 | 0038 | 1 | Correction of Image Size description | 12.2.0 | +| 2013-12 | CT#62 | CP-130619 | 0037 | 1 | Correction of CVO description | 12.2.0 | +| 2014-03 | CT#63 | CP-140025 | 0040 | - | Alignment of IE name for CVO | 12.3.0 | +| 2014-06 | CT#64 | CP-140245 | 0041 | 1 | e2e media security for TCP-based media using TLS – Functional requirements | 12.4.0 | +| 2014-06 | CT#64 | CP-140245 | 0042 | 4 | e2ae media security for TCP based media using TLS – Functional requirements | 12.4.0 | +| 2014-06 | CT#64 | CP-140245 | 0043 | 2 | e2ae media security for UDP-based media using DTLS – Functional requirements | 12.4.0 | +| 2014-06 | CT#64 | CP-140245 | 0054 | 1 | e2e media security for TCP-based media using TLS - Procedures | 12.4.0 | +| 2014-06 | CT#64 | CP-140245 | 0055 | 2 | e2ae media security for TCP-based media using TLS - Procedures | 12.4.0 | +| 2014-06 | CT#64 | CP-140245 | 0056 | 1 | e2ae media security for UDP-based media using DTLS – procedures | 12.4.0 | +| 2014-06 | CT#64 | CP-140245 | 0057 | 3 | Iq requirements for end-to-end TCP bearer connection control and related NAT traversal support | 12.4.0 | +| 2014-06 | CT#64 | CP-140256 | 0045 | 1 | Functional requirements – clarification of "stage 2" convention | 12.4.0 | +| 2014-06 | CT#64 | CP-140248 | 0046 | 3 | Support for Interactive Connectivity Establishment (ICE) | 12.4.0 | +| 2014-06 | CT#64 | CP-140249 | 0052 | 2 | WebRTC media security using DTLS-SRTP | 12.4.0 | +| 2014-06 | CT#64 | CP-140249 | 0053 | 2 | WebRTC support for Iq | 12.4.0 | +| 2014-09 | CT#65 | CP-140504 | 0058 | 1 | Procedures for TCP bearer connection control | 12.5.0 | +| 2014-09 | CT#65 | CP-140504 | 0060 | 1 | Bandwidth adjustment due to e2ae media security | 12.5.0 | +| 2014-09 | CT#65 | CP-140504 | 0061 | - | MSRP handling | 12.5.0 | +| 2014-12 | CT#66 | CP-140798 | 0047 | 3 | RTCP port allocation rules – Semantical clarification | 12.6.0 | +| 2014-12 | CT#66 | CP-140786 | 0062 | 2 | E2e media security for TCP-based media – terminals behind NAT | 12.6.0 | +| 2014-12 | CT#66 | CP-140786 | 0066 | - | Reference update: RFC 7345 (draft-ietf-mmusic-udptl-dtls) | 12.6.0 | +| 2014-12 | CT#66 | CP-140786 | 0074 | - | Reference update: draft-schwarz-mmusic-sdp-for-gw | 12.6.0 | +| 2014-12 | CT#66 | CP-140786 | 0075 | 2 | Client-initiated TLS session renegotiation not supported on the Iq interface | 12.6.0 | +| 2014-12 | CT#66 | CP-140777 | 0063 | 1 | WebRTC Architecture Update | 12.6.0 | +| 2014-12 | CT#66 | CP-140777 | 0064 | 4 | Consent Refreshness in WebRTC | 12.6.0 | +| 2014-12 | CT#66 | CP-140777 | 0067 | 4 | H.248 requirements for WebRTC | 12.6.0 | +| 2014-12 | CT#66 | CP-140777 | 0068 | 3 | Iq requirements for OPUS codec in WebRTC | 12.6.0 | +| 2014-12 | CT#66 | CP-140777 | 0069 | 3 | Iq requirements for ICE-TCP | 12.6.0 | +| 2014-12 | CT#66 | CP-140777 | 0072 | 5 | End-to-access-edge security for DTLS over TCP | 12.6.0 | +| 2014-12 | CT#66 | CP-140788 | 0070 | 3 | Iq requirements for EVS | 12.6.0 | +| 2014-12 | CT#66 | CP-140791 | 0071 | 3 | Alternative connection (ALTC) addresses management | 12.6.0 | + +| | | | | | | | +|---------|--------|-----------|------|---|--------------------------------------------------------------------------------------------------------------------------------------|--------| +| 2014-12 | CT#66 | CP-140799 | 0039 | 7 | Support of RTP transport multiplexing (lq, stage 2) | 13.0.0 | +| 2015-03 | CT#67 | CP-150027 | 0077 | 1 | IMS WebRTC reference updates | 13.1.0 | +| 2015-03 | CT#67 | CP-150030 | 0079 | 1 | DTLS roles and cross-reference correction | 13.1.0 | +| 2015-06 | CT#68 | CP-150258 | 0085 | - | 3GPP TLS profile reference | 13.2.0 | +| 2015-06 | CT#68 | CP-150260 | 0083 | 1 | Bearer Termination in Acknowledgements | 13.2.0 | +| 2015-06 | CT#68 | CP-150259 | 0081 | 1 | EVS corrections | 13.2.0 | +| 2015-09 | CT#69 | CP-150457 | 0088 | 2 | MSRP and WebRTC data channels | 13.3.0 | +| 2015-09 | CT#69 | CP-150452 | 0091 | 4 | Support for Video Enhancements by Region-of-Interest Information Signalling | 13.3.0 | +| 2015-12 | CT#70 | CP-150786 | 0092 | 7 | Support of SDP capability negotiation | 13.4.0 | +| 2015-12 | CT#70 | CP-150779 | 0093 | 4 | WebRTC Data Channel Call flows | 13.4.0 | +| 2015-12 | CT#70 | CP-150779 | 0095 | 3 | Update of WebRTC data channel references | 13.4.0 | +| 2015-12 | CT#70 | CP-150779 | 0100 | 2 | Support of WebRTC data channels (stage 2) | 13.4.0 | +| 2015-12 | CT#70 | CP-150779 | 0101 | 1 | WebRTC Data Channel Procedures | 13.4.0 | +| 2015-12 | CT#70 | CP-150779 | 0102 | 1 | WebRTC Data Channel Information Elements | 13.4.0 | +| 2015-12 | CT#70 | CP-150779 | 0094 | 4 | Support for Video Enhancements by Region-of-Interest Information Signalling | 13.4.0 | +| 2015-12 | CT#70 | CP-150779 | 0097 | 1 | Update of media security references | 13.4.0 | +| 2015-12 | CT#70 | CP-150779 | 0099 | 2 | Update of IMS WebRTC references | 13.4.0 | +| 2016-03 | CT#71 | CP-160015 | 0109 | 1 | Corrections to EVS AMR-WB IO mode-change-capability MIME parameter handling | 13.5.0 | +| 2016-03 | CT#71 | CP-160028 | 0104 | 2 | Release of WebRTC Data Channels | 13.5.0 | +| 2016-03 | CT#71 | CP-160034 | 0106 | 2 | Support of enhanced bandwidth negotiation mechanism for MTSI sessions | 13.5.0 | +| 2016-03 | CT#71 | CP-160032 | 0107 | 2 | WebRTC media plane optimization procedure | 13.5.0 | +| 2016-09 | CT#73 | CP-160429 | 0112 | 1 | Mandatory support of RTP/RTCP multiplexing | 14.0.0 | +| 2016-09 | CT#73 | CP-160429 | 0114 | 1 | Transport of T.140 and BFCP within data channels | 14.0.0 | +| 2016-12 | CT#74 | CP-160684 | 0115 | 1 | Support of RTP-level pause and resume functionality | 14.1.0 | +| 2016-12 | CT#74 | CP-160648 | 0116 | 4 | SDP offer/answer for TLS and DTLS protected media | 14.1.0 | +| 2016-12 | CT#74 | CP-160671 | 0118 | 2 | WebRTC Media plane optimization with DTLS termination | 14.1.0 | +| 2016-12 | CT#74 | CP-160671 | 0119 | 1 | TCP transport for WebRTC data channels | 14.1.0 | +| 2016-12 | CT#74 | CP-160647 | 0125 | 1 | Corrections to handling of the DTX related EVS MIME parameter | 14.1.0 | +| 2016-12 | CT#74 | CP-160661 | 0127 | 2 | Reference update for draft-ietf-mmusic-data-channel-sdpneg | 14.1.0 | +| 2017-03 | CT#75 | CP-170023 | 0129 | - | Reference update: draft-ietf-mmusic-dtls-sdp | 14.2.0 | +| 2017-03 | CT#75 | CP-170023 | 0131 | - | RFC 4572 obsoleted by draft-ietf-mmusic-4572-update | 14.2.0 | +| 2017-03 | CT#75 | CP-170030 | 0135 | 1 | Updates for WebRTC media plane optimization procedures related to the usage of the "dtls-id" SDP attribute and multiple fingerprints | 14.2.0 | +| 2017-03 | CT#75 | CP-170033 | 0132 | - | Reference update: RFC 8035 | 14.2.0 | +| 2017-03 | CT#75 | CP-170051 | 0133 | 2 | RTCP Codec Control Commands and Indications | 14.2.0 | +| 2017-06 | CT#76 | CP-171015 | 0137 | - | Reference update: RFC 8122 | 14.3.0 | +| 2017-06 | CT#76 | CP-171027 | 0138 | - | Reference update: draft-ietf-mmusic-mux-exclusive | 14.3.0 | +| 2017-06 | CT#76 | CP-171024 | 0140 | - | Reference update: draft-ietf-mmusic-sctp-sdp | 14.3.0 | +| 2017-06 | CT#76 | CP-171015 | 0142 | - | Reference update: draft-ietf-mmusic-dtls-sdp | 14.3.0 | +| 2017-12 | CT#78 | CP-173014 | 0144 | - | Reference update: draft-ietf-mmusic-dtls-sdp | 14.4.0 | +| 2018-03 | CT#79 | CP-180014 | 0145 | 1 | Removal of IETF draft for transport BFCP within data channels | 14.5.0 | +| 2018-06 | CT#80 | - | - | - | Update to Rel-15 version (MCC) | 15.0.0 | +| 2019-06 | CT#84 | CP-191053 | 0149 | 2 | Update IMS-ALG/IMS-AGW procedures for DBI support | 16.0.0 | +| 2019-12 | CT#86 | CP-193019 | 0156 | - | Reference update: draft-ietf-mmusic-msrp-usage-data-channel | 16.1.0 | +| 2019-12 | CT#86 | CP-193021 | 0152 | 1 | Reference update: draft-ietf-mmusic-t140-usage-data-channel | 16.1.0 | +| 2020-12 | CT#90e | CP-203024 | 0164 | - | Update on draft references | 16.2.0 | +| 2020-12 | CT#90e | CP-203025 | 0159 | - | Reference update: draft-ietf-mmusic-t140-usage-data-channel | 16.2.0 | +| 2021-03 | CT#91e | CP-210065 | 0168 | - | Reference update: RFC 8842 | 16.3.0 | +| 2021-03 | CT#91e | CP-210066 | 0172 | - | Reference update: RFC 8831, RFC 8841, RFC 8864 and RFC 8873 | 16.3.0 | +| 2021-03 | CT#91e | CP-210068 | 0175 | - | Reference update: RFC 8858 and RFC 8865 | 16.3.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23732/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/marked/Rel-16/23_series/23732/00504fc688ebcf131ccbeff94dfc9939_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..fed681b233f163021d06863e46d2d76cd5053f85 --- /dev/null +++ b/marked/Rel-16/23_series/23732/00504fc688ebcf131ccbeff94dfc9939_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03bd2b824d49eed4453efef7a7b1462ac7728021ef21911ec858536c0788c2f3 +size 59003 diff --git a/marked/Rel-16/23_series/23732/04cfca33e3fc26513abe649d7474f733_img.jpg b/marked/Rel-16/23_series/23732/04cfca33e3fc26513abe649d7474f733_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d92c1bebc5de553dc5920b696cd59fce6950521f --- /dev/null +++ b/marked/Rel-16/23_series/23732/04cfca33e3fc26513abe649d7474f733_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9794613afcf49a384a8d2580ad7536765616081c3ccaff74744706659d2b358c +size 95461 diff --git a/marked/Rel-16/23_series/23732/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg b/marked/Rel-16/23_series/23732/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8ccf9f319ecc2563bfabf80bd66d30dfb6f7841 --- /dev/null +++ b/marked/Rel-16/23_series/23732/05eb72d372e4bf78e3d6a64949d77bcc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d8d6e91fd506a964ee39bb182f22933df6666bf288dc2d50bc4bdd07edd98f96 +size 32823 diff --git a/marked/Rel-16/23_series/23732/080a7af02bc47cf21ebfae4e0be39745_img.jpg b/marked/Rel-16/23_series/23732/080a7af02bc47cf21ebfae4e0be39745_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..28ef7d8e08266507014b7a2bcc9da60a7079843d --- /dev/null +++ b/marked/Rel-16/23_series/23732/080a7af02bc47cf21ebfae4e0be39745_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:84e6a9694027c21a1157234a7991e615fd5cb0eb76b1661c50290fecf8a5a184 +size 24997 diff --git a/marked/Rel-16/23_series/23732/0997dbaa9dfecedd60029d70b53327b8_img.jpg b/marked/Rel-16/23_series/23732/0997dbaa9dfecedd60029d70b53327b8_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5e1eb9e663276e7216ce88c88dc31ba7e881a41a --- /dev/null +++ b/marked/Rel-16/23_series/23732/0997dbaa9dfecedd60029d70b53327b8_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f9c699a872d27f86aa8a199a30272839967fe6bb7fe7d6edfe8b1634989253d7 +size 36402 diff --git a/marked/Rel-16/23_series/23732/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/marked/Rel-16/23_series/23732/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e76323221913ea9cf9be754a75ecf8ace216d412 --- /dev/null +++ b/marked/Rel-16/23_series/23732/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e8b8ecca27c8beec0bd39c57656517de360eb57ebdea592becdde3629d879722 +size 57413 diff --git a/marked/Rel-16/23_series/23732/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg b/marked/Rel-16/23_series/23732/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bbd8c677b2175e834c9c5f0e5b194ae41c7b72ea --- /dev/null +++ b/marked/Rel-16/23_series/23732/0ea87c5f55e5857d0969bc5ca36dccba_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2c253cd00bdc661b551b9aec7afac4328619511a11a183f4d55cbcb8438f86e0 +size 52031 diff --git a/marked/Rel-16/23_series/23732/0f1767577a073167eb9628d72034e083_img.jpg b/marked/Rel-16/23_series/23732/0f1767577a073167eb9628d72034e083_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..ad288ebf8d4ce890392a6230451a9a8e14cfc8fe --- /dev/null +++ b/marked/Rel-16/23_series/23732/0f1767577a073167eb9628d72034e083_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9b208ef3305f822dd60af768d683d4974c25281c38126b5243480d75dac95b30 +size 42125 diff --git a/marked/Rel-16/23_series/23732/13fde41de77bf026013a0b81684d1fc9_img.jpg b/marked/Rel-16/23_series/23732/13fde41de77bf026013a0b81684d1fc9_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7823822c382062b578294f199603f502d60a15d1 --- /dev/null +++ b/marked/Rel-16/23_series/23732/13fde41de77bf026013a0b81684d1fc9_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:1c29ce15471b774f84f88830c60ad74350044786aa4ba518cc4ea5349a3f2cf8 +size 55985 diff --git a/marked/Rel-16/23_series/23732/18291be12b470a557e8c9f3a74e021be_img.jpg b/marked/Rel-16/23_series/23732/18291be12b470a557e8c9f3a74e021be_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6ec88d2ecc945d3de98e8e6b98d9b65d3bb6dd21 --- /dev/null +++ b/marked/Rel-16/23_series/23732/18291be12b470a557e8c9f3a74e021be_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cab9919b4936eedc344c54d9c1d77e42ece199bd1a2abda160ebda183de2f962 +size 33349 diff --git a/marked/Rel-16/23_series/23732/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/marked/Rel-16/23_series/23732/1a827b10290f33d4fec04d0e8ef7a897_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..eb4753c3233663f7dc3c8f1a649463456ebd0956 --- /dev/null +++ b/marked/Rel-16/23_series/23732/1a827b10290f33d4fec04d0e8ef7a897_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bd8f8c9853c68c74abf6ea49e0fcef91df78bc6ba335c98d8f0b9a34941b881f +size 51201 diff --git a/marked/Rel-16/23_series/23732/21ad58fee90f2be50708ff541d225507_img.jpg b/marked/Rel-16/23_series/23732/21ad58fee90f2be50708ff541d225507_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e8d3f785e3885accf44f62a76bb64aa43f7dd13e --- /dev/null +++ b/marked/Rel-16/23_series/23732/21ad58fee90f2be50708ff541d225507_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4c0ad04d91ad44459f3068bdcfef579ba814686050ba9216d7b880676b8e83f2 +size 42558 diff --git a/marked/Rel-16/23_series/23732/23cb65390082ab306c15bd3d8196135e_img.jpg b/marked/Rel-16/23_series/23732/23cb65390082ab306c15bd3d8196135e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..781a6cee2e71168203b22f9ad00cbc15af03af1e --- /dev/null +++ b/marked/Rel-16/23_series/23732/23cb65390082ab306c15bd3d8196135e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6814fbb5bd94c841473efb3e47b07970258fce71c4af18999a5887d4c1d0f802 +size 47927 diff --git a/marked/Rel-16/23_series/23732/26d664119ad25250780f554633444e54_img.jpg b/marked/Rel-16/23_series/23732/26d664119ad25250780f554633444e54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..21403f2dbbee552199fc4eb457e730964337ad97 --- /dev/null +++ b/marked/Rel-16/23_series/23732/26d664119ad25250780f554633444e54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:57e276dbfa989cc7af797cb96a4051b3b6c84751c680ff5f9aacf204fec8c374 +size 56960 diff --git a/marked/Rel-16/23_series/23732/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/marked/Rel-16/23_series/23732/27b06ec9f42b5d727a2630f61a5f1861_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a6b048ddaeefdb66480725f7e70e71bd3fb1c471 --- /dev/null +++ b/marked/Rel-16/23_series/23732/27b06ec9f42b5d727a2630f61a5f1861_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:33faaadd871eabf8d6f76df8e40417ce56f933f17815d05a0e4c570bb1c99bee +size 95509 diff --git a/marked/Rel-16/23_series/23732/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/marked/Rel-16/23_series/23732/2837ffdadcdb1e5bababa56b564e56ed_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c7a18991c9a7722fb06761cc048a9b89f988da4f --- /dev/null +++ b/marked/Rel-16/23_series/23732/2837ffdadcdb1e5bababa56b564e56ed_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7a87f0ce02567709f4470394fb9bb9f7f09b0202bdfb0432724a2571e93ce0b2 +size 37250 diff --git a/marked/Rel-16/23_series/23732/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/marked/Rel-16/23_series/23732/28d75f39a24203712ee907b32cf0bbe5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70357b694b720c0bb5d263f50fc0b30eddd90476 --- /dev/null +++ b/marked/Rel-16/23_series/23732/28d75f39a24203712ee907b32cf0bbe5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0f7524e630ab1fa2b2d7830960d416791340dc5dc26294db02edb65c723662b7 +size 60942 diff --git a/marked/Rel-16/23_series/23732/2dc649aff45a8a0924db45fc3bd6aabb_img.jpg b/marked/Rel-16/23_series/23732/2dc649aff45a8a0924db45fc3bd6aabb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f043194460fea148fb5b75412c269a14f6c81b8b --- /dev/null +++ b/marked/Rel-16/23_series/23732/2dc649aff45a8a0924db45fc3bd6aabb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d662b8b4fedc8aed7991804c72c4d3997727883f920ca22062db1c1356252b46 +size 53411 diff --git a/marked/Rel-16/23_series/23732/3263a25e110201638bda790456af2909_img.jpg b/marked/Rel-16/23_series/23732/3263a25e110201638bda790456af2909_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6574468b61391abbcfd0f583ab5a3e635c123098 --- /dev/null +++ b/marked/Rel-16/23_series/23732/3263a25e110201638bda790456af2909_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fe7120bee0885cead9d63c9d89fe7ddd4ed8a9660aae42df4bab7b36065cc5db +size 30387 diff --git a/marked/Rel-16/23_series/23732/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/marked/Rel-16/23_series/23732/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..42c6fabc3578d75458bfc754a9eae6ac28f10b31 --- /dev/null +++ b/marked/Rel-16/23_series/23732/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4cd11dc9f00057867c97a1472d0b43e348c73dac3a1fc9fb13d7b189fd5aca2a +size 44845 diff --git a/marked/Rel-16/23_series/23732/367378559e35017a5e1a6f5c30798c5a_img.jpg b/marked/Rel-16/23_series/23732/367378559e35017a5e1a6f5c30798c5a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..cb6b0c7b68ee1a88e73157692cc0c00cfbf2d55c --- /dev/null +++ b/marked/Rel-16/23_series/23732/367378559e35017a5e1a6f5c30798c5a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3f3c67bd45072c14dea6f9b769092af5c40498980714d77329dea4b13c207191 +size 28316 diff --git a/marked/Rel-16/23_series/23732/36fd537a1e39baa2471ecfaaf869751a_img.jpg b/marked/Rel-16/23_series/23732/36fd537a1e39baa2471ecfaaf869751a_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f4a3ae57ec72928b887423b507c8954017a04e7c --- /dev/null +++ b/marked/Rel-16/23_series/23732/36fd537a1e39baa2471ecfaaf869751a_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f3b8bc0adb0bc24020d214febc6c814c084d8f5886d197092ef01c65e4033fd1 +size 58703 diff --git a/marked/Rel-16/23_series/23732/376f80eb8a41369e87da63a0210d173e_img.jpg b/marked/Rel-16/23_series/23732/376f80eb8a41369e87da63a0210d173e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bf77b16ceca1c6da3ff6ba4f4eac9d1398e1fa8 --- /dev/null +++ b/marked/Rel-16/23_series/23732/376f80eb8a41369e87da63a0210d173e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cca416aa060cba149d78ed0143d21b315f4d278e1138e568d6f3ad4f4fe87b6f +size 48027 diff --git a/marked/Rel-16/23_series/23732/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/marked/Rel-16/23_series/23732/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f9cbaba64a9f78ac885161abe663241222e08ba6 --- /dev/null +++ b/marked/Rel-16/23_series/23732/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6c7be7039d2dbef4c69dd103fc7c524584c2560a41604f9559abd18a42659336 +size 67123 diff --git a/marked/Rel-16/23_series/23732/3da1a07cb87051bf616c9876db958cf0_img.jpg b/marked/Rel-16/23_series/23732/3da1a07cb87051bf616c9876db958cf0_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..04c1454b76c5200eee2d350eee7ec9e24141b541 --- /dev/null +++ b/marked/Rel-16/23_series/23732/3da1a07cb87051bf616c9876db958cf0_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:fba5f457064ea9cdf47017b621dc2867addbafabde13fdba03d7ed471195d35c +size 65400 diff --git a/marked/Rel-16/23_series/23732/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg b/marked/Rel-16/23_series/23732/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..01ce84cba45fafce1c33a18c5f775dada24f9918 --- /dev/null +++ b/marked/Rel-16/23_series/23732/3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:8234e64f8bed5512bed5fac44bc379476f83070b69704748846eee76dce9f80f +size 33098 diff --git a/marked/Rel-16/23_series/23732/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/marked/Rel-16/23_series/23732/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..45bac7e644c8c819b500f720f0c5006afff07383 --- /dev/null +++ b/marked/Rel-16/23_series/23732/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ed83265f9d366d7b69aff5e3ccbf951b741eddc37cccfc336921a3ec2632b2d6 +size 47883 diff --git a/marked/Rel-16/23_series/23732/42e18c25bfd455a5a57f207bacfcb970_img.jpg b/marked/Rel-16/23_series/23732/42e18c25bfd455a5a57f207bacfcb970_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2fbb63c4d40422b5084e3e1888de491c319036cf --- /dev/null +++ b/marked/Rel-16/23_series/23732/42e18c25bfd455a5a57f207bacfcb970_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:bbb8e8bad50304558611d277f856781608cd2f7811ac30cf020743c7a8880bd4 +size 54171 diff --git a/marked/Rel-16/23_series/23732/43979979715bb3304389a0cb18f34444_img.jpg b/marked/Rel-16/23_series/23732/43979979715bb3304389a0cb18f34444_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7357aa831c5a06e1b1a03fcdf586e1b4ef24c60c --- /dev/null +++ b/marked/Rel-16/23_series/23732/43979979715bb3304389a0cb18f34444_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:4a7ec29b6fb078ba24f7c8238b08fefddf1f9f2984a0cb2bfc5682f44a87ba3e +size 47089 diff --git a/marked/Rel-16/23_series/23732/48f209b7c0c1f91af40cfc3466dbd534_img.jpg b/marked/Rel-16/23_series/23732/48f209b7c0c1f91af40cfc3466dbd534_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..0e9ee212dadd954c8ac52edfd16ff0d1476ba758 --- /dev/null +++ b/marked/Rel-16/23_series/23732/48f209b7c0c1f91af40cfc3466dbd534_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9d1f641694631a891aa30a2dd3419ad00ed2d1196dd7808f8434dc7f93c066ac +size 26740 diff --git a/marked/Rel-16/23_series/23732/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg b/marked/Rel-16/23_series/23732/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..005e8d2fad9f0283220b7091e59825ff39beef80 --- /dev/null +++ b/marked/Rel-16/23_series/23732/4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a7cf3740304d01a34d992a5ec10047f751e0027212d65d1860382225357a7290 +size 57229 diff --git a/marked/Rel-16/23_series/23732/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg b/marked/Rel-16/23_series/23732/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..83d3579fcd898872f89d30209b0121bcd8fc2059 --- /dev/null +++ b/marked/Rel-16/23_series/23732/4cde160bcc69b7b6c81b648dd0e4252e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:d08a5f6b95e8718b739158528695fb0701b022319dfa47cb3450977d28d9b808 +size 56913 diff --git a/marked/Rel-16/23_series/23732/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/marked/Rel-16/23_series/23732/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7bcd51c0c1849dde5a74cc68b13233161e927c2a --- /dev/null +++ b/marked/Rel-16/23_series/23732/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0b789132b0cdec97c6613d22f1bc3c3c6e7acef646aa1f6c3f84f43be6c3d554 +size 28461 diff --git a/marked/Rel-16/23_series/23732/5e9af8986a5845504f251d3079da8078_img.jpg b/marked/Rel-16/23_series/23732/5e9af8986a5845504f251d3079da8078_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..e2ae7f4d54b868322c6fa331bcd3b58127781240 --- /dev/null +++ b/marked/Rel-16/23_series/23732/5e9af8986a5845504f251d3079da8078_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:939c108a8db30e03808f3abab654075d8b961ac675a0dc36ab2f148bd1421bc0 +size 39251 diff --git a/marked/Rel-16/23_series/23732/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg b/marked/Rel-16/23_series/23732/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..8e87f9427d1c28e0212fc28871fca0b6d8eed201 --- /dev/null +++ b/marked/Rel-16/23_series/23732/68a5a1a1a761c652b4b4c56da7cf9914_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:18e4ab1d763677a6aca0316595d78efcf3ebf8ea41cad5988d0d6cdddc5ab7d7 +size 42378 diff --git a/marked/Rel-16/23_series/23732/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/marked/Rel-16/23_series/23732/6e15fc9ea763541c5913d26f85072ae1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..7234f99039dd90bc7e1533b70d45e4569c2f6d31 --- /dev/null +++ b/marked/Rel-16/23_series/23732/6e15fc9ea763541c5913d26f85072ae1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:f86858ed0090711eef93458f384c8774490e7a3ac3d8ebc0769a2e2a2edbc4ef +size 31711 diff --git a/marked/Rel-16/23_series/23732/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg b/marked/Rel-16/23_series/23732/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..f35c354b047464c427b693730148a47aa9a3eec1 --- /dev/null +++ b/marked/Rel-16/23_series/23732/7d3d5fb5d09c0cd35a9d637be241651e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:05266be9fd131e1327e71d36b5bbb104002fca1e461cfb3e67c098e6b01cc51e +size 44324 diff --git a/marked/Rel-16/23_series/23732/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg b/marked/Rel-16/23_series/23732/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..845660c7b887edd84e4c9fad8f809fab09d36160 --- /dev/null +++ b/marked/Rel-16/23_series/23732/7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6ba0d8de4a9a0bd0a8f6db73b9cd8cf4e3e682a1a32c7961aa16d5f048e73686 +size 65467 diff --git a/marked/Rel-16/23_series/23732/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/marked/Rel-16/23_series/23732/7e670a2b556b53ea9002dfff3a420e08_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..65ad57d596e32295aa10cf7fad4c169a2186992c --- /dev/null +++ b/marked/Rel-16/23_series/23732/7e670a2b556b53ea9002dfff3a420e08_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7c111abbc5fb32842531c6a1fc4e60a98443e414fff269db0cbf06928ef22aa8 +size 45041 diff --git a/marked/Rel-16/23_series/23732/7ed5d5770331f31ade15439a21c31425_img.jpg b/marked/Rel-16/23_series/23732/7ed5d5770331f31ade15439a21c31425_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..dccf558c22d730e95e6286bb09d171a985872211 --- /dev/null +++ b/marked/Rel-16/23_series/23732/7ed5d5770331f31ade15439a21c31425_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:38946e1a308df6d5328afb33e5d06abacb69ca85d5c8835e914d5d8bc3ebe2e9 +size 40195 diff --git a/marked/Rel-16/23_series/23732/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/marked/Rel-16/23_series/23732/7efae06af3af43ffe5d4b956a679cf54_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0d8f8a28b2aa5bec9978ee27369cb33227c378c --- /dev/null +++ b/marked/Rel-16/23_series/23732/7efae06af3af43ffe5d4b956a679cf54_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:ba26846808ed01491695774f611a39a72f776178bec55e520d0f4051aa5885dd +size 68672 diff --git a/marked/Rel-16/23_series/23732/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/marked/Rel-16/23_series/23732/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..27fe34a6e1006fb3b3a605b03c226afcf991700f --- /dev/null +++ b/marked/Rel-16/23_series/23732/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:04854388a9c85f2f3ad9894859d75ee6add90321d19e0ff450e197cb2968e385 +size 49465 diff --git a/marked/Rel-16/23_series/23732/844077b3034f0030b404207db0ad76b4_img.jpg b/marked/Rel-16/23_series/23732/844077b3034f0030b404207db0ad76b4_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..a0c59c7581d5eaabc149a82f44bb5ac6afe5a858 --- /dev/null +++ b/marked/Rel-16/23_series/23732/844077b3034f0030b404207db0ad76b4_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:7068ebe772ba30d8f99fec9d201aa6f8a382b4cb721ace4efa16b9a79adcfbdc +size 67159 diff --git a/marked/Rel-16/23_series/23732/90ddb84c323b956e2d50a54d3f870566_img.jpg b/marked/Rel-16/23_series/23732/90ddb84c323b956e2d50a54d3f870566_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..926e88f359da44cc8243a4e9b0c65d2065cd0d75 --- /dev/null +++ b/marked/Rel-16/23_series/23732/90ddb84c323b956e2d50a54d3f870566_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d71182b5a456f8f5aa2ad0581d0d6fc756380fb604bb2a54ab440aa5882dc2f +size 56460 diff --git a/marked/Rel-16/23_series/23732/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/marked/Rel-16/23_series/23732/9c1d3678db4a12d5864cb2a4def1135d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..bcb7a58ba0d88b7acff936a3d276e8214ad71b21 --- /dev/null +++ b/marked/Rel-16/23_series/23732/9c1d3678db4a12d5864cb2a4def1135d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:634f3c1f65c58fe5bdf40ce5870e957ee48bca4c5a89adf44a989c1e8bb5d44f +size 56850 diff --git a/marked/Rel-16/23_series/23732/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/marked/Rel-16/23_series/23732/a26e142d3df5bef41a84a9dd099d7825_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..3640b78f36c3bdb156508db6e36282d1bb6e102f --- /dev/null +++ b/marked/Rel-16/23_series/23732/a26e142d3df5bef41a84a9dd099d7825_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:859a469ac7a25ccb313fecb416dbafba26275d8398f9678be12c13ec7aec57b6 +size 54345 diff --git a/marked/Rel-16/23_series/23732/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/marked/Rel-16/23_series/23732/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..577f186027145c9fdfff98ce1a95fffc5ac75f16 --- /dev/null +++ b/marked/Rel-16/23_series/23732/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:289a3bbbb0ff380169c1cbebc546706bd40cb5bf08de1c533fddaabd67eb6e4c +size 55517 diff --git a/marked/Rel-16/23_series/23732/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/marked/Rel-16/23_series/23732/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6bf213c09dfc9efd400203ecfc70a95fe4d1cf1f --- /dev/null +++ b/marked/Rel-16/23_series/23732/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cf7f6addfc6524e41a5fc60e1ae74904b73d72b188210ec77389587406f52017 +size 54892 diff --git a/marked/Rel-16/23_series/23732/b4f6d3668f7e851eaff07ccf26001623_img.jpg b/marked/Rel-16/23_series/23732/b4f6d3668f7e851eaff07ccf26001623_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..c173777c03d0782e2d89c0d9e8ce6dad3ab84d87 --- /dev/null +++ b/marked/Rel-16/23_series/23732/b4f6d3668f7e851eaff07ccf26001623_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3d8c7b0afdfa16fe824b6d5830830d05b29d8e900fa5f79ea5c8900cf95c5599 +size 45504 diff --git a/marked/Rel-16/23_series/23732/b5335262987c819d7f71ce40f99cb71b_img.jpg b/marked/Rel-16/23_series/23732/b5335262987c819d7f71ce40f99cb71b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..b43c68f5f4e0f171fcc6be9b7622b4a684950b8c --- /dev/null +++ b/marked/Rel-16/23_series/23732/b5335262987c819d7f71ce40f99cb71b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:c725c25a332dcc6237898ea16b11c3f7cce42e46b65f80520f4a493656e81477 +size 26035 diff --git a/marked/Rel-16/23_series/23732/b5987d63203a5fa601921039922ac520_img.jpg b/marked/Rel-16/23_series/23732/b5987d63203a5fa601921039922ac520_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..214508851100ff5051b5d347de8cd7ac676c66bd --- /dev/null +++ b/marked/Rel-16/23_series/23732/b5987d63203a5fa601921039922ac520_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3225ff7f8c1e78417e366ec84c7b656cab2862af219a1723650f7d398d936e72 +size 47447 diff --git a/marked/Rel-16/23_series/23732/b6ad8b32179842fca5ad086cf22b03eb_img.jpg b/marked/Rel-16/23_series/23732/b6ad8b32179842fca5ad086cf22b03eb_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..2c151a6d9f8630590177c8ef4e013048e5506922 --- /dev/null +++ b/marked/Rel-16/23_series/23732/b6ad8b32179842fca5ad086cf22b03eb_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:2549e23fac687eaa1f441b42806bb69b743abaa943c3f04536666f92b64f97f1 +size 62987 diff --git a/marked/Rel-16/23_series/23732/db39acbd11df5eb7e79ab84562fb8f74_img.jpg b/marked/Rel-16/23_series/23732/db39acbd11df5eb7e79ab84562fb8f74_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..47a0d07089527bc822fffe96e95c4b718e8fecfc --- /dev/null +++ b/marked/Rel-16/23_series/23732/db39acbd11df5eb7e79ab84562fb8f74_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:0d2360abe91e6ce395ca5885717d748b126db315ffad4b9951ef12aa047eb923 +size 50117 diff --git a/marked/Rel-16/23_series/23732/dd5771673aececa53d42ece89218299d_img.jpg b/marked/Rel-16/23_series/23732/dd5771673aececa53d42ece89218299d_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..70cc89642e1cf8b8085045cd61480a897459e57c --- /dev/null +++ b/marked/Rel-16/23_series/23732/dd5771673aececa53d42ece89218299d_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cac39e4b010d7e49626e2c50dfb58868c6a0faba920d5aa151d392ee5cfa085c +size 63860 diff --git a/marked/Rel-16/23_series/23732/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/marked/Rel-16/23_series/23732/e2c120be98ede6deb60dd341f5a9803b_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..d99377fca75df985a752b4e824257c1d184652d9 --- /dev/null +++ b/marked/Rel-16/23_series/23732/e2c120be98ede6deb60dd341f5a9803b_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:e51a11859b232efc175756084e26bb8ab27e910aa98051770738c2b7717e587b +size 47989 diff --git a/marked/Rel-16/23_series/23732/e94cbc0895c6914a2bb53f150ab7495e_img.jpg b/marked/Rel-16/23_series/23732/e94cbc0895c6914a2bb53f150ab7495e_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..4e09ca8e535a27fb6133403c1d7a437a959acbf0 --- /dev/null +++ b/marked/Rel-16/23_series/23732/e94cbc0895c6914a2bb53f150ab7495e_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:29e14221f5aba04c8385a917ef4cd9b7ca8105be6f936a433738ac3ef83c0122 +size 77115 diff --git a/marked/Rel-16/23_series/23732/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg b/marked/Rel-16/23_series/23732/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg new file mode 100644 index 0000000000000000000000000000000000000000..5f2392e94a81e42ef9e8200b68b1858eb51ebf48 --- /dev/null +++ b/marked/Rel-16/23_series/23732/fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:5bdd119a189f53555be271b4f966d7a568bce75f824be2c4e6881d624355a9e9 +size 63313 diff --git a/marked/Rel-16/23_series/23732/raw.md b/marked/Rel-16/23_series/23732/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..6d4f81271335dbdbe17107d3c61865bb094795b2 --- /dev/null +++ b/marked/Rel-16/23_series/23732/raw.md @@ -0,0 +1,2990 @@ + + +# **3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on User data interworking, coexistence and migration (Release 16)** --- + +## --- **Keywords** + +3GPP, 5G, Architecture, Coexistence, +Interworking, Migration, Study + +## **3GPP** + +## --- **Postal address** + +## --- **3GPP support office address** + +650 Route des Lucioles - Sophia Antipolis +Valbonne - FRANCE +Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 + +## --- **Internet** + + + +## --- **Copyright Notification** + +No part may be reproduced except as authorized by written permission. +The copyright and the foregoing restriction extend to reproduction in all media. + +© 2019, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). +All rights reserved. + +UMTSTM is a Trade Mark of ETSI registered for the benefit of its members +3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +LTE™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners +GSM® and the GSM logo are registered and owned by the GSM Association + +# Contents + +| | | +|------------------------------------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 6 | +| 1 Scope..... | 7 | +| 2 References..... | 7 | +| 3 Definitions and abbreviations ..... | 8 | +| 3.1 Definitions..... | 8 | +| 3.2 Abbreviations ..... | 8 | +| 4 Architectural Assumptions and Principles..... | 8 | +| 4.1 Architectural Assumptions..... | 8 | +| 4.2 Architectural Principles..... | 9 | +| 5 Key Issues ..... | 9 | +| 5.1 Key Issue 1: Interaction between UDM and HSS with separate repositories..... | 9 | +| 5.1.1 Description ..... | 9 | +| 5.2 Key Issue 2: Supporting a common repository for both HSS and UDM..... | 10 | +| 5.2.1 Description ..... | 10 | +| 6 Solutions..... | 10 | +| 6.1 Solution #1: Retrieving subscription data from separate UDR repositories for EPS and 5GS subscription data using a UDR Translation Function (UTF)..... | 10 | +| 6.1.1 Introduction ..... | 10 | +| 6.1.2 High-level Description ..... | 10 | +| 6.1.3 Services and Illustrated Procedures..... | 11 | +| 6.1.3.1 General..... | 11 | +| 6.1.3.2 5GS to EPS Interworking when N26 is not supported ..... | 13 | +| 6.1.3.2.1 5GS to EPS handover..... | 13 | +| 6.1.3.2.2 EPS to 5GS handover..... | 14 | +| 6.1.3.3 Terminating Access Domain Selection (T-ADS) ..... | 16 | +| 6.1.3.3.1 Alternative 1 ..... | 16 | +| 6.1.3.3.2 Alternative 2..... | 18 | +| 6.1.3.4 P-CSCF restoration..... | 18 | +| 6.1.4 Impacts on existing services and interfaces..... | 18 | +| 6.1.5 Evaluation..... | 19 | +| 6.2 Solution #2: Direct SBA UDM-HSS Interworking..... | 19 | +| 6.2.1 Introduction ..... | 19 | +| 6.2.2 High-level Description ..... | 19 | +| 6.2.3 Services and Illustrated Procedures..... | 21 | +| 6.2.3.1 General..... | 21 | +| 6.2.3.2 Subscriber Profile Indications..... | 22 | +| 6.2.3.3 Authentication..... | 22 | +| 6.2.3.3.1 Single AV Generation Engine in HSS(AuC) and Credentials stored in EPC-UDR ..... | 22 | +| 6.2.3.3.2 Single AV Generation Engine in UDM and Credentials stored in UDR ..... | 23 | +| 6.2.3.4 Mobility Scenarios..... | 24 | +| 6.2.3.4.1 Mobility from 5GC to EPC, single registration, with N26 Interface ..... | 24 | +| 6.2.3.4.2 Mobility from EPC to 5GC, single registration, with N26 Interface ..... | 25 | +| 6.2.3.4.3 Interworking without N26 Interface..... | 26 | +| 6.2.3.5 T-ADS..... | 27 | +| 6.2.3.6 P-CSCF Restoration..... | 27 | +| 6.2.3.7 SMS support ..... | 28 | +| 6.2.3.7.1 Terminating SMS location query ..... | 28 | +| 6.2.3.7.2 Terminating SMS delivery failure..... | 29 | +| 6.2.3.7.3 SMS Alerting..... | 30 | +| 6.2.4 Impacts on existing services and interfaces..... | 31 | +| 6.2.5 Evaluation..... | 32 | +| 6.3 Solution #3: UDM/HSS FE interaction reusing legacy protocol ..... | 32 | +| 6.3.1 Introduction ..... | 32 | + +| | | | +|-----------|-----------------------------------------------------------------------------------------------------------------|----| +| 6.3.2 | High-level Description ..... | 32 | +| 6.3.2.1 | Authentication..... | 32 | +| 6.3.2.2 | IP address continuity of interworking without N26 from 5GS to EPS..... | 33 | +| 6.3.2.3 | T-ADS for IMS voice ..... | 34 | +| 6.3.2.4 | Supporting IMS related procedures ..... | 35 | +| 6.3.2.5 | SMS over NAS ..... | 36 | +| 6.3.3 | Services and Illustrated Procedures..... | 37 | +| 6.3.3.1 | Authentication..... | 37 | +| 6.3.3.2 | IP address continuity of interworking without N26 from 5GS to EPS..... | 39 | +| 6.3.3.3 | T-ADS for IMS voice ..... | 40 | +| 6.3.3.4 | Supporting IMS related procedures ..... | 41 | +| 6.3.3.5 | SMSF address storage and retrieval..... | 42 | +| 6.3.4 | Impacts on existing services and interfaces..... | 43 | +| 6.3.4.1 | Authentication impacts ..... | 43 | +| 6.3.4.2 | IP address continuity impacts ..... | 43 | +| 6.3.4.3 | T-ADS for voice impacts..... | 43 | +| 6.3.4.4 | Supporting IMS related procedures ..... | 43 | +| 6.3.5 | Evaluation..... | 44 | +| 6.4 | Solution #4: Use of a Data Access Layer for interaction between HSS FE and UDM with common repository..... | 44 | +| 6.4.1 | Introduction ..... | 44 | +| 6.4.2 | High-level Description ..... | 44 | +| 6.4.2.1 | Assumptions..... | 44 | +| 6.4.2.2 | Architectural proposal..... | 45 | +| 6.4.3 | Services and Illustrated Procedures..... | 46 | +| 6.4.3.1 | General description ..... | 46 | +| 6.4.3.2 | 5GS procedures..... | 46 | +| 6.4.3.3 | EPS procedures ..... | 47 | +| 6.4.3.4 | Handover procedures ..... | 47 | +| 6.4.3.4.0 | General ..... | 47 | +| 6.4.3.4.1 | 5GS to EPS with N26..... | 49 | +| 6.4.3.4.2 | EPS to 5GS with N26..... | 49 | +| 6.4.3.4.3 | 5GS to EPS without N26 - single registration..... | 50 | +| 6.4.3.4.4 | EPS to 5GS without N26 - single registration..... | 50 | +| 6.4.3.4.5 | Handovers without N26 - dual registration ..... | 50 | +| 6.4.3.5 | IMS interaction ..... | 50 | +| 6.4.3.5.1 | Access to IMS data..... | 50 | +| 6.4.3.5.2 | P-CSCF Restoration procedures..... | 51 | +| 6.4.3.5.3 | Terminating domain selection information for IMS voice..... | 52 | +| 6.4.4 | Impacts on existing services and interfaces..... | 53 | +| 6.4.4.1 | General ..... | 53 | +| 6.4.4.2 | Summary of impacts on UDM..... | 54 | +| 6.4.4.3 | Summary of impacts on HSS FE ..... | 54 | +| 6.4.4.4 | Summary of impacts on EPS UDR..... | 54 | +| 6.4.5 | Evaluation..... | 54 | +| 6.5 | Solution #5: Use of a Data Access Layer for interaction between HSS FE and UDM with separate repositories ..... | 55 | +| 6.5.1 | Introduction ..... | 55 | +| 6.5.2 | High-level Description ..... | 55 | +| 6.5.2.1 | Assumptions..... | 55 | +| 6.5.2.2 | Architectural proposal..... | 56 | +| 6.5.3 | Services and Illustrated Procedures..... | 57 | +| 6.5.3.1 | General description ..... | 57 | +| 6.5.3.2 | 5GS procedures..... | 58 | +| 6.5.3.3 | EPS procedures ..... | 58 | +| 6.5.3.4 | Handover procedures ..... | 58 | +| 6.5.3.4.0 | General ..... | 58 | +| 6.5.3.4.1 | 5GS to EPS with N26..... | 60 | +| 6.5.3.4.2 | EPS to 5GS with N26..... | 61 | +| 6.5.3.4.3 | 5GS to EPS without N26 - single registration..... | 61 | +| 6.5.3.4.4 | EPS to 5GS without N26 - single registration..... | 61 | +| 6.5.3.4.5 | Handovers without N26 - dual registration ..... | 62 | + +| | | | +|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------|-----------| +| 6.5.3.5 | IMS interaction ..... | 62 | +| 6.5.3.5.1 | Access to IMS data..... | 62 | +| 6.5.3.5.2 | P-CSCF Restoration procedures..... | 62 | +| 6.5.3.5.3 | Terminating domain selection information for IMS voice..... | 63 | +| 6.5.4 | Impacts on existing services and interfaces..... | 64 | +| 6.5.4.1 | General..... | 64 | +| 6.5.4.2 | Summary of impacts on UDM..... | 65 | +| 6.5.4.3 | Summary of impacts on HSS FE ..... | 65 | +| 6.5.4.4 | Summary of impacts on EPS UDR or 5G repository ..... | 65 | +| 6.5.5 | Evaluation..... | 65 | +| 6.6 | Solution #6: Deployment and coexistence without interworking between UDM and existing HSS..... | 66 | +| 6.6.1 | Introduction ..... | 66 | +| 6.6.2 | High-level Description ..... | 66 | +| 6.6.3 | Services and Illustrated Procedures..... | 70 | +| 6.6.4 | Impacts on existing services and interfaces..... | 70 | +| 6.6.5 | Evaluation..... | 70 | +| 7 | Evaluation ..... | 70 | +| 7.1 | Evaluation of solutions..... | 70 | +| 7.1.1 | Evaluation of solutions with separation of FEs and repositories ..... | 71 | +| 7.1.2 | Evaluation of solutions with separation of FEs with common repository..... | 72 | +| 7.1.3 | Evaluation of solutions with common FEs with separate repositories..... | 72 | +| 7.1.4 | Evaluation of solutions with common FEs with common repository ..... | 73 | +| 8 | Conclusions..... | 73 | +| 8.1 | For EPS and 5GS interworking required for mobility cases from EPS to 5GS and from 5GS to EPS,
including the impacts on SMS handling ..... | 73 | +| 8.2 | For IMS and 5GS interworking required for T-ADS, P-CSCF restoration and NPLI retrieval ..... | 73 | +| Annex A: | Change history ..... | 75 | + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- 1 Scope + +The objective of this Technical Report is to investigate scenarios for co-existence of subscription data pertaining to legacy system (EPS) with data pertaining to the 5G system, when the HSS+UDM defined in Rel-15 is separated and both UDM and HSS are independent, and will propose solutions to support this deployment where necessary. + +NOTE 1: The subscription data referred to by this Technical Report comprises both static as well as dynamic data, including IMS, LCS, SMS data. + +- study diverse scenarios related to the storage of subscription data including, but not limited to, those of common repository for subscription data from EPS and 5GS, as well as separate repositories for EPS and 5GS subscription data, +- investigate the relevant procedures in TS 23.502 [2] (for e.g. authentication, mobility, handover and procedures for IMS and SMS handling in interworking between 5G system and EPS), +- determine if there is a need for interaction between the consumers of EPS and 5GS data, in the different interworking cases and deployment scenarios. + +Existing procedures in TS 23.502 [2] shall not be impacted. + +Provisioning aspects are outside this study. + +Direct interactions between the EPS UDR and the 5GS UDR are out of the scope of this TR (i.e. it is assumed that there is no direct interaction between these two repositories). + +# --- 2 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: "Vocabulary for 3GPP Specifications". +- [2] 3GPP TS 23.502: "Procedures for the 5G System". +- [3] 3GPP TS 23.335: "User Data Convergence (UDC); Technical realization and information flows; Stage 2". +- [4] 3GPP TS 29.335: "User Data Convergence (UDC); User data repository access protocol over the Ud interface; Stage 3". +- [5] 3GPP TS 23.002: "Network architecture". +- [6] 3GPP TS 23.501: "System Architecture for the 5G System". +- [7] 3GPP TS 23.228: "IP Multimedia Subsystem". +- [8] 3GPP TS 23.380: "IMS Restoration Procedures". +- [9] 3GPP TS 29.505: "5G System; Usage of the Unified Data Repository services for Subscription Data". + +- [10] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents". +- [11] 3GPP TS 29.328: "IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents". +- [12] 3GPP TS 33.501: "Security architecture and procedures for 5G System". +- [13] 3GPP TS 33.401: "System Architecture Evolution (SAE) - Security architecture". +- [14] 3GPP TS 23.794: "Study on Enhanced IMS to 5GC Integration". +- [15] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2". +- [16] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access". +- [17] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3". +- [18] 3GPP TS 29.214: "Policy and charging control over Rx reference point". + +# --- 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. + +**5G Repository:** Repository hosting subscription data for 5G UEs. + +**5GS UDR:** term used to identify the Unified Data Repository defined in TS 23.501 [6] (clause 4.2.5). + +**EPS UDR:** term used to identify the User Data Repository defined in TS 23.335 [3] (clause 4.2.3). + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. + +| | | +|---------|-------------------------------------------------------------------------------------| +| 5GC | 5G Core | +| 5GS | 5G System | +| 5GS UDR | 5G Unified Data Repository | +| HSS FE | Home Subscriber Server Front End | +| EPS | Enhanced Packet core System | +| EPS UDR | EPS User Data Repository | +| E-UTRAN | Evolved Universal mobile telecommunications system Terrestrial Radio Access Network | +| UDM | Unified Data Management | + +# --- 4 Architectural Assumptions and Principles + +## 4.1 Architectural Assumptions + +The 5GS data storage architecture defined in TS 23.501 [6], for structured data, is used as the baseline network architecture. + +The User Data Convergence concept specified in TS 23.335 [3], is used for reference to EPS/legacy system architecture for data storage, when layered architecture is deployed (i.e. application front-end decoupled from data repository using the standard interface Ud defined in TS 29.335 [4]). + +The Home Subscriber Server (HSS) architecture specified in clause 4.1.1 of TS 23.002 [5], is used for reference to EPS/legacy system architecture for data storage, when non-layered HSS architecture is deployed (i.e. monolithic deployment where user data are stored within the entity itself (or in an external entity via non-standard interfaces)). + +## 4.2 Architectural Principles + +In the UDC concept used for reference, HSS FE and EPS UDR defined in TS 23.335 [3] are assumed to interact for any data required by the study: no standardization will be considered for the interface between HSS FE and EPS UDR. + +# --- 5 Key Issues + +## 5.1 Key Issue 1: Interaction between UDM and HSS with separate repositories + +### 5.1.1 Description + +This key issue, which assumes the HSS is deployed using the UDC architecture in TS 23.335 [3], is to study how the UDM and HSS with separate repositories interact in the scenario that the HSS FE and UDM are separately deployed and the user data of 5G and 4G/3G/2G are also stored separately in different repositories (i.e. EPS UDR storing user data for 4G/3G/2G and IMS domains and 5GS UDR storing user data for 5G domain). + +The interaction between UDM and HSS FE with separate repositories should be based on specific procedures that require data from one to the other. + +The solutions to this key issue need to: + +- Clarify what user data is involved for the interaction between UDM and HSS FE with separate repositories; +- Study the scenarios of interaction between UDM and HSS FE with separate repositories, specifically: + - IMS and 5GS interworking required for the following cases: + - Terminating Access Domain Selection (T-ADS). + +When requested by IMS, the HSS+UDM shall be able to query the serving AMF for T-ADS related information (see clause 5.16.3.6 in TS 23.501 [6]). + +- P-CSCF Restoration + - As defined in clause 5.8.4 in TS 23.380 [8], upon request by IMS when P-CSCF failure is detected, the HSS+UDM shall send a P-CSCF restoration indication to either the SMF serving the IMS PDU session for the UE or to the AMF serving the UE. + - Network Provided Location Information (NPLI). + - As defined in clause Y.6 in TS 23.228 [7], an IMS AS can trigger the retrieval of the user location and/or UE Time Zone information from the AMF via the HSS+UDM. +- EPS and 5GS interworking required for mobility cases from EPS to 5GS and from 5GS to EPS, including the impacts on SMS handling. +- Avoid the impact on existing procedures between HSS/UDM and the rest of the network. + +## 5.2 Key Issue 2: Supporting a common repository for both HSS and UDM + +### 5.2.1 Description + +This key issue studies network deployments where a common repository (acting as EPS UDR and 5GS UDR) is shared between HSS and UDM, analyses the interactions between the HSS, UDM, & common repository, and examines the potential of shared data fields in the repository. + +The solutions to this key issue need to: + +- Study the scenarios of interaction between UDM and HSS FE with common repository, specifically: + +- IMS and 5GS interworking required for the following cases: + +- Terminating Access Domain Selection (T-ADS). + +When requested by IMS, the HSS+UDM shall be able to query the serving AMF for T-ADS related information (see clause 5.16.3.6 in TS 23.501 [6]). + +- P-CSCF Restoration + +As defined in clause 5.8.4 in TS 23.380 [8], upon request by IMS when P-CSCF failure is detected, the HSS+UDM shall send a P-CSCF restoration indication to either the SMF serving the IMS PDU session for the UE or to the AMF serving the UE. + +- Network Provided Location Information (NPLI). + +As defined in clause Y.6 in TS 23.228 [7], an IMS AS can trigger the retrieval of the user location and/or UE Time Zone information from the AMF via the HSS+UDM. + +- EPS and 5GS interworking required for mobility cases from EPS to 5GS and from 5GS to EPS, including the impacts on SMS handling. + +# --- 6 Solutions + +## 6.1 Solution #1: Retrieving subscription data from separate UDR repositories for EPS and 5GS subscription data using a UDR Translation Function (UTF) + +### 6.1.1 Introduction + +Solution #1 addresses Key Issue 1. + +### 6.1.2 High-level Description + +It is proposed to introduce a UTF (UDR Translation Function) to allow subscription data exchange between the HSS FE and the UDM when each function has a separate UDR repository. The UTF is a logical function that can be standalone or collocated with the UDM or HSS FE. The assumption with the proposed architecture is that the UDR database of the UDM contains the related 5G subscription data, whereas the UDR of the HSS FE contains the related EPS and IMS subscription data. + +The UTF function contains a translation table that allows conversion of an Nudr to a Ud request and vice versa. If the UDM requires information from the EPS UDR, the UTF allows facilitating translation of an Nudr request to Ud request. If the HSS FE requires information from the UDM UDR the UTF is responsible to convert the Ud request to an Nudr request targeting specific subscription data based on the semantics defined in TS 29.505 [9]. + +NOTE: The UTF would require to implement a translation table supporting the HSS FE vendor specific Ud implementation. + +The architecture is illustrated below: + +![Figure 6.1.2-1: UDM/HSS FE interworking architecture diagram](7e670a2b556b53ea9002dfff3a420e08_img.jpg) + +The diagram illustrates the interworking architecture between 5G and EPS systems. At the top, the 5GS UDR is connected to the PCF and UDM via Nudr interfaces. The EPS UDR is connected to the HSS FE via a Ud interface. The PCF and UDM are connected to the 5G Core via Npcf/Namf and Nudm interfaces respectively. The UDM is connected to the UDR Translation Function via a Nudr interface. The UDR Translation Function is connected to the HSS FE via a Ud interface. The HSS FE is connected to the IMS core via a Cx interface, to the SMS via a MAP interface, to the MSC/legacy core via a MAP interface, and to the 4G Core via an S6a interface. + +Figure 6.1.2-1: UDM/HSS FE interworking architecture diagram + +Figure 6.1.2-1: UDM/HSS FE interworking architecture + +### 6.1.3 Services and Illustrated Procedures + +#### 6.1.3.1 General + +When the HSS FE or UDM determine that subscription data needs to be fetched from a different UDR an Ud or Nudr message requesting subscription details is sent to UTF. The UTF translates the message into the corresponding message towards the HSS FE (Ud message) or UDM (Nudr message) that is proxied towards the UDR (Option 1). The UTF may also provide the translated message directly to the target UDR repository bypassing the target HSS FE or UDM (Option 2). + +An example procedure is illustrated below: + +![Sequence diagram showing the procedure to retrieve subscription data from a separate UDR repository. The diagram involves five lifelines: HSS FE, UDR (EPS), UTF, UDM, and UDR (5G). The process starts with a Subscription request to HSS FE. HSS FE identifies subscription data on external UDR and constructs a Ud message. UTF translates Ud to Nudr. The diagram then branches into two options: Option 1 (UDM proxies Nudr message to UDR (5G) to fetch data) and Option 2 (UTF sends Nudr message directly to UDR (5G)). Both options result in a Nudr response back to UTF, which translates it to Ud response. Finally, HSS FE sends a Subscription Request Response/Update location ack.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) + +``` + +sequenceDiagram + participant External + participant HSS_FE as HSS FE + participant UDR_EPS as UDR (EPS) + participant UTF + participant UDM + participant UDR_5G as UDR (5G) + + External->>HSS_FE: 1. Subscription request + HSS_FE->>HSS_FE: 2. Identify subscription data on external UDR + HSS_FE->>HSS_FE: 3. Construct Ud message to fetch subscription data + HSS_FE->>UTF: 4. Ud message + UTF->>UTF: 5. Translate Ud to Nudr + Note right of UTF: Option 1 + UTF->>UDM: 6. Nudr message + UDM->>UDM: 7. Proxy Nudr message + UDM->>UDR_5G: 8. Nudr message + UDR_5G->>UDR_5G: Fetch subscription data + UDR_5G->>UDM: 9. Nudr response + UDM->>UTF: 10. Nudr response + Note right of UTF: Option 2 + UTF->>UDR_5G: Nudr message + UDR_5G->>UTF: Nudr response + UTF->>UTF: 11. Translate Nudr to Ud + UTF->>HSS_FE: 12. Ud response + HSS_FE->>External: 13. Subscription Request Response/Update location ack + +``` + +Sequence diagram showing the procedure to retrieve subscription data from a separate UDR repository. The diagram involves five lifelines: HSS FE, UDR (EPS), UTF, UDM, and UDR (5G). The process starts with a Subscription request to HSS FE. HSS FE identifies subscription data on external UDR and constructs a Ud message. UTF translates Ud to Nudr. The diagram then branches into two options: Option 1 (UDM proxies Nudr message to UDR (5G) to fetch data) and Option 2 (UTF sends Nudr message directly to UDR (5G)). Both options result in a Nudr response back to UTF, which translates it to Ud response. Finally, HSS FE sends a Subscription Request Response/Update location ack. + +**Figure 6.1.3.1-1: Procedure to retrieve subscription data from separate UDR repository** + +The following cases have been identified where subscription data are retrieved from different UDR: + +- 5GS to EPS interworking when no N26 is supported: In 5GS to EPS handover, the HSS FE retrieves from the 5GS UDR the PGW-C+SMF ID in order to establish a UE requested PDN connection. In EPS to 5GS handover the UDM retrieves from the EPS UDR the PGW-C+SMF ID in order to establish a PDU session. + +- Support of T-ADS: When IMS core interfaces with the HSS FE and the UE is camped on a 5G network the HSS FE retrieves from the 5GS UDR the IMS over PS support and current RAT type. + +#### 6.1.3.2 5GS to EPS Interworking when N26 is not supported + +##### 6.1.3.2.1 5GS to EPS handover + +During 5GS to EPS handover when the HSS FE receives the Update Location Request from the MME (as described in step 8 of Figure 4.11.2.2-1 of TS 23.502 [2]) the HSS FE needs to retrieve the address of the combo PGW-C+SMF. The HSS FE is aware that the information is located at the 5G UDR as the UPDATE LOCATION REQUEST includes information that registration of an AMF shall not be cancelled. The HSS FE sends a vendor specific Ud request towards the UTF. The UTF must translate the vendor specific Ud request from the HSS FE to an Nudr\_DM\_Query service request including a Data Subset "UE Context in SMF data" towards the 5GS UDR (the Nudr request may be proxied via the UDM to the 5GS UDR). + +![Sequence diagram showing the interaction between HSS FE, UDR (EPS), UTF, UDM, and UDR (5G) for 5GS to EPS handover. The HSS FE receives an Update Location Request and needs to retrieve the PGW-C+SMF ID from the 5G UDR. It constructs a Ud message, which the UTF translates to an Nudr_DM_Query. The UDR (5G) fetches the subscription data and returns an Nudr response. The UTF translates this back to a Ud response, which the HSS FE uses to send an Update Location Ack.](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) + +``` + +sequenceDiagram + participant External + participant HSS_FE as HSS FE + participant UDR_EPS as UDR (EPS) + participant UTF + participant UDM + participant UDR_5G as UDR (5G) + + External->>HSS_FE: 1. Update Location Request +(step 8 of Figure 4.11.2.2-1 +of 3GPP TS 23.502) + HSS_FE->>HSS_FE: 2. Identify subscription data on external UDR + HSS_FE->>HSS_FE: 3. Construct Ud message to fetch subscription data + HSS_FE->>UTF: 4. Ud message + Note right of UTF: 5. Translate Ud to Nudr + UTF->>UDR_5G: 6. Nudr_DM_Query ("UE Context in SMF Data") + Note right of UDR_5G: Fetch subscription data + UDR_5G->>UDM: 8. Nudr response + Note right of UTF: 9. Translate Nudr to Ud + UTF->>HSS_FE: 10. Ud response + HSS_FE->>External: 11. Update Location Ack + +``` + +Sequence diagram showing the interaction between HSS FE, UDR (EPS), UTF, UDM, and UDR (5G) for 5GS to EPS handover. The HSS FE receives an Update Location Request and needs to retrieve the PGW-C+SMF ID from the 5G UDR. It constructs a Ud message, which the UTF translates to an Nudr\_DM\_Query. The UDR (5G) fetches the subscription data and returns an Nudr response. The UTF translates this back to a Ud response, which the HSS FE uses to send an Update Location Ack. + +Figure 6.1.3.2.1-1: HSS FE retrieves PGW-C + SMF ID from 5G UDR + +If during 5GS to EPS interworking the UE indicates that dual registration is not supported the HSS needs to notify the UDM to deregister the UE from the 5G network. Such notification can be supported indirectly via the UDR. The steps required are: + +- The HSS FE creates a vendor specific Ud request to delete the 5G subscription data of the UE from the 5G UDR +- The UTF translates the request into an Nudr\_DM\_Update message including information to remove all related 5G subscription data for the UE from the 5G UDR +- The 5G UDR deletes the subscription data and notify the UDM of the result using an Nudr\_DM\_Notify service operation +- The UDM notifies the AMF of the deregistration by invoking the Nudm\_UECM\_DeregistrationNotify service operation + +The steps are shown in the Figure below: + +![Sequence diagram showing the indirect procedure for the HSS to notify the UDM to deregister the UE from the 5G network. The diagram involves seven lifelines: MME, HSS FE, UDR (EPS), UTF, AMF, UDM, and UDR (5G). The process starts with the MME sending an Update Location Request to the HSS FE. The HSS FE identifies that dual registration is not supported and constructs a Ud message to delete subscription data in the 5G UDR. This message is sent to the UTF, which translates it into an Nudr_DM_Update message for the UDR (5G). The UDR (5G) responds with an Nudr response, then sends an Nudr_DM_Notify to the UDM, which in turn sends an Nudm_UECM_DeregistrationNotify to the AMF. The AMF responds with a Nud response, then sends an Nudm_SDM_Unsubscribe to the UDM, which finally responds with an Nudr response.](a26e142d3df5bef41a84a9dd099d7825_img.jpg) + +``` + +sequenceDiagram + participant MME + participant HSS_FE as HSS FE + participant UDR_EPS as UDR (EPS) + participant UTF + participant AMF + participant UDM + participant UDR_5G as UDR (5G) + + MME->>HSS_FE: 1. Update Location Request (step 8 of Figure 4.11.2.2-1 of 3GPP TS 23.502) + Note over HSS_FE: 2. Identify dual registration is not supported + Note over HSS_FE: 3. Construct Ud message to delete subscription data in 5G UDR + HSS_FE->>UTF: 4. Ud message(delete UE context) + Note over UTF: 5. Translate Ud to Nudr + UTF->>UDR_5G: 6. Nudr_DM_Update(UE subscription5G data) + UDR_5G-->>UTF: Nudr response + UDR_5G->>UDM: 7. Nudr_DM_Notify + UDM-->>UDR_5G: Nudr response + UDM->>AMF: 8. Nudm_UECM_DeregistrationNotify + AMF-->>UDM: Nud response + AMF->>UDM: 9. Nudm_SDM_Unsubscribe + UDM-->>AMF: Nudr response + +``` + +Sequence diagram showing the indirect procedure for the HSS to notify the UDM to deregister the UE from the 5G network. The diagram involves seven lifelines: MME, HSS FE, UDR (EPS), UTF, AMF, UDM, and UDR (5G). The process starts with the MME sending an Update Location Request to the HSS FE. The HSS FE identifies that dual registration is not supported and constructs a Ud message to delete subscription data in the 5G UDR. This message is sent to the UTF, which translates it into an Nudr\_DM\_Update message for the UDR (5G). The UDR (5G) responds with an Nudr response, then sends an Nudr\_DM\_Notify to the UDM, which in turn sends an Nudm\_UECM\_DeregistrationNotify to the AMF. The AMF responds with a Nud response, then sends an Nudm\_SDM\_Unsubscribe to the UDM, which finally responds with an Nudr response. + +**Figure 6.1.3.2.1-1: Indirect procedure for the HSS to notify the UDM to deregister the UE from the 5G network** + +##### 6.1.3.2.2 EPS to 5GS handover + +When the UDM requires the PGW-C+SMF ID the UDM sends an Nudr\_DM\_Query service request including a Data Subset "UE Context in SMF data" towards the UTF to retrieve the address. The UTF translates the Nudr request into a vendor specific Ud request in order to retrieve the same information from the EPS UDR. The UDM knows that the information required is located at the EPS UDR as the AMF sends an Update Location Request message to the UDM including the ULR-Flags indicating that registration of an MME shall not be cancelled. + +![Sequence diagram showing the interaction between UDM, UDR (5G), UTF, HSS FE, and UDR (EPS) to retrieve PGW-C + SMF ID from EPS UDR.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) + +``` + +sequenceDiagram + participant External + participant UDM + participant UDR_5G as UDR (5G) + participant UTF + participant HSS_FE as HSS FE + participant UDR_EPS as UDR (EPS) + + External->>UDM: 1. Update Location Request (step 5 of Figure 4.11.2.3-1 of 3GPP TS 23.502) + Note right of UDM: 2. Identify subscription data on external UDR + Note right of UDM: 3. Construct Nudr message to fetch subscription data + UDM->>UTF: 4. Nudr_DM_Query Request("UE Context in SMF Data") + Note right of UTF: 5. Translate Nudr to Ud + UTF->>UDR_EPS: 6. Ud message + Note right of UDR_EPS: Fetch subscription data + UDR_EPS->>UTF: 8. Ud response + Note right of UTF: 9. Translate Ud to Nudr + UTF->>UDM: 10. Nudr_DM_Query response( PGW-C + SMF ID) + UDM->>External: 11. Update Location Ack + +``` + +Sequence diagram showing the interaction between UDM, UDR (5G), UTF, HSS FE, and UDR (EPS) to retrieve PGW-C + SMF ID from EPS UDR. + +**Figure 6.1.3.2.2-1: UDM retrieves PGW-C + SMF ID from EPS UDR** + +If during EPS to 5G interworking the UE indicates that dual registration is not supported the UDM needs to notify the HSS to deregister the UE from the EPS network. The steps required are: + +- The UDM creates an Nudr\_DM\_Update request to delete the EPS subscription data +- The UTF translates the request into a vendor specific Ud request +- The EPS UDR deletes the subscription data and notify the HSS of the result +- The HSS notifies the MME of the deregistration by invoking a Cancel Location request. + +The steps are shown in the Figure below: + +![Sequence diagram illustrating the indirect procedure for the UDM to notify the HSS to deregister the UE from the EPS network. The diagram shows interactions between AMF, UDM, UDR(5G), UTF, MME, HSS, and UDR(EPS).](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UDM + participant UDR5G as UDR(5G) + participant UTF + participant MME + participant HSS + participant UDREPS as UDR(EPS) + + AMF->>UDM: 1. Update Location Request (step 5 of Figure 4.1.1.2.3-1 of 3GPP TS23.502) + UDM->>UDM: 2. Identify dual registration is not supported + UDM->>UDM: 3. Construct Ud message to delete subscription data in 5G UDR + UDM->>UTF: 4. Nudr_DM_Update(delete UE context) + UTF->>UTF: 5. Translate Nudr to Ud + UTF->>UDREPS: 6. Ud message + UDREPS->>HSS: 7. Ud notify + HSS->>MME: 8. Cancel Location + Note right of MME: Deletes UE context + MME->>HSS: 9. Cancel Location Ack + +``` + +Sequence diagram illustrating the indirect procedure for the UDM to notify the HSS to deregister the UE from the EPS network. The diagram shows interactions between AMF, UDM, UDR(5G), UTF, MME, HSS, and UDR(EPS). + +**Figure 6.1.3.2.2-2: Indirect procedure for the UDM to notify the HSS to deregister the UE from the EPS network** + +#### 6.1.3.3 Terminating Access Domain Selection (T-ADS) + +##### 6.1.3.3.1 Alternative 1 + +This alternative assumes the IMS network interfaces only with the HSS FE over Sh interface. + +When the HSS FE requires the homogeneous IMS voice over PS supporting indication and the UE is camped on 5G network, the HSS FE constructs a Ud request to retrieve the subscription information from the 5G UDR + +NOTE 1: It is assumed that the HSS FE first sends a request to retrieve the related information from the 4G UDR. When the 4G UDR responds that there is no 4G related subscription content the HSS FE determines that the user is camped on 5G access and re-sends the Ud message towards the UTF. + +The UTF must translate the vendor specific Ud request from the HSS FE to an Nudr\_DR\_Get service request including a Data Subset "Amf3GPPAccessRegistration" towards the 5GS UDR (the Nudr request may be proxied via the UDM to the UDR). + +NOTE 2: For T-ADS it is not possible to obtain the most recent access network capabilities for domain selection. The T-ADS makes the decision based on whether IMS over PS session is supported homogeneously over all TAs served by the AMF. + +If the network does not support N26 then the UE may operate in Dual Registration mode. In that case a UE may have an PDN connection for IMS over EPS core or an PDU session for IMS over 5G core. When the IMS AS requires the most recent access network capabilities for domain selection the IMS AS interrogates the HSS. + +One method to support the case of UEs in Dual Registration mode is for the IMS AS to derive from the P-Access-Network-Info header the core network access path (i.e. via EPS or 5G core) via which the UE has established an IMS session. When the IMS AS requires T-ADS information, the IMS AS includes in the Sh request the information on the network node (MME or AMF) that needs to be triggered. + +The IMS AS can derive the path (EPS or 5G core) via which a UE has established an IMS session from the "P-Access-Network-Info" header when the following take place: + +- P-CSCF adds within the PANI header the "access-class" field corresponding to the IP-CAN type provided by the PCRF as described in TS 24.229 [17] +- P-CSCF obtains from the PCRF via Rx the IP-CAN type when the PCRF subscribes to be informed of the IP-CAN type as described in TS 29.214 [18] + +NOTE 3: The above procedure may require further normative work in stage 3 + +This is illustrated schematically below taking into account that the IMS AS supports an Sh interface only towards the HSS. + +![Sequence diagram illustrating the support of T-ADS when the UE operates in Dual Registration mode (example of UE accessing IMS via 5G core).](21ad58fee90f2be50708ff541d225507_img.jpg) + +``` + +sequenceDiagram + participant UE + participant UDR_5G as UDR (5G) + participant UTF + participant HSS + participant IMS_AS as IMS AS + + Note right of IMS_AS: 2. Identifies that the user is on 5G core access + Note right of HSS: 4. Identifies that the user is on 5G core access + Note right of UTF: 6 Translate Ud to Nudr message + Note right of UDR_5G: 8. Obtain T-ADS info + + UE->>IMS_AS: 1. SIP Registration 5G core access (PANI includes Access Class 3GPP-NR) + IMS_AS->>HSS: 3. Request T-ADS information (Requested Node=AMF) + HSS->>UTF: 5. Ud message (T-ADS info) + UTF->>UDR_5G: 7. Nudr message (T-ADS info) + UDR_5G->>UTF: 9. Nudr response + UTF->>HSS: 10. Ud response + HSS->>IMS_AS: 11. Sh message (T-ADS info) + +``` + +Sequence diagram illustrating the support of T-ADS when the UE operates in Dual Registration mode (example of UE accessing IMS via 5G core). + +**Figure 6.1.3.3.1-1: Support of T-ADS when the UE operates in Dual Registration mode (example of UE accessing IMS via 5G core)** + +1. UE registers with IMS including the PANI header as specified in TS 24.229 [17] via the 5G core network +2. IMS AS identifies from the PANI header that the UE is accessing the 5G core network access +3. When the IMS AS requires T-ADS information the IMS AS includes in the Sh request information on the node that contain the information +4. The HSS identifies from the Sh request that T-ADS information is available from the 5G UDR +5. HSS constructs a Ud message towards the UTF +6. UTF converts the Ud to a Nudr message +7. UTF sends the Nudr message to the UDR of the UDM +8. The UDR obtains the T-ADS info +9. The UDR provides the T-ADS info within the Nudr response to the UTF +10. The UTF translates Nudr response to a Ud response and sends to HSS +11. HSS provides the T-ADS info within the Sh response to the IMS AS. + +##### 6.1.3.3.2 Alternative 2 + +This alternative assumes that the IMS AS can interface to both HSS and UDM over Sh interface. In such a case the IMS AS can obtain the most recent access network capabilities for domain selection by interrogating the HSS and UDM. + +When the UE is in dual registration the IMS AS can derive from the P-Access-Network-Info header the core network access path for IMS (i.e. via EPS or 5G core) via which the UE has established an IMS session. When the IMS AS requires T-ADS information the IMS AS interrogates the HSS or the UDM based on the derived core network access path for IMS. + +It is important to note that additional enhancements to UDM - IMS core network interaction will be defined by FS\_eIMS5G study where an SBI interface between the UDM and IMS AS will be supported. In such case support of lite Sh interface at the UDM will not be required and an SBI interface can be used instead. + +#### 6.1.3.4 P-CSCF restoration + +The P-CSCF restoration is an optional feature allowing the IMS network to notify the HSS or UDM to re-establish the IMS related PDU session in case of P-CSCF failure. + +One approach to support this feature is the S-CSCF to support a Cx interface to both HSS and UDM. In case of P-CSCF failure, the S-CSCF reports failure to the UDM or HSS. + +For networks that do not support N26, when the UE is in dual registration mode the S-CSCF can derive from the P-Access-Network-Info header the core network access path for IMS (i.e. via EPS or 5G core) via which the UE has established an IMS session. When the S-CSCF initiates P-CSCF restoration procedure the S-CSCF triggers the HSS or the UDM based on the derived core network access path for IMS. + +The UDM would support limited Cx functionality to be notified by the S-CSCF of a P-CSCF failure. Once notified the UDF invokes the procedures described in clause 5.8 of TS 23.380 [8]. + +NOTE: The IMS network interfaces with the HSS (i.e. via Cx/Sh interfaces) for any IMS related subscription information. + +It is important to note that additional enhancements to UDM - IMS core network interaction will be defined by FS\_eIMS5G study where an SBI interface between the UDM and S-CSCF will be supported. In such case support of lite Cx interface at the UDM will not be required and an SBI interface can be used instead. + +### 6.1.4 Impacts on existing services and interfaces + +The impacts are as follows: + +- HSS FE + - Identifies that subscription information is stored on a UDR repository containing 5GS subscription data + - For option 1: proxies a Ud request/answer from the UTF/UDR respectively +- UDM + - Identifies that subscription information is stored on a UDR repository containing EPS subscription data + - For Option 1: proxies an Nudr request/answer from the UTF/UDR respectively. +- S-CSCF + - When the network uses the P-CSCF restoration procedure via the AMF, the S-CSCF interrogates the HSS FE and the UDM in order to identify the serving network and report the P-CSCF failure + - For networks supporting no N26, where the UE operates in Dual Registration case, the S-CSCF uses the P-Access-Network-Info header to identify if the UE is accessing IMS via 5G or EPS access +- IMS AS + - For networks supporting no N26, where the UE operates in Dual Registration case, the IMS AS uses the P-Access-Network-Info header to identify if the UE is accessing IMS via 5G or EPS access + +### 6.1.5 Evaluation + +Solution 1 proposes an architecture that does not require direct interaction between the UDM and the HSS FE. The solution requires a new function (UTF) that translate subscription data exchange between the HSS FE and the UDM where each have a separate UDR repository. The solution assumes that the UDR of the HSS contains EPS and IMS subscription details whereas the UDR of the UDM contain 5G subscription details only. It is also assumed that the HSS contain all IMS subscription related information. The solution requires the standalone HSS to support the functionality to retrieve information from the UDR of the UDM in certain scenarios (e.g. T-ADS for IMS) as described in clause 6.1.3 of the present TR. The advantages of this solution is that: + +- It avoids defining a new interface between the HSS and UDM which would require both legacy HSS and UDM to support a new interface. +- It is possible to introduce only UDM and 5G UDR when deploying a 5GS system, without having to update/upgrade either HSS FE or the EPS UDR, or having to introduce these functionalities in deployments with single core networks. +- Standardisation is minimised and restricted to potential incorporation of lite Sh/Cx interfaces for the UDM, or even not needed in case the FS\_eIMS5G study incorporates the needed interactions of UDM with IMS +- Introduction of a UTF does not affect other network functions that may be accessing the different repositories, while it provides the means to further split other network functions defined in Rel-15 (i.e. PCF/PCRF). + +The disadvantage is that a new UTF is deployed in an operator's network that requires to support a vendor specific Ud implementation of the deployed HSS. + +Limitations of the solution are as follows: + +- Support of T-ADS: When the UE is camped on 5G core network the IMS AS can obtain T-ADS information only if there is homogeneous IMS voice over PS support. +- Support of P-CSCF restoration via HSS: When the UE is camped on 5G core network P-CSCF restoration is not possible via the HSS as the HSS cannot directly trigger the UDM to trigger P-CSCF restoration. + +The limitations can be solved with the following additions: + +- Support of T-ADS: UDM implements a lite Sh implementation. IMS AS triggers UDM directly for any T-ADS information. Requires the IMS AS to be aware of the core network access path for IMS sessions by inspecting the P-Access-Network-Identifier header. +- Support of P-CSCF restoration: Support of P-CSCF restoration is also supported via the PCRF/PCF which has no impacts on HSS/UDM. Alternatively, the UDM can implement a lite Cx implementation. S-CSCF triggers UDM directly for P-CSCF restoration. Requires the S-CSCF to be aware of the core network access path for IMS sessions by inspecting the P-Access-Network-Identifier header. + +## 6.2 Solution #2: Direct SBA UDM-HSS Interworking + +### 6.2.1 Introduction + +This solution is applicable to key issues 1 and 2. + +This solution proposes a new Service Based Interface between UDM and HSS. + +### 6.2.2 High-level Description + +This contribution proposes a service based interface between HSS and UDM. The architecture for this solution is outlined in the following figure: + +![Figure 6.2.2-1: Architecture for Direct UDM-HSS Interworking with independent UDRs](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) + +This diagram illustrates the architecture for direct UDM-HSS interworking with independent UDRs. At the top, two separate User Data Repositories are shown: 'UDR (5G)' and 'UDR (4G/IMS)'. The 'UDR (5G)' is connected to a 'UDM' (Unified Data Management) via the 'Nudr' interface. The 'UDR (4G/IMS)' is connected to an 'HSS' (Home Subscriber Server) via the 'Ud' interface. The 'UDM' and 'HSS' are grouped together in a dashed box labeled 'Combined HSS/UDM' and are interconnected by a red line labeled 'Nxx'. Below this box, the 'UDM' connects to a '5GC' (5G Core) via the 'N8/N10/N21' interface. The 'HSS' connects to an 'EPC' (PDN Gateway) via the 'S6a' interface and to an 'IMS' (IP Multimedia Subsystem) via the 'Cx/Sh' interface. The '5GC' and 'EPC' are connected to each other via the 'N26' interface. A common horizontal line at the bottom connects the '5GC', 'EPC', and 'IMS'. + +Figure 6.2.2-1: Architecture for Direct UDM-HSS Interworking with independent UDRs + +Figure 6.2.2-1: Architecture for Direct UDM-HSS Interworking with independent UDRs + +![Figure 6.2.2-2: Architecture for Direct UDM-HSS Interworking with a common repository](3da1a07cb87051bf616c9876db958cf0_img.jpg) + +This diagram illustrates the architecture for direct UDM-HSS interworking with a common repository. At the top, a 'Common repository (4G/IMS/5G)' is shown, which contains two sub-data sections: '5G subs data' and '4G/IMS subs data'. The '5G subs data' is connected to a 'UDM' (Unified Data Management) via the 'Nudr' interface. The '4G/IMS subs data' is connected to an 'HSS' (Home Subscriber Server) via the 'Ud' interface. The 'UDM' and 'HSS' are grouped together in a dashed box labeled 'Combined HSS/UDM' and are interconnected by a red line labeled 'Nxx'. Below this box, the 'UDM' connects to a '5GC' (5G Core) via the 'N8/N10/N21' interface. The 'HSS' connects to an 'EPC' (PDN Gateway) via the 'S6a' interface and to an 'IMS' (IP Multimedia Subsystem) via the 'Cx/Sh' interface. The '5GC' and 'EPC' are connected to each other via the 'N26' interface. A common horizontal line at the bottom connects the '5GC', 'EPC', and 'IMS'. + +Figure 6.2.2-2: Architecture for Direct UDM-HSS Interworking with a common repository + +Figure 6.2.2-2: Architecture for Direct UDM-HSS Interworking with a common repository + +A new reference point between UDM and HSS within the combined HSS/UDM (i.e. Nxx as depicted in Figures 6.2.2-1 and 6.2.2-2) is proposed. The new interface for interworking between HSS and UDM is proposed to be based on SBI principles. + +NOTE: The UDM and the HSS may be deployed in a stand-alone manner and could be from different vendors. + +### 6.2.3 Services and Illustrated Procedures + +Figure 6.2.3-1 shows a high-level illustration of the EPS/IMS and 5GS interworking procedures that requires interworking via HSS/UDM for procedures triggered from the EPS/IMS. + +#### 6.2.3.1 General + +![Sequence diagram illustrating HSS-UDM Interworking between 5GC, UDM, HSS, and IMS Core EPC. Steps 2 and 5 are highlighted in red as new service operations.](4cc7cdce3d498d8b0ba033a9be24ade5_img.jpg) + +``` + +sequenceDiagram + participant 5GC + participant UDM + participant HSS + participant IMS Core EPC + + IMS Core EPC->>HSS: 1. Cx/Sh/S6a Request (e.g. P-CSCF Resto, TADS, NPLI, ULR) + HSS->>UDM: 2. Nudm_newservice_Req (e.g. P-CSCF Resto, TADS, NPLI, AMF deReg) + UDM->>5GC: 3. Nudm/Namf Service Req (e.g. P-CSCF Resto, TADS, NPLI, AMF deReg) + 5GC->>UDM: 4. Nudm/Namf Service Resp (e.g. TADS, NPLI) + UDM->>HSS: 5. Nudm_newservice_Resp (e.g. P-CSCF Resto, TADS, NPLI, AMF deReg) + HSS->>IMS Core EPC: 6. Cx/Sh/S6a Response (e.g. P-CSCF Resto, TADS, NPLI, ULA) + +``` + +Sequence diagram illustrating HSS-UDM Interworking between 5GC, UDM, HSS, and IMS Core EPC. Steps 2 and 5 are highlighted in red as new service operations. + +**Figure 6.2.3-1: High Level Illustration of HSS-UDM Interworking** + +1. IMS/EPC interacts with HSS over existing interfaces for the purpose of e.g. Updating Location of an MME in HSS, and/or requesting HSS to execute some actions in the access network (e.g. P-CSCF restoration) or retrieve some information from the access network (e.g. TADS or NPLI information). +2. Depending on the type of request, the HSS may be able to serve the request and reply to the request with no interaction with UDM (e.g. for ULR from MME or P-CSCF restoration request from S-CSCF). In this case, the HSS replies the request as in step 6. + + Otherwise, the HSS interacts with UDM over the new Nxx reference point proposed in this solution using new service operations under the Nudm service set. The definition of these new service operations is out of the scope of the description of this solution. + + In either case, in a layered architecture, the HSS interacts with the 4G/IMS UDR (using Ud). The HSS does not need to retrieve any subscription data belonging to the 5G subscription profile. +3. UDM receives the request from HSS over the new Nxx reference point and interacts with the 5GC as needed using existing defined procedures. UDM interacts with the 5G UDR (using Nudr). The UDM does not need to retrieve any subscription data belonging to the 4G/IMS subscription profile. + +**Editor's note:** Analysis on the existing defined procedures in UDM that are used is FFS. + + Depending on the request, UDM may omit the request to the 5GC and reply to HSS as in step 5 based on information stored under the 5GC subscription profile (e.g. in case of a TADS requests for which the AMF has already informed UDM that "Homogeneous support for Voice over IP" is supported). + + In case of P-CSCF restoration or AMF deregistration, the UDM does not wait for the acknowledgement from 5GC, it sends the response back like in step 5. +4. 5GC replies the request from UDM including the requested information (e.g. TADS, NPLI) or confirming the execution of the requested action (e.g. P-CSCF restoration, deregistration of the UE from the AMF). +5. UDM responds to HSS including the requested information (e.g. TADS, NPLI) or confirming the execution of the requested action (e.g. for the P-CSCF restoration request, it confirms the deregistration of the UE from the AMF). + +6. HSS responds to EPC/IMS. Depending on the request, the response from HSS will include information received from 5GC via UDM (e.g. TADS, NPLI). + +Figure 6.2.3-2 shows a high-level illustration of the 5GS and EPS/IMS interworking procedures that requires interworking via HSS/UDM for procedures triggered from the 5GC. + +![Sequence diagram illustrating UDM-HSS Interworking. The diagram shows four lifelines: 5GC, UDM, HSS, and EPC. The sequence of messages is: 1. Nudm Service Req (e.g. AMF registration in UDM) from 5GC to UDM; 2. Nhss_newservice Req (e.g. Cancel MME location if any) from UDM to HSS; 3. S6a Request (e.g. CLR) from HSS to EPC; 4. S6a Response (e.g. CLA) from EPC to HSS; 5. Nhss_newservice Resp from HSS to UDM; 6. Nudm Service Resp from UDM to 5GC.](7d3d5fb5d09c0cd35a9d637be241651e_img.jpg) + +``` + +sequenceDiagram + participant 5GC + participant UDM + participant HSS + participant EPC + Note right of UDM: (UDM and HSS are in a single box) + 5GC->>UDM: 1. Nudm Service Req (e.g. AMF registration in UDM) + UDM->>HSS: 2. Nhss_newservice Req (e.g. Cancel MME location if any) + HSS->>EPC: 3. S6a Request (e.g. CLR) + EPC->>HSS: 4. S6a Response (e.g. CLA) + HSS->>UDM: 5. Nhss_newservice Resp + UDM->>5GC: 6. Nudm Service Resp + +``` + +Sequence diagram illustrating UDM-HSS Interworking. The diagram shows four lifelines: 5GC, UDM, HSS, and EPC. The sequence of messages is: 1. Nudm Service Req (e.g. AMF registration in UDM) from 5GC to UDM; 2. Nhss\_newservice Req (e.g. Cancel MME location if any) from UDM to HSS; 3. S6a Request (e.g. CLR) from HSS to EPC; 4. S6a Response (e.g. CLA) from EPC to HSS; 5. Nhss\_newservice Resp from HSS to UDM; 6. Nudm Service Resp from UDM to 5GC. + +**Figure 6.2.3-2: High Level Illustration of UDM-HSS Interworking** + +In this case, an interaction between the 5GC and the UDM (e.g. an AMF registration in UDM in the context of a mobility scenario from EPC to 5GC using interworking with N26 procedures) triggers a request from UDM to HSS over the new Nxx reference point proposed in this solution using new service operations under a new service set offered by the HSS, e.g. Nhss service set. + +Similar interactions as described for the HSS-UDM interworking for procedures triggered from the EPC/IMS apply here too. Depending on the procedure, the interactions between the UDM and the 5GC, the UDM and HSS and HSS and the EPS, may be executed asynchronously (e.g. the UDM may not wait to the response from HSS, not even to trigger the request to HSS to send a response to the 5GC). + +#### 6.2.3.2 Subscriber Profile Indications + +Different subscriber types may exist in a network with Nxx interface. For example, some subscribers will use the full network, i.e. 5GC, the EPC and the IMS, while others might use 5G and IMS but no EPC, and legacy subscribers might just remain limited to EPC and IMS services without subscription to the 5GC. The different subscription types determine, whether the use of the Nxx interface is required for a subscriber. Thus, a "5GC subscription indication" is part of the HSS subscription data as well as a "SMS via 5G NAS support" indication. Similarly, an "EPC subscription indication" and an "IMS subscription" indication are stored in the UDM subscription data. + +**Editor's note:** Requirement for "IMS subscription indication" to be confirmed. + +#### 6.2.3.3 Authentication + +If security credentials are stored in one single place in the system, there are multiple options for this storage. Some possibilities are analysed in this clause. + +##### 6.2.3.3.1 Single AV Generation Engine in HSS(AuC) and Credentials stored in EPC-UDR + +As an option, 5G and EPC users'credentials may be stored in the EPC-UDR, (i.e. credentials for existing and users with a 2/3/4G/5G subscriptions and also credentials for users with only 5G subscription) and the authentication vectors are generated in HSS(AuC). In this case, the UDM needs to retrieve the authentication vectors from the HSS. The collocation of the 5G and 4G/3G/2G credentials is required to avoid distributed vectors generation lacking coordinated Sequence numbers. + +Figure 6.2.3.3.1-1 shows the interaction in an interworking scenario with N26 interface, when the UE attaches to the 5GC, but authentication data are stored in the EPC-UDR and authentication vectors are generated in HSS(AuC). + +![Sequence diagram showing authentication in 5GC with generation of AV in HSS. Lifelines: AUSF, UDR, UDM, HSS, EPC-UDR. The HSS and EPC-UDR are grouped together in a dashed box. The sequence of messages is: 1. UDM sends Nudm_UE_Authentication_Get Req (SUPI) to AUSF; 2. UDM sends Nudr_DM_Query Req (SUPI) to UDR; 3. UDR sends Nudr_DM_Query Resp (IMSI, auth.method) to UDM; 4. UDM sends Nhss_UEAuthentication_Get Req (IMSI, auth.method) to HSS; 5. HSS sends Read (IMSI, SQN, ...) to EPC-UDR; 6. HSS generates authentication vectors in AuC; 7. HSS sends Update (SQN) to EPC-UDR; 8. HSS sends Nhss_UEAuthentication_Get Resp (authentication vectors) to UDM; 9. UDM sends Nudm_UE_Authentication_Get Resp (authentication vectors) to AUSF.](844077b3034f0030b404207db0ad76b4_img.jpg) + +``` + +sequenceDiagram + participant AUSF + participant UDR + participant UDM + subgraph HSS_EPC_UDR [ ] + participant HSS + participant EPC-UDR + end + Note right of HSS: 6. generate authentication vectors in AuC + UDM->>AUSF: 1. Nudm_UE_Authentication_Get Req (SUPI) + UDM->>UDR: 2. Nudr_DM_Query Req (SUPI) + UDR-->>UDM: 3. Nudr_DM_Query Resp (IMSI, auth.method) + UDM->>HSS: 4. Nhss_UEAuthentication_Get Req (IMSI, auth.method) + HSS->>EPC-UDR: 5. Read (IMSI, SQN, ...) + Note right of HSS: 6. generate authentication vectors in AuC + HSS->>EPC-UDR: 7. Update (SQN) + HSS-->>UDM: 8. Nhss_UEAuthentication_Get Resp (authentication vectors) + UDM-->>AUSF: 9. Nudm_UE_Authentication_Get Resp (authentication vectors) + +``` + +Sequence diagram showing authentication in 5GC with generation of AV in HSS. Lifelines: AUSF, UDR, UDM, HSS, EPC-UDR. The HSS and EPC-UDR are grouped together in a dashed box. The sequence of messages is: 1. UDM sends Nudm\_UE\_Authentication\_Get Req (SUPI) to AUSF; 2. UDM sends Nudr\_DM\_Query Req (SUPI) to UDR; 3. UDR sends Nudr\_DM\_Query Resp (IMSI, auth.method) to UDM; 4. UDM sends Nhss\_UEAuthentication\_Get Req (IMSI, auth.method) to HSS; 5. HSS sends Read (IMSI, SQN, ...) to EPC-UDR; 6. HSS generates authentication vectors in AuC; 7. HSS sends Update (SQN) to EPC-UDR; 8. HSS sends Nhss\_UEAuthentication\_Get Resp (authentication vectors) to UDM; 9. UDM sends Nudm\_UE\_Authentication\_Get Resp (authentication vectors) to AUSF. + +**Figure 6.2.3.3.1-1: Authentication in 5GC with generation of AV in HSS** + +1. The UDM receives a Nudm\_UEAuthentication\_Get Request, containing the SUPI of the user. +2. The UDM queries the UDR for the user profile belonging to the SUPI. +3. The UDM receives the user profile, which includes the IMSI, the authentication method, an EPC subscription indication, but no authentication data. +4. The UDM sends a Nhss\_UEAuthentication\_Get request to the HSS, containing the IMSI, Serving network information, and the Authentication Method (which specifies whether the 5G AKA or the EAP-AKA authentication methods is used) +5. If the EPC UDR is used, the HSS reads the IMSI, SQN and other data from the EPC-UDR. +6. The AuC as part of the HSS generates the 5G AKA or EAP-AKA authentication vectors. +7. If the EPC UDR is used, the HSS updates the SQN in the EPC-UDR. +8. The HSS provides the authentication vectors to the UDM in the Nhss\_UEAuthentication Response. +9. The UDM proceeds with the authentication. + +##### 6.2.3.3.2 Single AV Generation Engine in UDM and Credentials stored in UDR + +As an option, 5G and EPC users' credentials may be stored in the UDR (i.e. credentials for users with a 4G subscription and credentials for users with a 5G subscription) and the authentication vectors are generated in UDM(ARPF). In this case, the HSS needs to retrieve the authentication vectors from the UDM. + +Figure 6.2.3.3.2-1 shows the interaction in an interworking scenario, when the UE attaches to EPC, but authentication data is stored in the UDR. + +![Sequence diagram for Authentication in EPC with generation of AV in UDM. The diagram shows interactions between MME, HSS, UDM, and UDR. The HSS sends a Nudm_UEAuthentication_Get Req to the UDM. The UDM sends a Nudr_DM_Query req to the UDR. The UDR returns a Nudr_DM_Query resp to the UDM. The UDM generates AV in ARPF/AuC. The UDM sends a Nudr_DM_Update req to the UDR. The UDR returns a Nudr_DM_Update resp to the UDM. The UDM sends a Nudm_UEAuthentication_Get Resp to the HSS. The HSS sends an Authentication-Information-Response to the MME.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) + +``` + +sequenceDiagram + participant MME + participant HSS + participant UDM + participant UDR + Note right of UDM: 5. Generate AV in ARPF/AuC + MME->>HSS: 1. Authentication-Information-Request + HSS->>UDM: 2. Nudm_UEAuthentication_Get Req (IMSI, auth method) + UDM->>UDR: 3. Nudr_DM_Query req + UDR-->>UDM: 4. Nudr_DM_Query resp + UDM->>UDR: 6. Nudr_DM_Update req + UDR-->>UDM: 7. Nudr_DM_Update resp + UDM-->>HSS: 8. Nudm_UEAuthentication_Get Resp (authentication vectors) + HSS-->>MME: 9. Authentication-Information-Response + +``` + +Sequence diagram for Authentication in EPC with generation of AV in UDM. The diagram shows interactions between MME, HSS, UDM, and UDR. The HSS sends a Nudm\_UEAuthentication\_Get Req to the UDM. The UDM sends a Nudr\_DM\_Query req to the UDR. The UDR returns a Nudr\_DM\_Query resp to the UDM. The UDM generates AV in ARPF/AuC. The UDM sends a Nudr\_DM\_Update req to the UDR. The UDR returns a Nudr\_DM\_Update resp to the UDM. The UDM sends a Nudm\_UEAuthentication\_Get Resp to the HSS. The HSS sends an Authentication-Information-Response to the MME. + +**Figure 6.2.3.3.2-1: Authentication in EPC with generation of AV in UDM** + +1. The HSS receives an Authentication-Information-Request, containing the identification of the user. +2. The HSS sends a Nudm\_UEAuthentication\_Get request to the UDM, containing the user identification, Service Network Id (SNI) and the Authentication Method (e.g. EPS-AKA). + +NOTE: Whether one or multiple services are required, and specific naming for the operation, could be taken during normative phase. + +- 3,4. If the UDR is deployed, the UDM reads the credentials and related authentication data stored in the UDR. +5. The AuC/ARPF as part of the UDM generates the authentication vectors as requested. +- 6,7. If the UDR is used, the UDM updates the SQN in the UDR. +8. The UDM provides the authentication vectors to the HSS in the Nudm\_UEAuthentication\_Get response. +9. The HSS proceeds with the authentication. + +#### 6.2.3.4 Mobility Scenarios + +##### 6.2.3.4.1 Mobility from 5GC to EPC, single registration, with N26 Interface + +In a single registration scenario, the attachment in an MME triggers a cancellation of the AMF address in the UDM/UDR. + +Figure 6.2.3.4.1-1 shows the interaction in an interworking scenario with N26 interface, when the UE attaches to the EPC. + +![Sequence diagram for Mobility from 5GC to EPC. Lifelines: AMF, UDR, UDM, HSS, EPC-UDR, MME. The HSS and EPC-UDR are grouped together in a dashed box. The sequence of messages is: 1. S6a-ULR (IMSI) from MME to HSS; 2. Read (IMSI) from HSS to EPC-UDR; 3. Update (MME address) from HSS to EPC-UDR; 4. S6a-ULA from HSS to MME; 5. Nudm_UECM_Deregister* (IMSI) from UDM to HSS; 6. Nudm_UECM_Deregister* resp from HSS to UDM; 7. Nudr_DM_Query (IMSI) from UDM to UDR; 8. Nudm_UECM_DeregistrationNotification from UDM to AMF; 9. Nudr_DM_Update (Cancel AME address) from UDM to UDR.](26d664119ad25250780f554633444e54_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UDR + participant UDM + participant HSS + participant EPC-UDR + participant MME + + Note right of HSS: [HSS and EPC-UDR group] + + MME->>HSS: 1. S6a-ULR (IMSI) + HSS->>EPC-UDR: 2. Read (IMSI) + HSS->>EPC-UDR: 3. Update (MME address) + HSS->>MME: 4. S6a-ULA + UDM->>HSS: 5. Nudm_UECM_Deregister* (IMSI) + HSS->>UDM: 6. Nudm_UECM_Deregister* resp + UDM->>UDR: 7. Nudr_DM_Query (IMSI) + UDM->>AMF: 8. Nudm_UECM_DeregistrationNotification + UDM->>UDR: 9. Nudr_DM_Update (Cancel AME address) + +``` + +Sequence diagram for Mobility from 5GC to EPC. Lifelines: AMF, UDR, UDM, HSS, EPC-UDR, MME. The HSS and EPC-UDR are grouped together in a dashed box. The sequence of messages is: 1. S6a-ULR (IMSI) from MME to HSS; 2. Read (IMSI) from HSS to EPC-UDR; 3. Update (MME address) from HSS to EPC-UDR; 4. S6a-ULA from HSS to MME; 5. Nudm\_UECM\_Deregister\* (IMSI) from UDM to HSS; 6. Nudm\_UECM\_Deregister\* resp from HSS to UDM; 7. Nudr\_DM\_Query (IMSI) from UDM to UDR; 8. Nudm\_UECM\_DeregistrationNotification from UDM to AMF; 9. Nudr\_DM\_Update (Cancel AME address) from UDM to UDR. + +Figure 6.2.3.4.1-1: Mobility from 5GC to EPC + +1. The HSS receives an S6a ULR request containing the IMSI of the subscriber. +2. If the EPC UDR is used, the HSS reads the subscription information related to the IMSI from the EPC-UDR. In particular, it receives the 5GC subscription information. +3. If the EPC-UDR is used, the HSS updates the EPC-UDR with the new MME address. +4. The HSS responds to the MME with an S6a-ULA. +5. If the 5GC subscription indication is received in step 2, i.e. if there is an 5GC subscription for the user, then the HSS uses the Nudm\_UECM\_Deregister service of the HSS for the IMSI of the user. This does not include the AMF address as when a AMF triggers that hence this is marked with a \*. +6. The UDM responds to the HSS. +7. The UDM uses the Nudr\_DM\_Query service to retrieve the AMF address previously assigned to the UE, if any. If the UE is registered at an AMF, steps 8 and 9 are executed. +8. If there is an AMF address found for the user, the UDM cancels the attachment by sending a Nudm\_UECM\_DeregistrationNotification to the AMF. +9. In this case, the UDM also updates the UDR entry using the Nudr\_DM\_Update service. + +##### 6.2.3.4.2 Mobility from EPC to 5GC, single registration, with N26 Interface + +In a single registration scenario, the attachment in an AMF triggers a cancellation of the MME address in the HSS. + +Figure 6.2.3.4.2-1 shows the interaction in an interworking scenario with N26 interface, when the UE attaches to the 5GC. + +![Sequence diagram illustrating Mobility from EPC to 5GC. The diagram shows interactions between AMF, UDR, UDM, HSS, EPC-UDR, and MME. The HSS and EPC-UDR are grouped together in a dashed box. The sequence of messages is: 1. Nudm_UECM_Registration (SUPI) from AMF to UDM; 2. Nudr_DM_Query (SUPI) from UDM to UDR; 3. Nudr_DM_Query Resp (IMSI, EPC subscription, ...) from UDR to UDM; 4. Nudr_DM_Update (AMF address) from UDM to UDR; 5. Nhss_UECM_Deregister (IMSI) from UDM to HSS; 6. Nhss_UECM_Deregister resp from HSS to UDM; 7. Read (IMSI, ...) from HSS to EPC-UDR; 8. CLR from HSS to MME; 9. Update (MME address) from HSS to EPC-UDR.](90ddb84c323b956e2d50a54d3f870566_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UDR + participant UDM + participant HSS + participant EPC-UDR + participant MME + + Note right of HSS: [HSS and EPC-UDR Group] + + AMF->>UDM: 1. Nudm_UECM_Registration (SUPI) + UDM->>UDR: 2. Nudr_DM_Query (SUPI) + UDR-->>UDM: 3. Nudr_DM_Query Resp (IMSI, EPC subscription, ...) + UDM->>UDR: 4. Nudr_DM_Update (AMF address) + UDM->>HSS: 5. Nhss_UECM_Deregister (IMSI) + HSS-->>UDM: 6. Nhss_UECM_Deregister resp + HSS->>EPC-UDR: 7. Read (IMSI, ...) + HSS->>MME: 8. CLR + HSS-->>EPC-UDR: 9. Update (MME address) + +``` + +Sequence diagram illustrating Mobility from EPC to 5GC. The diagram shows interactions between AMF, UDR, UDM, HSS, EPC-UDR, and MME. The HSS and EPC-UDR are grouped together in a dashed box. The sequence of messages is: 1. Nudm\_UECM\_Registration (SUPI) from AMF to UDM; 2. Nudr\_DM\_Query (SUPI) from UDM to UDR; 3. Nudr\_DM\_Query Resp (IMSI, EPC subscription, ...) from UDR to UDM; 4. Nudr\_DM\_Update (AMF address) from UDM to UDR; 5. Nhss\_UECM\_Deregister (IMSI) from UDM to HSS; 6. Nhss\_UECM\_Deregister resp from HSS to UDM; 7. Read (IMSI, ...) from HSS to EPC-UDR; 8. CLR from HSS to MME; 9. Update (MME address) from HSS to EPC-UDR. + +Figure 6.2.3.4.2-1: Mobility from EPC to 5GC + +1. The UDM receives an Nudm\_UECM\_Registration request containing the SUPI of the subscriber. +2. The UDM queries the UDR with an Nudr\_DM\_query for the old AMF address and the EPC subscription indication belonging to the SUPI. +3. The UDR provides the requested data to the UDM. +4. The UDM updates the UDR with the new AMF registration data using the Nudr\_DM\_Update service. +5. If the EPC subscription indication is received in step 3, i.e. if there is an EPC subscription for the user, then the UDM uses the Nhss\_UECM\_Deregister service of the HSS for the IMSI of the user. +6. The HSS responds to the UDM. +7. If the EPC UDR is used, The HSS reads the MME mobility information in the EPC-UDR. If the UE is registered at an MME, steps 8 and 9 are executed. +8. If there is an MME address found for the user, the HSS cancels the attachment of the IMSI in the MME by sending a CLR via the S6a interface. +9. IF step 8 was executed, and EPC UDR is used, the HSS also updates the EPC-UDR entry to remove the MME assignment. + +##### 6.2.3.4.3 Interworking without N26 Interface + +For interworking without the N26 interface in Rel-15, IP address preservation is provided to UEs on inter-system mobility by storing and fetching PGW-C+SMF and corresponding APN/DDN information via the HSS+UDM, see TS 23.501 [6] clause 5.17.2.3.1. In an architecture with Nxx interface between HSS and UDM, this information must be exchanged via the Nxx interface. + +For mobility from 5GC to EPC, the HSS can use the Nudm\_SubscriberDataManagement (SDM) service for "UE context in SMF" data. + +For mobility from EPC to 5GC, the HSS Nhss\_SubscriberDataManagement service for the "UE context in PGW" provides the PDN-GW address per subscriber and APN. The UDM can use this service. + +This service is also applicable for interworking with non-3GPP access if IP address preservation is requested. + +#### 6.2.3.5 T-ADS + +Figure 6.2.3.5-1 shows the interaction when the SCC-AS sends a T-ADS query to the HSS, and the user is subscribed to 5GC as well. + +![Sequence diagram for Terminating Access Domain Selection (T-ADS) showing interactions between AMF, UDR, UDM, HSS, EPC-UDR, TAS, and EPC/MSC.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UDR + participant UDM + participant HSS + participant EPC-UDR + participant TAS + participant EPC_MSC as EPC / MSC + + Note right of HSS: [HSS and EPC-UDR group] + + TAS->>HSS: 1. Sh-UDR (T-ADS) + HSS->>EPC-UDR: 2. Read + HSS->>EPC_MSC: 3. S6a/d-IDR (TADS) and/or MAP-PSI + EPC_MSC-->>HSS: 3. S6a/d-IDR (TADS) and/or MAP-PSI + HSS->>UDM: 4. Nudm_MTProvideDomainSelectionInfo + UDM->>UDR: 5. Nudr_DM_Query + UDM-->>AMF: 6. Namf_ProvideDomainSelectionInfo + AMF-->>UDM: 7. Namf_ProvideDomainSelectionInfo resp (T-ADS info) + UDM-->>HSS: 8. Nudm_MT_ProvideDomainSelectionInfo resp (T-ADS info) + HSS->>TAS: 9. Sh-UDA (T-ADS info) + +``` + +Sequence diagram for Terminating Access Domain Selection (T-ADS) showing interactions between AMF, UDR, UDM, HSS, EPC-UDR, TAS, and EPC/MSC. + +Figure 6.2.3.5-1: Terminating Access Domain Selection + +1. The HSS receives a UDR T-ADS query from the SCC-AS over the Sh interface. +2. If EPC-UDR is used, the HSS reads the MME, SGSN, T-ADS related information and the 5G subscription indication from the EPC-UDR. +3. Depending on registration state, the HSS queries the MME and/or SGSN for IMS over PS session support. +4. If the user has a 5G subscription, the HSS requests 5GC-related T-ADS information from the UDM, using the Nudm\_MT\_ProvideDomainSelectionInfo service provided by the UDM. The HSS includes an indication, whether a time stamp of last attachment is required. +5. On receipt of the request, the UDM queries the UDR for the AMF registration state and the stored T-ADS related information (e.g. homogenous support). +6. If the user is registered in an AMF and there is no information regarding homogenous support or non-support, or if a time stamp has been requested by the HSS, the UDM sends an Namf\_MT\_ProvideDomainSelectionInfo service request to the AMF. +7. The AMF responds with the T-ADS information. +8. The UDM passes the T-ADS information to the HSS - in the response to the Nudm\_MT\_ProvideDomainSelectionInfo request. +9. The HSS combines the information related to SGSN, MME and AMF and provides it to the SCC-AS in the Sh-UDA message. + +#### 6.2.3.6 P-CSCF Restoration + +Figure 6.2.3.6-1 shows the interaction when the S-CSCF initiates a P-CSCF restoration at the HSS, and the user is attached to 5GC. In this example the AMF based restoration is shown. The procedure for the SMF follows the same approach and same method across the Nxx interface. + +![Sequence diagram for P-CSCF Restoration showing interactions between AMF, UDR, UDM, HSS, EPC-UDR, and S-CSCF.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) + +``` + +sequenceDiagram + participant S-CSCF + subgraph EPS + participant HSS + participant EPC-UDR + end + participant UDM + participant UDR + participant AMF + + Note right of S-CSCF: 1. Cx-SAR (P-CSCF restoration) + S-CSCF->>HSS: 1. Cx-SAR (P-CSCF restoration) + Note right of HSS: 2. Read + HSS->>EPC-UDR: 2. Read + Note right of HSS: 3. IMS deregistration; restoration in EPC + HSS->>HSS: 3. IMS deregistration; restoration in EPC + Note right of HSS: 4. Cx-SAA + HSS->>S-CSCF: 4. Cx-SAA + Note right of HSS: 5. Nudm_UECM_PscfRestoration + HSS->>UDM: 5. Nudm_UECM_PscfRestoration + Note right of UDM: 6. Nudr_DM_Query + UDM->>UDR: 6. Nudr_DM_Query + Note right of UDM: 7. Nudm_UECM_PscfRestoration notification + UDM->>AMF: 7. Nudm_UECM_PscfRestoration notification + Note right of UDM: 8. Nudm_UECM_PscfRestoration resp + UDM->>HSS: 8. Nudm_UECM_PscfRestoration resp + +``` + +Sequence diagram for P-CSCF Restoration showing interactions between AMF, UDR, UDM, HSS, EPC-UDR, and S-CSCF. + +Figure 6.2.3.6-1: P-CSCF Restoration + +1. The HSS receives a Cx-SAR (Server Assignment Request) message from the S-CSCF, which includes the P-CSCF restoration indication. +2. If the EPC-UDR is used, the HSS reads the subscriber data from the EPC-UDR. +3. If applicable, the HSS sends a P-CSCF restoration information towards the supporting nodes (SGSN, MME) and performs the unregistration/deregistration of the UE in IMS, as described in step 5 of TS 23.380 [8], clause 5.4.2.1. This includes the necessary updates in the EPC-UDR. +4. The HSS replies with a Cx SAA (Server Assignment Answer) to the S-CSCF. +5. In case of 5GC subscription indication, the HSS uses the enhanced Nudm\_UECM\_PscfRestoration service of the UDM to trigger the P-CSCF restoration indication in the 5GC. +6. The UDM reads the subscriber profile in the UDR to retrieve the relevant AMF address and callback-URI. +7. (copy of step 6 in TS 23.380 [8], clause 5.8.4.3) The UDM sends Nudm\_UECM\_PscfRestoration notification to the AMF serving the UE, using the received callback URI for P-CSCF restoration notifications. The AMF accepts the Nudm message and sends a response message to the UDM. +8. The UDM responds to the HSS. Note: Message 8 may be sent at the same time like message 7 and need not wait for the response to message 7. + +#### 6.2.3.7 SMS support + +The interworking between EPS and 5GC, as described in clause 6.2.3.4, also has an impact on SMS handling. For example, if an SMS cannot be delivered to a subscriber which is not attached to the mobile network at all, it cannot be predicted how the subscriber will be reachable for SMS next. The subscriber may attach in 2G/3G only, in LTE/EPC or in 5G via NR - the network must be prepared to deliver the SMS anyway. In the following clauses we focus on the SMS message flows initiated towards the HSS. Similar flows apply for the SMS delivery described in TS 23.502 [2]. + +##### 6.2.3.7.1 Terminating SMS location query + +Figure 6.2.3.7-1 shows the interaction when the SMSC or IP-SM-GW queries the HSS for SMS routing information. + +![Sequence diagram for SMS Location Query showing interactions between UDR, UDM, HSS, EPC-UDR, and SMSC.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) + +``` + +sequenceDiagram + participant SMSC + participant HSS + participant EPC-UDR + participant UDM + participant UDR + + Note right of HSS: (HSS and EPC-UDR are grouped) + + SMSC->>HSS: 1. MAP-SRI_SM or S6c-SRR + HSS->>EPC-UDR: 2. Read + HSS->>UDM: 3. Nudm_UEContextManagement_Get (SMSF address) + UDM->>UDR: 4. Nudr_DM_Query (SMSF address) + UDR-->>UDM: 5. Nudr_DM_Query resp (SMSF address) + UDM->>HSS: 6. Nudm_UEContextManagement resp (SMSF address) + HSS->>SMSC: 7. MAP-SRI_SM response or S6c-SRA (serving nodes) + +``` + +The diagram illustrates the sequence of messages for an SMS Location Query. It starts with the SMSC sending a MAP-SRI\_SM or S6c-SRR message to the HSS. The HSS then sends a Read message to the EPC-UDR. Next, the HSS sends a Nudm\_UEContextManagement\_Get request to the UDM, specifying the SMSF address. The UDM responds with a Nudr\_DM\_Query to the UDR, which returns the SMSF address(es) in a Nudr\_DM\_Query resp. The UDM then sends a Nudm\_UEContextManagement resp to the HSS, providing the SMSF address. Finally, the HSS sends a MAP-SRI\_SM response or S6c-SRA to the SMSC, indicating the serving nodes. + +Sequence diagram for SMS Location Query showing interactions between UDR, UDM, HSS, EPC-UDR, and SMSC. + +Figure 6.2.3.7-1: SMS Location Query + +1. The SMSC queries the HSS for routing information for SMS. +2. If the EPC-UDR is used, the HSS reads the necessary information from the EPC-UDR. +3. The HSS uses the Nudm\_UECM\_Get request to query the UDM for the serving SMSF address(es). +4. The UDM queries the UDR with an Nudr\_DM\_query for the SMSF address(es). +5. The UDR provides the SMSF address(es) to the UDM. +6. The UDM passes the SMSF address(es) to the HSS in the Nudm\_UECM response. +7. The HSS replies to the SMSC with a list of supporting nodes. + +##### 6.2.3.7.2 Terminating SMS delivery failure + +After delivery of an SMS failed, the HSS stores message waiting information. In order to enable message delivery via 5G NAS, the HSS subscribes to the UDM (and indirectly AMF) for UE availability. Figure 6.2.3.7-2 shows the related interaction; it is assumed that there was no previously waiting message before. + +![Sequence diagram for SMS Delivery Failure. Lifelines: AMF, UDR, UDM, HSS, EPC-UDR, SMSC. The diagram shows the interaction between these components when an SMS delivery fails. The SMSC sends a failure report to the HSS. The HSS interacts with the EPC-UDR to read and update information. The HSS then subscribes to UE reachability at the UDM. The UDM queries the UDR, receives information, subscribes to the AMF, updates the UDR, and finally acknowledges the subscription to the AMF.](dd5771673aececa53d42ece89218299d_img.jpg) + +``` + +sequenceDiagram + participant SMSC + participant HSS + participant EPC-UDR + participant UDM + participant UDR + participant AMF + + Note right of HSS: [EPC subsystem] + + SMSC->>HSS: 1. MAP/S6c-Report-SM-Delivery-Status (failure) + HSS->>EPC-UDR: 2. Read + HSS->>EPC-UDR: 3. Update + HSS->>SMSC: 4. MAP/S6c-Report-SM-Delivery-Status result + HSS->>UDM: 5. Nudm_EventExposure_Subscribe (UEReachability) + UDM->>UDR: 6. Nudr_DM_Query + UDR->>UDM: 7. Nudr_DM_Query resp + UDM->>AMF: 8. Namf_EventExposure_Subscribe (UEReachability) + AMF->>UDM: 9. Namf_EventExposure_Subscribe resp + UDM->>UDR: 10. Nudr_DM_Update + UDR->>UDM: 11. Nudr_DM_Update resp + UDM->>HSS: 12. Nudm_EventExposure_Subscribe resp + +``` + +Sequence diagram for SMS Delivery Failure. Lifelines: AMF, UDR, UDM, HSS, EPC-UDR, SMSC. The diagram shows the interaction between these components when an SMS delivery fails. The SMSC sends a failure report to the HSS. The HSS interacts with the EPC-UDR to read and update information. The HSS then subscribes to UE reachability at the UDM. The UDM queries the UDR, receives information, subscribes to the AMF, updates the UDR, and finally acknowledges the subscription to the AMF. + +**Figure 6.2.3.7-2: SMS Delivery Failure** + +1. The SMSC informs the HSS about the delivery failure. +2. The HSS reads the necessary information from the EPC-UDR. +3. The HSS updates the Message Waiting status in UDR. +4. The HSS acknowledges the receipt of the delivery status to the SMSC. +5. The HSS subscribes for UE reachability information at the UDM, using the Nudm\_EventExposure service. +6. The UDM requests the relevant subscriber information from the UDR. +7. The UDR provides the requested information. +8. The UDM subscribes for UE reachability information at the AMF, using the Namf\_EventExposure service. +9. The AMF acknowledges the subscription by the UDM. +10. UDM updates the subscriber specific event subscription information in the UDR. +11. The UDR acknowledges the update to the UDM. +12. The UDM acknowledges the subscription by the AMF. + +##### 6.2.3.7.3 SMS Alerting + +Once the UE becomes available again, the SMSC(s) will be informed about the availability. Figure 6.2.3.7-3 shows the related interaction if the UE becomes reachable in 5G. This assumes the existence of a subscription as described in clause 6.2.3.7.2. + +![Sequence diagram for SMS Alerting showing interactions between AMF, UDR, UDM, HSS, EPC-UDR, and SMSC.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant UDR + participant UDM + participant HSS + participant EPC-UDR + participant SMSC + + Note left of AMF: UE becomes available + AMF->>UDM: 1. Namf_EventExposure_Notify + UDM->>UDR: 2. Nudr_DM_Query + UDR-->>AMF: 3. Namf_EventExposure_Notify resp + UDM->>UDR: 4. Nudr_DM_Update + UDM->>HSS: 5. Nudm_EventExposure_Notify (Reachability) + HSS->>EPC-UDR: 6. Read + HSS-->>UDM: 7. Nudm_EventExposure_Notify resp + HSS->>SMSC: 8. MAP-AlertSC or S6c-ALR + HSS->>EPC-UDR: 9. Update + SMSC-->>HSS: 10. MAP-AlertSC resp or S6c-ALA + +``` + +Sequence diagram for SMS Alerting showing interactions between AMF, UDR, UDM, HSS, EPC-UDR, and SMSC. + +Figure 6.2.3.7-3: SMS Alerting + +1. The AMF informs the UDM about the UE reachability. +2. The UDM reads the necessary information from the UDR. +3. The UDM acknowledges the receipt of the Notification to the AMF. +4. The UDM updates the AMF-URRP flag in the UDR. +5. The UDM informs the HSS about the UE availability. +6. The HSS may read the subscriber related information in the EPC-UDR. +7. The HSS acknowledges the receipt of the notification to the UDM. +8. The HSS alerts all relevant SMSCs regarding the UE availability. Only one such SMSC is shown in the figure for simplicity. +9. The HSS may update the subscriber information in the EPC-UDR. +10. The SMSC replies to the alerting. + +### 6.2.4 Impacts on existing services and interfaces + +Following impacts are identified: + +#### a) Impacts in HSS: + +New SBA service at least with one operation Request/Response, at described in figure 6.2.3-2. + +This SBA service has to follow registration/discovery/selection procedures (by means of interaction with NRF or by configuration) as defined for Rel-15 or its evolution/adaptation to Rel-16. + +No impacts to existing interfaces or procedures. + +#### b) Impacts in UDM + +New SBA service at least with one operation Request/Response, at described in figure 6.2.3-1. + +### 6.2.5 Evaluation + +This solution identifies an approach that can work for both layered and not layered architectures of HSS. + +In addition, it supports all the procedures that have been defined on EPS and 5GS without any impact on any other interface than the one between HSS and UDM this solution defines. + +If this solution is adopted, it requires standardisation of the interface between HSS and UDM. + +## 6.3 Solution #3: UDM/HSS FE interaction reusing legacy protocol + +### 6.3.1 Introduction + +This solution addresses Key Issue #1: Interaction between UDM and HSS with separate repositories. + +The assumption of this solution is that 5GS UDR and EPS UDR are separate, between which there is no interface for direct interactions. The EPS and IMS profiles are stored in EPS UDR and the 5GS profile is stored in 5GS UDR. + +UDM and HSS FE interacts to retrieve or update the required user data for the following procedures: + +- Authentication procedure, i.e. initial attach/registration. +- Network Provided Location Information (NPLI). +- Procedure on IP address continuity of interworking without N26 from 5GS to EPS. +- T-ADS query for IMS voice. +- IMS related procedures related to Cx/Dx and Sh interfaces. +- SMS over NAS. + +To avoid the impact on legacy HSS, the interactions for retrieving or updating user data are initiated by UDM through reusing existing HSS supported protocol and procedures, i.e. this solution only requires UDM to retrieve or update user data stored in EPS UDR via HSS FE. The interface between HSS FE and EPS UDR is also not impacted. + +### 6.3.2 High-level Description + +#### 6.3.2.1 Authentication + +A new interface, Shu, between UDM and HSS FE is introduced, by which UDM initiates interactions with HSS FE to retrieve or update user data stored in EPS UDR. Shu is a Point-to-Point reference point. + +UDM is the only access point both to 5GC and EPC. + +![Figure 6.3.2.1.1: Solution architecture diagram showing the interconnection of EPS UDR, 5GS UDR, HSS FE, UDM, AUSF, AMF, and MME.](b5335262987c819d7f71ce40f99cb71b_img.jpg) + +``` + +graph TD + EPS_UDR[EPS UDR] --- HSS_FE[HSS FE] + 5GS_UDR[5GS UDR] --- UDM[UDM] + HSS_FE ---|Shu| UDM + UDM ---|Nudm| AUSF + AUSF --- AMF[AMF] + UDM ---|S6a| MME[MME] + +``` + +The diagram illustrates the solution architecture for interworking between EPS and 5GS. It features several network functions: EPS UDR, 5GS UDR, HSS FE, UDM, AUSF, AMF, and MME. The EPS UDR is connected to the HSS FE. The 5GS UDR is connected to the UDM. The HSS FE and UDM are connected via the Shu interface. The UDM is connected to the AUSF via the Nudm interface. The AUSF is connected to the AMF. The UDM is also connected to the MME via the S6a interface. + +Figure 6.3.2.1.1: Solution architecture diagram showing the interconnection of EPS UDR, 5GS UDR, HSS FE, UDM, AUSF, AMF, and MME. + +**Figure 6.3.2.1.1: Solution architecture** + +In some 5G deployment, when a 4G subscriber is updated to 5G subscriber, the 4G subscription profile keeps stored in EPS UDR while the new 5G subscription data is provisioned in 5GS UDR. In this case it is assumed that the authentication data is only stored in EPS UDR and is reused by 5GS authentication. + +For new 5G subscriber, all the subscription data is stored in 5GS UDR. Therefore, the solution described in this clause does not apply. + +In this scenario, when a UE with 5GS subscription registers on 5GS, the UDM needs to interact with HSS FE to retrieve authentication information data stored in EPS UDR. + +NOTE: The UDM is a combo node which simultaneously supports UDM and HSS FE functionality. + +In case of single registration in 5G, in order to cancel the registration in the other RAT, the UDM supports to perform a fake 4G registration in the HSS, as shown in Figure 6.3.3.1-2. This trigger the HSS to cancel the 4G registration. When the UE moves back to 4G, the HSS sends cancel location to UDM which trigger the UDM to deregister the UE in 5G. + +#### 6.3.2.2 IP address continuity of interworking without N26 from 5GS to EPS + +Shu interface defined in clause 6.3.2.1 is reused. + +UDM is the only access point both to 5GC and EPC. + +![Figure 6.3.2.2-1: Solution architecture diagram showing the central role of the UDM connected to various network functions.](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg) + +``` +graph TD; EPS_UDR[EPS UDR] --- HSS_FE[HSS FE]; 5GS_UDR[5GS UDR] --- UDM[UDM]; HSS_FE ---|Shu| UDM; UDM ---|Nudm| AMF[AMF]; UDM ---|S6a| MME[MME]; UDM ---|Nudm| PGW_C_SMF[PGW-C+SMF]; +``` + +The diagram illustrates the solution architecture centered around the Unified Data Management (UDM) function. The UDM is connected to the EPS UDR via the HSS FE (with a Shu interface), to the 5GS UDR directly, to the AMF via a Nudm interface, to the MME via an S6a interface, and to the PGW-C+SMF via another Nudm interface. + +Figure 6.3.2.2-1: Solution architecture diagram showing the central role of the UDM connected to various network functions. + +**Figure 6.3.2.2-1: Solution architecture** + +When a UE initially registers in 5GC, the FQDN for the S5/S8 interface of the PGW-C+SMF is registered into UDM via Nudm as specified in clause 4.11.2 of TS 23.502 [2]. + +When UE attaches in EPS due to interworking without N26, the procedure specified in clause 4.11.2 of TS 23.502 [2] applies. When MME sends Update Location Request to UDM, after forwarding the request to HSS FE, UDM needs to retrieve the stored PGW-C+SMF FQDN and add it into the Update Location Ack message returned from HSS FE. + +The MME use PGW-C+SMF FQDN received from the Update Location Ack message to determine the address of PGW-C+SMF. + +#### 6.3.2.3 T-ADS for IMS voice + +Shu interface defined in clause 6.3.2.1 is reused. + +UDM is the only access point both to 5GC, EPC and IMS, i.e. UDM supports S6a and Sh interfaces along with Nudm. + +![Figure 6.3.2.3-1: Solution architecture diagram showing the UDM connected to EPS UDR, 5GS UDR, HSS FE, AMF, MME, and SCC AS via various interfaces.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) + +``` +graph TD; EPS_UDR[EPS UDR] --- HSS_FE[HSS FE]; 5GS_UDR[5GS UDR] --- UDM[UDM]; HSS_FE ---|Shu| UDM; UDM ---|Nudm| AMF[AMF]; UDM ---|S6a| MME[MME]; UDM ---|Sh| SCC_AS[SCC AS]; +``` + +Figure 6.3.2.3-1: Solution architecture diagram showing the UDM connected to EPS UDR, 5GS UDR, HSS FE, AMF, MME, and SCC AS via various interfaces. + +**Figure 6.3.2.3-1: Solution architecture** + +SCC AS initiates T-ADS query towards UDM via Sh interface as specified in TS 29.328 [11]. + +To handle T-ADS query, the UDM queries T-ADS information towards HSS FE to get T-ADS information related to EPS and UMTS. HSS FE may query MME and SGSN to get information as specified in TS 23.401 [16] and TS 23.060 [15]. + +After receiving response of T-ADS query from HSS FE, UDM responds T-ADS query to SCC AS based on the T-ADS information received from HSS FE and T-ADS information in UDM. UDM may query AMF to get necessary information as specified in TS 23.501 [6]. + +#### 6.3.2.4 Supporting IMS related procedures + +Shu interface defined in clause 6.3.2.1 is reused. + +UDM, which is a combo node supporting UDM and HSS functionalities, is the only access point both to 5GC, EPC and IMS. + +![Figure 6.3.2.4-1: Solution architecture diagram showing the UDM as a central hub connected to various network functions.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) + +``` + +graph LR + EPS_UDR[EPS UDR] --- HSS_FE[HSS FE] + 5GS_UDR[5GS UDR] --- UDM[UDM] + HSS_FE ---|Shu| UDM + UDM ---|Nudm| AMF[AMF] + UDM ---|S6a| MME[MME] + UDM ---|Sh| IMS_AS[IMS AS] + UDM ---|Cx/Dx| I_S_CSCF[I/S-CSCF] + UDM ---|Nudm| PGW_C_SMF[PGW-C+SMF] + AUSF[AUSF] --- AMF + AUSF --- MME + AUSF --- IMS_AS + AUSF --- I_S_CSCF + AUSF --- PGW_C_SMF + AUSF ---|Nudr| UDM + +``` + +The diagram illustrates the solution architecture for IMS. At the center is the UDM (Unified Data Management). To its left, the EPS UDR (EPS User Data Repository) is connected to the HSS FE (Home Subscriber Server Front End), which in turn connects to the UDM via the Shu interface. Above the UDM, the 5GS UDR connects to it via the Nudr interface. To the right of the UDM, several network functions are connected: AMF (Access and Management Function) via Nudm, MME (Mobility Management Entity) via S6a, IMS AS (IMS Application Server) via Sh, I/S-CSCF (Interrogating/Serving CSCF) via Cx/Dx, and PGW-C+SMF (PDN Gateway-Cornerstone + SMF) via Nudm. An AUSF (Authentication Server Function) is also shown, connected to the AMF, MME, IMS AS, I/S-CSCF, and PGW-C+SMF, and to the UDM via the Nudr interface. + +Figure 6.3.2.4-1: Solution architecture diagram showing the UDM as a central hub connected to various network functions. + +Figure 6.3.2.4-1: Solution architecture + +Since IMS profile is stored in EPS UDR, the UDM needs to forward all the requests received from IMS via Cx/Dx or Sh interfaces to HSS FE to handle, and further forwards all the responses from HSS FE to IMS. + +For some scenarios that HSS FE and EPS UDR may generate requests to IMS, the UDM needs to forward all the requests received from HSS FE to IMS via Cx/Dx or Sh interfaces to handle, and further forwards all the responses from IMS to HSS FE. + +#### 6.3.2.5 SMS over NAS + +Shu interface defined in clause 6.3.2.1 is reused. + +UDM is the only access point both to SMSF, SMS router and SMSC/SM GMSC. + +![Figure 6.3.2.5-1: Solution architecture diagram for SMS over NAS.](3db5d62ad46e33647ec2b1ad6d2703bb_img.jpg) + +``` + +graph LR + EPS_UDR[EPS UDR] --- HSS_FE[HSS FE] + 5GS_UDR[5GS UDR] --- UDM[UDM] + HSS_FE ---|Shu| UDM + UDM ---|Nudr| 5GS_UDR + UDM ---|Nudm| SMSF[SMSF] + UDM ---|Sh| SMS_router[SMS router] + UDM ---|C/S6c| SMSC_SM_GMSC[SMSC/SM GMSC] + +``` + +The diagram illustrates the solution architecture for SMS over NAS. The UDM (Unified Data Management) is the central component. It is connected to the EPS UDR via the HSS FE and the Shu interface. The 5GS UDR is connected to the UDM via the Nudr interface. To the right of the UDM, three network functions are connected: SMSF (SMS Function) via Nudm, SMS router via Sh, and SMSC/SM GMSC (SMSC/SM Gateway Mobile Switching Center) via the C/S6c interface. + +Figure 6.3.2.5-1: Solution architecture diagram for SMS over NAS. + +Figure 6.3.2.5-1: Solution architecture + +### 6.3.3 Services and Illustrated Procedures + +#### 6.3.3.1 Authentication + +The procedure of the interaction between UDM and HSS FE for Authentication Information Retrieval is shown in Figure 6.3.3.1-1. + +![Sequence diagram illustrating the Authentication Info Retrieval Procedure between UDM and HSS FE. The diagram shows interactions between AMF, AUSF, MME, UDM, HSS FE, and HSS BE. The sequence starts with MME sending an Authentication-Information-Request to UDM (1a) or AMF invoking Nausf_UEAuthentication_authenticate to AUSF (1b). AUSF then invokes Nudm_UEAuthentication_Get to UDM (1b'). UDM sends an Authentication-Information-Request to HSS FE (2). HSS FE performs authentication information retrieval (3) and returns an Authentication-Information-Answer to UDM (4). UDM then forwards the answer to MME (5a) or AUSF (5b'). Finally, AUSF responds to AMF (5b).](fb18a83d10ebdad8e3e5ea2e86b36136_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant AUSF + participant MME + participant UDM + participant HSS FE + participant HSS BE + + Note right of HSS FE: 3. authentication information retrieval + + MME->>UDM: 1a. Authentication-Information-Request + AMF->>AUSF: 1b. Nausf_UEAuthentication_authenticate + AUSF->>UDM: 1b'. Nudm_UEAuthentication_Get invocation + UDM->>HSS FE: 2. Authentication-Information-Request + HSS FE->>UDM: 4. Authentication-Information-Answer (authentication vectors) + UDM->>MME: 5a. Authentication-Information-Answer (authentication vectors) + UDM->>AUSF: 5b'. Nudm_UEAuthentication_Get response + AUSF->>AMF: 5b. Nausf_UEAuthentication_authenticate response + +``` + +Sequence diagram illustrating the Authentication Info Retrieval Procedure between UDM and HSS FE. The diagram shows interactions between AMF, AUSF, MME, UDM, HSS FE, and HSS BE. The sequence starts with MME sending an Authentication-Information-Request to UDM (1a) or AMF invoking Nausf\_UEAuthentication\_authenticate to AUSF (1b). AUSF then invokes Nudm\_UEAuthentication\_Get to UDM (1b'). UDM sends an Authentication-Information-Request to HSS FE (2). HSS FE performs authentication information retrieval (3) and returns an Authentication-Information-Answer to UDM (4). UDM then forwards the answer to MME (5a) or AUSF (5b'). Finally, AUSF responds to AMF (5b). + +**Figure 6.3.3.1-1: Authentication Info Retrieval Procedure between UDM and HSS FE** + +- 1a. When the UE attaches from EPS, MME sends Authentication-Information-Request to UDM to get authentication information for the UE. The MME message is sent to UDM by DRA routing (i.e., based on IMSI range). +- 1b. When the UE registers from 5GS, AMF invokes Nausf\_UEAuthentication\_authenticate service operation to AUSF to get authentication information for the UE. +- 1b'. AUSF invokes Nudm\_UEAuthentication\_Get service operation. +2. When UDM receives Nudm\_UEAuthentication\_Get, it determines to generate and send S6a Authentication-Information-Request message to HSS-FE based on local configuration, if the authentication information is stored in EPS UDR due to operator's deployment. +3. HSS FE interacts with EPS UDR to retrieve authentication information of the UE via legacy UDC architecture. +4. HSS FE returns Authentication-Information-Answer with authentication vectors to UDM. +- 5a. UDM forwards Authentication-Information-Answer with authentication vectors to MME. +- 5b'. UDM generates the respond to Nudm\_UEAuthentication\_Get service operation invocation with authentication vectors received in Authentication-Information-Answer, and sends the respond to AUSF. +- 5b. AUSF response the AMF invoked Nausf\_UEAuthentication\_authenticate service. + +**Editor's note:** This procedure may be modified based on SA WG3 LS response. + +The procedure of the interaction between UDM and HSS FE for single Registration is shown in Figure 6.3.3.1-1. + +![Sequence diagram illustrating the Single Registration Procedure between UDM and HSS FE. The diagram shows interactions between AMF, MME, UDM, 5GS UDR, HSS, and EPS UDR. The process starts with UE Registration in 5G, followed by a check for single registration, then Update Location Request to HSS, storing info in EPS UDR, and subsequent cancellation and update requests.](04cfca33e3fc26513abe649d7474f733_img.jpg) + +``` + +sequenceDiagram + participant AMF + participant MME + participant UDM + participant 5GS UDR + participant HSS + participant EPS UDR + + Note over AMF, 5GS UDR: 1. UE Registration in 5G + Note over UDM: 2. Single Registration? + UDM->>HSS: 3. Update Location Request + Note over HSS, EPS UDR: 4. Store information in EPS UDR + HSS->>UDM: 5. Update Location Ack + HSS-->>MME: 6. Cancel Location Request + MME-->>HSS: 7. Cancel Location Response + MME->>UDM: 8. Update Location Request + Note over HSS, EPS UDR: 9. Store information in EPS UDR + HSS->>UDM: 10. Update Location Ack + HSS->>UDM: 11. Cancel Location Request + UDM->>HSS: 12. Cancel Location Response + Note over AMF, UDM: 13. UDM initiated UE deregistration procedure + +``` + +Sequence diagram illustrating the Single Registration Procedure between UDM and HSS FE. The diagram shows interactions between AMF, MME, UDM, 5GS UDR, HSS, and EPS UDR. The process starts with UE Registration in 5G, followed by a check for single registration, then Update Location Request to HSS, storing info in EPS UDR, and subsequent cancellation and update requests. + +**Figure 6.3.3.1-2: Single Registration Procedure between UDM and HSS FE** + +1. The UE is registered in 5G. The AMF perform UE registration in UDM. The AMF indicates whether it requires single registration or dual registration. +2. If the AMF requires single registration then the following steps are performed. Otherwise the procedure stops. +3. The UDM selects the HSS FE based on the SUPI and sends Update Location Request to HSS FE. In this message a dedicated MME Identity is included. This dedicated MME Identity is pointing to the UDM. From HSS FE point of view, the UDM is now acted as a MME. This message also includes an indication to indicate single registration and an indication to indicate the skip of subscription data so the HSS FE will not send the UE 4G subscription data. +4. The HSS FE stores the dedicated MME Identity into EPS UDR via Ud interface. +5. The HSS FE sends Update Location Response to UDM. +6. If the UE has been registered in an old MME, the HSS FE sends Cancel Location Request towards this old MME. This message will be routed to MME directly based on the old MME Identity. +7. The old MME deregisters the UE and sends Cancel Location Response to the HSS FE. + +8. After the UE reselects 4G and performs Tracking Area Update procedure in 4G, the new MME sends Update Location Request towards the HSS FE. As the UDM is the only access point both to 5GC and EPC, this message is sent to UDM and the UDM relays this message to HSS FE. +9. The HSS stores the new MME information into EPS UDR via Ud interface. +10. The HSS sends Update Location Response to new MME via UDM including the UE 4G subscription. +11. Because the UE has been registered in 5G and a dedicated MME Identity pointing to the UDM is stored in the EPS UDR, the EPS UDR triggers the HSS FE to send Cancel Location Request towards the UDM. This message will be routed to UDM based on the dedicated MME Identity. +12. UDM sends Cancel Location Response to HSS FE. +13. Upon receiving Cancel Location Request from HSS FE targeting to deregister the UE in 5G, the UDM initiated Deregistration procedure to deregister the UE in 5G. + +#### 6.3.3.2 IP address continuity of interworking without N26 from 5GS to EPS + +The procedure of the interaction between UDM and HSS FE is shown in Figure 6.3.3.2-1. + +![Sequence diagram illustrating the IP continuity procedure for interworking without N26 from 5GS to EPS. The diagram shows interactions between PGW-C+SMF, MME, UDM, 5GS UDR, HSS FE, and EPS UDR. The steps are: 0. PGW-C+SMF registers its FQDN in UDM during registration procedure; 1. MME sends Update Location Request to UDM; 2. UDM forwards Update Location Request to HSS FE; 3. HSS FE handles Update Location Request with EPS UDR; 4. HSS FE returns Update Location Ack to UDM; 5. UDM retrieves PGW-C+SMF FQDN from 5GS UDR; 6. UDM sends Update Location Ack (with PGW-C+SMF FQDN) to MME.](b6ad8b32179842fca5ad086cf22b03eb_img.jpg) + +``` + +sequenceDiagram + participant PGW-C+SMF + participant MME + participant UDM + participant 5GS UDR + participant HSS FE + participant EPS UDR + + Note over PGW-C+SMF, UDM: 0. PGW-C+SMF registers its FQDN in UDM during registration procedure + MME->>UDM: 1. Update Location Request + UDM->>HSS FE: 2. Update Location Request + Note over HSS FE, EPS UDR: 3. Update Location Request handling + HSS FE->>UDM: 4. Update Location Ack + Note over UDM, 5GS UDR: 5. PGW-C+SMF FQDN retrieval + UDM->>MME: 6. Update Location Ack (PGW-C+SMF FQDN) + +``` + +Sequence diagram illustrating the IP continuity procedure for interworking without N26 from 5GS to EPS. The diagram shows interactions between PGW-C+SMF, MME, UDM, 5GS UDR, HSS FE, and EPS UDR. The steps are: 0. PGW-C+SMF registers its FQDN in UDM during registration procedure; 1. MME sends Update Location Request to UDM; 2. UDM forwards Update Location Request to HSS FE; 3. HSS FE handles Update Location Request with EPS UDR; 4. HSS FE returns Update Location Ack to UDM; 5. UDM retrieves PGW-C+SMF FQDN from 5GS UDR; 6. UDM sends Update Location Ack (with PGW-C+SMF FQDN) to MME. + +**Figure 6.3.3.2-1: IP continuity procedure for interworking without N26 from 5GS to EPS** + +0. PGW-C+SMF registers its FQDN in UDM during registration procedure. UDM stores the FQDN in 5GS UDR. +1. When the UE attaches in EPS due to interworking without N26 from 5GS to EPS, during the procedure, MME sends Update Location Request to UDM. +2. UDM forwards Update Location Request to HSS FE for further handling. +3. HSS FE interacts with EPS UDR to handle Update Location Request. +4. HSS FE returns Update Location Ack to UDM. +5. after receiving Update Location Ack, UDM retrieve PGW-C+SMF FQDN from 5GS UDR. +6. UDM generates a new Update Location Ack to add PGW-C+SMF FQDN into the message and forwards the message to MME. + +NOTE: the other signalling interactions not related to the solution are not present in this figure for simplification. + +#### 6.3.3.3 T-ADS for IMS voice + +The procedure of the interaction between UDM and HSS FE is shown in Figure 6.3.3.3-1. + +![Sequence diagram illustrating the T-ADS Procedure between UDM and HSS FE. The diagram shows interactions between SCC AS, AMF, UDM, 5GS UDR, HSS FE, EPS UDR, MME, and SGSN. The process starts with SCC AS sending a User-Data-Request (T-ADS query) to UDM. UDM forwards this to HSS FE. HSS FE then queries MME and SGSN for additional information. HSS FE returns the information to UDM. UDM then queries AMF for more information. Finally, UDM sends a User-Data-Answer (T-ADS information) back to SCC AS.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) + +``` + +sequenceDiagram + participant SCC AS + participant AMF + participant UDM + participant 5GS UDR + participant HSS FE + participant EPS UDR + participant MME + participant SGSN + + Note right of HSS FE: 3. T-ADS query as specified in 23.401. + Note right of HSS FE: 4. T-ADS query as specified in 23.060. + Note right of UDM: 6. T-ADS query as specified in 23.501. + + SCC AS->>UDM: 1. User-Data-Request (T-ADS query) + UDM->>HSS FE: 2. User-Data-Request (T-ADS query) + HSS FE-->>MME: 3. T-ADS query as specified in 23.401. + HSS FE-->>SGSN: 4. T-ADS query as specified in 23.060. + HSS FE->>UDM: 5. User-Data-Answer (T-ADS information) + UDM-->>AMF: 6. T-ADS query as specified in 23.501. + UDM->>SCC AS: 7. User-Data-Answer (T-ADS information) + +``` + +Sequence diagram illustrating the T-ADS Procedure between UDM and HSS FE. The diagram shows interactions between SCC AS, AMF, UDM, 5GS UDR, HSS FE, EPS UDR, MME, and SGSN. The process starts with SCC AS sending a User-Data-Request (T-ADS query) to UDM. UDM forwards this to HSS FE. HSS FE then queries MME and SGSN for additional information. HSS FE returns the information to UDM. UDM then queries AMF for more information. Finally, UDM sends a User-Data-Answer (T-ADS information) back to SCC AS. + +**Figure 6.3.3.3-1: T-ADS Procedure between UDM and HSS FE** + +1. SCC AS initiates T-ADS query towards UDM by sending a User-Data-Request message via Sh interface. +2. UDM forwards this User-Data-Request message to get T-ADS information related to EPS and UMTS. +3. HSS FE may query MME to get more T-ADS information as specified in TS 23.401 [16]. +4. HSS FE may query SGSN to get more T-ADS information as specified in TS 23.060 [15]. +5. HSS FE returns T-ADS information based on the information it derives by sending a User-Data-Answer message. +6. after receiving T-ADS information from HSS FE, UDM may query AMF for more T-ADS information as specified in TS 23.501 [6]. +7. UDM determines T-ADS result based on T-ADS information received from HSS FE and AMF and responds to SCC AS with the T-ADS information by sending a User-Data-Answer message. + +NOTE: the other signalling interactions not related to the solution are not present in this figure for simplification. + +For the single registration case the following message flow in figure 6.3.3.3-2 applies: + +![Sequence diagram for T-ADS Procedure with Single registration and UE is 5GS registered. Lifelines: SCC-AS, AMF, UDM, 5GS UDR, HSS FE, EPS UDR, SGSN. The process involves a User-Data-Request (T-ADS query) from SCC-AS to UDM, which is then forwarded to HSS FE. HSS FE reads data from EPS UDR and SGSN, then returns a T-ADS response. UDM combines this with data from 5GS UDR and returns a User-Data-Answer to SCC-AS.](13fde41de77bf026013a0b81684d1fc9_img.jpg) + +``` + +sequenceDiagram + participant SCC-AS + participant AMF + participant UDM + participant 5GS UDR + participant HSS FE + participant EPS UDR + participant SGSN + + SCC-AS->>UDM: 1. User-Data-Request (T-ADS query) + UDM->>HSS FE: 2. User-Data-Request (T-ADS query) + HSS FE->>EPS UDR: Read data + HSS FE->>SGSN: 3a. T-ADS request as per 23.060 + SGSN->>HSS FE: 4a. T-ADS response as per 23.060 + HSS FE->>5GS UDR: Read data + 5GS UDR->>UDM: 3b. IDR (T-ADS) + UDM->>AMF: 4b. IDR (T-ADS) + AMF->>UDM: 5b. IDA + UDM->>HSS FE: 6b. IDA + HSS FE->>UDM: Combine T-ADS response + UDM->>SCC-AS: 8. User-Data-Answer + +``` + +Sequence diagram for T-ADS Procedure with Single registration and UE is 5GS registered. Lifelines: SCC-AS, AMF, UDM, 5GS UDR, HSS FE, EPS UDR, SGSN. The process involves a User-Data-Request (T-ADS query) from SCC-AS to UDM, which is then forwarded to HSS FE. HSS FE reads data from EPS UDR and SGSN, then returns a T-ADS response. UDM combines this with data from 5GS UDR and returns a User-Data-Answer to SCC-AS. + +Figure 6.3.3.3-2: T-ADS Procedure with Single registration and UE is 5GS registered + +In Figure 6.3.3.3-2 it is clear that due to the fake registration concept, the HSS is the entity that is in charge of taking T-ADS decisions, and not the UDM, even when the UE is registered in the 5GS with the UDM. + +#### 6.3.3.4 Supporting IMS related procedures + +The procedure of the interaction between UDM and HSS FE is shown in Figure 6.3.3.4-1. + +![Sequence diagram for IMS procedures between UDM and HSS FE. Lifelines: I/S-CSCF, IMS AS, UDM, HSS FE, EPS UDR. The process starts with Cx/Dx and Sh requests from IMS AS to UDM, which are forwarded to HSS FE. HSS FE handles these and returns responses. UDM then generates its own requests to HSS FE, which are forwarded back to IMS AS and I/S-CSCF.](e94cbc0895c6914a2bb53f150ab7495e_img.jpg) + +``` + +sequenceDiagram + participant I/S-CSCF + participant IMS AS + participant UDM + participant HSS FE + participant EPS UDR + + IMS AS->>UDM: 1a. Cx/Dx requests (MAR, SAR, LIR, etc.) + IMS AS->>UDM: 1b. Sh requests (UDR, PUR, SNR etc.) + UDM->>HSS FE: 2. Requests forwarding + HSS FE->>EPS UDR: 3. Requests handling + HSS FE->>UDM: 4. Responses forwarding + UDM->>I/S-CSCF: 5a. Cx/Dx Request responses + UDM->>IMS AS: 5b. Sh Request response + HSS FE->>EPS UDR: 6. Generating requests + HSS FE->>UDM: 7. Requests forwarding + UDM->>IMS AS: 8a. Sh Notification requests + UDM->>I/S-CSCF: 8b. Cx request (PNR) (RTR) + IMS AS->>UDM: 9a. Sh Notification response (PNA) + I/S-CSCF->>UDM: 9b. Cx request response (RTA) + UDM->>HSS FE: 10. Response forwarding + +``` + +Sequence diagram for IMS procedures between UDM and HSS FE. Lifelines: I/S-CSCF, IMS AS, UDM, HSS FE, EPS UDR. The process starts with Cx/Dx and Sh requests from IMS AS to UDM, which are forwarded to HSS FE. HSS FE handles these and returns responses. UDM then generates its own requests to HSS FE, which are forwarded back to IMS AS and I/S-CSCF. + +Figure 6.3.3.4-1: IMS procedures between UDM and HSS FE + +- 1a or 1b. UDM receives Cx/Dx requests or Sh requests from IMS. +2. UDM identifies these requests are for IMS procedures, and forwards the requests to HSS FE. +3. HSS FE interacts with EPS UDR to handle the requests. +4. HSS FE sends responses to the requests to UDM. +- 5a or 5b. UDM forwards the received responses to IMS accordingly. +6. EPS UDR and HSS FE may generates requests to IMS, e.g. PNR to IMS AS or RTR to S-CSCF. +7. HSS FE sends the requests to UDM. +- 8a or 8b. UDM forwards the requests to IMS accordingly. +- 9a or 9b. IMS sends responses to the requests to UDM. +10. UDM forwards the responses to HSS FE. + +NOTE: the other signalling interactions not related to the solution are not present in this figure for simplification. + +#### 6.3.3.5 SMSF address storage and retrieval + +The procedure of the interaction between UDM and HSS FE is shown in Figure 6.3.3.5-1. + +![Sequence diagram showing SMSF address storage and retrieval between UDM and HSS FE. The diagram involves four lifelines: SMSF, SMS-SC/SMS GMSC, UDM, and 5GS UDR. The sequence of messages is: 1. SMSF sends NUDM_UECM_registration (SMSF address) to UDM; 2. UDM performs SMSF address storage with 5GS UDR; 3. SMS-SC/SMS GMSC sends Send Routing Information for SM Request to UDM; 4. UDM performs SMSF address retrieval with 5GS UDR; 5. UDM sends Send Routing Information for SM Response (SMSF address) to SMS-SC/SMS GMSC.](43979979715bb3304389a0cb18f34444_img.jpg) + +``` + +sequenceDiagram + participant SMSF + participant SMS-SC/SMS GMSC + participant UDM + participant 5GS UDR + + Note right of UDM: 2. SMSF address storage + Note right of UDM: 4. SMSF address retrieval + + SMSF->>UDM: 1. NUDM_UECM_registration (SMSF address) + UDM->>5GS UDR: 2. SMSF address storage + SMS-SC/SMS GMSC->>UDM: 3. Send Routing Information for SM Request + UDM->>5GS UDR: 4. SMSF address retrieval + UDM->>SMS-SC/SMS GMSC: 5. Send Routing Information for SM Response (SMSF address) + +``` + +Sequence diagram showing SMSF address storage and retrieval between UDM and HSS FE. The diagram involves four lifelines: SMSF, SMS-SC/SMS GMSC, UDM, and 5GS UDR. The sequence of messages is: 1. SMSF sends NUDM\_UECM\_registration (SMSF address) to UDM; 2. UDM performs SMSF address storage with 5GS UDR; 3. SMS-SC/SMS GMSC sends Send Routing Information for SM Request to UDM; 4. UDM performs SMSF address retrieval with 5GS UDR; 5. UDM sends Send Routing Information for SM Response (SMSF address) to SMS-SC/SMS GMSC. + +Figure 6.3.3.5-1: SMSF address storage and retrieval between UDM and HSS FE + +1. SMSF invokes Nudm\_UECM\_Registration service operation to register its address in UDM. +2. UDM interacts with 5GS UDR to store the SMSF address. +3. When SMS-SC or SMS GMSC initiates MT SMS delivery procedure, SMS-SC or SMS GMSC send MAP request i.e. Send Routing Information for SM request, to UDM. +4. UDM interacts with 5GS UDR to retrieve stored SMSF address. +5. UDM responds with SMSF address. + +Editor's note: How other procedures is supported, e.g. UDM and HSS support MT SMS domain selection to provide other available SMS delivery addresses, is FFS. + +### 6.3.4 Impacts on existing services and interfaces + +#### 6.3.4.1 Authentication impacts + +UDM supports: + +- generating Diameter S6a Authentication-Information-Request message based on Nudm\_UEAuthentication\_Get service operation; +- forwarding Diameter S6a Authentication-Information-Answer message with authentication vectors to MME; +- generating the respond to Nudm\_UEAuthentication\_Get service operation invocation with authentication vectors received in Authentication-Information-Answer, and sends the respond to AMF; +- generating and sending Location Update Request message to perform fake 4G registration in HSS FE when the UE is registered in 5G; +- de-registering the UE in 5G when it receives Cancel Location request with dedicated MME Identity from the HSS FE. + +HSS FE: No impact. + +5GS UDR: No impact. + +EPS UDR: No impact. + +#### 6.3.4.2 IP address continuity impacts + +UDM supports: + +- forwarding Diameter S6a Update Location Request message to HSS FE; +- retrieving PGW-C+SMF FQDN from 5GS UDR after receiving Update Location Ack from HSS FE; +- generating new Update Location Ack to add PGW-C+SMF FQDN into the message and forwarding the message to MME. + +HSS FE: No impact. + +5GS UDR: No impact. + +EPS UDR: No impact. + +#### 6.3.4.3 T-ADS for voice impacts + +UDM supports: + +- forwarding User-Data-Answer message to HSS FE; +- determine T-ADS result based on T-ADS information received from HSS FE and AMF. + +HSS FE: No impact. + +5GS UDR: No impact. + +EPS UDR: No impact. + +#### 6.3.4.4 Supporting IMS related procedures + +UDM supports: + +- forwarding requests for IMS procedures received from IMS to HSS FE and further forwarding responses from HSS FE to IMS; + +- forwarding requests for IMS procedures received from HSS FE to IMS and further forwarding responses from IMS to HSS FE. + +HSS FE: No impact. + +5GS UDR: No impact. + +EPS UDR: No impact. + +### 6.3.5 Evaluation + +The Solution does not provide the possibility to deploy a pure UDM without HSS functionality. + +The EPS and 5GS UDRs both need to keep up to date registration status for the UE, i.e. the EPS UDR has to know the registration status of the UE also when the UE is in the 5GS (due to the fake registration concept). This means that there is duplication of registration data in EPS and 5GS UDR, which is adding load and storage requirement to the system + +Due to the fake registration concept, the T-ADS master node is always the legacy HSS, not the UDM, even when the UE is 5GS registered. So, the functional allocation between 5GS and EPS specific entities is blurred for as long as there are combined 4G/5G subscribers. + +S6a specification impact where the 5G authentication vectors need to be carried and also 5G vectors need to be requested. + +NOTE: The above authentication related issue should be evaluated by SA WG3. + +## 6.4 Solution #4: Use of a Data Access Layer for interaction between HSS FE and UDM with common repository + +### 6.4.1 Introduction + +This solution applies to Key Issue 2 and describes how HSS FE and UDM interact when data repositories are common. + +### 6.4.2 High-level Description + +#### 6.4.2.1 Assumptions + +It is assumed that: + +- UE 4G and 5G profiles in the common repository may be a common record for the UE or be split into different records. +- The solution leverages EPS UDR to become the common repository for 4G and 5G subscription profiles to be accessed by means of the Ud reference point. +- Technologies and protocols to access the data stored in the common repository are assumed to be database specific or proprietary, but exposing Ud operations to query, create, delete and update of data, as well as subscriptions/notifications to modifications of such data. +- 5G UEs are assumed to be provisioned in the repository and able to use 4G networks (with the corresponding limitations). 4G UEs are provisioned in the repository, as of today, but not assumed to be able to use 5G core services. +- From an authentication perspective, this proposal assumes ARPF to be a separate entity from UDM, collocated with or incorporated to the HE/AuC specified in TS 33.401 [13], and it does not specifically address separation of ARPF logic from ARPF storage, in which case the interface would remain unspecified as it is for HE(AuC). This implies that each system will retrieve authentication data from the same subscriber credentials storage and vectors generation will be performed without SQN reuse. For handovers security with and without N26 for single and dual registration modes, the same procedures as described in TS 33.501 [12] clause 8 are assumed. - The IMS data for the UEs is assumed to be stored in the same common repository. + +- From an IMS interaction perspective, it is assumed that IMS HSS/SLF is a logical entity that can act as an application front end making use of the common repository, following the specification TS 23.335 [3] and implementing Cx/Dx and Sh/Dh interfaces that remain untouched. The colocation of IMS HSS/SLF and HSS FE is an operator option. + +NOTE: This is considered as a temporary solution in order to cope with the transition of legacy IMS towards a service based IMS, work in progress in TR 23.794 [14]. + +#### 6.4.2.2 Architectural proposal + +This solution makes use of a layer that separates the applications front end logic from the database technology/protocol used, leveraging the authorisation and policing capabilities from Rel-15 data storage architecture, and incorporating additional features to serve interworking with legacy systems. + +Hence, in addition to access control for application front ends, policing and offering a common view of the information irrespective of where it is stored, the solution adds protocol conversion between application front ends and the repository, as well as a notifications engine to mimic the relevant notifications that will trigger specific procedures at the different front end applications and related to handovers between one system and the other. + +The solution facilitates keeping existing deployments of application front ends and their repositories without modification, and provides a flexible model to introduce new application front ends without having to impact existing deployments and procedures. + +With few updates compared to what is reflected in the next clauses, the solution also facilitates migration of 4G users to be able to receive services from the 5G core, with the limitations imposed by 4G subscriptions, as when e.g. accessing the 5GC from a E-UTRAN radio access (option 5 type of deployment). + +![High level architecture diagram showing EPC and 5GC connected to HSS FE and UDM respectively, which both connect to a common Data Access Layer, which in turn connects to UE subscriptions.](080a7af02bc47cf21ebfae4e0be39745_img.jpg) + +The diagram illustrates a high-level architecture for the interaction of HSS FE and UDM with a common repository. At the top, two curved lines represent the EPC (Evolved Packet Core) and 5GC (5G Core). Below the EPC is a rectangular box labeled 'HSS FE'. Below the 5GC is a rectangular box labeled 'UDM'. Both 'HSS FE' and 'UDM' have vertical lines connecting them to a central horizontal grey bar labeled 'Data Access Layer'. The connection from 'HSS FE' is labeled 'Ud', and the connection from 'UDM' is labeled 'Nudr'. A dashed line runs horizontally within the 'Data Access Layer' bar. Below the 'Data Access Layer' bar, a vertical line connects to a cylinder icon labeled 'UE subscriptions'. + +High level architecture diagram showing EPC and 5GC connected to HSS FE and UDM respectively, which both connect to a common Data Access Layer, which in turn connects to UE subscriptions. + +Figure 6.4.2.2-1: High level architecture for interaction of HSS FE and UDM with common repository + +![Figure 6.4.2.2-2: High level architecture for interaction of HSS FE, IMS HSS/SLF and UDM with common repository](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) + +This diagram illustrates the high-level architecture for the interaction of HSS FE, IMS HSS/SLF, and UDM with a common repository. At the top, three network elements are shown: EPC, IMS, and 5GC. Below EPC is the HSS FE, which connects to the IMS HSS/SLF (under IMS) and the UDM (under 5GC). The HSS FE, IMS HSS/SLF, and UDM all connect to a central 'Data Access Layer' (represented by a grey box). The HSS FE and IMS HSS/SLF use the 'Ud' interface, while the UDM uses the 'Nudr' interface. Below the Data Access Layer is a 'UE subscriptions' repository (represented by a cylinder). A dashed line within the Data Access Layer indicates a logical separation or boundary. + +Figure 6.4.2.2-2: High level architecture for interaction of HSS FE, IMS HSS/SLF and UDM with common repository + +Figure 6.4.2.2-2: High level architecture for interaction of HSS FE, IMS HSS/SLF and UDM with common repository + +### 6.4.3 Services and Illustrated Procedures + +#### 6.4.3.1 General description + +The proposed data access layer will subscribe to changes performed in the repository, issuing some notifications towards the UDM or the HSS FE for specific UEs that may maintain profiles for 4G and 5G. + +![Figure 6.4.3.1-1: General procedure for notifications via the Data Access Layer](48f209b7c0c1f91af40cfc3466dbd534_img.jpg) + +This diagram illustrates the general procedure for notifications via the Data Access Layer. It shows the HSS FE and UDM connected to the Data Access Layer (grey box) via 'Ud' and 'Nudr' interfaces respectively. Below the Data Access Layer is the 'UE subscriptions' repository. Notifications are shown as curved arrows originating from the repository and pointing to the HSS FE and UDM. Red arrows represent notifications for '4G UEs' to the HSS FE and '5G UEs' to the UDM. Blue arrows represent notifications for '5G UEs' to the HSS FE and '4G UEs' to the UDM. The Data Access Layer acts as an intermediary, receiving information from the repository and distributing it to the appropriate network element based on the UE type. + +Figure 6.4.3.1-1: General procedure for notifications via the Data Access Layer + +Figure 6.4.3.1-1: General procedure for notifications via the Data Access Layer + +#### 6.4.3.2 5GS procedures + +The procedures specified in TS 23.502 [2] for Registration (clause 4.2.2.2), Deregistration (clause 4.2.2.3), UE Configuration Update (clause 4.2.4), Reachability procedures (clause 4.2.5), Session Management (clause 4.3), and User profile Management (clause 4.2.5) do not change when introducing this solution. + +Authentication procedures at registration (step 9 in clause 4.2.2.2 of TS 23.502 [2]) does not change either when introducing this solution. + +Any potential query of information related to the 4G subscription profile of the UE, would imply a mapping/translation of the NUdr\_DM\_Query in the Data Access Layer to be converted into a Ud query. + +#### 6.4.3.3 EPS procedures + +EPS procedures, including authentication ones, are not expected to be affected from the point of view of network signalling. + +The Data Access Layer will subscribe to changes in the common repository related to 5G subscribers having also 4G profiles. When any action is performed at the level of 4G data for the particular UE (like attachment, detachment, etc), the Data Access Layer will issue a notification towards the UDM. UDM will perform any action needed depending on the status of the UE, interworking needed, etc. + +This is intended to facilitate the tracking of the subscriber in either system, in order to execute the relevant deregistration in case the subscriber moves from one to the other. + +![Sequence diagram showing notification to UDM when UE attaches to EPS. The diagram involves four lifelines: HSS FE, Data Access Layer, Common Repository, and UDM. The sequence of messages is: 1. Ud Request from Data Access Layer to Common Repository; 2. Ud Response from Common Repository to Data Access Layer; 3. Ud Notification from Common Repository to Data Access Layer (with a note 'UE marked in 4G network'); 4. Nudr_DM_Notify from Data Access Layer to UDM. The HSS FE initiates a 'Network procedure' and receives a 'Network procedure ack' from the Data Access Layer.](18291be12b470a557e8c9f3a74e021be_img.jpg) + +``` + +sequenceDiagram + participant HSS FE + participant DAL as Data Access Layer + participant CR as Common Repository + participant UDM + + Note left of HSS FE: Network procedure + HSS FE->>DAL: + Note left of HSS FE: Network procedure ack + DAL->>CR: 1. Ud Request + CR-->>DAL: 2. Ud Response + Note right of CR: UE marked in 4G network + CR->>DAL: 3. Ud Notification + DAL->>UDM: 4. Nudr_DM_Notify + +``` + +Sequence diagram showing notification to UDM when UE attaches to EPS. The diagram involves four lifelines: HSS FE, Data Access Layer, Common Repository, and UDM. The sequence of messages is: 1. Ud Request from Data Access Layer to Common Repository; 2. Ud Response from Common Repository to Data Access Layer; 3. Ud Notification from Common Repository to Data Access Layer (with a note 'UE marked in 4G network'); 4. Nudr\_DM\_Notify from Data Access Layer to UDM. The HSS FE initiates a 'Network procedure' and receives a 'Network procedure ack' from the Data Access Layer. + +**Figure 6.4.3.3-1: Notification to UDM when UE attaches to EPS** + +The Ud Request expected to trigger a notification is Update Data as specified by TS 23.335 [3]. There is no need to notify any query of data performed by HSS FE. + +Any potential query of information related to the 5G subscription profile of the UE, would imply a mapping/translation of the Ud Query in the Data Access Layer to be converted into a query to the common repository. + +As the technologies and protocols used to access the data stored in the common repository are operator deployment choices, the mapping of the response depicted in the previous chart to the Nudr\_DM\_Notify operation towards the UDM is left as an operator deployment choice in agreement with its vendors. + +#### 6.4.3.4 Handover procedures + +##### 6.4.3.4.0 General + +For handover procedures, three cases are differentiated according to TS 23.501 [6] and TS 23.502 [2]: + +- Single registration mode with N26 support. +- Single registration mode without N26 support. +- Dual registration. + +For single registration mode with N26 support, any registration/attachment shall convey a cancellation of the location in the source system. + +For single registration without N26 support, registration/attachment shall also convey a cancelation of the location in the source system if simultaneous registration of both MME and AMF is not supported, according to TS 23.501 [6] clause 5.17.2.3.1. + +NOTE 1: Since UDM and HSS FE are split but common repository exists, the support of simultaneous registration of MME and AMF should be configurable in UDM, HSS FE and in the proposed Access Data Layer + +This solution proposes that, in single registration modes with and without N26, the PGW-C+SMF with corresponding APN/DNN is stored in the common repository, either in a single record or separate ones, and updated/query by either party in the different handover scenarios. + +NOTE 2: Storing of PGW-C+SMF and APN/DNN information in the same EPS UDR record will preclude the possibility of proper behaviour of dual registration procedures. + +This can be achieved as follows: + +![Sequence diagram showing the storage of PGW-C+SMF and APN/DNN with UE camping in EPS in single registration mode. The diagram involves four lifelines: HSS FE, EPS UDR, Data Access Layer, and UDM. The process starts with a 'Network procedure: Update Location/Notify' at the HSS FE. Step 1: 'Ud Request' is sent from HSS FE to EPS UDR. Step 2: 'Ud Response' is sent from EPS UDR to HSS FE. Step 3: 'Ud Notify' is sent from EPS UDR to Data Access Layer, with a note 'PGW-C+SMF & APN/DNN Stored in repository'. Step 4: 'Nudm_DM_Notify (intersystem info)' is sent from Data Access Layer to UDM. The process ends with a 'Network procedure ack' at the HSS FE.](36fd537a1e39baa2471ecfaaf869751a_img.jpg) + +``` +sequenceDiagram + participant HSS FE + participant EPS UDR + participant DAL as Data Access Layer + participant UDM + + Note left of HSS FE: Network procedure: Update Location/Notify + HSS FE->>EPS UDR: 1. Ud Request + EPS UDR-->>HSS FE: 2. Ud Response + Note right of EPS UDR: PGW-C+SMF & APN/DNN Stored in repository + EPS UDR->>DAL: 3. Ud Notify + DAL->>UDM: 4. Nudm_DM_Notify (intersystem info) + Note left of HSS FE: Network procedure ack +``` + +Sequence diagram showing the storage of PGW-C+SMF and APN/DNN with UE camping in EPS in single registration mode. The diagram involves four lifelines: HSS FE, EPS UDR, Data Access Layer, and UDM. The process starts with a 'Network procedure: Update Location/Notify' at the HSS FE. Step 1: 'Ud Request' is sent from HSS FE to EPS UDR. Step 2: 'Ud Response' is sent from EPS UDR to HSS FE. Step 3: 'Ud Notify' is sent from EPS UDR to Data Access Layer, with a note 'PGW-C+SMF & APN/DNN Stored in repository'. Step 4: 'Nudm\_DM\_Notify (intersystem info)' is sent from Data Access Layer to UDM. The process ends with a 'Network procedure ack' at the HSS FE. + +Figure 6.4.3.4.0-1: Storage of PGW-C+SMF and APN/DNN with UE camping in EPS in single registration mode + +While for 5GS, it is stored as following: + +![Sequence diagram for Figure 6.4.3.4.0-2: Storage of PGW-C+SMF and APN/DNN with UE camping in 5GS in single registration mode. The diagram shows interactions between EPS UDR, Data Access Layer, and UDM. The process starts with a '1. Nudm_DM_Update' from UDM to Data Access Layer, labeled 'Network procedure: PDU session initiation'. The Data Access Layer sends a '2. Ud Request (Intersystem info)' to EPS UDR, with a note 'PGW-C+SMF & APN/DNN Stored in repository'. EPS UDR returns a '3. Ud Response' to the Data Access Layer. Finally, the Data Access Layer sends a '4. Ack' to the UDM, labeled 'Network procedure ack'.](0f1767577a073167eb9628d72034e083_img.jpg) + +Sequence diagram for Figure 6.4.3.4.0-2: Storage of PGW-C+SMF and APN/DNN with UE camping in 5GS in single registration mode. The diagram shows interactions between EPS UDR, Data Access Layer, and UDM. The process starts with a '1. Nudm\_DM\_Update' from UDM to Data Access Layer, labeled 'Network procedure: PDU session initiation'. The Data Access Layer sends a '2. Ud Request (Intersystem info)' to EPS UDR, with a note 'PGW-C+SMF & APN/DNN Stored in repository'. EPS UDR returns a '3. Ud Response' to the Data Access Layer. Finally, the Data Access Layer sends a '4. Ack' to the UDM, labeled 'Network procedure ack'. + +**Figure 6.4.3.4.0-2: Storage of PGW-C+SMF and APN/DNN with UE camping in 5GS in single registration mode** + +For handover procedures in dual registration mode, the information needs to be stored in different records of the EPS UDR. The UE will remain registered/attached to the two system simultaneously with valid subscription data for both systems at the same time. Moving sessions between systems remains a UE implementation option. + +##### 6.4.3.4.1 5GS to EPS with N26 + +In 5GS to EPS handovers, the attach in the EPS will generate a Ud Request to modify data by HSS FE followed by a Response by the repository and a notification to the Data Access Layer. This will trigger a notification to the UDM to indicate the UE is now under EPS control. UDM should in turn modify the location data in the 5G profile and will proceed to deregister the AMF the UE moved from. + +![Sequence diagram for Figure 6.4.3.4.1-1: Notification to the UDM at UE attachment to EPS. The diagram shows interactions between HSS FE, Common Repository, Data Access Layer, and UDM. The process starts with a '1. Ud Request' from HSS FE to Common Repository, labeled 'Network procedure'. Common Repository returns a '2. Ud Response' to HSS FE, labeled 'Network procedure ack'. Common Repository sends a '3. Ud Notification' to Data Access Layer, with a note 'UE marked in 4G network'. Data Access Layer sends a '4. Nudr_DM_Notify' to UDM. UDM returns a '5. Nudr_DM_Update' to Data Access Layer, labeled 'Network procedure to deregister UE from AMF'. Data Access Layer sends a '6. Ud Request' to Common Repository, with a note 'UE in 5G mark removed'.](b4f6d3668f7e851eaff07ccf26001623_img.jpg) + +Sequence diagram for Figure 6.4.3.4.1-1: Notification to the UDM at UE attachment to EPS. The diagram shows interactions between HSS FE, Common Repository, Data Access Layer, and UDM. The process starts with a '1. Ud Request' from HSS FE to Common Repository, labeled 'Network procedure'. Common Repository returns a '2. Ud Response' to HSS FE, labeled 'Network procedure ack'. Common Repository sends a '3. Ud Notification' to Data Access Layer, with a note 'UE marked in 4G network'. Data Access Layer sends a '4. Nudr\_DM\_Notify' to UDM. UDM returns a '5. Nudr\_DM\_Update' to Data Access Layer, labeled 'Network procedure to deregister UE from AMF'. Data Access Layer sends a '6. Ud Request' to Common Repository, with a note 'UE in 5G mark removed'. + +**Figure 6.4.3.4.1-1: Notification to the UDM at UE attachment to EPS** + +No other action is expected to be performed by the UDM, and the control by the EPS will proceed as specified in the TS 23.502 [2], clause 4.11.1.2.1, with the difference that the HSS FE will not cancel the location of the AMF during the TAU procedure. Instead, the HSS FE will acknowledge the location update to the new MME and proceed as normal. + +##### 6.4.3.4.2 EPS to 5GS with N26 + +In EPS to 5GS handovers, the registration in the 5GS will generate a Nudr request and subsequent notification when data is stored in the common repository. The Data Access Layer will capture that and generate a notification towards the HSS FE indicating the UE has left the EPS. + +![Sequence diagram showing notification to the HSS FE at UE registration in 5GS. The diagram involves four main entities: HSS FE, Common Repository, Data Access Layer, and UDM. The sequence starts with the UDM sending a '1. Nudr_DM_Update' to the Data Access Layer. The Data Access Layer then sends a '2. Ud Request' to the Common Repository, which responds with '3. Ud Response'. The Data Access Layer then sends a '4. Nudr_DM_Notify' to the UDM. The UDM then sends a '5. Ud Notification (Note)' to the HSS FE. The HSS FE then sends a '6. Ud Request' to the Common Repository. The Common Repository responds with 'UE marked in 5G network' and 'UE in 4G mark removed'. The HSS FE then initiates a 'Network procedure: Cancel Location to MME'. The UDM also initiates a 'Network procedure'.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) + +``` + +sequenceDiagram + participant HSS FE + participant CR as Common Repository + participant DAL as Data Access Layer + participant UDM + + Note right of UDM: Network procedure + UDM->>DAL: 1. Nudr_DM_Update + DAL->>CR: 2. Ud Request + CR-->>DAL: 3. Ud Response + DAL->>UDM: 4. Nudr_DM_Notify + Note right of UDM: Network procedure + UDM->>HSS FE: 5. Ud Notification (Note) + HSS FE->>CR: 6. Ud Request + Note left of HSS FE: Network procedure: Cancel Location to MME + Note right of CR: UE marked in 5G network + Note right of CR: UE in 4G mark removed + +``` + +Sequence diagram showing notification to the HSS FE at UE registration in 5GS. The diagram involves four main entities: HSS FE, Common Repository, Data Access Layer, and UDM. The sequence starts with the UDM sending a '1. Nudr\_DM\_Update' to the Data Access Layer. The Data Access Layer then sends a '2. Ud Request' to the Common Repository, which responds with '3. Ud Response'. The Data Access Layer then sends a '4. Nudr\_DM\_Notify' to the UDM. The UDM then sends a '5. Ud Notification (Note)' to the HSS FE. The HSS FE then sends a '6. Ud Request' to the Common Repository. The Common Repository responds with 'UE marked in 5G network' and 'UE in 4G mark removed'. The HSS FE then initiates a 'Network procedure: Cancel Location to MME'. The UDM also initiates a 'Network procedure'. + +**Figure 6.4.3.4.2-1: Notification to the HSS FE at UE registration in 5GS** + +NOTE: HSS FE subscribed to changes in the common repository when UE data was stored. + +The procedure follows the specification in TS 23.502 [2] clause 4.11.1.2.2 with the modification that it is the HSS FE the one initiating the relevant cancel location towards the MME node the UE has moved from. + +##### 6.4.3.4.3 5GS to EPS without N26 - single registration + +For single registration without N26, HSS FE will be configured as not supporting dual registration. Thus, the attach to the EPS when UE moves from 5GS to EPS, will imply a cancellation of location in the AMF from where the UE moved. + +This procedure is aligned with what is described in clause 6.4.3.4.1 of this solution. + +The EPS attach is expected to trigger a Ud Update operation towards the EPS UDR, and a response to HSS FE including the PGW-C+SMF address (together with APN/DNN information) being used. + +##### 6.4.3.4.4 EPS to 5GS without N26 - single registration + +For single registration without N26, UDM will be configured as not supporting dual registration. Thus, the registration to the 5GS when UE moves from EPS to 5GS, will imply a cancellation of location in the MME from where the UE moved. + +The registration in the 5GS, would trigger a notification to the Access Data Layer that, in turn, would imply a Ud notification to the HSS FE to cancel the location in the MME. This procedure is aligned with what is described in clause 6.4.3.4.2 of this solution. + +##### 6.4.3.4.5 Handovers without N26 - dual registration + +For handover procedures in dual registration mode, the UE will remain registered/attached to the two system simultaneously with valid subscription data for both systems at the same time, including valid session information for both systems. Moving sessions between systems remains as a UE implementation option. + +Attachment/Registration of the UE in either system does not convey any cancellation in the source system. This is achieved by analysing the UDM and HSS FE configuration to support or not dual registrations. + +#### 6.4.3.5 IMS interaction + +##### 6.4.3.5.1 Access to IMS data + +Access to IMS data for creation, deletion, query and modification follows the specification in TS 23.228 [7] and TS 23.335 [3] by IMS making use of the IMS HSS/SLF functionality (either as a stand-alone application front end or collocated with HSS FE). + +It is not expected that any of the IMS entities need to interact with UDM, with the exception of the P-CSCF restoration mechanism invoked by S-CSCF, and the T-ADS information retrieval by the IMS AS. + +For these specific cases, it is proposed to use the SLF functionality for UE identity to UDM identity or HSS FE identity resolution, according to TS 23.228 [7] clause 5.8. + +NOTE 1: It is proposed to introduce SLF functionality since the split of UDM and HSS FE will imply multiple addressable location servers for the 5G UEs and these IMS procedures. + +NOTE 2: Since the I-CSCF, S-CSCF and IMS AS will always interrogate the SLF to find the location server serving the UE, the SLF needs to be configured to return the IMS HSS address in first place since it is the front end able to return the IMS profile for the UE. + +Any Cx or Sh operation triggered by CSCF or IMS AS, except restoration and T-ADS information retrieval, will be handled by the IMS HSS front end (either stand alone or collocated with the HSS FE). + +When UE is registered to IMS, the common repository will contain the indication regarding the UE being served by 5GS or EPS. This is proposed to be done as per the description in the common procedures, regardless the UE re-registers or not to IMS when moving between the systems (according to clause 5.2.2.4 of TS 23.228 [7]). This indication is proposed to be checked when either P-CSCF restoration or T-ADS information retrieval is received by UDM or HSS FE (see next clauses). + +In principle, both UDM and HSS FE would not require any additional action than what is described before for the general procedures. + +##### 6.4.3.5.2 P-CSCF Restoration procedures + +The P-CSCF restoration procedure via UDM is an optional mechanism according to TS 23.380 [8]. + +The following two options are considered regardless the support of N26 and UE mode of operation (single or dual registration). + +- **Option 1:** When UDM and HSS FE are split, the preferred P-CSCF restoration procedure would be that performed by detection of the failure by SMF/UPF according to TS 23.380 [8] clause 5.8.3, or using the PCF based P-CSCF restoration as specified in clause 5.8.5 of TS 23.380 [8]. + +NOTE 1: The adaptation of IMS to service based architecture, making use of proper virtualisation/cloud mechanisms for e.g. self-healing, high availability, redundancy, etc, would most likely make unnecessary the use of the current restoration procedures. + +- **Option 2:** To enable the P-CSCF restoration via either the UDM or the HSS FE, the SLF functionality is invoked in order to perform a user identity to HSS FE identity or UDM identity resolution. + +The SLF will return the list of different servers (UDMs and HSS FEs) that may be in charge of the UE at that point in time, for the S-CSCF to request the relevant P-CSCF restoration mechanism to the relevant entity. This procedure is according to TS 29.228 [10] clause 6.4. + +![Sequence diagram for User identity to HSS FE identity or UDM identity resolution for S-CSCF. The diagram shows the interaction between S-CSCF, IMS HSS/SLF, HSS FE, and UDM. The process starts with a 'Dx/Cx request' from S-CSCF to IMS HSS/SLF. IMS HSS/SLF performs a 'location server lookup' and returns 'Redirect info' to S-CSCF. S-CSCF then sends a 'Cx request' to HSS FE. HSS FE returns a 'Cx answer' to S-CSCF. Additionally, IMS HSS/SLF sends a 'Cx request (Note 2)' to UDM, which returns a 'Cx answer (Note 2)' to IMS HSS/SLF. A note on the left indicates the network procedure is 'P-CSCF restoration'.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) + +``` + +sequenceDiagram + participant S-CSCF + participant IMS HSS/SLF + participant HSS FE + participant UDM + Note left of S-CSCF: Network procedure: P-CSCF restoration + S-CSCF->>IMS HSS/SLF: 1. Dx/Cx request + IMS HSS/SLF->>IMS HSS/SLF: location server lookup + IMS HSS/SLF-->>S-CSCF: 2. Redirect info + S-CSCF->>HSS FE: 3. Cx request + HSS FE-->>S-CSCF: 4. Cx answer + IMS HSS/SLF->>UDM: 3a. Cx request (Note 2) + UDM-->>IMS HSS/SLF: 4a. Cx answer (Note 2) + +``` + +Sequence diagram for User identity to HSS FE identity or UDM identity resolution for S-CSCF. The diagram shows the interaction between S-CSCF, IMS HSS/SLF, HSS FE, and UDM. The process starts with a 'Dx/Cx request' from S-CSCF to IMS HSS/SLF. IMS HSS/SLF performs a 'location server lookup' and returns 'Redirect info' to S-CSCF. S-CSCF then sends a 'Cx request' to HSS FE. HSS FE returns a 'Cx answer' to S-CSCF. Additionally, IMS HSS/SLF sends a 'Cx request (Note 2)' to UDM, which returns a 'Cx answer (Note 2)' to IMS HSS/SLF. A note on the left indicates the network procedure is 'P-CSCF restoration'. + +**Figure 6.4.3.5.2-1: User identity to HSS FE identity or UDM identity resolution for S-CSCF** + +NOTE 2: This assumes that UDM implements the Cx operations SAR/SAA to trigger the P-CSCF restoration. Potential conversion of Diameter Cx operation to an Nudm service operation is out of the scope of this study. + +NOTE 3: It is assumed that S-CSCF is aware of the IMS registration status of the UE prior to request P-CSCF restoration. + +Both HSS FE and UDM will check the UE registration status in the corresponding network (either 5GS or EPS) in order to either execute the procedure (according to TS 23.380 [8]) or reject it. + +No other impact is expected for restoration. + +##### 6.4.3.5.3 Terminating domain selection information for IMS voice + +According to TS 23.501 [6], clause 5.16.3.6, the UDM/HSS shall be able to query the serving AMF for T-ADS related information, and AMF shall respond to the query with the relevant information unless the UE is detached: + +- whether or not IMS voice over PS Session is supported in the registration area(s) where the UE is currently registered; +- whether or not IMS voice over PS Session Supported Indication over non-3GPP access is supported in the WLAN where the UE is currently registered; +- the time of the last radio contact with the UE; and +- the current Access Type and RAT type. + +Retrieval of T-ADS information is initiated by the IMS AS. + +To retrieve the T-ADS information from either the UDM or the HSS FE, the SLF functionality is invoked in order to perform a user identity to HSS FE identity or UDM identity resolution. + +The SLF will return the list of different servers (UDMs and HSS FEs) that may be in charge of the UE at that point in time, for the IMS AS to request the information for access domain selection. This procedure is according to TS 29.328 [11] clause 6.5. + +If the UE is attached to IMS via 5GS, the T-ADS information request to the IMS HSS/SLF will end up in a Sh request (UDR/UDA) to UDM, which in turn will invoke the AMF service Namf\_MT\_ProvideDomainSelectionInfo as specified in TS 23.501 [6] clause 5.16.3.6 and TS 23.228 [7] annex Y. + +To translate IMPU to SUPI, for the cases in which the Sh request is based on IMPU, the 5G UDR can incorporate a new data key (=IMPU) for the Subscription Data data set to be used for the Nudr\_DM\_Query operation, in order to request identifier translation from IMPU to SUPI. + +The query to the 5G UDR is simply converted by the Access Data Layer into a Ud request to the EPS UDR repository hosting the IMS data, in order to retrieve the IMSI that is associated with the IMPU received in the Sh request. + +The request from IMS AS, when the UE is attached to the EPS, should follow the same procedures as defined in TS 23.228 [7] clause 4.2.4a. + +NOTE 1: It is assumed that IMS AS is aware of the IMS registration status of the UE prior to request T-ADS information. + +Both UDM and HSS FE will check the registration status in the corresponding network in order to either execute the procedure (according to TS 23.228 [7]) or reject it. + +In case of dual registration, and according to annex D of TS 29.328 [11], the IMS AS will expect the T-ADS information containing 0 or 1 RAT types, depending on whether IMS Voice over PS is supported or not. So, in order to avoid impacts on the IMS AS, this solution proposes that UDM and HSS FE are configured with indication regarding being the default system for IMS voice. Both will inspect this default indication, in order to execute the T-ADS information retrieval procedure, or reject it. + +![Sequence diagram showing user identity resolution for IMS AS. Lifelines: IMS AS, IMS HSS/SLF, HSS FE, UDM. The process involves a Dh/Sh request from IMS AS to IMS HSS/SLF, a location server lookup, a Redirect info response, a Sh request from IMS AS to HSS FE, a Sh answer from HSS FE to IMS AS, a Sh request from HSS FE to UDM (Note 3a), and a Sh answer from UDM to HSS FE (Note 4a). Network procedures T-ADS, NPLI request over S6a, and Namf_MT_ProvideDomainSelectionInfo are indicated.](42e18c25bfd455a5a57f207bacfcb970_img.jpg) + +``` + +sequenceDiagram + participant IMS AS + participant IMS HSS/SLF + participant HSS FE + participant UDM + + Note left of IMS AS: Network procedure: T-ADS + IMS AS->>IMS HSS/SLF: 1. Dh/Sh request + IMS HSS/SLF->>IMS HSS/SLF: location server lookup + IMS HSS/SLF-->>IMS AS: 2. Redirect info + IMS AS->>HSS FE: 3. Sh request + Note right of HSS FE: Network Procedure: NPLI request over S6a + HSS FE-->>IMS AS: 4. Sh answer + HSS FE->>UDM: 3a. Sh request (Note) + Note right of UDM: Network Procedure: Namf_MT_ProvideDomainSelectionInfo + UDM-->>HSS FE: 4a. Sh answer (Note) + +``` + +Sequence diagram showing user identity resolution for IMS AS. Lifelines: IMS AS, IMS HSS/SLF, HSS FE, UDM. The process involves a Dh/Sh request from IMS AS to IMS HSS/SLF, a location server lookup, a Redirect info response, a Sh request from IMS AS to HSS FE, a Sh answer from HSS FE to IMS AS, a Sh request from HSS FE to UDM (Note 3a), and a Sh answer from UDM to HSS FE (Note 4a). Network procedures T-ADS, NPLI request over S6a, and Namf\_MT\_ProvideDomainSelectionInfo are indicated. + +Figure 6.4.3.5.3-1: User identity to HSS FE identity or UDM identity resolution for IMS AS + +NOTE 2: This assumes that UDM implements the Sh operations UDR/UDA to trigger the T-ADS retrieval procedure. Potential conversion of Diameter Sh operation to an Nudm service operation is out of the scope of this study. + +### 6.4.4 Impacts on existing services and interfaces + +#### 6.4.4.1 General + +This solution addresses scenarios in which the operator deployment is already a layered architecture according to TS 23.335 [3] or when user data are stored in an external entity via non-standard interfaces, according to TS 23.002 [5], clause 4.1.1. Purely monolithic scenarios, in which the user data are stored within the HSS itself, would need to migrate towards a layered architecture. + +The solution is basically an operator choice restricted to the introduction of a Data Access Layer with the capabilities described in clauses 6.4.3.1 to 6.4.3.4, and does not impact the specified interfaces with new operations. + +The solution is also based on network configuration, by including SLF functionality for every IMS operation directed towards a location server (either HSS FE, IMS HSS or UDM). The SLF is configured as the contact point for I-CSCF, S-CSCF and IMS AS, and needs to be provisioned with the list of location servers serving the UEs in the network. + +The solution proposes to add information regarding the system registration status, i.e. the system serving the UE: + +- For 5G profile, this extension can be handled as the resources Amf3GppAccessRegistration and AmfNon3GppAccessRegistration in the Nudr\_DM\_Update service operation as specified in TS 29.505 [9]. +- For 4G profile, this extension can be mapped to the repository field where MME reference is held. Since the organisation of data in the EPS UDR is not standardised, this mapping would be left for implementation. + +Finally, the solution proposes adding the Sh pair UDR/UDA (Diameter) to UDM as a temporary solution until IMS is adapted to service based architecture or any other solution is specified for T-ADS information retrieval by IMS. + +It also proposes to add a new data key (=IMPU) to the Subscription Data data set in the Nudr\_DM\_Query operation. + +#### 6.4.4.2 Summary of impacts on UDM + +- For handovers without N26 support: + - Add configuration indication regarding support or not of dual registrations +- For T-ADS information retrieval: Add Sh pair UDR/UDA in case of single and dual registrations: + - Add indication regarding default system for IMS Voice over PS for dual registration mode of operation. +- For P-CSCF restoration: + - For Option 1, no impact (i.e. make use of PCF based restoration or detection of failure by SMF/UPF) + - For Option 2: Add Cx pair SAR/SAA for P-CSCF restoration + +#### 6.4.4.3 Summary of impacts on HSS FE + +No impact for procedures with N26 support. + +For handovers without N26 support: + +- Add configuration indication regarding support or not of dual registrations. + +For T-ADS information retrieval in dual registration mode of operation: + +- Add indication regarding default system for IMS Voice over PS. + +#### 6.4.4.4 Summary of impacts on EPS UDR + +The impacts on the EPS UDR are left for implementation, since the protocols to access and the organisation of data is implementation specific. + +### 6.4.5 Evaluation + +Solution 4 proposes an architecture that does not require direct interaction between the UDM and the HSS FE. + +The solution makes use of an adaptation layer, named Access Data Layer, that separates the applications front end logic from database technology/protocol in the back end repositories. + +The solution addresses all interworking scenarios depicted in TS 23.501 [6] and TS 23.502 [2], including support for IMS procedures. + +The advantages of this solution is that: + +- It addresses effective separation of HSS FE and UDM to enable multivendor deployments +- It avoids new interface and new operations specification between the HSS and UDM + +- It is possible to introduce only UDM when deploying a 5GS system, without having to update/upgrade the HSS FE, or having to introduce this functionality in deployments with single core network. +- Standardisation effort is minimised and restricted to potential incorporation of Sh/Cx operations for UDM, in case FS\_eIMS5G study (TS 23.794 [14]) does not incorporate the changes needed for P-CSCF restoration and T-ADS information retrieval. +- Introduction of this solution does not impact other network functions that may be accessing the different repositories, while it provides the means to further split other network functions defined in Rel-15 (i.e. PCF/PCRF). + +The disadvantage of this solution is to making use of SLF functionality for IMS when some deployments may not be using it. + +This solution would not be possible if a monolithic HSS is deployed, unless this monolithic HSS becomes the shared subscriptions repository that interfaces to the Data access layer. + +In a scenario where a layered architecture is used, taking into account that Ud data model is not standardised, this would require that the Data Access Layer is aware of the structure of the Ud notifications deployed by the operator, i.e. the Data Access Layer needs to be implemented in alignment with the existing EPS UDR implementations. + +## 6.5 Solution #5: Use of a Data Access Layer for interaction between HSS FE and UDM with separate repositories + +### 6.5.1 Introduction + +This solution applies to Key Issue 1 and describes how HSS FE and UDM interact when data repositories are separate. + +### 6.5.2 High-level Description + +#### 6.5.2.1 Assumptions + +It is assumed that: + +- Technologies and protocols to access the data stored in the 5G repository are assumed to be database specific or proprietary, but exposing operations to query, create, delete and update of data, as well as subscriptions/notifications to modifications of such data.. +- 5G UEs are assumed to be provisioned in the 5G repository and able to use 4G networks (with the corresponding limitations). 4G UEs are provisioned in the EPS UDR, as of today, but not assumed to be able to use 5G core services. +- From an authentication perspective, this proposal assumes ARPF to be a separate entity from UDM, collocated with or incorporated to the HE/AuC specified in TS 33.401 [13], and it does not specifically address separation of ARPF logic from ARPF storage, in which case the interface would remain unspecified as it is for HE(AuC). This implies that each system will retrieve authentication data from the same subscriber credentials storage and vectors generation will be performed without SQN reuse. For handovers security with and without N26 for single and dual registration modes, the same procedures as described in TS 33.501 [12] clause 8 are assumed. +- The IMS data for the UEs is assumed to be stored in the EPS UDR. +- From an IMS interaction perspective, it is assumed that IMS HSS/SLF is a logical entity that can act as an application front end making use of the EPS UDR, following the specification TS 23.335 [3] and implementing Cx/Dx and Sh/Dh interfaces that remain untouched. The colocation of IMS HSS/SLF and HSS FE is an operator option. + +NOTE: This is considered as a temporary solution in order to cope with the transition of legacy IMS towards a service based IMS, work in progress in TR 23.794 [14]. + +#### 6.5.2.2 Architectural proposal + +This solution makes use of a layer that separates the applications front end logic from the database technology/protocol used, leveraging the authorisation and policing capabilities from Rel-15 data storage architecture, and incorporating additional features to serve interworking with legacy systems. + +Hence, in addition to access control for application front ends, policing and offering a common view of the information irrespective of where it is stored, the solution adds protocol conversion between application front ends and the repository, as well as a notifications engine to mimic the relevant notifications that will trigger specific procedures at the different front end applications and related to handovers between one system and the other. + +The solution uses similar concepts as the current Solution #1 ("Retrieving subscription data from separate UDR repositories for EPS and 5GS subscription data using a UDR Translation Function (UTF)"), but makes use of different procedures for IMS interactions. + +![High level architecture diagram showing EPC and 5GC connected to HSS FE and UDM respectively, which then connect to a Data Access Layer. The Data Access Layer connects to EPS UDR (4G subscriptions) and 5GS UDR (5G subscriptions).](0997dbaa9dfecedd60029d70b53327b8_img.jpg) + +The diagram illustrates a high-level architecture for the interaction of HSS FE and UDM with separate repositories. At the top, two network functions, EPC and 5GC, are shown. EPC is connected to an HSS FE, and 5GC is connected to a UDM. Both HSS FE and UDM have interfaces labeled 'Ud' and 'Nudr' respectively, which connect to a central 'Data Access Layer' represented by a horizontal grey bar. Below the Data Access Layer, there are two database repositories: 'EPS UDR' containing '4G subscriptions' and '5GS UDR' containing '5G subscriptions'. The Data Access Layer is connected to both repositories. A dashed line indicates a logical or data flow connection between the HSS FE and the 5GS UDR, passing through the Data Access Layer. + +High level architecture diagram showing EPC and 5GC connected to HSS FE and UDM respectively, which then connect to a Data Access Layer. The Data Access Layer connects to EPS UDR (4G subscriptions) and 5GS UDR (5G subscriptions). + +Figure 6.5.2.2-1: High level architecture for interaction of HSS FE and UDM with separate repositories + +![Figure 6.5.2.2-2: High level architecture for interaction of HSS FE, IMS HSS/SLF and UDM with separate repositories. The diagram shows three network functions (EPC, IMS, 5GC) connected to a central 'Data Access Layer'. EPC connects to HSS FE, which connects to the Data Access Layer via a 'Ud' interface. IMS connects to IMS HSS/SLF, which also connects to the Data Access Layer via a 'Ud' interface. 5GC connects to UDM, which connects to the Data Access Layer via a 'Nudr' interface. Below the Data Access Layer are two repositories: EPS UDR (containing 4G subscriptions) and 5GS UDR (containing 5G subscriptions). The Data Access Layer is shown interacting with both repositories.](7ed5d5770331f31ade15439a21c31425_img.jpg) + +Figure 6.5.2.2-2: High level architecture for interaction of HSS FE, IMS HSS/SLF and UDM with separate repositories. The diagram shows three network functions (EPC, IMS, 5GC) connected to a central 'Data Access Layer'. EPC connects to HSS FE, which connects to the Data Access Layer via a 'Ud' interface. IMS connects to IMS HSS/SLF, which also connects to the Data Access Layer via a 'Ud' interface. 5GC connects to UDM, which connects to the Data Access Layer via a 'Nudr' interface. Below the Data Access Layer are two repositories: EPS UDR (containing 4G subscriptions) and 5GS UDR (containing 5G subscriptions). The Data Access Layer is shown interacting with both repositories. + +Figure 6.5.2.2-2: High level architecture for interaction of HSS FE, IMS HSS/SLF and UDM with separate repositories + +### 6.5.3 Services and Illustrated Procedures + +#### 6.5.3.1 General description + +The proposed data access layer will subscribe to changes performed in the EPS UDR and 5G repository, issuing some notifications towards the UDM or the HSS FE for specific UEs that may maintain profiles for 4G and 5G. When needed, the Data Access layer translates Nudr operations issued by UDM into Ud requests towards the EPS UDR and vice-versa. + +![Figure 6.5.3.1-1: General procedure for notifications via a Data Access Layer. The diagram shows HSS FE and UDM connected to a central 'Data Access Layer'. HSS FE sends a 'Ud' request to the Data Access Layer, which then sends a notification (red arrow) to the '4G subscriptions' repository. UDM sends a 'Nudr' request to the Data Access Layer, which then sends a notification (blue arrow) to the '5G subscriptions' repository. The Data Access Layer also sends notifications (dashed arrows) to the HSS FE and UDM regarding '4G UEs' and '5G UEs'.](367378559e35017a5e1a6f5c30798c5a_img.jpg) + +Figure 6.5.3.1-1: General procedure for notifications via a Data Access Layer. The diagram shows HSS FE and UDM connected to a central 'Data Access Layer'. HSS FE sends a 'Ud' request to the Data Access Layer, which then sends a notification (red arrow) to the '4G subscriptions' repository. UDM sends a 'Nudr' request to the Data Access Layer, which then sends a notification (blue arrow) to the '5G subscriptions' repository. The Data Access Layer also sends notifications (dashed arrows) to the HSS FE and UDM regarding '4G UEs' and '5G UEs'. + +Figure 6.5.3.1-1: General procedure for notifications via a Data Access Layer + +#### 6.5.3.2 5GS procedures + +The procedures specified in TS 23.502 [2] for Registration (clause 4.2.2.2), Deregistration (clause 4.2.2.3), UE Configuration Update (clause 4.2.4), Reachability procedures (clause 4.2.5), Session Management (clause 4.3), and User profile Management (clause 4.2.5) do not change when introducing this solution. + +Authentication procedures at registration (step 9 in clause 4.2.2.2 of TS 23.502 [2]) does not change either when introducing this solution. + +Any potential query of information related to the 4G subscription profile of the UE, would imply a mapping/translation of the NUdr\_DM\_Query in the Data Access Layer to be converted into a Ud query to the EPS UDR. + +#### 6.5.3.3 EPS procedures + +EPS procedures, including authentication ones, are not expected to be affected from the point of view of network signalling. + +The Data Access Layer will subscribe to changes in the EPS UDR related to 5G subscribers having also 4G profiles in the EPS UDR. When any action is performed at the level of 4G data for the particular UE (like attachment, detachment, etc), the Data Access Layer will issue a notification towards the UDM. UDM will perform any action needed depending on the status of the UE, interworking needed, etc. + +This is intended to facilitate the tracking of the subscriber in either system, in order to execute the relevant deregistration in case the subscriber moves from one to the other. + +![Sequence diagram showing notification to UDM when UE attaches to EPS. The diagram involves four entities: HSS FE, EPS UDR, Data Access Layer, and UDM. The sequence starts with a '1. Ud Request' from HSS FE to EPS UDR, marked as a 'Network procedure'. The EPS UDR responds with '2. Ud Response', marked as 'UE marked in 4G network'. The EPS UDR then sends a '3. Ud Notify' to the Data Access Layer. Finally, the Data Access Layer sends a '4. Nudr_DM_Notify' to the UDM, marked as a 'Network procedure ack'.](3263a25e110201638bda790456af2909_img.jpg) + +``` + +sequenceDiagram + participant HSS FE + participant EPS UDR + participant DAL as Data Access Layer + participant UDM + + Note left of HSS FE: Network procedure + HSS FE->>EPS UDR: 1. Ud Request + EPS UDR-->>HSS FE: 2. Ud Response + Note right of EPS UDR: UE marked in 4G network + EPS UDR->>DAL: 3. Ud Notify + Note left of DAL: Network procedure ack + DAL->>UDM: 4. Nudr_DM_Notify + +``` + +Sequence diagram showing notification to UDM when UE attaches to EPS. The diagram involves four entities: HSS FE, EPS UDR, Data Access Layer, and UDM. The sequence starts with a '1. Ud Request' from HSS FE to EPS UDR, marked as a 'Network procedure'. The EPS UDR responds with '2. Ud Response', marked as 'UE marked in 4G network'. The EPS UDR then sends a '3. Ud Notify' to the Data Access Layer. Finally, the Data Access Layer sends a '4. Nudr\_DM\_Notify' to the UDM, marked as a 'Network procedure ack'. + +**Figure 6.5.3.3-1: Notification to UDM when UE attaches to EPS** + +The Ud Request expected to trigger a notification is Update Data as specified by TS 23.335 [3]. There is no need to notify any query of data performed by HSS FE. + +Any potential query of information related to the 5G subscription profile of the UE, would imply a mapping/translation of the Ud Query in the Data Access Layer to be converted into a query to the 5G repository. + +As the technologies and protocols used to access the data stored in the repositories are operator deployment choices, the mapping of the Ud Notify depicted in the previous chart to the Nudr\_DM\_Notify operation towards the UDM is left as an operator deployment choice in agreement with its vendors. + +#### 6.5.3.4 Handover procedures + +##### 6.5.3.4.0 General + +For handover procedures, three cases are differentiated according to TS 23.501 [6] and TS 23.502 [2]: + +- Single registration mode with N26 support. +- Single registration mode without N26 support. + +- Dual registration. + +For single registration mode with N26 support, any registration/attachment shall convey a cancelation of the location in the source system. The UE subscription data, with the exception of the Intersystem Continuity Data, will be valid in only one of the systems at a time. + +For single registration without N26 support, registration/attachment shall also convey a cancelation of the location in the source system if simultaneous registration of both MME and AMF is not supported, according to TS 23.501 [6] clause 5.17.2.3.1. + +NOTE 1: Since UDM and HSS FE are split and separate repositories exist, simultaneous registration of MME and AMF should always be possible, unless it is disabled by configuration in UDM, HSS FE and in the proposed Access Data Layer. + +This solution proposes that, in single registration modes with and without N26, the PGW-C+SMF with corresponding APN/DNN is replicated in both repositories and updated/queried by either party from their associated back-end repository. I.e. at handover 5GS-EPS, HSS FE will query from EPS UDR and at EPS-5GS, UDM will query the 5G UDR. + +This replication, together with an indication regarding the UE being served by 5GC or EPC facilitates all handover scenarios with single registration. + +This can be achieved as follows: + +![Sequence diagram illustrating the storage of PGW-C+SMF and APN/DNN with UE camping in EPS in single registration mode. The diagram shows interactions between HSS FE, EPS UDR, Data Access Layer, 5G Repository, and UDM.](7dfd8dd318dcfc36eaf4c967ddfb94c1_img.jpg) + +``` + +sequenceDiagram + participant HSS FE + participant EPS UDR + participant DAL as Data Access Layer + participant 5G Repository + participant UDM + + Note left of HSS FE: Network procedure: Update Location/Notify + HSS FE->>EPS UDR: 1. Ud Request + EPS UDR-->>HSS FE: 2. Ud Response + Note right of EPS UDR: PGW-C+SMF & APN/DNN Stored in repository + EPS UDR->>DAL: 3. Ud Notify + DAL->>UDM: 4. Nudm_DM_Notify(intersystem info) + Note right of UDM: Dual reg = NO + UDM->>DAL: 5. Nudm_DM_Update + DAL->>5G Repository: 6. Write + Note right of 5G Repository: PGW-C+SMF & APN/DNN Stored in repository + 5G Repository-->>DAL: 7. Ack + DAL-->>UDM: 8. Ack + Note left of HSS FE: Network procedure ack + +``` + +Sequence diagram illustrating the storage of PGW-C+SMF and APN/DNN with UE camping in EPS in single registration mode. The diagram shows interactions between HSS FE, EPS UDR, Data Access Layer, 5G Repository, and UDM. + +**Figure 6.5.3.4.0-1: Storage of PGW-C+SMF and APN/DNN with UE camping in EPS in single registration mode** + +While for 5GS, it is stored as following: + +![Sequence diagram for Figure 6.5.3.4.0-2: Storage of PGW-C+SMF and APN/DNN with UE camping in 5GS in single registration mode. The diagram shows interactions between EPS UDR, Data Access Layer, 5G Repository, and UDM. The process starts with a network procedure (PDU session initiation) at the UDM, followed by Nudm_DM_Update, Request to 5G Repository, Ack, and Ack. The Data Access Layer then sends a U Request (Intersystem info) to the EPS UDR, which responds with U Response. The EPS UDR also stores PGW-C+SMF & APN/DNN in the repository. A 'Dual reg = NO' flag is shown. The process ends with a network procedure ack at the UDM.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) + +``` + +sequenceDiagram + participant EPS UDR + participant DAL as Data Access Layer + participant 5G Repository + participant UDM + Note right of UDM: Network procedure: PDU session initiation + UDM->>DAL: 1. Nudm_DM_Update + DAL->>5G Repository: 2. Request to 5G Repository + 5G Repository-->>DAL: 3. Ack + Note right of 5G Repository: PGW-C+SMF & APN/DNN Stored in repository + DAL->>UDM: 4. Ack + DAL->>EPS UDR: 5. U Request (Intersystem info) + Note right of EPS UDR: PGW-C+SMF & APN/DNN Stored in repository + EPS UDR-->>DAL: 6. U Response + Note right of DAL: Dual reg = NO + Note right of UDM: Network procedure ack + +``` + +Sequence diagram for Figure 6.5.3.4.0-2: Storage of PGW-C+SMF and APN/DNN with UE camping in 5GS in single registration mode. The diagram shows interactions between EPS UDR, Data Access Layer, 5G Repository, and UDM. The process starts with a network procedure (PDU session initiation) at the UDM, followed by Nudm\_DM\_Update, Request to 5G Repository, Ack, and Ack. The Data Access Layer then sends a U Request (Intersystem info) to the EPS UDR, which responds with U Response. The EPS UDR also stores PGW-C+SMF & APN/DNN in the repository. A 'Dual reg = NO' flag is shown. The process ends with a network procedure ack at the UDM. + +**Figure 6.5.3.4.0-2: Storage of PGW-C+SMF and APN/DNN with UE camping in 5GS in single registration mode** + +NOTE 2: To avoid impacts on HSS FE and its related procedures, the data is written directly by the Data Access Layer. HSS FE will find the information available when UE camps back in EPS and requests continuity for single registration without N26 + +For handover procedures in dual registration mode, the UE will remain registered/attached to the two system simultaneously with valid subscription data in both systems at the same time. Moving sessions between systems remains as a UE implementation option. + +##### 6.5.3.4.1 5GS to EPS with N26 + +In 5GS to EPS handovers, the attach in the EPS will generate a Ud Request to modify data by HSS FE followed by a Ud Response by the EPS UDR and a Ud notification to the Data Access Layer. This will trigger a Nudr\_DM\_Notify to the UDM to indicate the UE is now under EPS control. UDM should in turn modify the location data in the 5G profile and will proceed to deregister the AMF the UE moved from. + +![Sequence diagram for Figure 6.5.3.4.1-1: Notification to UDM at UE attachment to EPS. The diagram shows interactions between HSS FE, EPS UDR, Data Access Layer, UDM, and 5G Repository. The process starts with a network procedure at the HSS FE, followed by Ud Request, Ud Response, and Ud Notify. The Data Access Layer then sends Nudr_DM_Notify to the UDM, which responds with Nudr_DM_Update. The Data Access Layer also sends a Request to 5G Repository. The UDM performs a network procedure to deregister the UE from the AMF. The process ends with the UE marked in the 5G repository.](b5987d63203a5fa601921039922ac520_img.jpg) + +``` + +sequenceDiagram + participant HSS FE + participant EPS UDR + participant DAL as Data Access Layer + participant UDM + participant 5G Repository + Note left of HSS FE: Network procedure + HSS FE->>EPS UDR: 1. Ud Request + EPS UDR-->>HSS FE: 2. Ud Response + Note right of EPS UDR: UE marked in 4G network + EPS UDR->>DAL: 3. Ud Notify + DAL->>UDM: 4. Nudr_DM_Notify + UDM-->>DAL: 5. Nudr_DM_Update + Note right of UDM: Network procedure to deregister UE from AMF + DAL->>5G Repository: 6. Request to 5G repository + Note right of 5G Repository: UE in 5G mark removed + Note left of HSS FE: Network procedure ack + +``` + +Sequence diagram for Figure 6.5.3.4.1-1: Notification to UDM at UE attachment to EPS. The diagram shows interactions between HSS FE, EPS UDR, Data Access Layer, UDM, and 5G Repository. The process starts with a network procedure at the HSS FE, followed by Ud Request, Ud Response, and Ud Notify. The Data Access Layer then sends Nudr\_DM\_Notify to the UDM, which responds with Nudr\_DM\_Update. The Data Access Layer also sends a Request to 5G Repository. The UDM performs a network procedure to deregister the UE from the AMF. The process ends with the UE marked in the 5G repository. + +**Figure 6.5.3.4.1-1: Notification to UDM at UE attachment to EPS** + +No other action is expected to be performed by the UDM, and the control by the EPS will proceed as specified in the TS 23.502 [2], clause 4.11.1.2.1, with the difference that the HSS FE will not cancel the location of the AMF during the TAU procedure. + +Instead, the HSS FE will acknowledge the location update to the new MME and proceed as normal and it will be the UDM the one deregistering the AMF following the flow shown before. + +##### 6.5.3.4.2 EPS to 5GS with N26 + +In EPS to 5GS handovers, the registration in the 5GS will generate a Nudr request and subsequent notification when data is stored in the 5G repository. The Data Access Layer will capture that and generate a notification towards the HSS FE indicating the UE has left the EPS. + +![Sequence diagram for EPS to 5GS with N26 registration notification. Lifelines: HSS FE, EPS UDR, Data Access Layer, UDM, 5G Repository. The sequence shows the Data Access Layer sending a Nudr_DM_Update to the UDM, which then sends a Request to the 5G Repository. The 5G Repository responds with an Ack. The Data Access Layer then sends a Ud Notify to the HSS FE. The HSS FE sends a Ud Request to the EPS UDR, which responds with a Ud Response. A note indicates a network procedure to cancel location in the MME is initiated by the HSS FE.](68a5a1a1a761c652b4b4c56da7cf9914_img.jpg) + +``` + +sequenceDiagram + participant HSS FE + participant EPS UDR + participant DAL as Data Access Layer + participant UDM + participant 5G Repository + + Note right of 5G Repository: UE in 5G + DAL->>UDM: 1. Nudr_DM_Update + Note right of UDM: Network procedure + UDM->>5G Repository: 2. Request to 5G repository + 5G Repository-->>UDM: 3. Ack + DAL->>HSS FE: 4. Ud Notify (Note 1) + HSS FE->>EPS UDR: 5. Ud Request + Note left of HSS FE: Network procedure : Cancel Location to MME + EPS UDR-->>HSS FE: 6. Ud Response + +``` + +Sequence diagram for EPS to 5GS with N26 registration notification. Lifelines: HSS FE, EPS UDR, Data Access Layer, UDM, 5G Repository. The sequence shows the Data Access Layer sending a Nudr\_DM\_Update to the UDM, which then sends a Request to the 5G Repository. The 5G Repository responds with an Ack. The Data Access Layer then sends a Ud Notify to the HSS FE. The HSS FE sends a Ud Request to the EPS UDR, which responds with a Ud Response. A note indicates a network procedure to cancel location in the MME is initiated by the HSS FE. + +Figure 6.5.3.4.2-1: Notification to HSS FE at UE registration in 5GS + +NOTE 1: HSS FE subscribed to changes regarding UEs having 4G and 5G profiles. + +The procedure follows the specification in TS 23.502 [2] clause 4.11.1.2.2 with the modification that it is the HSS FE the one initiating the relevant cancel location towards the MME node the UE has moved from. + +NOTE 2: The mapping of the acknowledgement from the 5G repository to the Ud Notify towards the HSS FE depicted in the previous chart is left for implementation based on operator deployment. + +As an alternative to the previous flow, the Data Access Layer can modify the UE data in the EPS UDR, which in turn would trigger a notification towards the HSS FE (HSS FE would have subscribed to changes in the EPS UDR). This alternative would save impacts in the HSS FE that would only need to subscribe to changes in the EPS UDR and be notified when the data is updated. + +##### 6.5.3.4.3 5GS to EPS without N26 - single registration + +For single registration without N26, HSS FE will be configured as not supporting dual registration. Thus, the attach to the EPS when UE moves from 5GS to EPS, will imply a cancellation of location in the AMF from where the UE moved. + +This procedure is aligned with what is described in clause 6.5.3.4.1 of this solution. + +The EPS attach is expected to trigger a Ud Update operation towards the EPS UDR, and a response to HSS FE including the PGW-C+SMF address (together with APN/DNN information) being used. + +The proposal with this solution is to replicate the information in both repositories. This way EPS UDR will contain the information about PGW-C+SMF needed for the handover cases and will return it to the MME in the Update Location Response. See general clause 6.5.3.4.0 of this solution. + +##### 6.5.3.4.4 EPS to 5GS without N26 - single registration + +For single registration without N26, UDM will be configured as not supporting dual registration. Thus, the registration to the 5GS when UE moves from EPS to 5GS, will imply a cancellation of location in the MME from where the UE moved. + +The registration in the 5GS, would trigger a notification to the Access Data Layer that, in turn, would imply a Ud notification to the HSS FE to cancel the location in the MME. This procedure is aligned with what is described in clause 6.5.3.4.2 of this solution. + +##### 6.5.3.4.5 Handovers without N26 - dual registration + +For handover procedures in dual registration mode, the UE will remain registered/attached to the two system simultaneously with valid subscription data in both systems at the same time. Moving sessions between systems remains as a UE implementation option. + +Attachment/Registration of the UE in either system does not convey any cancellation in the source system. This is achieved by analysing the UDM and HSS FE configuration to support or not dual registrations. + +#### 6.5.3.5 IMS interaction + +##### 6.5.3.5.1 Access to IMS data + +Access to IMS data for creation, deletion, query and modification follows the specification in TS 23.228 [7] and TS 23.335 [3] by IMS making use of the IMS HSS/SLF functionality (either as a stand alone application front end or collocated with HSS FE). + +It is not expected that any of the IMS entities need to interact with UDM, with the exception of the P-CSCF restoration mechanism invoked by S-CSCF, and the T-ADS information retrieval by the IMS AS. + +For these specific cases, it is proposed to use the SLF functionality for UE identity to UDM identity or HSS FE identity resolution, according to TS 23.228 [7] clause 5.8. + +NOTE 1: It is proposed to introduce SLF functionality since the split of UDM and HSS FE will imply multiple addressable location servers for the 5G UEs and these IMS procedures. + +NOTE 2: Since the I-CSCF, S-CSCF and IMS AS will always interrogate the SLF to find the location server serving the UE, the SLF needs to be configured to return the IMS HSS address in first place since it is the front end able to return the IMS profile for the UE. + +NOTE 3: The evolution of IMS can also imply the IMS profile of the 5G UEs to be moved into the 5G repository. This can impact the way some procedures are executed for the different UEs. + +Any Cx or Sh operation triggered by CSCF or IMS AS, except restoration and T-ADS information retrieval, will be handled by the IMS HSS front end (either stand alone or collocated with the HSS FE). + +When UE is registered to IMS, EPS UDR will contain the indication regarding the UE being served or not by EPS, and 5G repository will contain the indication regarding the UE being served by 5GS. This is proposed to be done as per the description in the common procedures, regardless the UE re-registers or not to IMS when moving between the systems (according to clause 5.2.2.4 of TS 23.228 [7]). + +These indications are proposed to be checked when either P-CSCF restoration or T-ADS information retrieval is received by UDM or HSS FE (see next clauses). + +In principle, both UDM and HSS FE would not require any additional action than what is described before for the general procedures. + +##### 6.5.3.5.2 P-CSCF Restoration procedures + +The P-CSCF restoration procedure via UDM is an optional mechanism according to TS 23.380 [8]. + +The following two options are considered regardless the support of N26 and UE mode of operation (single or dual registration). + +- **Option 1:** When UDM and HSS FE are split, the preferred P-CSCF restoration procedure would be that performed by detection of the failure by SMF/UPF according to TS 23.380 [8] clause 5.8.3, or using the PCF based P-CSCF restoration as specified in clause 5.8.5 of TS 23.380 [8]. + +NOTE 1: The adaptation of IMS to service based architecture, making use of proper virtualisation/cloud mechanisms for e.g. self-healing, high availability, redundancy, etc, would most likely make unnecessary the use of the current restoration procedures. + +- **Option 2:** To enable the P-CSCF restoration via either the UDM or the HSS FE, the SLF functionality is invoked in order to perform a user identity to HSS FE identity or UDM identity resolution. + +The SLF will return the list of different servers (UDMs and HSS FEs) that may be in charge of the UE at that point in time, for the S-CSCF to request the relevant P-CSCF restoration mechanism to the relevant entity. This procedure is according to TS 29.228 [10] clause 6.4. + +![Sequence diagram for User identity to HSS FE identity or UDM identity resolution for S-CSCF. The diagram shows four lifelines: S-CSCF, IMS HSS/SLF, HSS FE, and UDM. The process starts with a 'Dx/Cx request' from S-CSCF to IMS HSS/SLF. The IMS HSS/SLF performs a 'location server lookup' and returns 'Redirect info' to S-CSCF. S-CSCF then sends a 'Cx request' to HSS FE, which returns a 'Cx answer'. S-CSCF also sends a 'Cx request (Note 2)' to UDM, which returns a 'Cx answer (Note 2)'. A note on the left indicates this is part of the 'Network procedure: P-CSCF restoration'.](376f80eb8a41369e87da63a0210d173e_img.jpg) + +``` + +sequenceDiagram + participant S-CSCF + participant IMS HSS/SLF + participant HSS FE + participant UDM + + Note left of S-CSCF: Network procedure: P-CSCF restoration + S-CSCF->>IMS HSS/SLF: 1. Dx/Cx request + IMS HSS/SLF->>IMS HSS/SLF: location server lookup + IMS HSS/SLF->>S-CSCF: 2. Redirect info + S-CSCF->>HSS FE: 3. Cx request + HSS FE->>S-CSCF: 4. Cx answer + S-CSCF->>UDM: 3a. Cx request (Note 2) + UDM->>S-CSCF: 4a. Cx answer (Note 2) + +``` + +Sequence diagram for User identity to HSS FE identity or UDM identity resolution for S-CSCF. The diagram shows four lifelines: S-CSCF, IMS HSS/SLF, HSS FE, and UDM. The process starts with a 'Dx/Cx request' from S-CSCF to IMS HSS/SLF. The IMS HSS/SLF performs a 'location server lookup' and returns 'Redirect info' to S-CSCF. S-CSCF then sends a 'Cx request' to HSS FE, which returns a 'Cx answer'. S-CSCF also sends a 'Cx request (Note 2)' to UDM, which returns a 'Cx answer (Note 2)'. A note on the left indicates this is part of the 'Network procedure: P-CSCF restoration'. + +**Figure 6.5.3.5.2-1: User identity to HSS FE identity or UDM identity resolution for S-CSCF** + +NOTE 2: This assumes that UDM implements the Cx operations SAR/SAA to trigger the P-CSCF restoration. Potential conversion of Diameter Cx operation to an Nudm service operation is out of the scope of this study. + +NOTE 3: It is assumed that S-CSCF is aware of the IMS registration status of the UE prior to request P-CSCF restoration. + +Both HSS FE and UDM will check the UE registration status in the corresponding network in order to either execute the procedure (according to TS 23.380 [8]) or reject it. + +No other impact is expected for restoration. + +##### 6.5.3.5.3 Terminating domain selection information for IMS voice + +According to TS 23.501 [6], clause 5.16.3.6, the UDM/HSS shall be able to query the serving AMF for T-ADS related information, and AMF shall respond to the query with the relevant information unless the UE is detached: + +- whether or not IMS voice over PS Session is supported in the registration area(s) where the UE is currently registered; +- whether or not IMS voice over PS Session Supported Indication over non-3GPP access is supported in the WLAN where the UE is currently registered; +- the time of the last radio contact with the UE; and +- the current Access Type and RAT type. + +Retrieval of T-ADS information is initiated by the IMS AS. + +To retrieve the T-ADS information from either the UDM or the HSS FE, the SLF functionality is invoked in order to perform a user identity to HSS FE identity or UDM identity resolution. + +The SLF will return the list of different servers (UDMs and HSS FEs) that may be in charge of the UE at that point in time, for the IMS AS to request the information for access domain selection. This procedure is according to TS 29.328 [11] clause 6.5. + +If the UE is attached to IMS via 5GS, the T-ADS information request to the IMS HSS/SLF will end up in a Sh request (UDR/UDA) to UDM, which in turn will invoke the AMF service Namf\_MT\_ProvideDomainSelectionInfo as specified in TS 23.501 [6] clause 5.16.3.6 and TS 23.228 [7] Annex Y. + +To translate IMPU to SUPI, for the cases in which the Sh request is based on IMPU, the 5G UDR can incorporate a new data key (=IMPU) for the Subscription Data data set to be used for the Nudr\_DM\_Query operation, in order to request identifier translation from IMPU to SUPI. + +The query to the 5G UDR is simply converted by the Access Data Layer into a Ud request to the IMS data repository, in order to retrieve the IMSI that is associated with the IMPU received in the Sh request. + +The request from IMS AS, when the UE is attached to the EPS, should follow the same procedures as defined in TS 23.228 [7] clause 4.2.4a. + +NOTE 1: It is assumed that IMS AS is aware of the IMS registration status of the UE prior to request T-ADS information. + +Both UDM and HSS FE will check the registration status in the corresponding network in order to either execute the procedure (according to TS 23.228 [7]) or reject it. + +In case of dual registration, and according to annex D of TS 29.328 [11], the IMS AS will expect the T-ADS information containing 0 or 1 RAT types, depending on whether IMS Voice over PS is supported or not. So, in order to avoid impacts on the IMS AS, this solution proposes that UDM and HSS FE are configured with indication regarding being the default system for IMS voice. Both will inspect this default indication, in order to execute the T-ADS information retrieval procedure, or reject it. + +![Sequence diagram illustrating User identity to HSS FE identity or UDM identity resolution for IMS AS. The diagram shows four lifelines: IMS AS, IMS HSS/SLF, HSS FE, and UDM. The sequence of messages is: 1. Dh/Sh request (Network procedure: T-ADS) from IMS AS to IMS HSS/SLF; 2. Redirect info from IMS HSS/SLF to IMS AS; 3. Sh request from IMS AS to HSS FE; 4. Sh answer from HSS FE to IMS AS; 3a. Sh request (Note) from HSS FE to UDM; 4a. Sh answer (Note) from UDM to HSS FE. Annotations include 'location server lookup' for step 2, 'Network Procedure: NPLI request over S6a' for step 4, and 'Network Procedure: Namf_MT_ProvideDomainSelectionInfo' for step 4a.](2dc649aff45a8a0924db45fc3bd6aabb_img.jpg) + +``` + +sequenceDiagram + participant IMS AS + participant IMS HSS/SLF + participant HSS FE + participant UDM + + Note left of IMS AS: Network procedure: T-ADS + IMS AS->>IMS HSS/SLF: 1. Dh/Sh request + Note right of IMS HSS/SLF: location server lookup + IMS HSS/SLF-->>IMS AS: 2. Redirect info + IMS AS->>HSS FE: 3. Sh request + Note right of HSS FE: Network Procedure: NPLI request over S6a + HSS FE-->>IMS AS: 4. Sh answer + Note right of HSS FE: 3a. Sh request (Note) + HSS FE->>UDM: 3a. Sh request (Note) + Note right of UDM: Network Procedure: Namf_MT_ProvideDomainSelectionInfo + UDM-->>HSS FE: 4a. Sh answer (Note) + +``` + +Sequence diagram illustrating User identity to HSS FE identity or UDM identity resolution for IMS AS. The diagram shows four lifelines: IMS AS, IMS HSS/SLF, HSS FE, and UDM. The sequence of messages is: 1. Dh/Sh request (Network procedure: T-ADS) from IMS AS to IMS HSS/SLF; 2. Redirect info from IMS HSS/SLF to IMS AS; 3. Sh request from IMS AS to HSS FE; 4. Sh answer from HSS FE to IMS AS; 3a. Sh request (Note) from HSS FE to UDM; 4a. Sh answer (Note) from UDM to HSS FE. Annotations include 'location server lookup' for step 2, 'Network Procedure: NPLI request over S6a' for step 4, and 'Network Procedure: Namf\_MT\_ProvideDomainSelectionInfo' for step 4a. + +Figure 6.5.3.5.3-1: User identity to HSS FE identity or UDM identity resolution for IMS AS + +NOTE 2: This assumes that UDM implements the Sh operations UDR/UDA to trigger the T-ADS information retrieval procedure. Potential conversion of Diameter Sh operation to an Nudm service operation is out of the scope of this study. + +### 6.5.4 Impacts on existing services and interfaces + +#### 6.5.4.1 General + +This solution addresses scenarios in which the operator deployment is already a layered architecture according to TS 23.335 [3]. Non-layered scenarios would need to migrate towards a layered architecture prior to deploying this solution. + +The solution is basically an operator choice restricted to the introduction of a Data Access Layer with the capabilities described in clauses 6.5.3.1 to 6.5.3.4, and does not impact the specified interfaces with new operations. + +The solution is also based on network configuration, by including SLF functionality for every IMS operation directed towards a location server (either HSS FE, IMS HSS or UDM). The SLF is configured as the contact point for I-CSCF, S-CSCF and IMS AS, and needs to be provisioned with the list of location servers serving the UEs in the network. + +The solution proposes to add information regarding the system registration status, i.e. the system serving the UE: + +- For 5G profile, this extension can be handled as the resources Amf3GppAccessRegistration and AmfNon3GppAccessRegistration in the Nudr\_DM\_Update service operation as specified in TS 29.505 [9]. +- For 4G profile, this extension can be mapped to the repository field where MME reference is held. Since the organisation of data in the EPS UDR is not standardised, this mapping would be left for implementation. + +Finally, the solution proposes adding the Sh pair UDR/UDA (Diameter) to UDM as a temporary solution until IMS is adapted to service based architecture or any other solution is specified for T-ADS information retrieval by IMS. + +#### 6.5.4.2 Summary of impacts on UDM + +- For handovers without N26 support: + - Add configuration indication regarding support or not of dual registrations. +- For T-ADS information retrieval: Add Sh pair UDR/UDA in case of single and dual registrations: + - Add indication regarding default system for IMS Voice over PS for dual registration mode of operation. +- For P-CSCF restoration: + - For Option 1, no impact (i.e. make use of PCF based restoration or detection of failure by SMF/UPF). + - For Option 2: Add Cx pair SAR/SAA for P-CSCF restoration. + +#### 6.5.4.3 Summary of impacts on HSS FE + +No impact on network procedures. + +For handovers without N26 support: + +- Add configuration indication regarding support or not of dual registrations + +For T-ADS information retrieval in dual registration mode of operation: + +- Add indication regarding default system for IMS Voice over PS. + +Depending on operator choice either: + +- A new subscription/notification interaction between HSS FE and the Data Access Layer in order to be informed when a 5G UE that camped in the EPS has moved back to 5GS system (in order to trigger a cancel location procedure), or +- No impact expected, if alternative depicted in clause 6.5.3.4.2 is decided. + +#### 6.5.4.4 Summary of impacts on EPS UDR or 5G repository + +The impacts on the EPS UDR or 5G repository are left for implementation, since the protocols and technologies to access their data is implementation specific. + +### 6.5.5 Evaluation + +Solution 5 proposes an architecture that does not require direct interaction between the UDM and the HSS FE or interaction between EPS UDR and 5G UDR. + +The solution makes use of an adaptation layer, named Access Data Layer, that separates the applications front end logic from database technology/protocol in the back end repositories. + +The solution addresses all interworking scenarios depicted in TS 23.501 [6] and TS 23.502 [2], including support for IMS procedures. + +The advantages of this solution is that: + +- It addresses effective separation of HSS FE and UDM and EPS UDR from 5G UDR to enable multivendor deployments +- It avoids new interface and new operations specification between the HSS and UDM +- It is possible to introduce only UDM and 5G UDR when deploying a 5GS system, without having to update/upgrade either HSS FE or the EPS UDR, or having to introduce these functionalities in deployments with single core network. +- Standardisation effort is minimised and restricted to potential incorporation of Sh/Cx operations for UDM, in case FS\_eIMS5G study (TS 23.794 [14]) does not incorporate the changes needed for P-CSCF restoration and T-ADS information retrieval. +- Introduction of this solution does not impact other network functions that may be accessing the different repositories, while it provides the means to further split other network functions defined in Rel-15 (i.e. PCF/PCRF). + +The disadvantage of this solution is to making use of SLF functionality for IMS when some deployments may not be using it. + +Additionally, the Ud interaction which terminates on the 5GS UDR means that the structure of the notifications carried in Ud for this particular case remains proprietary, implying that the Data Access Layer needs to be implemented in alignment with the existing HSS FE and EPS UDR implementations. + +## 6.6 Solution #6: Deployment and coexistence without interworking between UDM and existing HSS + +### 6.6.1 Introduction + +This solution is applicable to Key Issue 1 and Key Issue 2. + +This solution proposes a deployment and coexistence alternative which avoids the need of specification of interworking procedures between UDM and the existing HSS. + +### 6.6.2 High-level Description + +This solution proposes an alternative for coexistence between UDM and HSS based on: + +- Deploying HSS and UDM in a single network entity, referred as Combined HSS/UDM, supporting interfaces and procedures specified for 5GC, EPC and IMS. +- UDM and HSS deployed in the Combined network entity may interact with a 5GS UDR that stores 4G/IMS/5G subscription data for 5G enabled users (when using a common repository). Alternatively, the Combined HSS/UDM may also use separate repositories for subscription data of 5G enabled users. +- The functions of the Combined HSS/UDM are provided by a single network entity, so that the interactions between HSS and UDM within the Combined entity are performed internally and therefore it is not required to define such interworking. +- The existing HSS and EPS UDR keep serving only 4G users. +- A routing solution routes Diameter EPC/IMS requests to either the Combined HSS/UDM for 5G enabled users or the existing HSS for 4G only users. This kind of solution can be achieved e.g. by using a network entity that provides SLF/DRA functionality and/or by local configuration in network entities interacting with HSS (e.g. + +configuring IMSI ranges in MME), and other alternatives may be possible. The routing solution includes redundancy mechanisms to prevent single point of failure issues. + +- There is no need of interworking between UDM and existing HSS out of the Combined network entity. +- The different options regarding deployment of subscription data repository are described below, gathering the considerations described previously. +- **Option 1:** A common repository is used for the Combined HSS/UDM. Subscription data of new 5G enabled users is directly provisioned in 5GS UDR. Subscription data of existing 4G users that becomes 5G enabled is relocated from existing EPS UDR to 5GS UDR. When and how the subscription data relocation is performed depends on the overall migration plan and the procedure designed for that purpose, and it is out of scope of the description of this solution. + +This option may be considered the most appropriate for a multivendor deployment, while providing centralization of subscription data, allowing consolidation of user profiles for a given user in a single repository. This consolidation simplifies provisioning process, providing a single point of provisioning and ensuring data consistency. + +It minimizes deployment impacts, providing a flexible network evolution to 5G while users become 5G enabled through subscription relocation according to plans and speed chosen by the operator. + +Additionally, this option may be considered to follow a smooth evolution of the subscription data repository used for 5G enabled users to a cloud native deployment. + +The figure 6.6.1-1 shows the network architecture using a common repository for the Combined HSS/UDM: + +![Figure 6.6.1-1: Coexistence of existing HSS and Combined HSS/UDM with common repository used by the Combined entity. The diagram shows a 'Common repository (4G/IMS/5G)' containing '5G subs data' and '4G/IMS subs data for 5G enabled users'. This repository is connected to a 'Combined HSS/UDM' via 'Nudr' and 'Ud' interfaces. The 'Combined HSS/UDM' is connected to a '5GC' via 'N8/N10/N21' and to a 'Routing function' via 'S6a/Cx/Sh'. The 'Routing function' is connected to an 'EPC' via 'S6a' and to an 'IMS' via 'Cx/Sh'. The 'EPC' is connected to the '5GC' via 'N26'. A separate 'EPS UDR (4G/IMS)' containing '4G/IMS subs data' is connected to an 'HSS' via 'Ud'. The 'HSS' is connected to the 'Routing function' via 'S6a/Cx/Sh'.](0ea87c5f55e5857d0969bc5ca36dccba_img.jpg) + +Figure 6.6.1-1: Coexistence of existing HSS and Combined HSS/UDM with common repository used by the Combined entity. The diagram shows a 'Common repository (4G/IMS/5G)' containing '5G subs data' and '4G/IMS subs data for 5G enabled users'. This repository is connected to a 'Combined HSS/UDM' via 'Nudr' and 'Ud' interfaces. The 'Combined HSS/UDM' is connected to a '5GC' via 'N8/N10/N21' and to a 'Routing function' via 'S6a/Cx/Sh'. The 'Routing function' is connected to an 'EPC' via 'S6a' and to an 'IMS' via 'Cx/Sh'. The 'EPC' is connected to the '5GC' via 'N26'. A separate 'EPS UDR (4G/IMS)' containing '4G/IMS subs data' is connected to an 'HSS' via 'Ud'. The 'HSS' is connected to the 'Routing function' via 'S6a/Cx/Sh'. + +**Figure 6.6.1-1: Coexistence of existing HSS and Combined HSS/UDM with common repository used by the Combined entity** + +- **Option 2:** Separate repositories are deployed for subscription data of 5G enabled users accessed by the Combined HSS/UDM. In this case, provisioning and/or subscription relocation to EPS UDR used by the Combined HSS/UDM is also needed. + +This option allows multivendor deployment for 5G enabled users and legacy users, as well as keeping open the way for the evolution of the subscription data repository used for 5G enabled users to a cloud native deployment. However, subscription data centralization is not achieved, and deployment, management and provisioning of subscription repositories becomes not optimal and complex. + +The figure 6.6.1-2 shows the network architecture using separate repositories for the Combined HSS/UDM: + +![Diagram illustrating the coexistence of existing HSS and Combined HSS/UDM with separate repositories. The diagram shows three user data repositories at the top: 5GS UDR (5G) with 5G subs data, EPS UDR (4G/IMS) with 4G/IMS subs data for 5G enabled users, and EPS UDR (4G/IMS) with 4G/IMS subs data. The 5GS UDR connects to a Combined HSS/UDM via the Nudr interface. The first EPS UDR connects to the Combined HSS/UDM via the Ud interface. The second EPS UDR connects to an HSS via the Ud interface. The Combined HSS/UDM connects to a 5GC via the N8/N10/N21 interface and to a Routing function via the S6a/Cx/Sh interface. The HSS connects to the Routing function via the S6a/Cx/Sh interface. The 5GC connects to the EPC via the N26 interface. The EPC connects to the IMS via the S6a interface. The IMS connects to the Routing function via the Cx/Sh interface.](db39acbd11df5eb7e79ab84562fb8f74_img.jpg) + +``` + +graph TD + subgraph TopRow [User Data Repositories] + UDR1[5GS UDR (5G) +5G subs data] + UDR2[EPS UDR (4G/IMS) +4G/IMS subs data for 5G enabled users] + UDR3[EPS UDR (4G/IMS) +4G/IMS subs data] + end + + UDR1 -- Nudr --> CHUDM[Combined HSS/UDM] + UDR2 -- Ud --> CHUDM + UDR3 -- Ud --> HSS + + CHUDM -- N8/N10/N21 --> 5GC + CHUDM -- S6a/Cx/Sh --> RF[Routing function] + HSS -- S6a/Cx/Sh --> RF + + 5GC -- N26 --> EPC + EPC -- S6a --> IMS + IMS -- Cx/Sh --> RF + +``` + +Diagram illustrating the coexistence of existing HSS and Combined HSS/UDM with separate repositories. The diagram shows three user data repositories at the top: 5GS UDR (5G) with 5G subs data, EPS UDR (4G/IMS) with 4G/IMS subs data for 5G enabled users, and EPS UDR (4G/IMS) with 4G/IMS subs data. The 5GS UDR connects to a Combined HSS/UDM via the Nudr interface. The first EPS UDR connects to the Combined HSS/UDM via the Ud interface. The second EPS UDR connects to an HSS via the Ud interface. The Combined HSS/UDM connects to a 5GC via the N8/N10/N21 interface and to a Routing function via the S6a/Cx/Sh interface. The HSS connects to the Routing function via the S6a/Cx/Sh interface. The 5GC connects to the EPC via the N26 interface. The EPC connects to the IMS via the S6a interface. The IMS connects to the Routing function via the Cx/Sh interface. + +**Figure 6.6.1-2: Coexistence of existing HSS and Combined HSS/UDM with separate repositories deployed for the Combined entity** + +- **Option 3:** Separate repositories are used and the existing EPS UDR keeps storing 4G/IMS subscription data for 5G enabled users as well as 4G only users, as shown in figure 6.6.1-3. Subscription relocation is not required in this option. + +Both the existing HSS and the HSS within the Combined entity interact with the EPS UDR using the same proprietary Ud interface, implying that a multivendor deployment will require integration of the non-standard Ud interface with the HSS in the Combined HSS/UDM. + +This option does not allow centralization of user profiles for a given user in a single repository, making provisioning more complex as multiple subscription repositories are required to be populated for the same user. + +It enables evolution of subscription repository to cloud native technology only for the 5G profiles. EPC and IMS profiles are assumed to be kept in the existing EPS UDR using legacy repository technology. + +![Figure 6.6.1-3: Coexistence of existing HSS and Combined HSS/UDM with separate repositories using existing EPS UDR for 4G/IMS subscription data. The diagram shows two separate User Data Repositories (UDRs) at the top. The left one is the 5GS UDR (5G) containing 5G subs data. The right one is the EPS UDR (4G/IMS) containing 4G/IMS subs data for 5G enabled users and 4G/IMS subs data. Below the 5GS UDR is the Combined HSS/UDM, which connects to it via the Nudr interface. Below the EPS UDR is the HSS, which connects to it via the Ud interface. Both the Combined HSS/UDM and the HSS connect to a central Routing function via S6a/Cx/Sh interfaces. The Combined HSS/UDM also connects to the 5GC via N8/N10/N21 interfaces. The 5GC connects to the EPC via the N26 interface. The EPC and IMS both connect to the Routing function via S6a and Cx/Sh interfaces respectively.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) + +Figure 6.6.1-3: Coexistence of existing HSS and Combined HSS/UDM with separate repositories using existing EPS UDR for 4G/IMS subscription data. The diagram shows two separate User Data Repositories (UDRs) at the top. The left one is the 5GS UDR (5G) containing 5G subs data. The right one is the EPS UDR (4G/IMS) containing 4G/IMS subs data for 5G enabled users and 4G/IMS subs data. Below the 5GS UDR is the Combined HSS/UDM, which connects to it via the Nudr interface. Below the EPS UDR is the HSS, which connects to it via the Ud interface. Both the Combined HSS/UDM and the HSS connect to a central Routing function via S6a/Cx/Sh interfaces. The Combined HSS/UDM also connects to the 5GC via N8/N10/N21 interfaces. The 5GC connects to the EPC via the N26 interface. The EPC and IMS both connect to the Routing function via S6a and Cx/Sh interfaces respectively. + +**Figure 6.6.1-3: Coexistence of existing HSS and Combined HSS/UDM with separate repositories using existing EPS UDR for 4G/IMS subscription data** + +- **Option 4:** Another option is to deploy a single repository to store subscription data for all domains used by the Combined HSS/UDM and the existing HSS, as depicted in figure 6.6.1-4. This option may not require subscription relocation either. + +This alternative allows user profiles centralization, although in a multivendor deployment it will require integration of the non-standard Ud interface with the HSS in the Combined HSS/UDM. + +![Figure 6.6.1-4: Coexistence of existing HSS and Combined HSS/UDM using a common repository. The diagram shows a single Common repository (4G/IMS/5G) at the top, containing 5G subs data, 4G/IMS subs data for 5G enabled users, and 4G/IMS subs data. Below this repository, the Combined HSS/UDM connects via the Nudr interface for 5G data and the Ud interface for 4G/IMS data. The HSS also connects to the repository via the Ud interface. Both the Combined HSS/UDM and the HSS connect to a central Routing function via S6a/Cx/Sh interfaces. The Combined HSS/UDM connects to the 5GC via N8/N10/N21 interfaces. The 5GC connects to the EPC via the N26 interface. The EPC and IMS both connect to the Routing function via S6a and Cx/Sh interfaces respectively.](23cb65390082ab306c15bd3d8196135e_img.jpg) + +Figure 6.6.1-4: Coexistence of existing HSS and Combined HSS/UDM using a common repository. The diagram shows a single Common repository (4G/IMS/5G) at the top, containing 5G subs data, 4G/IMS subs data for 5G enabled users, and 4G/IMS subs data. Below this repository, the Combined HSS/UDM connects via the Nudr interface for 5G data and the Ud interface for 4G/IMS data. The HSS also connects to the repository via the Ud interface. Both the Combined HSS/UDM and the HSS connect to a central Routing function via S6a/Cx/Sh interfaces. The Combined HSS/UDM connects to the 5GC via N8/N10/N21 interfaces. The 5GC connects to the EPC via the N26 interface. The EPC and IMS both connect to the Routing function via S6a and Cx/Sh interfaces respectively. + +**Figure 6.6.1-4: Coexistence of existing HSS and Combined HSS/UDM using a common repository** + +### 6.6.3 Services and Illustrated Procedures + +The interactions between UDM and HSS within the Combined network entity are internal, so it is not required to define such interworking. + +### 6.6.4 Impacts on existing services and interfaces + +This solution has no impact on existing services and interfaces. + +### 6.6.5 Evaluation + +Solution 6 proposes a coexistence scenario where a Combined HSS/UDM network entity serving 5G enabled users can coexist without interaction with any existing HSS supporting EPC and IMS for 4G only users. Since there is no interaction needed between UDM and the existing HSS out of the Combined entity, this solution does not require any standardization effort. Additionally, this solution avoids any impact on existing nodes (HSS, EPS UDR), services, protocols and interfaces. Some options require migration of subscriber data. + +For IMS and EPC services, the solution requires the use of a routing solution which can be based on standard functions (e.g. DRA/SLF) and it is normally deployed in the operator's network for different purposes. Impacts are limited to provisioning/configuration updates for the routing function to route Diameter EPC/IMS requests to either the Combined HSS/UDM for 5G enabled users or the existing HSS for 4G only users. Supporting SMS and the relevant routing capabilities during normative phase + +This solution offers different UDR deployment alternatives, from which option 1 as described previously is considered the option providing the most future proof benefits in terms of centralization/consolidation of subscription data for 5G enabled users, management of subscription data, multivendor support and network evolution. + +However, an operator may find among the different alternatives proposed the option that fits better its network evolution plans, based on the current deployment and evaluation of the aspects the operator considers as most relevant. + +# --- 7 Evaluation + +## 7.1 Evaluation of solutions + +This study has emerged from the need of a multivendor approach for UDM and HSS nodes, currently not allowed by Release 15 specifications for 5GS, and facilitate scenarios in which introducing only UDM and UDR is an effective way to introduce 5GS. + +According to the Study Item objectives, this technical report has focused on scenarios involving co-existence of EPS subscriber data and 5GS subscriber data with common or separate storages, determining whether interaction between UDM and HSS is needed in the different interworking cases and deployment scenarios. + +Thus, the evaluation of the solutions focus on the following technical and deployment requirements: + +- Decoupling of UDM and HSS - with common/separate repository. +- Interworking scenarios fulfilment. +- Impacts (standardisation, deployment, etc. +- Limitations. + +In addition, and considering that specific scenarios exist in which UDM and/or HSS provide support to IMS procedures, the evaluation should as well take into account these interactions, considering that the evolution of IMS work in progress is independent from this study, but may incorporate additions to specific solutions addressed in this document. + +The following graph shows how the different solutions address the different key issues: + +![Figure 7.1-1: Solutions vs Key Issues. A 2x2 matrix diagram showing solutions for two key issues across two architectural models.](5e9af8986a5845504f251d3079da8078_img.jpg) + +| | | | +|-----------------------------------|-------------------------------------------|----------------------------| +| | Split UDM and HSS | Combo UDM/HSS | +| KI #2
Common
Repository | Solution #2
Solution #4 | Solution #6 | +| KI #1
Separate
Repositories | Solution #1
Solution #2
Solution #5 | Solution #3
Solution #6 | + +Figure 7.1-1: Solutions vs Key Issues. A 2x2 matrix diagram showing solutions for two key issues across two architectural models. + +**Figure 7.1-1: Solutions vs Key Issues** + +### 7.1.1 Evaluation of solutions with separation of FEs and repositories + +Solutions 1, 2 and 5 address key issue #1 for separation of repositories and front ends. + +- Solution #1 provides an implementation option not requiring standardisation for separating the front ends and to access the back end repositories independently. The implementation is based on a translation function used to access data from the different repositories in order to execute different network procedures in EPS or 5GS. + +For IMS procedures, it proposes implementing a lite Sh interface by UDM in order to support T-ADS information retrieval when UE is camped in the 5GS and, as an alternative for P-CSCF restoration via UDM, a lite Cx interface by UDM. + +**EVALUATION:** the solution can be considered an option for deployments with separate 5GS UDR and EPS UDR, accessed by UDM and HSS respectively. It can be suitable for scenarios of interworking in which full separation of front ends exist; however, for IMS interaction, the AS and S-CSCF impacts may not be feasible/acceptable in some deployments and a different solution may be selected. + +- Solution #2 implies standardisation of a service based interface between HSS and UDM, for separation of front ends, that access the back end repositories independently. + +The solution addresses separation of UDM from HSS, where HSS contains as well IMS logic. + +For IMS procedures, the solution proposes operations Cx/Sh-like as part of the service based interface to support T-ADS information retrieval and P-CSCF restoration via UDM. + +**EVALUATION:** the solution can be considered an option for deployments using EPS UDR and 5GS UDR separate repositories, accessed by an HSS containing several applications front end logic (i.e. IMS HSS, AuC, EPS HSS) via Ud and by UDM via Nudr respectively, and when converting HSS into an SBA entity is a suitable/feasible operator option. + +**OPEN POINTS** if conclusion is to progress during normative work: + +- The solution does not address cases in which the applications front end logic is split +- The solution does not address the case of IMS requests based on IMPU (e.g. T-ADS information retrieval) that need to be translated into SUPI in order to obtain the right information, either from the 5GS UDR or from the AMF. +- Solution #5 provides, similarly to solution #1, an implementation option for separating the front ends and accessing the back end repositories, with the difference that this solution is based on using notifications triggered by the repositories, at data modification related to a particular 5G enabled subscriber, in order to execute different network procedures in EPS or 5GS. + +The solution assumes full separation of all front ends, i.e. UDM, IMS HSS, EPC HSS, and AuC/ARPF. + +For IMS procedures, the solution proposes making use of the IMS SLF functionality and implementation of a lite Sh interface by UDM in order to support T-ADS information retrieval when UE is camped in the 5GS and, as an alternative for P-CSCF restoration via UDM, a lite Cx interface by UDM. + +**EVALUATION:** the solution can be considered an implementation option for deployments with separate 5GS UDR and EPS UDR, accessed by UDM and HSS or IMS HSS respectively. It can be suitable for scenarios of interworking in which full separation of front ends and repositories exist; however, for IMS interaction, the introduction of SLF functionality and use of Diameter interfaces in the UDM may not be feasible/acceptable in some deployments and a different solution may be preferred. In order to reduce the number of options to address during normative phase, this solution is proposed to not be pursued during the normative stage 2 work in Rel-16. + +### 7.1.2 Evaluation of solutions with separation of FEs with common repository + +Solutions 2 and 4 address key issue #1 for common repository with separation of front ends. + +- Solution #2 implies standardisation of a service based interface between HSS and UDM, for separation of front ends, that access the back end repository independently. + +The access to the common repository is performed by both Nudr and Ud interfaces. + +The solution addresses separation of UDM from HSS, where HSS contains as well IMS logic. + +For IMS procedures, the solution proposes lite Cx/Sh operations as part of the service based interface to support T-ADS information retrieval and P-CSCF restoration via UDM. + +**EVALUATION:** the solution can be considered an option for deployments reusing EPS UDR as common repository, accessed by an HSS containing all applications front end logic (i.e. IMS HSS, AuC, EPS HSS) via Ud, and by UDM via Nudr, and when converting HSS into an SBA entity is a suitable/feasible option for the operator. + +**OPEN POINTS** if conclusion is to progress during normative work: + +- The solution does not address cases in which the applications front end logic is split +- The solution does not address conversion of Nudr to Ud when the common repository is based on EPS UDR. +- The solution does not address the case of IMS requests based on IMPU (e.g. T-ADS retrieval) that need to be translated into SUPI in order to obtain the right information, either from the 5GS UDR or from the AMF. +- Solution #4 provides an implementation option for separating the front ends and accessing the common back end repository, i.e. the EPS UDR. The implementation is based of using notifications triggered by the repository in order to execute different network procedures in EPS or 5GS. + +The solution assumes full separation of all front ends, i.e. UDM, IMS HSS, EPC HSS, and AuC/ARPF. + +For IMS procedures, the solution proposes making use of the IMS SLF functionality and implementation of a lite Sh interface by UDM in order to support T-ADS information retrieval when UE is camped in the 5GS and, as an alternative for P-CSCF restoration via UDM, a lite Cx interface by UDM. + +**EVALUATION:** the solution can be considered an implementation option for deployments reusing EPS UDR as common repository, accessed by UDM, HSS or IMS HSS independently. It can be suitable for scenarios of interworking in which full separation of front ends exist; however, for IMS interaction, the introduction of SLF functionality and use of Diameter interfaces in the UDM may not be feasible/acceptable in some deployments and a different solution may be preferred. + +### 7.1.3 Evaluation of solutions with common FEs with separate repositories + +Solutions 3 and 6 address key issue #2 for separate repositories, with no separation of front ends. + +- Solution #3 implies no standardisation of interfaces between UDM and HSS FE, as UDM acts as a combo node that is the single point of contact for IMS, SMS, 5GC and EPC. + +The solution assumes UDM incorporates HSS FE interfaces (i.e. S6a, Sh, Cx/Dx, C/S6c), with no impact on legacy HSS. + +The EPC repository holds both 4G and IMS data, whilst 5GS UDR holds 5G data. The combo node UDM/HSS FE interfaces both 5GS UDR, via Nudr, and EPS UDR via legacy interface. + +**EVALUATION:** This solution can be considered a suitable solution in order to introduce 5G subscription data without impacting or migrating legacy subscription data already provisioned, or impacting legacy HSS. + +**OPEN POINTS** if conclusion is to progress during normative work: + +- The solution does not address the case of IMS requests based on IMPU (e.g. T-ADS retrieval) that need to be translated into SUPI in order to obtain the right information, either from the 5GS UDR or from the AMF. +- Solution #6 implies another combo node UDM/HSS FE, interfacing separate 5GS UDR and EPS UDR holding 5G and 4G/IMS data, respectively. + +The solution assumes coexistence of the combo UDM/HSS FE with legacy HSS/UDR (monolithic or layered) that keeps serving legacy 4G subscribers. + +The solution assumes impacts for migration of 4G/IMS profiles when separate repositories are used and requires the introduction of a Routing Function based on subscriber IMSI. + +**EVALUATION:** This solution can be considered as addressing the goals of the study as long as migration of legacy 4G data is acceptable for the 5G enabled subscribers. It does not require standardisation so normative work will not be pursued. + +### 7.1.4 Evaluation of solutions with common FEs with common repository + +Solutions 6 addresses the case of common repository and no separation of front ends. However, this solution does not address any of the goals of the study and thus it is not intended to be progressed as standardisation work. + +# --- 8 Conclusions + +## 8.1 For EPS and 5GS interworking required for mobility cases from EPS to 5GS and from 5GS to EPS, including the impacts on SMS handling + +Solution #2 is considered to progress as normative optional feature, both stage 2 and stage 3 for deployments in which upgrading legacy systems to service based architectures is a feasible/acceptable option for the network operator. A number of open issues listed in clause 7 need to be addressed during normative phase. + +CT WG4 is expected to take the responsibility of the normative specification work while SA WG2 will add relevant references in affected 5G specifications (TS 23.501 [6], TS 23.502 [2]). + +Solutions #3 and #6 are feasible alternatives in different scenarios where migration of subscription data or upgrades of legacy systems are not possible/feasible, and conclusion is to document them as implementation/deployment options, addressing the open issues in the relevant evaluation clauses. + +**Editor's note:** A 900 series TR will be created from this TR, to clearly document these solutions with reference to the CT WG4 TS for what relates to solution #2. + +## 8.2 For IMS and 5GS interworking required for T-ADS, P-CSCF restoration and NPLI retrieval + +Three different scenarios are addressed by the proposed solutions: + +- HSS as single point of contact for IMS (diameter based). + +- An UDM/HSS combo as single point of contact for IMS (diameter based). +- IMS HSS/SLF as single point of contact for IMS (diameter based). + +To facilitate this, conclusion is to progress normative work for new service(s) with new service Request-Response operation(s) produced by UDM: for T-ADS (i.e. IMS over PS support) and NPLI (i.e. time stamp and RAT type), and for P-CSCF restoration. The decision about the number of operations is left for normative work. + +The operations can be consumed by HSS (as in solution #2) for scenarios in which HSS is the single point of contact for IMS (diameter based) interactions and adapted to SBA. + +The operations can be consumed by an IMS HSS when in stand-alone mode and acting as a single point of contact for a diameter-based IMS. This case would correspond to solution #2 when the HSS referred acts as IMS HSS and is adapted to SBA. + +NOTE 1: These new operations require coordination with the normative work derived from FS\_eIMS5G (TS 23.794 [14]). + +NOTE 2: Any Modification of TS 23.228 [7] to clarify the interactions between HSS, UDM and IMS will be coordinated with any normative work arising from FS\_eIMS5G (TS 23.794 [14]). + +Solutions #3 and #6 are feasible alternatives and concluded to be documented as implementation/deployment options. + +**Editor's note:** A 900 series TR will be created from this TR, to clearly document these solutions with reference to the CT WG4 TS for what relates to solution #2. + +# --- Annex A: Change history + +| Change history | | | | | | | | | +|----------------|---------|-----------|----|-----|-----|-----------------------------------------------------------------|--|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | | New version | +| 2018-12 | SP#82 | SP-181099 | - | - | - | MCC editorial update for presentation to TSG SA#82 | | 1.0.0 | +| 2019-03 | SP#83 | SP-181099 | - | - | - | MCC editorial update for presentation to TSG SA#83 for approval | | 2.0.0 | +| 2019-03 | SP#83 | - | - | - | - | MCC editorial update for publication (Rel-16) | | 16.0.0 | \ No newline at end of file diff --git a/marked/Rel-16/23_series/23735/raw.md b/marked/Rel-16/23_series/23735/raw.md new file mode 100644 index 0000000000000000000000000000000000000000..afba79fb806ff9ed386782ed42b333aaac94c01e --- /dev/null +++ b/marked/Rel-16/23_series/23735/raw.md @@ -0,0 +1,613 @@ + + + + + + +# Contents + +| | | +|-------------------------------------------------------------------------------------------------------------------------------|----| +| Foreword ..... | 5 | +| 1 Scope..... | 5 | +| 2 References..... | 5 | +| 3 Definitions and abbreviations ..... | 6 | +| 3.1 Definitions..... | 6 | +| 3.2 Abbreviations ..... | 6 | +| 4 Stage 2 Requirements for enhancements of Public Warning System..... | 6 | +| 5 Key issues ..... | 7 | +| 5.1 Key Issue 1: Support of language-independent content mapped to an event or a disaster in a warning message ..... | 7 | +| 5.1.1 General description..... | 7 | +| 5.1.2 Open issues..... | 7 | +| 5.2 Key Issue 2: Identification of characteristics of an event or a disaster for UEs with no user interface..... | 8 | +| 5.2.1 General description..... | 8 | +| 5.2.2 Open issues..... | 8 | +| 5.3 Key Issue 3: Support of the relay of Warning Notification ..... | 8 | +| 5.3.1 General description..... | 8 | +| 5.3.2 Open issues..... | 8 | +| 6 Solutions..... | 9 | +| 6.1 Solution 1: Support of language-independent content mapped to an event or a disaster in a warning message ..... | 9 | +| 6.1.1 Description ..... | 9 | +| 6.1.2 Procedure..... | 9 | +| 6.1.3 Impacts on existing nodes and functionality ..... | 9 | +| 6.1.4 Solution Evaluation ..... | 9 | +| 6.2 Solution 2: Identification of characteristics of an event or a disaster for UEs with no user interface ..... | 10 | +| 6.2.1 Description ..... | 10 | +| 6.2.2 Procedure..... | 11 | +| 6.2.3 Impacts on existing nodes and functionality ..... | 11 | +| 6.2.4 Solution Evaluation ..... | 11 | +| 6.3 Solution 3: Support of the relay of Warning Notification..... | 11 | +| 6.3.1 Description ..... | 11 | +| 6.3.2 Procedure..... | 12 | +| 6.3.3 Impacts on existing nodes and functionality ..... | 12 | +| 6.3.4 Solution Evaluation ..... | 12 | +| 6.4 Solution 4: Support of a stored language-independent content referenced by a warning message ..... | 12 | +| 6.4.1 Description ..... | 12 | +| 6.4.2 Procedure..... | 12 | +| 6.4.3 Impacts on existing nodes and functionality ..... | 12 | +| 6.4.4 Solution Evaluation ..... | 13 | +| 6.5 Solution 5: Carrying characteristics of an event or a disaster for UEs with no user interface in the message payload..... | 13 | +| 6.5.1 Description ..... | 13 | +| 6.5.2 Procedure..... | 13 | +| 6.5.3 Impacts on existing nodes and functionality ..... | 13 | +| 6.5.4 Solution Evaluation ..... | 14 | +| 7 Conclusions and recommendations..... | 14 | +| 7.1 Conclusions ..... | 14 | +| 7.1.1 Key issue 1: Support of language-independent content mapped to an event or a disaster in a warning message..... | 14 | +| 7.1.2 Key issue 2: Identification of characteristics of an event or a disaster for UEs with no user interface ..... | 14 | +| 7.1.3 Key issue 3: Support of the relay of Warning Notification..... | 14 | +| 7.2 Recommendations..... | 14 | + +**Annex A:      Classification of disasters..... 15** +A.1   Statistic data per disaster type..... 15 +A.2   Classification of disaster group..... 16 +Annex B:      Change history..... 19 + +# --- Foreword + +This Technical Report has been produced by the 3rd Generation Partnership Project (3GPP). + +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 the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: + +Version x.y.z + +where: + +- x the first digit: + - 1 presented to TSG for information; + - 2 presented to TSG for approval; + - 3 or greater 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 document. + +# --- 1 Scope + +The present document studies and evaluates possible enhancements of Public Warning System(ePWS) to address the following objectives: + +- to develop stage 2 specifications to support stage 1 requirements on ePWS as follows + - 1) Specify how to support the language-independent contents (e.g. non-text based icon or image mapping to a disaster). In detail, this is to specify how to map the disaster by using symbols or images so that users can recognize the disaster in their screens. (It is a useful scenario for foreigners who do not know languages.) + - 2) Specify how to support UEs with no user interface or UEs with a user interface that is incapable of displaying text based warning notification. In detail, there is a specific requirement on UEs with no user interface or UEs with a user interface that can not display a text based warning notification. UEs with no user interface can be IoT device and it was intended that the device performs some dedicated actions when the warning notification is received. + - 3) Specify how to support relay functionality for providing warning notification. +- to develop stage 3 specifications to support stage 1 requirements on ePWS. + +No new functionality for US WEA and Japan ETWS will be introduced. + +# --- 2 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: "Vocabulary for 3GPP Specifications". + +- [2] 3GPP TS 22.268: "Public Warning System (PWS) requirements". + - [3] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". + - [4] 3GPP TS 23.038: "Alphabets and language-specific information". + - [5] ECONOMIC LOSSES, POVERTY & DISASTERS 1998-2017, CRED and UNISDR + - [6] [www.emdat.be/classification](http://www.emdat.be/classification) (as of 27th August 2019) + - [7] CAP v1.2: "Common Alerting Protocol, version 1.2" +- + +# 3 Definitions and abbreviations + +## 3.1 Definitions + +For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. + +## 3.2 Abbreviations + +For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. + +--- + +# 4 Stage 2 Requirements for enhancements of Public Warning System + +It is recognised that UEs with different or no user interface or with different roles (e.g. devices implemented as wrist bands with a tiny screen and a limited or no user interface, sensors that support a simple functionality such as the control for power on/off, or UEs with relay functionality) are on the market. In addition, as 5G brings the connected society with the application of the 3GPP system to non-ICT industry businesses, the number of such UEs in the market is expected to increase in the near future. + +In addition, the number of mobile users who internationally travel or live in other countries than their mother country without knowledge of the local language is increasing. So, other means than texts (e.g. globally standardised graphical symbols or images that are mapped to disasters or any event triggering to disseminate a Warning Notification) might be much more powerful and efficient to let such mobile users recognise what is happening from the Warning Notification they receive. UEs may have accessibility capabilities that help mobile users with disabilities (e.g. people with vision impairment) understand text-based and language-dependent Warning Notifications. Warning Notifications may also supplement current content of Warning Notification with additional content tailored to the needs of users with disabilities. + +Requirements described in clause 9 of 3GPP TS 22.268 [2] are specified to define behaviours suitable for UEs with no user interface (e.g. things with no display screen) or with a user interface incapable of displaying text-based Warning Notifications and to improve the comprehension of Warning Notification for UEs of users who are not fluent in the language of the Warning Notifications and UEs of users with disabilities who have UEs supporting assistive technologies beyond text assistive technologies. + +The relay functionality of UEs is specified to extend the coverage supported by 3GPP system. Requirements described in clause 10 of 3GPP TS 22.268 [2] are specified to define behaviors of UEs that play the role of a relay UE or a remote UE when receiving a Warning Notification via the relay functionality. + +In order to support requirements specified in clause 9 and clause 10 of 3GPP TS 22.268, the following requirements shall be addressed to enhance Public Warning System for UEs described above. + +- A Warning Notification shall be capable of supporting the inclusion of the information mapped to an event or a disaster that enables a UE with ePWS functionality to identify a warning message and render such information to the user. + +NOTE 1: How the information mapped to an event or a disaster included in a Warning Notification is rendered or displayed to a user depends on UE implementation unless the content to be displayed is provided from Warning Notification. + +NOTE 2: In case of a UE of a user who is not fluent about the language used in texts described in a Warning Notification, a language-independent content such as pictogram or Unicode symbol can be the information included in a Warning Notification. + +NOTE 3: In case of a UE of a user with disabilities that has a user interface providing accessibility extensions for such a user, the information mapped to an event or a disaster can be same as legacy texts that can be displayed in a better comprehensive way to such a user depending on UE implementation. + +- A Warning Notification shall be capable of supporting the inclusion of the information that enables UEs with no user interface (e.g. IoT devices such as an elevator, an automotive or a robot with no user interface that are connected to 3GPP networks) and with ePWS functionality to identify a warning message. + +NOTE 4: How a UE with no user interface and with ePWS functionality behaves depends on UE implementation when such a UE receives a Warning Notification. + +- A UE with ePWS functionality and the remote UE functionality shall be capable of receiving a Warning Notification transmitted from UEs with the relay functionality. +- A UE with ePWS functionality and with the relay functionality shall be capable of unconditionally forwarding a Warning Notification broadcast received from the network. + +# --- 5 Key issues + +## 5.1 Key Issue 1: Support of language-independent content mapped to an event or a disaster in a warning message + +### 5.1.1 General description + +A text-based warning message can be understood by mobile users who know the language used in a text-based warning message. For users such as foreigners who are not fluent about the language used in a warning message, it is necessary to enable a language-independent content (e.g. a unicode symbol) mapped to an event or a disaster to be included in or referenced by a warning message in order to improve the comprehension of a warning message by such users. + +### 5.1.2 Open issues + +The following aspect should be studied and considered in proposed solutions. + +- How to enable a language-independent content (e.g. a unicode symbol) mapped to an event or a disaster to be included in a warning message or referenced by a warning message to a stored language-independent content, e.g. the warning message might contain an identifier of an image of a disaster (e.g. typhoon or hurricane) that is stored on the device + +## 5.2 Key Issue 2: Identification of characteristics of an event or a disaster for UEs with no user interface + +### 5.2.1 General description + +A UE with no user interface (e.g. elevator) is not able to take specific actions by reading a text-based warning message. In addition, characteristics of an event or a disaster (e.g. water in case of flooding, wind in case of hurricane or water and wind in case of typhoon) could be more appropriate to be notified to a UE with no user interface as well as the severity of an event or a disaster than a name of a disaster from the perspective of a UE with no user interface, i.e. things. + +In addition, each country has different kind of disasters that are critical to each country for public safety so it is desirable to describe characteristics of an event or a disaster rather than the kind of an event or a disaster in a message identifier dedicated to UEs with no user interface. + +### 5.2.2 Open issues + +The following aspects should be studied and considered in proposed solutions. + +- How to enable UEs with no user interface and with ePWS functionality to identify characteristics of an event or a disaster from a Warning Notification +- How to describe characteristics of an event or a disaster in a Warning Notification in order to make UEs with no user interface and with ePWS functionality take specific actions based on the information of characteristics of an event or a disaster + +## 5.3 Key Issue 3: Support of the relay of Warning Notification + +### 5.3.1 General description + +The relay functionality is specified to extend coverage supported by 3GPP system. The relay of Warning Notification can be useful for users who are not able to receive warning messages and who are near the place where an event or a disaster is occurring. In addition, it is of critical importance to keep warning messages transmitted by authorities for a reasonable period of time in order to be able to relay them to other users who possibly have not had an opportunity to receive those warning messages. + +### 5.3.2 Open issues + +The following aspects should be studied and considered in proposed solutions. + +- How to enable remote UEs which support ePWS functionality and the reception of relayed Warning Notifications to receive Warning Notifications transmitted by a UE which supports the relay functionality +- How to enable a UE with the relay functionality and ePWS functionality to forward a Warning Notification that is received from a 3GPP network +- How to enable a UE which support ePWS functionality and the reception of relayed Warning Notifications that is out of network coverage to inquire of other UEs which support ePWS functionality as well as the relay functionality whether any Warning Notification messages have been received by the other UEs and to connect to such UE to receive those messages. + +# --- 6 Solutions + +## 6.1 Solution 1: Support of language-independent content mapped to an event or a disaster in a warning message + +### 6.1.1 Description + +This solution applies to Key Issue 1 – Support of language-independent content mapped to an event or a disaster in a warning message. + +Message identifiers related to additional languages (i.e. 4383 to 4395 and 4397) are specified for foreigners who do not know a local language in 3GPP TS 23.041 [3]. However, most countries do not support additional languages or they support or prepare for supporting only the English language. In some countries, a warning message with a message identifier related to a local language includes texts written in both the local language and an additional language (e.g. English). + +Considering conventional use of warning messages by authorities in different countries, it is necessary to enable language-independent content (e.g. a unicode symbol) to be included in a warning message for devices that have a conventional display screen that was assumed when legacy procedures of broadcasting warning messages were specified in 3GPP. + +### 6.1.2 Procedure + +The inclusion of the language-independent content mapped to an event or a disaster in a warning message should be supported over the legacy architecture of broadcasting warning messages. + +**NOTE:** Language-independent contents mapped to disasters need to be formatted to be suitable to be included in a warning message like texts. It may be a unicode symbol that are standardised in other standardisation bodies. It is desirable that standardised symbols mapped to disasters are applied in all countries that provides warning messages for public safety. This will make it possible for foreigners to intuitively understand the meaning of language-independent contents displayed to their devices. + +In order to include language-independent content such as unicode symbol, ISO is requested to define new characters mapping to specific pictograms that intuitively remind users of disasters. In addition, UEs with ePWS functionality should be capable of identifying such new characters if they are included in a warning message and displaying them to users. + +### 6.1.3 Impacts on existing nodes and functionality + +This solution is assumed to be applied over the legacy procedure and architecture and the language-independent content is assumed to be a compatible format as texts to be included in a warning message. + +So there is no impact on existing nodes and functionality in terms of the network architecture and network procedure of broadcasting warning messages. + +And this solution requires UEs with ePWS functionality to be capable of identifying new characters mapped to specific pictograms that represent disasters and displaying them to users. + +### 6.1.4 Solution Evaluation + +This solution solves Key Issue 1 based on legacy procedure and architecture of broadcasting warning messages over the 3GPP system. + +## 6.2 Solution 2: Identification of characteristics of an event or a disaster for UEs with no user interface + +### 6.2.1 Description + +This solution applies to Key Issue 2 – Identification of characteristics of an event or a disaster for UEs with no user interface. + +Things as devices capable of receiving warning messages, i.e. UEs with no user interface, were not assumed when the legacy procedure and architecture of broadcasting warning messages was specified in 3GPP. In near future, diverse forms of things as devices capable of receiving warning messages are expected to be launched in markets. + +However, legacy text-based warning messages can not be understood by UEs with no user interface and may be useless to make UEs with no user interface properly take actions for damage reduction or public safety when a legacy text-based warning message is received. + +So it is necessary to address how to make UEs with no user interface take actions for damage reduction or public safety when they receive the legacy form of a warning message broadcast over the legacy architecture of broadcasting warning messages. + +Disasters that may cause severe damages are different in countries (for example, hurricane causes severe damage in the east of the United State of America but there is no severe damage caused by hurricanes in Korea), which means that the finite set of disasters may not be possible to be listed. In addition, characteristics of disasters could be more useful information to be notified to things than the type of disaster. + +So it is desirable to define new message identifiers of warning messages targeted for things so that things can directly extract information on characteristics of a disaster from message identifiers. + +Legacy message identifiers specified in 3GPP TS 23.041 [3] are classified by following categories and support the indication of the risk level about a disaster to be alerted. + +- 4370 for a local language and 4383 for additional language: a warning message shall be always displayed. +- 4371 to 4379 for a local language and 4384 to 4392 for additional language: a warning message shall be displayed when a user selects opt-in option. + +- 1) In case of CMAS CBS messages, 4371 to 4379 and 4384 to 4392 are classified by severity, urgency and certainty. + - 2) In case of EU-Alert messages, 4371 to 4379 and 4384 to 4392 are classified by level 1, level 2 and level 3. +- 4352 for earthquake warning, 4353 for tsunami warning and 4354 for earthquake and tsunami warning by ETWS messages + +However, in most countries a single message identifier (e.g. 4371 in case of a local language) is conventionally used because authorities select high level of risk indications regardless of the risk level specified in 3GPP when a warning message is broadcast to users. Considering the conventional use of message identifiers, it might be good to simplify the risk level of disasters to be notified to things from authority's perspective as a user of public warning system. + +Therefore, it is desirable to define new message identifiers classified by following categories to inform things of characteristics of disasters. + +- one message identifier to make UEs with no user interface and with ePWS functionality always take action when a warning message is received +- A group of message identifiers (e.g. the group of three message identifiers) per the characteristic (e.g. water) of disasters to indicate the risk level of characteristics of a disaster to be alerted. For example, three message identifiers per the characteristic of disasters can be defined to mean: + - a) both severity and urgency are high; + - b) severity is high but urgency is not high; + - c) severity is not high but urgency is high. + +Considering the conventional use of message identifiers and the important information about a disaster from things' perspective to decide whether proper action shall be taken immediately when receiving a warning message, the definition of new message identifiers targeted for things, i.e. UEs with no user interface and with ePWS functionality, should be described to take into account all aspects addressed above. + +### 6.2.2 Procedure + +Message identifiers from 4400 to 6399 are reserved for future PWS versions. A single new message identifier should be defined to make UEs with no user interface and with ePWS functionality always take pre-defined actions when a warning message is received like 4370 and 4383 regardless of the type of disasters and characteristics of a disaster. + +Example of characteristics of disasters or events that may cause serious damage to things is water, fire, pressure, wind, dust, chemical material and electricity. New message identifiers should be defined per the characteristic of disasters. A group of a few (e.g. three) message identifiers may need to be defined per the characteristic of disasters and a few message identifiers among a group may need to be defined to indicate the risk level of the characteristics of a disaster. + +NOTE 1: What number of reserved message identifiers are allocated is to be decided when the normative work starts. + +NOTE 2: How many characteristics of disasters are classified will be studied and reviewed by a few countries if possible and is to be decided when the normative work starts. + +NOTE 3: How many message identifiers among a group of message identifiers mapped to one of combined characteristics of disasters will be studied (e.g. three message identifiers to indicate the risk level are sufficient or not) and reviewed by a few countries if possible. Then, it will be decided when the normative work starts. + +### 6.2.3 Impacts on existing nodes and functionality + +This solution is assumed to be applied over the legacy procedure and architecture, so there is no impact on existing nodes and functionality in terms of network architecture and network procedure of broadcasting warning messages except for defining new message identifiers from 4400 to 6399 reserved for future PWS versions. + +### 6.2.4 Solution Evaluation + +This solution solves Key Issue 2 based on legacy procedure and architecture of broadcasting warning messages over the 3GPP system. + +## 6.3 Solution 3: Support of the relay of Warning Notification + +### 6.3.1 Description + +This solution applies to Key Issue 3 – Support of the relay of Warning Notification. + +The relay functionality was initially specified in 3GPP from the demand of public safety domain and then, other 5G vertical domains also have such demands to address their issues over 5G system. In order to satisfy such demands from diverse vertical domains including public safety domain over 5G system, studies related to the relay functionality supported over 5G system are ongoing in 3GPP to be targeted to start a normative work in 3GPP Release 17 as follows. + +- FS\_REFEC (Study on enhanced Relays for Energy eFficiency and Extensive Coverage) for Stage 1 study in SA WG1 +- FS\_5G\_ProSe (Study on System enhancement for Proximity based Services in 5GS) for Stage 2 study in SA WG2 + +Considering current progress in 3GPP, devices with relay functionality and devices receiving relayed messages from devices with relay functionality are expected to be on market from 3GPP Release 17 onwards. So it is desirable not to specify solution 3 for support of the relay of Warning Notification in 3GPP Release 16 specification. + +### 6.3.2 Procedure + +NOTE: There is no specified procedure in 3GPP Release 16 because devices with relay functionality are expected to be on markets from 3GPP Release 17 onwards. + +### 6.3.3 Impacts on existing nodes and functionality + +There is no impact on existing nodes and functionality + +### 6.3.4 Solution Evaluation + +This solution solves Key Issue 3 based on legacy procedure and architecture of broadcasting warning messages over the 3GPP system. + +## 6.4 Solution 4: Support of a stored language-independent content referenced by a warning message + +### 6.4.1 Description + +This solution applies to Key Issue 1 – Support of language-independent content mapped to an event or a disaster in a warning message. + +It is recently recognised that devices incapable of displaying text-based warning messages (e.g. devices with an augmented reality-based user interface or devices with a hologram-based user interface) are expected to be launched. Considering the limited capacity of a warning message broadcast from authorities, legacy procedures for broadcasting warning messages do not allow contents to be properly displayed to such devices. + +Assuming that users have several devices capable of receiving warning messages broadcast from authorities, it is desirable to alert users by displaying a stored language-independent content referenced by a warning message. In such case, there might be the limit of the number of language-independent contents stored in devices incapable of displaying text-based warning messages because of the restriction of those devices (e.g. memory size). + +Devices incapable of displaying text-based warning messages, such as devices with a augmented reality-based user interface or devices with a hologram-based user interface, were not assumed when the legacy procedure and architecture of broadcasting warning messages was specified in 3GPP. In addition, legacy warning messages are broadcast with the single message identifier (e.g. 4371) in most countries that currently provide warning messages, + +regardless of the type and severity of disasters. So it is desirable to make a stored language-independent content of such device be referenced in order to be displayed to a user of such device when a warning message is received. + +### 6.4.2 Procedure + +Message identifiers specified for legacy UEs with the conventional display method (i.e. display screen to be able to present text-based warning messages) should be able to make UEs with ePWS functionality incapable of displaying text-based warning messages reference a stored language-independent content from such UEs when warning messages are received. + +UEs with ePWS functionality incapable of displaying text-based warning messages shall be capable of mapping message identifiers of received warning messages to contents stored in UEs with ePWS functionality. + +### 6.4.3 Impacts on existing nodes and functionality + +This solution is assumed to be applied over the legacy procedure and architecture by using legacy message identifiers to reference a stored language-independent content to be displayed to users. + +So there is no impact on existing nodes and functionality in terms of the network architecture and network procedure of broadcasting warning messages. + +And this solution requires UEs with ePWS functionality to be capable of mapping message identifiers of warning messages to contents stored in UEs with ePWS functionality. + +This solution does not require any changes of information sent over radio interface. + +How to manage a stored language-independent content is out of the scope of this solution and depends on the manufacturers' implementation. + +### 6.4.4 Solution Evaluation + +This solution solves Key Issue 1 based on legacy procedure and architecture of broadcasting warning messages over the 3GPP system. + +## 6.5 Solution 5: Carrying characteristics of an event or a disaster for UEs with no user interface in the message payload + +### 6.5.1 Description + +This solution applies to Key Issue 2 – Identification of characteristics of an event or a disaster for UEs with no user interface. + +Things as devices capable of receiving warning messages, i.e. UEs with no user interface, were not assumed when the legacy procedure and architecture of broadcasting warning messages was specified in 3GPP. In the near future, diverse forms of things as devices capable of receiving warning messages are expected to be launched in markets. + +However, legacy text-based warning messages cannot be understood by UEs with no user interface and may be useless to make UEs with no user interface properly take appropriate action when a legacy text-based warning message is received. + +Therefore, it is necessary to address how to make UEs with no user interface take appropriate actions when they receive the legacy form of a warning message broadcast over the legacy architecture of broadcasting warning messages. + +Disasters have different characteristics in different countries, which means that it may not be possible to list an exhaustive list of disasters, but characteristics of disasters could be more useful information to be notified to things than the type of disaster. + +The content of the message could be a CAP message, which would make the characteristics independent of 3GPP specifications. + +The CAP v1.2 [7] protocol provides a generic format to relay warning messages, but the format is in XML which needs to be compressed (economized) in order to relay it in a CB message. The message identifier would relate to the device class (e.g. a device that understands a CAP payload) and not to an event. + +### 6.5.2 Procedure + +Legacy Warning Message Delivery as specified in TS 23.041 [3] would be used but a specific message identifier would need to be allocated to identify messages that have a CAP payload. + +The CB Data element (payload of CB message) is populated with a compressed version of a CAP message. The compression format is out of scope of the present study. + +Alternatively, the CB Data element could consist of one or more numbers which could be the same as the message identifiers that would be allocated in solution 2 to identify event characteristics. + +### 6.5.3 Impacts on existing nodes and functionality + +There is no impact on existing nodes and functionality in terms of the network architecture and network procedure of broadcasting warning messages. + +This solution requires UEs with ePWS functionality to be capable of parsing the compressed CAP message in the CB Data element in order to take appropriate action. + +### 6.5.4 Solution Evaluation + +This solution is an alternative to solution 2. The information about the disaster is carried in the payload (i.e. CB Data element) rather than in the value of the message identifier. The CAP elements allow characterizing the disaster and also the action that needs to be taken. + +Adding new characteristics of events is done in the CAP payload and is flexible and independent of 3GPP specifications. + +# --- 7 Conclusions and recommendations + +## 7.1 Conclusions + +### 7.1.1 Key issue 1: Support of language-independent content mapped to an event or a disaster in a warning message + +Solution 1 and solution 4 are recommended for normative work to support language-independent content mapped to an event or a disaster in a warning message. + +### 7.1.2 Key issue 2: Identification of characteristics of an event or a disaster for UEs with no user interface + +Solution 2 is recommended for normative work to address the identification of characteristics of an event or a disaster for UEs with no user interface based on legacy procedure and architecture of broadcasting warning message over the 3GPP system. + +### 7.1.3 Key issue 3: Support of the relay of Warning Notification + +For key issue 3, it is recommended that no solution be specified for normative work in 3GPP Release 16 specification. + +## 7.2 Recommendations + +It is recommended to start the normative work based on the conclusions described in clause 7.1 to address key issues described in chapter 4. + +# Annex A: Classification of disasters + +## A.1 Statistic data per disaster type + +UNISDR (United Nations Office for Disaster Risk Reduction) which is now renamed as UNDRR (UN Office for Disaster Risk Reduction) published the report [5] by the collaboration with CRED (Centre for Research on the Epidemiology of Disasters) and its report describes the statistic data on what kind of disasters cause economic loss as well as human death in the world from 1998 to 2017. + +According to the report [5], the number of disasters per type from 1998 to 2017 is as follows. + +**Table A.1-1: Number of disasters per type from 1998 to 1997** + +| Disaster | Flood | Storm | Earthquake | Extreme temperature | Landslide | Drought | Wildfire | Volcanic activity | Mass movement (dry) | +|------------|-------|-------|------------|---------------------|-----------|---------|----------|-------------------|---------------------| +| Number | 3,148 | 2,049 | 563 | 405 | 378 | 347 | 254 | 99 | 12 | +| Percentage | 43.4% | 28.2% | 7.8% | 5.6% | 5.2% | 4.8% | 3.5% | 1.4% | 0.2% | + +In addition, pictograms mapped to disasters described in Table A.1-1 are described in the report [5]. + +Disaster type responsible for the majority losses in top 10 countries or territories is also provided in its report [5] as follows. + +**Table A.1-2: Disaster type responsible for the majority losses in top 10 countries or territories from 1998 to 1997** + +| Disaster | Earthquake | Earthquake & Tsunami | Storm | Extreme temperature | Flood | Drought | +|----------|------------|----------------------|-------|---------------------|-------|---------| +|----------|------------|----------------------|-------|---------------------|-------|---------| + +In addition, the number of people affected and the number of deaths per disaster type from 1998 to 2017 are also provided in its report [5] as follows. + +- The number of people affected per disaster type from 1998 to 2017 + - 1) Flood: 2.0 billion (45% of all disaster types) + - 2) Drought: 1.5 billion (33% of all disaster types) + - 3) Storm: 726 million (16% of all disaster types) + - 4) Earthquake: 125 million (3% of all disaster types) + - 5) Extreme temperature: 97 million (2% of all disaster types) + - 6) Wildfire, volcanic activity, mass movement (dry): 6.2 million (0.1% of all disaster types) + - 7) Landslide: 4.8 million (0.1% of all disaster types) +- The number of deaths per disaster type from 1998 to 2017 + - 1) Earthquake: 747,234 deaths (56% of all disaster types) + - 2) Storm: 232,680 deaths (17% of all disaster types) + - 3) Extreme temperature: 166,346 deaths (13% of all disaster types) + - 4) Flood: 142,088 deaths (11% of all disaster types) + - 5) Drought: 21,563 deaths (2% of all disaster types) + +- 6) Landslide: 18,414 deaths (1% of all disaster types) +- 7) Wildfire, volcanic activity, mass movement (dry): 2,398 deaths (0.2% of all disaster types) + +Based on the reported economic losses per climate-related disaster type and per geophysical disaster type, following list is also provided in its report [5] as follows. + +- Reporting of economic losses per disaster type (climate-related) + - 1) Storm: 55% reported + - 2) Wildfire: 41% reported + - 3) Flood: 32% + - 4) Drought: 29% + - 5) Landslide: 13% + - 6) Extreme temperature: 11% +- Reporting of economic losses per disaster type (geophysical) + - 1) Earthquake: 43% reported + - 2) Volcanic activity: 11% reported + - 3) Mass movement (dry): 8% + +## A.2 Classification of disaster group + +The classification of disaster group is defined in EM-DAT website by CRED website [6] as follows. + +The disaster group is classified into the group of natural disaster and the group of technological disaster. The group of natural disaster is classified as disaster subgroups described in Table A.2-1 and the group of technological disaster is classified as disaster subgroups described in Table A.2-2. + +**Table A.2-1: General classification of natural disaster group** + +| Disaster Subgroup | Definition | Disaster Main Type | +|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Geophysical | A hazard originating from solid earth. This term is used interchangeably with the term geological hazard. | Earthquake | +| | | Mass Movement (dry) | +| | | Volcanic activity | +| Meteorological | A hazard caused by short-lived, micro- to meso-scale extreme weather and atmospheric conditions that last from minutes to days | Extreme Temperature | +| | | Fog | +| | | Storm | +| Hydrological | A hazard caused by the occurrence, movement, and distribution of surface and subsurface freshwater and saltwater. | Flood | +| | | Landslide | +| | | Wave action | +| Climatological | A hazard caused by long-lived, meso- to macro-scale atmospheric processes ranging from intra-seasonal to multi-decadal climate variability | Drought | +| | | Glacial Lake Outburst | +| | | Wildfire | +| Biological | A hazard caused by the exposure to living organisms and their toxic substances (e.g. venom, mold) or vector-borne diseases that they may carry. Examples are venomous wildlife and insects, poisonous plants, and mosquitoes carrying disease-causing agents such as parasites, bacteria or viruses (e.g. malaria). | Epidemic | +| | | Insect infestation | +| | | Animal Accident | +| Extraterrestrial | A hazard caused by asteroids, meteoroids, and comets as they pass near-earth, enter the Earth's atmosphere, and/or strike the Earth, and by changes in interplanetary conditions that affect the Earth's magnetosphere, ionosphere, and thermosphere. | Impact | +| | | Space weather | + +**Table A.2-2: General classification of technological disaster** + +| Disaster Subgroup | Disaster Main Type | +|------------------------|--------------------| +| Industrial accident | Chemical spill | +| | Collapse | +| | Explosion | +| | Fire | +| | Gas leak | +| | Poisoning | +| | Radiation | +| | Oil spill | +| | Other | +| Transport accident | Air | +| | Road | +| | Rail | +| | Water | +| Miscellaneous accident | Collapse | +| | Explosion | +| | Fire | +| | Other | + +In addition, each disaster subgroup in case of the group of natural disaster is classified into several disaster sub-type and disaster sub-sub-type and it is also described in Table A.2-3 to Table A.2-8. + +**Table A.2-3: Classification of geophysical disaster subgroup** + +| Disaster Subgroup | Disaster Main Type | Disaster Sub-Type | Disaster Sub-Sub-Type | +|-------------------|---------------------|-------------------|-----------------------| +| Geophysical | Earthquake | Ground movement | | +| | | Tsunami | | +| | Mass Movement (dry) | Rock fall | | +| | | Landslide | | +| | Volcanic activity | Ash fall | | +| | | Lahar | | +| | | Pyroclastic flow | | +| | | Lava flow | | + +**Table A.2-4: Classification of geophysical disaster subgroup** + +| Disaster Subgroup | Disaster Main Type | Disaster Sub-Type | Disaster Sub-Sub-Type | +|-------------------|---------------------|--------------------------|-----------------------| +| Meteorological | Storm | Extra-tropical storm | | +| | | Tropical storm | | +| | | Convective storm | | +| | | Derecho | | +| | | Hail | | +| | | Lightning/thunderstorm | | +| | | Rain | | +| | | Tornado | | +| | | Sand/dust storm | | +| | | Winter storm/blizzard | | +| | Extreme Temperature | | Storm/surge | +| | | | Wind | +| | | | Severe storm | +| | Fog | Cold wave | | +| | | Heat wave | | +| | | Severe winter conditions | Snow/ice | +| | | Frost/freeze | | + +**Table A.2-5: Classification of hydrological disaster subgroup** + +| Disaster Subgroup | Disaster Main Type | Disaster Sub-Type | Disaster Sub-Sub-Type | +|-------------------|--------------------|---------------------------------------------|-----------------------| +| Hydrological | Flood | Coastal flood | | +| | | Riverine flood | | +| | | Flash flood | | +| | | Ice jam flood | | +| | Landslide | Avalanche (snow, debris, mudflow, rockfall) | | +| | Wave action | Rogue wave | | +| | | Seiche | | + +**Table A.2-6: Classification of climatological disaster subgroup** + +| Disaster Subgroup | Disaster Main Type | Disaster Sub-Type | Disaster Sub-Sub-Type | +|-------------------|-----------------------|----------------------------------|-----------------------| +| Climatological | Drought | | | +| | Glacial Lake Outburst | | | +| | Wildfire | Forest Fire | | +| | | Land fire : Brush, bush, pasture | | + +**Table A.2-7: Classification of biological disaster subgroup** + +| Disaster Subgroup | Disaster Main Type | Disaster Sub-Type | Disaster Sub-Sub-Type | +|-------------------|--------------------|-------------------|-----------------------| +| Biological | Epidemic | Viral disease | | +| | | Bacterial disease | | +| | | Parasitic disease | | +| | | Fungal disease | | +| | | Prion disease | | +| | Insect infestation | Grasshopper | | +| | | Locust | | +| | Animal Accident | | | +| | | | | + +**Table A.2-8: Classification of extraterrestrial disaster subgroup** + +| Disaster Subgroup | Disaster Main Type | Disaster Sub-Type | Disaster Sub-Sub-Type | +|-------------------|--------------------|---------------------|-----------------------| +| Extraterrestrial | Impact | Airburst | | +| | Space weather | Energetic particles | | +| | | Geomagnetic storm | | +| | | Shockwave | | + +# Annex B: Change history + +| Change history | | | | | | | | +|----------------|---------|-----------|----|-----|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| +| Date | Meeting | TDoc | CR | Rev | Cat | Subject/Comment | New version | +| 2018-11 | | | | | | Initial draft | 0.0.1 | +| 2018-12 | CT1#113 | | | | | Implementation of the following P-CRs from CT1#113:
C1-188811, C1-188812, C1-188813.
Editorial changes by rapporteur. | 0.1.0 | +| 2019-01 | CT1#114 | | | | | Implementation of the following P-CRs from CT1#114:
C1-190385, C1-190386, C1-190387, C1-190650,
C1-190651.
Editorial changes by rapporteur. | 0.2.0 | +| 2019-04 | CT1#116 | C1-192461 | | | | Clarification on the description of the clause 4 | 0.3.0 | +| 2019-04 | CT1#116 | C1-192462 | | | | Clarification on the description of the clause 5.1 and the clause 5.2 | 0.3.0 | +| 2019-04 | CT1#116 | C1-192463 | | | | Clarification on the description of the clause 5.3 | 0.3.0 | +| 2019-04 | CT1#116 | C1-192464 | | | | Solution 1 for the support of a language-independent content mapped to an event or a disaster in a warning message and Solution 4 for the support of a stored language-independent content referenced by a warning message | 0.3.0 | +| 2019-04 | CT1#116 | C1-192797 | | | | Solution 2 for the identification of characteristics of an event or a disaster for things with no user interface | 0.3.0 | +| 2019-04 | CT1#116 | C1-192148 | | | | Solution 3 for support of the relay of Warning Notification | 0.3.0 | +| 2019-06 | CT-84 | CP-191149 | | | | Version 1.0.0 presented for information to TSG CT | 1.0.0 | +| 2019-08 | CT1#119 | C1-194730 | | | | Solution for carrying characteristics of an event or a disaster for UEs with no user interface in the message payload | 1.1.0 | +| 2019-08 | CT1#119 | C1-194732 | | | | pCR on Annex A (Informative) | 1.1.0 | +| 2019-08 | CT1#119 | C1-194731 | | | | pCR on solutions in clause 7.1 | 1.1.0 | +| 2019-08 | CT1#119 | C1-194125 | | | | pCR on recommendations in clause 7.2 | 1.1.0 | +| 2019-09 | CT#85 | CP-192086 | | | | Presentation for approval at TSG CT | 2.0.0 | +| 2019-09 | CT#85 | | | | | Version 2.0.0 created after approval | 16.0.0 | \ No newline at end of file